C.2 Stage-2 flow for steering of UE in VPLMN during registration

23.1223GPPNon-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle modeRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

The stage-2 flow for the case when the UE registers with VPLMN AMF is described below in figure C.2.1. The selected PLMN is the VPLMN. The AMF is located in the selected VPLMN.

Figure C.2.1: Procedure for providing list of preferred PLMN/access technology combinations and the SOR-CMCI, if any, or secured packet during registration

For the steps below, security protection is described in 3GPP TS 33.501 [66].

1) The UE to the VPLMN AMF: The UE initiates initial registration, emergency registration or registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) to the VPLMN AMF by sending REGISTRATION REQUEST message with the 5GS registration type IE indicating "initial registration", "emergency registration" or "mobility registration updating";

2) Upon receiving REGISTRATION REQUEST message, the VPLMN AMF executes the registration procedure as defined in clause 4.2.2.2 of 3GPP TS 23.502 [63]. As part of the registration procedure:

a) the AMF provides the registration type to the UDM using Nudm_UECM_Registration. As a consequence, in case of the 5GS registration type message indicates "initial registration" or "emergency registration" the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any, and the stored "ME support of SOR-SNPN-SI" indicator, if any, in UDR using Nudr_DM_Update service operation (see 3GPP TS 23.502 [63]).

NOTE 1: Nudr_DM_Update service operation corresponds to Nudr_DR_Update service operation (see 3GPP TS 29.504 [82] and 3GPP TS 29.505 [83]).

In addition:

a) if the VPLMN AMF does not have subscription data for the UE, the VPLMN AMF invokes Nudm_SDM_Get service operation to the HPLMN UDM to get amongst other information the Access and Mobility Subscription data for the UE (see step 14b in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]); or

b) if the VPLMN AMF already has subscription data for the UE and:

i) the 5GS registration type IE in the received REGISTRATION REQUEST message indicates "initial registration" and the "SoR Update Indicator for Initial Registration" field in the UE context is set to ‘the UDM requests the AMF to retrieve SoR information when the UE performs NAS registration type "initial registration"’ as specified in table 5.2.2.2.2-1 of 3GPP TS 23.502 [63]); or

ii) the 5GS registration type IE in the received REGISTRATION REQUEST message indicates "emergency registration" and the "SoR Update Indicator for Emergency Registration" field in the UE context is set to ‘the UDM requests the AMF to retrieve SoR information when the UE performs NAS registration type "emergency registration"’ as specified in table 5.2.2.2.2-1 of 3GPP TS 23.502 [63]);

then the VPLMN AMF invokes Nudm_SDM_Get service operation message to the HPLMN UDM to retrieve the steering of roaming information (see step 14b in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]);

otherwise the VPLMN AMF sends a REGISTRATION ACCEPT message without the steering of roaming information to the UE and steps 3a, 3b, 3c, 3d, 4, 5, 6 are skipped;

3a) If the user subscription information indicates to send the steering of roaming information due to initial registration in a VPLMN, then the HPLMN UDM shall provide the steering of roaming information to the UE when the UE performs initial registration in a VPLMN, otherwise the HPLMN UDM may provide the steering of roaming information to the UE, based on operator policy.

NOTE 2: Based on operator deployment and policy, if the UDM receives the list of preferred PLMN/access technology combinations from the UDR, and the UDM supports communication with the SP-AF, the UDM can send this list to the SP-AF requesting it to provide this information in a secured packet as defined in 3GPP TS 29.544 [71].

If the HPLMN UDM is to provide the steering of roaming information to the UE when the UE performs the registration in a VPLMN, and the HPLMN policy for the SOR-AF invocation is absent then steps 3b and 3c are not performed and the HPLMN UDM obtains the available list of preferred PLMN/access technology combinations or the available secured packet (i.e. all retrieved from the UDR). In addition, if the HPLMN UDM obtains the list of preferred PLMN/access technology combinations and the "ME support of SOR-CMCI" indicator is stored for the UE, then the HPLMN UDM shall obtain the SOR-CMCI, if available, otherwise the HPLMN UDM shall not obtain the SOR-CMCI. If the SOR-CMCI is provided then the HPLMN UDM may indicate to the UE to store the SOR-CMCI in the ME by providing the "Store SOR-CMCI in ME" indicator set to "Store SOR-CMCI in ME".

