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

Glossary term · Protocol

SABP

Service Area Broadcast Protocol

Protocol →

SABP is the 3GPP protocol used for broadcasting messages, such as emergency alerts, over a specific service area in UMTS networks to deliver information efficiently to multiple user devices simultaneously.

Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
4 specs
SABP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Service Area Broadcast Protocol (SABP) is a critical control-plane protocol defined within the 3GPP UMTS architecture, specifically for managing broadcast services. It operates between the Cell Broadcast Centre (CBC) and the UMTS Radio Access Network (UTRAN), specifically the Radio Network Controller (RNC). SABP is the primary interface (Iu-BC) for broadcast service delivery, enabling the CBC to instruct the RNC to broadcast messages over a defined geographical area, known as a Service Area. The protocol handles the setup, modification, and release of broadcast sessions, including the transfer of the actual broadcast message content and associated parameters like message identifiers, repetition rates, and broadcast area definitions.

Architecturally, SABP resides in the Core Network domain for control but directly interfaces with the RAN for execution. The CBC acts as the source and controller of broadcast messages, using SABP to communicate with one or more RNCs. The RNC is responsible for mapping the logical Service Area to physical cells and scheduling the broadcast on the UMTS Broadcast Control Channel (BCCH) or Forward Access Channel (FACH). SABP messages are carried over a Signalling Connection Control Part (SCCP) connection, ensuring reliable delivery of control commands. The protocol supports functions like Write-Replace, which allows updating or cancelling an ongoing broadcast, and Load Balancing, to manage traffic across different RNCs.

SABP's operation is connection-oriented for control but the resulting user-plane broadcast is connectionless. A typical flow involves the CBC sending a WRITE-REPLACE request message to the RNC, containing the message content, a message identifier, a list of target Service Areas (defined by a set of Location Areas or Routing Areas), and broadcast scheduling information. The RNC acknowledges this and begins broadcasting the message in the specified cells. SABP also includes error handling and status reporting mechanisms, allowing the CBC to monitor the success or failure of broadcast attempts. Its design ensures that broadcast resources in the RAN are used efficiently and that critical information, especially for public warning systems, can be disseminated rapidly and reliably across the network.

Purpose & Motivation

SABP was created to standardize and enable efficient cell broadcast services within 3G UMTS networks, addressing the need for a reliable one-to-many information distribution mechanism. Prior to 3G, GSM had the Cell Broadcast Service, but the UMTS architecture required a new, optimized protocol to interface between the evolved Core Network and the UTRAN. The primary problem SABP solves is the controlled delivery of broadcast messages (like emergency alerts, traffic information, or advertising) to all User Equipments (UEs) within a specific geographical area without establishing individual connections, thus conserving network signaling resources and enabling immediate, widespread notification.

Historically, the motivation stemmed from regulatory requirements for public warning systems (e.g., EU-Alert, CMAS) and commercial demand for location-based broadcast services. SABP provided a standardized, network-controlled method for the CBC to manage broadcasts, ensuring interoperability between equipment from different vendors. It addressed limitations of point-to-point messaging for mass notifications, which would cause signaling congestion. By defining a dedicated protocol for broadcast service management, 3GPP ensured that UMTS networks could support critical safety services and innovative broadcast applications with guaranteed performance and reliability.

What changed in its specifications

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

TS 25.410Rel-10 → Rel-11

Rel-11 brings only minor changes to TS 25.410: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.410 →
TS 25.414Rel-7 → Rel-8

Rel-8 brings only minor changes to TS 25.414: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.414 →

Technology family

Broadcast and multicast · Services

  1. Phase 1 CBC, CBCH, CBS, SMS-CB
  2. Phase 2 CBE
  3. R99 BMC, SABP
  4. Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
  5. Rel-7 MBSFN
  6. Rel-8 ETWS, MCE, PWS
  7. Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
  8. Rel-10 KPAS
  9. Rel-11 EU-Alert
  10. Rel-12 MooD
  11. Rel-13 MBMS group communication delivery method, SC-PTM
  12. Rel-14 MBMS transparent delivery method, Receive Only Mode
  13. Rel-15 CBCF, PWS-IWF
  14. Rel-16 5G Broadcast
  15. Rel-17 5MBS, Broadcast MBS session, MB-SMF, MB-UPF, MBS, MBS Distribution Session, MBS User Service, MBSF, MBSSF, MBSTF, Multicast MBS session, Object Distribution Method, Packet Distribution Method

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 2 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.

R99 introduced

SABP is specified for the first time as the protocol between the Cell Broadcast Centre and the RNC over the Iu-BC reference point, using ASN.1 PER and TCP port 3452.

  • “The present document specifies the Service Area Broadcast Protocol (SABP) between the Cell Broadcast Centre (CBC) and the Radio Network Controller (RNC).” TS 25.419 v3.11.0
  • “SABP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. [9].” TS 25.419 v3.11.0
  • “The TCP Destination Port number for SABP messages is 3452. It is the registered port number for SABP.” TS 25.414 v3.13.0
Rel-8 specification text

SABP gained ETWS support in Rel-8, including a Paging ETWS Indicator IE telling the RNC that a received SABP message carries ETWS content to be sent via paging to the UE.

  • “Paging ETWS Indicator IE is used to indicate to the RNC that the received SABP message contains ETWS contents” TS 25.419 v8.2.0
  • “CR on ETWS support in UTRAN SABP” TS 25.419 v8.2.0

Defining Specifications

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

SpecificationTitleRelease
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19 read
TS 25.414 vj00 UTRAN Iu Interface User Plane Transport Protocols Rel-19 read
TS 25.419 vj00 Service Area Broadcast Protocol (SABP) Rel-19 read
TS 25.703 vc00 HNB Emergency Warning Area Study for UTRA Rel-12 read