9.3 EMM connection management procedures (S1 mode only)

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.3.1 Service request procedure

9.3.1.1 Service request initiated by UE for user data

9.3.1.1.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED state and EMM-IDLE mode }

ensure that {

when { UE has user data pending }

then { UE establishes the RRC connection with the RRC establishmentCause set to ‘mo-Data’ and sends a SERVICE REQUEST message }

}

9.3.1.1.2 Conformance requirements

The conformance requirements covered in the current TC are specified in: TS 24.301 clauses 5.3.1.1, 5.1.3.2.2.4, 5.3.1.1, 5.6.1.1, 5.6.1.2, 5.6.1.4 and Annex D and TS 36.331 clause 5.3.3.3.

[TS 24.301 clause 5.3.1.1]

When the UE is in EMM-IDLE mode and needs to transmit an initial NAS message, the UE shall request the lower layer to establish a NAS signalling connection. In this request to the lower layer the NAS shall provide to the lower layer the RRC establishment cause and the call type as specified in annex D of this specification.

[TS 24.301 clause 5.1.3.2.2.4]

In the state EMM-REGISTERED an EMM context has been established and a default EPS bearer context has been activated in the UE.

…

The UE may initiate sending and receiving user data and signalling information and reply to paging. Additionally, tracking area updating procedure is performed (see subclause 5.5.3).

[TS 24.301 clause 5.3.1.1]

In S1 mode, when the RRC connection has been established successfully, the UE shall enter EMM-CONNECTED mode and consider the NAS signalling connection established.

[TS 24.301 clause 5.6.1.1]

The purpose of the service request procedure is to transfer the EMM mode from EMM-IDLE to EMM-CONNECTED mode and establish the radio and S1 bearers when uplink user data or signalling is to be sent.

…

The UE shall invoke the service request procedure when:

….

b) the UE, in EMM-IDLE mode, has pending user data to be sent;

[TS 24.301 clause 5.6.1.2]

If the UE has pending uplink data or uplink signalling in EMM-IDLE mode to be transmitted or it responds to paging with CN domain indicator set to "PS", the UE initiates the service request procedure by sending a SERVICE REQUEST message to the MME, starts the timer T3417, and enters the state EMM-SERVICE-REQUEST-INITIATED.

[TS 24.301 clause 5.6.1.4]

For cases a, b and c in subclause 5.6.1.1, the UE shall treat the indication from the lower layers that the user plane radio bearer is set up as successful completion of the procedure.

….

Upon successful completion of the procedure, the UE shall stop the timer T3417 and enter the state EMM-REGISTERED.

[TS 24.301, Annex D]

…

Table D.1.1: Mapping of NAS procedure to establishment cause and call type

NAS procedure	RRC establishment cause (according 3GPP TS 36.331 [22])	Call type
…
Service Request	If a SERVICE REQUEST is to request user plane radio resources, the RRC establishment cause shall be set to MO data. (See Note1)	"originating calls"
Service Request	If a SERVICE REQUEST is to request resources for UL signalling, the RRC establishment cause shall be set to MO data. (See Note 1)	"originating calls"
Note 1: For these NAS procedures initiated by UEs of access class 12, 13 or 14 in their home country, the RRC establishment cause will be set to "High priority access AC 11 – 15". For this purpose the home country is defined as the country of the MCC part of the IMSI, see 3GPP TS 22.011 [1A]. For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN or EHPLMN, the RRC establishment cause will be set to "High priority access AC 11 – 15".

[TS 36.331, clause 5.3.3.3]

…

The UE shall set the contents of RRCConnectionRequest message as follows:

1> set the ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else

3> draw a random value and set the ue-Identity to this value;

NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> Set the establishmentCause in accordance with the information received from upper layers;

9.3.1.1.3 Test description

9.3.1.1.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Loopback Activated (State 4) according to TS 36.508 [18] using the specific message content for ACTIVATE TEST MODE and CLOSE UE TEST LOOP messages in table 9.3.1.1.3.3-1 and table 9.3.1.1.3.3-2.

9.3.1.1.3.2 Test procedure sequence

Table 9.3.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits one IP Packet to the UE.	<–	IP packet	–	–
2	The SS waits 1 second after the IP packet has been transmitted in step 1 and then transmits an RRCConnectionRelease message. (Note 2)	–	–	–	–
3	Check: Does the UE transmit an RRCConnectionRequest message with establishmentCause set to ‘mo-Data’ followed by a SERVICE REQUEST message? (Note 1)	–>	SERVICE REQUEST	1	P
4-7	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.	–	–	–	–
Note 1: Triggered when timer T_delay_modeB (IP PDU delay time) expires and pending uplink data exist in buffered PDCP SDUs according to [25] clause 5.4.4.3. Note 2: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by the SS in step 1 to the UE test loop function before the RRCConnectionRelease message is sent by the SS in step 2.

9.3.1.1.3.3 Specific message contents

Table 9.3.1.1.3.3-1: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE B

Table 9.3.1.1.3.3-2: CLOSE UE TEST LOOP (preamble)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	0 0 0 0 0 1 0 1	5 seconds

Table 9.3.1.1.3.3-3: Message RRCConnectionRequest (step 3, Table 9.3.1.1.3.2-1)

Derivation path: 36.508 table 4.6.1-16
Information Element	Value/Remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mo-Data
}
}
}

9.3.1.2 Void

9.3.1.3 Service request / Mobile originating CS fallback

9.3.1.3.1 Test Purpose (TP)

(1)

with { UE in state EMM-REGISTERED and EMM-CONNECTED mode}

ensure that {
when { UE initiates mobile originating CS fallback }

then { UE sends EXTENDED SERVICE REQUEST message }

}

(2)

with { UE in state EMM-REGISTERED and EMM-IDLE mode}

ensure that {
when { UE initiates mobile originating CS fallback }

then { UE establishes the RRC connection with the RRC establishmentCause set to ‘mo-Data’ and sends EXTENDED SERVICE REQUEST message }

}

9.3.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.3.1.1, 5.6.1.1, 5.6.1.2 and Annex D and TS 36.331 clause 5.3.3.3.[TS 24.301 clause 5.3.1.1]

[TS 24.301 clause5.6.1.1]

The purpose of the service request procedure is to transfer the EMM mode from EMM-IDLE to EMM-CONNECTED mode and establish the radio and S1 bearers when uplink user data or signalling is to be sent. Another purpose of this procedure is to invoke MO/MT CS fallback procedures.

This procedure is used when:

…

– the UE in EMM-IDLE or EMM-CONNECTED mode has requested to perform mobile originating/terminating CS fallback; or

…

The service request procedure is initiated by the UE, however, for the downlink transfer of signalling or user data in EMM-IDLE mode, the trigger is given by the network by means of the paging procedure (see subclause 5.6.2).

The UE shall invoke the service request procedure when:

…

d) the UE, in EMM-IDLE or EMM-CONNECTED mode, has a mobile originating CS fallback request;.

…

[TS 24.301 clause5.6.1.2]

The UE shall send an EXTENDED SERVICE REQUEST message,

– regardless of the EMM mode, if the UE has a mobile originating CS fallback request; and

…

[TS 24.301 clause 5.6.1.5]

#39 (CS domain temporarily not available);

The UE shall start timer T3442 and shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to subclause 5.1.3.3). The UE shall enter the state EMM-REGISTERED.NORMAL-SERVICE.

The UE shall not try to send an EXTENDED SERVICE REQUEST message for mobile originating services to the network until timer T3442 expires or the UE sends a TRACKING AREA UPDATE REQUEST message.

…

[TS 24.301, Annex D]

…

Table D.1.1: Mapping of NAS procedure to establishment cause and call type

NAS procedure	RRC establishment cause (according 3GPP TS 36.331 [22])	Call type
…
Service Request	If a EXTENDED SERVICE REQUEST has service type set to "mobile originating CS fallback", the RRC establishment cause shall be set to MO data. (See Note1).	"originating calls"
…
Note 1: For these NAS procedures initiated by UEs of access class 12, 13 or 14 in their home country, the RRC establishment cause will be set to "High priority access AC 11 – 15". For this purpose the home country is defined as the country of the MCC part of the IMSI, see 3GPP TS 22.011 [1A]. For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN or EHPLMN, the RRC establishment cause will be set to "High priority access AC 11 – 15".

[TS 36.331, clause 5.3.3.3]

…

The UE shall set the contents of RRCConnectionRequest message as follows:

1> set the ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else

3> draw a random value and set the ue-Identity to this value;

NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> Set the establishmentCause in accordance with the information received from upper layers;

9.3.1.3.3 Test description

