MBS

Frequency Selection Area Identity

Identifier →
Introduced in Rel-13 Also in: Services, Core Network, User Equipment

MBS is the Frequency Selection Area Identity used in 5G networks to manage broadcast and multicast service areas for efficient radio resource allocation and simultaneous content delivery.

Category
Identifier
Introduced
Rel-13
Where
Radio Access Network › NG-RAN (5G)
Also touches
3 segments
Specifications
72 specs
MBS Description Purpose Related Classification Detected Changes Specifications

Description

The Frequency Selection Area Identity (MBS) is a critical network identifier within the 5G Multicast/Broadcast Service (MBS) framework, designed to manage and optimize the delivery of broadcast and multicast content. In 5G, MBS enables efficient point-to-multipoint transmission, where a single data stream is delivered to multiple User Equipments (UEs) within a specific geographical area, conserving radio resources compared to individual unicast transmissions. The MBS identifier is used to define a Frequency Selection Area (FSA), which is a logical area where specific frequency resources are allocated for MBS transmissions. This area can be dynamically configured based on factors such as user density, service demand, and network load, allowing operators to flexibly manage spectrum.

Architecturally, the MBS identifier is configured and managed by the 5G Core Network (5GC) and Radio Access Network (RAN). It is associated with MBS session contexts and is used by network functions like the Multicast/Broadcast Service Function (MBSF) and gNBs to coordinate resource allocation. When a UE subscribes to an MBS service, the network uses the MBS identifier to determine the appropriate frequency resources and transmission parameters. The identifier ensures that UEs within the same FSA can efficiently receive the multicast/broadcast stream without unnecessary signaling overhead, as they can synchronize to the same physical resources identified by the MBS.

How it works involves several steps. First, the 5GC establishes an MBS session and assigns an MBS identifier corresponding to a Frequency Selection Area. This identifier is communicated to the RAN and UEs via control signaling, such as through System Information Blocks (SIBs) or dedicated RRC messages. The gNB then schedules MBS transmissions on specific time-frequency resources (e.g., Physical Downlink Shared Channel slots) tagged with this identifier. UEs monitoring for MBS services use the MBS identifier to filter and decode the relevant transmissions, enabling them to receive content like live video streaming or software updates efficiently. The identifier also supports mobility, as UEs moving between FSAs can be handed over to new MBS identifiers to maintain service continuity.

Key components interacting with the MBS identifier include the MBSF in the core network, which manages MBS session policies, and the gNB in the RAN, which handles radio resource scheduling. The identifier plays a role in network slicing by allowing dedicated resources for MBS within a slice, ensuring QoS for broadcast services. Its technical implementation involves encoding in protocols like NGAP and F1AP for core-RAN communication and RRC for UE configuration, ensuring seamless integration into the 5G system architecture.

Purpose & Motivation

The MBS identifier was introduced to address the inefficiencies of using unicast transmissions for delivering popular content to many users simultaneously, such as live sports events or emergency alerts. In previous cellular generations, broadcast services like Multimedia Broadcast Multicast Service (MBMS) in LTE existed but had limitations in flexibility and integration with 5G's service-based architecture. The motivation for MBS in 5G, including its identifiers, stems from the growing demand for high-quality, low-latency group communications, which are essential for applications like public safety, automotive updates, and media distribution.

Historically, LTE's MBMS used temporary mobile group identities and service areas, but these were less dynamic and not fully integrated with 5G's network slicing and edge computing capabilities. The MBS identifier solves these problems by providing a more granular and flexible way to manage frequency resources for multicast/broadcast. It allows operators to dynamically define areas based on real-time demand, optimizing spectrum usage and reducing interference. This is particularly important in 5G, where spectrum is a scarce resource, and services require stringent QoS.

The creation of the MBS identifier was motivated by the need to support new use cases in 5G, such as Vehicle-to-Everything (V2X) communications and immersive media, where efficient group communication is critical. By enabling precise control over frequency selection areas, the identifier helps achieve the low latency and high reliability required for these applications. It also facilitates the convergence of broadcast and unicast services within a unified 5G framework, allowing operators to leverage existing infrastructure for innovative services.

Classification

