Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.502  Word version:  19.1.0

Top   Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.2.11…   4.2.11.5…   4.3…   4.3.2.2.2   4.3.2.2.3…   4.3.3…   4.3.3.3   4.3.4…   4.3.4.3   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1…   4.11.1.2.2   4.11.1.2.3   4.11.1.3…   4.11.1.3.3…   4.11.1.4…   4.11.1.5…   4.11.2…   4.11.3…   4.12…   4.12.6…   4.12a…   4.12b…   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.3.2.5…   4.15.4…   4.15.6…   4.15.6.7…   4.15.6.13…   4.15.6.14…   4.15.9…   4.15.9.4…   4.15.13…   4.15.13.4…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.16.14…   4.16.15…   4.17…   4.17.9…   4.18…   4.19…   4.22…   4.23…   4.23.7…   4.23.7.3.3   4.23.7.3.4…   4.23.9…   4.23.9.4…   4.23.11…   4.24…   4.25…   4.25.6…   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   5.2.18…   A…   E…   F…   G   H…

 

4.2.2.3  Deregistration proceduresp. 60

4.2.2.3.1  Generalp. 60
The Deregistration procedure allows:
  • the UE to inform the network that it does not want to access the 5GS any longer; and
  • the network to inform the UE that it does not have access to the 5GS any longer; or
  • the network to inform the UE that the UE's Registered PLMN is not allowed to operate at the UE location.
