Description
The Broadcast-Multicast Service Centre (BM-SC) is the central functional entity within the 3GPP architecture for Multimedia Broadcast Multicast Service (MBMS). It serves as the entry point for content providers to inject broadcast or multicast traffic into the mobile network and manages the entire MBMS service delivery lifecycle. The BM-SC interfaces with external content sources and the core network's Gateway GPRS Support Node (GGSN) or Packet Data Network Gateway (PGW) in later releases, acting as the authoritative source for MBMS session control and data distribution.
Architecturally, the BM-SC comprises several key logical functions defined in 3GPP specifications. The Membership Function handles subscription and authorization, determining which users are entitled to receive specific MBMS services. The Session and Transmission Function manages MBMS session scheduling, including start/stop times and quality of service parameters. The Proxy and Transport Function serves as the relay point for MBMS data between content providers and the core network, while the Service Announcement Function distributes information about available MBMS services to user equipment. The Security Function is responsible for key management and encryption, ensuring that only authorized users can access protected content.
In operation, the BM-SC initiates MBMS sessions by sending session start requests to the core network, which then establishes the necessary bearers across the radio access network. The BM-SC synchronizes content delivery using SYNC protocol, ensuring that all base stations transmit identical data at precisely coordinated times, which is essential for Single Frequency Network (MBSFN) operation where multiple cells transmit the same content simultaneously. The BM-SC also manages charging data collection and interfaces with billing systems, providing the necessary information for service providers to monetize MBMS offerings.
Throughout the MBMS session, the BM-SC monitors service delivery and can adapt transmission parameters based on network conditions and service requirements. It terminates sessions gracefully when content delivery is complete or according to schedule, releasing network resources. The BM-SC's centralized control enables efficient spectrum utilization by coordinating transmissions across multiple cells, reducing interference, and improving reception quality at cell edges through macro-diversity gain in MBSFN areas.
Purpose & Motivation
The BM-SC was created to address the fundamental inefficiency of delivering popular content using traditional unicast methods in mobile networks. Before MBMS, when multiple users in the same area requested the same content (such as live sports events, news broadcasts, or popular videos), the network had to establish individual connections to each user, consuming excessive radio resources and core network capacity. This approach scaled poorly and became economically unsustainable for mass content distribution.
The BM-SC enables true broadcast and multicast capabilities in 3GPP networks, allowing a single transmission to serve multiple users simultaneously within a defined service area. This dramatically improves spectral efficiency and reduces network load during peak demand periods. The technology was particularly motivated by the growing demand for mobile TV and video services in the mid-2000s, as well as the need for efficient distribution of software updates, emergency alerts, and other one-to-many communications.
Beyond efficiency gains, the BM-SC provides a standardized framework for service management, security, and charging that was previously lacking for broadcast services in mobile networks. It enables commercial broadcast services with proper subscription management, content protection, and billing integration. The architecture also supports both broadcast (to all users in an area) and multicast (to specific subscriber groups) modes, providing flexibility for different service models and business cases.
What changed in its specifications
The latest release-to-release comparison of specifications that define BM-SC. Each summary describes the whole specification, not only this term.
Rel-19 adds CAPIF Phase 3 procedures for unpublishing service APIs between interconnected core functions, revoking API invoker and resource owner authorization, open discovery of service APIs, and UE-hosted API invoker access to resources owned by other UEs.
Full comparison in TS 23.222 →Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.
Full comparison in TS 23.280 →Technology family
Broadcast and multicast · Services
- Phase 1 CBC, CBCH, CBS, SMS-CB
- Phase 2 CBE
- R99 BMC, SABP
- Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
- Rel-7 MBSFN
- Rel-8 ETWS, MCE, PWS
- Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
- Rel-10 KPAS
- Rel-11 EU-Alert
- Rel-12 MooD
- Rel-13 MBMS group communication delivery method, SC-PTM
- Rel-14 MBMS transparent delivery method, Receive Only Mode
- Rel-15 CBCF, PWS-IWF
- Rel-16 5G Broadcast
- 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
- BM-SC counterpart in another generation: MBSF
“Figure 5.2-1 depicts the system architecture for interworking between E-UTRAN/EPC eMBMS and MBS at service layer, with collocated BM-SC and MBSF/MBSTF functionalities.” TS 23.247
- BM-SC counterpart in another generation: MBSTF
“Figure 5.2-1 depicts the system architecture for interworking between E-UTRAN/EPC eMBMS and MBS at service layer, with collocated BM-SC and MBSF/MBSTF functionalities.” TS 23.247
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 11 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.
The BM-SC is first specified in Rel-6, with MBMS security roles (GBA key establishment, MIKEY key distribution) and Gmb Diameter procedures for registration, session start/stop with the GGSN.
- “The BM-SC is responsible for establishing shared secrets with the UE using GBA, authenticating the UE with HTTP digest authentication mechanism” TS 33.246 v6.12.0
- “The BM-SC initiates the MBMS session start procedure when it is ready to send data.” TS 29.061 v6.15.0
- “The BM-SC is responsible for the generation and distribution of the MBMS keys to the UE.” TS 33.246 v6.12.0
BM-SC gained IP multicast user-plane support towards the GGSN on Gmb, with mode negotiation and SSM address AVPs, and MIKEY/GBA key-management behaviour in MBMS security was extended.
- “BM-SC may indicate to GGSN that BM-SC supports sending the user plane IP multicast data without IP unicast encapsulation.” TS 29.061 v7.12.0
- “BM-SC and GGSN shall at least support IP unicast encapsulation of IP multicast datagrams, which shall be default mode of sending user plane data.” TS 29.061 v7.12.0
- “The counter shall be increased by one for each MSK message sent from the BM-SC to the UE even in case BM-SC retransmits” TS 33.246 v7.6.0
BM-SC behaviour changed: key management now authorizes MBMS Broadcast Mode users without the Membership function, the BM-SC FQDN is used as IDi, and the BM-SC can signal IP multicast distribution to the GGSN.
- “For MBMS Broadcast Mode this authorization is done without the help of Membership function because the Membership function is only defined in the context of MBMS Multicast Mode” TS 33.246 v8.4.0
- “BM-SC may indicate to GGSN that BM-SC supports sending the user plane IP multicast data without IP unicast encapsulation.” TS 29.061 v8.12.0
- “IDi is the ID (i.e. FQDN) of the BM-SC (i.e. NAF‑ID without the Ua security protocol identifier)” TS 33.246 v8.4.0
Rel-9 adds multiple BM-SC deployment with synchronized MTK use and single-BM-SC MSK management in TS 33.246, and BM-SC/MBMS GW user-plane unicast/multicast mode handling over SGi-mb in TS 29.061.
- “The BM-SCs shall use MTKs in a synchronized way. At a certain point in time the same MTK” TS 33.246 v9.1.0
- “The UE shall register to one BM-SC indicated in the Service Announcement and shall keep the same BM-SC” TS 33.246 v9.1.0
- “BM-SC and MBMS GW shall at least support IP unicast encapsulation of IP multicast datagrams, which shall be default mode of sending user plane data.” TS 29.061 v9.16.0
BM-SC behaviour in MBMS Session Update and Stop procedures changed: RAR from BM-SC may now carry MBMS-Data-Transfer-Start/Stop AVPs with absolute timestamps for E-UTRAN access, with revised AVP content.
- “the RAR message may also contain the MBMS-Data-Transfer-Start AVP containing the absolute time stamp of the data delivery start” TS 29.061 v11.12.0
- “the RAR message may also contain the MBMS-Data-Transfer-Stop AVP containing the absolute time stamp of the data delivery stop” TS 29.061 v11.12.0
BM-SC gained new security requirements on MB2-C/MB2-U toward the GCS AS (mutual authentication, integrity/confidentiality protection, access control) and a new SGmb MBMS heartbeat procedure for path failure and restart detection.
- “The signalling messages on MB2-C between the BM-SC and the GCS AS shall be integrity and confidentiality protected.” TS 33.246 v12.2.0
- “The BM-SC initiates the MBMS heartbeat procedure to detect a SGmb path failure or the restart of the MBMS GW” TS 29.061 v12.12.0
- Flow ID allocation by BM-SC only TS 23.468CR0039
BM-SC behaviour changed in Rel-13: session update now triggered by changes to service attributes (Service Area, cell list, Access indicator, ARP), plus new CRs on UE consumption reporting and overlapping broadcast areas.
- “The BM-SC initiates the MBMS session update procedure when service attributes (e.g. Service Area, MBMS cell list, Access indicator or ARP) for an ongoing MBMS session shall be modified.” TS 29.061 v13.7.0
- Support for UE Consumption Reporting towards BM-SC TS 23.246CR0394
- Clarify BM-SC behaviour in case of overlapping broadcast areas TS 23.468CR0066
Rel-14 adds BM-SC support for V2X Localized User Plane with local MBMS information, and specifies (D)TLS authentication and authorization between Content Provider and BM-SC on the xMB reference point.
- “the BM-SC may support, for V2X services, the V2X Localized User Plane procedures as defined in 3GPP TS 23.285 [23] subclause 5.4.2.2” TS 29.116 v14.5.0
- “The BM-SC shall indicate the M1 interface information of local MBMS information as specified in 3GPP TS 23.285 [112]” TS 29.061 v14.4.0
- “After the successful mutual D(TLS) authentication, the BM-SC shall perform authorization checks based on the subject field of the Content Provider certificate.” TS 33.246 v14.2.0
BM-SC gains requests and features to enable ROHC header compression and FEC protection of input flows over the MBMS channel, and 29061 changes the MBMS GW session start handling toward the BM-SC.
- “Requests the BM-SC to perform FEC (see IETF RFC 6363 [29]) protection of the input flow when transmitting over the MBMS channel.” TS 29.116 v15.3.0
- “This feature inficates the support of applying ROHC (see IETF RFC 5795 [27] and IETF RFC 3095 [28]) to downlink packet streams at the BM-SC.” TS 29.116 v15.3.0
- “Requests the BM-SC to enable ROHC (see IETF RFC 5795 [27] and IETF RFC 3095 [28]) on the input flow.” TS 29.116 v15.3.0
BM-SC gains xMB behaviour: it maps content provider QoS and ARP properties to AVPs, supports CAPIF as API provider, and retrieves CAPIF authorization information.
- “When CAPIF is used with BM-SC, BM-SC shall support the following as defined in 3GPP TS 29.222 [40]:” TS 29.116 v16.6.0
- “qci: QoS Class identifier. The BM-SC shall use this value for the QoS-Class-Identifier AVP.” TS 29.116 v16.6.0
- “The BM-SC may support CAPIF [10]. When CAPIF is supported, then:” TS 26.348 v16.3.0
The xMB interface of the BM-SC gained new requirements in Rel-17: authorization information retrieval from CAPIF for API invocation, and 5GMS AF control and 5GMS AS content ingest procedures.
- “upon API invocation, the BM-SC shall retrieve the authorization information from the CAPIF core function as described in 3GPP TS 29.222 [40], clause 5.6.2.4.” TS 29.116 v17.2.0
- “The 5GMS Application Function (5GMS AF) invokes xMB-C control plane procedures on the BM-SC as specified in clauses 5.3 and 5.4” TS 26.348 v17.1.0
Defining Specifications
3GPP specifications that define or reference BM-SC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.179 vd50 | MCPTT Functional Architecture | Rel-13 read |
| TS 23.222 vk10 | Common API Framework (CAPIF) | Rel-20 read |
| TS 23.280 vk51 | Mission Critical Services Architecture | Rel-20 read |
| TS 23.379 vk40 | Mission Critical Push-to-Talk Architecture | Rel-20 read |
| TS 23.468 vj00 | Group Communication System Enablers for LTE | Rel-19 read |
| TS 23.479 vj00 | MBMS API for Mission Critical Services | Rel-19 read |
| TS 23.722 vf10 | Common API Framework (CAPIF) for 3GPP Northbound APIs | Rel-15 read |
| TS 23.768 vc10 | GCSE_LTE Architecture Study | Rel-12 read |
| TR 23.780 ve00 | MBMS for Mission Critical Communication Services | Rel-14 read |
| TS 23.792 vg00 | MBMS API for Mission Critical Services | Rel-16 read |
| TS 23.795 vg10 | V2X Application Architecture Study | Rel-16 read |
| TS 23.846 v610 | MBMS Architecture and Functionality | Rel-6 read |
| TS 24.548 vk10 | Network Resource Management - SEAL Protocol Specification | Rel-20 read |
| TS 26.237 vj00 | IMS for PSS and MBMS Control | Rel-19 read |
| TS 26.346 vj30 | MBMS User Services Specification | Rel-19 read |
| TS 26.348 vj00 | xMB Interface Specification | Rel-19 read |
| TS 26.512 vj30 | 5G Media Streaming Protocols and APIs | Rel-19 read |
| TS 26.802 vk00 | 5G Media Streaming Multicast Enhancements | Rel-20 read |
| TS 26.827 vc00 | IMS-based Streaming & Download Delivery Enhancements | Rel-12 read |
| TS 26.848 vc00 | Enhanced MBMS for DASH over broadcast/unicast | Rel-12 read |
| TS 26.849 vc10 | MBMS Operation on Demand (MooD) | Rel-12 read |
| TS 26.852 ve20 | MBMS user service profiles, APIs and transport enabler study | Rel-14 read |
| TS 26.880 ve00 | MBMS Enhancements for Mission Critical Video | Rel-14 read |
| TS 26.881 vf00 | MBMS FEC for Mission Critical Services Study | Rel-15 read |
| TR 26.944 vj00 | QoE, ESQoS and SQoS metrics for 3G multimedia services | Rel-19 read |
| TR 26.946 vj00 | MBMS User Services Overview | Rel-19 read |
| TR 26.947 vj00 | FEC Evaluation for MBMS Enhancement | Rel-19 read |
| TR 26.948 vj00 | Video enhancements for 3GPP Multimedia Services | Rel-19 read |
| TR 26.981 vj00 | MBMS Provisioning & Content Ingestion Interface Study | Rel-19 read |
| TR 26.989 vj00 | MCPTT Enhancement Analysis | Rel-19 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.116 vj00 | REST-based protocol for xMB reference point | Rel-19 read |
| TS 29.199 | 3GPP TS 29.199 | Rel-6 read |
| TS 29.468 vj00 | MB2 Reference Point Protocol Definition | Rel-19 read |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.273 vj00 | MBMS Charging Management | Rel-19 read |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 read |
| TS 33.246 vj00 | MBMS Security Specification | Rel-19 read |
| TS 36.440 vj00 | E-UTRAN MBMS Architecture Description | Rel-19 read |
| TS 36.868 vc00 | Study on Group Communication for E-UTRA | Rel-12 read |
| TS 43.246 vj00 | MBMS in GERAN Stage 2 Specification | Rel-19 read |