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

5.4.4.3 Generic UE configuration update accepted 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 CONFIGURATION UPDATE COMMAND message, the UE shall stop timer T3346 if running and use the contents to update appropriate information stored within the UE.

If "acknowledgement requested" is indicated in the Acknowledgement bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message, the UE shall send a CONFIGURATION UPDATE COMPLETE message.

If the UE receives a new 5G-GUTI in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new 5G-GUTI as valid, the old 5G-GUTI as invalid, stop timer T3519 if running, and delete any stored SUCI; otherwise, the UE shall consider the old 5G-GUTI as valid. The UE shall provide the 5G-GUTI to the lower layer of 3GPP access if the CONFIGURATION UPDATE COMMAND message is sent over the non-3GPP access, and the UE is in 5GMM-REGISTERED in both 3GPP access and non-3GPP access in the same PLMN.

If the UE receives a new TAI list in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new TAI list as valid and the old TAI list as invalid; otherwise, the UE shall consider the old TAI list as valid. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, and

the UE already has stored allowed NSSAI for the current registration area, the UE shall store the allowed NSSAI for the current registration area in each of the allowed NSSAIs which are associated with each of the PLMNs in the registration area;
the UE already has stored rejected NSSAI for the current registration area, the UE shall store the rejected NSSAI for the current registration area in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area;
the UE already has stored rejected NSSAI for the failed or revoked NSSAA, the UE shall store the rejected NSSAI for the failed or revoked NSSAA in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area;
the UE already has stored rejected NSSAI for the maximum number of UEs reached, the UE shall store the rejected NSSAI for the maximum number of UEs reached in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area; and
the UE already has stored pending NSSAI, the UE shall store the pending NSSAI in each of the pending NSSAIs which are associated with each of the PLMNs in the registration area.

If the UE receives a new truncated 5G-S-TMSI configuration in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new truncated 5G-S-TMSI configuration as valid and the old truncated 5G-S-TMSI configuration as invalid; otherwise, the UE shall consider the old truncated 5G-S-TMSI configuration as valid.

If the UE receives a new service area list in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new service area list as valid and the old service area list as invalid; otherwise, the UE shall consider the old service area list, if any, as valid.

If the UE receives new NITZ information in the CONFIGURATION UPDATE COMMAND message, the UE considers the new NITZ information as valid and the old NITZ information as invalid; otherwise, the UE shall consider the old NITZ information as valid.

If the UE receives a LADN information IE in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the old LADN information as invalid and the new LADN information as valid, if any; otherwise, the UE shall consider the old LADN information as valid.

If the UE receives an Extended LADN information IE in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the old extended LADN information as invalid and the new extended LADN information as valid, if any; otherwise, the UE shall consider the old extended LADN information as valid.

If the UE receives a new allowed NSSAI for the associated access type in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new allowed NSSAI as valid for the associated access type, store the allowed NSSAI for the associated access type as specified in clause 4.6.2.2 and consider the old allowed NSSAI for the associated access type as invalid; otherwise, the UE shall consider the old allowed NSSAI as valid for the associated access type.

If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message, the UE shall consider the new configured NSSAI for the registered PLMN or SNPN as valid and the old configured NSSAI for the registered PLMN or SNPN as invalid; otherwise, the UE shall consider the old configured NSSAI for the registered PLMN or SNPN as valid. The UE shall store the new configured NSSAI as specified in clause 4.6.2.2. In addition, if the CONFIGURATION UPDATE COMMAND message contains:

an NSSRG information IE, the UE shall store the contents of the NSSRG information IE as specified in clause 4.6.2.2. If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and no NSSRG information IE, the UE shall delete any stored NSSRG information, if any, as specified in clause 4.6.2.2;

NOTE 1: When the UE receives the NSSRG information IE, the UE may provide the NSSRG information to lower layers for the purpose of NSAG-aware cell reselection.

an S-NSSAI location validity information IE, the UE shall store the contents of the S-NSSAI location validity information IE as specified in clause 4.6.2.2. If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and no S-NSSAI location validity information IE, the UE shall delete any stored S-NSSAI location validity information, if any, as specified in clause 4.6.2.2;
an S-NSSAI time validity information IE, the UE shall store the contents of the S-NSSAI time validity information IE as specified in clause 4.6.2.2. If the UE receives a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and no S-NSSAI time validity information IE, the UE shall delete any stored S-NSSAI time validity information, if any, as specified in clause 4.6.2.2; or
an On-demand NSSAI IE, the UE shall store the contents of the On-demand NSSAI IE as specified in clause 4.6.2.2. If the UE receives a new Configured NSSAI IE in the CONFIGURATION UPDATE COMMAND message and no On-demand NSSAI IE, the UE shall delete any stored on-demand NSSAI as specified in clause 4.6.2.2. The UE shall stop slice deregistration inactivity timer, if running for the S-NSSAI which is deleted from the on-demand NSSAI.

