Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.247  Word version:  18.7.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3   5…   6…   6.6…   7…   7.1.1.2   7.1.1.3   7.1.1.4…   7.1.1.6…   7.1.2…   7.2…   7.2.2…   7.2.3…   7.2.4…   7.2.4.3…   7.2.5…   7.2.6…   7.3…   7.3.5…   7.5…   8…   9…   9.2…   9.3…   9.4…   A… 
7.1.1.6 MBS Session Update without PCC  7.1.1.7 MBS Session Update with PCC 
...

 

7.1.1.6  MBS Session Update without PCC  p. 57

This procedure is used by the AF to update the MBS service area and/or MBS Service Information. Updating MBS Service Information may lead to addition of new MBS QoS Flow(s), removal of existing MBS QoS Flow(s) or update of existing MBS QoS Flow(s). The procedure applies to both multicast and broadcast communications unless otherwise stated.
If the MBSF acts as the MBS security function for multicast as defined in TS 33.501, it may use this procedure to provide an MSK for the MBS session via the control plane. In this case the MBSF may initiate this procedure and steps 1, 2 and 10 do not apply.
For local multicast services and location dependent multicast services, the AF may perform a Service Announcement towards UEs to update the MBS service area before the MBS Session Update procedure is started or after the MBS Session Update procedure is completed.
Reproduction of 3GPP TS 23.247, Fig. 7.1.1.6-1: MBS Session Update without PCC
Figure 7.1.1.6-1: MBS Session Update without PCC
Up
Step 1.
AF of content provider initiates MBS Session Update to a NEF/MBSF, e.g. to update MBS service area and/or update MBS Service Information (as defined in clause 6.14), or to activate or deactivate an MBS session. AF may provide updated information for an MBS session (identified by MBS session ID) by sending an Nnef_MBSSession_Update Request (MBS Session ID, [MBS Service Information], [MBS service area], [MBS session state (active/inactive)], [NR RedCap UE Information]).
If geographical area information or civic address information was provided by the AF as MBS service area, NEF/MBSF translates the MBS service area to Cell ID list or TAI list.
For broadcast communication, the AF may subsequently update "NR RedCap UE Information" parameter.
Step 2.
NEF checks authorization of AF.
Step 3.
NEF/MBSF sends Nmbsmf_MBSSession_Update Request to MB-SMF forwarding the updated information received from the AF in step 1. If the MBSF acts as the MBS security function for multicast as defined in TS 33.501, it may provide an updated multicast session security context for the MBS session in the Nmbsmf_MBSSession_Update Request.
If the MBS service area is not covered by the MB-SMF service area of the MB-SMF, the MB-SMF reduces the MBS service area to be within the MB-SMF service area and continues the procedure with the reduced MBS service area.
For broadcast communication, the NEF/MBSF forwards "NR RedCap UE Information" parameter to the MB-SMF, if received.
Step 4.
The MB-SMF derives any updated QoS parameters locally under consideration of the updated MBS Service Information. This may lead to addition of new MBS QoS Flow(s), removal of existing MBS QoS Flow(s) or update of existing MBS QoS Flow(s).
Step 5-6.
MB-SMF may need to update MB-UPF, e.g. if new MBS QoS Flow is to be created, or existing MBS QoS Flow is to be deleted.
Step 7.
For broadcast communication, the MB-SMF continues the procedure towards the AMF and NG-RAN as specified in clause 7.3.3. For multicast communication, the MB-SMF continues the procedure towards the AMF and NG-RAN as specified in clause 7.2.5 (for service activation/deactivation), clause 7.2.6 (for QoS updates and service area updates).
Step 8.
If an MBS service area is being updated, the MB-SMF stores the new service area in its profile at the NRF.
Step 9.
MB-SMF responds to the NEF/MBSF with a Nmbsmf_MBSSession_Update Response ([Information of area reduction]).
If the MB-SMF reduces the MBS service area in step 3, the MB-SMF includes result information in the response indicating that the MBS service area cannot be covered by the MB-SMF service area of the MB-SMF, and includes the Information of area reduction that relates to the reduced MBS service area.
Step 10.
NEF/MBSF responds to the AF with a Nnef_MBSSession_Update Response ([MBS service area information]).
If the NEF/MBSF receives the result information in step 9 indicating that the MBS service area cannot be covered by the MB-SMF service area of the MB-SMF, the NEF/MBSF includes that result information, and the Information of area reduction.
Up

