RFID Proximity Verification Using Dynamic Response Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

RFID systems, such as those used in automotive key fobs and NFC credit cards, are vulnerable to relay attacks where attackers amplify and relay RF signals to gain unauthorized access, compromising authentication and system control.

Innovation Solution

Implement a method to verify remote device proximity by sending computational challenges via RF communication, determining a maximum acceptable latency for responses, and performing actions only if responses meet predefined criteria based on this latency, which is dynamically adjusted using context information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional RF authentication is used without latency verification, then the system is easier to operate and faster, but it becomes vulnerable to relay attacks

Engineering Contradiction:
Improvesecurity against relay attacksVSAvoidauthentication process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by sending a computational challenge to the remote device before completing authentication. The challenge includes instructions for the device to perform computations and return results within a specific time window, establishing a baseline for legitimate response times before the relay attack can occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts the maximum acceptable latency threshold based on context information such as location, time of day, and usage patterns. This dynamic adaptation allows the authentication system to remain secure while accommodating legitimate variations in response time, making the security mechanism adaptable rather than static.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If a fixed maximum latency threshold is used, then the authentication process is simpler, but it cannot adapt to contextual variations in legitimate response times

Engineering Contradiction:
Improveadaptation to contextual variationsVSAvoidlatency determination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms by continuously monitoring authentication outcomes and contextual information. Based on this feedback, it adjusts the maximum acceptable latency threshold for future authentication attempts, creating a self-learning system that improves its adaptability over time while maintaining operational simplicity.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes the latency parameter dynamically based on contextual factors such as geographic location, time of day, and device usage patterns. This allows the authentication threshold to adapt to legitimate variations in response times without requiring complex manual configuration or rigid fixed values.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If computational challenges are sent to verify proximity, then relay attacks are prevented, but the authentication process takes longer

Engineering Contradiction:
Improveproximity verification accuracyVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The computational challenge serves multiple functions simultaneously: it verifies the remote device's proximity through latency measurement, authenticates the device's identity, and tests the device's computational capabilities. This multi-functionality reduces the need for separate verification steps, minimizing overall authentication time while maintaining high reliability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system rushes through the authentication process by setting tight latency thresholds that require rapid response from the remote device. Legitimate devices that can process computations and return results within the specified time window are authenticated quickly, while relayed signals that arrive too late are automatically rejected, speeding up the overall process.

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS12619838B2Systems and methods for verifying remote device proximity in RFID systems
Publication Date: 2026.05.05 CENTURYLINK INTELLECTUAL PROPERTY LLC
  • US12619838B2 patent drawing
  • US12619838B2 patent drawing
  • US12619838B2 patent drawing

AI summary

Systems and methods for verifying remote device proximity in RFID systems are described. To reduce the risk of relay attacks, a terminal may determine a distance of a remote device from the terminal. The terminal may send a computational challenge to the remote device and determine whether a latency of the response is within a maximum acceptable latency, indicating that the remote device is within a maximum acceptable distance. The maximum acceptable latency may be dynamically determined based on context information, such as a time of day, that may be correlated with a likelihood of attempted unauthorized accesses. The terminal may determine whether to perform an action associated with the remote device based on whether the response was received within the maximum acceptable latency.