9.3.1.3.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Generic RB established (state 3) on cell A according to TS 36.508 [18].

9.3.1.3.3.2 Test procedure sequence

Table 9.3.1.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Force the UE to initiate CS Voice call. (Note 1)	–		–	–
2	Check: Does the UE transmit EXTENDED SERVICE REQUEST message?	–>	EXTENDED SERVICE REQUEST	1	P
3	The SS sends SERVICE REJECT message with T3442 = 60 seconds in order that the UE enters EMM-REGISTERED.NORMAL-SERVICE.	<–	SERVICE REJECT	–	–
4	The SS releases the RRC connection	—		–	–
–	EXCEPTION: The behaviour in table 9.3.1.3.3.2-2 may occur in parallel with step 4A.	–	–	–	–
4A	SS waits for 60 seconds (T3442)	–	–	–	–
5	Force the UE to initiate CS Voice call. (Note1)	–		–	–
6	Check: Does the UE transmit an RRCConnectionRequest message with establishmentCause set to ‘mo-Data’ followed by EXTENDED SERVICE REQUEST message?	–>	EXTENDED SERVICE REQUEST	2	P
7	The SS sends SERVICE REJECT message with T3442 = 60 seconds in order that the UE enters EMM-REGISTERED.NORMAL-SERVICE.	<–	SERVICE REJECT	–	–
8	The SS releases the RRC connection	—		–	–
–	EXCEPTION: The behaviour in table 9.3.1.3.3.2-2 may occur in parallel with step 8A.	–	–	–	–
8A	SS waits for 60 seconds (T3442)	–	–	–	–
Note 1: This could be done by e.g. MMI or by AT command.

Table 9.3.1.3.3.2-2: Parallel Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message/PDU/SDU
1	The UE transmits a TRACKING AREA UPDATE REQUEST message.	–>	TRACKING AREA UPDATE REQUEST	–	–
2	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	TRACKING AREA UPDATE ACCEPT	–	–
3	The SS releases the RRC connection.	–	–	–	–

9.3.1.3.3.3 Specific message contents

Table 9.3.1.3.3.3-1: Message EXTENDED SERVICE REQUEST (step 2/6, Table 9.3.1.3.3.2-1)

Derivation Path: 36.508 clause 4.7.2-14A
Information Element	Value/remark	Comment	Condition
Service type	‘0000’B	“mobile originating CS fallback”
M-TMSI	M-TMSI1
CSFB response	Not present

Table 9.3.1.3.3.3-2: Message SERVICE REJECT (step 3 and7, Table 9.3.1.3.3.2-1)

Derivation Path: 36.508 clause 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	‘0010 0111’	“CS domain temporarily not available”
T3442 value	‘0010 0001’B	1 minute

Table 9.3.1.3.3.3-3: Message RRCConnectionRequest (step 6, Table 9.3.1.3.3.2-1)

Derivation path: 36.508 table 4.6.1-16
Information Element	Value/Remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mo-Data
}
}
}

Table 9.3.1.3.3.3-4 Message TRACKING AREA UPDATE ACCEPT (step 2, Table 9.3.1.3.3.2-2)

Derivation path: 36.508 table 4.7.2-24
Information Element	Value/Remark	Comment	Condition
GUTI	Not present
MS identity	Not present

Table 9.3.1.3.3.3-5: ATTACH ACCEPT (Preamble)

Derivation Path: 36.508 Table 4.7.2-1
Information Element	Value/remark	Comment	Condition
EPS network feature support	Not present

9.3.1.4 Service request / Rejected / IMSI invalid

9.3.1.4.1 Test Purpose (TP)

(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘Illegal UE’ }

then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, deletes any GUTI, last visited registered TAI, TAI list and KSI, considers the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed, enters the state EMM-DEREGISTERED }

}

(2)

with { UE having sent a SERVICE REQUEST message }

ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘Illegal UE’ }

then { UE handles the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and the MM parameters update status, TMSI, LAI and ciphering key sequence number }

}

9.3.1.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.6.1.5 and TS 24.008, clause 4.7.13.4.

[TS 24.301, clause 5.6.1.5]

If the service request cannot be accepted, the network shall return a SERVICE REJECT message to the UE including an appropriate EMM cause value. When the EMM cause value is #39 "CS domain temporarily not available", the MME shall include a value for timer T3442 in the SERVICE REJECT message.

On receipt of the SERVICE REJECT message, the UE shall stop timer T3417 and take the following actions depending on the received EMM cause value.

#3 (Illegal UE); or

…

The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed. The UE shall enter the state EMM-DEREGISTERED.

If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and the MM parameters update status, TMSI, LAI and ciphering key sequence number as specified in 3GPP TS 24.008 [13] for the case when the service request procedure is rejected with the GMM cause with the same value. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed.

NOTE 1: The possibility to configure a UE so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the UE, is out of scope of the present specification.

[TS 24.008, clause 4.7.13.4]

If the Service request cannot be accepted, the network returns a SERVICE REJECT message to the mobile station. An MS that receives a SERVICE REJECT message stops timer T3317. The MS shall then take different actions depending on the received reject cause value:

# 3 (Illegal MS); or

…

– The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and enter the state GMM-DEREGISTERED. Furthermore, it shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and shall consider the SIM/USIM as invalid for GPRS services until switching off or the SIM/USIM is removed.

– A GPRS MS operating in MS operation mode A shall in addition set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the SIM/USIM is removed.

If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301 [120] for the case when the service request procedure is rejected with the EMM cause with the same value.

9.3.1.4.3 Test description

9.3.1.4.3.1 Pre-test conditions

System Simulator:

– cell A and cell B;

– If (px_RATComb_Tested = EUTRA_UTRA OR px_RATComb_Tested = EUTRA_GERAN);- if pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA, cell 5 (belongs to LAI-1 and RAI-1, home PLMN) is configured;

– if pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN, cell 24 (belongs to LAI-1 and RAI-1, home PLMN) is configured;

– system information combination 10 as defined in TS 36.508[18] clause 4.4.3.1 is applied in E-UTRA cells;

– cell A is "Serving cell" and cell B, cell 5 and cell 24 are "non-Suitable cell".

– If (px_RATComb_Tested = EUTRA_Only):

– neither cell 5 nor cell 24 is configured;

– system information combination 1 as defined in TS 36.508[18] clause 4.4.3.1 is applied in E-UTRA cells.

UE:

– if pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA, the UE is previously registered on UTRAN cell 5 using default message contents according to TS 36.508 [18].

– if pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN, the UE is previously registered on GERAN cell 24 using default message contents according to TS 36.508 [18].

Preamble:

– the UE is in state Registered, Idle mode (state 2) on cell A according to TS 36.508 [18].

9.3.1.4.3.2 Test procedure sequence

Table 9.3.1.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to "PS".	–	–	–	–
–	The following messages are to be observed on Cell A unless explicitly stated otherwise.	–	–	–	–
2	The UE transmits a SERVICE REQUEST message.	–>	SERVICE REQUEST	–	–
3	The SS transmits a SERVICE REJECT message with the EMM cause set to ‘Illegal UE’.	<–	SERVICE REJECT	–	–
4	The SS releases the RRC connection.	–	–	–	–
5	Set the cell type of Cell A to the "non-Suitable cell". Set the cell type of Cell B to the "Serving cell".	–	–	–	–
–	The following messages are to be observed on Cell B unless explicitly stated otherwise.	–	–	–	–
6	Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds?	–>	ATTACH REQUEST	1	F
–	EXCEPTION: Steps 6Aa1 to 6Ba1 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported	–	–	–	–
6Aa1	IF pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA OR pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN THEN the SS sets the cell type of Cell B to the "non-Suitable cell" and sets the cell type of Cell 5 or Cell 24 to the "Serving cell".	–	–	–	–
–	The following messages are to be observed on Cell 5 or Cell 24 unless explicitly stated otherwise.	–	–	–	–
6Aa2	Void	–	–	–	–
6Aa3	Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds?	–>	ATTACH REQUEST	2	F
6Aa4	If possible (see ICS) switch off is performed or the USIM is removed, otherwise the power is removed.	–	–	–	–
6Aa5	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
–	EXCEPTION: Steps 6Aa5Aa1, 6Aa5Aa2 describe behaviour that depends on the UE capability; the “lower case letter” identifies a step sequence that take place if pc_AutomaticAttachSwitchON is NOT supported		–	–	–
6Aa5Aa1	IF NOT pc_AutomaticAttachSwitchON	–	Registration on CS	–	–
6Aa5Aa2	IF NOT pc_AutomaticAttachSwitchON the user initiates an attach by MMI or by AT command.	–	–	–	–
6Aa6	Check: Does the UE transmit an ATTACH REQUEST message?	–>	ATTACH REQUEST	2	P
6Ba1	If not (pc_UTRA or pc_GERAN) then (if possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed (Note 2)).	–	–	–	–
7-11	Void
11A	Set the cell type of the Cell B to the "non-Suitable cell". Set the cell type of Cell A to the "Serving cell". If px_RATComb_Tested = EUTRA_UTRA set the cell type of Cell 5 to the "Cell Off” or if px_RATComb_Tested = EUTRA_GERAN set Cell 24 to the "Cell Off”.	–	–	–	–
–	The following messages are to be observed on Cell A unless explicitly stated otherwise.	–	–	–	–
	EXCEPTION: Steps 12a1 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported
