NFC Application Identification via Decoupled Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
It is challenging for NFC readers to distinguish between applications of individual commerce application providers when they use a common underlying NFC infrastructure and generic business rules, making it difficult for the second party to determine usage and manage licensing fees.
Innovation Solution
The technology allows commerce application providers to deploy applications with identifiers decoupled from the underlying AID, enabling the second party to determine usage without registering an AID for each deployment, and facilitates the use of a common underlying NFC infrastructure and general application-specific rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a common underlying NFC infrastructure is used by multiple commerce application providers, then device complexity is reduced and development costs decrease, but the ability to distinguish between individual applications and track usage becomes difficult
Solution Approach 1:
The patent segments the application identification function from the NFC infrastructure layer by implementing it at the application layer. Multiple commerce applications share the common NFC infrastructure (protocol layers, hardware) but are distinguished through separate application-specific identifiers and logic within the host device's operating system. This allows infrastructure simplification while maintaining application distinguishability.
Solution Approach 2:
The patent introduces a new dimension for application identification by using application-layer protocols and data structures rather than relying solely on traditional card emulation identifiers. The identification mechanism operates at a different logical layer (application layer vs. protocol layer), enabling distinction between applications without complicating the underlying NFC infrastructure.
2Measurement precision
If traditional AID-based routing is used to identify NFC applications, then application distinction is achieved, but each deployment requires unique AID registration increasing administrative overhead
Solution Approach 1:
The patent implements self-service application identification where the host device's operating system automatically generates and manages application identifiers locally. Applications register themselves with the OS without requiring external AID registration authorities. The system serves its own identification needs through built-in mechanisms that automatically assign unique identifiers to each commerce application based on their characteristics and deployment context.
Solution Approach 2:
The patent changes the identification parameter from traditional AID (Application Identifier) to application-layer identifiers that are generated and managed within the host device. This parameter change allows flexible, dynamic identification without the constraints of pre-registered AIDs, enabling easier deployment while maintaining precise application distinction through alternative identification mechanisms.
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 approach enables the management of various NFC-enabled applications based on a common infrastructure, reducing application development costs and allowing for efficient tracking of usage and licensing without relying on unique AIDs.
Implementation Method 1
the reader can generate an RF field that can power a target that does not require batteries
Data Source
AI summary
Communicating via near field communication (NFC) between a reader and an application on an NFC-enabled device. A point of sale (POS) device and a consumer's mobile communication device establish an NFC session in accordance with each of the protocol layers of both International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 14443 and ISO/IEC 7816 standards. A commerce application executing on the consumer's mobile communication device at a protocol layer above the ISO/IEC 14443 and ISO/IEC 7816 standards communicates a plurality of NFC application protocol data units (APDUs) to the POS device. At least one such APDU includes a consumer identifier. The consumer identifier includes a portion identifying the commerce application.