Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

5.5.2  De-registration procedureWord‑p. 365

5.5.2.1  GeneralWord‑p. 365

The de-registration procedure is used:
  1. by the UE to de-register for 5GS services over 3GPP access when the UE is registered over 3GPP access;
  2. by the UE to de-register for 5GS services over non-3GPP access when the UE is registered over non-3GPP access;
  3. by the UE to de-register for 5GS services over 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses;
  4. by the network to inform the UE that it is deregistered for 5GS services over 3GPP access when the UE is registered over 3GPP access;
  5. by the network to inform the UE that it is deregistered for 5GS services over non-3GPP access when the UE is registered over non-3GPP access;
  6. by the network to inform the UE that it is deregistered for 5GS services over 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses;
  7. by the network to inform the UE to re-register to the network; and
  8. by the network to inform the UE supporting UAS service that it is deregistered for UAS services in 5GS.
The de-registration procedure with appropriate de-registration type shall be invoked by the UE:
  1. if the UE is switched off;
  2. as part of the eCall inactivity procedure defined in subclause 5.5.3; and
  3. as part of USIM removal.
The de-registration procedure with appropriate de-registration type shall be invoked by the network:
  1. if the network informs whether the UE should re-register to the network.
The de-registration procedure with appropriate access type shall be invoked by the UE:
  1. if the UE needs to de-register for 5GS services over 3GPP access when the UE is registered over 3GPP access;
  2. if the UE needs to de-register for 5GS services over non-3GPP access when the UE is registered over non-3GPP access;
  3. the UE needs to de-register for 5GS services over 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses; or
  4. to de-register for 5GS services over 3GPP access, if the UE is registered for disaster roaming over 3GPP access and has successfully registered over non-3GPP access on another PLMN.
The de-registration procedure with appropriate access type shall be invoked by the network:
  1. if the network needs to inform the UE that it is deregistered over 3GPP access when the UE is registered over 3GPP access;
  2. if the network needs to inform the UE that it is deregistered over non-3GPP access when the UE is registered over non-3GPP access; or
  3. if the network needs to inform the UE that it is deregistered over 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses.
If the de-registration procedure is triggered due to USIM removal, the UE shall indicate "switch off" in the de-registration type IE.
If the de-registration procedure is requested by the network for a UE that has an emergency PDU session, the AMF shall not send a DEREGISTRATION REQUEST message to the UE and indicate to the SMF to release all non-emergency PDU sessions as specified in TS 23.502.
If the de-registration procedure for 5GS services is performed, a local release of the PDU sessions, if any, for this particular UE is performed. If a PDU session is associated with one or more MBS sessions, the UE is considered as removed from the associated MBS sessions.
The UE is allowed to initiate the de-registration procedure even if the timer T3346 is running.
The AMF shall provide the UE with a non-3GPP de-registration timer.
When the AMF enters the state 5GMM-DEREGISTERED for 3GPP access, the AMF shall delete the stored UE radio capability information or the UE radio capability ID, if any.
When upper layers indicate that emergency services are no longer required, the UE if still registered for emergency services, may perform UE-initiated de-registration procedure followed by a re-registration to regain normal services, if the UE is in or moves to a suitable cell.
If the UE is registered for onboarding services in SNPN, after completing the configuration of one or more entries of the "list of subscriber data", the UE should perform UE-initiated de-registration procedure. To prevent the UE registered for onboarding services in SNPN from staying on the ON-SNPN or to prevent a UE whose subscription only allows for configuration of SNPN subscription parameters in PLMN via the user plane, from staying registered indefinitely, when an implementation specific timer expires:
  • if the AMF considers that the UE is in 5GMM-IDLE, the AMF shall locally de-registers the UE; or
  • if the UE is in 5GMM-CONNECTED, the AMF shall initiate the network-initiated de-registration procedure (see subclause 5.5.2.3).
If the de-registration procedure is not due to switch off and upper layers request establishing an emergency PDU session before the de-registration procedure has been completed, the UE shall abort the deregistration procedure, perform local de-registration and initiate a registration procedure.
If the UE in 5GMM-CONNECTED mode determines to obtain service on a higher priority PLMN due to SOR, then based on the conditions as specified in TS 23.122 annex C, where applicable, the UE shall perform UE-initiated de-registration procedure.
Up

5.5.2.2  UE-initiated de-registration procedureWord‑p. 367

5.5.2.2.1  UE-initiated de-registration procedure initiationWord‑p. 367
The de-registration procedure is initiated by the UE by sending a DEREGISTRATION REQUEST message (see example in Figure 5.5.2.2.1.1). The De-registration type IE included in the message indicates whether the de-registration procedure is due to a "switch off" or not. The access type included in the message indicates whether the de-registration procedure is:
  1. for 5GS services over 3GPP access when the UE is registered over 3GPP access;
  2. for 5GS services over non-3GPP access when the UE is registered over non-3GPP access; or
  3. for 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses.
If the UE has a valid 5G-GUTI, the UE shall populate the 5GS mobile identity IE with the valid 5G-GUTI. If the UE does not have a valid 5G-GUTI, the UE shall populate the 5GS mobile identity IE with its SUCI as follows:
  1. if timer T3519 is not running, generate a fresh SUCI as specified in TS 33.501, send a DEREGISTRATION REQUEST message with the SUCI, start timer T3519 and store the value of the SUCI sent in the DEREGISTRATION REQUEST message; and
  2. if timer T3519 is running, send a DEREGISTRATION REQUEST message with the stored SUCI.