12	Void	–	–	–	–
12a1	If not (pc_UTRA or pc_GERAN), the UE is brought back to operation or the USIM is inserted.	–	–	–	–
13	Check: Does the UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message?	–>	ATTACH REQUEST	1	P
14-30	Void	–	–	–	–
31a1-31a9	Void	–	–	–	–
32-43	The attach procedure is completed by executing steps 5 to 18a2 of the UE registration procedure in TS 36.508 sub clause 4.5.2.3.	–	–	–	–
–	At the end of this test procedure sequence, the UE is in end state E-UTRA Idle (E1) according to TS 36.508.	–	–	–	–
Note 1: Void. Note 2: Switching off, USIM removal, or power removal shall be done before T3310 and T3311 expire (30 seconds) so that the UE does not retransmit ATTACH REQUEST message.

9.3.1.4.3.3 Specific message contents

Table 9.3.1.4.3.3-1: SERVICE REJECT (step 3, Table 9.3.1.4.3.2-1)

Derivation Path: TS 36.508 Table 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	‘0000 0011’B	Illegal UE

Table 9.3.1.4.3.3-2: ATTACH REQUEST (step 13, Table 9.3.1.4.3.2-1)

Derivation Path: 36.508, Table 4.7.2-4
Information Element	Value/remark	Comment	Condition
NAS key set identifier
NAS key set identifier	‘111’B	no key is available
TSC	Any allowed value	TSC does not apply for NAS key set identifier value "111".
Old GUTI or IMSI	IMSI of the UE
Last visited registered TAI	Not present
Old location area identification	Not present
TMSI status	Not present or any other allowed value

Table 9.3.1.4.3.3-3: ATTACH REQUEST (step 6Aa6, Table 9.3.1.4.3.2-1)

Derivation Path: TS 24.008 , Table 9.4.1
Information Element	Value/remark	Comment	Condition
MS network capability	Any allowed value
Attach type	Any allowed value
GPRS ciphering key sequence number	‘111’B	No key is available (MS to network)
DRX parameter	Any allowed value
P-TMSI or IMSI	IMSI of the UE
Old routing area identification	All bits of octets 5 and 6 are set to 1, except bit 1 of octet 6 which is set to 0. Other bits are not checked.
MS Radio Access capability	Any allowed value
Old P-TMSI signature	Not present
Requested READY timer value	Not present or any allowed value
TMSI status	Not present
	‘0’B	no valid TMSI available	pc_SupportOpMode AND (px_AttachTypeTested = COMBINED_ATTACH)
PS LCS Capability	Not present or any allowed value
Mobile station classmark 2	Not present or any allowed value
Mobile station classmark 3	Not present or any allowed value
Supported Codecs	Not present or any allowed value
UE network capability	Not present or any allowed value
Additional mobile identity	Not present
Additional old routing area identification	Not present

9.3.1.5 Service request / Rejected / Illegal ME

9.3.1.5.1 Test Purpose (TP)

(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘Illegal ME’ }

}

(2)

with { UE supporting A/Gb mode or Iu mode and having sent a SERVICE REQUEST message }

ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘Illegal ME’ }

then { UE sets the GPRS update status to GU3 ROAMING NOT ALLOWED, deletes any P-TMSI, P-TMSI signature, TMSI, LAI, RAI and GPRS ciphering key sequence number and considers the SIM/USIM as invalid for GPRS services until switching off or the SIM/USIM is removed }

}

9.3.1.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.6.1.5 and TS 24.008, clause 4.7.13.4.

[TS 24.301, clause 5.6.1.5]

On receipt of the SERVICE REJECT message, the UE shall stop timer T3417 and take the following actions depending on the received EMM cause value.

…

#6 (Illegal ME);

The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed. The UE shall enter the state EMM-DEREGISTERED.

[TS 24.008, clause 4.7.13.4]

…

# 6 (Illegal ME);

9.3.1.5.3 Test description

The test description is identical to the one of subclause 9.3.1.4 except that the reject cause #3 “Illegal UE” is replaced with reject cause #6 “Illegal ME”.

9.3.1.6 Service request / Rejected / EPS services not allowed

9.3.1.6.1 Test Purpose (TP)

(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘EPS services not allowed’ }

}

(2)

with { UE supporting A/Gb mode or Iu mode and having sent a SERVICE REQUEST message }

ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘EPS services not allowed’ }

then { UE sets the GPRS update status to GU3 ROAMING NOT ALLOWED, deletes any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and considers the SIM/USIM as invalid for GPRS services until switching off or the SIM/USIM is removed }

}

9.3.1.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.6.1.5 and TS 24.008, clause 4.7.13.4.

[TS 24.301, clause 5.6.1.5]

On receipt of the SERVICE REJECT message, the UE shall stop timer T3417 and take the following actions depending on the received EMM cause value.

…

#7 (EPS services not allowed);

The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed. The UE shall enter the state EMM-DEREGISTERED.

A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation is still IMSI attached for non-EPS services. The UE shall set the update status to U2 NOT UPDATED, shall select GERAN or UTRAN radio access technology and proceed with appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-UTRAN radio access technology until switching off or the UICC containing the USIM is removed

…

[TS 24.008, clause 4.7.13.4]

…

# 7 (GPRS services not allowed);

– The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed. The new state is GMM-DEREGISTERED.

9.3.1.6.3 Test description

9.3.1.6.3.1 Pre-test conditions

System Simulator:

– cell A is configured as the "Serving cell";

– If (px_RATComb_Tested = EUTRA_UTRA OR px_RATComb_Tested = EUTRA_GERAN);

– if pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA, cell 5 (belongs to LAI-1 and RAI-1, home PLMN) is configured and set to as a ‘Non-suitable cell’;

– if pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN, cell 24 (belongs to LAI-1 and RAI-1, home PLMN) is configured and set to as a ‘Non-suitable cell’;

– system information combination 10 as defined in TS 36.508[18] clause 4.4.3.1 is applied in E-UTRA cells;

– If (px_RATComb_Tested = EUTRA_Only):

– neither cell 5 nor cell 24 is configured;

– system information combination 1 as defined in TS 36.508[18] clause 4.4.3.1 is applied in E-UTRA cells;

UE:

– if pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA, the UE is previously registered on UTRAN cell 5 using default message contents according to TS 36.508 [18].

– if pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN, the UE is previously registered on GERAN cell 24 using default message contents according to TS 36.508 [18].

Preamble:

– the UE is in state Registered, Idle mode (state 2) on cell A according to TS 36.508 [18].

9.3.1.6.3.2 Test procedure sequence

Table 9.3.1.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to "PS".	–	–	–	–
1A	Void	–	–	–	–
–	The following messages are to be observed on Cell A unless explicitly stated otherwise.	–	–	–	–
2	UE transmits a SERVICE REQUEST message.	–>	SERVICE REQUEST	–	–
3	The SS transmits a SERVICE REJECT message with EMM cause = "EPS services not allowed".	<–	SERVICE REJECT	–	–
4	The SS releases the RRC connection.	–	–	–	–
5	Check: Does the UE transmit a SERVICE REQUEST message in the next 30 seconds?	–>	SERVICE REQUEST	1	F
6	Check: Does the test result of the generic procedure in TS 36.508 subclause 6.4.2.5 indicates that the UE responds to paging when paged with S-TMSI included in GUTI-1 and with CN domain indicator set to "PS"?	–	–	1	–
–	EXCEPTION: Steps 7a1 to 7b8 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported	–	–	–	–
7a1	IF pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA THEN SS configures: – Cell A as ‘Non-suitable cell’ – Cell 5 as ‘Serving cell’	–	–	–	–
–	The following messages are to be observed on Cell 5 unless explicitly stated otherwise.	–	–	–	–
–	EXCEPTION: The behaviour in table 9.3.1.6.3.2-2 occurs in parallel with step 7a2.	–	–	–	–
7a2	Check: Does the UE transmit an ATTACH REQUEST message in the next 90 seconds?	–>	ATTACH REQUEST	2	F
7a3	The user initiates an attach by MMI or by AT command.	–	–	–	–
7a4	Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds?	–>	ATTACH REQUEST	1	F
7a5	If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed.	–	–	–	–
	EXCEPTION: Steps 7a6a1 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported	–	–	–	–
