11.2.8 Attach for emergency bearer services / Rejected / No suitable cells in tracking area / Emergency call using the CS domain / UTRA or GERAN
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
11.2.8.1 Test Purpose (TP)
(1)
with { the UE has sent an ATTACH REQUEST for emergency bearer services }
ensure that {
when { the UE receives an ATTACH REJECT message with the EMM cause set to “No suitable cells in tracking area” }
then { UE establishes the emergency call using the CS domain (UTRA or GERAN) }
}
11.2.8.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clauses 5.5.1.2.5 and 5.5.1.2.5A.
[TS 24.301, clause 5.5.1.2.5]
…
The UE shall take the following actions depending on the EMM cause value received in the ATTACH REJECT message.
…
#12 (Tracking area not allowed);
The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and eKSI. Additionally, the UE shall reset the attach attempt counter.
In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service" and enter the state EMM-DEREGISTERED.LIMITED-SERVICE.
In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE.
If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value.
…
#15 (No suitable cells in tracking area);
The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI and eKSI. Additionally, the UE shall reset the attach attempt counter.
In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for roaming" and enter the state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304 [21].
In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE.
If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008 [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value.
…
[TS 24.301, clause 5.5.1.2.5A]
Upon receiving the ATTACH REJECT message including one of the other EMM cause values, the UE shall perform the actions as described in subclause 5.5.1.2.5 with the following addition: upon request from upper layers a CS voice capable UE may establish the emergency call using the CS domain.
…
11.2.8.3 Test description
11.2.8.3.1 Pre-test conditions
System Simulator:
– cell A is set to ”Serving cell”
– If (px_RATComb_Tested = EUTRA_UTRA AND pc_CS_Em_Call_in_UTRA)
– cell 5 is configured as ”Suitable Neighbour cell”
– If (px_RATComb_Tested = EUTRA_GERAN AND pc_CS_Em_Call_in_GERAN)
– cell 24 is configured as ”Suitable Neighbour cell”
– System information combination 10 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.
UE:
None.
Preamble:
– the UE is switched on and camped on cell A in EMM-DEREGISTERED.LIMITED-SERVICE state according to 36.508 [18]. This is achieved by the SS rejecting an attempt to attach with EMM cause = "Tracking area not allowed". And then the Cell 5 or 24 as appropriate is configured as "Suitable Neighbour cell".
11.2.8.3.2 Test procedure sequence
Table 11.2.8.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Steps 1 to 3 of the generic procedures in TS 36.508 subclause 4.5A.5.3 are performed on cell A. |
– |
– |
– |
– |
|
2 |
The UE transmits an ATTACH REQUEST message to attach for emergency bearer services, together with a PDN CONNECTIVITY REQUEST message for emergency bearer services, on Cell A. |
–> |
ATTACH REQUEST PDN CONNECTIVITY REQUEST |
– |
– |
|
2A |
Steps 5 to 8 of the generic test procedure for UE registration (TS 36.508 4.5.2.3-1). |
– |
– |
– |
– |
|
3 |
The SS transmits an ATTACH REJECT message, EMM cause = “No suitable cells in tracking area”. |
<– |
ATTACH REJECT |
– |
– |
|
3A |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 4a1 A to 4b14 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. |
– |
– |
– |
– |
|
4a1 |
Void |
– |
– |
– |
– |
|
4a1A |
IF (px_RATComb_Tested = EUTRA_UTRA AND pc_CS_Em_Call_in_UTRA) |
– |
– |
– |
– |
|
4a2 |
Check: Does the UE transmit an RRC CONNECTION REQUEST message on Cell 5 with Establishment cause: Emergency Call in the next 60 seconds? |
–> |
RRC CONNECTION REQUEST |
1 |
P |
|
4a3 |
The SS transmits an RRC CONNECTION SETUP message. |
<– |
RRC CONNECTION SETUP |
– |
– |
|
4a4 |
The UE transmits an RRC CONNECTION SETUP COMPLETE message. |
–> |
RRC CONNECTION SETUP COMPLETE |
– |
– |
|
– |
EXCEPTION: In parallel to the event described in steps 4a5 to 4a14, 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. |
– |
– |
– |
– |
|
4a5 |
Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”? |
–> |
CM SERVICE REQUEST |
1 |
P |
|
4a6 |
The SS transmits an AUTHENTICATION REQUEST message. |
<– |
AUTHENTICATION REQUEST |
– |
– |
|
4a7 |
The UE transmits an AUTHENTICATION RESPONSE message. |
–> |
AUTHENTICATION RESPONSE |
– |
– |
|
4a7A |
The SS transmits a SECURITY MODE COMMAND message for the CS domain. |
<– |
SECURITY MODE COMMAND |
– |
– |
|
4a7B |
The UE transmits a SECURITY MODE COMPLETE message. |
–> |
SECURITY MODE COMPLETE |
– |
– |
|
4a8 |
Check: Does the UE transmit an EMERGENCY SETUP message? |
–> |
EMERGENCY SETUP |
1 |
P |
|
4a9-4a14 |
Steps 11 to 16 of the generic test procedure in TS 34.108 subclause 7.2.3.2.3 are performed on Cell 5. |
– |
– |
– |
– |
|
4b1 |
Void |
– |
– |
– |
– |
|
4b1A |
IF (px_RATComb_Tested = EUTRA_GERAN AND pc_CS_Em_Call_in_GERAN) |
– |
– |
– |
– |
|
4b2 |
Check: Does the UE transmit a CHANNEL REQUEST message on Cell 24 with Establishment cause: Emergency call in the next 60 seconds? |
–> |
CHANNEL REQUEST |
1 |
P |
|
4b3 |
The SS transmits an IMMEDIATE ASSIGNMENT message. |
<– |
IMMEDIATE ASSIGNMENT |
– |
– |
|
4b4 |
Check: Does the UE transmit a CM SERVICE REQUEST with CM service type IE indicating “Emergency call establishment”? |
–> |
CM SERVICE REQUEST |
1 |
P |
|
4b4A |
The UE transmits a Classmark Change message |
–> |
CLASSMARK CHANGE |
– |
– |
|
4b4B |
IF (pc_UTRA = true) the UE transmits a UTRAN Classmark Change message |
–> |
UTRAN CLASSMARK CHANGE |
– |
– |
|
4b5-4b17 |
Steps 5 to 17 of the generic test procedure in TS 51.010-1 subclause 10.2.3 are performed on Cell 24. |
– |
– |
– |
– |
11.2.8.3.3 Specific message contents
Table 11.2.8.3.3-1: ATTACH REQUEST (Step 2, Table 11.2.8.3.2-1)
|
Derivation Path: 36.508, Table 4.7.2-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EPS attach type |
‘0110’B |
EPS emergency attach |
|
|
NAS key set identifier |
|||
|
NAS key set identifier |
‘111’B |
No key is available |
|
|
EPS mobile identity |
IMSI |
||
|
Old location area identification |
Not present |
||
|
TMSI status |
Not present |
||
Table 11.2.8.3.3-2: PDN CONNECTIVITY REQUEST (Step 2, Table 11.2.8.3.2-1)
|
Derivation Path: 36.508, Table 4.7.3-20 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Request type |
‘0100’B |
emergency |
||
Table 11.2.8.3.3-3: ATTACH REJECT (Step 3, Table 11.2.8.3.2-1)
|
Derivation Path: TS 36.508 Table 4.7.2-3 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
EMM cause |
0000 1111 |
#15 “No suitable cells in tracking area” |
|
|
ESM message container |
Not present |
||
Table 11.2.8.3.3-4: RRC CONNECTION REQUEST (Step 4a2, Table 11.2.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.2.8.3.3-5: CM SERVICE REQUEST (Steps 4a5 and 4b4, Table 11.2.8.3.2-1)
|
Derivation Path: TS 24.008 Table 9.2.11 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
CM service type |
0010 |
Emergency call establishment |
|
Table 11.2.8.3.3-6: EMERGENCY SETUP (Steps 4a8 and 4b7, Table 11.2.8.3.2-1)
|
Derivation Path: TS 24.008 clause |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
Emergency setup message type |
001110 |
EMERGENCY SETUP |
|
Table 11.2.8.3.3-7: CHANNEL REQUEST (Step 4b2, Table 11.2.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 |
|