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

Glossary term · Interface

N11

Reference point between the AMF and the SMF

Interface →

N11 is a 5G Core Network reference point connecting the Access and Mobility Management Function (AMF) to the Session Management Function (SMF) to exchange session management signaling such as PDU Session establishment, modification, and release requests.

Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
1 specs
N11 Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The N11 interface is a critical component within the 5G Core Network's Service-Based Architecture (SBA). It defines the logical communication path and associated protocols between the Access and Mobility Management Function (AMF) and the Session Management Function (SMF). Unlike traditional point-to-point interfaces, N11 is realized using HTTP/2-based service-based interfaces, where the SMF exposes its services (e.g., Nsmf_PDUSession service) that the AMF can invoke. The primary protocol stack for this communication is built on HTTP/2, JSON, and TLS for security, aligning with the cloud-native principles of 5G.

Operationally, the N11 interface carries all signaling messages related to the management of a User Equipment's (UE) Protocol Data Unit (PDU) Sessions. When a UE initiates a request for a new data session, the AMF, which handles registration and connection management, selects an appropriate SMF. The AMF then uses the N11 interface to forward the PDU Session Establishment Request to the chosen SMF. The SMF processes this request, interacting with the User Plane Function (UPF) and Policy Control Function (PCF), and sends responses back to the AMF via N11. This includes providing the necessary tunnel endpoint information for the N1 (UE-AMF) and N2 (RAN-AMF) interfaces.

Key information exchanged over N11 includes PDU Session IDs, QoS profiles, DN access parameters, and user plane security policy information. The interface supports procedures for session establishment, modification (e.g., QoS change), and release. It also facilitates the transfer of SM-related NAS messages transparently between the UE and the SMF via the AMF. The design of N11, as part of the SBA, allows for independent scaling and lifecycle management of the AMF and SMF network functions, enhancing network flexibility and enabling efficient network slicing.

Purpose & Motivation

The N11 interface was created as part of the 5G Core's radical redesign in 3GPP Release 15. Its purpose is to enable the clean separation of control plane functions—specifically, the separation of mobility management (AMF) from session management (SMF). In previous 4G EPC architectures, the MME combined both mobility and session management responsibilities for a UE. This monolithic design limited flexibility and scalability.

The introduction of N11 solves this by defining a standardized, service-based interface that allows these two core functions to be deployed, scaled, and updated independently. This separation is a cornerstone of the Service-Based Architecture, which is essential for supporting diverse 5G use cases like enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). It allows network operators to deploy specialized SMF instances for different network slices or services without impacting the mobility management layer.

Furthermore, by using modern web protocols (HTTP/2, JSON), N11 facilitates cloud-native deployment, automation, and easier integration with operator IT systems. It addresses the limitations of the GTP-C protocol used in 4G's S11 interface by providing a more flexible, extensible, and software-friendly signaling framework that is better suited for virtualized and containerized network environments.

What changed in its specifications

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

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 →

Technology family

Core network interfaces and reference points · Core Network

  1. R97 Gi, Gn, Gp
  2. Rel-7 Gx
  3. Rel-8 S1-MME, S1-U, S11, S5, S8, SGi
  4. Rel-15 N11, N2, N3, N4, N6, N7, N9

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 5 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-15 introduced

N11 is defined for the first time in Rel-15 as the AMF–SMF reference point, carrying N1/N2 SM payloads, N11 cause codes and session management interactions between AMF and SMF.

  • “N11: Reference point between the AMF and the SMF.” TS 23.501 v15.13.0
  • “an N1 SM payload, an N2 SM payload or both, over N11 (see clause 6.1.6.4);” TS 29.502 v15.10.0
  • “No mapping is required for the Nsmf_PDUSession service over N11 since the SMF includes the 5GSM cause” TS 29.524 v15.2.0
Rel-16 1 CR

In Rel-16, N11 gained new behaviour: an I-SMF with an N11 interface to the AMF is inserted outside the SMF service area, and the APN Rate Control attribute is carried across N11 and N16.

  • “The I-SMF has a N11 interface with the AMF and a N16a interface with the SMF” TS 23.501 v16.20.0
  • APN Rate Control attribute during PDU Session Establishment across N11 and N16 TS 29.502CR0222
  • “the NRF provides the IP address or FQDN of the N11/N16 interface of the SMF+PGW-C” TS 23.502 v16.19.0
Rel-17 1 CR

Onboarding indication is carried over N11 in an ON-SNPN, and the I-SMF with an N11 interface to the AMF is now also inserted when the SMF cannot serve the target DNAI.

  • Onboarding indication over N11 in an ON-SNPN TS 24.501CR3923
  • “or current SMF cannot serve the target DNAI for the traffic routing for local access to the DN, an I-SMF is inserted” TS 23.501 v17.15.0
Rel-18 specification text

The SMF may also provide a PDU Session Priority to the AMF, based on QoS parameters such as ARP and 5QI of a PDU Session.

  • “Based on the QoS parameters (e.g. ARP, 5QI) of a PDU Session, the SMF may also provide a PDU Session Priority to the AMF.” TS 23.501 v18.12.0
Rel-19 1 CR

N11 and N16a were enhanced in Rel-19 to support I-SMF based Local Offloading Management, with an I-SMF now insertable between AMF and SMF within the SMF service area.

  • N11 and N16a enhancements for I-SMF based Local Offloading Management TS 29.502CR0810
  • “The I-SMF has a N11 interface with the AMF and a N16a interface with the SMF” TS 23.501 v19.9.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read