HCE Technical Support provides a soft implementation of the SE path, the service is implemented in many ways, can use files, use the network, and even connect real se.
Support for HCE's test phone: It is now possible to determine the use of NXP PN547 as a CLF NFC mobile phone has reached the HCE. Currently available on the market are Sony Xperia Z2 and Samsung Galaxy S5.
A reference material: http://developer.android.com/guide/topics/connectivity/nfc/hce.html written in very meticulous:
1. HCE work at ISO 7816-4, which is ISO-DEP level . (Students who want to emulate the MIFARE tag wash their sleep.)
2. The dispatch of the order is done based on the system takeover selectbyname instruction and the aid that the HCE service registers with the system. HCE distribution is higher than SE, does not support logic channel, and does not support GP's aid partial match.
3.HCE launches as an Android service, responding to APDU through interface functions. You can configure multiple aid groups, which can be configured as a type – payment class or other class, which is used for system policies when AID conflicts. The payment class is made by setting the default app, while the other class is the UI popup selection prompt.
4. When the screen is off, HCE is not available, the screen is locked HCE can choose support, or you can choose to prompt the user to unlock and then support.
5. In the case of the terminal only HCE no SE, ISO 14443-3 of the non-connected parameters by Android takeover, UID use random number, do not use HCE to implement any UID-based ID card.
The 6.Open Mobile API does not have access to hce like Access SE.
Hce:host-based card emulation Android device-based Sim