11.3 eCall over IMS

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

11.3.1 eCall Only mode / T3444 / eCall inactivity procedure / Removal of eCall only restriction after an eCall over IMS

11.3.1.1 Test Purpose (TP)

(1)

with { UE is switched ON with eCall only enabled USIM}

ensure that {

when { UE reads a ims-EmergencySupport-r9 and eCallOverIMS-Support-r14 from SystemInformationBlockType1}

then {UE enters substate EMM-DEREGISTERED.eCALL-INACTIVE and shall not start registration process.}

}

(2)

with { The UE is in the state EMM-DEREGISTERED.eCALL-INACTIVE}

ensure that {

when { UE is requested to make a manual eCall}

then { UE sends ATTACH REQUEST message with EPS attach type IE ‘combined EPS/IMSI attach’}

}

(3)

with { UE receives ATTACH ACCEPT message with EPS attach result ‘combined EPS/IMSI attach’ and

IMS voice over PS sessions is supported }

ensure that {

when { UE is in the EMM-REGISTERED.NORMAL-SERVICE state and an initial IMS registration is performed }

then { the UE transmits a PDN CONNECTIVITY REQUEST message with the request type set to

"emergency" }

}

(4)

with { UE receives an RRCConnectionRelease message and enters in RRC_IDLE state }

ensure that {

when { SS sends paging request for IMS MT speech call }

then {the UE answers the paging request for IMS MT speech call }

}

(5)

with { UE receives an RRCConnectionRelease message and enters in RRC_IDLE state }

ensure that {

when { UE starts T3444 for 12Hours and the periodic tracking area updating timer T3412 expires }

then { UE sends TRACKING AREA UPDATE REQUEST message with EPS update type = ’Periodic updating’ }

}

(6)

with { UE is in RRC_IDLE state }

ensure that {

when { eCall Inactivity timer T3444 expires }

then { The UE performs Detach procedure }

}

11.3.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.3.1.2.1, 5.5.3.4 and 10.2 and TS 36.331, clauses 6.2.2, 5.2.2.7

[TS 24.301 clause 5.3.1.2.1]

The signalling procedure for the release of the NAS signalling connection is initiated by the network.

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

If the UE is configured for eCall only mode as specified in 3GPP TS 31.102 [17] then:

– if the NAS signalling connection that was released had been established for eCall over IMS, the UE shall start timer T3444; and

– if the NAS signalling connection that was released had been established for a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service, the UE shall start timer T3445.

[TS 24.301 clause 5.5.3.4]

The eCall inactivity procedure is applicable only to a UE configured for eCall only mode as specified in 3GPP TS 31.102 [17]. The procedure shall be started when timer T3444 or timer T3445 expires or is found to have already expired in any EMM-REGISTERED substate except substates EMM-REGISTERED.PLMN-SEARCH or EMM-REGISTERED.NO-CELL-AVAILABLE. The UE shall then perform the following actions:

stop other running timers (e.g. T3411, T3412);
if the UE is currently registered to EPS services only, perform a detach procedure for EPS services only;

– if the UE is currently registered for both EPS services and non-EPS services, perform a combined detach procedure for EPS services and non-EPS services;

delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, and KSI; and
enter EMM-DEREGISTERED.eCALL-INACTIVE state.

[TS 24.301 clause 10.2]

TIMER NUM.	TIMER VALUE	STATE	CAUSE OF START	NORMAL STOP	ON EXPIRY
T3444	12 hours	All except EMM-NULL	UE configured for eCall only mode enters EMM-IDLE mode after an eCall over IMS	Removal of eCall only restriction	Perform eCall inactivity procedure as described in subclause 5.5.3.4
T3445	12 hours	All except EMM-NULL	UE configured for eCall only mode enters EMM-IDLE mode after a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service	Removal of eCall only restriction	Perform eCall inactivity procedure as described in subclause 5.5.3.4

[TS 36.331 clause 5.2.2.7]

Upon receiving the SystemInformationBlockType1 or SystemInformationBlockType1-BR either via broadcast or via dedicated signalling, the UE shall:

1> if in RRC_IDLE or in RRC_CONNECTED while T311 is running; and

…

3> forward the eCallOverIMS-Support to upper layers, if present;

[TS 36.331 clause 6.2.2]

eCallOverIMS-Support

Indicates whether the cell supports eCall over IMS services for UEs as defined in TS 23.401 [41]. If absent, eCall over IMS is not supported by the network in the cell. NOTE 2.

11.3.1.3 Test description

11.3.1.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18] and is the serving cell.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-2.

– The UE is equipped with a USIM containing values shown in Table 11.3.1.3.1-1.

Preamble:

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

11.3.1.3.2 Test procedure sequence

Table 11.3.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	Check: Does UE send an RRCConnectionRequest on Cell 1 within 120 seconds?	–>	RRCConnectionRequest	1	F
3	A manual eCall is initiated. (See Note 1)	–	–	–	–
4	Check: Does the UE sends an ATTACH REQUEST message with a PDN CONNECTIVITY REQUEST message to request PDN connectivity to the default PDN. EPS attach type = "combined EPS/IMSI attach"?	–>	ATTACH REQUEST	2	P
5-13	Steps 5-13 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.	–	–	–	–
14	The SS transmits an ATTACH ACCEPT message with the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message and SS assigns value of 186 minutes for the timer T3412.	<–	ATTACH ACCEPT	–	–
15-18b1	Steps 15-18b1 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.	–	–	–	–
19	Check: Does UE transmit a PDN connectivity REQUEST message to request an additional PDN, with ‘Request type’ set to ’emergency (‘0100’B)’?	–>	PDN CONNECTIVITY REQUEST	3	P
20-25	The UE performs Steps 20-25 of the generic test procedure for eCall over IMS establishment in EUTRA: eCall only mode described in TS 36.508 subclause 4.5A.27.3.	–	–	–	–
26-29	Release eCall over IMS using the generic procedure described in TS 34.229-1 [35] subclause C.33	–	–	–	–
30	Void	–	–	–	–
31	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
32	The SS waits 1 minute.	–	–	–	–
33-56	Steps 1 to 24 of the generic test procedure for IMS MT speech call specified in TS 36.508 subclause 4.5A.7.3	–	–	4	P
57-60	Generic test procedure for MT release of IMS call as described in annex C.33 of TS 34.229-1 [35] takes place.	–	–	–	–
61	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
62	Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message at the expiry of T3412 periodically for every 186 minutes and remains registered until T3444 expires? (See Note 2)	–>	TRACKING AREA UPDATE REQUEST	5	P
63	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	TRACKING AREA UPDATE ACCEPT	–	–
64	Check: Does the UE transmit a DETACH REQUEST message at expiry of T3444?	–>	DETACH REQUEST	6	P
65	The SS responds with DETACH ACCEPT message.	<–	DETACH ACCEPT	–	–
66	The SS releases the RRC connection.	–>	RRCConnectionRelease	–	–
Note 1: The request to originate a manual eCall may be performed by MMI or AT command. Note 2: Timer T3412 is reset and started with its initial value, when the UE changes from EMM-CONNECTED to EMM-IDLE mode so the timer T3412 should be started after step 61 and T3444 should be started after step 31.

11.3.1.3.3 Specific message contents

Table 11.3.1.3.3-1: Message SystemInformationBlockType1 (Preamble)

Derivation path: 36.508 table 4.4.3.2-3 Condition eCalloverIMS

Table 11.3.1.3.3-2: Message ATTACH ACCEPT (step 14, Table 11.3.1.3.2-1)

Derivation path: 36.508 table 4.7.2-1
Information Element	Value/Remark	Comment	Condition
EPS attach result	‘010’B	”Combined EPS/IMSI attach”
T3412 value
Unit	‘010’	”value is incremented in multiples of decihours”
Timer value	‘11111’	”186 minutes”
GUTI	GUTI-1
EPS network feature support	‘0000 0011’B	emergency bearer services in S1 mode and IMS voice over PS session in S1 mode are supported

Table 11.3.1.3.3-3: Message PDN CONNECTIVITY REQUEST (step 19, Table 11.3.1.3.2-1)

Derivation Path: 36.508 table 4.7.2-1
Information Element	Value/Remark	Comment	Condition
Request type	‘0100’B	emergency
Access point name	Not present

Table 11.3.1.3.3-4: Message TRACKING AREA UPDATE REQUEST (step 62, Table 11.3.1.3.2-1)

