UE Capability Reporting for Small Data Transmission in RRC Inactive State
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G NR networks, the RRC_INACTIVE state does not support data transmission, leading to unnecessary power consumption and signaling overhead due to the need to resume connections for small data packets, which is inefficient and battery-intensive for user equipment (UE).
Innovation Solution
Implementing a method for user equipment (UE) to report capability for small data transmission (SDT) in the RRC_INACTIVE state using random access (RA)-SDT and configured grant (CG)-SDT procedures, allowing data transmission without transitioning to the RRC_CONNECTED state, thereby reducing power consumption and signaling overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the UE resumes connection to RRC_CONNECTED state for small data transmission, then data transmission can be performed, but power consumption increases and signaling overhead is unnecessary
Solution Approach 1:
The patent segments the data transmission process into two distinct paths: one for small data packets (using SDT procedure in RRC_INACTIVE state) and another for larger data transmissions (using RRC_CONNECTED state). This segmentation allows the UE to remain in the low-power RRC_INACTIVE state for small data transmissions, avoiding the need to transition to RRC_CONNECTED state and thereby reducing power consumption while maintaining data transmission capability.
Solution Approach 2:
The patent introduces an intermediary mechanism (SDT procedure with random access or configured grant) that enables data transmission directly from RRC_INACTIVE state without requiring full connection resumption. This intermediary pathway acts as a bridge between the idle RRC_INACTIVE state and the data transmission function, eliminating the need for complete state transition and reducing power consumption.
2Productivity
If the UE transitions to RRC_CONNECTED state for small data packets, then data transmission is enabled, but signaling overhead increases
Solution Approach 1:
The patent extracts the essential data transmission function from the full RRC connection resumption process. By separating small data transmission needs from complete connection establishment, the system can perform data transmission using only the necessary minimal signaling (random access or configured grant) while remaining in RRC_INACTIVE state, thereby significantly reducing signaling overhead compared to full connection resumption.
Solution Approach 2:
The patent applies partial action by implementing data transmission functionality that requires only a subset of the full RRC connection procedures. Instead of performing complete connection resumption (which includes full handshaking, context establishment, and resource allocation), the system uses partial procedures (random access or configured grant) that are sufficient for small data transmissions, thereby reducing signaling overhead while maintaining adequate data transmission capability.
3Productivity
If frequent state transitions are performed for small data transmission, then data can be transmitted, but network resources are consumed inefficiently
Solution Approach 1:
The patent applies preliminary action by pre-configuring the UE with SDT capabilities and parameters before actual data transmission occurs. The UE is pre-configured with random access parameters or configured grant settings that enable immediate data transmission from RRC_INACTIVE state without requiring full connection resumption. This preliminary configuration eliminates the need for complex state transitions during data transmission, reducing network resource consumption while maintaining data transmission capability.
Data Source
AI summary
A method and a user equipment (UE) for reporting UE capability for small data transmission (SDT) are provided. The method includes: receiving, from a base station (BS), a UE capability enquiry message; setting, in response to receiving the UE capability enquiry message, a content of a UE capability information message to indicate whether the UE supports random access (RA)-SDT; and transmitting, to the BS, the UE capability information message after setting the content of the UE capability information message.