7a6a1	IF pc_CS THEN the UE optionally transmits an IMSI DETACH INDICATION message	–>	IMSI DETACH INDICATION	–	–
7a7	The UE is brought back to operation or the USIM is inserted.	–	–
7a8	Check: Does the UE transmit an ATTACH REQUEST message?	–>	ATTACH REQUEST	2	P
–	EXCEPTION: Steps 21a6a1, 21a6a2 describe behaviour that depends on the UE capability; the “lower case letter” identifies a step sequence that take place if pc_AutomaticAttachSwitchON is NOT supported	–	–	–	–
7a8Aa1	IF NOT pc_AutomaticAttachSwitchON	–	Registration on CS	–	–
7a8Aa2	IF NOT pc_AutomaticAttachSwitchON the user initiates an attach by MMI or by AT command.	–	–	–	–
7b1	IF pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN THEN SS configures: – Cell A as ‘Non-suitable cell’ – Cell 24 as ‘Serving cell’	–	–	–	–
–	The following messages are to be observed on Cell 24 unless explicitly stated otherwise.	–	–	–	–
–	EXCEPTION: The behaviour in table 9.3.1.6.3.2-2 occurs in parallel with step 7b2.	–	–	–	–
7b2	Check: Does the UE transmit an ATTACH REQUEST message in the next 90 seconds?	–>	ATTACH REQUEST	2	F
7b3	The user initiates an attach by MMI or by AT command.	–	–	–	–
7b4	Check: Does the UE transmit an ATTACH REQUEST message in the next 30 seconds?	–>	ATTACH REQUEST	1	F
7b5	If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed.	–	–	–	–
7b6	IF Location Updating procedure has been performed in step 1a1 of behaviour described in table 9.3.1.6.3.2-2 parallel to step 7b2 THEN the UE transmits an IMSI DETACH INDICATION message	–>	IMSI DETACH INDICATION	–	–
7b6A	The UE transmits a Classmark Change message	–>	CLASSMARK CHANGE	–	–
–	EXCEPTION: Step 7b6B describes behaviour that depends on UE capability.	–	–	–	–
7b6B	IF pc_UTRA THEN the UE transmits a Utran Classmark Change message.	–>	UTRAN CLASSMARK CHANGE	–	–
7b7	The UE is brought back to operation or the USIM is inserted.	–	–
7b8	Check: Does the UE transmit an ATTACH REQUEST message?	–>	ATTACH REQUEST	2	P
	EXCEPTION: Steps 8a1 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported
8a1	IF not (pc_UTRA or pc_GERAN) then (if possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed).	–	–	–	–
9	The SS configures: – Cell A as the ‘Serving cell’. – IF pc_UTRA AND px_RATComb_Tested = EUTRA_UTRA THEN Cell 5 ‘Non-suitable cell off ‘. – IF pc_GERAN AND px_RATComb_Tested = EUTRA_GERAN THEN Cell 24 ‘Non-suitable cell off ‘.	–	–	–	–
	EXCEPTION: Steps 10a1 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported
10a1	If not (pc_UTRA or pc_GERAN), the UE is brought back to operation or the USIM is inserted.	–	–	–	–
11	The UE transmits an ATTACH REQUEST message on cell A including a PDN CONNECTIVITY REQUEST message	–>	ATTACH REQUEST	–	–
12-25b1	The attach procedure is completed by executing steps 5-18b1 of the generic procedure for UE initial registration specified in TS 36.508 subclause 4.5.2.3.	–	–	–	–
–	At the end of this test procedure sequence, the UE is in end state E-UTRA idle (E1) according to TS 36.508.	–	–	–	–
Note 1: Void.

Table 9.3.1.6.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	EXCEPTION: Steps 1a1 and 1a4 describe a behaviour which depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported.	–	–	–	–
1a1	IF pc_CS THEN the UE optionally transmits a LOCATION UPDATING REQUEST message.	–>	LOCATION UPDATING REQUEST	–	–
–	EXCEPTION: The messages in the next two steps are sent only on Cell 24	–	–	–	–
1a1Aa1	The UE transmits a Classmark Change message	–>	CLASSMARK CHANGE	–	–
–	EXCEPTION: The next step describes behaviour that depends on UE capability.	–	–	–	–
1a1Aa2	IF pc_UTRA THEN the UE transmits a Utran Classmark Change message.	–>	UTRAN CLASSMARK CHANGE.	–	–
1a2	The SS transmits an AUTHENTICATION REQUEST message to initiate the authentication and AKA procedure.	<–	AUTHENTICATION REQUEST	–	–
1a3	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
1a4	The SS transmits a LOCATION UPDATING ACCEPT message including IMSI-1	<–	LOCATION UPDATING ACCEPT	–	–

9.3.1.6.3.3 Specific message contents

Table 9.3.1.6.3.3-1: SERVICE REJECT (step 3, Table 9.3.1.6.3.2-1)

Derivation Path: TS 36.508 Table 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	‘0000 0111’B	EPS services not allowed

Table 9.3.1.6.3.3-2: Message ATTACH REQUEST (step 11, Table 9.3.1.6.3.2-1)

Derivation path: TS 36.508 table 4.7.2-4
Information Element	Value/Remark	Comment	Condition
NAS key set identifier	‘111’B	no key is available
Old GUTI or IMSI	IMSI1
Last visited registered TAI	Not present

Table 9.3.1.6.3.3-3: Message ATTACH REQUEST (step 7a8 and 7b8, Table 9.3.1.6.3.2-1)

Derivation path: TS 24.008 table 9.4.1
Information Element	Value/Remark	Comment	Condition
GPRS ciphering key sequence number	‘111’B	no key is available
P-TMSI or IMSI	IMSI1
Old routing area identification	all bits of the location area code shall be set to one with the exception of the least significant bit which shall be set to zero	RAI is deleted
Old P-TMSI signature	Not present
TMSI status	Not present or 0

Table 9.3.1.6.3.3-4: Void

Table 9.3.1.6.3.3-5: Void

Table 9.3.1.6.3.3-6: LOCATION UPDATING ACCEPT (step 1a2, Table 9.3.1.6.3.2-2)

Derivation Path: TS 36.508 Table 4.7B.2-5
Information Element	Value/remark	Comment	Condition
Mobile identity
IMSI	IMSI-1

9.3.1.7 Service request / Rejected / UE identity cannot be derived by the network

9.3.1.7.1 Test Purpose (TP)