If the UE does not have a valid 5G-GUTI and it does not have a valid SUCI, then the UE shall populate the5GS mobile identity IE with its PEI.
If the de-registration request is not due to switch off and the UE is in the state 5GMM-REGISTERED or 5GMM-REGISTERED-INITIATED, timer T3521 shall be started in the UE after the DEREGISTRATION REQUEST message has been sent. The UE shall enter the state 5GMM-DEREGISTERED-INITIATED.
If the UE is to be switched off, the UE shall try for a period of 5 seconds to send the DEREGISTRATION REQUEST message. During this period, the UE may be switched off as soon as the DEREGISTRATION REQUEST message has been sent.
Reproduction of 3GPP TS 24.501, Fig. 5.5.2.2.1.1: UE-initiated de-registration procedure
Up
5.5.2.2.2  UE-initiated de-registration procedure completionWord‑p. 368
When the DEREGISTRATION REQUEST message is received by the AMF, the AMF shall send a DEREGISTRATION ACCEPT message to the UE, if the De-registration type IE does not indicate "switch off". Otherwise, the procedure is completed when the AMF receives the DEREGISTRATION REQUEST message.
The UE, when receiving the DEREGISTRATION ACCEPT message, shall stop timer T3521, stop timer T3519 if running, and delete any stored SUCI.
5.5.2.2.3  UE-initiated de-registration procedure completion for 5GS services over 3GPP accessWord‑p. 368
If the access type in the DEREGISTRATION REQUEST message indicates that the de-registration procedure is for 3GPP access, the AMF shall trigger the SMF to perform a local release of the PDU session(s) established over 3GPP access, if any, for this UE. The UE shall perform a local release of the PDU session(s) established over 3GPP access, if any. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the AMF shall trigger SMF to perform release of user plane resources on 3GPP access, and the UE shall consider the user plane resources on 3GPP access as released. If there is an MA PDU session with user plane resources established on 3GPP access only, the AMF shall trigger the SMF to perform a local release of the MA PDU session, and the UE shall perform a local release of the MA PDU session. The UE is marked as inactive in the AMF for 5GS services for 3GPP access. The AMF shall enter the state 5GMM-DEREGISTERED for 3GPP access.
If the UE supports N1 mode only and the de-registration request is not due to switch off, then:
  1. if the de-registration procedure was performed due to disabling of 5GS services, then the UE shall enter the 5GMM-NULL state for 3GPP access;
  2. otherwise, the UE shall enter the 5GMM-DEREGISTERED state for 3GPP access.
If the access type indicates that the de-registration procedure is for 3GPP access or for 3GPP access and non-3GPP access, and the UE is operating in single-registration mode, it shall additionally proceed as specified in TS 24.301, subclause 5.5.2.2.2, for the case when the UE receives an EMM message DETACH ACCEPT. Furthermore, if the UE supports A/Gb or Iu mode, it shall disable the N1 mode capability for 3GPP access.
Up
5.5.2.2.4  UE-initiated de-registration procedure completion for 5GS services over non-3GPP accessWord‑p. 368
If the access type in the DEREGISTRATION REQUEST indicates that the de-registration procedure is for non-3GPP access, the AMF shall trigger SMF to perform a local release of the PDU session(s) established over non-3GPP access, if any, for this UE. The UE shall perform a local release of the PDU session(s) established over non-3GPP access, if any. If a PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated MBS sessions and the SMF shall consider the UE as removed from the associated MBS sessions. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the AMF shall trigger SMF to perform release of user plane resources on non-3GPP access, and the UE shall consider the user plane resources on non-3GPP access as released. If the UE has an MA PDU session with user plane resources established on non-3GPP access only, the AMF shall trigger the SMF to perform a local release of the MA PDU session, and the UE shall perform a local release of the MA PDU session. The UE is marked as inactive in the AMF for 5GS services for non-3GPP access. The AMF shall enter the state 5GMM-DEREGISTERED over non-3GPP access.
If the de-registration request is not due to switch off, the UE shall:
  1. if the de-registration procedure was performed due to disabling of 5GS services, enter the 5GMM-NULL state for non-3GPP access;
  2. otherwise, enter the 5GMM-DEREGISTERED state for non-3GPP access.
Up
5.5.2.2.5  UE-initiated de-registration procedure completion for 5GS services over both 3GPP access and non-3GPP accessWord‑p. 369
If the access type in the DEREGISTRATION REQUEST indicates that the de-registration procedure is for both 3GPP access and non-3GPP access when the UE is registered in the same PLMN over both accesses, the descriptions for UE-initiated de-registration procedure completion for 5GS services over 3GPP access and over non-3GPP access, as specified in subclauses 5.5.2.2.3 and 5.5.2.2.4, shall be followed.
Up
5.5.2.2.6  Abnormal cases in the UEWord‑p. 369
The following abnormal cases can be identified:
a)
Lower layer failure or release of the N1 NAS signalling connection before reception of DEREGISTRATION ACCEPT message.
The de-registration procedure shall be aborted and the UE proceeds as follows:
  1. if the de-registration procedure was performed due to disabling of 5GS services, the UE shall enter the 5GMM-NULL state; or
  2. if the de-registration type "normal de-registration" was requested for reasons other than disabling of 5GS services, the UE shall enter the 5GMM-DEREGISTERED state.
b)
The lower layers indicate that the access attempt is barred.
The UE shall not start the de-registration signalling procedure. The UE stays in the current serving cell and applies the normal cell reselection process. Receipt of the access barred indication shall not trigger the selection of a different core network type (EPC or 5GCN).
The UE may perform a local de-registration either immediately or after an implementation-dependent time.
The de-registration signalling procedure is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated.
ba)
The lower layers indicate that:
  1. access barring is applicable for all access categories except categories 0 and 2 and the access category with which the access attempt was associated is other than 0 and 2; or
  2. access barring is applicable for all access categories except category 0 and the access category with which the access attempt was associated is other than 0.