Derivation path: 36.508 table 4.7.2-27
Information Element	Value/Remark	Comment	Condition
EPS update type
EPS update type value	‘011’B	”Periodic updating”
Old GUTI	GUTI-1

Table 11.3.1.3.3-5: DETACH REQUEST (Step 64, Table 11.3.1.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11
Information Element	Value/remark	Comment	Condition
Detach type
Type of detach	001	combined EPS/IMSI detach
Switch off	0	normal detach
GUTI or IMSI	GUTI-1

11.3.2 eCall Only mode / T3445 / eCall inactivity procedure / Removal of eCall only restriction after a call to URI for test service

11.3.2.1 Test Purpose (TP)

(1)

with { UE is in the state EMM-DEREGISTERED.eCALL-INACTIVE}

ensure that {

when { UE is requested to make an eCall to URI for test service}

then { UE sends ATTACH REQUEST message with EPS attach type IE ‘combined EPS/IMSI attach’}

}

(2)

with { UE receives ATTACH ACCEPT message with EPS attach result ‘combined EPS/IMSI attach’ and

IMS voice over PS sessions is supported }

ensure that {

when { UE is in the EMM-REGISTERED.NORMAL-SERVICE state and an initial IMS registration is performed }

then { UE transmits an initial INVITE request for ecall to uri for test services }

}

(3)

with { UE receives an RRCConnectionRelease message and enters in RRC_IDLE state }

ensure that {

when { SS sends paging request for IMS MT speech call }

then {the UE answers the paging request for IMS MT speech call }

}

(4)

with { UE receives an RRCConnectionRelease message and enters in RRC_IDLE state }

ensure that {

when { UE starts T3445 for 12Hours and the periodic tracking area updating timer T3412 expires }

then { UE sends TRACKING AREA UPDATE REQUEST message with EPS update type = ’Periodic updating’ }

}

(5)

with { UE is in RRC_IDLE state }

ensure that {

when { eCall Inactivity timer T3445 expires }

then { The UE performs Detach procedure }

}

11.3.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 5.3.1.2.1, 5.5.4 and 10.2

[TS 24.301 clause 5.3.1.2.1]

The signalling procedure for the release of the NAS signalling connection is initiated by the network.

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

If the UE is configured for eCall only mode as specified in 3GPP TS 31.102 [17] then:

– if the NAS signalling connection that was released had been established for eCall over IMS, the UE shall start timer T3444; and

[TS 24.301 clause 5.5.4]

– stop other running timers (e.g. T3411, T3412);

– if the UE is currently registered to EPS services only, perform a detach procedure for EPS services only;

– if the UE is currently registered for both EPS services and non-EPS services, perform a combined detach procedure for EPS services and non-EPS services;

– delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, and KSI; and

– enter EMM-DEREGISTERED.eCALL-INACTIVE state.

[TS 24.301 clause 10.2]

TIMER NUM.	TIMER VALUE	STATE	CAUSE OF START	NORMAL STOP	ON EXPIRY
T3444	12 hours	All except EMM-NULL	UE configured for eCall only mode enters EMM-IDLE mode after an eCall over IMS	Removal of eCall only restriction	Perform eCall inactivity procedure as described in subclause 5.5.4
T3445	12 hours	All except EMM-NULL	UE configured for eCall only mode enters EMM-IDLE mode after a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service	Removal of eCall only restriction	Perform eCall inactivity procedure as described in subclause 5.5.4

11.3.2.3 Test description

11.3.2.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18] and is the serving cell.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-2.

Preamble:

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

11.3.2.3.2 Test procedure sequence

Table 11.3.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	Wait for 60s for the UE to enter EMM-DEREGISTERED.eCALL-INACTIVE state	–	–	–	–
3	An eCall to URI for test service is initiated. (See Note 1)	–	–	–	–
4	Check: Does the UE sends an ATTACH REQUEST message with a PDN CONNECTIVITY REQUEST message to request PDN connectivity to the default PDN. EPS attach type = "combined EPS/IMSI attach"?	–>	ATTACH REQUEST	1	P
5-13	Steps 5-13 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.	–	–	–	–
14	The SS transmits an ATTACH ACCEPT message with the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message and SS assigns value of 186 minutes for the timer T3412.	<–	ATTACH ACCEPT	–	–
–	EXCEPTION: In parallel to the events described in steps 15-16c1 below, the behaviour in table 11.3.2.3.2-2 occurs.	–	–	–	–
15-16c1	Steps 15-16c1 of the generic procedure for UE registration specified in TS 36.508 sub clause 4.5.2.3 are performed.	–	–	–	–
17-25	Void	–	–	–	–
26a1-31	The UE performs Steps 9a1-14 of the generic test procedure as described in TS 36.508 sub clause 4.5A.6.3	–	–	–	–
32-35	Release eCall to URI for test service using the generic procedure described in TS 34.229-1 [35] sub clause C.33.	–	–	–	–
36	Void	–	–	–	–
37	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
38	The SS waits 1 minute.	–	–	–	–
39-62	Steps 1 to 24 of the generic test procedure for IMS MT speech call specified in TS 36.508 sub clause 4.5A.7.3.	–	–	3	P
63-66	Generic test procedure for MT release of IMS call as described in annex C.33 of TS 34.229-1 [35] takes place.	–	–	–	–
67	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
68	Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message at the expiry of T3412 periodically for every 186 minutes and remains registered until T3445 expires? (See Note 2)	–>	TRACKING AREA UPDATE REQUEST	4	P
69	The SS transmits a TRACKING AREA UPDATE ACCEPT message.	<–	TRACKING AREA UPDATE ACCEPT	–	–
70	The UE sends TRACKING AREA UPDATE COMPLETE message	–>	TRACKING AREA UPDATE COMPLETE	–	–
71	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
72	Check: Does the UE transmit a DETACH REQUEST message at expiry of T3445?	–>	DETACH REQUEST	5	P
73	The SS responds with DETACH ACCEPT message.	<–	DETACH ACCEPT	–	–
74	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
Note 1: The request to originate an eCall to URI for test service may be performed by MMI or AT command. Content of INVITE request as specified in TS 34.229-1 [35] Step-2 of Annex C.21 using condition A25. Note 2: Timer T3412 is reset and started with its initial value, when the UE changes from EMM-CONNECTED to EMM-IDLE mode so the timer T3412 should be started after step 67 and T3445 should be started after step 37.

Table 11.3.2.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits an INVITE request message as defined in step 1 of TS 34.229-1 [35] annex C.47.	–>	INVITE	2	P

11.3.2.3.3 Specific message contents

Table 11.3.2.3.3-1: Message SystemInformationBlockType1 (Preamble)

Derivation path: 36.508 table 4.4.3.2-3 Condition eCalloverIMS

Table 11.3.2.3.3-2: Message ATTACH ACCEPT (step 14, Table 11.3.2.3.2-1)

Derivation path: 36.508 table 4.7.2-1
Information Element	Value/Remark	Comment	Condition
EPS attach result	‘010’B	”Combined EPS/IMSI attach”
T3412 value
Unit	‘010’	”value is incremented in multiples of decihours”
Timer value	‘11111’	”186 minutes”
GUTI	GUTI-1
EPS network feature support	‘0000 0011’B	IMS voice over PS session in S1 mode is supported emergency bearer services in S1 mode supported

Table 11.3.2.3.3-3: Void

Table 11.3.2.3.3-4: Message TRACKING AREA UPDATE REQUEST (step 68, Table 11.3.2.3.2-1)

Derivation path: 36.508 table 4.7.2-27
Information Element	Value/Remark	Comment	Condition
EPS update type
EPS update type value	‘011’B	”Periodic updating”
Old GUTI	GUTI-1

Table 11.3.2.3.3-4A: Message TRACKING AREA UPDATE ACCEPT (step 69, Table 11.3.2.3.2-1)

Derivation path: 36.508 table 4.7.2-24
Information Element	Value/Remark	Comment	Condition
T3412 value
Unit	‘010’	”value is incremented in multiples of decihours”
Timer value	‘11111’	”186 minutes”
EPS network feature support	‘0000 0011’B	IMS voice over PS session in S1 mode is supported emergency bearer services in S1 mode supported

Table 11.3.2.3.3-5: Message DETACH REQUEST (Step 72, Table 11.3.2.3.2-1)

