11.5 eCall over IMS

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

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

11.5.1 eCall Only mode / T3444 / eCall inactivity procedure / Removal of eCall only restriction after an eCall over IMS / 5GS to EPS

11.5.1.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE reads ims-EmergencySupport and eCallOverIMS-Support from SIB1 }

then { UE enters substate 5GMM-DEREGISTERED.eCALL-INACTIVE and shall not start registration procedure }

}

(2)

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

ensure that {

when { UE is requested to make a manual eCall }

then { UE sends REGISTRATION REQUEST message with 5GS registration type set to ‘initial registration’ }

}

(3)

with { UE receives REGISTRATION ACCEPT message and IMS voice over PS session is supported over 3GPP access }

ensure that {

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

then { the UE establishes a New emergency PDU session by sending an UL NAS TRANSPORT message with Request type set to "initial emergency request" and a PDU SESSION ESTABLISHMENT REQUEST }

}

(4)

with { UE receives an RRCRelease message and enters RRC_IDLE state }

ensure that {

when { UE receives a Paging message with MT MMTEL voice call }

then {the UE answers the paging request for MT MMTEL voice call }

}

(5)

with { UE receives an RRCRelease message and enters RRC_IDLE state }

ensure that {

when { UE starts T3444 for 12Hours and the periodic registration update timer T3512 expires }

then { the UE initiates the registration procedure for mobility and periodic registration update

and indicates "periodic registration updating" in the 5GS registration type IE }

}

(6)

with { UE in state 5GMM-REGISTERED and 5GMM-IDLE on a 5GC NR cell }

ensure that {

when { UE detects a suitable EPC E-UTRA cell after the serving NGC cell becomes not suitable when eCall Inactivity timer T3444 is running }

then { UE performs a Inter-system change from N1 mode to S1 mode by initiating and successfully
completing a TAU procedure }

}

(7)

with { UE in state EMM-REGISTERED and EMM-IDLE on an E-UTRA cell }

ensure that {

when { UE detects a suitable NGC cell after the serving E-UTRA cell becomes not suitable when eCall Inactivity timer T3444 is running }

then { UE performs a Inter-system change from S1 mode to N1 mode by initiating and successfully
completing a mobility and periodic registration update procedure }

}

(8)

with { UE is in RRC_IDLE state }

ensure that {

when { eCall Inactivity timer T3444 expires }

then { The UE performs Deregistration procedure }

}

11.5.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in TS 24.501, clauses 5.1.3.2.1.3.8, 5.3.1.3, 5.5.3, TS 24.301, clauses 10.2 and TS 38.331, clauses 5.2.2.4.2, 6.2.2. Unless otherwise stated these are Rel-16 requirements.

[TS 24.501, clause 5.1.3.2.1.3.8]

The substate 5GMM-DEREGISTERED.eCALL-INACTIVE is chosen in the UE when:

a) the UE is configured for eCall only mode as specified in 3GPP TS 31.102 [22];

b) timer T3444 and timer T3445 have expired or are not running;

c) a PLMN has been selected as specified in 3GPP TS 23.122 [5];

d) the UE does not need to perform an eCall over IMS; and

e) the UE does not need to perform a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service.

In this substate, the UE shall not initiate any signalling towards the network, except to originate an eCall over IMS, or a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service.

[TS 24.501, clause 5.3.1.3]

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

In N1 mode, upon indication from lower layers that the access stratum connection has been released, the UE shall enter 5GMM-IDLE mode and consider the N1 NAS signalling connection released.

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

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

– if the N1 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.501, clause 5.5.3]

The eCall inactivity procedure is performed only in 3GPP access and applicable only to a UE configured for eCall only mode as specified in 3GPP TS 31.102 [22]. The procedure shall be started when:

a) the UE is in any 5GMM-REGISTERED substate except substates 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.NO-CELL-AVAILABLE;

b) the UE is in 5GMM-IDLE mode; and

c) one of the following conditions applies:

1) timer T3444 expires or is found to have already expired and timer T3445 is not running;

2) timer T3445 expires or is found to have already expired and timer T3444 is not running; or

3) timers T3444 and T3445 expire or are found to have already expired.

The UE shall then perform the following actions:

a) stop other running timers (e.g. T3511, T3512);

b) if the UE is currently registered to the network for 5GS services, perform a de-registration procedure;

c) delete any 5G-GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, and ngKSI; and

d) enter 5GMM-DEREGISTERED.eCALL-INACTIVE state.

[TS 24.301, clause 10.2]

T3444

NOTE 11

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

– UE configured for eCall only mode enters EMM-IDLE mode after an eCall over IMS

– UE configured for eCall only mode moves from GERAN/UTRAN to E-UTRAN with timer T3242 (see 3GPP TS 24.008 [13]) running

– UE configured for eCall only mode enters 5GMM-IDLE mode (defined in 3GPP TS 24.501 [54]) after an eCall over IMS

– Removal of eCall only restriction

– Intersystem change from S1 mode to A/Gb or Iu mode

Perform eCall inactivity procedure in EPS as described in clause 5.5.4.

Perform eCall inactivity procedure in 5GS as described in 3GPP TS 24.501 [54].

T3445

NOTE 12

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

– 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

– UE configured for eCall only mode moves from GERAN/UTRAN to E-UTRAN with timer T3243 (see 3GPP TS 24.008 [13]) running

– UE configured for eCall only mode enters 5GMM-IDLE mode (defined in 3GPP TS 24.501 [54]) after a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service

Removal of eCall only restriction

– Intersystem change from S1 mode to A/Gb or Iu mode

Perform eCall inactivity procedure in EPS as described in clause 5.5.4.

Perform eCall inactivity procedure in 5GS as described in 3GPP TS 24.501 [54].

[TS 38.331, clause 5.2.2.4.2]

Upon receiving the SIB1 the UE shall:

1> store the acquired SIB1;

…

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

[TS 38.331, clause 6.2.2]

eCallOverIMS-Support

Indicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell.

11.5.1.3 Test description

11.5.1.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-6 as defined in TS 38.508-1 [4], sub-clause 4.4.3.1.2.

– E-UTRA Cell 1 as defined in TS 36.508 [7] Table 4.4.2-2. System information combination 31 as defined in TS 36.508 [7], sub-clause 4.4.3.1.1.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.1.3.2 Test procedure sequence

Table 11.5.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NR Cell 1 as "Serving cell" – E-UTRA Cell 1 as "Non-suitable "off" cell".	–	–	–	–
2	The UE is switched on.	–	–	–	–
3	Check: Does the UE send an RRCSetupRequest on NR Cell 1 within 120 seconds?	–>	NR RRC: RRCSetupRequest	1	F
4	A manual eCall is initiated. (Note 1)	–	–	–	–
5	Check: Does the UE send REGISTRATION REQUEST message with 5GS registration type set to ‘initial registration’?	–>	5GMM: REGISTRATION REQUEST	2	P
6-14	Steps 5-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
15	The SS transmits a REGISTRATION ACCEPT message and assigns value of 7 hours for the timer T3512.	<–	5GMM: REGISTRATION ACCEPT	–	–
16-20a1	Steps 15-19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
21	Check: The UE transmits an ULInformationTransfer message with Request type set to "initial emergency request" and a PDU SESSION ESTABLISHMENT REQUEST message?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	3	P
22-26	Steps 22-26 of Table 4.9.29.2.2-1 of the test procedure in TS 38.508-1 [4] are performed.	–	–	–	–
27-28	Release eCall over IMS using the generic procedure described in TS 34.229-5 [41] subclause A.8.
29	The SS releases the RRC connection. (Note 2)	<–	NR RRC: RRCRelease	–	–
30	The SS waits 1 minute.	–	–	–	–
31-43	Steps 1 to 13 of the generic test procedure for IMS MT speech call establishment in 5GC specified in TS 38.508-1 [4] subclause 4.9.16 are performed.	–	–	4	P
44-45	Generic test procedure for MT release of Voice call in 5GS described in TS 34.229-5 [41] subclause A.8 takes place.	–	–	–	–
46	The SS releases the RRC connection. (Note 3)	<–	NR RRC: RRCRelease	–	–
47	Check: Does the UE transmit a REGISTRATION REQUEST message at the expiry of T3512?	–>	5GMM: REGISTRATION REQUEST	5	P
48	The SS transmits a REGISTRATION ACCEPT message including T3512 value IE.	<–	5GMM: REGISTRATION ACCEPT	–	–
49	The UE transmits a REGISTRATION COMPLETE message	–>	5GMM: REGISTRATION COMPLETE
50	The SS releases the RRC connection.	<–	NR RRC: RRCRelease	–	–
51	The SS configures: – NR Cell 1 as " Non-suitable "off" cell" – E-UTRA Cell 1 as "Serving cell".	–	–	–	–
52	Check: Does the UE perform on the E-UTRA Cell 1 the TAU procedure for Inter-system change from N1 mode to S1 mode as described in TS 38.508-1 [4], Table 4.9.7.2.2-1?	–	–	6	P
53	The SS configures: – NR Cell 1 as "Serving cell" – E-UTRA Cell 1 as "Non-suitable "off" cell".	–	–	–	–
54	Check: Does the UE perform on the NR Cell 1 the Test procedure for UE Tracking area updating for Inter-system change from S1 mode to N1 mode as described in TS 38.508-1 [4], Table 4.9.9.2.2-1?	–	–	7	P
55	Check: Does the UE transmit a DEREGISTRATION REQUEST message at expiry of T3444?	–>	5GMM: DEREGISTRATION REQUEST	8	P
Note 1: The request to originate a manual eCall may be performed by MMI or AT command. Note 2: Timer T3444 of 12hours starts. Note 3: Timer T3512 of 7hours starts.

