Shared RLC Transmission for Small Data in Access Networks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In wireless communication systems with distributed base stations, the process of establishing and releasing data resource bearers (DRBs) for terminal devices, especially in small data transmission scenarios, leads to increased processing and resource consumption due to the need for RRC connection resume and RLC entity establishment, which is inefficient and resource-intensive.

Innovation Solution

Implementing a common RLC entity in the distributed unit (DU) that transmits data packets based on logical channel identifiers (LCH IDs) meeting preset rules or dedicated indicators, allowing direct transmission without RRC connection resume and RLC entity establishment, thus optimizing data transmission efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a dedicated RLC entity is established for each terminal device in RRC inactive mode, then data transmission reliability is improved, but processing complexity and resource consumption increase

Engineering Contradiction:

Improvedata transmission reliabilityVSAvoidprocessing complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple dedicated RLC entities into a single shared RLC entity that serves multiple terminal devices. The DU maintains one RLC entity that can handle data packets from multiple UEs by identifying them through LCH IDs, eliminating the need to create separate RLC entities for each terminal device while maintaining reliable data transmission.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The shared RLC entity is designed with universal functionality to serve multiple terminal devices simultaneously. It uses LCH ID-based identification to distinguish between different UEs and their data packets, allowing a single RLC entity to perform the functions previously requiring multiple dedicated entities.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If RRC connection resume and RLC entity establishment are performed for each terminal device, then data transmission quality is improved, but signaling resource consumption increases

Engineering Contradiction:

Improvedata transmission qualityVSAvoidsignaling resource consumption

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent combines the RLC entity function into a single shared entity that handles data for multiple terminal devices. By merging these functions, the system eliminates redundant RLC entity establishment signaling and reduces the overall signaling burden while maintaining data transmission quality through LCH ID-based identification.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The DU pre-configures a shared RLC entity with the capability to handle multiple terminal devices before data transmission occurs. This preliminary setup eliminates the need for dynamic RLC entity establishment during data transmission, reducing signaling resources while maintaining transmission quality.

Inventive Principle:

Principle #10Preliminary action

3Productivity

If a shared RLC entity is used for multiple terminal devices, then processing overhead is reduced, but data packet identification complexity increases

Engineering Contradiction:

Improveprocessing efficiencyVSAvoiddata packet identification complexity

Core Design Contradiction:

ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies local quality differentiation by using LCH IDs as unique identifiers for each terminal device's data packets within the shared RLC entity. This allows the system to maintain clear identification and separation of data packets from different UEs while using a single shared RLC entity, thus avoiding identification complexity.

Inventive Principle:

Principle #3Local quality

4Reliability

If dedicated F1 tunnel and RLC entity are established for each terminal device, then data transmission reliability is improved, but transmission resource consumption increases

Engineering Contradiction:

Improvedata transmission reliabilityVSAvoidtransmission resource consumption

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple F1 tunnels and RLC entities into a single shared F1 tunnel and shared RLC entity. The shared RLC entity uses LCH ID-based identification to distinguish between different terminal devices, allowing multiple UEs to use the same transmission resources simultaneously without compromising reliability.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The shared F1 tunnel and shared RLC entity are designed with universal functionality to serve multiple terminal devices. The LCH ID mechanism enables the system to maintain reliable data transmission for multiple UEs through a single shared transmission path, reducing transmission resource consumption while preserving reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12495468B2Data transmission method applied to access network and device

Publication Date: 2025.12.09 HUAWEI TECH CO LTD

AI summary

A data transmission method applied to an access network and a device, the method including receiving, by a radio access network (RAN) device of an access network, a first data packet from a first terminal device, wherein the first data packet comprises a logical channel identifier (LCH ID), determining, by the RAN device, whether the LCH ID meets a first preset rule, and sending, by the RAN device, in response to determining that the LCH ID meets the first preset rule, the first data packet through a common radio link control (RLC) entity.