22.5.16 NB-IoT / Normal tracking area update / Rejected / EPS service not allowed /EPS services not allowed in this PLMN
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
22.5.16.1 Test Purpose (TP)
(1)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to "EPS service not allowed" }
then { UE considers the USIM as invalid for EPS services and enters state EMM-DEREGISTERED }
(2)
with { The UE is in the state EMM-DEREGISTERED }
ensure that {
when { UE is powered up or switched on }
then { UE sends ATTACH REQUEST message with ‘Old GUTI or IMSI IE = ‘IMSI"}
(3)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with the reject cause set to ‘EPS services not allowed in this PLMN’ }
then { UE deletes the GUTI, the last visited registered TAI and KSI and UE deletes the list of equivalent PLMNs and UE enters state EMM-DEREGISTERED.PLMN-SEARCH and UE stores the PLMN in the "forbidden PLMNs for GPRS service" }
(4)
with { UE in EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden PLMNs for GPRS service" }
ensure that {
when { UE enters a cell which is in the "forbidden PLMNs for GPRS service" }
then { UE doesn’t perform an attach procedure }
}
(5)
with { UE in EMM-DEREGISTERED.PLMN-SEARCH state and a PLMN is stored in the "forbidden PLMNs for GPRS service" }
ensure that {
when { UE enters a cell which is not in the "forbidden PLMNs for GPRS service" }
then { UE initiates an attach procedure }
}
(6)
with { UE is switched off and a PLMN is stored in the ‘forbidden PLMNs for GPRS service’ }
ensure that {
when { UE is power ON in a cell with forbidden PLMNs for GPRS service }
then { UE initiates an attach procedure }
22.5.16.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.5.3.2.5.
[TS 24.301 clause5.5.3.2.5]
If the tracking area updating cannot be accepted by the network, the MME sends a TRACKING AREA UPDATE REJECT message to the UE including an appropriate EMM cause value.
…
The UE shall take the following actions depending on the EMM cause value received in the TRACKING AREA UPDATE REJECT message.
…
#7 (EPS services not allowed);
The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.7a. The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.
If the EPS update type is "periodic updating", a UE operating in CS/PS mode 1 or CS/PS mode 2 of operation, which is IMSI attached for non-EPS services, is still IMSI attached for non-EPS services. The UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, shall attempt to select GERAN or UTRAN radio access technology and shall proceed with appropriate MM specific procedure according to the MM service state. The UE shall not reselect E‑UTRAN radio access technology until switching off or the UICC containing the USIM is removed.
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008 [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value.
…
#14 (EPS services not allowed in this PLMN);
The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3). Furthermore the UE shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-DEREGISTERED.PLMN-SEARCH.
The UE shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the UE is configured to use timer T3245 (see 3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.7a.
If the EPS update type is "TA updating", or the EPS update type is "periodic updating" and the UE is in PS mode 1 or PS mode 2 of operation, the UE shall perform a PLMN selection according to 3GPP TS 23.122 [6]. In this case, the UE supporting S1 mode only shall delete the list of equivalent PLMNs before performing the procedure.
If the EPS update type is "periodic updating", a UE operating in CS/PS mode 1 or CS/PS mode 2 of operation, which is IMSI attached for non-EPS services, is still IMSI attached for non-EPS services and shall proceed as follows:
– a UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED;
– a UE operating in CS/PS mode 1 of operation and supporting A/Gb mode or Iu mode may select GERAN or UTRAN radio access technology and proceed with the appropriate MM specific procedure according to the MM service state. In this case, the UE shall disable the E-UTRA capability (see subclause 4.5);
– a UE operating in CS/PS mode 1 of operation and supporting A/Gb mode or Iu mode may perform a PLMN selection according to 3GPP TS 23.122 [6];
– a UE operating in CS/PS mode 1 of operation and supporting S1 mode only, or operating in CS/PS mode 2 of operation shall delete the list of equivalent PLMNs and shall perform a PLMN selection according to 3GPP TS 23.122 [6].
If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing area updating attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value.
22.5.16.3 Test description
22.5.16.3.1 Pre-test conditions
System Simulator:
– Only three Ncells are active at a time
– Three NB-IoT cells Ncell 50, Ncell 51, and Ncell 55 are active from steps 1 to 34;
– Ncell 50 (belongs to TAI-1, home PLMN) is set to "Serving cell";
– Ncell 51 (belongs to TAI-2, home PLMN) is set to "Non-suitable cell";
– Ncell 55 (belongs to TAI-7, visited PLMN) is set to "Non-suitable cell";
– Three NB-IoT cells Ncell 55, Ncell 56, and Ncell 57 are active from steps 35 to 104;
– Ncell 55 (belongs to TAI-7, visited PLMN) is set to "Serving cell";
– Ncell 56 (belongs to TAI-8, visited PLMN, another TAC) is set to "Non-suitable cell";
– system information combination 3 as defined in TS 36.508[18] clause 8.1.4.3.1.2 is applied in NB-IoT cells.
Table 22.5.16.3.1-1: Time instances of cell power level
Parameter |
Unit |
Ncell 50 |
Ncell 51 |
Ncell 55 |
Ncell 56 |
|
T0 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-85 |
-120 |
-120 |
Off |
T1 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-120 |
-85 |
-120 |
Off |
T2 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-85 |
-120 |
-120 |
Off |
T3 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-120 |
-120 |
-85 |
Off |
T4 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-85 |
-120 |
-120 |
Off |
T5 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-85 |
Off |
T6 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-120 |
-85 |
T7 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-85 |
-120 |
T8 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-85 |
Off |
-120 |
-120 |
T9 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-120 |
Off |
-85 |
-120 |
Preamble:
– The UE is in state Registered, Idle Mode (State 3-NB) on Ncell 50 with power settings "T0" in table 22.5.16.3.1-1 according to [18].
22.5.16.3.2 Test procedure sequence
Table 22.5.16.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
Set the cell type of Ncell 50 to the "Non-Suitable cell". Set the cell type of Ncell 51 to the "Serving cell" according to row T1 of table 22.5.16.3.1-1. |
– |
– |
– |
– |
2 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 51. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
3 |
The SS transmits a TRACKING AREA UPDATE REJECT message with EMM cause = " EPS services not allowed ". |
<– |
TRACKING AREA UPDATE REJECT |
– |
– |
4 |
The SS releases the RRC connection. |
– |
– |
– |
– |
5 |
Set the cell type of Ncell 50 to the "Serving cell". Set the cell type of Ncell 51 to the "Non-Suitable cell" according to row T2 of table 22.5.16.3.1-1. |
– |
– |
– |
– |
6 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 90 seconds on Ncell 50? Note: Ncell 50 belongs to the same PLMN where the UE was rejected but a different TAC |
–> |
ATTACH REQUEST |
1 |
F |
7 |
The user initiates an attach by MMI or by AT command. |
– |
– |
– |
– |
8 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 90 seconds on Ncell 50? |
–> |
ATTACH REQUEST |
1 |
F |
9 |
Set the cell type of Ncell 50 to the " Non-Suitable cell". Set the cell type of Ncell 55 to the "Serving cell" according to row T3 of table 22.5.16.3.1-1. |
– |
– |
– |
– |
10 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 90 seconds on Ncell 55? Note: Ncell 55 belongs to a PLMN which is not the same like the one on which the UE was rejected. |
–> |
ATTACH REQUEST |
1 |
F |
11 |
The user initiates an attach by MMI or by AT command. |
– |
– |
– |
– |
12 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 90 seconds on Ncell 55? |
–> |
ATTACH REQUEST |
1 |
F |
13 |
If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. |
– |
– |
– |
– |
14 |
Set the cell type of Ncell 50 to the "Serving cell". Set the cell type of Ncell 55 to the "Non-Suitable cell" according to row T4 of table 22.5.16.3.1-1. |
– |
– |
– |
– |
15 |
The UE is brought back to operation or the USIM is inserted. |
– |
– |
– |
– |
16 |
Check: Does the UE transmit an ATTACH REQUEST message on Ncell 50? |
–> |
ATTACH REQUEST |
2 |
P |
17-33 |
Steps 5 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2.3 are performed on Ncell 50. |
– |
– |
– |
– |
34 |
The SS releases the RRC connection. |
– |
– |
– |
– |
If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. |
|||||
EXCEPTION: Step 34a describes behaviour |
|||||
34a |
If pc_SwitchOnOff or pc_USIM_Removal then UE sends DETACH REQUEST message |
–> |
DETACH REQUEST |
– |
– |
35 |
Set the cell type of Ncell 55 to the "Serving cell" according to row T5 of table 22.5.16.3.1-1. |
– |
– |
– |
– |
36-56 |
Steps 1 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2.3 are performed on Ncell 55. |
– |
– |
– |
– |
57 |
The SS releases the RRC connection. |
– |
– |
– |
– |
Set the cell type of Ncell 56 to the "Serving cell". Set the cell type of Ncell 55 to the "Non-Suitable cell" according to row T6 of table 22.5.16.3.1-1. |
|||||
58 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 56. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
59 |
The SS transmits a TRACKING AREA UPDATE REJECT message with EMM cause = "EPS services not allowed in this PLMN ". |
<– |
TRACKING AREA UPDATE REJECT |
– |
– |
60 |
The SS releases the RRC connection. |
– |
– |
– |
– |
61 |
Set the cell type of Ncell 55 to the "Serving cell". Set the cell type of Ncell 56 to the "Non-Suitable cell" according to row T7 of table 22.5.16.3.1-1. |
– |
– |
– |
– |
62 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 90 seconds on Ncell 55? Note: Ncell 55 belongs to the same PLMN where the UE was rejected but a different TAC |
–> |
ATTACH REQUEST |
3 |
F |
63 |
The user initiates an attach by MMI or by AT command. |
– |
– |
– |
– |
64 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 90 seconds on Ncell 55? |
–> |
ATTACH REQUEST |
4 |
F |
65 |
Set the cell type of Ncell 55 to the " Non-Suitable cell". Set the cell type of Ncell 50 to the "Serving cell" according to row T8 of table 22.5.16.3.1-1. |
– |
– |
– |
– |
66 |
Check: Does the UE send ATTACH REQUEST message on Ncell 50? Note: Ncell 50 belongs to a PLMN which is not the same like the one on which the UE was rejected. |
–> |
ATTACH REQUEST |
5 |
P |
67-82 |
steps 5 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2.3 are performed on Ncell 50. |
– |
– |
– |
– |
83 |
The SS releases the RRC connection. |
– |
– |
– |
– |
84 |
If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. |
– |
– |
– |
– |
EXCEPTION: Step 84a describes behaviour |
|||||
84a |
If pc_SwitchOnOff or pc_USIM_Removal then UE sends DETACH REQUEST message |
–> |
DETACH REQUEST |
– |
– |
85 |
Set the cell type of Ncell 55 to the "Serving cell". set the cell type of Ncell 50 to the "Non-Suitable cell" according to row T9 of table 22.5.16.3.1-1. |
– |
– |
– |
– |
86 |
The UE is brought back to operation or the USIM is inserted. |
– |
– |
– |
– |
87 |
Check: Does the UE transmit an ATTACH REQUEST message on Ncell 55? |
–> |
ATTACH REQUEST |
6 |
P |
88-103 |
steps 5 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2.3 are performed on Ncell 55. |
– |
– |
– |
– |
104 |
The SS releases the RRC connection. |
– |
– |
– |
– |
22.5.16.3.3 Specific message contents
Table 22.5.16.3.3-1: Message TRACKING AREA UPDATE REJECT (step 3, Table 22.5.16.3.2-1)
Derivation path: 36.508 table 4.7.2-24 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EMM cause |
00000111 |
#7 “EPS services not allowed”. |
Table 22.5.16.3.3-2: Message ATTACH REQUEST (step 16, Table 22.5.16.3.2-1)
Derivation path: 36.508 table 4.7.2-4 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Old GUTI or IMSI |
IMSI |
Table 22.5.16.3.3-3: Message TRACKING AREA UPDATE REJECT (step 59, Table 22.5.16.3.2-1)
Derivation path: 36.508 table 4.7.2-24 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EMM cause |
00001110 |
#14 “EPS services not allowed in this PLMN”. |
Table 22.5.16.3.3-4: Message ATTACH REQUEST (step 66, Table 22.5.16.3.2-1)
Derivation path: 36.508 table 4.7.2-4 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Old GUTI or IMSI |
IMSI |
||
Last visited registered TAI |
Not present |
Table 22.5.16.3.3-5: Message ATTACH REQUEST (step 87, Table 22.5.16.3.2-1)
Derivation path: 36.508 table 4.7.2-4 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Old GUTI or IMSI |
IMSI |
||
Last visited registered TAI |
TAI-1 |
Table 22.5.16.3.3-6: SystemInformationBlockType5-NB for Ncell 50 and Ncell51 (preamble and all steps, Table 22.5.16.3.3-1)
Derivation Path: 36.508 table 8.1.4.3.3-4 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType5-NB-r13 ::= SEQUENCE { |
|||
interFreqCarrierFreqList-NB-r13 ::= SEQUENCE { |
|||
dl-CarrierFreq-r13 ::= SEQUENCE { |
|||
carrierFreq-r13 |
f2 |
||
carrierFreqOffset-r13 |
f2 |
||
} |
|||
} |
|||
} |
Table 22.5.16.3.3-7: SystemInformationBlockType5-NB for Ncell 55 and Ncell 56 (preamble and all steps, Table 22.5.16.3.3-1)
Derivation Path: 36.508 table 8.1.4.3.3-4 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType5-NB-r13 ::= SEQUENCE { |
|||
interFreqCarrierFreqList-NB-r13 ::= SEQUENCE { |
|||
dl-CarrierFreq-r13 ::= SEQUENCE { |
|||
carrierFreq-r13 |
f1 |
||
carrierFreqOffset-r13 |
f1 |
||
} |
|||
} |
|||
} |