Dynamic Secure Messaging NFC Tag Counter Encryption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Near-field communication (NFC) technologies lack security measures, particularly in reader devices that do not implement authentication or secure messaging protocols, leading to privacy concerns and the potential for data tracking and replay attacks, as they cannot verify the authenticity of data read from NFC tags.
Innovation Solution
A near-field communication target device that responds to read requests by transmitting messages with an unencrypted portion and an encrypted portion, where the encrypted portion includes a counter that increments with each read request, ensuring dynamic encryption and preventing tracking, and includes a unique identification code for the target device, which can only be decrypted by a backend server, thereby enhancing security without requiring mutual authentication or key knowledge by the reader device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If static encryption or MAC/signature is used on NFC tags, then data confidentiality and integrity are protected, but the system becomes vulnerable to replay attacks and tracking due to the static nature of the security mechanisms
Solution Approach 1:
The patent applies dynamics by transitioning from static encryption/MAC to dynamic encryption where the encryption key changes with each read operation. The target device generates a new encryption key for each communication session based on a seed value and counter, ensuring that previously captured encrypted data cannot be replayed. This dynamic key generation mechanism directly addresses the replay attack vulnerability while maintaining data authenticity verification.
Solution Approach 2:
The patent changes the encryption parameter (key) dynamically based on the counter value and seed. Each read operation increments the counter, which combined with the seed generates a unique encryption key for that specific operation. This parameter change ensures that the same plaintext will produce different ciphertexts in different sessions, preventing tracking and replay attacks while maintaining reliable authenticity verification.
2Reliability
If application specific keys and authentication protocols are implemented in reader devices, then data authenticity can be verified, but device complexity and key management burden increase significantly
Solution Approach 1:
The patent introduces a backend server as an intermediary that handles the complex key generation and management tasks. The target device stores only a seed value, and the backend server generates the actual encryption keys and manages the counter values. This distributes the complexity from the reader device to the server, allowing simple reader devices to perform authentication without possessing or managing complex keys, thus verifying authenticity while minimizing local device complexity.
Solution Approach 2:
The target device performs self-service by autonomously generating dynamic encryption keys locally using its stored seed and the received counter value. It does not need to store multiple keys or perform complex key exchange protocols. The device independently computes the encryption key for each session and uses it to encrypt/decrypt data, simplifying the reader device's role to just initiating reads and receiving encrypted responses, thereby reducing key management complexity while maintaining authentication capability.
3Ease of operation
If counter values and confidential data are transmitted in clear text, then the communication process remains simple, but privacy is compromised as attackers can read and track the data
Solution Approach 1:
The patent segments the message into two distinct parts: an unencrypted portion containing non-sensitive data (such as counter values or public identifiers) and an encrypted portion containing confidential data. The unencrypted portion can be processed and validated in clear text maintaining communication simplicity, while the encrypted portion protects privacy by preventing attackers from reading confidential information even if they intercept the transmission. This segmentation allows selective encryption of only the necessary sensitive elements.
4Object-affected harmful factors
If dynamic encryption with incrementing counter is implemented in target device, then tracking and replay attacks are prevented, but the encryption system becomes more complex
Solution Approach 1:
The patent implements dynamics through the incrementing counter mechanism that automatically changes the encryption key for each read operation. The counter starts at an initial value and increments with each successful read, ensuring that the encryption parameters are always dynamic. This prevents tracking because the same target device will produce different encrypted outputs at different times, and prevents replay attacks because old encrypted data becomes invalid as the counter advances. The automatic incrementing nature keeps the system manageable despite the dynamic complexity.
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 provides enhanced security by ensuring confidentiality and preventing tracking and replay attacks, as each read request generates a unique message, and the backend server can verify authenticity, limiting the attack window and protecting against unauthorized data usage.
Implementation Method 1
NFC uses electromagnetic induction, requiring a pair of loop antennas typically operating over the RF ISM band around 13.56 MHz
Data Source
Figure 1~2
Figure 3
AI summary
The disclosure relates to dynamic secure messaging using near-field communication. Example embodiments include a near field communication target device (102) configured to respond to a read request (202) transmitted by a reader device (101) by transmitting a message (204) comprising an unencrypted portion and an encrypted portion, the encrypted portion incorporating a counter that is incremented each time a read request is received.