User Equipment Context Handling for Wireless Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing wireless communication systems face challenges in efficiently managing user equipment (UE) contexts across different service modules and network entities, leading to limitations in service deployment, latency, and resource management.

Innovation Solution

The proposed method involves a UE transmitting a resume identifier (ID) and service indices to a radio access network (RAN) while in an inactive state, allowing for the retrieval of valid UE contexts from a discovery entity or RAN context storage, enabling flexible service deployment and reduced latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If UE contexts are stored in a single location (source gNB), then context retrieval is reliable, but service deployment flexibility and geographical coverage are limited

Engineering Contradiction:
Improveservice deployment flexibilityVSAvoidcontext retrieval reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The UE context is segmented into service-specific contexts that can be independently stored and managed. Each service module has its own context that can be retrieved separately, allowing different parts of the context to be distributed across multiple network entities (source gNB, target gNB, or RAN context storage), thus improving flexibility while maintaining reliability through selective retrieval.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A discovery entity is introduced as an intermediary that receives resume IDs from UEs and directs them to the appropriate network entity (source gNB, target gNB, or RAN context storage) that holds the valid UE context. This intermediary enables flexible service deployment across multiple locations while ensuring reliable context retrieval by routing to the correct storage location.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If UE contexts are retrieved from source gNB only, then context accuracy is high, but latency increases due to longer retrieval paths

Engineering Contradiction:
Improvecontext retrieval latencyVSAvoidcontext accuracy
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

UE contexts are pre-stored or cached in multiple locations including the source gNB, target gNB, and RAN context storage before they are needed. When a UE resumes service, the context can be retrieved from the nearest or most accessible location rather than always traveling back to the source gNB, significantly reducing retrieval latency while maintaining context accuracy through the use of valid, pre-cached contexts.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If all service modules share the same UE context, then resource management is simplified, but resource utilization efficiency decreases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidcontext management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The monolithic UE context is segmented into multiple service-specific contexts, each corresponding to a particular service module. This allows each service to have its own dedicated context resources that can be independently managed and utilized, improving resource utilization efficiency while the standardized segmentation approach keeps management complexity manageable through systematic organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The segmented service-specific contexts are designed with universal structures that can be applied across different service modules. Each context follows a standardized format with service-specific parameters, allowing the same context management mechanisms to be universally applied to all services while enabling efficient, dedicated resource allocation for each service type.

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

Data Source

PatentUS20250168752A1User equipment context handling
Publication Date: 2025.05.22 QUALCOMM INC
  • US20250168752A1 patent drawing
  • US20250168752A1 patent drawing
  • US20250168752A1 patent drawing

AI summary

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a radio access network (RAN) configuration for a plurality of service modules that correspond to a plurality of services and a plurality of service-specific UE contexts. The UE may transmit, while in an inactive state, a resume identifier (ID) and one or more service indices corresponding to one or more requested services of the plurality of services. The UE may receive a response indicating one or more valid services of the one or more requested services. The UE may transmit a communication associated with a valid service of the one or more valid services. Numerous other aspects are described.