9.2.4 Attach and Tracking area updating procedures

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

9.2.4.1 eDRX

9.2.4.1.1 Attach & Normal tracking area update Procedure / Success / without Idle eDRX parameters / With Idle eDRX parameters

9.2.4.1.1.1 Test Purpose (TP)

(1)

with { the UE has sent an 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 sends an ATTACH COMPLETE message }

}

(2)

with { the UE has applied extended DRX parameters received in the ATTACH ACCEPT message }

ensure that {

when { the UE receives the Paging message in a valid paging occasion in paging hyperframe as per idle eDRX }

then { the UE sends a SERVICE REQUEST message }

}

(3)

with { the UE has sent a TAU EQUESTR message with extended DRX parameters IE }

ensure that {

when { the UE does not receive the extended DRX parameters in the TAU ACCEPT message }

then { the UE sends a TAU COMPLETE message }

}

(4)

with { the UE has not received extended DRX parameters in the TAU ACCEPT message }

ensure that {

when { the UE receives the Paging message in a valid paging occasion as per normal DRX }

then { the UE sends the SERVICE REQUEST message }

}

(5)

with { the U E has sent an ATTACH REQUEST message with extended DRX parameters IE }

ensure that {

when { the UE does not receive the extended DRX parameters in the ATTACH ACCEPT message }

then { the UE sends an ATTACH COMPLETE message}

}

(6)

with { the UE has not received extended DRX parameters in the ATTACH ACCEPT message }

ensure that {

when { the UE receives the Paging message in a valid paging occasion as per normal DRX }

then { the UE sends a SERVICE REQUEST message}

}

(7)

with { the UE has sent a 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 sends a TAU COMPLETE message}

}

(8)

with { the UE has applied the extended DRX parameters received in the TAU ACCEPT message }

ensure that {

when { the UE receives a Paging message in a valid paging occasion in paging hyperframe as per Idle eDRX }

then { the UE sends a SERVICE REQUEST message}

}

9.2.4.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.3.12, 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 clause5.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:

…

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 clause5.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 clause5.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 clause5.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.

9.2.4.1.1.3 Test description

9.2.4.1.1.3.1 Pre-test conditions

System Simulator:

– cell A (belongs to TAI-1, home PLMN) is set to ”Serving cell”;

– cell B (belongs to TAI-2, home PLMN) is set to ”Non- Suitable cell”;

UE:

– the UE is configured to request the use of eDRX (in the ATTACH REQUEST and TRACKING AREA UPDATE messages).

Preamble:

– the UE is in state Switched OFF (state 1) according to TS 36.508 [18].

9.2.4.1.1.3.2 Test procedure sequence

Table 9.2.4.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
	The following messages are sent and shall be received on cell A.	–	–	–	–
