NFC控制器和POS读卡器之间的初次握手 [英] Initial handshake between NFC controller and POS reader
问题描述
我有几个问题，当读者使用启动与HCE模拟NFC支付应用交易
I have few questions when the reader initiates the transaction with NFC emulated payment application using HCE
-
请问读者，与常规的非接触式卡的基础设施发送PPSE命令？
Does the reader send the PPSE command as with the regular contactless card infrastructure?
是否主机控制器以响应与PPSE AID的从路由表中列出的注册艾滋病list命令？
Does the host controller respond to PPSE command with the list of AID's from the registered AIDs listed in the routing table?
因此读者选择的AID后，主机控制器定向到适当的HCE服务？
So after the reader selects the AID, the host controller directs to the right HCE service?
请纠正我对上述概念的理解。
Please correct my understanding on the above concept.
推荐答案
这是EMV支付卡终端会的不的区别塑料卡，安全元件设卡或HCE仿真卡。在所有的情况下，它会说同样的协议。其实协议的取值作为EMV有几个不同的内核变种，讲（略）不同的协议与卡应用。但该分化是基于应用的变体和品牌（例如万事达EMV，万事达卡磁条，维萨等），而不是在外形/智能卡的硬件
An EMV payment card terminal will not distinguish plastic cards, secure element based cards or HCE emulated cards. In all cases it will speak the same protocol. Actually "protocols" as EMV has several different kernel variants that speak (slightly) different protocols with card applications. But that differentiation is based on application variants and brands (e.g. MasterCard EMV, MasterCard MagStripe, Visa, etc.) and not on form factor/"smartcard" hardware.
因此，一个非接触式EMV读者会选择任何类型的卡（塑料，SE，HCE等）的PPSE检测实际支付的应用程序。
So a contactless EMV reader will select the PPSE for any type of card (plastic, SE, HCE, etc.) to detect the actual payment application.
Android不跨preT的PPSE选择命令，因此，它不产生或发送可用的支付应用程序的列表。需要注意的是HCE支付应用程序是由用户通过设置界面选择，只有一个支付应用可以同时激活/访问。
Android does not interpret the PPSE selection command and, consequently, it does not generate or send a list of available payment applications. Note that HCE payment applications are selected by the user through the settings UI and only one payment application can be active/accessible at a time.
它留给应用程序来处理PPSE。因此，通常情况下，基于EMV标准HCE支付应用程序将注册为，支付应用程序AID和PPSE DF名。需要注意的是，从协议的角度看是有DF名和AID之间没有区别，所以你可以为它在你的主机APDU服务XML文件在为DF名称（2PAY.SYS.DDF01）的辅助过滤器注册其十六进制的ASCII重新presentation 325041592E5359532E4444463031 ：
It's left up to applications to handle the PPSE. So, typically, a HCE payment application based on EMV standards would register for both, the payment application AID and the PPSE DF name. Note that from a protocol perspective there is no difference between a DF name and an AID, so you can register for it in your host APDU service XML file with an AID filter for the DF name ("2PAY.SYS.DDF01") in its ASCII hexadecimal representation 325041592E5359532E4444463031:
<aid-filter android:name="325041592E5359532E4444463031" />
因此，您的主机APDU服务将需要处理PPSE选择命令并作出回应会的FCI包含在其可自由支配的数据模板的EMV支付应用程序列表。
Consequently, your host APDU service will need to handle the PPSE selection command and respond to it will an FCI that contains the list of EMV payment applications in its discretionary data template.
这篇关于NFC控制器和POS读卡器之间的初次握手的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
