Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.527  Word version:  18.2.0

Top   Top   Up   Prev   None
1…   4…   5…   6…   6.6…   7…   8…   8.3…   8.3.2.4   8.3.3…   8.4…

 

8.4  Restoration procedures for AMF failure |R18|p. 46

8.4.1  Multicast MBS session (de)activation or update after an AMF failurep. 46

8.4.1.1  Generalp. 46

Different NG-RAN nodes may establish shared delivery for the same MBS session via different AMFs of a same AMF set. During the shared delivery establishment:
  • each AMF involved in the establishment of shared delivery stores in its multicast MBS session context the RAN-ID of the NG-RAN nodes that have established shared delivery via this AMF, for subsequent signaling related to the multicast MBS Session (Multicast MBS session activation, deactivation or update); and
  • the MB-SMF stores in its multicast MBS session context the NF Instance ID of each AMF involved in the establishment of shared delivery to enable subsequent signalling towards these AMFs.
See clause 7.2.1.4 and Table 6.9.1-1 of TS 23.247.
The following procedure may be used to enable the MB-SMF to activate, deactivate or update the multicast MBS session, when an AMF of the AMF set through which one or more NG-RAN nodes had established shared delivery has failed with or without restart or is no longer reachable (e.g. due to networking issues, or because it has been de-instantiated from the AMF set).
Up

8.4.1.2  N2 MBS session request distribution with list of NG RAN Node IDs provided by MB-SMF to AMFp. 46

During the shared delivery establishment procedure (see clause 7.2.1.4 of TS 23.247), the MB-SMF stores, for each AMF involved in the establishment of shared delivery, the list of NG-RAN Node IDs having shared delivery established through the AMF.
The MB-SMF may then send any multicast MBS session activation, deactivation and update request towards the NG-RAN nodes that established shared delivery as defined in Figure 8.4.1.2-2.
Reproduction of 3GPP TS 23.527, Fig. 8.4.1.2-2: Multicast MBS session activation, deactivation or update via an alternative AMF of the AMF set
Up
Step 0.
NG RAN1 establishes shared delivery for the multicast MBS session via AMF1. NG RAN2 and NG RAN3 do so via AMF2. MB-SMF stores corresponding information in its MBS session context.
Step 1.
AMF2 becomes no longer available/reachable.
Step 2.
The MB-SMF needs to activate, deactivate or update the MBS session.
Step 3.
The MB-SMF sends an Namf_MBSCommunication_N2MessageTransfer Request to every AMF of the same AMF set that was involved in the establishment of shared delivery, as specified in clauses 7.2.5.2, 7.2.5.3 and 7.2.6 of TS 23.247, but with the request further including the list of NG RAN Node IDs known by the MB-SMF to have established shared delivery through the respective AMF. AMF1 distributes the request to the list of NG-RAN nodes received from the MB-SMF, if any, otherwise to the list of the NG-RAN nodes it has stored locally, if any.
Step 4.
If the MB-SMF is not yet aware that AMF2 has failed, it sends an Namf_MBSCommunication N2MessageTransfer Request to AMF2 as described in step 3 and detects that AMF2 is no longer available.
Step 5.
The MB-SMF sends an Namf_MBSCommunication_N2MessageTransfer Request to an alternative AMF (AMF1 in this example) of the same AMF set including the list of NG RAN Node IDs known by the MB-SMF to have established shared delivery through the failed AMF (AMF2). AMF1 distributes the request to the list of NG-RAN nodes received from the MB-SMF.
If the MB-SMF is already aware at the start of this procedure that AMF2 has failed, the MB-SMF may already include in step 3 the list of NG RAN Node IDs known by the MB-SMF to have established shared delivery through the failed AMF (AMF2).When using unicast transport over N3mb, the MB-SMF may determine that a NG-RAN node has failed or restarted as specified in clause 8.3.4. In this case, the MB-SMF shall remove this NG RAN node from its MBS session context.
In scenarios where the MB-SMF would request an AMF to distribute an activate, deactivate or update request to a NG RAN node that has no longer shared delivery established (e.g. the NG RAN node has restarted but this has not been detected by the MB-SMF), the NG RAN will return an activation or update failure to the AMF. To enable the MB-SMF to be notified about this failure and to remove the NG RAN node ID from its MBS session context, the MB-SMF shall include a notification URI in every Namf_MBSCommunication_N2MessageTransfer Request it sends and the AMF shall notify a failure received from an NG RAN node towards the MB-SMF by sending an Namf_MBSCommunication_Notify request to the notification URI that was received in the request.
Likewise, if an AMF receives an Namf_MBSCommunication_N2MessageTransfer Request including a NG RAN Node ID and the AMF cannot send any N2 message towards this NG RAN node (e.g. the NG-RAN node has failed without restart), the AMF shall notify the failure to send N2 MBS session requests to the NG RAN node by sending an Namf_MBSCommunication_Notify request to the notification URI that was received in the request.
Up

$  Change historyp. 48


Up   Top