hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.1.2 Nmbsmf_TMGI service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.1.2.1 General
|
Service description: NF Service Consumer can use this service to request the allocation of TMGIs and release allocated TMGIs.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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) for which the expiry time is to be extended).
Outputs, Required: TMGI(s), Expiry Time of the TMGI(s), Result Indication.
Outputs, Optional: NID.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.1.3 Nmbsmf_MBSSession service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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 multicast MBS 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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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, Area Session Policy ID, MBS Service Information (as defined in clause 6.14), Input Transport Address Request, MBS start time, MBS termination time, NR RedCap UE Information (as defined in clause 6.19). 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, Associated Session ID for resource sharing across broadcast MBS Sessions during network sharing.
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, Information of area reduction.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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, NR RedCap UE Information (as defined in clause 6.19). For multicast, session state (Active/Inactive), updated multicast session security context.
Output, Required: Result Indication.
Output, Optional: MBS FSA ID(s), Information of area reduction.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.2 PCF Services
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.2.2 Npcf_MBSPolicyControl service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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 by using 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 of the MBS Policy Association by providing information on the condition(s) that have been met using Npcf_MBSPolicyControl_Update. The PCF may provide updated policy information for the MBS session to the NF Service Consumer.
At MBS Session Release the NF Service Consumer, e.g. MB-SMF, requests the deletion of the corresponding MBS Policy Association.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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), Area Session Policy ID, 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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.2.2.3 Void
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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).
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.2.3 Npcf_MBSPolicyAuthorization Service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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), Request for location dependent MBS session.
Outputs, Required: Success (application session context) or Failure (reason for failure).
Outputs, Optional: Area Session Policy ID (for location dependent session), in the case of Failure, the MBS Service Information that can be accepted by the PCF.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.3 AMF Services
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.3.2 Namf_MBSBroadcast service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.3.2.1 General
|
Service description: This service is used by the consumer for broadcast communication.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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), Notification Endpoint.
Inputs, Optional: Area Session ID, Optional parameters in the N2 container (MBS IP Multicast Tunnel Info, Area Session ID, MBS FSA ID(s), Associated Session ID for resource sharing across broadcast MBS Sessions during network sharing).
Outputs, Required: Result Indication.
Outputs, Optional: N2 container (MBS Session ID, Area Session ID, NG-RAN MBS Tunnel Info).
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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)), Notification Endpoint.
Outputs, Required: Result Indication.
Outputs, Optional: N2 container (MBS Session ID, Area Session ID, NG-RAN MBS Tunnel Info).
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.3.3 Namf_MBSCommunication Service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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 multicast MBS session.
Input, Required: MBS Session ID, N2 SM information.
Input, Optional: MBS Area Session ID.
Output, Required: Result Indication.
Output, Optional: Cause.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.4 NEF Services
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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_MBSGroupMsgDelivery
Create
Request/Response
AF
Update
Request/Response
AF
Delete
Request/Response
AF
StatusNotify
Subscribe/Notify
AF
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.4.2 Nnef_MBSTMGI service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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) for which the expiry time is to be extended, MBS service area.
Outputs, Required: TMGIs, Expiry Time, Result Indication.
Outputs, Optional: NID.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.4.3 Nnef_MBSSession Service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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, NR RedCap UE Information (as defined in clause 6.19). 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), Associated Session ID for resource sharing across broadcast MBS Sessions during network sharing.
Output, Required: Result Indication.
Output, Optional: TMGI, NID, Cause, MB-UPF tunnel info, MBS FSA ID(s), Area Session ID, Information of area reduction.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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), NR RedCap UE Information (as defined in clause 6.19).
Output, Required: Result Indication.
Output, Optional: MBS FSA ID(s), Information of area reduction.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.4.4 Nnef_MBSGroupMsgDelivery Service
| |
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.4.4.2 Nnef_MBSGroupMsgDelivery_Create service operation
|
Service operation name: Nnef_MBSGroupMsgDelivery_Create
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, Notification Endpoint.
Inputs, Optional: Target UE Classes (as defined in TS 26.502 [18]).
Outputs, Required: Group Message Correlation ID, Delivery Status, service announcement information.
Outputs, Optional: Cause, service area without MBS capability.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.4.4.3 Nnef_MBSGroupMsgDelivery_Update service operation
|
Service operation name: Nnef_MBSGroupMsgDelivery_Update
Description: This service is used by the NF Service Consumer to replace group message delivery.
Inputs, Required: Group Message Correlation ID.
Inputs, Optional: Group Message Payload, MBS service area, Group Message Delivery Start Time, Stop Time, Notification Endpoint, Target UE Classes (as defined in TS 26.502 [18]).
Outputs, Required: Acceptance Status
Outputs, Optional: Cause, service area without MBS capability.
9.4.4.3a Nnef_MBSGroupMsgDelivery_Delete service operation
Service operation name: Nnef_MBSGroupMsgDelivery_Delete
Description: This service is used by the NF Service Consumer to recall (or cancel) group message delivery.
Inputs, Required: Group Message Correlation ID.
Inputs, Optional: None.
Outputs, Required: Acceptance Status.
Outputs, Optional: Cause.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
9.4.4.4 Nnef_MBSGroupMsgDelivery_StatusNotify service operation
|
Service operation name: Nnef_MBSGroupMsgDelivery_StatusNotify
Description: This service is used by the NEF to notify the NF service consumers of the status of a group message delivery.
NOTE: This notification corresponds to an implicit subscription.
Inputs, Required: Status Information, Notification Endpoint.
Inputs, Optional: None.
Outputs, Required: None.
Outputs, Optional: None.
|
1806a77330b2a3aa2bdd3771c88c0e91
|
23.247
|
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, or when the functionalities of MBS security is used (see clause 6.13). - 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), or when the functionalities of MBS security is used (see clause 6.13). - 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 activation/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 2023-03 SA#99 SP-230051 0146 3 B Update the scope of TS 23.247 18.1.0 2023-03 SA#99 SP-230051 0149 8 B Support of MBS multicast reception by UEs in RRC_INACTIVE state 18.1.0 2023-03 SA#99 SP-230051 0150 1 B Coexistence with existing power saving mechanisms for capability-limited devices 18.1.0 2023-03 SA#99 SP-230037 0152 2 A AMF knowing MBS support status of NG-RAN node (s) for Multicast Activation 18.1.0 2023-03 SA#99 SP-230037 0154 2 A Correction to description of Fig. 7.1.1.3-1 18.1.0 2023-03 SA#99 SP-230037 0156 1 A Correction to location dependent service for broadcast 18.1.0 2023-03 SA#99 SP-230037 0158 1 A Correction to Broadcast MBS Session handling 18.1.0 2023-03 SA#99 SP-230051 0159 7 B Support RRC_INACTIVE UE receiving multicast MBS data 18.1.0 2023-03 SA#99 SP-230051 0160 6 B Introducing functionality of resource efficiency in MOCN Network Sharing 18.1.0 2023-03 SA#99 SP-230051 0161 - C Resolve ENs on Group Message Delivery and corrections 18.1.0 2023-03 SA#99 SP-230051 0162 1 B Support MBS for UEs using power saving functions 18.1.0 2023-03 SA#99 SP-230051 0163 1 B On the Update of Group Message Delivery 18.1.0 2023-03 SA#99 SP-230051 0164 6 B On Clarifying the Scenario Considering the Power Saving Mechanism 18.1.0 2023-03 SA#99 SP-230051 0165 3 B On resource efficiency for MBS reception in RAN sharing scenario 18.1.0 2023-03 SA#99 SP-230037 0166 1 F Align the MB-SMF discovery enhancement in clause 7.1.2 18.1.0 2023-03 SA#99 SP-230051 0168 6 B Support of RRC Inactive state reception for MBS session 18.1.0 2023-03 SA#99 SP-230037 0170 3 A Clarification shared NG-U Termination among gNBs for Broadcast MBS session 18.1.0 2023-03 SA#99 SP-230051 0171 5 B KI#1, adding RRC inactive network functionality of NF description 18.1.0 2023-03 SA#99 SP-230051 0176 9 B KI#2, adding MOCN network sharing for the same content 18.1.0 2023-03 SA#99 SP-230051 0179 8 B Mobility procedures for UEs receiving multicast MBS session data in RRC Inactive state 18.1.0 2023-03 SA#99 SP-230037 0187 2 A Update on the security in accordance with SA3 LS 18.1.0 2023-06 SA#100 SP-230453 0205 1 A Alignment with RAN on Xn/N2 based handover for inactive MBS session 18.2.0 2023-06 SA#100 SP-230454 0207 1 F KI#1 Correction of mobility procedures for delivery of multicast MBS session data to RRC_INACTIVE UE 18.2.0 2023-06 SA#100 SP-230454 0210 1 C KI#2 Resolve EN in broadcast procedures for resource sharing in network sharing 18.2.0 2023-06 SA#100 SP-230454 0213 1 F Update functional entity clauses for group message delivery and power saving functions 18.2.0 2023-06 SA#100 SP-230454 0214 1 F Update the abbreviation for Release 18 18.2.0 2023-06 SA#100 SP-230454 0220 1 B Update group message delivery procedure 18.2.0 2023-06 SA#100 SP-230453 0224 1 A Connection resume with local multicast session 18.2.0 2023-06 SA#100 SP-230453 0225 1 A Connection resume with location dependent multicast session 18.2.0 2023-06 SA#100 SP-230454 0226 1 B Mobility Registration Update and Service Request procedures for local multicast service 18.2.0 2023-06 SA#100 SP-230454 0227 1 B Mobility Registration Update and Service Request procedures for location dependent multicast service 18.2.0 2023-06 SA#100 SP-230453 0230 1 A Clarification on the RRC resume failure for inactive MBS session 18.2.0 2023-06 SA#100 SP-230454 0231 1 B Resolving the EN on the MOCN enhancement for the location dependent MBS session 18.2.0 2023-06 SA#100 SP-230454 0232 1 F Resolving the EN on TMGI index and TMGI update for the configuration mechanism in the MOCN enhancement 18.2.0 2023-06 SA#100 SP-230454 0237 1 D Clarification of applications for Group Message Delivery 18.2.0 2023-06 SA#100 SP-230453 0239 1 A Handover Procedure correction 18.2.0 2023-06 SA#100 SP-230454 0240 1 F Open issue related to mobility procedures of RRC Inactivate state UE 18.2.0 2023-06 SA#100 SP-230453 0246 1 A Corrections for unicast tunnel establishment for MBS broadcast 18.2.0 2023-06 SA#100 SP-230454 0252 2 F Enabling simultaneous join for high number of UEs that support multicast RRC inactive reception 18.2.0 2023-06 SA#100 SP-230454 0253 1 F Mobility procedures for RRC inactive UEs 18.2.0 2023-06 SA#100 SP-230454 0258 1 B Update of MBS service announcement for capability-limited devices 18.2.0 2023-06 SA#100 SP-230454 0259 1 B MBS session activation for UEs using power saving functions 18.2.0 2023-06 SA#100 SP-230454 0260 1 F Resolving open issues for Multicast MBS procedures for UEs using power saving functions 18.2.0 2023-06 SA#100 SP-230454 0269 2 F Clarification on the NEF role and interface for the group message data delivery 18.2.0 2023-09 SA#101 SP-230834 0262 5 A Corrections related to indicating failure of establishing MBS broadcast transmission resources 18.3.0 2023-09 SA#101 SP-230843 0279 1 F Corrections for support of MBS data reception for UEs using power saving functions 18.3.0 2023-09 SA#101 SP-230843 0280 3 F Group Paging for Multicast MBS session data reception in RRC_INACTIVE state 18.3.0 2023-09 SA#101 SP-230834 0284 1 A Multicast over N6mb not applicable for location dependent MBS session 18.3.0 2023-09 SA#101 SP-230843 0285 1 F Alignment with stage 3 on Parameter Provisioning of MBS Assistance Information 18.3.0 2023-09 SA#101 SP-230843 0286 2 F Converting the requirement of AF handling service announcement to a NOTE 18.3.0 2023-09 SA#101 SP-230834 0288 2 A On the step number correction of 5MBS 18.3.0 2023-09 SA#101 SP-230834 0292 - A Correcting the figure and term 18.3.0 2023-09 SA#101 SP-230843 0297 1 F Resolving the EN on the RRC inactive assistant information 18.3.0 2023-09 SA#101 SP-230843 0300 2 F RRC INACTIVE UE Mobility within the same RNA 18.3.0 2023-09 SA#101 SP-230843 0301 1 F Clarification on the Resource sharing across broadcast MBS Sessions in MOCN 18.3.0 2023-09 SA#101 SP-230843 0303 1 F Editorial corrections 18.3.0 2023-12 SA#102 SP-231240 0201 4 A Correction to PCC procedures for location dependent MBS service 18.4.0 2023-12 SA#102 SP-231240 0276 4 A Handling of unsupported MBS service area 18.4.0 2023-12 SA#102 SP-231251 0278 3 F Alignment with RAN on transfer of assistance information during handover. 18.4.0 2023-12 SA#102 SP-231248 0307 - F Update UE pre-configuration 18.4.0 2023-12 SA#102 SP-231251 0316 1 F Correction on the references 18.4.0 2023-12 SA#102 SP-231251 0317 1 F Correction to the GroupMessage service operation 18.4.0 2023-12 SA#102 SP-231240 0319 1 A MBS Session deactivation and Mission Critical services 18.4.0 2023-12 SA#102 SP-231240 0321 2 A Correction to notification target address for context status notify of broadcast MBS 18.4.0 2023-12 SA#102 SP-231251 0322 3 F Pending MBS Session Release request at 5GS to EPS mobility 18.4.0 2023-12 SA#102 SP-231251 0323 3 F Resource sharing across broadcast MBS Sessions during network sharing 18.4.0 2023-12 SA#102 SP-231251 0324 - F Context Status Notification during transport change for resource sharing 18.4.0 2023-12 SA#102 SP-231251 0326 2 F Correction on shared N3mb tunnels towards NG-RAN in network sharing scenarios 18.4.0 2023-12 SA#102 SP-231240 0330 1 A Flow description within MBS Service Information if MBS data are transported in IP tunnel toward MB-UPF 18.4.0 2023-12 SA#102 SP-231240 0332 1 A Location Dependent MBS broadcast session with multiple MB-SMFs 18.4.0 2023-12 SA#102 SP-231251 0336 - F Mobility of UE in RRC_INACTIVE state receiving MBS data within RNA 18.4.0 2023-12 SA#102 SP-231251 0340 3 F Clarification on MBS session data reception in RRC_INACTIVE state 18.4.0 2023-12 SA#102 SP-231248 0343 1 F Correction for Multicast session leave procedure 18.4.0 2024-03 SA#103 SP-240092 0341 8 F Support for RedCap UEs in MBS Broadcast 18.5.0 2024-03 SA#103 SP-240092 0349 1 F On the general correction in TS 23.247 18.5.0 2024-03 SA#103 SP-240080 0350 3 A Correction on the AMF service operation for 5MBS 18.5.0 2024-03 SA#103 SP-240092 0352 1 F Clarification on the Multicast MBS procedures for UEs using power saving functions 18.5.0 2024-03 SA#103 SP-240080 0354 1 A MB-SMF Service Area Definition 18.5.0 2024-03 SA#103 SP-240464 0356 1 F Clarification on 5MBS charging 18.5.0 2024-06 SA#104 SP-240602 0358 2 F QMC Support for MBS Multicast and Broadcast 18.6.0 2024-06 SA#104 SP-240590 0359 2 F Providing MBS assistance information from SMF towards NG-RAN node during Xn handover 18.6.0 2024-06 SA#104 SP-240590 0362 - F correction on the reference and duplicate wording 18.6.0 2024-06 SA#104 SP-240590 0363 4 F FSA ID used for MBS session involving RedCap and non-RedCap UE 18.6.0 2024-06 SA#104 SP-240590 0368 1 D Cleanup CR for TS 23.247 18.6.0 2024-06 SA#104 SP-240590 0369 2 F Transport change for resource sharing across broadcast MBS Sessions & network sharing 18.6.0 2024-06 SA#104 SP-240590 0370 1 F Clarification on NR RedCap UEs Information and Group message delivery 18.6.0 2024-09 SA#105 SP-241238 0366 3 A Handling when MBS service area across multiple MB-SMFs 18.7.0 2024-09 SA#105 SP-241257 0371 1 F MBS Charging Support 18.7.0 2024-12 SA#106 SP-241484 0376 1 F Adding reference of MBS restoration procedures 19.0.0 2025-03 SA#107 SP-250037 0372 5 B MBS broadcast support for NTN 19.1.0 2025-03 SA#107 SP-250029 0380 - A The NEF/MBSF rejects the MBS session creation when handling MBS session creation request 19.1.0 2025-03 SA#107 SP-250037 0383 2 F Clarification on the Cell ID in MBS Service Area 19.1.0 2025-03 SA#107 SP-250033 0385 1 A Clarify the support of broadcast reception for eRedCap UEs 19.1.0
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
1 Scope
|
The present document specifies the functional architecture, procedures and information flows for UAS application enabler layer. This specification includes the capabilities of the application layer support for UAS that are necessary to ensure efficient use and deployment of UAS over 3GPP systems. The UAS application enabler capabilities applies to both EPS and 5GS.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP; Stage 1".
[3] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[4] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification, and tracking; Stage 2".
[5] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[6] 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage 2".
[7] 3GPP TS 23.558: "Architecture for enabling Edge Applications"
[8] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[9] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[10] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[11] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".
[12] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[13] 3GPP TS 23.502: "Procedures for the 5G System (5GS)".
[14] 3GPP TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".
[15] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services”.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
3 Definitions of terms and abbreviations
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
3.1 Terms
|
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
DAA application policy: The configuration provided to the UAS application specific client by a UAS application specific server for handling of detect and avoid.
DAA assist capability: The functionality for the UAE layer to assist the UAV application specific layer with handling of detect and avoid during flight.
LDGS capability: A UAE client with LDGS capability offers the ground based DAA support for the UAVs in the monitoring range of the LDGS. The Local DAA Ground-Station (LDGS) can be operated by a USS and can serve one or more USSes.
Multi-USS capability: The functionality for the UAE layer to assist at change of USS during flight.
NOTE: A UAV with Multi-USS capability can be controlled by more than one USS during a flight, but at any given time, the UAV is under the control of only one USS.
Multi-USS policy: The configuration provided by a UAS application specific server to assist at change of USS.
Remote Identification (Remote ID) of UAS: The ability of a UAS to provide identification and tracking information that can be received by other parties, to facilitate advanced operations for the UAS (such as Beyond Visual Line of Sight operations as well as operations over people), assist regulatory agencies, air traffic management agencies, law enforcement, and security agencies when a UAS appears to be flying in an unsafe manner or where the UAS is not allowed to fly.
UAS Service Supplier (USS): An entity that provides services to support the safe and efficient use of airspace by providing services to the operator / pilot of a UAS in meeting UTM operational requirements. A USS can provide any subset of functionality to meet the provider's business objectives (e.g., UTM, Remote Identification). In the scope of this specification, the term USS refers to both USS and USS/UTM.
UAV: The Uncrewed Aerial Vehicle (also called remotely piloted aircraft or drone) of a UAS.
No-transmit zone: A geographical area where UAVs are not allowed to transmit in a certain frequency band.
For the purposes of the present document, the following terms given in 3GPP TS 22.125 [2] apply
Command and Control (C2) Communication
Uncrewed Aerial System (UAS)
Uncrewed Aerial System Traffic Management (UTM)
UAV controller
For the purposes of the present document, the following terms given in clause 4.2 of 3GPP TS 22.125 [2] apply
Direct C2 Communication
Network-Assisted C2 communication
UTM-Navigated C2 communication
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
BVLOS Beyond Visual Line Of Sight
CAA Civil Aviation Authorities
C2 Command and Control
CAPIF Common API Framework for northbound APIs
DAA Detect And Avoid
EAS Edge Application Server
EDN Edge Data Network
EEC Edge Enabler Client
EES Edge Enablement Server
GM Group Management
GPSI General Public Subscription Identifier
LDGS Local DAA Ground Station
LM Location Management
NRM Network Resource Management
NTZ No-Transmit Zone
PQI PC5 QoS Identifier
QoS Quality of Service
SEAL Service Enabler Architecture Layer
UAE UAS Application Enabler
UAS Uncrewed Aerial System
UASS UAS Application Specific Server
UAV Uncrewed Aerial Vehicle
UAV-C Uncrewed Aerial Vehicle-Controller
USS UAS Service Supplier
UTM UAS Traffic Management
VAL Vertical Application Layer
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4 Architectural requirements
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.1 General
|
[AR-4.1-a] The UAS application enabler layer shall support one or more UAS applications.
[AR-4.1-b] The UAE capabilities should be offered as APIs to the UAS applications.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.2 Support for communications between UAVs
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.2.1 Description
|
This clause specifies the requirements for support for communications between UAVs.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.2.2 Requirements
|
[AR-4.2-a] The UAS application enabler layer shall provide mechanism to support communications between UAVs in a geographical area using unicast Uu.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.3 QoS provisioning for C2 communication
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.3.1 Description
|
This clause specifies the C2 QoS provisioning related requirements.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.3.2 Requirements
|
[AR-4.3.2-a] The UAE layer capabilities shall enable C2 application QoS parameter provisioning for network-assisted C2 communications to the 3GPP network system.
[AR-4.3.2-b] The UAE layer capabilities shall enable QoS differentiation for UAV operations.
[AR-4.3.2-c] The UAE server shall be capable of obtaining monitoring events related to the C2 QoS fulfilment/unfulfilment from the UAE clients (UAV and/or UAV controller).
[AR-4.3.2-d] The UAE layer capabilities shall enable QoS parameters modification to support meeting the C2 end-to-end application requirements, for paired-Uu connections between a UAV and UE-based UAV-C.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.4 C2 communication mode switching
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.4.1 Description
|
This clause specifies the C2 communication mode switching related requirements.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.4.2 Requirements
|
[AR-4.4.2-a] The UAE Server shall provide a mechanism for configuring the C2 communication modes at the UAE Client (UAV and UAV-C).
[AR-4.4.2-b] The UAE Client (UAV and UAV-C) and UAV Server shall provide mechanisms for switching between the C2 communication links.
[AR-4.4.2-c] The UAE Client (UAV and UAV-C) shall provide a mechanism for selecting a primary and a secondary communication link based on C2 communication mode configuration information.
[AR-4.4.2-d] The UAE Client (UAV or UAV-C) shall provide a mechanism to switch C2 communication link without involving the UAE Server when an immediate change of C2 communication mode is needed.
[AR-4.4.2-e] The UAE Server shall provide a mechanism for monitoring the availability of ProSe/PC5 link for C2 communications.
[AR-4.4.2-f] The UAE Client shall be capable of reporting the availability of ProSe/PC5 link for C2 communications.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.5 Support for monitoring of UAV location deviation
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.5.1 Description
|
This clause specifies the requirements for location reporting capabilities to monitor the UAV location deviation.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.5.2 Requirements
|
[AR-4.5.2-a] The SEAL layer shall provide mechanism to support the monitoring of UAV location.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.6 Support for reporting of UAV events
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.6.1 Description
|
This clause specifies the requirements for support for reporting of UAV events to USS/UTM.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.6.2 Requirements
|
[AR-4.6.2-a] The SEAL layer shall provide mechanism to support the reporting of the 3GPP related UAV events to the USS/UTM.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.7 Support for multi-USS deployments
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.7.1 Description
|
This clause specifies the requirements for support of multi-USS deployments.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.7.2 Requirements
|
[AR-4.7.2-a] The UAE Server shall provide a mechanism for the UAE Client to report its multi-USS capability to the UAE Server.
[AR-4.7.2-b] The UAE Server shall provide a mechanism for enabling USS for configuring the Multi-USS policies to the UAE Client (UAV).
[AR-4.7.2-c] The UAV Server shall provide a mechanism to support change of USS during UAS operations.
[AR-4.7.2-d] The UAE Client (UAV) shall provide a mechanism to support change of USS based on the policies for multi-USS configuration when an immediate change of USS is needed.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.8 Support of detect and avoid services and applications
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.8.1 Description
|
This clause specifies the requirements related to support for detect and avoid services and applications.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.8.2 Requirements
|
[AR-4.8.2-a] The UAE Server shall provide a mechanism for the UAE Client to report its DAA assist capability to the UAE Server.
[AR-4.8.2-b] The UAE Server shall provide a mechanism for enabling USS for configuring the DAA policies to the UAE Client (UAV).
[AR-4.8.2-c] The UAE layer shall provide a mechanism for a UAS application specific server to obtain DAA related events for a UAV.
[AR-4.8.2-d] The UAS application enabler layer shall provide a mechanism for a UAS application specific client to obtain DAA related events for a UAV.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.9 Support for NTZ indication
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.9.1 Description
|
This clause specifies the requirements related to support for indication of UAV NTZ enforcement.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
4.9.2 Requirements
|
[AR-4.3.2-a] The UAE layer capabilities shall enable NTZ provisioning to the 3GPP network system.
[AR-4.9.2-b] The UAE Server shall provide a mechanism for the UAE Client to report NTZ indications to the UAE Server.
[AR-4.9.2-c] The UAE layer shall provide a mechanism for a UAS application specific server to obtain NTZ indication events for a UAV.
[AR-4.9.2-d] The UAS application enabler layer shall provide a mechanism for a UAS application specific client to provide NTZ indications events for a UAV.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
5 Functional model
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
5.1 General
|
The functional model for the UAS application layer is organized into functional entities to describe a functional architecture which addresses the application layer support aspects for UAS applications.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
5.2 Functional model description
|
Figures 5.2-1 and 5.2-2 illustrates the simplified architectural models for the UAS application layer.
Figure 5.2-1: Simplified architectural model for the UAS application layer
Figure 5.2-2: Simplified architectural model for U2 connectivity between UAS UE1 and UAS UE2 at the UAS application layer
The UAS UE1 communicates with UAS application server over U1 reference point. The UAS UE1 and UAS UE2 communicate over U2 reference point.
NOTE 1: Support for UE-to-network relay architecture for UAS communications is out of scope of the present document.
The UAS UE1 and the UAS UE2 may be a UAV Controller or a UAV.
NOTE 2: The UAV Controller can connect to the UAV via a transport independent of 3GPP. Such UAV Controller is not a 3GPP UE and is out of scope of the present document.
NOTE 3: Support of PC5 at the U2 reference point for 5GS is out of scope of the present document.
The reference point U1 supports the UAS application related interactions between UAS UE and UAS application server. It is expected that this reference point is supported at least for unicast delivery mode, and may support multicast delivery mode. The reference point U2 supports the interactions between the UAS UEs. The UAS application server can be the USS/UTM.
The reference point U1 is based on Uu connectivity as specified in 3GPP TS 23.256 [4].
The reference point U2 is based on Uu connectivity as specified in 3GPP TS 23.256 [4].
NOTE 4: Support of multicast delivery over Uu for 5GS is out of scope of the present document.
Figure 5.2-3 illustrates the detailed UAS application layer functional model. It enhances the simplified architectural model for the UAS application layer by specifying the functional entities at the UAS application layer.
Figure 5.2-3: UAS application layer functional model
Figure 5.2-4 illustrates the detailed UAS application layer functional model where the UAV-C has a network‑assisted connectivity with the UAV.
Figure 5.2-4: UAS application layer functional model with UAV-C having network-assisted connectivity with UAV
The UAS application layer functional entities for the UAS UE and the UAS application server are grouped into the UAS application specific layer and the UAE layer. The UAE layer offers the UAE capabilities to the UAS application specific layer. The UAS application layer functional model utilizes the SEAL services as specified in 3GPP TS 23.434 [5].
The UAE server is located in the UAE layer. The SEAL services/UAS application specific layer utilized by UAE layer may include location management, group management, configuration management, identity management, key management and network resource management. The UAS application specific layer consists of the UAS application specific functionalities.
NOTE 5: The functionalities of the UAS application specific layer include the USS/UTM and are out of scope of the present document.
The following connectivity path for the UAS is supported when both the UAV-C and the UAV are 3GPP UEs:
- UAV-C to UAV over U2 (Uu connectivity).
The UAS application server consists of the UAE server, the SEAL servers and the UAS application specific server. The UAE server provides the UAS application layer support functions to the UAS application specific server over Us reference point. The SEAL servers provide the SEAL services to the UAS application specific server/UAE server over SEAL-S reference point.
The UAS UE consists of the UAE client, the SEAL clients and the UAS application specific client. The UAE client provides the UAS application layer support functions to the UAS application specific client over Uc reference point. The SEAL clients provide the SEAL services to the UAS application specific client/UAE client over SEAL-C reference point.
NOTE 6: In some deployments, the client and server entities of SEAL can be part of UAE client and UAE server respectively.
The UAS application specific client/UAE client acts as a VAL client for its interaction with the SEAL clients as specified in 3GPP TS 23.434 [5]. The UAS application specific server/UAE server acts as a VAL server for its interaction with the SEAL servers as specified in 3GPP TS 23.434 [5].
In the UAE layer, the UAE client communicates with the UAE server over U1-AE reference point. In the UAS application specific layer, the UAS application specific client communicates with UAS application specific server over U1-APP reference point.
NOTE 7: The U1-APP reference point includes UAV Controller/UAV to USS/UTM communication and is out of scope of the present document.
In the UAE layer, the UAE client of UAS UE2 communicates with UAE client of UAS UE1 over U2-AE reference point. In the UAS application specific layer, the UAS application specific client of UAS UE2 communicates with UAE client of UAS UE1 over U2-APP reference point.
NOTE 8: The U2-APP reference point is out of scope of the present document.
The following SEAL services for UAS applications may include:
- Location management as specified in 3GPP TS 23.434 [5];
- Group management as specified in 3GPP TS 23.434 [5];
- Configuration management as specified in 3GPP TS 23.434 [5];
- Identity management as specified in 3GPP TS 23.434 [5];
- Key management as specified in 3GPP TS 23.434 [5]; and
- Network resource management as specified in 3GPP TS 23.434 [5].
The UAS application specific client/UAE client interacts with SEAL clients over the SEAL-C reference point specified for each SEAL service. The UAS application specific server/UAE server interacts with SEAL servers over the SEAL-S reference point specified for each SEAL service. The interaction between the SEAL clients is supported by SEAL-PC5 reference point specified for each SEAL service. The interaction between a SEAL client and the corresponding SEAL server is supported by SEAL-UU reference point specified for each SEAL service.
NOTE 9: The SEAL-C, SEAL-S, SEAL-PC5, SEAL-UU reference points for each SEAL service is specified in 3GPP TS 23.434 [5].
To support distributed UAE server deployments, the UAE server interacts with another UAE server over UAE-E reference point.
A U1-AE message can be sent over at least unicast, and may be sent over transparent multicast via xMB or transparent multicast via MB2. The non-transparent multicast via xMB (as specified in 3GPP TS 26.348 [10]) is triggered by a U1-AE message. Multicast distribution can be supported by both transparent and non-transparent multicast modes.
The UAE server interacts with the 3GPP network system over U2, MB2, xMB, Rx, T8 and Nnef reference points.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
5.3 Functional entities description
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
5.3.1 General
|
Each clause specifies a description of a functional entity corresponding to UAS application layer and does not imply a physical entity.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
5.3.2 UAS application specific client
|
The UAS application specific client provides the client side functionalities corresponding to the UAS applications (e.g. Client interacting with USS/UTM). The UAS application specific client utilizes the UAE client for the UAS application layer support functions.
NOTE: The details of the UAS application specific client is out of scope of the present document.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
5.3.3 UAS application specific server
|
The UAS application specific server provides the server side functionalities corresponding to the UAS applications (e.g. USS/UTM). The UAS application specific server utilizes the UAE server for the UAS application layer support functions. If CAPIF is supported, the UAS application specific server acts as CAPIF's API invoker as specified in 3GPP TS 23.222 [3].
NOTE: The details of the UAS application specific server is out of scope of the present document.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.