22.5.14 NB-IoT / Attach / Rejected / Tracking Area not allowed / Roaming not allowed in this tracking area / No suitable cells in tracking area
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.14.1 Test Purpose (TP)
(1)
with { UE has sent an ATTACH REQUEST message PDN CONNECTIVITY REQUEST message or an ESM DUMMY MESSAGE }
ensure that {
when { UE receives an ATTACH REJECT message with the reject cause set to "Tracking area not allowed" }
then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, UE deletes the GUTI, last visited registered TAI and KSI, UE enters the state EMM-DEREGISTERED.LIMITED-SERVICE and UE stores the current TAI in the list of "forbidden tracking areas for regional provision of service" }
}
(2)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of "forbidden tracking areas for regional provision of service"}
ensure that {
when { serving cell belongs to TAI where UE was rejected }
then { UE does not attempt to attach on any other cell }
}
(3)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of "forbidden tracking areas for regional provision of service"}
ensure that {
when { UE re-selects a new cell in the same TAI it was already rejected }
then { UE does not attempt to attach }
}
(4)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of "forbidden tracking areas for regional provision of service"}
ensure that {
when { UE enters a cell belonging to a tracking area not in the list of "forbidden tracking areas for regional provision of service"}
then { UE attempts to attach with IMSI }
}
(5)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the list of "forbidden tracking areas for regional provision of service" contains more than one TAI}
ensure that {
when { UE re-selects a cell belonging to one of the TAIs in the list of "forbidden tracking areas for regional provision of service" }
then { UE does not attempt to attach }
}
(6)
with { UE is switched off }
ensure that {
when { UE is powered on in the cell belonging to the TAI which was in the list of "forbidden tracking areas for regional provision of service" before the UE was switched off }
then { UE performs registration on that cell }
}
(7)
with { the UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message or an ESM DUMMY MESSAGE }
ensure that {
when { the UE receives an ATTACH REJECT message with the reject cause set to "roaming not allowed in this tracking area" }
then { the UE sets the EPS update status to EU3 ROAMING NOT ALLOWED and the UE deletes the GUTI, the last visited registered TAI and KSI and the UE enters the state EMM-DEREGISTERED.LIMITED-SERVICE or optionally EMM-DEREGISTERED.PLMN-SEARCH and the UE stores the current TAI in the list of "forbidden tracking areas for roaming" }
}
(8)
with { the UE is in EMM-DEREGISTERED.LIMITED-SERVICE or EMM-DEREGISTERED.PLMN-SEARCH state and the TAI of the current cell belongs to the list of "forbidden tracking areas for roaming"}
ensure that {
when { the UE enters a cell belonging to a tracking area not in the list of "forbidden tracking areas for roaming"}
then { the UE attempts to attach with IMSI }
}
(9)
with { the UE is in EMM-DEREGISTERED.LIMITED-SERVICE or EMM-DEREGISTERED.PLMN-SEARCH state and the list of "forbidden tracking areas for roaming" contains more than one TAI}
ensure that {
when { the UE selects a cell belonging to one of the TAIs in the list of "forbidden tracking areas for roaming" }
then { the UE does not attempt to attach }
}
(10)
with { the UE is switched off or the UICC containing the USIM is removed }
ensure that {
when { UE is powered on in the cell belonging to the TAI which was in the list of "forbidden tracking areas for roaming" before the UE was switched off or the USIM is inserted again on that cell }
then { UE performs registration on that cell }
}
(11)
with { the UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message or an ESM DUMMY MESSAGE }
ensure that {
when { the UE receives an ATTACH REJECT message with the reject cause set to "roaming not allowed in this tracking area" }
then { the UE performs a PLMN selection }
}
(12)
with { the UE has sent an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message or an ESM DUMMY MESSAGE }
ensure that {
when { the UE receives an ATTACH REJECT message with the EMM cause set to "No suitable cells in tracking area" }
then { the UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, UE deletes any GUTI, last visited registered TAI and KSI and the UE enters the state EMM-DEREGISTERED.LIMITED-SERVICE and the UE stores the current TAI in the list of "forbidden tracking areas for roaming" }
}
(13)
with { the UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of "forbidden tracking areas for roaming"}
ensure that {
when { the UE re-selects a cell that belongs to the TAI where UE was rejected }
then { the UE does not attempt to attach }
}
(14)
with { the UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of "forbidden tracking areas for roaming" and KSI was deleted }
ensure that {
when { in the same PLMN, the UE enters a cell which provides normal service and belongs to a tracking area not in the list of "forbidden tracking areas for roaming" }
then { the UE attempts to attach with IMSI }
}
(15)
with { the UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the current TAI in the list of "forbidden tracking areas for roaming"}
ensure that {
when { there are cells in the same PLMN and other PLMN that provide normal service and belong to tracking areas not in the list of "forbidden tracking areas for roaming" }
then { UE attempts to attach to the cell in the same PLMN }
}
(16)
with { UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and the list of "forbidden tracking areas for roaming" contains more than one TAI}
ensure that {
when { UE re-selects a cell that belongs to one of the TAIs in the list of "forbidden tracking areas for roaming" }
then { UE does not attempt to attach }
}
(17)
with { UE is switched off }
ensure that {
when { UE is powered on in the cell belonging to the TAI which was in the list of "forbidden tracking areas for roaming" before the UE was switched off }
then { UE attempts to attach }
}
22.5.14.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.3.2, 5.5.1.2.2, 5.5.1.2.5, 5.2.2.3.2, 5.2.4.4, Annex C and TS 36.304 clause 4.3, 5.2.4.4.
[TS 24.301, clause 5.3.2]
The UE shall store a list of "forbidden tracking areas for roaming", as well as a list of "forbidden tracking areas for regional provision of service". These lists shall be erased when the UE is switched off or when the UICC containing the USIM is removed, and periodically (with a period in the range 12 to 24 hours).
…
In S1 mode, the UE shall update the suitable list whenever an ATTACH REJECT, TRACKING AREA UPDATE REJECT, SERVICE REJECT or DETACH REQUEST message is received with the EMM cause #12 "tracking area not allowed", #13 "roaming not allowed in this tracking area", or #15 "no suitable cells in tracking area".
Each list shall accommodate 40 or more TAIs. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted.
[TS 24.301, clause 5.5.1.2.2]
In state EMM-DEREGISTERED, the UE initiates the attach procedure by sending an ATTACH REQUEST message to the MME, starting timer T3410 and entering state EMM-REGISTERED-INITIATED (see example in figure 5.5.1.2.2.1). If timer T3402 is currently running, the UE shall stop timer T3402. If timer T3411 is currently running, the UE shall stop timer T3411.
The UE shall include the IMSI in the EPS mobile identity IE in the ATTACH REQUEST message if the selected PLMN is neither the registered PLMN nor in the list of equivalent PLMNs and:
– the UE is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17]; or
– the UE is in NB-S1 mode….
…
If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, or if the UE wants to request PDN connection with the attach procedure, the UE shall send the ATTACH REQUEST message together with a PDN CONNECTIVITY REQUEST message contained in the ESM message container IE.
If EMM-REGISTERED without PDN connection is supported by the UE and the MME, and the UE does not want to request PDN connection with the attach procedure, the UE shall send the ATTACH REQUEST message together with an ESM DUMMY MESSAGE contained in the ESM message container information element..
…
[TS 24.301, clause 5.5.1.2.5]
If the attach request cannot be accepted by the network, the MME shall send an ATTACH REJECT message to the UE including an appropriate EMM cause value.
…
Upon receiving the ATTACH REJECT message, if the message is integrity protected or contains a reject cause other than EMM cause value #25, the UE shall stop timer T3410.
…
#12 (Tracking area 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. Additionally, the UE shall reset the attach attempt counter.
In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service" and enter the state EMM-DEREGISTERED.LIMITED-SERVICE.
In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE 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 A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value.
#13 (Roaming not allowed in this tracking area);
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 delete the list of equivalent PLMNs and reset the attach attempt counter.
In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for roaming". Additionally, the UE shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE or optionally EMM-DEREGISTERED.PLMN-SEARCH. The UE shall perform a PLMN selection according to 3GPP TS 23.122 [6].
In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE 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 A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value.
…
#15 (No suitable cells in tracking area);
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. Additionally, the UE shall reset the attach attempt counter.
In S1 mode, the UE shall:
– store the current TAI in the list of "forbidden tracking areas for roaming" and enter the state EMM-DEREGISTERED.LIMITED-SERVICE. AND
– if the Extended EMM cause IE with value "E-UTRAN not allowed" is included in the ATTACH REJECT message, the UE supports "E-UTRA Disabling for EMM cause #15", and the "E-UTRA Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17] is present and set to enabled; then the UE shall disable the E-UTRA capability as specified in subclause 4.5 and search for a suitable cell in GERAN or UTRAN radio access technology; otherwise. the UE shall search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304 [21].
In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE 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 A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value.
…
[TS 24.301, clause 5.2.2.3.2]
The UE shall initiate an attach or combined attach procedure when entering a cell which provides normal service.
[TS 24.301, Annex C (normative)]
The following EMM parameters shall be stored on the USIM if the corresponding file is present:
– GUTI;
– last visited registered TAI;
– EPS update status;
– Allowed CSG list;
– Operator CSG list; and
– EPS security context parameters from a full native EPS security context (see 3GPP TS 33.401 [19]).
The presence and format of corresponding files on the USIM is specified in 3GPP TS 31.102 [17].
If the corresponding file is not present on the USIM, these EMM parameters except allowed CSG list are stored in a non-volatile memory in the ME together with the IMSI from the USIM. The allowed CSG list is stored in a non-volatile memory in the ME if the UE supports CSG selection. These EMM parameters can only be used if the IMSI from the USIM matches the IMSI stored in the non-volatile memory; else the UE shall delete the EMM parameters.
…
[TS 36.304, clause 4.3]
…
suitable cell:
A "suitable cell" is a cell on which the UE may camp on to obtain normal service. The UE shall have a valid USIM and such a cell shall fulfil all the following requirements.
– The cell is part of either:
– the selected PLMN, or:
– the registered PLMN, or:
– a PLMN of the Equivalent PLMN list
– For a CSG cell, the cell is a CSG member cell for the UE;
According to the latest information provided by NAS:
– The cell is not barred, see subclause 5.3.1;
– The cell is part of at least one TA that is not part of the list of "forbidden tracking areas for roaming" [4], which belongs to a PLMN that fulfils the first bullet above;
– The cell selection criteria are fulfilled, see subclause 5.2.3.2;
If more than one PLMN identity is broadcast in the cell, the cell is considered to be part of all TAs with TAIs constructed from the PLMN identities and the TAC broadcast in the cell.
[TS 36.304 subclause 5.2.4.4]
…
If the highest ranked cell or best cell according to absolute priority reselection rules is an intra-frequency or inter-frequency cell which is not suitable due to being part of the "list of forbidden TAs for roaming" or belonging to a PLMN which is not indicated as being equivalent to the registered PLMN, the UE shall not consider this cell and other cells on the same frequency, as candidates for reselection for a maximum of 300s. If the UE enters into state any cell selection, any limitation shall be removed. If the UE is redirected under E-UTRAN control to a frequency for which the timer is running, any limitation on that frequency shall be removed.
…
22.5.14.3 Test description
22.5.14.3.1 Pre-test conditions
System Simulator:
– a maximum of 3 cells are active at any given time. For cell setup refer to Table 8.1.4.2-3: Default NAS parameters for simulated Ncells in TS 36.508[18].
– NB-IOT system information combination 2 as defined in TS 36.508[18] clause 8.1.4.3.1.1 is used in all cells
Table 22.5.14.3-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Ncell 50 |
Ncell 51 |
Ncell 55 |
Ncell 56 |
Ncell 62 |
|
|
T1 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-85 |
-97 |
Off |
Off |
Off |
|
T2 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-97 |
-85 |
Off |
Off |
Off |
|
T3 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-85 |
-97 |
Off |
Off |
Off |
|
T4 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-85 |
-120 |
Off |
Off |
Off |
|
T5 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-85 |
Off |
Off |
|
T6 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-91 |
-85 |
Off |
|
T7 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-85 |
Off |
Off |
|
T8 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
-97 |
Off |
-85 |
Off |
Off |
|
T9 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-85 |
Off |
Off |
|
T10 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-85 |
Off |
-91 |
|
T11 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-91 |
Off |
-85 |
|
T12 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-85 |
Off |
Off |
|
T13 |
– |
– |
– |
– |
– |
– |
– |
|
T14 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-91 |
-85 |
-85 |
|
T15 |
Cell-specific NRS EPRE |
dBm/ 15kHz |
Off |
Off |
-91 |
-85 |
Off |
UE:
– the UE is configured to initiate EPS attach;
Preamble:
– the UE is in state Switched OFF (State 1-NB) according to TS 36.508 [18].
22.5.14.3.2 Test procedure sequence
Table 22.5.14.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS adjusts the cell power levels according to row T1 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 50 unless explicitly stated otherwise. All ATTACH REJECT messages must be sent integrity protected. |
– |
– |
– |
– |
|
2 |
The UE is switched on. |
– |
– |
– |
– |
|
3 |
The UE transmits an ATTACH REQUEST message. IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
– |
– |
|
4 |
The SS transmits an ATTACH REJECT message, EMM cause = "Tracking area not allowed". (The list of "forbidden tracking areas for regional provision of service " in the UE should now contain TAI-1) |
<– |
ATTACH REJECT |
– |
– |
|
5 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
6 |
Check: Does the UE transmit the ATTACH REQUEST message in the next 30 seconds on Ncell 50 or Ncell 51? |
–> |
ATTACH REQUEST |
1, 2 |
F |
|
7 |
The user initiates an attach by MMI or by AT command. |
– |
– |
– |
– |
|
8 |
Check: Does the UE transmit the ATTACH REQUEST message in the next 30 seconds? |
–> |
ATTACH REQUEST |
1 |
F |
|
9 |
SS adjusts the cell power levels according to row T2 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 51 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
10 |
Check: Does the UE transmit the ATTACH REQUEST message? IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
1,4 |
P |
|
10A-10D |
Steps 5 to 8 from procedure 8.1.5.2.3 in TS 36.508. |
– |
– |
– |
– |
|
11 |
The SS transmits an ATTACH REJECT message, EMM cause = "Tracking area not allowed". (The list of "forbidden tracking areas for regional provision of service " in the UE should now contain TAI-1 and TAI-2) |
<– |
ATTACH REJECT |
– |
– |
|
12 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
13 |
SS adjusts the cell power levels according to row T3 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 50 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
14 |
Check: Does the UE transmit the ATTACH REQUEST message in the next 30 seconds? |
–> |
ATTACH REQUEST |
1, 3, 5 |
F |
|
15 |
If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. |
– |
– |
– |
– |
|
16 |
SS adjusts the cell power levels according to row T4 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 50 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
17 |
The UE is brought back to operation or the USIM is inserted. |
– |
– |
– |
– |
|
18 |
Check: Does the UE transmit the ATTACH REQUEST message? IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
1, 6 |
P |
|
19-29 |
The attach procedure is completed by executing steps 5 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2. |
– |
– |
– |
– |
|
29A |
The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE. |
||||
|
29B |
The UE is switched of or the USIM is removed. |
||||
|
29C |
The UE transmits an RRCConnectionRequest-NB message. |
||||
|
29D |
SS transmits an RRCConnectionSetup-NB message. |
||||
|
29E |
The UE transmits an RRCConnectionSetupComplete-NB message. |
||||
|
29F |
The UE transmits a DETACH REQUEST message with the Detach Type IE indicating "switch off". |
–> |
DETACH REQUEST |
||
|
29G |
The SS transmits an RRCConnectionRelease-NB message. |
||||
|
30 |
SS adjusts the cell power levels according to row T5 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 55 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
31 |
The UE is switched on. |
– |
– |
– |
– |
|
32 |
The UE transmits an ATTACH REQUEST message. IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
– |
– |
|
33 |
The SS transmits an ATTACH REJECT message, EMM cause = "roaming not allowed in this tracking area ". (The list of "forbidden tracking areas for roaming" in the UE should now contain TAI-7) |
<– |
ATTACH REJECT |
– |
– |
|
34 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
35 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds? |
–> |
ATTACH REQUEST |
7,11 |
F |
|
36 |
The user initiates an attach by MMI or by AT command. |
– |
– |
– |
– |
|
37 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds? |
–> |
ATTACH REQUEST |
7,11 |
F |
|
– |
The following messages are to be observed on Ncell 56 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
38 |
SS adjusts the cell power levels according to row T6 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
39 |
Check: Does the UE transmit an ATTACH REQUEST message on Ncell 56 as specified? IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. Note: according to TS 24.301, the UE has the choice to enter "LIMITED-SERVICE" or "PLMN- SEARCH" state. But in any case it shall do a PLMN selection. In the first option, the UE shall apply reselection so it will select cell 56 and then attempt to attach; in the second option it will select the same PLMN again and exclude cells from forbidden TAs so it will select cell 56. |
–> |
ATTACH REQUEST |
7, 8 |
P |
|
39A-39D |
Steps 5 to 8 from procedure 8.1.5.2.3 in TS 36.508. |
– |
– |
– |
– |
|
40 |
The SS transmits an ATTACH REJECT message, EMM cause = "roaming not allowed in this tracking area". (The list of "forbidden tracking areas for roaming" in the UE should now contain TAI-7 and TAI-8) |
<– |
ATTACH REJECT |
– |
– |
|
41 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
42 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 60 seconds on Ncell 55 or Ncell 56? |
–> |
ATTACH REQUEST |
7, 9 |
F |
|
43 |
If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. |
– |
– |
– |
– |
|
44 |
SS adjusts the cell power levels according to row T7 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 55 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
45 |
The UE is brought back to operation or the USIM is inserted. |
– |
– |
– |
– |
|
46 |
The UE transmits an ATTACH REQUEST message? IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
10 |
P |
|
46A-46D |
Steps 5 to 8 from procedure 8.1.5.2.3 in TS 36.508 [18]. |
– |
– |
– |
– |
|
47 |
The SS transmits an ATTACH REJECT message, EMM cause = "roaming not allowed in this tracking area ". (The list of "forbidden tracking areas for roaming" in the UE should now contain TAI-7) |
<– |
ATTACH REJECT |
– |
– |
|
47A |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
48 |
SS adjusts the cell power levels according to row T8 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 50 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
49 |
Check: Does the UE transmit an ATTACH REQUEST message? IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
11 |
P |
|
50-60 |
The attach procedure is completed by executing steps 5 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2. |
– |
– |
– |
– |
|
61 |
If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. |
||||
|
61A |
The UE transmits a DETACH REQUEST message. |
DETACH REQUEST |
|||
|
62 |
SS adjusts the cell power levels according to row T9 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
63 |
The UE is brought back to operation or the USIM is inserted. |
||||
|
– |
The following messages are to be observed on Ncell 55 unless explicitly stated otherwise. |
||||
|
64 |
The UE transmits an ATTACH REQUEST message? IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
– |
– |
|
65 |
The SS transmits an ATTACH REJECT message, EMM cause = " No suitable cells in tracking area ". (The list of "forbidden tracking areas for roaming" in the UE should now contain TAI-7) |
<– |
ATTACH REJECT |
– |
– |
|
65A |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
66 |
SS adjusts the cell power levels according to row T10 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
67 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds on Ncell 55 or Ncell 62? |
–> |
ATTACH REQUEST |
12 |
F |
|
68 |
SS adjusts the cell power levels according to row T11 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
69 |
Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds on Ncell 55 or Ncell 62? |
–> |
ATTACH REQUEST |
13 |
F |
|
70 |
If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. |
– |
– |
– |
– |
|
71 |
SS adjusts the cell power levels according to row T12 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
72 |
The UE is brought back to operation or the USIM is inserted. |
||||
|
73 |
The UE transmits an ATTACH REQUEST message on Ncell 55. IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
– |
– |
|
74 |
Void |
||||
|
74A-74D |
Steps 5 to 8 from procedure 8.1.5.2.3 in TS 36.508 [18]. |
– |
– |
– |
– |
|
75 |
The SS transmits an ATTACH REJECT message, EMM cause = “No suitable cells in tracking area”. (The list of “forbidden tracking areas for roaming” in the UE should now contain TAI- 7) |
<– |
ATTACH REJECT |
– |
– |
|
76 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
76A |
SS adjusts the cell power levels according to row T14 in table 22.5.14.3-1. |
||||
|
77 |
Check: Does the UE transmit an ATTACH REQUEST message on Ncell 56? IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
14, 15 |
P |
|
77A-77D |
Steps 5 to 8 from procedure 8.1.5.2.3 in TS 36.508. |
– |
– |
– |
– |
|
78 |
The SS transmits an ATTACH REJECT message, EMM cause = “No suitable cells in tracking area”. (The list of “forbidden tracking areas for roaming” in the UE should now contain TAI-7 and TAI-8) |
<– |
ATTACH REJECT |
– |
– |
|
79 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
80 |
SS adjusts the cell power levels according to row T 15 in table 22.5.14.3-1. |
– |
– |
– |
– |
|
– |
The following messages are to be observed on Ncell 56 unless explicitly stated otherwise. |
– |
– |
– |
– |
|
81 |
Check: Does the UE transmit the ATTACH REQUEST message in the next 30 seconds? |
–> |
ATTACH REQUEST |
15, 16 |
F |
|
82 |
If possible (see ICS) switch off is performed. Otherwise the power is removed. |
– |
– |
– |
– |
|
83 |
The UE is brought back to operation. |
– |
– |
– |
– |
|
84 |
Check: Does the UE transmit an ATTACH REQUEST? IF AttachWithoutPDN AND UE sets “attachWithoutPDN-Connectivity” in RRCConnectionSetupComplete-NB THEN the ESM DUMMY MESSAGE is piggybacked in ATTACH REQUEST, OTHERWISE the PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST. |
–> |
ATTACH REQUEST |
17 |
P |
|
85-95 |
The attach procedure is completed by executing steps 5 to 14b1 of the UE registration procedure in TS 36.508 sub clause 8.1.5.2. |
– |
– |
– |
– |
|
– |
At the end of this test procedure sequence, the UE is in end state 2-NB Connected Mode according to TS 36.508. |
– |
– |
– |
– |
22.5.14.3.3 Specific message contents
Table 22.5.14.3.3-1: Message ATTACH REJECT (steps 4 and 11, Table 22.5.14.3.2-1)
|
Derivation path: 36.508 table 4.7.2-3 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EMM cause |
00001100 |
#12 "Tracking area not allowed" |
|
|
ESM message container |
Not present |
||
Table 22.5.14.3.3-2: Message ATTACH REQUEST (steps 10, 18, 39, 46, 49, 77 and 84 Table 22.5.14.3.2-1)
|
Derivation path: 36.508 table 4.7.2-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Old GUTI or IMSI |
IMSI-1 |
GUTI has been deleted after receiving ATTACH REJECT at step 4; only IMSI is available. |
|
|
Last visited registered TAI |
Not present |
TAI has been deleted after receiving ATTACH REJECT at step 4. |
|
Table 22.5.14.3.3-3: Message ATTACH REJECT (steps 33, 40 and 47 in table 22.5.14.3.2-1)
|
Derivation path: 36.508 table 4.7.2-3 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EMM cause |
00001101 |
#13 " roaming not allowed in this tracking area " |
|
|
ESM message container |
Not present |
||
Table 22.5.14.3.3-4: Message ATTACH REJECT (step 75 and 78 Table 22.5.14.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.2-3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EMM cause |
0000 1111 |
#15 “No suitable cells in tracking area” |
|
|
ESM message container |
Not present |
||