RRC Resume Security Context Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication networks, particularly in 5G NR, the RRC resume procedure can fail due to network rejection or integrity check failures, leading to synchronization issues between the UE and network security contexts.
Innovation Solution
The UE is designed to revert to an old security context upon a failed RRC resume procedure, ensuring that new security keys are derived from the old keys, maintaining synchronization with the network security context.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE generates new security keys during RRC resume procedure, then security is enhanced, but synchronization with network security context is lost upon resume failure
Solution Approach 1:
The UE stores the old security context before generating new security keys during the RRC resume procedure. This preliminary storage enables the UE to revert to the old context if the resume fails, maintaining synchronization with the network without requiring complex key management changes.
Solution Approach 2:
The invention prepares a fallback security context in advance by storing the old security parameters before attempting to generate new ones. This cushioning mechanism ensures that if the resume procedure fails, the UE has a pre-prepared security context to revert to, preventing unrecoverable states.
2Reliability
If the UE attempts RRC resume multiple times with new security keys, then security is strengthened, but the UE enters an unrecoverable state when resume fails
Solution Approach 1:
The UE stores the old security context before attempting resume, preparing a fallback option in advance. This allows the UE to revert to a known good state if resume fails, preventing service interruptions and unrecoverable states while still allowing multiple resume attempts.
3Reliability
If the UE reverts to old security context upon resume failure, then synchronization is maintained, but security is potentially weakened
Solution Approach 1:
The UE stores the old security context in advance before generating new keys, but only reverts to it if the resume procedure fails. This preliminary storage with conditional reversion maintains both synchronization (by reverting on failure) and security (by attempting new keys first).
Solution Approach 2:
The UE monitors the outcome of the RRC resume procedure and provides feedback to its security management. If the resume succeeds, new security keys are used; if it fails, the UE feedback-triggered reversion to the old context ensures synchronization while maintaining security through conditional key usage.
Data Source
AI summary
A communication system including a host computer is provided herein. The host computer may include processing circuitry configured to provide user data and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network comprises a base station having a radio interface and base station processing circuitry. The base station processing circuitry configured to store a previously active security context for the UE, receive from the UE an RRCResumeRequest message including a security token, generate a temporary security context for the UE, use the temporary security context to verify the security token, send an RRC message to the UE, if no response to the RRC message is received from the UE, discard the temporary security context and retrieve the previously active security context. Thereafter, the base station transmits the user data for a host application.