NFC AID Proxy Domain Name Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing AID-based routing mechanisms in NFC systems face challenges in supporting multiple environments and applications, leading to inefficient deployment and compatibility issues, especially when multiple SEs and HCE environments coexist, due to memory constraints and the need for specific AID storage.
Innovation Solution
The implementation of an NFC AID proxy that maps domain names to actual AIDs, allowing for efficient communication between an NFC reader and an NFC-enabled application by determining the availability of applications on a user computing device and routing commands accordingly, using a data store that correlates domain names with corresponding AIDs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional AID-based routing mechanisms are used in NFC systems, then application communication can be established, but memory constraints and deployment complexity increase when multiple SEs and HCE environments coexist
Solution Approach 1:
The patent introduces an AID proxy as an intermediary component that mediates between the NFC reader and the actual applications. The proxy maintains a simplified routing table mapping domain names to AIDs, acting as a mediator that translates reader requests into appropriate application routing decisions, thereby reducing the complexity of direct routing tables while supporting multiple environments
Solution Approach 2:
The patent shifts the routing dimension from direct AID-based routing to domain name-based routing through the proxy. Instead of managing complex routing tables with multiple AIDs directly, the system uses domain names as a higher-level abstraction dimension, mapping them to AIDs through the proxy's data store, which simplifies the routing mechanism while maintaining versatility
2Adaptability or versatility
If extensive AID storage is implemented to support multiple applications, then application availability can be determined, but memory usage increases
Solution Approach 1:
The patent extracts the AID storage function from the routing mechanism and consolidates it into the AID proxy's data store. By separating this function, the main routing table can remain minimal while the proxy handles the actual AID mapping and storage, reducing overall memory requirements while maintaining application availability detection capabilities
Solution Approach 2:
The patent uses domain names as copies or representations of actual AIDs. Instead of storing all possible AIDs directly in routing tables, the system stores domain names as simplified references and uses the proxy to translate them to actual AIDs when needed, reducing the quantity of data that must be stored while maintaining full functionality
3Reliability
If frequent user intervention is required for application selection, then application routing can be precise, but user experience and operational efficiency deteriorate
Solution Approach 1:
The patent implements self-service by enabling the AID proxy to automatically determine which application should respond to a reader based on domain name matching. The system autonomously performs routing decisions without requiring user intervention, while maintaining accurate application routing through the proxy's intelligent domain name to AID mapping
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
This solution enables seamless communication and reduces the need for frequent user intervention by automatically selecting the appropriate application, supporting multiple applications and updates without modifying the reader, and optimizing memory usage by eliminating the need for extensive AID storage.
Implementation Method 1
NFC is a short-range radio frequency (RF) communication technology, typically operating at a distance of 10 cm or less between two communicating devices
Data Source
AI summary
Communicating via near field communication (NFC) between a reader and an application on an NFC-enabled device. The device receives, from a reader, a selection of an application identifier (AID) proxy of the device. The proxy receives, from the reader, a query (including domain name) directed to the availability of an application on the device. The proxy determines whether the domain name corresponds to an AID of an application on the device by reference to a data store relating each domain name of each application to a corresponding AID. When the domain determined to correspond to an AID of an application on the device, the device transmits a response to the reader indicating the AID corresponding to the domain name. The device receives, from the reader, selection of the transmitted AID. The application corresponding to selected AID communicates with the reader in an NFC application protocol data unit communication session.