1	The UE is switched on.	–	–	–	–
2	The UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message and an Extended DRX parameters IE	–>	ATTACH REQUEST	–	–
3-11	Steps 5 to 13 of the generic test procedure in TS 36.508 Table 4.5.2.3-1 (Attach procedure) are performed on Cell A.	–	–	–	–
12	SS responds with ATTACH ACCEPT message including an Extended DRX parameters IE. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message	<–	ATTACH ACCEPT	–	–
–	EXCEPTION: In parallel to the event described in steps 13 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane if requested by the UE	–	–	–	–
–	EXCEPTION: IF PDN1_IMS (NOTE 1) THEN in parallel to the event described in steps 13 below the generic procedure for IMS signalling in the Uplane specified in TS 36.508 subclause 4.5A.3 takes place if requested by the UE	–	–	–	–
13	Check: Does the UE transmit an ATTACH COMPLETE message including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?	–>	ATTACH COMPLETE	1	P
13A1a1-13A3b1	Steps 16a1-18b1 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed	–	–	–	–
14	SS transmits a Paging message to the UE in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX	<–	Paging	–	–
15	Check: Does the UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	2	P
16-19	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.	–	–	–	–
20	The SS releases the RRC connection.	–	–	–	–
21	Set the cell type of cell A to the "Non-Suitable cell". Set the cell type of cell B to the "Serving cell"	–	–	–	–
22	The UE transmits a TRACKING AREA UPDATE REQUEST message including an Extended DRX parameters IE	–>	TRACKING AREA UPDATE REQUEST	–	–
23	The SS transmits a TRACKING AREA UPDATE ACCEPT message without an Extended DRX parameters IE.	<–	TRACKING AREA UPDATE ACCEPT	–	–
24	The UE transmits a TRACKING AREA UPDATE COMPLETE message.	–>	TRACKING AREA UPDATE COMPLETE	3	P
25	The SS releases the RRC connection.	–	–	–	–
26	SS transmits a Paging message to the UE in a valid PO as per normal DRX	<–	Paging
27	Check: Does the UE respond to Paging according to procedure TS 36.508 6.4.2.2-1 Steps 2 to 11?	–	–	4	P
28	If possible (see ICS) switch off is performed or otherwise the power is removed	–	–	–	–
–	EXCEPTION: Step 29 describes behaviour that depends on the UE capability.	–	–	–	–
29	If pc_SwitchOnOff or pc_USIM_Removal then UE sends DETACH REQUEST message.	–>	DETACH REQUEST
30	Set the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Non-Suitable cell".	–	–	–	–
31	The UE is switched on	–	–	–	–
32	The UE transmits an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message and an Extended DRX parameters IE.	–>	ATTACH REQUEST	–	–
33-41	Steps 5 to 13 of the generic test procedure in TS 36.508 Table 4.5.2.3-1 (Attach procedure) are performed on Cell A.	–	–	–	–
42	SS responds with ATTACH ACCEPT message without including an Extended DRX parameters IE. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message	<–	ATTACH ACCEPT	–	–
–	EXCEPTION: In parallel to the event described in steps 13 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane if requested by the UE.		–	–	–
—	EXCEPTION: IF PDN1_IMS (NOTE 1) THEN in parallel to the event described in steps 13 below the generic procedure for IMS signalling in the Uplane specified in TS 36.508 subclause 4.5A.3 takes place if requested by the UE	–	–	–	–
43	Check: Does the UE transmit an ATTACH COMPLETE message message including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?	–>	ATTACH COMPLETE	5	P
43A1a1-43A3b1	Steps16a1-18b1 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.	–	–	–	–
44	SS transmits a Paging message to the UE in a validPO as per normal DRX	<–	Paging	–	–
45	Check: Does the UE respond to Paging according to procedure TS 36.508 6.4.2.2-1 Steps 2 to 11?	–	–	6	P
46	Set the cell type of cell A to the "Non-Suitable cell". Set the cell type of cell B to the "Serving cell"	–	–	–	–
47	The UE transmits a TRACKING AREA UPDATE REQUEST message including an Extended DRX parameters IE	–>	TRACKING AREA UPDATE REQUEST	–	–
48	The SS transmits a TRACKING AREA UPDATE ACCEPT message including an Extended DRX parameters IE.	<–	TRACKING AREA UPDATE ACCEPT	–	–
49	The UE transmits a TRACKING AREA UPDATE COMPLETE message.	–>	TRACKING AREA UPDATE COMPLETE	7	P
50	The SS releases the RRC connection.	–	–	–	–
51	SS transmits a Paging message to the UE in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX	<–	Paging
52	Check: Does the UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	8	P
53-56	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.	–	–	–	–
57	The SS releases the RRC connection.	–	–	–	–
NOTE 1: PDN1_IMS as defined in TS 36.508 subclause 4.5.2.

9.2.4.1.1.3.3 Specific message contents

Table 9.2.4.1.1.3.3-1: SystemInformationBlockType1 for Cell A and Cell B

Derivation path: 36.508 Table 4.4.3.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}

Table 9.2.4.1.1.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell A and Cell B when UE under test is CAT M1

Derivation path: 36.508 Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}

