NFC Controller Routing Secure Element for Mobile Payments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current NFC technologies in mobile devices limit the functionality of the secure element (SE) to only payment transactions, restricting its use in other NFC modes such as Peer-To-Peer (P2P) and Reader/Writer modes, where security functions are not typically required, leaving devices vulnerable to malware and unauthorized data processing.
Innovation Solution
Implementing an NFC controller that determines whether a security function is required for each NFC operation mode, routing communications through the SE only when necessary, and using a remote server for provisioning the SE to ensure secure processing in modes that demand security, while allowing direct host processor handling in non-secure transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the secure element is restricted to only payment transactions, then the device maintains simplicity and security for critical functions, but the functionality and versatility of the secure element is limited and cannot support other NFC modes
Solution Approach 1:
The system dynamically routes NFC transactions based on the type of transaction and security requirements. The NFC controller determines whether to route transactions to the secure element or host processor in real-time, allowing the secure element to be selectively activated for specific NFC modes (card emulation, P2P, reader/writer) rather than being statically restricted to payments only.
Solution Approach 2:
Different security processing paths are applied to different NFC modes and transaction types. The system applies security element processing locally only when and where it is needed (specific NFC modes requiring security), while allowing direct host processor handling for other transactions, creating localized security enforcement rather than system-wide uniformity.
2Reliability
If the secure element is used for all NFC modes, then security is enhanced across all operations, but the device complexity increases and efficiency decreases for non-secure transactions
Solution Approach 1:
The NFC transaction processing is segmented into secure and non-secure paths. The NFC controller segments transactions based on their security requirements, routing only those requiring security (specific card emulation, P2P, or reader/writer modes) through the secure element, while allowing other transactions to proceed directly through the host processor without secure element involvement.
Solution Approach 2:
The NFC controller acts as an intermediary that mediates between the NFC transceiver and either the secure element or host processor. It determines the appropriate routing destination for each transaction based on security requirements, preventing direct routing of all transactions through the secure element while maintaining security where needed.
3Productivity
If the secure element is not available for non-payment NFC modes, then the device maintains efficiency for those modes, but security vulnerabilities arise from malware and unauthorized data processing
Solution Approach 1:
Security requirements for different NFC modes are predetermined and configured in advance. The system is pre-configured to recognize which NFC modes (card emulation, P2P, reader/writer) require security processing, allowing the NFC controller to automatically route these transactions through the secure element without real-time security analysis, maintaining efficiency while ensuring security.
Data Source
AI summary
A mobile device includes a wireless transceiver, a host processor, a secure element (SE), and a near field communication (NFC) system having an NFC transceiver and an NFC controller implementing a contactless front end. The contactless front end routes a near field communication related to a payment transaction between the NFC system and the SE without going to or from the host processor. The contactless front end routes a near field communication not related to a payment transaction, but requiring a security function, between the NFC system and the SE without going to or from the host processor. The contactless front end routes a near field communication not related to a payment transaction, and not requiring a security function, between the NFC system and host processor without going to or from the SE.