(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {

when { UE receives a SERVICE REJECT message with the EMM cause value = 9 (UE identity cannot be derived by the network) }

then { UE sets the EPS update status to EU2 NOT UPDATED and deletes any GUTI, last visited registered TAI, TAI list and KSI and automatically initiate the attach procedure }

}

9.3.1.7.2 Conformance requirements

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

[TS 24.301, clause 5.6.1.5]

On receipt of the SERVICE REJECT message, the UE shall stop timer T3417 and take the following actions depending on the received EMM cause value.

…

#9 (UE identity cannot be derived by the network);

The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and KSI. The UE shall enter the state EMM-DEREGISTERED.

Subsequently, the UE shall automatically initiate the attach procedure.

NOTE 3: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically.

9.3.1.7.3 Test description

9.3.1.7.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Registered, Idle mode (state 2) on cell A according to TS 36.508 [18].

9.3.1.7.3.2 Test procedure sequence

Table 9.3.1.7.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to "PS".	–	–	–	–
2	The UE transmits a SERVICE REQUEST message.	–>	SERVICE REQUEST	–	–
3	The SS transmits a SERVICE REJECT message with the EMM cause set to #9 (UE identity cannot be derived by the network).	<–	SERVICE REJECT	–	–
–	EXCEPTION: Steps 3a1-3a2 describes the behaviour that depends on UE behaviour (Note 1).	–	–	–	–
3a1	The SS releases the RRC connection.	–	–	–	–
–	EXCEPTION: Step 3a2 describes a behaviour which depends on the UE capability	–	–	–	–
3a2	IF NOT pc_Automatic_EPS_Re_Attach, the user initiates an attach by MMI or by AT command.	–	–	–	–
4	Check: Does the UE transmit an ATTACH REQUEST message including IMSI and without integrity protection?	–>	ATTACH REQUEST	1	P
5-18b1	The attach procedure is completed by executing steps 5 to 18b1 of the UE registration procedure in TS 36.508 sub clause 4.5.2.3.	–	–	–	–
–	At the end of this test procedure sequence, the UE is in end state E-UTRA idle (E1) according to TS 36.508.	–	–	–	–
Note 1: SS waits for 1.5 second to receive the Attach Request on the existing RRC Connection. In case Attach Request is not received within 1.5 second, existing RRC Connection is released.

9.3.1.7.3.3 Specific message contents

Table 9.3.1.7.3.3-1: SERVICE REJECT (step 3, Table 9.3.1.7.3.2-1)

Derivation Path: TS 36.508 Table 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	‘0000 1001’B	UE identity cannot be derived by the network

Table 9.3.1.7.3.3-2: ATTACH REQUEST (step 4, Table 9.3.1.7.3.2-1)

Derivation Path: 36.508, Table 4.7.2-4
Information Element	Value/remark	Comment	Condition
NAS key set identifier	‘111’B	no key is available
Old GUTI or IMSI	IMSI
Last visited registered TAI	Not present

9.3.1.7a Service request / Rejected / UE implicitly detached

9.3.1.7a.1 Test Purpose (TP)

(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {
when { UE receives a SERVICE REJECT message with the EMM cause set to ‘Implicitly detached’ }

then { UE enters the state EMM-DEREGISTERED.NORMAL-SERVICE, delete the EPS mapped EPS security context if any and performs a new attach procedure }

}

9.3.1.7a.2 Conformance requirements

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

[TS 24.301, clause 5.6.1.5]

If the service request cannot be accepted, the network shall return a SERVICE REJECT message to the UE including an appropriate EMM cause value.

…

On receipt of the SERVICE REJECT message, the UE shall stop timer T3417 and take the following actions depending on the received EMM cause value.

…

#10 (Implicitly detached);

The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete any mapped EPS security context or partial native EPS security context. The UE shall perform a new attach procedure.

NOTE 4: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically.

9.3.1.7a.3 Test description

9.3.1.7a.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Registered, Idle mode (state 2) on cell A according to TS 36.508 [18].

9.3.1.7a.3.2 Test procedure sequence

Table 9.3.1.7a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to "PS".	–	–	–	–
2	The UE transmits a SERVICE REQUEST message.	–>	SERVICE REQUEST	–	–
3	The SS transmits a SERVICE REJECT message with the EMM cause set to ‘Implicitly detached’.	<–	SERVICE REJECT	–	–
–	EXCEPTION: Steps 3a1 & 3a2 describes the behaviour that depends on UE behaviour (Note 1).	–	–	–	–
3a1	The SS releases the RRC connection.	–	–	–	–
–	EXCEPTION: Step 3a2 describes a behaviour which depends on the UE capability	–	–	–	–
3a2	IF NOT pc_Automatic_EPS_Re_Attach, the user initiates an attach by MMI or by AT command.	–	–	–	–
4	Check: Does the UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message and integrity protected using the native security context resulting from authentication during the test preamble?	–>	ATTACH REQUEST	1	P
5-18b1	The attach procedure is completed by executing steps 5 to 18b1 of the UE registration procedure in TS 36.508 sub clause 4.5.2.3.	–	–	–	–
–	At the end of this test procedure sequence, the UE is in end state E-UTRA idle (E1) according to TS 36.508.	–	–	–	–
Note 1: SS waits for 1.5 second to receive the Attach Request on the existing RRC Connection. In case Attach Request is not received within 1.5 second, existing RRC Connection is released.

9.3.1.7a.3.3 Specific message contents

Table 9.3.1.7a.3.3-1: SERVICE REJECT (step 3, Table 9.3.1.7a.3.2-1)

Derivation Path: TS 36.508 Table 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	‘0000 1010’B	Implicitly detached

Table 9.3.1.7a.3.3-2: ATTACH REQUEST (step 4, Table 9.3.1.7a.3.2-1)

Derivation Path: 36.508, Table 4.7.2-4
Information Element	Value/remark	Comment	Condition
NAS key set identifier
NAS key set identifier	NAS key set identifier allocated to UE during authentication in test preamble
TSC	‘0’B	Native security context
Old GUTI or IMSI	GUTI allocated to UE during previous attach on Cell A.
Last visited registered TAI	TAI-1

9.3.1.8 Void

9.3.1.9 Void

9.3.1.10 Void

9.3.1.11 Void

9.3.1.12 Void

9.3.1.12a Extended service request / Rejected / CS domain temporarily not available

9.3.1.12a.1 Test Purpose (TP)

(1)

with { UE has received a SERVICE REJECT message with the EMM cause set to ‘CS domain temporarily not available’ and T3442 expired }

ensure that {
when { UE is requested to initiate a CS call }

then { UE transmit EXTENDED SERVICE REQUEST message }

}

9.3.1.12a.2 Conformance requirements

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

[TS 24.301, clause 5.6.1.5]

On receipt of the SERVICE REJECT message, the UE shall stop timer T3417 and take the following actions depending on the received EMM cause value.

…

#39 (CS domain temporarily not available);

The UE shall start timer T3442 and enter the state EMM-REGISTERED.NORMAL-SERVICE.

The UE shall not try to send an EXTENDED SERVICE REQUEST message for mobile originating services to the network, except for mobile originating CS fallback for emergency calls, until timer T3442 expires or the UE sends a TRACKING AREA UPDATE REQUEST message.

9.3.1.12a.3 Test description

9.3.1.12a.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Registered, Idle Mode (state 2) according to TS 36.508 [18].

9.3.1.12a.3.2 Test procedure sequence

Table 9.3.1.12a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to "CS".	–	–	–	–
2	The UE transmits an EXTENDED SERVICE REQUEST message.	–>	EXTENDED SERVICE REQUEST	–	–
3	The SS transmits a SERVICE REJECT message with the EMM cause set to ‘CS domain temporarily not available’ and T3442 = 60 seconds.	<–	SERVICE REJECT	–	–
4	The SS releases the RRC connection.	–	–	–	–
–	EXCEPTION: The behaviour in table 9.3.1.12a.3.2-2 may occur in parallel with step 4A.	–	–	–	–
4A	SS waits for 60 seconds (T3442)	–	–	–	–
5	Cause the UE to originate CS call. (Note 1)	–	–	–	–
6	Check: Does the UE transmit an EXTENDED SERVICE REQUEST message?	–>	EXTENDED SERVICE REQUEST	1	P
6A	The SS sends SERVICE REJECT message with the EMM cause set to ‘CS domain temporarily not available’ and T3442 = 60 seconds.	<–	SERVICE REJECT	–	–
6B	The SS releases the RRC Connection,	–	–	–	–
–	EXCEPTION: The behaviour in table 9.3.1.12a.3.2-2 may occur in parallel with step 6C.	–	–	–	–
6C	The SS waits for 60 seconds (T3442)	–	–	–	–
7	If possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed. (Note 2)	–	–	–	–
Note 1: The trigger in step 5 is the same as in the generic procedure in 36.508 clause 6.4.3.5. Note 2: The UE is powered off, switched off, or the USIM is removed because the UE may retry a transmission of an EXTENDED SERVICE REQUEST message depending on the UE implementation after timer T3442 expires. Additionally, it is not clear which postamble procedure is performed, since the UE may search the UTRAN/GERAN cell after step 3.

Table 9.3.1.12a.3.2-2: Parallel Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message/PDU/SDU
1	The UE transmits a TRACKING AREA UPDATE REQUEST message.	–>	TRACKING AREA UPDATE REQUEST	–	–
2	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	TRACKING AREA UPDATE ACCEPT	–	–
3	The SS releases the RRC connection.	–	–	–	–

9.3.1.12a.3.3 Specific message contents

Table 9.3.1.12a.3.3-1: Message SERVICE REJECT (step 3 and 6A, Table 9.3.1.12a.3.2-1)

Derivation Path: TS 36.508, Table 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	‘0010 0111’B	CS domain temporarily not available
T3442 value
Timer value	‘0 0001’B	1 minute
Unit	‘001’B	value is incremented in multiples of 1 minute

Table 9.3.1.12a.3.3-2: Message TRACKING AREA UPDATE ACCEPT (step 2, Table 9.3.1.12a.3.2-2)

Derivation path: 36.508 table 4.7.2-24
Information Element	Value/Remark	Comment	Condition
GUTI	Not present
MS Identity	Not Present

Table 9.3.1.12a.3.3-3: ATTACH ACCEPT (Preamble)

Derivation Path: 36.508 Table 4.7.2-1
Information Element	Value/remark	Comment	Condition
EPS network feature support	Not present

9.3.1.13 Void

9.3.1.14 Void

9.3.1.15 Void

9.3.1.16 Service request / Abnormal case / Switch off

9.3.1.16.1 Test Purpose (TP)

(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {
when { UE is to be switched off }

then { UE performs the detach procedure within 5 sec. }

}

9.3.1.16.2 Conformance requirements

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

[TS 24.301, clause 5.6.1.6]

The following abnormal cases can be identified:

…

g) Switch off

If the UE is in state EMM-SERVICE-REQUEST-INITIATED at switch off, the detach procedure shall be performed.

[TS 24.301, clause 5.5.2.2.1]

If the UE is to be switched off, the UE shall try for a period of 5 seconds to send the DETACH REQUEST message. During this period, the UE may be switched off as soon as the DETACH REQUEST message has been sent.

9.3.1.16.3 Test description

9.3.1.16.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Registered, Idle mode (state 2) according to TS 36.508 [18].

9.3.1.16.3.2 Test procedure sequence

Table 9.3.1.16.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to "PS".	–	–	–	–
2	The UE transmits a SERVICE REQUEST message and starts timer T3417.	–>	SERVICE REQUEST	–	–
3	The SS does not respond to the SERVICE REQUEST message. NOTE: The SS does not transmit both SecurityModeCommand message and RRCConnectionReconfiguration message.	–	–	–	–
4	The UE is switched off.	–	–	–	–
5	Check: Does the UE transmit a DETACH REQUEST message in the next 5 sec.? (Note 1)	–>	DETACH REQUEST	1	P
6	Check: Does the test result of the generic procedure in TS 36.508 subclause 6.4.2.5 indicates that the UE responds to paging when paged with S-TMSI included in GUTI-1 and with CN domain indicator set to "PS"?	–	–	1	–
Note 1: Even though the UE may have successfully performed an IMS registration during the preamble, an IMS deregistration attempt of the UE before sending DETACH REQUEST is not allowed in step 5 as there is no AS security in the test case body.

9.3.1.16.3.3 Specific message contents

None.

9.3.1.17 Service request / Abnormal case / Procedure collision

9.3.1.17.1 Test Purpose (TP)

(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {
when { UE receives a DETACH REQUEST message with the Type of detach set to ‘re-attach required’ }

then { UE sends a DETACH ACCEPT message and performs the attach procedure }

}

(2)

with { UE having sent a SERVICE REQUEST message or an EXTENDED SERVICE REQUEST message}

ensure that {
when { UE receives a DETACH REQUEST message with the Type of detach set to the value other than ‘re-attach required’ }

then { UE sends a DETACH ACCEPT message }

}

9.3.1.17.2 Conformance requirements

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

[TS 24.301, clause 5.6.1.6]

The following abnormal cases can be identified:

…

h) Procedure collision

If the UE receives a DETACH REQUEST message with detach type "re-attach required" or "re-attach not required" with EMM cause other than #2 "IMSI unknown in HSS" from the network in state EMM-SERVICE-REQUEST-INITIATED, the detach procedure shall be progressed and the service request procedure shall be aborted.

Additionally, if the service request was initiated for CS fallback or 1xCS fallback, the EMM sublayer shall indicate to the MM sublayer or the cdma2000^® upper layers that the CS fallback or 1xCS fallback procedure has failed.

If the Detach type IE in the DETACH REQUEST message indicated "re-attach required", the attach procedure shall be performed.

9.3.1.17.3 Test description

9.3.1.17.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Registered, Idle mode (state 2) according to TS 36.508 [18].

9.3.1.17.3.2 Test procedure sequence

Table 9.3.1.17.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to "PS".	–	–	–	–
2	The UE transmits a SERVICE REQUEST message.	–>	SERVICE REQUEST	–	–
3	The SS transmits a DETACH REQUEST message with the Type of detach set to ‘re-attach required’.	<–	DETACH REQUEST	–	–
4	Check: Does the UE transmit a DETACH ACCEPT message?	–>	DETACH ACCEPT	1	P
5	Void	–	–	–	–
–	EXCEPTION: Steps 5a-5b describes a behaviour that depends on UE behaviour (Note 1).	–	–	–	–
5a	The SS releases the RRC connection.	–	–	–	–
–	EXCEPTION: Step 5b describes a behaviour which depends on the UE capability	–	–	–	–
5b	IF NOT pc_Automatic_Re_Attach, the user initiates an attach by MMI or by AT command.	–	–	–	–
6	Check: Does the UE transmit an ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message?	–>	ATTACH REQUEST	1	P
7-14	Void	–	–
14A1-14A14 b1	The attach procedure is completed by executing steps 5 to 18b1 of the UE registration procedure in TS 36.508 sub clause 4.5.2.3.
–	EXCEPTION: Steps 15a1 to 15b2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that take place if a capability is supported	–	–	–	–
15a1	IF (px_AttachTypeTested == COMBINED_ATTACH) and (pc_CS_Fallback is true) THEN the SS pages the UE using S-TMSI with CN domain indicator set to "CS".	–	–	–	–
15a2	The UE transmits an EXTENDED SERVICE REQUEST message.	–>	EXTENDED SERVICE REQUEST	–	–
15b1	ELSE the SS pages the UE using S-TMSI with CN domain indicator set to "PS".	–	–	–	–
15b2	The UE transmits a SERVICE REQUEST message.	–>	SERVICE REQUEST	–	–
16	The SS transmits a DETACH REQUEST message with the Type of detach set to the value other than ‘re-attach required’.	<–	DETACH REQUEST	–	–
17	Check: Does the UE transmit a DETACH ACCEPT message?	–>	DETACH ACCEPT	2	P
18	The SS releases the RRC connection.	–	–	–	–
–	At the end of this test procedure sequence, the UE is in end state E-UTRA deregistered (E4) according to TS 36.508.	–	–	–	–
Note 1: SS waits for 1.5 second to receive the Attach Request on the existing RRC Connection. In case Attach Request is not received within 1.5 second, existing RRC Connection is released.

9.3.1.17.3.3 Specific message contents

Table 9.3.1.17.3.3-1: Message DETACH REQUEST (step 3, Table 9.3.1.17.3.2-1)

Derivation Path: TS 36.508 Table 4.7.2-12
Information Element	Value/remark	Comment	Condition
Detach type
Type of detach	‘001’B	re-attach required
EMM cause	Not present	If the detach type IE indicates "IMSI detach" or "re-attach required", then the UE shall ignore the EMM cause IE if received.

Table 9.3.1.17.3.3-2: Message DETACH REQUEST (step 16, Table 9.3.1.17.3.2-1)

Derivation Path: TS 36.508 Table 4.7.2-12
Information Element	Value/remark	Comment	Condition
Detach type
Type of detach	‘010’B	re-attach not required
EMM cause	‘0000 0011’B	Illegal UE

9.3.1.18 Service request / Rejected / Not authorized for this CSG

9.3.1.18.1 Test Purpose (TP)

(1)

with { UE having sent a SERVICE REQUEST message }

ensure that {

when { UE receives a SERVICE REJECT message with the EMM cause value = 25 (Not authorized for this CSG) and this SERVICE REJECT message is not without integrity protection }

then { UE sets the EPS update status to EU3 ROAMING NOT ALLOWED, removes the CSG ID of the cell that sent SERVICE REJECT message from the Allowed CSG list, searches for a suitable cell in the same PLMN }

}

(2)

with { UE in state EMM-REGISTERED and EMM-IDLE mode and the CSG ID is removed from the Allowed CSG list }

ensure that {
when { UE detects entering new tracking areas not included in the TAI list }

then { UE attempts to enter a normal cell and does not select a cell which is not included in the allowed CSG list }

}

9.3.1.18.2 Conformance requirements

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

[TS 24.301, clause 5.6.1.5]

On receipt of the SERVICE REJECT message, the UE shall stop timer T3417 and take the following actions depending on the received EMM cause value.

…

#25 (Not authorized for this CSG);

Cause #25 is only applicable when received from a CSG cell. Cause #25 received from a non-CSG cell is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.6.

If the SERVICE REJECT message with cause #25 was received without integrity protection, then the UE shall discard the message.

The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3). The UE shall enter the state EMM-REGISTERED.LIMITED-SERVICE.

The UE shall remove the CSG ID of the cell where the UE has initiated the service request procedure from the Allowed CSG list.

The UE shall search for a suitable cell in the same PLMN according to 3GPP TS 36.304 [21].

9.3.1.18.3 Test description

9.3.1.18.3.1 Pre-test conditions

System Simulator:

– cell A(TAC1, frequency 1, is a CSG cell);

– cell B(TAC2, frequency 1, not a CSG cell);

– cell A is "Serving cell" and cell B " Non-suitable cell".

– System information combination 3 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cell B.

– System information combination 7 as defined in TS 36.508[18] clause 4.4.3.1 is used in cell A;

UE:

– the UE is previously registered on cell A using either manual CSG selection or a USIM with field EFACSGL preconfigured (so the allowed CSG list includes CSG ID of cell A).

Preamble:

– The UE is in state Registered, Idle mode (state 2) on cell A according to [18].

9.3.1.18.3.2 Test procedure sequence

Table 9.3.1.18.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to "PS".	–	–	–	–
–	The following messages are sent and shall be received on Cell A.	–	–	–	–
2	The UE transmits a SERVICE REQUEST message.	–>	SERVICE REQUEST	–	–
3	The SS transmits a SERVICE REJECT message with the EMM cause = " Not authorized for this CSG " as specified.	<–	SERVICE REJECT	–	–
4	The SS releases the RRC connection.	–	–	–	–
5	The SS configures: – Cell A as a "Serving cell". – Cell B as a "Suitable Neighbour intra-frequency cell“.	–	–	–	–
6	Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message on cell B?	–>	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	–	–
8A	The SS releases the RRC connection.	–	–	–	–
9	The SS configures: – Cell A as a " Serving cell". – Cell B as a " Not Suitable cell".	–	–	–	–
10	Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message on cell A in the next 30 seconds?	–>	TRACKING AREA UPDATE REQUEST	2	F

9.3.1.18.3.3 Specific message contents

Table 9.3.1.18.3.3-1: SERVICE REJECT (step 3, Table 9.3.1.18.3.2-1)

Derivation Path: TS 36.508 Table 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	‘00011001’B	#25 "Not authorized for this CSG"

Table 9.3.1.18.3.3-2: SystemInformationBlockType1 for Cell A, B(Pre-test conditions and all steps in Table 9.3.1.18.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
cellAccessRelatedInfo SEQUENCE {
csg-Indication	TRUE		Cell A
	FALSE		Cell B
csg-Identity	Not present		Cell B
	‘000 0000 0000 0000 0000 0000 0010’B		Cell A

9.3.2 Paging procedure

9.3.2.1 Paging procedure

9.3.2.1.1 Test Purpose (TP)

(1)

with { UE in ECM-IDLE }

ensure that {
when { the network initiates a paging procedure for EPS services using S-TMSI }

then { the UE responds to the paging by establishing an RRC connection and transmitting a SERVICE REQUEST message providing correct S-TMSI in the RRCConnectionRequest }

}

(2)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE receives a Paging message including an ue-Identity set an unmatched S-TMSI i.e. other than the one allocated to the UE at the UE registration procedure }

then { UE does not establish an RRC connection }

}

9.3.2.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clauses 5.6.1.1, 5.6.2.2.1, TS 33.401 clause 7.2.6.2, TS 36.331 clauses 5.3.2.3, 5.3.3.2, 5.3.3.3 and 5.3.3.4. Unless otherwise stated these are Rel-8 requirements.

[TS 24.301, clause 5.6.2.2.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 starts the timer T3413 for this paging procedure. Upon reception of a paging indication, the UE shall respond to the paging with a SERVICE REQUEST message (see 3GPP TS 23.401 [10] and 3GPP TS 36.413 [23]). If the paging for EPS services was received during an ongoing UE initiated EMM specific procedure or service request procedure, then the UE shall ignore the paging and the UE and the network shall proceed with the EMM specific procedure or the service request procedure.

[TS 24.301, clause 5.6.1.1]

The UE shall invoke the service request procedure when:

a) the UE in EMM-IDLE mode receives a paging request with CN domain indicator set to "PS" from the network;

[TS 33.401 clause 7.2.6.2]

The procedure the UE uses to transit from ECM-IDLE to ECM-CONNECTED when in EMM-REGISTERED state is initiated by a NAS Service Request message from the UE to the MME. As the UE is in EMM-REGISTERED state, a EPS security context exists in the UE and the MME, and this EPS security context further contains uplink and downlink NAS COUNTs. The NAS Service Request message sent in EMM-REGISTERED shall be integrity protected and contain the uplink NAS sequence number.

[TS 36.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity, and the cn-Domain to the upper layers.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

…

1>if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInfoBlockType2;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up to date system information applicable only for UEs in RRC_IDLE state. However, the UE needs to perform system information acquisition upon cell re-selection.

[TS 36.331, clause 5.3.3.3]

The UE shall set the contents of RRCConnectionRequest message as follows:

1> set the ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else:

3> draw a random value in the range 0 .. 2⁴⁰-1 and set the ue-Identity to this value;

NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCConnectionRequest message to lower layers for transmission.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.5.

[TS 36.331, clause 5.3.3.4]

NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

1> stop timer T300;

1> stop timer T302, if running;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> enter RRC_CONNECTED;

1> stop the cell re-selection procedure;

1> set the content of RRCConnectionSetupComplete message as follows:

2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]) from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;

