UE Context Cookie Storage for Low-Signaling 5G Reattachment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 5G network solutions for minimizing signaling in IoT devices after long periods of inactivity are inefficient, as they require the UE to send a complete state representation, leading to increased data transmission and battery consumption, and do not adequately address the dynamic nature of 5G networks and the need for separate context storage across network slices.
Innovation Solution
Implementing a context cookie solution where UE context is stored in a separate Context Cookie Storage Function (CCSF) decoupled from the Common Control Network Function (CCNF), allowing for per-slice storage and retrieval of context information using indexed links and security tokens, minimizing data transmission and optimizing resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If UE context is stored in the network using existing 5G solutions, then connection reestablishment can be minimized, but the UE must send complete state representation leading to increased data transmission and battery consumption
Solution Approach 1:
The patent extracts only the essential context information (resume ID, security context, session information) from the complete UE state representation and stores it separately in the network. This allows the UE to transmit only this minimal context data during reconnection instead of the complete state representation, significantly reducing energy consumption while maintaining fast reestablishment capability
Solution Approach 2:
The patent segments the UE context into separate components: context data is stored in the network while the UE stores only minimal identification information. This segmentation allows selective transmission of only necessary context data during reconnection, reducing the data transmission burden on the UE and conserving battery life
2Loss of time
If UE context is stored in the network, then signaling can be minimized, but data transmission requirements increase for complete state representation
Solution Approach 1:
The patent extracts only the essential context information (resume ID, security context, session information) from the complete UE state representation and stores it separately in the network. This allows the UE to transmit only this minimal context data during reconnection instead of the complete state representation, significantly reducing energy consumption while maintaining fast reestablishment capability
Solution Approach 2:
The patent creates a simplified copy of the UE context (context cookie containing resume ID, security context, session information) that is stored in the network. This copy allows rapid retrieval and reuse during reconnection without requiring transmission of the complete original state representation, reducing data volume significantly
3Device complexity
If context storage is integrated in CCNF, then system complexity is reduced, but flexibility for per-slice storage is lost
Solution Approach 1:
The patent segments the context storage function from the CCNF by introducing a separate Context Storage Function (CSF) that can be independently deployed. This allows context to be stored in a dedicated function rather than integrated within CCNF, providing architectural flexibility to support per-slice storage requirements while maintaining manageable system complexity through functional separation
Solution Approach 2:
The patent introduces dynamic flexibility by allowing the context storage location to be configurable on a per-slice basis. The system can dynamically determine whether to store context in the network or in the UE based on slice-specific requirements, enabling adaptability to different network conditions and slice configurations without fixing the architecture rigidly
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A network entity may determine whether a network context of a device is stored in the device or in the network based, at least in part, on a preference or capability of the device, as reported by the device during attachment to the network entity. The context may be stored in, and retrieved from, a dedicated context storage function that is independent of the network entity. A context storage function may be partitioned, or separate storage functions used, to automatically group and track access network contexts, core network contexts, or network slice contexts. The context storage function may provide to the device an index, such as a link or other identifier to be used in retrieving the stored context information. The context storage function may further provide a token to secure re-attachment communications among the device, the network entity, and the context storage function.