NFCC Discovery Notification Mechanism for NFC Host
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current NFC systems lack a mechanism for the device host (DH) to be informed of configuration preferences by a Near Field Communication Execution Environment (NFCEE) for RF discovery, leading to inefficient RF discovery processes.
Innovation Solution
The introduction of a mechanism where the NFC controller (NFCC) provides the DH with sufficient information, including RF technology, mode, and communication type preferences from the NFCEE, allowing the DH to generate an optimized RF discovery command.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the DH initiates RF discovery without NFCEE configuration parameters, then the discovery process can start immediately, but the NFCEE cannot ensure its preferred RF settings are used
Solution Approach 1:
The NFCEE's configuration parameters (RF technology, mode, communication type) are collected and stored in advance within the NFCC before the RF discovery process is initiated. This preliminary preparation ensures that when the DH requests RF discovery, the preferred settings are already available to be applied, eliminating the need for delays while maintaining preference accuracy.
Solution Approach 2:
The NFCC acts as an intermediary between the NFCEE and the DH. It receives configuration parameters from the NFCEE, stores them, and then provides these parameters to the DH when an RF discovery request is made. This intermediary role enables information flow from NFCEE to DH through the NFCC, allowing preference transmission without direct NFCEE-DH communication.
2Loss of information
If the NFCC stores configuration parameters from NFCEE, then the DH can be informed of preferences, but additional information management complexity is introduced
Solution Approach 1:
The NFCC is designed to perform multiple functions: it not only controls RF discovery operations but also serves as a storage repository for NFCEE configuration parameters and acts as an information intermediary. This multi-functionality consolidates what would otherwise require separate components, managing information complexity within the existing NFCC architecture.
Solution Approach 2:
The configuration parameters are nested within the NFCC's existing operational framework. The NFCEE preferences are stored as data structures within the NFCC's memory, integrated with its command processing logic. This nesting approach embeds the information management function within the existing control structure rather than adding external complexity.
3Reliability
If the DH generates RF discovery command with NFCEE parameters, then discovery is optimized for NFCEE, but the command structure becomes more complex
Solution Approach 1:
The RF discovery command structure is extended to include additional parameter fields for NFCEE preferences (RF technology type, operational mode, communication type). These parameters are appended or integrated into the existing command format, allowing the DH to specify multiple configuration options. The extended parameter structure enables precise configuration while maintaining a systematic command organization.
Data Source
AI summary
Aspects disclosed herein relate to providing a mechanism by which an NFCC (730) can provide a DH (734) with sufficient information to begin RF Discovery on behalf of a NFCEE (760). In one example, with a NFC device (700) a DH (734) may be equipped to receive (804) a discovery request notification from a NFCC (730) indicating a NFCEE (760) is requesting that the DH (734) perform a discovery process. The discovery request notification may include information formatted to simplify the creation of a RF discovery command. The DH (734) may further be equipped to determine (806) whether to generate the RF discovery command using the information included in the discovery request notification, generate (808) the DH (734) based discover command using the information included in the discovery request notification upon a determination to include the received information, and transmit (810) the RF discovery command to the NFCC (730).