NOTE 3: The secured packet obtained by the UDM can include SOR-CMCI only if the "ME support of SOR-CMCI" indicator is stored for the UE and the USIM of the indicated SUPI supports SOR-CMCI. Otherwise if only the "ME support of SOR-CMCI" indicator is stored for the UE, then SOR-CMCI, if any, cannot be included in the secured packet.

If the HPLMN UDM is to provide the steering of roaming information to the UE when the UE performs the registration in a VPLMN, and the HPLMN policy for the SOR-AF invocation is present, then the HPLMN UDM obtains the list of preferred PLMN/access technology combinations, SOR-CMCI, if any, or the secured packet from the SOR-AF using steps 3b and 3c;

3b) The HPLMN UDM to the SOR-AF: Nsoraf_SoR_Get request (VPLMN ID, SUPI of the UE, access type (see 3GPP TS 29.571 [72])). The VPLMN ID and the access type parameters, indicating where the UE is registering, are stored in the HPLMN UDM;

3c) The SOR-AF to the HPLMN UDM: Nsoraf_SoR_Get response (the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, and the "Store SOR-CMCI in ME" indicator, if any, or the secured packet, or neither of them);

Based on the information received in step 3b and any operator specific criteria, the SOR-AF may either:

– include the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, and optionally the "Store SOR-CMCI in ME" indicator, if any;

– provide the secured packet in the Nsoraf_SoR_Get response; or

– provide the Nsoraf_SoR_Get response with neither of the information above.

If the SOR-AF includes the list of preferred PLMN/access technology combinations and the ME supports the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally the "Store SOR-CMCI in ME" indicator, otherwise the SOR-AF shall provide neither the SOR-CMCI nor "Store the SOR-CMCI in ME" indicator.

NOTE 4: In this version of the specification, when the access type where the UE is registering indicates 3GPP access, then the UE is registering over the NG-RAN access technology.

NOTE 5: Based on operator deployment and policy, if the UDM receives the list of preferred PLMN/access technology combinations, and the SOR-CMCI, if any, in the Nsoraf_SoR_Get response from the SOR-AF, and the UDM supports communication with SP-AF, it can send this list, and the SOR-CMCI, if any, to SP-AF requesting it to provide this information in a secured packet as defined in 3GPP TS 29.544 [71].

NOTE 6: The SOR-AF can include a different list of preferred PLMN/access technology combinations, different SOR-CMCI, if any, and different "Store SOR-CMCI in ME" indicator, if any, or a different secured packet for each Nsoraf_SoR_Get request even if the same VPLMN ID, the SUPI of the UE, and the access type are provided to the SOR-AF.

NOTE 7: The SOR-AF can subscribe to the HPLMN UDM to be notified about the changes of the roaming status of the UE identified by SUPI.

NOTE 8: The SOR-AF can determine that the ME supports the SOR-CMCI if the Nsoraf_SoR_Info service operation has returned the "ME support of SOR-CMCI" indicator.

NOTE 9: Secured packet provided by the SOR-AF can include SOR-CMCI only if the SOR-AF has determined that the ME supports the SOR-CMCI and the USIM of the indicated SUPI supports SOR-CMCI. Otherwise if only the "ME support of SOR-CMCI" indicator is stored for the UE, then SOR-CMCI, if any, cannot be included in the secured packet.

NOTE 10: Secured packets do not include the "Store SOR-CMCI in ME" indicator.

3d) The HPLMN UDM forms the steering of roaming information as specified in 3GPP TS 33.501 [66] from:

– the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, and the "Store SOR-CMCI in ME" indicator, if any, or the secured packet obtained in step 3a; or

the list of preferred PLMN/access technology combinations and the SOR-CMCI, if any, and "Store the SOR-CMCI in ME" indicator, if any, or the secured packet, obtained in step 3c.

If:

– neither the list of preferred PLMN/access technology combinations nor the secured packet was obtained in steps 3a or 3c; or

– the SOR-AF has not sent to the HPLMN UDM an Nsoraf_SoR_Get response (step 3c) within an operator defined time after the HPLMN UDM sending to the SOR-AF an Nsoraf_SoR_Get request (step 3b);

NOTE 11: Stage 3 to define the timer needed for the SOR-AF to respond to the HPLMN UDM. The max time needs to be defined considering that this procedure is part of the registration procedure.

