Relay UE Buffer Status Reporting for Multi-Path Wireless Transmission
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face challenges in efficiently managing multi-path transmission scenarios, particularly in reporting buffer status in Evolved Universal Terrestrial Radio Access Networks (E-UTRAN) with the rise of IP data packet communication, which affects data throughput and service reliability.
Innovation Solution
A method and device are introduced to support multi-path transmission by configuring a relay User Equipment (UE) with a Radio Link Control (RLC) entity associated with an indirect bearer, allowing it to transmit buffer status reports (BSR) through a non-3GPP standard interface, including data volume in Packet Data Convergence Protocol (PDCP) entities, to enhance network node communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional mobile voice communication networks are used, then service simplicity is maintained, but data throughput capability deteriorates
Solution Approach 1:
The network is segmented into direct path and indirect path transmission routes. The relay UE divides the communication task by establishing separate RLC entities for different bearers (direct bearer for own data, indirect bearer for remote UE data), allowing parallel data flow through multiple paths simultaneously, thereby increasing overall throughput without requiring complete network redesign
Solution Approach 2:
The relay UE is designed with multi-functionality to serve both as a regular UE for direct communication and as a relay node for indirect communication. It maintains its own direct bearers while simultaneously establishing indirect bearers for remote UEs, allowing a single node to perform multiple functions and increasing network capacity without adding dedicated relay infrastructure
2Productivity
If multi-path transmission is implemented, then data throughput is improved, but buffer status reporting complexity deteriorates
Solution Approach 1:
The buffer status reporting is segmented by separating direct BSR and indirect BSR. The relay UE generates independent BSR reports for its own direct bearers and for the remote UE's indirect bearers. This segmentation allows the network to process buffer status information separately for each path type, managing complexity through structured division rather than attempting to report all buffer states in a single undifferentiated report
Solution Approach 2:
The relay UE acts as an intermediary that collects buffer status information from both its own PDCP/RLC entities and the remote UE's PDCP entity. It then formulates and transmits composite BSR reports to the network node, mediating between multiple data sources and the network's scheduling requirements, thereby simplifying the overall reporting structure through a centralized reporting mechanism
3Reliability
If indirect bearer with PDCP entity in remote UE is used, then service continuity is improved, but reporting overhead deteriorates
Solution Approach 1:
The relay UE merges the buffer status reporting of its own direct bearers and the remote UE's indirect bearers into unified BSR reports transmitted to the network node. By combining multiple reporting functions into single standardized BSR messages, the system maintains comprehensive service continuity monitoring while reducing the quantity of separate reporting transmissions, thereby lowering overall reporting overhead
Data Source
AI summary
A method and device for supporting multi-path (MP) transmission are disclosed. In one embodiment, a relay User Equipment (UE) connects with a network node. The relay UE also connect with a remote UE via a non-3GPP standard interface. Furthermore, the relay UE is configured with a Radio Link Control (RLC) entity associated with an indirect bearer of the remote UE by the network node. In addition, the relay UE transmits a buffer status report (BSR) to the network node, wherein the BSR includes data volume in a Packet Data Convergence Protocol (PDCP) entity and the RLC entity and wherein the PDCP entity is associated with the indirect bearer and is established in the remote UE.