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

Glossary term · Other

TNL

Transport Network Layer

Other →

TNL is the underlying IP-based network infrastructure that provides connectivity and transport services for user data and signaling between nodes in a 3GPP system.

Introduced
Rel-5
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
26 specs
TNL Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Transport Network Layer (TNL) in 3GPP systems refers to the foundational network infrastructure responsible for carrying all control plane signaling and user plane data traffic between different network functions and nodes. It is a logical layer that abstracts the physical transmission links (e.g., fiber, microwave) and switching/routing equipment. The TNL provides the transport service that interconnects elements of the Radio Access Network (RAN), the Core Network (CN), and between RAN and CN. Its primary role is to offer a reliable, scalable, and often quality-of-service (QoS)-aware packet delivery service.

Architecturally, the TNL is not a single entity but a collection of technologies and protocols. In modern 3GPP networks (from 3G onwards), it is predominantly based on Internet Protocol (IP). For user plane traffic in the RAN, the TNL utilizes the GPRS Tunneling Protocol for the user plane (GTP-U) over UDP/IP to create tunnels between nodes like the gNB and UPF, ensuring traffic isolation and forwarding based on Tunnel Endpoint Identifiers (TEIDs). For control plane signaling, protocols like Stream Control Transmission Protocol (SCTP) over IP are commonly used for reliable signaling transport, such as on the NGAP interface between gNB and AMF. The TNL also encompasses lower-layer technologies like Ethernet, MPLS, or optical transport (OTN) for the physical and data link layers.

How it works involves the higher 3GPP protocol layers (e.g., RRC, NGAP, F1-AP) using the services of the TNL. They pass Protocol Data Units (PDUs) to the TNL, which is responsible for their delivery to the peer entity. The TNL handles functions like routing, congestion control, fragmentation, and in some cases, security (e.g., IPsec). In the context of RAN, specific TNL associations (TNLAs) are established between nodes to provide redundancy and load distribution. The performance of the TNL—its latency, jitter, packet loss, and bandwidth—directly impacts the performance of the mobile services it supports, making its design and management critical for network operators.

Purpose & Motivation

The concept of a distinct Transport Network Layer has been fundamental since the early days of digital mobile networks. Its purpose is to separate the concerns of the radio-specific and service-specific protocol layers from the general problem of data transport. This abstraction allows the 3GPP radio and core network architectures to evolve independently of the underlying transport technology. Initially, in 2G and early 3G, transport was often based on TDM circuits. The shift to a packet-based TNL (IP) from 3GPP Release 5 onwards was driven by the need for greater efficiency, flexibility, and cost-effectiveness to handle growing data traffic.

The TNL solves several critical problems. It provides a unified, scalable backbone for aggregating traffic from thousands of base stations. It enables network sharing and virtualization by providing a common transport fabric. By defining standard transport protocols (like GTP, SCTP), it ensures multi-vendor interoperability between network equipment. The evolution towards an all-IP TNL addressed the limitations of circuit-switched transport, which was inefficient for bursty data traffic and cumbersome to scale. The ongoing purpose of the TNL is to support ever-increasing demands for capacity, lower latency (for URLLC), synchronization, and network slicing by incorporating advancements in transport technologies like Segment Routing, Time-Sensitive Networking (TSN), and enhanced QoS mechanisms.

What changed in its specifications

The latest release-to-release comparison of specifications that define TNL. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change
  • Introduction of TNL Address discovery for EN-DC TS 36.300CR1229

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read
TS 25.415 vj00 Iu Interface User Plane Protocol Rel-19 read
TS 25.424 vj00 UTRAN Iur Interface Data Transport & Signalling Rel-19 read
TS 25.425 vj00 UTRAN Iur Interface User Plane Protocols Rel-19 read
TS 25.435 vj00 UTRAN Iub Interface User Plane Protocols Rel-19 read
TS 25.442 vj00 Node B Implementation Specific O&M Transport via RNC Rel-19 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TS 28.874 vj10 Study on Management Aspects of NTN Phase 2 Rel-19 read
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19 read
TS 32.860 ve00 D-SON MLB OAM Enhancement Study Rel-14 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19 read
TS 36.410 vj00 S1 Interface: General Aspects and Principles Rel-19 read
TS 36.440 vj00 E-UTRAN MBMS Architecture Description Rel-19 read
TS 36.456 vj00 SLm Interface Introduction Rel-19 read
TS 36.459 vj00 SLmAP for E-UTRAN Positioning Rel-19 read
TS 36.842 vc00 Small Cell Enhancements for LTE Higher Layers Rel-12 read
TS 37.470 vj00 W1 Interface Introduction for ng-eNB Rel-19 read
TS 37.480 vj10 E1 Interface General Aspects and Principles Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.460 vj00 E1 Interface General Aspects and Principles Rel-19 read
TS 38.470 vj20 F1 Interface Specification for NG-RAN Rel-19 read