and the UE is performing initial registration in a VPLMN and the user subscription information indicates to send the steering of roaming information due to initial registration in a VPLMN, then the HPLMN UDM forms the steering of roaming information as specified in 3GPP TS 33.501 [66] from the HPLMN indication that ‘no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided’;

If the "Store SOR-CMCI in ME" indicator was not obtained in step 3a or 3c and the "ME support of SOR-CMCI" indicator is stored for the UE in the HPLMN UDM, the HPLMN UDM forms the steering of roaming information with the "Store SOR-CMCI in ME" indicator set to "Do not store SOR-CMCI in ME";

4) The HPLMN UDM to the VPLMN AMF: The HPLMN UDM sends a response to the Nudm_SDM_Get service operation to the VPLMN AMF, which includes the steering of roaming information within the Access and Mobility Subscription data. The Access and Mobility Subscription data type is defined in clause 5.2.3.3.1 of 3GPP TS 23.502 [63]).

NOTE 12: The UDM cannot provide the SOR-CMCI, if any, to the VPLMN AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]).

If the UE is performing initial registration or emergency registration and the HPLMN UDM supports SOR-CMCI, the HPLMN shall request the UE to acknowledge the successful security check of the received steering of roaming information, by providing the indication as part of the steering of roaming information in the Nudm_SDM_Get response service operation. Otherwise, the HPLMN may request the UE to acknowledge the successful security check of the received steering of roaming information, by providing the indication as part of the steering of roaming information in the Nudm_SDM_Get response service operation;

NOTE 13: If the UE is performing registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) after inter-system change from S1 mode to N1 mode and the HPLMN UDM supports SOR-CMCI, the HPLMN requests the UE to acknowledge the successful security check of the received steering of roaming information, by providing the indication as part of the steering of roaming information in the Nudm_SDM_Get response service operation, unless the HPLMN UDM has already received and stored the "ME support of SOR-CMCI" indicator for the UE during its former registration on the current VPLMN.

5) The VPLMN AMF to the HPLMN UDM: As part of the registration procedure, the VPLMN AMF also invokes Nudm_SDM_Subscribe service operation to the HPLMN UDM to subscribe to notification of changes of the subscription data (e.g. received in step 4) including notification of updates of the steering of roaming information included in the Access and Mobility Subscription data (see step 14c in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]);

6) The VPLMN AMF to the UE: The VPLMN AMF shall transparently send the received steering of roaming information to the UE in the REGISTRATION ACCEPT message;

7) If the steering of roaming information is received and the security check is successful, then:

a) if the UDM has not requested an acknowledgement from the UE, then the UE shall send the REGISTRATION COMPLETE message to the serving AMF without including an SOR transparent container;

b) if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]):

– the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41], if the service "data download via SMS Point-to-point" is allocated and activated in the USIM Service Table (see 3GPP TS 31.102 [40]);

NOTE 14: How the ME handles UICC responses and failures in communication between the ME and UICC is implementation specific and out of scope of this release of the specification.

– if the UDM has not requested an acknowledgement from the UE and:

A) the ME receives a USAT REFRESH with command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming" and either a SOR-CMCI is included, or the UE is configured with the SOR-CMCI, the UE shall perform items a), b) and c) of the procedure for steering of roaming in clause 4.4.6, and if the UE is in automatic network selection mode then it shall apply the actions in clause C.4.2. In this case steps 8 to 11 are skipped; or

B) the ME receives a USAT REFRESH command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming" and neither a SOR-CMCI is included, nor the UE is configured with the SOR-CMCI, it shall perform items a), b) and c) of the procedure for steering of roaming in clause 4.4.6 and if:

i) the UE has a list of available and allowable PLMNs in the area and based on this list or any other implementation specific means the UE determines that there is a higher priority PLMN than the selected VPLMN; or

ii) the UE does not have a list of available and allowable PLMNs in the area and is unable to determine whether there is a higher priority PLMN than the selected VPLMN using any other implementation specific means;

and the UE is in automatic network selection mode, then the UE shall either:

i) release the current N1 NAS signalling connection locally and then attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired. In this case, steps 8 to 11 are skipped. The UE shall suspend the transmission of 5GSM messages until the N1 NAS signalling is released. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services or establishing an emergency PDU session, until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]), the receipt of the steering of roaming information shall not trigger the release of the N1 NAS signalling connection. If camped on a NG-RAN cell, the UE shall release the current N1 NAS signalling connection locally subsequently after the emergency PDU session is released, otherwise the UE shall not take any further actions; or