7.1.1.7  MBS Session Update with PCC  p. 58

For local multicast services and location dependent multicast services, the AF may perform a Service Announcement towards UEs to update the MBS service area before the MBS Session Update procedure is started or after the MBS Session Update procedure is completed.
Reproduction of 3GPP TS 23.247, Fig. 7.1.1.7-1: MBS Session Update with PCC
Figure 7.1.1.7-1: MBS Session Update with PCC
Up
Step 1-2.
Same as in Figure 7.1.1.6-1.
Step 3.
For the interaction with the PCF in this procedure, the NEF/MBSF applies the same decision that was taken in step 10 in Figure 7.1.1.3-1 during the MBS Session Creation with PCC procedure unless the MBS session update only relates to an activation or deactivation of the MBS session and/or an MBS service area update and thus no PCF interactions are required.
If the NEF/MBSF decided to interact with the PCF, steps 4 to 6 are performed and in step 7 an indication that the PCF has to be contacted is provided, and MBS Service Information is not provided to the MB-SMF.
If the NEF/MBSF decided not to interact with the PCF, steps 4 to 6 are skipped and MBS Service Information is provided to the MB-SMF in step 7.
Step 4.
NEF/MBSF sends an Npcf_MBSPolicy_Authorization_Update Request (application session context, [MBS Service Information]) to the PCF forwarding the updated information received from the AF in step 1.
Step 5.
The PCF determines whether the update is authorized and if the update is authorized, the PCF derives the update for the QoS parameters based on the received MBS Service Information and determines whether this new QoS is allowed. If the new QoS is allowed, the PCF updates the policy information for the MBS session (as defined in clause 6.10) accordingly. If the policy information for the MBS session has changed, the PCF shall provide an indication that the PCF has to be contacted.
Step 6.
The PCF sends an Npcf_MBSPolicy_Authorization_Update Response (Result indication, [indication that the PCF has to be contacted]) to the NEF/MBSF.
If the update is not authorized or the new QoS is not allowed, the PCF indicates so in the response to the NEF/MBSF which in turn informs the AF about it (by sending the Nnef_MBSSession_Update Response) and ends this procedure.
Step 7.
The NEF/MBSF sends Nmbsmf_MBSSession_Update Request to the MB-SMF forwarding the updated information received from the AF in step 1. If the NEF/MBSF has decided not to interact with the PCF, the NEF/MBSF send the indication that the PCF has to be contacted, in addition.
If the NEF/MBSF has decided to interact with the PCF and thus provided the updated MBS Service Information to the PCF in step 4, the updated MBS Service Information is not forwarded. The NEF/MBSF forwards the indication that the PCF has to be contacted, if received from the PCF.
Step 8.
If the MB-SMF does not receive the indication that the PCF has to be contacted, the MB-SMF decides whether to interact with the PCF. If it decides not to interact with the PCF, it continues with step 11. Otherwise, the MB-SMF sends an Npcf_MBSPolicyControl_Update Request (MBS Policy Association ID, [MBS Service Information]) for the MBS session towards the PCF. The MB-SMF forwards the MBS Service Information to the PCF if received from the NEF/MBSF in the previous step 7.
If PCF receives MBS Service Information from the MB-SMF, the PCF performs the subsequent step 9. If the PCF does not receive MBS Service Information from the MB-SMF, the PCF identifies any updated policy information for the MBS session (as defined in clause 6.10) corresponding to the MBS Session ID received from the MB-SMF and continues with step 10.
Step 9.
The PCF determines whether the update is authorized and if the update is authorized, the PCF derives the update for the QoS parameters based on the received MBS Service Information and determines whether this new QoS is allowed. If the new QoS is allowed, the PCF updates the policy information for the MBS session (as defined in clause 6.10) accordingly.
Step 10.
The PCF responds with Npcf_MBSPolicyControl_Update Response ([updated policy information for the MBS session], Result indication).
If the request is not authorized or the required QoS is not allowed, the PCF indicates so in the response to the MB-SMF which in turn informs the AF about it (by sending the Nmbsmf_MBSSession_Update Response) and ends this procedure.
Step 11.-16.
Same as steps 5-10 in Figure 7.1.1.6-1.
Up

Up   Top   ToC