Table 9.2.4.1.1.3.3-2: Message ATTACH REQUEST (step 2 in Table 9.2.4.1.1.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 9.2.4.1.1.3.3-3: Message ATTACH ACCEPT (step 12 in Table 9.2.4.1.1.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	‘0001’B	2.56 seconds
eDRX value	‘0011’B	40.96 seconds

Table 9.2.4.1.1.3.3-4: Message TRACKING AREA UPDATE REQUEST (step 22 in Table 9.2.4.1.1.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 9.2.4.1.1.3.3-5: Message TRACKING AREA UPDATE Accept (step 23 in Table 9.2.4.1.1.3.2-1)

Derivation path: 36.508 table 4.7.2-24
Information Element	Value/Remark	Comment	Condition
Extended DRX parameters	Not Present

Table 9.2.4.1.1.3.3-6: Message ATTACH REQUEST (step 32 in Table 9.2.4.1.1.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 9.2.4.1.1.3.3-7: Message ATTACH ACCEPT (step 42 in Table 9.2.4.1.1.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 9.2.4.1.1.3.3-8: Message TRACKING AREA UPDATE REQUEST (step 47 in Table 9.2.4.1.1.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 9.2.4.1.1.3.3-9: Message TRACKING AREA UPDATE Accept (step 48 in Table 9.2.4.1.1.3.2-1)

Derivation path: 36.508 table 4.7.2-24
Information Element	Value/Remark	Comment	Condition
Extended DRX parameters
Paging Time Window	‘0001’B	2.56 seconds
eDRX value	‘0011’B	40.96 seconds

9.2.4.1.2 Attach & Normal tracking area update Procedure / Success / With and without Idle eDRX and PSM parameters

9.2.4.1.2.1 Test Purpose (TP)

(1)

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 sends an ATTACH COMPLETE message }

}

(2)

with { the UE has applied extended DRX parameters received in the ATTACH ACCEPT message }

ensure that {

when { the UE receives a Paging message in a valid paging occasion in paging hyperframe as per idle eDRX }

then { the UE sends a SERVICE REQUEST message }

}

(3)

with { the UE has sent a TAU REQUEST message with the 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 sends a TAU COMPLETE message }

}

(4)

with { the UE has received a TAU ACCEPT message not including extended DRX parameters IE but including T3324 IE }

ensure that {

when { the UE receives a Paging message after T3324 timer expiry in a valid paging occasion as per normal DRX }

then { the UE does not send the SERVICE REQUEST message }

}

(5)

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 parameters but not the T3324 IE }

then { the UE sends an ATTACH COMPLETE message }

}

(6)

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 message in a valid paging occasion in paging hyperframe as per Idle eDRX }

then { the UE sends a SERVICE REQUEST message }

}

9.2.4.1.2.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]

…

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]

[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 clause 5.5.3.2.4]

