UE Connection Management for RRC Inactive Base Station Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G networks, user equipment (UE) in a radio resource control (RRC) inactive state cannot communicate with base stations that do not support the RRC inactive state, as these stations cannot identify RRC resume requests, leading to communication failures when UE moves out of coverage areas.
Innovation Solution
The UE accesses a network using a first base station that supports the RRC inactive state and then switches to a second base station that does not, sending request messages to core network entities to release connections to the first base station, allowing communication to be maintained by switching to an idle state or performing PDU session deactivation procedures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If UE uses a base station that does not support RRC inactive state, then the UE can access the network, but the base station cannot identify RRC resume requests and communication fails
Solution Approach 1:
The core network entity acts as an intermediary to bridge the gap between UE supporting RRC inactive state and base stations not supporting it. The core network entity receives RRC resume requests from UE, translates them into appropriate messages, and manages the connection to base stations that cannot directly handle RRC inactive state protocols
Solution Approach 2:
The UE performs preliminary actions by sending RRC resume requests to core network entities before actually needing communication with base stations not supporting RRC inactive state. This allows the core network to prepare appropriate connection management in advance
2Ease of operation
If UE sends RRC resume request to base station not supporting RRC inactive state, then the UE attempts to communicate, but the base station cannot identify the request and communication fails
Solution Approach 1:
The core network entity serves as an intermediary that receives RRC resume requests from UE and translates them into messages that base stations not supporting RRC inactive state can understand and process correctly
3Area of stationary object
If UE moves from RAN notification area to cell of base station not supporting RRC inactive state, then the UE can expand network coverage, but the UE cannot communicate with the new base station
Solution Approach 1:
The core network entity acts as a mediator that enables UE to access base stations not supporting RRC inactive state by translating and managing connection protocols, thus allowing UE to expand coverage without losing communication capability
Solution Approach 2:
The UE performs preliminary actions by sending RRC resume requests to core network entities before actually needing communication with base stations not supporting RRC inactive state
Data Source
Figure 1
Figure 2
Figure 3
AI summary
This application discloses a connection management method, user equipment, a core network entity, and a system. The method includes: accessing, by UE, a network by using a first base station, where the UE is in an RRC inactive state; accessing, by the UE, a network by using a second base station, where the second base station does not support the RRC inactive state; and sending, by the UE, a first request message to a first core network entity by using the second base station, so that the first core network entity releases a connection to the first base station based on the first request message, or so that the first core network entity sends a second request message to a second core network entity, and the second core network entity releases a connection to the first base station based on the second request message. According to this application, communication can be implemented between UE that is in an RRC inactive state and a base station that does not support the RRC inactive state.