基于主机的卡模拟-在读取器设备上读取HCE时触发读取器应用 [英] Host-based Card Emulation - Trigger a reader app when HCE is read on reader device

查看:73
本文介绍了基于主机的卡模拟-在读取器设备上读取HCE时触发读取器应用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

NFC标签可以触发电话上可用的NFC阅读器应用程序,但是HCE不会触发任何阅读器应用程序.但是,如果我首先打开阅读器应用程序,则它可以正常运行,因此可以读取HCE仿真标签.

NFC tags can trigger an NFC reader app available on the phone, but HCE does not trigger any reader app. However, if I first open the reader app, then it works normally and, hence, can read the HCE emulated tag.

我需要HCE可以打开或提示选择阅读器应用程序的解决方案.

I need a solution where HCE can open or prompt to choose the reader app.

HCE是否有可能?为什么在检测到HCE设备时Android不提示不打开NFC阅读器应用程序?

Is this possible with HCE? Why does Android not prompt to open an NFC reader app when detecting a HCE device?

推荐答案

否,一台Android设备上的HCE应用程序不能用于触发(启动)另一台Android设备上的阅读器应用程序.原因是Android设备还实现了对等模式.因此,默认情况下,两个Android设备将自动以对等模式进行通信,并且阅读器端将看不到HCE仿真标签.

No, a HCE app on one Android device cannot be used to trigger (launch) a reader app on another Android device. The reason for this is that Android devices also implement peer-to-peer mode. Thus, by default, two Android devices will automatically communicate in peer-to-peer mode and the reader side won't see the HCE emulated tag.

仅当在使用读取器模式API禁用对等模式的读取器端启动读取器应用程序时,两个设备才开始以读取器/写入器模式+卡仿真模式进行通信.因此,只有HCE仿真的标签才对阅读器端可见.

Only if a reader app is started on the reader side that uses the reader-mode API to disable peer-to-peer mode, the two devices start communicating in reader/writer mode + card emulation mode. Thus, only then the HCE emulated tag becomes visible to the reader side.

请注意,从设置菜单禁用Beam不会对此进行任何更改,因为即使Beam(对等模式之上,Android设备目前唯一使用的应用程序协议)也保持对等模式启用被禁用.

Note that disabling Beam from the settings menu won't change anything about this because peer-to-peer mode stays enabled even if Beam (currently the only application protocol used by Android devices on top of peer-to-peer mode) is disabled.

这篇关于基于主机的卡模拟-在读取器设备上读取HCE时触发读取器应用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