MAC Subheader Type Field for L2 Relay Traffic Differentiation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Layer 2 (L2) relay configurations, remote UE cannot differentiate between routed and non-routed traffic, leading to challenges in delivering traffic to the correct RLC/PDCP layers, and lacks destination information for uplink traffic, resulting in inefficient communication.
Innovation Solution
Incorporating a Medium Access Control (MAC) subheader with a Type field to differentiate between non-routed and routed traffic, enabling the UE to identify and manage traffic types correctly, and using UE IDs to distinguish between relay and non-relay functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the relay UE combines routed and non-routed traffic together in the downlink, then the traffic can be transmitted through a single channel, but the remote UE cannot deliver different traffic into different RLC/PDCP layers
Solution Approach 1:
The patent segments traffic into two distinct types: routed traffic (intended for the network) and non-routed traffic (intended for the relay UE). This segmentation is achieved by introducing a Type field in the MAC subheader that clearly identifies the traffic type, allowing the remote UE to deliver different traffic into different RLC/PDCP layers appropriately.
Solution Approach 2:
The patent applies local quality by making the MAC subheader structure context-dependent. The presence or absence of the Type field in the MAC subheader provides local differentiation for traffic types, enabling the receiver to understand whether the payload is routed or non-routed traffic and process it accordingly in the appropriate protocol layer.
2Device complexity
If the remote UE transmits uplink traffic without destination information, then the transmission can be simplified, but the relay UE cannot determine whether to relay or terminate the traffic
Solution Approach 1:
The patent applies preliminary action by embedding the Type field in the MAC subheader before transmission. This allows the destination information to be encoded in advance in the uplink transmission, enabling the relay UE to determine whether to relay or terminate the traffic based on the Type field value without requiring additional signaling or complex processing.
3Device complexity
If no MAC subheader differentiation is used, then the protocol structure remains simple, but traffic types cannot be distinguished for proper routing
Solution Approach 1:
The patent extracts the traffic type identification function from the payload and places it in the MAC subheader through the Type field. This extraction allows traffic types to be distinguished early in the protocol stack without complicating the overall structure, enabling efficient routing decisions to be made based on the subheader information alone.
Data Source
AI summary
A user equipment (UE) is configured to communicate with a further UE via a sidelink (SL). The UE encodes traffic for transmission to the further UE, wherein the traffic comprises a payload and a medium access control (MAC) subheader, wherein the MAC subheader indicates whether the payload corresponds to non-routed traffic between the UE and the further UE or routed traffic between either one of the UE or the further UE and a base station, wherein an other one of the UE or the further UE functions as a relay for the routed traffic and transmits the traffic.