[TS 24.301 clause 5.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.

9.2.4.1.2.3 Test description

9.2.4.1.2.3.1 Pre-test conditions

System Simulator:

– cell A (belongs to TAI-1, home PLMN) is set to ”Serving cell”;

– cell B (belongs to TAI-2, home PLMN) is set to ”Non- Suitable cell”;

UE:

– the UE is configured to request the use of eDRX (in the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST messages).

– The UE is configured to use Power Saving Mode

– The UE is configured to set T3324 as two minutes

Preamble:

– the UE is in state Switched OFF (state 1) according to TS 36.508 [18].

9.2.4.1.2.3.2 Test procedure sequence

Table 9.2.4.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	The following messages are sent and shall be received on cell A.	–	–	–	–
1	The UE is switched on.	–	–	–	–
2	The UE transmits an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message and an Extended DRX parameters IE and T3324 IE set to two minutes	–>	ATTACH REQUEST	–	–
3-11	Steps 5 to 13 of the generic test procedure in TS 36.508 Table 4.5.2.3-1 (Attach procedure) are performed on Cell A.	–	–	–	–
12	SS responds with ATTACH ACCEPT message including an Extended DRX parameters IE and the T3324 IE set to two minutes. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message	<–	ATTACH ACCEPT	–	–
–	EXCEPTION: In parallel to the event described in steps 13 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane if requested by the UE.	–	–	–	–
–	EXCEPTION: IF PDN1_IMS (NOTE 1) then in parallel to the event described in steps 13 below the generic procedure for IMS signalling in the Uplane specified in TS 36.508 subclause 4.5A.3 takes place if requested by the UE	–	–	–	–
13	Check: Does the UE transmit an ATTACH COMPLETE message including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?	–>	ATTACH COMPLETE	1	P
14a1-16b1	Steps 16a1-18b1 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed	–	–	–	–
17	SS sends a Paging message to the UE in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX	<–	Paging	–	–
18	Check: Does the UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	2	P
19-22	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.	–	–	–	–
23	The SS releases the RRC connection.	–	–	–	–
24	SS sets the cell type of cell A to the "Non-Suitable cell". Set the cell type of cell B to the "Serving cell"	–	–	–	–
25	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	–	–
26	The SS transmits a TRACKING AREA UPDATE ACCEPT message without an Extended DRX parameters IE but with the T3324 IE set to 2 minutes.	<–	TRACKING AREA UPDATE ACCEPT	–	–
27	The UE transmits a TRACKING AREA UPDATE COMPLETE message.	–>	TRACKING AREA UPDATE COMPLETE	3	P
28	The SS releases the RRC connection.	–	–	–	–
29	When the T3324 timer expires the SS sends a Paging message including a matched identity in a valid PO as per normal DRX	<–	Paging	–	–
30	Check: Does the UE respond to the Paging message?	–	–	4	F
31	If possible (see ICS) the UE is switched off or otherwise the power is removed	–	–	–	–
–	EXCEPTION: Step 32a1 describes behaviour that depends on the UE capability.	–	–	–	–
32a1	If pc_SwitchOnOff or pc_USIM_Removal then UE send DETACH REQUEST message.	–>	DETACH REQUEST	–	–
33	SS sets the cell type of cell A to the "Serving cell". Set the cell type of cell B to the "Non-Suitable cell".	–	–	–	–
34	The UE is switched on	–	–	–	–
35	The UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message and an Extended DRX parameters IE and the T3324 IE set to two minutes	–>	ATTACH REQUEST	–	–
36-44	Steps 5 to 13 of the generic test procedure in TS 36.508 Table 4.5.2.3-1 (Attach procedure) are performed on Cell A.	–	–	–	–
45	SS responds with ATTACH ACCEPT message including an Extended DRX parameters IE but without the T3324 IE. The ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message is piggybacked in ATTACH ACCEPT message.	<–	ATTACH ACCEPT	–	–
46	Check: Does the UE transmit an ATTACH COMPLETE message including an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message?	–>	ATTACH COMPLETE	5	P
47a1-49b1	Steps 16a1-18b1 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed	–	–	–	–
50	SS sends a Paging message to the UE in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX	<–	Paging	–	–
51	Check: Does the UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	6	P
52-55	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.	–	–	–	–
56	The SS releases the RRC connection.	–	–	–	–
NOTE 1: PDN1_IMS as defined in TS 36.508 subclause 4.5.2.

9.2.4.1.2.3.3 Specific message contents

Table 9.2.4.1.2.3.3-1: SystemInformationBlockType1 for Cell A and Cell B

Derivation path: 36.508 Table 4.4.3.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}

Table 9.2.4.1.2.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell A and Cell B when UE under test is CAT M1

Derivation path: 36.508 Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}

Table 9.2.4.1.2.3.3-2: Message ATTACH REQUEST (step 2)

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
T3412 extended value	Not present
	Any allowed value		IF the UE indicates support for extended periodic timer value in the MS network feature support IE

Table 9.2.4.1.2.3.3-3: Message ATTACH ACCEPT (step 12)

Derivation path: TS 36.508 table 4.7.2-4
Information Element	Value/Remark	Comment	Condition
Extended DRX parameters
Paging Time Window	‘0001’B	2.56 second
eDRX value	‘0011’B	40.96 seconds
T3324	’00100010’B	2 minutes
T3412 extended value	Value received in ATTACH REQUEST	Included only if the IE ‘T3412 extended value’ was provided in the ATTACH REQUEST

Table 9.2.4.1.2.3.3-4: Message TRACKING AREA UPDATE REQUEST (step 25)

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
T3412 extended value	Not present
	Any allowed value		IF the UE indicates support for extended periodic timer value in the MS network feature support IE

Table 9.2.4.1.2.3.3-5: Message TRACKING AREA UPDATE ACCEPT (step 26)

Derivation path: 36.508 table 4.7.2-24
Information Element	Value/Remark	Comment	Condition
T3324 value	’00100010’B	2 minutes
T3412 extended value	Value received in TRACKING AREA UPDATE REQUEST	Included only if the IE ‘T3412 extended value’ was provided in the TRACKING AREA UPDATE REQUEST

Table 9.2.4.1.2.3.3-6: Message ATTACH REQUEST (step 35)

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 value	’00100010’B	2 minutes

Table 9.2.4.1.2.3.3-7: Message ATTACH ACCEPT (step 45)

Derivation path: TS 36.508 table 4.7.2-4
Information Element	Value/Remark	Comment	Condition
Extended DRX parameters
Paging Time Window	‘0001’B	2.56 seconds
eDRX value	‘0011’B	40.96 seconds
T3324	Not Present

