Relay Communication Unit Capability Reporting for Network Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In sidelink relay scenarios, remote communication units (RMCU) cannot report their capabilities to network nodes (NN) due to the lack of a direct path or RRC connection, leading to suboptimal relay path connectivity and unmet service requirements.

Innovation Solution

A method where a relay communication unit (RLCU) receives capability information from the RMCU and transmits it to the NN, enabling the configuration of a relay path by informing the NN about the RMCU's sidelink-related radio access capabilities, thereby establishing a proper relay connection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a relay communication unit transmits capability information from a remote communication unit to a network node, then the network node can properly configure relay paths and meet service requirements, but the system complexity increases due to additional capability reporting mechanisms

Engineering Contradiction:
Improverelay path connectivityVSAvoidcapability reporting mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The relay communication unit acts as an intermediary between the remote communication unit and the network node. It receives capability information from the RMCU and forwards it to the NN, enabling the NN to configure appropriate relay paths without requiring direct communication between the RMCU and NN. This resolves the contradiction by introducing a mediator that simplifies the overall system architecture while enabling reliable capability reporting.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The capability information is reported in advance during the relay path establishment phase, before actual data transmission begins. The RLCU collects capability information from the RMCU and transmits it to the NN proactively, allowing the NN to pre-configure optimal relay paths based on the reported capabilities. This preliminary action ensures reliable connectivity while avoiding complex real-time capability negotiation.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If capability information is reported through the relay communication unit, then service requirements can be met with proper configurations, but information loss occurs due to the indirect reporting path

Engineering Contradiction:
Improveservice requirement fulfillmentVSAvoidcapability information accuracy
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The relay communication unit serves as a faithful intermediary that transparently forwards capability information from the RMCU to the NN. The principle ensures that the RLCU does not alter or lose capability information during transmission, maintaining information accuracy while enabling indirect reporting. The RLCU simply relays the information without interpretation or modification.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements a feedback mechanism where the NN receives capability information from the RLCU, processes it to determine appropriate relay path configurations, and can request additional or clarified information if needed. This feedback loop ensures that complete and accurate capability information is obtained, allowing the NN to make informed configuration decisions that fulfill service requirements.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If direct communication path is established between remote communication unit and network node, then capability reporting is simplified, but coverage extension is limited in scenarios with partial or no network coverage

Engineering Contradiction:
Improvecapability reportingVSAvoidnetwork coverage flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The relay communication unit enables capability reporting in scenarios where direct communication between the RMCU and NN is not possible due to lack of network coverage. The RLCU, which has network coverage, acts as a mediator that receives capability information from the RMCU via sidelink and forwards it to the NN through the Uu interface. This approach maintains ease of operation by using standardized interfaces while extending adaptability to cover scenarios with partial or no network coverage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system transitions from a single-dimension direct communication model to a multi-dimensional communication architecture. Capability information can be transmitted through multiple paths: directly via Uu interface when coverage is available, or indirectly through sidelink followed by Uu interface transmission when coverage is limited. This dimensional change in communication pathways enhances both ease of operation and adaptability to various coverage scenarios.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentEP4189988B1Technique of relaying capability information to a network node
Publication Date: 2025.03.26 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP4189988B1 patent drawingFigure 1
  • EP4189988B1 patent drawingFigure 2
  • EP4189988B1 patent drawingFigure 3

AI summary

Disclosed is a technique for informing a network node, NN (1000), of a network (700) about at least one sidelink-related radio access capability of a remote communication unit, RMCU (900), to enable configuring a relay path between the RMCU (900) and the NN (1000) via a relay communication unit, RLCU (800), connected to the NN (1000). The RMCU (900) transmits, to the RLCU (800), first capability information indicative of the at least one sidelink-related radio access capability of the RMCU (900) so as to configure the RLCU (800) for transmission of the first capability information to the NN (1000). The RLCU (800) receives, from the RMCU (900), the first capability information and transmits the first capability information to the NN (1000). The NN (1000) receives the first capability information from the RLCU (800).