21 eCall over IMS

34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

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

For the eCall over IMS test cases, the default USIM settings are specified in TS 36.508 [94] clause 4.9.3.5.

21.1 eCall over IMS / Manual initiation / Normal registration / Emergency registration / Success / 200 OK with ACK

21.1.1 Definition

Test to verify that the UE can correctly perform eCall over IMS when initiated manually and that the SS releases the call after 200 OK with ACK is received. The process consists of emergency registration and MSD included in INVITE during call setup.

21.1.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.1]:

If the upper layers request establishment of an IMS emergency call of the manually initiated eCall type of emergency service, the service URN shall be "urn:service:sos.ecall.manual" as specified in RFC 8147 [244].

If the upper layers request establishment of an IMS emergency call of the automatically initiated eCall type of emergency service, the service URN shall be "urn:service:sos.ecall.automatic" as specified in RFC 8147 [244].

NOTE: The manually initiated eCall type of emergency service is used when the eCall IMS emergency session is invoked with user input. The automatically initiated eCall type of emergency service is used if the eCall IMS emergency session is invoked without user input.

[TS 24.229, clause 5.1.6.11.2]:

If the upper layers request establishment of an IMS emergency call of the automatically initiated eCall type of emergency service or of the manually initiated eCall type of emergency service and if allowed by IP-CAN specific annex, the UE shall send an INVITE request as specified in the procedures in subclause 5.1.6.8 with the following additions:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

a) insert a multipart/mixed body containing an "application/EmergencyCallData.eCall.MSD" MIME body part as defined in RFC 8147 [244], containing the MSD not exceeding 140 bytes and encoded in binary ASN.1 PER as specified in CEN EN 15722:2015 [245] and include a Content-Disposition header field with a "handling" header field parameter with an "optional" value, as described in RFC 3261 [26];

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

…

2) if the UE receives a 200 (OK) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful;

Reference(s)

3GPP TS 24.229 [10], clauses 5.1.6.11.1 and 5.1.6.11.2.

21.1.3 Test purpose

1) To verify that the UE can correctly register to IMS emergency services and initiate an eCall over IMS in manual mode when UE is registered to IMS non-emergency services, according to TS 24.229 [10] clause 5.1.6.11.1;

2) To verify that the UE sends a correctly composed initial INVITE request for eCall over IMS and will complete the eCall session setup after receiving 200 OK with ACK, according to 3GPP TS 24.229 [10] clause 5.1.6.11.2.

21.1.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application with eCall subscription on UICC. The UE has discovered P-CSCF, and registered to IMS services.

SS is configured with the IMSI within the USIM application, the home domain name, public and private user identities together with the shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) that is configured on the UICC card equipped into the UE. SS is listening to SIP default port 5060 for both UDP and TCP protocols. SS is able to perform AKAv1-MD5 authentication algorithm for that IMPI, according to 3GPP TS 33.203 [14] clause 6.1 and RFC 3310 [17].

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Manual eCall over IMS initiated at UE

2) Emergency registration according to C.20 is executed

3) SS waits for UE to send an INVITE request.

4) SS sends 200 OK with ACK.

5) Void

6)-9) MT Call release according to steps 1-4 of procedure C.33.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			UE is triggered to initiate a manual eCall
2-5			Steps 1-4 defined in C.20	IMS emergency registration. Referred from 36.508 [94] table 4.5A.26.3-1 for a UE with E-UTRA support.
6-8			Steps 1-3 defined in C.47	eCall setup
9-12			Steps 1-4 defined in C.33	The SS releases the call

Specific Message Contents

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A20.

Step 7 as specified in annex C.47, which is referring to A.3.1 default message content of 200 OK with condition A13.

BYE (Step 9)

Use the default message “BYE” in annex A.2.8.

200 OK for BYE (Step 10)

Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1.

21.1.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for manual eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

21.2 eCall over IMS / Automatic initiation / Normal registration / Emergency registration / Success / 200 OK with ACK

21.2.1 Definition

Test to verify that the UE can correctly perform eCall over IMS when initiated automatically and that the SS releases the call after 200 OK with ACK is received. The process consists of emergency registration and MSD included in INVITE during call setup.

21.2.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.1]:

[TS 24.229, clause 5.1.6.11.2]:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

…

2) if the UE receives a 200 (OK) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful;

Reference(s)

3GPP TS 24.229 [10], clauses 5.1.6.11.1 and 5.1.6.11.2.

21.2.3 Test purpose

1) To verify that the UE can correctly register to IMS emergency services and initiate an eCall over IMS in automatic mode when UE is registered to IMS non-emergency services, according to TS 24.229 [10] clause 5.1.6.11.1;

21.2.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall subscription. The UE has discovered P-CSCF, and registered to IMS services.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Automatic eCall over IMS initiated at UE

2) Emergency registration according to C.20 is executed

3) SS waits for UE to send an INVITE request.

4) SS sends 200 OK with ACK.

5) Void

6)-9) MT Call release according to steps 1-4 of procedure C.33.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			UE is triggered to initiate an automatic eCall
2-5			Steps 1-4 defined in C.20	IMS emergency registration. Referred from 36.508 [94] table 4.5A.26.3-1 for a UE with E-UTRA support.
6-8			Steps 1-3 defined in C.47	eCall setup
9-12			Steps 1-4 defined in C.33	The SS releases the call

Specific Message Contents

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A21.

Step 7 as specified in annex C.47, which is referring to A.3.1 default message content of 200 OK with condition A13.

BYE (Step 9)

Use the default message “BYE” in annex A.2.8.

200 OK for BYE (Step 10)

Use the default message “200 OK for other requests than REGISTER or SUBSCRIBE” in annex A.3.1.

21.2.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for automatic eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

21.3 eCall over IMS / Manual initiation / MSD transfer Failure / UE performs eCall in CS domain after Timer expiry / UTRAN or GERAN

21.3.1 Definition

Test to verify that the UE performs eCall in CS domain after MSD transfer failed during manual eCall Initiation. This process is described in 3GPP TS 24.229 [10].

21.3.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.3]:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

1) if the UE receives a 200 (OK) response to the INVITE request not containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall send the MSD using audio media stream encoded as described in 3GPP TS 26.267 [9C];

2) if the UE receives a 200 (OK) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful;

3) if the UE receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful and shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B]; and

4) in all other cases, the UE shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B].

Reference(s)

3GPP TS 24.229 [10], clause 5.1.6.11.2.

21.3.3 Test purpose

1) To verify that when the UE transmits eCall MSD with SIP INVITE, it waits for timer expiry to receive 200OK from network according to 3GPP TS 24.229 [10] 5.1.6.11.1 and 5.1.6.11.2

