Wireless Key Identifier Sync for Replay-Safe Message Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Wireless communication devices face challenges in preventing replay attacks due to incorrect storage of keys and counters, leading to invalidation of valid messages, particularly in scenarios where the Authentication Server Function (AUSF) key and counters associated with Steering of Roaming (SoR) and User Equipment (UE) Parameters Update (UPU) are stored in different storage units.

Innovation Solution

The system compares first and second key identifiers and counters to identify mismatches, replacing the second key identifier and updating counters based on the mismatch, ensuring valid messages are not ignored and security is maintained without requiring new primary authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If keys and counters are stored in separate storage units (e.g., USIM and NVM), then security is improved through distributed storage, but key identifier mismatches occur leading to valid messages being ignored

Engineering Contradiction:
ImprovesecurityVSAvoidkey identifier mismatch
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system implements a feedback mechanism where the UE compares the first key identifier (generated from key stored in first storage unit) with the second key identifier (stored in second storage unit). When a mismatch is detected, the system triggers an update procedure to synchronize the key identifiers, ensuring future messages are properly recognized while maintaining the security benefits of distributed storage.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary comparison of key identifiers before processing messages. By proactively detecting potential mismatches between key identifiers from different storage units, the system prevents valid messages from being ignored and ensures proper synchronization is performed in advance, avoiding communication failures.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If key identifiers are frequently updated to prevent mismatches, then message recognition is improved, but system complexity and processing overhead increase

Engineering Contradiction:
Improvemessage recognitionVSAvoidkey management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Instead of continuously updating key identifiers, the system performs updates only when necessary - specifically when a mismatch is detected between the first and second key identifiers. This partial action approach maintains message recognition while avoiding unnecessary processing overhead and complexity associated with frequent updates.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The UE autonomously detects key identifier mismatches and triggers update procedures without requiring external intervention. The system self-manages the synchronization of key identifiers by comparing them and performing updates only when needed, reducing overall system complexity while maintaining high message recognition rates.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12627491B2Key and counter management in wireless systems
Publication Date: 2026.05.12 QUALCOMM INC
  • US12627491B2 patent drawing
  • US12627491B2 patent drawing
  • US12627491B2 patent drawing

AI summary

Disclosed are wireless communications systems and techniques. For example, a wireless communication device (e.g., a user equipment (UE)) compares a first key identifier (generated from a key stored in a first storage unit, such as a universal subscriber identity module) to a second key identifier (stored in a second storage unit, such as non-volatile memory) to identify a mismatch between the key identifiers. Based on the mismatch, the device replaces, in the second storage unit, the second key identifier. In some examples, the device verifies integrity of a message using the key, replaces the second key identifier with the first key identifier, and updates a counter based on the message. In a second illustrative example, the device replaces the key with a replacement key, replaces the second key identifier with the third key identifier based on the replacement key, and resets a counter.