Description
The S1-MME interface is a specific implementation of the S1 control plane (S1-C) that connects the Evolved NodeB (eNodeB) in the E-UTRAN to the Mobility Management Entity (MME) in the Evolved Packet Core (EPC). As defined in 3GPP specifications, it is a logical interface that physically traverses an IP-based transport network, utilizing the Stream Control Transmission Protocol (SCTP) at the transport layer to ensure reliable, ordered, and error-checked delivery of signaling messages. The interface employs the S1 Application Protocol (S1AP), which encapsulates a wide range of procedures and messages necessary for the control and management of UE connections. S1-MME is point-to-point in nature, meaning each eNodeB establishes one or more S1-MME associations with MMEs, often in a pooled configuration to enhance reliability and load distribution.
Key operational aspects of S1-MME include the handling of Initial UE Context Setup, where the MME provides the eNodeB with UE-specific security and QoS parameters after authentication; Bearer Management, involving the activation, modification, and deactivation of Evolved Radio Access Bearers (E-RABs) to support user data flows; and Mobility Management, which encompasses handover preparation, execution, and cancellation procedures for UEs moving between cells or access technologies. The interface also supports Paging, where the MME initiates paging requests to locate idle UEs, and NAS Transport, which allows Non-Access Stratum messages (e.g., for attachment or tracking area updates) to be relayed transparently between the UE and MME. Additionally, S1-MME facilitates Error Indication and Reset procedures to maintain interface integrity and recover from failures.
Architecturally, S1-MME is designed with scalability and flexibility in mind, supporting features like S1-flex, which enables an eNodeB to connect to multiple MMEs within a pool area. This allows for load balancing and redundancy, reducing the risk of service disruption during MME failures. The interface strictly separates control plane signaling from user plane data (which flows over S1-U), adhering to the Control and User Plane Separation (CUPS) principle. This separation allows independent scaling and optimization of network functions—for instance, MMEs can be centralized for efficient signaling processing, while eNodeBs and user plane gateways are distributed to minimize latency. In practice, S1-MME is crucial for maintaining UE states (e.g., ECM-IDLE or ECM-CONNECTED), enforcing security policies through key management, and coordinating radio resource allocation, thereby forming the backbone of LTE's efficient, low-latency control plane.
Purpose & Motivation
The S1-MME interface was developed in 3GPP Release 8 as a core element of the LTE/EPC architecture to overcome inefficiencies in prior 3GPP systems like UMTS. In UMTS, the control plane interface (Iu-CS and Iu-PS) involved the Radio Network Controller (RNC) as an intermediary between NodeBs and the core network, adding complexity, latency, and potential bottlenecks. S1-MME was created to flatten the network by enabling direct signaling between the base station (eNodeB) and the control entity (MME), eliminating the RNC layer. This design reduces signaling delay, simplifies network topology, and improves responsiveness for mobility events and session management, which are vital for supporting high-speed data services and real-time applications.
Historically, the drive for S1-MME emerged from the need to transition to an all-IP network architecture that could handle exponential growth in mobile data traffic, spurred by the proliferation of smartphones and bandwidth-intensive apps. By separating the control plane (via S1-MME) from the user plane, 3GPP allowed operators to deploy and scale network functions independently—for example, concentrating MMEs for cost-effective signaling handling while distributing eNodeBs for coverage. This separation also facilitated the introduction of advanced features like network sharing, where multiple operators could use shared radio access infrastructure while maintaining independent core control, and laid the groundwork for future evolution toward 5G by providing a flexible interface that could be extended with new procedures.
Moreover, S1-MME addresses critical issues of reliability and scalability through mechanisms such as MME pooling and S1-flex, which distribute control traffic across multiple MME nodes to prevent single points of failure and balance load dynamically. This was a significant advancement over earlier architectures, where the failure of a control node could lead to widespread outages. By standardizing S1-MME across releases, 3GPP ensured backward compatibility and smooth interworking with legacy systems, enabling gradual network upgrades. Ultimately, S1-MME's purpose is to provide a robust, efficient, and scalable control plane interface that underpins key LTE functions like mobility management, security authentication, and bearer control, thereby enhancing overall network performance and user experience.
What changed in its specifications
The latest release-to-release comparison of specifications that define S1-MME. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.
Full comparison in TS 36.300 →Technology family
RAN interfaces · Radio Access Network
Core network interfaces and reference points · Core Network
- S1-MME counterpart in another generation: N2
“For 3GPP access the AMF determines the RAT type the UE is camping on based on the Global RAN Node IDs associated with the N2 interface” TS 23.501
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 sourcesDocumented changes in 4 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.
S1-MME is defined for the first time as the S1 control plane interface between the eNB and the MME, using SCTP/IP transport and the S1-AP protocol.
- “The S1 control plane interface (S1-MME) is defined between the eNB and the MME.” TS 36.300 v8.12.0
- “S1-MME towards an MME and S1-U towards an S- GW.” TS 36.410 v8.3.0
- “the eNodeB and MME shall exchange application level configuration data over the S1-MME application protocol with the S1 Setup Procedure” TS 36.300 v8.12.0
In Rel-10, S1-MME gains new roles: it carries the collocated L-GW IP address of the HeNB for LIPA and L-GW correlation ids, and the DeNB appears as an MME on S1-MME to a relay node.
- “transfer of the collocated L-GW IP address of the HeNB over S1-MME to the EPC at every idle-active transition,” TS 36.300 v10.12.0
- “Due to the proxy functionality, the DeNB appears as an MME (for S1-MME), an eNB (for X2) and an S-GW (for S1-U) to the RN.” TS 36.300 v10.12.0
S1-MME gains new roles in Rel-12: dual connectivity (single S1-MME per UE terminated at the MeNB), carrying the L-GW address for SIPTO@LN, and conveying ProSe authorization from MME to eNodeB.
- “There is only one S1-MME connection per DC UE between the MeNB and the MME.” TS 36.300 v12.10.0
- “transfer of the collocated L-GW IP address of the eNB over S1-MME to the EPC at every idle-active transition;” TS 36.300 v12.10.0
- “in case of ProSe it is also used to convey the ProSe direct services authorization from MME to eNodeB.” TS 23.303 v12.8.0
S1-MME gains new roles in Rel-13: carrying the SeNB L-GW address and SIPTO correlation information in dual connectivity, and terminating at the eNB for LWA with one connection per UE.
- “The MeNB supports the transfer of the L-GW IP address of SeNB over S1-MME to the EPC within every Uplink NAS Transport procedure;” TS 36.300 v13.14.0
- “There is only one S1-MME connection per LWA UE between the eNB and the MME.” TS 36.300 v13.14.0
- Correction of S1-MME definition to include authorization for ProSe Direct Communication TS 23.303CR0265
Defining Specifications
3GPP specifications that define or reference S1-MME, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.410 vj00 | S1 Interface: General Aspects and Principles | Rel-19 read |