If the CONFIGURATION UPDATE COMMAND message contains Partially allowed NSSAI IE the UE shall store the contents of the Partially allowed NSSAI IE as specified in clause 4.6.2.2. If the CONFIGURATION UPDATE COMMAND message contains Partially rejected NSSAI IE the UE shall store the contents of the Partially rejected NSSAI IE as specified in clause 4.6.2.2.

If the UE receives the Network slicing indication IE in the CONFIGURATION UPDATE COMMAND message with the Network slicing subscription change indication set to "Network slicing subscription changed", the UE shall delete the network slicing information and the NSSAI inclusion mode for each and every PLMN or SNPN except for the current PLMN or SNPN as specified in clause 4.6.2.2 and remove all tracking areas from the list of "5GS forbidden tracking areas for roaming" which were added due to rejection of S-NSSAI due to "S-NSSAI not available in the current registration area".

If the UE receives Operator-defined access category definitions IE in the CONFIGURATION UPDATE COMMAND message and the Operator-defined access category definitions IE contains one or more operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN and shall store the received operator-defined access category definitions for the RPLMN. If the UE receives the Operator-defined access category definitions IE in the CONFIGURATION UPDATE COMMAND message and the Operator-defined access category definitions IE contains no operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN. If the CONFIGURATION UPDATE COMMAND message does not contain the Operator-defined access category definitions IE, the UE shall not delete the operator-defined access category definitions stored for the RPLMN.

If the UE receives the SMS indication IE in the CONFIGURATION UPDATE COMMAND message with the SMS availability indication set to:

"SMS over NAS not available", the UE shall consider that SMS over NAS transport is not allowed by the network; and
"SMS over NAS available", the UE may request the use of SMS over NAS transport by performing a registration procedure for mobility and periodic registration update as specified in clause 5.5.1.3, after the completion of the generic UE configuration update procedure.

If the UE receives the CAG information list IE or the Extended CAG information list IE in the CONFIGURATION UPDATE COMMAND 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;

NOTE 2: When the UE receives the CAG information list IE or the Extended CAG information list IE in the HPLMN whose PLMN code is derived from the IMSI, the EHPLMN list is present and is not empty and the HPLMN is not present in the EHPLMN list, the UE behaves as if it receives the CAG information list IE or the Extended CAG information list IE in a VPLMN.

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 3: 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.

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.

The UE shall store the "CAG information list" received in the CAG information list IE or the Extended CAG information list IE as specified in annex C.

If the received "CAG information list" includes an entry containing the identity of the current PLMN and the UE had set the CAG bit to "CAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the UE shall operate as follows.

If the UE receives the CONFIGURATION UPDATE COMMAND message via a CAG cell, none of the CAG-ID(s) supported by the current CAG cell is authorized based on the "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list", and:

the entry for the current PLMN in the received "CAG information list" does not include an "indication that the UE is only allowed to access 5GS via CAG cells", then the UE shall enter the state 5GMM-REGISTERED.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"; or
the entry for the current PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and:

if one or more CAG-ID(s) are authorized based on the "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list", the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304 [28] with the updated "CAG information list"; or
if no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list" and:

A) the UE does not have an emergency PDU session, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122 [5] with the updated "CAG information list"; or

B) the UE has an emergency PDU session, then the UE shall perform a local release of all PDU sessions associated with 3GPP access except for the emergency PDU session and enter the state 5GMM-REGISTERED.LIMITED-SERVICE; or

If the UE receives the CONFIGURATION UPDATE COMMAND message via a non-CAG cell and the entry for the current PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and:

if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the current PLMN in the received "CAG information list", the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304 [28] with the updated "CAG information list"; or
if no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list"and:

the UE does not have an emergency PDU session, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122 [5] with the updated "CAG information list"; or
the UE has an emergency PDU session, then the UE shall perform a local release of all PDU sessions associated with 3GPP access except for the emergency PDU session and enter the state 5GMM-REGISTERED.LIMITED-SERVICE.

