Transit Network Selection

Description

Transit Network Selection (TNS) is a core network function defined within the 3GPP specifications that governs how a mobile network operator (MNO) selects an intermediate or transit network to route a call when the destination is outside its own network. It operates within the call session control functions, particularly at the originating side. When a call is destined for a subscriber in another operator's network or a different country, the originating network must decide which intermediary carrier or set of carriers will transport the call to the destination network. This selection is not arbitrary; it is based on a set of configurable criteria and data known as the Transit Network Selection list or data.

The architecture involves the network elements responsible for call control, such as the Mobile Switching Centre (MSC) in circuit-switched domains or the Call Session Control Function (CSCF) in the IP Multimedia Subsystem (IMS). These elements consult internal TNS data, which is typically provisioned by the operator. This data contains a prioritized list of preferred transit network identifiers, often using codes like the Carrier Identification Code (CIC) or network routing numbers. The selection logic evaluates factors such as the destination number (e.g., country code, national destination code), time of day, and commercial agreements (e.g., least-cost routing). The chosen transit network identifier is then included in the call setup signaling, such as in the Initial Address Message (IAM) in ISUP, to instruct subsequent switches on the desired route.

Its role is integral to the global telephony ecosystem. It enables operators to manage their interconnect relationships strategically. By selecting specific transit carriers, an operator can control costs, ensure service quality (e.g., by avoiding congested routes), and comply with regulatory requirements for call termination. The TNS mechanism ensures that the complex web of bilateral and multilateral agreements between operators is translated into actionable routing decisions on a per-call basis, making inter-operator communication both possible and economically viable.

Purpose & Motivation

The primary purpose of Transit Network Selection is to solve the fundamental problem of economically and reliably connecting calls between different telecommunications networks. In the early days of telephony, operators had direct connections (interconnects) with every other operator they needed to reach, which became impractical as the number of operators grew globally. TNS was created to introduce flexibility and efficiency into this process.

It addresses the limitation of static, point-to-point routing by allowing dynamic selection of intermediary carriers, known as transit networks. This enables operators to establish relationships with a few major transit carriers rather than every possible destination operator directly. The motivation was heavily commercial: to implement least-cost routing (LCR), where the network automatically chooses the cheapest available route for a call based on dynamically updated commercial agreements. Furthermore, it provides redundancy; if the primary transit carrier is unavailable, the system can fail over to a secondary one, improving call completion rates.

Historically, as networks evolved from national monopolies to competitive multi-operator environments, the need for a standardized, intelligent routing mechanism became critical. TNS provided this standardized framework within 3GPP, allowing operators to automate complex routing decisions that balance cost, quality, and reliability, which would be impossible to manage manually at the scale of millions of calls.

Key Features

• Enables dynamic selection of intermediary carriers (transit networks) for outbound calls.
• Supports routing based on destination analysis (e.g., country code, network code).
• Facilitates Least Cost Routing (LCR) by prioritizing transit options based on cost agreements.
• Provides routing redundancy and failover capabilities by using prioritized lists.
• Utilizes standardized identifiers like Carrier Identification Codes (CIC) in signaling.
• Configurable by the operator to reflect commercial agreements and routing policies.

Evolution Across Releases

Defining Specifications