13.1.21 Emergency Call setup from E-UTRA RRC_IDLE but IMS voice not available / IMS VoPS supported / EMC BS supported / UE performs emergency call via CS domain
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.21.1 Test Purpose (TP)
(1)
with { UE having received ATTACH ACCEPT set to IMS Voice over PS supported and Emergency bearer services indicator supported is in IMS voice not available state}
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.21.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.229 clauses L.3.1.2, TS 23.221 clause 7.2a, TS 23.167 clause H.5, TS 23.272 clause 4.6 and TS 24.301 clause 5.6.1.1. Unless otherwise stated these are Rel-9 requirements.
[TS 24.229, clause L.3.1.2]
The UE indicates to the non-access stratum the status of being not available for voice over PS when:
I) in response to receiving the IMSVoPS indicator indicating voice is supported, the UE:
– initiated an initial registration as specified in subclause 5.1.1.2, received a final response to the REGISTER request sent, but the conditions for indicating the status of being available for voice over PS are not met; or
– did not initiate an initial registration as specified in subclause 5.1.1.2 and, these conditions for indicating the status of being available for voice over PS are not met; or
II) the conditions for indicating the status of being available for voice over PS are no longer met.
NOTE 3: The status of being not available for voice over PS is used for domain selection for UE originating sessions / calls specified in 3GPP TS 23.221 [6] subclause 7.2a.
[TS 23.221, clause 7.2a]
To allow for appropriate domain selection for originating voice calls, a CSFB and/or IMS/CS-voice capable UE is set to behave as "Voice centric" or "Data centric" in E-UTRAN:
– A UE set to "Voice centric" shall always try to ensure that Voice service is possible. A CSFB and an IMS/CS-voice capable UE set to "Voice centric" unable to obtain voice service in E-UTRAN (e.g. CSFB and IMS voice are not supported or the configured preferences on how to handle voice services prevent usage of any available voice services or 3GPP PS Data Off activated and IMS voice is not included in 3GPP PS Data Off Exempt Services), shall disable the E-UTRAN capability, which results in re-selecting GERAN or UTRAN. The E-UTRAN capability is re-enabled by the UE under the conditions described in TS 24.301 [34]. A voice centric CSFB capable UE that receives "CSFB Not Preferred" or "SMS-only" indication as a result of combined EPS/IMSI attach or combined TA/LA Update procedures and unable to obtain voice services over IMS shall disable the E-UTRAN capability, which results in re-selecting GERAN or UTRAN.
[TS 23.167, clause H.5]
This clause details the domain priority and selection (see clause 7.3) for UE that attempts to make an emergency session for UTRAN, E-UTRAN or NG-RAN 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.
For NG-eCall (eCall over IMS) domain selection in clause H.6 applies. This clause is not applicable for NG-eCall.
Table H.1: Domain Selection Rules for emergency session attempts for UTRAN, E-UTRAN or NG-RAN 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 |
PS if ESFB is "Y" (NOTE 5). Else CS or PS for another 3GPP RAT with EMS or ESFB set to "Y" if available and supported and if the emergency session includes at least voice. Else PS for another 3GPP RAT with EMS or ESFB set to "Y" if available and supported if the emergency session contains only media other than voice. |
PS if first attempt in CS CS if first attempt in PS |
D |
Y |
N |
Y or N |
Y or N |
CS if the emergency session includes at least voice. PS if available and EMS or ESFB is "Y" and emergency session contains only media other than voice. |
PS if available and EMS or ESFB 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 (NOTE 2) 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 |
PS if ESFB is "Y" (NOTE 5). Else CS if the emergency session includes at least voice. |
CS if first attempt in PS PS for another 3GPP RAT if available and supported and EMS or ESFB is "Y" if first attempt in CS. |
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], TS 23.060 [2] and TS 23.502 [49]. EMS = IMS Emergency Services supported as indicated by Emergency Service Support indicator as defined in TS 23.401 [28], TS 23.060 [2], TS 23.501 [48] and TS 23.502 [49]. ESFB = Emergency Services Fallback for 5GS as defined in TS 23.501 [48] and TS 23.502 [49]. NOTE 1: 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. NOTE 2: Use of the same domain as for a non-EMC is restricted to UTRAN, E-UTRAN and NG-RAN access (e.g. excludes WLAN). NOTE 3: A UE in dual registration mode as defined in TS 23.501 [48] that is registered to both EPC and 5GC assumes attachment, for the purpose of the "PS Attached" column, to whichever of EPC or 5GC indicates EMS or ESFB as "Y". When both EPC and 5GC indicate EMS or ESFB as "Y", the UE shall assume attachment to EPC when camped on or connected to E-UTRA connected to EPC and to 5GC when camped on or connected to NR or E-UTRA connected to 5GC. NOTE 4: The other 3GPP RAT for row C and row F can be any of UTRA, E-UTRAN connected to EPC, E-UTRA connected to 5GC or NR connected to 5GC that is supported by the UE and differs from the RAT to which the UE is currently attached in the PS domain (or is assumed to be attached based on NOTE 3). NOTE 5: The condition ‘ESFB is "Y"’ only applies for a UE that is camped on or connected to 5GS via NR or via E-UTRA and that supports Emergency Services Fallback. In that case the emergency call will be provided over E-UTRAN or E-UTRA connected to 5GC as defined in procedures in TS 23.502 [49]. The condition ‘ESFB is "Y"’ is taken into consideration by the UE only when the network has indicated EMS = "N" for the RAT on which the UE is camping or connected. NOTE 6: For 5GS, the value of the column "EMS" is for the RAT that UE is camped on or is connected to. |
[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.
13.1.21.3 Test description
13.1.21.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 Switched OFF (state 1) according on Cell 1 to TS 36.508 [18].
13.1.21.3.2 Test procedure sequence
Table 13.1.21.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.21.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The UE is switched on. |
– |
– |
||
2-16 |
Steps 1 to 15 of the generic test procedure for UE registration (TS 36.508 4.5.2.3-1). |
– |
– |
||
– |
EXCEPTION: In parallel to the event described in step 17 below, if initiated by the UE the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane. |
– |
– |
||
– |
EXCEPTION: IF PDN1_IMS THEN in parallel to the event described in step 17 below the generic procedure for IMS signalling in the U-plane specified in Table 13.1.21.3.2-2 takes place if requested by the UE |
– |
– |
||
17-19 |
Steps 16 to 18 of the generic test procedure for UE registration (TS 36.508 4.5.2.3-1). |
– |
– |
||
Cause the UE to originate emergency call. (see Note 1) |
– |
– |
|||
20 |
Check: Does the UE transmit an RRCConnectionRequest message on Cell 1? |
–> |
RRCConnectionRequest |
1 |
P |
21 |
The SS transmits an RRCConnectionSetup message on Cell 1. |
<– |
RRCConnectionSetup |
– |
– |
22 |
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 23a1 to 23b15 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. |
– |
– |
– |
– |
23a1 |
IF (px_RATComb_Tested = EUTRA_UTRA), the SS reconfigures: Cell 1 as a "Suitable cell", Cell 5 as the "Serving cell". |
– |
– |
– |
– |
23a2 |
The SS transmits an RRCConnectionRelease message indicating redirection to cell 5 |
<– |
RRCConnectionRelease |
||
23a3 |
Check: Does the UE transmit a RRC CONNECTION REQUEST message on Cell 5 with Establishment cause: Emergency Call? |
–> |
RRC CONNECTION REQUEST |
1 |
P |
23a3A1 |
The SS changes cell 1 power level according to the row “T1” in table 13.1.21.3.2-0 |
– |
– |
– |
– |
23a4 |
The SS transmits an RRC CONNECTION SETUP message. |
<– |
RRC CONNECTION SETUP |
– |
– |
23a5 |
The UE transmits an RRC CONNECTION SETUP COMPLETE message. |
–> |
RRC CONNECTION SETUP COMPLETE |
– |
– |
– |
EXCEPTION: In parallel to the events described in step 23a6 to 23a17 the step specified in Table 13.1.21.3.2-4 takes place. |
– |
– |
– |
– |
23a6 |
The UE transmits a CM SERVICE REQUEST with CM Service Type indicating ‘Emergency call establishment. |
–> |
CM SERVICE REQUEST |
– |
– |
23a7 |
The SS transmits AUTHENTICATION REQUEST |
<– |
AUTHENTICATION REQUEST |
– |
– |
23a8 |
The UE transmits AUTHENTICATION RESPONSE |
–> |
AUTHENTICATION RESPONSE |
– |
– |
23a9 |
The SS transmits a SECURITY MODE COMMAND message for the CS domain. |
<– |
SECURITY MODE COMMAND |
– |
– |
23a10 |
The UE transmits a SECURITY MODE COMPLETE message. |
–> |
SECURITY MODE COMPLETE |
– |
– |
23a11 |
The UE transmits an EMERGENCY SETUP message. |
–> |
EMERGENCY SETUP |
– |
– |
23a12-23a17 |
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. |
– |
– |
– |
– |
23a17A |
The SS transmits a SECURITY MODE COMMAND message for the PS domain. (See Note 2) |
<– |
SECURITY MODE COMMAND |
– |
– |
23a17B |
The UE transmits a SECURITY MODE COMPLETE message. |
–> |
SECURITY MODE COMPLETE |
– |
– |
23a18 |
The SS transmits a ROUTING AREA UPDATE ACCEPT. |
<– |
ROUTING AREA UPDATE ACCEPT |
– |
– |
23a19 |
The UE sends ROUTING AREA UPDATE COMPLETE. |
–> |
ROUTING AREA UPDATE COMPLETE |
– |
– |
23b1 |
IF (px_RATComb_Tested = EUTRA_GERAN), the SS reconfigures: Cell 1 as a "Suitable cell", Cell 24 as the "Serving cell". |
– |
– |
– |
– |
23b2 |
The SS transmits an RRCConnectionRelease message indicating redirection to cell 24 |
<– |
RRCConnectionRelease |
– |
– |
23b3 |
Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call? |
–> |
CHANNEL REQUEST |
1 |
P |
23b3A1 |
The SS changes cell 1 power level according to the row “T1” in table 13.1.21.3.2-0 |
– |
– |
– |
– |
23b4 |
The SS transmits an IMMEDIATE ASSIGNMENT message. |
<– |
IMMEDIATE ASSIGNMENT |
– |
– |
23b5 |
The UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment” |
–> |
CM SERVICE REQUEST |
– |
– |
23b5A |
The UE transmits a Classmark Change message |
–> |
CLASSMARK CHANGE |
– |
– |
– |
EXCEPTION: Step 23b5B describes behaviour that depends on the UE capability. |
– |
– |
– |
– |
23b5B |
IF pc_UTRA then the UE transmits a Utran Classmark message |
–> |
UTRAN CLASSMARK CHANGE |
– |
– |
23b6 |
The SS transmits an AUTHENTICATION REQUEST message. |
<– |
AUTHENTICATION REQUEST |
– |
– |
23b7 |
The UE transmits an AUTHENTICATION RESPONSE message. |
–> |
AUTHENTICATION RESPONSE |
– |
– |
23b7A |
The SS transmits a CIPHERING MODE COMMAND message. |
<– |
CIPHERING MODE COMMAND |
– |
– |
23b7B |
The UE transmits a CIPHERING MODE COMPLETE message. |
–> |
CIPHERING MODE COMPLETE |
– |
– |
23b8 |
The UE transmits an EMERGENCY SETUP message. |
–> |
EMERGENCY SETUP |
– |
– |
23b9-23b15 |
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. |
– |
– |
– |
– |
23b16 |
The SS transmits DISCONNECT. |
<– |
DISCONNECT |
– |
– |
23b17 |
The UE transmits RELEASE.. |
–> |
RELEASE |
– |
– |
23b18 |
The SS transmits RELEASE COMPLETE. |
<– |
RELEASE COMPLETE |
– |
– |
23b19 |
The SS transmits CHANNEL RELEASE, with GPRS Resumption Field set to 1 |
<– |
CHANNEL RELEASE |
– |
– |
23b20-23b30 |
Steps 1 to 11 of the generic test procedure in TS 36.508 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 TS 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.21.3.2-2: Procedure for IMS signalling in the U-plane
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1-5 |
Registration procedure according Table 13.1.21.3.2-3. |
– |
– |
– |
– |
Table 13.1.21.3.2-3: Procedure for IMS Registration
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
TS 34.229-1 Annex C.17 or TS 34.229-1 C.18. |
|||
2 |
Void. |
|||
3 |
Optional P-CSCF address discovery using the DHCP procedure according to TS 34.229-1 Annex C.3 for IPv6 or TS 34.229-1 Annex C.4 for IPv4. |
|||
4 |
🡪 |
REGISTER |
The UE sends initial registration for IMS services. |
|
5 |
🡨 |
503 Service Unavailable |
The SS sends the default message “503 Service Unavailable” in TS 34.229-1 Annex A.4.2 with the exceptions as described in Table 13.1.21.3.3-5. |
Table 13.1.21.3.2-4: 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.21.3.3 Specific message contents
Table 13.1.21.3.3-1: RRCConnectionRequest (step 20, Table 13.1.21.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.21.3.3-2: EXTENDED SERVICE REQUEST (step 22, Table 13.1.21.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.21.3.3-3: RRCConnectionRelease (step 23a2, Table 13.1.21.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.21.3.3-4: RRCConnectionRelease (step 23b2, Table 13.1.21.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 |
||
} |
|||
} |
|||
} |
Table 13.1.21.3.3-5: 503 Service Unavailable (step 5, Table 13.1.21.3.2-3)
Header/param |
Value/remark |
Rel |
Reference |
---|---|---|---|
Retry-after |
RFC 3261 |
||
period |
3600 |
||
duration |
Not present |
||
comment |
Not present |