5G Anchor Non-Relocation Security Key Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication systems face challenges in securely handling security key refreshes during RRC inactive state resume procedures without anchor node relocation, particularly in 5G networks, where existing techniques are not applicable for anchor non-relocation scenarios.

Innovation Solution

The proposed solution involves methods and apparatus for securely handling security key refreshes during RRC inactive state resume procedures by deriving new security keys without anchor node relocation, using techniques such as horizontal and vertical key derivation, and providing indications within messages to ensure proper key usage by user equipment (UE) and base stations, enabling secure communication even when the PDCP anchor location does not change.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing key refresh techniques are used during RRC inactive state resume procedures, then security can be maintained in anchor relocation scenarios, but the techniques are not applicable for anchor non-relocation scenarios and require additional network signaling

Engineering Contradiction:
ImprovesecurityVSAvoidapplicability to anchor non-relocation scenarios
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent changes the key derivation parameters by introducing a new indicator field that specifies whether anchor relocation occurred. This allows the same key refresh mechanism to adapt to both anchor relocation and non-relocation scenarios by modifying the derivation input parameters rather than creating separate mechanisms.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent creates a universal key refresh mechanism that handles both anchor relocation and non-relocation scenarios through a single standardized procedure. The mechanism uses an indicator field to differentiate between scenarios, allowing one system to serve multiple functions without requiring separate specialized procedures.

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

2Reliability

If existing key refresh techniques are used during RRC inactive state resume procedures, then security can be maintained, but network signaling costs increase due to additional messages required

Engineering Contradiction:
ImprovesecurityVSAvoidnetwork signaling costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges the key refresh operation with the existing RRC resume procedure by incorporating the key derivation and verification steps into the ongoing message exchange. Rather than adding separate key management messages, the solution combines security operations with the resume signaling flow, reducing overall signaling overhead.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent enables the UE to autonomously derive the appropriate security key using locally available information (stored security context and the indicator field received in the resume message). This self-service approach eliminates the need for additional key distribution or verification messages between network and UE, reducing signaling requirements.

Inventive Principle:
Principle #25Self-service

3Reliability

If existing key refresh techniques are used during RRC inactive state resume procedures, then security can be maintained in anchor relocation scenarios, but UE behavior becomes more complex

Engineering Contradiction:
ImprovesecurityVSAvoidUE behavior complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an indicator field as an intermediary element that carries information about anchor relocation status from the network to the UE. This single-bit indicator simplifies the UE's decision-making process by providing explicit guidance on which key derivation path to follow, eliminating the need for complex UE-side analysis of whether anchor relocation occurred.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3811677B1Anchor non-relocation handling in 5g
Publication Date: 2023.04.19 QUALCOMM INC
  • EP3811677B1 patent drawingFigure 1
  • EP3811677B1 patent drawingFigure 2
  • EP3811677B1 patent drawingFigure 3

AI summary

Certain aspects of the present disclosure provide techniques and apparatus for anchor non-relocation security handling in 5G.