11.5.1.3.3 Specific message contents

Table 11.5.1.3.3-1: SIB1 for NR Cell 1 (All steps, Table 11.5.1.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.1.3.3-2: REGISTRATION ACCEPT (step 15, 48, 54 Table 11.5.1.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
T3512 value
Unit	‘001’B	value is incremented in multiples of 1 hour
Timer value	‘0 0111’B	7 hours

Table 11.5.1.3.3-3: UL NAS TRANSPORT (step 21, Table 11.5.1.3.2-1)

Derivation Path: TS 38.508-1 [4] table 4.7.1-10, condition INITIAL_PDU_REQUEST.
Information Element	Value/remark	Comment	Condition
Request type	‘011’B	initial emergency request
S-NSSAI	Not Present
DNN	Not Present

Table 11.5.1.3.3-4: REGISTRATION REQUEST (step 47, Table 11.5.1.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type
5GS registration type value	‘011’B		PERIODIC

Table 11.5.1.3.3-5: TRACKING AREA UPDATE REQUEST (Step 52, Table 11.5.1.3.2-1; step 3, TS 38.508-1 [4] Table 4.9.7.2.2-1)

Derivation Path: TS 38.508-1 [4] table 4.9.7.2.3-1 with condition First-N1-to-S1 = TRUE

Table 11.5.1.3.3-6: DEREGISTRATION REQUEST (step 55, Table 11.5.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-12
Information Element	Value/remark	Comment	Condition
De-registration type
Switch off	‘0’B	Normal de-registration

11.5.2 eCall Only mode / T3445 / eCall inactivity procedure / Removal of eCall only restriction after a call to URI for test service / 5GS to EPS

11.5.2.1 Test Purpose (TP)

(1)

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

ensure that {

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

then { UE sends REGISTRATION REQUEST message with 5GS registration type set to ‘initial registration’ }

}

(2)

with { UE receives REGISTRATION ACCEPT message and IMS voice over PS session is supported over 3GPP access }

ensure that {

when { UE is in 5GMM-REGISTERED.NORMAL-SERVICE state and an initial registration is performed }

then { the UE establishes a new PDU session by sending an UL NAS TRANSPORT message with Request type set to "initial request" and a PDU SESSION ESTABLISHMENT REQUEST }

}

(3)

with { UE receives an RRCRelease message and enters RRC_IDLE state }

ensure that {

when { UE receives a Paging message with MT MMTEL voice call }

then {the UE answers the paging request for MT MMTEL voice call }

}

(4)

with { UE receives an RRCRelease message and enters RRC_IDLE state }

ensure that {

when { UE starts T3445 for 12Hours and the periodic registration update timer T3512 expires }

then { the UE initiates the registration procedure for mobility and periodic registration update

and indicates "periodic registration updating" in the 5GS registration type IE }

}

(5)

with { UE in state 5GMM-REGISTERED and 5GMM-IDLE on a 5GC NR cell }

ensure that {

when { UE detects a suitable EPC E-UTRA cell after the serving NGC cell becomes not suitable when eCall Inactivity timer T3445 is running }

then { UE performs a Inter-system change from N1 mode to S1 mode by initiating and successfully
completing a TAU procedure }

}

(6)

with { UE in state EMM-REGISTERED and EMM-IDLE on an E-UTRA cell }

ensure that {

when { UE detects a suitable NGC cell after the serving E-UTRA cell becomes not suitable when eCall Inactivity timer T3445 is running }

then { UE performs a Inter-system change from S1 mode to N1 mode by initiating and successfully
completing a mobility and periodic registration update procedure }

}

(7)

with { UE is in RRC_IDLE state }

ensure that {

when { eCall Inactivity timer T3445 expires }

then { The UE performs Deregistration procedure }

}

11.5.2.2 Conformance requirements

[TS 24.501, clause 5.1.3.2.1.3.8]

The substate 5GMM-DEREGISTERED.eCALL-INACTIVE is chosen in the UE when:

a) the UE is configured for eCall only mode as specified in 3GPP TS 31.102 [22];

b) timer T3444 and timer T3445 have expired or are not running;

c) a PLMN has been selected as specified in 3GPP TS 23.122 [5];

d) the UE does not need to perform an eCall over IMS; and

e) the UE does not need to perform a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service.

[TS 24.501, clause 5.3.1.3]

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

In N1 mode, upon indication from lower layers that the access stratum connection has been released, the UE shall enter 5GMM-IDLE mode and consider the N1 NAS signalling connection released.

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

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

[TS 24.501, clause 5.5.3]

The eCall inactivity procedure is performed only in 3GPP access and applicable only to a UE configured for eCall only mode as specified in 3GPP TS 31.102 [22]. The procedure shall be started when:

a) the UE is in any 5GMM-REGISTERED substate except substates 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.NO-CELL-AVAILABLE;

b) the UE is in 5GMM-IDLE mode; and

c) one of the following conditions applies:

1) timer T3444 expires or is found to have already expired and timer T3445 is not running;

2) timer T3445 expires or is found to have already expired and timer T3444 is not running; or

3) timers T3444 and T3445 expire or are found to have already expired.

The UE shall then perform the following actions:

a) stop other running timers (e.g. T3511, T3512);

b) if the UE is currently registered to the network for 5GS services, perform a de-registration procedure;

c) delete any 5G-GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, and ngKSI; and

d) enter 5GMM-DEREGISTERED.eCALL-INACTIVE state.

[TS 24.301, clause 10.2]

T3444

NOTE 11

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

– UE configured for eCall only mode enters EMM-IDLE mode after an eCall over IMS

– UE configured for eCall only mode moves from GERAN/UTRAN to E-UTRAN with timer T3242 (see 3GPP TS 24.008 [13]) running

– UE configured for eCall only mode enters 5GMM-IDLE mode (defined in 3GPP TS 24.501 [54]) after an eCall over IMS

– Removal of eCall only restriction

– Intersystem change from S1 mode to A/Gb or Iu mode

Perform eCall inactivity procedure in EPS as described in clause 5.5.4.

Perform eCall inactivity procedure in 5GS as described in 3GPP TS 24.501 [54].

T3445

NOTE 12

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

– 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

– UE configured for eCall only mode moves from GERAN/UTRAN to E-UTRAN with timer T3243 (see 3GPP TS 24.008 [13]) running

– UE configured for eCall only mode enters 5GMM-IDLE mode (defined in 3GPP TS 24.501 [54]) after a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service

Removal of eCall only restriction

– Intersystem change from S1 mode to A/Gb or Iu mode

Perform eCall inactivity procedure in EPS as described in clause 5.5.4.

Perform eCall inactivity procedure in 5GS as described in 3GPP TS 24.501 [54].

[TS 38.331, clause 5.2.2.4.2]

Upon receiving the SIB1 the UE shall:

1> store the acquired SIB1;

…

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

[TS 38.331, clause 6.2.2]

eCallOverIMS-Support

Indicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell.

11.5.2.3 Test description

11.5.2.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-6 as defined in TS 38.508-1 [4], sub-clause 4.4.3.1.2.

– E-UTRA Cell 1 as defined in TS 36.508 [7] Table 4.4.2-2. System information combination 31 as defined in TS 36.508 [7], sub-clause 4.4.3.1.1.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.2.3.2 Test procedure sequence

