Relay UE Data Volume Counting for Remote UEs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the L2 UE to NW relay architecture, there is no visibility for the remote UE's PDCP PDU, making it difficult to directly count the Uu data volume from the remote UE, especially when a split bearer configuration is used, which can lead to decreased system performance.

Innovation Solution

A method performed by a relay UE that monitors data traffic volume, determines the size of data traffic volumes related to itself and the remote UE, and compares these sizes to data thresholds to accurately count and indicate the remote UE's data volume, enabling accurate data volume counting and improved system performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Volume of moving object

If L2 UE to NW relay architecture is used, then coverage extension is achieved, but visibility for remote UE's PDCP PDU is lost making data volume counting difficult

Engineering Contradiction:
Improvecoverage extensionVSAvoidvisibility for remote UE's PDCP PDU
Core Design Contradiction:
Volume of moving objectVSLoss of information

Solution Approach 1:

The relay UE acts as an intermediary between the remote UE and the network. It receives PDCP PDUs from the remote UE via PC5 interface, counts the data volume, and forwards this information to the network via Uu interface. This mediator approach allows the network to obtain data volume information indirectly through the relay UE, resolving the visibility loss issue while maintaining coverage extension benefits

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The relay UE implements feedback mechanisms by monitoring and counting the data volume of PDCP PDUs received from the remote UE. It then reports this counted data volume back to the network, creating a feedback loop that provides the network with visibility into remote UE data traffic despite the relay architecture. This feedback enables accurate data volume counting for billing, QoS, and resource allocation purposes

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If split bearer configuration is used, then data transmission flexibility is improved, but data volume counting accuracy deteriorates

Engineering Contradiction:
Improvedata transmission flexibilityVSAvoiddata volume counting accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent segments the data volume counting process into distinct portions: the relay UE counts the first portion of data volume for its own PDCP PDUs, and separately counts the second portion for the remote UE's PDCP PDUs. This segmentation allows accurate tracking of data volumes even when split bearer configurations are used, as each portion is counted independently at the appropriate location in the protocol stack

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension for data volume counting by implementing counting mechanisms at multiple levels: the relay UE counts data volume at the PDCP layer for both its own traffic and the remote UE's traffic, while also tracking data volume at lower layers. This multi-dimensional counting approach ensures accuracy regardless of split bearer configuration, as counting occurs at the PDCP layer where data volume information is most accurately available

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

Data Source

PatentUS20230328582A1Methods and apparatus for data volume counting
Publication Date: 2023.10.12 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20230328582A1 patent drawing
  • US20230328582A1 patent drawing
  • US20230328582A1 patent drawing

AI summary

Methods and apparatus supportive to D2D communications are disclosed. A method performed by a relay user equipment, relay UE, comprises: monitoring a data traffic volume at the relay UE; and determining a size of a first portion of the data traffic volume related to the relay UE, and a size of a second portion of the data traffic volume related to a remote UE that is connected to the relay UE.