Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Multicast session

Multicast session

Services →

Multicast session is the group context for providing the same multicast service, which end users join to become members and receive the associated multicast content.

Introduced
Rel-8
Where
Services › Codecs
Specifications
3 specs
Multicast session Description Purpose What changed Neighbours Specifications

Description

A multicast session represents the group construct through which a specific multicast service is provided to its members. Defined in 3GPP Release 8 and maintained through Release 19, the multicast session is the mechanism by which end users signal their interest in receiving a particular multicast service and become members of the associated delivery group. When a user joins a multicast session, they indicate to the network their desire to receive the multicast content, and the network tracks this membership to determine where and how to deliver the service. This concept operates at a level below the service subscription: while subscription establishes a user's eligibility for a multicast service, joining a multicast session represents the user's active participation in consuming that service.

The multicast session is closely related to the concept of the multicast group. In 3GPP terminology, a multicast session can be understood as the group that provides the same multicast service. When an end user joins the multicast session, they become a member of the multicast session, which is functionally equivalent to joining the multicast group associated with the specific multicast service. This joining operation is a dynamic process—users can join and leave sessions as their consumption needs change, and the network adjusts resource allocation accordingly. The session concept thus provides a level of indirection between the service (which is relatively static, tied to subscription) and the actual delivery resources (which are dynamically allocated based on current membership).

From an architectural perspective, the multicast session is managed through signaling between the user equipment and the network, as well as within the core network between functional entities. In the MBMS architecture, session initiation and management involves the BM-SC (Broadcast Multicast Service Center) and other core network nodes. The session start triggers resource allocation in the radio access network, while session stop releases those resources. User joining and leaving operations influence the network's decision about whether to use point-to-multipoint or point-to-point bearers in specific cells, depending on the number and distribution of members.

The distinction between multicast service and multicast session is important for understanding the layered model of 3GPP multicast delivery. A multicast service defines what content is offered and the rules for accessing it, while a multicast session represents an active instance of that service being consumed by a set of joined members. Multiple sessions could theoretically be associated with the same service (for example, different scheduled instances), and users interact with sessions to receive the service content. The session-context nature means that session membership is more transient than service subscription.

In later releases, the multicast session concept has been extended and refined, particularly with the introduction of 5G MBS (Multicast/Broadcast Service) in Release 17, where session management takes on new architectural forms while preserving the fundamental notion of a group context for service delivery. The multicast session remains a foundational concept for understanding how group-based content delivery is managed and controlled in 3GPP networks across generations.

Purpose & Motivation

The multicast session concept was introduced to provide a dynamic, session-level mechanism for managing user participation in multicast services, complementing the more static subscription model. Prior to this, the distinction between being authorized for a service and actively receiving it was not clearly formalized, which created ambiguity in resource management and signaling. The multicast session solves this by creating an explicit group membership construct that users join when they want to receive content and leave when they are done, allowing the network to know precisely which users are actively consuming the service at any given moment.

This distinction is crucial for efficient resource allocation. If the network only knew about subscriptions, it would have to provision resources for all subscribers at all times, which is wasteful. By tracking session membership, the network can allocate multicast resources only where and when users have actually joined, optimizing spectrum usage and backhaul capacity. This is particularly important for the radio access network, where the decision to use point-to-multipoint bearers (efficient for many users) versus point-to-point bearers (efficient for few users) depends on the number and location of active session members.

The concept also provides a clean interface for user-initiated control. Users can dynamically join and leave multicast sessions through well-defined signaling procedures, giving them control over their content consumption without requiring changes to their service subscriptions. This decoupling of subscription (a commercial/administrative relationship) from session participation (a technical/dynamic process) is a key architectural principle that has proven valuable across multiple generations of 3GPP technology, from the original MBMS in UMTS through LTE eMBMS and into 5G MBS.

What changed in its specifications

The latest release-to-release comparison of specifications that define Multicast session. Each summary describes the whole specification, not only this term.

TS 26.346Rel-16 → Rel-17

Added a profiled FLUTE FDT schema with semantics and versioning, plus 5GMS references and requirements, removing old schema clauses. Updated User Service Bundle Description schema versions and added a new unicast announcement FQDN format.

Full comparison in TS 26.346 →
TR 26.946Rel-12 → Rel-13

Rel-13 adds Enhanced DASH, replacing detailed partial file delivery clauses with references to other 3GPP specifications.

Full comparison in TR 26.946 →

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.

Rel-8 Initial

Initial definition introduced the multicast session as the group for providing the same multicast service, where the end user joins the multicast session to become a member. This established the session-level membership model that complements service-level subscription in the MBMS framework.

The definition carried over unchanged from Rel-8, with the session continuing to be defined as the group for providing the same multicast service.

[CHANGE UNKNOWN] The definition text was replaced by a pointer to 3GPP TS 22.146 [2]. The exact nature of the change cannot be assessed from the available wording, though the shift to a cross-reference suggests the concept may have been consolidated elsewhere in the specification structure.

[CHANGE UNKNOWN] The definition continues to reference 3GPP TS 22.146 [2]; the specific change from the previous release cannot be determined from the available wording.

[CHANGE UNKNOWN] The definition remains a cross-reference to 3GPP TS 22.146 [2]; the change cannot be assessed from the available wording.

[CHANGE UNKNOWN] References 3GPP TS 22.146 [2] with insufficient wording to determine what changed.

[CHANGE UNKNOWN] References 3GPP TS 22.146 [2] with insufficient wording to determine what changed.

[CHANGE UNKNOWN] References 3GPP TS 22.146 [2] with insufficient wording to determine what changed.

[CHANGE UNKNOWN] References 3GPP TS 22.146 [2] with insufficient wording to determine what changed.

[CHANGE UNKNOWN] References 3GPP TS 22.146 [2] with insufficient wording to determine what changed; this release also introduced 5G MBS which may have affected how multicast sessions are managed.

[CHANGE UNKNOWN] References 3GPP TS 22.146 [2] with insufficient wording to determine what changed.

[CHANGE UNKNOWN] References 3GPP TS 22.146 [2] with insufficient wording to determine what changed.

Defining Specifications

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

SpecificationTitleRelease
TS 26.346 vj30 MBMS User Services Specification Rel-19 read
TR 26.946 vj00 MBMS User Services Overview Rel-19 read
TS 29.199 3GPP TS 29.199 Rel-8 read