RRC Inactive Data Transfer With Buffer Status Reporting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The inefficiency of data transfer in the RRC_INACTIVE state of 5G communication systems, leading to excessive network overhead when transitioning to RRC_CONNECTED for data transmission, is addressed.

Innovation Solution

A method and apparatus for data transfer in RRC_INACTIVE state, involving a first resume procedure for resuming the RRC connection and a second resume procedure for data transmission and reception without transitioning to RRC_CONNECTED, utilizing predefined and system information-based information for buffer status reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the terminal transitions from RRC_INACTIVE to RRC_CONNECTED state for data transfer, then reliable data transmission is ensured, but network overhead increases and network efficiency decreases

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidnetwork efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the resume procedure into two distinct types: first resume procedure for control plane signaling and second resume procedure for user plane data transfer. This segmentation allows data transfer to occur in RRC_INACTIVE state without full connection establishment, reducing network overhead while maintaining reliability through appropriate procedure selection

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic selection between first and second resume procedures based on whether data transfer is required. The terminal determines the appropriate procedure type dynamically, enabling flexible adaptation between reliability-focused and efficiency-focused modes depending on the specific communication scenario

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If the terminal performs first resume procedure to transition to RRC_CONNECTED, then complete connection establishment is achieved, but data transfer efficiency decreases

Engineering Contradiction:
Improveconnection establishment completenessVSAvoiddata transfer efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent applies partial action by implementing a second resume procedure that performs only the necessary steps for data transfer without completing the full connection establishment. This partial resume allows the terminal to obtain uplink grants and transfer data while remaining in RRC_INACTIVE state, improving efficiency while maintaining sufficient connectivity for the specific purpose

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If the terminal uses second resume procedure for data transfer in RRC_INACTIVE state, then network efficiency is improved, but buffer status reporting complexity increases

Engineering Contradiction:
Improvenetwork efficiencyVSAvoidbuffer status reporting complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by having the network configure buffer status reporting parameters in advance through system information or RRCRelease message. The terminal stores these predefined parameters and uses them automatically during the second resume procedure, eliminating the need for complex real-time negotiations and reducing operational complexity despite the novel reporting mechanism

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12471174B2Method and apparatus for data transfer and buffer status reporting in RRC_INACTIVE state in mobile wireless communication system
Publication Date: 2025.11.11 BLACKPIN INC
  • US12471174B2 patent drawing
  • US12471174B2 patent drawing
  • US12471174B2 patent drawing

AI summary

A method and apparatus for data transfer in RRC_INACTIVE state is provided. Method for data transfer in RRC_INACTIVE state includes transmitting a UECapabilityInformation, receiving a RRCRelease, receiving a system information, initiating a second resume procedure and performing buffer status reporting based on a first information and a second information if second resume procedure is ongoing. The first information is predefined and the second information is included in the system information.