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

Glossary term · Protocol

S1AP

S1 Application Protocol

Protocol →

S1AP is the control plane protocol used over the S1 interface between the LTE radio network (eNodeB) and the core network (MME) to manage connections, mobility, and sessions.

Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
5 specs
Also in
Radio Access Network
S1AP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The S1 Application Protocol (S1AP) operates on the S1-MME interface, which is the control plane connection between the eNodeB in the radio access network and the Mobility Management Entity (MME) in the core network. It is a layer 3 protocol that uses SCTP (Stream Control Transmission Protocol) as its reliable transport layer over IP. S1AP is responsible for all signaling procedures necessary to manage the connection and mobility of User Equipment (UE) between the radio access and core network.

The protocol defines a set of Elementary Procedures (EPs), which are the basic units of interaction. These procedures are categorized into Class 1 (requiring a response) and Class 2 (response not required). Key procedures include the Initial UE Context Setup, which establishes the first signaling connection for a UE and activates default bearers; the UE Context Modification procedure for updating bearer parameters; and the Handover Preparation and Execution procedures for managing mobility between eNodeBs or to other 3GPP radio technologies. S1AP also handles paging to locate idle UEs, NAS (Non-Access Stratum) transport to relay signaling between the UE and MME, and error indication functions.

Architecturally, S1AP messages are encapsulated within SCTP packets. Each SCTP stream can carry multiple S1AP dialogues. The protocol uses unique identifiers like the eNB UE S1AP ID and MME UE S1AP ID to correlate messages pertaining to a specific UE context across the interface. S1AP's design separates radio network layer signaling from the transport layer, providing robustness and efficiency for critical control functions. In 5G Non-Standalone (NSA) architectures (EN-DC, NGEN-DC), S1AP continues to be used for the connection between the LTE eNodeB and the EPC core, while the new NGAP protocol serves the 5G NR connection to the 5GC.

Purpose & Motivation

S1AP was created as part of the 3GPP Long Term Evolution (LTE) standard to provide a standardized, IP-based control plane protocol for the new S1 interface. Prior 3GPP systems like UMTS used a different suite of protocols (e.g., RANAP over Iu-CS and Iu-PS interfaces) that were tied to older circuit-switched and packet-switched architectures. The shift to an all-IP, flat architecture in LTE required a new, streamlined protocol.

The primary problem S1AP solves is enabling efficient and reliable signaling for mobility management, session management, and bearer management between the RAN and a separate, centralized core control node (the MME). It decouples the radio network complexity from the core network intelligence, allowing for scalable and flexible network deployments. Its creation was motivated by the need for reduced latency, higher capacity for signaling, and support for seamless mobility in the new packet-optimized LTE system.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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 →
TS 24.301Rel-18 → Rel-19

Rel-19 adds store-and-forward satellite operation for NTN, control plane CIoT data overhead reduction via EMM TRANSPORT and Data container IE, and RAT utilization control. It also adds disaster roaming indications and MINT-EPS support, plus MPS priority for messaging paging.

Full comparison in TS 24.301 →

Protocol Stack

Technology family

RAN interfaces · Radio Access Network

  1. Phase 1 A interface, Abis
  2. R99 Iu, Iu-BC, Iu-CS, Iu-PS, Iub, Iur, NBAP, Uu
  3. Rel-5 Iur-g
  4. Rel-8 S1, S1-MME, S1-U, S1AP, X2
  5. Rel-15 E1, E1AP, F1, F1-C, F1-U, F1AP, NG, NG-C, NG-U, NGAP, Xn, Xn-C, Xn-U
  • S1AP counterpart in another generation: NGAP
    “The application layer signalling protocol is referred to as NGAP (NG Application Protocol).” TS 38.410

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

S1AP is specified for the first time in TS 36.413 as the E-UTRAN radio network layer signalling protocol for the S1 interface, with its services, functions and elementary procedures.

  • “The present document specifies the E-UTRAN radio network layer signalling protocol for the S1 interface.” TS 36.413 v8.10.0
  • “S1AP provides the signalling service between E-UTRAN and the evolved packet core (EPC)” TS 36.413 v8.10.0
  • “S1 Application Protocol (S1-AP): Application Layer Protocol between the eNodeB and the MME.” TS 23.401 v8.18.0
Rel-9 specification text

Rel-9 adds S1AP Kill and Write-Replace Warning procedures for PWS/CMAS, and RANAP/BSSGP-to-S1AP cause value mappings for inter-RAT handover.

  • “S1AP Kill procedure for cancellation of PWS warning messages” TS 36.413 v9.10.0
  • “S1AP Write-Replace Warning procedure for PWS/CMAS” TS 36.413 v9.10.0
  • “This subclause defines a mapping of RANAP and S1AP cause values used in connection with inter RAT Handover” TS 29.010 v9.4.1
Rel-10 specification text

The MME UE S1AP ID 2 IE can now be sent in INITIAL CONTEXT SETUP REQUEST and PATH SWITCH REQUEST ACKNOWLEDGE, and the eNB stores it in the UE context for use in subsequent X2 handovers.

  • “If the MME UE S1AP ID 2 IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the eNB shall, if supported, store this information” TS 36.413 v10.9.0
  • “If the MME UE S1AP ID 2 IE is contained in the PATH SWITCH REQUEST ACKNOWLEDGE message, the eNB shall store this information” TS 36.413 v10.9.0