Table 11.5.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NR Cell 1 as "Serving cell" – E-UTRA Cell 1 as "Non-suitable "off" cell".	–	–	–	–
2	The UE is switched on.	–	–	–	–
3	Wait for 60s for the UE to enter 5GMM-DEREGISTERED.eCALL-INACTIVE state	–	–	–	–
4	An eCall to URI for test service is initiated. (Note 1)	–	–	–	–
5	Check: Does the UE send REGISTRATION REQUEST message with 5GS registration type set to ‘initial registration’?	–>	5GMM: REGISTRATION REQUEST	1	P
6-14	Steps 5-13 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.	–	–	–	–
15	The SS transmits a REGISTRATION ACCEPT message and assigns value of 7 hours for the timer T3512.	<–	5GMM: REGISTRATION ACCEPT	–	–
16	The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message.	–>	5GMM: REGISTRATION COMPLETE	–	–
17	Step 19a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] is performed with ‘connected without release’. Check: The UE transmits an ULInformationTransfer message with Request type set to "initial request" and a PDU SESSION ESTABLISHMENT REQUEST message?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	2	P
18-28	Void
29	Step 1 of expected sequence from A.4.1 as defined in TS 34.229-5 [41] is performed.	–	–	–	–
30-34	Steps 9a1 to 13b3 of Table 4.9.15.2.2-1 of the test procedure in TS 38.508-1 [4] are performed.	–	–	–	–
35-36	Release eCall over IMS using the generic procedure described in TS 34.229-5 [41] subclause A.8.
37	The SS releases the RRC connection. (Note 2)	<–	NR RRC: RRCRelease	–	–
38	The SS waits 1 minute.	–	–	–	–
39-51	Steps 1 to 13 of the generic test procedure for IMS MT speech call establishment in 5GC specified in TS 38.508-1 [4] subclause 4.9.16 are performed.	–	–	3	P
52-53	Generic test procedure for MT release of Voice call in 5GS described in TS 34.229-5 [41] subclause A.8 takes place.	–	–	–	–
54	The SS releases the RRC connection. (Note 3)	<–	NR RRC: RRCRelease	–	–
55	Check: Does the UE transmit a REGISTRATION REQUEST message at the expiry of T3512?	–>	5GMM: REGISTRATION REQUEST	4	P
56	The SS transmits a REGISTRATION ACCEPT message including T3512 value IE.	<–	5GMM: REGISTRATION ACCEPT	–	–
57	The UE transmits a REGISTRATION COMPLETE message	–>	5GMM: REGISTRATION COMPLETE
58	The SS releases the RRC connection.	<–	NR RRC: RRCRelease	–	–
59	The SS configures: – NR Cell 1 as " Non-suitable "off" cell" – E-UTRA Cell 1 as "Serving cell".	–	–	–	–
60	Check: Does the UE perform on the E-UTRA Cell 1 the TAU procedure for Inter-system change from N1 mode to S1 mode as described in TS 38.508-1 [4], Table 4.9.7.2.2-1?	–	–	5	P
61	The SS configures: – NR Cell 1 as "Serving cell" – E-UTRA Cell 1 as "Non-suitable "off" cell".	–	–	–	–
62	Check: Does the UE perform on the NR Cell 1 the Test procedure for UE Tracking area updating for Inter-system change from S1 mode to N1 mode as described in TS 38.508-1 [4], Table 4.9.9.2.2-1?	–	–	6	P
63	Check: Does the UE transmit a DEREGISTRATION REQUEST message at expiry of T3445?	–>	5GMM: DEREGISTRATION REQUEST	7	P
Note 1: The request to originate a manual eCall may be performed by MMI or AT command. Note 2: Timer T3445 of 12hours starts. Note 3: Timer T3512 of 7hours starts.

11.5.2.3.3 Specific message contents

Table 11.5.2.3.3-1: SIB1 for NR Cell 1 (All steps, Table 11.5.2.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.2.3.3-2: REGISTRATION ACCEPT (step 15, 56, 62 Table 11.5.2.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-7
Information Element	Value/Remark	Comment	Condition
T3512 value
Unit	‘001’B	value is incremented in multiples of 1 hour
Timer value	‘0 0111’B	7 hours

Table 11.5.2.3.3-3: UL NAS TRANSPORT (step 17, Table 11.5.2.3.2-1)

Derivation Path: TS 38.508-1 [4] table 4.7.1-10, condition INITIAL_PDU_REQUEST.
Information Element	Value/remark	Comment	Condition
Request type	‘001’B	initial request
S-NSSAI	Not Present

Table 11.5.2.3.3-4: REGISTRATION REQUEST (step 55, Table 11.5.2.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.7.1-6
Information Element	Value/remark	Comment	Condition
5GS registration type
5GS registration type value	‘011’B		PERIODIC

Table 11.5.2.3.3-5: TRACKING AREA UPDATE REQUEST (Step 60, Table 11.5.2.3.2-1; step 3, TS 38.508-1 [4] Table 4.9.7.2.2-1)

Derivation Path: TS 38.508-1 [4] table 4.9.7.2.3-1 with condition First-N1-to-S1 = TRUE

Table 11.5.2.3.3-6: DEREGISTRATION REQUEST (step 63, Table 11.5.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-12
Information Element	Value/remark	Comment	Condition
De-registration type
Switch off	‘0’B	Normal de-registration

11.5.3 11.5.4 eCall Only mode / 5GS supports IMS voice over PS session / 5GS supports emergency service / eCall over IMS is supported on 5GS / RACH failure in NR cell / eCall over EPS

11.5.4.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE is requested to make an automatic eCall and RACH failure is observed in NR cell }

then { UE establishes eCall over EPS }

}

11.5.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.2.2.7, 6.2.2 , TS 38.331, clause 6.2.2 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> else:

2> if the frequency band indicated in the freqBandIndicator is part of the frequency bands supported by the UE and it is not a downlink only band; or

…

3> forward the ims-EmergencySupport to upper layers, if present;

[TS 23.167 clause H.6]

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

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	PS on another PS RAT if available with EMS=Y and ECL=Y or 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	PS on another PS RAT if available with EMS=Y or EMS unknown
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] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS.

NOTE: If the E-UTRAN and NG-RAN cells available to the UE have different settings, the UE assumes "PS Available" and "ECL" apply to whichever cell is indicated (as defined in TS 23.401 [28] and TS 23.501 [48]) as providing eCall over IMS support. When support by more than one cell is indicated, a UE may select any cell to attempt eCall over IMS according to the UE implementation.

[TS 38.331, clause 6.2.2]

eCallOverIMS-Support

Indicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell.

[TS 36.331, clause 6.2.2]

eCallOverIMS-Support

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

11.5.4.3 Test description

11.5.4.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-6 as defined in TS 38.508-1 [4], sub-clause 4.4.3.1.2.

– E-UTRA Cell 1 as defined in TS 36.508 [7] Table 4.4.2-2. System information combination 31 as defined in TS 36.508 [7], sub-clause 4.4.3.1.1.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.4.3.2 Test procedure sequence

Table 11.5.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS configures: – NR Cell 1 as "Serving cell" – E-UTRA Cell 1 as "Non-suitable "off" cell".	–	–	–	–
2	The UE is switched on.	–	–	–	–
3	Wait for 60s for the UE to enter 5GMM-DEREGISTERED.eCALL-INACTIVE state.	–	–	–	–
4	An automatic eCall is initiated. (Note 1)	–	–	–	–
–	EXCEPTION: In parallel to the events described in step 4 the steps specified in Table 11.5.4.3.2-2 should take place.	–	–	–	–
5	The UE transmits preamble on PRACH.	–>	PRACH Preamble	–	–
6	The SS configures: – E-UTRA Cell 1 as "Suitable cell".	–	–	–	–
–	The following messages are to be observed on E-UTRA Cell 1 unless explicitly stated otherwise	–	–	–	–
7	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
8-26	Steps 7 to 25 of Generic Test Procedure for eCall over IMS establishment in EUTRA: eCall Only Support specified in TS 36.508 subclause 4.5A.27 take place.	–	–	–	–
27	Release eCall over IMS using the generic procedure described in TS 34.229-1 [35] subclause C.33.	–	–	–	–
28	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
Note 1: The request to originate an automatic eCall may be performed by MMI or AT command.

Table 11.5.4.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 NR Cell 1.	–>	PRACH Preamble	–	–
2	The SS does not respond.	–	–	–	–

11.5.4.3.3 Specific message contents

Table 11.5.4.3.3-1: Message SystemInformationBlockType1 for NR Cell (All steps, Table 11.5.4.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.4.3.3-2: Message SystemInformationBlockType1 for E-UTRA Cell 1(All Steps, Table 11.5.4.3.2-1)

Derivation path: TS 36.508 [7] table 4.4.3.2-3 Condition eCalloverIMS

Table 11.5.4.3.3-3: Message ATTACH ACCEPT (step 17, Table 11.5.4.3.2-1)

Derivation path: TS 36.508 [7] table 4.7.2-1
Information Element	Value/Remark	Comment	Condition
EPS attach result	‘010’B	”Combined EPS/IMSI attach”
EPS network feature support	‘0000 0011’B	emergency bearer services in S1 mode and IMS voice over PS session in S1 mode are supported

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

11.5.5.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 RRCSetupRequest message }

}

(2)

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

ensure that {

when { UE is requested to make a manual eCall }

then { UE transmits a REGISTRATION REQUEST message with registration type set to “emergency” }

}

