基于主机的卡模拟如何处理AID(应用程序ID)? [英] How does Host-based Card Emulation deal with AID (Application ID)?

问题描述

我要编写基于Android 4.4(Kitkat)的基于主机的卡仿真(HCE)的付款应用程序，但在阅读此书后，我不理解AID(应用程序ID)和Android 4.4的HCE服务之间的过程文章基于主机的卡仿真.在清单文件中同时注册了付款"和其他"类别的应用程序ID之后，该AID还在哪里使用?或用于我们的书面HCE服务来识别然后执行我们的书面HCE服务中定义的任何内容?

I am gonna write a Payment Application based on Host-Based Card Emulation(HCE) of Android 4.4 (Kitkat) but I don't understand a process between AID (Application ID) and HCE service of Android 4.4 after I read this article Host-based Card Emulation. After we register an Application ID of both "Payment" and "Other" Category in the manifest file, Where else is the AID used? or It is used for Our written HCE service to recognize and then do whatever that define in our written HCE Service?

推荐答案

还是用于我们的书面HCE服务来识别然后执行我们的书面HCE服务中定义的所有内容?

or It is used for Our written HCE service to recognize and then do whatever that define in our written HCE Service?

是这种情况.您在清单文件中注册您的AID.如果读者选择了您的AID，则NfcService就会知道要启动哪个HCE服务并向其分发APDU传输.

This is the case. You register your AID in the manifest file. If a reader selects your AID the NfcService then knows which HCE-service to start and to dispatch APDU transfers to.

所有进一步的通信将被路由到您的HCE服务，直到阅读器选择其他AID或阅读器停止提供RF字段为止.

All further communication will then get routed to your HCE Service until the reader selects a different AID or the reader stops providing the RF field.

这篇关于基于主机的卡模拟如何处理AID(应用程序ID)?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！