9.2.4.1.3 Attach & Normal tracking area Procedure / Success / Emergency Calls/ without Idle eDRX parameters / With Idle eDRX parameters

9.2.4.1.3.1 Test Purpose (TP)

(1)

with { UE in EMM-DEREGISTERED state}

ensure that {
when { the UE initiates an Attach Procedure for emergency bearer services }

then { the UE sends an ATTACH REQUEST message without including the Extended DRX parameters IE }

}

(2)

with { UE attached for emergency bearer services }

ensure that {
when { the UE detects entering a new Tracking Area that is not included in the TAI list }

then { the UE sends a TAU REQUEST message without including the Extended DRX parameters IE }

}

(3)

with { the UE resumed eDRX after PDN disconnection for emergency bearer service }

ensure that {

when { the UE receives a Paging message in a valid paging occasion in paging hyperframe as per Idle eDRX }

then { the UE sends a SERVICE REQUEST message }

}

(4)

with { the UE resumed eDRX after PDN disconnection for emergency bearer service }

ensure that {

when { the UE detects entering a new Tracking Area not included in the TAI list }

then { the UE sends a TAU REQUEST message with the extended DRX parameters IE }

}

9.2.4.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.3.12.

[TS 24.301, clause 5.3.12]

– an attach for emergency bearer services procedure; or

– a tracking area updating procedure for the UE attached for emergency bearer services.

The UE and the network may negotiate eDRX parameters during a tracking area updating procedure when the UE has a PDN connection for emergency bearer services.

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 and the UE does not have a PDN connection for emergency bearer services. If the network did not accept the request to use eDRX, or if the UE has a PDN connection for emergency bearer services, the UE and the network shall use the stored UE specific DRX cycle, if any, instead of eDRX.

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.

While the UE has a PDN connection for emergency bearer services established, the UE shall not use eDRX. If the network has provided the extended DRX parameters IE during the last attach or tracking area updating procedure, upon successful completion of the PDN disconnect procedure of the PDN connection for emergency bearer services or EPS bearer context deactivation procedure of the EPS bearer context for emergency, the UE and the network shall resume eDRX. If the UE or the network locally releases the PDN connection for emergency bearer service, the UE or the network shall not use eDRX until the UE receives eDRX parameters during a tracking area updating procedure with EPS bearer context synchronization or upon successful completion of a service request procedure

9.2.4.1.3.3 Test description

9.2.4.1.3.3.1 Pre-test conditions

System Simulator:

– Cell A belongs to TAI-1 and is set to ”Serving cell”

– Cell B belongs to TAI-2 and is set to “Non-suitable off cell”

UE:

– The UE is configured to request the use of eDRX (the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST messages).

Preamble:

– UE sends an ATTACH REQUEST message with eDRX parameters in Cell A. SS sends an ATTACH REJECT message with EMM cause = "Tracking area not allowed". UE stores the TAI in the list of "forbidden tracking areas for regional provision of service" and enters EMM-DEREGISTERED.LIMITED-SERVICE state.

9.2.4.1.3.3.2 Test procedure sequence