If the DEREGISTRATION REQUEST message has not been sent, the UE shall proceed as specified for case b. If the DEREGISTRATION REQUEST message has been sent, the UE shall proceed as specified for case a.
c)
T3521 timeout.
On the first four expiries of the timer, the UE shall retransmit the DEREGISTRATION REQUEST message and shall reset and restart timer T3521. On the fifth expiry of timer T3521, the de-registration procedure shall be aborted and the UE proceeds as follows:
  1. if the de-registration procedure was performed due to disabling of 5GS services, the UE shall enter the 5GMM-NULL state; or
  2. if the de-registration type "normal de-registration" was requested for reasons other than disabling of 5GS services, the UE shall enter the 5GMM-DEREGISTERED state.
d)
De-registration procedure collision.
De-registration containing de-registration type "switch off":
  • If the UE receives a DEREGISTRATION REQUEST message before the UE-initiated de-registration procedure has been completed, this message shall be ignored and the UE-initiated de-registration procedure shall continue.
Otherwise:
  • If the UE receives a DEREGISTRATION REQUEST message before the UE-initiated de-registration procedure has been completed, it shall treat the message as specified in subclause 5.5.2.3.2 with the following modification:
    • If the DEREGISTRATION REQUEST message received by the UE contains de-registration type "re-registration required", and the UE-initiated de-registration procedure is with de-registration type "normal de-registration", the UE need not initiate the registration procedure for initial registration.
e)
De-registration and 5GMM common procedure collision.
De-registration containing de-registration type "switch off":
  • If the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed, this message shall be ignored and the de-registration procedure shall continue.
Otherwise:
  • If the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed, both the 5GMM common procedure and the de-registration procedure shall continue; or
  • If the UE receives a DL NAS TRANSPORT message containing payload container type "Service-level-AA container" before the de-registration procedure has been completed, this message shall be ignored and the de-registration procedure shall continue.
f)
Change of cell into a new tracking area.
If a cell change into a new tracking area that is not in the stored TAI list occurs before the UE-initiated de-registration procedure is completed, the UE proceeds as follows:
  1. if the de-registration procedure was initiated for reasons other than removal of the USIM and the UE is to be switched off, the de-registration procedure shall be aborted and re-initiated after successfully performing a registration procedure for mobility or periodic update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message); or
  2. if the de-registration procedure was initiated due to removal of the USIM or the UE is to be switched off, the UE shall abort the de-registration procedure, perform a local de-registration and enter the state 5GMM-DEREGISTERED.
g)
Transmission failure of DEREGISTRATION REQUEST message indication with TAI change from lower layers.
If the current TAI is not in the TAI list, the UE proceeds as follows:
  1. if the de-registration procedure was initiated for reasons other than removal of the USIM and the UE is to be switched off, the de-registration procedure shall be aborted and re-initiated after successfully performing a registration procedure for mobility or periodic update; or
  2. if the de-registration procedure was initiated due to removal of the USIM or the UE is to be switched off, the UE shall abort the de-registration procedure, perform a local de-registration and enter the state 5GMM-DEREGISTERED.
If the current TAI is still part of the TAI list, the UE shall restart the de-registration procedure.
h)
Transmission failure of DEREGISTRATION REQUEST message indication without TAI change from lower layers.
The UE shall restart the de-registration procedure.
i)
The lower layers indicate that the RRC connection has been suspended.
De-registration containing de-registration type "switch off":
  • The UE may perform a local de-registration either immediately or after an implementation-dependent time.
Otherwise:
  • The UE shall wait for an implementation-dependent time and shall restart the de-registration procedure, if still needed, upon expiry of the implementation-dependent time.
For the cases a, f, g and i:
  • Timer T3521 shall be stopped if still running.
Up
5.5.2.2.7  Abnormal cases in the network sideWord‑p. 371
The following abnormal cases can be identified:
  1. De-registration request received in a cell belonging to an SNPN with a non-globally-unique SNPN identity for which the UE has no valid subscription
    If the UE initiates a de-registration procedure in a cell belonging to an SNPN with a non-globally-unique SNPN identity for which the UE has no valid subscription, and the de-registration procedure is not due to "switch off", the network shall initiate the de-registration procedure. The AMF shall send a DEREGISTRATION REQUEST message including the 5GMM cause #74 "Temporarily not authorized for this SNPN".
  2. De-registration request received in a cell belonging to an SNPN with a globally-unique SNPN identity for which the UE has no valid subscription
    If the UE initiates a de-registration procedure in a cell belonging to an SNPN with a globally-unique SNPN identity for which the UE has no valid subscription, and the de-registration procedure is not due to "switch off", the network shall initiate the de-registration procedure. The AMF shall send a DEREGISTRATION REQUEST message including the 5GMM cause #75 "Permanently not authorized for this SNPN".
  3. De-registration request received in a CAG cell and none of the CAG ID broadcasted by the CAG cell is included in the UE's "allowed CAG list" for the current PLMN
    If the UE initiates a de-registration procedure in a CAG cell and none of the CAG ID broadcasted by the CAG cell is included in the UE's "allowed CAG list" for the current PLMN and the de-registration procedure is not due to "switch off", the AMF shall initiate the de-registration procedure. The AMF shall send a DEREGISTRATION REQUEST message including the 5GMM cause #76 "Not authorized for this CAG or authorized for CAG cells only" if the UE supports CAG. Otherwise, the network shall operate as described in bullet g) of subclause 5.5.2.3.5.
  4. De-registration request received in a non-CAG cell from a UE whose "CAG information list" includes an entry associated with the current PLMN, where the entry contains an "indication that the UE is only allowed to access 5GS via CAG cells"
    If the UE initiates a de-registration procedure in a non-CAG cell from a UE whose "CAG information list" includes an entry associated with the current PLMN, where the entry contains an "indication that the UE is only allowed to access 5GS via CAG cells" and the de-registration procedure is not due to "switch off", the AMF shall initiate the de-registration procedure. The AMF shall send a DEREGISTRATION REQUEST message including the 5GMM cause #76 "Not authorized for this CAG or authorized for CAG cells only" if the UE supports CAG. Otherwise, the network shall operate as described in bullet g) of subclause 5.5.2.3.5.
  5. De-registration and registration procedure for initial registration collision
    If the network receives a REGISTRATION REQUEST message indicating either "initial registration" or "emergency registration" in the 5GS registration type IE from the UE before the UE-initiated de-registration procedure, which is not due to switch off, has been completed, the network shall abort the de-registration procedure and the registration procedure shall be progressed.
