Secure Element Wrapping NCI Packets in HCP for NFC
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In secure near field communication (NFC) architectures, the lack of direct communication between the application processor (AP) and the NFC controller poses challenges in exchanging NFC controller interface (NCI) packets, necessitating an intermediary secure element (SE) to ensure security, but this introduces protocol mismatches and inefficiencies.
Innovation Solution
Implementing a processor circuit with an application processor to generate NCI packets, a secure element to wrap these packets in host controller protocol (HCP) packets, and an NFC controller with a tunneling module to unwrap the HCP packets, enabling secure and efficient communication between the AP and the NFC controller.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a secure element is introduced as an intermediary between the AP and NFC controller, then security is improved, but communication efficiency and protocol compatibility deteriorate
Solution Approach 1:
The patent applies the intermediary principle by introducing a secure element (SE) as a mediator between the application processor and NFC controller. The SE receives NCI packets from the AP, wraps them in HCP packets, and forwards them to the NFC controller. This intermediary structure maintains security while enabling communication through protocol translation, resolving the contradiction between security requirements and communication efficiency.
2Productivity
If the AP communicates directly with the NFC controller, then communication efficiency is improved, but security deteriorates
Solution Approach 1:
The secure element serves as a necessary intermediary that prevents direct communication between the AP and NFC controller. By routing all communications through the SE, the system maintains security controls while enabling functional communication. The SE's role in wrapping and unwrapping packets ensures that security requirements are met without completely blocking communication efficiency.
3Reliability
If protocol translation through the secure element is implemented, then security is improved, but device complexity increases
Solution Approach 1:
The secure element is designed to handle protocol translation internally, masking the complexity from the AP and NFC controller. The SE maintains NCI firmware stacks and HCP protocol knowledge, performing automatic translation without requiring complex integration logic in other components. This concentrates complexity in the intermediary rather than distributing it throughout the system.
4Adaptability or versatility
If the secure element wraps NCI packets in HCP packets, then protocol compatibility is improved, but processing time increases
Solution Approach 1:
The secure element performs preliminary actions by maintaining NCI firmware stacks and pre-configuring protocol translation rules. By having the NCI stack already established and ready in the SE, the system avoids time-consuming protocol negotiations during actual communication. The wrapping process becomes a straightforward encapsulation operation rather than a complex translation task.
Data Source
AI summary
Communication techniques for a secure near field communication (NFC) architecture are described. In one embodiment, for example, a wireless communications device may comprise a processor circuit, an application processor (AP) for execution on the processor circuit to generate a near field communication controller interface (NCI) packet, a secure element (SE) to wrap the NCI packet in a host controller protocol (HCP) packet, and an NFC controller to receive the HCP packet, the NFC controller comprising a tunneling module to obtain the NCI packet by unwrapping the HCP packet. Other embodiments are described and claimed.