2) To verify that the UE make eCall over CS domain after timer expiry

21.3.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall subscription. UE has discovered P-CSCF, and registered to IMS services.

– with 2 cells: as in TS 36.508

– E-UTRAN cell A

– if px_RATComb_Tested = EUTRA_UTRA, cell 5

– if px_RATComb_Tested = EUTRA_GERAN, GERAN cell 24

– Cell A power level is set as “serving cell” and cell 24/cell 5 power level is set as “suitable cell”

Note: Setting px_RATComb_Tested = EUTRA_Only is not allowed.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Manual eCall initiated at UE.2-5) Executes the procedures described in TS 36.508 [94] table 4.5A.26.3-1 steps 2 to 15 and parallel behaviour steps 1-4 for EPS emergency bearer context activation, and subsequent IMS emergency registration

6) SS waits for UE to send an INVITE request.

7) SS waits until expiry of emerg-request timer(15 seconds) so that transfer of MSD transfer fails

8-9) UE performs domain selection to a cell supporting CS domain (UTRAN/GERAN) based on capability supported and initiates CS domain emergency call with MM registration if necessary. CS eCall is established. CS eCall is maintained for at least 5 seconds and then the call is cleared by SS.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1	–		Make the UE attempt manual eCall Call
2-5	–		Step 1-4 defined in C.20	EPS emergency bearer context activation and subsequent IMS emergency registration by the UE. Referred from 36.508 [94] table 4.5A.26.3-1 for a UE with E-UTRA support.
6	–		Step1 defined in C.47	UE sends INVITE along with initial SDP offer and MSD
7	–			SS waits until expiry of emerg-request timer(15 seconds) so that transfer of MSD fails
–	–		EXCEPTION: The UE performs a domain selection for the emergency call and within 2 seconds after step 7 the UE may transmit EXTENDED SERVICE REQUEST
8a1	->		EXTENDED SERVICE REQUEST	If CS Fallback is performed, the UE sends service request with Service type set to mobile originating CS fallback emergency call as defined in 24.301 clause 9.9.3.27
8a2	<-		SS releases the RRC connection	SS waits for two seconds before sending RRC connection release. UE state is changed from RRC_CONNECTED to RRC_IDLE, and UE is redirected to UTRAN/GERAN (if supported)
–	–		EXCEPTION: Either step 9a1 or 9b1 is performed, depending on the value of px_RATComb_Tested
9a1	–		IF px_RATComb_Tested = EUTRA_UTRA UE performs CS fallback or cell reselection to a cell supporting CS domain (UTRAN) and performs eCall establishment in CS domain together with MM/GMM registration	NOTE 3: RAU procedure can take place in parallel to emergency CS call.
9a2	–		eCall is maintained for at least 5 seconds
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP re-registration defined in Annex C.46 of TS 34.229-1 can take place
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 can take place	The optional de-registration happens in parallel with the CS call release procedures.
9a3	–		SS configures cell A as a “non-suitable cell”
9a4	–		eCall is cleared by SS
9b1	—		IF px_RATComb_Tested = EUTRA_GERAN UE performs CS fallback or cell reselection to a cell supporting CS domain (GERAN cell) and performs eCall establishment in CS domain
9b2	–		eCall is maintained for at least 5 seconds
9b3	–		SS configures cell A as a “non-suitable cell”
9b4	–		eCall is cleared by SS
9b5	–		UE performs MM/GMM registration

Specific Message Contents

Step 2 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A20.

RRCConnectionRelease (step 8a2)

Derivation Path: 36.508 Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
utra-FDD	Downlink UARFCN of cell 5		UTRA-FDD
_utra-TDD	Downlink UARFCN of cell 5		UTRA-TDD
geran	ARFCN of cell 24		GERAN
}
}

ROUTING AREA UPDATE ACCEPT (Step 9b5)

Use the default message with the following specific contents

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

21.3.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for manual eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

In step 9a1 or 9b1, UE shall send an EMERGENCY SETUP message with the Service Category IE bit 6 = 1 and all other bits are set to 0.

21.4 eCall over IMS / Manual initiation / MSD transfer and 200 OK with ACK / SIP INFO request for MSD Update / Success

21.4.1 Definition

Test to verify that the UE retry MSD transfer after MSD transfer failed during manual eCall Initiation. This process is described in 3GPP TS 24.229 [10].

21.4.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.3]:

During an emergency session established for eCall type of emergency service as described in subclause 5.1.6.11.2, if the UE receives an INFO request with:

1) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

2) a multipart/mixed body including:

a) an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] containing a "request" element with an "action" attribute set to "send-data" and a "datatype" attribute set to "eCall.MSD"; and

b) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.Control+xml" MIME body part; and

3) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body;

the UE shall proceed as follows:

1) if the UE is able to provide an updated MSD, the UE shall send an INFO request containing:

a) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

b) a multipart/mixed body including:

i) an "application/EmergencyCallData.eCall.MSD" MIME body part as defined in RFC 8147 [244] containing the MSD not exceeding 140 bytes and encoded in binary ASN.1 as specified in CEN EN 15722:2015 [245]; and

ii) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.eCall.MSD" MIME body part; and

c) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body; and

2) if the UE is not able to provide an updated MSD, the UE shall send an INFO request containing:

a) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

b) a multipart/mixed body including:

i) an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

– a "ref" attribute set to the Content-ID of the "application/EmergencyCallData.Control+xml" MIME body part in the INFO request received by the UE; and

– an "actionResult" child element containing:

A) an "action" attribute set to "send-data";

B) a "success" attribute set to "false"; and

C) a "reason" attribute set to an appropriate value as defined in RFC 8147 [244]; and

ii) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.Control+xml" MIME body part; and

c) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body.

NOTE: Further content for the INFO request is as defined in RFC 8147 [244].

Reference(s)

3GPP TS 24.229 [10], clause 5.1.6.11.2.

21.4.3 Test purpose

1) To verify that the UE transmits eCall MSD with SIP INVITE for eCall over IMS in manual mode and receives corresponding 200 OK with ACK.

2) To verify that PSAP uses a SIP INFO with correct FROM-header to request an updated MSD and UE ACK the SIP INFO with a 200 OK.

3) UE sends updated MSD in a SIP INFO with correct Request-URI and To-header. PSAP ACK the updated MSD with 200 OK.

21.4.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall subscription. UE has discovered P-CSCF, and registered to IMS services.

SS is configured with the shared secret key of IMS AKA algorithm, related to the IMS private user identity (IMPI) configured on the UICC card equipped into the UE. SS has performed AKAv1-MD5 authentication with the UE and accepted the registration.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Manual eCall initiated at UE.

2) Emergency registration according to C.20 is executed

3) SS waits for UE to send an INVITE request.

