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

Glossary term · Interface

S11

Reference point between the MME and the Serving GW

Interface →

S11 is a 4G EPC reference point connecting the Mobility Management Entity to the Serving Gateway as a pure control-plane interface using GTP-C for session, mobility, S-GW selection, and EPS bearer management signaling.

Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
1 specs
S11 Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The S11 is a critical control plane-only interface within the 4G Evolved Packet Core, connecting the Mobility Management Entity (MME)—the primary control node for the access network—with the Serving Gateway (S-GW)—the main user plane anchor. It operates exclusively using the GPRS Tunneling Protocol for the control plane (GTP-Cv2). The interface does not carry any user data traffic; its sole purpose is to exchange signaling messages that manage the user plane tunnels (GTP-U) established over interfaces like S1-U and S5.

The MME uses the S11 interface to control the S-GW's user plane resources. Key procedures initiated by the MME over S11 include the Create Session Request, which instructs the S-GW to establish a default bearer towards the P-GW (via S5) and towards the eNodeB (via S1-U). This message includes crucial information such as the UE's IMSI, APN, and the assigned IP address from the P-GW. The S-GW responds with the necessary Tunnel Endpoint Identifiers (TEIDs) for the downlink data path.

During mobility events, such as a handover that triggers an S-GW change, the MME coordinates the relocation via S11 signaling with both the source and target S-GWs. It also uses S11 for bearer management procedures like Modify Bearer (to update TEIDs or QoS) and Delete Session. The interface also supports the forwarding of temporary user identities (e.g., S-TMSI) and charging identifiers between the network entities. The protocol stack typically runs over IP (UDP or SCTP) and is secured within the operator's trusted core network domain.

Purpose & Motivation

The S11 interface was created in 3GPP Release 8 to establish a clear separation between the control plane (MME) and the user plane (S-GW) in the new LTE architecture. In pre-4G systems, such as UMTS, the SGSN handled both signaling and user data forwarding, which limited scalability and flexibility for handling massive data traffic growth anticipated with LTE.

The S11 interface solved this by providing a standardized signaling channel that allows the MME to manage user plane resources without being in the data path. This separation enables independent scaling of control and user plane capacities; operators can deploy large pools of MMEs for signaling capacity and separate, high-throughput S-GWs for data processing. It is a key enabler of the EPC's flat IP architecture.

Furthermore, S11 provides the MME with direct control over the S-GW, which is essential for efficient mobility management. It allows the MME to select the optimal S-GW for a UE during initial attachment and to seamlessly relocate the S-GW during tracking area updates or handovers, ensuring session continuity. This design directly influenced the 5G architecture, where a similar functional split exists between the AMF and SMF/UPF, albeit with different protocols (HTTP/2 vs. GTP-C).

What changed in its specifications

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

TS 23.401Rel-18 → Rel-19

Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.

Full comparison in TS 23.401 →

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 12 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-8 introduced

S11 is specified for the first time as the MME–Serving GW reference point, using GTPv2-C for EPS bearer management, with TEID-C handling and S11 control-plane protocol stack.

  • “S11: Reference point between MME and Serving GW.” TS 23.401 v8.18.0
  • “GPRS Tunnelling Protocol for the control plane (GTP‑C): This protocol tunnels signalling messages between MME and S‑GW (S11).” TS 23.401 v8.18.0
  • “GTPv2-C shall be used across the following EPC signalling interfaces: S3, S4, S5, S8, S10, S11 and S16.” TS 29.274 v8.12.0
Rel-9 specification text

TS 29.274 Rel-9 adds S11/S4 GTP-C requirements, such as new flags and IE inclusion rules for MME-to-SGW signalling during attach, TAU and handover with SGW relocation.

  • “This IE shall be included by the MME over S11 during Initial Attach, UE Requested PDN Connectivity procedure.” TS 29.274 v9.14.0
  • “Change Reporting support Indication: shall be used on S4/S11, S5/S8 and set if the SGSN/MME supports location Info Change Reporting.” TS 29.274 v9.14.0
  • “If ISR is active, this IE shall also be included on the S11 interface in the S1-U GTP-U tunnel setup procedure” TS 29.274 v9.14.0
Rel-10 specification text

S11 behaviour changed in Rel-10: GTPv2-C message and IE usage on S11 was revised, and the S11 interface was newly used between the MME and the S-GW/P-GW functions in the DeNB for relay node operation.

  • “Downlink Data Notification, Downlink Data Notification Acknowledge and Downlink Data Notification Failure Indication messages sent on S11/S4 as part of the Network Triggered Service Restoration procedure” TS 29.274 v10.15.0
  • “The MME performs S11 interface signalling with the S-GW/P-GW located in the DeNB;” TS 23.401 v10.13.0
  • “The MME/SGSN shall include the ME Identity (MEI) IE on the S11/S4 interface:” TS 29.274 v10.15.0
Rel-11 1 CR

GTPv2-C messaging on S11 was extended: Downlink Data Notification and PGW Downlink Triggering Notification handling on S11/S4 changed, and S11/S4 cause mapping and IE presence conditions were specified or corrected.

  • “Downlink Data Notification message sent on S11/S4 as part of the Network Triggered Service Restoration procedure” TS 29.274 v11.14.0
  • “PGW Downlink Triggering Acknowledge message on S11/S4” TS 29.274 v11.14.0
  • Mapping of NAS ESM/SM Cause codes to S11/S4 Cause codes TS 29.274CR1198
