Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 38.413  Word version:  17.1.1

Top   Top   Up   Prev   Next
1…   4…   8…   8.2…   8.2.3…   8.3…   8.3.4…   8.4…   8.4.3…   8.5…   8.7…   8.8…   8.10…   8.12…   8.17…   9…   9.2.5…   9.3…   9.3.2…   10…

 

8.17  Broadcast Session Management Procedures |R17|p. 114

8.17.1  Broadcast Session Setupp. 114

8.17.1.1  Generalp. 114

The purpose of the Broadcast Session Setup procedure is to request the NG-RAN node to setup MBS resources for an MBS session of a broadcast service. The procedure uses non-UE associated signalling.

8.17.1.2  Successful Operationp. 114

Reproduction of 3GPP TS 38.413, Fig. 8.17.1.2-1: Broadcast Session Setup, successful operation.
Up
The AMF initiates the procedure by sending a BROADCAST SESSION SETUP REQUEST message to the NG-RAN node. If the NG-RAN node accepts all the flows in the MBS session at least in one of its cells, the NG-RAN node responds with the BROADCAST SESSION SETUP RESPONSE message.
If the MBS Service Area IE is included in the BROADCAST SESSION SETUP REQUEST message, the NG-RAN node shall take it into account as specified in TS 23.247.
If the MBS Session FSA ID List IE is included in the BROADCAST SESSION SETUP REQUEST message, the NG-RAN node shall take it into account to determine cells/frequencies within the MBS service area to broadcast MBS session data as specified in TS 23.247.
Up

8.17.1.3  Unsuccessful Operationp. 114

Reproduction of 3GPP TS 38.413, Fig. 8.17.1.3-1: Broadcast Session Setup, unsuccessful operation.
Up
If the NG-RAN node is not able to provide the resources for all the flows in the MBS session in any of its cells, it shall send the BROADCAST SESSION SETUP FAILURE message.

8.17.1.4  Abnormal Conditionsp. 114

Void.

8.17.2  Broadcast Session Modificationp. 115

8.17.2.1  Generalp. 115

The purpose of the Broadcast Session Modification procedure is to request the NG-RAN node to update the broadcast area or the MBS information related to a previously established MBS session. The procedure uses non-UE associated signalling.

8.17.2.2  Successful Operationp. 115

Reproduction of 3GPP TS 38.413, Fig. 8.17.2.2-1: Broadcast Session Modification, successful operation.
Up
The AMF initiates the procedure by sending a BROADCAST SESSION MODIFICATION REQUEST message to the NG-RAN node.
If the MBS Service Area IE is included in the BROADCAST SESSION MODIFICATION REQUEST message, the NG-RAN node shall update the MBS service area and send the BROADCAST SESSION MODIFICATION RESPONSE message.
If the MBS Session Modification Request Transfer IE is included in the BROADCAST SESSION MODIFICATION REQUEST message, the NG-RAN node shall replace the previously provided information by the newly received one and update the MBS context and resources as necessary and send the BROADCAST SESSION MODIFICATION RESPONSE message.
Up

8.17.2.3  Unsuccessful Operationp. 115

Reproduction of 3GPP TS 38.413, Fig. 8.17.2.3-1: Broadcast Session Modification, unsuccessful operation.
Up
If the NG-RAN node fails to update any requested modification, the NG-RAN node shall send the BROADCAST SESSION MODIFICATION FAILURE message.

8.17.2.4  Abnormal Conditionsp. 115

Void.

8.17.3  Broadcast Session Releasep. 116

8.17.3.1  Generalp. 116

The purpose of the Broadcast Session Release procedure is to release the MBS context corresponding to the previous established MBS session. The procedure uses non-UE assocated signalling.

8.17.3.2  Successful Operationp. 116

Reproduction of 3GPP TS 38.413, Fig. 8.17.3.2-1: Broadcast Session Release, successful operation.
Up
The AMF initiates the procedure by sending a BROADCAST SESSION RELEASE REQUEST message to the NG-RAN node.
Upon reception of the BROADCAST SESSION RELEASE REQUEST message, the NG-RAN node shall respond with the BROADCAST SESSION RELEASE RESPONSE message. The NG-RAN node node shall stop broadcasting and release all resources associated with the broadcast session.
Upon reception of the BROADCAST SESSION RELEASE RESPONSE message, the AMF shall transfer transparently the Broadcast Session Release Response Transfer IE, if available, to the MB-SMF.
Up