Up

5.5.2.3  Network-initiated de-registration procedureWord‑p. 372

5.5.2.3.1  Network-initiated de-registration procedure initiationWord‑p. 372
The network initiates the de-registration procedure by sending a DEREGISTRATION REQUEST message to the UE (see example in Figure 5.5.2.3.1.1).
The network may include a 5GMM cause IE to specify the reason for the DEREGISTRATION REQUEST message. The network shall start timer T3522. The network shall indicate whether re-registration is needed or not in the De-registration type IE. The network shall also indicate via the access type whether the de-registration procedure is:
  1. for 3GPP access only;
  2. for non-3GPP access only; or
  3. for 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN for both accesses.
If the network de-registration is triggered due to network slice-specific authentication and authorization failure or revocation as specified in subclause 4.6.2.4, then the network shall set the 5GMM cause value to #62 "No network slices available" in the DEREGISTRATION REQUEST message. In addition, if the UE supports extended rejected NSSAI, the AMF shall include the Extended rejected NSSAI IE in the DEREGISTRATION REQUEST message; otherwise the AMF shall include the Rejected NSSAI IE in the DEREGISTRATION REQUEST message.
If the UE supports extended rejected NSSAI and the network de-registration is triggered due to mobility management based network slice admission control as specified in subclause 4.6.2.5, then the network shall set the 5GMM cause value to #62 "No network slices available" in the DEREGISTRATION REQUEST message. In addition, the network may include a back-off timer value for each S-NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE of the DEREGISTRATION REQUEST message.
If the network de-registration is triggered for a UE supporting CAG due to CAG restrictions, the network shall set the 5GMM cause value to #76 "Not authorized for this CAG or authorized for CAG cells only" and should include the "CAG information list" in the CAG information list IE in the DEREGISTRATION REQUEST message.
If the network de-registration is triggered for a UE not supporting CAG due to CAG restrictions, the network shall operate as described in bullet g) of subclause 5.5.2.3.5.
If the network de-registration is triggered because the network determines that the UE is in a location where the network is not allowed to operate, see TS 23.502, the network shall set the 5GMM cause value in the DEREGISTRATION REQUEST message to #78 "PLMN not allowed to operate at the present UE location" and may include an information element in the DEREGISTRATION REQUEST message to indicate the country of the UE location.
If the network de-registration is triggered due to an unsuccessful outcome of an ongoing UUAA-MM procedure or UUAA revocation for a UE supporting UAS service requesting UAS services, or because the UE is not allowed to use UAS services via 5GS due to a change of the aerial UE subscription information, the network shall set the 5GMM cause value in the DEREGISTRATION REQUEST message to #79 "UAS services not allowed".
If the network de-registration is triggered for a UE supporting MINT due to a disaster condition no longer being applicable, the network shall set the 5GMM cause value to #11 "PLMN not allowed" and may include a disaster return wait range in the Disaster return wait range IE in the DEREGISTRATION REQUEST message.
The AMF shall trigger the SMF to release locally the PDU session(s) over the indicated access(es), if any, for the UE and enter state 5GMM-DEREGISTERED-INITIATED. If a PDU session is associated with one or more MBS sessions, the SMF shall consider the UE as removed from the associated MBS sessions.
Reproduction of 3GPP TS 24.501, Fig. 5.5.2.3.1.1: Network-initiated de-registration procedure
Up
5.5.2.3.2  Network-initiated de-registration procedure completion by the UEWord‑p. 373
Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration required" and the de-registration request is for 3GPP access, the UE shall perform a local release of the PDU sessions over 3GPP access, if any. If a PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated MBS sessions. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the UE shall perform a local release of the user plane resources on 3GPP access. If there is an MA PDU session with user plane resources established on 3GPP access only, the UE shall perform a local release of the MA PDU session. The UE shall stop the timer(s) T3346, T3396, T3584, T3585 and 5GSM back-off timer(s) not related to congestion control (see subclause 6.2.12), if running. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for 3GPP access. Furthermore, the UE shall, after the completion of the de-registration procedure, and the release of the existing NAS signalling connection, initiate an initial registration. The UE should also re-establish any previously established PDU sessions over 3GPP access. For any previously established MA PDU sessions with user plane resources established on both accesses the UE should also re-establish the user plane resources over 3GPP access, and for any previously established MA PDU sessions with user plane resources established only on the 3GPP access the UE should re-establish the MA PDU session over 3GPP access.
Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration required" and the de-registration request is for non-3GPP access, the UE shall perform a local release of the PDU sessions over non-3GPP access, if any. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the UE shall perform a local release of the user plane resources on non-3GPP access. If there is an MA PDU session with user plane resources established on non-3GPP access only, the UE shall perform a local release of the MA PDU session. The UE shall stop the timer(s) T3346, T3396, T3584 and T3585, if it is running. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for non-3GPP access. Furthermore, the UE shall, after the completion of the de-registration procedure, and the release of the existing NAS signalling connection, initiate an initial registration over non-3GPP. The UE should also re-establish any previously established PDU sessions over non-3GPP access. For any previously established MA PDU sessions with user plane resources established on both accesses the UE should also re-establish the user plane resources over non-3GPP access, and for any previously established MA PDU sessions with user plane resources established only on the non-3GPP access the UE should re-establish the MA PDU session over 3GPP access.
Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration required" and the de-registration request is for both 3GPP access and non-3GPP access when the UE is registered in the same PLMN for both accesses, the UE shall perform a local release of the MA PDU sessions and PDU sessions over both 3GPP access and non-3GPP access, if any. The UE shall stop the timer(s) T3346, T3396, T3584 and T3585, if it is running. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for both 3GPP access and non-3GPP access. Furthermore, the UE shall, after the completion of the de-registration procedure, and the release of the existing NAS signalling connection, initiate an initial registration over both 3GPP access and non-3GPP access. The UE should also re-establish any previously established PDU sessions over both 3GPP access and non-3GPP access. For any previously established MA PDU sessions the UE should also re-establish the the MA PDU session and the user plane resources which were established previously.
Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration not required" and the de-registration request is for 3GPP access, the UE shall perform a local release of the PDU sessions over 3GPP access, if any. If a PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated MBS sessions. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the UE shall perform a local release of the user plane resources on 3GPP access. If there is an MA PDU session with user plane resources established on 3GPP access only, the UE shall perform a local release of the MA PDU session. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for 3GPP access.
Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration not required" and the de-registration request is for non-3GPP access, the UE shall perform a local release of the PDU sessions over non-3GPP access, if any. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the UE shall perform a local release of the user plane resources on non-3GPP access. If there is an MA PDU session with user plane resources established on non-3GPP access only, the UE shall perform a local release of the MA PDU session. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for non-3GPP access.
Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message indicates "re-registration not required" and the de-registration request is for both 3GPP access and non-3GPP access when the UE is registered in the same PLMN for both accesses, the UE shall perform a local release of the MA PDU sessions and PDU sessions over both 3GPP access and non-3GPP access, if any. The UE shall send a DEREGISTRATION ACCEPT message to the network and enter the state 5GMM-DEREGISTERED for both 3GPP access and non-3GPP access.
Upon receiving the DEREGISTRATION REQUEST message, if the DEREGISTRATION REQUEST message includes the rejected NSSAI, the UE takes the following actions based on the rejection cause in the rejected S-NSSAI(s):
"S-NSSAI not available in the current PLMN or SNPN"
The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN or SNPN as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN until switching off the UE, the UICC containing the USIM is removed, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2.
"S-NSSAI not available in the current registration area"
The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as described in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area until switching off the UE, the UE moving out of the current registration area, the UICC containing the USIM is removed, an entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2.
"S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization"
The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the failed or revoked NSSAA as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed or deleted as described in subclause 4.6.1 and 4.6.2.2.
"S-NSSAI not available due to maximum number of UEs reached"
The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN over the current access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2.
If there is one or more S-NSSAIs in the rejected NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached", then for each S-NSSAI, the UE shall behave as follows:
  1. stop the timer T3526 associated with the S-NSSAI, if running;
  2. start the timer T3526 with:
    1. the back-off timer value received along with the S-NSSAI, if a back-off timer value is received along with the S-NSSAI that is neither zero nor deactivated; or
    2. an implementation specific back-off timer value, if no back-off timer value is received along with the S-NSSAI; and
  3. remove the S-NSSAI from the rejected NSSAI for the maximum number of UEs reached when the timer T3526 associated with the S-NSSAI expires.