2> if upper layers provide the ‘Registered MME’, include and set the registeredMME as follows:

3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers:

4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the ‘Registered MME’ received from upper layers;

3> set the mmegi and the mmec to the value received from upper layers;

2> set the dedicatedInfoNAS to include the information received from upper layers;

2> submit the RRCConnectionSetupComplete message to lower layers for transmission, upon which the procedure ends.

9.3.2.1.3 Test description

9.3.2.1.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

– none.

Preamble:

– the UE is in Registered, Idle Mode (state 2) according to TS 36.508 [18].

9.3.2.1.3.2 Test procedure sequence

Table 9.3.2.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS transmits a Paging message including an unmatched identity (incorrect S-TMSI).	<–	Paging	–	–
0A	Check: Does the UE transmit an RRCConnectionRequest message within 5 s?	–>	RRCConnectionRequest	2	F
1	SS pages the UE using S-TMSI with CN domain indicator set to "PS"	–	–	–	–
2	Check: Does the UE transmit RRCConnectionRequest message providing correct S-TMSI?	–>	RRCConnectionRequest	1	P
2A	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
2B	Check: Does the UE transmit an RRCConnectionSetupComplete message including SERVICE REQUEST to confirm the successful completion of the connection establishment?	–>	RRCConnectionSetupComplete	1	P
3	Check: Does the UE respond with a SERVICE REQUEST message?	–>	SERVICE REQUEST	1	P
4-7	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.	–	–	–	–