The Deregistration request by the UE and Deregistration request by the network include whether the Deregistration applies to the 3GPP access, to the non-3GPP access, or to both. When the UE is registered to both accesses in the same PLMN, the Deregistration message can be sent over any access regardless of the access the Deregistration is applied to.
Network-initiated Deregistration may be initiated if the UE's registered PLMN is not allowed to operate in the present UE location.
Up
4.2.2.3.2  UE-initiated Deregistrationp. 60
The UE uses this procedure to deregister from the registered PLMN as shown in Figure 4.2.2.3.2-1.
Reproduction of 3GPP TS 23.502, Fig. 4.2.2.3.2-1: UE-initiated Deregistration
Up
Step 1.
The UE sends NAS message Deregistration Request (5G-GUTI, Deregistration type (e.g. Switch off), Access Type, [Unavailability Period Duration], [NAS message container]) to the AMF.
Access type indicates whether the Deregistration procedure applies to the 3GPP access, to the non-3GPP access, or to both if the 3GPP access and non-3GPP access of the UE are served by the same AMF (refer to TS 23.501). The AMF shall invoke the Deregistration procedure for the target access indicated by the UE.
If the UE and network support Unavailability Period and an event is triggered in the UE that would make the UE unavailable for a period of time, the UE includes Unavailability Period Duration as described in clause 5.4.1.4 of TS 23.501.
The NAS message container shall be included if the UE is sending a Deregistration Request message as an Initial NAS message and the UE has a valid 5G NAS security context and the UE needs to send non-cleartext IEs, see clause 4.4.6 of TS 24.501. If the UE does not need to send non-cleartext IEs, the UE shall send a Deregistration Request message without including the NAS message container.
Step 1a.
[Conditional] If the Deregistration Request message was not sent integrity protected or integrity protection verification failed, the NAS security initiation is performed as described in TS 33.501, the UE includes the full Deregistration Request message as defined in TS 24.501.
Step 2.
[Conditional] AMF to SMF (or V-SMF): Nsmf_PDUSession_ReleaseSMContext (SM Context ID).
If the UE has no established PDU Session over the target access indicated in step 1, then steps 2 to 5 are not executed. All PDU Sessions over the target access(es), which belong to the UE are released by the AMF sending Nsmf_PDUSession_ReleaseSMContext Request (SM Context ID) message to the SMF (or V-SMF) for each PDU Session. If the AMF determines that the secondary RAT usage reporting is required for the PDU Session, the AMF shall execute step 7 and 8 and then wait for the completion of step 8 to receive the secondary RAT usage data from the NG-RAN. After that, steps 2 to 6 in this procedure are performed to e.g. release the PDU Session(s).
For home routed roaming case, the V-SMF initiates the release of the PDU Session at the H-SMF by invoking the Nsmf_PDUSession_Release request.
Step 3.
[Conditional] The SMF (or H-SMF) releases all resources e.g. the IP address / Prefix(es) that were allocated to the PDU Session and releases the corresponding User Plane resources:
Step 3a.
[Conditional] The SMF (or H-SMF) sends N4 Session Release Request (N4 Session ID) message to the UPF(s) of the PDU Session. The UPF(s) shall drop any remaining packets of the PDU Session and release all tunnel resource and contexts associated with the N4 Session.
Step 3b.
[Conditional] The UPF(s) acknowledges the N4 Session Release Request by the transmission of an N4 Session Release Response (N4 Session ID) message to the SMF.
Step 4.
[Conditional] The SMF (or V-SMF) responds with Nsmf_PDUSession_ReleaseSMContext Response message.
For home routed roaming case, the H-SMF responds to the V-SMF with a Nsmf_PDUSession_Release response. The V-SMF releases the corresponding User Plane resources. The V-SMF responds to AMF with Nsmf_PDUSession_ReleaseSMContext Response message.
Step 5a.
[Conditional] If dynamic PCC applied to this session the SMF performs an SM Policy Association Termination procedure as defined in clause 4.16.6.
Step 5b-c.
[Conditional] If it is the last PDU Session the SMF is handling for the UE for the associated (DNN, S-NSSAI), the SMF unsubscribes from Session Management Subscription data changes notification with the UDM by means of the Nudm_SDM_Unsubscribe service operation. The SMF invokes the Nudm_UECM_Deregistration service operation so that the UDM removes the association it had stored between the SMF identity and the associated DNN and PDU Session ID.
Step 6.
[Conditional] If there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated AM Policy Association Termination procedure as defined in clause 4.16.3.2 delete the association with the PCF.
Step 6a.
[Conditional] If there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated UE Policy Association Termination procedure as defined in clause 4.16.13.1 delete the association with the PCF.
Step 7.
[Conditional] The AMF sends NAS message Deregistration Accept to UE depending on the Deregistration type i.e. if Deregistration type is switch-off, AMF does not send Deregistration Accept message.
Step 7a.
[Conditional] If Unavailability Period Duration is received from the UE and there is "Loss of Connectivity" monitoring event subscription for the UE, the AMF triggers "Loss of Connectivity" monitoring event report and includes the remaining value of the Unavailability Period Duration.
Step 8.
[Conditional] AMF to AN: N2 UE Context Release Request (Cause)
If the target access for Deregistration procedure is 3GPP access or both 3GPP access and non-3GPP access and there is N2 signalling connection to NG-RAN, the AMF sends N2 UE Release command to NG-RAN with Cause set to Deregistration to release N2 signalling connection. The details of this step are covered by steps 2 to 4 in the AN Release procedure, as described in clause 4.2.6.
If the target access for Deregistration procedure is non-3GPP access or both 3GPP access and non-3GPP access and there is N2 signalling connection to the N3IWF/TNGF/W-AGF, the AMF sends N2 UE Release command to N3IWF/TNGF/W-AGF with Cause set to Deregistration to release N2 signalling connection. The details of this step are covered by steps 2 to 5 in the "Deregistration procedure for (un)trusted non-3gpp access", as described in clauses 4.12.3 / 4.12a.3 and in clause 7.2.1 of TS 23.316 for W-5GAN access.
Up
4.2.2.3.3  Network-initiated Deregistrationp. 62
The procedure depicted in Figure 4.2.2.3.3-1 shows Network-initiated Deregistration procedure. The AMF can initiate this procedure for either explicit (e.g. by O&M intervention or if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE or the UE's registered PLMN is not allowed to operate in the present UE location or if a disaster condition is no longer being applicable, the AMF initiates Network-initiated Deregistration to trigger the return of UEs to the PLMN that had a Disaster Condition) or implicit (e.g. expiring of Implicit Deregistration timer). The UDM can trigger this procedure for operator-determined purposes (e.g. if a disaster condition is no longer being applicable as specified in clause 5.40.5 of TS 23.501) to request the removal of a subscriber's RM context and PDU Session(s) of the UE.
If the Network-initiated Deregistration procedure is triggered for MBSR IAB-UE that is registered with authorization to act as MBSR, the AMF behaves as described in clause 5.35A.4 of TS 23.501.
Reproduction of 3GPP TS 23.502, Fig. 4.2.2.3.3-1: Network-initiated Deregistration
Up
Step 1.
[Conditional] If the UDM wants to request the immediate deletion of a subscriber's RM contexts and PDU Sessions, the UDM shall send a Nudm_UECM_DeregistrationNotification (SUPI, Access Type, Removal Reason) message with Removal Reason set to Subscription Withdrawn to the registered AMF. The Access Type may indicate 3GPP Access, non-3GPP Access or both.
Step 2.
If the AMF receives Nudm_UECM_DeregistrationNotification in Step 1 with Removal Reason as Subscription Withdrawn, the AMF executes Deregistration procedure over the access(es) the Access Type indicates.
The AMF-initiated Deregistration procedure is either explicit (e.g. by O&M intervention or if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE) or implicit. The AMF does not send the Deregistration Request message to the UE for Implicit Deregistration. If the UE is in CM-CONNECTED state, the AMF may explicitly deregister the UE by sending a Deregistration Request message (Deregistration type, Access Type, [list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value]) to the UE. The Deregistration type may be set to Re-registration in which case the UE should re-register at the end of the Deregistration procedure. Access Type indicates whether Deregistration procedure applies to the 3GPP access or non-3GPP access, or both. If the Deregistration Request message is sent over 3GPP access and the UE is in CM-IDLE state in 3GPP access, the AMF pages the UE. The list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value, is provided if the AMF determines that no S-NSSAI can be provided to the UE in the Allowed NSSAI.
If the UE has established PDU Session associated with emergency service, the AMF shall not initiate Deregistration procedure. In this case, the AMF performs network requested PDU Session Release for any PDU session associated with non-emergency service as described in clause 4.3.4.
For NR satellite access, the AMF initiates Network-initiated Deregistration if it detects that the UE's registered PLMN is not allowed to operate in the present UE location. In this case, the AMF shall provide the appropriate cause value indicating the PLMN is not allowed to operate in the present UE location, see clause 5.4.11.4 of TS 23.501.
If the network de-registration is triggered for a UE registered for Disaster Roaming due to a disaster condition no longer being applicable, the Deregistration Request shall contain the cause value "PLMN not allowed" and include a disaster return wait range as described in clause 5.5.2.3.1 of TS 24.501 and as specified in clause 5.40.5 of TS 23.501, the network, shall organise the return of the Disaster Roaming UEs in a manner that does not cause overload (e.g. of signalling) in the PLMN that previously had the Disaster Condition.
If the MBSR authorization state changes for a MBSR (IAB-UE) registered in network as specified in clause 5.35A.4 of TS 23.501, based on operator configuration, the AMF triggers Deregistration procedure.
Step 3.
[Conditional] If the Deregistration procedure is triggered by UDM (Step 1), the AMF acknowledges the Nudm_UECM_DeRegistrationNotification to the UDM.
If Access Type indicates 3GPP Access or non-3GPP Access and AMF does not have UE context for another access type, or if Access Type indicates both, the AMF unsubscribes with the UDM using Nudm_SDM_Unsubscribe service operation.
Step 4.
[Conditional] If the UE has any established PDU Session over the target access for deregistration indicated in step 2, then step 2 ~ step 5 of UE-initiated Deregistration procedure in clause 4.2.2.3.2 is performed.
Step 5.
[Conditional] As in step 6 of Figure 4.2.2.3.2-1.
Step 5a.
[Conditional] As in step 6a of Figure 4.2.2.3.2-1.
Step 6.
[Conditional] If the UE receives the Deregistration Request message from the AMF in step 2, the UE sends a Deregistration Accept message to the AMF any time after step 2. The NG-RAN forwards this NAS message to the AMF along with the TAI+ Cell identity of the cell which the UE is using.
Step 7.
[Conditional] AMF to AN: N2 UE Context Release Request (Cause): as in step 8 of Figure 4.2.2.3.2-1.
If the UE is deregistered over only 3GPP access or non-3GPP access and the AMF does not have UE context for the other, or if the procedure applies to both access types, then at any time, AMF can unsubscribe from the UDM, otherwise the AMF can deregister from UDM using Nudm_UECM_Deregistration request by indicating its associating access type.
Up

Up   Top   ToC