4) SS sends with 200 OK.

5) SS waits for ACK.

6) SS sends INFO request to transfer MSD.

7) SS expects and receives 200 OK.

8) SS expects and receives INFO request from the UE with MSD contents.

9) SS responds with 200 OK for INFO request from UE.

10) SS sends BYE to the UE.

11) SS expects and receives 200 OK for BYE from the UE.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			Make the UE attempt manual eCall
2-5			Steps 1-4 defined in C.20	IMS emergency registration. Referred from 36.508 [94] table 4.5A.26.3-1 for a UE with E-UTRA support.
6-12			Steps 1-7 defined in C.47	eCall setup
13	🡨		BYE	The SS sends BYE to release the call.
14	🡪		200 OK	The UE sends 200 OK for the BYE request and ends the call.

Specific Message Contents:

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A20.

Step 7 as specified in annex C.47, which is referring to A.3.1 default message content of 200 OK with condition A13.

21.4.5 Test requirements

The UE shall send requests and responses as described in clause 21.4.4.

21.5 eCall over IMS / Automatic initiation / MSD transfer and 200 OK with ACK / SIP INFO request for MSD Update / Success

21.5.1 Definition

Test to verify that the UE updates MSD successfully after automatic eCall established using SIP INFO procedure. This process is described in 3GPP TS 24.229 [10].

21.5.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.3]:

During an emergency session established for eCall type of emergency service as described in subclause 5.1.6.11.2, if the UE receives an INFO request with:

1) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

2) a multipart/mixed body including:

b) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.Control+xml" MIME body part; and

3) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body;

the UE shall proceed as follows:

1) if the UE is able to provide an updated MSD, the UE shall send an INFO request containing:

a) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

b) a multipart/mixed body including:

ii) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.eCall.MSD" MIME body part; and

c) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body; and

2) if the UE is not able to provide an updated MSD, the UE shall send an INFO request containing:

a) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

b) a multipart/mixed body including:

i) an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

– a "ref" attribute set to the Content-ID of the "application/EmergencyCallData.Control+xml" MIME body part in the INFO request received by the UE; and

– an "actionResult" child element containing:

A) an "action" attribute set to "send-data";

B) a "success" attribute set to "false"; and

C) a "reason" attribute set to an appropriate value as defined in RFC 8147 [244]; and

ii) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.Control+xml" MIME body part; and

c) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body.

NOTE: Further content for the INFO request is as defined in RFC 8147 [244].

Reference(s)

3GPP TS 24.229 [10], clause 5.1.6.11.2

21.5.3 Test Purpose

1) To verify that the UE transmits eCall MSD with SIP INVITE for eCall over IMS in automatic mode and receives 200 OK with ACK.

2) To verify that PSAP uses a SIP INFO with correct FROM-Header to request an updated MSD and UE ACK the SIP INFO with a 200 OK.

3) UE sends updated MSD in a SIP INFO with correct Request-URI and To-header. PSAP ACK the updated MSD with 200 OK.

21.5.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall subscription. UE has discovered P-CSCF, and registered to IMS services.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Automatic eCall over IMS initiated at UE

2-5) UE executes the procedures described in TS 36.508 [94] table 4.5A.26.3-1 steps 2 to 15 and parallel behaviour steps 1-4 for EPS emergency bearer context activation, and subsequent IMS emergency registration,

6-12) eCall is established successfully and MSD transferred successfully using INFO procedure as defined in C.47

13) SS sends BYE to the UE

14) SS expects and receives 200 OK for BYE from the UE

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			Make the UE to initiate automatic eCall
2-5			Steps 1-4 defined in C.20	EPS emergency bearer context activation and subsequent IMS emergency registration by the UE. Referred from 36.508 [94] table 4.5A.26.3-1 for a UE with E-UTRA support.
6-12			Steps 1-7 defined in C.47	eCall Setup and MSD transfer using INFO message
13	🡨		BYE	The SS sends BYE to release the call.
14	🡪		200 OK	The UE sends 200 OK for the BYE request and ends the call.

Specific Message Contents:

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A21.

Step 7 as specified in annex C.47, which is referring to A.3.1 default message content of 200 OK with condition A12 and A13.

21.5.5 Test requirements

UE shall update MSD as defined in steps 11-12.

21.6 eCall over IMS / Automatic initiation / MSD transfer and 200 OK with ACK / SIP INFO request for unsupported MSD / UE indicates unsuccessful in SIP INFO

21.6.1 Definition

Test to verify that the UE sends SIP INFO with correct contents as a response to SIP INFO with unsupported MSD transfer upon automatic eCall Initiation. This process is described in 3GPP TS 24.229 [10].

21.6.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.3]:

During an emergency session established for eCall type of emergency service as described in subclause 5.1.6.11.2, if the UE receives an INFO request with:

1) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

2) a multipart/mixed body including:

b) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.Control+xml" MIME body part; and

3) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body;

the UE shall proceed as follows:

1) if the UE is able to provide an updated MSD, the UE shall send an INFO request containing:

a) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

b) a multipart/mixed body including:

ii) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.eCall.MSD" MIME body part; and

c) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body; and

2) if the UE is not able to provide an updated MSD, the UE shall send an INFO request containing:

a) an Info-Package header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244];

b) a multipart/mixed body including:

i) an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

– a "ref" attribute set to the Content-ID of the "application/EmergencyCallData.Control+xml" MIME body part in the INFO request received by the UE; and

– an "actionResult" child element containing:

A) an "action" attribute set to "send-data";

B) a "success" attribute set to "false"; and

C) a "reason" attribute set to an appropriate value as defined in RFC 8147 [244]; and

ii) a Content-Disposition header field set to "By-Reference" associated with the "application/EmergencyCallData.Control+xml" MIME body part; and

c) a Content-Disposition header field set to "Info-Package" associated with the multipart/mixed body.

NOTE: Further content for the INFO request is as defined in RFC 8147 [244].

Reference(s)

3GPP TS 24.229 [10], clause 5.1.6.11.2

21.6.3 Test purpose

1) To verify that the UE transmits eCall MSD with SIP INVITE for eCall over IMS in automatic mode and receives 200 OK with ACK.

2) To verify that PSAP uses a SIP INFO with correct FROM-Header to request an unsupported MSD and UE ACK the SIP INFO with a 200 OK.

3) UE responds with SIP INFO with correct contents with indication of unsuccessful transfer. PSAP returns 200 OK.

21.6.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall subscription. UE has discovered P-CSCF, and registered to IMS services.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Automatic eCall over IMS initiated at UE

6-7) eCall is established successfully

8-11) Execute MSD transfer procedure as defined in Annex C.47 from steps 4-7

12) SS sends BYE to the UE