Derivation Path: 36.508, Table 4.7.2-11
Information Element	Value/remark	Comment	Condition
Detach type
Type of detach	001	combined EPS/IMSI detach
Switch off	0	normal detach
GUTI or IMSI	GUTI-1

11.3.3 eCall capable / EPS supports IMS voice over PS session / EPS supports emergency service / eCall over IMS is not supported / eCall using the CS domain / emergency call over IMS if eCall using the CS domain is not available / UTRA or GERAN

11.3.3.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE is requested to make an automatic eCall}

then { UE establishes the eCall using the CS domain (UTRA or GERAN)}

}

(2)

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

ensure that {

when { UE is requested to make an automatic eCall}

then { UE establishes the normal emergency call on LTE, UE establishes the RRC connection with the RRC establishmentCause set to ‘emergency’ and sends a SERVICE REQUEST message }

}

11.3.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 6.2.2, 5.2.2.7 and TS 23.167 Annex H.6

[TS 36.331 clause 5.2.2.7]

Upon receiving the SystemInformationBlockType1 or SystemInformationBlockType1-BR either via broadcast or via dedicated signalling, the UE shall:

1> if in RRC_IDLE or in RRC_CONNECTED while T311 is running; and

…

3> forward the eCallOverIMS-Support to upper layers, if present;

[TS 36.331 clause 6.2.2]

eCallOverIMS-Support

Indicates whether the cell supports eCall over IMS services for UEs as defined in TS 23.401 [41]. If absent, eCall over IMS is not supported by the network in the cell. NOTE 2.

[TS 23.167 Annex H.6]

This clause details the domain priority and selection (see clause 7.3) for a UE that attempts to make an eCall over IMS session using E-UTRAN radio access networks based on the availability of the CS or PS domains and the network support for IMS emergency, eCall over IMS and IMS voice over PS.

The following table (Table H.2) defines these rules based on the UE (last 2 columns) for different initial conditions (first 4 columns) when an eCall over IMS session is initiated and when the UE is not in limited service state.

Table H.2: Domain Selection Rules for eCall over IMS session attempts for E-UTRAN radio access networks

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	CS if available
B	Y	Y	Y	N	CS if available	PS (UE establishes IMS emergency session)
C	Y	Y or N	N	N	CS if available	No attempt is made in the PS domain
D	Y	N	Y	Y	PS or CS if available	CS if first attempt in PS PS if first attempt in CS
E	Y	N	Y	N	CS if available	PS (UE establishes IMS emergency session)
F	N		–	–	CS if available
VoIMS = Voice over IMS over PS sessions support as indicated by IMS Voice over PS session supported indication as defined in TS 23.401 [28]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28].

11.3.3.3 Test description

11.3.3.3.1 Pre-test conditions

System Simulator:

– Cell A is set to “Serving cell”

– If (px_RATComb_Tested = EUTRA_UTRA AND pc_CS_Em_Call_in_UTRA)

– cell 5 is configured as ”Suitable Neighbour cell”

– If (px_RATComb_Tested = EUTRA_GERAN AND pc_CS_Em_Call_in_GERAN)

– cell 24 is configured as ”Suitable Neighbour cell”

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

– The SS broadcasts IMS Emergency Call support in System Information Block Type 1 on Cell A.

– The SS broadcasts eCall over IMS is not supported in System Information Block Type 1 on Cell A.

UE:

– The eCall capable UE is equipped with ‘eCall support’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-1.

Preamble:

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

11.3.3.3.2 Test procedure sequence

Table 11.3.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Cause the UE to originate Automatic eCall. (Note 1)	–	–	–	–
–	EXCEPTION: Steps 4a1 A to 4b14 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.	–	–	–	–
2a1	IF (px_RATComb_Tested = EUTRA_UTRA AND pc_CS_Em_Call_in_UTRA)	–	–	–	–
2a2	Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with Establishment cause: Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
2a3	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
2a4	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
2a5	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
2a6	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
2a7	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
2a8	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
2a9	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2a10	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 7 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
2a11-2a16	Steps 11 to 16 of the generic test procedure in TS 34.108 subclause 7.2.3.2.3 are performed on Cell 5. NOTE: the CS call setup is completed.	–	–	–	–
2a17	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
2a18	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
2a19	The UE transmits RELEASE.	–>	RELEASE	–	–
2a20	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
2a21	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
	The UE transmits RRC CONNECTION RELEASE COMPLETE.		RRC CONNECTION RELEASE COMPLETE
2b1	IF (px_RATComb_Tested = EUTRA_GERAN AND pc_CS_Em_Call_in_GERAN)	–	–	–	–
2b2	Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call?	–>	CHANNEL REQUEST	1	P
2b3	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
2b4	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
2b5	The SS transmits an AUTHENTICATION REQUEST message.	<–	AUTHENTICATION REQUEST	–	–
2b6	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
2b7	The SS transmits a CIPHERING MODE COMMAND.	<–	CIPHERING MODE COMMAND	–	–
2b8	The UE transmits a CIPHERING MODE COMPLETE.	–>	CIPHERING MODE COMPLETE	–	–
2b9	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 7 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
2b10-2b16	Steps 11 to 17 of the generic test procedure in TS 51.010-1 subclause 10.2.3 are performed on Cell 24. NOTE: the CS call setup is completed.	–	–	–	–
2b17	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
2b18	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
2b19	The UE transmits RELEASE.	–>	RELEASE	–	–
2b20	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
2b21	The SS transmits CHANNEL RELEASE	<–	CHANNEL RELEASE	–	–
3	if possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed.	–	–	–	–
–	EXCEPTION: Step 4a1 describes behaviour that depends on the UE capability.	–	–	–	–
4a1	If pc_SwitchOnOff or pc_USIM_Removal then UE sends DETACH REQUEST message	–>	DETACH REQUEST	–	–
5	Set the power level of Cell 5 and Cell 24 to Non-suitable" Off" level.	–	–	–	–
6	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
7-23	Steps 2 to 18 of the registration procedure described in TS 36.508 subclause 4.5.2.3 are performed on Cell A. NOTE: The UE performs registration and the RRC connection is released.	–	–	–	–
24	Cause the UE to originate Automatic eCall. (see Note 1)	–	–	–	–
25	Check: Does the UE transmit an RRCConnectionRequest message on Cell A with Establishment cause: Emergency?	–>	RRCConnectionRequest	2	P
26-39	Steps 2 to 15 of the generic test procedure for IMS Emergency call establishment in EUTRA: in EUTRA: Normal Service (TS 36.508 subclause 4.5A.4.3-1). (Note 2)	–	–	–	–
40	Release IMS Call (Note 3)	–	–	–	–
41	The SS releases the RRC connection.	–	–	–	–
Note 1: The request to originate an automatic eCall may be performed by MMI or AT command. Note 2: The UE shall set the “Request URI and To header” to "urn:service:sos.ecall.automatic" and shall not include the initial MSD in the SIP INVITE message. Note 3: The IMS Call is released using the generic procedure in TS 34.229-1 [35] subclause C.33.

11.3.3.3.3 Specific message contents

Table 11.3.3.3.3-1: RRC CONNECTION REQUEST (Step 2a2, Table 11.3.3.3.2-1)

Derivation Path: TS 34.108 clause 9.1.1
Information Element	Value/remark	Comment	Condition
Establishment cause	Emergency Call

Table 11.3.3.3.3-2: CM SERVICE REQUEST (Steps 2a5 and 2b4, Table 11.3.3.3.2-1)

Derivation Path: TS 24.008 Table 9.2.11
Information Element	Value/remark	Comment	Condition
CM service type	0010	Emergency call establishment

Table 11.3.3.3.3-3: CHANNEL REQUEST (Step 2b2, Table 11.3.3.3.2-1)

Derivation Path: TS 44.018 Table 9.1.8.1
Information Element	Value/remark	Comment	Condition
Establishment cause	101	Emergency call

Table 11.3.3.3.3-4: RRCConnectionRequest (step 25, Table 11.3.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	emergency
}
}
}

11.3.4 eCall Only mode / EPS supports IMS voice over PS session / EPS does not support emergency service / eCall over IMS is not supported / eCall using CS domain / eCall failure if CS domain is not available

11.3.4.1 Test Purpose (TP)

(1)

with { UE in eCall Only mode is in the state EMM-DEREGISTERED.eCALL-INACTIVE }

ensure that {

when { When EPS supports IMS voice over PS but does not support emergency service and does not support eCall over IMS and when UE is requested to make an automatic eCall }

then { UE establishes the eCall using the CS domain (UTRA or GERAN)}

}