11.5.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 23.122 [38], subclause 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.

11.5.5.3 Test description

11.5.5.3.1 Pre-test conditions

System Simulator:

– NGC Cell A

– The PLMN is defined in Table 11.5.5.3.1-1.

Table 11.5.5.3.1–1: PLMN identifier

NGC 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 38.508-1 [4] Table 6.4.1-26.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.5.3.2 Test procedure sequence

Table 11.5.5.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 NGC Cell A as an acceptable cell.	–	–	–	–
3	A manual eCall is initiated. (Note 1)	–	–	–	–
4A-4B	Steps 1-2 of test procedure 4.9.12 in TS 38.508-1 [4] are performed.	–	–	–	–
4C	Check: Does the UE transmits an RRCSetupComplete message and a REGISTRATION REQUEST message with ‘Registration type’ set to ’emergency’?	–>	NR RRC: RRCSetupComplete 5GMM: REGISTRATION REQUEST	2	P
4D-4O	Steps 4-15 of test procedure 4.9.12 in TS 38.508-1 [4] are performed.	–	–	–	–
–	EXCEPTION: In parallel to the events described in steps 4P-4R below the events specified Table 11.5.5.3.2-2 take place.	–	–	–	–
4P-4R	Steps 16-18 of test procedure 4.9.12 in TS 38.508-1 [4] are performed.	–	–	–	–
5	Test procedure for IMS MT Emergency call release is performed as specified in TS 38.508-1 [4], subclause 4.9.12B on NGC Cell A.	–	–	–	–
6	Void	–	–	–	–
7	The SS releases the RRC connection.	<–	RRC: RRCRelease	–	–
8	Wait for 5 seconds	–	–	–	–
9	An eCall to URI for test service is initiated. (Note 2)	–	–	–	–
10	Check: Does UE send an RRCConnectionRequest on NGC Cell A within 120 seconds?	–>	RRC: RRCSetupRequest	1	F
Note 1: The request to originate a manual eCall may be performed by MMI or AT command. Note 2: The request to originate an eCall to URI for test service may be performed by MMI or AT command.

Table 11.5.5.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message/PDU/SDU
1-3	Steps 1-3 of generic test procedure for setting up eCall as defined in TS 34.229-5 [47] annex A.23 are performed.	–	–	–	–

11.5.5.3.3 Specific message contents

Table 11.5.5.3.3-1: SIB1 for NGC Cell A (All steps, Table 11.5.5.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.5.3.3-2: REGISTRATION REQUEST (step 4C, Table 11.5.5.3.2-1)

Derivation Path: Table 4.7.1-6, condition EMERGENCY.

11.5.6 eCall capable / 5GS supports IMS voice over PS session / 5GS 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

11.5.6.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode }

ensure that {

when { eCallOverIMS-Support is not indicated in SIB1 and UE is requested to make an automatic eCall and UTRA Cell is available }

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

}

(2)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode }

ensure that {

when { eCallOverIMS-Support is not indicated in SIB1 and UE is requested to make an automatic eCall }

then { UE establishes an RRC connection for normal emergency call with the RRC establishmentCause set to "emergency", and, sends a SERVICE REQUEST message with Service type IE set to "emergency services" }

}

11.5.6.2 Conformance requirements

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

[TS 38.331, clause 5.2.2.4.2]

Upon receiving the SIB1 the UE shall:

1> store the acquired SIB1;

…

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

[TS 38.331, clause 6.2.2]

eCallOverIMS-Support

Indicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell.

[TS 23.167, clause 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 or NG-RAN 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 or NG-RAN radio access networks

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	PS on another PS RAT if available with EMS=Y and ECL=Y or 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	PS on another PS RAT if available with EMS=Y or EMS unknown
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] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS.

11.5.6.3 Test description

11.5.6.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2.

– UTRA Cell 5 is configured as Non-suitable "Off" cell as defined in TS 36.508 [7].

UE:

– the eCall capable UE is equipped with USIM configured as per TS 38.508-1 [4] Table 6.4.1-23.

Preamble:

– The UE is in test state 1N-A as defined in TS 38.508-1 [4], subclause 4.4A.2 on NR Cell 1.

11.5.6.3.2 Test procedure sequence

Table 11.5.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	EXCEPTION: Steps 1a1 to 1a27 describes behaviour that depends on the UE capability pc_UTRA = TRUE; the "lower case letter" identifies a step sequence that takes place if a capability is supported.	–	–	–	–
1a1	The SS configures UTRA Cell 5 as ”Suitable Neighbour cell”.	–	–	–	–
1a2	Cause the UE to originate an automatic eCall. (Note 1)	–	–	–	–
1a3	Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with establishment cause set to Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
1a4	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
1a5	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
–	EXCEPTION: In parallel to the event described in steps 1a6 to 1a17, if initiated by the UE the steps 5 to 13 of the generic procedure for Registration on PS specified in TS 34.108 subclause 7.2.2.2.3 take place.	–	–	–	–
1a6	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
1a7	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
1a8	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
1a9	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
1a10	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
1a11	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
1a12-1a17	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.	–	–	–	–
1a18	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
1a19	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
1a20	The UE transmits RELEASE.	–>	RELEASE	–	–
1a21	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
1a22	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
1a23	The UE transmits RRC CONNECTION RELEASE COMPLETE.		RRC CONNECTION RELEASE COMPLETE
1a24	if possible (see ICS) switch off is performed or the USIM is removed. Otherwise the power is removed.	–	–	–	–
–	EXCEPTION: Step1a24Aa1 describes behaviour that depends on the UE capability.	–	–	–	–
1a24Aa1	If pc_SwitchOnOff or pc_USIM_Removal then UE sends DETACH REQUEST message	–>	DETACH REQUEST	–	–
1a25	Set the power level of Cell 5 to Non-suitable" Off" level.	–	–	–	–
1a26	The UE is brought back to operation or the USIM configured as per TS 38.508-1 [4] Table 6.4.1-23 is inserted.	–	–	–	–
1a27	The Generic test procedure for NR RRC_IDLE described in TS 38.508-1 [4], Table 4.5.2.2-2 is performed. The UE performs registration and the RRC connection is released.	–	–	–	–
2-17a1	Void	–	–	–	–
18	Cause the UE to originate Automatic eCall. (see Note 1)	–	–	–	–
19	Check: Does the UE perform Generic Test Procedure for IMS Emergency call establishment with IMS Emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11? (see Note 2)	–	–	2	–
20	Test procedure for IMS MT Emergency call release is performed as specified in TS 38.508-1 [4], subclause 4.9.12B.	–	–	–	–
21	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.

11.5.6.3.3 Specific message contents

