Terminal Buffer Status Reporting in RRC Inactive State
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The transition from RRC_INACTIVE to RRC_CONNECTED state in 5G mobile communication systems is inefficient due to excessive overhead when data transfer is not justified, impacting network efficiency.
Innovation Solution
A method and apparatus for data transfer in the RRC_INACTIVE state, involving a first and second resume procedure that allow data transmission and reception without transitioning to RRC_CONNECTED, utilizing RRC Reconfiguration and Release messages to manage buffer status reporting and power headroom reporting, enabling efficient data transfer and state management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the terminal transitions from RRC_INACTIVE to RRC_CONNECTED state for data transfer, then data transmission capability is improved, but network overhead increases
Solution Approach 1:
The patent segments the data transfer process by introducing a second resume procedure that allows data transmission in RRC_INACTIVE state for small data packets, while reserving RRC_CONNECTED state for larger data transfers. This segmentation enables the system to avoid full state transitions for small data, reducing overhead while maintaining capability for larger transfers.
Solution Approach 2:
The patent applies partial action by allowing the terminal to perform Buffer Status Reporting (BSR) and Power Headroom Reporting (PHR) in RRC_INACTIVE state without completing the full transition to RRC_CONNECTED. This partial reporting mechanism provides the network with sufficient information to allocate resources efficiently without requiring the overhead of complete connection establishment.
2Productivity
If the terminal performs BSR and PHR in RRC_INACTIVE state, then network resource allocation efficiency is improved, but signaling overhead increases
Solution Approach 1:
The patent implements preliminary action by having the terminal report BSR and PHR information while still in RRC_INACTIVE state, before full connection establishment. This allows the network to pre-allocate resources and prepare for upcoming data transfers, improving allocation efficiency while avoiding the overhead of complete RRC connection setup.
Solution Approach 2:
The patent introduces an intermediary mechanism where BSR and PHR reports are transmitted through simplified signaling in RRC_INACTIVE state, serving as a mediator between the terminal's data transmission needs and the network's resource allocation. This intermediary reporting reduces the signaling overhead compared to full RRC_CONNECTED procedures while still providing necessary resource allocation information.
3Loss of time
If the system supports data transfer in RRC_INACTIVE state, then latency is reduced, but device complexity increases
Solution Approach 1:
The patent applies dynamics by enabling flexible state transitions - the terminal can remain in RRC_INACTIVE for small data transfers (reducing latency) or transition to RRC_CONNECTED for larger transfers. The system dynamically selects the appropriate operation mode based on data size and requirements, with the terminal maintaining capability to perform BSR/PHR reporting in both states.
Solution Approach 2:
The patent implements universality by designing the terminal and network to support multiple functions within RRC_INACTIVE state - not only data transfer but also BSR and PHR reporting. This multi-functionality allows the system to handle diverse data transfer scenarios without requiring separate procedures, managing complexity through unified state handling.
Data Source
AI summary
A method and apparatus for data transfer in RRC_INACTIVE state is provided. Method for data transfer in RRC_INACTIVE state includes receiving RRC Reconfiguration message, receiving RRC Release message and triggering BSR based on the first BSR configuration and first LCGs or based on the second BSR configuration and second LCGs.