22.5.18 NB-IoT / Attach & Normal tracking area update Procedure / Success / without Idle eDRX parameters / With Idle eDRX parameters/ With and without Idle eDRX and PSM parameters
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.18.1 Test Purpose (TP)
(1)
with { the UE sent Attach Request message with “extended DRX parameters IE”}
ensure that {
when { the UE receives the extended DRX parameters in the ATTACH ACCEPT message }
then { the UE shall use the extended DRX parameters and send Attach complete message}
}
(2)
with { the UE applied extended DRX parameters received in Attach Accept }
ensure that {
when { the UE receives the paging-nb message in the paging occasion in paging hyperframe}
then { the UE shall send the control plane service request message}
}
(3)
with { the UE sent TAU Request message with “extended DRX parameters IE” }
ensure that {
when { the UE does not receives the extended DRX parameters in the TAU ACCEPT message }
then { the UE shall not use the extended DRX parameters and use the idle DRX parameters, and, send TAU complete message}
}
(4)
with { the UE not received extended DRX parameters in TAU Accept }
ensure that {
when { the UE receives the paging-nb message in the eDRX sleep }
then { the UE shall send the control plane service request message}
}
(5)
with { the UE sent Attach Request message with “extended DRX parameters IE” }
ensure that {
when { UE does not receive the extended DRX parameters in the ATTACH ACCEPT message }
then { the UE shall not use the extended DRX parameters and use the idle DRX parameters and send Attach complete message}
}
(6)
with { the UE not received extended DRX parameters in Attach Accept }
ensure that {
when { the UE receives the paging-nb message in the eDRX sleep }
then { the UE shall send the control plane service request message}
}
(7)
with { the UE sent TAU Request message with “extended DRX parameters IE” }
ensure that {
when { the UE receives the extended DRX parameters in the TAU ACCEPT message }
then { the UE use the extended DRX parameters and send TAU complete message}
}
(8)
with { the UE applied extended DRX parameters received in TAU Accept }
ensure that {
when { the UE receives paging-nb message in the paging occasion in paging hyperframe }
then { the UE shall send the control plane service request message}
}
(9)
with { the UE has sent an Attach Request message with the “extended DRX parameters IE” and the “T3324 IE” }
ensure that {
when { the UE receives the ATTACH ACCEPT message including the extended DRX and T3324 IE parameters }
then { the UE shall send Attach complete message to network }
}
(10)
with { the UE applied extended DRX parameters received in Attach Accept }
ensure that {
when { the UE receives a paging-nb message in a valid paging occasion in paging hyperframe as per idle eDRX }
then { the UE shall send the control plane service request message to network }
}
(11)
with { the UE has sent a TAU Request message with “extended DRX parameters IE” and the “T3324 IE” }
ensure that {
when { the UE receives the TAU ACCEPT message not including the extended DRX parameters but including the T3324 IE }
then { the UE shall send TAU complete message }
}
(12)
with { the UE has received TAU ACCEPT message not including extended DRX parameters IE but including T3324 IE }
ensure that {
when { the UE receives a paging-nb message after T3324 timer expiry in a valid paging occasion as per normal DRX }
then { the UE shall not send the control plane service request message to network }
}
(13)
with { the UE has sent an Attach Request message with “extended DRX parameters IE” and the “T3324 IE” }
ensure that {
when { the UE receives the ATTACH ACCEPT message including the extended DRX parameters but not the T3324 IE }
then { the UE shall send Attach complete message to network }
}
(14)
with { the UE has received an ATTACH ACCEPT message including extended DRX parameters IE but not the T3324 IE }
ensure that {
when { the UE receives a paging-nb message in a valid paging occasion in paging hyperframe as per Idle eDRX}
then { the UE shall send the control plane service request message to network }
}
22.5.18.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.3.11, 5.3.12, 5.3.13, 5.5.1.2.2, 5.5.1.2.4, 5.5.3.2.2, 5.5.3.2.4 and 5.6.2.2.1.1
[TS 24.301 clause 5.3.11]
The UE can request the use of power saving mode (PSM) during an attach or tracking area updating procedure (see 3GPP TS 23.682 [11A] and 3GPP TS 23.401 [10]). The UE shall not request the use of PSM during:
– an attach for emergency bearer services procedure;
– an attach procedure for initiating a PDN connection for emergency bearer services with attach type not set to "EPS emergency attach";
– a tracking area updating procedure for initiating a PDN connection for emergency bearer services; or
– a tracking area updating procedure when the UE has a PDN connection established for emergency bearer services.
The network accepts the use of PSM by providing a specific value for timer T3324 when accepting the attach or tracking area updating procedure. The UE may use PSM only if the network has provided the T3324 value IE during the last attach or tracking area updating procedure with a value different from "deactivated".
[TS 24.301 clause 5.3.12]
The UE may request the use of extended idle-mode DRX cycle (eDRX) during an attach or tracking area updating procedure by including the extended DRX parameters IE (see 3GPP TS 23.682 [11A] and 3GPP TS 23.401 [10]). The UE shall not request the use of eDRX during:
…
The network accepts the request to use the eDRX by providing the extended DRX parameters IE when accepting the attach or the tracking area updating procedure. The UE shall use eDRX only if the network has provided the extended DRX parameters IE during the last attach or tracking area updating procedure.
NOTE: If the UE wants to keep using eDRX, the UE includes the extended DRX parameters IE in each attach or tracking area updating procedure.
[TS 24.301 clause 5.3.13]
The UE can request the use of both PSM and eDRX during an attach or tracking area update procedure but it is up to the network to decide to enable none, one of them or both (see 3GPP TS 23.682 [11A] and 3GPP TS 23.401 [10]).
If the network accepts the use of both PSM (see subclause 5.3.11) and eDRX (see subclause 5.3.12), the extended DRX parameters IE provided to the UE should allow for multiple paging occasions before the active timer expires.
[TS 24.301 clause 5.5.1.2.2]
If the UE supports eDRX and requests the use of eDRX, the UE shall include the extended DRX parameters IE in the ATTACH REQUEST message.
[TS 24.301 clause 5.5.1.2.4]
The MME shall include the extended DRX parameters IE in the ATTACH ACCEPT message only if the extended DRX parameters IE was included in the ATTACH REQUEST message, and the MME supports and accepts the use of eDRX.
[TS 24.301 clause 5.5.3.2.2]
The UE in state EMM-REGISTERED shall initiate the tracking area updating procedure by sending a TRACKING AREA UPDATE REQUEST message to the MME,
- when the UE detects entering a tracking area that is not in the list of tracking areas that the UE previously registered in the MME;
…
u) when the UE needs to request the use of eDRX or needs to stop the use of eDRX;
v) when a change in the eDRX usage conditions at the UE requires different extended DRX parameters;
…
If the UE supports eDRX and requests the use of eDRX, the UE shall include the extended DRX parameters IE in the TRACKING AREA UPDATE REQUEST message.
[TS 24.301 clause5.5.3.2.4]
The MME shall include the extended DRX parameters IE in the TRACKING AREA UPDATE ACCEPT message only if the extended DRX parameters IE was included in the TRACKING AREA UPDATE REQUEST message, and the MME supports and accepts the use of eDRX.
[TS 24.301 clause5.6.2.2.1.1]
To initiate the procedure the EMM entity in the network requests the lower layer to start paging (see 3GPP TS 36.300 [20], 3GPP TS 36.413 [23]) and shall start the timer:
– T3415 for this paging procedure, if the network accepted to use eDRX for the UE.
22.5.18.3 Test description
22.5.18.3.1 Pre-test conditions
System Simulator:
– NB-IoT Ncell 1, set to "Serving cell";
– NB-IoT Ncell 11, set to Non-Suitable cell".
– System information combination 2 as defined in TS 36.508[18] clause 8.1.4.3.1.1 is used in NB-IoT cells.
UE:
– The UE is previously registered on E-UTRAN, and when on E-UTRAN, the UE is last authenticated and registered on the NB-IoT cell using default message contents according to TS 36.508 [18].
– the UE is configured to request the use of eDRX (in the ATTACH REQUEST and TRACKING AREA UPDATE messages).
– The UE is configured to use Power Saving Mode.
– The UE is configured to set T3324 to two minutes.
Preamble:
– UE is in State 1-NB switched off.
22.5.18.3.2 Test procedure sequence
Table 22.5.18.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
The following messages are sent and shall be received on Ncell 1. |
– |
– |
– |
– |
|
|
1-14b1 |
Steps 1 – 14b1 of the generic procedure specified in TS 36.508 subclause 8.1.5.2.3 are performed |
– |
– |
– |
– |
|
15 |
Check: Does the UE transmit an ATTACH COMPLETE message including an Extended DRX parameters IE? |
–> |
ATTACH COMPLETE |
1 |
P |
|
16 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
17 |
SS transmits a Paging message to the UE in a valid paging occasion in paging hyperframe as per Idle eDRX |
<– |
Paging-NB |
– |
– |
|
18-19 |
Steps 2 to 3 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508 8.1.5A.2.3) are executed. |
– |
– |
– |
– |
|
20-21 |
Void |
– |
– |
– |
– |
|
21A |
Check: Does the UE transmit a CONTROL PLANE SERVICE REQUEST according to step 4a1a1 or 4a1b1 in the generic procedure in TS 36.508, clause 8.1.5A.2.3? |
–> |
CONTROL PLANE SERVICE REQUEST |
2 |
P |
|
21B |
Steps 4a1b1 to 5 or only step 5 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508, clause 8.1.5A.2.3) are executed |
– |
– |
– |
– |
|
22 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
23 |
Set the cell type of Ncell 1 to the "Non-Suitable cell". Set the cell type of Ncell 11 to the " Serving cell" |
||||
|
24 |
The UE transmits a TRACKING AREA UPDATE REQUEST message including an Extended DRX parameters IE |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
|
25 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message without an Extended DRX parameters IE. GUTI-1 is included. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
|
26 |
Check: Does the UE transmit a TRACKING AREA UPDATE COMPLETE message without an Extended DRX parameters IE? |
–> |
TRACKING AREA UPDATE COMPLETE |
3 |
P |
|
27 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
28 |
SS transmits a Paging-NB message to the UE in a valid paging occasion as per normal DRX |
<– |
Paging-NB |
||
|
29–30 |
Steps 2 to 3 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508 8.1.5A.2.3) are executed. |
– |
– |
– |
– |
|
31-32 |
Void |
– |
– |
– |
– |
|
32A |
Check: Does the UE transmit a CONTROL PLANE SERVICE REQUEST according to step 4a1a1 or 4a1b1 in the generic procedure in TS 36.508, clause 8.1.5A.2.3? |
–> |
CONTROL PLANE SERVICE REQUEST |
4 |
P |
|
32B |
Steps 4a1b1 to 5 or only step 5 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508, clause 8.1.5A.2.3) are executed |
– |
– |
– |
– |
|
33 |
The UE is switched off, see Note 1. |
– |
– |
– |
– |
|
34 |
Set the cell type of Ncell 1 to the "Serving cell". Set the cell type of Ncell 11 to the "Non-Suitable cell". |
– |
– |
– |
– |
|
35 |
The UE is switched on |
– |
– |
– |
– |
|
36–48b1 |
Steps 2 – 14b1 of the generic procedure specified in TS 36.508 subclause 8.1.5.2.3 are performed |
– |
– |
– |
– |
|
49 |
Check: Does the UE transmit an ATTACH COMPLETE message without an Extended DRX parameters IE? |
–> |
ATTACH COMPLETE |
5 |
P |
|
50 |
The SS releases the RRC connection |
– |
– |
– |
– |
|
51 |
SS transmits a Paging-NB message to the UE in a valid paging occasion as per normal DRX |
<– |
Paging-NB |
||
|
52–53 |
Steps 2 to 3 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508 8.1.5A.2.3) are executed. |
– |
– |
– |
– |
|
54-55 |
Void |
– |
– |
– |
– |
|
55A |
Check: Does the UE transmit a CONTROL PLANE SERVICE REQUEST according to step 4a1a1 or 4a1b1 in the generic procedure in TS 36.508, clause 8.1.5A.2.3? |
–> |
CONTROL PLANE SERVICE REQUEST |
6 |
P |
|
55B |
Steps 4a1b1 to 5 or only step 5 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508, clause 8.1.5A.2.3) are executed |
– |
– |
– |
– |
|
55C |
The SS releases the RRC connection |
– |
– |
– |
– |
|
56 |
Set the cell type of Ncell 1 to the "Non-Suitable cell". Set the cell type of Ncell 11 to the " Serving cell" |
||||
|
57 |
The UE transmits a TRACKING AREA UPDATE REQUEST message including an Extended DRX parameters IE |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
|
58 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message including an Extended DRX parameters IE. GUTI-2 is included. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
|
59 |
The UE transmits a TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
7 |
P |
|
60 |
The SS releases the RRC connection. |
– |
– |
||
|
61 |
SS transmits a Paging-NB message to the UE in a valid paging occasion in paging hyperframe as per Idle eDRX |
<– |
Paging-NB |
||
|
62–63 |
Steps 2 to 3 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508 8.1.5A.2.3) are executed. |
||||
|
64-65 |
Void |
– |
– |
– |
– |
|
65A |
Check: Does the UE transmit a CONTROL PLANE SERVICE REQUEST according to step 4a1a1 or 4a1b1 in the generic procedure in TS 36.508, clause 8.1.5A.2.3? |
–> |
CONTROL PLANE SERVICE REQUEST |
8 |
P |
|
65B |
Steps 4a1b1 to 5 or only step 5 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508, clause 8.1.5A.2.3) are executed |
– |
– |
– |
– |
|
66 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
67 |
The UE is switched off, see Note 1. |
– |
– |
– |
– |
|
68 |
SS sets the cell type of Ncell 1 to the "Serving cell". Set the cell type of Ncell 11 to the "Non-Suitable cell". |
– |
– |
– |
– |
|
– |
The following messages are sent and shall be received on Ncell 1. |
– |
– |
– |
– |
|
70–83b1 |
Steps 1 – 14b1 of the generic procedure specified in TS 36.508 subclause 8.1.5.2.3 is performed |
– |
– |
– |
– |
|
84 |
Check: Does the UE transmit an ATTACH COMPLETE message including an Extended DRX parameters IE and the T3324 IE set to two minutes? |
–> |
ATTACH COMPLETE |
9 |
P |
|
85 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
86 |
SS transmits a Paging message to the UE in a valid paging occasion in paging hyperframe as per Idle eDRX |
<– |
Paging-NB |
– |
– |
|
87–88 |
Steps 2 to 3 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508 8.1.5 A.2.3) are executed. |
||||
|
89-90 |
Void |
– |
– |
– |
– |
|
90A |
Check: Does the UE transmit a CONTROL PLANE SERVICE REQUEST according to step 4a1a1 or 4a1b1 in the generic procedure in TS 36.508, clause 8.1.5A.2.3? |
–> |
CONTROL PLANE SERVICE REQUEST |
10 |
P |
|
90B |
Steps 4a1b1 to 5 or only step 5 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508, clause 8.1.5A.2.3) are executed |
– |
– |
– |
– |
|
91 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
92 |
SS sets the cell type of Ncell 1 to the "Non-Suitable cell". Set the cell type of Ncell 11 to the " Serving cell" |
– |
– |
– |
– |
|
93 |
The UE transmits a TRACKING AREA UPDATE REQUEST message including an Extended DRX parameters IE and the T3324 IE set to two minutes. |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
|
94 |
The SS transmits a TRACKING AREA UPDATE ACCEPT message without an Extended DRX parameters IE but with the T3324 IE set to 2 minutes. GUTI-3 is included. |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
|
95 |
The UE transmits a TRACKING AREA UPDATE COMPLETE message. |
–> |
TRACKING AREA UPDATE COMPLETE |
11 |
P |
|
96 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
97 |
When the T3324 timer expires the SS sends Paging message including a matched identity in a valid paging occasion as per normal DRX |
<– |
Paging-NB |
– |
– |
|
98 |
Check: Does the UE respond to the paging message? |
– |
– |
12 |
F |
|
98A |
The SS waits 4 minutes. (Expiry of T3412 extended value) |
– |
– |
– |
– |
|
98B |
The UE transmits a TRACKING AREA UPDATE REQUEST message |
–> |
TRACKING AREA UPDATE REQUEST |
– |
– |
|
98C |
The SS transmits a TRACKING AREA UPDATE ACCEPT message |
<– |
TRACKING AREA UPDATE ACCEPT |
– |
– |
|
98D |
The UE transmits a TRACKING AREA UPDATE COMPLETE message? |
–> |
TRACKING AREA UPDATE COMPLETE |
– |
– |
|
98E |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
99 |
If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 99a1 describes behaviour that depends on the UE capability. |
||||
|
99a1 |
If pc_SwitchOnOff or pc_USIM_Removal then the UE transmits a DETACH REQUEST. |
–> |
DETACH REQUEST |
– |
– |
|
100 |
SS sets the cell type of Ncell 1 to the "Serving cell". Set the cell type of Ncell 11 to the "Non-Suitable cell". |
– |
– |
– |
– |
|
101 |
The UE is switched on |
– |
– |
– |
– |
|
102–114b1 |
Steps 2 – 14b1 of the generic procedure specified in TS 36.508 subclause 8.1.5.2.3 is performed |
– |
– |
– |
– |
|
115 |
Check: Does the UE transmit an ATTACH COMPLETE message including an Extended DRX parameters IE but without the T3324 IE? |
–> |
ATTACH COMPLETE |
13 |
P |
|
115A |
The SS releases the RRC connection. |
||||
|
116 |
SS sends a Paging message to the UE in a valid paging occasion in paging hyperframe as per Idle eDRX |
<– |
Paging-NB |
– |
– |
|
117–118 |
Steps 2 to 3 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508 8.1.5 A.2.3) are executed. |
– |
– |
– |
– |
|
119-120 |
Void |
– |
– |
– |
– |
|
120A |
Check: Does the UE transmit a CONTROL PLANE SERVICE REQUEST according to step 4a1a1 or 4a1b1 in the generic procedure in TS 36.508, clause 8.1.5A.2.3? |
–> |
CONTROL PLANE SERVICE REQUEST |
14 |
P |
|
120B |
Steps 4a1b1 to 5 or only step 5 of the NB-IoT Control Plane CIoT MT user data transfer non-SMS transport procedure (TS 36.508, clause 8.1.5A.2.3) are executed |
– |
– |
– |
– |
|
121 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
NOTE 1: This implies detaching of the UE, releasing of the RRC connection and resetting of the radio bearers at the SS side. |
|||||
22.5.18.3.3 Specific message contents
Table 22.5.18.3.3-1: Void
Table 22.5.18.3.3-2: Message ATTACH REQUEST (step 1-14b1 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
Any Value |
||
|
eDRX value |
Any Value |
||
Table 22.5.18.3.3-3: Message ATTACH ACCEPT (step 1-14b1 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
‘0000’B |
2.56 seconds |
|
|
eDRX value |
‘0011’B |
40.96 seconds |
|
Table 22.5.18.3.3-4: Void
Table 22.5.18.3.3-5: Message TRACKING AREA UPDATE REQUEST (step 24 in Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
Any Value |
||
|
eDRX value |
Any Value |
||
Table 22.5.18.3.3-6: Message TRACKING AREA UPDATE ACCEPT (step 25 in Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-24 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
GUTI |
GUTI-1 |
||
|
Extended DRX parameters |
Not Present |
||
Table 22.5.18.3.3-7: Message TRACKING AREA UPDATE COMPLETE (step 26 in Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-25 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
GUTI |
GUTI-1 |
||
Table 22.5.18.3.3-8: Message ATTACH REQUEST (step 36–48b1 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
Any Value |
||
|
eDRX value |
Any Value |
||
Table 22.5.18.3.3-9: Message ATTACH ACCEPT (step 36–48b1 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
Not present |
||
Table 22.5.18.3.3-10: Message ATTACH COMPLETE (step 49 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-2 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
Not present |
||
Table 22.5.18.3.3-11: Message TRACKING AREA UPDATE REQUEST (step 57 in Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
Any Value |
||
|
eDRX value |
Any Value |
||
Table 22.5.18.3.3-12: Message TRACKING AREA UPDATE ACCEPT (step 58 in Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-24 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
‘0000’B |
2.56 seconds |
|
|
eDRX value |
‘0011’B |
40.96 seconds |
|
|
GUTI |
GUTI-2 |
||
Table 22.5.18.3.3-13: Message ATTACH REQUEST (step 70–83b1 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
Any Value |
||
|
eDRX value |
Any Value |
||
|
T3324 |
‘00100010’B |
2 minutes |
|
Table 22.5.18.3.3-14: Message ATTACH ACCEPT (step 70–83b1 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
‘0000’B |
2.56 seconds |
|
|
eDRX value |
‘0011’B |
40.96 seconds |
|
|
T3324 |
‘00100010’B |
2 minutes |
|
Table 22.5.18.3.3-15: Void
Table 22.5.18.3.3-16: Message TRACKING AREA UPDATE REQUEST (step 93 in Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
Any Value |
||
|
eDRX value |
Any Value |
||
|
T3324 value |
‘00100010’B |
2 minutes |
|
Table 22.5.18.3.3-17: Message TRACKING AREA UPDATE ACCEPT (step 94 in Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-24 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
GUTI |
GUTI-3 |
||
|
Extended DRX parameters |
Not Present |
||
|
T3324 value |
‘00100010’B |
2 minutes |
|
|
T3412 extended value |
‘10100100’B |
4 minutes |
|
Table 22.5.18.3.3-18: Message TRACKING AREA UPDATE COMPLETE (step 95 in Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-25 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
GUTI |
GUTI-3 |
||
Table 22.5.18.3.3-19: Message ATTACH REQUEST (step 102–114b1 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
Any Value |
||
|
eDRX value |
Any Value |
||
|
T3324 |
‘00100010’B |
2 minutes |
|
Table 22.5.18.3.3-20: Message ATTACH ACCEPT (step 102–114b1 in Table 22.5.18.3.2-1)
|
Derivation path: TS 36.508 table 4.7.2-1 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
Extended DRX parameters |
|||
|
Paging Time Window |
‘0000’B |
2.56 seconds |
|
|
eDRX value |
‘0011’B |
40.96 seconds |
|
|
T3324 |
Not present |
||
Table 22.5.18.3.3-21: Void
Table 22.5.18.3.3-22: Message TRACKING AREA UPDATE REQUEST (step 98B, Table 22.5.18.3.2-1)
|
Derivation path: 36.508 table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS update type |
011 |
periodic updating’ |
|