(2)

with { UE in eCall Only mode is in the state EMM-DEREGISTERED.eCALL-INACTIVE }

ensure that {

when { When EPS supports IMS voice over PS but does not support emergency service and does not support eCall over IMS and CS domain is not available and when UE is requested to make an automatic eCall }

then { UE does not establishes an normal emergency call, eCall over IMS or eCall over CS domain }

}

11.3.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause 4.4.3.1.1 and TS 23.167 Annex H.6. Unless otherwise stated these are Rel-14 requirements.

[TS 23.122 clause 4.4.3.1.1]

The MS selects and attempts registration on other PLMN/access technology combinations, if available and allowable, in the following order:

i) either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present) ;

ii) each PLMN/access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);

iii) each PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);

iv) other PLMN/access technology combinations with received high quality signal in random order;

v) other PLMN/access technology combinations in order of decreasing signal quality.

When following the above procedure the following requirements apply:

…

l) In i to v, if the MS is in eCall only mode, the MS shall not consider PLMNs which do not advertise support for eCall over IMS, unless such PLMNs are available in GERAN or UTRAN.

NOTE 6: As an implementation option, an MS in eCall only mode that was not able to select any PLMN according to l) can perform a second iteration of i to v with no restriction.

…

[TS 23.167 Annex H.6]

Table H.2: Domain Selection Rules for eCall over IMS session attempts for E-UTRAN radio access networks

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	CS if available
B	Y	Y	Y	N	CS if available	PS (UE establishes IMS emergency session)
C	Y	Y or N	N	N	CS if available	No attempt is made in the PS domain
D	Y	N	Y	Y	PS or CS if available	CS if first attempt in PS PS if first attempt in CS
E	Y	N	Y	N	CS if available	PS (UE establishes IMS emergency session)
F	N		–	–	CS if available
VoIMS = Voice over IMS over PS sessions support as indicated by IMS Voice over PS session supported indication as defined in TS 23.401 [28]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28].

11.3.4.3 Test description

11.3.4.3.1 Pre-test conditions

System Simulator:

– Cell A is set to “Serving cell”

– If (px_RATComb_Tested = EUTRA_UTRA AND pc_CS_Em_Call_in_UTRA)

– cell 5 is configured as ”Suitable Neighbour cell”

– If (px_RATComb_Tested = EUTRA_GERAN AND pc_CS_Em_Call_in_GERAN)

– cell 24 is configured as ”Suitable Neighbour cell”

– System information combination 10 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells. – The SS broadcasts IMS Emergency Call is not supported in System Information Block Type 1 on Cell A.

– The SS broadcasts eCall over IMS is not supported in System Information Block Type 1 on Cell A.

UE:

– The eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-2.

Preamble:

– The UE is in state OFF (state 1)

11.3.4.3.2 Test procedure sequence

Table 11.3.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The UE is switched on and SS waits 15 sec to allow the UE to camp on the serving cell and enter and remain in substate EMM-DEREGISTERED.eCALL-INACTIVE.	–	–	–	–
1	Cause the UE to originate Automatic eCall. (Note 1)	–	–	–	–
–	EXCEPTION: Steps 4a1 A to 4b14 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.	–	–	–	–
2a1	IF (px_RATComb_Tested = EUTRA_UTRA AND pc_CS_Em_Call_in_UTRA)	–	–	–	–
2a2	Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with Establishment cause: Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
2a3	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
2a4	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
2a5	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
2a6	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
2a7	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
2a8	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
2a9	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
2a10	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 7 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
2a11-2a16	Steps 11 to 16 of the generic test procedure in TS 34.108 subclause 7.2.3.2.3 are performed on Cell 5. NOTE: the CS call setup is completed.	–	–	–	–
2a17	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
2a18	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
2a19	The UE transmits RELEASE.	–>	RELEASE	–	–
2a20	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
2a21	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
	The UE transmits RRC CONNECTION RELEASE COMPLETE.		RRC CONNECTION RELEASE COMPLETE
2b1	IF (px_RATComb_Tested = EUTRA_GERAN AND pc_CS_Em_Call_in_GERAN)	–	–	–	–
2b2	Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call?	–>	CHANNEL REQUEST	1	P
2b3	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
2b4	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
2b5	The SS transmits an AUTHENTICATION REQUEST message.	<–	AUTHENTICATION REQUEST	–	–
2b6	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
2b7	The SS transmits a CIPHERING MODE COMMAND.	<–	CIPHERING MODE COMMAND	–	–
2b8	The UE transmits a CIPHERING MODE COMPLETE.	–>	CIPHERING MODE COMPLETE	–	–
2b9	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 7 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
2b10-2b16	Steps 11 to 17 of the generic test procedure in TS 51.010-1 subclause 10.2.3 are performed on Cell 24. NOTE: the CS call setup is completed.	–	–	–	–
2b17	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
2b18	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
2b19	The UE transmits RELEASE.	–>	RELEASE	–	–
2b20	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
2b21	The SS transmits CHANNEL RELEASE	<–	CHANNEL RELEASE	–	–
3	if possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed.	–	–	–	–
–	EXCEPTION: Step 4a1 describes behaviour that depends on the UE capability.	–	–	–	–
4a1	If pc_SwitchOnOff or pc_USIM_Removal then UE sends DETACH REQUEST message	–>	DETACH REQUEST	–	–
5	Set the power level of Cell 5 and Cell 24 to Non-suitable" Off" level.	–	–	–	–
6	The UE is brought back to operation or the USIM is inserted.	–	–	–	–
7	SS waits 15 sec to allow the UE to camp on the serving cell and enter and remain in substate EMM-DEREGISTERED.eCALL-INACTIVE.	–	–	–	–
8	Cause the UE to originate Automatic eCall. (see Note 1)	–	–	–	–
9	Check: Does the UE transmit an RRCConnectionRequest message on Cell A with Establishment cause: Emergency in the next 2 sec?	–>	RRCConnectionRequest	2	F
Note 1: The request to originate an automatic eCall may be performed by MMI or AT command.

11.3.4.3.3 Specific message contents

Table 11.3.4.3.3-1: SystemInformationBlockType1 for Cell A (preamble and all steps)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
ims-EmergencySupport-r9	Not present	Not support IMS emergency call
eCallOverIMS-Support-r14	Not present	Not support eCall over IMS services.
}

Table 11.3.4.3.3-2: RRC CONNECTION REQUEST (Step 2a2, Table 11.3.4.3.2-1)

Derivation Path: TS 34.108 clause 9.1.1
Information Element	Value/remark	Comment	Condition
Establishment cause	Emergency Call

Table 11.3.4.3.3-3: CM SERVICE REQUEST (Steps 2a5 and 2b4, Table 11.3.4.3.2-1)

Derivation Path: TS 24.008 Table 9.2.11
Information Element	Value/remark	Comment	Condition
CM service type	0010	Emergency call establishment

Table 11.3.4.3.3-4: CHANNEL REQUEST (Step 2b2, Table 11.3.4.3.2-1)

Derivation Path: TS 44.018 Table 9.1.8.1
Information Element	Value/remark	Comment	Condition
Establishment cause	101	Emergency call

11.3.5 eCall Only mode / EPS supports IMS voice over PS session / EPS supports emergency service / eCall over IMS is supported / RACH failure in EUTRA cell / eCall using the CS domain

11.3.5.1 Test Purpose (TP)

(1)

with { UE is in the state EMM-DEREGISTERED.eCALL-INACTIVE }

ensure that {

when { UE is requested to make automatic eCall and RACH failure is observed in EUTRA cell during 1st attempt }

then { UE establishes the eCall using the CS domain (UTRA or GERAN)}

}

11.3.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 23.167 Annex H.6

[TS 23.167 Annex H.6]

Table H.2: Domain Selection Rules for eCall over IMS session attempts for E-UTRAN radio access networks

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	CS if available
B	Y	Y	Y	N	CS if available	PS (UE establishes IMS emergency session)
C	Y	Y or N	N	N	CS if available	No attempt is made in the PS domain
D	Y	N	Y	Y	PS or CS if available	CS if first attempt in PS PS if first attempt in CS
E	Y	N	Y	N	CS if available	PS (UE establishes IMS emergency session)
F	N		–	–	CS if available
VoIMS = Voice over IMS over PS sessions support as indicated by IMS Voice over PS session supported indication as defined in TS 23.401 [28]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28].

