22.5.8 NB-IoT / TRACKING AREA UPDATE REJECT / Change of cell into a new tracking area / Access barred due to access class control or NAS signalling connection establishment rejected by the network / Success or fail after several attempts due to no network response / TA belongs to TAI list and status is UPDATED / Tracking area updating and detach procedure collision.
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.8.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 reject cause #95"semantically incorrect message" }
then { the UE sets the tracking area updating attempt counter to 5, starts timer T3402, and performs tracking area updating on the expiry of timers T3402}
(2)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #96" invalid mandatory information" }
then { the UE sets the tracking area updating attempt counter to 5, starts timer T3402, and performs tracking area updating on the expiry of timers T3402}
(3)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #97"message type non-existent or not implemented" }
then { the UE sets the tracking area updating attempt counter to 5, starts timer T3402, and performs tracking area updating on the expiry of timers T3402}
(4)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #99"information element non-existent or not implemented" }
then { the UE sets the tracking area updating attempt counter to 5, starts timer T3402, and performs tracking area updating on the expiry of timers T3402}
(5)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a TRACKING AREA UPDATE REJECT message with reject cause #111"protocol error, unspecified" }
then { the UE sets the tracking area updating attempt counter to 5, starts timer T3402, and performs tracking area updating on the expiry of timers T3402}
(6)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { cell change into a new tracking area occurs before the tracking area updating procedure is completed }
then { UE aborts the tracking area updating procedure and re-initiates it in the new tracking area immediately }
}
(7)
with { UE has sent a TRACKING AREA UPDATE REQUEST message and has the tracking area updating attempt counter set to four }
ensure that {
when { UE detects release of the NAS signalling connection }
then { UE starts timer T3402, sets the update status to EU2 NOT UPDATED, changes to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE or optionally to EMM-REGISTERED.PLMN-SEARCH in order to perform a PLMN selection }
}
(8)
with { The UE is in the state EMM-REGISTERED }
ensure that {
when { Access is barred for signalling in the cell UE is camping [Access Class barred in System information] }
then { the UE will not initiate the tracking area updating procedure on the current cell }
}
(9)
with { The UE is in the state EMM-REGISTERED }
ensure that {
when { Access is barred for signalling in the cell UE is camping [T302 running due to RRCConnectionReject message reception] }
then { the UE will not initiate the tracking area updating procedure on the current cell }
}
(10)
with { The UE is in the state EMM-REGISTERED }
ensure that {
when { Access is not barred for signalling in the cell UE is camping }
then { the UE will initiate the tracking area updating procedure on the current cell }
}
(11)
with { The UE is in the state EMM-REGISTERED }
ensure that {
when { Access was barred for signalling in the cell and UE has reselected an new cell where access for "signalling" is granted }
then { the UE will initiate the tracking area updating procedure on the new cell }
}
(12)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to ‘Periodic updating’ and has the tracking area updating attempt counter set to the value less than four, the TAI of the current serving cell is included in the TAI list and the update status is equal to EU1 UPDATED }
ensure that {
when { UE detects release of the NAS signalling connection }
then { UE keeps the update status to EU1 UPDATED, enters state EMM-REGISTERED.NORMAL-SERVICE and starts timer T3411 }
}
(13)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to ‘Periodic updating’, has the tracking area updating attempt counter set to the value less than four, has detected T3430 expiry, the TAI of the current serving cell is included in the TAI list and the update status is equal to EU1 UPDATED }
ensure that {
when { UE detects T3411 expiry }
then { UE initiates the tracking area updating procedure }
}
(14)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to ‘TA updating’ and has the tracking area updating attempt counter set to the value less than four and the TAI of the current serving cell is not included in the TAI list or the update status is different to EU1 UPDATED }
ensure that {
when { UE detects release of the NAS signalling connection }
then { UE starts timer T3411, sets the update status to EU2 NOT UPDATED and changes to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE }
}
(15)
with { UE has sent a TRACKING AREA UPDATE REQUEST message with EPS update type set to ‘TA updating’, has the tracking area updating attempt counter set to the value less than four, has detected T3430 expiry and the TAI of the current serving cell is not included in the TAI list or the update status is different to EU1 UPDATED }
ensure that {
when { UE detects T3411 expiry }
then { UE initiates the tracking area updating procedure }
}
(16)
with { UE has sent a TRACKING AREA UPDATE REQUEST message}
ensure that {
when { UE receives a DETACH REQUEST message before the tracking area updating procedure has been completed }
then { the tracking area updating procedure shall be aborted and the detach procedure shall be progressed }
}
22.5.8.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.5.3.2.6, 5.5.3.1, 5.5.3.3.6, and TS 36.331, clause 5.3.3.12.
[TS 24.301 clause5.5.3.2.6]
The following abnormal cases can be identified:
a) Access barred because of access class barring, ACDC or NAS signalling connection establishment rejected by the network without "Extended wait time" received from lower layers
In WB-S1 mode, if the tracking area updating procedure is started in response to a paging request from the network, access class barring or ACDC is not applicable.
In NB-S1 mode, if the tracking area updating procedure is started in response to a paging request from the network, access barring is not applicable.
In WB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331 [22]), the tracking area updating procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. The tracking area updating procedure is started as soon as possible and if still necessary, e.g. when access for "originating signalling" is granted on the current cell or when the UE moves to a cell where access for "originating signalling" is granted.
In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331 [22]), the tracking area updating procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. Further UE behaviour is implementation specific, e.g. the tracking area updating procedure is started again after an implementation dependent time.
In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331 [22]), a request for an exceptional event is received from the upper layers, then the tracking area updating procedure shall be started.
NOTE 1: In NB-S1 mode, the EMM layer cannot receive the access barring alleviation indication from the lower layers (see 3GPP TS 36.331 [22]).
If access is barred because of access class barring for "originating signalling" (see 3GPP TS 36.331 [22]) and if:
– one of the MO MMTEL voice call is started, MO MMTEL video call is started or MO SMSoIP is started conditions is satisfied;
– the upper layers request to send a mobile originated SMS over NAS or SMS over S102; or
– the upper layers request user plane radio resources, ACDC is applicable to the request and the UE supports ACDC.
then the tracking area updating procedure shall be started according to subclause 5.5.3.2.2. The call type used shall be per annex D of this document.
NOTE 2: If more than one of MO MMTEL voice call is started, MO MMTEL video call is started or MO SMSoIP is started conditions are satisfied, it is left to UE implementation to determine the call type based on Annex D of this document.
If access is barred for a certain ACDC category (see 3GPP TS 36.331 [22]), and if the upper layers request user plane radio resources for a higher ACDC category and the UE supports ACDC, then the tracking area updating procedure shall be started according to subclause 5.5.3.2.2.
If an access request for an uncategorized application is barred due to ACDC (see 3GPP TS 36.331 [22]), and if the upper layers request user plane radio resources for a certain ACDC category and the UE supports ACDC, then the tracking area updating procedure shall be started according to subclause 5.5.3.2.2.
If the trigger for the tracking area update procedure is the response to a paging request from the network and the NAS signalling connection establishment is rejected by the network, the tracking area update procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. The tracking area update procedure may be started if it is still necessary when access for "terminating calls" is granted or because of a cell change.
b) Lower layer failure or release of the NAS signalling connection without "Extended wait time" received from lower layers before the TRACKING AREA UPDATE ACCEPT or TRACKING AREA UPDATE REJECT message is received
The tracking area updating procedure shall be aborted, and the UE shall proceed as described below.
c) T3430 timeout
The UE shall abort the procedure and proceed as described below. The NAS signalling connection, if any, shall be released locally.
NOTE 3: The NAS signalling connection can also be released if the UE deems that the network has failed the authentication check as specified in subclause 5.4.2.7.
d) TRACKING AREA UPDATE REJECT, other causes than those treated in subclause 5.5.3.2.5, and cases of EMM cause values #22 and #25, if considered as abnormal cases according to subclause 5.5.3.2.5
If the tracking area updating request is not for initiating a PDN connection for emergency bearer services, upon reception of the EMM causes #95, #96, #97, #99 and #111 the UE should set the tracking area updating attempt counter to 5.
The UE shall proceed as described below.
e) Change of cell into a new tracking area
If a cell change into a new tracking area occurs before the tracking area updating procedure is completed, the tracking area updating procedure shall be aborted and re-initiated immediately. The UE shall set the EPS update status to EU2 NOT UPDATED.
The UE shall proceed as described below.
f) Tracking area updating and detach procedure collision
EPS detach containing detach type "re-attach required" or "re-attach not required":
If the UE receives a DETACH REQUEST message before the tracking area updating procedure has been completed, the tracking area updating procedure shall be aborted and the detach procedure shall be progressed. If the DETACH REQUEST message contains detach type "re-attach not required" and EMM cause #2 "IMSI unknown in HSS", the UE will follow the procedure as described below for the detach type "IMSI detach".
EPS detach containing detach type "IMSI detach":
If the UE receives a DETACH REQUEST message before the tracking area updating procedure has been completed, the DETACH REQUEST message shall be ignored and tracking area updating procedure shall be progressed.
The UE shall proceed as described below.
For the cases b, c, d, e, f with detach type "re-attach required" or "re-attach not required" with EMM cause other than #2 "IMSI unknown in HSS", and k, the UE shall stop any ongoing transmission of user data.
For the cases b, c, d, k and l, the UE shall proceed as follows:
Timer T3430 shall be stopped if still running.
For the cases b, c, d, and k when the "Extended wait time" is ignored, if the tracking area updating request is not for initiating a PDN connection for emergency bearer services, the tracking area updating attempt counter shall be incremented, unless it was already set to 5.
If the tracking area updating attempt counter is less than 5, and the TAI of the current serving cell is included in the TAI list, and the EPS update status is equal to EU1 UPDATED and the TIN does not indicate "P-TMSI":
the UE shall keep the EPS update status to EU1 UPDATED and enter state EMM-REGISTERED.NORMAL-SERVICE. The UE shall start timer T3411.
If in addition the TRACKING AREA UPDATE REQUEST indicated "periodic updating" or if tracking area updating procedure was initiated to recover NAS signalling connection due to "RRC Connection failure" from the lower layers, the timer T3411 may be stopped when the UE enters EMM-CONNECTED mode.
If timer T3411 expires the tracking area updating procedure is triggered again.
If the tracking area updating attempt counter is less than 5, and the TAI of the current serving cell is not included in the TAI list or the EPS update status is different to EU1 UPDATED or the TIN indicates "P-TMSI":
– for the cases k and l, the tracking area updating procedure is started, if still necessary, when timer T3346 expires or is stopped.
– for the cases b, c, d, and k when the "Extended wait time" is ignored, if the tracking area updating request is not for initiating a PDN connection for emergency bearer services, the UE shall start timer T3411, shall set the EPS update status to EU2 NOT UPDATED and change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. When timer T3411 expires the tracking area updating procedure is triggered again.
If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GPRS update status as specified in 3GPP TS 24.008 [13] for the abnormal case when a normal or periodic routing area updating procedure fails and the routing area updating attempt counter is less than 5 and the GPRS update status is different from GU1 UPDATED.
[TS 24.301 clause5.5.3.3.6]
The UE shall proceed as follows:
3) otherwise, the abnormal cases specified in subclause 5.5.3.2.6 apply with the following modification.
If the tracking area updating attempt counter is incremented according to subclause 5.5.3.2.6 the next actions depend on the value of the tracking area updating attempt counter.
– If the tracking area updating attempt counter is less than 5, the UE shall set the update status to U2 NOT UPDATED, but shall not delete any LAI, TMSI, ciphering key sequence number and list of equivalent PLMNs; or
– if the tracking area updating attempt counter is equal to 5, the UE shall delete any LAI, TMSI and ciphering key sequence number and set the update status to U2 NOT UPDATED.
[TS 24.301, clause 5.5.3.1]
A tracking area updating attempt counter is used to limit the number of subsequently rejected tracking area update attempts. The tracking area updating attempt counter shall be incremented as specified in subclause 5.5.3.2.6. Depending on the value of the tracking area updating attempt counter, specific actions shall be performed. The tracking area updating attempt counter shall be reset when:
– an attach or combined attach procedure is successfully completed;
– a normal or periodic tracking area updating or a combined tracking area updating procedure is successfully completed;
– a normal or periodic tracking area updating or a combined tracking area updating procedure is rejected with EMM cause #11, #12, #13, #14, #15, #25 or #35:
– a combined attach procedure or a combined tracking area updating procedure is completed for EPS services only with cause #2 or #18;or
– a new PLMN is selected.
Additionally the tracking area updating attempt counter shall be reset when the UE is in substate EMM-REGISTERED.ATTEMPTING-TO-UPDATE or EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, and:
– a new tracking area is entered;
– timer T3402 expires; or
– timer T3346 is started.
[TS 36.331, clause 5.3.3.12]
The UE shall:
1> if SystemInformationBlockType14 is present and includes the eab-Param:
2> if the eab-Common is included in the eab-Param:
3> if the UE belongs to the category of UEs as indicated in the eab-Category contained in eab-Common; and
3> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the corresponding bit in the eab-BarringBitmap contained in eab-Common is set to one:
4> consider access to the cell as barred;
3> else:
4> consider access to the cell as not barred due to EAB;
2> else (the eab-PerPLMN-List is included in the eab-Param):
3> select the entry in the eab-PerPLMN-List corresponding to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]);
3> if the eab-Config for that PLMN is included:
4> if the UE belongs to the category of UEs as indicated in the eab-Category contained in eab-Config; and
4> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the corresponding bit in the eab-BarringBitmap contained in eab-Config is set to one:
5> consider access to the cell as barred;
4> else:
5> consider access to the cell as not barred due to EAB;
3> else:
4> consider access to the cell as not barred due to EAB;
1> else:
2> consider access to the cell as not barred due to EAB;
22.5.8.3 Test description
22.5.8.3.1 Pre-test conditions
System Simulator:
– 4 cells: Ncell 50, Ncell 51, Ncell 52, Ncell 53.
– NB-IoT system information combination 4 as defined in TS 36.508 [18] clause 8.1.4.3.1.1 is used in all cells.
UE:
None.
Preamble:
– the UE is in state Registered, NB-IoT Idle Mode (state 3-NB) on Ncell 50 according to TS 36.508 except for those shown in table 22.5.8.3.3-6;
22.5.8.3.2 Test procedure sequence
22.5.8.3.2 Test procedure sequence
Table 22.5.8.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|||||||
U – S |
Message |
||||||||||
1 |
The SS configures: Set the cell type of Ncell 50 to the "’Serving cell ". |
– |
– |
– |
– |
||||||
2 |
The SS waits for T3412 to elapse. |
– |
– |
– |
– |
||||||
3 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 50. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
4 |
The SS transmits a TRACKING AREA UPDATE REJECT message with EMM cause #95"semantically incorrect message" as specified. (Note 1) |
<– |
TRACKING AREA UPDATE REJECT |
– |
– |
||||||
5 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
6 |
Check: When the timer T3402 expires does the UE re-transmit TRACKING AREA UPDATE REQUEST message on Ncell 50? |
–> |
TRACKING AREA UPDATE REQUEST |
1 |
P |
||||||
7 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
8 |
The UE transmits a TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
9 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
10 |
The SS waits for T3412 to elapse. |
– |
– |
– |
– |
||||||
11 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 50. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
12 |
The SS transmits a TRACKING AREA UPDATE REJECT message with EMM cause #96" invalid mandatory information" as specified. (Note 1) |
<– |
TRACKING AREA UPDATE REJECT |
– |
– |
||||||
13 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
14 |
Check: When the timer T3402 expires does the UE re-transmit TRACKING AREA UPDATE REQUEST message on Ncell 50? |
–> |
TRACKING AREA UPDATE REQUEST |
2 |
P |
||||||
15 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
16 |
The UE transmits a TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
17 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
18 |
The SS waits for T3412 to elapse |
– |
– |
– |
– |
||||||
19 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 50. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
20 |
The SS transmits a TRACKING AREA UPDATE REJECT message with EMM cause #97"message type non-existent or not implemented". (Note 1) |
<– |
TRACKING AREA UPDATE REJECT |
– |
– |
||||||
21 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
22 |
Check: When the timer T3402 expires does the UE re-transmit TRACKING AREA UPDATE REQUEST message on Ncell 50? |
–> |
TRACKING AREA UPDATE REQUEST |
3 |
P |
||||||
23 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
24 |
The UE transmits a TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
25 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
26 |
The SS waits for T3412 to elapse. |
– |
– |
– |
– |
||||||
27 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 50. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
28 |
The SS transmits a TRACKING AREA UPDATE REJECT message with EMM cause #99"information element non-existent or not implemented" as specified. (Note) |
<– |
TRACKING AREA UPDATE REJECT |
– |
– |
||||||
29 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
30 |
Check: When the timer T3402 expires does the UE re-transmit TRACKING AREA UPDATE REQUEST message on Ncell 50? |
–> |
TRACKING AREA UPDATE REQUEST |
4 |
P |
||||||
31 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
32 |
The UE transmits a TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
33 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
34 |
The SS waits for T3412 to elapse. |
– |
– |
– |
– |
||||||
35 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 50. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
36 |
The SS transmits a TRACKING AREA UPDATE REJECT message with EMM cause #111"protocol error, unspecified" as specified. (Note 1) |
<– |
TRACKING AREA UPDATE REJECT |
– |
– |
||||||
37 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
38 |
Check: When the timer T3402 expires does the UE re-transmit TRACKING AREA UPDATE REQUEST message on Ncell 50? |
–> |
TRACKING AREA UPDATE REQUEST |
5 |
P |
||||||
39 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
40 |
the UE transmit a TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
41 |
The SS releases the RRC connection. |
||||||||||
42 |
The SS configures: Set the cell type of Ncell 50 to the "Non-Suitable cell". Set the cell type of Ncell 51 to the "Serving cell". |
– |
– |
– |
– |
||||||
43 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 51 (Note 2). |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
44 |
The SS configures: Set the cell type of Ncell 51 to the "Non-Suitable off cell". Set the cell type of Ncell 53to the "Serving cell". |
– |
– |
– |
– |
||||||
45 |
Void. |
– |
– |
– |
– |
||||||
46 |
Void. |
– |
– |
– |
– |
||||||
47 |
Check: Does the UE transmit TRACKING AREA UPDATE REQUEST message on Ncell 53? |
–> |
TRACKING AREA UPDATE REQUEST |
6 |
P |
||||||
48 |
SS responds with TRACKING AREA UPDATE ACCEPT message |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
49 |
UE sends TRACKING AREA UPDATE COMPLETE |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
49A |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
50 |
Switch-off the UE. |
– |
– |
– |
– |
||||||
50A |
The UE transmits a DETACH REQUEST message. |
–> |
DETACH REQUEST |
– |
– |
||||||
50B |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
50C |
The SS configures: Set the cell type of Ncell 50 to the "Serving cell". Set the cell type of Ncell 51 to the "non-Suitable cell". Set the cell type of Ncell 52 to the "non-Suitable cell". Set the cell type of Ncell 53 to the "non-Suitable off cell". |
– |
– |
– |
– |
||||||
– |
The following messages are to be observed on Ncell 50 unless explicitly stated otherwise. |
– |
– |
– |
– |
||||||
51 |
The UE is powered on or switched on. |
– |
– |
– |
– |
||||||
52 |
Steps 2-10a2 of the generic procedure for UE registration specified in TS 36.508 subclause 8.1.5.2 are performed. |
– |
– |
– |
– |
||||||
53 |
SS responds with ATTACH ACCEPT message. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ESM DUMMY MESSAGE message is piggybacked in ATTACH ACCEPT message |
<– |
ATTACH ACCEPT |
– |
– |
||||||
54 |
Steps 14b1 of the generic procedure for UE registration specified in TS 36.508 subclause 8.1.5.2 are performed. |
– |
– |
– |
– |
||||||
55 |
The SS releases the RRC connection. |
||||||||||
56 |
Wait for 6 min to ensure that T3412 expires. |
– |
– |
– |
– |
||||||
57 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘Periodic updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
58 |
Wait for T3430 and T3411 (265s) expiry. NOTE: The tracking area updating attempt counter is 1. |
– |
– |
– |
– |
||||||
59 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘Periodic updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
60 |
Wait for T3430 and T3411 (265s) expiry. NOTE: The tracking area updating attempt counter is 2. |
– |
– |
– |
– |
||||||
61 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘Periodic updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
62 |
Wait for T3430 and T3411 (265s) expiry. NOTE: The tracking area updating attempt counter is 3. |
– |
– |
– |
– |
||||||
63 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘Periodic updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
64 |
Wait for T3430 and T3411 (265s) expiry. NOTE: The tracking area updating attempt counter is 4. |
– |
– |
– |
– |
||||||
65 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘Periodic updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
66 |
The SS releases the RRC connection. NOTE: The tracking area updating attempt counter is 5. |
– |
– |
– |
– |
||||||
67 |
Wait for 12 min to ensure that T3402 expires. |
– |
– |
– |
– |
||||||
68 |
Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’? NOTE: The tracking area updating attempt counter is reset. |
–> |
TRACKING AREA UPDATE REQUEST |
7 |
P |
||||||
69 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
70 |
The SS configures: Set the cell type of Ncell 50 to the "non-Suitable cell". Set the cell type of Ncell 51 to the "Serving cell". |
– |
– |
– |
– |
||||||
– |
The following messages are to be observed on Ncell 51 unless explicitly stated otherwise. |
– |
– |
– |
– |
||||||
71 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’. NOTE: The tracking area updating attempt counter is reset. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
72 |
Wait for T3430 and T3411 (265s) expiry. NOTE: The tracking area updating attempt counter is 1. |
– |
– |
– |
– |
||||||
73 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
74 |
Wait for T3430 and T3411 (265s) expiry. NOTE: The tracking area updating attempt counter is 2. |
– |
– |
– |
– |
||||||
75 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
76 |
Wait for T3430 and T3411 (265s) expiry. NOTE: The tracking area updating attempt counter is 3. |
– |
– |
– |
– |
||||||
77 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
78 |
Wait for T3430 and T3411 (265s) expiry. NOTE: The tracking area updating attempt counter is 4. |
– |
– |
– |
– |
||||||
79 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
80 |
The SS releases the RRC connection. NOTE: The tracking area updating attempt counter is 5 and reset. |
– |
– |
– |
– |
||||||
81 |
The SS configures: Set the cell type of Ncell 51 to the "non-Suitable cell". Set the cell type of Ncell 52 to the "Serving cell". |
– |
– |
– |
– |
||||||
– |
The following messages are to be observed on Ncell 52 unless explicitly stated otherwise. |
– |
– |
– |
– |
||||||
82 |
Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’? |
–> |
TRACKING AREA UPDATE REQUEST |
7 |
P |
||||||
83 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
84 |
The UE transmits a TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
85 |
The SS releases the RRC connection. |
||||||||||
86 |
The SS configures: The SS sets the cell type of Ncell 50 to the "Serving cell", Sets the cell type of Ncell 51 to the " Non-Suitable cell", Set the cell type of Ncell 52 to the "non-Suitable Off cell". And sets SystemInformationBlockType14-NB parameters as described in table 22.5.8.3.3-18 |
– |
– |
– |
– |
||||||
– |
The following messages are to be observed on Ncell 50 unless explicitly stated otherwise. |
– |
– |
– |
– |
||||||
87 |
Check: for 60 seconds if UE initiates the tracking area updating procedure on Ncell 50? |
– |
– |
8 |
F |
||||||
88 |
Void |
– |
– |
– |
– |
||||||
89 |
The SS changes SystemInformationBlockType14-NB parameters to parameters as described in table 22.5.8.3.3-19. |
– |
– |
– |
– |
||||||
90 |
The UE transmits RRC Connection Request |
– |
– |
– |
– |
||||||
91 |
SS responds with RRCConnectionReject message with IE extendedWaitTime set to 10 seconds (Max Value). |
– |
– |
– |
– |
||||||
92 |
Check: for 10 seconds if UE initiates the tracking area updating procedure and hence transmits RRC Connection Request? |
– |
– |
9 |
F |
||||||
93 |
Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST? |
–> |
TRACKING AREA UPDATE REQUEST |
10 |
P |
||||||
94 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
95 |
The UE sends TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
96 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
97 |
The SS set SystemInformationBlockType1-NB and SystemInformationBlockType14-NB parameters as described in table 22.5.8.3.3-20 and table 22.5.8.3.3-21. |
– |
– |
– |
– |
||||||
98 |
The SS configures: Sets the cell type of Ncell 51 to the "serving cell", Sets the cell type of Ncell 50 to “non-suitable off Cell”. |
||||||||||
99 |
Check: For 60 seconds if the UE initiates the tracking area update procedure on Ncell 51? |
– |
– |
8 |
F |
||||||
100 |
The SS configures: Sets the cell type of Ncell 51 to “Suitable neighbour intra-frequency cell”. Sets the cell type of Ncell 53 to “serving cell”. |
– |
– |
– |
– |
||||||
– |
The following messages are to be observed on Ncell 53 unless explicitly stated otherwise. |
– |
– |
– |
– |
||||||
101 |
Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST? |
–> |
TRACKING AREA UPDATE REQUEST |
11 |
P |
||||||
102 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
103 |
The UE sends TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
103AA |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
103A |
Cause switch off. |
||||||||||
103B |
The UE transmit a DETACH REQUEST message. |
–> |
DETACH REQUEST |
– |
– |
||||||
103C |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
104 |
The SS configures: Set the cell type of Ncell 50 to the "Serving cell". Set the cell type of Ncell 51 to the "non-Suitable cell". Set the cell type of Ncell 52 to the "non-Suitable off cell". Sets the cell type of Ncell 53 to “non-Suitable off cell”. |
– |
– |
– |
– |
||||||
104A |
The SS changes SystemInformationBlockType14-NB parameters to parameters as described in table 22.5.8.3.3-31. |
– |
– |
– |
– |
||||||
– |
The following messages are to be observed on Ncell 50 unless explicitly stated otherwise. |
– |
– |
– |
– |
||||||
105 |
The UE is powered on or switched on. |
– |
– |
– |
– |
||||||
106 |
Steps 2-10a2 of the generic procedure for UE registration specified in TS 36.508 subclause 8.1.5.2 are performed |
– |
– |
– |
– |
||||||
107 |
The SS activates UE radio bearer test mode. |
– |
– |
– |
– |
||||||
108 |
The SS responds with an ATTACH ACCEPT message with the T3412 value indicating 6 min. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST or ESM DUMMY MESSAGE message is piggybacked in ATTACH ACCEPT message. |
<– |
ATTACH ACCEPT |
– |
– |
||||||
109 |
The UE transmits an ATTACH COMPLETE message including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT or ESM DUMMY MESSAGE message. NOTE: The tracking area updating attempt counter is reset. |
–> |
ATTACH COMPLETE |
– |
– |
||||||
110 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
110A |
The SS configures: Set the cell type of Ncell 51 to the "Suitable neighbour intra-frequency cell". |
– |
– |
– |
– |
||||||
111 |
Wait for 6 min to ensure that T3412 expires. |
– |
– |
– |
– |
||||||
112 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘Periodic updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
113 |
The SS releases the RRC connection. NOTE: The tracking area updating attempt counter is 1. |
– |
– |
– |
– |
||||||
114 |
Void |
– |
– |
– |
– |
||||||
115 |
Void |
– |
– |
– |
– |
||||||
116 |
Steps 1 – 4a1b3a2 of the generic procedure to check the UE response to paging specified in TS 36.508 [18] clause 8.1.5A.2 are performed |
12 |
– |
||||||||
117 |
The SS transmits a SERVICE REJECT message with EMM cause set to "Congestion". |
<– |
SERVICE REJECT |
– |
– |
||||||
118 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
119 |
Wait for 10s after step 113 to ensure that T3411 expires. |
– |
– |
– |
– |
||||||
– |
EXCEPTION: Steps 120a1 to 120a4 describes behaviour depending on UE behaviour; the “lower case letter” identifies a step sequence that take place if the UE does not transmit any TRACKING AREA UPDATE REQUEST message |
– |
– |
– |
– |
||||||
120a1 |
IF the UE does not transmit any TRACKING AREA UPDATE REQUEST message THEN wait for 6 min to ensure that T3412 expires. |
– |
– |
– |
– |
||||||
120a2 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘Periodic updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
120a3 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
120a4 |
Wait for 10s after step 120a3 to ensure that T3411 expires. |
– |
– |
– |
– |
||||||
121 |
Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘Periodic updating’? |
–> |
TRACKING AREA UPDATE REQUEST |
13 |
P |
||||||
122 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. NOTE: The tracking area updating attempt counter is reset. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
123 |
The SS transmits an ACTIVATE TEST MODE message to activate test mode G (loopback of the User data container content of any received downlink ESM DATA TRANSPORT). |
<– |
RRC: DLInformationTransfer-NB TC: ACTIVATE TEST MODE |
– |
– |
||||||
124 |
The UE transmits an ACTIVATE TEST MODE COMPLETE message. |
–> |
RRC: ULInformationTransfer-NB TC: ACTIVATE TEST MODE COMPLETE |
– |
– |
||||||
125 |
Generic test procedure in TS 36.508 [18] clause 8.1.5.4 is performed. NOTE: The UE enters the UE test loop mode. |
– |
– |
– |
– |
||||||
126 |
The SS transmits one IP Packet to the UE. |
<– |
IP packet |
– |
– |
||||||
127 |
Wait for 1s after the IP packet has been transmitted in step 126 (Note 3). |
– |
– |
– |
– |
||||||
127A |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
EXCEPTION: Steps 128a to 128b describes behaviour depending on UE behaviour; the “lower case letter” identifies a step sequence that take place if the UE does not transmit PDN CONNECTIVITY REQUEST message during attach procedure at step106 |
– |
– |
– |
– |
|||||||
128a |
Steps 2 – 5 of the generic procedure to check the UE response to paging specified in TS 36.508 [18] clause 8.1.5A.2 are performed |
– |
– |
– |
– |
||||||
128b |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
130 |
The SS configures: Set the cell type of Ncell 50 to the "non-Suitable cell". Set the cell type of Ncell 51 to the "Serving cell". |
– |
– |
– |
– |
||||||
– |
The following messages are to be observed on Ncell 51 unless explicitly stated otherwise. |
– |
– |
– |
– |
||||||
131 |
The UE transmits a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
132 |
Wait for 255s after step 131 to ensure that T3430 expires. |
– |
– |
– |
– |
||||||
133 |
The SS releases the RRC connection. NOTE: The tracking area updating attempt counter is 1. |
– |
– |
– |
– |
||||||
134 |
Check: Does the UE transmit a CONTROL PLANE SERVICE REQUEST message within 5s? |
–> |
CONTROL PLANE SERVICE REQUEST |
14 |
F |
||||||
135 |
Wait for 10s after step 133 to ensure that T3411 expires. |
– |
– |
– |
– |
||||||
136 |
Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message with the EPS update type value set to ‘TA updating’? |
–> |
TRACKING AREA UPDATE REQUEST |
15 |
P |
||||||
137 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
||||||
– |
EXCEPTION: Step 138 and Step 139a1 can occur in any order. |
– |
– |
– |
– |
||||||
138 |
The UE transmits a TRACKING AREA UPDATE COMPLETE message. NOTE: The tracking area updating attempt counter is reset. |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
||||||
– |
EXCEPTION: Step 139a1 describes behaviour that depends on UE implementation; the "lower case letter" identifies a step sequence that takes place if the UE has user data pending. |
– |
– |
– |
– |
||||||
139 a1 |
IF the UE has user data pending THEN the UE loop backs the IP packet received in step 126 via control plane associated with the default EPS bearer context on Ncell 51 within 5s. |
– |
– |
– |
– |
||||||
140 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
141 |
Set the cell type of Ncell 50 to the "Serving cell cell". Set the cell type of Ncell 51 to the "Non-Suitable cell’. |
– |
– |
– |
– |
||||||
142 |
The UE transmits a TRACKING AREA UPDATE REQUEST on Ncell 50 (Note 2). |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
||||||
143 |
SS does not send TRACKING AREA UPDATE ACCEPT to the UE. |
– |
– |
– |
– |
||||||
144 |
The SS transmits a DETACH REQUEST message with Detach type = ‘re-attach not required’ on Ncell 50. |
<– |
DETACH REQUEST |
– |
– |
||||||
144A |
UE responds with DETACH ACCEPT message |
–> |
DETACH ACCEPT |
16 |
P |
||||||
145 |
The SS releases the RRC connection. |
– |
– |
– |
– |
||||||
146 |
SS sends a Paging message to the UE |
<- |
RRC: Paging-NB |
– |
– |
||||||
147 |
Check: Does the UE transmit an RRCConnectionRequest-NB message in the next 30 seconds? |
–> |
RRC: RRCConnectionRequest-NB |
16 |
F |
||||||
NOTE 1: Upon reception of TRACKING AREA UPDATE REJECT message with EMM causes #95, #96, #97, #99 and #111, timer T3402 shall be started. NOTE 2: Any type of tracking area update is acceptable. NOTE 3: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by the SS in step 126 to the UE test loop function before the RRCConnectionRelease message is sent by the SS in step 129. NOTE 4: Void. |
22.5.8.3.3 Specific message contents
Table 22.5.8.3.3-1: Message TRACKING AREA UPDATE REJECT (step 4, Table 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-26 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EMM cause |
01011111 |
#95 "semantically incorrect message " |
Table 22.5.8.3.3-2: Message TRACKING AREA UPDATE REJECT (step 12, Table 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-26 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EMM cause |
01100000 |
#96 " invalid mandatory information " |
Table 22.5.8.3.3-3: Message TRACKING AREA UPDATE REJECT (step 20, Table 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-26 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EMM cause |
01100001 |
#97 " message type non-existent or not implemented " |
Table 22.5.8.3.3-4: Message TRACKING AREA UPDATE REJECT (step 28, Table 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-26 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EMM cause |
01100011 |
#99 " information element non-existent or not implemented " |
Table 22.5.8.3.3-5: Message TRACKING AREA UPDATE REJECT (step 36, Table 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-26 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
EMM cause |
01101111 |
#111 " protocol error, unspecified " |
Table 22.5.8.3.3-6: Message ATTACH ACCEPT (For the UE registration procedure in TS 36.508 clause 8.1.5.2)
Derivation path: 36.508 table 4.7.2-1 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
T3412 value |
1 minute |
||
Timer value |
‘00001’B |
||
Unit |
‘001’B |
||
T3402 value |
30 seconds |
||
Timer value |
‘01111’B |
||
Unit |
‘000’B |
Table 22.5.8.3.3-7: Message TRACKING AREA UPDATE ACCEPT (steps 7,15,23,31,39, Table 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-1 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
T3412 value |
1 minute |
||
Timer value |
‘00001’B |
||
Unit |
‘001’B |
||
T3402 value |
30 seconds |
||
Timer value |
‘01111’B |
||
Unit |
‘000’B |
Table 22.5.8.3.3-8: Message TRACKING AREA UPDATE REQUEST (steps 3,11,19,27,35 Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-27 |
|||
Information Element |
Value/remark |
Comment |
Condition |
EPS update type |
|||
EPS update type Value |
‘011’B |
Periodic updating |
Table 22.5.8.3.3-9: Message TRACKING AREA UPDATE REQUEST (step 43, step 47, Table 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-27 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Old GUTI |
GUTI-1 |
||
Last visited registered TAI |
TAI-1 |
Table 22.5.8.3.3-10: Message TRACKING AREA UPDATE ACCEPT (step 48, 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-24 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
GUTI |
GUTI-2 |
||
TAI list |
|||
Length of tracking area identity list contents |
‘00000110’B |
||
Partial tracking area identity list |
|||
Number of elements |
‘00000’B |
||
Type of list |
’00’B |
"list of TACs belonging to one PLMN, with non-consecutive TAC values" |
|
MCC MNC TAC 1 |
TAC =4 |
"PLMN is set to the same MCC/MNC stored in EFIMSI" "TAI-4" |
Table 22.5.8.3.3-11: Void
Table 22.5.8.3.3-12: Void
Table 22.5.8.3.3-13: Message ATTACH ACCEPT (step 53, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
T3412 value |
6 minutes |
||
Timer value |
‘0 0001’B |
||
Unit |
‘010’B |
value is incremented in multiples of decihours |
|
GUTI |
GUTI-1 |
Table 22.5.8.3.3-14: Message TRACKING AREA UPDATE REQUEST (step 57, step 59, step 61, step 63 and step 65, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-27 |
|||
Information Element |
Value/remark |
Comment |
Condition |
EPS update type |
|||
EPS update type Value |
‘011’B |
Periodic updating |
|
Old GUTI |
GUTI-1 |
||
Last visited registered TAI |
TAI-1 |
Table 22.5.8.3.3-15: Message TRACKING AREA UPDATE REQUEST (step 68, step 71, step 73, step 75, step 77, step 79 and step 82, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-27 |
|||
Information Element |
Value/remark |
Comment |
Condition |
EPS update type |
|||
EPS update type value |
‘000’B |
TA updating |
|
Old GUTI |
GUTI-1 |
||
Last visited registered TAI |
TAI-1 |
Table 22.5.8.3.3-16: Message TRACKING AREA UPDATE ACCEPT (step 69, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-24 |
|||
Information Element |
Value/remark |
Comment |
Condition |
GUTI |
Not present |
Table 22.5.8.3.3-17: Message TRACKING AREA UPDATE ACCEPT (step 83, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-24 |
|||
Information Element |
Value/remark |
Comment |
Condition |
GUTI |
GUTI-3 |
Table 22.5.8.3.3-18: SystemInformationBlockType14-NB for Ncell 50 (step 86, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.4.3.3-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType14-NB-r13 ::= SEQUENCE { |
|||
ab-Param-r13 CHOICE { |
|||
ab-Common-r13 ::= SEQUENCE { |
|||
ab-Category-r13 |
a |
||
ab-BarringBitmap-r13 |
‘1111111111’B |
||
ab-BarringExceptionData-r13 |
Not present |
||
ab-BarringForSpecialAC-r13 |
‘11111’B |
||
} |
|||
} |
|||
lateNonCriticalExtension |
Not present |
||
} |
Table 22.5.8.3.3-19: SystemInformationBlockType14-NB for Ncell 50 (step 89, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.4.3.3-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType14-NB-r13 ::= SEQUENCE { |
|||
ab-Param-r13 CHOICE { |
|||
ab-Common-r13 ::= SEQUENCE { |
|||
ab-Category-r13 |
a |
||
ab-BarringBitmap-r13 |
‘000000000’B |
||
ab-BarringExceptionData-r13 |
Not present |
||
ab-BarringForSpecialAC-r13 |
‘00000’B |
||
} |
|||
} |
|||
lateNonCriticalExtension |
Not present |
||
} |
Table 22.5.8.3.3-20: SystemInformationBlockType14-NB for Ncell 51 (step 97, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.4.3.3-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType14-NB-r13 ::= SEQUENCE { |
|||
ab-Param-r13 CHOICE { |
|||
ab-Common-r13 ::= SEQUENCE { |
|||
ab-Category-r13 |
a |
||
ab-BarringBitmap-r13 |
‘1111111111’B |
||
ab-BarringExceptionData-r13 |
Not present |
||
ab-BarringForSpecialAC-r13 |
‘11111’B |
||
} |
|||
} |
|||
lateNonCriticalExtension |
Not present |
||
} |
Table 22.5.8.3.3-21: SystemInformationBlockType1-NB for Ncell 51 (step 97, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.4.3.2-3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
cellAccessRelatedInfo SEQUENCE { |
|||
intraFreqReselection-r13 |
allowed |
||
} |
|||
} |
Table 22.5.8.3.3-22: ACTIVATE TEST MODE (step 107, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 8.1.5.2A.4-1, condition TL_MODE_G or TL_MODE_H |
Table 22.5.8.3.3-23: Message ATTACH ACCEPT (step 108, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
T3412 value |
6 minutes |
||
Timer value |
‘0 0001’B |
||
Unit |
‘010’B |
value is incremented in multiples of decihours |
|
GUTI |
GUTI-1 |
Table 22.5.8.3.3-24: Message TRACKING AREA UPDATE REQUEST (step 112, step 120a2 and step 121, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-27 |
|||
Information Element |
Value/remark |
Comment |
Condition |
EPS update type |
|||
EPS update type Value |
‘011’B |
Periodic updating |
|
Old GUTI |
GUTI-1 |
||
Last visited registered TAI |
TAI-1 |
Table 22.5.8.3.3-25: Message TRACKING AREA UPDATE ACCEPT (step 122, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-24 |
|||||||
Information Element |
Value/remark |
Comment |
Condition |
||||
GUTI |
Not present |
||||||
MS identity |
Not present |
Table 22.5.8.3.3-26: CLOSE UE TEST LOOP (step 125, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 8.1.5.2A.4-1, condition TL_MODE_G or TL_MODE_H |
|||
Information Element |
Value/remark |
Comment |
Condition |
UE test loop mode |
|||
UL data delay |
‘0001 0100’B |
20seconds |
Table 22.5.8.3.3-27: Message TRACKING AREA UPDATE REQUEST (step 131, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-27 |
|||
Information Element |
Value/remark |
Comment |
Condition |
Old GUTI |
GUTI-1 |
||
Last visited registered TAI |
TAI-1 |
Table 22.5.8.3.3-28: Message TRACKING AREA UPDATE REQUEST (step 136, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-27 |
|||
Information Element |
Value/remark |
Comment |
Condition |
EPS update type |
|||
"Active" flag |
Any allowed value |
The UE may set this flag due to failing SERVICE REQUEST procedure. |
|
Old GUTI |
GUTI-1 |
||
Last visited registered TAI |
TAI-1 |
Table 22.5.8.3.3-29: Message TRACKING AREA UPDATE ACCEPT (step 137, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.7.2-24 |
|||
Information Element |
Value/remark |
Comment |
Condition |
GUTI |
GUTI-2 |
Table 22.5.8.3.3-30: Message DETACH REQUEST (step 144, Table 22.5.8.3.2-1)
Derivation path: 36.508 table 4.7.2-12 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Detach type |
‘010’B |
“re-attach not required” |
|
EMM cause |
‘00001100’B |
"Tracking area not allowed" |
Table 22.5.8.3.3-31: SystemInformationBlockType14-NB for Ncell 51 (step 104A, Table 22.5.8.3.2-1)
Derivation Path: 36.508, Table 4.4.3.3-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType14-NB-r13 ::= SEQUENCE { |
|||
ab-Param-r13 CHOICE { |
|||
ab-Common-r13 ::= SEQUENCE { |
|||
ab-Category-r13 |
a |
||
ab-BarringBitmap-r13 |
‘000000000’B |
||
ab-BarringExceptionData-r13 |
Not present |
||
ab-BarringForSpecialAC-r13 |
‘00000’B |
||
} |
|||
} |
|||
lateNonCriticalExtension |
Not present |
||
} |
Table 22.5.8.3.3-32: Message ACTIVATE TEST MODE (step 123, Table 22.5.8.3.2-1)
Derivation path: TS 36.508 [18], table 4.7A-1, Condition UE TEST LOOP MODE G |
Table 22.5.8.3.3-33: MasterInformationBlock-NB for Ncell 50 (Step 86, Table 22.5.8.3.2-1)
Derivation Path: 36.508 Table 8.1.4.3.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-NB ::= SEQUENCE { |
|||
ab-Enabled-r13 |
TRUE |
||
} |
Table 22.5.8.3.3-33A: MasterInformationBlock-TDD-NB for Ncell 50 (Step 86, Table 22.5.8.3.2-1)
Derivation Path: 36.508 Table 8.1.4.3.2-1A |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-TDD-NB-r15 ::= SEQUENCE { |
|||
ab-Enabled-r15 |
TRUE |
||
} |
Table 22.5.8.3.3-34: MasterInformationBlock-NB for Ncell 51 (Step 97, Table 22.5.8.3.2-1)
Derivation Path: 36.508 Table 8.1.4.3.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-NB ::= SEQUENCE { |
|||
ab-Enabled-r13 |
TRUE |
||
} |
Table 22.5.8.3.3-35: MasterInformationBlock-TDD-NB for Ncell 51 (Step 97, Table 22.5.8.3.2-1)
Derivation Path: 36.508 Table 8.1.4.3.2-1A |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-TDD-NB-r15 ::= SEQUENCE { |
|||
ab-Enabled-r15 |
TRUE |
||
} |