Glossary term · Services

SA

File Service Announcement File

Services →

SA is a structured data file used in 3GPP MBMS and eMBMS that contains metadata describing broadcast service offerings, enabling user devices to discover and join broadcast sessions.

Introduced
Rel-4
Specifications
35 specs
Category
Services
Introduced
Rel-4
Specifications
35 specs
SA Description Purpose Related Classification Specifications

Description

The Service Announcement (SA) file is a core component of the 3GPP Multimedia Broadcast/Multicast Service (MBMS) and evolved MBMS (eMBMS) service layer. It is not a media file itself, but a metadata container that provides User Equipment (UE) with all necessary information to discover, select, and access available broadcast/multicast services. The SA file is typically delivered to UEs via a low-bitrate bearer, such as the File Delivery over Unidirectional Transport (FLUTE) protocol, or can be provisioned via other means like HTTP.

The file is structured according to specific 3GPP specifications (often using XML schemas defined in TS 26.346 for MBMS). Its contents include a list of available broadcast services, each with attributes like a human-readable service name, a unique service identifier, and a detailed service description. Crucially, it contains the technical parameters required to join the media delivery session. This includes the IP multicast address and port number for the session, the associated Temporary Mobile Group Identity (TMGI) which identifies the broadcast bearer at the radio level, and the session description protocol (e.g., SDP) information detailing the media codecs and formats. It may also include scheduling information (start time, duration) and metadata for electronic service guides (ESG).

From an architectural perspective, the SA file is generated and managed by the Broadcast-Multicast Service Center (BM-SC) in the network. The BM-SC is responsible for service announcement provisioning, session and transmission scheduling, and security (key management). The UE's MBMS client application receives and parses the SA file. Using the information within, the UE can then instruct its lower layers to activate the appropriate MBMS bearer, join the specified IP multicast group, and begin receiving the broadcast media streams. This decouples service discovery from media delivery, allowing for efficient dynamic service updates.

Purpose & Motivation

The Service Announcement file was created to solve the fundamental challenge of service discovery in a cellular broadcast system. In a traditional unicast network, a user requests a specific service, and a point-to-point connection is established. In broadcast, the network transmits content to a wide area, and potentially millions of devices need to know what is being broadcasted and how to tune in.

The SA file provides a standardized, efficient mechanism to advertise broadcast services. Before its definition, there was no unified way for a network to inform devices about available multicast sessions, their schedules, and the technical parameters needed for reception. Its creation was motivated by the rollout of MBMS, enabling services like mobile TV, live event streaming, and software/update distribution over cellular networks. It allows operators to dynamically manage a bouquet of services and gives users an interactive guide to select content, making broadcast services user-friendly and manageable.

Classification

Part ofMBMS
Related approachesFLUTE

Evolution Across Releases

Rel-4 Initial

Introduced with the initial Multimedia Broadcast/Multicast Service (MBMS) framework. Defined the concept and basic structure of the Service Announcement file for advertising broadcast services, enabling UEs to discover available MBMS sessions and the parameters required to join them.

Explore further

Broader topics and technologies where SA plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.048 v1590 Secured Packets Structure for SMS and UICC Management Rel-5
TS 23.501 vk20 5G System Architecture Stage 2 Rel-20
TR 23.794 vh00 Study on enhanced IMS to 5GC integration Rel-17
TS 24.109 vj00 HTTP Digest AKA & GAA Stage 3 Rel-19
TS 24.193 vk00 ATSSS Procedures for 5G Multi-Access Rel-20
TS 24.501 vk00 5G System (5GS) Non-Access Stratum (NAS) Protocol Rel-20
TS 24.502 vk00 Non-3GPP Access Network Discovery and Selection Rel-20
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19
TS 25.414 vj00 UTRAN Iu Interface User Plane Transport Protocols Rel-19
TS 25.419 vj00 Service Area Broadcast Protocol (SABP) Rel-19
TS 25.703 vc00 HNB Emergency Warning Area Study for UTRA Rel-12
TS 26.346 vj30 MBMS User Services Specification Rel-19
TS 28.552 vk30 5G Performance Measurements & Network Slicing Rel-20
TS 29.273 vj20 EPS AAA Reference Points and Procedures Rel-19
TS 31.117 vj20 USAT Tests for Non-Removable UICC Rel-19
TS 31.127 vi50 UE Behavioural Tests for Non-Removable UICC/USIM Rel-18
TS 33.203 vk00 IMS Security Features and Mechanisms Rel-20
TS 33.204 vj00 TCAP Security (TCAPsec) Stage 2 Specification Rel-19
TS 33.210 vj30 Network Domain Security for IP Protocols Rel-19
TS 33.223 vj00 GBA Push Function Specification Rel-19
TS 33.224 vj00 Generic Push Layer (GPL) Specification Rel-19
TS 33.320 vj00 H(e)NB Subsystem Security Architecture Rel-19
TS 33.402 vj00 Security for non-3GPP access to EPS Rel-19
TS 33.821 v1900 LTE/SAE Security Architecture Rationale Rel-9
TR 33.938 vj20 3GPP Cryptographic Inventory for 5G System Rel-19
TS 37.718 3GPP TR 37.718 Rel-4
TR 37.941 vj20 RF Conformance Testing Background for Radiated BS Requirements Rel-19
TR 37.985 vj00 Overview of V2X features in LTE and NR Rel-19
TS 38.106 vj50 NR Repeater RF Requirements Rel-19
TS 38.133 vk00 NR RRM Requirements Rel-20
TS 38.719 vj10 NR Inter-band CA/DC Configurations Rel-19
TR 38.889 vg00 NR-based access to unlicensed spectrum study Rel-16
TR 38.913 vj00 Next Gen Access Tech Scenarios & Requirements Rel-19
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19