11.3.5.3 Test description

11.3.5.3.1 Pre-test conditions

System Simulator:

– Cell A is set to “Serving cell”

– If (px_RATComb_Tested = EUTRA_UTRA AND pc_CS_Em_Call_in_UTRA)

– Cell 5 is configured as ”Suitable Neighbour cell”

– If (px_RATComb_Tested = EUTRA_GERAN AND pc_CS_Em_Call_in_GERAN)

– Cell 24 is configured as ”Suitable Neighbour cell”

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

– The SS broadcasts IMS Emergency Call support in System Information Block Type 1 on Cell A.

– The SS broadcasts eCall over IMS is supported in System Information Block Type 1 on Cell A.

UE:

– The eCall capable UE is equipped with ‘eCall support’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-2.

Preamble:

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

11.3.5.3.2 Test procedure sequence

Table 11.3.5.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	An Automatic eCall is initiated. (Note 1)	–	–	–	–
3	Check: Does the UE transmit preamble on PRACH?	–>	PRACH Preamble	–	–
–	EXCEPTION: In parallel to the events described in step 3 the steps specified in Table 11.3.5.3.2-2 should take place.	–	–	–	–
4a1	IF (px_RATComb_Tested = EUTRA_UTRA AND pc_CS_Em_Call_in_UTRA)	–	–	–	–
4a2	Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with Establishment cause: Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
4a3	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
4a4	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
4a5	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
4a6	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
4a7	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
4a8	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
4a9	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
4a10	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 7 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
4a11-4a16	Steps 11 to 16 of the generic test procedure in TS 34.108 sub clause 7.2.3.2.3 are performed on Cell 5. NOTE: the CS call setup is completed.	–	–	–	–
4a17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
4a18	The UE transmits RELEASE.	–>	RELEASE	–	–
4a19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
4a20	The SS transmits an RRCConnectionRelease message.	<–	RRCConnectionRelease	–	–
5b1	IF (px_RATComb_Tested = EUTRA_GERAN AND pc_CS_Em_Call_in_GERAN)	–	–	–	–
5b2	Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call?	–>	CHANNEL REQUEST	1	P
5b3	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
5b4	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
5b5	The SS transmits an AUTHENTICATION REQUEST message	<–	AUTHENTICATION REQUEST	–	–
5b6	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
5b7	The SS transmits a CIPHERING MODE COMMAND.	<–	CIPHERING MODE COMMAND	–	–
5b8	The UE transmits a CIPHERING MODE COMPLETE.	–>	CIPHERING MODE COMPLETE	–	–
5b9	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 7 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
5b10-5b16	Steps 11 to 17 of the generic test procedure in TS 51.010-1 subclause 10.2.3 are performed on Cell 24. NOTE: the CS call setup is completed.	–	–	–	–
5b17	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
5b18	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
5b19	The UE transmits RELEASE.	–>	RELEASE	–	–
5b20	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
5b21	The SS transmits CHANNEL RELEASE	<–	CHANNEL RELEASE	–	–
Note 1: The request to originate an automatic eCall may be performed by MMI or AT command.

Table 11.3.5.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	EXCEPTION: The steps 1 and 2 below are repeated for the duration of T300.	–	–	–	–
1	The UE attempts to perform RACH procedure on Cell A.	–	–	–	–
2	The SS does not respond.	–	–	–	–

11.3.5.3.3 Specific message contents

Table 11.3.5.3.3-1: Message SystemInformationBlockType1 (Preamble)

Derivation path: 36.508 table 4.4.3.2-3 Condition eCalloverIMS

Table 11.3.5.3.3-2: RRC CONNECTION REQUEST (Step 4a2, Table 11.3.5.3.2-1)

Derivation Path: TS 34.108 clause 9.1.1
Information Element	Value/remark	Comment	Condition
Establishment cause	Emergency Call

Table 11.3.5.3.3-3: CM SERVICE REQUEST (Steps 4a5 and 5b4, Table 11.3.5.3.2-1)

Derivation Path: TS 24.008 Table 9.2.11
Information Element	Value/remark	Comment	Condition
CM service type	0010	Emergency call establishment

Table 11.3.5.3.3-4: CHANNEL REQUEST (Step 5b2, Table 11.3.5.3.2-1)

Derivation Path: TS 44.018 Table 9.1.8.1
Information Element	Value/remark	Comment	Condition
Establishment cause	101	Emergency call

11.3.6 eCall Only mode / Limited service state / Call to URI for test service should not be attempted / eCall over IMS should be attempted

11.3.6.1 Test Purpose (TP)

(1)

with { UE in eCALL-INACTIVE.LIMITED-SERVICE state }

ensure that {

when { UE is requested to make an eCall to URI for test service}

then { UE does not transmit any RRCConnectionRequest message }

}

(2)

with { UE in eCALL-INACTIVE.LIMITED-SERVICE state }

ensure that {

when { UE is requested to make a manual eCall}

then { UE transmits an ATTACH REQUEST message to attach for emergency bearer services, together with a PDN CONNECTIVITY REQUEST message with ‘Request type’ set to ’emergency’ }

}

11.3.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 23.122, clauses 2

[TS 23.122 clause 2]

If the MS is in eCall only mode, it attempts to camp on a suitable cell and enters an "eCall inactive" state in which it can only attempt an eCall over IMS, or a call to a non-emergency MSISDN or URI for test or terminal reconfiguration services as specified in 3GPP TS 31.102 [40].

If the MS is in eCall only mode and is unable to find a suitable cell to camp on, it attempts to camp on an acceptable cell in limited service state, and enters an "eCall inactive" state in which it can only attempt an eCall over IMS. The signalling procedure for the release of the NAS signalling connection is initiated by the network.

11.3.6.3 Test description

11.3.6.3.1 Pre-test conditions

System Simulator:

– Cell A

– The PLMN is defined in Table 11.3.6.3.1-1.

Table 11.3.6.3.1–1: PLMN identifier

Cell	PLMN name	MCC / MNC
A	PLMN4	004 / 31

UE:

– The eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-2.

– The UE is equipped with a USIM containing values shown in Table 11.3.6.3.1-2.

Table 11.3.6.3.1-2: USIM configuration

USIM field	Value
EF_FPLMN	PLMN4

Preamble:

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

11.3.6.3.2 Test procedure sequence

Table 11.3.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	Wait 60s for the UE to camp on Cell A as an acceptable cell.	–	–	–	–
3	An eCall to URI for test service is initiated. (Note 1)	–	–	–	–
4	Check: Does UE send an RRCConnectionRequest on Cell A within 120 seconds?	–>	RRC: RRCConnectionRequest	1	F
5	A manual eCall is initiated. (Note 2)	–	–	–	–
6	Check: Does the UE transmit an RRCConnectionRequest message with ‘establishmentCause’ set to ’emergency’?	–>	RRC: RRCConnectionRequest	–	–
7	SS transmits an RRCConnectionSetup message.	<–	RRC: RRCConnectionSetup	–	–
8	Check: Does the UE transmit an ATTACH REQUEST message to attach for emergency bearer services, together with a PDN CONNECTIVITY REQUEST message with ‘Request type’ set to ’emergency?	–>	NAS: ATTACH REQUEST NAS: PDN CONNECTIVITY REQUEST	2	P
9-23	Steps 5 to 19 of the generic test procedure for IMS Emergency call establishment in EUTRA: Limited Service (TS 36.508 subclause 4.5A.5.3-1).	–	–	–	–
24-27	Release eCall over IMS using the generic procedure described in TS 34.229-1 [35] subclause C.33.	–	–	–	–
28	Void	–	–	–	–
29	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
Note 1: The request to originate an eCall to URI for test service may be performed by MMI or AT command. Note 2: The request to originate a manual eCall may be performed by MMI or AT command.

11.3.6.3.3 Specific message contents

Table 11.3.6.3.3-1: Message SystemInformationBlockType1 (Preamble)

Derivation path: 36.508 table 4.4.3.2-3 Condition eCalloverIMS

11.3.7 eCall Only mode / SRVCC Handover to CS domain / UTRAN / MSD Update / Success

11.3.7.1 Test Purpose (TP)

(1)

with { UE in eCall Only Mode and an IMS eCall is ongoing }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and an UTRA Speech RAB combination is configured for an UTRA cell }

then { UE transmits a HANDOVER TO UTRAN COMPLETE message on the utra cell }

}