Rel-11 specification text

S1AP gained new procedure content in Rel-11, including the UE RADIO CAPABILITY MATCH REQUEST message, a HO cause value added to UE history information, and a PDCP SN extension modification.

  • “The MME initiates the procedure by sending a UE RADIO CAPABILITY MATCH REQUEST message.” TS 36.413 v11.8.0
  • “Addition of HO cause value to the UE history information in S1AP” TS 36.413 v11.8.0
  • “S1AP modification for PDCP SN extension” TS 36.413 v11.8.0
Rel-12 specification text

S1AP in Rel-12 gained new features: SIPTO@LN stand-alone, ProSe UE authorization, a new RRC establishment cause for VoLTE, and a secondary transparent container IE.

Rel-13 specification text

S1AP gained new behaviour in Rel-13: Connection Suspend/Resume procedures with UE Context Suspend/Resume messages, S1 Setup now clearing MME overload state, and ProSe UE relaying support.

  • “The MME sends an S1AP: UE Context Suspend Response message to the eNB to successfully terminate the Connection Suspend procedure initiated by the eNB” TS 23.401 v13.14.0
  • “The eNodeB notifies the MME that the UE's RRC connection is resumed in the S1-AP UE Context Resume Request message” TS 23.401 v13.14.0
  • “This procedure erases any existing application level configuration data in the two nodes and replaces it by the one received and clears MME overload state information at the eNB.” TS 36.413 v13.8.0
Rel-14 1 CR

S1AP in Rel-14 gains new procedure content: an eNB UE S1AP ID allocated and carried in the eNB CP RELOCATION INDICATION message, plus a new S1AP Cause for E-UTRAN pre-emption operations.

  • “The eNB shall allocate a unique eNB UE S1AP ID to be used for the UE and the eNB shall include this identity” TS 36.413 v14.9.0
  • S1AP Cause for E-UTRAN Pre-emption operations TS 36.413CR1534
Rel-15 2 CRs

S1AP (TS 36.413) gained new functionality in Rel-15, including unlicensed secondary RAT support, Warning Area Coordinates, Bluetooth/WLAN MDT measurements and an EPS Fallback indicator, and its transparent containers now also carry NG-RAN information.

  • Support for unlicensed access as secondary RAT in S1AP TS 36.413CR1563
  • S1AP Introduction of New Indicator for EPS Fallback TS 36.413CR1694
  • “which may carry either NG-RAN, E-UTRAN, UTRAN or GERAN specific information” TS 36.413 v15.11.0
Rel-16 3 CRs

S1AP in Rel-16 gained new cause values (insufficient UE capabilities, bearer pre-emption rate limit), UE Radio Capability for Paging support in RACS context, Error Indication changes, and NGAP-S1AP cause mapping.

  • Cause value on S1AP for insufficient UE capabilities CR 36.413 TS 36.413CR1816
  • (S1AP CR) support the UE Radio Capability for Paging in RACS context TS 36.413CR1840
  • S1AP Cause value for exceeding the bearer pre-emption rate limitation TS 36.413CR1824
Rel-17 1 CR

S1AP gained a Voice Service Indication in the Paging message for the Paging Cause Indication for Voice Service feature, alongside corrections to S1AP in TS 36.413 such as UPIP and NR NTN mobility restrictions.

  • “should provide a Voice Service Indication in the S1AP Paging message for the MMTel voice service” TS 23.401 v17.11.0
  • UPIP EPC Correction on S1AP TS 36.413CR1886
  • “Mobility Restrictions with NR NTN - S1AP Impacts” TS 36.413 v17.6.0
Rel-18 3 CRs

S1AP gained support for coarse UE location information reporting from MME to eNB and for mobility restrictions with NR NTN, and the S1AP PPID and SCTP destination port number were corrected.

  • Coarse UE Location Information Reporting from MME to eNB - S1AP Impacts TS 36.413CR1957
  • Mobility Restrictions with NR NTN - S1AP Impacts TS 36.413CR1924
  • Correction on S1AP PPID and Destination Port Number over SCTP TS 36.412CR0024
Rel-19 1 CR

S1AP in Rel-19 gains Time Reference Distribution Information support, and the ERROR INDICATION procedure now allows identifying an NB-IoT UE by S-TMSI under Control Plane CIoT EPS Optimisation.

  • Time Reference Distribution Information in S1AP TS 36.413CR1956
  • “upon receiving the S-TMSI IE in the ERROR INDICATION message, the receiving node shall use the S-TMSI to identify the UE” TS 36.413 v19.2.0

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 24.301 vk10 EPS NAS Mobility and Session Management Rel-20 read
TS 24.801 v810 CT1 SAE NAS Aspects for EPC Rel-8 read
TS 36.410 vj00 S1 Interface: General Aspects and Principles Rel-19 read
TS 36.455 vj00 LTE Positioning Protocol Annex (LPPa) Rel-19 read