Upon sending a DEREGISTRATION ACCEPT message, the UE shall delete the rejected NSSAI as specified in subclause 4.6.2.2.
If the de-registration type indicates "re-registration required", then the UE shall ignore the 5GMM cause IE if received.
If the de-registration type indicates "re-registration not required", the UE shall take the actions depending on the received 5GMM cause value:
#3 (Illegal UE);
#6 (Illegal ME)
The message was received via 3GPP access and the UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI.
In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.19a.1;
In case of SNPN, if the UE does not support access to an SNPN using credentials from a credentials holder, the UE shall consider the entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid until the UE is switched off, the entry is updated or the timer T3245 expires as described in clause 5.3.19a.2. In case of SNPN, if the UE supports access to an SNPN using credentials from a credentials holder, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in clause 5.3.19a.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.19a.2.
The UE shall delete the list of equivalent PLMNs (if any) and shall enter the state 5GMM-DEREGISTERED.NO-SUPI.
The UE shall delete the 5GMM parameters stored in non-volatile memory of the ME as specified in Annex C.
If the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, TAI list and eKSI as specified in TS 24.301 for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a in TS 24.301.
If the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value.
#7 (5GS services not allowed).
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI.
In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.19a.1;
In case of SNPN, if the UE does not support access to an SNPN using credentials from a credentials holder, the UE shall consider the entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for 5GS services until the UE is switched off, or the entry is updated or the timer T3245 expires as described in clause 5.3.19a.2. In case of SNPN, if the UE supports access to an SNPN using credentials from a credentials holder, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in clause 5.3.19a.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.19a.2.
The UE shall enter the state 5GMM-DEREGISTERED.NO-SUPI.
The UE shall delete the 5GMM parameters stored in non-volatile memory of the ME as specified in Annex C.
If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in TS 24.301 for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required".
If the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value.
#11 (PLMN not allowed).
This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4.
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs, shall reset the registration attempt counter. For 3GPP access the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH, and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE.
The UE shall store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A and if the UE is configured to use timer T3245 then the UE shall start timer T3245 and proceed as described in clause 5.3.19a.1.
For 3GPP access the UE shall perform a PLMN selection according to TS 23.122, and for non-3GPP access the UE shall perform network selection as defined in TS 24.502.
If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in TS 24.301 for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required".
If the UE also supports the registration procedure over the other access to the same PLMN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value.
If the UE receives the Disaster return wait range IE in the DEREGISTRATION REQUEST message and the UE supports MINT, the UE shall delete the disaster return wait range stored in the ME, if any, and store the disaster return wait range included in the Disaster return wait range IE in the ME.
#12 (Tracking area not allowed).
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall reset the registration attempt counter and shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE.
If the UE is not operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service". Otherwise, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, the selected entry of the "list of subscriber data" or the selected PLMN subscription.
If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters, EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in TS 24.301 for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required".
#13 (Roaming not allowed in this tracking area).
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs (if available), reset the registration attempt counter. For 3GPP access the UE shall change to state 5GMM-DEREGISTERED.PLMN-SEARCH, and for non-3GPP access the UE shall change to state 5GMM-DEREGISTERED.LIMITED-SERVICE.
If the UE is not operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming". Otherwise, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, the selected entry of the "list of subscriber data" or the selected PLMN subscription.
For 3GPP access the UE shall perform a PLMN selection or SNPN selection according to TS 23.122, and for non-3GPP access the UE shall perform network selection as defined in TS 24.502.
If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in TS 24.301 for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required".
#15 (No suitable cells in tracking area).
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall reset the registration attempt counter and shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE.
If the UE is not operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming". Otherwise the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, the selected entry of the "list of subscriber data" or the selected PLMN subscription.
The UE shall search for a suitable cell in another tracking area according to TS 38.304 or TS 36.304.
If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in TS 24.301 for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required".
If received over non-3GPP access and de-registration request is for non-3GPP access only, the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.2.3.4.
#22 (Congestion).
If the T3346 value IE is present in the DEREGISTRATION REQUEST message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.2.3.4.
The UE shall stop timer T3346 if it is running, set the 5GS update status to 5U2 NOT UPDATED, reset the registration attempt counter and enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION.
The UE shall start timer T3346 with the value provided in the T3346 value IE.
If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall set the EPS update status to EU2 NOT UPDATED, reset the attach attempt counter and shall enter the state EMM-DEREGISTERED.
#27 (N1 mode not allowed).
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter and shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE.
The UE shall disable the N1 mode capability for both 3GPP access and non-3GPP access (see subclause 4.9).
If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter and enter the state EMM-DEREGISTERED.
#62 (No network slices available).
The UE shall set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED.NORMAL-SERVICE or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter.
The UE receiving the rejected NSSAI in the DEREGISTRATION REQUEST message takes the following actions based on the rejection cause in the rejected S-NSSAI(s):
"S-NSSAI not available in the current PLMN or SNPN"
The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN or SNPN as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current PLMN or SNPN until switching off the UE, the UICC containing the USIM is removed, an entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed or deleted as described in subclause 4.6.2.2.
"S-NSSAI not available in the current registration area"
The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as described in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area until switching off the UE, the UE moving out of the current registration area, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed or deleted as described in subclause 4.6.2.2.
"S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization"
The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the failed or revoked NSSAA as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed or deleted as described in subclause 4.6.1 and 4.6.2.2.
"S-NSSAI not available due to maximum number of UEs reached"
The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN over the current access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2.
If the UE has an allowed NSSAI or configured NSSAI that contains S-NSSAI(s) which are not included any of the rejected NSSAI for the current PLMN or SNPN, the rejected NSSAI for the current registration area, the rejected NSSAI for the failed or revoked NSSAA, and rejected NSSAI for the maximum number of UEs reached, the UE may stay in the current serving cell, apply the normal cell reselection process and start an initial registration with a requested NSSAI that includes any S-NSSAI from the allowed NSSAI or the configured NSSAI that is neither in the rejected NSSAI for the PLMN or SNPN nor in the rejected NSSAI for the current registration area nor in the rejected NSSAI for the failed or revoked NSSAA nor rejected NSSAI for the maximum number of UEs reached. Otherwise the UE may perform a PLMN selection or SNPN selection according to TS 23.122 and additionally, the UE may disable the N1 mode capability for the current PLMN or SNPN if the UE does not have an allowed NSSAI and each S-NSSAI in configured NSSAI, if available, was rejected with cause "S-NSSAI not available in the current PLMN or SNPN" or "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" or "S-NSSAI not available due to maximum number of UEs reached" as described in subclause 4.9.
If the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN and has a default configured NSSAI containing one or more S-NSSAIs that are not included in any of the rejected NSSAI for the PLMN or SNPN, the rejected NSSAI for the current registration area, the rejected NSSAI for the failed or revoked NSSAA, and rejected NSSAI for the maximum number of UEs reached,
  1. the UE may stay in the current serving cell, apply the normal cell reselection process, and start an initial registration with a requested NSSAI with that default configured NSSAI; or
  2. if all the S-NSSAI(s) in the default configured NSSAI are rejected and at least one S-NSSAI is rejected due to "S-NSSAI not available in the current registration area",
    1. if the UE is not operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; or
    2. if the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE.