13) SS expects and receives 200 OK for BYE from the UE

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			Make the UE attempt Automatic eCall
2-5			Step 1-4 defined in C.20	EPS emergency bearer context activation and subsequent IMS emergency registration by the UE. Referred from 36.508 [94] table 4.5A.26.3-1 for a UE with E-UTRA support.
6-7A			Steps 1-3 defined in C.47	eCall over IMS initiated automatically. Referred from 36.508 [94] table 4.5A.26.3-1 for a UE with E-UTRA support.
8-11			Steps 4-7 defined in C.47	eCall over IMS initiated automatically. Referred from 36.508 [94] table 4.5A.26 for a UE with E-UTRA support.
12	🡨		BYE	The SS sends BYE to release the call.
13	🡪		200 OK	The UE sends 200 OK for the BYE request and ends the call.

NOTE: The default messages contents in annex A are used with condition "IMS security" or "GIBA" when applicable

Specific Message Contents:

Step 6 as specified in Annex C.47, which is referring to A.2.1 default message content of INVITE with condition A21.

Step 7 as specified in Annex C.47, which is referring to A.3.1 default message content of 200 OK with condition A12 and A13.

Step 8 as specified in Annex C.47 except datatype attribute with the value ‘eCall.invalidMSD’ in message body.

Step 10 as specified in Annex C.47, which is referring to A.2.19 default message content of MO INFO with condition A4.

21.6.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for automatic eCall over IMS.

In step 10, UE shall transmit MO INFO with ‘success’ attribute set to “false” in message body.

21.7 to 21.12 Void

21.13 eCall only mode / Manual initiation / Emergency registration / Abnormal case / IM CN sends a 486 (Busy Here) / UE performs eCall in CS domain / UTRAN or GERAN

21.13.1 Definition

Test to verify that on reception of reject cause 486 Busy here for a manually initiated INVITE for eCall over IMS, UE initiates the eCall in supported CS domain over UTRAN or GERAN.

21.13.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.1]:

[TS 24.229, clause 5.1.6.11.2]:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

…

3) if the UE receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful and shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B]; and

4) in all other cases, the UE shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B].

Reference(s)

3GPP TS 24.229 [10], clauses 5.1.6.11.1 and 5.1.6.11.2.

21.13.3 Test purpose

1) To verify that the UE is able to handle 486 (Busy here) SIP error message for a manually initiated INVITE for eCall over IMS; and

2) To verify that the UE is able to establish legacy eCall in CS domain in UTRAN or GERAN system after receiving 486 (Busy here) SIP error message.

21.13.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall Only subscription. UE is switched on not registered to IMS services.

The SS is configured:

– with 2 cells: as in TS 36.508 [94]

– E-UTRAN cell A

– if px_RATComb_Tested = EUTRA_UTRA, cell 5

– if px_RATComb_Tested = EUTRA_GERAN, GERAN cell 24

– Cell A power level is set as “serving cell” and cell 24/cell 5 power level is set as “suitable cell”

NOTE: Setting px_RATComb_Tested = EUTRA_Only is not allowed.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Manual eCall over IMS initiated at UE

1A-1H) IMS registration according to C.2 is executed.

2-5) IMS Emergency registration according to C.20 is executed.

6) SS waits for UE to send an INVITE request.

7) SS sends 486 Busy here.

8-9) UE performs domain selection to a cell supporting CS domain (UTRAN/GERAN) based on capability supported and initiates CS domain emergency call with MM registration if necessary. CS eCall is established and maintained for 5 seconds and then the call is cleared by SS.

Expected sequence:

Step	Direction		Message	Comment
	UE	SS
1	–		UE is triggered to initiate a manual eCall	Step 2 in generic procedure 36.508 [94] table 4.5A.27.3-1.
2-5	–		Steps 1-4 defined in Annex C.20	Steps 19 to 25 in generic procedure 36.508 [94] table 4.5A.27.3-1. UE establishes the emergency PDN and performs IMS emergency registration.
6	–		Step 1 defined in C.47	eCall setup is initiated.
7	<-		486 Busy here	The SS sends 486 Busy here
	–		EXCEPTION: The UE performs a domain selection for the emergency call and within 2 seconds of step 7 the UE may transmit EXTENDED SERVICE REQUEST
8a1	🡪		EXTENDED SERVICE REQUEST	If CS Fallback is performed, the UE sends service request with Service type set to mobile originating CS fallback emergency call as defined in 24.301 clause 9.9.3.27
8a2	–		SS releases the RRC connection	SS waits for two seconds before sending RRC connection release. UE state is changed from RRC_CONNECTED to RRC_IDLE, and UE is redirected to UTRAN/GERAN (if supported)
–	–		EXCEPTION: Either step 9a1 or 9b1 is performed, depending on the value of px_RATComb_Tested
9a1	–		IF px_RATComb_Tested = EUTRA_UTRA UE performs domain selection to a cell supporting CS domain (UTRAN) and performs eCall establishment in CS domain together with MM registration	NOTE: RAU procedure can take place in parallel to normal CS call.
9a2	–		SS configures cell A as a “non-suitable cell”
9a3	–		eCall is maintained for 5 seconds
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP re-registration defined in Annex C.46 of TS 34.229-1 can take place
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 can take place	The optional de-registration happens in parallel with the CS call release procedures.
9a4	–		eCall is cleared by SS
9b1	–		IF px_RATComb_Tested = EUTRA_GERAN UE performs domain selection to a cell supporting CS domain (GERAN cell) and performs eCall establishment in CS domain
9b2	–		SS configures cell A as a “non-suitable cell”
9b3	–		eCall is maintained for 5 seconds
9b4	–		eCall is cleared by SS
9b5	–		UE performs MM/GMM registration

Specific Message Contents

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A20

Step 7 486 Busy Here message as in Annex A.2.21

RRCConnectionRelease (step 8a2)

Derivation Path: 36.508 Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
utra-FDD	Downlink UARFCN of cell 5		UTRA-FDD
_utra-TDD	Downlink UARFCN of cell 5		UTRA-TDD
geran	ARFCN of cell 24		GERAN
}
}

ROUTING AREA UPDATE ACCEPT (Step 9b5)

Use the default message with the following specific contents

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

21.13.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for manual eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

In step 9a1 or 9b1, UE shall send an EMERGENCY SETUP message with the Service Category IE bit 6 = 1 and all other bits are set to 0.

21.14 eCall only mode / Automatic initiation / Emergency registration / Abnormal case / IM CN sends a 486 (Busy Here) / UE performs eCall in CS domain / UTRAN or GERAN

21.14.1 Definition

Test to verify that on reception of reject cause 486 Busy here for automatically initiated INVITE for eCall over IMS, UE initiates the eCall in supported CS domain over UTRAN or GERAN.

