11.2.8a Attach for emergency bearer services / Rejected / No suitable cells in tracking area / Emergency call using the CS domain / CDMA2000 1xRTT
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.8a.1 Test Purpose (TP)
Same Test Purpose as in clause 11.2.8.1 except: UE establishes the emergency call using the CDMA2000 1xRTT as CS domain.
11.2.8a.2 Conformance requirements
Same conformance requirements as in clause 11.2.8.2. For the present TCs the CS domain shall be understood as the CDMA2000 1xRTT CS domain.
11.2.8a.3 Test description
11.2.8a.3.1 Pre-test conditions
System Simulator:
– Cell A is set to ”Serving cell”
– Cell 19 is set to ”Suitable Neighbour cell”
– System information combination 6 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.
– The SS broadcasts Emergency Call support in System Information Block 1 on Cell A.
UE:
– UE contains ISIM and USIM and CSIM applications on UICC.
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".
– The UE is not attached for emergency bearer services.
11.2.8a.3.2 Test procedure sequence
Table 11.2.8a.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 |
– |
– |
|
3 |
The SS transmits an ATTACH REJECT message, EMM cause = “No suitable cells in tracking area”. |
<– |
ATTACH REJECT |
– |
– |
|
4 |
The SS releases the RRC connection. |
– |
– |
– |
– |
|
5 |
The SS reconfigures: Cell A as a "Suitable cell", Cell 19 as the "Serving cell". |
– |
– |
– |
– |
|
6 |
Check: Does the UE transmit an Origination message on Cell 19 in the next [60] seconds? |
–> |
Origination |
1 |
P |
|
7 |
The SS transmits an Extended Channel Assignment message on Cell 19. |
<– |
Extended Channel Assignment |
– |
– |
|
8 |
After the SS detects that Traffic Channel Initialization is successful, it transmits an Acknowledgement Order message on Cell 19. |
<– |
Acknowledgement Order |
– |
– |
|
9 |
The SS transmits a Service Connect message on Cell 19. |
<– |
Service Connect |
– |
– |
|
10 |
The UE transmits a Service Connect Completion message on Cell 19. |
–> |
Service Connect Completion |
– |
– |
11.2.8a.3.3 Specific message contents
Table 11.2.8a.3.3-1: ATTACH REQUEST (Step 2, Table 11.2.8a.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.8a.3.3-2: PDN CONNECTIVITY REQUEST (Step 2, Table 11.2.8a.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.8a.3.3-3: ATTACH REJECT (Step 3, Table 11.2.8a.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.8a.3.3-4: Origination (Step 6, Table 11.2.8a.3.2-1)
|
Field |
Value/remark |
Comment |
Condition |
|
MSG_ID |
‘000100’B |
Origination Message |
this value shall be verified by TTCN |
|
SPECIAL_SERVICE |
‘1’B |
||
|
SERVICE_OPTION |
Any value mapping to a voice service option |
Table 11.2.8a.3.3-5: Extended Channel Assignment (Step 7, Table 11.2.8a.3.2-1)
|
Field |
Value/remark |
Comment |
Condition |
|
MSG_ID |
‘010101’B |
Extended Channel Assignment Message |
|
|
ASSIGN_MODE |
‘000’B |
Traffic Channel Assignment |
Table 11.2.8a.3.3-6: Acknowledgment Order (Step 8, Table 11.2.8a.3.2-1)
|
Field |
Value/remark |
Comment |
Condition |
|
MSG_ID |
‘00000001’B |
Order Message |
|
|
ORDER |
‘010000’B |
Base Station Acknowledgment Order |
|
|
ORDQ |
‘00000000’B |
Table 11.2.8a.3.3-7: Service Connect (Step 9, Table 11.2.8a.3.2-1)
|
Field |
Value/remark |
Comment |
Condition |
|
MSG_ID |
‘00010100’B |
Service Connect Message |
|
|
SERV_CON_SEQ |
Set by SS |
Table 11.2.8a.3.3-8: Service Connect Completion (Step 10, Table 11.2.8a.3.2-1)
|
Information Element |
Value/remark |
Comment |
Condition |
|
MSG_ID |
‘00001110’B |
Service Connect Completion Message |
this value shall be verified by TTCN |
|
SERV_CON_SEQ |
Same value as SERV_CON_SEQ received in Service Connect Message (Table 11.2.8a.3.3-7 |