If the received "CAG information list" does not include an entry containing the identity of the current PLMN and the UE receives the CONFIGURATION UPDATE COMMAND message via a CAG cell, the UE shall enter the state 5GMM-REGISTERED.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 CONFIGURATION UPDATE COMMAND message indicates "registration requested" in the Registration requested bit of the Configuration update indication IE and:

contains no other information elements or contains at least one information element with one of the following parameters: an allowed NSSAI, a partially allowed NSSAI, a configured NSSAI, an NSSRG information or the Network slicing subscription change indication, and:

an emergency PDU session exists, the UE shall, after the completion of the generic UE configuration update procedure, the release of the emergency PDU session, and the release of the existing N1 NAS signalling connection:

if any Tsor-cm timer(s) were running and have stopped, attempt to obtain service on a higher priority PLMN (see 3GPP TS 23.122 [5]); or
in all other cases, start a registration procedure for mobility and periodic registration update as specified in clause 5.5.1.3; or

no emergency PDU Session exists, the UE shall, after the completion of the generic UE configuration update procedure and the release of the existing N1 NAS signalling connection:

if any Tsor-cm timer(s) were running and have stopped, attempt to obtain service on a higher priority PLMN (see 3GPP TS 23.122 [5]); or
in all other cases, start a registration procedure for mobility and periodic registration update as specified in clause 5.5.1.3;

a MICO indication is included without an allowed NSSAI, a configured NSSAI, an NSSRG information or the Network slicing subscription change indication, the UE shall, after the completion of the generic UE configuration update procedure via the existing N1 NAS signalling connection, start a periodic registration procedure for mobility and registration update as specified in clause 5.5.1.3 to re-negotiate MICO mode with the network;
an Additional configuration indication IE is included, and:

"release of N1 NAS signalling connection not required" is indicated in the Signalling connection maintain request bit of the Additional configuration indication IE; and
an allowed NSSAI, a configured NSSAI, an NSSRG information or the Network slicing subscription change indication is not included in the CONFIGURATION UPDATE COMMAND message,

the UE shall, after the completion of the generic UE configuration update procedure, start a registration procedure for mobility and periodic registration update via the existing N1 NAS signalling connection as specified in clause 5.5.1.3; or

a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested" is included, and:

the UE is not in NB-N1 mode;
an allowed NSSAI, a configured NSSAI, an NSSRG information or a Network slicing subscription change indication is not included; and
the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message,

the UE shall, after the completion of the generic UE configuration update procedure via the existing N1 NAS signalling connection, start a registration procedure for mobility and periodic registration update as specified in clause 5.5.1.3.

The UE receiving the rejected NSSAI in the CONFIGURATION UPDATE COMMAND 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 add 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, 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 in the current registration area"

The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as specified 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"

The UE shall add 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 4: 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 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 receives the NSAG information IE in the CONFIGURATION UPDATE COMMAND message, the UE shall store the NSAG information as specified in clause 4.6.2.2.

If the UE receives the Alternative NSSAI IE in the CONFIGURATION UPDATE COMMAND message, the UE shall store the alternative NSSAI as specified in clause 4.6.2.2.

If the UE receives a T3447 value IE in the CONFIGURATION UPDATE COMMAND message and has indicated "service gap control supported" in the REGISTRATION REQUEST, then the UE shall replace the stored T3447 value with the received value in the T3447 value IE, and if neither zero nor deactivated use the received T3447 value with the timer T3447 next time it is started. If the received T3447 value is zero or deactivated, then the UE shall stop the timer T3447 if running.

If the UE is not in NB-N1 mode, the UE has set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the CONFIGURATION UPDATE COMMAND message includes:

a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall delete any network-assigned UE radio capability IDs associated with the RPLMN or RSNPN 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 stored at the UE; or
a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C.

If the UE is not currently registered for emergency services and the emergency registered bit of the 5GS registration result IE in the CONFIGURATION UPDATE COMMAND message is set to "Registered for emergency services", the UE shall consider itself registered for emergency services and shall locally release all non-emergency PDU sessions, if any.

If the UE receives the service-level-AA container IE of the CONFIGURATION UPDATE COMMAND message, the UE passes it to the upper layer.

