RRC Link Maintenance Using Dummy Packets Before Inactivity Release
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication systems experience significant delays in re-establishing Radio Resource Control (RRC) connections due to the use of inactivity timers, which are inefficient for services requiring low latency, such as industrial automation and vehicle-to-everything applications.
Innovation Solution
A method and device for a terminal device to estimate the timing duration of an inactivity timer by determining the end time of a service and the reception of an RRC release message, allowing it to send a virtual data packet before the timer expires to maintain the RRC connection, thereby reducing service delays without requiring network-side modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If the network uses an inactivity timer to release RRC connection after no traffic, then the network can save resources and reduce connection maintenance overhead, but services with high delay requirements experience large delays when re-establishing RRC connection
Solution Approach 1:
The terminal device performs preliminary actions by estimating the inactivity timer duration and proactively sending virtual data packets before the timer expires. This prevents the RRC connection from being released, thereby avoiding the delay that would occur during re-establishment while still allowing the network to maintain connections only when necessary.
Solution Approach 2:
The terminal device uses feedback mechanisms by monitoring the RRC release message timing and adjusting its virtual data packet transmission strategy accordingly. The device estimates the timer duration based on observed RRC release patterns and adapts its behavior to maintain connections proactively without causing unnecessary resource consumption.
2Loss of time
If the terminal device sends virtual data packets to maintain RRC connection, then service delay is reduced for low-latency services, but the terminal device must estimate timer duration accurately which increases device complexity
Solution Approach 1:
The terminal device performs self-service by autonomously estimating the inactivity timer duration and deciding when to send virtual data packets without requiring network-side assistance or complex configuration. The device uses its own observations of RRC release timing to make these decisions, simplifying the overall system architecture.
Solution Approach 2:
The terminal device changes operational parameters by dynamically adjusting its behavior based on estimated timer durations. Instead of using fixed thresholds, the device adapts its virtual data packet transmission timing based on observed network patterns, allowing flexible adaptation to different network conditions without increasing structural complexity.
3Reliability
If the terminal device proactively manages the inactivity timer, then RRC connection is maintained for low-latency services, but the terminal device must continuously monitor and estimate timer duration which increases operational complexity
Solution Approach 1:
The terminal device ensures continuity of useful action by continuously monitoring RRC connection status and proactively sending virtual data packets to maintain the connection before the inactivity timer expires. This continuous proactive management ensures reliable connection maintenance without requiring complex operational procedures, as the device simply needs to observe timing patterns and respond accordingly.
Data Source
Figure 1~2
Figure 3~4
Figure 5~7
AI summary
A link maintenance method, apparatus, and system, a terminal, and a readable storage medium. The link maintenance method comprises: after a first service is initiated for a network side, determining the end time point of the first service (101); upon the receipt of an RRC release message corresponding to the first service and sent from the network side, determining the time point of receiving the RRC release message (102); according to the end time point and the time point of receiving the RRC release message, estimating the timing duration of an inactivity timer set by the network side (103); and after a second service is initiated for the network side, starting timing from the end of the second service, and before the duration of the timing reaches the timing duration, sending a dummy data packet to the network side to maintain the RRC connection between a terminal and the network side (104).