21.14.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.1]:

[TS 24.229, clause 5.1.6.11.2]:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

…

3) if the UE receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful and shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B]; and

4) in all other cases, the UE shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B].

Reference(s)

3GPP TS 24.229 [10], clauses 5.1.6.11.1 and 5.1.6.11.2.

21.14.3 Test purpose

1) To verify that the UE is able to handle 486 (Busy here) SIP error message for an Automatically initiated INVITE for eCall over IMS; and

2) To verify that the UE is able to establish legacy eCall in CS domain in UTRAN or GERAN system after receiving 486 (Busy here) SIP error message.

21.14.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall Only subscription. The UE is switched on not registered to IMS services.

The SS is configured:

– with 2 cells: as in TS 36.508 [94]

– E-UTRAN cell A

– if px_RATComb_Tested = EUTRA_UTRA, cell 5

– if px_RATComb_Tested = EUTRA_GERAN, GERAN cell 24

– Cell A power level is set as “serving cell” and cell 24/cell 5 power level is set as “suitable cell”

NOTE: Setting px_RATComb_Tested = EUTRA_Only is not allowed.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Automatic eCall over IMS is initiated at the UE

1A-1H) IMS registration according to C.2 is executed.

2-5) Emergency registration according to C.20 is executed.

6) SS waits for UE to send an INVITE request

7) SS sends 486 Busy here.

8-9) UE performs domain selection to a cell supporting CS domain (UTRAN/GERAN) based on capability supported and initiates CS domain emergency call with MM registration if necessary. CS eCall is established and maintained for 5 seconds and then the call is cleared by SS.

Expected sequence:

Step	Direction		Message	Comment
	UE	SS
1	–		UE is triggered to initiate an automatic eCall	Step 2 in generic procedure 36.508 [94] table 4.5A.27.3-1.
1A-1H	–		Steps 4-11 in Annex C.2	Steps 3 to 18 in generic procedure in 36.508 [94] table 4.5A.27.3-1. UE attaches to the NW, establishes the default PDN, and performs IMS registration.
2-5	–		Step 1-4 defined in C.20	Steps 19 to 25 in generic procedure 36.508 [94] table 4.5A.27.3-1. UE establishes the emergency PDN and performs IMS emergency registration.
6	–		Step1 defined in C.47	UE sends INVITE along with initial SDP offer and MSD
7	<-		486 Busy here	The SS sends 486 Busy here
–	–		EXCEPTION: The UE performs a domain selection for the emergency call and the UE may transmit EXTENDED SERVICE REQUEST
8a1	->		EXTENDED SERVICE REQUEST	If CS Fallback is performed, the UE sends service request with Service type set to mobile originating CS fallback emergency call as defined in 24.301 clause 9.9.3.27
8a2	<-		SS releases the RRC connection	SS waits for two seconds before sending RRC connection release. UE state is changed from RRC_CONNECTED to RRC_IDLE, and UE is redirected to UTRAN/GERAN (if supported)
–	–		EXCEPTION: Either step 9a1 or 9b1 is performed, depending on the value of px_RATComb_Tested
9a1	–		IF px_RATComb_Tested = EUTRA_UTRA UE performs domain selection to a cell supporting CS domain (UTRAN) and performs eCall establishment in CS domain together with MM registration	NOTE: RAU procedure can take place in parallel to normal CS call.
9a2	–		SS configures cell A as a “non-suitable cell”
9a3	–		eCall is maintained for 5 seconds
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP re-registration defined in Annex C.46 of TS 34.229-1 can take place
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 can take place	The optional de-registration happens in parallel with the CS call release procedures.
9a4	–		eCall is cleared by SS
9b1	–		IF px_RATComb_Tested = EUTRA_GERAN UE performs domain selection to a cell supporting CS domain (GERAN cell) and performs eCall establishment in CS domain
9b2	–		SS configures cell A as a “non-suitable cell”
9b3	–		eCall is maintained for 5 seconds
9b4	–		eCall is cleared by SS
9b5	–		UE performs MM/GMM registration

Specific Message Contents

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A21

Step 7 486 Busy Here message as in Annex A.2.21.

RRCConnectionRelease (step 8a2)

Derivation Path: 36.508 Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
utra-FDD	Downlink UARFCN of cell 5		UTRA-FDD
_utra-TDD	Downlink UARFCN of cell 5		UTRA-TDD
geran	ARFCN of cell 24		GERAN
}
}

ROUTING AREA UPDATE ACCEPT (Step 9b5)

Use the default message with the following specific contents

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

21.14.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for Automatic eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

In step 9a1 or 9b1, UE shall send an EMERGENCY SETUP message with the Service Category IE bit 7= 1 and all other bits are set to 0.

21.15 eCall only mode / Manual initiation / Emergency registration / Abnormal case / IM CN sends a 600 (Busy Everywhere) / UE performs eCall in CS domain / UTRAN or GERAN

21.15.1 Definition

Test to verify that on reception of reject cause 600 Busy everywhere for a manually initiated INVITE for eCall over IMS, UE initiates the eCall in supported CS domain over UTRAN or GERAN.

21.15.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.1]:

[TS 24.229, clause 5.1.6.11.2]:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

…

3) if the UE receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful and shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B]; and

4) in all other cases, the UE shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B].

Reference(s)

3GPP TS 24.229 [10], clauses 5.1.6.11.1 and 5.1.6.11.2.

21.15.3 Test purpose

1) To verify that the UE is able to handle 600 (Busy Everywhere) SIP error message for a manually initiated INVITE for eCall over IMS; and

2) To verify that the UE is able to establish legacy eCall in CS domain in UTRAN or GERAN system after receiving 600 (Busy Everywhere) SIP error message.

21.15.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall Only subscription. The UE is switched on not registered to IMS services.

The SS is configured:

– with 2 cells: as in TS 36.508 [94]

– E-UTRAN cell A

– if px_RATComb_Tested = EUTRA_UTRA, cell 5

– if px_RATComb_Tested = EUTRA_GERAN, GERAN cell 24

– Cell A power level is set as “serving cell” and cell 24/cell 5 power level is set as “suitable cell”

NOTE: Setting px_RATComb_Tested = EUTRA_Only is not allowed.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Manual eCall over IMS is initiated at the UE

1A-1H) IMS registration according to C.2 is executed.

2-5) Emergency registration according to C.20 is executed.

6) SS waits for UE to send an INVITE request

7) SS sends 600 Busy everywhere.

8-9) UE performs domain selection to a cell supporting CS domain (UTRAN/GERAN) based on capability supported and initiates CS domain emergency call with MM registration if necessary. CS eCall is established and maintained for 5 seconds and then the call is cleared by SS.