able 11.5.6.3.3-0: SIB1 of NR Cell 1 (All steps, Table 11.5.6.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28
Information Element	Value/remark	Comment	Condition
SIB1 ::= SEQUENCE {
eCallOverIMS-Support	Not present
}

Table 11.5.6.3.3-1: RRC CONNECTION REQUEST (Step 1a3, Table 11.5.6.3.2-1)

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

Table 11.5.6.3.3-2: CM SERVICE REQUEST (Step 1a6, Table 11.5.6.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

11.5.7 eCall Only mode / SRVCC Handover to CS domain / UTRAN / MSD Update / Success / 5GS

11.5.7.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE receives a MobilityFromNRCommand 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.5.7.2 Conformance requirements

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

[TS 38.331, clause 5.4.3.3]

Reception of the MobilityFromNRCommand by the UE

The UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> if T316 is running:

2> stop timer T316;

2> clear the information included in VarRLF-Report, if any;

1> if T390 is running:

2> stop timer T390 for all access categories;

2> perform the actions as specified in 5.3.14.4;

1> if the targetRAT-Type is set to eutra:

2> consider inter-RAT mobility as initiated towards E-UTRA;

2> forward the nas-SecurityParamFromNR to the upper layers, if included;

1> else if the targetRAT-Type is set to utra-fdd:

2> consider inter-RAT mobility as initiated towards UTRA-FDD;

2> forward the nas-SecurityParamFromNR to the upper layers, if included;

1> 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. This applies when a single EATF instance is deployed (see clause 6c.2.3 for multiple EATF instances).

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

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 26.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 of the MS in the "null" state receives an indication "MM connection establishment due to SRVCC handover" then:

– the call control entity shall indicate to the upper layers that call establishment is due to SRVCC handover;

– if the upper layers indicate that the media stream(s) is/are 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 call states for the transactions and the setting of the TI value and TI flag for these additional media streams are described in 3GPP TS 24.237 [136].

11.5.7.3 Test Description

11.5.7.3.1 Pre-test conditions

System Simulator:

– NR Cell 1 with system information combination NR-1 as defined in TS 38.508-1 [4].

– UTRA Cell 5 as defined in TS 36.508 [7].

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.7.3.2 Test procedure sequence

Table 11.5.7.3.2-1/2 illustrate the downlink power levels and other changing parameters to be applied for the cell at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause. The configuration T0 indicates the initial conditions for preamble. Configurations marked "T1" and “T2” are applied at the points indicated in the Main behaviour description in Table 11.5.7.3.2-3.

Table 11.5.7.3.2-1: Time instances of cell power level and parameter changes for FR1

	Parameter	Unit	NR Cell 1	UTRA Cell 5	Remark
T0	SS/PBCH SSS EPRE	dBm/ SCS	-88	–
T0	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz	–	Off
T1	SS/PBCH SSS EPRE	dBm/ SCS	-88	–
T1	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz		-60
T2	SS/PBCH SSS EPRE	dBm/ SCS	Off	–
T2	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz		-60

Table 11.5.7.3.2-2: Time instances of cell power level and parameter changes for FR2

	Parameter	Unit	NR Cell 1	UTRA Cell 5	Remark
T0	SS/PBCH SSS EPRE	dBm/ SCS	-82	–
T0	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz	–	Off
T1	SS/PBCH SSS EPRE	dBm/ SCS	-82	–
T1	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz		-60
T2	SS/PBCH SSS EPRE	dBm/ SCS	Off	–
T2	CPICH_Ec (UTRA FDD)	dBm/3.84 MHz		-60

Table 11.5.7.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1-12	A manual eCall is established by following the test procedure as defined in steps 1 to 12 of TS 38.508-1 [4], subclause 4.9.29.	–	–	–	–
13	The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for NR and UTRA.	<–	NR RRC: UECapabilityEnquiry	–	–
14	The UE transmits a UECapabilityInformation message. NOTE: The start-CS values received, should be used to configure ciphering on cell 5.	–>	NR RRC: UECapabilityInformation	–	–
15-26	Steps 15-26 of generic procedure specified in Table 4.9.29.2.2-1 of TS 38.508-1 [4] are performed.	–	–	–	–
27	Set the power levels according to “T1” as per Table 11.5.7.3.2-1/2.	–	–	–	–
28	The SS transmits a MobilityFromNRCommand message.	<–	NR RRC: MobilityFromNRCommand	–	–
–	The following messages are to be observed on UTRA Cell 5 unless explicitly stated otherwise.	–	–	–	–
29	Check: Does the UE transmit a HANDOVER TO UTRAN COMPLETE message on cell 5?	–	HANDOVER TO UTRAN COMPLETE	1	P
30	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
31	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
32	The SS transmits an UTRAN MOBILITY INFORMATION message to notify CN information.	<–	UTRAN MOBILITY INFORMATION	–	–
33	The UE transmits an UTRAN MOBILITY INFORMATION CONFIRM message.	–>	UTRAN MOBILITY INFORMATION CONFIRM	–	–
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	The CS traffic channel is kept alive by UE for at-least 5 seconds for in-band MSD transfer.	–	–	–	–
37	Set the power levels according to “T2” as per Table 11.5.7.3.2-1/2.	–	–	–	–
38	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
39	The UE transmits RELEASE.	–>	RELEASE	–	–
40	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
41	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
42	The UE transmits RRC CONNECTION RELEASE COMPLETE.	–>	RRC CONNECTION RELEASE COMPLETE	–	–
Note 1: The request to originate a manual eCall may be performed by MMI or AT command.

11.5.7.3.3 Specific message contents

Table 11.5.7.3.3-1: SIB1 for NR Cell 1 (All steps, Table 11.5.7.3.2-3)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.7.3.3-2: Message REGISTRATION REQUEST (step 5, Table 11.5.7.3.2-3)

Derivation path: TS 38.508-1 [4], table 4.7.1-6
Information Element	Value/Remark	Comment	Condition
5GMM capability	‘???? ???? ???? ???? ???? ???? ???? ???1 *’B	5G-SRVCC from NG-RAN to UTRAN supported

Table 11.5.7.3.3-3: UECapabilityEnquiry (step 13, Table 11.5.7.3.2-3)

Derivation Path: 38.508-1 [4], Table 4.6.1-31
Information Element	Value/remark	Comment	Condition
UECapabilityEnquiry ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
ueCapabilityEnquiry SEQUENCE {
ue-CapabilityRAT-RequestList SEQUENCE (SIZE (1.. maxRAT-CapabilityContainers)) OF CapabilityRAT-Request {	2 entries
UE-CapabilityRAT-Request[1] SEQUENCE {		entry 1
rat-Type	nr
}
UE-CapabilityRAT-Request[2] SEQUENCE {		entry 2
rat-Type	utra-fdd-v1610
}
}
lateNonCriticalExtension	Not present
nonCriticalExtension	Not present
}
criticalExtensionsFuture
}
}

Table 11.5.7.3.3-4: UECapabilityInformation (step 14, Table 11.5.7.3.2-3)

Derivation Path: 38.508-1 [4], Table 4.6.1-32
Information Element	Value/remark	Comment	Condition
UECapabilityInformation ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
ueCapabilityInformation SEQUENCE {
ue-CapabilityRAT-ContainerList SEQUENCE (SIZE (0..maxRAT-CapabilityContainers)) OF CapabilityRAT-Request {	2 entries
UE-CapabilityRAT-Request[1] SEQUENCE {		entry 1
rat-Type	nr
ueCapabilityRAT-Container	Not checked
}
UE-CapabilityRAT-Request[2] SEQUENCE {		entry 2
rat-Type	utra-fdd-v1610
ueCapabilityRAT-Container	Octet string	INTER RAT HANDOVER INFO
}
}
lateNonCriticalExtension	Not checked
nonCriticalExtension	Not checked
}
criticalExtensionsFuture	Not checked
}
}

Table 11.5.7.3.3-5: MobilityFromNRCommand (step 28, Table 11.5.7.3.2-3)

Derivation Path: 38.508-1 [4] Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
MobilityFromNRCommand::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier
criticalExtensions CHOICE {
mobilityFromNRCommand ::= SEQUENCE {
targetRAT-Type	utra-fdd-v1610
targetRAT-MessageContainer	HANDOVER TO UTRAN COMMAND(UTRA RRC message)
nas-SecurityParamFromNR	4 LSB of the downlink NAS COUNT
}
}
}

Table 11.5.7.3.3-6: HANDOVER TO UTRAN COMMAND (Table 11.5.7.3.3-5)

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

Table 11.5.7.3.3-7: SECURITY MODE COMMAND (step 30, Table 11.5.7.3.2-3)

Derivation Path: 36.508 [7], Table 4.7B.1-n
Information Element	Condition	Value/remark
Ciphering mode info		Not Present

11.5.8 eCall Only mode / 5GS supports IMS voice over PS session / 5GS supports emergency service / eCall over IMS is supported / RACH failure in NR cell / eCall using the CS domain

11.5.8.1 Test Purpose (TP)

(1)

with { UE is in state 5GMM-DEREGISTERED.eCALL-INACTIVE }

ensure that {

when { UE is requested to make an automatic eCall over IMS and RACH failure is observed in NR cell }

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

}

11.5.8.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 or NG-RAN radio access networks

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	PS on another PS RAT if available with EMS=Y and ECL=Y or 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	PS on another PS RAT if available with EMS=Y or EMS unknown
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] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS.

11.5.8.3 Test description

11.5.8.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport and eCallOverIMS-Support.

– if px_NR_RATComb_Tested = NR_UTRA, UTRA Cell 5 as defined in TS 36.508 [7].

– cell 5 is configured as ”Suitable Neighbour cell”.

– if px_NR_RATComb_Tested = NR_GERAN, GERAN cell 24 as defined in TS 36.508 [7].