Part ofRAN
Specific typesTSA
Related approachesMBSF

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (370 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-17 207 changes

In Release 17, the MBS function introduced key procedures for session resilience and management, including MBS session restoration upon MB-UPF or NG-RAN failure and mechanisms for a UE to join or leave an MBS session. It also added support for network-requested and UE-requested PDU session modification to manage UE membership, along with features like updating the MBS service area and implementing an MBS back-off timer for join rejection. Furthermore, the release defined the impact of procedures like PDU session release, deregistration, and inter-system change on the removal of a UE from its joined MBS sessions.

  • MBS session restoration upon MB-UPF failure with restart TS 23.527CR0041
  • MBS session restoration upon MB-UPF failure without restart TS 23.527CR0042
  • Restoration of a Broadcast MBS session upon NG-RAN failure with or without restart TS 23.527CR0048
  • Restoration of a Multicast MBS session upon NG-RAN failure with or without restart TS 23.527CR0049
  • Support of Broadcast MBS Session with an AMF set being deployed TS 23.527CR0056
  • Network-requested PDU session modification procedure to be used for removing joined UE from MBS session(s) TS 24.501CR3399

+ 201 more changes

Rel-18 152 changes

In Release 18, the MBS (Frequency Selection Area Identity) function was expanded with new support for Broadcast Remote ID and V2X services, including the definition of specific 5QIs for V2X and A2X message delivery. It introduced enhanced procedures for multicast MBS session management, such as (de)activation after an AMF failure and mechanisms for UEs using power-saving functions like MICO mode and eDRX. Furthermore, the release standardized the use of 5G MBS transmission within MCVideo, MCData, and MCPTT services, adding specific inter-RAT information and control procedures to their signalling and media planes.

  • MBS support for Broadcast Remote ID TS 23.256CR0089
  • MBS support for V2X services TS 23.287CR0187
  • MBS service for UE using power saving functions TS 23.501CR3834
  • 5QI for V2X message delivery via MBS TS 23.501CR3881
  • 5QI for A2X message delivery via MBS TS 23.501CR4249
  • Multicast MBS session (de)activation or update after an AMF failure TS 23.527CR0063

+ 146 more changes

Rel-19 11 changes

In Release 19, the enhancements for MBS (Multicast Broadcast Service) focused on improving service resilience and expanding delivery methods. Key introductions included a defined Multicast MBS session restoration procedure for handling N3mb path failures and NG-RAN restarts, as well as new capabilities for in-session Unicast Repair for MBS Object Distribution. The release also advanced features for combined MBS and unicast services and expanded support for MBS within Non-Terrestrial Networks (NTN).

  • Multicast MBS session restoration procedure for N3mb path failure TS 23.527CR0082
  • [AMD-ARCH-MED] In-session Unicast Repair for MBS Object Distribution TS 26.502CR0033
  • [AMD-ARCH-MED] MBS User Service and Delivery Protocols for eMBMS TS 26.502CR0034
  • [AMD-ARCH-MED] MBS Time Synchronization TS 26.502CR0035
  • [FS_AMD] Advanced Media Delivery Features for MBS User Services TS 26.802CR0005
  • Support for Regenerative Payload and MBS broadcast in NR NTN TS 38.413CR1212

+ 5 more changes

Explore further

Broader topics and technologies where MBS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 22.261 vk30 5G System Service Requirements Rel-20
TS 23.256 vj50 UAS Support Architecture Enhancements Rel-19
TS 23.287 vj00 5G V2X Architecture Enhancements Rel-19
TS 23.501 vk00 5G System Architecture Stage 2 Rel-20
TS 23.527 vj50 5G System Restoration Procedures Rel-19
TS 24.281 vj40 MCVideo Signalling Control Specification Rel-19
TS 24.282 vj50 MCData Signalling Control Protocols Rel-19
TS 24.379 vj50 Mission Critical Push To Talk (MCPTT) call control Rel-19
TS 24.380 vj10 MCPTT Media Plane Control Protocol Rel-19
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 24.548 vj10 SEAL Network Resource Management Protocol Rel-19
TS 24.575 vj00 UE Pre-configuration for MBS Rel-19
TS 24.577 vj10 A2X Services in 5GS Rel-19
TS 24.578 vj00 UE policies for A2X services in 5GS Rel-19
TS 24.581 vj00 MCVideo Media Plane Control Protocol Specification Rel-19
TS 24.582 vj00 MCData Media Plane Control Protocols Rel-19
TS 24.587 vj30 V2X Services Protocols for 5G System Rel-19
TS 24.588 vj00 UE Policies for V2X Services in 5GS Rel-19
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19
TS 25.306 vj00 UE Radio Access Capabilities Specification Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19
TS 25.453 vj00 PCAP Protocol Specification Rel-19
TS 26.502 vj30 5G Multicast-Broadcast User Services Architecture Rel-19
TS 26.512 vj10 5G Media Streaming Protocols & APIs Rel-19
TS 26.517 vj10 5G MBS User Service Protocols and Formats Rel-19
TS 26.802 vj20 Multicast Enhancements for 5G Media Streaming Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TR 26.857 vi00 Technical Report on Media Service Enablers Rel-18
TR 26.942 vj00 Study on Media Energy Consumption Exposure & Evaluation Rel-19
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19
TS 27.007 vj40 AT Command Set for UE Rel-19
TS 29.171 vj00 LCS Application Protocol (LCS-AP) Specification Rel-19
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 29.510 vj50 NRF Service Based Interface Protocol Rel-19
TS 29.513 vj40 5G PCC Signalling Flows & QoS Mapping Rel-19
TS 29.518 vj50 AMF Service Based Interface Protocol Rel-19
TS 29.522 vj40 5G NEF Northbound APIs Stage 3 Rel-19
TS 29.532 vj30 MB-SMF Service Based Interface Protocol Rel-19
TS 29.537 vj10 5G Multicast/Broadcast Policy Control Services Rel-19
TS 32.255 vk10 Telecom Management; Charging for 5G Data Connectivity Rel-20
TS 32.279 vj00 5G MBS Session Converged Charging Rel-19
TR 33.850 vh00 5G MBS Security Study Rel-17
TS 36.305 vj00 UE Positioning in E-UTRAN Stage 2 Rel-19
TS 36.355 vj00 LTE Positioning Protocol (LPP) Rel-19
TS 36.509 vh40 EPC Special UE Conformance Testing Functions Rel-17
TS 37.171 vj00 UE Positioning Performance Requirements Rel-19
TS 37.355 vj20 LTE Positioning Protocol (LPP) Rel-19
TS 37.480 vj00 E1 Interface General Aspects and Principles Rel-19
TS 37.483 vj10 E1 Application Protocol (E1AP) Rel-19
TS 37.571 vj00 UE Conformance for Positioning Rel-19
TS 38.212 vj10 NR Multiplexing and Channel Coding Rel-19
TS 38.213 vj10 NR Physical Layer Control Procedures Rel-19
TS 38.300 vj00 NG-RAN Overall Description Rel-19
TS 38.304 vj00 UE RRC_IDLE and RRC_INACTIVE Procedures Rel-19
TS 38.305 vj00 NG-RAN UE Positioning Stage 2 Rel-19
TS 38.306 vj00 NR UE Radio Access Capability Parameters Rel-19
TS 38.321 vj00 NR MAC Protocol Specification Rel-19
TS 38.322 vj00 NR Radio Link Control (RLC) Protocol Rel-19
TS 38.323 vj00 Packet Data Convergence Protocol (PDCP) Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 38.410 vj10 NG Interface Introduction for NG-RAN to 5GC Rel-19
TS 38.413 vj10 NG Application Protocol (NGAP) Rel-19
TS 38.415 vj10 PDU Session User Plane Protocol Rel-19
TS 38.420 vj10 Introduction to Xn interface specifications Rel-19
TS 38.423 vj10 Xn Application Protocol (XnAP) specification Rel-19
TS 38.425 vj10 NR User Plane Protocol Specification Rel-19
TS 38.470 vj10 F1 Interface Introduction Rel-19
TS 38.473 vj10 5G F1 Application Protocol (F1AP) Rel-19
TS 38.523 vj20 5G NR UE Conformance Testing: Idle/Inactive Rel-19
TR 38.890 vh00 NR QoE Management and Optimization Rel-17
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.