LTE Terminal Random Access Control via RRC Reconfiguration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The frequent random access processes triggered by the Media Access Control (MAC) in LTE systems significantly impact the access performance and stability of the network, leading to inefficient use of resources and increased data transmission instability, with an average of three successful random access processes required to achieve a stable status.
Innovation Solution
A processing method and terminal for random access that determines whether to trigger subsequent random access attempts based on successful initial access and receipt of an RRC reconfiguration message carrying SR-related parameters, allowing the use of effective PUCCH resources to reduce unnecessary retransmissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the random access process is triggered frequently by MAC, then the SR can be sent when triggered, but the access performance and stability of the LTE system are greatly influenced and random access triggering times increase
Solution Approach 1:
The patent applies preliminary action by having the terminal determine whether to trigger next random access before actually executing it. The terminal checks if an RRC reconfiguration message carrying SR related parameter is received and if the parameter is effective, only then triggers the random access process. This preliminary determination prevents unnecessary random access triggering while ensuring SR can be sent when needed, thus improving access performance and stability without increasing triggering times.
2Ease of operation
If the terminal continuously performs random access process, then the SR can be sent, but the PRACH resource is occupied and user access performance of the entire network system is affected
Solution Approach 1:
The patent applies feedback by having the terminal check whether the SR related parameter in the RRC reconfiguration message is effective before triggering random access. The terminal uses this feedback information to determine whether to proceed with random access or wait for the parameter to take effect. This feedback mechanism ensures that random access is only triggered when necessary, preventing PRACH resource occupation and maintaining network system access performance while still enabling SR sending when conditions are met.
3Reliability
If the terminal waits for RRC reconfiguration message to be received, then the SR parameter can take effect, but a time interval of about 100 ms exists between delivering the message and first successful random access
Solution Approach 1:
The patent applies preliminary action by having the terminal determine whether to trigger next random access immediately after receiving the RRC reconfiguration message, before the parameter fully takes effect. The terminal checks if the SR related parameter is effective and makes a determination to trigger or not trigger random access in advance. This preliminary determination allows the terminal to prepare for successful access while minimizing the waiting time, reducing the 100 ms time interval without compromising parameter effectiveness.
Data Source
AI summary
A processing method and a terminal for random access are provided in the embodiments of the present invention. The method includes: triggering, by a terminal, first random access through Media Access Control (MAC), and successfully accessing a device at a network side; when a Scheduling Request (SR) of the terminal is triggered, determining whether to trigger next random access, where if the next random access is determined not to be triggered, the terminal does not execute the random access; receiving, by the terminal, a Radio Resource Control (RRC) reconfiguration message that carries an SR related parameter and the RRC reconfiguration message is sent by the device at the network side; and determining, according to the SR related parameter, by the terminal, a Physical Uplink Control Channel (PUCCH) resource for sending the SR, and sending the SR by using the PUCCH resource.