Expected sequence:

Step	Direction		Message	Comment
	UE	SS
1	–		UE is triggered to initiate a manual eCall
1A-1H	–		Steps 4-11 in Annex C.2	Steps 3 to 18 in generic procedure in 36.508 [94] table 4.5A.27.3-1. UE attaches to the NW, establishes the default PDN, and performs IMS registration.
2-5	–		Step 1-4 defined in C.20	Steps 19 to 25 in generic procedure 36.508 [94] table 4.5A.27.3-1. UE establishes the emergency PDN and performs IMS emergency registration.
6	–		Step1 defined in C.47	UE sends INVITE along with initial SDP offer and MSD
7	<-		600 Busy everywhere	The SS sends 600 Busy everywhere
–	–		EXCEPTION: The UE performs a domain selection for the emergency call and the UE may transmit EXTENDED SERVICE REQUEST
8a1	->		EXTENDED SERVICE REQUEST	If CS Fallback is performed, the UE sends service request with Service type set to mobile originating CS fallback emergency call as defined in 24.301 clause 9.9.3.27
8a2	<-		SS releases the RRC connection	SS waits for two seconds before sending RRC connection release. UE state is changed from RRC_CONNECTED to RRC_IDLE, and UE is redirected to UTRAN/GERAN (if supported)
–	–		EXCEPTION: Either step 9a1 or 9b1 is performed, depending on the value of px_RATComb_Tested
9a1	–		IF px_RATComb_Tested = EUTRA_UTRA UE performs domain selection to a cell supporting CS domain (UTRAN) and performs eCall establishment in CS domain together with MM registration	NOTE: RAU procedure can take place in parallel to normal CS call.
9a2	–		SS configures cell A as a “non-suitable cell”
9a3	–		eCall is maintained for 5 seconds
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP re-registration defined in Annex C.46 of TS 34.229-1 can take place
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 can take place	The optional de-registration happens in parallel with the CS call release procedures.
9a4	–		eCall is cleared by SS
9b1	–		IF px_RATComb_Tested = EUTRA_GERAN UE performs domain selection to a cell supporting CS domain (GERAN cell) and performs eCall establishment in CS domain
9b2	–		SS configures cell A as a “non-suitable cell”
9b3	–		eCall is maintained for 5 seconds
9b4	–		eCall is cleared by SS
9b5	–		UE performs MM/GMM registration

Specific Message Contents

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A20

Step 7 600 Busy Everywhere message as in Annex A.2.22.

RRCConnectionRelease (step 8a2)

Derivation Path: 36.508 Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
utra-FDD	Downlink UARFCN of cell 5		UTRA-FDD
_utra-TDD	Downlink UARFCN of cell 5		UTRA-TDD
geran	ARFCN of cell 24		GERAN
}
}

ROUTING AREA UPDATE ACCEPT (Step 9b5)

Use the default message with the following specific contents

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

21.15.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for manual eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

In step 9a1 or 9b1, UE shall send an EMERGENCY SETUP message with the Service Category IE bit 6 = 1 and all other bits are set to 0.

21.16 eCall only mode / Automatic initiation / Emergency registration / Abnormal case / IM CN sends a 600 (Busy Everywhere) / UE performs eCall in CS domain / UTRAN or GERAN

21.16.1 Definition

Test to verify that on reception of reject cause 600 Busy everywhere for an automatically initiated INVITE for eCall over IMS, UE initiates the eCall in supported CS domain over UTRAN or GERAN.

21.16.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.1]:

[TS 24.229, clause 5.1.6.11.2]:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

…

3) if the UE receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful and shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B]; and

4) in all other cases, the UE shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B].

Reference(s)

3GPP TS 24.229 [10], clauses 5.1.6.11.1 and 5.1.6.11.2.

21.16.3 Test purpose

1) To verify that the UE is able to handle 600 (Busy Everywhere) SIP error message for an automatically initiated INVITE for eCall over IMS; and

2) To verify that the UE is able to establish legacy eCall in CS domain in UTRAN or GERAN system after receiving 600 (Busy Everywhere) SIP error message.

21.16.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall Only subscription. UE is switched on not registered to IMS services.

The SS is configured:

– with 2 cells: as in TS 36.508 [94]

– E-UTRAN cell A

– if px_RATComb_Tested = EUTRA_UTRA, cell 5

– if px_RATComb_Tested = EUTRA_GERAN, GERAN cell 24

– Cell A power level is set as “serving cell” and cell 24/cell 5 power level is set as “suitable cell”

NOTE: Setting px_RATComb_Tested = EUTRA_Only is not allowed.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Automatic eCall over IMS is initiated at the UE

1A-1H) IMS registration according to C.2 is executed.

2-5) Emergency registration according to C.20 is executed.

6) SS waits for UE to send an INVITE request

7) SS sends 600 Busy everywhere.

8-9) UE performs domain selection to a cell supporting CS domain (UTRAN/GERAN) based on capability supported and initiates CS domain emergency call with MM registration if necessary. CS eCall is established and maintained for 5 seconds and then the call is cleared by SS.

Expected sequence:

Step	Direction		Message	Comment
	UE	SS
1	–		UE is triggered to initiate an automatic eCall	Step 2 in generic procedure 36.508 [94] table 4.5A.27.3-1.
1A-1H	–		Steps 4-11 in Annex C.2	Steps 3 to 18 in generic procedure in 36.508 [94] table 4.5A.27.3-1. UE attaches to the NW, establishes the default PDN, and performs IMS registration.
2-5	–		Step 1-4 defined in C.20	Steps 19 to 25 in generic procedure 36.508 [94] table 4.5A.27.3-1. UE establishes the emergency PDN and performs IMS emergency registration.
6	–		Step 1 defined in C.47	UE sends INVITE along with initial SDP offer and MSD
7	<-		600 Busy everywhere	The SS sends 600 Busy everywhere
–	–		EXCEPTION: The UE performs a domain selection for the emergency call and the UE may transmit EXTENDED SERVICE REQUEST
8a1	->		EXTENDED SERVICE REQUEST	If CS Fallback is performed, the UE sends service request with Service type set to mobile originating CS fallback emergency call as defined in 24.301 clause 9.9.3.27
8a2	<-		SS releases the RRC connection	SS waits for two seconds before sending RRC connection release. UE state is changed from RRC_CONNECTED to RRC_IDLE, and UE is redirected to UTRAN/GERAN (if supported)
–	–		EXCEPTION: Either step 9a1 or 9b1 is performed, depending on the value of px_RATComb_Tested
9a1	–		IF px_RATComb_Tested = EUTRA_UTRA UE performs domain selection to a cell supporting CS domain (UTRAN) and performs eCall establishment in CS domain together with MM registration	NOTE: RAU procedure can take place in parallel to normal CS call.
9a2	–		SS configures cell A as a “non-suitable cell”
9a3	–		eCall is maintained for 5 seconds
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP re-registration defined in Annex C.46 of TS 34.229-1 can take place
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 can take place	The optional de-registration happens in parallel with the CS call release procedures.
9a4	–		eCall is cleared by SS
9b1	–		IF px_RATComb_Tested = EUTRA_GERAN UE performs domain selection to a cell supporting CS domain (GERAN cell) and performs eCall establishment in CS domain
9b2	–		SS configures cell A as a “non-suitable cell”
9b3	–		eCall is maintained for 5 seconds
9b4	–		eCall is cleared by SS
9b5	–		UE performs MM/GMM registration

