3GPP 24.501 v20.0.0 — the document's own text

5.5.2.3.2 Network-initiated de-registration procedure completion by the UE

Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).

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 multicast MBS sessions, the UE shall locally leave the associated multicast 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. If the MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. The UE shall stop the timer(s) T3346, T3396, T3584, T3585 and 5GSM back-off timer(s) not related to congestion control (see clause 6.2.12), if running. If the UE is operating in single-registration mode, the UE shall also stop the ESM back-off timer(s) not related to congestion control (see clause 6.3.6 in 3GPP TS 24.301 [15]), 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, if any Tsor-cm timer(s) were running and have stopped, the UE shall attempt to obtain service on a higher priority PLMN (see 3GPP TS 23.122 [5]) on 3GPP access, otherwise 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 a PDN connection as a user-plane resource and user plane resources established on non-3GPP access, 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 non-3GPP access, and for any previously established MA PDU sessions with a PDN connection as a user-plane resource and user plane resources established on non-3GPP access the UE should re-establish the user plane resources over non-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. If an MA PDU session or a PDU sessions is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. 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, if any Tsor-cm timer(s) were running and have stopped, the UE shall attempt to obtain service on a higher priority PLMN (see 3GPP TS 23.122 [5]) on 3GPP access, otherwise 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 MA PDU session and the user plane resources which were established previously.

NOTE 1: When the De-registration type IE indicates "re-registration required", user interaction is necessary in some cases when the UE cannot re-establish the PDU session (s), if any, automatically.

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 multicast MBS sessions, the UE shall locally leave the associated multicast 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. If the MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. 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 a PDN connection as a user-plane resource and user plane resources established on non-3GPP access, 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. If an MA PDU session or a PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. 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 clause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over any access 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, if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, the selected entry of the "list of subscriber data" is updated, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both or the rejected S-NSSAI(s) are removed as described in clause 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 clause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area over the current access 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 clause 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 clause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN 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 as described in clause 4.6.1 and 4.6.2.2.

"S-NSSAI not available due to maximum number of UEs reached"

Unless the back-off timer value received along with the S-NSSAI is zero, the UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached as specified in clause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN 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 clauses 4.6.1 and 4.6.2.2.

NOTE 2: If the back-off timer value received along with the S-NSSAI in the rejected NSSAI for the maximum number of UEs reached is zero as specified in clause 10.5.7.4a of 3GPP TS 24.008 [12], the UE does not consider the S-NSSAI as the rejected S-NSSAI.

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:

stop the timer T3526 associated with the S-NSSAI, if running;
start the timer T3526 with:

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
an implementation specific back-off timer value, if no back-off timer value is received along with the S-NSSAI; and

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 clause 4.6.2.2.

Regardless of the 5GMM cause value received in the DEREGISTRATION REQUEST message via satellite NG-RAN,

-- if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE and the Access technology utilization control IE is not included in the DEREGISTRATION REQUEST message, the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for roaming"; and

if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE in the DEREGISTRATION REQUEST message, the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for regional provision of service".

Upon receiving the DEREGISTRATION REQUEST message for the 5G-RG, the 5G-RG shall delete the contexts of the AUN3 devices behind the 5G-RG, if any.

NOTE 2A: The 5G-RG can identify whether the received DEREGISTRATION REQUEST message is targeting the 5G-RG or an AUN3 device behind the 5G-RG via W-CP protocol as specified in 3GPP TS 23.316 [6D].

If the De-registration type IE indicates "re-registration required", then the UE shall ignore the 5GMM cause IE if received.

If the De-registration type IE 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 UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to clause 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 is not registered for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected 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, equivalent SNPNs, or both, 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.

If the UE is not registered for onboarding services in SNPN, the UE shall delete the list of equivalent PLMNs (if any) or the list of equivalent SNPNs (if any), and shall enter the state 5GMM-DEREGISTERED.NO-SUPI.

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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, TAI list and eKSI as specified in 3GPP TS 24.301 [15] 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 3GPP TS 24.301 [15].

If the UE is registered for onboarding services in SNPN, the UE shall reset the registration attempt counter, store the SNPN identity in the "permanently forbidden SNPN for onboarding services in SNPN" list, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122 [5].

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 clause 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 is not registered for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected 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 is not registered for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, 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.

If the UE is not registered for onboarding services in SNPN, the UE shall enter the state 5GMM-DEREGISTERED.NO-SUPI.

