SA

File Service Announcement File

Services
Introduced in Rel-4
The File Service Announcement File (SA) is a structured data file used in 3GPP Multimedia Broadcast/Multicast Service (MBMS) and evolved MBMS (eMBMS). It contains metadata describing broadcast service offerings, such as service names, schedules, and access information, enabling user devices to discover and join broadcast sessions.

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.

Key Features

  • Contains metadata for MBMS/eMBMS service discovery
  • Includes technical access parameters (IP multicast address, port, TMGI)
  • May provide service schedules and electronic service guide (ESG) data
  • Typically delivered via FLUTE or HTTP provisioning
  • Structured according to 3GPP XML schemas
  • Generated and managed by the BM-SC in the network

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.

Defining Specifications

SpecificationTitle
TS 23.048 3GPP TS 23.048
TS 23.501 3GPP TS 23.501
TS 23.794 3GPP TS 23.794
TS 24.109 3GPP TS 24.109
TS 24.193 3GPP TS 24.193
TS 24.501 3GPP TS 24.501
TS 24.502 3GPP TS 24.502
TS 24.890 3GPP TS 24.890
TS 25.410 3GPP TS 25.410
TS 25.414 3GPP TS 25.414
TS 25.419 3GPP TS 25.419
TS 25.703 3GPP TS 25.703
TS 26.346 3GPP TS 26.346
TS 28.552 3GPP TS 28.552
TS 29.273 3GPP TS 29.273
TS 31.117 3GPP TR 31.117
TS 31.127 3GPP TR 31.127
TS 33.203 3GPP TR 33.203
TS 33.204 3GPP TR 33.204
TS 33.210 3GPP TR 33.210
TS 33.223 3GPP TR 33.223
TS 33.224 3GPP TR 33.224
TS 33.320 3GPP TR 33.320
TS 33.402 3GPP TR 33.402
TS 33.821 3GPP TR 33.821
TS 33.938 3GPP TR 33.938
TS 37.718 3GPP TR 37.718
TS 37.941 3GPP TR 37.941
TS 37.985 3GPP TR 37.985
TS 38.106 3GPP TR 38.106
TS 38.133 3GPP TR 38.133
TS 38.719 3GPP TR 38.719
TS 38.889 3GPP TR 38.889
TS 38.913 3GPP TR 38.913
TS 44.318 3GPP TR 44.318