Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

Ingress link

Ingress link

Radio Access Network →

Ingress link is the radio link on which a node receives a packet from a relay UE, remote UE, or network node in sidelink relay and multi-hop forwarding contexts.

Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
Ingress link Description Purpose Neighbours Specifications

Description

In the context of 3GPP sidelink relay specifications, an ingress link is the radio link over which a packet is received by a node. The term is used to describe the incoming direction of packet flow in relay and multi-hop communication scenarios. It is defined in TS 38.340 (Backhaul adaptation protocol) and TS 38.351 (Sidelink relay adaptation protocol), which specify the adaptation layer protocols for sidelink relay in 5G.

The concept is fundamental to how relay nodes process and forward packets. When a relay UE or a network node receives a packet, it must determine whether the packet arrived over an ingress link and, based on the destination, decide whether to forward it over an egress link. The ingress link is therefore paired with the egress link, which is the radio link on which a packet is transmitted. Together, they define the forwarding path through a relay. In a UE-to-Network Relay scenario, the remote UE sends a packet over the PC5 link to the relay UE; for the relay UE, that PC5 link is the ingress link, and the Uu link towards the network is the egress link. Conversely, for downlink traffic, the Uu link is the ingress link and the PC5 link is the egress link.

The definition has evolved to cover more types of endpoints. In Rel-16, the definition was generic: a radio link on which a packet is received by a node. In Rel-17, the wording changed to specify that the packet is received from a U2N Relay UE, a U2N Remote UE, or a network node. This reflects the introduction of 5G ProSe UE-to-Network relaying and the need to distinguish the roles of the UEs and network nodes involved. In Rel-18, the definition was further extended to include U2U Remote UE and U2U Relay UE, reflecting the addition of UE-to-UE relay communication in Rel-18. The Rel-19 definition carried over unchanged from Rel-18.

The ingress link concept is used in the adaptation layer to support routing and bearer mapping. The adaptation layer header may carry information that allows the receiving node to identify the ingress link and to apply the correct forwarding treatment. This is important for multi-hop relay, where a packet may traverse multiple relay UEs before reaching its destination. By identifying the ingress link, the relay can avoid loops, select the correct egress link, and apply quality-of-service handling per hop.

In summary, the ingress link is a foundational term for sidelink relay and multi-hop forwarding in 5G. It provides a common way to describe the incoming radio link at a node, enabling standardized procedures for packet forwarding, routing, and bearer mapping across relay UEs and network nodes.

Purpose & Motivation

The ingress link concept exists to provide a clear and standardized way to describe the incoming direction of packet flow in relay and multi-hop communication. In a relay network, a node may receive packets from different sources, such as a remote UE, a relay UE, or a network node, and it must know which link the packet arrived on in order to forward it correctly. Without a defined term and associated protocol behavior, relay implementations would be ambiguous and interoperability would suffer.

The term was introduced in Rel-16 as part of the initial work on sidelink relay and adaptation layer protocols. At that time, the definition was generic, reflecting the early stage of the work. As 5G ProSe evolved, the definition was refined in Rel-17 to explicitly list the types of endpoints, namely U2N Relay UE, U2N Remote UE, and network node, which aligned with the 5G ProSe UE-to-Network relay architecture. In Rel-18, the definition was extended again to include U2U Remote UE and U2U Relay UE, reflecting the introduction of UE-to-UE relay communication.

The motivation for these refinements is to ensure that the adaptation layer protocols can handle the growing variety of relay scenarios. By explicitly naming the possible sources of packets on an ingress link, the specifications make it clear which entities can be involved in relay forwarding and how the adaptation layer should process packets from each. This supports functions such as routing, bearer mapping, and loop prevention, which are essential for reliable multi-hop communication. The stability of the definition in Rel-19 indicates that the concept has matured and is expected to remain stable in future releases.

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.

Rel-16 Initial

Initial definition introduced in TS 38.340 and TS 38.351. It defines an ingress link generically as a radio link on which a packet is received by a node, establishing the basis for adaptation layer forwarding in sidelink relay.

Wording changed to specify that the packet is received from a U2N Relay UE, a U2N Remote UE, or a network node. This aligns the definition with the 5G ProSe UE-to-Network relay architecture introduced in Rel-17.

Definition extended to include U2U Remote UE and U2U Relay UE, reflecting the addition of UE-to-UE relay communication. The ingress link now covers packets received from these additional entity types.

The definition text carried over unchanged from Rel-18. No further revision to the meaning of ingress link is indicated by the quoted definition.

Defining Specifications

3GPP specifications that define or reference Ingress link, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 38.340 vj00 Backhaul Adaptation Protocol (BAP) Specification Rel-19 read
TS 38.351 vj10 Sidelink Relay Adaptation Protocol (SRAP) Rel-19 read