11.3.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.4.3.3, TS 23.237, clauses 5.3.3, 6c.2.1, TS 23.216, clause 5.3.4.2, TS 26.267, clause 4.3, and TS 24.008, clause 5.2.4.2.

[TS 36.331, clause 5.4.3.3]

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to handover:

2> if the targetRAT-Type is set to utra or geran:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 23.237, clause 5.3.3]

The Emergency Access Transfer Function (EATF) provides IMS-based mechanisms for enabling service continuity of IMS emergency sessions and eCall over IMS. It is a function in the serving (visited if roaming) IMS network, providing the procedures for IMS emergency session anchoring and PS to CS Access Transfer. The EATF acts as a routing B2BUA which invokes third party call control (3pcc) for enablement of Access Transfer.

When supporting PS to CS DRVCC for IMS emergency, the EATF provides the following functions:

– Generates and sends an E-STN-DR to UE for session continuity procedure toward the CS domain. The E-STN-DR is used by the EATF to correlate two access legs, and is unique for each access transfer function within an EATF.

The EATF performs the session continuity when the Access Transfer request indicated by the E-STN-SR is received.

[TS 23.237, clause 6c.2.1]

Figure 6c.2.1-1 provides flow for SRVCC for IMS emergency session, when the IMS emergency session is active session.

Figure 6c.2.1-1: IMS level Call flow for SRVCC for IMS emergency session with E-STN-SR

1. MSC Server initiates the session transfer with the E-STN-SR and it includes the equipment identifier.

2. The I-CSCF routes the INVITE directly to the EATF via I5 by using similar procedures to that defined in TS 23.228 [4] for PSI based Application Server termination.

NOTE 1: The use of indirect routeing for PSI based Application Server Termination as described in TS 23.228 [4] in clause 5.7.6 cannot be used for routing the INVITE to the EATF.

3.-4. The EATF uses the E-STN-SR to determine that Access Transfer is requested. The EATF proceeds with the Access Transfer of the active session with bi-directional speech for the UE by updating the Remote Leg with the media description and other information using the Remote Leg Update procedure as specified in clause 6.3.1.5. For SRVCC session transfer of an eCall over IMS, the EATF indicates in the reINVITE that the EATF shall exclude INFO requests for any Info Packages related to eCall over IMS as defined in RFC 6086 [34] clause 5.2.2.

NOTE: Indicating an unwillingness to receive INFO requests will prevent an emergency centre/PSAP from sending an INFO message to request an updated MSD from the UE.

5. The E-CSCF forwards the Re-INVITE to the MGCF associated with the PSAP if the PSAP is located in the PSTN or CS Domain (the u-plane path is switched between the UE and the MGW) or the Re-INVITE is sent directly to an IP-capable PSAP (the u-plane path between the UE and the PSAP is switched end-to-end).

6. When session modification procedures complete, the source access leg (i.e. the access leg previously established over IMS) is released as specified in clause 6.3.1.6.

NOTE 2: If non-voice media was part of the original Multimedia emergency call session, the non-voice media will be released.

[TS 23.216, clause 5.3.4.2]

3GPP SRVCC UE is needed to perform SRVCC (see clause 3.1 for 3GPP SRVCC UE definition). The interaction between UE and E-UTRAN is described in TS 36.300 [16] and between UE and UTRAN (HSPA) is described in TS 25.331 [19].

The SRVCC UE indicates to the network that the UE is SRVCC capable when being configured for using IMS speech service supported by the home operator, e.g. the IMS Multimedia Telephony Service for bi-directional speech as described in TS 22.173 [26].

For an eCall Over IMS after handover to GERAN/UTRAN is complete, the SRVCC UE shall support in-band transfer of updated MSD according to TS 26.267 [43].

[TS 23.267, clause 4.3]

After an emergency voice call has been (automatically or manually) established, the IVS modem receiver constantly monitors the incoming signal from the speech decoder output. When prompted by a request from the PSAP operator for MSD, the IVS connects the IVS data modem transmitter to the input of the speech coder and mutes any speech from the motorist for the duration of MSD transmission to prevent it from interfering with the eCall data transmission. Alternatively, it can be the IVS that may trigger the MSD transmission. In this case, the IVS asks the PSAP to request an MSD transmission.

The first operation mode shall be referred to as the pull mode whereas the latter one is the push mode. Essentially, push mode is realized by a request from the IVS to the PSAP to pull the MSD.

The requirement about the modem to be configured in either push or pull mode is beyond the scope of this specification. Refer to clause 4.2 for a reproduction of eCall service requirements.

[TS 24.008, clause 5.2.4.2]

If the MS supports single radio PS to CS access transfer for calls in alerting state as specified in 3GPP TS 24.237 [136] subclause 12.2.3B, and the MS has a single voice media stream over the PS domain that is handed over to the CS domain via SRVCC, and the call control entity in "null" state receives an indication "MM connection establishment due to SRVCC handover", then:

– if the voice media stream is associated with a mobile originated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237 [136] subclause 12.2.3B.3.2, the call control entity of the MS shall enter the "call delivered" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call; and

…

If the MS has additional voice media streams carried over the PS domain that are handed over to the CS domain via SRVCC, the state for the transactions and the setting of the TI value and TI flag for these additional media streams is described in 3GPP TS 24.237 [136].

11.3.7.3 Test description

11.3.7.3.1 Pre-test conditions

System Simulator:

– Cell A and Cell 5.

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

UE:

– The eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-2.

Preamble:

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

11.3.7.3.2 Test procedure sequence

Table 11.3.7.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 11.3.7.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell A	Cell 5	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-60	–	The power level values are such that entering conditions for event B2 are not satisfied.
	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz	–	-88
	PCCPCH_Ec (UTRA LCR TDD)	dBm/1.28 MHz	–	-88
T1	Cell-specific RS EPRE	dBm/15kHz	-84	–	The power level values are such that entering conditions for event B2 are satisfied.
	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz	–	-64
	PCCPCH_Ec (UTRA LCR TDD)	dBm/1.28 MHz	–	-64
T2	Cell-specific RS EPRE	dBm/15kHz	Non-suitable “Off”	–
	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz	–	-64
	PCCPCH_Ec (UTRA LCR TDD)	dBm/1.28 MHz	–	-64

Table 11.3.7.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	Wait 60s for the UE to camp on Cell A as an acceptable cell.	–	–	–	–
3	A manual NG eCall is initiated. (See Note 1).	–	–	–	–
4-26	Steps 3 to 25 of the generic test procedure for eCall over IMS establishment in EUTRA: eCall only mode (TS 36.508 4.5A.27).	–	–	–	–
27	The SS transmits an RRCConnectionReconfiguration message on Cell A to setup inter-RAT measurement and reporting for event B2.	<–	RRCConnectionReconfiguration	–	–
28	The UE transmits an RRCConnectionReconfigurationComplete message on Cell A.	–>	RRCConnectionReconfigurationComplete	–	–
29	The SS changes the power level for Cell A and Cell 5 according to the row "T1" in Table 11.3.7.3.2-1.	–	–	–	–
30	The UE transmits a MeasurementReport message on Cell A to report event B2 for Cell 5.	–>	MeasurementReport	–	–
31	The SS transmits a UECapabilityEnquiry message on Cell A to request UE radio access capability information for E-UTRA and UTRA.	<–	UECapabilityEnquiry	–	–
32	The UE transmits a UECapabilityInformation message on Cell A. NOTE: The start-CS values received, should be used to configure ciphering on Cell 5.	–>	UECapabilityInformation	–	–
33	The SS transmits a MobilityFromEUTRACommand message on Cell A.	<–	MobilityFromEUTRACommand	–	–
34	Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message on Cell 5?	–>	HANDOVER TO UTRAN COMPLETE	1	P
–	EXCEPTION: In parallel to the events described in step 35 to 40 the steps specified in Table 11.3.7.3.2-3 takes place.	–	–	–	–
35	The SS transmits a SECURITY MODE COMMAND message for the CS domain on Cell 5.	<–	SECURITY MODE COMMAND	–	–
36	The UE transmits a SECURITY MODE COMPLETE message on Cell 5.	–>	SECURITY MODE COMPLETE	–	–
37	The SS transmits an UTRAN MOBILITY INFORMATION message on Cell 5 to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
38	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message on Cell 5.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
39	The SS transmits a TMSI REALLOCATION COMMAND message on Cell 5.	<–	TMSI REALLOCATION COMMAND	–	–
40	The UE transmits a TMSI REALLOCATION COMPLETE message on Cell 5.	–>	TMSI REALLOCATION COMPLETE	–	–
41	The CS traffic channel is kept alive by UE for at-least 5 seconds for in-band MSD transfer	–	–	–	–
42	SS adjusts cell levels according to row T2 of table 11.3.7.3.2-1.	–	–	–	–
–	The UE is in end state UTRA CS call.	–	–	–	–
Note 1: The request to originate a manual eCall may be performed by MMI or AT command.

