eNodeB RRC Reestablishment via MME Context Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices experience dropped calls and interruptions during radio link failures due to eNodeB rejecting RRC connection reestablishment requests when context data is unavailable, leading to inefficient network signaling and user experience degradation.
Innovation Solution
A method and system where the first eNodeB communicates an initial mobile device service request to an MME, which locates and retrieves mobile device context data from a second eNodeB, allowing the MME to reestablish the RRC connection without requiring the mobile device to switch to an RRC_IDLE state and perform a new connection request.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the eNodeB rejects the RRC connection reestablishment request when context data is unavailable, then the network signaling is simplified, but the call reliability deteriorates causing dropped calls and interruptions
Solution Approach 1:
The patent introduces the MME as an intermediary entity that mediates between the eNodeB and the mobile device during RRC connection reestablishment. When the eNodeB receives a reestablishment request but lacks context data, it forwards the request to the MME instead of immediately rejecting it. The MME then coordinates with the second eNodeB to retrieve the necessary context data and facilitates the reestablishment process, thereby maintaining call reliability while managing network signaling complexity through centralized coordination.
Solution Approach 2:
The patent implements preliminary action by having the eNodeB forward the reestablishment request to the MME in advance of actually needing the context data. This allows the MME to proactively locate and retrieve the context data from the second eNodeB before the first eNodeB needs it for completing the reestablishment. This preliminary retrieval action prevents call drops by ensuring data availability while avoiding the complexity of real-time data fetching during the critical reestablishment moment.
2Reliability
If the mobile device switches to RRC_IDLE state and performs a new connection request, then the network can重新 establish context data, but the service continuity deteriorates causing call drops and interruptions
Solution Approach 1:
The patent maintains continuity of useful action by keeping the mobile device in RRC_CONNECTED state throughout the reestablishment process rather than forcing a transition to RRC_IDLE. The device continues its service request and data transmission activities uninterrupted while the network handles the context data retrieval in the background. This approach ensures service continuity by eliminating the idle state transition that would otherwise cause call drops and service interruptions.
Solution Approach 2:
The MME acts as an intermediary that enables continuous service by coordinating the context data retrieval from the second eNodeB without requiring the mobile device to interrupt its current service. The mediator handles the background data fetching and coordination while the device maintains its connected state and service flow, thereby preserving service continuity and minimizing reestablishment time.
3Reliability
If the first eNodeB retrieves context data from the second eNodeB through MME, then the connection reestablishment success rate improves, but the network signaling overhead increases
Solution Approach 1:
The MME serves as an efficient intermediary that reduces overall signaling overhead by consolidating the coordination functions. Instead of having the first eNodeB directly communicate with the second eNodeB (which would require multiple direct signaling exchanges), the MME centralizes the context data retrieval process. The first eNodeB sends a single request to the MME, and the MME handles all subsequent communication with the second eNodeB, thereby reducing the total number of signaling messages and improving reestablishment success rate while minimizing energy consumption.
Data Source
AI summary
Methods and systems for reestablishing a mobile device RRC connection based on eNodeB messaging. An RRC (Radio Resource Control) connection reestablishment request for the mobile device is received at a first eNodeB (Evolved NodeB). It is determined that the RRC connection reestablishment request requires mobile device context data that is unavailable at the first eNodeB. The first eNodeB communicates an initial mobile device service request message to an MME (Mobility Management Entity) based on a determination that the RRC connection request requires the mobile device context data that is unavailable at the first eNodeB. Upon communicating the initial mobile device service request message, the first eNodeB receives the mobile device context data in order to reestablish the mobile device RRC connection.