If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and 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 3GPP TS 24.301 [15] 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 is registered for onboarding services in SNPN, the UE shall reset the registration attempt counter, store the SNPN identity in the "permanently forbidden SNPNs for onboarding services in SNPN" list, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122 [5].

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 and the UE is operating in SNPN access operation mode is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.2.3.4.

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to clause 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 clause 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 3GPP TS 23.122 [5], and for non-3GPP access the UE shall perform network selection as defined in 3GPP TS 24.502 [18].

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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 3GPP TS 24.301 [15] 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).

If the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE is not included in the DEREGISTRATION REQUEST message, 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 the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5] clause 3.9), 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 the selected entry of the "list of subscriber data" or the selected PLMN subscription, along with the GIN(s) broadcasted by the SNPN if any.

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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 3GPP TS 24.301 [15] 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 clause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI, ngKSI, and the list of equivalent PLMNs (if available) or the list of equivalent SNPNs (if available). The UE shall 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 and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the DEREGISTRATION REQUEST message, 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 the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5] clause 3.9), the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, along with the GIN(s) broadcasted by the SNPN if any.

For 3GPP access the UE shall perform a PLMN selection or SNPN selection according to 3GPP TS 23.122 [5], and for non-3GPP access the UE shall perform network selection as defined in 3GPP TS 24.502 [18].

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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 3GPP TS 24.301 [15] 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 PLMN of the AMF is an allowable PLMN of the UE and 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.

#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 clause 5.1.3.2.2) and shall delete any last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI 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 Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the DEREGISTRATION REQUEST message and Access technology utilization control IE is not included in the DEREGISTRATION REQUEST message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming".

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 the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5] clause 3.9), the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, along with the GIN(s) broadcasted by the SNPN if any.

If the Access technology utilization control IE is present in DEREGISTRATION REQUEST message, the UE shall store the received access technology utilization control information together with the PLMN identity of the current PLMN in the list of "PLMNs with associated access technology restrictions" as defined in as specified in clause 4.2A.2.

The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304 [28] or 3GPP TS 36.304 [25C].

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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 3GPP TS 24.301 [15] 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 clause 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 clause 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 de-registration request is for 3GPP access only or for both 3GPP access and non-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 clause 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 clause 4.9).

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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.

#36 (IAB-node operation not authorized).

This cause value is only applicable when received over 3GPP access by a UE operating as an IAB-node. This cause value received from a 5G access network other than 3GPP access or received by a UE not operating as an IAB-node is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.2.3.4.

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI.

If:

the UE is not operating in SNPN access operation mode,

the UE shall delete the list of equivalent PLMNs and reset the registration attempt counter and store the PLMN identity in the forbidden PLMN list as specified in clause 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. The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122 [5]; and
If the UE is operating in single-registration mode, the UE shall in addition 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 3GPP TS 24.301 [15] for the case when DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required"; or

the UE is operating in SNPN access operation mode,

the UE shall reset the registration attempt counter and store the SNPN identity in the "temporarily forbidden SNPNs" list for 3GPP access and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription or "temporarily forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5]) for 3GPP access and the selected entry of the "list of subscriber data" or the selected PLMN subscription or the selected PLMN subscription or in the "temporarily forbidden SNPNs for onboarding services in SNPN" list, if the UE is performing initial registration for onboarding services in SNPN, for 3GPP access. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "temporarily forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" (if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5]) along with the GIN(s) broadcasted by the SNPN if any, for 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 3GPP TS 23.122 [5].

#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 clause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current PLMN or SNPN over any access 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 as described in clause 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 clause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area over the current access 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 as described in clause 4.6.2.2.

"S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization"

"S-NSSAI not available due to maximum number of UEs reached"

NOTE 3: If the back-off timer value received along with the S-NSSAI in the rejected NSSAI for the maximum number of UEs reached is zero as specified in clause 10.5.7.4a of 3GPP TS 24.008 [12], the UE does not consider the S-NSSAI as the rejected S-NSSAI.

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:

stop the timer T3526 associated with the S-NSSAI, if running;
start the timer T3526 with:

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
an implementation specific back-off timer value, if no back-off timer value is received along with the S-NSSAI; and

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.

If the UE has an allowed NSSAI or configured NSSAI that contains S-NSSAI(s) which are not included in the rejected NSSAI, 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 not in the rejected NSSAI. Otherwise the UE may perform a PLMN selection or SNPN selection according to 3GPP TS 23.122 [5] 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" as described in clause 4.9.

If the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and,

if at least one S-NSSAI in the default configured NSSAI is not rejected, 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
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",