Table 11.3.7.3.2-3: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a ROUTING AREA UPDATE REQUEST message on Cell 5.	–>	ROUTING AREA UPDATE REQUEST	–	–
2	The SS transmits a SECURITY MODE COMMAND message for the PS domain on Cell 5.	<–	SECURITY MODE COMMAND	–	–
3	The UE transmits a SECURITY MODE COMPLETE message on Cell 5.	–>	SECURITY MODE COMPLETE	–	–
4	The SS transmits a ROUTING AREA UPDATE ACCEPT message on Cell 5.	<–	ROUTING AREA UPDATE ACCEPT	–	–
5	The UE transmits a ROUTING AREA UPDATE COMPLETE message on Cell 5.	–>	ROUTING AREA UPDATE COMPLETE	–	–

11.3.7.3.3 Specific message contents

Table 11.3.7.3.3-1: Message SystemInformationBlockType1 (Preamble)

Derivation path: 36.508 table 4.4.3.2-3 Condition eCalloverIMS

Table 11.3.7.3.3-2: ATTACH REQUEST (preamble)

Derivation path: 36.508 Table 4.7.2-4
Information Element	Value/remark	Comment	Condition
MS network capability	SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported
Mobile station classmark 2	Any allowed value
Supported Codecs	Any allowed value

Table 11.3.7.3.3-3: RRCConnectionReconfiguration (step 27, Table 11.3.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 11.3.7.3.3-4: MeasConfig (Table 11.3.7.3.3-3)

Derivation Path: 36.508, Table 4.6.6-1, condition UTRAN
Information Element	Value/remark	Comment	Condition
MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	2 entries
measObjectId[1]	IdMeasObject-f1
measObject[1]	MeasObjectEUTRA-GENERIC(f1)
measObject[1]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
measObjectId[2]	IdMeasObject-f8
measObject[2]	MeasObjectUTRA-f8
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfig-B2-UTRA
reportConfig[1]	ReportConfigInterRAT-B2-UTRA (-72, -76)
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f8
reportConfigId[1]	IdReportConfig-B2-UTRA
}
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	2 entries		Band > 64
measObjectEUTRA-v9e0[1] SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
measObjectEUTRA-v9e0[2] SEQUENCE {}
}
}
}

Condition	Explanation
Band > 64	If band > 64 is selected

Table 11.3.7.3.3-5: MeasObjectUTRA-f8 (Table 11.3.7.3.3-4)

Derivation Path: 36.508, Table 4.6.6-3
Information Element	Value/remark	Comment	Condition
MeasObjectUTRA ::= SEQUENCE {
carrierFreq	Same downlink ARFCN as used for Cell 5
cellsToAddModList CHOICE {
cellsToAddModListUTRA-FDD SEQUENCE (SIZE (1..maxCellMeas)) OF SEQUENCE {	1 entry		UTRA-FDD
cellIndex[1]	1
physCellId[1]	PhysicalCellIdentity of Cell 5
}
cellsToAddModListUTRA-TDD SEQUENCE (SIZE (1..maxCellMeas)) OF SEQUENCE {			UTRA-TDD
cellIndex[1]	1
physCellId[1]	PhysicalCellIdentity of Cell 5
}
}
csg-allowedReportingCells-v930	Not present
}

Condition	Explanation
UTRA-FDD	UTRA FDD cell environment
UTRA-TDD	UTRA TDD cell environment

Table 11.3.7.3.3-6: MeasurementReport (step 30, Table 11.3.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5
Information Element	Value/remark	Comment	Condition
MeasurementReport ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
measurementReport-r8 SEQUENCE {
measResults SEQUENCE {
measId	1
measResultPCell SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
measResultNeighCells CHOICE {
measResultListUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {	1 entry
physCellId[1] CHOICE {
fdd	PhysicalCellIdentity of Cell 5		UTRA-FDD
tdd	PhysicalCellIdentity of Cell 5		UTRA-TDD
}
cgi-Info[1]	Not present
measResult[1] SEQUENCE {
utra-RSCP	(-5..91)
utra-EcN0	Not present
additionalSI-Info-r9	Not present
}
}
}
measResultForECID-r9	Not present
locationInfo-r10	Not present
measResultServFreqList-r10	Not present
}
}
}
}
}

Condition	Explanation
UTRA-FDD	UTRA FDD cell environment
UTRA-TDD	UTRA TDD cell environment

Table 11.3.7.3.3-7: UECapabilityEnquiry (step 31, Table 11.3.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-22
Information Element	Value/remark	Comment	Condition
UECapabilityEnquiry ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
ueCapabilityEnquiry-r8 SEQUENCE {
ue-CapabilityRequest (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {	2 entries
RAT-Type[1]	eutra
RAT-Type[2]	utra
}
}
}
}
}

Table 11.3.7.3.3-8: MobilityFromEUTRACommand (step 33, Table 11.3.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6
Information Element	Value/remark	Comment	Condition
MobilityFromEUTRACommand ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
mobilityFromEUTRACommand-r8 SEQUENCE {
cs-FallbackIndicator	False
purpose CHOICE {
handover SEQUENCE {
targetRAT-Type	utra
targetRAT-MessageContainer	HANDOVER TO UTRAN COMMAND(UTRA RRC message)
nas-SecurityParamFromEUTRA	The 4 least significant bits of the NAS downlink COUNT value
systemInformation	Not present
}
}
}
}
}
}

Table 11.3.7.3.3-9: HANDOVER TO UTRAN COMMAND (Table 11.3.7.3.3-8)

Derivation Path: 36.508, Table 4.7B.1-1, condition UTRA Speech