Table 9.2.4.1.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Make the UE attempt an IMS emergency call	–	–	–	–
2-3	Steps 2 to 3 of the generic procedures in TS 36.508 subclause 4.5A.5.3 are performed in Cell A	–	–	–	–
4	Check: Does the UE transmit an ATTACH REQUEST message to attach for emergency bearer services without including “Extended DRX parameters” IE and including a PDN CONNECTIVITY REQUEST message?	–>	ATTACH REQUEST PDN CONNECTIVITY REQUEST	1	P
5-19	Steps 5 to 19 of the generic test procedure for IMS Emergency call establishment in EUTRA: Limited Service (TS 36.508 Table 4.5A.5.3-1).	–	–	–	–
20	Set the cell type of Cell A to the ”Non-Suitable cell”. Set the cell type of Cell B to the ”Suitable cell”.	–	–	–	–
21	Check: Does the UE send TRACKING AREA UPDATE REQUEST in Cell B without including Extended DRX parameters IE?	–>	TRACKING AREA UPDATE REQUEST	2	P
22	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	TRACKING AREA UPDATE ACCEPT
23	The UE transmit a TRACKING AREA UPDATE COMPLETE message.	–>	TRACKING AREA UPDATE COMPLETE
24	The SS releases the RRC connection	–	–	–	–
25	If possible (see ICS) switch off is performed. Otherwise the power is removed	–	–	–	–
–	EXCEPTION: Step 26 describes behaviour that depends on the UE capability.	–	–	–	–
26	If pc_SwitchOnOff or pc_USIM_Removal then the UE transmits a DETACH REQUEST	–>	DETACH REQUEST	–	–
27	Set the cell type of cell A to “Suitable cell”. Set the cell type of cell B to ”Non-Suitable off cell”	–	–	–	–
28	Power on the UE	–	–	–	–
29-46	Steps 2 to 18b1 of the registration procedure described in TS 36.508 subclause 4.5.2.3 are performed on Cell A.	–	–	–	–
47	Cause the UE to request connectivity to an additional PDN for emergency bearer service	–	–	–	–
48-61	Steps 2 to 15 of the generic test procedure for IMS Emergency call establishment in EUTRA: in EUTRA: Normal Service (TS 36.508 Table 4.5A.4.3-1).	–	–	–	–
62	The SS waits for 5 seconds.	–
63	Release IMS Call (see Note 1).	–
64	The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST including the EPS bearer identity of the default EPS bearer to the additional PDN	–	DEACTIVATE EPS BEARER CONTEXT REQUEST	–	–
65	UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT	–	DEACTIVATE EPS BEARER CONTEXT ACCEPT	–	–
66	The SS releases the RRC connection	–	–	–	–
67	The SS waits 5 second	–	–	–	–
68	SS sends a Paging message to the UE in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX	<–	Paging	–	–
69	Check: Does the UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	3	P
70-72	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure	–	–	–	–
73	The SS releases the RRC connection.	–	–	–	–
74	Set the cell type of cell A to “Non-Suitable cell”. Set the cell type of cell B to ”Suitable cell”	–	–	–	–
75	Check: Does the UE send TRACKING AREA UPDATE REQUEST including the Extended DRX parameters IE?	–>	TRACKING AREA UPDATE REQUEST	4	P
76	The SS transmits a TRACKING AREA UPDATE ACCEPT message	<–	TRACKING AREA UPDATE ACCEPT	–	–
77	The UE transmit a TRACKING AREA UPDATE COMPLETE message	–>	TRACKING AREA UPDATE COMPLETE	–	–
78	SS releases RR the C Connection	–	–	–	–
Note 1: The IMS Call is released using the generic procedure in TS 34.229-1 [35] subclause C.32.

9.2.4.1.3.3.3 Specific message contents

Table 9.2.4.1.3.3.3-1: SystemInformationBlockType1 for Cell A and Cell B

Derivation path: 36.508 Table 4.4.3.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}
}
}
}
}

Table 9.2.4.1.3.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell A and Cell B when UE under test is CAT M1

Derivation path: 36.508 Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}
}
}
}
}

Table 9.2.4.1.3.3.3-2: Message ATTACH REQUEST (Preamble)

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 9.2.4.1.3.3.3-2: Message ATTACH REQUEST (step 4 in Table 9.2.4.1.3.3.2-1)

Derivation path: TS 36.508 table 4.7.2-4
Information Element	Value/Remark	Comment	Condition
EPS attach type	‘0110’B	EPS emergency attach
Extended DRX parameters	Not Present

Table 9.2.4.1.3.3.3-3: PDN CONNECTIVITY REQUEST (Step 4, Table 9.2.4.1.3.3.2-1)

Derivation Path: 36.508, Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
Request type	‘0100’B	emergency

Table 9.2.4.1.3.3.3-4: Message TRACKING AREA UPDATE REQUEST (step 21 in Table 9.2.4.1.3.3.2-1)

Derivation path: 36.508 table 4.7.2-27
Information Element	Value/Remark	Comment	Condition
Extended DRX parameters	Not Present

Table 9.2.4.1.3.3.3-5: Message ATTACH REQUEST (step 31 in Table 9.2.4.1.3.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 9.2.4.1.3.3.3-6: Message ATTACH ACCEPT (step 41 in Table 9.2.4.1.3.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	‘0001’B	2.56 second
eDRX value	‘0011’B	40.96 seconds

Table 9.2.4.1.3.3.3-7: Message TRACKING AREA UPDATE REQUEST (step 75 in Table 9.2.4.1.3.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