9.3.2.1.3.3 Specific message contents

Table 9.3.2.1.3.3-1: RRCConnectionRequest (step 2, Table 9.3.2.1.3.2-1)

Derivation Path: Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
ue-Identity[1] CHOICE {
s-TMSI	Set to the value of the S-TMSI of the UE
}
}
}
}

Table 9.3.2.1.3.3-2: Paging (step 1, Table 9.3.2.1.3.2-1)

Derivation Path: 36.508 Table 4.6.1-7
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList SEQUENCE (SIZE (1..maxPageRec)) OF SEQUENCE {	1 entry
ue-Identity[1] CHOICE {
s-TMSI SEQUENCE {
mmec	Set to the different value from the S-TMSI of the UE
m-TMSI	Set to the different value from the S-TMSI of the UE
}
}
}
}

9.3.2.2 Paging for CS fallback / Idle mode

9.3.2.2.1 Test Purpose (TP)

(1)

with { UE in state EMM-REGISTERED and EMM-IDLE mode}

ensure that {
when { UE received Paging for mobile termination CS fallback from NW }

then { UE establishes the RRC connection with the RRC establishmentCause set to ‘mt-Access’ and sends EXTENDED SERVICE REQUEST message }

}

9.3.2.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.3.1.1, 5.6.1.1, 5.6.2.3 and Annex D and TS 36.331 clause 5.3.3.3.

[TS 24.301 clause 5.3.1.1]

[TS 24.301 clause5.6.1.1]

This procedure is used when:

…

– the UE in EMM-IDLE or EMM-CONNECTED mode has requested to perform mobile originating/terminating CS fallback; or

…

The UE shall invoke the service request procedure when:

…

e) the UE, in EMM-IDLE or EMM-CONNECTED mode, has a CS fallback response to be sent to the network; or

…

[TS 24.301 clause5.6.2.3]

The network may initiate the paging procedure for non-EPS services when the UE is IMSI attached for non-EPS services.

To initiate the procedure when no NAS signalling connection exists, the EMM entity in the network requests the lower layer to start paging (see 3GPP TS 36.300 [2012], 3GPP TS 36.413 [2315]) and starts the timer T3413 for this paging procedure. The paging message includes a CN domain indicator set to ”CS” in order to indicate that this is paging for CS fallback. Upon reception of a paging indication, the UE may respond to the paging immediately or may request upper layers input i.e. to accept or reject CS fallback. The response is indicated in the CSFB response information element in the EXTENDED SERVICE REQUEST message in both EMM-IDLE and EMM-CONNECTED modes.