NOTE 5: The service-level-AA container IE can include a service-level-AA payload of type "C2 authorization payload" that includes pairing information for the direct C2 communication, or the security information as specified in TS 33.256 [24B], or both.

If the CONFIGURATION UPDATE COMMAND message includes the service-level-AA response in the Service-level-AA container IE with the SLAR field set to "Service level authentication and authorization was not successful or service level authorization is revoked", the UE shall forward the service-level-AA response to the upper layers, so the UUAA authorization data is deleted as specified in 3GPP TS 33.256 [24B].

If the UE receives the List of PLMNs to be used in disaster condition IE in the CONFIGURATION UPDATE COMMAND message and the UE supports MINT, MINT-EPS or both, the UE shall delete the "list of PLMN(s) to be used in disaster condition" stored in the ME together with the PLMN ID of the RPLMN, if any, and may store the "list of PLMN(s) to be used in disaster condition" included in the List of PLMNs to be used in disaster condition IE in the ME together with the PLMN ID of the RPLMN.

If the UE receives the Disaster roaming wait range IE in the CONFIGURATION UPDATE COMMAND message and the UE supports MINT, MINT-EPS or both, the UE shall delete the disaster roaming wait range stored in the ME, if any, and store the disaster roaming wait range included in the Disaster roaming wait range IE in the ME.

If the UE receives the Disaster return wait range IE in the CONFIGURATION UPDATE COMMAND message and the UE supports MINT, MINT-EPS or both, 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.

If the UE receives, the Discontinuous coverage maximum time offset IE in the CONFIGURATION UPDATE COMMAND message, the UE shall replace any previously received discontinuous coverage maximum time offset value on the same satellite NG-RAN access technology and PLMN with the latest received timer value.

If the UE receives the Updated PEIPS assistance information IE in the CONFIGURATION UPDATE COMMAND message and the UE supports PEIPS assistance information, the UE shall use the PEIPS assistance information included in the Updated PEIPS assistance information IE.

If the UE receives a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit in the Priority indicator IE set to "Access identity 1 valid":

via 3GPP access; or
via non-3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access;

the UE shall act as a UE with access identity 1 configured for MPS, as described in clause 4.5.2, in all NG-RAN of the registered PLMN and its equivalent PLMNs or in the case of SNPN, as described in clause 4.5.2A, in all NG-RAN of the registered SNPN and its equivalent SNPNs.

If the UE receives a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit in the Priority indicator IE set to "Access identity 1 valid":

via non-3GPP access; or
via 3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access;

the UE shall act as a UE with access identity 1 configured for MPS, as described in clause 4.5.2, in non-3GPP access of the registered PLMN and its equivalent PLMNs or in the case of SNPN, as described in clause 4.5.2A, in non-3GPP access of the registered SNPN and its equivalent SNPNs.

The MPS indicator bit in the Priority indicator IE provided in the CONFIGURATION UPDATE COMMAND message is valid:

in all NG-RAN of the registered PLMN and its equivalent PLMNs, or in the case of SNPN in all NG-RAN of the registered SNPN and its equivalent SNPNs, until:

the UE receives a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 not valid" or the UE receives a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit of the Priority indicator IE set to "Access identity 1 not valid":

via 3GPP access; or
via non-3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; or

the UE selects a non-equivalent PLMN (or in the case of SNPN, selects a non-equivalent SNPN); or

in non-3GPP access of the registered PLMN and its equivalent PLMNs, or in the case of SNPN in non-3GPP access of the registered SNPN and its equivalent SNPNs, until:

the UE receives a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 not valid" or the UE receives a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit of the Priority indicator IE set to "Access identity 1 not valid":

via non-3GPP access; or
via 3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; or

the UE selects a non-equivalent PLMN (or in the case of SNPN, selects a non-equivalentSNPN).

Access identity 1 is only applicable while the UE is in N1 mode.

If the UE receives a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit in the Priority indicator IE set to "Access identity 2 valid":

via 3GPP access; or
via non-3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access;

the UE shall act as a UE with access identity 2 configured for MCS, as described in clause 4.5.2, in all NG-RAN of the registered PLMN and its equivalent PLMNs or in the case of SNPN, as described in clause 4.5.2A, in all NG-RAN of the registered SNPN and its equivalent SNPNs.

If the UE receives a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit in the Priority indicator IE set to "Access identity 2 valid":

via non-3GPP access; or
via 3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access;