ii) not release the current N1 NAS signalling connection locally (e.g. if the UE has established PDU session(s)) and skip steps 8 to 10;

c) if the steering of roaming information contains the list of preferred PLMN/access technology combinations, the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME with the received list of preferred PLMN/access technology combinations, and delete the PLMNs identified by the list of preferred PLMN/access technology combinations from the Forbidden PLMN list and from the Forbidden PLMNs for GPRS service list, if they are present in these lists. Additionally, if:

and the UE is in automatic network selection mode:

A) if the UE is configured with the SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, the UE shall apply the actions in clause C.4.2. In this case steps 8 to 11 are skipped;

B) otherwise, the UE shall:

i) release the current N1 NAS signalling connection locally and then attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired. In this case, steps 8 to 11 are skipped. The UE shall suspend the transmission of 5GSM messages until the N1 NAS signalling is released. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services or establishing an emergency PDU session, until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]), the receipt of the steering of roaming information shall not trigger the release of the N1 NAS signalling connection. If camped on a NG-RAN cell, he UE shall release the current N1 NAS signalling connection locally subsequently after the emergency PDU session is released, otherwise the UE shall not take any further actions. If the UE needs to disable the N1 mode capability (see 3GPP TS 24.501 [64]) and there is no emergency service pending, the UE shall first attempt to obtain service on a higher priority PLMN as described in this step, and if no higher priority PLMN can be selected but the last registered PLMN is selected, then the UE shall disable the N1 mode capability; or

ii) not release the current N1 NAS signalling connection locally (e.g. if the UE has established PDU session(s)) and skip steps 8 to 10;

NOTE 15: When the UE is in the manual mode of operation or the current chosen VPLMN is part of the "User Controlled PLMN Selector with Access Technology" list, the UE stays on the VPLMN.

8) If the UE’s USIM is configured with indication that the UE is to receive the steering of roaming information due to initial registration in a VPLMN, but neither the list of preferred PLMN/access technology combinations nor the secured packet nor the HPLMN indication that ‘no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided’ is received in the REGISTRATION ACCEPT message, when the UE performs initial registration in a VPLMN or if the steering of roaming information is received but the security check is not successful, then the UE shall:

a) if the SOR transparent container is included in the REGISTRATION ACCEPT message, send the REGISTRATION COMPLETE message to the serving AMF without including an SOR transparent container;

b) if the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to SOR", and is not part of "User Controlled PLMN Selector with Access Technology" list and the UE is not in manual mode of operation:

i) if the steering of roaming information is received but the security check is not successful when the UE performs registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) in a VPLMN and the UE has a SOR-CMCI stored in the non-volatile memory of the ME, and there are ongoing PDU sessions or services, the UE shall apply the actions in clause C.4.2. In this case, current PLMN is considered as lowest priority and steps 9 to 11 are skipped;

ii) otherwise, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with an exception that the current PLMN is considered as lowest priority, and skip steps 9 to 11. The UE shall suspend the transmission of 5GSM messages until the N1 NAS signalling is released. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services or establishing an emergency PDU session, until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]), if camped on a NG-RAN cell, the UE shall release the current N1 NAS signalling connection locally after the release of the emergency PDU session, otherwise the UE shall not take any further actions. If the UE needs to disable the N1 mode capability (see 3GPP TS 24.501 [64]) and there is no emergency service pending, the UE shall first attempt to obtain service on a higher priority PLMN as described in this step, and if no higher priority PLMN can be selected but the last registered PLMN is selected, then the UE shall disable the N1 mode capability; and

c) if the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to SOR", store the PLMN identity in the list of "PLMNs where registration was aborted due to SOR";

NOTE 16: When the UE is in the manual mode of operation or the current chosen VPLMN is part of the "User Controlled PLMN Selector with Access Technology" list, the UE stays on the VPLMN.

9) The UE to the VPLMN AMF: If the UDM has requested an acknowledgement from the UE and the UE verified that the steering of roaming information has been provided by the HPLMN in step 7, then:

a) the UE sends the REGISTRATION COMPLETE message to the serving AMF with an SOR transparent container including the UE acknowledgement;