– cell 24 is configured as ”Suitable Neighbour cell”.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in state 0-A(Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.8.3.2 Test procedure sequence

Table 11.5.8.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 enter 5GMM-DEREGISTERED.eCALL-INACTIVE state	–	–	–	–
3	An automatic eCall is initiated. (NOTE 1)	–	–	–	–
4	UE transmits preamble on PRACH	–>	PRACH Preamble	–	–
–	EXCEPTION: In parallel to the events described in step 4, the steps specified in Table 11.5.8.3.2-2 should take place.	–	–	–	–
–	EXCEPTION: Steps 5a1 to 5b20 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.	–	–	–	–
5a1	IF (px_NR_RATComb_Tested = NR_UTRA), Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with establishment cause set to Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
5a2	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
5a3	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
5a4	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
5a5	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
5a6	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
5a7	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
5a8	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
5a9	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
5a10-5a15	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.	–	–	–	–
5a16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
5a17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
5a18	The UE transmits RELEASE.	–>	RELEASE	–	–
5a19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
5a20	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
5a21	The UE transmits RRC CONNECTION RELEASE COMPLETE.	–>	RRC CONNECTION RELEASE COMPLETE	–	–
5b1	IF (px_NR_RATComb_Tested = NR_GERAN), Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call?	–>	CHANNEL REQUEST	1	P
5b2	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
5b3	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
5b4	The SS transmits an AUTHENTICATION REQUEST message.	<–	AUTHENTICATION REQUEST	–	–
5b5	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
5b6	The SS transmits a CIPHERING MODE COMMAND.	<–	CIPHERING MODE COMMAND	–	–
5b7	The UE transmits a CIPHERING MODE COMPLETE.	–>	CIPHERING MODE COMPLETE	–	–
5b8	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
5b9-5b15	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.	–	–	–	–
5b16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
5b17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
5b18	The UE transmits RELEASE.	–>	RELEASE	–	–
5b19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
5b20	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.5.8.3.2-2: Parallel behaviour

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

11.5.8.3.3 Specific message contents

Table 11.5.8.3.3-1: SIB1 for NR Cell 1 (All steps, Table 11.5.8.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.8.3.3-2: RRC CONNECTION REQUEST (Step 5a1, Table 11.5.8.3.2-1)

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

Table 11.5.8.3.3-3: CM SERVICE REQUEST (Steps 5a4 and 5b3, Table 11.5.8.3.2-1)

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

Table 11.5.8.3-4: CHANNEL REQUEST (Step 5b1, Table 11.5.8.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.5.9 eCall Only mode / Manual initiation / Emergency registration / Abnormal case / IMS CN sends 486 (Busy Here) / UE performs eCall in CS domain / UTRAN or GERAN / 5GS

11.5.9.1 Test Purpose (TP)

(1)

with { UE is in state 5GMM-DEREGISTERED.eCALL-INACTIVE and requested to make a manual eCall over IMS }

ensure that {

when { UE receives 486 Busy Here in response to INVITE }

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

}

11.5.9.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.229, clauses 5.1.6.11.1, 5.1.6.11.2 and TS 23.167, Annex H.6.

[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 1: 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:

…

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

[TS 23.167 clause H.6]

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

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	PS on another PS RAT if available with EMS=Y and ECL=Y or 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	PS on another PS RAT if available with EMS=Y or EMS unknown
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] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS.

11.5.9.3 Test description

11.5.9.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3.

– if px_NR_RATComb_Tested = NR_UTRA, UTRA Cell 5 as defined in TS 36.508 [7].

– cell 5 is configured as ”Suitable Neighbour cell”.

– if px_NR_RATComb_Tested = NR_GERAN, GERAN cell 24 as defined in TS 36.508 [7].

– cell 24 is configured as ”Suitable Neighbour cell”.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.9.3.2 Test procedure sequence

Table 11.5.9.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 enter 5GMM-DEREGISTERED.eCALL-INACTIVE state.	–	–	–	–
3	A manual eCall is initiated. (Note 1)	–	–	–	–
4-21	Steps 2 to 19 of generic procedure specified in Table 4.5.2.2-2 of 38.508-1 [4] takes place.	–	–	–	–
22-24	Steps 8-10 of generic procedure specified in Table 4.9.11.2.2-1 of TS 38.508-1 [4] with condition ‘eCall’ are performed.	–	–	–	–
25	Step 1 of Annex A.23 of TS 34.229-5 [41] happens	–>	INVITE	–	–
26	SS sends 486 Busy Here response	<–	486 Busy Here	–	–
–	EXCEPTION: Steps 27a1 to 27b20 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.	–	–	–	–
27a1	IF (px_NR_RATComb_Tested = NR_UTRA), Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with establishment cause set to Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
27a2	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
27a3	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
27a4	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
27a5	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
27a6	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
27a7	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
27a8	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
27a9	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 6 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
27a10-27a15	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.	–	–	–	–
27a16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
27a17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
27a18	The UE transmits RELEASE.	–>	RELEASE	–	–
27a19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
27a20	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
27a21	The UE transmits RRC CONNECTION RELEASE COMPLETE.	–>	RRC CONNECTION RELEASE COMPLETE	–	–
27b1	IF (px_NR_RATComb_Tested = NR_GERAN), Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call?	–>	CHANNEL REQUEST	1	P
27b2	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
27b3	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
27b4	The SS transmits an AUTHENTICATION REQUEST message.	<–	AUTHENTICATION REQUEST	–	–
27b5	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
27b6	The SS transmits a CIPHERING MODE COMMAND.	<–	CIPHERING MODE COMMAND	–	–
27b7	The UE transmits a CIPHERING MODE COMPLETE.	–>	CIPHERING MODE COMPLETE	–	–
27b8	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 6 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
27b9-27b15	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.	–	–	–	–
27b16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
27b17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
27b18	The UE transmits RELEASE.	–>	RELEASE	–	–
27b19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
26b20	The SS transmits CHANNEL RELEASE	<–	CHANNEL RELEASE	–	–
Note 1: The request to originate a manual eCall may be performed by MMI or AT command.

11.5.9.3.3 Specific message contents

Table 11.5.9.3.3-1: SIB1 for NR Cell 1 (All steps, Table 11.5.9.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.9.3.3-2: INVITE (step 25, Table 11.5.9.3.2-1)

Derivation path: TS 34.299-5 [41] Step 1 in Annex A.23 Condition A20

Table 11.5.9.3.3-3: 486 Busy Here (step 26, Table 11.5.9.3.2-1)

Derivation path: TS 34.229-1 [35] Annex A.2.21 Condition A1

Table 11.5.9.3.3-4: RRC CONNECTION REQUEST (Step 27a1, Table 11.5.9.3.2-1)

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

Table 11.5.9.3.3-5: CM SERVICE REQUEST (Steps 27a4 and 27b3, Table 11.5.9.3.2-1)

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

Table 11.5.9.3.3-6: CHANNEL REQUEST (Step 27b1, Table 11.5.9.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.5.10 eCall Only mode / Automatic initiation / Emergency registration / Abnormal case / IMS CN sends 600 (Busy Everywhere) / UE performs eCall in CS domain / UTRAN or GERAN / 5GS

11.5.10.1 Test Purpose (TP)

(1)

with { UE is in state 5GMM-DEREGISTERED.eCALL-INACTIVE and requested to make an automatic eCall over IMS }

ensure that {

when { UE receives 600 Busy Everywhere in response to INVITE }

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

}

11.5.10.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.229, clauses 5.1.6.11.1, 5.1.6.11.2 and TS 23.167, Annex H.6.

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

[TS 23.167 clause H.6]

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

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	PS on another PS RAT if available with EMS=Y and ECL=Y or 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	PS on another PS RAT if available with EMS=Y or EMS unknown
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] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS.

11.5.10.3 Test description

11.5.10.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3.

– if px_NR_RATComb_Tested = NR_UTRA, UTRA Cell 5 as defined in TS 36.508 [7].

– cell 5 is configured as ”Suitable Neighbour cell”.

– if px_NR_RATComb_Tested = NR_GERAN, GERAN cell 24 as defined in TS 36.508 [7].

– cell 24 is configured as ”Suitable Neighbour cell”.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.10.3.2 Test procedure sequence

Table 11.5.10.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 enter 5GMM-DEREGISTERED.eCALL-INACTIVE state.	–	–	–	–
3	An automatic eCall is initiated. (Note 1)	–	–	–	–
4-21	Steps 2 to 19 of generic procedure specified in Table 4.5.2.2-2 of 38.508-1 [4] takes place.	–	–	–	–
22-24	Steps 8-10 of generic procedure specified in Table 4.9.11.2.2-1 of TS 38.508-1 [4] with condition ‘eCall’ are performed.	–	–	–	–
25	Step 1 of Annex A.23 of TS 34.229-5 [41] happens	–>	INVITE	–	–
26	SS sends 600 Busy Everywhere response	<–	600 Busy Everywhere	–	–
–	EXCEPTION: Steps 27a1 to 27b20 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.	–	–	–	–
27a1	IF (px_NR_RATComb_Tested = NR_UTRA), Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with establishment cause set to Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
27a2	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
27a3	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
27a4	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
27a5	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
27a6	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
27a7	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
27a8	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
27a9	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
27a10-27a15	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.	–	–	–	–
27a16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
27a17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
27a18	The UE transmits RELEASE.	–>	RELEASE	–	–
27a19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
27a20	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
27a21	The UE transmits RRC CONNECTION RELEASE COMPLETE.	–>	RRC CONNECTION RELEASE COMPLETE	–	–
27b1	IF (px_NR_RATComb_Tested = NR_GERAN), Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call?	–>	CHANNEL REQUEST	1	P
27b2	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
27b3	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
27b4	The SS transmits an AUTHENTICATION REQUEST message.	<–	AUTHENTICATION REQUEST	–	–
27b5	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
27b6	The SS transmits a CIPHERING MODE COMMAND.	<–	CIPHERING MODE COMMAND	–	–
27b7	The UE transmits a CIPHERING MODE COMPLETE.	–>	CIPHERING MODE COMPLETE	–	–
27b8	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
27b9-27b15	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.	–	–	–	–
27b16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
27b17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
27b18	The UE transmits RELEASE.	–>	RELEASE	–	–
27b19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
26b20	The SS transmits CHANNEL RELEASE	<–	CHANNEL RELEASE	–	–
Note 1: The request to originate an automatic eCall may be performed by MMI or AT command.

11.5.10.3.3 Specific message contents

Table 11.5.10.3.3-1: SIB1 for NR Cell 1 (All steps, Table 11.5.10.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.10.3.3-2: INVITE (step 25, Table 11.5.10.3.2-1)

Derivation path: TS 34.299-5 [41] Step 1 in Annex A.23 Condition A21

Table 11.5.10.3.3-3: 600 Busy Everywhere (step 26, Table 11.5.10.3.2-1)

Derivation path: TS 34.229-1 [35] Annex A.2.22 Condition A1

Table 11.5.10.3.3-4: RRC CONNECTION REQUEST (Step 27a1, Table 11.5.10.3.2-1)

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

Table 11.5.10.3.3-5: CM SERVICE REQUEST (Steps 27a4 and 27b3, Table 11.5.10.3.2-1)

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

Table 11.5.10.3.3-6: CHANNEL REQUEST (Step 27b1, Table 11.5.10.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.5.11 eCall Only mode / Automatic initiation / Emergency registration / Abnormal case / IMS CN sends 603 (Decline) / UE performs eCall in CS domain / UTRAN or GERAN / 5GS

11.5.11.1 Test Purpose (TP)

(1)

with { UE is in state 5GMM-DEREGISTERED.eCALL-INACTIVE and requested to make an automatic eCall over IMS }

ensure that {

when { UE receives 603 Decline in response to INVITE }

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

}

11.5.11.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.229, clauses 5.1.6.11.1, 5.1.6.11.2 and TS 23.167, Annex H.6.

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

[TS 23.167 clause H.6]

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

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	PS on another PS RAT if available with EMS=Y and ECL=Y or 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	PS on another PS RAT if available with EMS=Y or EMS unknown
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] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS.

11.5.11.3 Test description

11.5.11.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3.

– if px_NR_RATComb_Tested = NR_UTRA, UTRA Cell 5 as defined in TS 36.508 [7].

– cell 5 is configured as ”Suitable Neighbour cell”.

– if px_NR_RATComb_Tested = NR_GERAN, GERAN cell 24 as defined in TS 36.508 [7].

– cell 24 is configured as ”Suitable Neighbour cell”.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.11.3.2 Test procedure sequence

Table 11.5.11.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 enter 5GMM-DEREGISTERED.eCALL-INACTIVE state.	–	–	–	–
3	An automatic eCall is initiated. (Note 1)	–	–	–	–
4-21	Steps 2 to 19 of generic procedure specified in Table 4.5.2.2-2 of 38.508-1 [4] takes place.	–	–	–	–
22-24	Steps 8-10 of generic procedure specified in Table 4.9.11.2.2-1 of TS 38.508-1 [4] with condition ‘eCall’ are performed.	–	–	–	–
25	Step 1 of Annex A.23 of TS 34.229-5 [41] happens	–>	INVITE	–	–
26	SS sends 603 Decline response	<–	603 Decline	–	–
–	EXCEPTION: Steps 27a1 to 27b20 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.	–	–	–	–
27a1	IF (px_NR_RATComb_Tested = NR_UTRA), Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with establishment cause set to Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
27a2	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
27a3	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
27a4	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
27a5	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
27a6	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
27a7	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
27a8	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
27a9	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
27a10-27a15	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.	–	–	–	–
27a16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
27a17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
27a18	The UE transmits RELEASE.	–>	RELEASE	–	–
27a19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
27a20	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
27a21	The UE transmits RRC CONNECTION RELEASE COMPLETE.	–>	RRC CONNECTION RELEASE COMPLETE	–	–
27b1	IF (px_NR_RATComb_Tested = NR_GERAN), Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call?	–>	CHANNEL REQUEST	1	P
27b2	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
27b3	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
27b4	The SS transmits an AUTHENTICATION REQUEST message.	<–	AUTHENTICATION REQUEST	–	–
27b5	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
27b6	The SS transmits a CIPHERING MODE COMMAND.	<–	CIPHERING MODE COMMAND	–	–
27b7	The UE transmits a CIPHERING MODE COMPLETE.	–>	CIPHERING MODE COMPLETE	–	–
27b8	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
27b9-27b15	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.	–	–	–	–
27b16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
27b17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
27b18	The UE transmits RELEASE.	–>	RELEASE	–	–
27b19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
26b20	The SS transmits CHANNEL RELEASE	<–	CHANNEL RELEASE	–	–
Note 1: The request to originate an automatic eCall may be performed by MMI or AT command.

11.5.11.3.3 Specific message contents

Table 11.5.11.3.3-1: SIB1 for NR Cell 1 (All steps, Table 11.5.11.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.11.3.3-2: INVITE (step 25, Table 11.5.11.3.2-1)

Derivation path: TS 34.299-5 [41] Step 1 in Annex A.23 Condition A21

Table 11.5.11.3.3-3: 603 Decline (step 26, Table 11.5.11.3.2-1)

Derivation path: TS 34.229-1 [35] Annex A.2.23 Condition A1

Table 11.5.11.3.3-4: RRC CONNECTION REQUEST (Step 27a1, Table 11.5.11.3.2-1)

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

Table 11.5.11.3.3-5: CM SERVICE REQUEST (Steps 27a4 and 27b3, Table 11.5.11.3.2-1)

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

Table 11.5.11.3.3-6: CHANNEL REQUEST (Step 27b1, Table 11.5.11.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.5.12 eCall Only mode / 5GS supports IMS voice over PS session / 5GS supports emergency service / eCall over IMS is not supported on 5GS / eCall over EPS

11.5.12.1 Test Purpose (TP)

(1)

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

ensure that {

when { eCallOverIMS-Support on 5GS is not indicated, eCallOverIMS-Support-r14 on EPS is indicated and UE is requested to make an automatic eCall }

then { UE establishes eCall over EPS }

}

11.5.12.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.2.2.7, 6.2.2 , TS 38.331, clause 6.2.2 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> else:

2> if the frequency band indicated in the freqBandIndicator is part of the frequency bands supported by the UE and it is not a downlink only band; or

…

3> forward the ims-EmergencySupport to upper layers, if present;

[TS 23.167 clause H.6]

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

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	PS on another PS RAT if available with EMS=Y and ECL=Y or 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	PS on another PS RAT if available with EMS=Y or EMS unknown
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] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS.

[TS 38.331, clause 6.2.2]

eCallOverIMS-Support

Indicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell.

[TS 36.331, clause 6.2.2]

eCallOverIMS-Support

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

11.5.12.3 Test description

11.5.12.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-6 as defined in TS 38.508-1 [4], sub-clause 4.4.3.1.2.

– E-UTRA Cell 1 as defined in TS 36.508 [7] Table 4.4.2-2. System information combination 31 as defined in TS 36.508 [7], sub-clause 4.4.3.1.1.

UE:

– the eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-24.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.5.12.3.2 Test procedure sequence

Table 11.5.12.3.2-1 illustrate the downlink power levels to be applied for NR Cell 1, and E-UTRA Cell 1 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble.

Table 11.5.12.3.2-1: Power levels in FR1

Parameter

Unit

NR Cell 1

E-UTRA

Cell 1

Remark

SS/PBCH

SSS EPRE

dBm/

SCS

-85

–

Cell-specific RS EPRE

dBm/15kHz

-93

Editor’s Note: FR2 power levels are FFS

11.5.12.3.3 Test procedure sequence

Table 11.5.12.3.3-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 enter eCALL-INACTIVE state.	–	–	–	–
3	An automatic eCall is initiated. (Note 1)	–	–	–	–
–	The following messages are to be observed on E-UTRA Cell 1 unless explicitly stated otherwise	–	–	–	–
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-23	Steps 7 to 25 of Generic Test Procedure for eCall over IMS establishment in EUTRA: eCall Only Support specified in clause 4.5A.27 of TS 36.508 [7] take place.	–	–	–	–
24	Release eCall over IMS using the generic procedure described in TS 34.229-1 [35] subclause C.33	–	–	–	–
25	The SS releases the RRC connection.	<–	RRCConnectionRelease	–	–
Note 1: The request to originate an automatic eCall may be performed by MMI or AT command.

11.5.12.3.4 Specific message contents

Table 11.5.12.3.4-1: Message SystemInformationBlockType1 for E-UTRA Cell 1 (All Steps)

Derivation path: TS 36.508 [7] table 4.4.3.2-3 Condition eCalloverIMS

Table 11.5.12.3.4-2: SIB1 of NR Cell 1 (All steps)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28
Information Element	Value/remark	Comment	Condition
SIB1 ::= SEQUENCE {
eCallOverIMS-Support	Not present
}

Table 11.5.12.3.4-3: Message ATTACH ACCEPT (step 14, Table 11.5.12.3.3-1)

Derivation path: TS 36.508 [7] table 4.7.2-1
Information Element	Value/Remark	Comment	Condition
EPS attach result	‘010’B	”Combined EPS/IMSI attach”
EPS network feature support	‘0000 0011’B	emergency bearer services in S1 mode and IMS voice over PS session in S1 mode are supported

11.5.13 eCall capable / Manual initiation / MSD Transfer failure / UE performs eCall in CS domain after Timer expiry / UTRAN or GERAN / 5GS

11.5.13.1 Test Purpose (TP)

(1)

with { UE in state 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode and requested to make a manual eCall over IMS }

ensure that {

when { UE does not receive any response to INVITE }

then { UE establishes the eCall using CS domain (UTRA or GERAN) after emerg-request timer expiry }

}

11.5.13.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.229, clauses 5.1.6.11.2, 5.1.6.8.1, Table 7.8.1 and TS 23.167, Annex H.6.

[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:

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

[TS 24.229 Table 7.8.1]

Table 7.8.1: IM CN subsystem

Timer	Value to be applied at the UE	Value to be applied at the P-CSCF	Value to be applied at the S-CSCF	Meaning
emerg-request	Configurable value between 5 seconds and 15 seconds	not applicable	not applicable	The timer is used by the UE during initial request for emergency service. For detailed usage of the timer see subclause 5.1.6.8.1.

[TS 24.229 clause 5.1.6.8.1]

If the UE supports the emerg-request timer defined in Table 7.8.1, the UE shall start the emerg-request timer when sending the initial INVITE request for emergency service. The UE shall stop the timer upon receipt of any 18x provisional SIP response. When the emerg-request timer expires, the UE shall consider that the emergency service request has failed and apply the procedures related to emergency service request failure that are defined in 3GPP TS 23.167 [4B] subclause 7.3 with clarifications in clause H.5. The UE may support being configured for the emerg-request timer using one or more of the following methods:

a) the Timer_Emerg-request leaf of the EF_IMSConfigData file described in 3GPP TS 31.102 [15C];

b) the Timer_Emerg-request leaf of the EF_{IMSConfigData} file described in 3GPP TS 31.103 [15B]; and

c) the Timer_Emerg-request leaf of 3GPP TS 24.167 [8G].

If the UE is configured with both the Timer_Emerg-request leaf of 3GPP TS 24.167 [8G] and the Timer_Emerg-request leaf of the EF_{IMSConfigData} file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the Timer_Emerg-request leaf of the EF_{IMSConfigData} file shall take precedence.

[TS 23.167 clause H.6]

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

	PS Available	VoIMS	EMS	ECL	First eCall Attempt	Second eCall Attempt
A	Y	Y	Y	Y	PS	PS on another PS RAT if available with EMS=Y and ECL=Y or 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	PS on another PS RAT if available with EMS=Y or EMS unknown
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] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.501 [48] and TS 23.502 [49]. ECL = eCall Over IMS support as indicated by the eCall support indicator defined in TS 23.401 [28] and TS 23.501 [48]. NOTE 1: As an implementation option, when the first attempt uses PS and fails for reasons other than related to IMS, the second attempt may use PS with a different 3GPP RAT. In this case the UE, can make a third attempt using CS.

11.5.13.3 Test description

11.5.13.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3.

– if px_NR_RATComb_Tested = NR_UTRA, UTRA Cell 5 as defined in TS 36.508 [7].

– cell 5 is configured as ”Suitable Neighbour cell”.

– if px_NR_RATComb_Tested = NR_GERAN, GERAN cell 24 as defined in TS 36.508 [7].

– cell 24 is configured as ”Suitable Neighbour cell”.

UE:

– the eCall capable UE is equipped with ecall enabled USIM configured as per TS 38.508-1 [4] Table 6.4.1-23.

Preamble:

– The UE is in test state 1N-A as defined in TS 38.508-1 [4], subclause 4.4A.2 on NR Cell 1.

11.5.13.3.2 Test procedure sequence

Table 11.5.13.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	A manual eCall is initiated. (Note 1)	–	–	–	–
2-11	Steps 1-10 of generic procedure specified in Table 4.9.11.2.2-1 of TS 38.508-1 [4] with condition ‘eCall’ are performed.	–	–	–	–
12	Step 1 of Annex A.23 of TS 34.229-5 [41] happens	–>	INVITE	–	–
13	SS waits 15s for emerg-request timer to expire so that MSD transfer fails.	–	–	–	–
–	EXCEPTION: Steps 14a1 to 14b20 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.	–	–	–	–
14a1	IF (px_NR_RATComb_Tested = NR_UTRA), Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with establishment cause set to Emergency Call?	–>	RRC CONNECTION REQUEST	1	P
14a2	The SS transmits an RRC CONNECTION SETUP message.	<–	RRC CONNECTION SETUP	–	–
14a3	The UE transmits an RRC CONNECTION SETUP COMPLETE message.	–>	RRC CONNECTION SETUP COMPLETE	–	–
–	EXCEPTION: In parallel to the event described in steps 1a6 to 1a17, if initiated by the UE the steps 5 to 13 of the generic procedure for Registration on PS specified in TS 34.108 subclause 7.2.2.2.3 take place.	–	–	–	–
14a4	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
14a5	The SS transmits an AUTHENTICATION REQUEST.	<–	AUTHENTICATION REQUEST	–	–
14a6	The UE transmits AUTHENTICATION RESPONSE.	–>	AUTHENTICATION RESPONSE	–	–
14a7	The SS transmits a SECURITY MODE COMMAND message for the CS domain.	<–	SECURITY MODE COMMAND	–	–
14a8	The UE transmits a SECURITY MODE COMPLETE message.	–>	SECURITY MODE COMPLETE	–	–
14a9	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 6 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
14a10-14a15	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.	–	–	–	–
14a16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
14a17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
14a18	The UE transmits RELEASE.	–>	RELEASE	–	–
14a19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
14a20	The SS transmits an RRC CONNECTION RELEASE message.	<–	RRC CONNECTION RELEASE	–	–
14a21	The UE transmits RRC CONNECTION RELEASE COMPLETE.	–>	RRC CONNECTION RELEASE COMPLETE	–	–
14b1	IF (px_NR_RATComb_Tested = NR_GERAN), Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call?	–>	CHANNEL REQUEST	1	P
14b2	The SS transmits an IMMEDIATE ASSIGNMENT message.	<–	IMMEDIATE ASSIGNMENT	–	–
14b3	Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”?	–>	CM SERVICE REQUEST	1	P
14b4	The SS transmits an AUTHENTICATION REQUEST message.	<–	AUTHENTICATION REQUEST	–	–
14b5	The UE transmits an AUTHENTICATION RESPONSE message.	–>	AUTHENTICATION RESPONSE	–	–
14b6	The SS transmits a CIPHERING MODE COMMAND.	<–	CIPHERING MODE COMMAND	–	–
14b7	The UE transmits a CIPHERING MODE COMPLETE.	–>	CIPHERING MODE COMPLETE	–	–
14b8	Check: Does the UE transmit an EMERGENCY SETUP message with Emergency Service Category IE bit 6 set to 1 and all other bits are set to 0?	–>	EMERGENCY SETUP	1	P
14b9-14b15	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.	–	–	–	–
14b16	Traffic channel is kept active for at least 5 seconds.	–	–	–	–
14b17	The SS transmits DISCONNECT.	<–	DISCONNECT	–	–
14b18	The UE transmits RELEASE.	–>	RELEASE	–	–
14b19	The SS transmits RELEASE COMPLETE.	<–	RELEASE COMPLETE	–	–
14b20	The SS transmits CHANNEL RELEASE	<–	CHANNEL RELEASE	–	–
Note 1: The request to originate a manual eCall may be performed by MMI or AT command.

11.5.13.3.3 Specific message contents

Table 11.5.13.3.3-1: SIB1 for NR Cell 1 (All steps, Table 11.5.13.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.6.1-28 Condition eCalloverIMSforNR

Table 11.5.13.3.3-2: INVITE (step 12, Table 11.5.13.3.2-1)

Derivation path: TS 34.229-5 [41] Step 1 in Annex A.23 Condition A20

Table 11.5.13.3.3-3: RRC CONNECTION REQUEST (Step 14a1, Table 11.5.13.3.2-1)

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

Table 11.5.13.3.3-4: CM SERVICE REQUEST (Steps 14a4 and 14b3, Table 11.5.13.3.2-1)

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

Table 11.5.13.3.3-5: CHANNEL REQUEST (Step 14b1, Table 11.5.13.3.2-1)

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