if the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the DEREGISTRATION REQUEST message, the UE shall store the TAI(s) belonging to current registration area in the list of "5GS forbidden tracking areas for roaming", memorize the TAI(s) belonging to current registration area were stored in the list of "5GS forbidden tracking areas for roaming" for S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area not belonging to current registration area according to 3GPP TS 38.304 [28] or 3GPP TS 36.304 [25C]; or
if the UE is operating in SNPN access operation mode, the UE shall store the TAI(s) belonging to current registration area in the list of "5GS forbidden tracking areas for roaming", memorize the TAI(s) belonging to current registration area were stored in the list of "5GS forbidden tracking areas for roaming" for S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area not belonging to current registration area according to 3GPP TS 38.304 [28] or 3GPP TS 36.304 [25C].

otherwise, the UE may perform a PLMN selection or SNPN selection according to 3GPP TS 23.122 [5] 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 clause 4.9.

If:

the UE has allowed NSSAI for the current PLMN or SNPN or configured NSSAI for the current PLMN or SNPN or both and all the S-NSSAIs included in the allowed NSSAI or the configured NSSAI or both are rejected; or
the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and all the S-NSSAIs included in the default configured NSSAI are rejected,

and the UE has rejected NSSAI for the maximum number of UEs reached, 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 clause 4.6.2.2.

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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 clause 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.

NOTE 4: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see clauses 4.7.2 and 5.1.3).

The UE shall disable the N1 mode capability for non-3GPP access (see clause 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 3GPP TS 23.122 [5].

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 clause 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 and the UE is operating in SNPN access operation mode. 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 clause 5.5.2.3.4.

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list, ngKSI and the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and shall store the SNPN identity in the "temporarily forbidden SNPNs" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5]) for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription, or in the "temporarily forbidden SNPNs for onboarding services in SNPN" list, if the UE is registered for onboarding services in SNPN, for the specific access type for which the message was received. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "temporarily forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" (if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5]) along with the GIN(s) broadcasted by the SNPN if any, for 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 3GPP TS 23.122 [5]. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122 [5].

#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 and the UE is operating in SNPN access operation mode. 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 clause 5.5.2.3.4.

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list, ngKSI and the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and store the SNPN identity in the "permanently forbidden SNPNs" list or "permanently forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5]) for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription, or in the "permanently forbidden SNPNs for onboarding services in SNPN" list, if the UE is registered for onboarding services in SNPN, for the specific access type for which the message was received. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "permanently forbidden SNPNs for access for localized services in SNPN" (if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122 [5]) along with the GIN(s) broadcasted by the SNPN if any, for 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 3GPP TS 23.122 [5]. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122 [5].

#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 and the UE is operating in SNPN access operation mode is considered as an abnormal case and the behaviour of the UE is specified in clause 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:

a CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the DEREGISTRATION REQUEST message, the UE shall:

replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN;
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 or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or

NOTE 5: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored.

iii) remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE or the Extended 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, if the CAG-ID(s) are authorized based on the "Allowed CAG list". 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:

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 one or more CAG-ID(s) are authorized based on the updated "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304 [28] or 3GPP TS 36.304 [25C] with the updated "CAG information list";
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 no CAG-ID is authorized based on the updated "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122 [5] with the updated "CAG information list"; or

iii) if the "CAG information list" does not include an entry for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304 [28] or 3GPP TS 36.304 [25C] with the updated "CAG information list".

a non-CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the DEREGISTRATION REQUEST message, the UE shall:

replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN;
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 or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or

NOTE 6: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored.

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:

if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304 [28] with the updated CAG information; or
if no CAG-ID is authorized based on the "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122 [5] 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 clause 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 clause 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 clause 5.3.23.

NOTE 7: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see clauses 4.7.2 and 5.1.3).

#78 (PLMN not allowed to operate at the present UE location).

If this cause value is received from a cell which is not deployed in a 5G PLMN/access technology combination with specific satellite features, it shall be considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.2.3.4.

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete the list of equivalent PLMNs, 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store:

for satellite NG-RAN access, 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"; or
for NG-RAN access, the PLMN/access technology combination and, if it is known, the current geographical location in the list of "LSP PLMNs not allowed to operate at the present UE location",

and shall start a corresponding timer instance (see clause 4.23.2). The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122 [5].

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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 3GPP TS 24.301 [15] 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".

#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 clause 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. If the UE re-attempt the registration procedure to the current PLMN, the UE shall not include the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of REGISTRATION REQUEST message.

If the de-registration request is for 3GPP access only or for both 3GPP access and non-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.

#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 and the UE is operating in SNPN access operation mode is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.2.3.4.

If the UE is not operating in SNPN access operation mode, the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122 [5].

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 3GPP TS 23.122 [5].

NOTE 8: In case the configuration of one or more entries of the "list of subscriber data" was not completed at the time of network-initiated de-registration procedure, the UE can retry registration after the de-registration procedure is completed.