NNI

Network to Network Interfaces

Interface →
Introduced in R99 Also in: Services, Radio Access Network

NNI is the standardized interface between different networks or network elements in 3GPP systems that enables interoperability, signaling, and data exchange across network boundaries.

Category
Interface
Introduced
R99
Where
Core Network › Evolved Packet Core
Also touches
2 segments
Specifications
20 specs
NNI Description Purpose Related Classification Detected Changes Specifications

Description

Network to Network Interfaces (NNI) are standardized interfaces defined by 3GPP that facilitate communication between distinct networks or between different network elements within a multi-network environment. These interfaces are critical for enabling interoperability, signaling, and data exchange across network boundaries, such as between two mobile network operators, between a core network and an external network, or between different administrative domains. NNI specifications cover protocols, message formats, and procedures to ensure seamless interaction.

In 3GPP architecture, NNI interfaces are implemented across various domains, including core network interfaces (e.g., between MMEs in different networks), roaming interfaces (e.g., for inter-carrier communication), and interfaces with external networks like IP networks or other service providers. Examples include interfaces for mobility management, session establishment, charging data transfer, and security context exchange. They often use protocols such as Diameter, GTP, or SIP, tailored for inter-network scenarios.

The operation of an NNI involves standardized message exchanges between network entities. For instance, during inter-network roaming, an NNI allows the home network to authenticate a user visiting a foreign network, transfer subscriber data, and handle billing information. Key components include the interface endpoints (e.g., network gateways or border controllers), the protocol stack (defining transport, session, and application layers), and the message set (including requests, responses, and error codes). These interfaces ensure that networks can cooperate without proprietary adaptations, supporting global mobility and service continuity.

NNIs play a vital role in enabling features like international roaming, inter-carrier service delivery, and network federation. They provide the technical foundation for networks to share resources, coordinate policies, and offer seamless user experiences across administrative boundaries. By standardizing NNIs, 3GPP ensures that mobile operators worldwide can interconnect reliably, fostering a cohesive global telecommunications ecosystem.

Purpose & Motivation

NNI interfaces were created to solve the problem of interoperability between different networks and network elements in mobile telecommunications. As mobile networks evolved from isolated systems to interconnected global infrastructures, the need for standardized interfaces became paramount to enable roaming, multi-network services, and efficient resource sharing. Without NNIs, each network interconnection would require custom, proprietary solutions, leading to complexity, high costs, and limited scalability.

Historically, early mobile networks had limited inter-network capabilities, but with the growth of global roaming and multi-operator services, 3GPP introduced NNI specifications from R99 onwards. These interfaces address limitations such as incompatible signaling protocols, disparate charging mechanisms, and security gaps between networks. They provide a common framework for networks to exchange user data, manage sessions, handle billing, and enforce security policies across boundaries.

The motivation for NNI development includes supporting international mobility, enabling service providers to offer seamless experiences across networks, and facilitating network resource optimization (e.g., sharing infrastructure). By defining NNIs, 3GPP allows operators to interconnect efficiently, reducing deployment barriers and fostering competition and innovation in the telecommunications market. They are essential for the modern mobile ecosystem, where users expect uninterrupted service regardless of network or location.

Classification

Part ofGTP

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 4 changes

In Release 15, enhancements to the NNI included the introduction of Functional Alias Management over the II-NNI interface and the definition of the bSRVCC-MT NNI procedure. Corrections were also made to II-NNI conditions specifically regarding the handling of the P-Early-Media header field within SIP UPDATE requests.

  • Functional Alias Management over II-NNI TS 29.165CR0961
  • bSRVCC-MT NNI TS 29.165CR0947
  • Correction of II-NNI condition related to P-Early-Media header field TS 29.165CR0938
  • Correction of II-NNI condition related to P-Early-Media header field for the UPDATE request TS 29.165CR0940
Rel-16 3 changes

In Release 16, the specifications for the Inter-IMS Network to Network Interface (II-NNI) were enhanced with clarifications and corrections. Specifically, this included defining usage restrictions for the P-Asserted-Identity header field and providing corrections for the P-Charging-Vector header field over this interface. Furthermore, new requirements for the Registration-Loss (RLOS) procedure were added to operate over the II-NNI.

  • Clarification of the usage restriction of P-Asserted-Identity header field over the II-NNI. TS 29.165CR0990
  • Corrections on the II-NNI specifications on the P-Charging-Vector header field TS 29.165CR1006
  • Adding the RLOS requirements over the II-NNI TS 29.165CR1008
Rel-17 1 change

In Release 17, the enhancement for NNI functions introduced support for an IMS data channel at the Inter-IMS Network to Network Interface (II-NNI). This provides a new capability for transporting data session information directly over this critical inter-network interface.

  • IMS data channel at the II-NNI TS 29.165CR1024

Explore further

Broader topics and technologies where NNI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19
TS 23.205 vj00 Bearer Independent CS Core Network Stage 2 Rel-19
TS 23.218 vj00 IMS Call Model Specification Rel-19
TS 23.231 vj00 SIP-I based CS core network stage 2 Rel-19
TS 23.278 vj00 CAMEL for IMS Stage 2 Specification Rel-19
TS 23.889 va00 Local Call Local Switch Core Network Impact Study Rel-10
TS 24.802 vc10 IMS II-NNI Traversal Scenario Determination Study Rel-12
TS 25.424 vj00 UTRAN Iur Interface Data Transport & Signalling Rel-19
TS 25.426 vj00 UTRAN Iur/Iub Transport Bearers Rel-19
TS 26.114 vj10 IMS Multimedia Telephony Media Handling Rel-19
TR 26.930 vj00 WebRTC Enhancements for Immersive RTC over 5G Rel-19
TS 29.165 vj10 Inter-IMS Network to Network Interface (NNI) Rel-19
TS 29.235 vj00 SIP-I CS Core Network Interworking Rel-19
TS 29.414 vj00 Nb Interface Bearer Transport & Control Protocols Rel-19
TS 32.260 vj10 IMS Charging Management Rel-19
TS 32.298 vj30 Charging Data Record (CDR) Parameter Specification Rel-19
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 33.790 vj10 Security for Next-Gen Real-Time Communication Phase 2 Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.