ISO 7816-4: GET RESPONSE and ENVELOPE command
http://www.cardwerk.com/smartcards/smartcard_standard_ISO7816-4_7_transmission_interindustry_commands.aspx
7. Transmission-oriented Interindustry Commands
7.1 GET RESPONSE command
7.2 ENVELOPE command
It shall not be mandatory for all cards complying to this part of ISO/IEC 7816 to support all the described commands or all the options of a supported command.
When international interchange is required, a set of card system services and related commands and options shall be used as defined in clause 9.
Table 11 provides a summary of the commands defined in this part of ISO/IEC 7816.
The impact of secure messaging (see 5.6) on the message structure is not described in this clause.
The list of error and warning conditions given in each clause 7.X.5 is not exhaustive (see 5.4.5).
7.1 GET RESPONSE command
7.1.1 Definition and scope
7.1.2 Conditional usage and security
7.1.3 Command message
7.1.4 Reponse message (nominal case)
7.1.5 Status conditions
7.1.1 Definition and scope
The GET RESPONSE command is used to transmit from the card to the interface device APDU(s) (or part of the APDUs) which otherwise could not be transmitted by the available protocols.
7.1.2 Conditional usage and security
No condition.
7.1.3 Command message
Table 74 - GET RESPONSE command APDU
CLA | As defined in 5.4.1 |
INS | 'C0' |
P1-P2 | '0000' (other values are RFU) |
Lc field | Empty |
Data field | Empty |
Le field | Maximum length of data expected in response |
7.1.4 Response message (nominal case)
Table 75 - GET RESPONSE response APDU
Data field | (Part of) APDU according to Le |
SW1-SW2 | Status bytes |
7.1.5 Status conditions
The following specific normal processing may occur :
SW1='61' with SW2
- 'XX': Normal processing: more data bytes are available ('XX' indicates a number of extra data bytes still available by subsequent GET RESPONSE).
The following specific warning condition may occur :SW1='62' with SW2=
- '81': Part of returned data may be corrupted
The following specific error conditions may occur.
SW1='67' with SW2=
- '00': Wrong length (the Lc field is incorrect)
SW1='6A' with SW2=
- '86': Incorrect parameters P1-P2
SW1='6C' with SW2=
- 'XX': Wrong length (wrong Le field, 'XX' indicates the exact length)
7.2 ENVELOPE command
7.2.1 Definition and scope
7.2.2 Conditional usage and security
7.2.3 Command message
7.2.4 Reponse message (nominal case)
7.2.5 Status conditions
7.2.1 Definition and scope
The ENVELOPE command is used to transmit APDU(s) or part of APDUs or any data string which otherwise could not be transmitted by the available protocols.
NOTE - The usage of ENVELOPE for SM is shown in annex F .
7.2.2 Conditional usage and security
No condition.
7.2.3 Command message
Table 76 - ENVELOPE command APDU
CLA | As defined in 5.4.1 |
INS | 'C2' |
P1-P2 | '0000' (other values are RFU) |
Lc field | Length of the subsequent data field |
Data field | (Part of) APDU |
Le field | Empty of length of expected data |
When the ENVELOPE command is used under T=0 for transmitting data strings, an empty data field in an ENVELOPE command APDU means end of data string.
7.1.4 Response message (nominal case)
Table 77 - ENVELOPE response APDU
Data field | Empty or (part of) APDU according to Le |
SW1-SW2 | Status bytes |
NOTE - The status bytes belong to the ENVELOPE command. Status bytes of a command transmitted in the data field of the ENVELOPE command may be found in the data field of the ENVELOPE response.
7.2.5 Status conditions
The following specific error conditions may occur.
SW1='67' with SW2=
- '00': Wrong length (the Lc field is incorrect)
ISO 7816-4: GET RESPONSE and ENVELOPE command的更多相关文章
- ISO 7816-4: Interindustry Commands for Interchange
5. Basic Organizations 5.1 Data structures5.2 Security architecture of the card 5.3 APDU message str ...
- ISO 7810 协议小结
ISO 7816规定了Smart Card的传输协议分为 T=0 异步半双工字符传输协议 T=1 异步半双工块传输协议 T=0命令介绍 命令总是由接口设备启动,他以一个5字节的报头通知卡要做什么,然后 ...
- ISO 7816-4: Annex A: Transportation of APDU messages by T=0
http://www.cardwerk.com/smartcards/smartcard_standard_ISO7816-4_annex-a.aspx Annex A: Transportation ...
- request和response简介
Tomcat收到客户端的http请求,会针对每一次请求,分别创建一个代表请求的request对象.和代表响应的response对象. 既然request对象代表http请求,那么我们获取浏览器提交过来 ...
- 在Android中访问内置SE和基于SE的卡模拟(一)
2013-10-10 编写 前言 在“十问Android NFC手机上的卡模拟”文中仅仅简单的介绍了一下相关的概念,如果需要了解基于SE的卡模拟的更多细节,也就是,究竟在Android的NFC手机上, ...
- 智能卡 APTU命令
一条命令APDU含有一个头标和一个本体.本体可有不同长度,或者在相关数据字段为空时,整个可以不存 在. 头标由四个数据元组成,它们是类CLA(ClAss)字节,命令INS(INStructic,n)字 ...
- 基于Codeigniter框架实现的APNS批量推送—叮咚,查水表
最近兼职公司已经众筹成功的无线门铃的消息推送出现了问题,导致有些用户接收不到推送的消息,真是吓死宝宝了,毕竟自己一手包办的后台服务,影响公司信誉是多么的尴尬,容我简单介绍一下我们的需求:公司开发的是一 ...
- 使用WCF的Trace与Message Log功能
原创地址:http://www.cnblogs.com/jfzhu/p/4030008.html 转载请注明出处 前面介绍过如何创建一个WCF Service http://www.cnblo ...
- C#邮件接收系统核心代码(接收POP3邮件IMAP邮件)
/* * Created by SharpDevelop. * User: Administrator * Date: 2013/11/18 * Time: 20:55 * * To change t ...
随机推荐
- Maven私服安装及配置——(十二)
0.私服实际是B/S架构的,需要通过浏览器访问.访问地址在 nexus-2.12.0-01\conf\nexus.properties中查看.
- Implement Queue by Two Stacks & Implement Stack using Queues
Implement Queue by Two Stacks Implement the following operations of a queue using stacks. push(x) -- ...
- VCForPython27.msi安装后, 还显示error: Unable to find vcvarsall.bat
C:\Users\zpc\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\VC 增加环境变量: SET VCPYTH ...
- react-native 报错
报错信息: java.lang.RuntimeException: Unable to load script from assets 'index.android.bundle'. Make sur ...
- FormData介绍
FormData XMLHttpRequest Level 2添加了一个新的接口FormData.利用FormData对象,我们可以通过JavaScript用一些键值对来模拟一系列表单控件,我们还可以 ...
- 网络图片转换到本地并转换成base64位
/** * 网络图片转换到本地并转换成base64位 * @param $url * @return string */ public function imgzhuanhuan($url) { // ...
- Java编程的逻辑 (17) - 继承实现的基本原理
本系列文章经补充和完善,已修订整理成书<Java编程的逻辑>,由机械工业出版社华章分社出版,于2018年1月上市热销,读者好评如潮!各大网店和书店有售,欢迎购买,京东自营链接:http: ...
- CF 554B 找相同行
给定一个由n*n块地砖铺成的房间,每块砖用0表示未打扫,1表示已打扫. 要求打扫时只能整列地扫,未打扫的会变为已打扫,已打扫的会变为未打扫.即1会变成0,而0会变成1,目标是 使最后整行为1的行数最大 ...
- 用 scikit-learn 和 pandas 学习线性回归
用 scikit-learn 和 pandas 学习线性回归¶ from https://www.cnblogs.com/pinard/p/6016029.html 就算是简单的算法,也需要跑通整 ...
- 015 jquery中包裹节点
1.介绍 2.程序 <!DOCTYPE html> <html> <head> <meta charset="UTF-8"> < ...