Table 11.3.7.3.3-10: SECURITY MODE COMMAND (step 35, Table 11.3.7.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-n
Information Element	Value/remark	Comment	Condition
Ciphering mode info	Not present

Table 11.3.7.3.3-13: ROUTING AREA UPDATE ACCEPT (step 4, Table 11.3.7.3.2-3)

Derivation path: 36.508, Table 4.7B.2-2
Information Element	Value/Remark	Comment	Condition
PDP context status	0	NSAPI(0) – NSAPI(15) is set to 0, which means that the SM state of all PDP contexts is PDP-INACTIVE

11.3.8 eCall Only mode / SRVCC Handover to CS domain / GERAN / MSD Update / Success

11.3.8.1 Test Purpose (TP)

(1)

with { UE in eCall Only Mode and an IMS eCall is ongoing }

ensure that {

when { UE receives a MobilityFromEUTRACommand message and an UTRA Speech RAB combination is configured for an UTRA cell }

then { UE transmits a HANDOVER COMPLETE message on the geran cell }

}

11.3.8.2 Conformance requirements

[TS 36.331, clause 5.4.3.3]

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to handover:

2> if the targetRAT-Type is set to utra or geran:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

[TS 23.237, clause 5.3.3]

When supporting PS to CS DRVCC for IMS emergency, the EATF provides the following functions:

The EATF performs the session continuity when the Access Transfer request indicated by the E-STN-SR is received.

[TS 23.237, clause 6c.2.1]

Figure 6c.2.1-1 provides flow for SRVCC for IMS emergency session, when the IMS emergency session is active session.

Figure 6c.2.1-1: IMS level Call flow for SRVCC for IMS emergency session with E-STN-SR

1. MSC Server initiates the session transfer with the E-STN-SR and it includes the equipment identifier.

2. The I-CSCF routes the INVITE directly to the EATF via I5 by using similar procedures to that defined in TS 23.228 [4] for PSI based Application Server termination.

NOTE 1: The use of indirect routeing for PSI based Application Server Termination as described in TS 23.228 [4] in clause 5.7.6 cannot be used for routing the INVITE to the EATF.

3 – 4. The EATF uses the E-STN-SR to determine that Access Transfer is requested. The EATF proceeds with the Access Transfer of the active session with bi-directional speech for the UE by updating the Remote Leg with the media description and other information using the Remote Leg Update procedure as specified in clause 6.3.1.5. For SRVCC session transfer of an eCall over IMS, the EATF indicates in the reINVITE that the EATF shall exclude INFO requests for any Info Packages related to eCall over IMS as defined in RFC 6086 [34] clause 5.2.2.

NOTE: Indicating an unwillingness to receive INFO requests will prevent an emergency centre/PSAP from sending an INFO message to request an updated MSD from the UE.

6. When session modification procedures complete, the source access leg (i.e. the access leg previously established over IMS) is released as specified in clause 6.3.1.6.

NOTE 2: If non-voice media was part of the original Multimedia emergency call session, the non-voice media will be released.

[TS 23.216, clause 5.3.4.2]

For an eCall Over IMS after handover to GERAN/UTRAN is complete, the SRVCC UE shall support in-band transfer of updated MSD according to TS 26.267 [43].

[TS 23.267, clause 4.3]

The first operation mode shall be referred to as the pull mode whereas the latter one is the push mode. Essentially, push mode is realized by a request from the IVS to the PSAP to pull the MSD.

The requirement about the modem to be configured in either push or pull mode is beyond the scope of this specification. Refer to clause 4.2 for a reproduction of eCall service requirements.

[TS 24.008, clause 5.2.4.2]

…

11.3.8.3 Test description

11.3.8.3.1 Pre-test conditions

System Simulator:

– Cell A and Cell 24.

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

UE:

– The eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-2.

Preamble:

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

11.3.8.3.2 Test procedure sequence

Table 11.3.8.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 11.3.8.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell A	Cell 24	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	–	The power level values are such that entering conditions for event B2 are not satisfied.
T0	RSSI	dBm	–	-85
T1	Cell-specific RS EPRE	dBm/15kHz	-85	–	The power level values are such that entering conditions for event B2 are satisfied.
T1	RSSI	dBm	–	-65
T2	Cell-specific RS EPRE	dBm/15kHz	Non-suitable “Off”	–
T2	RSSI	dBm	–	-65

Table 11.3.8.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	Wait 60s for the UE to camp on Cell A as an acceptable cell.	–	–	–	–
3	A manual NG eCall is initiated. (See Note 1).	–	–	–	–
4-26	Steps 3 to 25 of the generic Test Procedure for eCall over IMS establishment in EUTRA: eCall only mode (TS 36.508 4.5A.27).	–	–	–	–
27	The SS transmits an RRCConnectionReconfiguration message on Cell A to setup inter-RAT measurement and reporting for event B2.	<–	RRCConnectionReconfiguration	–	–
28	The UE transmits an RRCConnectionReconfigurationComplete message on Cell A.	–>	RRCConnectionReconfigurationComplete	–	–
29	The SS changes the power level for Cell A and Cell 24 according to the row "T1" in Table 11.3.8.3.2-1.	–	–	–	–
30	The UE transmits a MeasurementReport message on Cell A to report event B2 for Cell 24.	–>	MeasurementReport	–	–
31	The SS transmits a MobilityFromEUTRACommand message on Cell A.	<–	MobilityFromEUTRACommand	–	–
32	Check: Does the UE transmit a HANDOVER COMPLETE message on cell 24?	–>	HANDOVER COMPLETE	1	P
33	The UE transmits a GPRS SUSPENSION REQUEST message	–>	GPRS SUSPENSION REQUEST	–	–
34	The SS transmits a TMSI REALLOCATION COMMAND message.	<–	TMSI REALLOCATION COMMAND	–	–
35	The UE transmits a TMSI REALLOCATION COMPLETE message.	–>	TMSI REALLOCATION COMPLETE	–	–
36	SS adjusts cell levels according to row T2 of table 11.3.8.3.2-1.	–	–	–	–
37	The CS traffic channel is kept alive by UE for at least 5 seconds for In-band MSD transfer	–	–	–	–
38-52	Steps 20 to 34 of the generic test procedure described in TS 36.508 subclause 6.4.3.8.1 are performed on Cell 24. NOTE: Call is released and UE performs a RAU procedure.	–	–	–	–
Note 1: The request to originate a manual eCall may be performed by MMI or AT command.

11.3.8.3.3 Specific message contents

Table 11.3.8.3.3-1: Message SystemInformationBlockType1 (Preamble)

Derivation path: 36.508 table 4.4.3.2-3 Condition eCalloverIMS

Table 11.3.8.3.3-2: ATTACH REQUEST (preamble)

Derivation path: 36.508 Table 4.7.2-4
Information Element	Value/remark	Comment	Condition
MS network capability	SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported
Mobile station classmark 2	Any allowed value
Supported Codecs	Any allowed value

Table 11.3.8.3.3-3: RRCConnectionReconfiguration (step 27, Table 11.3.8.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 11.3.8.3.3-4: MeasConfig (Table 11.3.8.3.3-3)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition GERAN
Information Element	Value/Remark	Comment	Condition
measurementConfiguration ::= SEQUENCE {
measObjectToAddModifyList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	2 entries
measObjectId[1]	IdMeasObject-f11
measObject[1]	MeasObjectGERAN-GENERIC(f11)
measObjectId[2]	IdMeasObject-f1
measObject[2]	MeasObjectEUTRA-GENERIC(f1)
measObject[2]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
}
reportConfigToAddModifyList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfigInterRAT-B2-GERAN
reportConfig[1]	ReportConfigInterRAT-B2-GERAN (-69, -75)
}
measIdToAddModifyList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f11
reportConfigId[1]	IdReportConfigInterRAT-B2-GERAN
}
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	2 entries		Band > 64
measObjectEUTRA-v9e0[1] SEQUENCE {}
measObjectEUTRA-v9e0[2] SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
}
}

Condition	Explanation
Band > 64	If band > 64 is selected

Table 11.3.8.3.3-5: MeasurementReport (step 30, Table 11.3.8.3.2-2)

Derivation Path: 36.508, table 4.6.1-5
Information Element	Value/remark	Comment	Condition
MeasurementReport ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
measurementReport-r8 SEQUENCE {
measResults SEQUENCE {
measId	1
measResultServCell SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
measResultNeighCells CHOICE {
measResultListGERAN SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {	1 entry
physCellId	PhysicalCellIdentity of Cell 24
cgi-Info[1]	Not present
measResult[1] SEQUENCE {
rssi	The value of rssi is present but contents not checked
}
}
}
}
}
}
}
}

Table 11.3.8.3.3-6: MobilityFromEUTRACommand (step 31, Table 11.3.8.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6
Information Element	Value/remark	Comment	Condition
MobilityFromEUTRACommand ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
mobilityFromEUTRACommand-r8 SEQUENCE {
cs-FallbackIndicator	False
purpose CHOICE{
handover SEQUENCE {
targetRAT-Type	GERAN
targetRAT-MessageContainer	HANDOVER COMMAND(GERAN RR message) , see Table 11.3.8.3.3-7
nas-SecurityParamFromEUTRA	The 4 least significant bits of the NAS downlink COUNT value
systemInformation	Not present
}
}
}
}
}
}

Table 11.3.8.3.3-7: HANDOVER COMMAND (Table 11.3.8.3.3-6)

Derivation Path: 51.010, Table 40.2.4.33
Information Element	Value/remark	Comment	Condition
Cell Description
Network Colour Code	1
Base Station Colour Code	5
BCCH Carrier Number	The BCCH Carrier ARFCN as per table in clause 40.1.1 of 51.010-1.
Description of the First Channel, after time
Channel Description
Channel Type and TDMA offset	TCH/F + ACCH’s
Timeslot Number	Chosen arbitrarily, but not Zero.
Training Sequence Code	Same as the BCCH
Hopping channel	Single RF channel
ARFCN	The first ARFCN in the cell allocation as per table in clause 40.2.1.1.1 of 51.010-1
Cipher Mode Setting	1001xxxy	See TS 44.018 §9.1.15.10 xxx – px_GSM_CipherAlg y – px_GSM_CipheringOnOff

Table 11.3.8.3.3-10: ROUTING AREA UPDATE ACCEPT (step 51, Table 11.3.8.3.2-2)

Derivation path: 36.508, Table 4.7B.2-2
Information Element	Value/Remark	Comment	Condition
PDP context status	0	NSAPI(0) – NSAPI(15) is set to 0, which means that the SM state of all PDP contexts is PDP-INACTIVE