Transport Network Layer Association

Description

A Transport Network Layer Association (TNLA) is a logical connectivity context established between two peer network functions over the Transport Network Layer (TNL). It represents a specific transport path, identified by a combination of transport layer addressing information. For example, between a gNB (or ng-eNB) and an AMF in the 5G system, a TNLA is defined for the NG interface and is associated with a specific Stream Control Transmission Protocol (SCTP) association. Each SCTP association between the gNB and an AMF, characterized by a specific pair of IP addresses and SCTP port numbers, constitutes one TNLA. A single gNB can establish multiple TNLAs to a single AMF or to multiple AMFs for redundancy and load distribution.

Architecturally, TNLAs are a crucial part of the N2 (NG-C) and N3 (NG-U) interface management. For the control plane (N2), each TNLA supports the transport of NG Application Protocol (NGAP) messages. The AMF and gNB use the TNLA Identifier (TNL Association ID) to reference a specific transport path when sending messages. The setup of TNLAs is part of the NG interface setup procedure. The concept also extends to the user plane, where multiple TNLAs can be used for N3 GTP-U tunnels between a gNB and a UPF, although the management mechanisms differ.

How it works involves several procedures. During initial setup, a gNB discovers available AMFs and initiates the establishment of SCTP associations, thereby creating TNLAs. The gNB and AMF exchange configuration data and assign a TNL Association ID to each. Once established, NGAP messages can be sent over any available TNLA to the peer. The endpoints perform load balancing and failover across TNLAs. If one TNLA fails (e.g., due to a path or SCPT association failure), traffic is seamlessly shifted to another active TNLA, ensuring high availability. The management of TNLAs includes monitoring their status (up/down), capacity, and performance, which is vital for network reliability and efficient load distribution.

Purpose & Motivation

The TNLA concept was formally introduced and emphasized in 3GPP Release 15 as part of the 5G New Radio (NR) architecture to address the requirements for enhanced reliability, scalability, and flexibility in the transport network interconnecting disaggregated RAN and core network functions. Its creation was motivated by the need to move beyond simple point-to-point links. Previous generations had redundancy mechanisms, but 5G's service-based architecture and cloud-native deployment models demanded more explicit and flexible transport path management.

TNLA solves the problem of single point of failure in the transport connectivity between critical nodes like the gNB and AMF. By enabling multiple independent transport paths (TNLAs), it provides inherent redundancy. It also addresses load balancing; network traffic (signaling load) can be distributed across multiple TNLAs to prevent congestion on a single path. This is especially important in centralized/cloud RAN deployments where a central unit may connect to many distributed units and core functions. Furthermore, TNLAs facilitate flexible AMF pooling and load balancing in the core network, as a gNB can have TNLAs to different AMFs within an AMF Set. This allows for efficient resource utilization and graceful maintenance operations without service interruption.

Key Features

• Represents a logical transport path, typically mapped to an SCTP association for control plane
• Identified by a TNL Association ID and transport addresses (IP, port)
• Enables multiple parallel connections between a node pair for redundancy
• Supports load balancing of application protocol messages (e.g., NGAP) across associations
• Allows for independent failure and recovery of individual transport paths
• Fundamental for AMF pooling and workload distribution in 5GC

Evolution Across Releases

Defining Specifications