Description
The term 'egress link' is defined in 3GPP TS 38.340 (NR sidelink relay adaptation protocol) and TS 38.351 (NR sidelink relay adaptation protocol, possibly a different aspect) as a radio link on which a packet is transmitted by a specific node type. It is used in the context of 5G NR sidelink relaying, where a UE can act as a relay to extend network coverage or enable UE-to-UE communication. The definition evolved from a generic 'a radio link on which a packet is transmitted by a node' in Rel-16 to a more specific enumeration of node types in later releases, reflecting the expansion of relay architectures (U2N and U2U).
Architecturally, egress link is a directional concept: for a given packet, the egress link is the link over which the packet leaves the node that is currently forwarding it. In UE-to-Network (U2N) relaying, a U2N Relay UE forwards packets between a U2N Remote UE and the network (gNB). The egress link could be the link from the Remote UE to the Relay UE (if the Remote UE transmits), or from the Relay UE to the gNB (if the Relay UE transmits). Similarly, in UE-to-UE (U2U) relaying, a U2U Relay UE forwards packets between two U2U Remote UEs. The term helps specify protocol behavior, such as adaptation layer routing and bearer mapping, by distinguishing the ingress link (where a packet arrives) from the egress link (where it is sent).
How it works: The sidelink relay adaptation protocol (SRAP) in TS 38.340 uses the concepts of ingress and egress links to route packets. When a relay UE receives a packet on an ingress link, it determines the egress link based on the destination UE ID or bearer configuration, then transmits the packet on that egress link. The egress link is thus the outgoing radio link for that packet. The definition's evolution to include U2N Relay UE, U2N Remote UE, U2U Remote UE, U2U Relay UE, and network node reflects the different roles that can transmit on an egress link in various relay scenarios.
Key components include the relay UE (which may be a U2N Relay UE or U2U Relay UE), the remote UE (U2N Remote UE or U2U Remote UE), and the network node (gNB). The egress link itself is a radio link (PC5 sidelink or Uu) over which the packet is transmitted. The term is used in specifications to define procedures for packet forwarding, QoS handling, and security in sidelink relay.
Its role is to provide precise language for describing packet flow in relay architectures, enabling standardized implementation of multi-hop relaying in 5G NR. By clarifying which link is the egress link, the specs ensure that functions like header compression, ciphering, and bearer mapping are applied correctly at each hop.
Purpose & Motivation
The egress link concept was introduced to support the standardization of 5G NR sidelink relaying, which allows UEs to act as relays to extend network coverage and enable direct UE-to-UE communication. In earlier releases, relaying was not fully specified for NR sidelink, and the generic definition in Rel-16 ('a radio link on which a packet is transmitted by a node') was sufficient for initial work. As relay architectures matured, the need arose to distinguish between different node types and link directions to specify protocol behavior accurately.
The term solves the problem of ambiguity in describing packet forwarding in multi-hop relay scenarios. Without a clear distinction between ingress and egress links, it would be difficult to define how a relay UE should process packets (e.g., which adaptation layer headers to add or remove, how to map bearers). The evolution of the definition to explicitly list U2N and U2U relay/remote UEs and network nodes reflects the expansion of relay use cases, including public safety, coverage extension, and wearable devices.
Historically, the egress link definition was refined in Rel-17 to include U2N Relay UE and U2N Remote UE, and further in Rel-18 to include U2U Remote UE and U2U Relay UE. This mirrors the 3GPP work on NR sidelink relay in Rel-17 (U2N) and Rel-18 (U2U). The term is part of the broader effort to integrate sidelink relaying into the 5G ecosystem, enabling new services and improving network resilience.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Egress link, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.340 vj00 | Backhaul Adaptation Protocol (BAP) Specification | Rel-19 read |
| TS 38.351 vj10 | Sidelink Relay Adaptation Protocol (SRAP) | Rel-19 read |