b) the UE shall set the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container to "supported";

c) if the UE supports access to an SNPN using credentials from a credentials holder, the UE may set the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container to "supported"; and

d) if:

– the steering of roaming information contained a secured packet, then when the UE receives the USAT REFRESH command qualifier of type "Steering of Roaming" and neither a SOR-CMCI is included, nor the UE is configured with the SOR-CMCI, it performs items a), b) and c) of the procedure for steering of roaming in clause 4.4.6;

– the steering of roaming information contained a secured packet, then when the UE receives a USAT REFRESH with command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming" and either a SOR-CMCI is included, or the UE is configured with the SOR-CMCI, the UE shall perform items a), b) and c) of the procedure for steering of roaming in clause 4.4.6 and if the UE is in automatic network selection mode then it shall apply the actions in clause C.4.2, and step 11 is skipped;

– the steering of roaming information contains the list of preferred PLMN/access technology combinations, the UE is configured with the SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, and the UE is in automatic network selection mode, then the UE shall apply the actions in clause C.4.2, and step 11 is skipped; or

– the steering of roaming information contains an indication that ‘no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided’, then step 11 is skipped;

10) The VPLMN AMF to the HPLMN UDM: If an SOR transparent container is received in the REGISTRATION COMPLETE message, the AMF uses the Nudm_SDM_Info service operation to provide the received SOR transparent container to the UDM. If the HPLMN decided that the UE is to acknowledge the successful security check of the received steering of roaming information in step 4, the UDM verifies that the acknowledgement is provided by the UE as specified in 3GPP TS 33.501 [66]. If the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container is set to "supported", then the HPLMN UDM shall store the "ME support of SOR-CMCI" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any. Additionally, if the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container is set to "supported", then the HPLMN UDM shall store the "ME support of SOR-SNPN-SI" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-SNPN-SI" indicator, if any.

NOTE 17: The UDM cannot receive the "ME support of SOR-CMCI" indicator or the "ME support of SOR-SNPN-SI" from the VPLMN AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]).

10a) The HPLMN UDM to the SOR-AF: Nsoraf_SoR_Info (SUPI of the UE, successful delivery, "ME support of SOR-CMCI" indicator, if any, "ME support of SOR-SNPN-SI" indicator, if any). If the HPLMN policy for the SOR-AF invocation is present and the HPLMN UDM received and verified the UE acknowledgement in step 10, then the HPLMN UDM informs the SOR-AF about successful delivery of the list of preferred PLMN/access technology combinations, or of the secured packet to the UE. If the "ME support of SOR-CMCI" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-CMCI" indicator. Additionally, if the "ME support of SOR-SNPN-SI" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-SNPN-SI" indicator; and

NOTE 18: How the SOR-AF determines that the USIM for the indicated SUPI supports SOR-CMCI is implementation specific.

11) If the UE has a list of available PLMNs in the area and based on this list the UE determines that there is a higher priority PLMN than the selected VPLMN and the UE is in automatic network selection mode, then the UE shall attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired after the release of the N1 NAS signalling connection. If within an implementation dependent time the N1 NAS signalling connection is not released, then the UE may locally release the N1 NAS signalling connection except when the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]). The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services or establishing an emergency PDU session, until the attempts to obtain service on a higher priority PLMN are completed.

When the UE performs initial registration for emergency services (see 3GPP TS 24.501 [64] and 3GPP TS 23.502 [63]) while the UE has a valid USIM and the AMF performs the authentication procedure, then based on HPLMN policy, the SOR procedure described in this clause may apply.

If:

– the UE in manual mode of operation encounters scenario mentioned in step 8 above; and

– upon switching to automatic network selection mode, the UE remembers that it is still registered on the PLMN where the missing or security check failure of SOR information was encountered as described in clause 8;

the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3, by acting as if timer T that controls periodic attempts has expired, with an exception that the current registered PLMN is considered as lowest priority. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services or establishing an emergency PDU session, until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session, then the UE shall attempt to perform the PLMN selection subsequently after the emergency PDU session is released.

NOTE 19: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session.

NOTE 20: The list of available and allowable PLMNs in the area is implementation specific.

NOTE 21: If the UE is served by any access technology other than NG-RAN, the HPLMN can initiate a steering of roaming procedure as specified in clause 4.4.6.