Specific Message Contents

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A21.

Step 7 600 Busy Everywhere message as in Annex A.2.22.

RRCConnectionRelease (step 8a2)

Derivation Path: 36.508 Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
utra-FDD	Downlink UARFCN of cell 5		UTRA-FDD
_utra-TDD	Downlink UARFCN of cell 5		UTRA-TDD
geran	ARFCN of cell 24		GERAN
}
}

ROUTING AREA UPDATE ACCEPT (Step 9b5)

Use the default message with the following specific contents

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

21.16.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for automatic eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

In step 9a1 or 9b1, UE shall send an EMERGENCY SETUP message with the Service Category IE bit 7 = 1 and all other bits are set to 0.

21.17 eCall only mode / Manual initiation / Emergency registration / Abnormal case / IM CN sends a 603 (Decline) / UE performs eCall in CS domain / UTRAN or GERAN

21.17.1 Definition

Test to verify that on reception of reject cause 603 Decline for a manually initiated INVITE for eCall over IMS, UE initiates the eCall in supported CS domain over UTRAN or GERAN.

21.17.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.1]:

[TS 24.229, clause 5.1.6.11.2]:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

…

3) if the UE receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful and shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B]; and

4) in all other cases, the UE shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B].

Reference(s)

3GPP TS 24.229 [10], clauses 5.1.6.11.1 and 5.1.6.11.2.

21.17.3 Test purpose

1) To verify that the UE is able to handle 603 (Decline) SIP error message for an automatically initiated INVITE for eCall over IMS; and

2) To verify that the UE is able to establish legacy eCall in CS domain in UTRAN or GERAN system after receiving 603 (Decline) SIP error message.

21.17.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall Only subscription.

The UE is switched on not registered to IMS services.

The SS is configured:

– with 2 cells: as in TS 36.508 [94]

– E-UTRAN cell A

– if px_RATComb_Tested = EUTRA_UTRA, cell 5

– if px_RATComb_Tested = EUTRA_GERAN, GERAN cell 24

– Cell A power level is set as “serving cell” and cell 24/cell 5 power level is set as “suitable cell”

NOTE: Setting px_RATComb_Tested = EUTRA_Only is not allowed.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Manual eCall over IMS is initiated at the UE

1A-1H) IMS registration according to C.2 is executed.

2-5) IMS Emergency registration according to C.20 is executed.

6) SS waits for UE to send an INVITE request

7) SS sends 603 Decline.

8-9) UE performs domain selection to a cell supporting CS domain (UTRAN/GERAN) based on capability supported and initiates CS domain emergency call with MM registration if necessary.

Expected sequence:

Step	Direction		Message	Comment
	UE	SS
1	–		UE is triggered to initiate a manual eCall	Step 2 in generic procedure 36.508 [94] table 4.5A.27.3-1.
1A-1H	–		Steps 4-11 in Annex C.2	Steps 3 to 18 in generic procedure 36.508 [94] table 4.5A.27.3-1. UE attaches to the NW, establishes the default PDN, and performs IMS registration.
2-5	–		Step 1-4 defined in C.20	Steps 19 to 25 in generic procedure 36.508 [94] table 4.5A.27.3-1. UE establishes the emergency PDN and performs IMS emergency registration.
6	–		Step 1 defined in C.47	UE sends INVITE along with initial SDP offer and MSD
7	<-		603 Decline	The SS sends 603 Decline
–	–		EXCEPTION: The UE performs a domain selection for the emergency call and the UE may transmit EXTENDED SERVICE REQUEST
8a1	->		EXTENDED SERVICE REQUEST	If CS Fallback is performed, the UE sends service request with Service type set to mobile originating CS fallback emergency call as defined in 24.301 clause 9.9.3.27
8a2	<-		SS releases the RRC connection	SS waits for two seconds before sending RRC connection release. UE state is changed from RRC_CONNECTED to RRC_IDLE, and UE is redirected to UTRAN/GERAN (if supported)
–	–		EXCEPTION: Either step 9a1 or 9b1 is performed, depending on the value of px_RATComb_Tested
9a1	–		IF px_RATComb_Tested = EUTRA_UTRA UE performs domain selection to a cell supporting CS domain (UTRAN) and performs eCall establishment in CS domain together with MM registration	NOTE: RAU procedure can take place in parallel to normal CS call.
9a2	–		SS configures cell A as a “non-suitable cell”
9a3	–		eCall is maintained for 5 seconds
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP re-registration defined in Annex C.46 of TS 34.229-1 can take place
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 can take place	The optional de-registration happens in parallel with the CS call release procedures.
9a4	–		eCall is cleared by SS
9b1	–		IF px_RATComb_Tested = EUTRA_GERAN UE performs domain selection to a cell supporting CS domain (GERAN cell) and performs eCall establishment in CS domain
9b2	–		SS configures cell A as a “non-suitable cell”
9b3	–		eCall is maintained for 5 seconds
9b4	–		eCall is cleared by SS
9b5	–		UE performs MM/GMM registration

Specific Message Contents

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A21

Step 7 603 Decline message as in Annex A.2.23.

RRCConnectionRelease (step 8a2)

Derivation Path: 36.508 Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
utra-FDD	Downlink UARFCN of cell 5		UTRA-FDD
_utra-TDD	Downlink UARFCN of cell 5		UTRA-TDD
geran	ARFCN of cell 24		GERAN
}
}

ROUTING AREA UPDATE ACCEPT (Step 9b5)

Use the default message with the following specific contents

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

21.17.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for automatic eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

In step 9a1 or 9b1, UE shall send an EMERGENCY SETUP message with the Service Category IE bit 6 = 1 and all other bits are set to 0.

21.18 eCall only mode / Automatic initiation / Emergency registration / Abnormal case / IM CN sends a 603 (Decline) / UE performs eCall in CS domain / UTRAN or GERAN

21.18.1 Definition