Otherwise, the UE may perform a PLMN selection or SNPN selection according to TS 23.122 and additionally, the UE may disable the N1 mode capability for the current PLMN or SNPN if each S-NSSAI in the default configured NSSAI was rejected with cause "S-NSSAI not available in the current PLMN or SNPN" or "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" as described in subclause 4.9.
If the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN and has rejected NSSAI for the reached maximum number of UEs, and the UE wants to obtain services in the current serving cell without performing a PLMN selection or SNPN selection, the UE may stay in the current serving cell and attempt to use the rejected S-NSSAI(s) for the maximum number of UEs reached in the current serving cell after the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2.
If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the attach attempt counter and enter the state EMM-DEREGISTERED.
#72 (Non-3GPP access to 5GCN not allowed).
If received over non-3GPP access when the UE is registered over non-3GPP access, or received over 3GPP access and de-registration request is for non-3GPP access when the UE is registered in the same PLMN for both accesses, the UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI for non-3GPP access. Additionally, the UE shall reset the registration attempt counter and enter the state 5GMM-DEREGISTERED for non-3GPP access.
The UE shall disable the N1 mode capability for non-3GPP access (see subclause 4.9.3).
As an implementation option, if the UE is not currently registered over 3GPP access, the UE may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to TS 23.122.
If received over 3GPP access and de-registration request is for 3GPP access only, the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.2.3.4.
#74 (Temporarily not authorized for this SNPN).
5GMM cause #74 is only applicable when received from a cell belonging to an SNPN. 5GMM cause #74 received from a cell not belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4.
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall reset the registration attempt counter and shall store the SNPN identity in the "temporarily forbidden SNPNs" list for the specific access type for which the message was received and, if the UE supports access to an SNPN using credentials from a credentials holder, the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE is not registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to TS 23.122. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection for onboarding services according to TS 23.122.
#75 (Permanently not authorized for this SNPN).
5GMM cause #75 is only applicable when received from a cell belonging to an SNPN with a globally-unique SNPN identity. 5GMM cause #75 received from a cell not belonging to an SNPN or a cell belonging to an SNPN with a non-globally-unique SNPN identity is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4.
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall reset the registration attempt counter and store the SNPN identity in the "permanently forbidden SNPNs" list for the specific access type for which the message was received and, if the UE supports access to an SNPN using credentials from a credentials holder, the selected entry of the "list of subscriber data" or the selected PLMN subscription. The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to TS 23.122.
#76 (Not authorized for this CAG or authorized for CAG cells only).
This cause value received via non-3GPP access or from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4.
The UE shall set the 5GS update status to 5U3.ROAMING NOT ALLOWED, store the 5GS update status according to clause 5.1.3.2.2, and reset the registration attempt counter.
If 5GMM cause #76 is received from:
  1. a CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE included in the DEREGISTRATION REQUEST message, the UE shall:
    1. replace the "CAG information list" stored in the UE with the received CAG information list IE when received in the HPLMN or EHPLMN;
    2. replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE when the UE receives the CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or
    3. remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE does not contain the serving VPLMN's entry.
    Otherwise, the UE shall delete the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN. In the case the "allowed CAG list" for the current PLMN only contains a range of CAG-IDs, how the UE deletes the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN is up to UE implementation. In addition:
    1. if the entry in the "CAG information list" for the current PLMN does not include an "indication that the UE is only allowed to access 5GS via CAG cells" or if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and the updated "allowed CAG list" for the current PLMN includes one or more CAG-IDs, then the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to TS 38.304 or TS 36.304 with the updated "CAG information list"; or
    2. if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and the updated "allowed CAG list" for the current PLMN does not include any CAG-ID, then the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in TS 23.122 with the updated "CAG information list".
  2. a non-CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE included in the DEREGISTRATION REQUEST message, the UE shall:
    1. replace the "CAG information list" stored in the UE with the received CAG information list IE when received in the HPLMN or EHPLMN;
    2. replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE when the UE receives the CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or
    3. remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE does not contain the serving VPLMN's entry.
    Otherwise, the UE shall store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN, if any. If the "CAG information list" stored in the UE does not include the current PLMN's entry, the UE shall add an entry for the current PLMN to the "CAG information list" and store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN. If the UE does not have a stored "CAG information list", the UE shall create a new "CAG information list" and add an entry with an "indication that the UE is only allowed to access 5GS via CAG cells" for the current PLMN.
