hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.2.2 Manual Network Selection Mode
|
The Manual Network Selection Mode Procedure of clause 4.4.3.1.2 is followed.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.2.3 Manual CSG selection
|
The procedure of clause 4.4.3.1.3 is followed.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.3 In VPLMN
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.3.1 Automatic and manual network selection modes
|
4.4.3.3.1.1 Automatic and manual network selection modes when not registered for disaster roaming services
If the MS is in a VPLMN and not registered for disaster roaming services, and the MS shall periodically attempt to obtain service on its HPLMN (if the EHPLMN list is not present or is empty) or one of its EHPLMNs (if the EHPLMN list is present) or a higher priority PLMN/access technology combinations listed in "user controlled PLMN selector" or "operator controlled PLMN selector" by scanning in accordance with the requirements that are applicable to i), ii) and iii) as defined in the Automatic Network Selection Mode in clause 4.4.3.1.1.
NOTE 1: Additionally if signal level enhanced network selection is applicable and the received signal quality of the registered PLMN is lower than the "Operator controlled signal threshold per access technology", the procedures defined in clause 4.4.3.5 are applicable.
For this purpose, a value of timer T may be stored in the SIM. The interpretation of the stored value depends on the radio capabilities supported by the MS:
- For an MS that does not support any of the following: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]);
a) if the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, T is in the range 6 multiplied by integer M minutes to 8 multiplied by integer M hours in 6 multiplied by integer M minutes steps or T indicates that no periodic attempts shall be made. If no value for M is stored in the SIM, a default value of M equal to one is used; or
b) otherwise, T is either in the range 6 minutes to 8 hours in 6 minutes steps or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 60 minutes is used for T.
- For an MS that only supports any of the following or a combination of: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 2 hours to 240 hours, using 2 hour steps from 2 hours to 80 hours and 4 hour steps from 84 hours to 240 hours, or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 72 hours is used.
- For an MS that supports both:
a) any of the following or a combination of: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]); and
b) any other than the following: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]),
T is interpreted depending on what is in use as specified below:
a) if the MS is using any of the following at the time of starting timer T: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 2 hours to 240 hours, using 2 hour steps from 2 hours to 80 hours and 4 hour steps from 84 hours to 240 hours, or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 72 hours is used; and
b) if the MS is not using any of the following at the time of starting timer T: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 6 minutes to 8 hours in 6 minutes steps or it indicates that no periodic attempts shall be made. If the MS is using the satellite NG-RAN access technology or the satellite E-UTRAN access technology with a shared MCC at the time of starting timer T: T is in the range 6 multiplied by integer M minutes to 8 multiplied by integer M hours in 6 multiplied by integer M minutes steps. If no value for M is stored in the SIM, a default value of M equal to one is used. If no value for T is stored in the SIM, a default value of 60 minutes is used for T.
If the MS is configured with the MinimumPeriodicSearchTimer as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40], the MS shall not use a value for T that is less than the MinimumPeriodicSearchTimer. If the value stored in the SIM, or the default value for T (when no value is stored in the SIM), is less than the MinimumPeriodicSearchTimer, then T shall be set to the MinimumPeriodicSearchTimer.
The MS does not stop timer T, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when it activates power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or mobile initiated connection only mode (MICO) as described in 3GPP TS 24.501 [64].
The MS does not stop timer T, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when the access stratum is de-activated due to discontinuous coverage (see 3GPP TS 23.401 [58] and 3GPP TS 24.301 [23A]).
The MS does not stop timer T when it activates unavailability period as described in 3GPP TS 24.501 [64].
The MS can be configured for Fast First Higher Priority PLMN search as specified in 3GPP TS 31.102 [40] or 3GPP TS 24.368 [50]. Fast First Higher Priority PLMN search is enabled if the corresponding configuration parameter is present and set to enabled. Otherwise, Fast First Higher Priority PLMN search is disabled.
The attempts to access the HPLMN or an EHPLMN or higher priority PLMN shall be as specified below:
a) The periodic attempts shall only be performed in automatic mode when the MS is roaming, and not while the MS is attached for emergency bearer services, is registered for emergency services, has a PDU session for emergency services or has a PDN connection for emergency bearer services;
b) The MS shall make the first attempt after a period of at least 2 minutes and at most the time configured for T:
- only after switch on if Fast First Higher Priority PLMN search is disabled; or
- after switch on or upon selecting a VPLMN if Fast First Higher Priority PLMN search is enabled.
c) The MS shall make the following attempts if the MS is on the VPLMN at time T after the last attempt according to the present clause or according to clause 4.4.3.5;
d) Periodic attempts shall only be performed by the MS while in idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]);
d1) Periodic attempts may be postponed while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or when the access stratum is deactivated due to discontinuous coverage (see 3GPP TS 23.401 [58] and 3GPP TS 24.301 [23A]).
d2) Periodic attempts may be postponed while the MS is receiving eMBMS transport service in idle mode (see 3GPP TS 23.246 [68]).
d3) Periodic attempts may be postponed while the MS is receiving broadcast MBS service in idle mode (see 3GPP TS 23.247 [85]) or in 5GMM-CONNECTED mode with RRC inactive indication.
d4) Periodic attempts may be postponed till the next eDRX occasion while the MS is configured with eDRX.
d5) Periodic attempts may be postponed while the MS is in relaxed monitoring (see 3GPP TS 36.304 [43]).
d6) Periodic attempts may be postponed while the MS is in Mobile Initiated Connection Only mode (MICO).
d7) Periodic attempts may be postponed while the MS unavailability period is activated as described in 3GPP TS 24.501 [64].
d8) Periodic attempts may be postponed while the MS is receiving multicast MBS service in 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 23.247 [85]).
e) If the HPLMN (if the EHPLMN list is not present or is empty) or a EHPLMN (if the list is present) or a higher priority PLMN is not found, the MS shall remain on the VPLMN.
f) In steps i), ii) and iii) of clause 4.4.3.1.1 the MS shall limit its attempts to access higher priority PLMN/access technology combinations to PLMN/access technology combinations of the same country as the current serving VPLMN, as defined in Annex B.
EXCEPTION: If the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, the MS may attempt to access higher priority PLMN/access technology combinations irrespective of their MCC values.
EXCEPTION: If the MS is in a VPLMN, the MS may attempt to access higher priority PLMNs with a shared MCC with satellite NG-RAN access technology or satellite E-UTRAN access technology irrespective of their MCC values.
f1) In the case that the MS has a stored "Equivalent PLMNs" list the MS shall only select a PLMN if it is of a higher priority than those of the same country as the current serving PLMN which are stored in the "Equivalent PLMNs" list.
EXCEPTION: If the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, the MS shall only select a PLMN if it is of a higher priority than those which are stored in the "Equivalent PLMNs" list.
EXCEPTION: If the MS is in a VPLMN, the MS shall only select a PLMN if it is of a higher priority than those of the same country as the current serving PLMN or those with a shared MCC with satellite NG-RAN access technology or satellite E-UTRAN access technology which are stored in the "Equivalent PLMNs" list.
g) Only the priority levels of Equivalent PLMNs of the same country as the current serving VPLMN, as defined in Annex B, and which are not in the list of "PLMNs where registration was aborted due to SOR" if the UE has a list of "PLMNs where registration was aborted due to SOR" shall be taken into account to compare with the priority level of a selected PLMN.
h) If the PLMN of the highest priority PLMN/access technology combination available is the current VPLMN, or one of the PLMNs in the "Equivalent PLMNs" list and is not in the list of "PLMNs where registration was aborted due to SOR" if the UE has a list of "PLMNs where registration was aborted due to SOR", the MS shall remain on the current PLMN/access technology combination.
i) In step iii) of clause 4.4.3.1.1 the MS shall consider PLMNs which are in the list of "PLMNs where registration was aborted due to SOR" as lowest priority, if the UE has a list of "PLMNs where registration was aborted due to SOR".
j) In steps i), ii) and iii) of clause 4.4.3.1.1, if signal level enhanced network selection is applicable (see clause 3.11 and step d) of clause 4.4.3.5), the MS shall only select a PLMN, if the received signal quality of the candidate PLMN/access technology combination is equal to or greater than the "Operator controlled signal threshold per access technology".
NOTE 2: As an MS implementation option, the MS can make an attempt when the timer TD, TE, TF, TG, TH, TL or TS expires and there is a PLMN/access technology combination which the MS could not select while the timer was running (e.g. the PLMN was in the list of PLMNs where voice service was not possible in E-UTRAN) that is higher priority than the current serving PLMN and belongs to the same country as the current serving PLMN, as defined in Annex B.
NOTE 3: As an MS implementation option, upon a transition in or out of international areas, a UE supporting satellite NG-RAN or satellite E-UTRAN can attempt to obtain service on a higher priority PLMN as defined in this clause. It is up to the UE implementation to determine when it is transitioning in and out of international areas. What constitutes an international area is out of scope of this specification and not the responsibility of 3GPP.
4.4.3.3.1.2 Automatic and manual network selection modes when registered for disaster roaming services
If the MS is registered for disaster roaming services, the MS shall periodically attempt to obtain service on an allowable PLMN of the same country as the current serving PLMN in accordance with the requirements as defined in the Automatic Network Selection Mode in clause 4.4.3.1.1.
If the MS is registered for disaster roaming services, timer T is either in the range 30 minutes to 40 hours in 30 minute steps, or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 60 minutes is used for T.
If the MS is configured with the MinimumPeriodicSearchTimer as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40], the MS shall not use a value for T that is less than the MinimumPeriodicSearchTimer. If the value stored in the SIM, or the default value for T (when no value is stored in the SIM), is less than the MinimumPeriodicSearchTimer, then T shall be set to the MinimumPeriodicSearchTimer.
The MS does not stop timer T, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when it activates power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or mobile initiated connection only mode (MICO) as described in 3GPP TS 24.501 [64].
The MS does not stop timer T when it activates unavailability period as described in 3GPP TS 24.501 [64].
The attempts to obtain service on an allowable PLMN shall be as specified below:
a) The periodic attempts shall only be performed in automatic mode when the MS is registered for disaster roaming services and does not have a PDU session for emergency services;
a1) The MS shall make the first attempt after a period of at least 2 minutes and at most the time configured for T, after completion of the initial registration for disaster roaming services or of the mobility registration for disaster roaming services;
b) The MS shall make the following attempts if the MS is registered for disaster roaming services at time T after the last attempt;
c) The periodic attempts shall only be performed by the MS while in idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]);
d) The periodic attempts may be postponed:
- while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]);
- while the MS is receiving eMBMS transport service in idle mode (see 3GPP TS 23.246 [68]);
- while the MS is receiving broadcast MBS service in idle mode (see 3GPP TS 23.247 [85]) or in 5GMM-CONNECTED mode with RRC inactive indication;
- till the next eDRX occasion while the MS is configured with eDRX;
- while the MS is in relaxed monitoring (see 3GPP TS 36.304 [43]);
- while the MS is in Mobile Initiated Connection Only mode (MICO);
- while the unavailability period is activated in MS as described in 3GPP TS 24.501 [64]; or
- while the MS is receiving multicast MBS service in 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 23.247 [85]).
e) The MS shall limit its attempts to access allowable PLMN/access technology combinations of the same country as the current serving VPLMN, as defined in Annex B.
EXCEPTION: If the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, the MS may attempt to access higher priority PLMN/access technology combinations irrespective of their MCC values.
EXCEPTION: If the MS is in a VPLMN through non-satellite access, the MS may attempt to access higher priority PLMNs with a shared MCC with satellite NG-RAN access technology or satellite E-UTRAN access technology.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.3.2 Manual CSG selection
|
The procedure of clause 4.4.3.1.3 is followed.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.4 Investigation Scan for higher prioritized PLMN
|
The support of this procedure is mandatory if the ME supports GSM COMPACT and otherwise optional.
An MS capable of both GSM voice and packet service shall, when indicated in the SIM, investigate if there is service from a higher prioritized PLMN not offering GSM voice service, either HPLMN (if the EHPLMN list is not present or is empty) or one of its EHPLMNs (if the EHPLMN list is present) or a PLMN in a "PLMN Selector with Access Technology " data file on the SIM.
The MS shall scan for PLMNs in accordance with the requirements described for automatic network selection mode in clause 4.4.3.1.1 that are applicable to i), ii) and iii) with the exception of requirement a) and b) in clause 4.4.3.1. Requirement a) and b) that are specified for automatic network selection mode in clause 4.4.3.1 shall be ignored during the investigation scan.
If indicated on the SIM, the investigation scan shall be performed:
i) After each successful PLMN selection and registration is completed, when the MS is in idle mode. This investigation scan may rely on the information from the already performed PLMN selection and may not necessarily require a rescan
ii) When the MS is unable to obtain normal service from a PLMN, (limited service state) see clause 3.5.
The investigation scan is restricted to automatic selection mode and shall only be performed by an MS that is capable of both voice and packet data. It shall only be performed if the selected PLMN is not already the highest prioritized PLMN in the current country. (HPLMN in home country, otherwise according to PLMN selector lists)
The MS shall return to RPLMN after the investigation scan is performed.
If a higher prioritized PLMN not offering GSM voice service is found, this shall be indicated to the user. The MS shall not select the PLMN unless requested by the user.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.3.5 Periodic attempts for signal level enhanced network selection
|
If signal level enhanced network selection is applicable (see clause 3.11) and the received signal quality of registered PLMN observed over an averaging window is lower than the "Operator controlled signal threshold per access technology" the MS shall periodically attempt to obtain service on an allowable PLMN/access technology combination for which the received signal quality of the candidate PLMN/access technology combination is equal to or greater than the "Operator controlled signal threshold per access technology" in accordance with the requirements that are applicable to i), ii), iii), iv) and v) as defined in the Automatic Network Selection Mode in clause 4.4.3.1.1. For this purpose, the value of the timer TSENSE is configured with an MS implementation specific value with a minimum value of 2 min and a maximum value set to the value applicable for timer T as defined in clause 4.4.3.3.1.1.
The averaging window shall be shorter than the value of the timer TSENSE.
The MS does not stop timer TSENSE, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when it activates power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or mobile initiated connection only mode (MICO) as described in 3GPP TS 24.501 [64].
The MS does not stop timer TSENSE, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when the access stratum is de-activated due to discontinuous coverage (see 3GPP TS 23.401 [58] and 3GPP TS 24.301 [23A]) or when the MS activates unavailability period as described in 3GPP TS 24.501 [64].
The attempts to obtain service on an allowable PLMN shall be as specified below:
a) The periodic attempts shall only be performed in automatic mode, and not while the MS is attached for emergency bearer services, is registered for emergency services, has a PDN connection for emergency bearer services or has a PDU session for emergency services.
b) When the MS detects that the received signal quality of the current cell of the registered PLMN is below the "Operator controlled signal threshold per access technology" either upon registration or any time later, the MS shall start timer TSENSE, if not already running.
c) If upon expiry of timer TSENSE the received signal quality of the registered PLMN observed over an averaging window is equal to or greater than the "Operator controlled signal threshold per access technology" the MS shall stay on the current selected PLMN. If timer T defined in clause 4.4.3.3.1.1 expires while timer TSENSE is running and the received signal quality of registered PLMN observed over an averaging window is lower than the "Operator controlled signal threshold per access technology", the MS shall stop timer TSENSE and shall perform the actions defined in this clause instead of the action defined for timer T expiry defined in clause 4.4.3.3.1.1.
d) If the received signal quality of the registered PLMN and all other available and allowable PLMN/access technology combinations are lower than the "Operator controlled signal threshold per access technology", the MS shall stop applying signal level enhanced network selection and repeat the network selection procedure as specified in clause 4.4.3.3.1.1.
e) The attempts shall only be performed by the MS while in idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]).
f) The attempts may be postponed:
- while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or when the access stratum is deactivated due to discontinuous coverage or when the UE activated unavailability period (see 3GPP TS 23.401 [58] and 3GPP TS 24.301 [23A]);
- while the MS is receiving eMBMS transport service in idle mode (see 3GPP TS 23.246 [68]);
- till the next eDRX occasion while the MS is configured with eDRX;
- while the MS is in relaxed monitoring (see 3GPP TS 36.304 [43]);
- while the MS is in Mobile Initiated Connection Only mode (MICO).
g) The MS shall limit its attempts to access allowable PLMN/access technology combinations of the same country as the current serving VPLMN, as defined in Annex B.
EXCEPTION: If the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, the MS may attempt to access higher priority PLMN/access technology combinations irrespective of their MCC values.
EXCEPTION: If the MS is in a VPLMN through non-satellite access, the MS may attempt to access higher priority PLMNs with a shared MCC with satellite NG-RAN access technology or satellite E-UTRAN access technology.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.4 Abnormal cases
|
If there is no SIM in the MS, if there is an authentication failure, or if the MS receives an "IMSI unknown in HLR", "illegal ME" or "illegal MS" response to an LR request, then effectively there is no selected PLMN ("No SIM" state). In these cases, the states of the cell selection process are such that no PLMN selection information is used. Except when performing GPRS attach, EPS attach for emergency bearer services, an initial registration for emergency services, or EPS attach for access to RLOS, no further attempts at registration on any PLMN are made until the MS is switched off and on again, or a SIM is inserted. When performing GPRS attach, EPS attach for emergency bearer services, an initial registration for emergency services or EPS attach for access to RLOS, the PLMN of the current serving cell is temporarily considered as the selected PLMN.
When in Automatic Network Selection mode and the MS is in the "not updated" state with one or more suitable cells to camp on; then after the maximum allowed unsuccessful LR requests (controlled by the specific attempt counters) the MS may continue (or start if it is not running) the user reselection procedure of clause 4.4.3.2.1.
A multi mode MS that also supports 3GPP2 access technology may fall back to 3GPP2 mode if no SIM is inserted.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.5 Roaming not allowed in this LA or TA
|
If in either PLMN selection mode the LR response "Roaming not allowed in this LA" or "Roaming not allowed in this TA" is received:
The PLMN Automatic or Manual Mode Selection Procedure of clause 4.4.3.1 are followed, depending on whether the MS is in automatic or manual mode.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.4.6 Steering of roaming
|
If the MS receives a USAT REFRESH command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming", the MS shall:
a) replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME with the list provided in the REFRESH command, if any, or replace the SOR-CMCI in the ME with the SOR-CMCI provided in REFRESH command, if any, or both;
b) delete the PLMNs identified by the list in the REFRESH command from the Forbidden PLMN list and from the Forbidden PLMNs for GPRS service list, if they are present in these lists. This includes any information stored in the SIM and the ME internal memory;
c) take the new information into account in subsequent attempts to access a higher priority PLMN; and
d) 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 order to avoid unnecessary signalling, the network operator should avoid repeatedly using steering of roaming of a particular MS.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.5 Location registration process
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.5.1 General
|
When the MS is switched on and capable of services requiring registration, the action taken by the location registration process is as follows:
a) SIM present and no LR needed (because of the status of the stored registration area identity and "attach" flag): The MS is in the update state "Updated";
b) SIM present and LR needed: A LR request is made;
c) No SIM present: The MS enters the update state "Idle, No IMSI".
In case b) above, and subsequently whenever a LR request is made, the MS enters a state depending on the outcome of the LR request, as listed in clause 4.3.3 above. In case c) the GPRS and the non-GPRS update state enters "Idle, No IMSI".
Whenever the MS goes to connected mode and then returns to idle mode again, the MS selects the appropriate state.
A multi mode MS that also supports 3GPP2 access technology may fall back to 3GPP2 mode if no SIM is inserted.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.5.2 Initiation of Location Registration
|
An LR request indicating Normal Updating is made when, in idle mode,
- the MS changes cell while the update status is "NOT UPDATED"; (for MS capable of GPRS and non-GPRS services when at least one of both update statuses is "NOT UPDATED")
- the MS detects that it has entered a new registration area, i.e., when the received registration area identity differs from the one stored in the MS, and the LAI, TAI or PLMN identity is not contained in any of the lists of "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs" respectively, while being in one of the following update statuses:
- UPDATED;
- NOT UPDATED;
- ROAMING NOT ALLOWED.
- the MS detects that it has entered a new registration area, i.e., when the received registration area identity differs from the one stored in the MS, and the MS is attached for access to RLOS;
- the MS detects that it has entered a registration area that has the same identity as the one stored in the MS, while the update status is "ROAMING NOT ALLOWED", and
the LAI, TAI or PLMN identity is not contained in any of the lists of "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs" respectively; and
- if the selected cell is a satellite NG-RAN cell or a satellite E-UTRAN cell, it does not fulfil the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, i.e. it is considered as candidate for PLMN selection.
- the periodic location updating timer expires while the non-GPRS update status is "NOT UPDATED" (triggers location updating);
- the periodic routing area update timer expires while the GPRS update status is "NOT UPDATED" (triggers routing area update);
- the periodic tracking area update timer expires while the EPS update status is "NOT UPDATED" (triggers tracking area update);
- the periodic registration update timer expires while the 5GS update status is "NOT UPDATED" (triggers mobility and periodic registration update procedure);
- a manual network reselection has been performed, an acceptable cell of the selected PLMN or the selected SNPN is present, and the MS is not in the update status "UPDATED" on the selected PLMN or the selected SNPN; or
- emergency bearer services over packet services are requested by upper layers.
An MS which is attached for PS services other than RLOS and enters a new PLMN shall perform a routing area update or a tracking area update or an MS which is registered via NG-RAN and enters a new PLMN or SNPN shall perform a registration update if the following conditions are fulfilled:
a) if the MS:
1) does not operate in SNPN access operation mode over 3GPP access, is in S1 mode or N1 mode and the currently stored TAI list does not contain the TAI of the current serving cell; or
2) operates in SNPN access operation mode over 3GPP access;
b) the LAI, TAI or PLMN identity of the current serving cell is not contained in any of the lists "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs", or the MS has a PDN connection for emergency bearer services, or the MS has a PDU session for emergency services;
b1) if the selected cell is a satellite NG-RAN cell or a satellite E-UTRAN cell, it does not fulfil the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, i.e. it is considered as candidate for PLMN selection; and
c) the current update state is different from "Idle, No IMSI"; and
1) the MS is configured to perform the attach procedure with IMSI at PLMN change (see "AttachWithIMSI" leaf of the NAS configuration MO in 3GPP TS 24.368 [50] or USIM file NASCONFIG in 3GPP TS 31.102 [40]) and the new PLMN is the registered PLMN or an equivalent PLMN; or
2) the MS is not configured to perform the attach procedure with IMSI at PLMN change.
An MS which is attached for access to RLOS and enters a new PLMN shall perform tracking area update if the following condition is fulfilled:
- the currently stored TAI list does not contain the TAI of the current serving cell.
If the new PLMN the MS has entered is neither the registered PLMN nor an equivalent PLMN, an MS which is attached for PS services and configured to perform the attach procedure with IMSI at PLMN change (see "AttachWithIMSI" leaf of the NAS configuration MO in 3GPP TS 24.368 [50] or USIM file NASCONFIG in 3GPP TS 31.102 [40]) shall perform an attach procedure using IMSI as mobile identity.
An LR request indicating periodic location updating is made when, in idle mode, the periodic location updating timer expires while the non-GPRS update status is "UPDATED".
An LR request indicating periodic routing area update is made when the periodic routing area update timer expires while the GPRS update status is "UPDATED", except when the MS is attached for emergency bearer services.
An LR request indicating periodic tracking area update is made when the periodic tracking area update timer expires while the EPS update status is "UPDATED", except when the MS is attached for emergency bearer services.
An LR request indicating Periodic Registration Updating is made when the periodic registration timer expires while the 5GS update status is "UPDATED", except when the MS is registered for emergency services.
An LR request indicating IMSI attach is made when the MS is activated in the same location area in which it was deactivated while the non-GPRS update status is "UPDATED", and the system information indicates that IMSI attach/detach shall be used.
A GPRS attach is made by a GPRS MS when activated and capable of services which require registration. A GPRS attach may only be performed if the selected PLMN is not contained in the list of "forbidden PLMNs for GPRS service". Depending on system information about GPRS network operation mode MSs operating in MS operation mode A or B perform combined or non-combined location registration procedures. When the combined routing area update or GPRS attach is accepted with indication "MSC not reachable" or is not answered the MS performs also the corresponding location updating procedure or falls back to a GPRS only MS. When the combined routing area update or GPRS attach is rejected with cause "GPRS not allowed" the GPRS update status is "ROAMING NOT ALLOWED" and the MS performs the corresponding location updating procedure.
An LR request indicating Disaster Roaming registration updating is made when the MS supporting MINT needs to register to the PLMN offering disaster roaming services for the first time.
Furthermore, an LR request indicating normal location updating is also made when the response to an outgoing request shows that the MS is unknown in the VLR or SGSN, respectively.
Table 2 in clause 5 summarizes the events in each state that trigger a new LR request. The actions that may be taken while being in the various states are also outlined in table 2.
A GPRS MS which is both IMSI attached for GPRS and non-GPRS services and which is capable of simultaneous operation of GPRS and non-GPRS services shall perform routing area update in connected mode when it has entered a new routing area which is not part of a LA contained in the list of "forbidden location areas for roaming" or "forbidden location areas for regional provision of service".
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.5.3 Periodic Location Registration
|
A Periodic Location Updating timer (for non-GPRS operation), a Periodic Routing Area Update timer (for GPRS operation), a Periodic Tracking Area Update timer (for EPS operation) and a Periodic Registration Update timer (for 5GS operation) with the following characteristics shall be implemented in the MS (MS shall implement all timers corresponding to supported operations):
i) Upon switch on of the MS or when the system information indicates that periodic location registration shall be applied, and the timer is not running, the timer shall be loaded with a random value between 0 and the broadcast or signalled time‑out value and started.
ii) The time‑out value for the periodic location updating timer shall be within the range of 1 deci‑hour to 255 deci‑hours with a granularity of 1 deci‑hour.
iii) When the timer reaches its expiry value, it shall be initiated with respect to the relevant time‑out value, and the MS shall initiate the periodic location registration corresponding to the expired timer. If the MS is attached for emergency bearer services or the MS is registered for emergency services, the MS shall locally detach instead of performing periodic location registration.
iv) The periodic location updating timer shall be prevented from triggering periodic location updating during connected mode. When the MS returns to idle mode, the periodic location updating timer shall be initiated with respect to the broadcast time‑out value, then started. Thereafter, the procedure in iii) shall be followed.
v) The periodic routing area update timer shall be prevented from triggering the periodic routing area update during Ready state. At transition from Ready to Standby state the periodic routing area update timer shall be initiated with respect to its time‑out value, then started. Thereafter, the procedure in iii) shall be followed.
vi) If the MS performs a successful combined routing area update the periodic location updating timer shall be prevented from triggering the periodic location updating until the MS starts using location updating procedure, for example because of a changed network operation mode or the MS uses non-GPRS services only.
vii) When a change in the time‑out value occurs (at a change of serving cell or a change in the broadcast time‑out value or a change in the signalled time-out value), the related timer shall be reloaded so that the new time to expiry will be: "old time to expiry" modulo "new time‑out value".
viii) The periodic tracking area update timer shall be prevented from triggering periodic tracking Area updating during connected mode. When the MS returns to idle mode, the periodic tracking area update timer shall be initiated with respect to the signalled time‑out value, then started. Thereafter, the procedure in iii) shall be followed.
ix) The periodic registration update timer shall be prevented from triggering periodic registration updating during connected mode. If periodic timer is not running due to Strictly periodic registration feature, when the MS returns to idle mode, the periodic registration update timer shall be initiated with respect to the signalled time‑out value, then started. Thereafter, the procedure in iii) shall be followed.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.5.4 IMSI attach/detach operation
|
The system information will contain an indicator indicating whether or not IMSI attach/detach operation is mandatory to use in the cell. The MS shall operate in accordance with the received value of the indicator.
A GPRS MS shall perform GPRS attach/detach procedures independent of the value of the IMSI attach/detach indicator. When a GPRS MS has to perform IMSI attach/detach independent of GPRS procedures (for example GPRS network operation mode 2) the handling described in the clause above applies.
When IMSI attach/detach operation applies, an MS shall send the IMSI detach message to the network when the MS is powered down or the SIM is removed while the update status is "UPDATED". The IMSI detach message will not be acknowledged by the network.
When the MS returns to the active state, the MS shall perform an LR request indicating IMSI attach, provided that the MS still is in the same registration area. If the registration area has changed, an LR request indicating normal location updating according to clause 4.5.2 shall be performed.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.5.5 No Suitable Cells In Location Area
|
If during location registration the LR response "No Suitable Cells In Location Area" or "No Suitable Cells In Tracking Area" is received:
- The MS shall attempt to find another LA or TA of the same PLMN, the same SNPN, an equivalent PLMN or an equivalent SNPN, on which it received the LR response. If the MS is able to find another LA or TA it shall attempt registration. If the MS is unable to find an LA or TA, the PLMN Automatic or Manual Mode Selection Procedure of clause 4.4.3.1 or the SNPN Automatic or Manual Mode Selection Procedure of clause 4.9.3.1 shall be followed, depending on whether the MS is in automatic or manual mode and whether the MS operates in SNPN access operation mode over 3GPP access.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.6 Service indication (A/Gb mode only)
|
This is an indication to the user that service or CTS service is available.
The service indication should be set if the following conditions are all satisfied:
a) Cell Selection: Camped on a suitable cell and in updated state, or in connected mode having been camped on a suitable cell.
b) Location registration: In updated state, for MSs capable of services requiring registration.
A specific CTS service indication should be set when the CTS MS is attached to a CTS FP.
However due to the fact that there may be some transitory changes of state, the service indication is permitted to continue to be set for up to 10 seconds after the above conditions cease to be met. Also the service indication is permitted to take up to 1 second to be set after the above conditions are met.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.7 Pageability of the mobile subscriber
|
An MS is required to listen to all paging messages that could address it (see 3GPP TS 45.002 [24]), when the following conditions are all satisfied:
- A SIM is inserted;
- The MS is camped on a cell;
- The MS is not in state "Idle, No IMSI"; and
- The MS is not performing the task to search for available PLMNs or available SNPNs. (Whenever possible during this task, the MS should listen for paging.). However, when the MS is camped on a cell, is registered in a PLMN and is performing its regular search for a higher priority PLMN, as specified in 3GPP TS 22.011 [9], then it shall listen to all paging messages that could address it.
NOTE: In A/Gb mode, during cell reselection there is a certain period when the MS is no longer camped on the old cell but must decode the full BCCH, CPBCCH or EC-BCCH before camping on the new cell. This leads to a period of slightly more than 8 51 frame multiframes when the MS will not necessarily be pageable (full BCCH or CPBCCH is decoded) or up to 32 51 frame multiframes when the MS will not necessarily be pageable (full EC-BCCH is decoded).
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.8 MM Restart Procedure
|
In some cases, e.g. on change of SIM data, there is a need for the MM to be restarted without the need for user intervention.
To perform the procedure the MS shall behave as if the SIM is removed and afterwards a new SIM is inserted.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9 SNPN selection process
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.1 General
|
The MS operating in SNPN access operation mode over 3GPP access shall perform the SNPN selection process.
The MS not operating in SNPN access operation mode over 3GPP access shall not perform the SNPN selection process.
There are two SNPN selection modes - automatic SNPN selection mode and manual SNPN selection mode.
In the SNPN selection process, the MS shall consider only the access networks of the NG-RAN access technology.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.2 Registration on an SNPN
|
The MS shall perform registration on the SNPN if the MS is capable of services which require registration. In both automatic SNPN selection mode and manual SNPN selection mode, the concept of registration on an SNPN is used. An MS successfully registers on an SNPN if:
a) the MS has found a suitable cell of the SNPN to camp on; and
b) an LR request from the MS has been accepted in the registration area of the cell on which the MS is camped.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3 SNPN selection
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.0 General
|
The ME is configured with a "list of subscriber data" containing zero or more entries. Each entry of the "list of subscriber data" consists of:
a) a subscriber identifier in the form of a SUPI with the SUPI format "network specific identifier" containing a network-specific identifier or with the SUPI format "IMSI" containing an IMSI, except when the subscribed SNPN uses:
1) the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or
2) the 5G AKA based primary authentication and key agreement procedure;
NOTE 1: A subscriber identifier in the form of a SUPI with the SUPI format "network specific identifier" containing a network-specific identifier or with the SUPI format "IMSI" containing an IMSI, is available in USIM if the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure.
NOTE 2: If the MS supports access to an SNPN using credentials from a credentials holder and is configured with the SNPN selection parameters as described in h), the subscriber identifier in the form of a SUPI configured in the ME or the USIM needs to be:
- with the SUPI format "network specific identifier"; or
- with the SUPI format "IMSI", if the subscribed SNPN has an assigned PLMN ID.
b) credentials except when the subscribed SNPN uses:
1) the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or
2) the 5G AKA based primary authentication and key agreement procedure.
If the MS supports access to an SNPN using credentials from a credentials holder, the credentials can include an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure;
NOTE 3: Credentials are available in USIM if the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure. If the MS supports access to an SNPN using credentials from a credentials holder, credentials available in USIM can include an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure.
ba) optionally, a routing indicator, except when the subscribed SNPN uses:
1) the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or
2) the 5G AKA based primary authentication and key agreement procedure;
NOTE 3A: Routing indicator is available in USIM if the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure.
bb) optionally, the protection scheme identifier as specified in 3GPP TS 33.501 [66], except when the subscribed SNPN uses:
1) the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or
2) the 5G AKA based primary authentication and key agreement procedure;
If the protection scheme identifier is configured in the entry of the "list of subscriber data" and not set to "null-scheme", the entry of the "list of subscriber data" also contains the home network public key and the home network public key identifier as specified in in 3GPP TS 33.501 [66];
NOTE 3B: The protection scheme identifier, the home network public key and the home network public key identifier are available in USIM if the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure.
c) an SNPN identity of the subscribed SNPN;
d) optionally, the unified access control configuration indicating for which access identities (see 3GPP TS 24.501 [64]) the ME is configured, when the MS accesses an SNPN using the entry.
Access identity 11 or 15, if configured, is applicable for the MS only in the subscribed SNPN.
Access identity 12, 13 or 14, if configured, is applicable for the MS only:
1) in the subscribed SNPN; and
2) if the MCC of the SNPN identity of the subscribed SNPN is not the MCC of value 999, in the non-subscribed SNPNs of the same country as the subscribed SNPN;
Access identity 1 or 2, if configured, is applicable for the MS only:
1) in the subscribed SNPN;
2) if the MCC of the SNPN identity of the subscribed SNPN is not the MCC of value 999, in the non-subscribed SNPNs of the same country as the subscribed SNPN; and
3) in an SNPN equivalent to the subscribed SNPN;
e) zero or more sets of pre-configured URSP rules (see 3GPP TS 24.526 [77]), each set for the subscribed SNPN or a non-subscribed SNPN;
f) optionally, the default configured NSSAI (see 3GPP TS 24.501 [64]);
g) optionally, if the MS supports access to an SNPN using credentials from a credentials holder:
1) the SNPN selection parameters, consisting of:
i) a user controlled prioritized list of preferred SNPNs, where each entry contains an SNPN identity;
ii) a credentials holder controlled prioritized list of preferred SNPNs, where each entry contains an SNPN identity;
iii) a credentials holder controlled prioritized list of Group IDs for Network Selection (GINs); and
iv) optionally, if the MS supports access to an SNPN providing access for localized services in SNPN, the SNPN selection parameters for access for localized services in SNPN, consisting of:
A) a "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", where each entry contains:
- an SNPN identity;
- validity information consisting of time validity information and optionally, location validity information; and
- optionally, location assistance information; and
B) a "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", where each entry contains:
- a GIN;
- validity information consisting of time validity information and optionally, location validity information; and
- optionally, location assistance information; and
NOTE 3C: The location assistance information, if available, is used to aid the UE where to search for SNPN providing the localized services in SNPN.
NOTE 3D: The location validity information, if available, is used to indicate the area where access to SNPN for accessing the localized services in SNPN is allowed.
NOTE 3E: SNPN can provide both localized services in SNPN and services which are not localized services in SNPN, in the same location, for a UE.
2) optionally, an indication to expect to receive the steering of roaming information due to initial registration in a non-subscribed SNPN;
NOTE 4: How the ME is configured with the "list of subscriber data" is out of scope of 3GPP in this release of the specification.
NOTE 5: Multiple entries can include the same subscriber identifier and credentials.
NOTE 6: Handling of more than one entry with the same SNPN identity is left up to MS implementation.
NOTE 7: Handling of the case when the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure and the MS has multiple valid USIMs (3GPP TS 31.102 [40]) is left up to MS implementation.
NOTE 8: To enable UE mobility between SNPNs in 5GMM-IDLE mode, SNPN identities in the credentials holder controlled prioritized list of preferred SNPNs are assumed to be globally-unique SNPN identities.
h) optionally:
1) an indication of whether the MS shall ignore all warning messages received in the subscribed SNPN or an equivalent SNPN of the subscribed SNPN; and
2) an indication of whether the MS shall ignore all warning messages received in an non-subscribed SNPN or an equivalent SNPN of the non-subscribed SNPN.
NOTE 9: The ME can be configured with an indication to use anonymous SUCI associated with an entry of "list of subscriber data" when the EAP method associated with the credentials of the entry supports SUPI privacy at the EAP layer.
NOTE 10: Anonymous SUCI is not used if the subscribed SNPN of the entry uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure.
The MS which supports onboarding services in SNPN shall be pre-configured with default UE credentials for primary authentication and may be pre-configured with onboarding SNPN selection information. Contents of the onboarding SNPN selection information are MS implementation specific. Contents of default UE credentials for primary authentication are out of scope of 3GPP.
Additionally, if the MS has a USIM with a PLMN subscription, the ME may be configured with the SNPN selection parameters associated with the PLMN subscription, consisting of:
a) a user controlled prioritized list of preferred SNPNs, where each entry contains an SNPN identity;
b) a credentials holder controlled prioritized list of preferred SNPNs, where each entry contains an SNPN identity;
c) a credentials holder controlled prioritized list of GINs; and
d) optionally, if the MS supports access to an SNPN providing access for localized services in SNPN, with the following SNPN selection parameters for access for localized services in SNPN associated with the PLMN subscription, consisting of:
1) a "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", where each entry contains:
- an SNPN identity;
- validity information consisting of time validity information and optionally, location validity information; and
- optionally, location assistance information; and
2) a "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", where each entry contains:
- a GIN;
- validity information consisting of time validity information and optionally, location validity information; and
- optionally, location assistance information
NOTE 10A: The location assistance information, if available, is used to aid the UE where to search for SNPN providing the localized services in SNPN.
NOTE 10B: The location validity information, if available, is used to indicate the area where access to SNPN for accessing the localized services in SNPN is allowed.
and with the following configuration parameters associated with the PLMN subscription:
a) zero or more sets of pre-configured URSP rules (see 3GPP TS 24.526 [77]), each set for the HPLMN or a non-subscribed SNPN; and
b) optionally, an indication to expect to receive the steering of roaming information due to initial registration in a non-subscribed SNPN.
NOTE 11: To enable MS mobility between SNPNs in 5GMM-IDLE mode, SNPN identities in the credentials holder controlled prioritized list of preferred SNPNs are assumed to be globally-unique SNPN identities.
NOTE 12: If an MS accesses an SNPN using the PLMN subscription, access identity 1, 2, 12, 13, or 14 is configured in the USIM of the MS, and the SNPN is of the same country as the HPLMN, then the configured access identity 1, 2, 12, 13, or 14 is applicable for the MS.
NOTE 13: If an MS accesses an SNPN using the PLMN subscription, an indication of whether the MS shall ignore all warning messages in an SNPN is configured in the USIM of the MS.
NOTE 14: Handling of URSP rules is specified in 3GPP TS 24.526 [77].
The time validity information contains one or more time periods.
The location validity information contains one or more location information.
If:
a) the location validity information is not available and at least one time period of the time validity information matches UE's current time; or
b) the location validity information is available, at least one time period of the time validity information matches UE's current time and at least one location information of the location validity information matches UE's current location;
then the validity information is met otherwise the validity information is not met.
The MS shall maintain a list of "temporarily forbidden SNPNs" and a list of "permanently forbidden SNPNs" in the ME. Each entry of those lists consists of an SNPN identity. If the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the MS shall maintain one list of “temporarily forbidden SNPNs” and one list of “permanently forbidden SNPNs” per entry of the “list of subscriber data”. If the MS supports access to an SNPN using credentials from a credentials holder, the MS shall maintain one list of "temporarily forbidden SNPNs" and one list of "permanently forbidden SNPNs" per the PLMN subscription. If the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the MS shall use the lists associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. In addition, if the MS supports access to an SNPN providing access for localized services in SNPN, the MS shall maintain one list of "temporarily forbidden SNPNs for access for localized services in SNPN" and one list of "permanently forbidden SNPNs for access for localized services in SNPN" per entry of the "list of subscriber data" and per the PLMN subscription. If the MS supports access to an SNPN providing access for localized services in SNPN, the MS shall use the lists associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. In addition, if the MS supports onboarding services in SNPN, a list of "permanently forbidden SNPNs for onboarding services in SNPN" and a list of "temporarily forbidden SNPNs for onboarding services in SNPN" shall be maintained.
The MS shall add an SNPN to:
a) the list of "temporarily forbidden SNPNs" which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription;
b) the list of "temporarily forbidden SNPNs for access for localized services in SNPN" associated with 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; or
c) the list of "temporarily forbidden SNPNs for onboarding services in SNPN", if the MS is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN;
if a message with cause value #74 "Temporarily not authorized for this SNPN" (see 3GPP TS 24.501 [64]) is received by the MS in response to an LR request from the SNPN. In addition, if:
- the message is integrity-protected; or
- the message is not integrity-protected, and the value of the SNPN-specific attempt counter for that SNPN is equal to the MS implementation specific maximum value as defined in 3GPP TS 24.501 [64];
then the MS shall start an MS implementation specific timer not shorter than 60 minutes.
The MS shall remove an SNPN from:
a) the list of "temporarily forbidden SNPNs" which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription;
b) the list of "temporarily forbidden SNPNs for access for localized services in SNPN" associated with 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; or
c) the list of "temporarily forbidden SNPNs for onboarding services in SNPN", if the MS is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN;
if:
a) there is a successful LR after a subsequent manual selection of the SNPN;
b) the MS implementation specific timer not shorter than 60 minutes expires;
c) the MS is configured to use timer T3245 and timer T3245 expires;
d) the MS is not configured to use timer T3245, the timer T3247 expires and the value of the SNPN-specific attempt counter for that SNPN is less than the MS implementation specific maximum value as defined in 3GPP TS 24.501 [64];
e) the MS is switched off;
f) an entry of the "list of subscriber data" with the subscribed SNPN identity identifying the SNPN is updated or the USIM is removed 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 selected SNPN; or
g) the selected entry of the "list of subscriber data" is updated or USIM is removed for the selected PLMN subscription.
If an SNPN is removed from the list of "temporarily forbidden SNPNs", list of "temporarily forbidden SNPNs for access for localized services in SNPN" or list of "temporarily forbidden SNPNs for onboarding services in SNPN", the MS shall stop the MS implementation specific timer not shorter than 60 minutes, if running.
NOTE 15: If the MS supports access to an SNPN providing access for localized services in SNPN, the UE ensures that such an SNPN is not inaccessible due to being in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" when the validity information of the SNPN changes from not met to met. As a UE implementation option, the MS can remove an SNPN from the list of "temporarily forbidden SNPNs for access for localized services in SNPN" associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, when the validity information of the SNPN changes from not met to met.
The MS shall add an SNPN to:
a) the list of "permanently forbidden SNPNs" which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription;
b) the list of "permanently forbidden SNPNs for access for localized services in SNPN" associated with 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; or
c) the list of "permanently forbidden SNPNs for onboarding services in SNPN", if the MS is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN;
if a message with cause value #75 "Permanently not authorized for this SNPN", #3 "Illegal UE" (applicable in an onboarding SNPN only), #6 "Illegal ME" (applicable in an onboarding SNPN only), or #7 "5GS services not allowed" (applicable in an onboarding SNPN only) (see 3GPP TS 24.501 [64]) is received by the MS in response to an LR request from the SNPN.
The MS shall remove an SNPN from:
a) the list of "permanently forbidden SNPNs" which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription;
b) the list of "permanently forbidden SNPNs for access for localized services in SNPN" associated with 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; or
c) the list of "permanently forbidden SNPNs for onboarding services in SNPN", if the MS is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN;
if:
a) there is a successful LR after a subsequent manual selection of the SNPN;
b) the MS is configured to use timer T3245 and timer T3245 expires;
c) the MS is not configured to use timer T3245, the timer T3247 expires and the value of the SNPN-specific attempt counter for that SNPN is less than the MS implementation specific maximum value as defined in 3GPP TS 24.501 [64];
d) an entry of the "list of subscriber data" with the subscribed SNPN identity identifying the SNPN is updated or the USIM is removed 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 selected SNPN; or
e) the selected entry of the "list of subscriber data" is updated or USIM is removed for the selected PLMN subscription.
NOTE 16: If the MS supports access to an SNPN providing access for localized services in SNPN, the UE ensures that such an SNPN is not inaccessible due to being in the list of "permanently forbidden SNPNs for access for localized services in SNPN" when the validity information of the SNPN changes from not met to met. As a UE implementation option the MS can remove an SNPN from the list of "permanently forbidden SNPNs for access for localized services in SNPN" associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, when the validity information of the SNPN changes from not met to met.
When the MS reselects to a cell in a shared network, and the cell is a suitable cell for multiple SNPN identities received in the broadcast information as specified in 3GPP TS 38.331 [65], the AS indicates these multiple SNPN identities to the NAS according to 3GPP TS 38.304 [61]. The MS shall select one of these SNPNs. If the registered SNPN is available among these SNPNs, the MS shall not select a different SNPN.
The MS operating in SNPN access operation mode over 3GPP access shall maintain one or more lists of "5GS forbidden tracking areas for roaming", each associated with an SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, entry of the "list of subscriber data" or, if the MS supports access to an SNPN using credentials from a credentials holder, the PLMN subscription. The MS shall use the list of "5GS forbidden tracking areas for roaming" associated with the selected SNPN and, if the MS 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. If the MS selects a new SNPN, the MS shall keep the list of "5GS forbidden tracking areas for roaming" associated with the previously selected SNPN and, if the MS 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. If the number of the lists to be kept is higher than supported, the MS shall delete the oldest stored list of "5GS forbidden tracking areas for roaming". The MS shall delete all lists of "5GS forbidden tracking areas for roaming", periodically (with period in the range 12 to 24 hours) or when the MS is switched off. The MS shall delete the list of "5GS forbidden tracking areas for roaming" associated with an SNPN:
a) when the entry with the subscribed SNPN identifying the SNPN in the "list of subscriber data" is updated;
b) when the USIM is removed if:
- the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or
- the 5G AKA based primary authentication and key agreement procedure;
was performed in the selected SNPN; or
c) if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, when the list of "5GS forbidden tracking areas for roaming" is associated with:
- the entry of the "list of subscriber data" and the entry of the "list of subscriber data" is updated; or
- the PLMN subscription and USIM is removed.
NOTE 17: The number of the lists of "5GS forbidden tracking areas for roaming" supported by the MS is MS implementation specific.
If a message with cause value #15 (see 3GPP TS 24.501 [64]) is received by an MS operating in SNPN access operation mode over 3GPP access, the TA is added to the list of "5GS forbidden tracking areas for roaming" of the selected 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,. The MS shall then search for a suitable cell in the same SNPN but belonging to a TA which is not in the "5GS forbidden tracking areas for roaming" list of the selected 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.
The MS should maintain a list of SNPNs for which the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed". When the MS disables its N1 mode capability due to receipt of a reject from an SNPN with 5GMM cause #27 "N1 mode not allowed":
- the MS should add the SNPN identity of the SNPN which sent a reject with 5GMM cause #27 "N1 mode not allowed" to the list of SNPNs for which the N1 mode capability was disabled and should start timer TJ if timer TJ is not already running. The number of SNPNs for which the N1 mode capability was disabled that the MS can store is implementation specific, but it shall be at least one. The value of timer TJ is MS implementation specific;
- in automatic SNPN selection, the MS shall not select an SNPN for which the N1 mode capability was disabled as SNPN selection candidates, unless no other SNPN is available;
- if the MS is not configured to use timer T3245, the MS maintains a list of SNPN-specific attempt counters for 3GPP access as specified in 3GPP TS 24.501 [64], and T3247 expires, then the MS removes for each SNPN-specific attempt counter for 3GPP access that has a value greater than zero and less than the MS implementation-specific maximum value the respective SNPN from the list of SNPNs for which the N1 mode capability was disabled, as specified in clause 5.3.20.3 in 3GPP TS 24.501 [64]; and
- the MS shall delete stored information on SNPNs for which the N1 mode capability was disabled when the MS is switched off, the USIM is removed, the entries of the "list of subscriber data" for the SNPNs are updated, or timer TJ expires.
NOTE 18: The expiry of timer TJ does not cause a reset of the SNPN-specific attempt counters for 3GPP access (see 3GPP TS 24.501 [64]).
If the MS does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the MS should maintain a list of SNPNs where the N1 mode capability was disabled because IMS voice was not available and the MS's usage setting was "voice centric". If the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the MS should maintain one list of SNPNs where the N1 mode capability was disabled because IMS voice was not available and the MS's usage setting was "voice centric", per entry of the "list of subscriber data" or per the PLMN subscription. If the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the MS shall use the list associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. When the MS disables its N1 mode capability due to IMS voice not available and the MS's usage setting was "voice centric":
- the MS should add the SNPN identity of the SNPN to the list of SNPNs where voice service was not possible in N1 mode and should start timer TK if timer TK is not already running. The number of SNPNs that the MS can store where voice services is not possible is implementation specific, but it shall be at least one. The value of timer TK is MS implementation specific;
- in automatic SNPN selection the MS shall not consider SNPNs where voice service was not possible in N1 mode as SNPN selection candidates, unless no other SNPN is available; and
- the MS shall delete stored information on SNPNs where voice service was not possible in N1 mode when the MS is switched off, the USIM is removed, the entries of the "list of subscriber data" for the SNPNs are updated, or timer TK expires.
The MS may support equivalent SNPNs. If the MS supports equivalent SNPNs, the ME shall store up to one list of equivalent SNPNs:
- per entry of "list of subscriber data"; or
- per the PLMN subscription, if the MS supports access to an SNPN using credentials from a credentials holder.
SNPNs in the list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription shall be regarded by the MS as equivalent to each other for SNPN selection, cell selection, and cell re-selection. The list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription is created, replaced or deleted at the end of each registration procedure. The stored list consists of a list of equivalent SNPNs as provided by the network plus the SNPN identity of the registered SNPN that provided the list. When the MS is switched off, the MS shall keep the stored list(s) so that they can be used for SNPN selection after switch on. The MS shall delete the stored list associated with an entry of "list of subscriber data" or the PLMN subscription, when the USIM is removed, the associated entry of "list of subscriber data" is updated, or the MS registered for emergency services deregisters.
NOTE 19: The MS can provide the list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription to the lower layers.
NOTE 20: The list of equivalent SNPNs is not provided by the network when the MS is registering or is registered for onboarding services in SNPN.
An MS that is registering or registered for emergency services, may access SNPNs in the list of "temporarily forbidden SNPNs", "permanently forbidden SNPNs", "permanently forbidden SNPNs for access for localized services in SNPN", "temporarily forbidden SNPNs for access for localized services in SNPN", "permanently forbidden SNPNs for onboarding services in SNPN" and "temporarily forbidden SNPNs for onboarding services in SNPN". The MS shall not remove any entry from the list "temporarily forbidden SNPNs", "permanently forbidden SNPNs", "permanently forbidden SNPNs for access for localized services in SNPN", "temporarily forbidden SNPNs for access for localized services in SNPN", "permanently forbidden SNPNs for onboarding services in SNPN" and "temporarily forbidden SNPNs for onboarding services in SNPN" as a result of such accesses.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.1 At switch‑on or recovery from lack of coverage
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.1.0 General
|
At switch on, following recovery from lack of coverage, or when the MS starts operating in the SNPN access operation mode over 3GPP access, the MS selects the registered SNPN or an equivalent SNPN (if it is available) using NG-RAN access technology and if necessary (in the case of recovery from lack of coverage, see clause 4.5.2) attempts to perform an LR.
NOTE 1: The MS in automatic SNPN selection mode can end the SNPN search procedure once the registered SNPN or an equivalent SNPN is found on NG-RAN access technology.
NOTE 2: An MS in automatic SNPN selection mode can use location information to determine which SNPNs can be available in its present location.
If successful registration is achieved, the MS indicates the selected SNPN.
If there is no registered SNPN, or registration is not possible due to the SNPN and all equivalent SNPNs, if any, being unavailable or registration failure, unless the MS needs to select an SNPN for onboarding services in SNPN, the MS follows the procedure in clause 4.9.3.1.1 or clause 4.9.3.1.2 depending on its SNPN selection mode. If the MS needs to select an SNPN for onboarding services in SNPN, the MS follows the procedure in clause 4.9.3.1.3 or clause 4.9.3.1.4 depending on its SNPN selection mode for onboarding services in SNPN. At switch on, the MS shall use the SNPN selection mode and the SNPN selection mode for onboarding services in SNPN that were used before switching off.
NOTE 3: If successful registration is achieved, then the current serving SNPN becomes the registered SNPN and the MS does not store the previous registered SNPN for later use.
If registration is not possible on recovery from lack of coverage due to the registered SNPN and all equivalent SNPNs, if any, being unavailable, an MS may, optionally, continue looking for the registered SNPN or an equivalent SNPN for an implementation dependent time.
NOTE 4: An MS registered to an SNPN should behave as described above only if one or more PDU sessions are currently active.
EXCEPTION: As an alternative option to this, if the MS is in automatic SNPN selection mode and it finds coverage of a subscribed SNPN (for the selected entry of "list of subscriber data"), the MS may register to that SNPN and not return to the registered SNPN or equivalent SNPN.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.1.1 Automatic SNPN selection mode procedure
|
If:
- there is at least one entry in the "list of subscriber data"; or
- there is zero or more entries in the "list of subscriber data", the MS has a USIM with a PLMN subscription and the ME is provisioned with the SNPN selection parameters associated with the PLMN subscription,
the MS shall select one entry in the "list of subscriber data", if any, or the PLMN subscription, if any, to be used for automatic SNPN selection. How the MS selects the entry in the "list of subscriber data" or the PLMN subscription is MS implementation specific.
The MS selects an SNPN, if available and allowable, in the following order:
a0) if the MS supports access to an SNPN providing access for localized services in SNPN and access for localized services in SNPN is enabled, then, using the SNPN selection parameters for access for localized services in SNPN in the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription:
1) the SNPN previously selected as result of an entry of a list of bullet a0) 2) or a0) 3) with which the UE was last registered, if validity information of the entry is still met, or the equivalent SNPN if it is available and validity information of the entry of the SNPN previously selected as result of an entry of a list of bullet a0) 2) or a0) 3) with which the UE was last registered is still met;
2) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in an entry of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" (in priority order), if the validity information of the entry is met; and
3) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which broadcast a GIN contained in an entry of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" (in priority order), if the validity information of the entry is met. If more than one such SNPN broadcast the same GIN, the order in which the MS attempts registration on those SNPNs is MS implementation specific;
a) the SNPN with which the UE was last registered or an equivalent SNPN, except if the registered SNPN was previously selected as result of an entry of a list of bullet a0) 2) or a0) 3) and validity information of the entry is no longer met or access for localized services in SNPN is no longer enabled;
b) the SNPN identified by an SNPN identity of the subscribed SNPN in the selected entry of the "list of subscriber data" in the ME, if any;
c) if the MS supports access to an SNPN using credentials from a credentials holder, using the SNPN selection parameters in the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription:
1) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in the user controlled prioritized list of preferred SNPNs (in priority order);
2) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in the credentials holder controlled prioritized list of preferred SNPNs (in priority order);
3) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which broadcast a GIN contained in the credentials holder controlled prioritized list of GINs (in priority order). If more than one such SNPN broadcast the same GIN, the order in which the MS attempts registration on those SNPNs is MS implementation specific; and
4) each SNPN identified by an SNPN identity which is included neither in the SNPN selection parameters of the entries of the "list of subscriber data" nor in the SNPN selection parameters associated with the PLMN subscription, which does not broadcast a GIN which is included in the credentials holder controlled prioritized list of GINs, and which broadcasts an indication that the SNPN allows registration attempts from MSs that are not explicitly configured to select the SNPN. If more than one such SNPN is available, the order in which the MS attempts registration on those SNPNs is MS implementation specific.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
Once the MS selects the SNPN, the MS attempts registrations on the selected SNPN using the NG-RAN access technology, the subscriber identifier and the credentials from the selected entry of the "list of subscriber data" or from the USIM, if the PLMN subscription is selected.
If successful registration is achieved, the MS indicates the selected SNPN.
If:
a) in bullet a0), the MS is unable to select an SNPN for access for localized services in SNPN and the validity information of
- an entry of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN"; or
- an entry of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN",
of the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription is still met;
b) the MS is not registered for emergency services; and
c) the MS does not have an established emergency PDU session,
the MS shall re-attempt to perform the SNPN selection to select an SNPN providing access for localized services in SNPN in accordance with the requirements that are applicable to bullets a0). This re-attempt and subsequent re-attempts if still required is determined by the MS in an implementation specific way, and should be triggered if the validity information is still met.
If registration cannot be achieved because no SNPNs are available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME, the MS indicates "no service" to the user, waits until a new SNPN is available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME and then repeats the procedure.
If there were one or more SNPNs which were available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME but an LR failure made registration on those SNPNs unsuccessful, the MS selects one of those SNPNs again and enters a limited service state.
If an SNPN is being removed from the "temporarily forbidden SNPNs" or the "permanently forbidden SNPNs" list (e.g due to MS implementation specific timer not shorter than 60 minutes expires or timer T3245 expires), and the MS is in limited service state, and the MS does not have a PDU session for emergency services, the MS shall perform SNPN selection as described in subclause 4.9.3.1. If the MS has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection subsequently after the emergency PDU session is released.
If:
a) the MS supports access to an SNPN providing access for localized services in SNPN;
b) the access for localized services in SNPN has been enabled;
c) the MS is in limited service state;
d) the MS does not have a PDU session for emergency services; and
e) an SNPN is being removed from the list of "permanently forbidden SNPNs for access for localized services in SNPN" or "temporarily forbidden SNPNs for access for localized services in SNPN" (e.g due to MS implementation specific timer not shorter than 60 minutes expires, timer T3245 expires or validity information of the SNPN becomes valid);
the MS shall perform SNPN selection as described in subclause 4.9.3.1. If the MS has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection subsequently after the emergency PDU session is released.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.1.2 Manual SNPN selection mode procedure
|
The MS indicates to the user any available SNPNs which meet the criteria specified in bullets a) and b). If the MS does not support access to an SNPN using credentials from a credentials holder, this includes SNPNs in the list of "permanently forbidden SNPNs", and the list of "temporarily forbidden SNPNs". The MS may indicate to the user whether the available SNPNs are present in the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs". If the MS supports access to an SNPN using credentials from a credentials holder, this includes SNPNs in the lists of "permanently forbidden SNPNs", and the lists of "temporarily forbidden SNPNs", each list associated with an entry of the "list of subscriber data" or the PLMN subscription. If the MS supports equivalent SNPNs, this includes SNPNs in the lists of "permanently forbidden SNPNs", and the lists of "temporarily forbidden SNPNs", each list associated with an entry of the "list of subscriber data". The MS may indicate to the user whether the available SNPNs are present in a list of "temporarily forbidden SNPNs" or a list of "permanently forbidden SNPNs" for an entry of the "list of subscriber data" or the PLMN subscription. If the MS supports access to an SNPN providing access for localized services in SNPN, this includes SNPNs in the lists of "permanently forbidden SNPNs for access for localized services in SNPN", and the lists of "temporarily forbidden SNPNs for access for localized services in SNPN", each list associated with an entry of the "list of subscriber data" or the PLMN subscription. If the MS supports access to an SNPN providing access for localized services in SNPN, the MS may indicate to the user whether an available SNPN is identified by an SNPN identity contained in an entry of one of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" and whether the validity information of the entry is met, whether an available SNPN is broadcasting a GIN contained in an entry of one of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" and whether the validity information of the entry is met and whether an available SNPNs are present in a list of "temporarily forbidden SNPNs for access for localized services in SNPN" or a list of "permanently forbidden SNPNs for access for localized services in SNPN" for an entry of the "list of subscriber data" or the PLMN subscription.
a) SNPNs with the following order:
1) identified by an SNPN identity contained in one of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" configured in the ME if the validity information of the entry is met, the MS supports access to an SNPN providing access for localized services in SNPN. Prioritization between the different lists is MS implementation specific;
2) broadcast a GIN contained in one of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" configured in the ME if the validity information of the entry is met, the MS supports access to an SNPN providing access for localized services in SNPN. Prioritization between the different lists is MS implementation specific. If more than one SNPN broadcast the same GIN, the order in which those SNPNs are indicated is MS implementation specific;
3) identified by an SNPN identity contained in one of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" configured in the ME if the validity information of the entry is not met, the MS supports access to an SNPN providing access for localized services in SNPN. Prioritization between the different lists is MS implementation specific;
4) broadcast a GIN contained in one of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" configured in the ME if the validity information of the entry is not met, the MS supports access to an SNPN providing access for localized services in SNPN. Prioritization between the different lists is MS implementation specific. If more than one SNPN broadcast the same GIN, the order in which those SNPNs are indicated is MS implementation specific; and
5) identified by an SNPN identity in an entry of the "list of subscriber data" in the ME, if any. The order in which those SNPNs are indicated is MS implementation specific;
b) if the MS supports access to an SNPN using credentials from a credentials holder, for the SNPNs which broadcast the indication that access using credentials from a credentials holder is supported:
1) each SNPN which is identified by an SNPN identity contained in one of the user controlled prioritized lists of preferred SNPNs configured in the ME. SNPNs included in the same list are indicated in the order in which they are included in the list. Prioritization between the different lists is MS implementation specific;
2) each SNPN which is identified by an SNPN identity contained in one of the credentials holder controlled prioritized lists of preferred SNPNs configured in the ME. SNPNs included in the same list are indicated in the order in which they are included in the list. Prioritization between the different lists is MS implementation specific;
3) each SNPN which broadcasts a GIN contained in one of the credentials holder controlled prioritized lists of GINs configured in the ME. SNPNs broadcasting a GIN included in the same list are indicated in the order in which the GIN is included in the list. Prioritization between the different lists is MS implementation specific. If more than one SNPN broadcast the same GIN, the order in which those SNPNs are indicated is MS implementation specific; and
4) each SNPN identified by an SNPN identity which is not indicated in any of bullets a), b) 1), b) 2) or b) 3). The order in which those SNPNs are indicated is MS implementation specific.
For each of the SNPNs indicated to the user, the MS shall forward a human-readable network name along with the SNPN identity to the upper layers if the system information broadcasted for the SNPN includes the human-readable network name for the SNPN.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
If the UE has a PDU session for emergency services manual SNPN selection shall not be performed.
The user may select an SNPN. If the user selects an SNPN, the MS then initiates registration on this SNPN using the NG-RAN access technology and for such registration the MS shall ignore the contents of the "5GS forbidden tracking areas for roaming", "5GS forbidden tracking areas for regional provision of service", "temporarily forbidden SNPNs", "permanently forbidden SNPNs", "permanently forbidden SNPNs for access for localized services in SNPN" and "temporarily forbidden SNPNs for access for localized services in SNPN". For such registration, the subscriber identifier and the credentials from the selected entry of the "list of subscriber data" or from USIM, if the PLMN subscription is selected, are determined as follows:
- for bullet a) 1) above:
i) the entry of the "list of subscriber data" which contains the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN shall be considered as selected, if the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is included in the entry of the "list of subscriber data" and validity information of the selected SNPN in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is met; or
ii) the PLMN subscription shall be considered as selected, if the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" associated with the PLMN subscription includes the SNPN identity of the selected SNPN and validity information of the selected SNPN in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is met;
- for bullet a) 2) above:
i) the entry of the "list of subscriber data" which contains the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN broadcast by the selected SNPN shall be considered as selected, if the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN broadcasted by the selected SNPN is included in the entry of the "list of subscriber data" and validity information of the GIN in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN is met; or
ii) the PLMN subscription shall be considered as selected, if the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" associated with the PLMN subscription includes the GIN broadcast by the selected SNPN and validity information of the GIN in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN is met;
- for bullet a) 3) above:
i) the entry of the "list of subscriber data" which contains the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN shall be considered as selected, if the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is included in the entry of the "list of subscriber data" and validity information of the selected SNPN in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is not met; or
ii) the PLMN subscription shall be considered as selected, if the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" associated with the PLMN subscription includes the SNPN identity of the selected SNPN and validity information of the selected SNPN in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is not met;
- for bullet a) 4) above:
i) the entry of the "list of subscriber data" which contains the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN broadcast by the selected SNPN shall be considered as selected, if the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN broadcasted by the selected SNPN is included in the entry of the "list of subscriber data" and validity information of the GIN in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN is not met; or
ii) the PLMN subscription shall be considered as selected, if the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" associated with the PLMN subscription includes the GIN broadcast by the selected SNPN and validity information of the GIN in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN is not met;
- for bullet a) 5) above, the entry of the "list of subscriber data", with the SNPN identity matching the selected SNPN (this may take place at any time during the presentation of SNPNs), shall be considered as selected;
- for bullet b-1) above:
i) the entry of the "list of subscriber data" which contains the user controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN shall be considered as selected, if the user controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN is included in the entry of the "list of subscriber data"; or
- the PLMN subscription shall be considered as selected, if the user controlled prioritized list of preferred SNPNs associated with the PLMN subscription includes the SNPN identity of the selected SNPN;
- for bullet b-2) above:
i) the entry of the "list of subscriber data" which contains the credentials holder controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN shall be considered as selected, if the credentials holder controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN is included in the entry of the "list of subscriber data"; or
ii) the PLMN subscription shall be considered as selected, if the credentials holder controlled prioritized list of preferred SNPNs associated with the PLMN subscription includes the SNPN identity of the selected SNPN;
- for bullet b-3) above:
i) the entry of the "list of subscriber data" which contains the credentials holder controlled prioritized list of GINs that includes the GIN broadcast by the selected SNPN shall be considered as selected, if the credentials holder controlled prioritized list of GINs that includes the GIN broadcast by the selected SNPN is included in the entry of the "list of subscriber data"; or
ii) the PLMN subscription shall be considered as selected, if the credentials holder controlled prioritized list of GINs associated with the PLMN subscription includes the GIN broadcast by the selected SNPN; and
- for bullet b-4) above, the entry of the "list of subscriber data" or the PLMN subscription shall be selected by MS implementation specific means.
NOTE1: If the SNPN identity of the selected SNPN is included in more than one of the following: one or more user controlled prioritized list(s) of preferred SNPNs configured in the ME, one or more credentials holder controlled prioritized list(s) of preferred SNPNs configured in the ME or the list of SNPNs which are broadcasting a GIN included in one or more credentials holder controlled prioritized list(s) of GINs configured in the ME, which subscription is selected is MS implementation specific.
Once the MS has registered on an SNPN selected by the user, the MS shall not automatically register on a different SNPN unless:
a) the user selects automatic SNPN selection mode;
b) the user initiates an emergency call while the MS is in limited service state and either the SNPN does not broadcast the indication of support of emergency calls in limited service state or the registration request for emergency services is rejected by the network; or
c) the new SNPN is declared as an equivalent SNPN by the registered SNPN.
NOTE 2: If case b) occurs, the MS can provide an indication to the upper layers that the MS has exited manual network SNPN selection mode.
If the user does not select an SNPN, the selected SNPN shall be the one that was selected either automatically or manually before the SNPN selection procedure started. If no such SNPN was selected or that SNPN is no longer available, then the MS shall attempt to camp on any acceptable cell and enter the limited service state.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.1.3 Automatic SNPN selection mode procedure for onboarding services in SNPN
|
When the MS needs to access an SNPN for onboarding services in SNPN, the MS shall select an SNPN indicating that onboarding is allowed and, if the onboarding SNPN selection information is pre-configured, also matching the onboarding SNPN selection information. If more than one such SNPNs are available, how the MS selects one of those SNPNs is MS implementation specific. The MS shall not select an SNPN not indicating that onboarding is allowed or not matching the onboarding SNPN selection information, if pre-configured, for onboarding services in SNPN.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
Once the MS selects the SNPN, the MS shall attempt initial registration for onboarding services in SNPN on the selected SNPN using the NG-RAN access technology and the default UE credentials for primary authentication.
If successful registration is achieved, the MS may indicate to upper layers the selected SNPN. How this indication is displayed by upper layers is implementation specific.
If successful registration is not achieved and one or more other SNPNs indicating that onboarding is allowed and matching the onboarding SNPN selection information, if pre-configured, are available, the MS can select such other SNPN and attempt initial registration for onboarding services in SNPN on the selected SNPN using the NG-RAN access technology and the default UE credentials for primary authentication, or the MS can perform SNPN selection not for onboarding services in SNPN as specified in clause 4.9.3.1.1 or clause 4.9.3.1.2 depending on its SNPN selection mode.
If:
- registration cannot be achieved because no SNPNs indicating that onboarding is allowed and matching the onboarding SNPN selection information, if pre-configured, are available; or
- there were one or more SNPNs indicating that onboarding is allowed and matching the onboarding SNPN selection information, if pre-configured, but an LR failure made registration on all those SNPNs unsuccessful;
the MS can indicate no onboarding services to upper layers, enter limited service state and wait until a new SNPN indicating that onboarding is allowed and matching the onboarding SNPN selection information, if pre-configured, is available and then repeat the procedure, or the MS can perform SNPN selection not for onboarding services in SNPN as specified in clause 4.9.3.1.1 or clause 4.9.3.1.2 depending on its SNPN selection mode.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.1.4 Manual SNPN selection mode procedure for onboarding services in SNPN
|
The MS shall indicate to upper layers one or more SNPNs, which are available and indicate that onboarding is allowed.
These include SNPNs in the list of "permanently forbidden SNPNs for onboarding services in SNPN" and the list of "temporarily forbidden SNPNs for onboarding services in SNPN". The MS may indicate to the user whether the available SNPNs are present in the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs".
The MS shall limit its search for the SNPN to the NG-RAN access technology.
For each SNPN indicated to upper layers, the MS shall indicate to the upper layers along with the SNPN identity:
a) whether the SNPN matches the onboarding SNPN selection information, if pre-configured; and
b) the human-readable network name, if the system information broadcast includes the human-readable network name for the SNPN.
Once the user selects the SNPN for onboarding services, the MS shall attempt initial registration for onboarding services in SNPN on the selected SNPN using the default UE credentials for primary authentication. For such a registration the MS shall ignore the contents of the "5GS forbidden tracking areas for roaming", "5GS forbidden tracking areas for regional provision of service", "temporarily forbidden SNPNs for onboarding services in SNPN" and "permanently forbidden SNPNs" for onboarding services in SNPN".
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.1.5 Void
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.2 User reselection
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.2.0 General
|
At any time the user may request the MS to initiate reselection and registration onto an available SNPN, according to the following procedures, dependent upon the SNPN selection mode of the UE.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.2.1 Automatic SNPN selection mode
|
If:
- there is at least one entry in the "list of subscriber data"; or
- there is zero or more entries in the "list of subscriber data", the MS has a USIM with a PLMN subscription and the ME is provisioned with the SNPN selection parameters associated with the PLMN subscription,
the MS shall select one entry in the "list of subscriber data", or the PLMN subscription, if any, to be used for automatic SNPN selection. How the MS selects the entry in the "list of subscriber data" or the PLMN subscription is MS implementation specific.
The MS selects an SNPNs, if available and allowable, in accordance with the following order:
a0) if the MS supports access to an SNPN providing access for localized services in SNPN and access for localized services in SNPN is enabled, then, using the SNPN selection parameters for access for localized services in SNPN in the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription:
1) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and is identified by an SNPN identity contained in an entry of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" (in priority order), if the validity information of the entry is met, excluding the previously selected SNPN; and
2) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and broadcasts a GIN contained in an entry of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" (in priority order), if the validity information of the entry is met, excluding the previously selected SNPN. If more than one such SNPN broadcast the same GIN, the order in which the MS attempts registration on those SNPNs is MS implementation specific;
a) the SNPN identified by an SNPN identity of the subscribed SNPN in the selected entry of the "list of subscriber data" in the ME, if any, excluding the previously selected SNPN;
b) if the MS supports access to an SNPN using credentials from a credentials holder, using the SNPN selection parameters in the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription:
1) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in the user controlled prioritized list of preferred SNPNs (in priority order), excluding the previously selected SNPN;
2) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in the credentials holder controlled prioritized list of preferred SNPNs (in priority order), excluding the previously selected SNPN;
3) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which broadcast a GIN contained in the credentials holder controlled prioritized list of GINs (in priority order), excluding the previously selected SNPN. If more than one such SNPN broadcast the same GIN, the order in which the MS attempts registration on those SNPNs is MS implementation specific; and
4) each SNPN identified by an SNPN identity which is included neither in the SNPN selection parameters of the entries of the "list of subscriber data" nor in the SNPN selection parameters associated with the PLMN subscription and which broadcasts an indication that the SNPN allows registration attempts from MSs that are not explicitly configured to select the SNPN, excluding the previously selected SNPN. If more than one such SNPN is available, the order in which the MS attempts registration on those SNPNs is MS implementation specific.
c) the previously selected SNPN.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
The previously selected SNPN is the SNPN which the MS has selected prior to the start of the user reselection procedure.
The equivalent SNPNs list shall not be applied to the user reselection in automatic SNPN selection mode.
Once the MS selects an SNPN, if the selected SNPN is other than the previously selected SNPN, the MS attempts registrations on the selected SNPN using the NG-RAN access technology, the subscriber identifier and the credentials from the selected entry of the "list of subscriber data" or from the USIM, if the PLMN subscription is selected.
NOTE: If the previously selected SNPN is selected, and registration has not been attempted on any other SNPNs, then the MS is already registered on the SNPN, and so registration is not necessary.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.2.2 Manual SNPN selection mode procedure
|
The manual SNPN selection mode procedure of clause 4.9.3.1.2 is followed.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.3.3 Additional conditions for SNPN selection for MS supports access to an SNPN providing access for localized services in SNPN
|
If the MS supports access to an SNPN providing access for localized services in SNPN, the UE is in automatic SNPN selection mode and:
a) access for localized services in SNPN is changed between disabled and enabled; or
b) access for localized services in SNPN is enabled; and:
1) the selected SNPN is an SNPN selected for localized services in SNPN, and the validity information for the selected SNPN is no longer met; or
2) the selected SNPN is not an SNPN selected for localized services in SNPN, and the validity information for an entry in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" changes from not met to met;
then:
- if the MS does not have an emergency PDU session and is not registered for emergency services, the MS may perform SNPN selection according to clause 4.9.3.1.1; or
- otherwise, if the validity information for the selected SNPN is no longer met the MS shall perform a local release of all PDU sessions except for the emergency PDU session. The MS may perform SNPN selection according to clause 4.9.3.1.1 after the emergency PDU session is released.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
4.9.4 Abnormal cases
|
If:
a) the MS does not support access to an SNPN using credentials from a credentials holder and:
1) the "list of subscriber data" is empty; or
2) for each entry of the "list of subscriber data", such that an SNPN with the SNPN identity of the entry or an equivalent SNPN, is available:
i) there has been an authentication failure for the subscriber identifier of the entry on the SNPN or an equivalent SNPN; or
ii) the MS has received an "illegal ME" or "illegal UE" response to an LR request for the subscriber identifier of entry on the SNPN or an equivalent SNPN; or
b) the MS supports access to an SNPN using credentials from a credentials holder and:
1) the "list of subscriber data" is empty and:
i) the MS is not provisioned with SNPN selection parameters associated with the PLMN subscription;
ii) the MS does not have a USIM; or
iii) both of the above;
2) for each entry of the "list of subscriber data", such that an SNPN with the SNPN identity of the subscribed SNPN of the entry or an equivalent SNPN, is available:
i) there has been an authentication failure for the subscriber identifier of the entry on the SNPN or an equivalent SNPN; or
ii) the MS has received an "illegal ME" or "illegal UE" response to an LR request for the subscriber identifier of entry on the SNPN or an equivalent SNPN;
and:
i) the MS is not provisioned with SNPN selection parameters associated with the PLMN subscription;
ii) the MS does not have a USIM; or
iii) both of the above; or
3) for each available SNPN which broadcasts an indication that access using credentials from a credentials holder is supported and:
i) is identified by an SNPN identity contained in one of the user controlled prioritized lists of preferred SNPNs configured in the ME;
ii) is identified by an SNPN identity contained in one of:
- the credentials holder controlled prioritized lists of preferred SNPNs configured in the ME; or
- the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" configured in the ME supporting access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN is enabled and the validity information of the SNPN is met;
iii) broadcasts a GIN contained in one of:
- the credentials holder controlled prioritized lists of GINs configured in the ME; or
- the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" configured in the ME supporting access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN is enabled and the validity information of the SNPN is met;
iv) is identified by an SNPN identity which is included neither in the SNPN selection parameters of the entries of the "list of subscriber data" nor in the SNPN selection parameters associated with the PLMN subscription, which does not broadcast a GIN which is included in one of the credentials holder controlled prioritized lists of GINs configured in the ME and which broadcasts an indication that the SNPN allows registration attempts from MSs that are not explicitly configured to select the SNPN;
the following applies:
i) there has been an authentication failure in the SNPN; or
ii) the MS has received an "illegal ME" or "illegal UE" response to an LR request from the SNPN;
then effectively there is no selected SNPN ("No SIM" state).
In these cases, the states of the cell selection process are such that the "list of subscriber data" (if any) or the PLMN subscription (if any) is not used. An MS in "No SIM" state configured with default UE credentials for primary authentication may perform SNPN selection procedure for onboarding services in SNPN. Except when an MS in "No SIM" state performs an initial registration for emergency services to an SNPN or an MS in "No SIM" state configured with default UE credentials for primary authentication performs registration for onboarding services in SNPN, no further attempts at registration on any SNPN are made until the MS is switched off and on again, or an entry of the "list of subscriber data" with the SNPN identity of the SNPN is updated or the USIM is inserted. When performing an initial registration for emergency services, an SNPN supporting emergency services, of the current serving cell is temporarily considered as the selected SNPN. If the MS needs to make an emergency call, the MS supports accessing a PLMN and there is no available SNPN supporting emergency services, the MS shall stop operating in SNPN access operation mode over 3GPP access and attempt to camp on a cell of a PLMN so that emergency calls can be made. After an emergency call is released, the MS may re-start operating in SNPN access operation mode over 3GPP access and perform SNPN selection.
When in automatic SNPN selection mode and the MS is in the "not updated" state with one or more suitable cells to camp on; then after the maximum allowed unsuccessful LR requests (controlled by the specific attempt counters) the MS may continue (or start if it is not running) the user reselection procedure in clause 4.9.3.2.1.
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
5 Tables and Figures
|
Table 1: Effect of LR Outcomes on PLMN Registration
Location Registration Task State
Registration Status
Registered PLMN is
Updated
Successful
Indicated in the stored registration area identity
Idle, No IMSI
Unsuccessful
No registered PLMN (3) (4)
Roaming not allowed:
a) PLMN not allowed
Unsuccessful
No registered PLMN (4)
b) LA not allowed or TA not allowed
Indeterminate(1)
No registered PLMN
c) Roaming not allowed in this LA or Roaming not allowed in this TA
Indeterminate (2)
No registered PLMN (4)
d) No suitable cells in location area or No suitable cells in tracking area
Indeterminate (5)
No registered PLMN
e) Not authorized for this CSG
Indeterminate (6)
No registered PLMN
Not updated
Unsuccessful
No registered PLMN (4)
1) The MS will perform a cell selection and will eventually either enter a different state when the registration status will be determined, or fail to be able to camp on a new cell, when registration status will be unsuccessful.
2) The MS will select the HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is present) if in automatic mode and will enter Automatic Network Selection Mode Procedure of clause 4.4.3.1.1. If in manual mode, the MS will display the list of available PLMNs and follow the Manual Network Selection Mode Procedure of clause 4.4.3.1.2 If the appropriate process does not result in registration, the MS will eventually enter the limited service state.
3) An MS may have different update states for GPRS and non-GPRS. A PLMN is registered when at least one of both update states is updated.
4) The stored list of equivalent PLMNs is invalid and can be deleted.
5) The MS will attempt registration on another LA or TA of the same PLMN, or equivalent PLMN if available.Otherwise it will enter either the Automatic Network Selection Mode procedure of clause 4.4.3.1.1 or follow the Manual Network Selection Mode procedure of clause 4.4.3.1.2. If the appropriate process does not result in registration, the MS will eventually enter the limited service state.
6) The MS will attempt registration on another cell of the same PLMN, or equivalent PLMN if available.Otherwise it will enter either the Automatic Network Selection Mode procedure of clause 4.4.3.1.1 or follow the Manual Network Selection Mode procedure of clause 4.4.3.1.2. If the appropriate process does not result in registration, the MS will eventually enter the limited service state.
NOTE 1: MSs capable of GPRS and non-GPRS services may have different registration status for GPRS and for non-GPRS.
NOTE 2: The registered PLMN is determined by looking at the stored registration area identity and stored location registration status.
Table 2: LR Process States and Allowed Actions
Location Registration
New LR request when
Normal Calls
Paging responded
Task State
Changing Cell
Changing registration area
Changing PLMN
Other
Supported (1)
to
Null (4)
No
Yes
Yes
No
No
No
Updated, (5)
No
Yes
Yes
(2)
Yes
Yes
Idle, No IMSI (7)
No
No
No
No
No
No
Roaming not allowed:
a) Idle, PLMN not allowed
No
No
Yes
No
No
Optional if with IMSI
b) Idle, LA not allowed or TA not allowed
No
Yes(6)
Yes
No
No
Optional if with IMSI
c) Idle, Roaming not allowed in this LA or
Roaming not allowed in this TA
No
Yes(6,8)
Yes
No
No
Optional if with IMSI
d) No suitable cells in location area or
No suitable cells in tracking area
No
Yes(6,8)
Yes
No
No
Optional if with IMSI
e) Not authorized for this CSG
No
Yes (6,8)
Yes
No
No
Optional if with IMSI
Not updated
Yes
Yes
Yes
(2)&(3)
(3)
Yes if with IMSI
1): Emergency calls may always be made, subject to access control permitting it.
2): A new LR is made when the periodic registration timer expires.
3): If a normal call request is made, an LR request is made. If successful the updated state is entered and the call may be made.
4): The MS is in the null state from switch on until it has camped on a cell and either made an LR attempt or decided that no LR attempt is needed.
5): In this state, IMSI detach is performed if the MS is deactivated and the BCCH indicates that IMSI attach/detach shall be used. An LR request indicating IMSI attach is performed if the MS is activated in the same registration area in which it was deactivated while being in this state.
6): An MS shall not perform a new LR when the new routing area is part of an LA or TA contained in any of the lists "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service" or the new cell is a CSG cell which is not part of any of the lists "Allowed CSG list", "Operator CSG list". The MS shall not perform a LR on a satellite NG-RAN cell or a satellite E-UTRAN cell if it fulfils the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, i.e. if it is not considered as candidate for PLMN selection.
7): The conditions in which the GPRS and/or non-GPRS registration status "Idle, No IMSI" is entered are specified in clause 4.3.3.
8): An MS shall perform a LR if it has entered a registration area whatever the registration area stored in the MS.
Figure 1: Overall Idle Mode process
The individual steps are the following (they are not necessarily executed in the number sequence):
(1) The PLMN selection mode is set (e.g. by the user via the user interface or by AT command).
(2) The list of available PLMNs is presented to the user, according to the rules given in clause 4.4.3.1.2.
(3) In manual PLMN selection mode the user selects from the available PLMNs.
(4) If the MS supports CSGs, the list of available PLMNs and CSGs, together with an indication as to which of the available CSGs is in the Allowed or Operator CSG list, is presented to the user upon request. The detailed rules are defined in clause 5.5.4 of 3GPP TS 22.220 [49].
(5) Only for MSs supporting CSGs: when camping on a cell, the available CSGs (with PLMN information) are conveyed to the CSG selection/restriction procedure (see clause 3.1A).
(6) Only for MSs supporting CSGs: in manual CSG selection mode the user selects from the available CSGs.
(7) Only for MSs supporting CSGs: if the selected CSG is associated with the RPLMN, the MS performs selection of a cell belonging to this CSG.
(8) Only for MSs supporting CSGs: if the selected CSG is associated with a PLMN different from the RPLMN, the MS enters the PLMN selection process and performs the parts applicable after manual selection of a PLMN.
(9) After it has selected a PLMN, the MS performs selection of a cell belonging to this PLMN; this selection is additionally restricted by the selected CSG, if the PLMN selection was triggered by a manual CSG selection.
(10) After having selected a new cell and the registration area has changed, the MS shall enter the LR process (see figure 3).
(10a) An MS's CM requests may lead to a registration request.
(11) If the LR is not successful, and if the cause received from the network does not exclude the RPLMN, the MS performs another cell selection (i.e. cell re-selection) within the RPLMN.
(12) The information on available PLMNs, as detected by the cell selection process from detectable broadcast information, is made available to the PLMN selection process.
(13) If the LR is not successful, and if the cause received from the network excludes the RPLMN, the MS performs PLMN selection.
(14) The positive result of cell selection (suitable cell and in updated state, or in connected mode having been camped on a suitable cell) and location registration (updated, for MSs capable of services requiring registration) is indicated to the user.
Possible sequences of steps are e.g.:
1) 1 2 3 9 10 11 (manual PLMN selection, MS is not CSG capable)
2) 1 9 4 5 6 8 9 10 11 (automatic PLMN selection, MS is CSG capable, manual CSG selection);
Figure 2a: PLMN Selection State diagram (automatic mode)
Figure 2b: PLMN Selection State diagram (manual mode)
NOTE 1: Whenever the MS goes to connected mode and then returns to idle mode again the MS selects appropriate state.
NOTE 2: An MS capable of GPRS and non-GPRS services has two Task State machines one for GPRS and one for non-GPRS operation.
Figure 3: Location Registration Task State diagram
|
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
6 MS supporting access technologies defined both by 3GPP and 3GPP2
| |
dfbc08aa381ddcd388edbd0947c0541e
|
23.122
|
6.1 General
|
An MS that supports access technologies defined both by 3GPP and 3GPP2 (see 3GPP TS 31.102 [40]) shall consider all supported access technologies in all supported bands when performing PLMN selection. The goal of the PLMN selection process for such a multi mode MS is to find the highest priority PLMN and to attempt to register to it. A multi mode MS shall follow the requirements in the present document for the PLMN selection procedures across both 3GPP and 3GPP2 access technologies. Additionally, the MS shall follow the requirements of the present document in its signalling procedures towards any 3GPP network. If the common PLMN selection procedure leads to selection of a 3GPP2 network, then the MS shall follow 3GPP2 specifications in meeting any 3GPP2 specific system selection constraints and in all signalling procedures towards the 3GPP2 network. While registered to VPLMN via 3GPP2 access, the MS shall follow the 3GPP2 specifications for scan of higher priority PLMNs. Additionally to the requirements specified for 3GPP2 system, a multi mode MS while registered to a 3GPP2 VPLMN shall follow the requirements specified in clause 4.4.3.3. NOTE: It is assumed that the MS can determine the PLMN identity of networks supporting 3GPP2 technologies from the information broadcast over the air. Annex A (normative): HPLMN Matching Criteria With the introduction of PCS1900 with the regulatory mandate to allocate 3-digit MNC codes, additional functionality is required to identify the HPLMN. Assumptions An MNC code shall consist of 2 or 3 decimal digits. In NA PCS1900, all SIMs shall store 3 digit MNCs. Any network using a 2 digit MNC code shall broadcast the hexadecimal code "F" in place of the 3rd digit. For PCS1900 for North America, regulations mandate that a 3-digit MNC shall be used; however during a transition period, a 2 digit MNC may be broadcast by the Network and, in this case, the 3rd digit of the SIM is stored as 0 (this is the 0 suffix rule). With the exception of North America during the transition period: a) Within a single country (or area identified by a MCC) all networks shall broadcast a 2 digit MNC code, or all networks shall broadcast a 3 digit MNC code. A mixture of broadcast 2 and 3 digit MNC codes is not permitted within a single country (or area identified by a MCC). b) A network which broadcasts a 2 digit MNC code, will issue SIMs with a 2 digit MNC code in the IMSI on the SIM. A network which broadcasts a 3 digit MNC code, will issue SIMs with a 3 digit MNC code in the IMSI on the SIM. Definitions and abbreviations BCCH-MCC For GERAN, the MCC part of the LAI read from System Information type 3 messages broadcast on the BCCH by the network (see 3GPP TS 44.018 [34]), for UTRA, the MCC part of the PLMN broadcasted as specified in 3GPP TS 25.331 [33], for E-UTRA, the MCC part of the PLMN broadcasted as specified in 3GPP TS 36.331 [42], or for NR, the MCC part of the PLMN broadcasted as specified in 3GPP TS 38.331 [65]. BCCH-MNC For GERAN the MNC part of the LAI read from System Information type 3 messages broadcast on the BCCH by the network (see 3GPP TS 44.018 [34]), for UTRA, the MNC part of the PLMN broadcasted as specified in 3GPP TS 25.331 [33], for E-UTRA, the MNC part of the PLMN broadcasted as specified in 3GPP TS 36.331 [42], or for NR, the MNC part of the PLMN broadcasted as specified in 3GPP TS 38.331 [65]. SIM-MCC The MCC part of the IMSI or of additional entries in the EHPLMN list read from the SIM. SIM-MNC The MNC part of the IMSI or of additional entries in the EHPLMN list read from the SIM. HPLMN Matching Criteria in mobiles which don't support PCS1900 for NA: Figure A.1 illustrates the logic flow described below. The text below is normative. Figure A.1 is informative. (1) The MS shall compare using all 3 digits of the SIM-MCC with the BCCH-MCC. If the values do not match, then the HPLMN match fails. NOTE: If the MCC codes match, then the number of digits used for the SIM-MNC must be the same as the number of digits used for the BCCH-MNC. (2) The MS shall read the 3rd digit of the BCCH-MNC. If the 3rd digit is Hex F, then proceed to step (4). (3) The MS shall compare using all 3 digits of the SIM-MNC with the BCCH-MNC. If the values match, then the HPLMN match succeeds, otherwise the HPLMN match fails. (4) The MS shall compare using just the 1st 2 digits the SIM-MNC with the BCCH-MNC. If the values match, then the HPLMN match succeeds, otherwise the HPLMN match fails. If the EHPLMN list is present and is empty or if the EHPLMN list is not present, the matching procedure shall be done for the MCC/MNC of the IMSI. If the EHPLMN list is present and is not empty, the matching procedure shall be done for all entries in the EHPLMN list until a match is found or all matches fail. Figure A.1: HPLMN Matching Criteria Logic Flow for mobiles which support GSM and DCS1800 (informative) HPLMN Matching Criteria for mobiles which support PCS1900 for NA: Figure A.2 illustrates the logic flow described below. The text below is normative. Figure A.2 is informative. (1) The MS shall compare using all 3 digits the SIM-MCC with the BCCH-MCC. If the values do not match, then the HPLMN match fails. (2) The MS shall read the 3rd digit of the BCCH-MNC. If the 3rd digit is Hex F, then proceed to step (4). (3) The MS shall compare using all 3 digits the SIM-MNC with the BCCH-MNC. If the values match, then the HPLMN match succeeds, otherwise the HPLMN match fails. NOTE: These rules (1) – (3) are the same as for mobiles which don't support PCS1900 for NA, except step (4) is different. (4) The MS shall determine if the BCCH-MCC lies in the range 310-316 (i.e., whether this network is a PCS1900 for NA network). If the BCCH-MCC lies outside the range 310-316, then proceed to step (6). (5) The MS shall compare the 3rd digit of the SIM-MNC with '0'. If the 3rd digit is not '0' then the HPLMN match fails. NOTE: This is the '0' suffix rule. (6) The MS shall compare using just the 1st 2 digits of the SIM-MNC with the BCCH-MNC. If the values match, then the HPLMN match succeeds, otherwise the HPLMN match fails. NOTE: When PCS1900 for NA switches over to broadcasting 3 digit MNCs in all networks, then the additional requirements for PCS1900 for NA can be deleted. If the EHPLMN list is present and is empty or if the EHPLMN list is not present, the matching procedure shall be done for the MCC/MNC of the IMSI. If the EHPLMN list is present and is not empty, the matching procedure shall be done for all entries in the EHPLMN list until a match is found or all matches fail. Guidance for Networks in PCS1900 for NA There may be some problems in the transition period from broadcasting 2 MNC digits to broadcasting 3 MNC digits. Here are some guidelines to avoid these problems. (1) Existing network codes. Operators who currently use a 2 digit BCCH-MNC xy should use the new code xy0. (2) New operators allocated 3 digit MNC codes with the same 1st 2 digits as an existing operator shall not use a 3rd digit of 0. Figure A.2: HPLMN Matching Criteria Logic Flow for mobiles which support PCS1900 for NA (informative) Annex B (normative): PLMN matching criteria to be of same country as VPLMN While an MS is roaming on a VPLMN, the VPLMN and a PLMN are of the same country only if their MCC values identify the same country. See clause 1.2 for the definition of country. Annex C (normative): Control plane solution for steering of roaming in 5GS C.0 Requirements for 5G steering of roaming over the control plane In addition to the requirements specified in 3GPP TS 22.011 [9] clause 3.2.2.8, 3GPP TS 22.261 [74] clause 6.30 and 3GPP TS 23.501 [62] clause 5.30.2.2, the requirements in this clause apply. The UE supporting N1 mode shall support the control plane solution for steering of roaming in 5GS. If the HPLMN or subscribed SNPN supports and wants to use the control plane solution for steering of roaming in 5GS, then the HPLMN or subscribed SNPN shall provide the steering of roaming information to the UE using the control plane mechanism defined in this annex. The VPLMN shall transparently relay the steering of roaming information received from the HPLMN to the UE. The UE shall be able to detect whether the VPLMN removed the steering of roaming information during the initial registration procedure in the VPLMN. The UE shall be able to detect whether the VPLMN altered the steering of roaming information. If the UE detects that the VPLMN altered or removed the steering of roaming information then the UE shall consider the current VPLMN as the lowest priority PLMN and perform PLMN selection as defined in this annex. The non-subscribed SNPN shall transparently relay the steering of roaming information received from the HPLMN or subscribed SNPN to the UE. The UE shall be able to detect whether the non-subscribed SNPN removed the steering of roaming information during the initial registration procedure in the non-subscribed SNPN. The UE shall be able to detect whether the non-subcribed SNPN altered the steering of roaming information. If the UE detects that the non-subscribed SNPN altered or removed the steering of roaming information then the UE shall consider the current SNPN as the lowest priority SNPN and perform SNPN selection as defined in this annex. C.1 General C.1.1 Steering of roaming over the control plane in a PLMN The purpose of the control plane solution for steering of roaming in 5GS procedure in a PLMN is to allow the HPLMN to update one or more of the following via NAS signalling: a) the "Operator Controlled PLMN Selector with Access Technology" list in the UE by providing the HPLMN protected list of preferred PLMN/access technology combinations or a secured packet; b) the SOR-CMCI; c) the SOR-SNPN-SI associated with the selected PLMN subscription in the ME; d) the SOR-SNPN-SI-LS associated with the selected PLMN subscription in the ME; and e) the SOR-SENSE (i.e the "Operator controlled signal threshold per access technology") provided in a secured packet. If the selected PLMN is a VPLMN, the HPLMN can provide the steering of roaming information to the UE using the control plane mechanism during and after registration. If the selected PLMN is the HPLMN, the HPLMN can provide the steering of roaming information to the UE using the control plane mechanism after registration only. The HPLMN updates the "Operator Controlled PLMN Selector with Access Technology" based on the operator policies, which can be based on the registered VPLMN, the location of the UE, etc. The HPLMN may update the "Operator controlled signal threshold per access technology" based on the operator policies and the operator specific data analytic information. The HPLMN can configure their subscribed UE's USIM to indicate that the UE is expected to receive the steering of roaming information due to initial registration in 5GS in a VPLMN. At the same time the HPLMN will mark the UE is expected to receive the steering of roaming information due to initial registration in 5GS in a VPLMN, in the subscription information in the UDM. In this case, it is mandatory for the HPLMN to provide the steering of roaming information to the UE during initial registration in a VPLMN. Otherwise, if such configuration is not provided in the USIM, it is optional for the HPLMN to provide the steering of roaming information to the UE during initial registration (based on operator policy). The HPLMN can provide the steering of roaming information to the UE during the registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) and initial registration procedure for emergency services. In addition, the HPLMN can request the UE to provide an acknowledgement of successful reception of the steering of roaming information. NOTE 1: In annex C of this specification, the User Data Repository (UDR) is considered as part of the UDM. As the HPLMN needs to consider certain criteria including the number of customers distributed through multiple VPLMNs in the same country or region, the list of the preferred PLMN/access technology combinations is not necessarily the same at all times and for all users. The list of the preferred PLMN/access technology combinations needs to be dynamically generated, e.g. generated on demand, by a dedicated steering of roaming application function (SOR-AF) providing operator specific data analytics solutions. NOTE 2: The functional description of this dedicated application function (SOR-AF) is out of scope of 3GPP. The steering of roaming connected mode control information (SOR-CMCI) enables the HPLMN to control the timing of a UE in 5GS connected mode to move to idle mode to perform the steering of roaming. If the UE selects a cell of any access technology other than NG-RAN, the SOR procedure is terminated (see clause C.4.2). The UE shall support the SOR-CMCI. The support and use of SOR-CMCI by the HPLMN is based on the HPLMN's operator policy. The following requirements are applicable for the SOR-CMCI: - The HPLMN may configure SOR-CMCI in the UE and may also send SOR-CMCI over N1 NAS signalling. The SOR-CMCI received over N1 NAS signalling has precedence over the SOR-CMCI configured in the UE. NOTE 3: Based on HPLMN policy, while setting the SOR-CMCI the HPLMN can take into consideration the user preference for the service(s) not to be interrupted due to SOR (e.g. MMTEL voice call, MMTEL video call, HPLMN defined services, among others). The user can communicate its preference for the service(s) not to be interrupted due to SOR to the HPLMN utilizing non-standard operator-specific mechanisms, e.g. web-based. - The UE shall indicate ME's support for SOR-CMCI to the HPLMN. NOTE 4: The HPLMN has the knowledge of the USIM's capabilities in supporting SOR-CMCI. - While performing SOR, the UE shall consider the list of preferred PLMN/access technology combinations or secured packet received in the SOR information together with the available SOR-CMCI. - The HPLMN may provision the SOR-CMCI in the UE over N1 NAS signalling. The UE shall store the configured SOR-CMCI in the non-volatile memory of the ME or in the USIM as described in clause C.4. The following requirement is applicable for the SOR-SNPN-SI: - If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall indicate ME's support for SOR-SNPN-SI to the HPLMN or EHPLMN. The following requirement is applicable for the SOR-SNPN-SI-LS: - If the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall indicate ME's support for SOR-SNPN-SI-LS to the HPLMN. In order to support various deployment scenarios, the UDM may support at least one of the following functionalities: a) obtaining a list of preferred PLMN/access technology combinations, SOR-CMCI, if any (if supported by the UDM and required by the HPLMN), or a secured packet which is available or becomes available in the UDM (i.e. retrieved from the UDR); or NOTE 5: A secured packet can be made available at the UDR via implementation specific means. In this case the implementation specific means are required to ensure that the secured packet satisfies the "Replay detection and Sequence Integrity counter" (see ETSI TS 102 225 [73]) every time it is sent out from the HPLMN to the UE. b) obtaining a list of preferred PLMN/access technology combinations, SOR-CMCI, if any (if supported by the UDM and required by the HPLMN), or a secured packet from the SOR-AF. The HPLMN policy for the SOR-AF invocation can be present in the UDM only if the UDM supports obtaining a list of preferred PLMN/access technology combinations, SOR-CMCI, if any, or a secured packet from the SOR-AF. The UDM discards any list of preferred PLMN/access technology combinations, SOR-CMCI, if any, or any secured packet obtained from the SOR-AF or which is or becomes available in the UDM (i.e. retrieved from the UDR), either during registration (as specified in annex C.2) or after registration (as specified in annex C.3 and C.4.3), when the UDM cannot successfully forward the SOR information to the AMF (e.g. in case the UDM receives the response from the SOR-AF with the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, if any, the secured packet after the expiration of the operator specific timer, or if there is no AMF registered for the UE). The UE maintains a list of "PLMNs where registration was aborted due to SOR". If the UE receives steering of roaming information in the REGISTRATION ACCEPT or DL NAS TRANSPORT message and the security check to verify that the steering of roaming information is provided by HPLMN is successful, the UE shall remove the current selected PLMN from the list of "PLMNs where registration was aborted due to SOR". The UE shall delete the list of "PLMNs where registration was aborted due to SOR" when the MS is switched off or the USIM is removed. The UE may also remove PLMN(s) from the list of "PLMNs where registration was aborted due to SOR" after a UE implementation dependent time. If: a) the UE's USIM is configured to indicate that the UE shall expect to receive the steering of roaming information during initial registration procedure but did not receive it or security check on the steering of roaming information fails; b) the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to SOR"; c) the current chosen VPLMN is not part of "User Controlled PLMN Selector with Access Technology" list; and d) the UE is not in manual mode of operation; then the UE will perform PLMN selection with the current VPLMN considered as lowest priority. It is mandatory for the VPLMN to transparently forward to the UE the steering of roaming information received from HPLMN and to transparently forward to the HPLMN the acknowledgement of successful reception of the steering of roaming information received from UE, both while the UE is trying to register onto the VPLMN as described in clause C.2, and after the UE has registered onto the VPLMN as described in clause C.3 and C.4.3. If the last received steering of roaming information contains the list of preferred PLMN/access technology combinations then the ME shall not delete the "Operator Controlled PLMN Selector with Access Technology" list stored in the non-volatile memory of the ME when the UE is switched off. The "Operator Controlled PLMN Selector with Access Technology" list shall be stored in the non-volatile memory of the ME together with the SUPI from the USIM. The ME shall delete the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME when a new USIM is inserted. The procedure in this annex for steering of UE in VPLMN can be initiated by the network while the UE is trying to register onto the VPLMN as described in clause C.2, or after the UE has registered onto the HPLMN or the VPLMN as described in clause C.3, C.7 and C.4.3. C.1.2 Steering of roaming over the control plane in an SNPN The purpose of the control plane solution for steering of roaming in 5GS procedure in an SNPN is to allow the HPLMN or subscribed SNPN to update one or more of the following via NAS signalling: a) the SOR-SNPN-SI associated with the selected entry of "list of subscriber data" or the selected PLMN subscription in the ME, for a UE which supports access to an SNPN using credentials from a credential holder; b) the SOR-CMCI; and c) the SOR-SNPN-SI-LS associated with the selected entry of "list of subscriber data" or the selected PLMN subscription in the ME, if the UE supports access to an SNPN providing access for localized services in SNPN. The control plane solution for steering of roaming in 5GS procedure in an SNPN can also be used by the HPLMN to update the "Operator Controlled PLMN Selector with Access Technology" list in the UE by providing the HPLMN protected list of preferred PLMN/access technology combinations or a secured packet via NAS signalling. The HPLMN or subscribed SNPN can provide the steering of roaming information to the UE using the control plane mechanism during and after registration. The HPLMN or subscribed SNPN updates the SOR-SNPN-SI based on the HPLMN or subscribed SNPN policies, which can be based on the registered SNPN, the location of the UE, etc. The control plane solution for steering of roaming in 5GS procedure in an SNPN is not applicable for credentials holder with AAA server. If the UE supports access to an SNPN using credentials from a credentials holder: a) the UE shall indicate ME's support for SOR-SNPN-SI when registering in a subscribed SNPN, in the HPLMN or in the EHPLMN; and aa) the UE supporting equivalent SNPNs shall indicate ME's support for SOR-SNPN-SI when registering in a non-subscribed SNPN; and b) the UE may indicate ME's support for SOR-SNPN-SI when sending an SOR transparent container including a UE acknowledgement in a PLMN. When the UE indicates ME's support for SOR-SNPN-SI in the 5GMM capability in initial registration or emergency registration or when ME's support for SOR-SNPN-SI changes in mobility registration update, the AMF shall inform the UDM. When the UE supports equivalent SNPNs, the ME does not support SOR-SNPN-SI and the UE is in an equivalent SNPN of the subscribed SNPN, the AMF shall inform the UDM. The HPLMN or subscribed SNPN can configure their subscribed UEs' SNPN configuration parameters associated with the PLMN subscription or the selected entry of the "list of subscriber data", respectively, to expect to receive the steering of roaming information due to initial registration in a non-subscribed SNPN. At the same time the HPLMN or subscribed SNPN will mark the UE as expecting to receive the steering of roaming information due to initial registration in a non-subscribed SNPN, in the subscription information in the UDM. In this case, it is mandatory for the HPLMN or subscribed SNPN to provide the steering of roaming information to the UE during initial registration in a non-subscribed SNPN. Otherwise if such configuration is not provided in the ME, it is optional for the HPLMN or subscribed SNPN to provide the steering of roaming information to the UE during initial registration (based on HPLMN or subscribed SNPN policy). The HPLMN or subscribed SNPN can provide the steering of roaming information to the UE during the registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) and initial registration procedure for emergency services. In addition, the HPLMN or subscribed SNPN can request the UE to provide an acknowledgement of successful reception of the steering of roaming information. NOTE 1: In annex C of this specification, the User Data Repository (UDR) is considered as part of the UDM. As the HPLMN or subscribed SNPN needs to consider certain criteria including the number of customers distributed through multiple SNPNs in the same country or region, the SOR-SNPN-SI is not necessarily the same at all times and for all users. NOTE 2: The functional description of this dedicated application function (SOR-AF) is out of scope of 3GPP. The steering of roaming connected mode control information (SOR-CMCI) enables the HPLMN or subscribed SNPN to control the timing of a UE in connected mode to move to idle mode, if the UE decides to perform SNPN selection upon receiving the steering of roaming information. The UE shall support the SOR-CMCI. The support and use of SOR-CMCI by the HPLMN or subscribed SNPN is based on the HPLMN or subscribed SNPN policy. The following requirements are applicable for the SOR-CMCI: - The HPLMN or subscribed SNPN may configure SOR-CMCI in the UE and may also send SOR-CMCI over N1 NAS signalling. The SOR-CMCI received over N1 NAS signalling has precedence over the SOR-CMCI configured in the UE. - The UE shall indicate ME's support for SOR-CMCI to the HPLMN or subscribed SNPN. NOTE 3: If the credentials holder is the HPLMN, the HPLMN has the knowledge of the USIM's capabilities in supporting SOR-CMCI. - While performing SOR, the UE shall consider the SOR-SNPN-SI and SOR-SNPN-SI-LS (if any) received in the SOR information together with the available SOR-CMCI. - The HPLMN or subscribed SNPN may provision the SOR-CMCI in the UE over N1 NAS signalling. The UE shall store the configured SOR-CMCI in the non-volatile memory of the ME or in the USIM as described in clause C.4. The following requirement is applicable for the SOR-SNPN-SI-LS: - If the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall indicate ME's support for SOR-SNPN-SI-LS to the subscribed SNPN or the HPLMN. In order to support various deployment scenarios, the UDM may support: - obtaining the SOR-SNPN-SI and SOR-SNPN-SI-LS, if any (if supported by the UDM and required by the HPLMN), which are or becomes available in the UDM (i.e. retrieved from the UDR); - obtaining the SOR-SNPN-SI and SOR-SNPN-SI-LS, if any (if supported by the UDM and required by the HPLMN), from the SOR-AF; or - both of the above. The HPLMN or subscribed SNPN policy for the SOR-AF invocation can be present in the UDM only if the UDM supports obtaining the SOR-SNPN-SI and SOR-SNPN-SI-LS, if any, from the SOR-AF. The UDM discards any SOR-SNPN-SI and SOR-SNPN-SI-LS, if any, obtained from the SOR-AF or which are or becomes available in the UDM (i.e. retrieved from the UDR), either during registration (as specified in annex C.5) or after registration (as specified in annex C.6), when the UDM cannot successfully forward the SOR information to the AMF (e.g. in case the UDM receives the response from the SOR-AF with the SOR-SNPN-SI and SOR-SNPN-SI-LS, if any, after the expiration of the HPLMN or subscribed SNPN specific timer, or if there is no AMF registered for the UE). If the UE is registering on the subscribed SNPN and the UE has not indicated ME's support for SOR-SNPN-SI in the REGISTRATION REQUEST message, the UDM shall delete the stored "ME support of SOR-SNPN-SI" indicator, if any, and shall not provide the SOR-SNPN-SI to the UE after registration. If the UE is registering on the subscribed SNPN and the UE has indicated ME's support for SOR-SNPN-SI in the REGISTRATION REQUEST message, the UDM shall store the "ME support of SOR-SNPN-SI" indicator and may provide the SOR-SNPN-SI to the UE after registration based on the subscribed SNPN or HPLMN policy. The UE maintains a list of "SNPNs where registration was aborted due to SOR" per entry of the "list of subscriber data" or the PLMN subscription. If the UE receives steering of roaming information in the REGISTRATION ACCEPT or DL NAS TRANSPORT message in an SNPN and the security check to verify that the steering of roaming information is provided by the HPLMN or subscribed SNPN is successful, the UE shall remove the current selected SNPN from the list of "SNPNs where registration was aborted due to SOR" for the selected entry of the "list of subscriber data" or the selected PLMN subscription. The UE shall delete the list of "SNPNs where registration was aborted due to SOR" when the selected entry of the "list of subscriber data" is updated or the UICC containing the USIM is removed. If: - the UE's ME is configured to indicate that the UE shall expect to receive the steering of roaming information during initial registration procedure for the selected entry of the "list of subscriber data" or the selected PLMN subscription but did not receive it or security check on the steering of roaming information fails; - the current chosen non-subscribed SNPN is not contained in the list of "SNPNs where registration was aborted due to SOR" for the selected entry of the "list of subscriber data" or the selected PLMN subscription; - the current chosen non-subscribed SNPN is not part of the user controlled prioritized list of preferred SNPNs for the selected entry of the "list of subscriber data" or the selected PLMN subscription; and - the UE is not in manual mode of operation; then the UE will perform SNPN selection with the current SNPN considered as lowest priority. It is mandatory for the non-subscribed SNPN to transparently forward to the UE the steering of roaming information received from the HPLMN or subscribed SNPN and to transparently forward to the HPLMN or subscribed SNPN the acknowledgement of successful reception of the steering of roaming information received from the UE, both while the UE is trying to register onto the non-subscribed SNPN as described in clause C.5, and after the UE has registered onto the non-subscribed SNPN as described in clause C.6. The ME shall delete the SOR-SNPN-SI and SOR-SNPN-SI-LS (if available) stored in the ME when the subscriber identifier, the SNPN identity of the subscribed SNPN, or both, of the selected entry of the "list of subscriber data" are updated or the UICC containing the USIM is removed. The procedure in this annex for steering of UE in an SNPN can be initiated by the network while the UE is trying to register onto a non-subscribed SNPN as described in clause C.5, or after the UE has registered onto the subscribed SNPN or a non-subscribed SNPN as described in clause C.6 and C.8. C.2 Stage-2 flow for steering of UE in VPLMN during registration 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, the stored "ME support of SOR-SNPN-SI" indicator, if any, and the stored "ME support of SOR-SNPN-SI-LS" 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. NOTE 4: The secured packet obtained by the UDM can include SOR-SENSE only if the USIM of the indicated SUPI supports SOR-SENSE. 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.550 [88])). The VPLMN ID and the access type parameters, indicating where the UE is registering, are stored in the HPLMN UDM; NOTE 5: Information about UE supporting SOR-SENSE can be available directly in SOR-AF (or in OAM which configures the secure packet in UDM/UDR). 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 6: 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 7: 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 8: 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 9: 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 10: 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 11: 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 12: 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 13: 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 14: 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 15: 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 16: 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. NOTE 17:If the SOR-SENSE has been updated in the USIM, the UE uses the "Operator controlled signal threshold per access technology" information stored on the USIM in accordance to clause 3.11 of this 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. 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, establishing an emergency PDU session or performing emergency service fallback until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session or is performing emergency services fallback (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: 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: 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. 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, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session or is performing emergency services fallback (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 18: 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 stored SOR-CMCI, and there are ongoing PDU sessions or services, the UE shall apply the actions in clause C.4. 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, establishing an emergency PDU session or performing emergency services fallback 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 19: 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"; c1) if the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall set the "ME support of SOR-SNPN-SI-LS" 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, 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, 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; - 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; and - the "ME support of SOR-SNPN-SI-LS" 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-LS" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any. NOTE 20: The UDM cannot receive the "ME support of SOR-CMCI" indicator, the "ME support of SOR-SNPN-SI" indicator, or "ME support of SOR-SNPN-SI-LS" indicator 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, "ME support of SOR-SNPN-SI-LS" 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 - 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 - the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator; and NOTE 21: 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 or is performing emergency services fallback (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, establishing an emergency PDU session or performing emergency services fallback, 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, emergency services fallback 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 22: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. NOTE 23: The list of available and allowable PLMNs in the area is implementation specific. NOTE 24: 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. C.3 Stage-2 flow for steering of UE in HPLMN or VPLMN after registration The stage-2 flow for the steering of UE in HPLMN or VPLMN after registration is indicated in figure C.3.1. The selected PLMN can be the HPLMN or a VPLMN. The AMF is located in the selected PLMN. In this procedure, the SOR-CMCI, if any, is sent together with the list of preferred PLMN/access technology combinations in plain text or is sent within the secured packet. The procedure is triggered: - If the HPLMN UDM supports obtaining a list of preferred PLMN/access technology combinations and SOR-CMCI, if any, or a secured packet from the SOR-AF, the HPLMN policy for the SOR-AF invocation is present in the HPLMN UDM, and the SOR-AF provides the HPLMN UDM with a new list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI. If the ME supports the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally provides the "Store SOR-CMCI in ME" indicator otherwise the SOR-AF shall provide neither the SOR-CMCI nor the "Store SOR-CMCI in ME" indicator. The secured packet provided by the SOR-AF may 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 the SOR-AF shall not include the SOR-CMCI, if any, in the secured packet; or NOTE 1: 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. How the SOR-AF determines that the USIM for the indicated SUPI supports SOR-CMCI is implementation specific. - When a new list of preferred PLMN/access technology combinations or a secured packet becomes available in the HPLMN UDM (i.e. retrieved from the UDR). If the "ME support of SOR-CMCI" indicator is stored for the UE and the new list of preferred PLMN/access technology combinations becomes available in the HPLMN UDM (i.e. retrieved from the UDR), the HPLMN UDM shall obtain the SOR-CMCI and the "Store SOR-CMCI in ME" indicator, if available, otherwise the HPLMN UDM shall obtain neither the SOR-CMCI nor the "Store SOR-CMCI in ME" indicator. NOTE 3: Based on operator deployment and policy, if the UDM receives the list of preferred PLMN/access technology combinations, SOR-CMCI, if any, the "Store SOR-CMCI in ME" indicator, if any, and the USIM of the indicated SUPI supports SOR-CMCI from the UDR, and the UDM supports communication with the SP-AF, the UDM can send this list and SOR-CMCI to the SP-AF requesting it to provide this information in a secured packet as defined in 3GPP TS 29.544 [71]. NOTE 4: Before providing the HPLMN UDM with a new list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI, the SOR-AF, based on operator policies or criteria, can obtain the user location information by triggering the unified location service exposure procedure as defined in 3GPP TS 23.273 [70] clause 6.5, or additionally based on implementation specific criteria, by requesting the UE location information from other application function using implementation specific method. This user location information can then be used in the SOR-AF algorithms. NOTE 5: 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 the SOR-CMCI, if any, cannot be included in the secured packet. Figure C.3.1: Procedure for providing list of preferred PLMN/access technology combinations and the SOR-CMCI, if any, or secured packet after registration For the steps below, security protection is described in 3GPP TS 33.501 [66]. 1) The SOR-AF to the HPLMN UDM: Nudm_ParameterProvision_Update request is sent to the HPLMN UDM to trigger the update of the UE with the new list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, and the "Store SOR-CMCI in ME" indicator, if any, or a secured packet for a UE identified by SUPI. 2) The HPLMN UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. The Nudm_SDM_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the HPLMN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm_SDM_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. If the SOR-CMCI was obtained, the HPLMN UDM shall include the SOR-CMCI into the steering of roaming information. If the "Store SOR-CMCI in ME" indicator was obtained, the HPLMN UDM shall include the "Store SOR-CMCI in ME" indicator; otherwise, the HPLMN UDM shall include the "Store SOR-CMCI in ME" indicator set to "Do not store SOR-CMCI in ME"; NOTE 6: 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]). 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. 4) Upon receiving the steering of roaming information, the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by HPLMN, and: - if the security check is successful and: a) if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]) and the service "data download via SMS Point-to-point" is allocated and activated in the USIM Service Table (see 3GPP TS 31.102 [40]), the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41]. If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message and the ME receives UICC responses indicating that the UICC has received the secured packet successfully, then the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE: - shall set the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container to "supported"; - may set the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN using credentials from a credentials holder; and - shall set the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN providing access for localized services in SNPN. NOTE 7: How the ME handles UICC responses that do not indicate that the UICC has received the secured packet successfully and failures in communication between the ME and UICC is implementation specific and out of scope of this release of the specification. When the ME receives a USAT REFRESH command qualifier (see 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. If the UE is in automatic network selection mode, 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. 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 or performing emergency service fallback, until the attempts to obtain service on a higher priority PLMN are completed; or - 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. If the UE is in automatic network selection mode it shall apply the actions in clause C.4; b) 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. If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE: - shall set the "ME support of SOR-CMCI" indicator to "supported" - may set the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN using credentials from a credentials holder; and - shall set the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN providing access for localized services in SNPN. If the UE is in automatic network selection mode and the selected PLMN is a VPLMN, then: - if the UE has a stored SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, the UE shall apply the actions in clause C.4; or - 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. 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, emergency services fallback or establishing an emergency PDU session, until the attempts to obtain service on a higher priority PLMN are completed. If the selected PLMN is a VPLMN and 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, if the UE is in automatic network selection mode. If the UDM has not requested an acknowledgement from the UE, then step 5 is skipped; and - if the selected PLMN is a VPLMN, the security check is not successful and the UE is in automatic network selection mode, then: - if the UE has a stored SOR-CMCI, the current PLMN is considered as lowest priority and the UE shall apply the actions in clause C.4; or - if there are ongoing PDU sessions or services, the UE shall apply the actions in clause C.4; or - 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. 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, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed; - if the UE does not have a stored SOR-CMCI, then: - if there are ongoing PDU sessions or services, 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 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, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. If the selected PLMN is a VPLMN and the UE has an established emergency PDU session, then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released; or - if there are no ongoing PDU sessions or services, 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. 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, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. Step 5 is skipped; NOTE 8: 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. 5) The AMF to the HPLMN UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, 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 successful security check of the received steering of roaming information in step 1, the UDM verifies that the acknowledgement is provided by the UE. 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; - 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; and - the "ME support of SOR-SNPN-SI-LS" 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-LS" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any; and 6) 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, "ME support of SOR-SNPN-SI-LS" 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 5, then the HPLMN UDM informs the SOR-AF about successful delivery of the list of preferred PLMN/access technology combinations, SOR-CMCI, if any, 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; - 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 - the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator. If the selected PLMN is a VPLMN and: - the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and - upon switching to automatic network selection mode, the UE remembers that it is still registered on the PLMN where the security check failure of SOR information was encountered; 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, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. If the selected PLMN is a VPLMN and the UE has an established emergency PDU session, then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released. NOTE 9: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. NOTE 10: If the selected PLMN is the HPLMN, regardless of whether the UE is in automatic network selection mode or manual network selection mode, regardless of whether the UE has an established emergency PDU session or not, and regardless of whether the security check is successful or not successful, the UE is not required to perform the PLMN selection. C.4 Enhanced 5G control plane steering of roaming for the UE in connected mode C.4.1 General The HPLMN or subscribed SNPN, based on operator policy, may provide the UE with SOR-CMCI to control the timing when the UE enters idle mode and performs higher priority PLMN/access technology or SNPN selection. This is achieved by the HPLMN indicating to the UE the criteria for releasing specific PDU session(s) or services and entering idle mode. NOTE 1: The released PDU sessions may be re-established by the application once the UE successfully registers on a higher priority PLMN or SNPN. User interaction is required for some applications. The HPLMN or subscribed SNPN may configure the SOR-CMCI in the UE, and may also provide the SOR-CMCI to the UE over N1 NAS signalling. The SOR-CMCI received over N1 NAS signalling takes precedence over the SOR-CMCI stored in the non-volatile memory of the ME or stored in the USIM. NOTE 2: The SOR-CMCI received over N1 NAS signalling in the steering of roaming information is either the SOR-CMCI in the USAT REFRESH with command qualifier of type "Steering of Roaming" (see 3GPP TS 31.111 [41]) which is received in a secured packet, or the SOR-CMCI received in plain text. If the UE receives SOR information containing the list of preferred PLMN/access technology combinations or SOR-SNPN-SI without SOR-CMCI, or the ME receives USAT REFRESH with command qualifier (see 3GPP TS 31.111 [41]) of type "Steering of Roaming" without SOR-CMCI, or the security check of the received steering of roaming information is not successful as described in clause C.2, clause C.3 and clause C.4.3, then: 1) if the UE has SOR-CMCI stored in the non-volatile memory of the ME, the UE shall use the SOR-CMCI stored in the non-volatile memory of the ME; and 2) if the UE has no SOR-CMCI stored in the non-volatile memory of the ME, the UE shall use the SOR-CMCI stored in the USIM, if any. The UE shall delete the stored SOR-CMCI, if any, in the non-volatile memory of the ME and store the received SOR-CMCI in the non-volatile memory of the ME when: 1) the ME receives SOR-CMCI in the USAT REFRESH with command qualifier (see 3GPP TS 31.111 [41]) of type "Steering of Roaming"; or 2) the UE receives the steering of roaming information containing the SOR-CMCI in plain text over N1 NAS signalling and the UE receives the "Store SOR-CMCI in ME" indicator set to "Store SOR-CMCI in ME"; The SOR-CMCI shall be stored in the non-volatile memory of the ME together with the SUPI from the USIM. The ME shall not delete the SOR-CMCI when the UE is switched off. The ME shall delete the SOR-CMCI when a new USIM is inserted. If the UE receives the steering of roaming information over N1 NAS signalling containing the SOR-CMCI together with the "Store SOR-CMCI in ME" indicator set to "Do no store SOR-CMCI in ME", the UE shall not overwrite the SOR-CMCI stored in the ME, if any, with the received SOR-CMCI, and shall apply the received SOR-CMCI for the procedure triggered by receiving the steering of roaming information containing that SOR-CMCI. If there is an ongoing SOR procedure, then the UE shall apply the received SOR-CMCI as described in clause C.4. SOR-CMCI consists of SOR-CMCI rules. Each SOR-CMCI rule consists of the following parameters: i) a criterion of one of the following types: - PDU session attribute type criterion; - service type criterion; - SOR security check criterion; or - match all type criterion; and ii) a value for Tsor-cm timer associated with each criterion presented in i) indicating the time the UE shall wait before releasing the PDU sessions or the services and entering idle mode. SOR-CMCI contains zero, one or more SOR-CMCI rules with PDU session attribute type criterion, zero, one or more SOR-CMCI rules with service type criterion, zero or one SOR-CMCI rule with SOR security check criterion and zero or one SOR-CMCI rule with match all type criterion. PDU session attribute type criterion consists of one of the following: a) DNN of the PDU session; b) S-NSSAI STT of the PDU session; or c) S-NSSAI SST and SD of the PDU session. Service type criterion consists of one of the following: a) IMS registration related signalling; b) MMTEL voice call; c) MMTEL video call; or d) SMS over NAS or SMSoIP. SOR security check criterion consists of: a) SOR security check not successful. Match all type criterion consists of: a) match all. The MS shall be able to handle at least: - 4 SOR-CMCI rules for PDU session attribute type criterion DNN of the PDU session; - 4 SOR-CMCI rules for PDU session attribute type criterion S-NSSAI STT of the PDU session or S-NSSAI SST and SD of the PDU session; and - 6 SOR-CMCI rules for any of the following types: service type criterion, SOR security check criterion or match all type criterion. When the SOR-CMCI received by the UE over N1 NAS signalling contains no SOR-CMCI rules, the UE shall stop all running Tsor-cm timers, if any, and shall not follow the procedure described in clause C.4.2. Additionally: - if the SOR-CMCI is received in plain text and it also contains the "Store SOR-CMCI in ME" indicator set to "Store SOR-CMCI in ME", the UE shall delete the stored SOR-CMCI in the non-volatile memory of the ME, if any; and - if the SOR-CMCI is received in a secured packet, and the USIM provides the ME with the SOR-CMCI in the USAT REFRESH with command qualifier of type "Steering of Roaming" (see 3GPP TS 31.111 [41]), then the UE shall delete the stored SOR-CMCI in the non-volatile memory of the ME, if any. The HPLMN may update the SOR-CMCI in the USIM such that it contains no SOR-CMCI rules, in which case the UE behaviour described in clause C.4.2 applies. Also the HPLMN may make the SOR-CMCI file in the USIM unavailable (see 3GPP TS 31.102 [40]). If there are more than one criterion applicable for a PDU session (e.g., a criterion for the PDU session and another one for the service) then the Tsor-cm timer with the highest value shall apply. If there are more than one criterion applicable to different ongoing PDU sessions or services leading to multiple applicable Tsor-cm timers, then all the applicable Tsor-cm timers shall be started. Further handling of such cases is described in clause C.4.2. If the value for Tsor-cm timer equals "infinity" then the UE shall wait until the PDU session is released or the service is stopped. The Tsor-cm timer is applicable only if the UE is in automatic network selection mode. Upon switching to the manual network selection mode, the UE shall stop any Tsor-cm timer, if running. In this case, the UE is not required to enter idle mode and perform the de-registration procedure. The UE shall consider the following services as exempted from being forced to release the related established PDU session, if any, enter idle mode and perform high priority PLMN/access technology or SNPN selection. These services are known to the UE by default and the UE shall not follow the SOR-CMCI criteria even if configured to interrupt such services: i) emergency services. The UE configured with high priority access in the selected PLMN or SNPN shall consider all services and all related established PDU sessions, if any, to be exempted from being forced to be released to enter idle mode and perform high priority PLMN/access technology or SNPN selection. C.4.2 Applying SOR-CMCI in the UE During SOR procedure and while applying SOR-CMCI, the UE shall determine the time to release the PDU session(s) or the services as follows: - If the UE encounters SOR security check not successful on the received steering of roaming information, and: - if a matching criterion "SOR security check not successful" is included in the stored SOR-CMCI, then the UE shall: - if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; - stop all other running Tsor-cm timers, if any; and - not start any new Tsor-cm timer while Tsor-cm timer associated with "SOR security check not successful" criterion is running; - otherwise, the UE shall keep the Tsor-cm timers running, if any, and apply actions when the timers expire as described in this clause. - If the UE encounters SOR security check successful on the received steering of roaming information and one or more SOR-CMCI rules are included in SOR-CMCI, where for each criterion: a) DNN of the PDU session: the UE shall check whether it has a PDU session with a DNN matching to the DNN included in SOR-CMCI, and if any, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; b) S-NSSAI SST of the PDU session: the UE shall check whether it has a PDU session with a S-NSSAI SST matching the S-NSSAI SST included in SOR-CMCI, and if any, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; b1) S-NSSAI SST and SD of the PDU session: the UE shall check whether it has a PDU session with a S-NSSAI SST and SD matching the S-NSSAI SST and SD included in SOR-CMCI, and if any, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; c) IMS registration related signalling: the UE shall check whether IMS registration related signalling is ongoing, and if it is ongoing, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; d) MMTEL voice call: the UE shall check whether MMTEL voice call is ongoing, and if it is ongoing, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; e) MMTEL video call: the UE shall check whether MMTEL video call is ongoing, and if it is ongoing, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; f) SMS over NAS or SMSoIP: the UE shall check whether SMS over NAS or SMSoIP services is ongoing, and if it is ongoing, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; or g) match all: the UE shall check whether there are any PDU sessions or services for which there is no matching criterion in a) to f) above. If such PDU session or service exists, then for each of these PDU sessions or services, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI. If the SOR-CMCI is available, and: - the SOR-CMCI used is in the USIM, contains no SOR-CMCI rule; - there are one or more SOR-CMCI rules but there is no criterion matched with any ongoing PDU session or service; or - there are one or more SOR-CMCI rules and there is one or more criteria matched with an ongoing PDU session or service, but the highest Tsor-cm timer value associated with the matched criteria is equal to zero; then there is no Tsor-cm timer started for any PDU session or service. While one or more Tsor-cm timers are running, the UE shall check the newly established PDU session or service for a matching criterion in the SOR-CMCI: - If a matching criterion is found and the applicable Tsor-cm timer indicated the value "infinity" then the UE shall start the Tsor-cm timer associated to the newly established PDU session or service with the value set to infinity; or - For all other cases, if a matching criterion is found and the timer value is not zero then the UE shall start the Tsor-cm timer associated to the newly established PDU session or service with the value included in the SOR-CMCI, with the exception that if the value of the Tsor-cm timer included in the SOR-CMCI exceeds the highest value among the current values of all running Tsor-cm timers, then the value of the Tsor-cm timer for the newly established PDU session or service shall be set to the highest value among the current values of all running Tsor-cm timers. NOTE 1: For newly established PDU session or service as described above, the timer is set irrespective of whether other ongoing PDU sessions or services that match the same criteria exist and for which corresponding Tsor-cm timers are running. NOTE 2: NAS 5GMM layer will receive an explicit indication from the upper layers that a service is started or stopped. When a service is started, it is handled as a new service in the procedures described in this clause. NOTE 3: While one or more Tsor-cm timers are running, the UE can trigger any 5GSM procedure or start new services. While one or more Tsor-cm timers are running, upon receiving a new SOR-CMCI as described in annex C.4.3, the UE shall check if there is a matching criterion found for any ongoing PDU session or service in the new SOR-CMCI: - if a matching criterion is found and the value of Tsor-cm timer in the new SOR-CMCI indicates the value "infinity", then: a) if the Tsor-cm timer associated to the PDU session or service is not running, then the UE shall start the Tsor-cm timer associated to the PDU session or service with the value set to infinity; or b) if the Tsor-cm timer associated to the PDU session or service is already running, then the UE shall set the value of the Tsor-cm timer associated to the PDU session or service to infinity without stopping and restarting the timer; - if a matching criterion is found and the value of Tsor-cm timer in the new SOR-CMCI is other than infinity and is smaller than the current value of the running Tsor-cm timer for the associated PDU session or service, then the Tsor-cm timer value for the associated PDU session or service shall be replaced with the value in the new SOR-CMCI without stopping and restarting the timer; or - for all other cases, the running Tsor-cm timers for the associated PDU sessions or services are kept unchanged. The Tsor-cm timer shall be stopped when the associated PDU session is released or the associated service is stopped. If the security check on the received steering of roaming information is successful, the UE shall stop the Tsor-cm timer associated with "SOR security check not successful", if running, and act on the received steering of roaming information. The current PLMN or SNPN is not considered as lowest priority. NOTE 4: This also applies to the case when the current PLMN or SNPN is different from the PLMN or SNPN in which the Tsor-cm timer associated with "SOR security check not successful" was started. If the UE, while one or more Tsor-cm timers are running: a) enters idle mode not due to lower layer failure (see 3GPP TS 24.501 [64]); b) is not able to successfully recover the N1 NAS signalling connection (see 3GPP TS 24.501 [64]); or c) enters 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]); then the UE shall stop the timer(s). In these cases, if: a) the UE has a list of available and allowable PLMNs or SNPNs in the area and based on this list or any other implementation specific means, the UE determines that there is a higher priority PLMN or SNPN than the selected VPLMN or non-subscribed SNPN; or b) the UE does not have a list of available and allowable PLMNs or SNPNs in the area and is unable to determine whether there is a higher priority PLMN or SNPN than the selected VPLMN or non-subscribed SNPN using any other implementation specific means; then the UE shall attempt to obtain service on a higher priority PLMN or SNPN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired or as specified in clause 4.9.3. NOTE 5: When the UE enters idle mode due to lower layer failure while one or more Tsor-cm timers are running, then the UE does not stop Tsor-cm timer(s) as recovery of NAS signalling connection is possible (see 3GPP TS 24.501 [64]). When the UE determines that no Tsor-cm timer is started for any PDU session or service, the last running Tsor-cm timer is stopped due to release of the associated PDU sessions or stop of the associated services, or the last running Tsor-cm timer expires, if: i) the UE has a list of available and allowable PLMNs or SNPNs in the area and based on this list or any other implementation specific means, the UE determines that there is a higher priority PLMN or SNPN than the selected VPLMN or non-subscribed SNPN; or ii) the UE does not have a list of available and allowable PLMNs or SNPNs in the area and is unable to determine whether there is a higher priority PLMN or SNPN than the selected VPLMN or non-subscribed SNPNusing any other implementation specific means; then if the UE is in 5GMM-CONNECTED mode, the UE shall perform the de-registration procedure (see clause 4.2.2.3 of 3GPP TS 23.502 [63]) that releases all the established PDU sessions and services, if any, and once the UE enters idle mode it shall attempt to obtain service on a higher priority PLMN or SNPN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired or as specified in clause 4.9.3. NOTE 6: The list of available and allowable PLMNs or SNPNs in the area is implementation specific. The UE which has an emergency PDU session, receives a request from the upper layers to establish an emergency PDU session or perform emergency services fallback, registers for emergency services, or is configured for high priority access in the selected PLMN or SNPN is not required to enter idle mode if the last running Tsor-cm timer for any PDU session or service stops or expires. In this case, the UE shall attempt to perform the PLMN or SNPN selection after the emergency PDU session or the high priority service is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). If the UE selects a cell of any access technology other than NG-RAN, the ongoing SOR procedure is terminated and the UE shall stop applying SOR-CMCI and stop all running Tsor-cm timers without triggering any further actions. NOTE 7: 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. C.4.3 Stage-2 flow for providing UE with SOR-CMCI in HPLMN, VPLMN, subscribed SNPN or non-subscribed SNPN after registration The stage-2 flow for providing UE with SOR-CMCI in HPLMN, VPLMN, subscribed SNPN or non-subscribed SNPN after registration is indicated in figure C.4.3.1, when the ME supports the SOR-CMCI. The selected PLMN or SNPN can be the HPLMN, a VPLMN, the subscribed SNPN or a non-subscribed SNPN. The AMF is located in the selected PLMN or SNPN. The UDM is located in the HPLMN or the subscribed SNPN. In this procedure, the SOR-CMCI is sent without the list of preferred PLMN/access technology combinations and the SOR-SNPN-SI. In this procedure, the SOR-CMCI is sent in plain text or is sent within the secured packet. NOTE 0: When the UE is registered in a non-subscribed SNPN, the SOR-CMCI can be provided in a secured packet only if the UE is using a PLMN subscription to access the non-subscribed SNPN. NOTE 1: 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. The UDM can determine that the ME supports the SOR-CMCI if the "ME support of SOR-CMCI" indicator is stored for the UE. How the SOR-AF determines that the USIM for the indicated SUPI supports SOR-CMCI is implementation specific. NOTE 2: The 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. The procedure is triggered: - If the UDM supports obtaining the parameters of the list of preferred PLMN/access technology combinations, the SOR-SNPN-SI, the SOR-CMCI, and the "Store SOR-CMCI in ME" indicator, if any, or a secured packet from the SOR-AF, the HPLMN or subscribed SNPN policy for the SOR-AF invocation is present in the UDM and the SOR-AF provides the UDM with the SOR-CMCI for a UE identified by SUPI; or - When the SOR-CMCI becomes available in the UDM (i.e., retrieved from the UDR). Figure C.4.3.1: Procedure for configuring UE with SOR-CMCI after registration For the steps below, security protection is described in 3GPP TS 33.501 [66]. 1) The SOR-AF to the UDM: Nudm_ParameterProvision_Update request is sent to the UDM to trigger the update of the UE with the SOR-CMCI (in plain text or secured packet). In case of providing SOR-CMCI in plain text, include the "Store SOR-CMCI in ME" indicator, if applicable. In case of providing SOR-CMCI in a secured packet, include an indication that "the list of preferred PLMN/access technology combinations is not included in the secured packet". 2) The UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. The Nudm_SDM_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the HPLMN or subscribed SNPN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm_SDM_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. The UDM: - upon receiving the SOR-CMCI (in plain text), shall: i) if the UE is registered in the HPLMN or a VPLMN, include the SOR-CMCI, the "Store SOR-CMCI in ME" indicator, if any, and 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'; ii) if the UE is registered in a non-subcribed SNPN, include the SOR-CMCI, the "Store SOR-CMCI in ME" indicator, if any, and the HPLMN or subscribed SNPN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'; and iii) if the UE is registered in a subcribed SNPN and the AMF has reported to the UDM that the UE supports SOR-SNPN-SI, include the SOR-CMCI, the "Store SOR-CMCI in ME" indicator, if any, and the HPLMN or subscribed SNPN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'; or - upon receiving the SOR-CMCI in secured packet, shall include the secured packet into the steering of roaming information; NOTE 3: The UDM considers "the list of preferred PLMN/access technology combinations is not included in the secured packet" received together with the secured packet from the SOR-AF to indicate that the UE is not expected to perform SOR based on the associated steering of roaming information sent to the UE. However, the SOR-CMCI included in the secured packet can be applied by the UE if the UE has one or more Tsor-cm timers running as described in C.4.2. NOTE 4: The UDM cannot provide the SOR-CMCI, if any, to the AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. 4) Upon receiving the steering of roaming information containing the SOR-CMCI and 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' or the HPLMN or subscribed SNPN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided', or the secured packet, the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by HPLMN or subscribed SNPN, and: a) if the security check is successful, the UE shall store the SOR-CMCI according to clause C.4.1. If the UE has one or more Tsor-cm timers running, the UE shall apply the received SOR-CMCI as described in C.4.2. If the steering of roaming information contains a secured packet and the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set the "ME support of SOR-CMCI" indicator to "supported" only after the ME receives UICC responses indicating that the UICC has received the secured packet successfully. Otherwise, if the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set the "ME support of SOR-CMCI" indicator to "supported". Additionally, if the UE supports access to an SNPN using credentials from a credentials holder and the UE is in a PLMN, the UE may set the "ME support of SOR-SNPN-SI" indicator to "supported". If the UDM has not requested an acknowledgement from the UE then step 5 is skipped; and b) if the selected PLMN is a VPLMN or a non-subscribed SNPN, the security check is not successful and the UE is in automatic network selection mode, then: - if the UE has a stored SOR-CMCI, the current PLMN is considered as lowest priority and the UE shall apply the actions in clause C.4.2; - otherwise, 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 PLMN is considered as lowest priority, or before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the selected PLMN or SNPN is a VPLMN or a non-subscribed SNPN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). Step 5 is skipped; NOTE 5: 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 or the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs for the selected entry of the "list of subscriber data" the selected PLMN subscription, the UE stays on the VPLMN or non-subscribed SNPN. 5) The AMF to the UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, the AMF uses the Nudm_SDM_Info service operation to provide the received SOR transparent container to the UDM. If the HPLMN or subscribed SNPN decided that the UE is to acknowledge successful security check of the received steering of roaming information in step 2, the UDM verifies that the acknowledgement is provided by the UE. If: - the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-CMCI" indicator, otherwise the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any; and - the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-SNPN-SI" indicator, otherwise the UDM shall delete the stored "ME support of SOR-SNPN-SI" indicator, if any; and 6) The UDM to the SOR-AF: Nsoraf_SoR_Info (SUPI of the UE, successful delivery, "ME support of SOR-CMCI" indicator, "ME support of SOR-SNPN-SI" indicator, if any). If the HPLMN or subscribed SNPN policy for the SOR-AF invocation is present and the UDM received and verified the UE acknowledgement in step 5, then the UDM informs the SOR-AF about successful delivery of the SOR-CMCI to the UE. The UDM shall include the "ME support of SOR-CMCI" indicator. If the "ME support of SOR-SNPN-SI" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI" indicator. If the selected PLMN is a VPLMN or a non-subscribed SNPN and: - the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and - upon switching to automatic network selection mode the UE remembers that it is still registered on the PLMN the non-subscribed SNPN where the security check failure of SOR information was encountered; 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, or before attempting to obtained service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the selected PLMN is a VPLMN or the selected SNPN is a non-subscribed SNPN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). NOTE 6: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. C.5 Stage-2 flow for steering of UE in SNPN during registration The stage-2 flow for the case when the UE registers in a non-subscribed SNPN is described below in figure C.5.1. The AMF is located in the non-subscribed SNPN. The UDM is located in the HPLMN or subscribed SNPN. Figure C.5.1: Procedure for providing SOR-SNPN-SI and SOR-SNPN-SI-LS (if any) during registration For the steps below, security protection is described in 3GPP TS 33.501 [66]. 1) The UE to the 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 AMF by sending REGISTRATION REQUEST message with the 5GS registration type IE indicating "initial registration", "emergency registration" or "mobility registration updating"; 2) Upon receiving the REGISTRATION REQUEST message, the 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-LS" 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 AMF does not have subscription data for the UE, the AMF invokes Nudm_SDM_Get service operation to the 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 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 AMF invokes Nudm_SDM_Get service operation message to the 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 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 UE is registering on a non-subscribed SNPN except if the UE supports equivalent SNPNs, the ME does not support SOR-SNPN-SI and the UE is in an equivalent SNPN of the subscribed SNPN,the UDM shall store the "ME support of SOR-SNPN-SI" indicator. Except if the UE supports equivalent SNPNs, the ME does not support SOR-SNPN-SI and the UE is in an equivalent SNPN of the subscribed SNPN: a) if the user subscription information indicates to send the steering of roaming information due to initial registration in a non-subscribed SNPN, then when the UE performs initial registration in a non-subscribed SNPN, the UDM shall provide the steering of roaming information to the UE; and b) otherwise, when the UE is registering on a non-subscribed SNPN, the UDM may provide the SOR-SNPN-SI to the UE based on the subscribed SNPN or HPLMN policy. If the UDM is to provide the steering of roaming information to the UE when the UE performs the registration in a non-subscribed SNPN and the subscribed SNPN or HPLMN policy for the SOR-AF invocation is absent then steps 3b and 3c are not performed and the UDM obtains the available SOR-SNPN-SI (i.e. all retrieved from the UDR). In addition, if the UDM obtains the SOR-SNPN-SI and - the "ME support of SOR-CMCI" indicator is stored for the UE, then the UDM shall obtain the SOR-CMCI, if available, otherwise the UDM shall not obtain the SOR-CMCI. If the SOR-CMCI is provided then the UDM may indicate to the UE to store the SOR-CMCI in the ME by providing the "Store the SOR-CMCI in the ME" indicator; and - the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, then the UDM shall obtain the SOR-SNPN-SI-LS, if available, otherwise the UDM shall not obtain the SOR-SNPN-SI-LS. If the UDM is to provide the steering of roaming information to the UE when the UE performs the registration in a non-subscribed SNPN and the subscribed SNPN or HPLMN policy for the SOR-AF invocation is present, then the UDM obtains the SOR-SNPN-SI, SOR-CMCI, if any, and SOR-SNPN-SI-LS, if any, from the SOR-AF using steps 3b and 3c; 3b) The UDM to the SOR-AF: Nsoraf_SoR_Get request (SNPN identity, SUPI of the UE, access type (see 3GPP TS 29.571 [72])). The SNPN identity and the access type parameters, indicating where the UE is registering, are stored in the UDM; 3c) The SOR-AF to the UDM: Nsoraf_SoR_Get response (the SOR-SNPN-SI, the SOR-CMCI, if any, the "Store the SOR-CMCI in the ME" indicator, if any, and the SOR-SNPN-SI-LS, if any); Based on the information received in step 3b and any subscribed SNPN or HPLMN specific criteria, the SOR-AF may include the SOR-SNPN-SI, the SOR-CMCI, if any, optionally the "Store the SOR-CMCI in the ME" indicator, if any, and the SOR-SNPN-SI-LS, if any. If the SOR-AF includes the SOR-SNPN-SI and the ME supports: - the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally the "Store the SOR-CMCI in the ME" indicator, otherwise the SOR-AF shall provide neither the SOR-CMCI nor the "Store the SOR-CMCI in the ME" indicator;and - the SOR-SNPN-SI-LS, the SOR-AF may provide the SOR-SNPN-SI-LS, otherwise the SOR-AF shall not provide SOR-SNPN-SI-LS. NOTE 1: 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 2: The SOR-AF can include a different SOR-SNPN-SI, different SOR-CMCI, if any, different "Store the SOR-CMCI in the ME" indicator, if any, and different SOR-SNPN-SI-LS, if any, for each Nsoraf_SoR_Get request even if the same SNPN identity, the SUPI of the UE, and the access type are provided to the SOR-AF. NOTE 3: The SOR-AF can subscribe to the UDM to be notified about the changes of the roaming status of the UE identified by SUPI. NOTE 4: The SOR-AF can determine that the ME supports the SOR-CMCI or the SOR-SNPN-SI-LS if the Nsoraf_SoR_Info service operation has returned the "ME support of SOR-CMCI" indicator or the "ME support of SOR-SNPN-SI-LS" indicator, respectively. 3d) The UDM forms the steering of roaming information as specified in 3GPP TS 33.501 [66] from the SOR-SNPN-SI, the SOR-CMCI, if any, the "Store the SOR-CMCI in the ME" indicator, if any, and SOR-SNPN-SI-LS, if any, obtained in step 3a or the SOR-SNPN-SI, the SOR-CMCI, if any, the "Store the SOR-CMCI in the ME" indicator, if any, and SOR-SNPN-SI-LS, if any, obtained in step 3c. If: - the SOR-SNPN-SI was not obtained in steps 3a or 3c; or - the SOR-AF has not sent to the UDM an Nsoraf_SoR_Get response (step 3c) within an operator defined time after the UDM sending to the SOR-AF an Nsoraf_SoR_Get request (step 3b); NOTE 5: Stage 3 to define the timer needed for the SOR-AF to respond to the 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 non-subscribed SNPN and the user subscription information indicates to send the steering of roaming information due to initial registration in a non-subscribed SNPN, then the UDM forms the steering of roaming information as specified in 3GPP TS 33.501 [66] from the subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'; 4) The UDM to the AMF: The UDM sends a response to the Nudm_SDM_Get service operation to the 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 6: The UDM cannot provide the SOR-SNPN-SI, the SOR-CMCI, if any, or the SOR-SNPN-SI-LS to the 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 UDM supports SOR-CMCI or SOR-SNPN-SI-LS, the subscribed SNPN or 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 subscribed SNPN or 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; 5) The AMF to the UDM: As part of the registration procedure, the SNPN also invokes Nudm_SDM_Subscribe service operation to the 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 AMF to the UE: The 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; and b) if the steering of roaming information contains the SOR-SNPN-SI, the ME shall replace the credentials holder controlled prioritized list of preferred SNPNs for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received credentials holder controlled prioritized list of preferred SNPNs, if any, and the ME shall replace the credentials holder controlled prioritized list of GINs for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received credentials holder controlled prioritized list of GINs, if any, and delete the SNPNs identified by the credentials holder controlled prioritized list of preferred SNPNs or the SNPN(s) stored along with GIN(s) identified by the credentials holder controlled prioritized list of GINs from the list of "temporarily forbidden SNPNs" and the list of "permanently forbidden SNPNs", if they are present in these lists. If the SOR information contains the SOR-SNPN-SI-LS, the ME shall replace the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", if any, and the ME shall replace the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", if any, and delete the SNPNs identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or the SNPN(s) stored along with GIN(s) identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "temporarily forbidden SNPNs for access for localized services in SNPN" and the list of "permanently forbidden SNPNs for access for localized services in SNPN", if they are present in these lists. The ME shall delete the tracking area(s) included in the location validity information corresponding to an SNPN identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" from the list of "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" associated with the SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, if they are present in these lists. The ME shall delete the tracking area(s) included in the location validity information corresponding to a GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" associated with an SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, if the tracking area(s) in these lists is associated with the GIN. Additionally, the UE may perform SNPN selection. If the UE decides to perform SNPN selection: i) if the UE has a list of available and allowable SNPN in the area and based on this list or any other implementation specific means the UE determines that there is a higher priority SNPN than the selected SNPN; or ii) the UE does not have a list of available and allowable SNPN in the area and is unable to determine whether there is a higher priority SNPN than the selected SNPN using any other implementation specific means; 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 SNPN as specified in clause 4.9.3. 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 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 SNPN 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. The UE shall release the current N1 NAS signalling connection locally subsequently after the emergency PDU session is released. 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 SNPN as described in this step, and if no higher priority SNPN can be selected but the last registered SNPN 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 7: When the UE is in the manual mode of operation or the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs, the UE stays on the current chosen non-subscribed SNPN. 8) If the UE's ME is configured with an indication that the UE is to receive the steering of roaming information due to initial registration in a non-subscribed SNPN, but neither the SOR-SNPN-SI nor the subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI 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 non-subscribed SNPN is not contained in the list of "SNPNs where registration was aborted due to SOR" for the selected entry in the "list of subscriber data" or the selected PLMN subscription, and is not part of the user controlled prioritized list of preferred SNPNs for the selected entry in the "list of subscriber data" or the selected PLMN subscription, and the UE is not in manual mode of operation, release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN 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. If the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]), the UE shall release the current N1 NAS signalling connection locally after the release of the emergency PDU session. 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 SNPN as described in this step, and if no higher priority SNPN can be selected but the last registered SNPN is selected, then the UE shall disable the N1 mode capability; and c) if the current chosen non-subscribed SNPN is not contained in the list of "SNPNs where registration was aborted due to SOR" for the selected entry in the "list of subscriber data" or the selected PLMN subscription, store the SNPN identity in the list of "SNPNs where registration was aborted due to SOR" for the selected entry in the "list of subscriber data" or the selected PLMN subscription; NOTE 8: When the UE is in the manual mode of operation or the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs, the UE stays on the current chosen non-subscribed SNPN. 9) The UE to the 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 subscribed SNPN or 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"; b1) if the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall set the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container to "supported"; and c) if: 1) the steering of roaming information contains the SOR-SNPN-SI, the UE is configured with the SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, the UE is in automatic network selection mode and the UE decides to perform SNPN selection, then the UE shall apply the actions in clause C.4.2, and step 11 is skipped; or 2) the steering of roaming information contains subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided', then step 11 is skipped; 10) The AMF to the 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 subscribed SNPN or 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 UDM shall store the “ME support of SOR-CMCI” indicator, otherwise the UDM shall delete the stored “ME support of SOR-CMCI” indicator, if any; and - the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-SNPN-SI-LS" indicator, otherwise the UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any NOTE 9: The UDM cannot receive the "ME support of SOR-CMCI" indicator or the "ME support of SOR-SNPN-SI-LS" indicator from the AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). 10a) The 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-LS" indicator, if any). If the subscribed SNPN or HPLMN policy for the SOR-AF invocation is present and the UDM received and verified the UE acknowledgement in step 10, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI to the UE. If: - the "ME support of SOR-CMCI" indicator is stored for the UE, the UDM shall include the "ME support of SOR-CMCI" indicator; and - the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator; and 11) If the UE has a list of available SNPNs in the area and based on this list the UE determines that there is a higher priority SNPN than the selected SNPN and the UE is in automatic network selection mode, then the UE may attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3 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 signalling connection except when the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]). When the UE performs initial registration for emergency services (see 3GPP TS 24.501 [64] and 3GPP TS 23.502 [63]) and the AMF performs the authentication procedure, then based on subscribed SNPN or 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 where the security check failure of SOR information was encountered as described in step 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 SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the UE has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection subsequently after the emergency PDU session is released. NOTE 10: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. NOTE 11: The list of available and allowable SNPNs in the area is implementation specific. C.6 Stage-2 flow for steering of UE in SNPN after registration The stage-2 flow for the steering of UE in SNPN after registration is indicated in figure C.6.1. The UE is registered on an SNPN which can be the subscribed SNPN or a non-subscribed SNPN. The AMF is located in the selected SNPN. The UDM is located in the HPLMN or subscribed SNPN. The procedure is triggered if: a) the UDM supports obtaining SOR-SNPN-SI, if any, SOR-CMCI, if any, and SOR-SNPN-SI-LS, if any, from the SOR-AF, the subscribed SNPN or HPLMN policy for the SOR-AF invocation is present in the UDM, and the SOR-AF provides the UDM with: - the SOR-SNPN-SI for a UE identified by SUPI if the ME supports SOR-SNPN-SI; - the SOR-CMCI for a UE identified by SUPI if the ME supports SOR-CMCI; or - the SOR-SNPN-SI-LS for a UE identified by SUPI if the ME supports SOR-SNPN-SI-LS; or NOTE 0: The SOR-AF can determine that the ME supports SOR-SNPN-SI if the Nsoraf_SoR_Info service operation has returned the "ME support of SOR-SNPN-SI" indicator. The UDM determines that the ME supports SOR-SNPN-SI if the UDM stores "ME support of SOR-SNPN-SI" indicator for the UE. NOTE 1: 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. How the SOR-AF determines that the USIM for the indicated SUPI supports SOR-CMCI is implementation specific. NOTE 1a: The SOR-AF can determine that the ME supports SOR-SNPN-SI-LS if the Nsoraf_SoR_Info service operation has returned the "ME support of SOR-SNPN-SI-LS" indicator. The UDM determines that the ME supports SOR-SNPN-SI-LS if the UDM stores "ME support of SOR-SNPN-SI-LS" indicator for the UE. b) a SOR-SNPN-SI (if supported by ME), a SOR-CMCI (if supported by ME), or a SOR-SNPN-SI-LS (if supported by ME) becomes available in the UDM (i.e. retrieved from the UDR). NOTE 2: Before providing the UDM with SOR-SNPN-SI for a UE identified by SUPI, the SOR-AF, based on subscribed SNPN or HPLMN policies or criteria, can obtain the user location information by triggering the unified location service exposure procedure as defined in 3GPP TS 23.273 [70] clause 6.5, or additionally based on implementation specific criteria, by requesting the UE location information from other application function using implementation specific method. This user location information can then be used in the SOR-AF algorithms. NOTE 3: Before providing the UDM with a new SOR-SNPN-SI for a UE identified by SUPI, the SOR-AF, based on subscribed SNPN or HPLMN policies or criteria, can obtain the user location information by triggering the unified location service exposure procedure as defined in 3GPP TS 23.273 [70] clause 6.5, or additionally based on implementation specific criteria, by requesting the UE location information from other application function using implementation specific method. This user location information can then be used in the SOR-AF algorithms. Figure C.6.1: Procedure for providing SOR-SNPN-SI (if any) and SOR-SNPN-SI-LS (if any) after registration For the steps below, security protection is described in 3GPP TS 33.501 [66]. 1) The SOR-AF to the UDM: Nudm_ParameterProvision_Update request is sent to the UDM to trigger the update of the UE with the SOR-SNPN-SI,if any, the SOR-CMCI, if any, the "Store the SOR-CMCI in the ME" indicator, if any, and the SOR-SNPN-SI-LS, if any, for a UE identified by SUPI. 2) The UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. The Nudm_SDM_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the subscribed SNPN or HPLMN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm_SDM_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. If the SOR-SNPN-SI was obtained, the UDM shall include the SOR-SNPN-SI in to the SOR information. If the SOR-CMCI was obtained, the UDM shall include the SOR-CMCI into the steering of roaming information and shall requests an acknowledgement from the UE as part of the steering of roaming information. If the "Store the SOR-CMCI in the ME" indicator was obtained, the UDM shall include the "Store the SOR-CMCI in the ME" indicator If the SOR-SNPN-SI-LS was obtained, the UDM shall include the SOR-SNPN-SI-LS into the SOR information; NOTE 4: The UDM cannot provide the SOR-SNPN-SI SOR-CMCI, or SOR-SNPN-SI-LS to the AMF which does not support receiving SOR transparent container (see 3GPP TS 29.503 [78]). 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. 4) Upon receiving the steering of roaming information, the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by the subscribed SNPN or HPLMN, and i) if the security check is successful, then: a) if the steering of roaming information contains the SOR-SNPN-SI, the ME shall replace the credentials holder controlled prioritized list of preferred SNPNs for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received credentials holder controlled prioritized list of preferred SNPNs, if any, the ME shall replace the credentials holder controlled prioritized list of GINs for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received credentials holder controlled prioritized list of GINs, if any, and the ME shall delete the SNPNs identified by the credentials holder controlled prioritized list of preferred SNPNs or the SNPN(s) stored along with GIN(s) identified by the credentials holder controlled prioritized list of GINs from the list of "temporarily forbidden SNPNs" and the list of "permanently forbidden SNPNs", if they are present in these lists. If the SOR information contains the SOR-SNPN-SI-LS, the ME shall replace the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", if any, and the ME shall replace the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", if any, and delete the SNPNs identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or the SNPN(s) stored along with GIN(s) identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "temporarily forbidden SNPNs for access for localized services in SNPN" and the list of "permanently forbidden SNPNs for access for localized services in SNPN", if they are present in these lists. The ME shall delete the tracking area(s) included in the location validity information corresponding to an SNPN identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" from the list of "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" associated with the SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, if they are present in these lists. The ME shall delete the tracking area(s) included in the location validity information corresponding to a GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" associated with an SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, if the tracking area(s) in these lists is associated with the GIN; b) if the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set: - the "ME support of SOR-CMCI" indicator to "supported"; and - the "ME support of SOR-SNPN-SI-LS" indicator to "supported" if the UE supports access to an SNPN providing access for localized services in SNPN. c) if the UE is in automatic network selection mode, the selected SNPN is a non-subscribed SNPN and the UE decides to perform SNPN selection, then: - 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; or - 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 SNPN as specified in clause 4.9.3. d) if the selected SNPN is a non-subscribed SNPN and the UE has an established emergency PDU session then the UE may attempt to perform the SNPN selection subsequently after the emergency PDU session is released, if the UE is in automatic network selection mode. e) if the UDM has not requested an acknowledgement from the UE, then steps 4 is skipped; and ii)the security check is not successful: a) step 5 is skipped; and b) if the selected SNPN is a non-subscribed SNPN and the UE is in automatic network selection mode, then: A) if the UE has a stored SOR-CMCI, then: - if there are ongoing PDU sessions or services, the UE shall apply the actions in clause C.4.2, and the current SNPN is considered as lowest priority; or - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority; B) if the UE does not have a stored SOR-CMCI, then: - if there are ongoing PDU sessions or services, 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 SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority. If the selected SNPN is a non-subscribed SNPN and the UE has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection after the emergency PDU session is released; or - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority. NOTE 5: When the UE is in the manual mode of operation and the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs, the UE stays on the current chosen non-subscribed SNPN. 5) The AMF to the UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, the AMF uses the Nudm_SDM_Info service operation to provide the received SOR transparent container to the UDM. If the subscribed SNPN or HPLMN decided that the UE is to acknowledge successful security check of the received steering of roaming information in step 1, the UDM verifies that the acknowledgement is provided by the UE. If: - the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-CMCI" indicator, otherwise the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any; and - the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-SNPN-SI-LS" indicator, otherwise the UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any. If the present flow was invoked by the UDM after receiving from the SOR-AF the SOR-SNPN-SI, if any, SOR-CMCI, if any, and SOR-SNPN-SI-LS, if any, for a UE identified by SUPI using an Nudm_ParameterProvision_Update request, and the UDM verification of the UE acknowledgement is successful, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI,if any SOR-CMCI, if any, and SOR-SNPN-SI-LS, if any, using Nsoraf_SoR_Info (SUPI of the UE, successful delivery); and 6) The 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-LS" indicator, if any). If the subscribed SNPN or HPLMN policy for the SOR-AF invocation is present and the UDM received and verified the UE acknowledgement in step 5, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI, if any, SOR-CMCI, if any, SOR-SNPN-SI-LS, if any, to the UE. If: - the "ME support of SOR-CMCI" indicator is stored for the UE, the UDM shall include the "ME support of SOR-CMCI" indicator; and - the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator. If the selected SNPN is a non-subscribed SNPN and: - the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and - upon switching to automatic network selection mode, the UE remembers that it is still registered on the where the security check failure of SOR information was encountered; 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 SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the selected SNPN is a non-subscribed SNPN and the UE has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection after the emergency PDU session is released. NOTE 6: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. NOTE 7: If the selected SNPN is the subscribed SNPN, regardless of whether the UE is in automatic network selection mode or manual network selection mode, regardless of whether the UE has an established emergency PDU session or not, and regardless of whether the security check is successful or not successful, the UE is not required to perform the SNPN selection. C.7 Stage-2 flow for providing UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in HPLMN or VPLMN after registration The stage-2 flow for providing UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in HPLMN or VPLMN after registration is indicated in figure C.7.1, when the ME and the HPLMN support the SOR-SNPN-SI or SOR-SNPN-SI-LS, respectively. The selected PLMN can be the HPLMN or a VPLMN. The AMF is located in the selected PLMN. The UDM is located in the HPLMN. In this procedure, the SOR-SNPN-SI or SOR-SNPN-SI-LS is sent without the list of preferred PLMN/access technology combinations. NOTE 1: The SOR-AF can determine that the ME supports the SOR-SNPN-SI or SOR-SNPN-SI-LS if the Nsoraf_SoR_Info service operation has returned the "ME support of SOR-SNPN-SI" indicator or "ME support of SOR-SNPN-SI-LS" indicator, respectively. The UDM can determine that the ME supports the SOR-SNPN-SI or SOR-SNPN-SI-LS if the "ME support of SOR-SNPN-SI" indicator or "ME support of SOR-SNPN-SI-LS" indicator, respectively, is stored for the UE. The procedure is triggered if: a) the UDM supports obtaining the SOR-SNPN-SI or SOR-SNPN-SI-LS from the SOR-AF, the HPLMN policy for the SOR-AF invocation is present in the UDM, and the SOR-AF provides the UDM with the SOR-SNPN-SI or the SOR-SNPN-SI-LS for a UE identified by SUPI; or b) the SOR-SNPN-SI or the SOR-SNPN-SI-LS becomes available in the UDM (i.e., retrieved from the UDR). Figure C.7.1: Procedure for configuring UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in a PLMN after registration For the steps below, security protection is described in 3GPP TS 33.501 [66]. 1) The SOR-AF to the UDM: Nudm_ParameterProvision_Update request is sent to the UDM to trigger the update of the UE with the SOR-SNPN-SI or SOR-SNPN-SI-LS. 2) The UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. The Nudm_SDM_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the HPLMN or subscribed SNPN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm_SDM_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. Upon receiving the SOR-SNPN-SI or the SOR-SNPN-SI-LS, the UDM shall include the SOR-SNPN-SI (if any), SOR-SNPN-SI-LS (if any), and 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'. NOTE 2: The UDM cannot provide the SOR-SNPN-SI, or the SOR-SNPN-SI-LS to the AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. 4) Upon receiving the steering of roaming information containing the SOR-SNPN-SI (if any), the SOR-SNPN-SI-LS (if any), and 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', the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by HPLMN, and: a) if the security check is successful, then: - the ME shall replace the credentials holder controlled prioritized list of preferred SNPNs for the selected PLMN subscription with the received credentials holder controlled prioritized list of preferred SNPNs, if any, the ME shall replace the credentials holder controlled prioritized list of GINs for the selected PLMN subscription with the received credentials holder controlled prioritized list of GINs, if any, and the ME shall delete the SNPNs identified by the credentials holder controlled prioritized list of preferred SNPNs or the SNPN(s) stored along with GIN(s) identified by the credentials holder controlled prioritized list of GINs from the list of "temporarily forbidden SNPNs" and the list of "permanently forbidden SNPNs", if they are present in these lists: and - the ME shall replace the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" for the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", if any, the ME shall replace the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" for the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", if any, and the ME shall delete the SNPNs identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or the SNPN(s) stored along with GIN(s) identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "temporarily forbidden SNPNs for access for localized services in SNPN" and the list of "permanently forbidden SNPNs for access for localized services in SNPN", if they are present in these lists. The ME shall delete the tracking area(s) included in the location validity information corresponding to an SNPN identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" from the list of "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" associated with the SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, if they are present in these lists. The ME shall delete the tracking area(s) included in the location validity information corresponding to a GIN identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" associated with an SNPN and the selected entry of the "list of subscriber data" or PLMN subscription, if the tracking area(s) in these lists is associated with the GIN. If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE: - may set the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN using credentials from a credentials holder; and - shall set the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN providing access for localized services in SNPN. If the UDM has not requested an acknowledgement from the UE then step 5 is skipped; and b) if the selected PLMN is a VPLMN, the security check is not successful and the UE is in automatic network, then - if the UE has a stored SOR-CMCI, then: - if there are ongoing PDU sessions or services, the current PLMN is considered as lowest priority and the UE shall apply the actions in clause C.4.2; - if there are no ongoing PDU sessions or services, 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.9.3, with an exception that the current PLMN is considered as lowest priority; - if the UE does not have a SOR-CMCI stored in the non-volatile memory of the ME, then: - if there are ongoing PDU sessions or services, 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 PLMN is considered as lowest priority. If the selected PLMN is a VPLMN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]); or - if there are no ongoing PDU sessions or services, 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.9.3, with an exception that the current PLMN is considered as lowest priority. Step 5 is skipped; NOTE 3: 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. 5) The AMF to the UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, 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 successful security check of the received steering of roaming information in step 2, the UDM verifies that the acknowledgement is provided by the UE. If: - the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-CMCI" indicator, otherwise the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any; - the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-SNPN-SI" indicator, otherwise the UDM shall delete the stored "ME support of SOR-SNPN-SI" indicator, if any; and - the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-SNPN-SI-LS" indicator, otherwise the UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any, If the present flow was invoked by the UDM after receiving from the SOR-AF the SOR-SNPN-SI or the SOR-SNPN-SI-LS for a UE identified by SUPI using an Nudm_ParameterProvision_Update request, and the UDM verification of the UE acknowledgement is successful, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI or the SOR-SNPN-SI-LS using Nsoraf_SoR_Info (SUPI of the UE, successful delivery); and 6) The UDM to the SOR-AF: Nsoraf_SoR_Info (SUPI of the UE, successful delivery, "ME support of SOR-SNPN-SI" indicator, if any, "ME support of SOR-SNPN-SI-LS" 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 5, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI or the SOR-SNPN-SI-LS to the UE. If the "ME support of SOR-SNPN-SI" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI" indicator. If the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator. If the selected PLMN is a VPLMN and: - the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and - upon switching to automatic network selection mode the UE remembers that it is still registered on the PLMN where the security check failure of SOR information was encountered; 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. If the selected PLMN is a VPLMN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). NOTE 4: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. C.8 Stage-2 flow for providing UE with list of preferred PLMN/access technology combinations in SNPN after registration The stage-2 flow for providing UE with the list of preferred PLMN/access technology combinations in an SNPN after registration is indicated in figure C.8.1. The selected SNPN is a non-subscribed SNPN. The AMF is located in the selected SNPN. The UDM is located in the HPLMN. The ME and the HPLMN support the SOR-SNPN-SI or SOR-SNPN-SI-LS, respectively. In this procedure, the list of preferred PLMN/access technology combinations is sent in plain text or sent within the secured packet, without the SOR-SNPN-SI. Based on HPLMN policy, if the HPLMN supports sending the list of preferred PLMN/access technology combinations in plain text or secured packet to the UE when the UE is registered to an SNPN, then the procedure is triggered: - If the UDM supports obtaining a list of preferred PLMN/access technology combinations or a secured packet from the SOR-AF, the HPLMN policy for the SOR-AF invocation is present in the UDM and the SOR-AF provides the UDM with a new list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI; or - When a new list of preferred PLMN/access technology combinations or a secured packet becomes available in the UDM (i.e., retrieved from the UDR). Figure C.8.1: Procedure for configuring UE with list of preferred PLMN/access technology combinations in an SNPN after registration For the steps below, security protection is described in 3GPP TS 33.501 [66]. 1) The SOR-AF to the UDM: Nudm_ParameterProvision_Update request is sent to the UDM to trigger the update of the UE with the new list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI. 2) The UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. The Nudm_SDM_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the HPLMN or subscribed SNPN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm_SDM_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. 4) Upon receiving the steering of roaming information, the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by HPLMN, and: a) if the security check is successful: - if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]) and the service "data download via SMS Point-to-point" is allocated and activated in the USIM Service Table (see 3GPP TS 31.102 [40]), the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41]; and - 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. If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set the "ME support of SOR-SNPN-SI" indicator to "supported". If the UDM has not requested an acknowledgement from the UE then step 5 is skipped; and b) if the security check is not successful and the UE is in automatic network selection mode, then: - if the UE has a stored SOR-CMCI, then: - if there are ongoing PDU sessions or services, the current SNPN is considered as lowest priority and the UE shall apply the actions in clause C.4.2; - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority; - if the UE does not have a SOR-CMCI stored in the non-volatile memory of the ME, then: - if there are ongoing PDU sessions or services, 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 SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority. If the UE has an established emergency PDU session then the UE shall attempt to perform the SNPN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]); or - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority. Step 5 is skipped; NOTE 1: When the UE is in the manual mode of operation or the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs, the UE stays on current chosen non-subscribed SNPN. 5) The AMF to the UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, 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 successful security check of the received steering of roaming information in step 2, the UDM verifies that the acknowledgement is provided by the UE. The UDM shall store the "ME support of SOR-SNPN-SI" indicator except if the UE supports equivalent SNPNs, the ME does not support SOR-SNPN-SI and the UE is in an equivalent SNPN of the subscribed SNPN. If the present flow was invoked by the UDM after receiving from the SOR-AF a list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI using an Nudm_ParameterProvision_Update request, and the UDM verification of the UE acknowledgement is successful, then the UDM informs the SOR-AF about successful delivery of the steering of roaming information using Nsoraf_SoR_Info (SUPI of the UE, successful delivery); and 6) The UDM to the SOR-AF: Nsoraf_SoR_Info (SUPI of the UE, successful delivery, "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 5, then the UDM informs the SOR-AF about successful delivery of the steering of roaming information to the UE. If the "ME support of SOR-SNPN-SI" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI" indicator. If: - the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and - upon switching to automatic network selection mode the UE remembers that it is still registered on non-subscribed SNPN where the security check failure of SOR information was encountered; 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 SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the UE has an established emergency PDU session then the UE shall attempt to perform the SNPN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). NOTE 2: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. Annex D (informative): Change history TSG# Tdoc SPEC VERS CR REV PHASE CAT N_VER SUBJECT comment 03.22 8.2.0 R99 Split of 03.22/R99 to 03.22 and 23.122 #6 23.122 0.0.0 R99 3.0.0 Was approved in the TSGN#6 plenary #4 N1-99573 23.102 3.0.0 001 R99 F 3.1.0 PLMN selection for GPRS mobiles Mirrored from CRA032r2 REMOVED in V3.1.1, where it is not approved by SMG2 #6 N1-99D13 23.122 3.0.0 002 R99 A 3.1.0 Correction of Figure A.2 in Annex A Mirrored from CR006r1for 23.022 #7 N1-000546 23.122 3.1.1 004 1 R99 D 3.2.0 UMTS references in 23.122 Correction of references #8 N1-000796 23.122 3.2.0 003 5 R99 F 3.3.0 Modification of PLMN Selection Procedures to support UMTS+COMPACT Network Selection WI: GSM/UMTS interworking Note As a result of two conflicting CRs N1-000796 is merged with the existing text in V.3.2.0 by the rapporteur #9 NP-000443/ N1-001020 23.122 3.3.0 009 2 R99 F 3.4.0 Clarifications of the PLMN Selection procedures for UMTS and COMPACT. 23.122 3.4.0 3.4.1 Correction of text in version3.4.0 (There was text to be deleted in clause 4.4.3.2.1 bullet point 2) 23.Oct.2000 Implementation correction 23.122 3.4.1 3.4.2 Correction of a systematic search for "TS" and replace it with "3GPP TS" has gone wrong as much more than the TSs for Technical Specifications have been changed also. 1 Nov..2000 Implementation correction #10 NP-000674/ N1-001415 23.122 3.4.2 010 1 R99 F 3.5.0 Correction of terminology "In UMTS", "In GSM" Cat F/ WI=TEI #10 NP-000671/ N1-001236 23.122 3.4.2 012 R99 F 3.5.0 Restoration of figure A.1 Cat F/ WI=GSM - UMTS Interworking #10 NP-000671/ N1-001237 23.122 3.4.2 013 R99 F 3.5.0 Alignment of figure 2a with PLMN selection for UMTS Cat F/ WI=GSM - UMTS Interworking #11 NP-010207/ N1-010472 23.122 3.5.0 014 3 R99 F 3.6.0 Clarification of the PLMN selection for UMTS regarding high quality signal GSM - UMTS Interworking #11 NP-010168/ N1-010224 23.122 3.5.0 016 1 R99 F 3.6.0 Roaming restrictions for GPRS service GSM - UMTS Interworking #11 NP-010205/ N1-010334 23.122 3.5.0 017 R99 F 3.6.0 remove use of GSM as default access technology in PLMN search T.E.I #11 NP-01089/ N1-010443 23.122 3.5.0 018 R99 F 3.6.0 Requirement of priority on High Quality Signal cell concerning Acceptable cell (for limited service as emergency call) T.E.I #11 NP-010186/ N1-010489 23.122 3.5.0 019 4 R99 F 3.6.0 Clarifications to PLMN search T.E.I #11 NP-010186/ N1-010490 23.122 3.5.0 020 1 R99 F 3.6.0 Clarifications to PLMN search T.E.I #11 NP-010180 23.122 3.5.0 022 1 R99 F 3.6.0 Equivalent handling of PLMNs with different PLMN codes GSM - UMTS Interworking #11 3.6.0 4.0.0 Upgraded to Release 4. #12 NP-010352 23.122 4.0.0 024 1 Rel-4 A 4.1.0 Stored list of equivalent PLMNs and error/abnormal cases GSM-UMTS INTERWORKING #12 NP-010276 23.122 4.0.0 027 1 Rel-4 A 4.1.0 Corrections and clarifications to PLMN Selection GSM-UMTS INTERWORKING #12 NP-010275 23.122 4.0.0 030 3 Rel-4 A 4.1.0 Partial Roaming – restriction by location area TEI #12 NP-010276 23.122 4.0.0 032 Rel-4 A 4.1.0 Removal of 'Requirement of priority on High Quality Signal cell concerning Acceptable cell TEI #12 NP-010276 23.122 4.0.0 034 Rel-4 A 4.1.0 Alignment with stage 1 specification on PLMN background search TEI NP-16 NP-020243 23.122 4.1.0 048 Rel-5 F 5.0.0 Role of the equivalent PLMNs list in the PLMN user reselection TEI5 NP-17 NP-020369 23.122 5.0.0 051 Rel-5 A 5.1.0 Removal of CBQ2 COMPACT NP-17 NP-020383 23.122 5.0.0 052 1 Rel-5 F 5.1.0 Applicability of the lists of "forbidden LAs" TEI5 NP-17 NP-020367 23.122 5.0.0 055 Rel-5 A 5.1.0 Routing Area Update at network change TEI NP-18 NP-020549 23.122 5.1.0 058 Rel-5 A 5.2.0 Correction of references TEI 5.1.0 Rel-5 5.2.0 Additional clenup done to references by ETSI/MCC NP-21 NP-030405 23.122 5.2.0 061 Rel-5 A 5.3.0 Removal of RPLMNAcT field TEI NP-23 NP-040037 23.122 5.3.0 067 1 Rel-6 F 6.0.0 Definition of MS idle mode TEI6 NP-23 NP-040037 23.122 5.3.0 068 Rel-6 F 6.0.0 Usage of HPLMNAcT by the UE TEI6 NP-24 NP-040202 23.122 6.0.0 069 5 Rel-6 F 6.1.0 Clarification on the use of the RAT during background scanning. TEI6 NP-24 NP-040202 23.122 6.0.0 071 1 Rel-6 F 6.1.0 Role of ePLMN list in manual PLMN selection mode TEI6 NP-24 NP-040202 23.122 6.0.0 072 1 Rel-6 F 6.1.0 Roaming not allowed for GPRS update state TEI6 NP-24 NP-040202 23.122 6.0.0 073 Rel-6 D 6.1.0 Data field -> data file TEI6 NP-25 NP-040375 23.122 6.1.0 76 2 Rel-6 B 6.2.0 Clarification on the registered PLMN for UEs that support network sharing in a shared network NTShar NP-25 NP-040378 23.122 6.1.0 77 1 Rel-6 F 6.2.0 Correction of definitions of PLMNs in the same country TEI6 NP-26 NP-040513 23.122 6.2.0 086 1 Rel-6 B 6.3.0 Clarifiaction of PLMN selection in shared networks NTShar NP-26 NP-040514 23.122 6.2.0 084 1 Rel-6 F 6.3.0 Clarification on the use of the RAT during background scanning TEI6 NP-26 NP-040516 23.122 6.2.0 082 7 Rel-7 C 7.0.0 Support of multiple HPLMN codes TEI7 NP-27 NP-050083 23.122 7.0.0 089 Rel-7 A 7.1.0 Addition of domain specific access control decscription ACBOP NP-27 NP-050086 23.122 7.0.0 087 1 Rel-7 F 7.1.0 Minor Clarifications to EHPLMN handling TEI7 CP-28 CP-050068 23.122 7.1.0 91 Rel-7 A 7.2.0 Correction of the PLMN Selection State diagram (automatic mode) TEI6 CP-29 CP-050366 23.122 7.2.0 93 1 Rel-7 C 7.3.0 Enhancement of the EHPLMN feature to allow load balancing TEI7 CP-31 CP-060126 23.122 7.3.0 0094 - Rel-7 F 7.4.0 EPLMN list is not invalid on receipt of reject cause values #12 and #15 TEI7 CP-31 CP-060126 23.122 7.3.0 0095 - Rel-7 F 7.4.0 EHPLMN in automatic network selection mode TEI7 CP-31 CP-060175 23.122 7.3.0 0096 4 Rel-7 C 7.4.0 First higher priority PLMN scan in VPLMN TEI7 CP-32 CP-060359 23.122 7.4.0 0098 2 Rel-7 B 7.5.0 ME capability for Network Selection TEI7 CP-33 CP-060460 23.122 7.5.0 0099 1 Rel-7 C 7.6.0 Manual PLMN selection power-on NSP-CR CP-34 CP-060668 23.122 7.6.0 0101 1 Rel-7 C 7.7.0 Presentation of EHPLMN NSP-CR CP-34 CP-060668 23.122 7.6.0 0102 2 Rel-7 C 7.7.0 Presentation of Additional Information in Manual Mode NSP-CR CP-34 CP-060670 23.122 7.6.0 0103 1 Rel-7 F 7.7.0 Correction to the definition of national roaming and international roaming to include the EHPLMN TEI7 CP-34 CP-060670 23.122 7.6.0 0104 - Rel-7 F 7.7.0 Correction of the PLMN Selection state diagram (automatic mode) TEI7 CP-35 CP-070152 23.122 7.7.0 0111 3 Rel-7 B 7.8.0 Last RPLMN NSP-CR CP-35 CP-070152 23.122 7.7.0 0113 1 Rel-7 B 7.8.0 Optional network selection mode at switch-on NSP-CR CP-35 CP-070173 23.122 7.7.0 0106 2 Rel-7 C 7.8.0 Pingpong avoidance on PLMN change for search for higher priority PLMNs TEI7 CP-36 CP-070477 23.122 7.8.0 0114 4 Rel-7 B 7.9.0 PLMN selection for steering of roaming NSP-CR CP-37 CP-070597 23.122 7.9.0 0115 1 REl-7 C 7.10.0 Steering of Roaming procedure NSP-CR CP-38 CP-070802 23.122 7.10.0 0117 Rel-7 F 7.11.0 Single EHPLMN Display Name in Manual Mode TEI7 CP-38 CP-070813 23.122 7.11.0 0118 1 Rel-8 B 8.0.0 PPACR CR to 23.122 PPACR-CT1 CP-39 CP-080125 23.122 8.0.0 0120 1 Rel-8 A 8.1.0 Inclusion of EHPLMN in the optimisation for automatic network selection NSP-CR CP-40 CP-080361 23.122 8.1.0 0119 3 Rel-8 B 8.2.0 PLMN Selection on receipt of GAN cause Location not allowed TEI8 CP-41 CP-080536 23.122 8.2.0 0121 0 Rel-8 F 8.3.0 Clarifications for RAT usage in manual network selection mode TEI8 CP-41 CP-080536 23.122 8.2.0 0122 1 Rel-8 F 8.3.0 Clarification on MS behavior further to LU Reject causes #13 and #15 TEI8 CP-42 CP-080866 23.122 8.3.0 0124 1 Rel-8 B 8.4.0 Multi system PLMN selection SAES CP-42 CP-080860 23.122 8.3.0 0125 1 Rel-8 B 8.4.0 CR on description of PPAC PPACR-CT1 CP-42 CP-080866 23.122 8.3.0 0126 1 Rel-8 B 8.4.0 3GPP2 system selection SAES CP-42 CP-080966 23.122 8.3.0 0128 2 Rel-8 B 8.4.0 CSG selection – NAS aspects HomeNB-3G, HomeNB-LTE CP-42 23.122 8.3.0 Rel-8 8.4.0 Editorial cleanup by MCC CP-43 CP-090157 23.122 8.4.0 0129 1 Rel-8 8.5.0 Correction on CSG related NAS requirement HomeNB-LTE, HomeNB-3G CP-43 CP-090222 23.122 8.4.0 0130 2 Rel-8 8.5.0 CSG selection process in idle mode HomeNB-LTE, HomeNB-3G CP-43 CP-090157 23.122 8.4.0 0132 1 Rel-8 8.5.0 Introduction of cause#25 handling in LR state diagram HomeNB-3G CP-44 CP-090413 23.122 8.5.0 0131 1 Rel-8 F 8.6.0 Addition of missing requirements for tracking area updating SAES CP-45 CP-090679 23.122 8.6.0 0133 2 Rel-8 F 8.7.0 RAT selection when "HPLMN selector with access technology" data file is missing in the SIM or "PLMN selector" data file is used TEI8 CP-45 CP-090694 23.122 8.7.0 0139 1 Rel-9 B 9.0.0 Introduction of Operator CSG List EHNB-CT1 CP-45 CP-090694 23.122 8.7.0 0140 1 Rel-9 F 9.0.0 Manual CSG selection across PLMN EHNB-CT1 CP-46 CP-090930 23.122 9.0.0 0142 2 Rel-9 F 9.1.0 PLMN selection during emergency attach IMS_EMER_GPRS_EPS CP-46 CP-090935 23.122 9.0.0 0143 Rel-9 F 9.1.0 Correct definitions related to CSG EHNB-CT1 CP-46 CP-090922 23.122 9.0.0 0146 Rel-9 F 9.1.0 Correction of condition for tracking area updating TEI9 CP-46 CP-090900 23.122 9.0.0 0148 Rel-9 A 9.1.0 Adding missing requirements for PLMN selection in EPS SAES CP-47 CP-100148 23.122 9.1.0 0144 4 Rel-9 F 9.2.0 Support for Operator CSG List EHNB-CT1 CP-47 CP-100144 23.122 9.1.0 0149 1 Rel-9 F 9.2.0 Manual CSG selection during emergency IMS_EMER_GPRS_EPS CP-47 CP-100130 23.122 9.1.0 0151 1 Rel-9 A 9.2.0 Clarification to LR state when rejected for cause value #25. HomeNB-LTE, HomeNB-3G CP-47 CP-100148 23.122 9.1.0 0152 1 Rel-9 F 9.2.0 Clarification to the LR Process States and Allowed Actions EHNB-CT1 CP-47 CP-100130 23.122 9.1.0 0156 1 Rel-9 A 9.2.0 Clarify manual CSG selection across technologies HomeNB-LTE, HomeNB-3G CP-47 CP-100144 23.122 9.1.0 0160 1 Rel-9 F 9.2.0 Correct definition of "acceptable cell" to include criteria for E-UTRAN (S1-mode) IMS_EMER_GPRS_EPS CP-47 CP-100148 23.122 9.1.0 0161 Rel-9 F 9.2.0 Correction to the manual CSG ID selection in Release 9 EHNB-CT1 CP-47 CP-100134 23.122 9.1.0 0162 1 Rel-9 F 9.2.0 Corrections/clarifications for equivalent and forbidden PLMN handling, state descriptions and overall idle mode procedure TEI9 CP-48 CP-100362 23.122 9.2.0 0165 Rel-9 F 9.3.0 Deleting editor's note related manual CSG selection EHNB-CT1 CP-48 CP-100339 23.122 9.2.0 0168 1 Rel-9 A 9.3.0 Reference Update SAES CP-48 CP-100370 23.122 9.3.0 0166 1 Rel-10 F 10.0.0 Manual CSG Selection using CSG Identities not in Allowed CSG List and Operator CSG List TEI10 CP-49 CP-100521 23.122 10.0.0 0171 2 Rel-10 A 10.1.0 Definition of CSG whitelist EHNB-CT1 CP-49 CP-100498 23.122 10.0.0 0176 1 Rel-10 A 10.1.0 HeNB name for manual CSG selection HomeNB-LTE, HomeNB-3G CP-49 CP-100518 23.122 10.0.0 0178 1 Rel-10 F 10.1.0 Correction to Initiation of Location Registration TEI10 CP-49 CP-100518 23.122 10.0.0 0179 Rel-10 F 10.1.0 Adding Reference for PLMN selection TEI10 CP-50 CP-100748 23.122 10.1.0 0182 3 Rel-10 A 10.2.0 Support for displaying only CSGs in the Operator CSG List for manual selection EHNB-CT1 CP-50 CP-100747 23.122 10.1.0 0184 1 Rel-10 A 10.2.0 Inter PLMN mobility for emergency bearer services IMS_EMER_GPRS_EPS CP-50 CP-100747 23.122 10.1.0 0186 2 Rel-10 A 10.2.0 Handling forbidden PLMN list for emergency bearer services IMS_EMER_GPRS_EPS CP-50 CP-100747 23.122 10.1.0 0188 1 Rel-10 A 10.2.0 Handling of equivalent PLMN list when attached for emergency bearer services only IMS_EMER_GPRS_EPS CP-50 CP-100887 23.122 10.1.0 0192 3 Rel-10 C 10.2.0 MTC/Low-Priority PLMN Reselection Timer value NIMTC CP-50 CP-100748 23.122 10.1.0 0195 Rel-10 A 10.2.0 Removing the CSG ID from ACL and OCL simutaneously EHNB-CT1 CP-50 CP-100664 23.122 10.1.0 0190 3 Rel-10 F 10.2.0 Location Registration when entering new PLMN NIMTC, TEI10 CP-51 CP-110193 23.122 10.2.0 0196 1 Rel-10 F 10.3.0 UEs configured with long minimum periodic PLMN search time limit NIMTC CP-51 CP-110193 23.122 10.2.0 0198 5 Rel-10 B 10.3.0 EAB support NIMTC CP-52 CP-110446 23.122 10.3.0 0205 1 Rel-10 A 10.4.0 Aligning NAS and AS on CSG HomeNB-3G, HomeNB-LTE CP-52 CP-110462 23.122 10.3.0 0206 1 Rel-10 B 10.4.0 Reference to NAS configuration in USIM NIMTC CP-53 CP-110680 23.122 10.4.0 0210 1 Rel-10 F 10.5.0 Correction to EAB NIMTC CP-53 CP-110695 23.122 10.5.0 0207 4 Rel-11 B 11.0.0 Support for multiple MCC countries TEI11 CP-53 CP-110737 23.122 10.5.0 0208 2 Rel-11 B 11.0.0 EAB references SIMTC-RAN_OC CP-54 CP-110888 23.122 11.0.0 0211 1 Rel-11 F 11.1.0 Clarification to the manual PLMN selection procedure SAES2 CP-56 CP-120309 23.122 11.1.0 0212 Rel-11 F 11.2.0 Correction on location registration task state TEI11 CP-56 CP-120315 23.122 11.1.0 0213 Rel-11 F 11.2.0 EAB configuration SIMTC-RAN_OC CP-56 CP-120315 23.122 11.1.0 0214 1 Rel-11 F 11.2.0 UE configured for EAB accessing with access class 11-15 or initiating emergency call SIMTC-RAN_OC CP-56 CP-120315 23.122 11.1.0 0215 Rel-11 F 11.2.0 Applicability of EAB when the UE is responding to paging SIMTC-RAN_OC CP-56 CP-120309 23.122 11.1.0 0217 Rel-11 F 11.2.0 Handling of forbidden PLMNs for GPRS service list TEI11 CP-57 CP-120595 23.122 11.2.0 0216 4 Rel-11 F 11.3.0 PLMN selection timer for E-UTRA disabling SAES2, SAES2-CSFB CP-57 CP-120589 23.122 11.2.0 0219 2 Rel-11 F 11.3.0 EAB overriding handling SIMTC-Reach CP-57 CP-120584 23.122 11.2.0 0220 Rel-11 F 11.3.0 Removing NMO III TEI11 CP-58 CP-120794 23.122 11.3.0 0218 2 Rel-11 F 11.4.0 Correction on cause #2 in response to an LR TEI11 CP-58 CP-120807 23.122 11.3.0 0221 3 Rel-11 F 11.4.0 E-UTRA disabling stored information deletion criteria correction SAES2 CP-58 CP-120794 23.122 11.3.0 0222 Rel-11 F 11.4.0 Corrections to steps in clause 5 related to CSG selection TEI11 CP-58 CP-120797 23.122 11.3.0 0223 3 Rel-11 B 11.4.0 Access control and DSAC for shared networks GDSAC, FULL_MOCN-GERAN CP-58 CP-120794 23.122 11.3.0 0224 1 Rel-11 F 11.4.0 Ignoring Forbidden Lists During Manual CSG Selection TEI11 CP-58 CP-120794 23.122 11.3.0 0225 3 Rel-11 F 11.4.0 HPLMN or RPLMN selection clarification TEI11 CP-58 CP-120807 23.122 11.3.0 0226 1 Rel-11 F 11.4.0 Clean-up the confusion between the term update state and update status SAES2, TEI11 CP-59 CP-130129 23.122 11.4.0 0229 2 Rel-12 F 12.0.0 EHPLMN selection clarification TEI12 CP-60 CP-130264 23.122 12.0.0 0230 2 Rel-12 F 12.1.0 Corrections to manual CSG selection TEI12 CP-60 CP-130264 23.122 12.0.0 0231 2 Rel-12 F 12.1.0 GERAN Iu mode TEI12 CP-60 CP-130264 23.122 12.0.0 0232 1 Rel-12 F 12.1.0 Missing reference for GERAN specification TEI12 CP-61 CP-130510 23.122 12.1.0 0234 1 Rel-12 F 12.2.0 Last PLMN selection mode at switch on TEI12 CP-61 CP-130510 23.122 12.1.0 0235 1 Rel-12 F 12.2.0 Switch off after manual CSG selection in a PLMN different from the RPLMN TEI12 CP-61 CP-130510 23.122 12.1.0 0237 Rel-12 F 12.2.0 Clarifying requirement for steering of roaming TEI12 CP-61 CP-130510 23.122 12.1.0 0238 Rel-12 F 12.2.0 Handling the received error cause #25 TEI12 CP-62 CP-130762 23.122 12.2.0 0236 4 Rel-12 C 12.3.0 Fast higher priority PLMN search upon entering VPLMN TEI12 CP-62 CP-130762 23.122 12.2.0 0241 1 Rel-12 F 12.3.0 Terminology Alignment for name of forbidden lists between Stage 2 and Stage 3 TEI12 CP-62 CP-130762 23.122 12.2.0 0242 Rel-12 F 12.3.0 Duplicate entries in ACL and OCL when forming CSG Whitelist TEI12 CP-62 CP-130762 23.122 12.2.0 0243 4 Rel-12 F 12.3.0 User initiated PLMN selection after manual CSG selection and registration on a CSG cell. TEI12 CP-62 CP-130762 23.122 12.2.0 0244 Rel-12 D 12.3.0 Clean-up of references TEI12 CP-62 CP-130762 23.122 12.2.0 0246 Rel-12 F 12.3.0 HPLMN criteria matching correction TEI12 CP-63 CP-140144 23.122 12.3.0 0250 2 Rel-12 F 12.4.0 Incorrect combination of stored duplicate of RPLMN and current PLMN selection mode due to multiple CSG selections TEI12 CP-63 CP-140144 23.122 12.3.0 0251 1 Rel-12 F 12.4.0 No CSG cell and re-enable E-UTRA TEI12 CP-64 CP-140331 23.122 12.4.0 0249 4 Rel-12 F 12.5.0 PLMN selection timer for enhanced EMM cause #15 TEI12 CP-64 CP-140323 23.122 12.4.0 0253 1 Rel-12 F 12.5.0 Updates due to power saving mode MTCe-UEPCOP-CT CP-64 CP-140331 23.122 12.4.0 0255 Rel-12 F 12.5.0 Clarification regarding cause #25 received by the UE TEI12 CP-64 CP-140328 23.122 12.4.0 0257 2 Rel-12 F 12.5.0 Triggering a CS call from the selected CSG SAES3-CSFB CP-66 CP-140862 23.122 12.5.0 0262 5 Rel-13 F 13.0.0 Correct Automatic Network Selection Mode Procedure for UE supporting E-UTRAN SAES4 CP-67 CP-150205 23.122 13.0.0 0272 2 Rel-13 A 13.1.0 Clarification on limited service state ProSe-CT CP-67 CP-150206 23.122 13.0.0 0273 2 Rel-13 A 13.1.0 Clarification on limited service state TEI12 CP-68 CP-150316 23.122 13.1.0 0269 8 Rel-13 A 13.2.0 PLMN selection triggered by ProSe direct communication ProSe-CT CP-68 CP-150323 23.122 13.1.0 0274 Rel-13 F 13.2.0 Correct Automatic Network Selection Mode Procedure for UE supporting E-UTRA SAES4 CP-68 CP-150316 23.122 13.1.0 0280 Rel-13 A 13.2.0 Correction of limited service state for ProSe direct communication ProSe-CT CP-69 CP-150534 23.122 13.2.0 0278 3 Rel-13 B 13.3.0 Introduction of ACDC for access control ACDC-CT CP-69 CP-150517 23.122 13.2.0 0282 1 Rel-13 A 13.3.0 Correction of limited service state for ProSe direct communication ProSe-CT CP-69 CP-150529 23.122 13.2.0 0283 1 Rel-13 F 13.3.0 Inconsistency where PLMN selection in automatic mode is performed while GPRS services are not available TEI13 CP-71 CP-160157 23.122 13.3.0 0289 1 Rel-13 F 13.4.0 ProSe direct discovery for public safery use in limited service state eProSe-Ext-CT CP-72 CP-160309 23.122 13.4.0 0293 2 Rel-13 C 13.5.0 Disabling emergency calls for NB-IoT devices in limited service state CIoT-CT CP-72 CP-160318 23.122 13.4.0 0295 1 Rel-13 F 13.5.0 Handling of PLMN background scan during PSM TEI13 CP-72 CP-160302 23.122 13.4.0 0300 1 Rel-13 A 13.5.0 PLMN selection triggered by ProSe communication in manually selected CSG cell ProSe-CT, TEI12 CP-72 CP-160309 23.122 13.4.0 0292 7 Rel-13 C 13.5.0 Extend search cycle for higher priority PLMN CIoT-CT CP-72 CP-160318 23.122 13.4.0 0297 2 Rel-13 B 13.5.0 Addition of EC-GSM-IoT access to PLMN selection TEI13, CIoT_EC_GSM CP-72 CP-160309 23.122 13.4.0 0298 3 Rel-13 B 13.5.0 PLMN selection when the network and UE capabilities for CIoT do not match CIoT-CT Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2016-09 CP-73 CP-160486 0302 F Addition of NB-S1 mode to PLMN selection 13.6.0 2016-09 CP-73 CP-160487 0304 F Corrections due to added CIoT requirements 13.6.0 2016-09 CP-73 CP-160519 0301 1 F Minor corrections for EC GPRS 14.0.0 2016-09 CP-73 CP-160512 0303 1 B PLMN selection for eCall over IMS 14.0.0 2016-12 CP-74 CP-160739 0305 F MS in eCall only mode 14.1.0 2016-12 CP-74 CP-160739 0306 1 B Update of requirements on limited service state for MS in eCall only mode 14.1.0 2016-12 CP-74 CP-160753 0308 1 F Skip ACDC for emergency call, MO MMTEL voice/video and MO SMSoIP 14.1.0 2016-12 CP-74 CP-160754 0310 1 F V2X communication over PC5 is used for UEs in limited service state 14.1.0 2017-03 CP-75 CP-170138 0315 F PLMN selection triggered by V2X communication over PC5 14.2.0 2017-06 CP-76 CP-171092 0321 F Correction in handling of cause value "GPRS services not allowed in this PLMN" or "EPS services not allowed in this PLMN" 14.3.0 2017-06 CP-76 CP-171094 0318 1 F Adding a NOTE for HPLMN and RPLMN selection 15.0.0 2017-09 CP-77 CP-172122 0322 1 F Clarification to network selection procedures 15.1.0 2017-09 CP-77 CP-172132 0326 A Corrections to handling of EFFPLMN file in the SIM and of "forbidden PLMNs for GPRS service" list 15.1.0 2017-12 CP-78 CP-173067 0327 A Max length of timer TE for IoT devices 15.2.0 2017-12 CP-78 CP-173079 0328 D Editorial correction: wrong color 15.2.0 2017-12 CP-78 CP-173079 0329 F Correction for classification of EC-GSM-IoT high quality signal 15.2.0 2017-12 CP-78 CP-173079 0332 1 F Allow exiting manual PLMN selection mode due to emergency call 15.2.0 2018-03 CP-79 CP-180076 0333 4 B Addition of NG-RAN 15.3.0 2018-03 CP-79 CP-180089 0334 1 F Informing user of exit from manual network selection mode 15.3.0 2018-03 CP-79 CP-180076 0335 1 B Addition of 5GS forbidden TA lists 15.3.0 2018-03 CP-79 CP-180076 0337 1 B N1 mode disabling - use of PLMN id in subsequent PLMN selections 15.3.0 2018-03 CP-79 CP-180076 0339 2 B 5GS forbidden TA for regional provision of service 15.3.0 2018-03 CP-79 CP-180157 0340 5 B Stage 2 solution of Steering Of Roaming (SOR) 15.3.0 2018-06 CP-80 CP-181057 0343 1 F Terminology correction in handling of PLMNs where N1 mode was disabled 15.4.0 2018-06 CP-80 CP-181057 0344 B Adding support for eCall over IMS in 5GS 15.4.0 2018-06 CP-80 CP-181057 0345 3 B Alignment: replacing the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list 15.4.0 2018-06 CP-80 CP-181058 0347 6 B Updates to Stage 2 solution of Steering Of Roaming (SOR) 15.4.0 2018-06 CP-80 CP-181058 0348 1 F Disabling and re-enabling capabilities in the NAS layer 15.4.0 2018-06 CP-80 CP-181076 0349 2 B PLMN selection for disabling NB-IoT 15.4.0 2018-06 CP-80 CP-181058 0350 1 B Updating terms in definitions and abbreviations due to 5GS 15.4.0 2018-06 CP-80 CP-181053 0352 A Forbidden PLMN operation for cause value "Requested service option not authorized in this PLMN" 15.4.0 2018-06 CP-80 CP-181058 0356 1 C Updates due to network sharing for 5GS 15.4.0 2018-09 CP-81 CP-182128 0357 2 F Introduce 5GS registration procedure 15.5.0 2018-09 CP-81 CP-182106 0358 4 B Updates to Stage 2 solution of Steering Of Roaming (SOR) 15.5.0 2018-09 CP-81 CP-182128 0359 2 F Unclear how to derive PLMN ID from broadcast in 3G, 4G, and 5G 15.5.0 2018-09 CP-81 CP-182158 0360 C Per RAT higher priority PLMN search timer T for UEs supporting IoT and non IoT RATs 15.5.0 2018-09 CP-81 CP-182158 0361 F Alignment on handling of forbidden LAI/TAI list 15.5.0 2018-09 CP-81 CP-182128 0364 1 B Cause #15 has been successfully used for releases. 15.5.0 2018-09 CP-81 CP-182128 0365 7 B Aligning SOR stage-2 flow as per SA3 agreements and other editorials 15.5.0 2018-09 CP-81 CP-182106 0366 3 F Steering of Roaming for IMS emergency sessions and correction for NAS Transport for SOR 15.5.0 2018-09 CP-81 CP-182128 0367 2 F PLMN selection when UE's N1 mode capability is disabled per access type 15.5.0 2018-12 CP-82 CP-183030 0368 F Correction to Nudm_SDM_UpdateNotification service operation name 15.6.0 2018-12 CP-82 CP-183134 0369 2 F Correction for sending of Nudm_SDM_info 15.6.0 2018-12 CP-82 CP-183030 0370 3 F Updates on steering of roaming call flow 15.6.0 2018-12 CP-82 CP-183030 0371 F Corrections to SoR procedure after registration 15.6.0 2018-12 CP-82 CP-183076 0372 1 F Correction of requirements for the extension of the "forbidden PLMNs" list 15.6.0 2018-12 CP-82 CP-183030 0373 3 F Correction to location registration for N1 mode 15.6.0 2018-12 CP-82 CP-183076 0375 1 F Correction to handling of cause #15 15.6.0 2018-12 CP-82 CP-183030 0377 1 F VPLMN AMF behavior clarification. 15.6.0 2018-12 CP-82 CP-183030 0378 1 F SOR stage-2 requirements 15.6.0 2018-12 CP-82 CP-183030 0381 1 F Resolving inconsistencies in terminology 15.6.0 2018-12 CP-82 CP-183030 0382 F Clarification on mandatory conditions and INACTIVE state. 15.6.0 2018-12 CP-82 CP-183030 0383 1 F Managing OPLMN list 15.6.0 2018-12 CP-82 CP-183077 0374 1 C Delaying periodic higher priority PLMN searches when receiving eMBMS service in idle mode 16.0.0 2019-03 CP-83 CP-190082 0384 4 A Correct procedure for SOR using secured packet over NAS after receiving REFRESH 16.1.0 2019-03 CP-83 CP-190082 0386 1 A Correct procedure for identificating the PLMN to which a NR cell belongs 16.1.0 2019-03 CP-83 CP-190082 0390 1 A Correction of text - SOR procedure 16.1.0 2019-03 CP-83 CP-190082 0392 A UE behaviour in connected mode when receiving SOR info in a secured packet 16.1.0 2019-03 CP-83 CP-190101 0393 F Missing references to 24.501 16.1.0 2019-03 CP-83 CP-190082 0395 1 A Inhibition of NAS signalling local release upon receiving SoR information during emergency services 16.1.0 2019-03 CP-83 CP-190101 0398 2 F Adding clarification on CN Type 16.1.0 2019-03 CP-83 CP-190082 0400 2 A Providing SoR information due to mobility registration update 16.1.0 2019-03 CP-83 CP-190082 0402 1 A Correction to condition when list of PLMNs where registration was aborted due to SOR is deleted 16.1.0 2019-03 CP-83 CP-190202 0404 2 Idle mode procedures for access to restricted local operator services 16.1.0 2019-03 CP-83 CP-190082 0407 1 A Clarification and resolving editors notes in SOR procedure. 16.1.0 2019-03 CP-83 CP-190108 0408 F Clause correction. 16.1.0 2019-03 CP-83 CP-190108 0409 1 F Consideration of WB-S1/CE mode in the PLMN selection procedure 16.1.0 2019-03 CP-83 CP-190202 0410 2 B Support of restricted local operator services for UEs in limited service state 16.1.0 2019-03 CP-83 CP-190082 0412 2 A Mandating UE sending registration complete for SOR 16.1.0 2019-06 CP-84 CP-191148 0403 2 B CAG selection 16.2.0 2019-06 CP-84 CP-191148 0413 2 B SNPN selection - new clauses 16.2.0 2019-06 CP-84 CP-191148 0414 3 B SNPN selection - update of existing clauses 16.2.0 2019-06 CP-84 CP-191144 0415 2 B Configuration of RLOS preferred PLMN list 16.2.0 2019-06 CP-84 CP-191131 0418 1 F Add MICO requirements to the clause on "No suitable cell" 16.2.0 2019-06 CP-84 CP-191147 0419 1 F Adding "limited service state" as a definition 16.2.0 2019-06 CP-84 CP-191131 0420 1 F E-UTRA access in N1 mode 16.2.0 2019-06 CP-84 CP-191128 0421 1 B PLMN selection based on Preferred CIoT Network Behavior 16.2.0 2019-06 CP-84 CP-191144 0424 1 B Additional updates to Network Selection procedure for access to RLOS 16.2.0 2019-06 CP-84 CP-191128 0425 1 B PLMN selection for WB-N1 UEs operating in CE mode 16.2.0 2019-06 CP-84 CP-191144 0426 2 F NO Service and RLOS 16.2.0 2019-06 CP-84 CP-191131 0427 4 F Managing OPLMN list 16.2.0 2019-06 CP-84 CP-191144 0429 1 B Manual PLMN selection for RLOS 16.2.0 2019-06 CP-84 CP-191131 0431 1 F Dynamic generation of SOR Information 16.2.0 2019-06 CP-84 CP-191131 0432 1 F Emergency service handling for SOR 16.2.0 2019-06 CP-84 CP-191131 0433 F Scope update for RRC inactive 16.2.0 2019-09 CP-85 CP-192072 0435 3 F Corrections for CAG selection 16.3.0 2019-09 CP-85 CP-192072 0436 1 F Missing SNPN terms 16.3.0 2019-09 CP-85 CP-192072 0437 1 F Corrections for SNPN selection 16.3.0 2019-09 CP-85 CP-192072 0438 1 F Lists of temporarily and permanently forbidden SNPNs 16.3.0 2019-09 CP-85 CP-192072 0439 2 F "5GS forbidden tracking areas for regional provision of service" and MS operating in SNPN access mode 16.3.0 2019-09 CP-85 CP-192055 0440 4 F Interactions between SOR-AF and other core network entities 16.3.0 2019-09 CP-85 CP-192055 0441 F Clarification of possible PLMN/RAT selection due to cause value#15 16.3.0 2019-09 CP-85 CP-192071 0442 3 F eDRX/relaxed monitoring HPLMN scan conflicts 16.3.0 2019-09 CP-85 CP-192055 0444 1 F Handling of SOR failure encountered in manual mode of operation 16.3.0 2019-09 CP-85 CP-192072 0446 1 F Addition of unified access control configuration to the "list of subscriber data" for access to SNPNs 16.3.0 2019-09 CP-85 CP-192055 0449 1 F OPLMN list handling 16.3.0 2019-12 CP-86 CP-193092 0445 2 F Clarification on sending of REGISTRATION COMPLETE message for SOR during registration 16.4.0 2019-12 CP-86 CP-193092 0448 2 F Periodic location registration for 5GS operation 16.4.0 2019-12 CP-86 CP-193112 0451 3 B RLOS conditions for LR 16.4.0 2019-12 CP-86 CP-193117 0453 1 F SNPN and credentials of AKA based authentication 16.4.0 2019-12 CP-86 CP-193117 0454 1 F "5GS forbidden tracking areas for roaming" and MS operating in SNPN access mode 16.4.0 2019-12 CP-86 CP-193092 0455 F Forbidden PLMNs related updates 16.4.0 2019-12 CP-86 CP-193092 0456 F Corrections to SOR procedures 16.4.0 2019-12 CP-86 CP-193117 0458 F Manual CAG selection not allowed during emergency PDU session. 16.4.0 2019-12 CP-86 CP-193117 0459 2 F Handling of the forbidden TAI list for regional provision of service and forbidden SNPN lists when the SIM is removed in case of AKA-based SNPN 16.4.0 2019-12 CP-86 CP-193117 0460 2 F IMSI-based SUPI in an SNPN and impact to the "list of subscriber data" 16.4.0 2019-12 CP-86 CP-193117 0461 1 F No suitable cell in an SNPN 16.4.0 2019-12 CP-86 CP-193117 0462 1 F Resolution of editor's notes on states, figures and tables for SNPN 16.4.0 2019-12 CP-86 CP-193092 0465 4 F Acquiring user location information for SOR 16.4.0 2019-12 CP-86 CP-193117 0467 C Handling of multiple entries with same SNPNt 16.4.0 2019-12 CP-86 CP-193117 0468 F Definitions and abbreviations update for SNPN Access Technology and other correction 16.4.0 2019-12 CP-86 CP-193117 0469 F Missing condition for entering limited service in SNPN access mode 16.4.0 2019-12 CP-86 CP-193114 0470 F Handling of CSG selection mode 16.4.0 2019-12 CP-86 CP-193092 0474 F Adding definition for SoR-AF function 16.4.0 2019-12 CP-86 CP-193099 0475 2 F SOR - adding a reference to OTAFspecification 16.4.0 2019-12 CP-86 CP-193117 0477 1 F NAS providing AS with a "CAG information list" 16.4.0 2019-12 CP-86 CP-193117 0478 1 F Clarification on figures for PLMN selection 16.4.0 2019-12 CP-86 CP-193092 0479 2 F SOR call flow corrections in 23.122 16.4.0 2020-03 CP-87e CP-200110 0482 F Streamlining RAT's that can be scanned after E-UTRAN disable due to no voice service 16.5.0 2020-03 CP-87e CP-200110 0483 F Emergency service missing condition for performing registration update 16.5.0 2020-03 CP-87e CP-200110 0484 2 F Clarification of forbidden PLMNs list 16.5.0 2020-03 CP-87e CP-200094 0485 3 F Update of steering of roaming information for different registration types 16.5.0 2020-03 CP-87e CP-200110 0486 1 F Usage of SoR-AF function 16.5.0 2020-03 CP-87e CP-200110 0488 4 F Correction to handling of a PDU session for emergency service at SOR 16.5.0 2020-03 CP-87e CP-200129 0489 F Clarification to manual CAG selection 16.5.0 2020-03 CP-87e CP-200129 0491 1 B Limited Service state on CAG cell. 16.5.0 2020-03 CP-87e CP-200129 0492 1 F Correction to Limited service state for SNPN 16.5.0 2020-03 CP-87e CP-200129 0493 2 F Presentation of PLMN with non-CAG cells for manual selection 16.5.0 2020-03 CP-87e CP-200124 0494 1 F Clarify that a UE operating in N1 mode do not attempt to access RLOS. 16.5.0 2020-03 CP-87e CP-200124 0495 2 B Support of restriction on access to RLOS 16.5.0 2020-03 CP-87e CP-200124 0496 B Manual network selection procedure for access to RLOS 16.5.0 2020-03 CP-87e CP-200129 0497 1 F Correction on term "shared network" definition for SNPN 16.5.0 2020-03 CP-87e CP-200129 0498 C UE identifier for SNPN 16.5.0 2020-03 CP-87e CP-200129 0500 F Determination of CAG cell 16.5.0 2020-03 CP-87e CP-200129 0502 1 F List of SNPNs for which the N1 mode capability was disabled 16.5.0 2020-03 CP-87e CP-200129 0503 1 F Display of the human readable name of an SNPN 16.5.0 2020-03 CP-87e CP-200105 0504 F "CAG information list" preventing selection of any available and allowable PLMN 16.5.0 2020-06 CP-88e CP-201100 0481 5 F Correction for SoR-AF 16.6.0 2020-06 CP-88e CP-201135 0499 7 C Manual CAG selection 16.6.0 2020-06 CP-88e CP-201100 0508 F SoR in HPLMN after registration 16.6.0 2020-06 CP-88e CP-201100 0509 1 F Modification of exchanges between SOR-AF and UDM 16.6.0 2020-06 CP-88e CP-201107 0510 1 F OTAF renamed to SP-AF 16.6.0 2020-06 CP-88e CP-201135 0511 1 C Management of forbidden SNPNs list upon receipt of a non-integrity protected reject message 16.6.0 2020-06 CP-88e CP-201100 0513 F Correction of the handling of timer TG 16.6.0 2020-06 CP-88e CP-201135 0517 1 F Correction on no suitable cell 16.6.0 2020-06 CP-88e CP-201360 0518 5 C Presentation of Human readable name for CAG cell 16.6.0 2020-06 CP-88e CP-201135 0522 2 F Sending CAG information list – option 1 16.6.0 2020-06 CP-88e CP-201135 0524 F figures 1, 2a, 2b, 3 and table 2 not applicable in SNPN 16.6.0 2020-06 CP-88e CP-201135 0525 1 C Selected CAG-ID from the NAS layer to the AS layer 16.6.0 2020-06 CP-88e CP-201135 0526 1 F CAG selection is optional in the manual network selection mode 16.6.0 2020-06 CP-88e CP-201135 0528 2 F correction to network selection in case of multiple subscribed SNPNs 16.6.0 2020-06 CP-88e CP-201135 0529 F Correction to Manual CAG selection procedure 16.6.0 2020-06 CP-88e CP-201100 0530 1 F UDM support of communication with SOR-AF 16.6.0 2020-06 CP-88e CP-201100 0532 1 F SOR-AF in scope 16.6.0 2020-06 CP-88e CP-201135 0536 2 F Updates to SNPN selection 16.6.0 2020-06 CP-88e CP-201100 0538 F Storing the PLMN identity in the "forbidden PLMN list" for 5GMM cause #73 "Serving network not authorized" 16.6.0 2020-06 CP-88e CP-201100 0539 F Clarification of the use of T3245 16.6.0 2020-06 CP-88e CP-201135 0540 F Reference correction for SNPN 16.6.0 2020-06 CP-88e CP-201131 0544 1 F Clarification of cause #35 in limited service state 16.6.0 2020-06 CP-88e CP-201314 0545 2 F Correction to CAG selection in automatic mode. 16.6.0 2020-06 CP-88e CP-201135 0547 F Resolving editor's note in Limited service condition on a CAG cell. 16.6.0 2020-06 CP-88e CP-201135 0548 1 F Removal of selected CAG-ID in automatic selection mode. 16.6.0 2020-06 CP-88e CP-201135 0549 F Clarification to SNPN manual selection. 16.6.0 2020-06 CP-88e CP-201135 0550 1 F Clarification to SNPN registration after SNPN selection. 16.6.0 2020-06 CP-88e CP-201100 0552 2 F On the parameters provided to the SOR-AF from the UDM. 16.6.0 2020-06 CP-88e CP-201107 0554 F SP-AF services. 16.6.0 2020-07 CP-88e Editorial corrections by rapporteur 16.6.1 2020-09 CP-89e CP-202170 0527 5 F Human readable network name for SNPN 16.7.0 2020-09 CP-89e CP-202170 0542 2 F Alternative to CR#0514: Correction of the handling of timer TG for SNPNs 16.7.0 2020-09 CP-89e CP-202170 0559 F Correction of implementation of CP-201314 16.7.0 2020-09 CP-89e CP-202257 0561 3 F SUPI types of subscriber identifier in "list of subscriber data" 16.7.0 2020-09 CP-89e CP-202149 0564 1 F Security checking of Steering of roaming 16.7.0 2020-09 CP-89e CP-202149 0565 F Steering of roaming to a forbidden PLMN 16.7.0 2020-09 CP-89e CP-202170 0568 1 F Automatic selection with empty "CAG information list" 16.7.0 2020-09 CP-89e CP-202170 0569 F Correction for CAG selection 16.7.0 2020-09 CP-89e CP-202149 0570 1 F Storage of SOR related information in the UDR 16.7.0 2020-09 CP-89e CP-202149 0571 F SOR-AF UDM exchanges alignment in after registration case 16.7.0 2020-09 CP-89e CP-202170 0583 F Resolution of Editors Note related to HRNN handling of CAG 16.7.0 2020-09 CP-89e CP-202149 0584 3 F Storage of SOR related information in the UDM/UDR 16.7.0 2020-09 CP-89e CP-202149 0585 1 F Editor's Note resolution for SOR 16.7.0 2020-09 CP-89e CP-202173 0560 F Periodic removal of "forbidden location areas for regional provision of service" 17.0.0 2020-09 CP-89e CP-202175 0566 1 B Enhancement for CP-SOR for UE in connected mode 17.0.0 2020-09 CP-89e CP-202175 0572 2 B Introducing the definition "Steering of roaming connected mode control information" 17.0.0 2020-09 CP-89e CP-202173 0574 1 F Removal of a VPLMN from the forbidden PLMNs list upon T3247 expiry 17.0.0 2020-09 CP-89e CP-202173 0580 1 F Clarification on the successfully received SoR case when UE is in manual mode 17.0.0 2020-12 CP-90e CP-203168 0573 3 D Editorial corrections 17.1.0 2020-12 CP-90e CP-203167 0587 2 A Correction of the Service Operation of SoR-AF 17.1.0 2020-12 CP-90e CP-203181 0591 1 B Introducing new requirements for CP-SOR in connected mode 17.1.0 2020-12 CP-90e CP-203181 0592 1 B Updating the requirements for CP-SOR in 5GS 17.1.0 2020-12 CP-90e CP-203181 0593 2 B SOR-CMCI configuration and session handling for enhanced control plane SOR in connected mode 17.1.0 2020-12 CP-90e CP-203167 0595 3 A Suspending transmission of 5GSM messages during SOR procedure 17.1.0 2020-12 CP-90e CP-203218 0597 1 A Aligning to TS 22.261 requirements on manual CAG selection 17.1.0 2020-12 CP-90e CP-203103 0600 5 F Handling of Higher Priority PLMN selection with the presence of "PLMNs where registration was aborted due to SOR" list 17.1.0 2020-12 CP-90e CP-203167 0601 1 A In SoR error cases, UE to always send Registration Complete at the end of Registration procedure if UE is either in Manual mode of operation or camped in UPLMN 17.1.0 2020-12 CP-90e CP-203168 0605 1 F Use of T3245 in an SNPN 17.1.0 2020-12 CP-90e CP-203167 0606 A Clarification on High Priority Search in 5GMM-Connected Mode with RRC Inactive 17.1.0 2020-12 CP-90e CP-203168 0611 3 B Initial CAG information list 17.1.0 2020-12 CP-90e CP-203168 0613 5 F No need to release NAS signalling connection when the selected VPLMN is the highest priority PLMN 17.1.0 2020-12 CP-90e CP-203181 0615 1 F Obtaining SOR-CMCI 17.1.0 2020-12 CP-90e CP-203168 0618 1 F Handling of periodic registration timer expiry 17.1.0 2020-12 CP-90e CP-203168 0619 F Periodic PLMN searches in MICO mode 17.1.0 2020-12 CP-90e CP-203188 0620 A Add reference to 24.587 and 38.331 in V2X triggered PLMN selection 17.1.0 2020-12 CP-90e CP-203167 0621 1 A Skipping step 9 if UDM has not requested an acknowledgment from the UE 17.1.0 2020-12 CP-90e CP-203215 0624 1 F CAG support and CAG information are only applicable when MS is in 5GS 17.1.0 2020-12 CP-90e CP-203102 0629 3 F Handling of "PLMNs where registration was aborted due to SOR" list 17.1.0 2020-12 CP-90e CP-203101 0630 2 F Conflict between PLMN reselection due to SOR and RAT disabling due to missing Voice support 17.1.0 2020-12 CP-90e CP-203168 0632 1 F The definition of non-CAG cell 17.1.0 2020-12 CP-90e CP-203168 0635 1 F Adding the definition of CAG cell 17.1.0 2020-12 CP-90e CP-203214 0639 1 F Secured packet upload of ME 17.1.0 2020-12 CP-90e CP-203165 0640 3 F Sending acknowledgement for steering of roaming procedure after registration 17.1.0 2020-12 CP-90e CP-203168 0641 1 F Clarification of Country definition 17.1.0 2020-12 CP-90e CP-203168 0643 1 F REGISTRATION COMPLETE sending 17.1.0 2021-012 Deletion of extra instances of figure C.2.1 17.1.1 2021-03 CP-91e CP-210116 0602 6 F Handling of PLMN selection with presence of PLMNs where registration was aborted due to SOR list 17.2.0 2021-03 CP-91e CP-210122 0644 1 B Handling and coordination of multiple Tsor-cm timers 17.2.0 2021-03 CP-91e CP-210122 0645 3 B Setting Tsor-cm timer for new PDU session or service 17.2.0 2021-03 CP-91e CP-210122 0646 3 B Removing resolved Editor's Notes and general corrections 17.2.0 2021-03 CP-91e CP-210122 0647 1 F No de-registration signalling when Tsor-cm stops due to going to idle mode 17.2.0 2021-03 CP-91e CP-210122 0651 1 F Configuring UE with SOR-CMCI 17.2.0 2021-03 CP-91e CP-210122 0652 1 B Configuration of services exempted from release due to SOR at the UE 17.2.0 2021-03 CP-91e CP-210122 0653 1 B Storage of SOR-CMCI in the UE 17.2.0 2021-03 CP-91e CP-210122 0654 1 F Correction of CP-SOR 17.2.0 2021-03 CP-91e CP-210122 0655 1 F Providing SOR-CMCI in figures 17.2.0 2021-03 CP-91e CP-210122 0656 1 F UDM obtaining SOR-CMCI 17.2.0 2021-03 CP-91e CP-210122 0657 3 B UE behavior upon receiving new timer valuer for Tsor-cm timer 17.2.0 2021-03 CP-91e CP-210122 0658 1 B Handling of timer Tsor-cm when changing the network selection mode to manual mode 17.2.0 2021-03 CP-91e CP-210122 0660 1 F PLMN selection when the emergency PDU session is released 17.2.0 2021-03 CP-91e CP-210114 0662 A Correction of handling of CAG information from a "PLMN equivalent to the HPLMN" 17.2.0 2021-03 CP-91e CP-210135 0669 1 D Inclusive language review 17.2.0 2021-03 CP-91e CP-210122 0670 1 F Including the SOR-CMCI in the steering of roaming information 17.2.0 2021-03 CP-91e CP-210133 0672 D Editorial corrections 17.2.0 2021-03 CP-91e CP-210116 0673 1 F Clarifications on PLMN and SNPN URSP storage - 23.122 part 17.2.0 2021-03 CP-91e CP-210116 0674 F Correction to automatic PLMN selection rule for a data centric MS 17.2.0 2021-03 CP-91e CP-210122 0675 1 F Clarification on SOR with SOR-CMCI and emergency PDU session 17.2.0 2021-03 CP-91e CP-210122 0676 2 B Prevention of SOR-CMCI provisioning when a UE does not support SOR-CMCI 17.2.0 2021-06 CP-92e CP-211128 0708 1 A PLMN selection triggered by V2X communication over PC5 17.3.0 2021-06 CP-92e CP-211137 0663 3 C SNPN selection for access to SNPNs using credentials from an entity separate from the SNPN 17.3.0 2021-06 CP-92e CP-211137 0694 1 B Lists of 5GS forbidden tracking areas 17.3.0 2021-06 CP-92e CP-211137 0695 1 B Forbidden SNPNs 17.3.0 2021-06 CP-92e CP-211137 0702 1 C SUPI for an SNPN using credentials owned by an SNPN CH 17.3.0 2021-06 CP-92e CP-211137 0703 5 C Emergency registration to an SNPN by a UE in the limited service state or no SIM state 17.3.0 2021-06 CP-92e CP-211137 0710 1 B Mobility registration update upon entering a new SNPN 17.3.0 2021-06 CP-92e CP-211137 0711 1 B Selection for onboarding in SNPN 17.3.0 2021-06 CP-92e CP-211137 ¸0713 1 B SNPN selection for voice centric UE 17.3.0 2021-06 CP-92e CP-211137 0719 B Adding default configured NSSAI in the "list of subscriber data" 17.3.0 2021-06 CP-92e CP-211144 0712 F Removal of editor's note on CAG information list in USIM 17.3.0 2021-06 CP-92e CP-211145 0714 1 F The handling of wildcard CAG ID-solution#1 17.3.0 2021-06 CP-92e CP-211146 0718 1 D Editorial corrections in TS 23.122 17.3.0 2021-06 CP-92e CP-211147 0724 1 F Send REGISTRATION COMPLETE message only if the SOR information is received 17.3.0 2021-06 CP-92e CP-211150 0716 2 F Clarification to few scenarios related to manual CAG selection 17.3.0 2021-06 CP-92e CP-211151 0679 1 F General corrections and alignments for SOR 17.3.0 2021-06 CP-92e CP-211151 0684 1 F Clarify the UE behaviour when the emergency PDU session is released 17.3.0 2021-06 CP-92e CP-211151 0685 1 F Clarify the UE behaviour when the the last running Tsor-cm timer expires 17.3.0 2021-06 CP-92e CP-211151 0687 1 B UE behavior upon updating "user controlled list of services exempted from release 17.3.0 2021-06 CP-92e CP-211151 0688 1 F SOR-CMCI provision with legacy AMF 17.3.0 2021-06 CP-92e CP-211151 0691 1 B Resolve EN on the SOR-CMCI storage in the UE 17.3.0 2021-06 CP-92e CP-211151 0692 1 F Clarification on handling the storage of the SOR-CMCI in the ME 17.3.0 2021-06 CP-92e CP-211151 0696 1 F Preventing configuring SOR-CMCI when the UE does not support SOR-CMCI 17.3.0 2021-06 CP-92e CP-211151 0697 1 F Consider stored/configured SOR-CMCI information when processing REFRESH due to SOR 17.3.0 2021-06 CP-92e CP-211151 0699 1 F Maintaining the user controlled list of services exempted from release due to SOR 17.3.0 2021-06 CP-92e CP-211151 0700 1 F Setting the timer value of Tsor-cm 17.3.0 2021-06 CP-92e CP-211151 0704 1 C Correction of setting the SOR-CMCI criteria 17.3.0 2021-06 CP-92e CP-211151 0705 1 C Correcting the SOR-CMCI format sent to the UE 17.3.0 2021-06 CP-92e CP-211151 0717 1 F Removal of ENs related to SOR-CMCI criteria 17.3.0 2021-06 CP-92e CP-211151 0720 1 F Performing PLMN selection after the emergency PDU session is released 17.3.0 2021-06 CP-92e CP-211151 0721 2 C Radio link failure during Tsor timer is running 17.3.0 2021-06 CP-92e CP-211151 0726 1 C Remove unnecessary requirement on handling on receipt of SOR-CMCI 17.3.0 2021-06 CP-92e CP-211151 0727 1 B Storage of user controlled list of services exempted from release due to SOR 17.3.0 2021-06 CP-92e CP-211152 0681 1 B Access Technology Identifier "satellite NG-RAN" 17.3.0 2021-09 CP-93e CP-212158 0777 1 F No use of non-globally-unique SNPN identity for accessing SNPN using credentials from CH 17.4.0 2021-09 CP-93e CP-212230 0739 3 F Attempt to select a higher priority PLMN/RAT combination when a PLMN/RAT combination is re-enabled 17.4.0 2021-09 CP-93e CP-212141 0731 1 C Corrections to the procedure in C.4.3 and other editorial corrections 17.4.0 2021-09 CP-93e CP-212141 0732 - F Removing resolved Editor's Notes in Annex C 17.4.0 2021-09 CP-93e CP-212125 0734 1 B Automatic PLMN selection updates for MINT 17.4.0 2021-09 CP-93e CP-212152 0735 - F Resolution of an EN about a range of CAG IDs 17.4.0 2021-09 CP-93e CP-212140 0737 1 F Correction on the description of TJ in SNPN selection-Rel17 17.4.0 2021-09 CP-93e CP-212125 0742 2 B Provisioning of list of PLMN(s) to be used in disaster condition in the UE 17.4.0 2021-09 CP-93e CP-212155 0744 1 F Clarification for Manual PLMN selection when emergency PDU or PDN connection exists 17.4.0 2021-09 CP-93e CP-212124 0745 1 B Adding support for PWS in SNPNs 17.4.0 2021-09 CP-93e CP-212141 0746 1 F Correction to SOR-CMCI attribute type criterion. 17.4.0 2021-09 CP-93e CP-212141 0748 - F Correction of secured packet definition 17.4.0 2021-09 CP-93e CP-212117 0749 1 A Miscellaneous changes on PLMN selection triggered by V2X communication in 5G 17.4.0 2021-09 CP-93e CP-212134 0751 1 B PLMN selection triggered by ProSe communicatins over NR-PC5 17.4.0 2021-09 CP-93e CP-212129 0756 - F Reference for the abbreviation of GIN 17.4.0 2021-09 CP-93e CP-212125 0757 2 B Higher priority PLMN search in disaster roaming scenario 17.4.0 2021-09 CP-93e CP-212155 0758 1 F The condition to store the PLMN identity in the list of PLMNs where registration was aborted due to SOR 17.4.0 2021-09 CP-93e CP-212141 0760 1 F Tsor-cm not related with PDU sessions 17.4.0 2021-09 CP-93e CP-212141 0761 1 F The timer value for Tsor-cm being zero 17.4.0 2021-09 CP-93e CP-212141 0762 1 F SOR-CMCI content definition 17.4.0 2021-09 CP-93e CP-212129 0764 2 F Attempt to obtain onboarding services during the No SIM state 17.4.0 2021-09 CP-93e CP-212129 0765 - F Correction on a UE supporting access to an SNPN using credentials from a CH configured with the SNPN selection parameters 17.4.0 2021-09 CP-93e CP-212129 0766 1 F Re-enable SNPN access mode after emergency call is finished 17.4.0 2021-09 CP-93e CP-212140 0771 1 F Camp on acceptable cell no need consider CAG information 17.4.0 2021-09 CP-93e CP-212141 0774 - F Removal of editor's notes on SOR-CMCI 17.4.0 2021-09 CP-93e CP-212129 0776 - F Obtaining emergency call in SNPN limited service state 17.4.0 2021-12 CP-94e CP-213034 0837 - F Resolution of an EN about CAG-ID range-23.122 17.5.0 2021-12 CP-94e CP-213037 0778 1 F IMSI based SUPI 17.5.0 2021-12 CP-94e CP-213037 0822 2 F Pre-configured AIs, URSP, and default configured NSSAI in an SNPN accessed using the PLMN subscription 17.5.0 2021-12 CP-94e CP-213037 0790 5 B Use of SOR to update the credentials holder controlled prioritized lists of preferred SNPNs and GINs 17.5.0 2021-12 CP-94e CP-213048 0830 2 F UDM not interrogating SOR-AF if no acknowledgement received from UE 17.5.0 2021-12 CP-94e CP-213048 0834 1 F Acknowledgment for the security packet of SOR information 17.5.0 2021-12 CP-94e CP-213048 0835 1 F Clarification when receiving no change of Operator Controlled PLMN 17.5.0 2021-12 CP-94e CP-213048 0850 1 F Deletion of PLMNs where registration was aborted due to SOR 17.5.0 2021-12 CP-94e CP-213055 0788 3 B Update of UE provisioning information for disaster roaming 17.5.0 2021-12 CP-94e CP-213055 0792 1 B Initiation of location registration for MINT 17.5.0 2021-12 CP-94e CP-213055 0794 3 B Clarification regarding reselection to EPLMN in manual mode disaster roaming. 17.5.0 2021-12 CP-94e CP-213055 0795 3 B Sending indication to user regarding disaster roaming support in Manual mode. 17.5.0 2021-12 CP-94e CP-213055 0796 3 B Clarification of provision of 'list of PLMNs to be used in Disaster condition during registration procedure. 17.5.0 2021-12 CP-94e CP-213055 0808 1 F UE leaving manual mode when the RPLMN is considered as the PLMN with disaster condition 17.5.0 2021-12 CP-94e CP-213055 0810 1 F Ignore RPLMN if UE not eligible for disaster roaming. 17.5.0 2021-12 CP-94e CP-213055 0841 1 F Disaster related indication 17.5.0 2021-12 CP-94e CP-213056 0783 1 C Removal of the user controlled list of services exempted from release due to SOR 17.5.0 2021-12 CP-94e CP-213056 0784 3 C Clarifying the conditions when SOR-CMCI is empty 17.5.0 2021-12 CP-94e CP-213056 0785 3 F SOR-CMCI rule for SMS 17.5.0 2021-12 CP-94e CP-213056 0798 1 F Clarification on match all type criterion in SOR-CMCI 17.5.0 2021-12 CP-94e CP-213056 0799 1 F Correction on timers when applying SOR-CMCI 17.5.0 2021-12 CP-94e CP-213056 0800 1 F USIM and SOR-CMCI in after registration scenario 17.5.0 2021-12 CP-94e CP-213056 0801 1 D Corrections in Annex C of 23.122 17.5.0 2021-12 CP-94e CP-213056 0805 1 F Release of high priority access PDU sessions while receiving SOR-CMCI 17.5.0 2021-12 CP-94e CP-213056 0806 1 D ME supporting the SOR-CMCI 17.5.0 2021-12 CP-94e CP-213056 0809 1 B SOR-CMCI configuration for SOR security check failure 17.5.0 2021-12 CP-94e CP-213056 0814 1 F Trigger on providing UE with SOR-CMCI after registration 17.5.0 2021-12 CP-94e CP-213056 0815 1 F Clarification on SSCMI 17.5.0 2021-12 CP-94e CP-213056 0816 2 F Clarification for storage of Operator Controlled PLMN list and SOR-CMCI along with SUPI 17.5.0 2021-12 CP-94e CP-213056 0827 1 C Correcting when the HPLMN requests ACK while supporting SOR-CMCI 17.5.0 2021-12 CP-94e CP-213056 0831 - F Clarification on timer associated with SST and SD 17.5.0 2021-12 CP-94e CP-213056 0833 1 F Update of conditions to use Operator Controlled PLMN Selector with Access Technology list stored in the ME 17.5.0 2021-12 CP-94e CP-213056 0843 1 F Correction on content of SOR information 17.5.0 2021-12 CP-94e CP-213056 0844 - F Store SOR-CMCI in ME indicator only in plain text 17.5.0 2021-12 CP-94e CP-213056 0845 1 F Providing UE with SOR-CMCI in secured packet after registration 17.5.0 2021-12 CP-94e CP-213056 0846 2 F Providing UE with SOR-CMCI no SOR-CMCI rules included 17.5.0 2021-12 CP-94e CP-213057 0807 - F Access Technology Identifier including satellite NG-RAN 17.5.0 2022-03 CP-95e CP-220229 0883 1 A RID for SNPN UEs 17.6.0 2022-03 CP-95e CP-220236 0863 - F Resolution of editor's note in clause 3.5 17.6.0 2022-03 CP-95e CP-220236 0864 - F Resolution of editor's note in clause 4.9.4 17.6.0 2022-03 CP-95e CP-220236 0865 - F Resolution of editor's note in clause 4.9.3.1.3 17.6.0 2022-03 CP-95e CP-220236 0867 - F Onboarding SNPN network selection information 17.6.0 2022-03 CP-95e CP-220236 0868 - B PLMN/SNPN selection upon stopping/starting operating in SNPN access mode 17.6.0 2022-03 CP-95e CP-220236 0791 6 C Allowing SNPN-enabled UE not operating in SNPN access mode to obtain emergency services in any SNPN 17.6.0 2022-03 CP-95e CP-220236 0858 1 B Enabling update of SOR-SNPN-SI in a PLMN 17.6.0 2022-03 CP-95e CP-220236 0859 1 C UE configuration for warning message reception in SNPNs 17.6.0 2022-03 CP-95e CP-220236 0872 1 B SNPN selection for onboarding services with lists of forbidden SNPNs 17.6.0 2022-03 CP-95e CP-220237 0866 1 F Resolution of editor's note in clause 4.9.3.1.4 17.6.0 2022-03 CP-95e CP-220237 0862 1 B Indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure 17.6.0 2022-03 CP-95e CP-220237 0884 - F Editor's note in clause 4.9.3.0 17.6.0 2022-03 CP-95e CP-220237 0896 - F No SOR-SNPN-SI via CP-SoR for CH with AAA server 17.6.0 2022-03 CP-95e CP-220238 0892 1 F Exiting manual network SNPN selection mode by a UE in the limited service state 17.6.0 2022-03 CP-95e CP-220238 0885 1 B Enabling update of list of preferred PLMNs in an SNPN 17.6.0 2022-03 CP-95e CP-220238 0893 1 F Correction for voice-centric UEs 17.6.0 2022-03 CP-95e CP-220245 0861 1 F L2 remote UE PLMN selection 17.6.0 2022-03 CP-95e CP-220248 0826 3 F SOR signalling connection handling in case of an emergency session 17.6.0 2022-03 CP-95e CP-220248 0880 1 F Clarification to when the UE performs higher priority PLMN selection 17.6.0 2022-03 CP-95e CP-220260 0879 1 F Clarify condition to use MINT based on non-3GPP access 17.6.0 2022-03 CP-95e CP-220260 0873 1 B Handling of forbidden PLMN list for disaster roaming 17.6.0 2022-03 CP-95e CP-220260 0870 2 F HPLMN control in the roaming area. 17.6.0 2022-03 CP-95e CP-220260 0891 1 F Pre-configuration of 'list of PLMNs to be used in disaster condition' in USIM. 17.6.0 2022-03 CP-95e CP-220260 0895 1 F Storage of 'List of PLMNs to be used in disaster condition' in NVM 17.6.0 2022-03 CP-95e CP-220260 0876 2 F Clarification on the applicability of MINT in a CAG cell. 17.6.0 2022-03 CP-95e CP-220261 0852 1 F Correcting the service operation leading to deleting the ME support of SOR-CMCI 17.6.0 2022-03 CP-95e CP-220261 0853 1 F Corrections in the SOR procedures after registration 17.6.0 2022-03 CP-95e CP-220261 0701 4 F Tsor-cm timer handling in case of IRAT transitions 17.6.0 2022-03 CP-95e CP-220261 0874 1 F HPLMN indication not apply for secured packet 17.6.0 2022-03 CP-95e CP-220261 0854 1 F Including the Store SOR-CMCI in ME indicator in the secured packet 17.6.0 2022-03 CP-95e CP-220261 0889 1 F Handling of MT services in SOR-CMCI - 23.122 17.6.0 2022-03 CP-95e CP-220261 0894 1 F Tsor-cm for security check failure upon successful check of the received SOR 17.6.0 2022-03 CP-95e CP-220262 0877 - B Adding requirements for NR RedCap devices 17.6.0 2022-03 CP-95e CP-220265 0825 4 C PLMN selection for satellite access 17.6.0 2022-03 CP-95e CP-220265 0828 4 B Higher priority PLMN search for MS in satellite NG-RAN access 17.6.0 2022-03 CP-95e CP-220265 0887 1 B Interval of Time between Searches for Higher Priority PLMN via Satellite NG-RAN 17.6.0 2022-03 CP-95e CP-220265 0741 7 B Validity of cause code #78 17.6.0 2022-06 CP-96 CP-221190 0905 3 F Configuration for anonymous SUCI usage 17.7.0 2022-06 set of CR Pack approved CRs were not implemented by mistake. All CRs below dated 2022-06 belong to this group. 17.7.1 2022-06 CP-96 CP-221203 0930 - F Editor's notes in clause 1.2 and clause C.7 17.7.1 2022-06 CP-96 CP-221203 0931 - F Editor's note in C.5 17.7.1 2022-06 CP-96 CP-221203 0935 1 F Removal of Editor's note on encoding of the indication of whether the MS shall ignore all warning messages in an SNPN in the USIM 17.7.1 2022-06 CP-96 CP-221212 0933 1 F Manual Selection of a non-member CAG cell 17.7.1 2022-06 CP-96 CP-221212 0937 1 F Remove manual selected PLMN from the forbidden PLMNs for GPRS service list 17.7.1 2022-06 CP-96 CP-221212 0939 1 F Procedure name correction 17.7.1 2022-06 CP-96 CP-221213 0936 1 F Release N1 NAS signalling connection when security check fails 17.7.1 2022-06 CP-96 CP-221213 0942 1 F At switch on and no RPLMN in manual mode when UE support CAG 17.7.1 2022-06 CP-96 CP-221219 0869 3 F MINT and higher priority PLMN Selection 17.7.1 2022-06 CP-96 CP-221219 0906 1 B Disaster related indication and UE determined PLMN with disaster condition 17.7.1 2022-06 CP-96 CP-221219 0911 1 F Removing the editor's note related to CT6 17.7.1 2022-06 CP-96 CP-221219 0923 1 F Clarification on provision of disaster romaing related information 17.7.1 2022-06 CP-96 CP-221219 0932 2 F UE without RPLMN 17.7.1 2022-06 CP-96 CP-221219 0943 1 F Clarification to Manual CAG selection 17.7.1 2022-06 CP-96 CP-221220 0924 1 F Correction on Steering of Roaming information 17.7.1 2022-06 CP-96 CP-221220 0925 1 F Starting Tsor-cm timer associated with SOR security check not successful criterion 17.7.1 2022-06 CP-96 CP-221220 0928 1 F Correction that UE needs to wait for UICC to reply to network 17.7.1 2022-06 CP-96 CP-221220 0929 1 F Clarification when no change to SOR-SNPI-SI 17.7.1 2022-06 CP-96 CP-221221 0910 4 C Handling of discontinuous coverage 17.7.1 2022-06 CP-96 CP-221221 0914 1 B PLMN selection for satellite E-UTRAN access 17.7.1 2022-06 CP-96 CP-221221 0917 - F Availability of a PLMN via satellite E-UTRAN 17.7.1 2022-06 CP-96 CP-221224 0900 - F Correction for CR 0828, deletion of moved sentence 17.7.1 2022-06 CP-96 CP-221224 0909 1 F Correction to the rules for higher priority PLMN selection in VPLMN 17.7.1 2022-06 CP-96 CP-221224 0916 - F Availability of a PLMN via satellite NG-RAN 17.7.1 2022-06 CP-96 CP-221224 0941 1 F Storage Information alignment on list of PLMNs not allowed to operate at the present UE location 17.7.1 2022-06 CP-96 CP-221241 0907 - F PLMN selection based on RRC container from L2 relay 17.7.1 2022-06 CP-96 CP-221249 0901 1 F Editor's note in C.1.2 17.7.1 2022-06 CP-96 CP-221249 0902 1 F Access identity applicability in non-subscribed SNPN 17.7.1 2022-06 CP-96 CP-221249 0903 - F Editor's note in clause 4.9.3.0 17.7.1 2022-06 CP-96 CP-221249 0915 1 F Signalling UE support for SOR-SNPN-SI in SOR ACK 17.7.1 2022-06 CP-96 CP-221249 0920 1 F URSP rules for SNPN 17.7.1 2022-09 CP-97e CP-222137 0945 - F Default UE credentials for primary authentication 17.8.0 2022-09 CP-97e CP-222137 0946 1 F Correction in configuration for anonymous SUCI usage 17.8.0 2022-09 CP-97e CP-222137 0964 1 F Perform automatic network selection in SNPN access mode 17.8.0 2022-09 CP-97e CP-222147 0950 1 F Suspension of NAS signalling during SOR triggered higher priority PLMN selection 17.8.0 2022-09 CP-97e CP-222152 0958 1 F Disaster related indication semantic update 17.8.0 2022-09 CP-97e CP-222153 0962 1 F Clarification on UE behavior due to handover 17.8.0 2022-09 CP-97e CP-222153 0965 - F Correction on UE behavior with no SOR-CMCI in ME 17.8.0 2022-09 CP-97e CP-222156 0960 1 F UE operation in terms of a VPLMN through satellite NG-RAN access with a shared MCC 17.8.0 2022-09 CP-97e CP-222159 0951 1 F Clarification on the timer handling for #78 17.8.0 2022-09 CP-97e CP-222159 0956 1 F Update of conditions for deleting entries in # 78 list to align with 24.501 17.8.0 2022-09 CP-97e CP-222152 0947 1 F Correction for PLMN with disaster condition 18.0.0 2022-09 CP-97e CP-222165 0968 1 F Clarification on first attempt for higher priority search 18.0.0 2022-09 CP-97e CP-222165 0967 1 F Clarification on IMS registration related signalling 18.0.0 2022-09 CP-97e CP-222165 0969 1 F Clarfication on the storage to NVM in the ME 18.0.0 2022-09 CP-97e CP-222172 0966 - D Fixing unnecessary capitalization in procedures naming and other corrections 18.0.0 2022-09 CP-97e CP-222185 0961 2 F Timer T handling 18.0.0 2022-09 CP-97e CP-222200 0949 1 F Correction to the handling of PSM and MICO mode 18.0.0 2022-09 CP-97e CP-222234 0948 1 F Correction on manual mode PLMN selection state diagram 18.0.0 2022-12 CP-98e CP-223133 0976 1 A Correction to name of List of PLMNs offering disaster roaming services 18.1.0 2022-12 CP-98e CP-223157 0977 2 F Correction to mode switching between SNPN and PLMN modes for emergency services 18.1.0 2022-12 CP-98e CP-223157 0978 1 F Correction to steering of UE in SNPN after registration 18.1.0 2022-12 CP-98e CP-223157 0979 1 F Manual PLMN selection to HPLMN/EHPLMN when MS supports CAG 18.1.0 2022-12 CP-98e CP-223157 0980 F Correction on reference no. of 33.501 18.1.0 2022-12 CP-98e CP-223115 0984 1 A Correct the value of higher priority PLMN search timer T 18.1.0 2022-12 CP-98e CP-223157 0986 2 F Providing a geographical location to the AS-23.122 18.1.0 2022-12 CP-98e CP-223133 0990 1 A Allowed access attempts while timer precluding registration is running 18.1.0 2022-12 CP-98e CP-223133 0992 1 A State while timer precluding registration is running 18.1.0 2022-12 CP-98e CP-223148 0995 1 A ProSe communications in limited service states 18.1.0 2022-12 CP-98e CP-223117 0997 1 A Postponing periodic PLMN reselection attempts for broadcast MBS services 18.1.0 2022-12 CP-98e CP-223122 0998 1 A Clarification on secured packet is provided by HPLMN in SNPN access mode R18 18.1.0 2022-12 CP-98e CP-223129 1000 2 A Clarification regarding deactivation of the access stratum in discontinuous coverage 18.1.0 2022-12 CP-98e CP-223122 1002 1 A UE configuration with protection scheme for concealing the SUPI 18.1.0 2022-12 CP-98e CP-223120 1003 2 B Equivalent SNPN usage in SNPN selection 18.1.0 2022-12 CP-98e CP-223120 1004 B Equivalent SNPN usage in UAC configuration validity 18.1.0 2022-12 CP-98e CP-223157 1006 1 F Access mode during SNPN onboarding. 18.1.0 2022-12 CP-98e CP-223157 1007 1 F Perform SNPN selection in limited service state. 18.1.0 2022-12 CP-98e CP-223157 1008 F Common requirements on satellite access technologies 18.1.0 2022-12 CP-98e CP-223122 1010 1 A UE behavior when receiving unsuccessful security check SOR information R18 18.1.0 2022-12 CP-98e CP-223157 1012 1 F No suppress of NAS signalling transmission for purpose of emergency services R18 18.1.0 2022-12 CP-98e CP-223157 1014 1 F Handling for the running Tsor-cm timer when security check fail 18.1.0 2022-12 CP-98e CP-223115 1016 F Correction to #78 timer handling 18.1.0 2022-12 CP-98e CP-223144 1017 F Correction to #78 timer handling 18.1.0 2022-12 CP-98e CP-223239 1021 1 F Clarification on the UE behaviour upon receiving “do not store SOR-CMCI in ME” 18.1.0 2023-03 CP-99 CP-230285 1022 - F Correction for using the stored SOR-CMCI in the UE 18.2.0 2023-03 CP-99 CP-230231 1037 - B Equivalent SNPNs: forbidden SNPNs in TS 23.122 18.2.0 2023-03 CP-99 CP-230215 1018 2 F Clarification on #11, #35 with integrity protection in HPLMN 18.2.0 2023-03 CP-99 CP-230231 1049 - F Single CH-controlled prioritized list of preferred SNPNs/GINs 18.2.0 2023-03 CP-99 CP-230231 1050 - F SOR information delivery via an SNPN 18.2.0 2023-03 CP-99 CP-230278 1028 1 F Equivalent SNPNs: completion of selection 18.2.0 2023-03 CP-99 CP-230278 1036 1 B Equivalent SNPNs: 5GS forbidden tracking areas in TS 23.122 18.2.0 2023-03 CP-99 CP-230278 1038 2 B Equivalent SNPN information provided to lower layers for cell reselection 18.2.0 2023-03 CP-99 CP-230214 1059 3 F Clarification of USAT REFRESH command qualifier of type of Steering of Roaming 18.2.0 2023-03 CP-99 CP-230278 1039 2 B SOR-SNPN-SI for access for localized services in SNPN 18.2.0 2023-03 CP-99 CP-230278 1029 4 B Access for localized services 18.2.0 2023-03 CP-99 CP-230278 1035 1 F Term reference for SNPN access mode 18.2.0 2023-03 CP-99 CP-230265 1026 1 B Enhanced CAG selection - additional information 18.2.0 2023-03 CP-99 CP-230265 1027 1 B Enhanced CAG selection - enforcement in idle mode procedures 18.2.0 2023-03 CP-99 CP-230319 0952 13 B Signal level enhanced network selection requirements for PLMN selection 18.2.0 2023-03 CP-99 CP-230209 1031 2 F Emergency service and limited service state for satellite access 18.2.0 2023-03 CP-99 CP-230317 0985 10 B Updates to Automatic PLMN Selection for SENSE 18.2.0 2023-06 CP-100 CP-231232 1061 2 F Handling of forbidden PLMN lists when MS is in manual mode 18.3.0 2023-06 CP-100 CP-231271 1066 1 B Periodic PLMN searches when unavailability period is activated 18.3.0 2023-06 CP-100 CP-231217 1075 1 F Handling last registered SNPN 18.3.0 2023-06 CP-100 CP-231232 1076 1 F SOR related information in list of subscriber data for SNPN 18.3.0 2023-06 CP-100 CP-231238 1090 1 B Forbidden SNPN lists for localized services 18.3.0 2023-06 CP-100 CP-231217 1080 1 F Correction to SOR for SNPN during registration 18.3.0 2023-06 CP-100 CP-231217 1087 1 F Clarification on the deletion of PLMNs were registration was aborted due to SOR 18.3.0 2023-06 CP-100 CP-231270 1073 1 B Adding USAT REFRESH for updating operator threshold for SENSE 18.3.0 2023-06 CP-100 CP-231238 1068 1 B SNPN selection for the localized services 18.3.0 2023-06 CP-100 CP-231232 1091 - F Handling of the list of forbidden PLMN for GPRS service when MS is in manual mode 18.3.0 2023-06 CP-100 CP-231232 1095 - D Reordering of definitions 18.3.0 2023-06 CP-100 CP-231277 1100 - B PLMN selection triggered by A2X communication over PC5 18.3.0 2023-06 CP-100 CP-231232 1118 - F Restricting manual selection during emergency services 18.3.0 2023-06 CP-100 CP-231270 1005 7 B Periodic attempts for signal level enhanced network selection 18.3.0 2023-06 CP-100 CP-231270 1072 2 B Resolution of editor's note on updation of operator threshold via CP-SOR 18.3.0 2023-06 CP-100 CP-231238 1114 1 F Removing references of SNPN access mode. 18.3.0 2023-06 CP-100 CP-231239 1083 3 B SNPN manual selection and credentials holder controlled prioritized list of preferred SNPNs and GINs for access for localized services in SNPN 18.3.0 2023-06 CP-100 CP-231239 1115 1 C SNPN selection on validity condition change 18.3.0 2023-06 CP-100 CP-231239 1107 1 F Clear forbidden SNPN list for localized service on receiving SOR-SNPN-SI-LS 18.3.0 2023-06 CP-100 CP-231282 1113 1 F Provide CAG information list authorized by allowed CAG list to AS. 18.3.0 2023-06 CP-100 CP-231282 1105 1 F Location validity information for enhanced CAG list in TS 23.122 18.3.0 2023-06 CP-100 CP-231217 1093 1 F Clarification for manual SNPN selection mode procedure for onboarding services 18.3.0 2023-06 CP-100 CP-231232 1096 1 F Definition of Access Technology 18.3.0 2023-06 CP-100 CP-231232 1092 1 F Clarification on handling equivalent PLMN(s) when PLMN is considered disabled on one or more RAT(s) 18.3.0 2023-06 CP-100 CP-231217 1097 2 F SOR-CMCI: number of rules supported by the UE 18.3.0 2023-06 CP-100 CP-231270 1013 8 B CP-SOR for SENSE capable UE 18.3.0 2023-06 CP-100 CP-231283 1025 7 B Introduction of Enhanced Access to Support Network Slice -slice-based PLMN selection 18.3.0 2023-06 CP-100 CP-231270 1109 3 F Clarification for SENSE applicability considering the EFOCST in the USIM 18.3.0 2023-06 CP-100 CP-231239 1069 4 B Handling of location assistance information provided in the SoR SNPN selection information for localized services 18.3.0 2023-06 CP-100 Fixing Errors 18.3.1 2023-08 CP-100 Section 4.4.3.5 not listed in ToC 18.3.2 2023-09 CP-101 CP-232222 1130 - F Providing UE's subscribed S-NSSAI(s) to the SOR-AF 18.4.0 2023-09 CP-101 CP-232217 1147 - F Correction for the SOR-SENSE 18.4.0 2023-09 CP-101 CP-232191 1150 - F Clarification whether a CAG ID is authorized or CAG IDs of a CAG cell is authorized needs to be considered during manual selection 18.4.0 2023-09 CP-101 CP-232222 1137 1 C Add the additional requirements for slice-based PLMN selection 18.4.0 2023-09 CP-101 CP-232191 1131 1 F Equivalent SNPN Enhancements for Warning Message Configurations 18.4.0 2023-09 CP-101 CP-232191 1120 1 F Time validity information structure and evaluation 18.4.0 2023-09 CP-101 CP-232217 1125 1 F Updating the requirements for SENSE 18.4.0 2023-09 CP-101 CP-232217 1128 1 F Miscellaneous corrections for SENSE 18.4.0 2023-09 CP-101 CP-232191 1135 1 F Condition on enabling localized services in SNPN 18.4.0 2023-09 CP-101 CP-232191 1136 1 F EN resolution on location validity information 18.4.0 2023-09 CP-101 CP-232195 1122 1 D Editorial issues 18.4.0 2023-09 CP-101 CP-232217 1129 1 F Correction to periodic PLMN selection for Signal level enhanced network selection 18.4.0 2023-09 CP-101 CP-232191 1143 1 F Limited state system selection for localized services 18.4.0 2023-09 CP-101 CP-232191 1144 1 F No SIM state in the UE while accessing localized services in SNPN 18.4.0 2023-09 CP-101 CP-232191 1149 1 F Clarification on SNPN selection procedure when emergency is ongoing 18.4.0 2023-09 CP-101 CP-232192 1108 4 F Clear forbidden SNPN list for localized service on validation criterion met 18.4.0 2023-09 CP-101 CP-232192 1141 3 F Resolution of EN on equivalent SNPNs assignment during onboarding registration 18.4.0 2023-09 CP-101 CP-232192 1121 4 F SNPN selection upon validity condition changing between met and not met 18.4.0 2023-12 CP-102 CP-233162 1165 - D Editorial correction to SOR-SNPN-SI-LS 18.5.0 2023-12 CP-102 CP-233143 1167 - F Delete SNPN identified by GIN in SOR-SNPN-SI from forbidden SNPN list 18.5.0 2023-12 CP-102 CP-233162 1174 - B Manual selected SNPN and forbidden lists handling 18.5.0 2023-12 CP-102 CP-233162 1175 - B User reselection and localized service 18.5.0 2023-12 CP-102 CP-233145 1172 1 B Clarification to timer Tsense for unavailability period 18.5.0 2023-12 CP-102 CP-233162 1173 1 B equivalent SNPN used by the UE for Localized Services 18.5.0 2023-12 CP-102 CP-233141 1177 2 F Correction to the list of PLMNs to be used in Disaster condition by VPLMNs 18.5.0 2023-12 CP-102 CP-233141 1178 1 F Allowing EMSFB during SOR 18.5.0 2023-12 CP-102 CP-233162 1161 2 B SNPN selection for localized services in case of SNPN is not available 18.5.0 2023-12 CP-102 CP-233189 1163 3 F Up to one entry associated with same PLMN 18.5.0 2023-12 CP-102 CP-233142 1181 D Editorial correction in forbidden SNPN list names 18.5.0 2023-12 CP-102 CP-233143 1189 1 F CP-SOR corrections in 23.122 18.5.0 2023-12 CP-102 CP-233162 1168 4 F Forbidden SNPN lists for localized services for manual SNPN selection 18.5.0 2023-12 CP-102 CP-233162 1185 1 F Covering user reselection for localized service 18.5.0 2023-12 CP-102 CP-233162 1186 1 F Correction on SNPN selection for localized services 18.5.0 2023-12 CP-102 CP-233162 1196 1 F For Consistency text in SNPN selection clause 18.5.0 2023-12 CP-102 CP-233189 1184 1 F PLMN search in IDLE with suspend indication 18.5.0 2023-12 CP-102 CP-233184 1190 2 F Clarification for SOR procedure for signal level enhanced network selection 18.5.0 2023-12 CP-102 CP-233162 1194 2 F Minor Corrections for clarification in SNPN selection clause in TS 23.122 18.5.0 2023-12 CP-102 CP-233162 1162 5 B Location validity information for localized services 18.5.0 2023-12 CP-102 CP-233181 1197 - C Removal of slice-based PLMN selection feature 18.5.0 2024-03 CP-103 CP-240105 1203 1 F Correction on lists of SNPNs with N1 mode capability disabled 18.6.0 2024-03 CP-103 CP-240105 1204 1 F Correction on the list associated per entry of list of subscriber data or per PLMN subscription 18.6.0 2024-03 CP-103 CP-240105 1208 1 B CP-SOR corrections in 23.122 18.6.0 2024-03 CP-103 CP-240093 1198 1 F Correction to C.3 if SOR information contains a secured packet and no SOR-CMCI is applicable 18.6.0 2024-03 CP-103 CP-240125 1205 1 F Support of SOR-SNPN-SI in EHPLMN 18.6.0 2024-03 CP-103 CP-240096 1201 2 F Postpone periodic PLMN access attempts while receiving broadcast MBS 18.6.0 2024-03 CP-103 CP-240105 1211 3 F Clarifications on Location validity information for localized services 18.6.0 2024-03 CP-103 CP-240096 1202 2 F Postpone periodic PLMN access attempts while receiving multicast MBS 18.6.0 2024-06 CP-104 CP-241175 1220 - F SOR-SNPN-SI indicator set in PLMN 18.7.0 2024-06 CP-104 CP-241176 1215 1 F Correction for ME's support for SOR-SNPN-SI 18.7.0 2024-06 CP-104 CP-241175 1217 1 F Correction on SOR-SNPN-SI indicator handling in UDM 18.7.0 2024-06 CP-104 CP-241175 1218 1 F SOR-SNPN-SI indicator handling in UDM 18.7.0 2024-06 CP-104 CP-241161 1209 3 F MINT corrections in 23.122 18.7.0 2024-06 CP-104 CP-241175 1219 1 F SOR-SNPN-SI indicator handling in UDM 18.7.0 2024-06 CP-104 CP-241203 1166 7 F PLNM selection on time validity change of CAG 18.7.0 2024-06 CP-104 CP-241184 1223 3 F Disaster return wait range timer 18.7.0 2024-06 CP-104 CP-241184 1221 3 F Storing MINT parameters from USIM to ME 18.7.0 2024-06 CP-104 CP-241202 1233 - B Resolving ENs on RAN specifications references for A2X communication over PC5 18.7.0 2024-06 CP-104 CP-241198 1243 - F Clarification that 'match-all' can be applied only when security check is successful. 18.7.0 2024-06 CP-104 CP-241198 1230 1 F Correction to PLMN selection for UE in eCall only mode 18.7.0 2024-06 CP-104 CP-241175 1225 1 F Corrections for forbidden SNPNs in 23.122 18.7.0 2024-06 CP-104 CP-241176 1234 1 F UDM determination on ME supports SOR-SNPN-SI-LS 18.7.0 2024-06 CP-104 CP-241176 1222 3 F The recognition of SNPN providing ac3.5 ess for localized services in SNPN 18.7.0 2024-06 CP-104 CP-241176 1246 1 F Correction for the SNPN access operation mode 18.7.0 2024-06 CP-104 CP-241184 1227 1 D Replacement of MS with UE for the term MS determined PLMN with disaster condition 18.7.0 2024-06 CP-104 CP-241169 1241 1 F Correction to SOR-CMCI rule handling to add the missing security criterion type 18.7.0 2024-06 CP-104 CP-241175 1236 1 F SOR-SNPN-SI indicator set at UE 18.7.0 2024-06 CP-104 CP-241175 1235 2 F UDM to SOR-AF: ME support of SOR-SNPN-SI indicator 18.7.0 2024-06 CP-104 CP-241184 1228 2 F LR failure Disaster roaming for the determined PLMN with disaster condition not allowed 18.7.0 2024-06 CP-104 CP-241187 1199 4 F Adding requirement for NR eRedCap UE 18.7.0 2024-06 CP-104 CP-241169 1242 3 F Clarification on the deletion of SOR-CMCI received over N1 NAS signalling 18.7.0 2024-06 CP-104 CP-241264 1240 3 F Clarification on the timer handling when SOR-CMCI contains no SOR-CMCI rule 18.7.0 2024-06 CP-104 Fixing errors 18.7.1 2024-09 CP-105 CP-242183 1248 1 F PLMN selection tiggered by CAG time validity information change 18.8.0 2024-09 CP-105 CP-242183 1251 1 F Localized services in SNPN and voice centric UEs 18.8.0 2024-09 CP-105 CP-242201 1263 1 F Missing handling of cause #36 18.8.0 2024-09 CP-105 CP-242183 1264 2 F Correction to the use of FPLMN or FSNPN for emergency services 18.8.0 2024-09 CP-105 CP-242171 1247 3 C 5GMM cause code #15 indicating Satellite NG-RAN not allowed in PLMN 18.8.0 2024-09 CP-105 CP-242201 1252 - D Editorial issues 19.0.0 2024-09 CP-105 CP-242201 1256 - F Clarification on the definition of Equivalent HPLMN list 19.0.0 2024-09 CP-105 CP-242175 1253 2 B Managing PLMN selection candidates when considering PLMNs with RAT restriction 19.0.0 2024-09 CP-105 CP-242183 1258 1 F Handling of TAs on reception of SOR-SNPN-SI-LS 19.0.0 2024-09 CP-105 CP-242190 1261 1 F Correction to the automatic PLMN selection mode procedure for MINT 19.0.0 2024-09 CP-105 CP-242190 1259 1 F Disaster roaming in manual mode 19.0.0 2024-12 CP-106 CP-243182 1272 1 A Corrections to 5GMM cause code #15 indicating Satellite NG-RAN not allowed in PLMN 19.1.0 2024-12 CP-106 CP-243207 1273 1 B Updates to PLMN selection due to RAT restriction 19.1.0 2024-12 CP-106 CP-243207 1269 2 B Storing RAT utilization control information in non-volatile-memory 19.1.0 2024-12 CP-106 CP-243200 1266 4 C EMM cause #15 indicating Satellite E-UTRAN not allowed in PLMN 19.1.0 2024-12 CP-106 CP-243181 1270 1 F Satellite access technology considerations for PLMN selection requirements related to disabling N1 mode capability because voice service was not available 19.1.0 2024-12 CP-106 CP-243177 1281 1 F Correction for the case of using 5G ProSe when no suitable cell is found 19.1.0 2024-12 CP-106 CP-243201 1282 2 B SNPN selection triggered by ProSe communications 19.1.0 2024-12 CP-106 CP-243200 1284 2 F Re-enabling S1/N1 mode capability when IMS becomes available 19.1.0 2024-12 CP-106 CP-243184 1288 1 B PLMN selection during OOS for UE supporting eCall and normal call 19.1.0 2024-12 CP-106 CP-243211 1287 2 B No LR via restricted access technology in RPLMN and its equivalent PLMNs 19.1.0 2024-12 CP-106 CP-243186 1274 3 F Deletion of FTA for localized services identified by GIN 19.1.0 2024-12 CP-106 CP-243196 1276 4 F UE exiting manual network selection mode 19.1.0 2025-03 CP-107 CP-250142 1286 2 D Moving the conditions of UE handling of SOR-CMCI rules to after the list of SOR-CMCI rules 19.2.0 2025-03 CP-107 CP-250148 1295 3 B Handling manual PLMN/access technology selection with RAT restriction 19.2.0 2025-03 CP-107 CP-250148 1298 1 F Corrections for the term RAT 19.2.0 2025-03 CP-107 CP-250148 1299 3 F Handling of list of PLMNs with associated RAT restrictions 19.2.0 2025-03 CP-107 CP-250164 1301 1 A Corrections of CR implementation error for PLMN selection 19.2.0 2025-03 CP-107 CP-250144 1302 1 F Corrections for PLMN selection at switch on or recovery from lack of coverage 19.2.0 2025-03 CP-107 CP-250143 1312 2 B How to handle MS configured for high priority access in a disaster condition 19.2.0 2025-03 CP-107 CP-250144 1313 1 F Additional trigger for disaster condition end 19.2.0 2025-03 CP-107 CP-250145 1315 1 F Re-enabling satellite NG-RAN capability when IMS becomes available 19.2.0
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
1 Scope
|
This document defines the stage 2 service description for emergency services in the IP Multimedia Core Network Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services and IM emergency services for eCall. ITU‑T Recommendation I.130 [4] describes a three-stage method for characterisation of telecommunication services and ITU‑T Recommendation Q.65 [3] defines stage 2 of the method.
This document covers also the Access Network aspects that are crucial for the provisioning of IMS emergency services. Other 3GPP specifications that are related to the IMS emergency services are TS 23.228 [1] on IMS in general, including fixed broadband access aspects, TS 23.060 [2] describing GPRS (UTRAN): TS 23.401 [28] describing EPS (UTRAN and E-UTRAN); TS 23.402 [29] describing Non 3GPP access (WLAN) to EPC; TS 23.271 [5] that covers location services; TS 23.216 [31] and TS 23.237 [32] describing Single Radio Voice Call Continuity (SRVCC) and Dual Radio Voice Call Continuity (DRVCC) for IMS Emergency session, TS 23.292 [45] describing the use of IMS services when using CS access for the media bearer and TS 23.501 [48] and TS 23.502 [49] describing support of emergency services and location for 5GS. TS 25.301 [6] contains an overall description of the UMTS Terrestrial Radio Access Network; TS 36.300 [30] contains an overall description of the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); and TS 38.300 [50] contains an overall description of the Next Generation Radio Access Network (NG-RAN). Other non-3GPP specifications that are related to the IMS emergency services include 3GPP2 cdma2000 HRPD IP‑CAN, as specified in 3GPP2 X.S0060 [25] when the UE is connected to a PDS core network and 3GPP2 X.S0057‑A [39] when the UE is connected to an EPC core network.
The emergency support in different IP-CANs is described in the Informative Annex E.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 23.228: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS); Stage 2".
[2] 3GPP TS 23.060: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; General Packet Radio Service (GPRS); Service description; Stage 2".
[3] CCITT Recommendation Q.65: "Methodology – Stage 2 of the method for the characterisation of services supported by an ISDN".
[4] ITU Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".
[5] 3GPP TS 23.271: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Functional stage 2 description of LCS".
[6] 3GPP TS 25.301: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Interface Protocol Architecture".
[7] Void.
[8] 3GPP TS 22.101: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Service aspects; Service principles".
[9] IETF RFC 3825: "Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information".
[10] IETF RFC 4676: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information ".
[11] 3GPP TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications".
[12] 3GPP TS 23.002: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Network architecture".
[13] 3GPP TS 24.008: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[14] IETF RFC 4119: "A Presence-based GEOPRIV Location Object Format".
[15] OMA AD SUPL: "Secure User Plane Location Architecture", http://www.openmobilealliance.org.
[16] OMA TS ULP: "User Plane Location Protocol", http://www.openmobilealliance.org.
[17] NENA I2 architecture: "Interim VoIP Architecture for Enhanced 9-1-1 Services (i2)".
[18] ETSI ES 282 004: "Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)".
[19] 3GPP TS 24.229: "IP multimedia call control protocol based on SIP and SDP; stage 3".
[20] 3GPP TS 23.203: "Policy and Charging Control architecture".
[21] 3GPP TS 23.003: "Numbering, addressing and identification".
[22] Void.
[23] ANSI/J‑STD-036‑B: "Enhanced Wireless 9-1-1, Phase 2".
[24] 3GPP2 X.S0002‑0: "MAP Location Services Enhancements".
[25] 3GPP2 X.S0060: "HRPD Support for Emergency Service".
[26] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[27] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network subsystem; Stage 1".
[28] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[29] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[30] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[31] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SR VCC); Stage 2".
[32] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[33] 3GPP TS 24.301: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[34] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction".
[35] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[36] ETSI TS 181 019 V2.0.0: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Business Communication Requirements".
[37] ETSI TS 182 024 v.2.1.1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Hosted Enterprise Services; Architecture, functional description and signalling".
[38] ETSI TS 182 025 v.2.1.1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Business trunking; Architecture and functional description".
[39] 3GPP2 X.S0057‑C v1.0: "E‑UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects".
[40] NENA 08‑002, Version 1.0 (i3): "NENA Functional and Interface Standards for Next Generation 9-1-1".
[41] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[42] 3GPP TS 26.267: "Digital cellular telecommunication systems (Phase 2+); Universal Mobile Telecommunication System (UMTS); eCall data transfer; In-band modem solution General description".
[43] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents".
[44] 3GPP TS 33.203: "3G security; Access security for IP-based services".
[45] ATIS-0700028: "Location Accuracy Improvements for Emergency Calls".
[46] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services".
[47] IEEE Std 802.11‑2012: "IEEE Standard for Information technology--Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
[48] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[49] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[50] 3GPP TS 38.300: "NR; Overall description; Stage-2".
[51] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[52] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[53] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[54] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in idle mode and in RRC Inactive state".
[55] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification".
[56] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[57] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification".
[58] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[59] CEN EN 17184:2024: "Intelligent transport systems - eSafety - eCall High level application Protocols (HLAP) using IP Multimedia Subsystem (IMS) over packet switched network".
[60] 3GPP TS 23.221: "Architectural requirements".
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
3 Definitions, symbols and abbreviations
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TR 21.905 [11] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [11].
Charging Data Record: Record generated by a network element for the purpose of billing a subscriber for the provided service. See TS 32.260 [35] for further details.
Connectivity Session Location and Repository Function (CLF): As per ETSI ES 282 004 [18], the Connectivity Session Location and Repository Function (CLF) registers the association between the IP address allocated to the UE and related network location information, i.e.: access transport equipment characteristics, line identifier (Logical Access ID), IP Edge identity.
NG-eCall (eCall Over IMS): A manually or automatically initiated IMS emergency call, from a vehicle, supplemented with a minimum set of emergency related initial data (MSD).
Emergency Call Server (ECS): The functional entity consists of a Location Retrieval Function (LRF) and either a routing proxy or a redirect server, e.g. an ECS contains a VPC and a Routing Proxy or Redirect Server in NENA I2 architecture [17].
Emergency‑CSCF: The Emergency‑CSCF handles certain aspects of emergency sessions, e.g. routing of emergency requests to the correct emergency centre or PSAP.
Emergency Service Query Key (ESQK): A 10-digit North American Numbering Plan number used to identify a particular emergency call instance. It is used by the LRF as a key to look up for the location information and callback information associated with the emergency call instance and is also used by the PSAP to query location information from the LRF.
Emergency Service Routing Key (ESRK): see TS 23.271 [5] or J‑STD‑036 [23].
Emergency Service Routing Number (ESRN): North American Numbering Plan number used for routing of an emergency call to the appropriate gateway for an eventual delivery towards a CS-based PSAP.
Geographical Location Information: Location indicated in geographical terms, for example geographical coordinates or street address (e.g. as supported by IETF RFC 4119 [14]).
Local regulation: Condition defined by the authority whose legislation applies where the emergency service is invoked.
Location Identifier: Information about the current location of the UE in the network. Location is indicated in network terms, for example using the global cell id in cellular networks, line-id in fixed broadband networks, (OMA-Location also uses this term, but OMA so far defines the Location Identifier only for cellular access.)
Location Information: The location information may consist of the Location Identifier and/or the Geographical location information.
Location Retrieval Function (LRF): This functional entity handles the retrieval of location information for the UE including, where required, interim location information, initial location information and updated location information. The LRF may interact with a separate RDF or contain an integrated RDF in order to obtain routing information. The LRF may interact with a separate Location Server or contain an integrated Location Server in order to obtain location information. The LRF may interact with or contain other types of location server functions in order to obtain location information.
Location Server (LS): General term for the entity responsible for obtaining the location of the UE (e.g. GMLC see TS 23.271 [5], MPC see 3GPP2 X.S0002 [24] or SLP see OMA AD SUPL [15]).
Last Routing Option (LRO): A number, which may be used in the event of network failure towards a specific location based PSAP or a number that can be associated to a national or default PSAP/Emergency centre.
Operator policy: Condition set by operator.
Private Numbering Plan: According to ETSI TS 181 019 [36], a numbering plan explicitly relating to a particular private numbering domain.
Public Safety Answering Point (PSAP): A physical location, where emergency calls from the public are received.
Routing Determination Function (RDF): The functional entity, which may be integrated in a Location Server or in an LRF, provides the proper PSAP destination address to the E‑CSCF for routing the emergency request. It can interact with a LS to manage ESQK allocation and management and deliver location information to the PSAP.
Stand-alone Non-Public Network: A non-public network not relying on network functions provided by a PLMN.
For the purposes of the present document, the following terms and definitions given in TS 24.229 [19] apply:
Private Network Traffic
NOTE: All traffic from UEs having registered a contact bound to a public user identity receiving hosted enterprise services, is private network traffic.
Public Network Traffic
For the purposes of the present document, the following terms and definitions given in TS 23.401 [28] apply:
eCall Only Mode: See TS 23.401 [28].
For the purposes of the present document, the following terms and definitions given in TS 22.101 [8] apply:
eCall: See TS 22.101 [8].
Minimum Set of Data (MSD): See TS 22.101 [8].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply:
CDR Charging Data Record
CLF Connectivity session Location and repository Function
CS Circuit Switched
DRVCC Dual Radio Voice Call Continuity
E‑CSCF Emergency‑CSCF
EATF Emergency Access Transfer Function
ECS Emergency Call Server
ESQK Emergency Service Query Key
ESRK Emergency Service Routing Key
ESRN Emergency Service Routing Number
HRPD High Rate Packet Data
LRF Location Retrieval Function
LRO Last Routing Option
LS Location Server
MPC Mobile Positioning Centre
MSD Minimum Set of emergency related Data
PDS Packet Data Subsystem
PSAP Public Safety Answering Point
RDF Routing Determination Function
SET SUPL Enabled Terminal
SLP SUPL Location Platform
SNPN Standalone Non-Public Network
SRVCC Single Radio Voice Call Continuity
SUPL Secure User Plane for Location
URN Uniform Resource Name
VPC VoIP Positioning Centre
WLAN Wireless LAN
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
4 High level Principles
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
4.1 Architectural Principles
|
The solution for emergency sessions in the IMS fulfils the emergency principles and requirements of TS 22.101 [8], TS 22.228 [27] and the following architectural requirements:
1. Void.
2. Emergency services are independent from the IP-CAN with respect to the detection and routing of emergency sessions. The emergency services shall be possible over at least a cellular access network (terrestrial or satellite), a fixed broadband access, a nomadic access and a WLAN access to EPC or non-3GPP access to 5GC.
2a. Emergency numbers and associated types or URN information received via WLAN (for access to EPC) are only used for detecting emergency calls in the same country, if permission from PLMN selected in 3GPP access was received (see TS 23.401 [28] and TS 23.060 [2] for EPC access).
NOTE 1: Some features described in this clause do not apply for emergency session set-up over WLAN access to EPC or to 5GC. The limitations are documented in Annex J and Annex L.
2b. Emergency numbers and associated types received using a list as described in TS 24.008 [13] are only used for detecting emergency calls in the same country. The UE can obtain these numbers and associated types via mobility management procedures as described in TS 24.008 [13], TS 24.301 [33] and TS 24.501 [52]. The associated types consist of a limited number of emergency service categories from which a limited number of URNs can be derived.
2c. Emergency numbers and associated URN information received using a list as described in TS 24.301 [33] are only used when they are valid. The validity of these numbers and associated URN information is specified in clause 10.4.1 of TS 22.101 [8] (i.e. the serving network indicates whether this list is valid in the country or only in the PLMN or SNPN). The UE can obtain these numbers and associated URN information via mobility management procedures as described in TS 24.301 [33] and TS 24.501 [52].
3. Any kind of emergency numbers and emergency SIP and TEL‑URIs as specified in TS 22.101 [8] and special indications for emergency sessions within the SIP signalling shall be supported. The URIs allowed to resolve to emergency services may be subject to local regulation in the serving network.
4. Emergency sessions should be prioritized over non-emergency sessions by the system.
5. The establishment of IMS emergency sessions shall be possible for users with a barred public user identity.
6. The primary solution shall be that the UE can detect an emergency session (e.g. by evaluating the SIP-URI or the dialled number) by itself and indicates the emergency session to the network. The cases where the UE can't detect an emergency session shall also be supported.
7. The solution shall work if the UE has sufficient credentials to authenticate with the IMS and is registered to the IMS or is not registered with the IMS. The case where the UE does not have sufficient credentials to authenticate with the IMS shall also be supported if required by local regulation.
In the case that UE is not already IMS registered, it shall perform a registration for the support of emergency services (emergency registration).
In the case a UE is already IMS registered, the UE may skip the additional emergency registration if the UE is aware that it is in its home network (e.g. including IP-CANs where roaming outside the home network is not supported).
If the UE does not have sufficient credentials to authenticate with the IMS it shall be possible to perform session establishment without an existing security association between UE and P‑CSCF and the UE shall include an equipment identifier (the specific details of the equipment identifier to use may depend upon the IP-CAN) in the request to establish an emergency session.
Subject to local regulation or operator policy, the network and the UE shall support the same authentication and security methods for an emergency service request as for non-emergency requests.
8. It shall be possible to reject emergency service requests from an UE, without sufficient credentials to authenticate with the IMS in networks where emergency services from UEs with sufficient credentials to authenticate with the IMS are required.
9. Emergency Service is not a subscription service.
9a. When the UE has roamed out of its home network, emergency services shall not be provided by the home network and shall be provided in the roamed-to network if the roamed-to network supports emergency sessions. If a UE has sufficient credentials, it shall initiate an emergency registration with the network (requiring the involvement of the home network). The CSCFs providing service for emergency sessions may be different from the CSCFs involved in the other IMS services. If the registration fails and if the serving IMS has indicated support for anonymous IMS emergency sessions as part of the IMS registration failure, the UE shall attempt an anonymous emergency session. If the IMS registration fails and if the serving IMS has not indicated support for anonymous IMS emergency sessions as part of the IMS registration failure, the UE may attempt an anonymous IMS emergency session.
NOTE 2: UEs compliant with pre-Rel‑14 versions of this specification are unable to interpret this indication and ignore the indication. Such UEs might attempt an anonymous IMS emergency session or proceed according to Annex H.5.
10. If an emergency session establishment request is routed to a P‑CSCF located in the home network, the home network should be able to detect that the session is for emergency service (whether indicated as such or not) and respond to the UE indicating that the UE should initiate an emergency session in the visited network (e.g. via the CS domain of the visited network).
11. Emergency centres and PSAPs may be connected to the PSTN, CS domain, PS domain or any other packet network.
12. The architecture shall enable emergency centres and PSAPs to request a PSAP call back to a UE with which the Emergency centres or PSAPs had an emergency session. The serving network of the UE shall use the appropriate call termination procedures e.g. IMS if the UE is available for voice over PS, or ICS if the user is available over CS. PSAP call back is subject to local regulation.
NOTE 3: PSAP call back sessions are treated as normal calls.
NOTE 4: Subject to local regulation, any supported media can be used during a call back attempt from a PSAP.
13. The IMS core network shall be able to transport information on the location of the subscriber.
14. Void.
15. The network shall be able to retrieve the caller's location;
16. As a regional option, the network shall be capable of assigning a routable location key (i.e. Emergency Services Query Key, a.k.a. ESQK, which has the same properties as the existing ESRK in wireless 911 services) to an IMS emergency session and releasing the ESQK when the emergency session is terminated.
17. The network shall provide the caller's location information to the PSAP upon query from the PSAP.
18. The network shall provide the possibility to route to a default answering point given the scenario where the local PSAP can not be determined.
19. The network may provide a capability to enable a UE to obtain local emergency numbers.
20 A UE should support a capability to obtain local emergency numbers from the network once such a capability has been defined and agreed.
21. The network (e.g. in the E‑CSCF) shall prevent the sending of the information of the users, such as public user identifiers and the location information, to the PSAP if explicitly requested by the user (i.e. request on session by session basis) and local regulation requires the operator to provide privacy to the user.
22. Void.
NOTE 5: TS 24.008 [13] contains a procedure to provide local emergency numbers for UMTS and GPRS access but the procedure is not applicable to cdma2000 HRPD and contains a limited number of emergency service categories.
23. Void.
24. Subject to operator policy, the architecture shall allow an emergency session to be initiated by a trusted AS on behalf of a user that is not roaming.
25 Subject to local regulation, for non-roaming subscribers the network shall apply normal routing procedures for private network traffic even if that is marked as emergency session.
26. When a call is established with a PSAP that supports voice only, voice media is supported and GTT if required by local regulation or operator policy.
27. When a call is established with a PSAP that supports voice and other media, voice, GTT and other media according to TS 22.101 [8] (e.g. video, session mode text-based instant messaging) can be used during an IMS emergency session if required by local regulation. This media may be used in addition to or instead of voice and/or GTT.
28. NG-eCall is a variant of IMS emergency services and follows the same principles, architecture and procedures as other emergency services over IMS.
29. An originating network that is processing an emergency session shall, if configured through operator policies, invoke an AS for the signing of attestation and identity information and Resource-Priority information, if available in the incoming request. The originating network shall include the signed information in the outgoing emergency request.
30. A network serving a UE receiving a PSAP call back shall, if configured through operator policies, invoke an AS for the verification of signed caller identity information and Resource-Priority information, if available in the incoming request.
In addition to the architectural requirements, the following architectural principles apply to IMS emergency sessions:
- The IMS network shall be able to discriminate between emergency sessions and other sessions. This shall allow special treatment (e.g. with respect to filtering, higher priority, routing, QoS, supplementary services interactions) of emergency sessions.
- If a visited network can support PS emergency service, the emergency session shall be established in the visited network whether or not UE is registered in IMS in the home network.
- When a UE using public network traffic initiates an emergency session, the P‑CSCF is the IMS network entity, which is responsible to detect the request for emergency session. The P-CSCF then forwards the request to E‑CSCF in the same network, unless authentication and security procedures (see principle #7) require the request to be forwarded to the S-CSCF in the same network.
NOTE 6: While in the home network, forwarding of an emergency session to the S-CSCF is only expected over a non-emergency registration.
- The P‑CSCF serving the emergency call is the IMS network entity which may retrieve the location identifier from the IP-CAN. For emergency sessions initiated by a trusted AS on behalf of a non-roaming subscriber, the AS may provide the location identifier.
- The P‑CSCF serving the emergency call is the IMS network entity which may receive additional caller related identifier(s) from the IP-CAN (e.g. IP-CAN level's subscriber ID). If required by local regulation, these additional identifier(s) shall be forwarded by the IMS network to the emergency control centre/PSAP for those UEs that have not been authenticated by IMS network and are requesting to establish an emergency session,
- The E‑CSCF is the IMS network entity, which shall be able to retrieve geographical location information from the LRF in the case that the geographical location information is not available and is required.
- If required, the E‑CSCF shall be able to forward the location information to the LRF for validation of geographical location information in the case that the geographical location information is included by the UE over any access network type.
- The E‑CSCF is the IMS network entity, which is responsible to route the request to an emergency centre/PSAP via or BGCF, IBCF or IP multimedia network based on location information and additionally other information such as type of emergency service in the request.
- As a regional option where the emergency centre/PSAP is connected to the IMS of another network (e.g. TTC spec), emergency sessions may be routed over Inter-IMS Network to Network Interface between two IM CN subsystem networks.
- The architecture shall allow for compliance with other regional regulations (i.e. ATIS and NENA specs in North America region) in which the originating network shall have the ability to route an emergency call via an IBCF to an emergency services network.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
4.2 Naming and Addressing
|
When a UE performs an emergency registration, barring and roaming restrictions are ignored. The implicit registration set of the Public User Identifier used for emergency registrations shall contain an associated TEL‑URI.
NOTE: Annex G provides recommendations for the provisioning of TEL‑URI(s) in the IMS subscription for the purposes of IMS emergency sessions.
When a call is initiated to a PSAP from a UE without credentials, the E-CSCF shall derive a non-dialable callback number where required by local regulation (e.g. see Annex C of ANSI/J‑STD‑036 B [23]).
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
4.3 Location information for Emergency Sessions
|
Location information is needed for 2 main reasons in emergency services. The initial purpose of the location information is to enable the IMS network to determine which PSAP serves the area where the UE is currently located, so that the IMS network can route the emergency session to the correct PSAP. The second purpose is for the PSAP to get more accurate or updated location information for the terminal during or after the emergency session where required by local regulation.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
4.3.1 General Location Information Principles
|
The following general principles shall apply regarding the handling of location information:
- If the UE has location information available, the UE shall include the location information in the request to establish an emergency session. The location information may consist of network location information, that is the Location Identifier and/or the Geographical location information.
NOTE 1: For untrusted non-3GPP access to 5GC, provided location information can only correspond to the UE IP address seen by the N3IWF and used for traffic destined towards the UE.
NOTE 2: For NR satellite access to 5GC, an NR CGI (NCGI) provided in the location information by the UE can differ from the NCGI provided by NG-RAN and the area indicated by the former NCGI can differ from the area indicated by the latter NCGI.
- The P‑CSCF may query the IP‑CAN to obtain location identifier.
- If a trusted AS is used for the emergency session, the AS may provide the location identifier.
- When an emergency session is coming from a private network, it is assumed that the private network includes the initial location information in the request to establish an emergency session and subsequent location information as requested.
The E‑CSCF, if required, may query the LRF for additional location information. If the E‑CSCF does not receive location information in the emergency service request, it may query the LRF for location information.
- The E‑CSCF shall be able to query the LRF to validate the location information if provided initially by the UE.
- For WLAN access, the LRF may query HSS for NPLI if the UE is not roaming. In some regions, for example in the North American region [45], if the BSSID of the serving WLAN is available, the LRF may query a database subject to national regulations and operator policies for the dispatchable location associated with the BSSID of the WLAN Access Point.
- The E‑CSCF routes the emergency request to the PSAP/Emergency Centre that corresponds to the type of emergency service requested and to the type of emergency service requested and to the current location of the UE or to a default PSAP/Emergency Centre. The access dependent variations of this approach are described in the respective access specific annexes, for the cases where the UE is using GPRS (UTRAN), EPS (UTRAN and E-UTRAN), 5GS (NG-RAN), fixed broadband access, WLAN access to EPC or non-3GPP access to 5GC for the emergency service.
- The E‑CSCF forwards the SIP request containing the UE's location information to the PSAP/Emergency Centre via PS domain or via BGCF/MGCF through the CS domain. The location information can contain explicit location information and/or a reference key to allow the PSAP to retrieve location at a later stage.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
4.3.2 Void
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
4.4 IP-CAN
|
The following are the expectations on the IP-CAN for IMS emergency services:
- Except for emergency services over WLAN access to EPC or non-3GPP access to 5GC, it shall be possible to access the IP-CAN without sufficient security credentials.
- It shall be possible to reject requests from UE without sufficient security credentials to establish bearer resources.
- In the case that the IP-CAN receives a request to establish bearer resources for emergency services, it shall be possible for the IP-CAN to prioritise emergency services traffic. PCC (Policy and Charging Control) methods may be used to inform the IP-CAN and request appropriate handling of the emergency service. The QoS information for emergency traffic is specified in TS 23.203 [20].
- In the case that the IP-CAN receives a request to establish bearer resources for emergency services, the IP-CAN shall ensure that the IP flows using the requested resources are only for communication with the network entities involved in the support of the emergency services. Applicable service data flow filters for emergency traffic need to be defined by the operator according to the details described in TS 23.203 [20].
- In the case that the IP-CAN receives a request to establish bearer resources for emergency services, the IP-CAN may provide additional identifier(s) to IMS network (e.g. IP-CAN level's subscriber ID).
- The IP-CAN may support emergency services free of charge. Applicable PCC rules need to be defined by the operator according to the details described in TS 23.203 [20].
- The IP-CAN may provide emergency numbers to the UE in order to ensure that local emergency numbers are known to the UE (see TS 22.101 [8]).
If the IP-CAN is a GPRS (UTRAN) network, the detailed procedures are described in TS 23.060 [2]. If the IP-CAN is an EPS (UTRAN and E-UTRAN) network, the detailed procedures are described in TS 23.401 [28] and TS 23.060 [2] and in Annex H. If the IP- CAN corresponds to WLAN access to EPC, the detailed procedures are described in TS 23.402 [29] and in Annex J. If the IP-CAN is a 5GS (NG-RAN) network, the detailed procedures are described in TS 23.502 [49] and in Annex H. If the IP-CAN corresponds to non-3GPP access to 5GC, the detailed procedures are described in TS 23.502 [49] and in Annex L.
The emergency support in different IP-CAN scenarios is described in the Informative Annex E.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
4.5 Media
|
- When the call is established with a PSAP that supports voice only, voice and subject to local regulation, GTT media is allowed during the IMS emergency session.
- When the call is established with a PSAP that supports voice and other media, subject to UE and network support for the other media and local regulation, voice, GTT and other media according to TS 22.101 [8] can be used during the IMS emergency session.
- For sessions with a PSAP that supports voice and other media, media can be added, modified or removed during the IMS emergency session (e.g. adding video to a voice call) per media negotiation in TS 23.228 [1].
- When a PSAP that supports voice and other media attempts to add media, the media shall be added if accepted by the UE.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
5 Architecture model and reference points
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
5.1 Reference architecture
|
This specification introduces an additional CSCF role to those defined in the IMS architecture TS 23.002 [12], called Emergency CSCF (E‑CSCF), see figure 5.1.
Legend:
Dashed lines: optional interfaces
Figure 5.1: E‑CSCF in reference architecture
NOTE 1: P‑CSCF, MSC Server enhanced for ICS, EATF and E-CSCF are always located in the same (serving) network; this is the visited network when the UE is roaming. For emergency session initiation, the S-CSCF and AS are only applicable for non-roaming cases.
NOTE 2: For simplicity, not all functional components, e.g. IBCF, MGCF and BGCF, are shown in this figure.
NOTE 3: Based on operator policy, the E‑CSCF can route the emergency IMS session to the PSAP via an ECS. See the details in Annex D.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
5.2 Reference points
|
The E‑CSCF uses Mw, Mg, Mi, Ml, Mm, Mx and I4 reference points to connect to other IMS entities and other IP Networks.
I4 is a reference point between an E-CSCF and an EATF. See TS 23.237 [32].
I5 is a reference point between an I‑CSCF and an EATF. See TS 23.237 [32].
I6 is a reference point between an MSC Server enhanced for ICS and E-CSCF. See TS 23.292 [46].
Sh is a reference point between LRF and HSS. See TS 29.328 [43].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6 Functional description
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.1 UE
|
- Should be able to detect an emergency session establishment request.
- In the case of NG-eCall, the IMS emergency session establishment request may be invoked either automatically without user input or manually via user input.
- Initiate an IMS emergency registration request.
- The UE may perform an IMS emergency session establishment without prior emergency registration when already IMS registered and it is in home network (e.g. including IP-CANs where roaming outside the home network is not supported).
- Otherwise, the UE shall perform an IMS emergency registration.
- Include an emergency service indication in the emergency session request.
- UE may support the GIBA procedure defined in TS 24.229 [19] as part of the emergency IMS registration procedure.
- In the case of emergency IMS registration failure the UE shall be able to interpret the indication, if provided by the serving IMS, whether anonymous IMS emergency sessions are supported in the serving IMS. If the serving IMS has indicated support, the UE shall proceed with an anonymous IMS emergency session, otherwise it proceeds according to clause H.5.
NOTE 1: UEs compliant with pre-Rel‑14 versions of this specification are unable to interpret this indication and ignore the indication. Such UEs might attempt an anonymous IMS emergency session or proceed according to clause H.5.
- Include an equipment identifier in the request to establish an emergency session for "anonymous user".
NOTE 2: "Anonymous user" in this context is the person who does not have sufficient credential for IMS registration. No Stage 3 work is expected as the anonymous user detection already existed today.
- Include an equipment identifier in the request to establish an emergency session when the UE supports SRVCC as specified in TS 23.237 [32].
- Include identity information for the IP-CAN if available (e.g. MCC-MNC or an equivalent)
NOTE 3: UE provided IP-CAN identity information will not be completely reliable.
- Attempt the emergency call in CS domain, if capable.
- Handle a 380 (Alternative Service) response with the type set to "emergency" e.g. as a result of non UE detectable emergency attempt.
- Handle a response with an indication, IMS emergency registration required as a result of emergency session establishment attempt.
- Other general requirements of UE shall be referred to the general requirements of emergency calls in TS 22.101 [8].
- For NG-eCall, where transfer of the MSD is not acknowledged by the PSAP, the UE shall fall back to the in-band transfer of the MSD, as in CS domain defined in TS 26.267 [42].
The UE initiates the emergency session establishment request and for the purpose of processing the request properly in the network, the following specific information is supplied in the request message.
- Emergency service indication.
- A registered Public User Identifier. If the UE performed an emergency registration using a temporary Public User Identifier then the UE should not use the temporary Public User Identifier to initiate the emergency session. The selected Public User Identifier shall be part of an implicit registration set that includes a TEL‑URI.
NOTE 4: The UE can be preconfigured with information to select the appropriate Public User Identifier if more than one Public User Identifier is provisioned in the UE.
- Optionally, type of emergency service. It could be implied in the above emergency service indication.
- For an NG-eCall an eCall indication including whether eCall is automatic or manual.
- A UE that supports test eCall, should be able to detect an IMS call request of the test eCall type and shall reject the request if the UE is in limited service state. A UE not in limited service state performs domain selection same as for a normal IMS call as defined in TS 23.221 [60] and TS 23.501 [48]. If the IM CN subsystem is selected and the UE is not currently registered, the UE shall perform an initial registration. The requirements for a UE supporting test eCall are further specified in clause 5.1.6A of TS 24.229 [19].
- UE's location information, if available.
- The TEL‑URI associated to the Public User Identifier, if available.
- GRUU, if available.
In the case of a non UE detectable emergency call, upon reception of indication from the network, the UE shall handle the call as described in clause 7.1.2.
NOTE 5: If the indication was received in a rejection message the UE performs appropriate emergency error handling procedures.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2 IMS Functional entities
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.1 Proxy‑CSCF
|
- Handle registration requests with an emergency registration indication like any other registration request, except that it may reject an emergency registration request if the IM CN subsystem that the P‑CSCF belongs to can not support emergency sessions for the UE (e.g. due to operator policy or UE is not within IM CN subsystem's geographical area or IP-CAN not supported).
- Detect an emergency session establishment request.
- Reject/allow unmarked emergency requests.
- Reject/allow anonymous emergency requests.
- Prevent non-emergency requests that are associated with an emergency registration.
- May query IP-CAN for location identifier.
- May query IP-CAN for additional subscriber related identifier(s).
- Select an Emergency CSCF in the same network to handle the emergency session request. The selection method is not standardized in the present document.
- Alternatively, for non-roaming subscribers and when the request is received over a non-emergency registration, the P-CSCF may forward an emergency session to an S-CSCF if so instructed by operator policy or local regulation.
NOTE: This can be for example the case if the P‑CSCF recognizes that an emergency session was not received via a security association for a UE previously authenticated with digest type proxy authentication.
- Do not apply emergency session detection if requested using private network traffic and forward the session to the S-CSCF, except if operator policy requires the P-CSCF to detect emergency session requests and treat detected emergency session requests as if they are part of public network traffic.
- For UEs without credentials, forward the equipment identifier to the E-CSCF that was received from the UE.
- For UEs without credentials and subjected to local regulation, forward the additional subscriber related identifier(s) received from IP-CAN to the E-CSCF.
- Prioritize the emergency session.
- Check the validity of the caller TEL‑URI if provided by the UE and shall provide the TEL‑URI in the session establishment request if it is aware about the TEL‑URI associated with the Public User Identifier used for an emergency registration.
- May respond to a UE with an emergency service indication as a result of detecting a non UE detectable emergency session establishment request
- May respond to the UE with an indication, IMS emergency registration required as a result of processing the emergency session establishment attempt.
- Should be able to identify the service data flow associated with emergency service and inform PCRF accordingly.
- Upon IMS registration failure the P-CSCF may indicate to the UE whether anonymous IMS emergency sessions are supported.
- P-CSCF may, based on operator policy, insert attestation information related to the asserted calling identity associated with an emergency session, if operating in a network that supports calling number attestation and signing.
- P-CSCF may assert Resource-Priority information for an emergency session if configured through operator policies.
- For a test eCall as defined in Annex X, detect a session establishment request for a test eCall. The detection of test eCall can be based on e.g. Request-URI set to a configured value of non-emergency service URN (e.g. urn:service:test.sos.ecall).
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.2 Emergency‑CSCF
|
- Receive an emergency session establishment request from a P‑CSCF or an S-CSCF.
- If the UE does not have credentials, a non-dialable callback number shall be derived where required by local regulation (e.g. see Annex C of J‑STD‑036 [23]).
- If location information is not included in the emergency request or additional location information is required, the E‑CSCF may request the LRF to retrieve location information as described in clause 7.6 Retrieving Location information for Emergency Session.
- If required, the E‑CSCF requests the LRF to validate the location information if included by the UE.
- Determines or queries the LRF for the proper routing information/PSAP destination.
- Route emergency session establishment requests to an appropriate destination including anonymous session establishment requests.
- Subject to local regulation, the E‑CSCF may send the contents of the P-asserted ID or UE identification to the LRF.
- Based on operator policy, the E‑CSCF may route the emergency IMS call to ECS for further call process.
- For supporting SRVCC and/or DRVCC, see TS 23.237 [32] and TS 23.216 [31], the E CSCF forwards the session establishment request to the EATF in the serving IMS network for anchoring.
- Generation of CDRs.
- For an NG-eCall and if an LRF/RDF is not deployed, the E-CSCF may use an indication of an automatic eCall or a manual eCall to assist routing of an emergency session establishment request.
- For supporting emergency session request from MSC Server enhanced with ICS, see TS 23.292 [46]. E-CSCF follows the same procedure as defined for handling emergency session request from P-CSCF.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.3 Location Retrieval Function
|
The Location Retrieval Function (LRF) is responsible for retrieving the location information of the UE that has initiated an IMS emergency session. It shall be possible to support configurations where the Location Retrieval Function (LRF) may consist of a Routing Determination Function (RDF) and a LS, the interface between Location Server and RDF is out of scope of this specification. For WLAN access and for non-roaming UEs, if the LRF is configured then it may interact with HSS to provide an NPLI before interacting with the RDF. In some regions, for example in the North American region, ATIS-0700028 [45], if the BSSID of the serving WLAN is available, the LRF may query a database subject to national regulations and operator policies for the dispatchable location associated with the BSSID of the WLAN Access Point.
The LRF utilizes the RDF to provide the routing information to the E‑CSCF for routing the emergency request. The RDF can interact with a LS and manage ESQK allocation and management. The ESQK is used by the PSAP to query the LRF for location information and optionally a callback number. The LRF-PSAP interactions are outside the scope of this specification.
Information provided by the LRF to the E‑CSCF includes the routing information and other parameters necessary for emergency services, which are subject to local regulation. For example, this information may include the ESQK, ESRN, LRO in North America, location number in EU, PSAP SIP‑URI or TEL‑URI.
In order to provide the correct PSAP destination address to the E‑CSCF, the LRF may require interim location information for the UE.
In some regions, for example in the North American region, it may be a requirement to provide the PSAP with an accurate initial location estimate for the UE and possibly to provide an accurate updated location estimate for the UE if requested by the PSAP. When this requirement exists, the LRF may store a record of the emergency session including all information provided by the E‑CSCF and shall only release this record when informed by the E‑CSCF that the emergency session has terminated. The information provided by the LRF to the E‑CSCF (e.g. ESQK) shall then include correlation information identifying both the LRF and the emergency session record in the LRF. This correlation information shall be transferred to the PSAP during session establishment (e.g. in a SIP INVITE or via SS7 ISUP signalling from the MGCF). The PSAP may use this information to request an initial location estimate from the LRF and/or to request an updated location estimate.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.4 Serving-CSCF
|
When the S‑CSCF receives an Emergency Registration, the S‑CSCF determine the duration of the registration by checking the value of the Expires header in the received REGISTER request and based on local regulation or operator policy of the serving system.
NOTE 1: The value of the emergency registration time is subject to local regulation and can be subject to roaming agreements.
The emergency registration shall be handled as normal IMS registrations with the following considerations:
- Upon emergency registration:
- If a normal registration for the user does not exist, the S-CSCF shall download corresponding user profile from HSS to ensure that HSS allocates S-CSCF name to this subscriber and the registration status is set to UNREGISTERED.
- Otherwise, S-CSCF shall ensure that the registration status of the user is not changed in the HSS.
- Upon deregistration or expiration of the last normal session:
- If an emergency registration for the user still exists, the S-CSCF shall ensure that the HSS keeps S-CSCF name allocated to this subscriber and the registration status is set to UNREGISTERED.
- Upon expiration of an emergency registration:
- If a normal registration for the user still exists, the S-CSCF shall ensure that the registration status of the user is not changed in the HSS.
- Otherwise, the S-CSCF can either de-register the user in HSS or keep the registration status of the user unchanged in the HSS.
When an S-CSCF receives a session initiated by a non-roaming subscriber marked as emergency session from a P-CSCF, the S-CSCF:
- performs caller authentication in the same way as for any other sessions;
- if required, uses filter criteria to route to AS;
- and forwards the request to an E-CSCF.
When an S-CSCF receives a session marked as emergency session from an AS, the S-CSCF:
- if required, uses filter criteria to route to other ASs;
- and forwards the request to an E-CSCF.
NOTE 2: The AS can initiate an emergency request on behalf of a non-roaming user, can convert private network traffic to public network traffic, or can interpret a number in private numbering plan and detect that the request is for emergency session.
NOTE 3: Reception of a session initiation request marked as an emergency session from a P-CSCF and/or an AS by the S-CSCF is only expected over a non-emergency registration.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.5 Void
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.6 Emergency Access Transfer Function (EATF)
|
The EATF provides IMS emergency session continuity which is specified in TS 23.237 [32].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.7 Interrogating-CSCF
|
I-CSCF supports IMS emergency session continuity which is specified in TS 23.237 [32].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.8 AS
|
An AS can be involved in emergency session handling (e.g. for emergency sessions made via hosted enterprise services ETSI TS 182 024 [37], or for AS initiated session).
NOTE 1: The participation of an AS in emergency session handling is only expected over a non-emergency registration.
Dependent on the service provided by the AS, if the AS is the first point that identifies an IMS emergency session, then the AS shall provide the following emergency session handling functions:
- Detect an emergency session establishment request.
- Verify that the UE is not roaming.
- Optionally obtain location.
- Prioritize the emergency session.
- Provide in the session establishment request the TEL URI associated to the public user identity, in global format, if known and not already present.
- Check the validity of the caller TEL URI if provided by the UE.
- Mark the request as an emergency session request.
NOTE 2: If the AS converts a request marked as private network traffic to public network traffic and the request is marked by the AS as emergency session, the AS routes the request back to the S-CSCF, which will forward the request towards a public PSAP. If a request is targeted to a private PSAP, then it is marked as private network traffic and normal routing procedures in the IMS network will deliver the request to its target, possibly with priority handling if mandated by local regulations.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.9 HSS
|
In the course of an emergency registration, the HSS shall not apply any barring condition and/or roaming restriction associated with the Public User Identity received in the emergency registration request.
The emergency registration shall be handled with the considerations defined in clause 6.2.4.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.10 Media Gateway Control Function (MGCF)
|
For NG-eCall MGCF handles the emergency session as normal emergency call establishment.
NOTE: The MGCF does not forward the initial MSD, if received in the emergency session request.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.11 MSC Server enhanced with ICS
|
The MSC Server enhanced with ICS may provide interworking mechanisms to support emergency call using CS media bearer and using IMS for routing/handling the emergency call toward PSAP. From the view point of E-CSCF, MSC Server enhanced with ICS behaves like a P-CSCF. Further details on MSC Server procedure are defined in TS 23.292 [46].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
6.2.12 IBCF
|
- Forward emergency session establishment requests.
- Prioritize the emergency session based on operator policy.
- For an emergency session leaving an IBCF, the IBCF, if configured through operator policies, invokes an AS for the signing of attested caller identity and asserted Resource-Priority information, if available in the incoming request. The IBCF includes the signed information in the outgoing request.
- For a call back received by an IBCF, the IBCF, if configured through operator policies, shall invoke an AS for the verification of Resource-Priority information, if available in the incoming request.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7 Procedures related to establishment of IMS emergency session
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.1 High Level Procedures for IMS Emergency Services
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.1.1 UE Detectable Emergency Session
|
The following flow contains a high level description of the emergency service procedures performed when the UE can detect the emergency session is being requested.
Figure 7.1: Terminal Detected Emergency Calls
The following steps are performed:
1. The UE detects the request for the establishment of an emergency session. Step 2 to 6 may be skipped based on the conditions specified in clause 6.1.
2. In the case that the UE has insufficient resources or capabilities to establish an emergency call due to other ongoing sessions then the UE should terminate the ongoing communication and release reserved bearer resources.
3. In the case that bearer registration is required and has not been performed, the UE shall perform bearer registration to the IP-CAN. If the UE is already bearer registered, then the bearer registration procedures are not required to be performed.
NOTE 1: Depending on the IP-CAN, the UE may be assigned an IP address at this stage.
4. In the case that bearer resources for the transport of the IMS related signalling are required to be reserved in the IP-CAN, the UE shall reserve the resources in the IP-CAN. The IP‑CAN may support a UE indication that this request is for an emergency service.
If the IP-CAN does not provide an IP address to the UE in step 3, then the IP-CAN shall allocate an IP address to the UE during the bearer resource request procedures.
5. UE performs a P‑CSCF discovery procedure, where the UE discovers a P‑CSCF in the local network suitable for use in emergency sessions.
NOTE 2: The exact means for the P‑CSCF discovery is dependent upon the IP-CAN.
6. If the UE has sufficient credentials to authenticate with the IMS network, it shall initiate an IMS emergency registration by providing the IP address obtained at step 3 or step 4 to the P‑CSCF selected at step 5. The IP address used for signalling purposes is allocated in association with step 3 or step 4. The IMS registration request shall include an emergency indication. The implicit registration set of the SIP URI used in the emergency registration request used by the UE when the UE performs a non-emergency registration shall contain an associated TEL‑URI that is used to call back the UE.
The S‑CSCF may set the proposed registration expiration according to the local regulation or operator policy of the serving system. The subsequent registration flows are like any other registration with the considerations defined in clauses 6.2.4 and 6.2.9.
If the UE does not have sufficient credentials to authenticate with the IMS network, it shall not initiate an IMS emergency registration request, but instead immediately establish an emergency session towards the P‑CSCF as described in clause 7.4 and skip step 7.
7. The UE shall initiate the IMS emergency session establishment using the IMS session establishment procedures containing an emergency service indication, or the eCall type of emergency service indication in the case of eCall and any registered Public User Identifier. If the UE has performed emergency registration, the UE shall use an emergency registered Public User Identifier.
Whether the procedures are activated individually by the UE or some of them are performed automatically depends on the implementation of the terminal and on the UE's configuration. For instance, the multimedia application in the UE could start the application level registration and steps 2-4 would have to be executed in response to support the operation initiated by the application. Interaction with the UE may happen during these steps.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.1.2 Non UE detectable Emergency Session
|
As the UE could not detect the emergency session, the session establishment request will be sent to a P‑CSCF in the visited PLMN or a P‑CSCF in the home PLMN as per a normal session establishment procedure. The former is only applicable to a roaming situation whereas the latter can apply to both a roaming and non-roaming situation and for the case of SNPN. Prior to sending the session establishment request the UE must be registered in the IMS as per the normal registration procedure.
In the case that the P‑CSCF detects that this is a request to establish an emergency session, based upon operator policy (e.g. checking access type):
- the P‑CSCF may reject the session initiation request with an indication that this is for an emergency session. When the UE receives the session rejection then the UE shall:
- select a domain for the emergency session;
- if the PS domain is selected, follow the procedure in clause 7.1.1;
- for systems based on TS 24.008 [13], if the CS domain is selected and a dialled number is available, attempt a normal call (i.e. TS 11, see TS 22.003 [26]) using the dialled number if:
- an emergency service information is included by the P-CSCF with either a country specific emergency subservice type (see TS 24.229 [19]) or a emergency subservice type (see TS 24.229 [19]) that does not map into an emergency service category for the CS domain; or
- no emergency service information is included by the P-CSCF;
- for systems based on TS 24.008 [13], if the CS domain is selected, attempt an emergency call (i.e. TS 12, see TS 22.003 [26]) if:
- a dialled number is not available; or
- an emergency service information is included by the P-CSCF with no emergency subservice type or a emergency subservice type (see TS 24.229 [19]) that maps into an emergency service category for the CS domain;
- if the CS domain is selected and for CS systems that do not support emergency call handling procedures (e.g. as described by TS12 in TS 22.003 [26] for systems based on TS 24.008 [13] or in systems providing access to IM CN subsystem using a cdma2000 network, for example) a normal call is made;
- If prior attempting the call in the CS domain the UE receives a list of local emergency numbers, the UE may verify if and recognizes the dialled number is an emergency number and if verified, the UE shall attempt an emergency call set up indicating the appropriate emergency call type.
- Alternatively, the P‑CSCF in the visited PLMN or the P‑CSCF in the home PLMN for a non-roaming UE may allow the session initiation request to continue by inserting the explicit emergency indication in the session request. The P-CSCF in the visited PLMN forwards that request to an Emergency CSCF in the same network. The P-CSCF in the home PLMN for a non-roaming UE may forward that request to a Serving CSCF or to an Emergency CSCF in the same network, based on local regulation or operator policy. The E‑CSCF shall inform the UE that the session has been marked as an emergency session so the UE can treat the session as an emergency session establishment.
- For the case when a SNPN uses IMS services provided by an independent IMS provider, the P-CSCF is located in the IMS provider network according to TS 23.228 [1], Annex A.
If the AS detects that this is a request to establish an emergency session, the AS shall handle the request as specified in clause 6.2.8 and forward the request marked as an emergency services request to the S-CSCF.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.1.3 Emergency Session Establishment using LRF/RDF
|
Figure 7.2 illustrates a high level call flow for the IMS emergency session establishment procedure using LRF/RDF to retrieve location and routing information.
Figure 7.2: Emergency Session Establishment procedure with using LRF/RDF
1. UE initiates an emergency session request by sending a SIP INVITE message with including emergency URI.
2. If required, the IMS network may access the LRF to retrieve the UE's location. For WLAN access and for non-roaming UEs, if the LRF is configured then it may interact with HSS to provide an NPLI. In some regions, for example in the North American region, ATIS-0700028 [45], if the BSSID of the serving WLAN is available, the LRF may query a database subject to national regulations and operator policies for the dispatchable location associated with the BSSID of the WLAN Access Point.
NOTE 1: The details of the LRF querying a national database (e.g. in North America) are outside the scope of this specification.
3. If required, LRF invokes the RDF to determine the proper PSAP destination. LRF returns the necessary location/routing information (e.g. ESQK for North America or location number for EU) to the IMS network.
4. The IMS network uses the routing information returned by the LRF to route the emergency session request towards the appropriate PSAP.
NOTE 2: If the LRF provides an ESQK to the IMS network in step 3 or assigns any other dedicated resource to the emergency session, the IMS network shall inform the LRF when the session is released in order to allow the LRF to release this resource.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.2 IMS Registration for Emergency Session
|
The IMS emergency registration procedure shall follow the procedures as described in clause 5.2.2.3 of TS 23.228 [1] with the following modifications:
- The UE shall initiate an IMS emergency registration when all of the following conditions are met:
- either the UE is not already IMS registered or the UE is IMS registered but is roaming outside its home network;
- the UE has sufficient credentials to authenticate with the IMS network;
- the UE is able to detect emergency session.
The UE shall also initiate an IMS emergency registration when it receives an "IMS emergency registration required" response as a result of the emergency session request:
- If the UE initiates an IMS emergency registration, it shall first initiate an emergency access to the IP-CAN if emergency access has been defined for the particular type of IP-CAN. This is to ensure that the session attempt is handled in the VPLMN when the UE is roaming and provides appropriate priority treatment and access to appropriate network elements (e.g. to a particular PDG or UPF and P‑CSCF in the VPLMN).
- If the UE had already performed an emergency access when it receives an "IMS emergency registration required" response as a result of an emergency registration or emergency session request, it shall perform an emergency access followed by an emergency registration using a different VPLMN or SNPN if available to prevent looping.
- The UE shall use an indication in the emergency registration request. This indication may be used to inform the home network that roaming restrictions may not be applied.
- The user's home network should ignore roaming restrictions for emergency registration requests.
P‑CSCF handles the registration requests with an emergency indication like any other registration request.
The S‑CSCF in the home network may modify the received registration expiration value from the request according to local regulation or operator policy in the serving system. The subsequent registration flows are like any other registration with the considerations defined in clauses 6.2.4 and 6.2.9.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.3 Emergency Session Establishment in the Serving IMS network
|
If the UE is able to detect that the user is requesting an emergency session then it shall include an emergency service indication in the emergency session establishment request. In the case of NG-eCall, the UE shall include the eCall type of emergency service (automatic or manual) in the emergency session establishment request.
The UE shall follow the requirements in TS 22.101 [8] for domain priority and selection when UE attempts to make an emergency call.
For an attempt in the IM CN Subsystem of the PS domain, the attempt should be in the serving (visited if roaming) IM CN Subsystem of the PS domain.
If the initial attempt is in the CS domain and it fails, the serving (visited if roaming) IM CN Subsystem of the PS domain shall be attempted if the UE is capable and if not disallowed by applicable domain selection rules. If the initial attempt is in the IM CN Subsystem of the PS domain and it fails, the UE shall make the attempt in the CS domain (if the UE is capable and if for an appropriate service e.g. voice).
If the UE is aware that it does not have sufficient credentials to authenticate with the IMS network, it shall not initiate an IMS registration but immediately establish an emergency session towards the P‑CSCF, see clause 7.4.
Upon receiving an initial request for an emergency session, the P‑CSCF shall follow the rules and procedures described in TS 23.228 [1] with the following additions and clarifications:
- When a UE using public network traffic initiates an emergency session, the P‑CSCF is the IMS network entity, which detects an emergency session.
- For the case that the initial request carries an indication that the request is for emergency services and the UE is not registered in the IMS network, see clause 7.4 for details.
- For the case that UE is IMS registered and the initial request does not carry an indication that the request is for emergency services and the P‑CSCF is able to detect that the request is for emergency services, the P‑CSCF shall perform the "Non UE detectable Emergency Session" described in clause 7.1.2 above.
- For the case that the initial request carries an indication that the request is for emergency services and the UE is registered in the IMS network, but not performed emergency registration:
a) the P‑CSCF shall reject the request indicating that IMS emergency registration required, if the UE is roaming;
b) the home P‑CSCF may reject the request indicating that IMS emergency registration required, based on operator policy.
- On receipt of a session establishment request, which is recognized to be for an emergency service, the P‑CSCF shall check whether the UE provided a TEL‑URI as its identity in the request. If a TEL‑URI is present in the request, the P‑CSCF shall check the validity of this TEL‑URI. If no TEL‑URI is present in the request and the P‑CSCF is aware about the TEL‑URI associated with the emergency registration, it shall provide the TEL‑URI to the E‑CSCF in the session establishment request.
- A P-CSCF operating in a network that supports calling number attestation and signing may, based on operator policy, be responsible for inserting attestation information related to the asserted calling identity associated with an emergency session.
- The P‑CSCF may query the IP-CAN for the location identifier.
- P‑CSCF shall prioritize emergency sessions over other non-emergency sessions.
- A P-CSCF may assert Resource-Priority information for an emergency session, if configured through operator policies.
- Emergency IP flows need to be identified by P‑CSCF in the Rx interface signalling to allow the PCRF to prioritize emergency service data flows over non-emergency service data flows within IP‑CAN. The detailed procedures are specified in TS 23.203 [20].
Handling of emergency sessions detected by an AS is specified in clause 6.2.8.
For the case where the emergency session is provided via the interconnect from a private network (as defined in ETSI TS 182 025 [38]), the following procedures apply:
- For private network traffic where operator policy allows so, do not apply emergency session detection and forward the session according to normal procedures.
- Otherwise emergency sessions within the IMS are routed to the PSAP via the E-CSCF.
Upon receiving an initial request for an emergency session, the E‑CSCF shall perform the following:
- if location information is not included in the emergency service request or if additional location information is required, the E‑CSCF, if required, retrieves the UE's location information as described in clause 7.6 Retrieving Location information for Emergency Session.
- If location information is included by the UE, the E‑CSCF, if required requests the LRF to validate the location information.
- May determine or may request the LRF to determine the appropriate routing information which could be based on the type of emergency service requested, the UE's location and any indication of an eCall.
- determine the default PSAP destination if routing based on UE's location is required but the location is unknown.
- If the PSAP/emergency centre contains a point of presence within the IMS connectivity network, the E‑CSCF shall forward the emergency session initiation request directly to the PSAP/emergency centre, including any additional subscriber related identifier(s) received from P-CSCF.
- If the PSAP/emergency centre has its point of presence in the PSTN/ISDN network or the CS domain, the E‑CSCF uses the TEL‑URI obtained from the LRF and forwards the request to an appropriate BGCF/MGCF for routing in the GSTN. This number shall have the same format as used for CS emergency calls. The MGCF may insert any available location information in the PSTN/CS signalling.
NOTE: If an ESRN is received from the LRF, the E‑CSCF maps the received ESRN from the LRF to a TEL-URI before forwarding the request to MGCF.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.4 IMS Emergency Session Establishment without Registration
|
When the UE initiates an emergency session establishment without prior IMS registration, it shall include both the "anonymous user" and "emergency service" indications in the emergency session establishment request to the P‑CSCF.
Based on local regulation, the P‑CSCF may reject "anonymous user" emergency session establishment with appropriate error code. UE shall not reattempt the "anonymous user" emergency session again via the same network.
When P‑CSCF accepts the "anonymous user" emergency session establishment, it forwards this request to an appropriate E‑CSCF although no security association between UE and P‑CSCF is established. Based on local regulation, P‑CSCF may retrieve additional subscriber related identifier(s) from IP-CAN and forward those identifiers to E-CSCF. Prior to forwarding the request to an appropriate E-CSCF, the P-CSCF may assert Resource-Priority information for an emergency session if configured through operator policies.
The E‑CSCF shall follow the same rules and procedure as defined for the Emergency Session Establishment in the Serving IMS network in clause 7.3 to route the anonymous emergency session.
Where required by local regulation, the E-CSCF shall derive a non-dialable callback number to include as the UE's identity in the session establishment request and the location/routeing request (e.g. see Annex C of J‑STD‑036 [23]).
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.5 Interworking with PSAP
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.5.1 PSAP/Emergency centre located at the GSTN
|
No special procedure is defined. PSAP uses the MSISDN (E.164) of the user for call back. Emergency call and call back feature interactions are handled as specified in TS 22.101 [8].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.5.2 PSAP/Emergency centre connected via IP using SIP
|
No special procedure is defined. PSAP uses any public user identity that it has received from the user for call back. Emergency call and call back feature interactions are handled as specified in TS 22.101 [8].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.5.3 PSAP/Emergency centre connected via ECS
|
No special procedures are identified in IMS Core, the routing determination will be performed by the ECS. Emergency call and call back feature interactions are handled as specified in TS 22.101 [8].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.5.4 PSAP supporting NG-eCall
|
It is assumed that the PSAP supporting the NG-eCall shall be able to receive and verify the consistency of the initial MSD within the initial SIP INVITE.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.6 Retrieving Location information for Emergency Session
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.6.1 Acquiring location information from the UE or the network
|
When performing an emergency service, four scenarios for retrieving location information for routing purposes are considered:
- the UE knows its own location;
- the UE retrieves its location information from the network;
- the IMS core retrieves the location information. The related high level procedures are described below;
- location information is not needed to route the emergency call by the IMS core, optionally the emergency routing determination and location information retrieval may be performed by the Emergency Call Server (ECS) as part of the emergency session establishment procedure. In this case, the IMS core does not need to obtain the location information. See the details in Annex D.
Figure 7.6-1: Handling of location information in IMS emergency calls
1. The user initiates an emergency call.
2. The UE determines its own location or location identifier if possible. If the UE is not able to determine its own location, the UE may, if capable, request its location information from the IP-CAN, if that is supported for the used IP-CAN. If applicable, the IP-CAN delivers to the UE the UE's geographical location information and/or the location identifier.
3. The UE sends an INVITE with an emergency indication to the IMS core. The INVITE should contain any location information that the terminal has. The location information may be geographical location information or a location identifier, which is dependent upon the access network technology. If the UE is not able to provide any location information, the IMS core may seek to determine the UE's location from the LRF as described below. The INVITE may optionally contain information concerning the location solutions and position methods supported by the UE.
NOTE: The location solutions and position methods conveyed in the INVITE and the means of inclusion in the INVITE are outside the scope of this specification.
4. If the location information provided in step 3 is trusted and sufficient to determine the correct PSAP, the procedure continues from step 7 onwards. If the location information is insufficient or if the IMS core requires emergency routing information, or if the IMS core is required to validate the location information, or if the IMS core is required to map the location identifier received from the UE into the corresponding geographical location information, the IMS core sends a location request to the LRF. The request shall include information identifying the IP-CAN and the UE and may include means to access the UE (e.g. UE's IP address). The request shall also include any location information provided by the UE in step 2. The request may optionally include any information concerning the location solutions and position methods supported by the UE.
5. The LRF may already have the information requested by IMS core or LRF may request the UE's location information.
5a. The means to obtain the location information may differ depending on the access technology the UE is using to access the IMS. The SUPL procedures defined in OMA AD SUPL: "Secure User Plane Location Architecture" [15], OMA TS ULP: "User Plane Location Protocol" [16], may be used if supported by the terminal and if it is possible to establish a user plane connection between the UE and the SUPL server. Information provided in step 4 concerning the location solutions and position methods supported by the UE may optionally be used by the LRF to help determine the means to obtain the location information.
5b. If configured to provide an NPLI for WLAN access and if the UE is not roaming, the LRF queries HSS for every access the LRF is configured for. The LRF issues a separate query for every access. If the LRF cannot obtain an NPLI, it shall invoke procedure 5a.
The LRF may invoke an RDF to convert the location information received in step 4 or obtained in step 5a into PSAP routing information, but LRF's interactions with RDF are out of scope of the present specification. The LRF may store the location information, but only for a defined limited time in certain regions, according to regional requirements.
6. The LRF sends the location information and/or the routing information to the IMS core. The LRF may also return correlation information (e.g. ESQK) identifying itself and any record stored in step 5a.
7. The IMS core uses the routing information provided in step 6 or selects an emergency centre or PSAP based on location information provided in step 3 or 6 and sends the request including the location information and any correlation information and possibly location information source, e.g. positioning method that was used to obtain the location information to the emergency centre or PSAP.
7a. The INVITE is sent to an MGCF/MGW;
7b. The IAM is continued towards the emergency centre or PSAP; or
7c. The INVITE is sent directly to the emergency centre or PSAP.
8. The emergency call establishment is completed.
9. The PSAP may send a location request to the LRF to get the initial location information for the target UE, or to request LRF to get updated, i.e. current, location information for the target UE. The PSAP may determine the LRF based on the location and/or correlation information received in step 7. The PSAP may also include the correlation information in the request to the LRF.
10. Depending on the access type, UE location is determined as follows:
10a. For non WLAN-access and optionally for WLAN access, the LRF determines the target UE's location using one of the means listed in step 5a above. The LRF may use the correlation information received in step 9 to retrieve information about the UE that was stored in step 5a.
10b. For WLAN access, the LRF may use the correlation information received in step 6 to send a request to the IMS core to retrieve a UPLI from the UE. The IMS core uses the emergency call signalling channel for that purpose. Steps 10b1 to 10b4 depict this procedure. If UPLI is not available when the request comes to the UE (e.g. due to insufficient time) and UPLI cannot be returned, the UE may also provide UPLI once, when available by executing step 10b3 following step 8.
10c. For WLAN access and if the LRF is configured to provide an NPLI for WLAN access and if the UE is not roaming, the LRF queries HSS for every access the LRF is configured for. The LRF issues a separate query for every access. If the LRF cannot obtain an NPLI, it shall invoke procedure 10a.
11. The LRF returns the initial or updated location information to the emergency centre or PSAP. As an option for initial location, the LRF may instigate the location step 10a before the request in step 9 is received and may send the initial location to the emergency centre or PSAP either after the request in step 9 is received or before it is received.
12. The emergency call is released.
13. The IMS core may indicate to the LRF that the call is released. The LRF deletes any record stored in step 5a.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.6.2 Void
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.6.3 Void
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.7 Transfer of MSD for eCall
| |
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.7.1 MSD Transfer/Acknowledgement during Session Establishment with PSAP supporting NG-eCall
|
Figure 7.7.1-1 illustrates a high level call flow for an interworking scenario between a UE and a PSAP supporting NG-eCall.
This scenario occurs, when the UE detects that the NG-eCall is supported by the IP-CAN.
Figure 7.7.1-1: NG-eCall Scenario with PSAP supporting NG-eCall
1. The UE performs steps 1 to 6 of the procedure shown in Figure 7.1.
2. The UE sends an initial emergency SIP INVITE to the IMS core. The SIP INVITE shall contain the initial MSD and the eCall type of emergency service indicator (automatic, manual).
3a. The IMS core routes the SIP INVITE towards the appropriate PSAP.
NOTE: Routing within the IMS core is based on the UE location and the eCall type of emergency service indication, but not on the content of the initial MSD. The PSAP may use also location data contained within the initial MSD.
3b. The PSAP verifies the correctness of the initial MSD and returns a SIP 200 OK to the IMS core. The SIP 200 OK explicitly includes a positive or negative acknowledgement for the initial MSD.
3c. The IMS core proxies the SIP 200 OK to the UE.
4. The emergency call establishment is completed. In addition to the transfer of MSD, media channels are established. In this case the emergency voice channel is established.
5. The established audio channel supports bidirectional voice communication,
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.7.2 MSD Transfer/Acknowledgement during Session Establishment with a PSAP Not supporting NG-eCall (inband means)
|
Figure 7.7.2-1 illustrates a high level call flow for an interworking scenario between a UE and a PSAP via the CS domain.
This scenario may occur in the case, when PS access is available, but the UE does not detect that the NG-eCall is supported by the IP-CAN and there is no CS access available. In this case, the UE shall establish a regular IMS emergency call.
A similar scenario may occur in the case, when the UE detects that the IP_C AN supports NG-eCall and initiates an NG eCall but the session is handled by a PSAP not supporting NG-eCall. The only exception would be step 2 and where the SIP INVITE shall contain the initial MSD and the eCall type of emergency service indicator (automatic, manual).
Figure 7.7.2-1: eCall Scenario with PSAP not supporting NG-eCall
1. The UE performs steps 1 to 6 of the procedure shown in Figure 7.1.
2. The UE sends an initial emergency SIP INVITE to the IMS core. The SIP INVITE shall be setup as follows:
- if the UE has not received the "eCall supported" indication, the UE shall include the eCall type of emergency service indication (automatic, manual) and shall not include the initial MSD if the PS access is available;
- if the UE has received the "eCall supported" indication, the UE shall include the initial MSD and the eCall type of emergency service indicator (automatic, manual).
3. The IMS core routes the emergency SIP INVITE towards the appropriate PSAP. In this call flow, the appropriate PSAP is accessed over the MGCF and the CS domain after translating the eCall type of emergency service indication into the corresponding MSISDN.
3a. The SIP INVITE is sent to an MGCF/MGW for interfacing to the CS domain.
3b. The MGCF sends an IAM towards the appropriate PSAP for the emergency voice call.
4. The emergency voice call establishment is completed with a voice path only.
5. If the UE has sent the MSD in step 2 and did not receive either a positive or negative acknowledgement for the initial MSD included in the SIP INVITE, or the UE did not send the MSD in step 2 the UE shall attempt to transfer the MSD to the PSAP via the eCall Inband Modem, as defined in TS 26.267 [42].
NOTE: Receipt of the MSD using audio media stream encoded as described in TS 26.267 [42] is optional for a PSAP that supports eCall over IMS according to CEN EN 17184:2024 [59].
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.7.3 Transfer of an updated MSD
|
Figure 7.7.3-1 illustrates a high level call flow for transfer of an updated MSD in the case that the emergency centre or PSAP is accessed via the PS domain. The call flow is applicable following establishment of an emergency services session for eCall as described in clause 7.1.1 in which the initial MSD is transferred in the INVITE and prior to release of the emergency services session. The call flow is also applicable during an incoming IMS call for PSAP call back.
Figure 7.7.3-1: Sending an updated MSD for eCall
1. If the emergency centre or PSAP requires an MSD update, it may send a request for MSD to the IMS Core.
2. The IMS Core shall forward the request to the UE.
3. The UE shall send the most recent MSD to the IMS Core.
4. The IMS Core shall forward the MSD to the emergency centre or PSAP.
NOTE: Whether an acknowledgement message for the successful receipt of updated MSD by the PSAP is further provided to the UE is resolved in stage 3 level.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.7.8 Callback from an NG capable PSAP with transfer of updated MSD
|
Figure 7.7.8-1 illustrates a high level call flow for callback to a UE from an NG capable PSAP with transfer of updated MSD after the UE has established an eCall over IMS with the PSAP using the procedure in clause 7.7.1.
Figure 7.7.8-1: Callback from an NG capable PSAP with transfer of updated MSD
1. The UE and PSAP perform steps 1 to 5 of the procedure shown in Figure 7.7.1-1 after which, at some later point in time, the call is released. Alternatively, the UE and PSAP perform steps 1, 2 and 3a of the procedure shown in Figure 7.7.1-1 with the PSAP returning an indication to the UE that the PSAP cannot accept the call at this time.
2. The PSAP sends a SIP INVITE to the IMS core in the HPLMN. The SIP INVITE contains a public user identity of the UE as obtained by the PSAP at step 1 and an indication of support by the PSAP for transfer of updated MSD.
NOTE 1: The UE is assumed to be still attached or registered to the PS domain with a normal IMS registration when step 2 occurs.
3. The IMS core forwards the SIP INVITE to the UE and includes an indication that the sender is a PSAP.
4. The UE sends a 200 OK to the IMS Core. If the INVITE includes the PSAP indication and an indication of support for updated MSD at step 3 and if the INVITE at step 3 was received within a configurable time period of either the release or non-acceptance of the eCall over IMS at step 1, then the UE includes an indication of support for transfer of updated MSD.
NOTE 2: The configurable period is associated with transfer of updated MSD for a PSAP callback and is defined in TS 24.229 [19].
5. The IMS core forwards the SIP 200 OK to the PSAP.
6. The audio channel is established to support bidirectional voice communication.
7. The PSAP and UE may perform steps 1 to 4 of Figure 7.7.3-1 for transfer of updated MSD. The UE only supports step 7 if the conditions for including an indication of support for transfer of updated MSD at step 4 were met.
8. If the transfer of updated MSD at step 7 fails, the PSAP may request and the UE may return updated MSD transfer via the eCall Inband Modem, as defined in TS 26.267 [42]. The UE conditions for supporting step 8 are the same as the conditions for supporting step 7.
NOTE 3: MSD transfer could fail if not supported by the IMS Core in the HPLMN or, when there is roaming and IMS local breakout, by the IMS Core in the VPLMN or by some intermediate transit network.
|
28fb130c860d2849fabf78866d8fab81
|
23.167
|
7.7.9 Callback from a PSAP in the CS domain with transfer of updated MSD
|
Figure 7.7.9-1 illustrates a high level call flow for callback to a UE from a PSAP in the CS domain with transfer of updated MSD. This scenario may occur following eCall session establishment and release with a PSAP not supporting NG-eCall as in clause 7.7.2 or may occur following eCall session establishment and release when the UE is in the CS domain and where the UE later attaches to or registers with a network in the PS domain. Figure 7.7.9-1: Callback from a PSAP in the CS domain with transfer of updated MSD 1a. The UE performs steps 1 to 5 of the procedure shown in Figure 7.7.2-1 followed by a later call release. Alternatively, the UE and PSAP perform steps 1, 2, 3a and 3b of the procedure shown in Figure 7.7.2-1 with the PSAP returning an indication to the UE that the call cannot be accepted. 1b. As an alternative, the UE, when in the CS domain, establishes or attempts to establish an eCall with a PSAP using procedures in TS 24.008 [13]. The eCall is either later released or not accepted by the PSAP and UE mobility occurs to the PS domain. 2. The PSAP sends or instigates an IAM to an MGCF/MGW in the HPLMN for interfacing to the CS domain. The IAM contains a public telephone identity of the UE as obtained by the PSAP at step 1a or step 1b. NOTE 1: The UE is assumed to be attached or registered to the PS domain with a normal IMS registration when step 2 occurs. 3. The MGCF sends a SIP INVITE to the IMS core in the HPLMN. 4. The IMS core forwards the SIP INVITE to the UE and may include an indication that the sender is a PSAP. 5. Voice call establishment is completed with a voice path only. 6. The PSAP sends a request for an updated MSD via the eCall Inband Modem, as defined in TS 26.267 [42]. 7. The UE returns updated MSD via the eCall Inband Modem, as defined in TS 26.267 [42] if the following conditions are met: - The INVITE at step 4 was received within a configurable time period of the release or non-acceptance of the eCall over IMS at step 1; and - as an implementation option, the INVITE at step 4 includes the PSAP indication. NOTE 2: The configurable time period is associated with transfer of updated MSD for a PSAP callback and is defined in TS 24.229 [19]. NOTE 3: Receipt of the PSAP indication is an optional condition because it can be difficult for an IMS core in an HPLMN to verify PSAP origination from the CS domain. If this condition is not enforced, the use of the eCall Inband Modem for steps 6 and 7 can still act as an indication of callback from a PSAP. Annex A (informative): Void Annex B (informative): Void Annex C (normative): IMS emergency services using Fixed Broadband Access C.1 Location Retrieval for emergency services over fixed broadband access These procedures described in this annex apply when the IP-CAN contains a Network Attachment Subsystem with a CLF as specified in ETSI ES 282 004 [18]. C.1.1 High Level Principles for Emergency location information for fixed broadband access In addition to the architecture described in clause 5.1 above, the P‑CSCF may have an interface to an LRF which may contain a CLF as described below in figure C.1. For more information on the CLF refer to ETSI ES 282 004 [18]. Figure C.1: Additional P‑CSCF interface for fixed broadband access For fixed broadband access, the UE may know its own network location or geographical location. If the UE knows its location, it shall insert the location information in the SIP INVITE request when establishing the emergency IMS session. As an alternative, if the UE is not able to determine its own location, the UE should try to request its location from the access network, if the UE supports such functionality. The access network may know the location of the access point where the UE is connected to. In this case, the UE should request the location information from the access network according to clause 7.6. The UE shall insert the location information received as a response to the location query, if any, in the emergency SIP INVITE request. This location information may be network based, e.g. line identification, or geographical location information. If the UE does not know its location and is unable to obtain its location from the access network, the UE should have a means to indicate in the emergency SIP INVITE that its location is unknown. If the UE does not provide location information, the P‑CSCF may request location information from the LRF as described in clause 7.6 and insert the location information in the received INVITE request. The IMS network may also request location information from the LRF in the case that verification of the location information provided by the UE is required. After such verification, the IMS network may insert the location information received from the LRF or override the location information received from the UE before routing the request to the PSAP. Alternatively, subject to operator policy, the S-CSCF may receive from the HSS a reference location of the user at registration and insert it in the INVITE request, when network-provided location information is not already present. The reference location (e.g. line identification) is determined by the operator as part of the user profile. NOTE: The reference location alternative is applicable to non-nomadic services provided on fixed lines for emergency sessions that are routed through the S-CSCF (see clause 6.2.4). The reference location corresponds the physical location of the fixed line. C.1.2 Retrieval of location information for emergency services over fixed broadband access In addition to clause 7.6, the following applies for a fixed broadband access: - When the UE is requesting to retrieve the location information from IP-CAN, the UE may use the DHCP option for coordinate-based geographic location of the client as specified by IETF in RFC 3825 [9] and the DHCP option that allows hosts to learn their civic location via DHCP, as specified in RFC 4676 [10]. This DHCP option shall not be used by an UE on an IP-CAN using 3GPP RAT. - The line identifier used by the UE with fixed broadband access may be authenticated by the IMS core. Annex D (informative): Examples of call flows according to NENA I2 recommendations This clause provides the examples of call flows according to NENA I2 recommendations [17]. D.1 ECS redirecting IMS emergency call Figure D.1 This flow is supported by the procedures in clause 7.3, where the E‑CSCF need not enquire the LRF for location information. Additional steps defined here are standard SIP methods, but not defined in this specification. Detailed description of the procedure: 1) An IMS emergency call is initiated. 2) The E‑CSCF sends an Invite message with 911 or other well-known emergency number as the dialled number, the UE's location information in a Location Object (LO) if available and the UE's media capabilities encapsulated in a SDP payload, to the ECS. 3) Based on the received Location Object (LO), the ECS will determine to which PSAP/EC the call should be routed and allocate an ESQK from the ESQK pool associated with that particular PSAP/EC. The ECS then will format a SIP response with the retrieved ESRN/ESQK in the Contact fields to redirect the emergency call. 4) The IMS Core uses the ESRN/ESQK received in the call redirect message to format an INVITE message properly and sends it to the MGCF/MGW. A P-Asserted-Identity field may be inserted in the INVITE message, it contains either an ESQK or the CBN. 5) The emergency call setup continues with the PSAP/EC. 6) The ECS initiates a subscription at the IMS Core to request a notification of call termination of the emergency call. 7) An acknowledgement is returned. 8) The emergency session establishment signalling continues. 9) The PSAP retrieves location from the ECS. 10) The emergency session is released. 11) The IMS Core sends an Event Notification message to the ECS with an Event indicating that the 911 call has been terminated. At this time, the ESQK allocated to the emergency session can be released. 12) An acknowledgement is returned to the IMS Core. D.2 ECS routes the emergency call to the gateway with record route Figure D.2 This flow is supported by the procedures in clause 7.3, where the E‑CSCF need not enquire the LRF for location information. Detailed description of the procedure: 1) An IMS emergency call is initiated. 2) The E‑CSCF sends an Invite message with 911 or other well-known emergency number as the dialled number, the UE's location information in a Location Object (LO) if available and the UE's media capabilities encapsulated in a SDP payload, to the ECS. 3) Based on the received Location Object (LO), the ECS will determine to which PSAP/EC the call should be routed and allocate an ESQK from the ESQK pool associated with that particular PSAP/EC. The ECS then re-issues an Invite to an appropriate MGCF/MGW with the ESRN/LRO, ESQK and a record route indication. or the call to be routed to PSAP the P-Asserted-Identity contains ESQK, A P-Asserted-Identity field may be inserted in the INVITE message, f for the call to be routed to other emergency answering centre the P-Asserted-Identity contains the CBN. 4) The emergency call setup continues with the PSAP/EC. 5) The emergency session establishment signalling continues. 6) The PSAP retrieves location from the ECS. 7) Either the caller or PSAP initiates the call termination signalling. 8) The E‑CSCF or MGCF/MGW forwards the hang-up message to the ECS. At this time, the ESQK allocated to the emergency session can be released. 9) The ECS sends an OK to the E‑CSCF or MGCF/MGW. 10) The call termination signalling continues. Annex E (informative): Emergency support in different IP-CANs Support for emergency services in the IP Multimedia Core Network can be provided by certain IP-CANs according to table E.1, which shows the level of possible emergency support in this version of the specification. The UE may be able to use also other IP-CANs that are not included in table E.1 to access emergency services in the IP Multimedia Core Network, but the support of such access technologies is out of scope of this specification. Table E.1: Support for IMS Emergency Services by Different IP-CANs IP-CAN Normal Access Emergency support Insufficient Security Credentials GPRS (UTRAN) X X X Fixed Broadband X X X cdma2000 HRPD/PDS X X X cdma2000 HRPD/EPC X X X EPS (UTRAN and E-UTRAN) X X X WLAN access to EPS X (NOTE 1) X - 5GS (NG-RAN) X X X non-3GPP access to 5GC X (NOTE 1) X - NOTE 1: Emergency Sessions use a normal access to EPC/5GC only in the case of emergency sessions not detected by the UE and nevertheless served by the IMS network. The term "normal access" in table E.1 means that the IP-CAN is not made aware of the UE intent to establish an emergency services session and therefore provides no special emergency support e.g. call priority. The term "emergency support" in the table means that the IP-CAN is made aware of the UE intent to establish an emergency services session, or at least of the priority nature of the access, so that the access network is able to handle the emergency call with appropriate priority. The term "insufficient security credentials" in the table means that the IP CAN is able to allow a UE with no UICC card or a UICC card with insufficient credentials to obtain IP bearer access for emergency services in the IP Multimedia Core Network. Annex F (normative): IMS Emergency Services Using HRPD/PDS Network F.1 cdma2000 HRPD/PDS Options The following options from the normative clauses of this TS are applicable in cdma2000 HRPD systems with a PDS core network: 1) Clause 7.1.1, step 4 "The IP-CAN may support a UE indication that this request is for an emergency service". The following options from the normative clauses of this TS are not applicable in cdma2000 HRPD/PDS systems: 1) Clause 4.1 "The P‑CSCF serving the emergency call is the IMS network entity which may retrieve the location identifier from the IP‑CAN". F.2 Requirements on the HRPD Network as an IP-CAN For an emergency call over HRPD, the requirements on the IP‑CAN are specified in 3GPP2 X.S0060 [25]. F.3 Information Flows The informational flows for emergency calls over HRPD are provided in 3GPP2 X.S0060 [25]. Annex G (informative): TEL‑URI provisioning considerations for IMS emergency call back In order to support emergency call-back from the PSTN or CS Domain: - For a single or multiple device subscription that contain both a SIP‑URI and TEL‑URI in at least one implicit registration set for each device (including subscriptions that share SIP-URIs and TEL‑URIs between devices), IMS emergency sessions can already be supported. If the user registers with a temporary public user identity (e.g. the subscription has a device containing a USIM) ensure that a TEL‑URI is provisioned in the same implicit registration set as the temporary public user identity. - For a multiple device subscription that has TEL‑URIs for some devices but has one or more devices that are not assigned an implicit registration set containing a TEL‑URI (e.g. because these devices in the subscription are not allowed to use a TEL‑URI in normal originations), the existing TEL‑URIs in the subscription cannot be shared between all devices for the purposes of IMS emergency sessions. Annex H (normative): IMS emergency services using UTRAN, E-UTRAN and NG-RAN radio access network H.1 General This annex includes additional requirements and clarifications when the IP-CAN is a PS Domain supporting UTRAN, E-UTRAN or NG-RAN radio access network. NOTE: For SNPN, as defined in TS 23.501 [48] the only supported RAT is NR and there is no support for Emergency Services Fallback. If a PLMN supports other emergency numbers than those listed in TS 22.101 [8], the UE is connected to the PLMN using UTRAN, E-UTRAN or NG-RAN radio access network and the UE needs to know these other emergency numbers, then such emergency numbers shall be provided to the UE via the mobility management procedures as described in TS 24.301 [33], TS 24.008 [13] and TS 24.501 [52]. If an SNPN supports other emergency numbers than those listed in TS 22.101 [8], the UE is connected to the SNPN using NR access and the UE needs to know these other emergency numbers, then such emergency numbers shall be provided to the UE via the mobility management procedures as described in TS 24.501 [52]. For registration requests received from an emergency PDN connection or emergency PDU session, the P-CSCF shall reject any IMS registration which is not for the emergency purpose. eCall is supported with E-UTRAN and NG-RAN for PLMNs only, i.e. eCall is not supported for SNPNs. UE configured for eCall Only Mode can receive a PSAP call back for a limited duration following the termination of the eCall due to its specific mobility management procedures requirement as defined in TS 22.101 [8]. H.2 UE specific behaviour For the specific case where the UE has selected to make an emergency call over EPS, GPRS or 5GS the UE shall use the following procedures: - A UE shall establish an emergency PDN connection or emergency PDU session and perform an IMS emergency registration before initiating a UE detectable emergency session via UTRAN, E-UTRAN or NG-RAN. - A UE shall not establish an emergency PDN connection or emergency PDU session if the UE initiated a non UE detectable emergency session and is subsequently informed by the network that the ongoing session is an emergency session. NOTE 1: If SRVCC is required in the network, an operator could download the local emergency numbers to avoid non UE detectable emergency sessions since UTRAN and E-UTRAN will not be able to identify emergency SRVCC handling without an emergency PDN connection. - If the UE initiates a non UE detectable emergency session and the session initiation request is rejected by the P‑CSCF with an indication that this is an emergency session, the UE shall select a domain according to the requirements for domain priority and selection in clause H.5 when applying the requirements in clause 7.1.2. - A UE in 5GS shall not initiate establishment of an IMS emergency session over Non-3GPP access unless the emergency session could not be established via 3GPP access. - If the UE has not been authenticated in the PS domain, the UE shall initiate an IMS emergency session establishment without registration according to clause 7.4. - The UE shall include the latest available Cell Global Identification (CGI) in the IMS emergency request establishing the emergency call. - When the UE is using NR satellite access to 5GC, the UE shall include an indication of NR satellite access in the IMS request. NOTE 2: When using UTRAN, the UE is not always able to read the current cell identity and in some cases the UE can be connected to several cells simultaneously. NOTE 3: For NR satellite access to 5GC the NR CGI (NCGI) available to the UE and the NCGI provided from NG-RAN to 5GC might be different. The NCGI provided by the UE might not relate to the UE's geographic location. A P-CSCF relying only on the UE provided NCGI could then lead to errors. - If the UE is required to include an equipment identifier (according to clauses 4.1 and 6.1) the equipment identifier shall be the IMEI. - For the media supported during IMS emergency sessions in clause 10.4 of TS 22.101 [8], media codec and format support is specified in TS 26.114 [34]. - UE shall only perform eCall procedure over IMS as specified in clause 7.7.1 when it detects the "eCall supported" indication as defined in TS 23.401 [28] and TS 23.501 [48]. - When PS access is available, but the UE does not detect the "eCall supported" indication as defined in TS 23.401 [28] and TS 23.501 [48] and there is no CS access available, the UE shall establish a regular IMS emergency call. - If the broadcast indicators in an E-UTRA cell connected to 5G and EPC as defined in TS 23.501 [48] indicate only one core network (EPC or 5GC) supports emergency services then the UE shall register to the core network which supports emergency services when the UE initiates emergency services. If broadcast indicators indicate that both 5GC and EPC support emergency services then the UE initiates emergency services to either EPC or 5GC according to the UE implementation. - If the broadcast indicator in an NR cell indicates that the cell provides access to SNPNs and that 5GC supports emergency services, the UE shall only register to the core network of the SNPN that indicates support for emergency services. If broadcast indicators indicate that one or more SNPNs and/or PLMNs support emergency services, then the UE initiates emergency services to either a SNPN or a PLMN according to UE implementation. H.3 High Level Procedures for IMS emergency calls For the high level procedures (as described in clause 7.1.1) the following statements apply for UE detected emergency calls when PS domain with UTRAN, E-UTRAN or NG-RAN access is used: - the bearer registration to the IP-CAN is the PS attach or PS Registration procedure; - the IP-CAN bearer resource is the PDP context for GPRS, EPS Bearer for EPS and QoS Flow for 5GS and TS 23.060 [2], TS 23.401 [28] and TS 23.501 [48] respectively describe how to indicate that the request is for emergency; - the release of reserved bearer resources is the release of a PDP context, an EPS Bearer or a QoS Flow. For the high level procedures (as described in clause 7.1.2) the following statements apply for Non UE detectable emergency calls when PS domain with UTRAN, E-UTRAN or NG-RAN access is used: - The P-CSCF rejects the session initiation request with an indication that this is an emergency session; or - the P-CSCF allows the session initiation request to continue and the E-CSCF informs the UE that it is an emergency session. Such a session will not use an emergency PDN connection or emergency PDU session and will not have SRVCC or SRVCC for IMS emergency session support. For the IMS Emergency Session Establishment without Registration (as described in clause 7.4), P-CSCF retrieves the additional subscriber related identifier(s) from IP-CAN via PCC in TS 23.203 [20] when PS domain with UTRAN and E-UTRAN access is used. H.4 Location handling The applicable location solutions are specified in TS 23.271 [5] for control plane with UTRAN and E-UTRAN access, in TS 23.501 [48] and TS 23.502 [49] for control plane with NG-RAN access and in SUPL 2.0 (OMA AD SUPL[15], OMA TS ULP [16]) for user plane. For SUPL, SUPL Initiation Function using UDP/IP (OMA AD SUPL [15]) shall be supported by the SET. If the operator policy requires network provided location using PCC-based solutions for the UE location (e.g. serving cell), the P-CSCF retrieves location information from the access network and includes it in the emergency service request, as described in TS 23.228 [1]. The UE location is marked as being network provided to distinguish it from location information that the UE provided. If the operator policy requires network provided location using the LRF-based solution for the UE location (e.g. serving cell), the P-CSCF forwards the emergency request to E-CSCF. The E-CSCF retrieves location information from LRF as described in clause 6.2.2. Operator policies in the P-CSCF and E-CSCF should be aligned to ensure that the E-CSCF doesn't attempt to retrieve location information from the LRF if network-provided location information is present in the initial emergency request. However, as described in clause 6.2.2, the E-CSCF may request the LRF to retrieve additional location information (e.g. the UE's geographical location information). H.5 Domain Priority and Selection Rules for Emergency Session Attempts This clause details the domain priority and selection (see clause 7.3) for UE that attempts to make an emergency session for UTRAN, E-UTRAN or NG-RAN radio access networks based on the UE attach status to CS or PS domains and the network support for IMS emergency and IMS voice over PS. The following table (Table H.1) defines these rules based on the UE (last 2 columns) for different initial conditions (first 4 columns) when an emergency session is initiated and when the UE is not in limited service state. NOTE: The behaviour of the UE in limited service state is defined in e.g. TS 23.122 [41], TS 36.304 [58] and TS 38.304 [54] and is supported by the broadcast of the ims-EmergencySupport bit (see TS 36.331 [55]; TS 38.331 [56]). The behaviour is that a UE supporting voice services performs cell reselection to a cell that does support emergency voice calls. For NG-eCall (eCall over IMS) domain selection in clause H.6 applies. This clause is not applicable for NG-eCall. When a 5G ProSe enabled UE (as specified in TS 23.304 [53]) does not have direct connection to the network for emergency service, the UE can obtain emergency service via 5G ProSe UE-to-Network Relay as specified in Annex M. Table H.1: Domain Selection Rules for emergency session attempts for UTRAN, E-UTRAN or NG-RAN radio access networks CS Attached (NOTE 9) PS Attached VoIMS EMS First EMC Attempt Second EMC Attempt A N Y Y Y PS CS if available and supported (NOTE 7, NOTE 8) B N Y N Y PS or CS if the emergency session includes at least voice. PS if the emergency session contains only media other than voice. PS if first attempt in CS CS if first attempt in PS (NOTE 7, NOTE 8) C N Y Y or N N PS if ESFB is "Y" (NOTE 5). Else CS or PS for another 3GPP RAT with EMS or ESFB set to "Y" if available and supported and if the emergency session includes at least voice. Else PS for another 3GPP RAT with EMS or ESFB set to "Y" if available and supported if the emergency session contains only media other than voice. PS if first attempt in CS CS if first attempt in PS (NOTE 7, NOTE 8) D Y N Y or N Y or N CS if the emergency session includes at least voice. PS if available and EMS or ESFB is "Y" and emergency session contains only media other than voice. PS if available and EMS or ESFB is "Y" E Y Y Y Y If the emergency session includes at least voice, follow rules in TS 22.101 [8] which say to use the same domain as for a non-EMC (NOTE 2) PS if the emergency session contains only media other than voice. PS if first attempt in CS CS if first attempt in PS F Y Y Y or N N PS if ESFB is "Y" (NOTE 5). Else PS for another 3GPP RAT with EMS if available and supported or CS, if the emergency session includes at least voice. CS if first attempt in PS PS for another 3GPP RAT if available and supported and EMS or ESFB is "Y" if first attempt in CS. G Y Y N Y CS if the emergency session includes at least voice. PS if the emergency session contains only media other than voice. PS EMC = Emergency Session. EMC includes also normal calls initiated in the CS domain that are treated by the CS CN as emergency calls. VoIMS = Voice over IMS over PS sessions support as indicated by IMS Voice over PS session supported indication as defined in TS 23.401 [28], TS 23.060 [2] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28], TS 23.060 [2], TS 23.501 [48] and TS 23.502 [49]. ESFB = Emergency Services Fallback for 5GS as defined in TS 23.501 [48] and TS 23.502 [49]. NOTE 1: If the UE selects the CS domain and initiates a normal call using the dialled local emergency number (see clause 7.1.2) and the UE enters limited service state (e.g. due to a Location Registration failing), then the UE camps on an acceptable cell (see TS 23.122 [41]) and may proceed with the EMC by initiating an emergency call in limited service state. NOTE 2: Use of the same domain as for a non-EMC is restricted to UTRAN, E-UTRAN and NG-RAN access (e.g. excludes WLAN). NOTE 3: This NOTE applies to a UE in dual registration mode as defined in TS 23.501 [48]. A dual registration mode UE that is registered to both EPC and 5GC assumes attachment, for the purpose of the "PS Attached" column, to whichever of EPC or 5GC indicates EMS as "Y". When both EPC and 5GC indicate EMS as "Y", the UE shall assume attachment to either EPC or 5GC based on implementation. A UE that is registered to both EPC and 5GC does not use emergency services fallback and ignores the ESFB condition when performing domain selection. NOTE 4: The other 3GPP RAT for row C and row F can be any of UTRA, E-UTRAN connected to EPC, E-UTRA connected to 5GC or NR connected to 5GC that is supported by the UE and differs from the RAT to which the UE is currently attached in the PS domain (or is assumed to be attached based on NOTE 3). NOTE 5: The condition 'ESFB is "Y"' only applies for a UE that is camped on or connected to 5GS via NR or via E-UTRA and that supports Emergency Services Fallback. In that case the emergency call will be provided over E-UTRAN or E-UTRA connected to 5GC as defined in procedures in TS 23.502 [49]. The condition 'ESFB is "Y"' is taken into consideration by the UE only when the network has indicated EMS = "N" for the RAT on which the UE is camping or connected. NOTE 6: For 5GS, the value of the column "EMS" is for the RAT that UE is camped on or is connected to. NOTE 7: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE can make a third attempt using CS. NOTE 8: As an implementation option, when the first attempt uses PS and fails because the first discovered P-CSCF is not available, additional attempts may use PS with alternate P-CSCFs (see clause E.1.1.1 of TS 23.228 [1] and clause 4.3.2.2.1 of TS 23.502 [49]). In this case the UE can make an attempt using CS after making failed PS attempts on all discovered alternate P-CSCFs. NOTE 9: With E-UTRAN access, "CS attached" means that the UE has performed a combined Attach/TAU and has been accepted by the network for EPS and non-EPS services. If the UE has been accepted for EPS and "SMS-only" then, for the purposes of this table, the UE should behave as if it is not CS attached. H.6 eCall over IMS This clause details the domain priority and selection (see clause 7.3) for a UE that attempts to make an eCall over IMS session using E-UTRAN or NG-RAN radio access networks based on the availability of the CS or PS domains and the network support for IMS emergency, eCall over IMS and IMS voice over PS. The following table (Table H.2) defines these rules based on the UE (last 2 columns) for different initial conditions (first 4 columns) when an eCall over IMS session is initiated. Table H.2: Domain Selection Rules for eCall over IMS session attempts for E-UTRAN or NG-RAN radio access networks PS Available VoIMS EMS ECL First eCall Attempt Second eCall Attempt A Y Y Y Y PS PS on another PS RAT if available with EMS=Y and ECL=Y or CS if available B Y Y Y N CS if available PS (UE establishes IMS emergency session) (NOTE 2) C Y Y or N N N CS if available PS on another PS RAT if available with EMS=Y or EMS unknown (NOTE 2) D Y N Y Y PS or CS if available CS if first attempt in PS PS if first attempt in CS (NOTE 2) E Y N Y N CS if available PS (UE establishes IMS emergency session) (NOTE 2) F N - - CS if available VoIMS = Voice over IMS over PS sessions support as indicated by IMS Voice over PS session supported indication as defined in TS 23.401 [28] and TS 23.502 [49]. For the purposes of this table, a UE in limited service state shall assume that Voice over IMS over PS sessions is supported when EMS=Y or ECL=Y. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. A UE in limited service state shall use the ims-EmergencySupport broadcast bit (TS 36.331 [55]; TS 38.331 [56]) instead of the Emergency Service Support indicator. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS. NOTE 2: Fallback to the PS domain with ECL=N shall only occur after the UE has attempted but failed to select another PLMN in the PS domain with ECL=Y or in the CS domain according to PLMN selection rules for a UE in eCall only mode in clause 4.4.3.1.1 of TS 23.122 [41]. NOTE: If the E-UTRAN and NG-RAN cells available to the UE have different settings, the UE assumes "PS Available" and "ECL" apply to whichever cell is indicated (as defined in TS 23.401 [28] and TS 23.501 [48]) as providing eCall over IMS support. When support by more than one cell is indicated, a UE may select any cell to attempt eCall over IMS according to the UE implementation. If a UE that is not in limited service state, receives a response from the PSAP for an attempt over PS indicating non-acceptance of the eCall over IMS by the PSAP and a positive acknowledgment for the MSD, the UE shall not reattempt the eCall using another PS RAT or the CS domain and shall instead wait for a callback from the PSAP. Annex I (normative): IMS Emergency Services Using HRPD/EPC Network I.1 cdma2000 HRPD/EPC Options The following options from the normative clauses of this TS are applicable in cdma2000 HRPD systems with an EPC core network: 1) Clause 7.1.1, step 4 "The IP‑CAN may support a UE indication that this request is for an emergency service". The following options from the normative clauses of this TS are not applicable in cdma2000 HRPD/EPC systems: 1) Clause 4.1 "The P‑CSCF serving the emergency call is the IMS network entity which may retrieve the location identifier from the IP‑CAN". I.2 Requirements on the HRPD/EPC Network as an IP‑CAN For an emergency call over HRPD/EPC, the requirements on the IP CAN are specified in 3GPP2 X.S0057-A [39]. I.3 Information Flows The informational flows for emergency calls over HRPD are provided in 3GPP2 X.S0057-A [39]. Annex J (normative): IMS emergency services using WLAN access to EPC J.1 General This annex includes additional clarifications when the IP-CAN corresponds to a WLAN access to EPC. Both trusted WLAN access (S2a) and Untrusted WLAN access (S2b) to EPC for emergency sessions are supported. NOTE: This annex only applies to EPC access using S2a or S2b. The UE may issue an Emergency session over WLAN access to EPC only when 3GPP access for emergency call is not possible or available (e.g. no 3GPP coverage). Further details on the procedures defined for WLAN access to EPC support of support emergency sessions are defined in TS 23.402 [29]. J.2 UE specific behaviour Procedure for determining the list of emergency numbers: - In addition to the emergency numbers and associated types stored either on the USIM or on the user equipment specified in clause 10.1.1 of TS 22.101 [8], the UE shall use the stored Local Emergency Numbers List received from the 3GPP network to detect that the number dialled is an emergency number. - If a UE has a SIM/USIM and has received a list of emergency numbers and associated types via mobility management procedures as described in TS 24.301 [33] or TS 24.008 [13] when connected to the PLMN using GERAN, UTRAN, E-UTRAN or TS 24.501 [52] when connected to NG-RAN or non-3GPP access connected to 5GC, or, for a UE supporting access to 5GC using non-3GPP access, as specified in Annex L, the UE shall use this list to determine if the dialled digits correspond to an emergency call as long as the UE has determined that the list is valid (see clause 4.1). - The UE may also determine that the dialled digits and associated types or URN information correspond to an emergency call based on the list of emergency numbers retrieved by one of the following means: NOTE: How the UE uses two lists (a list of emergency numbers and associated types or URN information received via mobility management procedures and a list of emergency numbers and associated types or URN information retrieved via the WLAN) is a stage 3 decision. a) via Access Network Query Protocol (ANQP) procedures defined in IEEE Std 802.11 2012 [47] from the associated WLAN AP upon completing authentication with the trusted WLAN access to EPC, with management frame protection enabled. b) via a previous query to a DNS only when that DNS is in the same country as the UE and is an internal DNS server in the 3GPP network whose address is acquired from the ePDG; or c) via IKEv2 procedures from ePDG. - The list of downloaded emergency numbers shall be deleted at country change or, if the particular list is only valid for a PLMN, see clause 10.4.1 of TS 22.101 [8]), at successful registration with a different PLMN. For the specific case where the UE has selected to make an emergency call over WLAN access to EPC (hence the UE has detected that the target URI or dialled digits correspond to an emergency sessions), the UE shall use the following procedures: - The UE shall establish an emergency PDN connection over WLAN and shall perform an IMS emergency registration before sending an IMS emergency session request. - The UE shall include any available location information in the IMS emergency session request. This is further detailed in TS 23.228 [1]. - For the media supported during IMS emergency sessions, media codec and format support is specified in TS 26.114 [34]. - For the support of DRVCC on emergency call on WLAN, see TS 23.237 [32]. A UE shall not establish an emergency PDN connection over WLAN if the UE initiated a normal (i.e. non-emergency) session and is subsequently informed by the network that the ongoing session is accepted by the network even though it is an emergency session. J.3 High Level Procedures for IMS emergency calls For the high level procedures (as described in clause 7.1.1) the following statements apply for UE detected emergency calls when EPC access over WLAN is used: - the IP-CAN bearer resource is a PDN connection dedicated for emergency services. The TS 23.402 [29] describes how to indicate that a PDN connection request is for emergency; - For registration requests received from an emergency PDN connection, the P-CSCF shall reject any IMS registration which is not for the emergency purpose. NOTE 1: When the IMS network detects that the UE is establishing an emergency session over WLAN access to EPC while the UE is not in its Home country, local policies in the Home IMS network may determine whether to nevertheless handle the emergency session For the high level procedures (as described in clause 7.1.2) the following statements apply for Non UE detectable emergency calls when WLAN access to EPC is used: - The P-CSCF may reject the session initiation request with an indication that this is an emergency session or may allow the session initiation request to continue. The following flow contains a high level description of the emergency service procedures performed over WLAN access to EPC when the UE can detect that an emergency PDN connection is being needed. This flow provides details (or references) related with WLAN access to EPC on top of the general procedure described in clause 7.1. Figure J.3: Terminal Detected Emergency Calls (WLAN access to EPC) The following steps are performed: 1. Same as step 1 of Figure 7.1. 2. The UE releases any PDN connection it may have over untrusted access to EPC. 3. Void. 4. As described in TS 23.402 [29]: - in the case of untrusted access, the UE selects an ePDG for emergency services and sets-up a PDN connection for emergency services; - in the case of trusted access, the UE sets-up a PDN connection for emergency services. The UE is assigned an IP address at this stage. NOTE 2: No specific WLAN AP selection is carried out to support emergency services. 5. Same as step 5 of Figure 7.1. 6. Same as step 6 of Figure 7.1. 7. Same as step 7 of Figure 7.1. J.4 Location handling When a UE performs an emergency registration or initiates an emergency session over WLAN access to EPC the UE provides location information that is further defined in TS 23.228 [1]. If the operator policy requires network provided location using PCC-based solutions for the UE location, the P-CSCF may retrieve location information from the access network as defined in TS 23.203 [20] and includes it in the emergency session request, as described in TS 23.228 [1]. Annex K (normative): Support of IMS emergency sessions for roaming users in deployments without IMS-level roaming interfaces K.1 General This annex includes network impact and call flows for support of IMS emergency sessions for roaming users in deployments without IMS-level roaming interface between the P-CSCF in the VPLMN and the S-CSCF in the HPLMNs. This annex also applies to IMS emergency sessions for SNPN users when there is no support for IMS-level roaming, or the user has no IMS credentials. This annex is only applicable to UTRAN, E-UTRAN and NG-RAN access networks. IMS authentication is performed by linking the IMS registration to user's EPS or 5GS authentication based on the user's IP address and IMSI. This mechanism is similar to GIBA (GPRS-IMS bundled authentication) specified in TS 33.203 [44]. The P-CSCF performs the GIBA procedure over Gm with the UE as defined in TS 24.229 [19]. If this procedure is not supported, UE may perform anonymous emergency session. A callback number for the user may also be retrieved via the PCRF or PCF. K.2 Functional description K.2.1 General This clause lists the additional functionality in the network that is required to support IMS emergency sessions for roaming users in network deployments where there are no IMS-level roaming interfaces between the serving IMS network and the home IMS network. K.2.2 P-CSCF In addition to the functionality described in clause 6.2.1, the P-CSCF supports the functionality listed below: - P-CSCF shall be able to retrieve the UE/user's IMSI, IMEI and MSISDN (if available) from the PCRF/PCF. - P-CSCF may support the GIBA procedure over Gm as defined in TS 24.229 [19]. - P-CSCF may verify the IMSI/IMEI provided in the SIP REGISTER message against the IMSI/IMEI provided by the PCRF or PCF. K.2.3 PCRF or PCF - PCRF or PCF shall be able to provide the IMSI, the ME Identity (IMEISV) and MSISDN (if available) over Rx to the P-CSCF. K.2.4 PGW or SMF/UPF - PGW or SMF/UPF shall be able to prevent "source IP address spoofing" for IMS emergency PDN connections if GIBA authentication, defined in TS 33.203 [44], is used as part of emergency IMS registration. K.2.4 HSS or UDM - The EPS user subscription at the HSS should contain exactly one MSISDN which should be the same as that in the IMS profile. - The 5GS user subscription at the UDM should contain exactly one MSISDN based GPSI which should be the same as that in the IMS profile. K.3 IMS Emergency Registration and Session Establishment The call flow for support of IMS emergency sessions for roaming users in deployments without IMS-level roaming interfaces for UTRAN, E-UTRAN or NG-RAN access networks is described in Figure K.3-1. Figure K.3-1: IMS Emergency Session Establishment in deployments without IMS roaming interface between VPLMN and HPLMN 1. UE establishes a PDN connection (for EPC) or PDU session (for 5GC) for IMS emergency services. 2. For EPC, IMSI and IMEI(SV) are retrieved from the UE. The MSISDN (if available) is provided by the HSS. For 5GC, the SUPI and PEI are retrieved from the UE context stored in the AMF; the SUPI needs to contain an IMSI for PLMN accesses and may contain an IMSI or a network-specific identifier (NSI) that takes the form of an NAI for SNPN access. TS 23.003 [21] specifies the IMPI and IMPI derivation for a NAI-based SUPI. The PEI needs to contain an IMEI(SV). The GPSI (if available) is provided by the UDM; the GPSI needs to contain an MSISDN. 3. For EPC: MME/SGSN sends a Create Session Request towards the PGW including the IMSI, the IMEI(SV) and the MSISDN (if available) as specified in TS 23.401 [28]. For 5GS: AMF sends a Nsmf_PDUSession_CreateSMContextRequest towards the SMF/UPF including the SUPI, the PEI and the GPSI (if available) as specified in TS 23.502 [49]. 4. For EPC, PGW establishes an IP-CAN session with the PCRF as described in TS 23.401 [28] and TS 23.203 [20]. The IP-CAN session is identified with UE's IPv4 address of IPv6 prefix associated with the PDN connection for IMS emergency services. The IMSI, the IMEI(SV) and the MSISDN (if available) are passed to the PCRF as part of the IP-CAN session establishment. For 5GC, SMF establishes an SM Policy Association with the PCF as described in TS 23.502 [49] and TS 23.503 [51]. The PDU session is identified with UE's IPv4 address or IPv6 prefix. The SUPI, PEI, GPSI (if available) and emergency DNN are passed to the PCF. 5. The Attach or UE requested PDN connection procedure (for EPC) or the PDU Session Establishment procedure (for 5GC) is being completed. Steps 6-12 apply if the UE performs IMS Emergency Registration, based on conditions specified in clause 4.1 e.g. UE is aware that it has sufficient IMS authentication material. 6. UE initiates IMS emergency registration by sending a SIP REGISTER (UserID-1) message. The UserID-1 parameter is an IMPI and optionally an IMPU. 7a. Upon reception of the SIP REGISTER message the P-CSCF determines that there is no IMS NNI to the user's HPLMN and the access type is not set to "3GPP-NR-ProSe-L3UNR" as described in Annex M. The P-CSCF requests the PCRF or PCF for EPS-level identities (e.g. IMSI, IMEI(SV), MSISDN) in the Rx session establishment request. For 5GC, P-CSCF may use the Npcf_PolicyAuthorization service as described in TS 23.502 [49] and TS 23.503 [51] instead of the Rx interface. 7b. For EPC, the PCRF performs session binding based on the UE's IP address/prefix (as defined in clause 6.1.1.2 of TS 23.203 [20]) and provides one or more EPS-level identities and the MSISDN (if available) to the P-CSCF. For 5GC, the PCF performs session binding based on the UE's IP address/prefix (as defined in TS 23.503 [51]). If the Rx interface is used, the PCF extracts IMSI, IMEI(SV) and if available MSISDN from SUPI, PEI and GPSI, respectively and provides the former identities to the P-CSCF. If the Npcf_PolicyAuthorization service is used, the PCF provides SUPI, PEI and if available GPSI and the P-CSCF extracts IMSI, IMEI(SV) and if available MSISDN from those identities. Step 7a and 7b can be skipped when the P-CSCF determines that there is no IMS NNI and the UE is a 5G ProSe Layer-3 Remote UE based on the access type "3GPP-NR-ProSe-L3UNR" as described in clause Annex M. 8. Based on operator configuration and if the network supports the GIBA procedure over Gm as defined in TS 24.229 [19], the P-CSCF responds with a 420 response with sec-agree value listed in the unsupported header field. Otherwise it rejects the IMS registration request with SIP 403 (Forbidden) as defined in TS 24.229 [19]. If the network supports anonymous IMS emergency sessions, P-CSCF may add an indication whether it supports anonymous IMS emergency sessions to the 403 or 420 response. Steps 9-12 apply if the P-CSCF has responded with a 420 response in step 8 and if the UE supports GIBA procedure as part of emergency IMS registration (irrespective of whether indication of anonymous IMS emergency session support was included in step 8). 9. UE according to TS 24.229 [19], performs a new initial registration by sending a SIP REGISTER (UserID-2, IMEI) message and without inclusion of the Authorization header field. UserID-2 is a public user identity derived from SUPI (IMSI or NSI). P-CSCF may verify the IMSI/NSI/IMEI provided by the PCRF or PCF in step 7b against the IMSI/NSI/IMEI derived from the public user identity provided by the UE if step 7b is performed, prior to accepting the SIP REGISTER message. 10. P-CSCF accepts the registration with 200 OK and provides a tel-URI based on the MSISDN (if available) received from PCRF in step 7b to the UE. From the UE point of view, the procedure is the same as specified for GIBA (GPRS-IMS bundled authentication) procedures in TS 24.229 [19]. 11. UE then attempts an IMS emergency session by sending a SIP INVITE (UserID-3) message. UserID-3 is set to UE's public identity (i.e. MSISDN as Tel-URI received in step 10). 12. The P-CSCF verifies whether the UserID-3 indicated in the SIP INVITE message complies with the tel-URI that was provided to the UE. If compliant, P-CSCF forwards the SIP INVITE towards the PSAP including a callback parameter (CallBackPar) in the form of TEL-URI derived from the MSISDN received in step 7 if step 7 is performed. The procedure stops here. Steps 13-15 apply if the UE attempts anonymous IMS emergency session, e.g. the P-CSCF has responded in step 8 with a 403 (Forbidden) response, or the P-CSCF has responded in step 8 with 420 response and the UE does not support GIBA as part of emergency IMS registration, or if the UE skipped IMS emergency registration: 13. The UE may attempt an unauthenticated IMS emergency session including an "anonymous user" parameter in the SIP INVITE message. 14. Upon reception of the SIP INVITE and the access type is not set to "3GPP-NR-ProSe-L3UNR" as described in Annex M the P-CSCF either internally retrieves the one or more EPS-level identities and the MSISDN (if available) that were received in step 7b, or performs step 7 again. 15. The P-CSCF forwards the SIP INVITE (UserID-4, CallBackPar) towards the PSAP. UserID-4 is derived from one of the EPS-level identities received in step 7b. CallBackPar in the form of TEL-URI is derived from the MSISDN received in step 7b. The procedure stops here. Step 16 applies if the UE attempts an emergency call in the CS domain as specified in clause 4.1: 16. Subsequent to the IMS registration failure in step 8 or subsequent to an anonymous SIP INVITE attempt the UE may attempt an emergency call in the CS domain. K.4 Non UE detectable Emergency Session In addition to clause 7.1.2, the following is applicable for this scenario: - It is recommended that local emergency call numbers are provided to the UE according to the procedures specified in TS 24.501 [52], TS 24.301 [33], TS 24.008 [13] or Annex J.2. This helps to reduce the number of non-UE detected emergency numbers even for those PLMNs where only a subset of the local emergency numbers can be downloaded to the UEs. - When the UE registers in the IMS, the P-CSCF may retrieve the VPLMN-ID or SNPN ID of the UE as described in clause W.3 of TS 23.228 [1] and may access a database to obtain a list of all local emergency numbers for the visited PLMN, if not already available in the P-CSCF. These numbers are used for detection of non UE detectable emergency calls during IMS session setup. The database of PLMN-/SNPN- specific emergency numbers and its interface with the P-CSCF are not specified by 3GPP. Annex L (normative): IMS emergency services using non-3GPP access to 5GC L.1 General This annex includes additional clarifications when the IP-CAN corresponds to a non-3GPP access to 5GC. Trusted and untrusted non-3GPP access to 5GC for emergency sessions are supported. The UE may issue an Emergency session over non-3GPP access to 5GC only when 3GPP access for emergency call is not possible or available (e.g. no 3GPP coverage). Further details on the procedures defined for non-3GPP access to 5GC support of support emergency sessions are defined in TS 23.502 [49]. L.2 UE specific behaviour Procedure for determining the list of emergency numbers: - In addition to the emergency numbers and associated types stored either on the USIM or on the user equipment specified in clause 10.1.1 of TS 22.101 [8], the UE shall use the stored Local Emergency Numbers List received from the 3GPP network to detect that the number dialled is an emergency number. - If a UE has a SIM/USIM and has received a list of emergency numbers and associated types or URN information via mobility management procedures as described in TS 24.301 [33] and TS 24.008 [13] when connected to the PLMN using GERAN, UTRAN, E-UTRAN, or TS 24.501 [52] when connected to NG-RAN or non-3GPP access connected to 5GC, or, for a UE supporting access to EPC via WLAN, as specified in Annex J, the UE shall use this list to determine if the dialled digits correspond to an emergency call as long as the UE has determined that the list is valid (see clause 4.1). NOTE: How the UE uses two lists (a list of emergency numbers and associated types or URN information received via mobility management procedures and , for a UE supporting access to EPC via WLAN, a list as specified in Annex J) is a stage 3 decision. - The list of downloaded emergency numbers shall be deleted at country change or, if the particular list is only valid for a PLMN (see clause 10.4.1 of TS 22.101 [8]), at successful registration with a different PLMN. For the specific case where the UE has selected to make an emergency call over non-3GPP access to 5GC (hence the UE has detected that the target URI or dialled digits correspond to an emergency sessions), the UE shall use the following procedures: - The UE shall establish an emergency PDU session over non-3GPP and shall perform an IMS emergency registration before sending an IMS emergency session request. - The UE shall include any available location information in the IMS emergency session request. This is further detailed in TS 23.228 [1]. - For the media supported during IMS emergency sessions, media codec and format support is specified in TS 26.114 [34]. A UE shall not establish an emergency PDU session over non-3GPP access if the UE initiated a normal (i.e. non-emergency) session and is subsequently informed by the network that the ongoing session is accepted by the network even though it is an emergency session. L.3 High Level Procedures for IMS emergency calls For the high-level procedures (as described in clause 7.1.1) the following statements apply for UE detected emergency calls when 5GC access over non-3GPP access is used: - the IP-CAN bearer resource is a PDU session dedicated for emergency services. TS 23.502 [49] describes how to indicate that a PDU Session Request is for emergency. - For registration requests received from an emergency PDU session, the P-CSCF shall reject any IMS registration which is not for the emergency purpose. NOTE 1: When the IMS network detects that the UE is establishing an emergency session over non-3GPP access to 5GC while the UE is not in its Home country, local policies in the Home IMS network may determine whether to nevertheless handle the emergency session. For the high-level procedures (as described in clause 7.1.2) the following statements apply for Non UE detectable emergency calls when non-3GPP access to 5GC is used: - The P-CSCF may reject the session initiation request with an indication that this is an emergency session or may allow the session initiation request to continue. The following flow contains a high-level description of the emergency service procedures performed over non-3GPP access to 5GC when the UE can detect that an emergency PDU session is being needed. This flow provides details (or references) related with non-3GPP access to 5GC on top of the general procedure described in clause 7.1. Figure L.3: Terminal Detected Emergency Calls (non-3GPP access to 5GC) The following steps (numbering being the same as in figure 7.1) are performed: 1. Same as step 1 of Figure 7.1. 2. In some exceptional cases (e.g. in congestion situation), the UE may release some PDU session it may have over non-3GPP access to 5GC. 3. Void (no "bearer registration" as described in step 3 of Figure 7.1). 4. As described in TS 23.502 [49]: - in the case of untrusted access, the UE selects an N3IWF as for accessing regular services and sets-up a PDU session for emergency services; - in the case of trusted access, the UE sets-up a PDU session for emergency services. The UE is assigned an IP address at this stage. NOTE 2: When non-3GPP access is WLAN, no specific WLAN AP selection is carried out to support emergency services. 5. Same as step 5 of Figure 7.1. 6. Same as step 6 of Figure 7.1. 7. Same as step 7 of Figure 7.1, except that eCall is not supported via untrusted non-3GPP access. L.4 Location handling When a UE performs an emergency registration or initiates an IMS emergency session over untrusted non-3GPP access to EPC the UE provides location information that is further defined in TS 23.228 [1]. For untrusted non-3GPP access to 5GC, provided location information can only correspond to the UE IP address seen by the N3IWF and used for traffic destined towards the UE. Annex M (normative): IMS emergency service from 5G ProSe Remote UE via 5G ProSe UE-to-Network Relay M.1 General For a 5G ProSe enabled UE as specified in TS 23.304 [53], if the UE does not have access to emergency service via any of the IP-CANs in table E.1, the UE (in the role of 5G ProSe Remote UE) may attempt to obtain emergency service via 5G ProSe UE-to-Network Relay if available. Refer to TS 23.304 [53] for further details how the 5G ProSe Remote UE initiates emergency service via the 5G ProSe UE-to-Network Relay. M.2 UE specific behaviour A 5G ProSe Remote UE identifies that the dialled digits correspond to an emergency call as specified in TS 22.101 [8]. For 5G ProSe Layer-3 UE-to-Network relaying, the 5G ProSe Remote UE may obtain P-CSCF address from the 5G ProSe UE-to-Network Relay via DHCP. NOTE 1: Remote UE obtaining P-CSCF address via DHCP is specified in clause 14A.2.1 of TS 24.379 [57]. The 5G ProSe Remote UE sets the access type "3GPP-NR-ProSe-L2UNR" or "3GPP-NR-ProSe-L3UNR" to P-CSCF for the access via 5G ProSe UE-to-Network Relay depending on whether Layer-2 or Layer-3 relaying is applied. NOTE 2: The access types are specified in clause 7.2.15.3 of TS 24.229 [19]. M.3 Location handling When a 5G ProSe Remote UE performs an emergency registration or initiates an emergency session over a 5G ProSe UE-to-Network Relay, if the operator policy requires network provided location using PCC-based solutions for the UE location, the P-CSCF may retrieve location information from the access network as defined in TS 23.503 [51] and include it in the emergency session request as described in TS 23.228 [1]. NOTE: The user location information contains the 5G ProSe Relay UE's location. When a 5G ProSe Remote UE establishes an emergency call over a 5G ProSe UE-to-Network Relay, the 5G ProSe Remote UE shall include in the IMS emergency request the NR Cell Global Identity (NCGI) obtained from the 5G ProSe UE-to-Network Relay e.g. during the 5G ProSe UE-to-Network Relay Discovery procedure specified in TS 23.304 [53]. When the P-CSCF determines that the emergency call is from a 5G ProSe Remote UE based on the access type "3GPP-NR-ProSe-L3UNR", the P-CSCF provides to the E-CSCF the NCGI and the UE Identity of 5G ProSe UE-to-Network Relay received from the PCF. The E-CSCF uses the NCGI and UE Identity of 5G ProSe UE-to-Network Relay to query the LRF to validate the NCGI provided by the 5G ProSe Remote UE as described in clause 4.3.1. NOTE 1: For the location validation, it is only applied to IPv6 case as specified in TS 23.304 [53]. NOTE 2: If the Remote UE provides location information other than NCGI, then the validation for such information can be skipped. Annex N (normative): Procedures for a Test eCall over IMS N.1 General The purpose of a test eCall over IMS is to provide a high level of assurance that an eCall capable UE and particularly a UE configured for eCall Only Mode (which may be used very rarely) can reliably support a real eCall over IMS when an actual emergency occurs. Test eCalls could be used during a) the initial deployment to see whether devices are working properly, e.g. product acceptance tests; b) product conformity testing and car type-approval in certification labs; c) periodic technical inspection over the lifetime of a vehicle (e.g. once every 1-2 years). A test eCall over IMS includes all features of a real eCall over IMS except for features that are specific to an emergency services call. A test eCall over IMS thus excludes for example the use of an emergency indication at the RRC level, an emergency PDU session or emergency PDN connection, IMS emergency registration and an emergency service indication or eCall type of emergency service indication in a SIP INVITE. However, it includes other aspects of an eCall over IMS as described in clause 7.7, including MSD transfer, MSD update and call back with MSD update. NOTE: A test eCall over IMS is a normal IMS session and not an emergency IMS service and thus is established either using the home IMS alone when not roaming or when roaming with IMS home routing or using both the home and visited IMS when roaming with IMS local breakout. Support for a test eCall over IMS is thus always needed from the home IMS. This support is assumed to be enabled through a IMS roaming agreement when the UE is roaming. However, support by a visited IMS is only needed when roaming with IMS local breakout. Because visited IMS support may not always be provided (e.g. in a VPLMN that does not support a real eCall over IMS), HPLMN operators can choose to enforce use of IMS home routing via a roaming agreement that use the architecture in clause 4.15b of TS 23.228 [1] (Roaming Architecture for Voice over IMS with home routed traffic), for any UE that is eCall capable and would require support for a test eCall over IMS. N.2 Test eCall over IMS Session Establishment to a Test Point Figure N.2-1 illustrates a high level call flow for a Test eCall over IMS session establishment to a test point which may either be NG capable and accessible in the PS domain or non NG capable and accessible only in the CS domain. The UE is assumed to be either already attached to or registered on the PS domain if the UE is not in eCall only mode or camped on the PS domain if the UE is in eCall only mode. NOTE 1: A non NG capable test point that is accessible only in the CS domain may be a legacy test point used to test eCall in the CS domain. It is beneficial to make use of such test points for scenarios where an NG capable test point is not available. Figure N.2-1: Test eCall over IMS Session Establishment to a Test Point 1. The user requests a test eCall. If the UE is not in limited service state and not already attached to or registered on the PS domain, the UE attaches to or registers on the PS domain. The UE performs a normal IMS registration if not already IMS registered. If the UE is in limited service state, the user request is denied and remaining steps are skipped. 2. The UE sends a SIP INVITE to the IMS core. The Request-URI in the SIP INVITE includes a non-emergency service identity that is defined by a national regulator, PSAP or eCall test provider for testing purposes. The UE also includes initial MSD and an indication of support for transfer of updated MSD. The initial MSD indicates a test eCall. 3a. If the public user identity for the test point indicates that the test point is accessible in the PS domain, the IMS core routes the SIP INVITE towards the test point. 3b. If the public user identity for the test point indicates that the test point is accessible in the CS domain, the SIP INVITE is sent to an MGCF/MGW for interfacing to the CS domain. 3c. If step 3b occurs, the MGCF sends an IAM towards the test point. 4a. If step 3a occurs, the test point verifies the correctness of the initial MSD and returns a SIP 200 OK to the IMS core. The SIP 200 OK explicitly includes a positive or negative acknowledgement for the initial MSD and an indication of support for transfer of updated MSD. 4b. If step 3c occurs, the test point returns an ANM to the IMS core. 4c. If step 4b occurs, the MGCF returns a SIP 200 OK to the IMS core. 5. The IMS core returns the 200 OK received in step 4a or step 4c to the UE. 6. The test call establishment is completed with a voice path only. NOTE 2: If the test call establishment fails at any of steps 1 to 6, the UE may fallback to a different PS RAT or to the CS domain if available, the same as for any other normal call. Steps 7 and 8 apply only when the test point is accessible in the CS domain: 7. If the UE did not receive a positive or negative acknowledgement for the initial MSD in the 200 OK at step 5, the UE shall attempt to transfer the MSD to the test point via the eCall Inband Modem, as defined in TS 26.267 [42]. 8. The test point may optionally request an updated MSD from the UE. If step 4a occurred, the test point and UE use the procedure defined in clause 7.7.3 to request and transfer the updated MSD. If step 4c occurred, the test point and UE use the eCall Inband Modem procedure, as defined in TS 26.267 [42]. N.3 Callback from a Test Point with transfer of updated MSD Figure N.3-1 illustrates a high level call flow for callback to a UE from test point with transfer of updated MSD. This scenario may occur immediately after a test eCall over IMS has been established to a test point as defined in Annex N.2 and has been released. Successful completion of the procedure in Figure N.3-1 would provide some assurance that a UE would support a PSAP callback with transfer of updated MSD for a real eCall over IMS. Figure N.3-1: Callback from a Test Point with transfer of updated MSD 1. The UE performs steps 1 to 8 of the procedure shown in Figure N.2-1 followed by a later call release. The UE remains in the PS domain with a normal IMS registration. 2a. If steps 3a and 4a had occurred in Figure N.2-1 as part of step 1, the test point sends a SIP INVITE to the IMS Core and includes a public user identity of the UE obtained in step 1. The INVITE also includes an indication that the test point supports transfer of an updated MSD. 2b. If steps 3c and 4b had occurred in Figure N.2-1 as part of step 1, the test point sends or instigates an IAM to an MGCF/MGW in the HPLMN for interfacing to the CS domain. The IAM contains a public telephone identity of the UE as obtained by the test point at step 1. 2c. If step 2b occurs, the MGCF sends a SIP INVITE to the IMS core in the HPLMN. 4. The IMS core forwards the SIP INVITE from step 2a or step 2c to the UE, after the UE has been paged if IDLE. 5. Voice call establishment is completed with a voice path only. 6a. If step 2a occurred, the test point may instigate the procedure in Figure 7.7.3-1 to request and obtain an updated MSD. The UE shall reject the request for MSD if not received within a configurable time period of release of the test eCall in step 1. 6b. If step 2b occurred, the test point may request and obtain an updated MSD via the eCall Inband Modem, as defined in TS 26.267 [42]. The UE shall reject the request for MSD if not received within a configurable time period of release of the test eCall in step 1 or if the SIP INVITE in step 4 did not identify the calling party using the same non-emergency service identity that was used by the UE to establish the test eCall over IMS at step 2 in Figure N.2-1. NOTE: The configurable time period in steps 6a and 6b is a short period to enable call back to occur as part of the same test eCall from a user perspective and to reduce a risk of transferring updated MSD to an unauthorized calling party. Annex O (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2010-12 SA#50 SP-100694 0182 3 B Retrieval of reference location for emergency session routed via the S-CSCF 11.0.0 2011-01 - - - - - Update of LTE logo to LTE-Advanced logo 11.0.1 2011-03 SA#51 SP-110063 0186 1 A PSAP call back handling in S-CSCF 11.1.0 2011-09 SA#53 SP-110455 0189 1 A Correction of emergency procedures 11.2.0 2011-09 SA#53 SP-110469 0190 1 C Emergency location information for fixed broadband access 11.2.0 2011-12 SA#54 SP-110740 0192 1 F Media support during an IMS emergency session 11.3.0 2011-12 SA#54 SP-110730 0197 1 A Correction of Emergency procedures 11.3.0 2011-12 SA#54 SP-110737 0201 1 A Clarification on S-CSCF handling when receiving emergency session from AS. 11.3.0 2011-12 SA#54 SP-110869 0204 5 A Clarifications on non UE detectable emergency call 11.3.0 2011-12 SA#54 SP-110740 0205 2 B Media support on PSAP callback 11.3.0 2012-03 SA#55 SP-120080 0207 1 B Codecs supported for IMS emergency sessions 11.4.0 2012-03 SA#55 SP-120081 0208 1 B Support of Network-provided Location for IMS functionality 11.4.0 2012-03 SA#55 SP-120080 0212 3 B Domain Selection Rules for IMSESOM with E-UTRAN and UTRAN Access 11.4.0 2012-06 SA#56 SP-120250 0215 1 F Handling of Emergency Registrations at Home IMS 11.5.0 2012-06 SA#56 SP-120250 0216 1 F S-CSCF and AS in Emergency Calls 11.5.0 2012-12 SA#58 SP-120250 0220 1 A Defining S-CSCF procedures for registration and emergency registration relationships 11.6.0 2013-06 SA#60 SP-130309 0223 1 F Domain selection before UE detectable emergency session 11.7.0 2013-06 SA#60 SP-130309 0226 2 F Domain selection in the event emergency bearer services are not supported 11.7.0 2013-09 SA#61 SP-130367 0232 2 A Requirement Alignment for emergency registration and call back 11.8.0 2013-09 SA#61 SP-130376 0234 1 C Requirement Alignment for call back 11.8.0 2013-12 SA#62 SP-130518 0251 1 A Treatment of a 380 Response for an undetected IMS Emergency Call 11.9.0 2014-03 SA#63 SP-140097 0259 1 A Non UE detected emergency call correction when the retry attempt is made in CS domain 11.10.0 2014-03 SA#63 SP-140098 0261 - A Clarification when using a private network for emergency calls 11.10.0 2014-06 SA#64 SP-140247 0264 3 A 380 - Emergency call clarification 11.11.0 2014-09 SA#65 - - - - Update to Rel-12 version (MCC) 12.0.0 2015-03 SA#67 SP-150109 0275 1 F Correction to support of I-WLAN in TS 23.167 12.1.0 2015-09 SA#69 SP-150503 0279 2 B Location to Support Emergency services over WLAN access to EPC 13.0.0 2015-09 SA#69 SP-150503 0280 2 B Introduction of the Support of Emergency services over WLAN access to EPC 13.0.0 2015-12 SA#70 SP-150614 0281 - F Clarification on the UE behaviour when initiates the emergency call 13.1.0 2016-03 SA#71 SP-160162 0283 - F Correction of 3GPP2 specification reference 13.2.0 2016-06 SA#72 SP-160299 0284 9 B eCall over IMS - Initial MSD 14.0.0 2016-06 SA#72 SP-160299 0286 5 B Domain Selection for eCall Over IMS 14.0.0 2016-06 SA#72 SP-160299 0287 2 B Transfer of Updated MSD for eCall Over IMS 14.0.0 2016-06 SA#72 SP-160302 0289 2 B Support for Sh in LRF for NPLI and Support for UE updated Location mid-emergency session over emergency signalling channel 14.0.0 2016-06 SA#72 SP-160302 0292 3 B WLAN to CS session continuity for Emergency call over WLAN 14.0.0 2016-06 SA#72 SP-160302 0294 3 B Determine of Emergency number for call over WLAN 14.0.0 2016-06 SA#72 SP-160304 0295 3 C Support of IMS emergency sessions for roaming users in deployments without IMS-level roaming interfaces 14.0.0 2016-09 SA#73 SP-160659 0282 4 B Providing subscriber ID in case of anonymous emergency calls 14.1.0 2016-09 SA#73 SP-160652 0296 2 B Support for dispatchable civic location for indoor environments for North American. 14.1.0 2016-09 SA#73 SP-160647 0297 1 F Editorial change to Transfer of Updated MSD for eCall Over IMS call flow 14.1.0 2016-09 SA#73 SP-160658 0299 1 B Indication for support of anonymous IMS emergency sessions 14.1.0 2016-09 SA#73 SP-160651 0300 3 C Capturing solution for non UE detectable emergency call for S8 Home routing 14.1.0 2016-09 SA#73 SP-160647 0301 2 F Clarifications when inband is used by a UE to convey MSD 14.1.0 2016-09 SA#73 SP-160647 0302 - F Definition for eCall Over IMS 14.1.0 2016-09 SA#73 SP-160654 0303 2 B Allowing ICS MSC to interact with IMS for IMS emergency call handling. 14.1.0 2016-12 SA#74 SP-160817 0305 3 F Update with SEW2 capabilities 14.2.0 2016-12 SA#74 SP-160816 0306 1 F Correction from IMPI to IMPU 14.2.0 2016-12 SA#74 SP-160817 0311 3 F Correction to emergency number determination for call over WLAN 14.2.0 2016-12 SA#74 SP-160817 0312 - F Enable use of SUPL to locate a UE with WLAN Access 14.2.0 2016-12 SA#74 SP-160817 0313 2 F Unsolicited Provision of UPLI by a UE for WLAN Access 14.2.0 2017-03 SA#75 SP-170053 0314 2 F Clarification of functionality for interconnection of emergency call over II-NNI 14.3.0 2017-03 SA#75 SP-170079 0315 1 F Alignment of emergency procedures 14.3.0 2017-06 SA#76 SP-170367 0316 1 F Downloading emerg number from ePDG 14.4.0 2017-09 SA#77 SP-170723 0318 - F Clarification for voice domain selection rules applicability in Annex H 14.5.0 2017-12 SA#78 SP-170919 0319 2 B Support of IMS Emergency Calls for NG-RAN access to 5GS 15.0.0 2018-03 SA#79 SP-180094 0320 3 F Emergency services over 5GC via untrusted non-3GPP access 15.1.0 2018-03 SA#79 SP-180094 0321 2 F Handling of emergency sessions over untrusted N3GPP access in 5GS 15.1.0 2018-03 SA#79 SP-180094 0324 1 F Delivery of local emergency numbers in NAS 15.1.0 2018-03 SA#79 SP-180094 0325 2 F Addition of Emergency Services Support using Fallback to Domain Selection Rules 15.1.0 2018-06 SA#80 SP-180479 0326 1 F Clarification on Domain Selection for Emergency Service. 15.2.0 2018-06 SA#80 SP-180475 0327 1 F Domain selection for eCall over IMS 15.2.0 2018-06 SA#80 SP-180475 0329 - F Correction on domain selection for eCall over IMS 15.2.0 2018-06 SA#80 SP-180475 0330 2 F Correction to NOTE 5 in domain selection for Emergency services 15.2.0 2018-09 SA#81 SP-180712 0331 2 F Update on Domain Selection Rules for emergency session attempts 15.3.0 2018-09 SA#81 SP-180712 0332 - F UE handling of emergency numbers list when using untrusted non-3GPP access to 5GC 15.3.0 2018-09 SA#81 SP-180711 0334 - A Correct conditions for using valid local emergency number list 15.3.0 2018-09 SA#81 SP-180712 0335 - F Domain selection for dual registration mode UE 15.3.0 2018-09 SA#81 SP-180712 0336 2 F Support of eCall and emergency call when eUTRAN is connected to 5GS and EPS 15.3.0 2018-12 SA#82 SP-181083 0337 1 F Correct procedures for obtaining local emergency number list 15.4.0 2018-12 SA#82 SP-181083 0338 1 F Correct validity of local emergency number list 15.4.0 2018-12 SA#82 SP-181083 0339 1 F Correcting usage of emergency service indication and emergency session indication 15.4.0 2018-12 SA#82 SP-181083 0341 - C More Flexible Domain selection for Emergency Calls using the PS Domain 15.4.0 2019-09 SA#85 SP-190604 0346 2 F Correcting principle stating that procedures for untrusted access are to be used even over trusted WLAN 15.5.0 2019-09 SA#85 SP-190609 0344 1 F Enabling emergency call using trusted non-3GPP access to 5GC 16.0.0 2019-12 SA#86 SP-191089 0350 3 F Support of IMS emergency sessions for roaming users in 5GS deployments without IMS-level roaming interfaces 16.1.0 2020-07 SA#87 SP-200420 0355 - A Correction for IMS Emergency Registration and Session Establishment 16.2.0 2020-07 SA#87 SP-200552 0357 1 C Domain selection for support of NG-eCall over NR 16.2.0 2020-12 SA#90E SP-200959 0358 1 F Correction of reference for Sh interface 16.3.0 2021-03 SA#91E SP-210088 0359 - B Support for Caller Identity Attestation and Assertion of Emergency sessions 17.0.0 2021-06 SA#92E SP-210332 0364 1 F NG eCall domain selection corrections 17.1.0 2021-06 SA#92E SP-210353 0360 4 C KI#3: Support for IMS emergency over SNPN 17.1.0 2021-06 SA#92E SP-210342 0361 2 B Support of IMS Emergency Calls over NR Satellite Access 17.1.0 2021-09 SA#93E SP-210936 0365 - F Usage of alternate P-CSCF for emergency registration 17.2.0 2023-03 SA#99 SP-230047 0369 4 B Introducing 5G ProSe ph2 function for KI#7 (Support of Emergency for UE-to-Network Relaying) 18.0.0 2023-03 SA#99 SP-230080 0370 1 F Emergency call domain selection after 2G/3G radio switch off and/or UE in limited service state 18.0.0 2023-06 SA#100 SP-230449 0372 3 B KI#7_Not perform UE identities verification for the remote UE 18.1.0 2023-12 SA#102 SP-231247 0373 4 F Location validation for the L3 remote UE by the E-CSCF 18.2.0 2024-12 SA#106 SP-241484 0375 2 C Alignment of eCall over IMS with CEN 19.0.0 2024-12 SA#106 SP-241484 0376 2 C Support of MSD transfer for a PSAP Callback for eCall over IMS 19.0.0 2024-12 SA#106 SP-241484 0377 2 C Support of a Test eCall over IMS 19.0.0
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
1 Scope
|
This document specifies the functional architecture, procedures and information flows needed to support mission critical services in the IOPS mode of operation. IOPS mode of operation allows an isolated 3GPP network to maintain a level of MC services in case the backhaul connection is lost. For example, for EPS the IOPS mode of operation is defined in 3GPP TS 23.401 [2].
The corresponding service requirements are defined in 3GPP TS 22.346 [9] and 3GPP TS 22.280 [11].
The present document is applicable to support mission critical services in the IOPS mode of operation for 3GPP access types, such as E-UTRAN or 5G.
The functional architecture to support mission critical services in the IOPS mode of operation can be used for public safety applications and also for general commercial applications, e.g. utility companies and railways, for the case of a backhaul failure.
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[3] 3GPP TS 23.280: "Common functional architecture to support mission critical services ".
[4] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[5] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[6] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[7] 3GPP TS 23.002: "Network Architecture".
[8] 3GPP TS 23.203: "Policy and charging control architecture".
[9] 3GPP TS 22.346: "Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1".
[10] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[11] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[12] 3GPP TS 22.289: "Mission Critical services over 5G System; Stage 2".
[13] 3GPP TS 23.501: "System architecture for the 5G System (5GS)".
[14] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services".
[15] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
3 Definitions and abbreviations
| |
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
IOPS MC system: The collection of application functions and enabling capabilities required to support mission critical services in the IOPS mode of operation.
IOPS mode of operation: Provides the ability to maintain a level of communications for MC users in case the backhaul connection is lost.
IOPS 3GPP system: It is a group of 3GPP core entities that are either co-sited with or co-located in an IOPS capable base station.
Broadcast/multicast session: Is either the MBMS bearer in EPS or the MBS session in 5GS.
Unicast session: A unicast session is either a unicast bearer in EPS, or a unicast PDU session in 5GS.
For the purposes of the present document, the following terms given in 3GPP TS 23.280 [3] apply
MC service
MC service client
MC service group
MC service ID
MC service user
MC service UE
MC user
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
APN Access Point Name
DNN Data Network Name
IOPS Isolated Operation for Public Safety
EPC Evolved Packet Core
EPS Evolved Packet System
MBMS Multimedia Broadcast and Multicast Service
MC Mission Critical
PLMN Public Land Mobile Network
|
17ba42c440e050d74c1fc2ffcb25f033
|
23.180
|
4 Introduction
|
For the case of a backhaul failure, mission critical (MC) services (e.g. MCPTT defined in 3GPP TS 23.379 [5] and MCData defined in 3GPP TS 23.282 [6]) can also be supported based on the availability of an isolated operation for public safety (IOPS) MC system. The IOPS MC system provides MC services support to the MC service UE via a single public land mobile network (PLMN) dedicated to the IOPS mode of operation, for example as defined in 3GPP TS 23.401 [2].
A common functional architecture, including application plane and signalling plane, to support MC services in the IOPS mode of operation is specified in this document.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.