Test to verify that on reception of reject cause 603 Decline for an automatically initiated INVITE for eCall over IMS, UE initiates the eCall in supported CS domain over UTRAN or GERAN.

21.18.2 Conformance requirement

[TS 24.229, clause 5.1.6.11.1]:

[TS 24.229, clause 5.1.6.11.2]:

1) the UE shall set the Request-URI to "urn:service:sos.ecall.automatic" or "urn:service:sos.ecall.manual"; and

2) if the IP-CAN indicates the eCall support indication, the UE shall:

b) insert an Accept header field indicating the UE is willing to accept an "application/EmergencyCallData.Control+xml" MIME type as defined in RFC 8147 [244]; and

c) insert a Recv-Info header field set to "EmergencyCallData.eCall.MSD" as defined in RFC 8147 [244].

NOTE: Further content for the INVITE is as defined in RFC 8147 [244].

Then the UE shall proceed as follows:

…

3) if the UE receives a 486 (Busy Here), 600 (Busy Everywhere) or 603 (Decline) response to the INVITE request containing:

a) a multipart/mixed body containing an "application/EmergencyCallData.Control+xml" MIME body part as defined in RFC 8147 [244] with an "ack" element containing:

i) a "received" attribute set to "true"; and

ii) a "ref" attribute set to the Content-ID of the MIME body part containing the MSD sent by the UE;

then the UE shall consider the initial MSD transmission as successful and shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B]; and

4) in all other cases, the UE shall perform domain selection to re-attempt the eCall as specified in 3GPP TS 23.167 [4B].

Reference(s)

3GPP TS 24.229 [10], clauses 5.1.6.11.1 and 5.1.6.11.2.

21.18.3 Test purpose

1) To verify that the UE is able to handle 603 (Decline) SIP error message for an automatically initiated INVITE for eCall over IMS; and

2) To verify that the UE is able to establish legacy eCall in CS domain in UTRAN or GERAN system after receiving 603 (Decline) SIP error message.

21.18.4 Method of test

Initial conditions

UE contains either ISIM and USIM applications or only USIM application on UICC with eCall Only subscription.

The UE is switched on not registered to IMS services.

The SS is configured:

– with 2 cells: as in TS 36.508 [94]

– E-UTRAN cell A

– if px_RATComb_Tested = EUTRA_UTRA, cell 5

– if px_RATComb_Tested = EUTRA_GERAN, GERAN cell 24

– Cell A power level is set as “serving cell” and cell 24/cell 5 power level is set as “suitable cell”

NOTE: Setting px_RATComb_Tested = EUTRA_Only is not allowed.

Test procedure applicable for a UE with E-UTRA support (TS 34.229-2 [5] A.18/1)

1) Automatic eCall over IMS is initiated at the UE

1A-1H) IMS registration according to C.2 is executed.

2-5) Emergency registration according to C.20 is executed.

6) SS waits for UE to send an INVITE request

7) SS sends 603 Decline.

8-9) UE performs domain selection to a cell supporting CS domain (UTRAN/GERAN) based on capability supported and initiates CS domain emergency call with MM registration if necessary. CS eCall is established and maintained for 5 seconds and then the call is cleared by SS.

Expected sequence:

Step	Direction		Message	Comment
	UE	SS
1	–		UE is triggered to initiate an automatic eCall	Step 2 in generic procedure 36.508 [94] table 4.5A.27.3-1.
1A-1H	–		Steps 4-11 in Annex C.2	Steps 3 to 18 in generic procedure in 36.508 [94] table 4.5A.27.3-1. UE attaches to the NW, establishes the default PDN, and performs IMS registration.
2-5	–		Step 1-4 defined in C.20	Steps 19 to 25 in generic procedure 36.508 [94] table 4.5A.27.3-1. UE establishes the emergency PDN and performs IMS emergency registration.
6	–		Step 1 defined in C.47	UE sends INVITE along with initial SDP offer and MSD
7	<-		603 Decline	The SS sends 603 Decline
–	–		EXCEPTION: The UE performs a domain selection for the emergency call and the UE may transmit EXTENDED SERVICE REQUEST
8a1	->		EXTENDED SERVICE REQUEST	If CS Fallback is performed, the UE sends service request with Service type set to mobile originating CS fallback emergency call as defined in 24.301 clause 9.9.3.27
8a2	<-		SS releases the RRC connection	SS waits for two seconds before sending RRC connection release. UE state is changed from RRC_CONNECTED to RRC_IDLE, and UE is redirected to UTRAN/GERAN (if supported)
–	–		EXCEPTION: Either step 9a1 or 9b1 is performed, depending on the value of px_RATComb_Tested
9a1	–		IF px_RATComb_Tested = EUTRA_UTRA UE performs domain selection to a cell supporting CS domain (UTRAN) and performs eCall establishment in CS domain together with MM registration	NOTE: RAU procedure can take place in parallel to normal CS call.
9a2	–		SS configures cell A as a “non-suitable cell”
9a3	–		eCall is maintained for 5 seconds
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP re-registration defined in Annex C.46 of TS 34.229-1 can take place
–	–		EXCEPTION: Depending on the UE implementation, the generic test procedure for mobile initiated IMS SIP de-registration defined in Annex C.30 of TS 34.229-1 can take place	The optional de-registration happens in parallel with the CS call release procedures.
9a4	–		eCall is cleared by SS
9b1	–		IF px_RATComb_Tested = EUTRA_GERAN UE performs domain selection to a cell supporting CS domain (GERAN cell) and performs eCall establishment in CS domain
9b2	–		SS configures cell A as a “non-suitable cell”
9b3	–		eCall is maintained for 5 seconds
9b4	–		eCall is cleared by SS
9b5	–		UE performs MM/GMM registration

Specific Message Contents

Step 6 as specified in annex C.47, which is referring to A.2.1 default message content of INVITE with condition A21

Step 7 603 Decline message as in Annex A.2.23.

RRCConnectionRelease (step 8a2)

Derivation Path: 36.508 Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCConnectionRelease ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionRelease-r8 SEQUENCE {
redirectedCarrierInfo ::= CHOICE {
utra-FDD	Downlink UARFCN of cell 5		UTRA-FDD
_utra-TDD	Downlink UARFCN of cell 5		UTRA-TDD
geran	ARFCN of cell 24		GERAN
}
}

ROUTING AREA UPDATE ACCEPT (Step 9b5)

Use the default message with the following specific contents

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

21.18.5 Test requirements

In step 6, UE shall transmit INVITE with all applicable headers for automatic eCall over IMS.

In step 6, UE shall transmit MSD in the INVITE.

In step 9a1 or 9b1, UE shall send an EMERGENCY SETUP message with the Service Category IE bit 7 = 1 and all other bits are set to 0.