In addition:
  1. if the "allowed CAG list" for the current PLMN includes one or more CAG-IDs, then the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to TS 38.304 with the updated CAG information; or
  2. if the "allowed CAG list" for the current PLMN does not include any CAG-ID, then the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in TS 23.122 with the updated "CAG information list".
If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED, reset the attach attempt counter and enter the state EMM-DEREGISTERED.
#77 (Wireline access area not allowed).
5GMM cause #77 is only applicable when received from a wireline access network by the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device). 5GMM cause #77 received from a 5G access network other than a wireline access network and 5GMM cause #77 received by the W-AGF acting on behalf of the FN-BRG are considered as abnormal cases and the behaviour of the UE is specified in subclause 5.5.2.3.4.
When received over wireline access network, the 5G-RG and the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2), shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI, shall reset the registration attempt counter, shall enter the state 5GMM-DEREGISTERED and shall act as specified in subclause 5.3.23.
#78 (PLMN not allowed to operate at the present UE location).
This cause value received from a non-satellite NG-RAN cell is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4.
The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location" and shall start a corresponding timer instance (see subclause 4.23.2). The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to TS 23.122.
#79 (UAS services not allowed).
  • A UE which is not a UE supporting UAS services receiving this cause value shall considered it as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4.
    A UE supporting UAS service shall set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED.NORMAL-SERVICE or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. The UE shall not attempt to register for UAS services to the current PLMN until the UE is switched off or the UICC containing the USIM is removed.
