Bulk User Equipment Context Transfer in Evolved Packet Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional evolved packet systems face inefficiencies in user equipment context distribution, particularly with Machine-Type Communication, as they require reactive exchanges and involve user equipment in signaling, leading to increased signaling and data transfer, and are not flexible enough for proactive offloading.
Innovation Solution
A method and system for bulk transfer of user equipment context from one mobility management entity to another, including reconfiguration of mobility management entity codes and storage in the first entity, which reduces offload times and allows proactive distribution without involving user equipment, leveraging existing S1-AP protocol functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If reactive exchange of user equipment context between mobility management entities is used, then user equipment context can be transferred, but offload times are long and user equipment must be involved in signaling
Solution Approach 1:
The patent applies preliminary action by proactively transferring user equipment context from the first MME to the second MME before the actual offload operation is needed. This allows the second MME to have the context ready in advance, eliminating the need for time-consuming reactive transfers and reducing offload times significantly.
Solution Approach 2:
The patent extracts the user equipment context from the source MME and stores it in the target MME's database separately. This extraction allows the context to be independently managed and accessed without involving the user equipment, enabling fast offloading by simply changing the MME identifier in the GUTI.
2Adaptability or versatility
If reactive exchange of user equipment context is performed, then context can be transferred, but signaling between core network and user equipment increases
Solution Approach 1:
The patent implements self-service by enabling the target MME to autonomously obtain and store user equipment context from the source MME without requiring user equipment participation. The MMEs exchange context information directly through interface S11, and the target MME independently updates its database and reconfigures MME codes, eliminating the need for signaling with the user equipment.
Solution Approach 2:
The patent uses the S11 interface between MMEs as an intermediary channel for context transfer. Instead of signaling through the user equipment, the context is transferred directly between MMEs via this intermediary interface, reducing signaling overhead while maintaining flexibility in context distribution.
3Productivity
If conventional context transfer methods are used, then user equipment context can be moved, but data transfer between core network and radio access network increases
Solution Approach 1:
The patent performs preliminary action by pre-transferring the complete user equipment context to the target MME before offloading occurs. This includes all necessary data such as bearer contexts, security information, and mobility management data. By having everything ready in advance, the actual offload requires minimal data transfer, improving efficiency while reducing data transfer volume.
Solution Approach 2:
The patent creates a copy of the user equipment context in the target MME's database rather than maintaining the original in the source MME. This copying approach allows the context to be reused without additional data transfer, as the target MME has its own complete copy that can be used immediately for offloaded user equipment.
Data Source
AI summary
A method for distributing user equipment context in an evolved packet system, including a plurality of user equipment, at least one eNodeB, a first mobility management entity and a second mobility management entity and one serving gateway connected to the first and second mobility management entity, the plurality of user equipment being connected via one of the eNodeBs to the second mobility management entity and to the serving gateway, wherein the user equipment context for the plurality of user equipment is each stored at the second mobility management entity, includes: a) transferring bulk user equipment context for the plurality of user equipment context, each having a mobility management entity code, to the first mobility management entity, b) reconfiguring the mobility management entity codes, c) storing the transferred user equipment context in the first mobility management entity, and d) transferring reconfigured mobility management entity codes to the at least one eNodeB.