the UE shall act as a UE with access identity 2 configured for MCS, as described in clause 4.5.2, in non-3GPP access of the registered PLMN and its equivalent PLMNs or in the case of SNPN, as described in clause 4.5.2A, in non-3GPP access of the registered SNPN and its equivalent SNPNs.

The MCS indicator bit in the Priority indicator IE provided in the CONFIGURATION UPDATE COMMAND message is valid:

in all NG-RAN of the registered PLMN and its equivalent PLMNs, or in the case of SNPN in all NG-RAN of the registered SNPN and its equivalent SNPNs, until:

the UE receives a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 not valid" or the UE receives a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit of the Priority indicator IE set to "Access identity 2 not valid":

via 3GPP access; or
via non-3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; or

the UE selects a non-equivalent PLMN (or in the case of SNPN, selects a non-equivalent SNPN); or

in non-3GPP access of the registered PLMN and its equivalent PLMNs, or in the case of SNPN in non-3GPP access of the registered SNPN and its equivalent SNPNs, until:

the UE receives a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 not valid" or the UE receives a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit of the Priority indicator IE set to "Access identity 2 not valid":

via non-3GPP access; or
via 3GPP access if the UE is registered to the same PLMN or SNPN over 3GPP access and non-3GPP access; or

the UE selects a non-equivalent PLMN (or in the case of SNPN, selects a non-equivalentSNPN).

Access identity 2 is only applicable while the UE is in N1 mode.

If the UE supporting UAS services is not currently registered for UAS services and the CONFIGURATION UPDATE COMMAND message includes the service-level-AA service status indication in the Service-level-AA container IE with the UAS field set to "UAS services enabled", then the UE passes the service-level-AA service status indication to the upper layers.

If the UE supporting the reconnection to the network due to RAN timing synchronization status change receives the RAN timing synchronization IE with the RecReq bit set to "Reconnection requested" in the CONFIGURATION UPDATE COMMAND message, the UE shall operate as specified in clauses 5.3.1.4, 5.5.1.3.2, and 5.6.1.1.

If the UE operating as MBSR receives the MBSRAI field of the Feature authorization indication IE in the CONFIGURATION UPDATE COMMAND message, the UE NAS layer informs the lower layers of the status of MBSR authorization.

If the UE supporting access technology utilization control receives the Access technology utilization control IE with the length of access technology utilization control contents field set to a non-zero value, in the CONFIGURATION UPDATE COMMAND 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 specified in clause 4.2A.2.

NOTE 6: The Access technology utilization control IE indicating access technology of the NG-RAN cell on which the CONFIGURATION UPDATE COMMAND message is received (i.e. NG-RAN or satellite NG-RAN), as restricted, does not trigger the UE to locally release the N1 NAS signalling connection.

If the UE supports access technology utilization control and the CONFIGURATION UPDATE COMMAND message contains the Access technology utilization control IE with the length of access technology utilization control contents field set to zero, the UE shall remove the previously stored access technology utilization control information associated with the current PLMN, if any. If the CONFIGURATION UPDATE COMMAND message does not contain the Access technology utilization control IE, the UE shall maintain the stored access technology utilization control information associated with the current PLMN from the list of "PLMNs with associated access technology restrictions", if any.

If the UE receives the Updated LP-WUSPS assistance information IE with the length of LP-WUSPS assistance information contents field set to a non-zero value in the CONFIGURATION UPDATE COMMAND message and the UE supports LP-WUSPS assistance information, the UE shall use the LP-WUSPS assistance information included in the Updated LP-WUSPS assistance information IE. If the UE supports LP-WUSPS assistance information and the CONFIGURATION UPDATE COMMAND message contains the Updated LP-WUSPS assistance information IE with the length of LP-WUSPS assistance information contents field set to zero, the UE shall stop use of LP-WUSPS assistance information and delete any existing LP-WUSPS assistance information previously received from the network. If the CONFIGURATION UPDATE COMMAND message does not contain the Updated LP-WUSPS assistance information IE, the UE shall use the existing LP-WUSPS assistance information received from the network, if any.

If the UE supports LP-WUS disabling and the CONFIGURATION UPDATE COMMAND message includes the LP-WUS status IE, the UE shall indicate LP-WUS status in the received LP-WUS status IE to lower layers. If the UE supports LP-WUS disabling and the CONFIGURATION UPDATE COMMAND message does not contain the LP-WUS status IE, the UE shall indicate "LP-WUS enabled" to lower layers.