8.17.3.3  Unsuccessful Operationp. 116

Not applicable.

8.17.3.4  Abnormal Conditionsp. 116

Void.

8.17.4  Broadcast Session Release Requiredp. 116

8.17.4.1  Generalp. 116

The purpose of the Broadcast Session Release Required procedure is to trigger the AMF to release the MBS context corresponding to the previously established MBS session. The procedure uses non-UE associated signalling.

8.17.4.2  Successful Operationp. 117

Reproduction of 3GPP TS 38.413, Fig. 8.17.4.2-1: Broadcast Session Release Required, successful operation.
Up
The NG-RAN node initiates the procedure by sending a BROADCAST SESSION RELEASE REQUIRED message to the AMF.
Upon receiption of the BROADCAST SESSION RELEASE REQUIRED message, the AMF shall realize there is no adequate resources for NG-RAN node to provide the broadcast service over radio and start to release the MBS context corresponding to the previously established MBS session.

8.17.4.3  Abnormal Conditionsp. 117

Void.

8.18  Multicast Session Management Procedures |R17|p. 117

8.18.1  Distribution Setupp. 117

8.18.1.1  Generalp. 117

The purpose of the Distribution Setup procedure is to assign NG-U resources for an MBS session. The procedure uses non-UE-associated signalling.

8.18.1.2  Successful Operationp. 117

Reproduction of 3GPP TS 38.413, Fig. 8.18.1.2-1: Distribution Setup, successful operation.
Up
The NG-RAN node initiates the procedure by sending a DISTRIBUTION SETUP REQUEST message to the AMF. The AMF responds with a DISTRIBUTION SETUP RESPONSE message.
For location dependent multicast sessions, the NG-RAN node shall include the MBS Area Session ID IE in the DISTRIBUTION SETUP REQUEST message, and the AMF shall provide the same value of the MBS Area Session ID IE in the DISTRIBUTION SETUP RESPONSE message.
If the Shared NG-U Unicast TNL Information IE is included in the MBS Distribution Setup Request Transfer IE in the DISTRIBUTION SETUP REQUEST message, the MB-SMF shall use the included information as the downlink termination point for the shared NG-U transport.
If the Shared NG-U Unicast TNL Information IE is not included in the MBS Distribution Setup Request Transfer IE in the DISTRIBUTION SETUP REQUEST message, the MB-SMF shall interpret that the IP multicast is used for this shared NG-U transport, and include the Shared NG-U Multicast TNL Information IE in the MBS Distribution Setup Response Transfer IE in the DISTRIBUTION SETUP RESPONSE message.
Up

8.18.1.3  Unsuccessful Operationp. 118

Reproduction of 3GPP TS 38.413, Fig. 8.18.1.3-1: Distribution Setup, unsuccessful operation.
Up
In case the shared NG-U transport cannot be setup successfully, the AMF shall respond with the DISTRIBUTION SETUP FAILURE message to the NG-RAN node with an appropriate cause value.

8.18.1.4  Abnormal Conditionsp. 118

Void.

8.18.2  Distribution Releasep. 118

8.18.2.1  Generalp. 118

The purpose of the Distribution Release procedure is to enable the release of an already established NG-U resources for a given MBS session, or for a given area session of the MBS session. The procedure uses non-UE-associated signalling.

8.18.2.2  Successful Operationp. 118

Reproduction of 3GPP TS 38.413, Fig. 8.18.2.2-1: Distribution Release, successful operation.
Up
The NG-RAN node initiates the procedure by sending a DISTRIBUTION RELEASE REQUEST message.
Upon receipt of the DISTRIBUTION RELEASE REQUEST message, the AMF shall send the DISTRIBUTION RELEASE RESPONSE message after successfully removing the corresponding NG-U resource for the MBS session.
For location dependent multicast session, the NG-RAN node shall include the MBS Area Session ID IE in the DISTRIBUTION RELEASE REQUEST message, and the AMF shall provide the same value of the MBS Area Session ID IE in the DISTRIBUTION RELEASE RESPONSE message.
If unicast shared NG-U transport is used, the NG-RAN node shall include the Shared NG-U TNL Information IE in the MBS Distribution Release Request Transfer IE in the DISTRIBUTION RELEASE REQUEST message, and the MB-SMF shall release the corresponding shared NG-U transport as specified in TS 23.247.
Up

8.18.2.3  Unsuccessful Operationp. 119

Not applicable.

8.18.2.4  Abnormal Conditionsp. 119

Void.

8.18.3  Multicast Session Activationp. 119

8.18.3.1  Generalp. 119

The purpose of the Multicast Session Activation procedure is to request a NG-RAN node to activate the MBS resources of one MBS session. The procedure uses non-UE-associated signalling.

8.18.3.2  Successful Operationp. 119

Reproduction of 3GPP TS 38.413, Fig. 8.18.3.2-1: Multicast Session Activation, successful operation.
Up
The AMF initiates the procedure by sending a MULTICAST SESSION ACTIVATION REQUEST message to the NG-RAN node.
Upon receipt of the MULTICAST SESSION ACTIVATION REQUEST, the NG-RAN node activates the MBS resources corresponding to the MBS session indicated in the MULTICAST SESSION ACTIVATION REQUEST message and indicates in the MULTICAST SESSION ACTIVATION RESPONSE message for which MBS session the request was fulfilled.

8.18.3.3  Unsuccessful Operationp. 120

Reproduction of 3GPP TS 38.413, Fig. 8.18.3.3-1: Multicast Session Activation, unsuccessful operation.
Up
If the NG-RAN node cannot activate the MBS resources indicated in the MULTICAST SESSION ACTIVATION REQUEST message, it shall respond with a MULTICAST SESSION ACTIVATION FAILURE message with an appropriate cause value.

8.18.3.4  Abnormal Conditionsp. 120

Void.

8.18.4  Multicast Session Deactivationp. 120

8.18.4.1  Generalp. 120

The purpose of the Multicast Session Deactivation procedure is to request a NG-RAN node to deactivate the MBS resources of one MBS session. The procedure uses non-UE-associated signalling.

8.18.4.2  Successful Operationp. 120

Reproduction of 3GPP TS 38.413, Fig. 8.18.4.2-1: Multicast Session Deactivation, successful operation.
Up
The AMF initiates the procedure by sending a MULTICAST SESSION DEACTIVATION REQUEST message to the NG-RAN node.
Upon receipt of this message, the NG-RAN node shall deactivate the MBS resources corresponding to the MBS session indicated in the MULTICAST SESSION DEACTIVATION REQUEST message and shall indicate in the MULTICAST SESSION DEACTIVATION RESPONSE message for which MBS session the request was fulfilled.

8.18.4.3  Unsuccessful Operationp. 121

Not applicable.

8.18.4.4  Abnormal Conditionsp. 121

Void.

8.18.5  Multicast Session Updatep. 121

8.18.5.1  Generalp. 121

The purpose of the Multicast Session Update procedure is to request the NG-RAN node to update the MBS service area and/or the MBS QoS information related to a MBS session, or to an area session of a location dependent multicast session. The procedure uses non-UE associated signalling.

8.18.5.2  Successful Operationp. 121

Reproduction of 3GPP TS 38.413, Fig. 8.18.5.2-1: Multicast Session Update, successful operation.
Up
The AMF initiates the procedure by sending a MULTICAST SESSION UPDATE REQUEST message to the NG-RAN node.
Upon receipt of the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall update the QoS profile and/or MBS Service Area for the multicast service and send the MULTICAST SESSION UPDATE RESPONSE message to the AMF.
For location dependent multicast session, the AMF shall include the MBS Area Session ID IE in the MULTICAST SESSION UPDATE REQUEST message, and the NG-RAN node shall provide the same value of the MBS Area Session ID IE in the MULTICAST SESSION UPDATE RESPONSE message.
In case the MBS Service Area Information IE is included in the Multicast Session Update Request Transfer IE in the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall update the stored MBS Service Area Information for that service, as specified in TS 23.247.
In case the MBS QoS Flows To Be Setup or Modify List IE is included in the Multicast Session Update Request Transfer IE in the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall setup or modify the MBS QoS information accordingly.
In case the MBS QoS Flows To Be Release List IE is included in the Multicast Session Update Request Transfer IE in the MULTICAST SESSION UPDATE REQUEST message, the NG-RAN node shall release the indicated MBS QoS flows.
Up

8.18.5.3  Unsuccessful Operationp. 122

Reproduction of 3GPP TS 38.413, Fig. 8.18.5.3-1: Multicast Session Update, unsuccessful operation.
Up
If the NG-RAN node is not able to perform any of the requested update, it shall respond with a MULTICAST SESSION UPDATE FAILURE message with an appropriate cause value.

8.18.5.4  Abnormal Conditionsp. 122

Void.

Up   Top   ToC