At a glance
- MBS User Services: the MBSF (control plane) and MBSTF (user plane) in the network, the optional MBS AF, MBS AS and MBSSF, and the MBS Client in the UE. TS 26.502 adds reference points MBS-1 to MBS-11 to the Nmb reference points of TS 23.247.
- APIs: Nmbsf (TS 29.580) at Nmb10 and Nmb5, Nmbstf (TS 29.581) at Nmb2; the announcement, repair and key retrieval protocols at MBS-1, MBS-5, MBS-4-UC and MBS-10 are in TS 26.517.
- MBS: the MB-SMF and MB-UPF, with MBS extensions to the AMF, SMF, UPF, PCF, NEF, NRF, UDM and NG-RAN. New reference points include N3mb, N4mb, N6mb and N19mb.
- Delivery: 5GC Shared delivery (one copy to each NG-RAN node) is used for broadcast and multicast; 5GC Individual delivery (one copy per UE, in a PDU Session) only for multicast. Over the radio, NG-RAN uses PTM or PTP.
MBS User Services
Functions
- MBSF: receives provisioning and control from the MBS Application Provider, directly at Nmb10 or through the NEF at Nmb5. It invokes MBS Session operations on the MB-SMF at Nmb1 and configures the MBSTF at Nmb2. It compiles the User Service Announcement for each MBS User Data Ingest Session and manages its updates.
- MBSTF: receives user plane data at Nmb8 and sends MBS data packets to the MB-UPF at Nmb9. It acts as a user plane anchor when it sources IP multicast traffic. It receives its Distribution Session configurations from the MBSF at Nmb2 and sends notification events back, for example data ingest failure, session terminated or delivery started. For the Object Distribution Method its subfunctions are object ingest, object segmentation into payload units, optional Application Layer FEC (AL-FEC), packetisation and packet scheduling to a target bit rate.
- MBS AF (optional): serves User Service Announcements to the MBSF Client by unicast at MBS-5, and object manifests and announcements to the MBSTF at MBS-11. The MBSF configures it at MBS-3, an interaction TS 26.502 does not define further.
- MBS AS (optional): provides a byte-range file repair service to the MBSTF Client at MBS-4-UC, for the Object Distribution Method. It may stand alone or be co-located with the MBSTF or with a 5GMS AS.
- MBSSF (optional): the MBS Security Function. It provides a security anchor at MBS-10, realising the user plane security procedure of TS 33.501, and may be co-located with the MBSF or the MBSTF.
- MBS Client, in the UE, split into two subfunctions. The MBSF Client communicates with the MBS AF at MBS-5 on User Service control, and with the MBSSF at MBS-10. The MBSTF Client receives from the MBSTF at MBS-4-MC and from the MBS AS at MBS-4-UC, and provides an MBS Application Data Session to the application.
- MBS-Aware Application: uses the MBS Client at MBS-6 and MBS-7.
- MBS Application Provider: plays the role of the AF/AS. Outside the trusted data network it reaches the MBSF through the NEF at N33 instead of Nmb10.
The functions are shown as standalone. In deployments they may be co-located with other functions.
Reference points
TS 26.502 reuses seven reference points of TS 23.247 (Nmb1, Nmb2, Nmb5, Nmb8, Nmb9, Nmb10 and Nmb12) and adds its own.
Reference points of MBS User Services
| Reference point | Between | Purpose | Specified |
|---|---|---|---|
| Nmb10 | MBS Application Provider (AF/AS) and MBSF | Provisioning of MBS User Services, by invoking the Nmbsf service | TS 26.502 cl. 7.2; TS 29.580 |
| Nmb5 | NEF and MBSF | The same Nmbsf service, for an AF/AS outside the trusted domain | TS 26.502 cl. 7.2; TS 29.580 |
| Nmb1 | MBSF and MB-SMF | MBS Session operations (Nmbsmf) | TS 23.247 cl. 9.1 |
| Nmb2 | MBSF and MBSTF | Configuration and control of the distribution methods (Nmbstf); push of object manifests | TS 26.502 cl. 7.3; TS 29.581 |
| Nmb8 | MBS Application Provider and MBSTF | Content ingest by the MBSTF, pull or push | TS 26.502 cl. 4.3.3 |
| Nmb9 | MBSTF and MB-UPF | MBS data packets towards the MB-UPF | TS 23.247 cl. 5.3.1 |
| Nmb12 | MBSF and PCF | QoS for the MBS Session, set from the provisioned 5QI | TS 26.502 table 4.5.6-1 |
| MBS-1 | MBSF and MBS Application Provider | Exposure of the User Service Announcement for private advertisement at MBS-8 | TS 26.517 cl. 8A |
| MBS-3 | MBSF and MBS AF | Configuration of the MBS AF and publication of announcements to it. Not described further | none |
| MBS-4-MC | MBSTF and MBS Client | Unidirectional multicast distribution of content | TS 26.517 cl. 6 and 7 |
| MBS-4-UC | MBSTF Client and MBS AS | File-based unicast repair | TS 26.517 cl. 10 |
| MBS-5 | MBSF Client and MBS AF | User plane interactions for control and service handling | TS 26.517 cl. 9 |
| MBS-6 | MBS-Aware Application and MBSF Client | API to manage and control MBS User Services | none |
| MBS-7 | MBS-Aware Application and MBSTF Client | API to receive the distributed user data | none |
| MBS-8 | MBS Application Provider and MBS-Aware Application | Announcement of MBS User Services. Beyond the scope of 3GPP | none |
| MBS-9 | MBSF and MBS AS | Configuration of the MBS AS. Not described further | none |
| MBS-10 | MBSF Client and MBSSF | Authorisation of access to security-protected MBS data | TS 26.517 cl. 11 |
| MBS-11 | MBSTF and MBS AF | Retrieval of object manifests and the announcements they list | TS 26.502 cl. 4.3.3.2 |
Two more reference points, MBS-6′ and MBS-7′, sit inside the MBS Client between the MBSF Client and the MBSTF Client. They are outside the scope of MBS User Services.
Services and APIs
The MBSF exposes two services and the MBSTF one. An MBS Application Provider outside the trusted data network reaches the MBSF services through the NEF, as Nnef_MBSUserService and Nnef_MBSUserDataIngestSession. The protocol and data model of each service are specified in TS 29.580 (Nmbsf) and TS 29.581 (Nmbstf); TS 29.580 calls the Destroy operation of TS 26.502 "Delete".
Services, operations and resources
| Service | Operations (TS 26.502) | Consumer | Resources (stage 3) |
|---|---|---|---|
| Nmbsf_MBSUserService | Create, Retrieve, Update, Destroy | AF, NEF | TS 29.580 cl. 6.1: /mbs-user-services, /mbs-user-services/{mbsUserServId} |
| Nmbsf_MBSUserDataIngestSession | Create, Retrieve, Update, Destroy, StatusSubscribe, StatusUnsubscribe, StatusNotify, StatusSubscribeMod | AF, NEF | TS 29.580 cl. 6.2: /sessions, /sessions/{sessionId}, /status-subscriptions, /status-subscriptions/{subscriptionId} |
| Nmbstf_MBSDistributionSession | Create, Retrieve, Update, Destroy, StatusSubscribe, StatusUnsubscribe, StatusNotify, StatusSubscribeMod | MBSF | TS 29.581 cl. 6.1: /dist-sessions, /dist-sessions/{distSessionRef}, /dist-sessions/{distSessionRef}/subscriptions |
| Reference point | API or protocol | TS 26.517 |
|---|---|---|
| MBS-1 | User Service Description retrieval API, exposed by the MBSF | cl. 8A |
| MBS-5 | User Service Description retrieval API, exposed by the MBS AF, base path {apiRoot}/3gpp-mbs-user-service-discovery/{apiVersion}/ | cl. 9 |
| MBS-4-UC | Unicast Object Repair protocol, between the MBSTF Client and the MBS AS | cl. 10 |
| MBS-10 | MBS Service Key retrieval from the MBSSF, using the protocol of TS 33.246 clause 6.3 | cl. 11 |
| Nmb8 | General HTTP provisions for the MBSTF endpoint that receives pushed objects | cl. 8.2.1.3 |
Distribution methods
| Method | What it delivers | Operating modes (TS 26.502 tables 6.1-1 and 6.2-1) |
|---|---|---|
| Object Distribution Method | Discrete binary objects, in real time or not, including media segments | OBJECT_SINGLE: each ingested object is distributed once. OBJECT_COLLECTION: a set of objects described by a manifest, distributed once. OBJECT_CAROUSEL: a set of objects repeated as the manifest specifies, with changes reflected at the next opportunity. OBJECT_STREAMING: a sequence of objects streamed in real time, for example on the schedule of a DASH MPD |
| Packet Distribution Method | Application Data Units, delivered transparently | PACKET_FORWARD_ONLY: the payloads of ingested IP packets are forwarded to the MB-UPF in new IP packets (Layer 3 proxying). PACKET_PROXY: the payloads of ingested UDP packets are forwarded in new UDP packets (Layer 4 proxying). RTP packets can be distributed in either mode |
When FLUTE realises the Object Distribution Method, the MBS Distribution Session conforms to the MBMS Download Profile of TS 26.346 clause L.4, with the additions of TS 26.517 clause 6.2. TS 26.517 recommends the OBJECT_STREAMING mode for streaming DASH or HLS content to a Media Player in the UE. The Packet Distribution Method combines three delivery methods of TS 26.346, the MBMS Streaming, Group Communication and Transparent Delivery Methods, with modifications.
For the Object Distribution Method, ingest at Nmb8 is pull-based (the MBSTF fetches objects from the MBS Application Provider) or push-based (the MBS Application Provider sends them).
Sessions and their life cycle
An MBS Application Provider provisions an MBS User Service, and within it time-bound MBS User Data Ingest Sessions. Each ingest session has one or more MBS Distribution Sessions; an ingest session without any is not valid. A Distribution Session uses an MBS Session for delivery, identified by a TMGI or a Source-Specific Multicast (SSM) address. It has one MBS Session Context, unless several target service areas are specified.
An ingest session may carry a set of active periods. If none is given, it and its Distribution Sessions are active until further notice. The Service type (multicast or broadcast) of an MBS User Service cannot be changed; the other parameters assigned by the provider can be updated at any time.
| State of a Distribution Session | What happens (TS 26.502 clause 4.6.1) |
|---|---|
| INACTIVE | The state when the session is first provisioned in the MBSF, and its replica in the MBSTF |
| ESTABLISHED | Shortly before the start of the active period, the MBSF reserves resources with the MB-SMF and establishes the session in the MBSTF, which may start ingesting data but not distributing it. The MBSF advertises the session |
| ACTIVE | At the start time, the MBSTF starts sending MBS data packets to the MB-UPF at Nmb9, and MBS Clients that activated reception start receiving at MBS-4-MC |
| DEACTIVATING | At the end time, or on a severe error, the MBSF stops advertising the session, deactivates and releases it in the MBSTF, and releases the resources with the MB-SMF |
How a User Service is provisioned and announced
TS 26.502 clauses 5.3 to 5.5, condensed, with the step numbers:
- Optional TMGI pre-allocation (step 1). The MBS Application Provider may pre-allocate a TMGI with Nmbsmf_TMGI_Allocate on the MB-SMF at Nmb13 (or N33+N29mb through the NEF).
- User Service (step 2). It invokes Nmbsf_MBSUserService_Create at Nmb10 (or N33+Nmb5).
- Ingest session (steps 3 and 4). It invokes Nmbsf_MBSUserDataIngestSession_Create, with the details of one or more Distribution Sessions, and subscribes to its status events.
- MBS Session (steps 6 to 9). Shortly before the active period, the MBSF may allocate a TMGI, then invokes Nmbsmf_MBSSession_Create on the MB-SMF at Nmb1. The MB-SMF can allocate the TMGI as a side effect.
- Distribution Session in the MBSTF (steps 10 to 15). The MBSF invokes Nmbstf_MBSDistributionSession_Create at Nmb2, a mirror of its own entity. The MBSTF tries to establish content ingest at Nmb8; on success the session becomes ESTABLISHED.
- Announcement (clause 5.4). The MBSF compiles an MBS User Service Announcement describing the current Distribution Sessions. It is delivered by unicast at MBS-5, in the MBS User Service Announcement Channel at MBS-4-MC (an MBS Distribution Session in OBJECT_CAROUSEL mode), or passed back to the provider for private advertisement at MBS-8.
- Activation (clause 5.5.1). At the start time, for a multicast service, the MBSF activates the Multicast MBS Session in the MB-SMF so that UEs can join. It then sets the Distribution Session to ACTIVE in the MBSTF with Nmbstf_MBSDistributionSession_Update.
- Reception (clause 5.5.2). The MBS-Aware Application asks the MBSF Client at MBS-6 to activate the User Service; the MBSTF Client receives the MBS data at MBS-4-MC.
- Deactivation (clause 5.5.4). At the end time, the MBSF tears down the MBS Session for a broadcast service, or for the last period. For a multicast service with further periods, it only deactivates the MBS Session.
MBS
Functions in the 5G System
Functions and their MBS roles (TS 23.247 clause 5.3.2)
| Function | MBS role, as TS 23.247 lists it |
|---|---|
| MB-SMF | MBS session management, including QoS control; configures the MB-UPF; allocates and de-allocates TMGIs; for broadcast, controls shared delivery through the AMF; for multicast, provides MBS Session Context information to the SMF and controls the MB-UPF for individual delivery |
| MB-UPF | Processes incoming downlink multicast and broadcast packets; enforces QoS; delivers data to NG-RAN nodes for 5GC Shared delivery, and multicast data to the UPF for 5GC Individual delivery |
| SMF | Discovers the MB-SMF for a Multicast MBS session; authorises join requests if needed; interacts with RAN and UPF for individual delivery. The SMF and MB-SMF may be co-located |
| UPF | Receives multicast data from the MB-UPF and delivers it to UEs through PDU Sessions, for individual delivery |
| AMF | Signalling with NG-RAN and the MB-SMF for MBS Session management; selects the NG-RAN nodes for broadcast distribution and for multicast activation notification of UEs in CM-IDLE |
| NG-RAN | Delivers MBS data over radio with PTM or PTP; controls switching between PTM and PTP per UE; supports multicast service continuity at Xn and N2 handover; group paging; may move multicast UEs to RRC_INACTIVE |
| UE | Receives multicast with PTM or PTP in RRC_CONNECTED, and if supported with PTM in RRC_INACTIVE; receives broadcast with PTM; joins and leaves Multicast MBS sessions |
| AF | Requests multicast or broadcast service with service information, including QoS requirements |
| NEF | Interface to AFs for MBS service provisioning, session and QoS management; selects the MB-SMF |
| MBSF | Service level functionality and interworking with LTE MBMS; selects the MB-SMF; controls the MBSTF if used |
| MBSTF | Media anchor; sourcing of IP multicast; packet transport functions such as framing and FEC; delivery of input files as objects or object flows |
| PCF | QoS handling and policy information for the MBS Session, when dynamic PCC is needed |
| UDM, UDR | MBS subscription data for authorising UEs for multicast MBS sessions |
| NRF | The MB-SMF and MBSF NF types; MB-SMF discovery |
Reference points and interfaces
New reference points (TS 23.247 clause 5.3.1)
| Reference point | Between |
|---|---|
| N3mb | RAN and MB-UPF |
| N4mb | MB-SMF and MB-UPF (protocols in TS 29.244) |
| N6mb | MB-UPF and AF/AS |
| N7mb | MB-SMF and PCF |
| N11mb | AMF and MB-SMF |
| N16mb | SMF and MB-SMF |
| N19mb | UPF and MB-UPF |
| N29mb | MB-SMF and NEF |
| Nmb1 | MB-SMF and MBSF |
| Nmb2 | MBSF and MBSTF |
| Nmb5 | MBSF and NEF |
| Nmb8 | MBSTF and AF/AS |
| Nmb9 | MB-UPF and MBSTF |
| Nmb10 | MBSF and AF/AS |
| Nmb12 | MBSF and PCF |
| Nmb13 | MB-SMF and AF/AS |
| Nmb14 | NEF and MBSTF |
| N101 | MB-SMF and CHF |
In functionality, Nmb13, N29mb and Nmb1 are identical, Nmb5 and Nmb10 are identical, and Nmb9 and N6mb are identical. The existing reference points N1, N2, N4, N5, N10, N11, N30, N33 and N40 are enhanced for MBS. Between NG-RAN and the MB-SMF, the AMF relays the N2 SM information transparently.
Service-based interfaces and their services (TS 23.247 clause 9)
| Interface | Service | Operations | Consumers |
|---|---|---|---|
| Nmbsmf (MB-SMF) | Nmbsmf_TMGI | Allocate, Deallocate | NEF, MBSF, AF |
| Nmbsmf_MBSSession | Create, Update, Delete, StatusSubscribe, StatusUnsubscribe, StatusNotify | MBSF, NEF, AF | |
| ContextStatusSubscribe, ContextStatusUnsubscribe, ContextStatusNotify | SMF | ||
| ContextUpdate | AMF, SMF | ||
| Npcf (PCF) | Npcf_MBSPolicyControl | Create, Update, Delete | MB-SMF |
| Npcf_MBSPolicyAuthorization | Create, Update, Delete | AF, NEF, MBSF | |
| Namf (AMF) | Namf_MBSBroadcast | ContextCreate, ContextUpdate, ContextRelease, ContextStatusNotify | MB-SMF |
| Namf_MBSCommunication | N2MessageTransfer | MB-SMF | |
| Nnef (NEF) | Nnef_MBSTMGI | Allocate, Deallocate, ExpiryNotify | AF |
| Nnef_MBSSession | Create, Update, Delete, StatusNotify, StatusSubscribe, StatusUnsubscribe | AF | |
| Nnef_MBSGroupMsgDelivery | Create, Update, Delete, StatusNotify | AF | |
| Nmbsf (MBSF) | defined in TS 26.502 |
NGAP procedures between NG-RAN and the AMF (TS 38.413 clauses 8.17 and 8.18)
| Procedure | Purpose |
|---|---|
| Broadcast Session Setup | Set up MBS session resources in the NG-RAN node for a broadcast MBS session |
| Broadcast Session Modification | Update the resources or the area of a broadcast MBS session |
| Broadcast Session Release | Release the resources of a broadcast MBS session |
| Broadcast Session Release Required | Lets the NG-RAN node trigger the AMF to release a broadcast MBS session |
| Broadcast Session Transport | Assign NG-U resources for a broadcast MBS session |
| Distribution Setup | Assign NG-U resources for a multicast MBS session |
| Distribution Release | Release the NG-U resources of a multicast MBS session, or of one area session of it |
| Multicast Session Activation | Activate the resources of a multicast MBS session in an NG-RAN node |
| Multicast Session Deactivation | Deactivate them |
| Multicast Session Update | Update the resources or the area of a multicast MBS session |
All of them use non-UE-associated signalling.
Delivery methods
Between the 5G Core and NG-RAN there are two delivery methods. TS 23.247 does not call them unicast, multicast or broadcast:
- 5GC Shared MBS traffic delivery: the 5G Core receives a single copy of the MBS data packets and delivers a single copy to an NG-RAN node, which delivers it to one or more UEs. It is used for broadcast and multicast MBS sessions, and is required in all MBS deployments.
- 5GC Individual MBS traffic delivery: the 5G Core delivers separate copies to individual UEs, each through a PDU Session associated with the Multicast MBS session. It is used only for multicast, and is required for mobility where NG-RAN nodes do not all support MBS.
Over the radio, NG-RAN has two delivery methods:
- Point-to-Multipoint (PTM): a single copy over the radio interface to multiple UEs.
- Point-to-Point (PTP): separate copies over the radio interface to individual UEs.
NG-RAN may combine PTP and PTM. For a broadcast service only 5GC Shared delivery with PTM applies. For a multicast service, an NG-RAN node that supports MBS is served with 5GC Shared delivery; the same multicast session may be delivered with Shared delivery to some UEs and Individual delivery to others.
| 5GC Shared | 5GC Individual | |
|---|---|---|
| MBS sessions | Broadcast and multicast | Multicast only |
| From the MB-UPF to | NG-RAN nodes, at N3mb | UPFs, at N19mb; the UPF forwards the data in the N3 tunnel of each associated PDU Session |
| Transport | A common GTP-U tunnel per MBS session with IP multicast, otherwise a GTP-U tunnel per MBS session per NG-RAN node | A common GTP-U tunnel per MBS session with IP multicast, otherwise one per MBS session per UPF |
| Shared by | All UEs that joined the multicast session through that NG-RAN node (one tunnel per session, MBS service area and node) | All associated PDU Sessions served by that UPF |
| Radio | PTM or PTP | Unicast radio bearers of the associated PDU Session |
The MB-UPF is the MBS Session Anchor. When the MBSTF is involved, the MBSTF is the media anchor. The MB-UPF adds a sequence number to the MBS data of each MBS QoS Flow.
NG-RAN
The overall NG-RAN architecture applies to NR MBS. The Layer 2 stack for MBS uses the same sublayers, with a reduced set of functions: SDAP maps MBS QoS flows to MBS Radio Bearers (MRBs), and PDCP keeps transfer, sequence numbers, header compression, reordering and duplicate discarding.
MBS Radio Bearers (TS 38.300 clause 16.10.3)
| Session | UE state | MRB configurations |
|---|---|---|
| Multicast | RRC_CONNECTED, by dedicated RRC signalling | RLC-UM or RLC-AM for PTP; DL-only RLC-UM for PTM; or two or three RLC entities that combine a PTP leg (RLC-UM or RLC-AM) with a PTM leg (DL-only RLC-UM). The gNB may change the MRB type |
| Multicast | RRC_INACTIVE, by broadcast and/or dedicated RRC signalling | DL-only RLC-UM for PTM |
| Broadcast | RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED, by broadcast RRC signalling | One DL-only RLC-UM entity for PTM |
| Item | Role (TS 38.300) |
|---|---|
| MTCH (MBS Traffic Channel) | PTM downlink channel for the data of a multicast or broadcast session |
| DTCH | PTP channel for the data of a multicast session |
| MCCH (MBS Control Channel) | PTM downlink channel for broadcast or multicast control information. Broadcast MCCH and multicast MCCH are independent channels; the multicast MCCH is used only for reception in RRC_INACTIVE |
| G-RNTI | Identifies dynamically scheduled PTM transmissions of MTCH |
| G-CS-RNTI | Identifies PTM transmissions of MTCH scheduled with a configured grant |
| MCCH-RNTI | Identifies MCCH transmissions and change notifications for broadcast |
| Multicast MCCH-RNTI | Identifies MCCH transmissions and change notifications for multicast in RRC_INACTIVE |
| SIB20, SIB21 | MCCH configuration, and service continuity information, for broadcast |
| SIB24 | Information to acquire the multicast MCCH and MTCH configuration for RRC_INACTIVE |
In a PTP transmission, the gNB schedules a UE-specific PDSCH with a PDCCH whose CRC is scrambled by a UE-specific RNTI, such as the C-RNTI. In a PTM transmission, it schedules a group-common PDSCH with a group-common PDCCH whose CRC is scrambled by a group-common RNTI. When a UE has both a PTM and a PTP leg, the gNB decides dynamically which to use, based on information such as the session QoS requirements, the number of joined UEs and the UE feedback on reception quality. The same QoS requirements apply whichever it chooses.
Multicast session states
| State | In TS 23.247 clause 4.3 |
|---|---|
| Configured | Information about the session (for example QoS) is held in the 5G Core, but no user plane resources towards NG-RAN are reserved and no data can be sent. A TMGI can be allocated |
| Active | The session is established and data can be sent to the UEs that joined it. Radio resources are established |
| Inactive | The session is established but no data is sent. Radio resources are released |
The first accepted join request establishes the session towards NG-RAN and the UE. For a broadcast MBS session, TS 23.247 clause 4.2.2 describes phases: MBS Session Creation and establishment by the AF, service announcement, data transfer, and Session Release, at which the 5G System releases the resources and deletes the session.
Sources for this page
- MBS User Services, functions and reference points: TS 26.502 V18.6.0, clauses 4.2.1, 4.2.2, 4.3.1 to 4.3.6 and 4.4.1, table 4.5.6-1.
- Services and APIs: TS 26.502 V18.6.0, clause 7 and tables 7.2-1 and 7.3-1; TS 29.580 V18.8.0, clauses 1, 5.2, 5.3, 6.1.3 and 6.2.3; TS 29.581 V18.6.0, clauses 1, 4.1 and 6.1.3; TS 26.517 V18.6.0, clauses 8.2.1.3, 8A, 9, 10 and 11.
- Distribution methods: TS 26.502 V18.6.0, clauses 3.1, 4.3.3.2, 6.1 and 6.2; TS 26.517 V18.6.0, clauses 6.2.1, 6.2.3.5 and 7.2.1.
- Sessions and their life cycle; provisioning and announcement: TS 26.502 V18.6.0, clauses 3.1, 4.5.2 to 4.5.6, 4.6.1, 5.3, 5.3A, 5.4, 5.5.1, 5.5.2 and 5.5.4.
- MBS, functions, reference points and services: TS 23.247 V18.8.0, clauses 5.1, 5.3.0, 5.3.1, 5.3.2, 8.1 and 9; TS 38.413 V18.11.0, clauses 8.17 and 8.18.
- Delivery methods: TS 23.247 V18.8.0, clauses 3.1, 4.1, 6.7 and 7.2.1.3.
- NG-RAN: TS 38.300 V18.11.0, clauses 3.1, 7.3.1, 8.1, 16.10.2 to 16.10.4 and 16.10.5.4.
- Multicast session states: TS 23.247 V18.8.0, clauses 4.2.2, 4.3 and 7.2.1.1.