9 Network Function Services
23.2473GPPArchitectural enhancements for 5G multicast-broadcast servicesRelease 18TS
9.1 MB-SMF Services
9.1.1 General
The following table illustrates the MB-SMF Services for MBS.
Table 9.1.1-1: NF services provided by MB-SMF
|
Service Name |
Service Operations |
Operation Semantics |
Example Consumer (s) |
|
Nmbsmf_TMGI |
Allocate |
Request/Response |
NEF, MBSF, AF |
|
Deallocate |
Request/Response |
NEF, MBSF, AF |
|
|
ContextStatusSubscribe |
SMF |
||
|
Nmbsmf_MBSSession |
ContextStatusUnsubscribe |
Subscribe/Notify |
SMF |
|
ContextStatusNotify |
SMF |
||
|
ContextUpdate |
Request/Response |
AMF, SMF |
|
|
StatusSubscribe |
Subscribe/Notify |
MBSF, NEF, AF |
|
|
StatusUnsubscribe |
MBSF, NEF, AF |
||
|
StatusNotify |
MBSF, NEF, AF |
||
|
Create |
Request/Response |
MBSF, NEF, AF |
|
|
Update |
Request/Response |
MBSF, NEF, AF |
|
|
Delete |
Request/Response |
MBSF, NEF, AF |
9.1.2 Nmbsmf_TMGI service
9.1.2.1 General
Service description: NF Service Consumer can use this service to request the allocation of TMGIs and release allocated TMGIs.
9.1.2.2 Nmbsmf_TMGI_Allocate service operation
Service operation name: Nmbsmf_TMGI_Allocate
Description: This service is used by the NF Service Consumer to request the allocation of TMGI(s) or request to refresh previously allocated TMGI(s).
Inputs, Required: Number of TMGIs.
Inputs, Optional: TMGI(s) (i.e. the TMGI(s) to be extended the expiry time).
Outputs, Required: TMGI(s), Expiry Time of the TMGI(s).
Outputs, Optional: NID.
9.1.2.3 Nmbsmf_TMGI_Deallocate service operation
Service operation name: Nmbsmf_TMGI_Deallocate
Description: NF Service Consumer can use this service to request the release of TMGI(s).
Inputs, Required: TMGI(s).
Inputs, Optional: None.
Outputs, Required: Success or not.
Outputs, Optional: None.
9.1.3 Nmbsmf_MBSSession service
9.1.3.1 General
Service description: The following are the key functionalities of this NF service:
– (between AMF or SMF and MB-SMF) For multicast, NF Service Consumer can use this service to request the reception of MBS data or to terminate the reception of MBS data of a Multicast MBS session, or for a location dependent Multicast MBS session, the part of the MBS multicast session within a service area;
– (between SMF and MB-SMF) For multicast, allow consumer NFs to query information (e.g. QoS information) about MBS Session. This service will be invoked by SMF for UE join event;
– (between SMF (only for multicast) or MBSF/NEF and MB-SMF) Allow consumer NFs to subscribe and unsubscribe for an Event ID and MBS Session, or for a location dependent MBS session, related to the part of the MBS session within a service area (only for MBSF/NEF);
– (between SMF (only for multicast) or MBSF/NEF and MB-SMF) Notifying events on the MBS Session, or for a location dependent MBS session, related to the part of the MBS session within a service area (only for MBSF/NEF), to the subscribed NFs;
– (between MBSF/NEF/AF and MB-SMF) Creation/Modification/Activation/Deactivation/Release of Multicast MBS session, or for a location dependent Multicast MBS session, the part of the Multicast MBS session within a service area; and
– (between MBSF/NEF and MB-SMF) Creation/Modification/Start/Stop/Release of Broadcast MBS sessions, or for a location dependent Broadcast MBS session, the part of the Broadcast MBS session within a service area.
The following events related to MBS Session Context can be subscribed by SMF as consumer NF:
– (between SMF and MB-SMF, only for multicast) QoS change: The event notification is sent when QoS within a Multicast MBS session changes, e.g. adding/removing QoS flow(s);
– (between SMF and MB-SMF only for multicast) multicast session state (Active, Inactive);
– (between SMF and MB-SMF only for multicast) Multicast MBS session service area change (for a location dependent Broadcast MBS session, the notification relates to the part of the Broadcast MBS session within a service area);
– (between SMF and MB-SMF only for multicast) Multicast MBS session release;
– (between SMF and MB-SMF only for multicast) multicast session security context update.
The following events related to an MBS session, or for a location dependent MBS session, related to the part of the MBS session within a service area, can be subscribed by MBSF, NEF, or AF as consumer NF:
– (between MBSF/NEF/AF and MB-SMF) MBS session release due to TMGI expiry;
– (between MBSF/NEF/AF and MB-SMF) Broadcast delivery status.
NOTE: Whether event IDs are needed can be determined by stage 3.
9.1.3.2 Nmbsmf_MBSSession_ContextUpdate service operation
Service operation name: Nmbsmf_MBSSession_ContextUpdate
Description: NF Service Consumer can use this service to request or terminate the reception of data of a multicast session, or for a location dependent MBS session, related to the part of the MBS session within a service area.
Inputs, Required: MBS Session ID, if consumer is AMF: N2 container (Establishment or Release, MBS Session ID, Possible Area Session ID, Possible GTP Tunnel info for unicast transport, Possible tracking Area IDs), AMF ID, if consumer is SMF: SMF ID, MBS Session ID, Action(Establishment or Release).
Inputs, Optional: if consumer is SMF: Area Session ID, Unicast GTP Tunnel info of the UPF.
Outputs, Required: Success or not.
Outputs, Optional: if consumer is AMF: N2 container (MBS Session ID, Possible Multicast DL tunnel info, multicast QoS flow information, session state (Active/Inactive), [MBS service areas]); if consumer is SMF: Multicast DL tunnel info.
9.1.3.3 Nmbsmf_MBSSession_ContextStatusSubscribe service operation
Service operation name: Nmbsmf_MBSSession_ContextStatusSubscribe
Description: Service Consumer NF can use this service operation to request information (e.g. QoS information) about a multicast session and to subscribe to notification of events about the multicast session context.
Inputs, Required: MBS Session ID, Notification Target Address, Events ID(s).
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: Event information (e.g. QoS information for multicast session, multicast MBS session state (Active, Inactive), multicast session service area for local multicast service), Start time of multicast MBS session, multicast DL tunnel info, if consumer is SMF: indication that the multicast MBS session allows any UE to join, multicast session security context.
9.1.3.4 Nmbsmf_MBSSession_ContextStatusNotify service operation
Service operation name: Nmbsmf_MBSSession_ContextStatusNotify
Description: This service operation, which is applicable to multicast MBS session, is used by the MB-SMF to notify its consumers about events of an MBS Session, or for a location dependent MBS session, related to a service area change.
Inputs, Required: MBS Session ID, Event ID.
Inputs, Optional: Event information (e.g. QoS information of MBS Session, MBS service area, Area Session ID, updated multicast session security context).
Outputs, Required: Operation execution result indication.
Outputs, Optional: Cause.
9.1.3.5 Nmbsmf_MBSSession_ContextStatusUnsubscribe service operation
Service operation name: Nmbsmf_MBSSession_ContextStatusUnsubscribe
Description: This service operation, which is applicable to multicast MBS session, is used by the consumer to unsubscribe to notifications about MBS context events.
Inputs, Required: MBS Session ID.
Inputs, Optional: None.
Outputs, Required: Operation execution result indication.
Outputs, Optional: None.
9.1.3.6 Nmbsmf_MBSSession_Create service operation
Service operation name: Nmbsmf_MBSSession_Create
Description: Create a new multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area. Optionally subscribe to notifications for this MBS session.
Input, Required: MBS Session ID (SSM or TMGI) or TMGI allocation request, MBS Service Type (multicast or broadcast).
Input, Optional: DNN, S-NSSAI, MBS service area, MBS Service Information (as defined in clause 6.14), Input Transport Address Request, MBS start time, MBS termination time. For a multicast session, indication that any UE may join, multicast session security context. For a broadcast session, MBS FSA ID(s). For subscription to notifications event ID(s), Notification Target Address, Request for location dependent MBS session.
Output, Required: Result Indication.
Output, Optional: TMGI, NID, Expiry Time of the TMGI, Cause, MB-UPF tunnel info, MBS FSA ID(s), Area Session ID.
9.1.3.7 Nmbsmf_MBSSession_Update service operation
Service operation name: Nmbsmf_MBSSession_Update
Description: Update the established multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area, e.g. QoS update.
Input, Required: MBS Session ID.
Input, Optional: MBS Service Information (as defined in clause 6.14), MBS service area, for a broadcast session, MBS FSA ID(s), Area Session ID, indication that the PCF has to be contacted. For multicast, session state (Active/Inactive), updated multicast session security context.
Output, Required: Result Indication.
Output, Optional: Cause, MBS FSA ID(s).
9.1.3.8 Nmbsmf_MBSSession_Delete service operation
Service operation name: Nmbsmf_MBSSession_Delete
Description: Release the multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area. The MBS session is deleted and the subscription (if any) to notifications about events related to the status of the MBS session is terminated.
Input, Required: MBS Session ID.
Input, Optional: Area Session ID.
Output, Required: Result Indication.
Output, Optional: Cause.
9.1.3.9 Nmbsmf_MBSSession_StatusNotify service operation
Service operation name: Nmbsmf_MBSSession_StatusNotify
Description: This service operation is used by the MB-SMF to notify its consumers about the status change of the MBS session, or for a location dependent MBS session, of the part of the MBS session within a service area.
Input, Required: MBS Session ID, Event ID.
Input, Optional: Event information, Area Session ID.
Output, Required: Result Indication.
9.1.3.10 Nmbsmf_MBSSession_StatusSubscribe service operation
Service operation name: Nmbsmf_MBSSession_StatusSubscribe
Description: This service operation is used by the NF service consumer (e.g. NEF, MBSF, AF) to subscribe notification about events related to the status of the MBS session, or for a location dependent MBS session, the part of the MBS session within a service area.
Input, Required: MBS Session ID, event ID(s), Notification Target Address.
Input, Optional: Area Session ID.
Output, Required: When the subscription is accepted: Subscription Correlation ID.
9.1.3.11 Nmbsmf_MBSSession_StatusUnsubscribe service operation
Service operation name: Nmbsmf_MBSSession_StatusUnsubscribe
Description: This service operation, is used by the NF service consumer (e.g. NEF, MBSF, AF) to unsubscribe to notification about events related to the status of the MBS session, or for a location dependent MBS session, the part of the MBS session within a service area.
Input, Required: Subscription Correlation ID.
Input, Optional: Area Session ID.
Output, Required: Result Indication.
9.2 PCF Services
9.2.1 General
The following table illustrates the PCF Services for MBS.
Table 9.2.1-1: NF services provided by PCF for MBS
|
Service Name |
Service Operations |
Operation Semantics |
Example Consumer (s) |
|
Npcf_MBSPolicyControl |
Create |
Request/Response |
MB-SMF |
|
Update |
Request/Response |
MB-SMF |
|
|
Delete |
Request/Response |
MB-SMF |
|
|
Npcf_MBSPolicy Authorization |
Create |
Request/Response |
AF, NEF, MBSF |
|
Update |
Request/Response |
AF, NEF, MBSF |
|
|
Delete |
Request/Response |
AF, NEF, MBSF |
9.2.2 Npcf_MBSPolicyControl service
9.2.2.1 General
Service description: NF Service Consumer, e.g. MB-SMF, can create and manage a MBS Policy Association in the PCF through which the NF Service Consumer receives policy information for the MBS Session.
As part of this service, the PCF may provide the NF Service Consumer, e.g. MB-SMF, with policy information for the MBS Session that may contain (the details are defined in clause 6.10):
– Policy information applicable for an entire MBS Session.
– PCC rule information.
– Policy Control Request Trigger information.
At MBS Session establishment the NF Service Consumer, e.g. MB-SMF, requests the creation of a corresponding MBS Policy Association with the PCF (Npcf_MBSPolicyControl_Create) and provides relevant parameters about the MBS Session to the PCF.
– When the PCF has created the "MBS Policy Association", the PCF may provide policy information as defined above.
When a Policy Control Request Trigger condition is met the NF Service Consumer, e.g. MB-SMF, requests the update (Npcf_MBSPolicyControl_Update) of the MBS Policy Association by providing information on the condition(s) that have been met. The PCF may provide updated policy information for the MBS session to the NF Service Consumer.
The PCF may at any time provide updated policy information for the MBS session (Npcf_MBSPolicyControl_UpdateNotify).
At MBS Session Release the NF Service Consumer, e.g. MB-SMF, requests the deletion of the corresponding MBS Policy Association.
9.2.2.2 Npcf_MBSPolicyControl_Create service operation
Service operation name: Npcf_MBSPolicyControl_Create
Description: The NF Service Consumer can request the creation of a MBS Policy Association and provide relevant parameters about the MBS Session to the PCF.
Inputs, Required: MBS Session ID.
Inputs, Optional: MBS Service Information (as defined in clause 6.14), DNN, S-NSSAI..
Outputs, Required: Success or Failure. In the case of Success, MBS Policy Association ID and Policy information for the MBS Session (as defined in clause 6.10).
Outputs, Optional: In the case of Failure, the Service Information that can be accepted by the PCF. In the case of Failure, indication that another PCF shall be contacted and an ID of that other PCF.
9.2.2.3 Void
9.2.2.4 Npcf_MBSPolicyControl_Delete service operation
Service operation name: Npcf_MBSPolicyControl_Delete
Description: The NF Service Consumer (i.e. MB-SMF) can request the deletion of the MBS Policy Association and of the associated resources.
Inputs, Required: MBS Policy Association ID.
Inputs, Optional: None.
Outputs, Required: Success or Failure.
Outputs, Optional: None.
9.2.2.5 Npcf_MBSPolicyControl_Update service operation
Service operation name: Npcf_MBSPolicyControl_Update
Description: The NF Service Consumer can request an update of the MBS Policy Association.
Inputs, Required: MBS Policy Association ID.
Inputs, Optional: MBS Service Information (as defined in clause 6.14), Information on the Policy Control Request Trigger condition that has been met.
Outputs, Required: Success or Failure.
Outputs, Optional: In the case of Failure, the Service Information that can be accepted by the PCF. In the case of Success, Policy information for the MBS Session (as defined in clause 6.10).
9.2.3 Npcf_MBSPolicyAuthorization Service
9.2.3.1 General
Service description: This service is to authorise an AF / NEF / MBSF request for an MBS service and to create policies as requested by the authorized AF for the MBS Service. This service also allows the NF consumer to subscribe/unsubscribe the notification of events.
9.2.3.2 Npcf_MBSPolicyAuthorization_Create service operation
Service operation name: Npcf_MBSPolicyAuthorization_Create
Description: Authorize the request, and optionally determines and installs MBS Policy Control Data according to the information provided by the NF Consumer.
Inputs, Required: MBS Session ID.
Inputs, Optional: DNN if available, S-NSSAI if available, MBS Service Information (as defined in clause 6.14).
Outputs, Required: Success (application session context) or Failure (reason for failure).
Outputs, Optional: In the case of Failure, the MBS Service Information that can be accepted by the PCF.
9.2.3.3 Npcf_MBSPolicyAuthorization_Update service operation
Service operation name: Npcf_MBSPolicyAuthorization_Update
Description: Provides updated information to the PCF.
Inputs, Required: Identification of the application session context.
Inputs, Optional: MBS Service Information (as defined in clause 6.14).
Outputs, Required: Success or Failure (reason for failure).
Outputs, Optional: In the case of Failure, the MBS Service Information that can be accepted by the PCF. In the case of Success, indication that the PCF has to be contacted.
Provides updated application level information and communicates with Npcf_MBSPolicyControl service to determine and install the policy according to the information provided by the NF Consumer. Updates an application context in the PCF.
9.2.3.4 Npcf_MBSPolicyAuthorization_Delete service operation
Service operation name: Npcf_MBSPolicyAuthorization_Delete
Description: Provides means for the NF Consumer to delete the context of application level session information.
Inputs, Required: Identification of the application session context.
Inputs, Optional: None.
Outputs, Required: Success or Failure.
Outputs, Optional: None.
9.3 AMF Services
9.3.1 General
The Namf_MT_EnableGroupReachability service operation is defined in TS 23.502 [6].
The following table illustrates the new AMF Service for broadcast communication.
Table 9.3.1-1: NF services provided by AMF
|
Service Name |
Service Operations |
Operation Semantics |
Example Consumer (s) |
|
Namf_MBSBroadcast |
ContextCreate |
Request/Response |
MB-SMF |
|
ContextUpdate |
Request/Response |
MB-SMF |
|
|
ContextRelease |
Request/Response |
MB-SMF |
|
|
ContextStatusNotify |
Subscribe/Notify |
MB-SMF |
|
|
Namf_MBSCommunication |
N2MessageTransfer |
Request/Response |
MB-SMF |
9.3.2 Namf_MBSBroadcast service
9.3.2.1 General
Service description: This service is used by the consumer for broadcast communication.
9.3.2.2 Namf_MBSBroadcast_ContextCreate service operation
Service operation name: Namf_MBSBroadcast_ContextCreate
Description: This service operation is used to create the broadcast session context towards the AMF.
Inputs, Required: MBS Session ID, Broadcast service area, N2 container (e.g. MBS Session ID, MBS QoS profile, Broadcast service area).
Inputs, Optional: Area Session ID, Optional parameters in the N2 container (MBS IP Multicast Tunnel Info, Area Session ID, MBS FSA ID(s)).
Outputs, Required: Result Indication.
Outputs, Optional: N2 container (NG-RAN MBS Tunnel Info).
9.3.2.3 Namf_MBSBroadcast_ContextUpdate service operation
Service operation name: Namf_MBSBroadcast_ContextUpdate
Description: This service operation is used to update the broadcast session context towards the AMF.
Inputs, Required: MBS Session ID.
Inputs, Optional: Broadcast service area, N2 container (MBS Session ID, Possible MBS QoS profile, Possible Broadcast service area, Possible Area Session ID, Possible MBS IP Multicast Tunnel Info, MBS FSA ID(s)).
Outputs, Required: Result Indication.
Outputs, Optional: N2 container (MBS Session ID, NG-RAN MBS Tunnel Info).
9.3.2.4 Namf_MBSBroadcast_ContextRelease service operation
Service operation name: Namf_MBSBroadcast_ContextRelease
Description: This service operation is used to release the broadcast session context towards the AMF.
Inputs, Required: MBS Session ID, N2 container (MBS Session ID).
Inputs, Optional: None.
Outputs, Required: Result Indication.
Outputs, Optional: None.
9.3.2.5 Namf_MBSBroadcast_ContextStatusNotify service operation
Service operation name: Namf_MBSBroadcast_ContextStatusNotify
Description: This service operation is used to notify its consumers about the status change of a broadcast session context.
Inputs, Required: MBS Session ID.
Inputs, Optional: Event ID (e.g. change of NG-RAN MBS Tunnel Info), N2 SM information.
Outputs, Required: Result Indication.
Outputs, Optional: None.
9.3.3 Namf_MBSCommunication Service
9.3.3.1 General
Service description: This service enables MBS multicast related N2 message transfer towards the NG-RAN via the AMF, during multicast session activation/deactivation/update/release.
9.3.3.2 Namf_MBSCommunication_N2MessageTransfer service operation
Service operation name: Namf_MBSCommunication_N2MessageTransfer
Description: This service operation is used by the NF Consumer to request the AMF to transfer the MBS related N2 message to the NG-RAN nodes serving the MBS multicast session.
Input, Required: MBS Session ID, N2 SM information.
Input, Optional: MBS Area Session ID.
Output, Required: Result Indication.
Output, Optional: Cause.
9.4 NEF Services
9.4.1 General
The following table illustrates the NEF Services for MBS.
Table 9.4.1-1: NF services provided by NEF
|
Service Name |
Service Operations |
Operation Semantics |
Example Consumer (s) |
|
Nnef_MBSTMGI |
Allocate |
Request/Response |
AF |
|
Deallocate |
Request/Response |
AF |
|
|
ExpiryNotify |
Subscribe/Notify |
AF |
|
|
Nnef_MBSSession |
Create |
Request/Response |
AF |
|
Update |
Request/Response |
AF |
|
|
Delete |
Request/Response |
AF |
|
|
StatusNotify |
Subscribe/Notify |
AF |
|
|
StatusSubscribe |
AF |
||
|
StatusUnsubscribe |
AF |
||
|
Nnef_MBSGroupMsg |
Delivery |
Request/Response |
AF |
|
Modify |
Request/Response |
AF |
|
|
StatusNotify |
Notify |
AF |
Editor’s note: The service operation and parameters are FFS.
Editor’s note: It requires further investigation on whether the service operation should align more with T8 interface (delivery & modify) or follows the SBI design principles (CRUD).
Editor’s note: It requires further investigation on whether StatusSubscribe and StatusUnsubscribe are needed or not.
9.4.2 Nnef_MBSTMGI service
9.4.2.1 General
Service description: NF Service Consumer can use this service to request the allocation of TMGIs and deallocate TMGIs previously allocated.
9.4.2.2 Nnef_MBSTMGI_Allocate service operation
Service operation name: Nnef_MBSTMGI_Allocate
Description: This service is used by the NF Service Consumer to request allocation of TMGI(s), or to refresh the expiry time for already allocated TMGI(s).
Inputs, Required: Number of TMGIs (may be zero if only a refresh of expiry time is requested).
Inputs, Optional: TMGI(s) to be refreshed, MBS service area.
Outputs, Required: TMGIs, Expiry Time, Success or not.
Outputs, Optional: NID.
9.4.2.3 Nnef_MBSTMGI_Deallocate service operation
Service operation name: Nnef_MBSTMGI_Deallocate
Description: This service is used by the NF Service Consumer to request deallocation the TMGI(s).
Inputs, Required: TMGI(s).
Inputs, Optional: None.
Outputs, Required: Success or not.
Outputs, Optional: None.
9.4.2.4 Nnef_MBSTMGI_ExpiryNotify service operation
Service operation name: Nnef_MBSTMGI_ExpiryNotify
Description: This service is used by the NEF to notify the NF service consumer of the timer expiry for TMGI(s).
Inputs, Required: TMGI(s).
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
9.4.3 Nnef_MBSSession Service
9.4.3.1 General
Service description: This service operates on the multicast and broadcast MBS sessions. The following are the key functionalities of this NF service:
– Create/Update Delete for both multicast and broadcast MBS session, or for a location dependent MBS session, the part of the MBS session within a service area;
– Provide a Notification about subscribed events. The following events are supported:
– MBS session release due to TMGI expiry.
– Broadcast delivery status.
9.4.3.2 Nnef_MBSSession_Create service operation
Service operation name: Nnef_MBSSession_Create
Description: Create a new multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area. Optionally implicitly subscribe to notifications for this MBS session.
Input, Required: MBS Session ID (SSM or TMGI) or TMGI allocation request, MBS Service Type (broadcast or multicast).
Input, Optional: MBS service area (mandatory for broadcast. Can be Cell ID list and/or TAI list, or geographical area information, or civic address information), MBS start time, MBS stop time, MBS Service Information (as defined in clause 6.14), Input Transport Address Request, session state (Active/Inactive), for subscription to notifications notification target address. For a multicast session, indication that any UE may join the multicast session. Request for location dependent MBS session. For a broadcast session, MBS FSA ID(s).
Output, Required: Result Indication.
Output, Optional: TMGI, NID, Cause, MB-UPF tunnel info, MBS FSA ID(s), Area Session ID.
9.4.3.3 Nnef_MBSSession_Update service operation
Service operation name: Nnef_MBSSession_Update
Description: This service is used by the NF service consumer to update the established multicast session or broadcast session, or for a location dependent MBS session, the part of the MBS session within a service area, e.g. QoS update. For multicast MBS Session, this service is also used to activate or deactivate the MBS Session.
Input, Required: MBS Session ID.
Input, Optional: MBS Service Information (as defined in clause 6.14), MBS service area, session state (Active/Inactive), Area Session ID. For a broadcast session, MBS FSA ID(s).
Output, Required: Result Indication.
Output, Optional: Cause, MBS FSA ID(s).
9.4.3.4 Nnef_MBSSession_Delete service operation
Service operation name: Nnef_MBSSession_Delete
Description: This service is used to delete the multicast or broadcast MBS session, or for a location dependent MBS session, the part of the MBS session within a service area.
Input, Required: MBS Session ID.
Input, Optional: Area Session ID.
Output, Required: Result Indication.
Output, Optional: Cause.
9.4.3.5 Nnef_MBSSession_StatusNotify service operation
Service operation name: Nnef_MBSSession_StatusNotify
Description: This service is used by the MB-SMF to notify the NF service consumers of the subscribed events related to an MBS session, or for a location dependent MBS session, related to the part of the MBS session within a service area.
Inputs, Required: Status Information, MBS Session ID.
Inputs, Optional: Area Session ID.
Outputs, Required: None.
Outputs, Optional: None.
9.4.3.6 Nnef_MBSSession_StatusSubscribe service operation
Service operation name: Nnef_MBSSession_StatusSubscribe
Description: This service is used by the NF service consumers to subscribe to the MBS Session status information of an MBS session, or for a location dependent MBS session, of the part of the MBS session within a service area.
Inputs, Required: Status Information, MBS Session ID.
Inputs, Optional: Area Session ID.
Outputs, Required: None.
Outputs, Optional: None.
9.4.3.7 Nnef_MBSSession_StatusUnsubscribe service operation
Service operation name: Nnef_MBSSession_StatusUnsubscribe
Description: This service is used by the NF service consumers to unsubscribe to the MBS Session status information of an MBS session or for a location dependent MBS session, of the part of the MBS session within a service area.
Inputs, Required: Status Information, MBS Session ID.
Inputs, Optional: Area Session ID.
Outputs, Required: None.
Outputs, Optional: None.
9.4.4 Nnef_MBSGroupMsg Service
Editor’s note: The service operation and parameters are FFS.
Editor’s note: It requires further investigation on whether the service operation should align more with T8 interface (delivery & modify) or follows the SBI design principles (CRUD).
Editor’s note: It is FFS whether TLTRI (T8 Long Term Transaction Reference ID) should be kept or use Group Message Correlation ID instead.
9.4.4.1 General
Service description: NF Service Consumer can use this service to request group message delivery or to modify or to cancel previously submitted group message delivery.
9.4.4.2 Nnef_MBSGroupMsg_Delivery service operation
Service operation name: Nnef_ MBSGroupMsg_Delivery
Description: This service is used by the NF Service Consumer to request group message delivery.
Inputs, Required: Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time, External Group Identifier.
Inputs, Optional: None.
Outputs, Required: Group Message Correlation ID, Delivery Status
Outputs, Optional: Cause, service area without MBS capability.
9.4.4.3 Nnef_MBSGroupMsg_Modify service operation
Service operation name: Nnef_MBSGroupMsg_Modify
Description: This service is used by the NF Service Consumer to recall or replace group message delivery.
Inputs, Required: Group Message Correlation ID, Request Action (Modify/Cancel), External Group Identifier.
Inputs, Optional: Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time.
Outputs, Required: Acceptance Status
Outputs, Optional: Cause, service area without MBS capability.
9.4.4.4 Nnef_MBSGroupMsg_StatusNotify service operation
Service operation name: Nnef_ MBSGroupMsg_StatusNotify
Description: This service is used by the NEF to notify the NF service consumers of the status of a group message delivery request.
Inputs, Required: Status Information, Group Message Correlation ID.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
9.5 MBSF Services
MBSF services are defined in TS 26.502 [18].
Annex A (normative):
Configuration options at Service and/or Application for MBS
Figure A-1 provides the reference architecture with all configuration variants for Application Function interaction with 5G Core Network, usage of NEF or MBSF in the control plane, and usage of N6, MB2-U or xMB-U in user plane.
Figure A-1: Configuration options at Service and/or Application
The following characteristics describe each of the Configuration options:
– Configuration Option 1: No MBSF:
– This configuration is used for Transport Only Mode (i.e. MBS provides only transport of MBS data in a transparent manner without modifying the data), when the Multicast service or Broadcast service does not require service layer interworking with LTE MBMS.
– The control plane entry point for the Application Function outside the trusted domain towards 5GC to request establishment of an MBS session is the NEF via N33.
– An application function within the trusted domain can directly use the N30, N5 and N29mb service based interfaces. In this case some NEF functionality related to PCF and MB-SMF interaction is incorporated in AF.
NOTE 1: Application function within the trusted domain selects MB-SMF based on e.g. its local configuration, or query NRF based on location, etc.
– The user plane entry point for the Application Function towards 5GC is the MB-UPF via N6mb.
– Configuration Option 2: MBSF, N33 towards AF:
– This configuration may be used for Service Mode (i.e. MBS provides service layer capability, allows to modify the data), or when service layer interworking with LTE MBMS is required.
– When interworking with LTE MBMS for Transport Only Mode services, N33/Nmb5 and Nmb8 provide the same functionalities as N33/N13mb and N6mb respectively.
– The control plane entry point from the Application Function to request establishment of an MBS session is the NEF via N33.
– The user plane entry point for the Application Function towards 5GC is the MBSTF via MB2-U, xMB-U or Nmb8.
– The NEF and MBSF may be collocated.
– If the MBSF is not collocated with the NEF, the reference point between the NEF and MBSF is Nmb5.
– An application function within the trusted domain may be collocated with MBSF.
– Configuration Option 3: MBSF, MB2-C/xMB-C/Nmb10 towards AF:
– This configuration may be used for Service Mode (xMB-C or Nmb10), or when interworking with LTE MBMS is required (MB2-C, xMB-C or Nmb10).
– When interworking with LTE MBMS for Transport Only Mode services, Nmb10 and Nmb8 provide the same functionalities as Nmb13 and N6mb respectively.
– The control plane entry point from the Application Function to request establishment of an MBS session is the MBSF via MB2-C, xMB-C or Nmb10.
– The user plane entry point for the Application Function is the MBSTF via MB2-U, xMB-U or Nmb8.
For service mode, MBSF shall be used, i.e. either Configuration 2 or Configuration 3 shall be used. In this case, the MBSF instructs the MBSTF to modify the MBS data (e.g. including the FEC or MBS data transcoding).
For Configuration Option 2 and Option 3, when interworking with LTE MBMS is used, LTE MBMS and MBS use the same mode (i.e. both use Transport Only Mode or Service Mode).
For Transport Only mode:
– If interworking with LTE MBMS at 5GC is required for the service, MBSF and MBSTF shall be used, i.e. either Configuration 2 or Configuration 3 shall be used.
– If interworking with LTE MBMS is not required for the service, MBSF and MBSTF are optional.
NOTE 2: Interworking providing by AF is out of scope of this specification.
MBSTF shall be used when MBSF is used.
Any particular deployment may support any combination of these configurations.
Annex B (informative):
Service levels for multicast communication service
The following service levels for the multicast communication service are defined:
NOTE 1: Transport Only mode and Full-Service mode of operation as defined in TS 23.246 [8] differ from the service levels defined here.
– Basic service level. The following requirements are defined:
– Media transported transparently through the 5GS.
– Interactions between UE and network for receiving the multicast communication service.
– Packet distribution from the 5GS ingress to NG-RAN node(s).
– Data delivery from NG-RAN node(s) to the UE.
– Enhanced service level, with additional requirements on top of basic service level. Different requirements out of the set below may be necessary to address each use case:
– Local MBS service.
– User authentication and authorization for Multicast MBS session.
NOTE 2: User authentication and authorization is an optional feature in 5GS.
– Explicit configuration of Multicast MBS session by AF, including group member information.
– Enhanced QoS support. E.g. to differentiate MBS data flow with different QoS over 5GS.
Annex C (normative):
Interworking at reference points MB2 and xMB
To allow the MBS System to interwork with a GCS AS supporting the MB2 interfaces defined in TS 23.468 [10]:
– In addition to supporting the Nmbsf service-based API at Nmb10 (as defined in clause 5.1) the MBSF shall support interfaces MB2 C.
– In addition to supporting content ingest interfaces defined in TS 26.502 [18] at Nmb8 (as defined in clause 5.1) the MBSTF shall support interfaces MB2 U.
To allow the MBS System to interwork with a Content Provider supporting the xMB interfaces defined in TS 26.348 [11]:
– In addition to supporting the Nmbsf service-based API at Nmb10 (as defined in clause 5.1) the MBSF shall support interface xMB C.
– In addition to supporting content ingest interfaces defined in TS 26.502 [18] at Nmb8 (as defined in clause 5.1) the MBSTF shall support interface xMB U.
Figure C-1: Interworking with GCS AS supporting MB2 interfaces and with Content Provider supporting xMB interfaces
Annex D (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2021-03 |
SA2#143E |
S2-2101423 |
– |
– |
– |
TS skeleton approved at S2#143E |
0.0.0 |
|
2021-06 |
SA#92E |
SP-210368 |
– |
– |
– |
MCC editorial update for presentation to TSG SA#92E for information |
1.0.0 |
|
2021-09 |
SA#93E |
SP-210941 |
– |
– |
– |
MCC editorial update for presentation to TSG SA#93E for approval |
2.0.0 |
|
2021-09 |
SA#93E |
– |
– |
– |
– |
MCC editorial update for publication after TSG SA#93E approval |
17.0.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0001 |
– |
F |
Clarification on interworking with EPS |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0002 |
3 |
F |
MBS Session Management vs Configuration |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0006 |
1 |
F |
Multicast MBS Session: resolving ENs and cleanup |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0008 |
2 |
F |
Interworking with MBMS over E-UTRAN for broadcast service |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0010 |
2 |
F |
Local MBS service and Location dependent MBS service |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0012 |
1 |
F |
Multicast session join and session establishment |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0014 |
3 |
F |
Multicast session leave and session release |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0015 |
3 |
F |
Clarifications on functional entities |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0019 |
2 |
F |
NRF service operation for broadcast service |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0021 |
4 |
F |
Clarification of the local MBS service |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0022 |
4 |
F |
Leftover issue for MBS session activation and deactivation |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0023 |
1 |
F |
Lossless handover for MBS session |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0025 |
1 |
F |
When UE joining UE authorization for the multicast MBS session |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0026 |
3 |
F |
Miscellaneous corrections |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0027 |
1 |
F |
Clarification on User Plane Management |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0029 |
4 |
F |
Updates on cases that SMF rejects UE join request |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0031 |
1 |
D |
Editorial modification on terms, abbreviations |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0032 |
1 |
F |
Modification on session join and shared tunnel establishment related procedures |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0033 |
1 |
F |
Modification on session leave and shared tunnel release related procedures |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0035 |
2 |
F |
Modification on handover procedures |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211285 |
0038 |
3 |
F |
Replacement reference architecture figures |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0041 |
1 |
F |
Update to the Multicast session join and session establishment, and removing procedure. |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0043 |
1 |
F |
Clarification on the MBS service actication/deactivation/update and related service operation |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0044 |
1 |
F |
modification on the MBS Broadcast session management |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0045 |
1 |
F |
Clarification on the Qos handling and Policy control in the clause 6 |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0050 |
2 |
F |
PCC related MBS corrections |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0051 |
1 |
F |
Corrections to MBS Broadcast Session Establishment |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0054 |
– |
F |
Clarification on local multicast |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0055 |
1 |
F |
Minimize multicast service interruption caused by unintended PDU session release |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0057 |
1 |
F |
Multicast MBS service for SNPN |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0060 |
1 |
F |
Updates to NF services for MBS |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0062 |
1 |
F |
Modification on activation procedure |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0064 |
1 |
F |
Clarification on NF services |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0066 |
1 |
F |
Clarification on Annex A for transport mode |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0067 |
1 |
F |
Fixing the EN and Nmbsmf_MBSSession service operation parameters. |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0068 |
1 |
F |
clarification on PDR and FAR in A-UPF for MBS data traffic in individual delivery |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0073 |
1 |
F |
Clarification on the input of PCF/NEF/MB-SMF service operation |
17.1.0 |
|
2021-12 |
SA#94E |
SP-211286 |
0074 |
1 |
F |
Broadcast Frequency selection Identifier |
17.1.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0075 |
1 |
F |
Clarification on MBS Session Update procedures |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0077 |
1 |
D |
Adding a heading of clause 5 |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0078 |
1 |
F |
Corrections for Location dependent MBS session |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0079 |
– |
F |
Removing UE from Multicast MBS Session |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0081 |
1 |
F |
Resolving ENs, cleanup and corrections |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0083 |
1 |
F |
Corrections to MBS procedures for broadcast Session |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0085 |
1 |
F |
Paging strategy handling for multicast MBS session |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0086 |
1 |
F |
Restoration of multicast MBS session following AN release |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0089 |
1 |
F |
Miscellaneous corrections on TS 23.247 |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0092 |
1 |
F |
MBS Frequency Selection Area Identifier |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0093 |
1 |
F |
Indication whether MBS session is active |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0095 |
1 |
F |
Resolving the PCC related EN and issue |
17.2.0 |
|
2022-03 |
SA#95E |
SP-220052 |
0096 |
1 |
F |
Clarification on the MBS session Create and update procedure. |
17.2.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0090 |
5 |
F |
Clarification of MBS data forwarding |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0101 |
1 |
F |
Correction on the mobility procedures for MBS |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0102 |
– |
F |
Broadcast MBS Session Release Require Procedure |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0103 |
1 |
F |
MBS Service Area for MB-SMF selection in TMGI Allocation |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0104 |
1 |
F |
Alignment with RAN3 and other corrections |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0105 |
1 |
F |
Correction to MBS Session Context and MBS Session Activation procedure |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0106 |
1 |
F |
Resolve the residual ENs and Clean-up in TS 23.247 |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0107 |
1 |
F |
Mega CR to clean up |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0110 |
– |
F |
Clarification on MBS security function |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0111 |
1 |
F |
Usage of NAS message for UE joining procedure |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0112 |
– |
F |
Clarification on MBS session activation procedure |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0113 |
– |
F |
Clarification on Activation procedure |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0115 |
1 |
F |
Clarification on local dependent MBS session |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0116 |
1 |
F |
Miscellaneous corrections |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0117 |
– |
F |
Clarifications on traffic usage reporting and charging |
17.3.0 |
|
2022-06 |
SA#96 |
SP-220395 |
0119 |
1 |
F |
Tunnel between MBSTF and MB-UPF |
17.3.0 |
|
2022-09 |
SA#97E |
SP-220775 |
0109 |
4 |
F |
Update of PCC procedure for 5MBS |
17.4.0 |
|
2022-09 |
SA#97E |
SP-220775 |
0122 |
– |
F |
MBS Session Status and broadcast MBS Session |
17.4.0 |
|
2022-09 |
SA#97E |
SP-220775 |
0124 |
– |
F |
Clarification on local multicast |
17.4.0 |
|
2022-09 |
SA#97E |
SP-220775 |
0126 |
1 |
F |
Correction to MB-SMF update in NRF |
17.4.0 |
|
2022-09 |
SA#97E |
SP-220775 |
0127 |
1 |
F |
Correction and editorial improvement |
17.4.0 |
|
2022-09 |
SA#97E |
SP-220775 |
0130 |
1 |
F |
Clarification on the mobility in RRC inactive |
17.4.0 |
|
2022-09 |
SA#97E |
SP-220775 |
0132 |
1 |
F |
Removing the EN on the HO |
17.4.0 |
|
2022-12 |
SA#98E |
SP-221068 |
0129 |
2 |
F |
Clarification on the traffic handling in MBSTF for interworking |
17.5.0 |
|
2022-12 |
SA#98E |
SP-221068 |
0134 |
1 |
F |
Handling of tunnel between UPF and MB_UPF for Multicast MBS session Deactivation and Reactivation |
17.5.0 |
|
2022-12 |
SA#98E |
SP-221068 |
0135 |
– |
F |
Missing NID in output parameters to AF for SNPN |
17.5.0 |
|
2022-12 |
SA#98E |
SP-221068 |
0137 |
1 |
F |
Clean-up of PCC procedures for 5MBS |
17.5.0 |
|
2022-12 |
SA#98E |
SP-221068 |
0139 |
5 |
F |
CR on MTK or MSK processing |
17.5.0 |
|
2022-12 |
SA#98E |
SP-221068 |
0141 |
1 |
F |
Clarification on the shared delivery tunnel management for common gNB UP case |
17.5.0 |
|
2022-12 |
SA#98E |
SP-221095 |
0143 |
1 |
B |
Group Message Delivery |
18.0.0 |