The network shall stop the timer T3413 for the paging procedure when a response is received from the UE.

To notify the UE about an incoming mobile terminating CS service when a NAS signalling connection exists, the EMM entity in the network shall send a CS SERVICE NOTIFICATION message.

[TS 24.301, Annex D]

…

Table D.1.1: Mapping of NAS procedure to establishment cause and call type

NAS procedure	RRC establishment cause (according 3GPP TS 36.331 [22])	Call type
…
Service Request	If a EXTENDED SERVICE REQUEST has service type set to "mobile terminating CS fallback", the RRC establishment cause shall be set to MT access. (See Note1).	"terminating calls"
…
Note 1: For these NAS procedures initiated by UEs of access class 12, 13 or 14 in their home country, the RRC establishment cause will be set to "High priority access AC 11 – 15". For this purpose the home country is defined as the country of the MCC part of the IMSI, see 3GPP TS 22.011 [1A]. For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN or EHPLMN, the RRC establishment cause will be set to "High priority access AC 11 – 15".

[TS 36.331, clause 5.3.3.3]

…

The UE shall set the contents of RRCConnectionRequest message as follows:

1> set the ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else

3> draw a random value and set the ue-Identity to this value;

NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> Set the establishmentCause in accordance with the information received from upper layers;

9.3.2.2.3 Test description

9.3.2.2.3.1 Pre-test conditions

System Simulator:

– cell A.

UE:

none.

Preamble:

– the UE is in state Registered, Idle Mode (state 2) on cell A according to TS 36.508 [18].

9.3.2.2.3.2 Test procedure sequence

Table 9.3.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS sends a paging message which CN domain indicates ”CS” domain to the UE.	–	–	–	–
2	The UE accepts CS fallback	–	–	–	–
3	Check: Does the UE transmit an RRCConnectionRequest message with establishmentCause set to ‘mt-Access’ followed by EXTENDED SERVICE REQUEST message?	–>	EXTENDED SERVICE REQUEST	1	P
4	The SS sends SERVICE REJECT message with T3442 = 60 seconds in order that the UE enters EMM-REGISTERED.NORMAL-SERVICE.	<–	SERVICE REJECT	–	–
5	The SS releases the RRC connection.	–	–	–	–
–	EXCEPTION: The behaviour in table 9.3.2.2.3.2-2 may occur in parallel with step 6.	–	–	–	–
6	SS waits for 60 seconds (T3442)	–	–	–	–

Table 9.3.2.2.3.2-2: Parallel Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message/PDU/SDU
1	The UE transmits a TRACKING AREA UPDATE REQUEST message.	–>	TRACKING AREA UPDATE REQUEST	–	–
2	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	TRACKING AREA UPDATE ACCEPT	–	–
3	The SS releases the RRC connection.	–	–	–	–

9.3.2.2.3.3 Specific message contents

Table 9.3.2.2.3.3-0: Message RRCConnectionRequest (step 3, Table 9.3.2.2.3.2-1)

Derivation path: 36.508 table 4.6.1-16
Information Element	Value/Remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mt-Access
}
}
}

Table 9.3.2.2.3.3-1: Message EXTENDED SERVICE REQUEST (step 3, Table 9.3.2.2.3.2-1)

Derivation Path: 36.508 clause 4.7.2-14A
Information Element	Value/remark	Comment	Condition
M-TMSI	M-TMSI1

Table 9.3.2.2.3.3-2: Message SERVICE REJECT (step 4, Table 9.3.2.2.3.2-1)

Derivation Path: 36.508 clause 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	’0010 0111’B	CS domain temporarily not available
T3442 value	‘0010 0001’B	1 minute

Table 9.3.2.2.3.3-3: Message TRACKING AREA UPDATE ACCEPT (step 2, Table 9.3.2.2.3.2-2)

Derivation path: 36.508 table 4.7.2-24
Information Element	Value/Remark	Comment	Condition
GUTI	Not present
MS identity	Not present

9.3.2.2a Paging for CS fallback / Connected mode

9.3.2.2a.1 Test Purpose (TP)

(1)

with { UE in state EMM-REGISTERED and EMM-CONNECTED mode}

ensure that {
when { UE receives a CS SERVICE NOTIFICATION message for mobile termination CS fallback from NW }

then { UE sends EXTENDED SERVICE REQUEST message }

}

9.3.2.2a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.3.1.1, 5.6.1.1, 5.6.2.3 and Annex D and TS 36.331 clause 5.3.3.3.

[TS 24.301 clause 5.3.1.1]

[TS 24.301 clause5.6.1.1]

This procedure is used when:

…

– the UE in EMM-IDLE or EMM-CONNECTED mode has requested to perform mobile originating/terminating CS fallback; or

…

The UE shall invoke the service request procedure when:

…

e) the UE, in EMM-IDLE or EMM-CONNECTED mode, has a CS fallback response to be sent to the network; or

…

[TS 24.301 clause5.6.2.3]

The network may initiate the paging procedure for non-EPS services when the UE is IMSI attached for non-EPS services.

The network shall stop the timer T3413 for the paging procedure when a response is received from the UE.

To notify the UE about an incoming mobile terminating CS service when a NAS signalling connection exists, the EMM entity in the network shall send a CS SERVICE NOTIFICATION message.

[TS 24.301, Annex D]

…

Table D.1.1: Mapping of NAS procedure to establishment cause and call type

NAS procedure	RRC establishment cause (according 3GPP TS 36.331 [22])	Call type
…
Service Request	If a EXTENDED SERVICE REQUEST has service type set to "mobile terminating CS fallback", the RRC establishment cause shall be set to MT access. (See Note1).	"terminating calls"
…
Note 1: For these NAS procedures initiated by UEs of access class 12, 13 or 14 in their home country, the RRC establishment cause will be set to "High priority access AC 11 – 15". For this purpose the home country is defined as the country of the MCC part of the IMSI, see 3GPP TS 22.011 [1A]. For these NAS procedures initiated by UE of access class 11 or 15 in their HPLMN or EHPLMN, the RRC establishment cause will be set to "High priority access AC 11 – 15".

9.3.2.2a.3 Test description

9.3.2.2a.3.1 Pre-test conditions

System Simulator:

– Cell A(TAI-1) is set to ”Serving cell”

UE:

None.

Preamble:

– The UE is in state Generic RB established (state 3) on cell A according to [18].

9.3.2.2a.3.2 Test procedure sequence

Table 9.3.2.2a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS sends a CS SERVICE NOTIFICATION message to the UE.	<–	CS SERVICE NOTIFICATION	–	–
2	The UE accepts CS fallback	–		–	–
3	Check: Does the UE transmit an EXTENDED SERVICE REQUEST message to SS?	–>	EXTENDED SERVICE REQUEST	1	P
4	The SS sends a SERVICE REJECT message with T3442 = 60 seconds in order that the UE enters EMM-REGISTERED.NORMAL-SERVICE.	<–	SERVICE REJECT	–	–
5	The SS releases the RRC connection.	–	–	–	–
–	EXCEPTION: The behaviour in table 9.3.2.2a.3.2-2 may occur in parallel with step 6.	–	–	–	–
6	SS waits for 60 seconds (T3442)	–	–	–	–

Table 9.3.2.2a.3.2-2: Parallel Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message/PDU/SDU
1	The UE transmits a TRACKING AREA UPDATE REQUEST message.	–>	TRACKING AREA UPDATE REQUEST	–	–
2	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	TRACKING AREA UPDATE ACCEPT	–	–
3	The SS releases the RRC connection.	–	–	–	–

9.3.2.2a.3.3 Specific message contents

Table 9.3.2.2a.3.3-1: Message EXTENDED SERVICE REQUEST (step 3, Table 9.3.2.2a.3.2-1)

Derivation Path: 36.508 clause 4.7.2-14A
Information Element	Value/remark	Comment	Condition
M-TMSI	M-TMSI1

Table 9.3.2.2a.3.3-2: Message SERVICE REJECT (step 4, Table 9.3.2.2a.3.2-1)

Derivation Path: 36.508 clause 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	’00100111’B	CS domain temporarily not available
T3442 value	‘0010 0001’B’	1 minute

Table 9.3.2.2a.3.3-3: Message TRACKING AREA UPDATE ACCEPT (step 2, Table 9.3.2.2a.3.2-2)

Derivation path: 36.508 table 4.7.2-24
Information Element	Value/Remark	Comment	Condition
GUTI	Not present
MS identity	Not present