13.1.19 Emergency call setup from E-UTRAN RRC_IDLE / IMS VoPS supported / EMC BS not supported / CS fallback to UTRAN or GERAN with redirection
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
13.1.19.1 Test Purpose (TP)
(1)
with { UE is in E-UTRA RRC_IDLE state having received ATTACH ACCEPT set to IMS Voice over PS supported and Emergency bearer services indicator not supported }
ensure that {
when { the user initiates an emergency call }
then { UE transmits an RRCConnectionRequest message with establishmentCause set to "emergency" and an EXTENDED SERVICE REQUEST message with Service type IE set to "mobile originating CS fallback emergency call or 1xCS fallback emergency call" and attempts a CS emergency call on UTRAN or GERAN cell }
}
13.1.19.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.272 clause 4.6, TS 24.301 clause 5.6.1.1 and TS 23.167 Annex H. Unless otherwise stated these are Rel-9 requirements.
[TS 23.272, clause 4.6]
When UE is performing CS fallback procedure for Mobile Originating Call for the purpose of emergency call, it shall indicate to the MME that this CS fallback request is for emergency purpose. MME also indicates to the E-UTRAN via the appropriate S1-AP message that this CS fallback procedure is for emergency purpose. If PS handover is initiated, E‑UTRAN may indicate priority level of the CS fallback to the target RAT, as specified in TS 25.413 [29], in order to prepare radio resource at target RAT in appropriate way, e.g. priority allocation of the RAB resource.
NOTE 1: E-UTRAN may use the emergency indication for selecting a particular radio access network (2G or 3G) for CS emergency handling.
[TS 24.301, clause 5.6.1.1]
The UE shall invoke the service request procedure when:
…
d) the UE in EMM-IDLE or EMM-CONNECTED mode is configured to use CS fallback and has a mobile originating CS fallback request from the upper layer;
[TS 23.167, Annex H]
This clause details the domain priority and selection (see clause 7.3) for UE that attempts to make an emergency session for UTRAN and E-UTRAN radio access networks based on the UE attach status to CS or PS domains and the network support for IMS emergency and IMS voice over PS.
The following table (Table H.1) defines these rules based on the UE (last 2 columns) for different initial conditions (first 4 columns) when an emergency session is initiated and when the UE is not in limited service state.
Table H.1: Domain Selection Rules for emergency session attempts for UTRAN and E-UTRAN radio access networks
CS Attached |
PS Attached |
VoIMS |
EMS |
First EMC Attempt |
Second EMC Attempt |
|
A |
N |
Y |
Y |
Y |
PS |
CS if available and supported |
B |
N |
Y |
N |
Y |
PS or CS if the emergency session includes at least voice. PS if the emergency session contains only media other than voice. |
PS if first attempt in CS CS if first attempt in PS |
C |
N |
Y |
Y or N |
N |
CS if available and supported and if the emergency session includes at least voice. |
No attempt is made in the PS domain |
D |
Y |
N |
Y or N |
Y or N |
CS if the emergency session includes at least voice. PS if available and EMS is "Y" and emergency session contains only media other than voice. |
PS if available and EMS is "Y" |
E |
Y |
Y |
Y |
Y |
If the emergency session includes at least voice, follow rules in TS 22.101 [8] which say to use the same domain as for a non-EMC PS if the emergency session contains only media other than voice. |
PS if first attempt in CS CS if first attempt in PS |
F |
Y |
Y |
Y or N |
N |
CS if the emergency session includes at least voice. |
No attempt is made in the PS domain |
G |
Y |
Y |
N |
Y |
CS if the emergency session includes at least voice. PS if the emergency session contains only media other than voice. |
PS |
EMC = Emergency Session. EMC includes also normal calls initiated in the CS domain that are treated by the CS CN as emergency calls. 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.060 [2]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28] and TS 23.060 [2]. NOTE: If the UE selects the CS domain and initiates a normal call using the dialled local emergency number (see clause 7.1.2), and the UE enters limited service state (e.g. due to a Location Registration failing), then the UE camps on an acceptable cell (see TS 23.122 [41]) and may proceed with the EMC by initiating an emergency call in limited service state. |
13.1.19.3 Test description
13.1.19.3.1 Pre-test conditions
System Simulator:
– Cell 1.
– System information combination 10 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cell.
– If (px_RATComb_Tested = EUTRA_UTRA)
– cell 5 is configured as ”Suitable Neighbour cell”
– If (px_RATComb_Tested = EUTRA_GERAN)
– cell 24 is configured as ”Suitable Neighbour cell”
UE:
None.
Preamble:
– The UE is in state Registered, Idle mode (state 2) on Cell 1 according to [18].
13.1.19.3.2 Test procedure sequence
Table 13.1.19.3.2-0: instances of cell power level and parameter changes
Parameter |
Unit |
Cell 1 |
Remark |
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
-115 |
The power levels are such that reselection back to cell 1 should not occur |
Table 13.1.19.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
Cause the UE to originate emergency call. (see Note 1) |
– |
– |
– |
– |
2 |
Check: Does the UE transmit an RRCConnectionRequest message on Cell 1? |
–> |
RRCConnectionRequest |
1 |
P |
3 |
The SS transmits an RRCConnectionSetup message on Cell 1. |
<– |
RRCConnectionSetup |
– |
– |
4 |
Check: Does the UE transmit an RRCConnectionSetupComplete message on Cell 1 including an EXTENDED SERVICE REQUEST message with Service type IE set to "mobile originating CS fallback emergency call or 1xCS fallback emergency call"? |
–> |
RRCConnectionSetupComplete |
1 |
P |
– |
EXCEPTION: Steps 5a1 to 5b15 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_RATComb_Tested = EUTRA_UTRA), the SS reconfigures: Cell 1 as a "Suitable cell", Cell 5 as the "Serving cell". |
– |
– |
– |
– |
5a2 |
The SS transmits an RRCConnectionRelease message indicating redirection to cell 5 |
<– |
RRCConnectionRelease |
||
5a3 |
Check: Does the UE transmit a RRC CONNECTION REQUEST message on Cell 5 with Establishment cause: Emergency Call? |
–> |
RRC CONNECTION REQUEST |
1 |
P |
5a3A1 |
The SS changes cell 1 power level according to the row “T1” in table 13.1.19.3.2-0 |
– |
– |
– |
– |
5a4 |
The SS transmits an RRC CONNECTION SETUP message. |
<– |
RRC CONNECTION SETUP |
– |
– |
5a5 |
The UE transmits an RRC CONNECTION SETUP COMPLETE message. |
–> |
RRC CONNECTION SETUP COMPLETE |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 5a6 to 5a17 the step specified in Table 13.1.19.3.2-2 takes place. |
– |
– |
– |
– |
5a6 |
The UE transmits a CM SERVICE REQUEST with CM Service Type indicating ‘Emergency call establishment. |
–> |
CM SERVICE REQUEST |
– |
– |
5a7 |
The SS transmits AUTHENTICATION REQUEST |
<– |
AUTHENTICATION REQUEST |
– |
– |
5a8 |
The UE transmits AUTHENTICATION RESPONSE |
–> |
AUTHENTICATION RESPONSE |
– |
– |
5a9 |
The SS transmits a SECURITY MODE COMMAND message for the CS domain. |
<– |
SECURITY MODE COMMAND |
– |
– |
5a10 |
The UE transmits a SECURITY MODE COMPLETE message. |
–> |
SECURITY MODE COMPLETE |
– |
– |
5a11 |
The UE transmits an EMERGENCY SETUP message. |
–> |
EMERGENCY SETUP |
– |
– |
5a12-5a17 |
Steps 12 to 17 of the test procedure in TS 34.123-1 [7] subclause 13.2.1.1 are performed. NOTE: Emergency call is established. |
– |
– |
– |
– |
5a17A |
The SS transmits a SECURITY MODE COMMAND message for the PS domain. (See Note 2) |
<– |
SECURITY MODE COMMAND |
– |
– |
5a17B |
The UE transmits a SECURITY MODE COMPLETE message. |
–> |
SECURITY MODE COMPLETE |
– |
– |
5a18 |
The SS transmits a ROUTING AREA UPDATE ACCEPT. |
<– |
ROUTING AREA UPDATE ACCEPT |
– |
– |
5a19 |
The UE sends ROUTING AREA UPDATE COMPLETE. |
–> |
ROUTING AREA UPDATE COMPLETE |
– |
– |
5a20 |
Wait for 2 seconds to provide enough time to finish up optional IMS deregistration. |
– |
– |
||
5b1 |
IF (px_RATComb_Tested = EUTRA_GERAN), the SS reconfigures: Cell 1 as a "Suitable cell", Cell 24 as the "Serving cell". |
– |
– |
– |
– |
5b2 |
The SS transmits an RRCConnectionRelease message indicating redirection to cell 24 |
<– |
RRCConnectionRelease |
– |
– |
5b3 |
Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call? |
–> |
CHANNEL REQUEST |
1 |
P |
5b3A1 |
The SS changes cell 1 power level according to the row “T1” in table 13.1.19.3.2-0 |
– |
– |
– |
– |
5b4 |
The SS transmits an IMMEDIATE ASSIGNMENT message. |
<– |
IMMEDIATE ASSIGNMENT |
– |
– |
5b5 |
The UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment” |
–> |
CM SERVICE REQUEST |
– |
– |
5b5A |
The UE transmits a Classmark Change message |
–> |
CLASSMARK CHANGE |
– |
– |
– |
EXCEPTION: Step 5b5B describes behaviour that depends on the UE capability. |
– |
– |
– |
– |
5b5B |
IF pc_UTRA then the UE transmits a Utran Classmark message |
–> |
UTRAN CLASSMARK CHANGE |
– |
– |
5b6 |
The SS transmits an AUTHENTICATION REQUEST message. |
<– |
AUTHENTICATION REQUEST |
– |
– |
5b7 |
The UE transmits an AUTHENTICATION RESPONSE message. |
–> |
AUTHENTICATION RESPONSE |
– |
– |
5b7A |
The SS transmits a CIPHERING MODE COMMAND message. |
<– |
CIPHERING MODE COMMAND |
– |
– |
5b7B |
The UE transmits a CIPHERING MODE COMPLETE message. |
–> |
CIPHERING MODE COMPLETE |
– |
– |
5b8 |
The UE transmits an EMERGENCY SETUP message. |
–> |
EMERGENCY SETUP |
– |
– |
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. |
– |
– |
– |
– |
5b16 |
The SS transmits DISCONNECT. |
<– |
DISCONNECT |
– |
– |
5b17 |
The UE transmits RELEASE.. |
–> |
RELEASE |
– |
– |
5b18 |
The SS transmits RELEASE COMPLETE. |
<– |
RELEASE COMPLETE |
– |
– |
5b19 |
The SS transmits CHANNEL RELEASE, with GPRS Resumption Field set to 1 |
<– |
CHANNEL RELEASE |
– |
– |
5b20-5b30 |
Steps 1 to 11 of the generic test procedure in sub clause 6.4.2.9 are performed. |
– |
– |
– |
– |
– |
At the end of this test procedure sequence, the UE is in end state GERAN idle (G1) according to TS 36.508. |
– |
– |
– |
– |
Note 1: The trigger in step 1 is the same as in the generic procedure in 36.508 clause 6.4.3.5. Note 2: A real network will initiate the security mode command procedure for the PS domain immediately after receiving the ROUTING AREA UPDATE REQUEST, but in this test procedure it was chosen to complete the procedure for CS domain first, in order to avoid the possibility of a security mode command procedure running in parallel with another RRC procedure. |
Table 13.1.19.3.2-2: Parallel behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The UE transmits a ROUTING AREA UPDATE REQUEST message. |
–> |
ROUTING AREA UPDATE REQUEST |
– |
– |
13.1.19.3.3 Specific message contents
Table 13.1.19.3.3-1: ATTACH ACCEPT (Preamble)
Derivation Path: 36.508 Table 4.7.2-1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
EPS network feature support |
‘0000 0001’B |
IMS voice over PS session in S1 mode supported, emergency bearer services in S1 mode not supported |
Table 13.1.19.3.3-2: RRCConnectionRequest (step 2, Table 13.1.19.3.2-1)
Derivation Path: 36.508, Table 4.6.1-16 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCConnectionRequest ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcConnectionRequest-r8 SEQUENCE { |
|||
establishmentCause |
emergency |
||
} |
|||
} |
|||
} |
Table 13.1.19.3.3-3: EXTENDED SERVICE REQUEST (step 4, Table 13.1.19.3.2-1)
Derivation Path: TS 36.508, Table 4.7.2-14A |
|||
Information Element |
Value/remark |
Comment |
Condition |
Service type |
‘0010’B |
mobile originating CS fallback emergency call or 1xCS fallback emergency call |
|
CSFB response |
Not present |
Table 13.1.19.3.3-4: RRCConnectionRelease (step 5a2, Table 13.1.19.3.2-1)
Derivation Path: TS 36.508, Table 4.7.2-14A |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCConnectionRelease ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
rrcConnectionRelease-r8 SEQUENCE { |
|||
redirectedCarrierInfo ::= CHOICE { |
|||
Utran |
f8 |
||
} |
|||
} |
|||
} |
Table 13.1.19.3.3-5: RRCConnectionRelease (step 5b2, Table 13.1.19.3.2-1)
Derivation Path: TS 36.508, Table 4.7.2-14A |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCConnectionRelease ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
rrcConnectionRelease-r8 SEQUENCE { |
|||
redirectedCarrierInfo ::= CHOICE { |
|||
Geran |
f11 |
||
} |
|||
} |
|||
} |