#93 (Onboarding services terminated).
If the UE is not registered for onboarding services in SNPN, this cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4.
If the UE is not operating in SNPN access operation mode, and its subscription is not only for configuration of SNPN subscription parameters in PLMN via the user plane, this cause value received from a cell belonging to an PLMN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.2.3.4.
If the UE is not operating in SNPN access operation mode, and its subscription is only for configuration of SNPN subscription parameters in PLMN via the user plane, it shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to TS 23.122.
If the UE is operating in SNPN access operation mode, the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to TS 23.122.
Up
5.5.2.3.3  Network-initiated de-registration procedure completion by the networkWord‑p. 383
The network shall stop timer T3522 upon receipt of the DEREGISTRATION ACCEPT message. The network shall enter state 5GMM-DEREGISTERED for 3GPP access if the de-registration request is for 3GPP access. The network shall enter state 5GMM-DEREGISTERED for non-3GPP access if the de-registration request is for non-3GPP access. The network shall enter state 5GMM-DEREGISTERED for both 3GPP access and non-3GPP access if the de-registration request is for both 3GPP access and non-3GPP access.
5.5.2.3.4  Abnormal cases in the UEWord‑p. 383
The following abnormal cases can be identified:
  1. Transmission failure of DEREGISTRATION ACCEPT message indication from lower layers.
    The de-registration procedure shall be progressed and the UE shall send the DEREGISTRATION ACCEPT message.
  2. DEREGISTRATION REQUEST, other 5GMM cause values than those treated in subclause 5.5.2.3.2, cases of 5GMM cause value#11, #15, #22, #72, #74, #75, #76, #77, #78, #79 and #XX that are considered as abnormal cases according to subclause 5.5.2.3.2 or no 5GMM cause IE is included, and the De-registration type IE indicates "re-registration not required".
    The UE shall delete 5G-GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs (if any), ngKSI, shall set the 5GS update status to 5U2 NOT UPDATED and shall start timer T3502.
    A UE not supporting S1 mode may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection or SNPN selection according to TS 23.122; otherwise the UE shall enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION.
    If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall:
    • enter the state 5GMM-DEREGISTERED and attempt to select E-UTRAN radio access technology and proceed with the appropriate EMM specific procedures. In this case, the UE may disable the N1 mode capability (see subclause 4.9); or
    • enter the state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to TS 23.122.
    If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall set the EPS update status to EU2 NOT UPDATED, enter the state EMM-DEREGISTERED and shall delete the EMM parameters 4G-GUTI, last visited registered TAI, TAI list and eKSI.
Up
5.5.2.3.5  Abnormal cases in the network sideWord‑p. 383
The following abnormal cases can be identified:
  1. T3522 time-out
    On the first expiry of the timer, the network shall retransmit the DEREGISTRATION REQUEST message and shall start timer T3522. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3522, the de-registration procedure shall be aborted. The network shall change to the state 5GMM-DEREGISTERED for the access type which the de-registration procedure is intended for.
  2. Lower layer failure
    The de-registration procedure is aborted. The network shall change to the state 5GMM-DEREGISTERED for the access type which the de-registration procedure is intended for.
  3. De-registration procedure collision
    If the network receives a DEREGISTRATION REQUEST message with "switch off" indication, before the network-initiated de-registration procedure has been completed, both procedures shall be considered completed.
    If the network receives a DEREGISTRATION REQUEST message without "switch off" indication, before the network-initiated de-registration procedure has been completed, the network shall send a DEREGISTRATION ACCEPT message to the UE.
  4. De-registration and registration procedure for initial registration collision
    If the network receives a REGISTRATION REQUEST message indicating either "initial registration" or "emergency registration" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the network shall abort the de-registration procedure and the registration procedure shall be progressed after the PDU sessions associated with the access type the REGISTRATION REQUEST message is sent over have been deleted.
  5. De-registration and registration procedure for mobility and periodic registration update collision
    If the network sent a DEREGISTRATION REQUEST message without 5GMM cause value #11, #12, #13 or #15 and the network receives a REGISTRATION REQUEST message indicating either "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the de-registration procedure shall be progressed, i.e. the REGISTRATION REQUEST message shall be ignored.
    If the network sent a DEREGISTRATION REQUEST message with 5GMM cause value #11, #12, #13 or #15 and the network receives a REGISTRATION REQUEST message indicating either "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the de-registration procedure shall be aborted and the registration procedure shall be progressed.
  6. De-registration and service request procedure collision
    If the network receives a SERVICE REQUEST message or a CONTROL PLANE SERVICE REQUEST message before the network-initiated de-registration procedure has been completed (e.g. the DEREGISTRATION REQUEST message is pending to be sent to the UE), the network shall progress the de-registration procedure.
  7. De-registration requested for a UE not supporting CAG due to CAG restrictions
    Based on operator policy, if the network-initiated de-registration procedure is triggered for a UE not supporting CAG due to CAG restrictions, the network shall send the DEREGISTRATION REQUEST message including a 5GMM cause value other than the 5GMM cause #76 (Not authorized for this CAG or authorized for CAG cells only).
Up

5.5.3  eCall inactivity procedureWord‑p. 385

The eCall inactivity procedure is performed only in 3GPP access and applicable only to a UE configured for eCall only mode as specified in TS 31.102. The procedure shall be started when:
  1. the UE is in any 5GMM-REGISTERED substate except substates 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.NO-CELL-AVAILABLE;
  2. the UE is in 5GMM-IDLE mode; and
  3. one of the following conditions applies:
    1. timer T3444 expires or is found to have already expired and timer T3445 is not running;
    2. timer T3445 expires or is found to have already expired and timer T3444 is not running; or
    3. timers T3444 and T3445 expire or are found to have already expired.
The UE shall then perform the following actions:
  1. stop other running timers (e.g. T3511, T3512);
  2. if the UE is currently registered to the network for 5GS services, perform a de-registration procedure;
  3. delete any 5G-GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, and ngKSI; and
  4. enter 5GMM-DEREGISTERED.eCALL-INACTIVE state.
Up

Up   Top   ToC