Rel-12 1 CR

GTPv2 on S11 gained new requirements in Rel-12: GTP-C overload control information is carried on S11/S4, and flags such as Piggybacking Supported and Change Reporting support indication were specified for S11.

  • “the MME/S4-SGSN shall include this IE on the S11/S4 interface. In that case, the SGW shall forward this IE on the S5/S8 interface.” TS 29.274 v12.15.0
  • “This feature is supported over S4, S11, S5 and S8 interfaces via GTPv2 control plane protocol.” TS 23.401 v12.11.0
  • Overload/Load Control Information IE on S2a/S2b/S4/S11 TS 29.274CR1542
Rel-13 specification text

In Rel-13 GTPv2-C on S11 gained new signalling: an S11-U Tunnel Flag for user data in NAS signalling, an NBIFOM support indication, and UE Available for Signalling handling on S11.

  • “S11-U Tunnel Flag: this flag shall be set to 1 on the S11 interface if user data is transported in NAS signalling.” TS 29.274 v13.13.0
  • “NBIFOM Support Indication: This flag shall be set to 1 on S11/S4 if the MME/SGSN supports NBIFOM.” TS 29.274 v13.13.0
  • “the new MME shall setup the S11 user plane with the new Serving GW and invoke data forwarding” TS 23.401 v13.14.0
Rel-14 specification text

Rel-14 adds an eNB Change Reporting Support Indication flag for S11 and S5/S8, and allows the MME to include an IE on S11 when the IMSI is unavailable.

  • “eNB Change Reporting Support Indication: This flag shall be set to 1 on S11 and S5/S8 interfaces if the MME supports location Info Change Reporting” TS 29.274 v14.8.0
  • “The MME/SGSN may include this IE on the S11/S4 interface if the IMSI is not available.” TS 29.274 v14.8.0
Rel-15 specification text

In Rel-15, S11 gained new signalling: flags such as 5GS Interworking Indication and LTE-M RAT Type reporting, MME-to-SGW Secondary RAT usage data reporting, and a description in TS 23.401 of S11 as a control-plane reference point with an S11-U user plane for CIoT.

  • “5GS Interworking Indication(5GSIWKI): this flag shall be set to 1 on S11, S5/S8 and S2b interfaces if the UE supports N1 mode” TS 29.274 v15.9.0
  • “the MME shall include this IE on the S11 interface if it has received Secondary RAT usage data from eNodeB in an X2-based handover with Serving GW relocation” TS 29.274 v15.9.0
  • “in order to support Control Plane CIoT EPS Optimisation, the S11-U reference point provides user plane between MME and Serving GW.” TS 23.401 v15.13.0
Rel-16 specification text

GTP-C on S11 gained new flags and IE conditions in Rel-16, including 5GC Not Restricted indications, MT-EDT applicability flags, and an MT-EDT feature indication from SGW to MME.

  • “this flag shall be set to 1 on S11, S5/S8 and S2b interfaces if the sending node (i.e. MME or ePDG) supports setting the 5GCNRI flag.” TS 29.274 v16.13.0
  • “this flag shall be set to "1" on the S11 interface if MT-EDT is applicable to the PDN connection;” TS 29.274 v16.13.0
  • “Support of this feature may be indicated over the S11 interface, from the SGW to the MME.” TS 29.274 v16.13.0
Rel-17 specification text

Rel-17 adds a User Plane Integrity Protection Support Indication flag set by the MME on S11 and forwarded by the SGW on S5/S8, plus PGW Change Indication handling for PDN connection restoration over S11.

  • “This flag shall be set to 1 by the MME on the S11 interface, if the UE, MME and E-UTRAN supports User Plane Integrity Protection with EPS.” TS 29.274 v17.12.0
  • “this flag shall be set to 1 by the MME/ePDG over the S11/S2b interface if the Create Session Request is to move an existing PDN connection” TS 29.274 v17.12.0
Rel-18 1 CR

GTP-C signalling on S11 was extended in Rel-18, including a new Satellite RAT Type reporting to PGW indication (SRTPI) flag and Trace Reporting Consumer URI for streaming trace, plus support of the PGW-C/SMF Set feature over S11.

  • “Satellite RAT Type reporting to PGW Indication (SRTPI): this flag shall be set to 1 on S11, based on operator policy or roaming agreements” TS 29.274 v18.8.0
  • “This IE may be present on the S4/S11 interface if an SGW trace is activated” TS 29.274 v18.8.0
  • Support of PGW-C/SMF Set feature over S11 TS 29.274CR2094
Rel-20 specification text

Adds new S11 flags for UDP/IP Header Removal & Restoration: UHRRSI set by the MME when it supports the feature, and UHRREI set by the SGW when the PGW has enabled it.

  • “UHRR Support Indication (UHRRSI): this flag shall be set to 1 on the S11 interface if the MME supports UDP/IP Header Removal & Restoration.” TS 29.274 v20.0.0
  • “This flag shall also be set to 1 on the S11 interface if the SGW receives this indication from the PGW.” TS 29.274 v20.0.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read