Description
The MBS session resource is a concept introduced in 3GPP Release 17 to describe the set of NG-RAN interface resources and radio resources that are provided to support a Multicast/Broadcast Service (MBS) Session. In the 5G System, MBS allows the same content (e.g., live streaming, software updates, emergency alerts) to be delivered efficiently to many users simultaneously, either in multicast mode (where only interested UEs receive the data) or broadcast mode (where all UEs in a coverage area can receive it). The MBS session resource is the RAN-side realization of this service: it represents the commitment of transport and radio resources across the NG-RAN to carry the session's traffic.
The term spans multiple interface specifications because an MBS session must be established and maintained across the whole NG-RAN topology. On the NG interface (TS 38.413), the MBS session resource is set up between the 5G Core (specifically the MB-SMF and UPF) and the gNB, carrying session context such as TMGI, QoS parameters, and multicast transport information. On the Xn interface (TS 38.423), it supports distribution of MBS session context between gNBs, enabling mobility and coordinated delivery across neighboring nodes. On the F1 interface (TS 38.473), it allows a gNB-CU to configure and manage MBS resources in its gNB-DUs, while on the E1 interface (TS 37.483) it coordinates the bearer-level resources between the gNB-CU-CP and gNB-CU-UP. TS 38.401 (NG-RAN architecture) provides the overarching framework describing how these resources fit together.
Architecturally, the MBS session resource is identified and managed per MBS session, which is associated with a Temporary Mobile Group Identity (TMGI) and a set of QoS flows. The resource encompasses both user-plane transport resources (e.g., multicast GTP-U tunnels, shared delivery bearers) and control-plane context (e.g., session identifiers, area session information, and configuration parameters). For multicast MBS, the resource may be shared among multiple UEs in a cell, while for broadcast it is available to all UEs. The NG-RAN decides how to map the MBS session onto radio resources, including whether to use point-to-multipoint (PTM) or point-to-point (PTP) delivery depending on UE density and radio conditions.
The MBS session resource is central to the efficiency of 5G multicast/broadcast. Instead of establishing individual unicast bearers for each UE, the network allocates a single shared resource per session per area, dramatically reducing signaling and radio overhead. This is particularly important for use cases such as live event streaming, V2X group communications, public safety, and IoT firmware distribution, where thousands of devices may need the same data. The resource model also supports mobility: as UEs move between cells, the MBS session resource context can be transferred or re-established so that service continuity is maintained.
In summary, the MBS session resource is the NG-RAN's abstraction for all interface and radio assets dedicated to an MBS session. It is defined consistently across NG, Xn, F1, and E1 specifications to ensure that multicast/broadcast sessions can be established, modified, and released coherently throughout the 5G RAN, enabling scalable and spectrally efficient group content delivery.
Purpose & Motivation
The MBS session resource exists to provide a standardized, coherent way to allocate and manage network resources for 5G multicast and broadcast services. Before Release 17, 5G had no native support for group content delivery; operators relied on unicast or on LTE-based eMBMS, which could not integrate cleanly with 5G NR and the 5G Core. Delivering the same content to many users via individual unicast bearers wastes radio spectrum, backhaul capacity, and signaling resources, and scales poorly for large audiences.
By defining the MBS session resource across NG, Xn, F1, and E1 interfaces, 3GPP enabled a single session to be established once and shared by many UEs, while still allowing the RAN to adapt delivery (PTM vs PTP) per cell. This addresses the scalability limitations of unicast and the architectural mismatch of legacy eMBMS. It also provides a common vocabulary for multi-vendor interoperability, ensuring that core network functions, centralized units, distributed units, and gNBs can coordinate MBS delivery consistently.
The concept was motivated by demanding new use cases: immersive media, live sports, public warnings, V2X, and massive IoT updates. These require efficient one-to-many delivery with 5G-grade latency and reliability. The MBS session resource provides the resource-management foundation for these services, allowing operators to offer multicast/broadcast as a first-class 5G capability rather than an overlay.
What changed in its specifications
The latest release-to-release comparison of specifications that define MBS session resource. Each summary describes the whole specification, not only this term.
Rel-19 adds Wireless Access Backhaul (WAB) architecture and node procedures to TS 38.401. It also adds multi-hop Layer-2 sidelink UE-to-Network relay with First, Intermediate and Last U2N Relay UE roles. Ambient IoT support is added, including A-IoT session contexts and AMF connectivity.
Full comparison in TS 38.401 →Rel-19 adds A-IoT procedures and messages, NTN aerial UE flight reporting, Geography Based MDT, and XR PDU Set and bitrate monitoring to TS 38.413. It also adds NG Removal and WAB-node definitions and MBS User Plane Failure Indication.
Full comparison in TS 38.413 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial introduction of the MBS session resource concept, defining how NG-RAN interface and radio resources are provided to support an MBS Session across NG, Xn, F1, and E1 interfaces. This established the architectural foundation for 5G multicast/broadcast in TS 38.401, 38.413, 38.423, 38.473, and 37.483.
The definition text carried over unchanged from Release 17, with the same scope across NG, Xn, F1, and E1 interfaces. Release 18 work focused on enhancements and refinements to MBS operation rather than altering the core definition of the MBS session resource.
Defining Specifications
3GPP specifications that define or reference MBS session resource, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 37.483 vj40 | E1 Application Protocol (E1AP) | Rel-19 read |
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |
| TS 38.423 vj40 | NG-RAN Xn Application Protocol | Rel-19 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |