8.12 Pre- and postambles for GERAN to UTRAN tests
34.123-33GPPPart 3: Abstract test suite (ATS)TSUser Equipment (UE) conformance specification
8.12.1 Preamble for GERAN to UTRAN tests
Before running inter-RAT test cases, radio conditions should be such that the mobile has to select the cell of the intended original RAT. The following steps should be used before running GERAN to UTRAN test cases.
1. UTRAN cell is powered OFF. The default radio conditions for a suitable GERAN cell are used for the serving cell, as defined in 3GPP TS 34.108 [3], clause 6.1.7. This step is performed while the UE is still switched OFF.
2. UE is switched ON and performs registration and attach.
3. The UTRAN cell is powered ON with an RF level such that the cell is a suitable neighbour cell, using the RF conditions defined in 3GPP TS 34.108 [3], clause 6.1.5, so that the UE will not re-select the UTRAN cell.
8.12.2 Postamble for GERAN to UTRAN tests
The following procedure is used after inter-RAT handover or cell change order test cases in case the test needs to be performed multiple times in a loop.
8.12.2.1 GERAN to UTRAN handover in CS
The test cases are defined in 3GPP TS 51.010-1 [26], clause 60.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
<– |
SECURITY MODE COMMAND |
Integrity protection is activated. UTRAN security keys in CS domain derived from GERAN |
|
|
2 |
–> |
SECURITY MODE COMPLETE |
||
|
3 |
<– |
UTRAN MOBILITY INFORMATION |
RRC |
|
|
4 |
–> |
UTRAN MOBILITY INFORMATION CONFIRM |
RRC |
|
|
5 |
–> |
ROUTING AREA UPDATE REQUEST |
GMM – Update type = ‘RA updating’. Not performed by CS only mobile. |
|
|
5a |
<– |
SECURITY MODE COMMAND |
Integrity protection is activated. UTRAN security keys in PS domain derived from GERAN |
|
|
5b |
–> |
SECURITY MODE COMPLETE |
||
|
6 |
<– |
ROUTING AREA UPDATE ACCEPT |
GMM – P-TMSI is included |
|
|
7 |
–> |
ROUTING AREA UPDATE COMPLETE |
||
|
8 |
The call is terminated. SS releases the RRC connection. |
|||
|
9 |
–> |
RRC CONNECTION REQUEST |
RRC – establishment cause = ‘registration’ |
|
|
10 |
<– |
RRC CONNECTION SETUP |
RRC |
|
|
11 |
–> |
RRC CONNECTION SETUP COMPLETE |
RRC |
|
|
12 |
–> |
ROUTING AREA UPDATE REQUEST |
CS/PS mobiles: GMM – Update type" = ‘combined RA/LA updating’ or ‘combined RA/LA updating with ISMI Attach’ Note: CS only mobiles will perform a normal LAU |
|
|
13 |
<– |
SECURITY MODE COMMAND |
Integrity protection is activated. |
|
|
14 |
–> |
SECURITY MODE COMPLETE |
||
|
15 |
<– |
ROUTING AREA UPDATE ACCEPT |
P-TMSI is included |
|
|
16 |
–> |
ROUTING AREA UPDATE COMPLETE |
||
|
17 |
The SS releases the RRC connection. |
|||
|
18 |
UE is powered OFF |
|||
Specific message contents
UTRAN MOBILITY INFORMATION message:
Use the same message sub-type found in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
CN information info |
|
|
– PLMN identity |
Not present |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
00 00H |
|
– CN domain specific DRX cycle length coefficient |
7 |
SECURITY MODE COMMAND message:
Use the same message sub-type found in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
Not present |
All remaining Specific message contents shall be referred to 34.108 clause 9 "Default Message Contents of Layer3 Messages for Layer 3 Testing".
8.12.2.2 GERAN to UTRAN cell change in PS (in PMM-CONNECTED)
These test cases are defined in 3GPP TS 51.010-1 [26], clause 42.4.7.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
–> |
ROUTING AREA UPDATE REQUEST |
GMM – Update type = ‘Combined RA / LA updating’ or ‘combined RA/LA updating with ISMI Attach ‘for CS/PS mobiles, and ‘RA updating’ for PS only mobiles. Follow-on request is made. |
|
|
2 |
<– |
SECURITY MODE COMMAND |
Integrity protection is activated, UTRAN security keys in PS domain derived from GERAN |
|
|
3 |
–> |
SECURITY MODE COMPLETE |
||
|
4 |
<– |
ROUTING AREA UPDATE ACCEPT |
GMM – P-TMSI is included |
|
|
5 |
–> |
ROUTING AREA UPDATE COMPLETE |
||
|
SS releases the RRC connection |
||||
|
UE is powered OFF. |
||||
8.12.2.3 GERAN to UTRAN DTM test cases
These test cases are defined in 3GPP TS 51.010-1 [26], clauses 41.5.1.1.1.4 and 47.3.4.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
The SS releases the RR connection |
||||
|
1 |
–> |
RRC CONNECTION REQUEST |
RRC – establishment cause = ‘registration’ |
|
|
2 |
<– |
RRC CONNECTION SETUP |
RRC |
|
|
3 |
–> |
RRC CONNECTION SETUP COMPLETE |
RRC |
|
|
A4 |
–> |
ROUTING AREA UPDATE REQUEST |
UE behaviour type A, if the UE is still attached: GMM – Update type = ‘Combined RA / LA updating’ or ‘combined RA/LA updating with ISMI Attach |
|
|
A5 |
<– |
SECURITY MODE COMMAND |
Integrity protection is activated, UTRAN security keys in PS domain derived from GERAN |
|
|
A6 |
–> |
SECURITY MODE COMPLETE |
||
|
A7 |
<– |
ROUTING AREA UPDATE ACCEPT |
GMM – P-TMSI is included |
|
|
A8 |
–> |
ROUTING AREA UPDATE COMPLETE |
||
|
B4 |
–> |
LOCATION UPDATING REQUEST |
UE behaviour type B, if the UE has already detached |
|
|
B5 |
AUTHENTICATION REQUEST |
|||
|
B6 |
AUTHENTICATION RESPONSE |
|||
|
B7 |
<– |
SECURITY MODE COMMAND |
Integrity protection is activated, UTRAN security keys in CS domain derived from GERAN |
|
|
B8 |
–> |
SECURITY MODE COMPLETE |
||
|
B8a |
<– |
LOCATION UPDATING ACCEPT |
||
|
B8b |
–> |
TMSI REALLOCATION COMPLETE |
||
|
9 |
SS releases the RRC connection |
|||
|
10 |
UE is powered OFF. |
|||