NFC Controller Application Routing for Multiple Execution Environments

The system segments the communication channel management by creating dedicated channels for each NFCEE. The NFC controller maintains multiple separate communication channels, one for each NFCEE, allowing independent activation and management. This segmentation enables the controller to handle multiple NFCEEs simultaneously while maintaining the low-latency advantage of pre-activated channels.

The NFC controller performs preliminary actions by pre-activating communication channels for each NFCEE before external reader requests arrive. This preliminary activation eliminates communication delays when requests are received, as the channels are already ready for immediate data exchange. The controller maintains a registry of available applications across NFCEEs to quickly route requests to the appropriate pre-activated channel.

The NFC controller acts as an intermediary that maintains a registry or mapping table of applications to their hosting NFCEEs. This intermediary structure allows the controller to identify which NFCEE hosts a requested application without the NFCEEs themselves needing to share their internal application data with each other. The registry serves as a centralized information hub that preserves security while enabling accurate routing.

The NFC controller performs multiple functions: it manages communication channels, maintains application location information, routes external reader requests to appropriate NFCEES, and preserves security boundaries. This multi-functional approach allows a single component to handle both the identification of application locations and the maintenance of privacy, eliminating the need for NFCEEs to directly share sensitive information.