SL-RLC Configuration for Out-of-Coverage Sidelink Relay UEs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication technologies face challenges in properly configuring parameters for data and signaling transmission in UE-to-UE relay architectures, particularly in scenarios where UEs are out of coverage or have poor communication environments.
Innovation Solution
A method for configuring sidelink radio link controls (SL-RLCs) and remote UE local IDs to facilitate data and signaling transmission between source and target UEs via a relay UE, using predefined or default configurations specified by protocols or configured by the UEs themselves.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If sidelink relay architecture is implemented for out-of-coverage UEs, then communication coverage is extended, but parameter configuration complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-configuring default RLC and MAC parameters for sidelink relay connections before actual data transmission. The source UE, relay UE, and target UE establish predefined configuration templates that include RLC configuration (logical channel ID, sequence number length) and MAC configuration (priority, logical channel group). When a relay connection is established, these pre-defined configurations are automatically applied, eliminating the need for complex real-time parameter negotiation and configuration.
Solution Approach 2:
The patent implements self-service through autonomous configuration management where each UE (source, relay, target) independently applies configurations to its own SL-RLC entities without requiring manual intervention or complex coordination. The UEs autonomously select and apply appropriate configurations based on their roles in the relay architecture, simplifying the overall system complexity while maintaining comprehensive coverage support.
2Reliability
If multiple SL-RLC configurations are applied for source-relay and relay-target connections, then transmission reliability is improved, but configuration management difficulty increases
Solution Approach 1:
The patent applies segmentation by dividing the sidelink relay connection into two independent SL-RLC configurations: one for the source-relay link and another for the relay-target link. Each SL-RLC entity is configured separately with its own RLC and MAC parameters, allowing independent optimization and management of each connection segment. This segmentation enables reliable transmission across both links while simplifying configuration management through modular, independent configuration sets.
3Stability of the object's composition
If protocol-specified fixed configurations are used, then configuration consistency is ensured, but flexibility in adapting to different scenarios is reduced
Solution Approach 1:
The patent applies parameter changes by defining configurable parameters within the SL-RLC configurations that can be adjusted based on specific transmission scenarios. The RLC configuration parameters (logical channel ID, sequence number length) and MAC configuration parameters (priority, logical channel group) can be modified according to different service requirements, traffic types, and channel conditions, providing flexibility while maintaining consistent configuration structures across all sidelink relay connections.
Data Source
AI summary
The present invention provides a method performed by a user equipment and a user equipment. The method comprises: when a PC5 radio resource control (PC5-RRC) connection is established between UE1 and UE2, or when a PC5-RRC connection is established between UE1 and UE3, performing, by UE1, an operation including at least one of the following operations: applying a configuration of a first SL-RLC; applying a configuration of a second SL-RLC; initiating the configuration of the first SL-RLC; initiating the configuration of the second SL-RLC; and initiating a configuration of a remote UE local ID, wherein if UE1 is a source UE, UE2 is a relay UE and UE3 is a target UE; if UE1 is a target UE, UE2 is a relay UE and UE3 is a source UE; and if UE1 is a relay UE, UE2 is a source UE and UE3 is a target UE.