8.3.7 Inter-system hard handover from UTRAN to GSM
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
Clauses 8.3.7 contains test procedures to be used for executing Inter-system Handover from UTRAN to GSM tests. Table 8.3.7‑1 contains a summary of the different combinations of parameters being tested, together with a reference to the appropriate generic test procedure. If a test uses a parameter which the UE under test does not support, the test shall be skipped. Test cases in this clause are applicable only to the UE supporting both UTRAN and GSM. The test TEST USIM shall support service 27 to carry out these test cases.
Table 8.3.7-1
From |
To |
State of call |
Ref. clause |
Exec counter |
Remark |
---|---|---|---|---|---|
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM AMR |
U10 |
8.3.7.1 |
1 |
call active state; UEA1/UIA1 applied in UTRAN, A5/1 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM EFR |
U10 |
8.3.7.1 |
2 |
call active state; UEA1/UIA1 applied in UTRAN, A5/1 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.1 |
3 |
call active state; UEA1/UIA1 applied in UTRAN, A5/1 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM HR |
U10 |
8.3.7.1 |
4 |
call active state; UEA1/UIA1 applied in UTRAN, A5/1 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM AMR |
U10 |
8.3.7.1a |
1 |
call active state; UEA1/UIA1 applied in UTRAN, A5/3 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM EFR |
U10 |
8.3.7.1a |
2 |
call active state; UEA1/UIA1 applied in UTRAN, A5/3 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.1a |
3 |
call active state; UEA1/UIA1 applied in UTRAN, A5/3 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM HR |
U10 |
8.3.7.1a |
4 |
call active state; UEA1/UIA1 applied in UTRAN, A5/3 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM AMR |
U10 |
8.3.7.1b |
1 |
call active state; UEA2/UIA2 applied in UTRAN, A5/3 in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM EFR |
U10 |
8.3.7.1b |
2 |
call active state; UEA2/UIA2 applied in UTRAN, A5/3 in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.1b |
3 |
call active state; UEA2/UIA2 applied in UTRAN, A5/3 in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM HR |
U10 |
8.3.7.1b |
4 |
call active state; UEA2/UIA2 applied in UTRAN, A5/3 in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM AMR |
U10 |
8.3.7.1c |
1 |
call active state; UEA1/UIA1 applied in UTRAN, A5/4 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM EFR |
U10 |
8.3.7.1c |
2 |
call active state; UEA1/UIA1 applied in UTRAN, A5/4 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.1c |
3 |
call active state; UEA1/UIA1 applied in UTRAN, A5/4 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM HR |
U10 |
8.3.7.1c |
4 |
call active state; UEA1/UIA1 applied in UTRAN, A5/4 applied in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM AMR |
U10 |
8.3.7.1d |
1 |
call active state; UEA2/UIA2 applied in UTRAN, A5/4 in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM EFR |
U10 |
8.3.7.1d |
2 |
call active state; UEA2/UIA2 applied in UTRAN, A5/4 in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.1d |
3 |
call active state; UEA2/UIA2 applied in UTRAN, A5/4 in GSM |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM HR |
U10 |
8.3.7.1d |
4 |
call active state; UEA2/UIA2 applied in UTRAN, A5/4 in GSM |
UTRAN (Streaming/unknown/ uplink:14.4 DL:14.4 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 14.4 kbps CS data |
U10 |
8.3.7.2 |
1 |
Same data rate |
UTRAN (Streaming/unknown/ uplink:14.4 DL:14.4 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 14.4 kbps HSCSD |
U10 |
8.3.7.2a |
1 |
Same data rate |
UTRAN (Streaming/unknown/ uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 28.8 kbps CS data |
U10 |
8.3.7.2a |
2 |
Same data rate |
UTRAN (Streaming/unknown/ uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 57.6 kbps CS data |
U10 |
8.3.7.2a |
3 |
Same data rate |
UTRAN (Streaming/unknown/ uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 14.4 kbps CS data |
U10 |
8.3.7.3 |
1 |
Data rate down grading |
UTRAN (Streaming/unknown/ uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 14.4 kbps CS data |
U10 |
8.3.7.3 |
2 |
Data rate down grading |
UTRAN (Streaming/unknown/ uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 14.4 kbps HSCSD |
U10 |
8.3.7.3a |
1 |
Data rate down grading |
UTRAN (Streaming/unknown/ uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 14.4 kbps HSCSD |
U10 |
8.3.7.3a |
2 |
Data rate down grading |
UTRAN (Streaming/unknown/ uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBS) |
GSM 28.8 kbps HSCSD or E-TCH/F28.8 |
U10 |
8.3.7.3a |
3 |
Data rate down grading |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U1 |
8.3.7.4 |
1 |
During call establishment |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.5 |
1 |
failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.6 |
1 |
failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.7 |
1 |
failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.8 |
1 |
failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.9 |
1 |
failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.10 |
1 |
failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.11 |
1 |
failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U10 |
8.3.7.12 |
1 |
failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBS) |
GSM FR |
U1 |
8.3.7.13 |
1 |
call under establishment |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + interactive/ background UL: 32kbps, DL 🙁 max bit rate depending on UE category) PS RAB + uplink:3.4 DL3.4 kbps SRBs) |
GSM AMR |
U10 |
8.3.7.14 |
1 |
Call active state |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + interactive/ background UL: 32kbps, DL 🙁 max bit rate depending on UE category) PS RAB + uplink:3.4 DL3.4 kbps SRBs) |
GSM AMR |
U10 |
8.3.7.15 |
1 |
Failure case |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + interactive/ background UL: 64kbps, DL :64kbps PS RAB + uplink:3.4 DL3.4 kbps SRBs) |
GSM FR |
U10 |
8.3.7.16 |
1 |
Call active state |
UTRAN AMR (conversational/speech/ uplink:12.2 DL:12.2 kbps/CS RAB + interactive/ background UL: 64kbps, DL :64kbps PS RAB + uplink:3.4 DL3.4 kbps SRBs) |
DTM |
U10 |
8.3.7.17 |
1 |
Call active state |
8.3.7.1 Inter system handover from UTRAN/To GSM/Speech/Success with UEA1/UIA1 and A5/1 ciphering
8.3.7.1.1 Definition
This test case verifies the UE behaviour in the scenario of interRAT speech handover from UTRAN to GERAN including the UE capability to switch between different ciphering algorithms applied in each RAT: the UIA1/UEA1 are applied in the UTRAN cell; the A5/1 ciphering algorithm is applied in the GERAN cell.
8.3.7.1.2 Conformance requirement
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" |
Standard to apply |
Inter RAT Message |
GSM |
GSM TS 04.18, version 8.5.0 or later |
HANDOVER COMMAND |
cdma2000 |
TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later |
1> if the IE "System type" has the value "GSM":
2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain":
3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message.
NOTE: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1.
NOTE: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification.
Upon successfully completing the handover, the UE shall:
1> if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology.
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4.
NOTE: The release of the UMTS radio resources is initiated from the target RAT.
…
In the case of inter-RAT or inter-mode handover to GERAN A/Gb mode, the HANDOVER COMMAND message shall always contain the cipher mode setting IE (see sub-clause 3.4.4.1).
Reference(s)
TS 25.331 clause 8.3.7.3, 8.3.7.4.
TS 43.018 clause 3.4.4, 9.1.15.10.
8.3.7.1.3 Test purpose
To test that the UE supporting both GSM and UTRAN hands over from a UTRAN serving cell to the indicated channel of GSM target cell when the UE is in the speech call active state and receives an HANDOVER FROM UTRAN COMMAND.
UIA1/UEA1 are applied in the UTRAN cell. The A5/1 ciphering algorithm is applied in the GERAN cell. The UE shall be able to handle the change of algorithm when moving from UTRAN to GERAN.8.3.7.1.4 Method of test
Initial conditions
System Simulator: 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9.
Parameter |
Unit |
Cell 9 (GSM) |
Qsearch_I (TDD) |
dBm |
15 (never) |
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports GSM AMR,
– UE supports GSM EFR,
– UE supports GSM FR,
– UE supports GSM HR,
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810,
– px_CipherKey (64 bits).
Foreseen final state of the UE
The UE is in CC state U10 on cell 9.
Test Procedure
The SS brings the UE into call active state (CC state U10) with AMR on cell 1 (UTRAN), ciphering used is UIA1/UEA1. The SS configures the appropriate traffic channel on cell 9 (the GSM cell), then sends HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell, and the type of Ciphering Algorithm to be used at the GSM side set to A5/1. After the UE receives the command it shall configure itself accordingly and switch to the new channel on the target GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS through GSM cell. The SS applies the GSM ciphering algorithm A5/1 on the new (GSM) cell.
Depending on the PIXIT parameters the above procedure is executed maximum four times, each time with a different target channel in the GSM cell.
For UEs where the PIXIT indicates support for the GSM/ DCS 1800 and/ or GSM/ PCS 1900 band, the whole test should be repeated to cover these frequencies in order to verify the correct handling of the IE "Frequency band".
Inter RAT handover is normally preceded by the configuration and activation of compressed mode (depending on UE capabilities/ PIXIT) and the configuration of inter- RAT measurements. The inter RAT handover is normally initiated by the SS upon receiving an event triggered measurement report. The verification of this functionality is covered by other subclauses.
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2, 3, 4, depending on the PIXIT parameters.
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS bring the UE into UTRAN U10 state in cell 1. Ciphering used is UIA1/UEA1. |
||
2 |
SS |
The SS configures a traffic channel on cell 9 (GSM cell): for GSM AMR (M = 1); or for GSM EFR (M = 2); or for GSM FR (M = 3); or for GSM HR (M = 4). |
||
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: the target channel for GSM AMR (M = 1); or the target channel for GSM EFR (M = 2); or the target channel for GSM FR (M = 3); or the target channel for GSM HR (M = 4). IE Cipher Mode Setting the HANDOVER COMMAND message is set to A5/1. |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
PHYSICAL INFORMATION |
SS starts ciphering immediately (i.e. before even the reception of a correct access burst), and the message is sent enciphered |
|
10 |
|
SABM |
||
11 |
|
UA |
||
12 |
|
HANDOVER COMPLETE |
The SS receives the message on the traffic channel of GSM cell. |
|
The SS performs a ‘postamble’ and restores both UE and SS to their initial state so that the test can be repeated from step 1 for executions 2,3 and 4 (if required). |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Arbitrarily selects one integer between 0 to 3 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
Activation time |
now |
RAB Info |
|
– RAB identity |
0000 0001B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
– CN domain identity |
CS domain |
– NAS Synchronization Indicator |
Not present |
– Re-establishment timer |
Use T314 |
Inter-system message |
|
– CHOICE System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted and coded according to GSM specifications as Variable Length BIT STRING without Length Indicator. The first/ leftmost/ most significant bit of the bit string contains bit 8 of the first octet of the GSM message. The contents of the HANDOVER COMMAND see next table. |
For execution 1:
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 3, and, Cipher Mode Setting IE is included with SC=1 and algorithm identifier=000 cipher with algorithm A5/1 |
For execution 2:
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 2, and, Cipher Mode Setting IE is included with SC=1 and algorithm identifier=000 cipher with algorithm A5/1 |
For execution 3:
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 1, and, Cipher Mode Setting IE is included with SC=1 and algorithm identifier=000 cipher with algorithm A5/1 |
For execution 4:
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 4 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 1, and, Cipher Mode Setting IE is included with SC=1 and algorithm identifier=000 cipher with algorithm A5/1 |
8.3.7.1.5 Test requirement
During the procedure for bringing the UE into UTRAN U10 state on cell 1, the UE support for A5/1 is checked in RRC Connection Setup Complete/UE RAT Specific Capability/GSM/GSM Classmark 2; and, the UEA1 support is checked in RRC Connection Setup Complete/UE Radio Access Capability/Security Capability/Ciphering Algorithm Capability. Correct message exchange after the ciphering at the UTRA side is initiated, implicitly verifies that the UE can handle UIA1/UEA1 correctly.
At step 5 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has switched to the GSM cell.
At step 9 SS starts ciphering on the GSM cell using the A5/1 algorithm. Correct message exchange, after the ciphering at the GSM side is initiated, implicitly verifies that the UE can handle A5/1 correctly. At step 12 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
8.3.7.1a Inter system handover from UTRAN/To GSM/Speech/Success with UEA1/UIA1 and A5/3 ciphering
8.3.7.1a.1 Definition
This test case verifies the UE behaviour in the scenario of interRAT speech handover from UTRAN to GERAN including the UE capability to switch between different ciphering algorithms applied in each RAT: the UIA1/UEA1 are applied in the UTRAN cell; the A5/3 ciphering algorithm is applied in the GERAN cell.
8.3.7.1a.2 Conformance requirement
Identical to 8.3.7.1.2
8.3.7.1a.3 Test purpose
Identical to 8.3.7.1.3 but in GSM cell A5/3 is applied
8.3.7.1a.4 Method of test
Identical to 8.3.7.1.4 with exception of:
Related ICS/IXIT statement(s)
As in Related ICS/IXIT statement(s) in 8.3.7.1.4 with the addition of
– UE supports A5/3
Specific message contents
Similar to the specific message contents in 8.3.7.1.4 and the UE capability to support A5/3 is checked additionally.
The GSM HANDOVER COMMAND included in the HANDOVER FROM UTRAN COMMAND indicates in the Cipher Mode Setting information element that A5/3 ciphering algorithm is applied in the GSM cell.
8.3.7.1a.5 Test requirement
Similar to the Test requirement in 8.3.7.1.5 with the UE capability to support A5/3 on the GERAN side being checked instead.
8.3.7.1b Inter system handover from UTRAN/To GSM/Speech/Success with UEA2/UIA2 and A5/3 ciphering
8.3.7.1b.1 Definition
This test case verifies the UE behaviour in the scenario of interRAT speech handover from UTRAN to GERAN including the UE capability to switch between different ciphering algorithms applied in each RAT: the UIA2/UEA2 are applied in the UTRAN cell; the A5/3 ciphering algorithm is applied in the GERAN cell.
8.3.7.1b.2 Conformance requirement
Identical to 8.3.7.1.2
8.3.7.1b.3 Test purpose
Identical to 8.3.7.1.3 but in UTRAN cell UIA2/UEA2 are applied and in GSM cell A5/3 is applied
8.3.7.1b.4 Method of test
Identical to 8.3.7.1.4 with the exception of
Related ICS/IXIT statement(s)
As in Related ICS/IXIT statement(s) in 8.3.7.1.4 with the addition of
– UE supports A5/3- UE support of UIA2/UEA2
Specific message contents
Similar to the specific message contents in 8.3.7.1.4 but instead, the UE capability to support UEA2/UIA2 and A5/3 is checked.
The GSM HANDOVER COMMAND included in the HANDOVER FROM UTRAN COMMAND indicates in the Cipher Mode Setting information element that A5/3 ciphering algorithm is applied in the GSM cell.
8.3.7.1b.5 Test requirement
Similar to the Test requirement in 8.3.7.1.5 with the UE capability to support UIA2/UEA2 on the UTRAN side and A5/3 on the GERAN side being checked instead.
8.3.7.1c Inter system handover from UTRAN/To GSM/Speech/Success with UEA1/UIA1 and A5/4 ciphering
8.3.7.1c.1 Definition
This test case verifies the UE behaviour in the scenario of interRAT speech handover from UTRAN to GERAN including the UE capability to switch between different ciphering algorithms applied in each RAT: the UIA1/UEA1 are applied in the UTRAN cell; the A5/4 ciphering algorithm is applied in the GERAN cell.
8.3.7.1c.2 Conformance requirement
Identical to 8.3.7.1.2.
8.3.7.1c.3 Test purpose
Identical to 8.3.7.1.3 but in the GSM cell the A5/4 is applied.
8.3.7.1c.4 Method of test
Identical to 8.3.7.1.4 with exception of:
Related ICS/IXIT statement(s)
As in Related ICS/IXIT statement(s) in 8.3.7.1.4 with the addition/modification of
– UE supports A5/4
– px_CipherKey128 (128 bits)
Specific message contents
Similar to the specific message contents in 8.3.7.1.4 and the UE capability to support A5/4 is checked additionally.
The GSM HANDOVER COMMAND included in the HANDOVER FROM UTRAN COMMAND indicates in the Cipher Mode Setting information element that A5/4 ciphering algorithm is applied in the GSM cell.
8.3.7.1c.5 Test requirement
Similar to the Test requirement in 8.3.7.1.5 with the UE capability to support A5/4 on the GERAN side being checked instead.
8.3.7.1d Inter system handover from UTRAN/To GSM/Speech/Success with UEA2/UIA2 and A5/4 ciphering
8.3.7.1d.1 Definition
This test case specifies the UE behaviour in the scenario of interRAT speech handover from UTRAN to GERAN including the UE capability to switch between different ciphering algorithms applied in each RAT: the UIA2/UEA2 are applied in the UTRAN cell; the A5/4 ciphering algorithm is applied in the GERAN cell.
8.3.7.1d.2 Conformance requirement
Identical to 8.3.7.1.2.
8.3.7.1d.3 Test purpose
Identical to 8.3.7.1.3 but in the UTRAN cell the UIA2/UEA2 are applied and in the GSM cell the A5/4 is applied.
8.3.7.1d.4 Method of test
Identical to 8.3.7.1.4 with exception of:
Related ICS/IXIT statement(s)
As in Related ICS/IXIT statement(s) in 8.3.7.1.4 with the addition/modification of
– UE supports A5/4
– UE supports UIA2/UEA2
– px_CipherKey128 (128 bits)
Specific message contents
Similar to the specific message contents in 8.3.7.1.4 but instead also the UE capability to support UEA2/UIA2 and A5/4 is checked.
The GSM HANDOVER COMMAND included in the HANDOVER FROM UTRAN COMMAND indicates in the Cipher Mode Setting information element that A5/4 ciphering algorithm is applied in the GSM cell.
8.3.7.1d.5 Test requirement
Similar to the Test requirement in 8.3.7.1.5 with the UE capability to support UIA2/UEA2 on the UTRAN side and A5/4 on the GERAN side being checked instead.
8.3.7.2 Inter system handover from UTRAN/To GSM/Data/Same data rate/Success
8.3.7.2.1 Definition
8.3.7.2.2 Conformance requirement
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" |
Standard to apply |
Inter RAT Message |
GSM |
GSM TS 04.18, version 8.5.0 or later |
HANDOVER COMMAND |
cdma2000 |
TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later |
1> if the IE "System type" has the value "GSM":
2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain":
3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message.
NOTE 1: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1.
NOTE 2: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification.
Upon successfully completing the handover, the UE shall:
1> if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology.
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4.
NOTE 3: The release of the UMTS radio resources is initiated from the target RAT.
Reference(s)
TS 25.331 Clauses 8.3.7.3, 8.3.7.4.
8.3.7.2.3 Test purpose
To test that the UE hands over to the indicated channel of same data rate in the GSM target cell when it is in the data call active state in the UTRAN serving cell and receives an HANDOVER FROM UTRAN COMMAND.
8.3.7.2.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports UTRAN Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs,
– UE supports GSM 14.4 kbps data ( full rate traffic channel for 14.4 kbit/s user data (TCH/F14.4)),
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810.
Foreseen final state of the UE
The UE is in CC state U10 on cell 9.
Test Procedure
The SS brings the UE into data call active state (CC state U10) with Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs. The SS configures a 14.4 kbps data channel on the GSM cell, then sends a HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell.
UEs for which the PIXIT indicates support for the GSM/ DCS 1800 and/ or GSM/ PCS 1900 band, the test should cover these frequencies in order to verify the correct handling of the IE "Frequency band".
Inter RAT handover is normally preceded by the configuration and activation of compressed mode (depending on UE capabilities/ PIXIT) and the configuration of inter- RAT measurements. The inter RAT handover is normally initiated by the SS upon receiving an event triggered measurement report. The verification of this functionality is covered by other subclauses.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS bring the UE into UTRAN U10 state in cell 1, the configuration is: Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs |
||
2 |
SS |
The SS configures a traffic channel on cell 9 (GSM cell): for GSM 14.4 kbps data. |
||
3 |
|
HANDOVER FROM UTRAN COMMAND GSM |
Send on cell 1 (UTRAN cell) and the message indicates: the target channel for GSM 14.4 kbps data |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
PHYSICAL INFORMATION |
||
10 |
|
SABM |
||
11 |
|
UA |
||
12 |
|
HANDOVER COMPLETE |
The SS receives the message on the traffic channel of GSM cell. |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Arbitrarily selects one integer between 0 to 3 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
Activation time |
now |
RAB Info |
|
– RAB identity |
0000 0001B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
– CN domain identity |
CS domain |
– NAS Synchronization Indicator |
Not present |
– Re-establishment timer |
Use T314 |
Inter-system message |
|
– CHOICE System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
GSM message List |
– Message |
GSM HANDOVER COMMAND formatted and coded according to GSM specifications as BIT STRING(1..512). The first/ leftmost/ most significant bit of the bit string contains bit 8 of the first octet of the GSM message. The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = data, 14.5 kbit/s radio interface rate (14.4 kbit/s user data (TCH/F14.4)) |
NOTE: This test case requires that the size of the HANDOVER COMMAND does not exceed 64 octets. Whenever the contents for the 04.18 HANDOVER COMMAND is changed, a check is needed to verify that size constraint is still met.
8.3.7.2.5 Test requirements
At step 5 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has switched to the GSM cell.
At step 12 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
8.3.7.2a Inter system handover from UTRAN/To GSM/Data/Same data rate/Extended Rates/Success
8.3.7.2a.1 Definition
8.3.7.2a.2 Conformance requirement
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" |
Standard to apply |
Inter RAT Message |
GSM |
GSM TS 04.18, version 8.5.0 or later |
HANDOVER COMMAND |
cdma2000 |
TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later |
1> if the IE "System type" has the value "GSM":
2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain":
3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message.
NOTE: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1.
NOTE: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification.
Upon successfully completing the handover, the UE shall:
1> if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology.
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4.
NOTE: The release of the UMTS radio resources is initiated from the target RAT.
Reference(s)
TS 25.331 Clauses 8.3.7.3, 8.3.7.4.
8.3.7.2a.3 Test purpose
To test that the UE hands over to the indicated channel of same data rate in the GSM target cell when it is in the data call active state in the UTRAN serving cell and receives an HANDOVER FROM UTRAN COMMAND.
8.3.7.2a.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 26.6.5.1 or clause 26.13.1.3 (for HSCSD) shall be referenced for the default parameters of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports UTRAN Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs,
– UE supports UTRAN Streaming/unknown/uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs,
– UE supports UTRAN Streaming/unknown/uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs,
– UE supports GSM 14.4 kbps data (HSCSD),
– UE supports GSM 28.8 kbps data (HSCSD or enhanced circuit switched full rate traffic channel for 28.8 kbit/s user date (E-TCH/F28.8)),
– UE supports GSM 57.6 kbps data,
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS.
Foreseen final state of the UE
The UE is in CC state U10 on cell 9.
Test Procedure
The SS brings the UE into data call active state (CC state U10) with a suitable configuration (e.g. Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs for M = 1). The SS configures an appropriate traffic channel (e.g. 14.4 kbps HSCSD data channel for M = 1)on the GSM cell, then sends a HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell.
Depending on the PIXIT parameters the above procedure is executed maximum three times, each time with a different target channel in the GSM cell.
UEs for which the PIXIT indicates support for the GSM/ DCS 1800 and/ or GSM/ PCS 1900 band, the test should cover these frequencies in order to verify the correct handling of the IE "Frequency band".
Inter RAT handover is normally preceded by the configuration and activation of compressed mode (depending on UE capabilities/ PIXIT) and the configuration of inter- RAT measurements. The inter RAT handover is normally initiated by the SS upon receiving an event triggered measurement report. The verification of this functionality is covered by other subclauses.
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2, 3, depending on the PIXIT parameters.
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS bring the UE into UTRAN U10 state in cell 1, the configuration is: Streaming/unknown/uplink:14.4 DL:14.4 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs (for M = 1); Streaming/unknown/uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs (for M = 2); Streaming/unknown/uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs (for M = 3). |
||
2 |
SS |
The SS configures a traffic channel on cell 9 (GSM cell): for GSM HSCSD 14.4 kbps data (M = 1); or for GSM 28.8 kbps data (M = 2); or for GSM 57.6 kbps data (M = 3). |
||
3 |
|
HANDOVER FROM UTRAN COMMAND GSM |
Send on cell 1 (UTRAN cell) and the message indicates: the target channel for GSM HSCSD 14.4 kbps data (M = 1); or for GSM 28.8 kbps data (M = 2); or for GSM 57.6 kbps data (M = 3). |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
PHYSICAL INFORMATION |
||
10 |
|
SABM |
||
11 |
|
UA |
||
12 |
|
HANDOVER COMPLETE |
The SS receives the message on the traffic channel of GSM cell. |
|
The SS performs a ‘postamble’ and restores both UE and SS to their initial state so that the test can be repeated from step 1 for executions 2 and 3 (if required). |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Arbitrarily selects one integer between 0 to 3 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
Activation time |
now |
RAB Info |
|
– RAB identity |
0000 0001B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
– CN domain identity |
CS domain |
– NAS Synchronization Indicator |
Not present |
– Re-establishment timer |
Use T314 |
Inter-system message |
|
– CHOICE System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
GSM message List |
– Message |
GSM HANDOVER COMMAND formatted and coded according to GSM specifications as BIT STRING(1..512). The first/ leftmost/ most significant bit of the bit string contains bit 8 of the first octet of the GSM message. The contents of the HANDOVER COMMAND see next table. |
For execution 1:
HANDOVER COMMAND
Same as the HANDOVER COMMAND in clause 26.13.1.3 of GSM 51.010, except that the Description of a multi-slot configuration supporting 14.4 kbps user data. |
NOTE 1: This test case requires that the size of the HANDOVER COMMAND does not exceed 64 octets. Whenever the contents for the 04.18 HANDOVER COMMAND is changed, a check is needed to verify that size constraint is still met.
For execution 2:
If the UE supports enhanced circuit switched full rate traffic channel for 28.8 kbps user data:
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = data, 29.0 kbit/s radio interface rate (28.8 kbit/s user data (E-TCH/F28.8)) |
NOTE 2: This test case requires that the size of the HANDOVER COMMAND does not exceed 64 octets. Whenever the contents for the 04.18 HANDOVER COMMAND is changed, a check is needed to verify that size constraint is still met.
If the UE supports HSCSD:
HANDOVER COMMAND
Same as the HANDOVER COMMAND in clause 26.13.1.3 of GSM 51.010, except that the Description of a multi-slot configuration supporting 28.8 kbps user data. |
NOTE 3: This test case requires that the size of the HANDOVER COMMAND does not exceed 64 octets. Whenever the contents for the 04.18 HANDOVER COMMAND is changed, a check is needed to verify that size constraint is still met.
For execution 3:
HANDOVER COMMAND
Same as the HANDOVER COMMAND in clause 26.13.1.3 of GSM 51.010, except that the Description of a multi-slot configuration supporting 57.6 kbps user data. |
NOTE 4: This test case requires that the size of the HANDOVER COMMAND does not exceed 64 octets. Whenever the contents for the 04.18 HANDOVER COMMAND is changed, a check is needed to verify that size constraint is still met.
8.3.7.2a.5 Test requirements
At step 5 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has switched to the GSM cell.
At step 12 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
8.3.7.3 Inter system handover from UTRAN/To GSM/Data/Data rate down grading/Success
8.3.7.3.1 Definition
8.3.7.3.2 Conformance requirement
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" |
Standard to apply |
Inter RAT Message |
GSM |
GSM TS 04.18, version 8.5.0 or later |
HANDOVER COMMAND |
cdma2000 |
TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later |
1> if the IE "System type" has the value "GSM":
2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain":
3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message.
NOTE: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1.
NOTE: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification.
Upon successfully completing the handover, the UE shall:
1> if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology.
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4.
NOTE: The release of the UMTS radio resources is initiated from the target RAT.
Reference(s)
TS 25.331 Clauses 8.3.7.3, 8.3.7.4.
8.3.7.3.3 Test purpose
To test that the UE hands over to the indicated channel of lower data rate in the GSM target cell when it is in the data call active state in the UTRAN serving cell and receives an HANDOVER FROM UTRAN COMMAND.
8.3.7.3.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports UTRAN Streaming/unknown/uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs,
– UE supports UTRAN Streaming/unknown/uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs,
– UE supports GSM 14.4 kbps data ( full rate traffic channel for 14.4 kbit/s user data (TCH/F14.4)),
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810.
– UE support CS and PS service.
Foreseen final state of the UE
The UE is in CC state U10 on cell 9.
Test Procedure
The SS brings the UE into data call active state (CC state U10) with a suitable configuration (e.g. Streaming/unknown/uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs for M = 1). The SS configures a 14.4 kbps data channel on the GSM cell, then sends a HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell.
Upon completion of the handover, depending on UE capabilities, the UE performs routing area update and (re-) establishes the connection towards the PS domain.
Depending on the PIXIT parameters the above procedure is executed maximum two times, each time with different target channel in the GSM cell.
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2 depending on the PIXIT parameters.
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
1 |
UE |
The SS bring the UE into UTRAN U10 state in cell 1, the configuration is: Streaming/unknown/uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs (for M = 1); Streaming/unknown/uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs (for M = 2). |
||
2 |
SS |
The SS configures a traffic channel on cell 9 (GSM cell): for GSM 14.4 kbps data (M = 1 and 2). |
||
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: the target channel for GSM 14.4 kbps data (M = 1 and 2). |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
PHYSICAL INFORMATION |
||
10 |
|
SABM |
||
11 |
|
UA |
||
12 |
|
HANDOVER COMPLETE |
The SS receives the message on the traffic channel of GSM cell. |
|
13 |
|
ROUTING AREA UPDATE |
Conditional on Class A UE. |
|
The SS performs a ‘postamble’ and restores both UE and SS to their initial state so that the test can be repeated from step 1 for execution 2 (if required). |
Specific message contents
For execution 1:
Same as the message contents of clause 8.3.7.2 Procedure 1 for M = 1.
For execution 2:
Same as the message contents of clause 8.3.7.2 Procedure 1 for M = 1.
8.3.7.3.5 Test requirement
At step 5 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has switched to the GSM cell.
At step 12 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
8.3.7.3a Inter system handover from UTRAN/To GSM/Data/Data rate down grading/Extended Rates/Success
8.3.7.3a.1 Definition
8.3.7.3a.2 Conformance requirement
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" |
Standard to apply |
Inter RAT Message |
GSM |
GSM TS 04.18, version 8.5.0 or later |
HANDOVER COMMAND |
cdma2000 |
TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later |
1> if the IE "System type" has the value "GSM":
2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain":
3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message.
NOTE: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1.
NOTE: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification.
Upon successfully completing the handover, the UE shall:
1> if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology.
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4.
NOTE: The release of the UMTS radio resources is initiated from the target RAT.
Reference(s)
TS 25.331 Clauses 8.3.7.3, 8.3.7.4.
8.3.7.3a.3 Test purpose
To test that the UE hands over to the indicated channel of lower data rate in the GSM target cell when it is in the data call active state in the UTRAN serving cell and receives an HANDOVER FROM UTRAN COMMAND.
8.3.7.3a.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 26.6.5.1 or clause 26.13.1.3 (for HSCSD) shall be referenced for the default parameters of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports UTRAN Streaming/unknown/uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs,
– UE supports UTRAN Streaming/unknown/uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs,
– UE supports GSM 14.4 kbps data (HSCSD),
– UE supports GSM 28.8 kbps data (HSCSD or enhanced circuit switched full rate traffic channel for 28.8 kbit/s user date (E-TCH/F28.8)),
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480 GSM-PCS.
– UE support CS and PS service.
Foreseen final state of the UE
The UE is in CC state U10 on cell 9.
Test Procedure
The SS brings the UE into data call active state (CC state U10) with a suitable configuration (e.g. Streaming/unknown/uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs for M = 1). The SS configures a traffic channel (e.g. 14.4 kbps HSCSD data channel for M = 1)on the GSM cell, then sends a HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell.
Upon completion of the handover, depending on UE capabilities, the UE performs routing area update and (re-) establishes the connection towards the PS domain.
Depending on the PIXIT parameters the above procedure is executed maximum three times, each time with different target channel in the GSM cell.
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2, 3, depending on the PIXIT parameters.
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
1 |
UE |
The SS bring the UE into UTRAN U10 state in cell 1, the configuration is: Streaming/unknown/uplink:28.8 DL:28.8 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs (for M = 1); Streaming/unknown/uplink:57.6 DL:57.6 kbps/CS RAB + uplink:3.4 DL:3.4 kbps SRBs (for M = 2 and 3). |
||
2 |
SS |
The SS configures a traffic channel on cell 9 (GSM cell): for GSM 14.4 kbps HSCSD data (M = 1 and 2); or for GSM 28.8 kbps data (M = 3). |
||
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: the target channel for GSM HSCSD 14.4 kbps data (M = 1 and 2); or for GSM 28.8 kbps data (M = 3). |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
PHYSICAL INFORMATION |
||
10 |
|
SABM |
||
11 |
|
UA |
||
12 |
|
HANDOVER COMPLETE |
The SS receives the message on the traffic channel of GSM cell. |
|
13 |
|
ROUTING AREA UPDATE |
Conditional on Class A UE. |
|
The SS performs a ‘postamble’ and restores both UE and SS to their initial state so that the test can be repeated from step 1 for executions 2 and 3 (if required). |
Specific message contents
For execution 1:
Same as the message contents of clause 8.3.7.2.2 Procedure 2 for M = 1.
For execution 2:
Same as the message contents of clause 8.3.7.2.2 Procedure 2 for M = 1.
For execution 3:
Same as the message contents of clause 8.3.7.2.2 Procedure 2 for M = 2.
8.3.7.3a.5 Test requirement
At step 5 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has switched to the GSM cell.
At step 12 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
8.3.7.4 Inter system handover from UTRAN/To GSM/Speech/Establishment/Success
8.3.7.4.1 Definition
8.3.7.4.2 Conformance requirement
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" |
Standard to apply |
Inter RAT Message |
GSM |
GSM TS 04.18, version 8.5.0 or later |
HANDOVER COMMAND |
cdma2000 |
TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later |
1> if the IE "System type" has the value "GSM":
2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain":
3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message.
NOTE: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1.
NOTE: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification.
Upon successfully completing the handover, the UE shall:
1> if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology.
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4.
NOTE: The release of the UMTS radio resources is initiated from the target RAT.
Reference(s)
TS 25.331 Clauses 8.3.7.3, 8.3.7.4.
8.3.7.4.3 Test purpose
To test that the UE hands over to the indicated channel in the GSM target cell when it is in the call establishment phase in the UTRAN serving cell and receives an HANDOVER FROM UTRAN COMMAND.
8.3.7.4.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9 except the BCCH ARFCN for GSM 900 should be 18 and for GSM 1900 should be 646.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports UTRAN AMR,
– UE supports GSM FR,
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810.
Foreseen final state of the UE
The UE is in CC state U1 on cell 9.
Test Procedure
The UE is triggered to initialise an MO speech call. During the call establishment phase, after the SS receives SETUP message the SS configures a dedicated channel on the GSM cell, then sends the UE a HANDOVER FROM UTRAN COMMAND indicating the dedicated channel in the target GSM cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
To trigger the UE to initialise an MO call |
||
2 |
|
SETUP |
U1 |
|
3 |
SS |
The SS configures a dedicated channel SDCCH on the GSM cell. |
||
4 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: the dedicated channel SDCCH. |
|
5 |
UE |
The UE accepts the handover command and switches to the GSM dedicated channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
6 |
|
HANDOVER ACCESS |
The SS receives this burst on the dedicated channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
HANDOVER ACCESS |
||
10 |
|
PHYSICAL INFORMATION |
||
11 |
|
SABM |
||
12 |
|
UA |
||
13 |
|
HANDOVER COMPLETE |
The SS receives the message on the dedicated channel of GSM cell. |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Arbitrarily selects one integer between 0 to 3 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
Activation time |
now |
RAB Info |
Not present |
Inter-system message |
|
– CHOICE System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted and coded according to GSM specifications as Variable Length BIT STRING without Length Indicator. The first/ leftmost/ most significant bit of the bit string contains bit 8 of the first octet of the GSM message. The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 4 in clause 26.6.5.2 of GSM 51.010 except that ‘Mode of first channel’ IE should be set to ‘signalling only’ and the BCCH ARFCN for GSM 900 should be 18 and for GSM 1900 should be 646 |
8.3.7.4.5 Test requirement
At step 13 the SS shall receive HANDOVER COMPLETE message on the dedicated channel of the GSM cell.
8.3.7.5 Inter system handover from UTRAN/To GSM/Speech/Failure
8.3.7.5.1 Definition
8.3.7.5.2 Conformance requirement
If the UE does not succeed in establishing the connection to the other target radio access technology, it shall
1> revert back to the UTRA configuration;
1> establish the UTRA physical channel(s) used at the time for reception of HANDOVER FROM UTRAN COMMAND;
…
transmit the HANDOVER FROM UTRAN FAILURE message setting the information elements as specified below:
2> include the IE "RRC transaction identifier"; and
2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and
2> clear that entry;
2> set the IE "Inter-RAT handover failure" to "physical channel failure".
1> When the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layer for transmission:
2> the procedure ends.
Reference(s)
TS 25.331 Clause 8.3.7.5.
8.3.7.5.3 Test purpose
To test that the UE reactivates the old configuration and uses this to transmit a HANDOVER FROM UTRAN FAILURE message to the network including IE "Inter-RAT Handover failure cause" which is set to "physical channel failure", when it receives an HANDOVER FROM UTRAN COMMAND and the connection to GSM for handover can not be established.
To verify that after the handover failure the UE resumes previously configured compressed mode patterns and measurements.
8.3.7.5.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports GSM FR,
– UE supports UTRAN AMR,
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810
– UE supports compressed mode (FDD only).
Foreseen final state of the UE
The UE is in CC state U10 on cell 1.
Test Procedure
The SS brings the UE into call active state (CC state U10) with AMR. If the UE requires compressed mode (refer ICS/IXIT), the SS sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to configure the compressed mode pattern sequence parameters. When the PHYSICAL CHANNEL RECONFIGURATION COMPLETE is received from the UE, the SS sends a MEASUREMENT CONTROL message indicating two GSM cells of which only one is actually configured. This message is used to provide measurement control parameters (GSM RSSI) to the UE and to start compressed mode for the measurement if required according to the UE capabilities. The UE replies according to request by sending RRC: MEASUREMENT REPORT messages periodically to SS (reporting period is 4000 ms).
The SS sends a HANDOVER FROM UTRAN COMMAND indicating a dedicated channel (not configured) of the target GSM cell to the UE through DCCH of the serving UTRAN cell. The UE receives the command and configures itself accordingly but can not complete the handover. The SS checks that the handover is failed by checking that the UE transmits the HANDOVER FROM UTRAN FAILURE message to the SS using the old UTRAN configuration.
After the handover failure, the UE re-activates compressed mode (if configured) and resumes periodic measurement reporting including sending MEASUREMENT REPORT messages periodically to SS.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS bring the UE into U10 state in UTRAN cell 1. If the UE does not require compressed mode (refer ICS/IXIT), then goto step 1c. |
||
1a |
|
PHYSICAL CHANNEL RECONFIGURATION |
Compressed mode pattern sequence parameters are loaded to UE. |
|
1b |
|
PHYSICAL CHANNEL RECONFIGURATION COMPLETE |
||
1c |
|
MEASUREMENT CONTROL |
SS provides GSM RSSI measurement control parameters to UE. Compressed mode for GSM RSSI measurement is started if required as per UE capabilities. |
|
1d |
|
MEASUREMENT REPORT |
UE reports measurement results of GSM RSSI measurement to SS. |
|
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: the target channel for GSM FR which does not exist in the GSM cell. |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER FROM UTRAN FAILURE |
The SS receives the message via the old UTRAN configuration. |
|
5a |
|
MEASUREMENT REPORT |
The SS shall verify that the UE resumes periodic measurement reporting for GSM RSSI measurements |
Specific message contents
PHYSICAL CHANNEL RECONFIGURATION (Step 1a)
Use the same message sub-type as in TS 34.108 titled "Speech in CS", with the following exceptions:
Information Element |
Value/remark |
Version |
Downlink information common for all radio links |
||
– DPCH compressed mode info |
||
– TGPSI |
1 |
|
– TGPS Status Flag |
Deactivate |
|
– TGCFN |
Not present |
|
– Transmission gap pattern sequence configuration parameters |
||
– TGMP |
GSM Carrier RSSI Measurement |
|
– TGPRC |
Infinity |
|
– TGSN |
4 |
|
– TGL1 |
7 |
|
– TGL2 |
Not present |
|
– TGD |
Undefined |
|
– TGPL1 |
12 |
|
– TGPL2 |
Not present |
R99 and REL-4 only |
– RPP |
Mode 0 |
|
– ITP |
Mode 0 |
|
CHOICE UL/DL Mode |
UL&DL or UL-only or DL-only (depends on UE’s Measurement capability) |
|
– Downlink compressed mode method |
SF/2 |
|
– Uplink compressed mode method |
SF/2 |
|
– Downlink frame type |
A |
|
– DeltaSIR1 |
20 (2.0) |
|
– DeltaSIRAfter1 |
10 (1.0) |
|
– DeltaSIR2 |
Not Present |
|
– DeltaSIR2After2 |
Not Present |
|
– N identify abort |
Not Present |
|
– T Reconfirm abort |
Not Present |
|
– TGPSI |
2 |
|
– TGPS Status Flag |
Deactivate |
|
– TGCFN |
Not present |
|
– Transmission gap pattern sequence configuration parameters |
||
– TGMP |
GSM Initial BSIC identification |
|
– TGPRC |
Infinity |
|
– TGSN |
4 |
|
– TGL1 |
7 |
|
– TGL2 |
Not present |
|
– TGD |
undefined |
|
– TGPL1 |
8 |
|
– TGPL2 |
Not present |
R99 and REL-4 only |
– RPP |
Mode 0 |
|
– ITP |
Mode 0 |
|
CHOICE UL/DL Mode |
UL&DL or UL-only or DL-only (depends on UE’s Measurement capability) |
|
– Downlink compressed mode method |
SF/2 |
|
– Uplink compressed mode method |
SF/2 |
|
– Downlink frame type |
A |
|
– DeltaSIR1 |
20 (2.0) |
|
– DeltaSIRAfter1 |
10 (1.0) |
|
– DeltaSIR2 |
Not Present |
|
– DeltaSIR2After2 |
Not Present |
|
– N identify abort |
128 |
|
– T Reconfirm abort |
Not Present |
MEASUREMENT CONTROL (Step 1c)
Information Element |
Value/remark |
---|---|
Measurement Identity |
15 |
Measurement Command |
Setup |
Measurement Reporting Mode |
|
– Measurement Reporting Transfer Mode |
Acknowledged Mode RLC |
– Periodic Reporting / Event Trigger Reporting Mode |
Periodical reporting |
Additional measurements list |
Not Present |
CHOICE measurement type |
|
– inter-RAT measurement |
|
– inter-RAT measurement object list |
|
CHOICE Inter-RAT Cell Removal |
Remove all inter-RAT cells |
– New inter-RAT cells |
|
– inter-RAT cell id |
0 |
CHOICE Radio Access Technology |
GSM |
– Cell individual offset |
0 (0 dB) |
– Cell selection and re-selection info |
Not present |
– BSIC |
Value set to correspond with HANDOVER COMMAND IEs seen in TS 51.010 clause 26.6.5.1 M=2 |
– Band indicator |
GSM/DCS-1800 or GSM/PCS-1900 (dependent on band used) |
– BCCH ARFCN |
Value the same as HANDOVER COMMAND in TS 51.010 clause 26.6.5.1 M=2 (dependant on band used) |
– inter-RAT cell id |
1 |
CHOICE Radio Access Technology |
GSM |
– Cell individual offset |
0 (0 dB) |
– Cell selection and re-selection info |
Not present |
– BSIC |
BSIC2 |
– Band indicator |
GSM/DCS-1800 or GSM/PCS-1900 (dependent on band used) |
– BCCH ARFCN |
Value according to the GSM band under test (see 3GPP 34.123-1 table 6.5 for details on the ARFCN) |
– Cell for measurement |
Not present |
– inter-RAT measurement quantity |
|
– Measurement quantity for UTRAN quality estimate |
Not present |
CHOICE system |
GSM |
– Measurement quantity |
GSM carrier RSSI |
– Filter coefficient |
0 |
– BSIC verification required |
not required |
– inter-RAT reporting quantity |
|
UTRAN estimated quality |
FALSE |
CHOICE system |
GSM |
– Observed time difference to GSM cell reporting indicator |
FALSE |
– GSM carrier RSSI reporting indicator |
TRUE |
– Reporting cell status |
|
CHOICE reported cell |
|
– Reported cells within active set or within |
|
virtual active set or of the other RAT |
|
– Maximum number of reported cells |
6 |
CHOICE report criteria |
|
– Periodical reporting criteria |
|
– Amount of reporting |
infinity |
– Reporting interval |
4000 |
Physical channel information elements |
|
– DPCH compressed mode status info |
If the UE requires compressed mode (refer ICS/IXIT), this IE is present and contains the IEs as follows. If the UE does not require compressed mode (refer ICS/IXIT), this IE is not present. |
– TGPS reconfiguration CFN |
(Current CFN + (256 – TTI/10msec))mod 256 |
– Transmission gap pattern sequence |
|
– TGPSI |
1 |
– TGPS status flag |
Activate |
– TGCFN |
(Current CFN + (256 – TTI/10msec))mod 256 |
– TGPSI |
2 |
– TGPS status flag |
Deactivate |
– TGCFN |
Not present |
MEASUREMENT REPORT, if the UE requires compressed mode (refer ICS/IXIT) (Step 1d and step 5a)
Information Element |
Value/remark |
Measurement identity |
Check to see if set to 15 |
Measured Results |
|
– CHOICE measurement |
Check to see if set to "Inter-RAT measured results list" |
– Inter-RAT measured result list |
|
– CHOICE system |
GSM |
– Measured GSM cells |
|
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Check to see if present |
– Observed time difference to GSM cell |
Check that not present |
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Non verified BSIC |
– BCCH ARFCN |
Check that is set to the correct value according to the GSM band under test (see 3GPP 34.123-1 table 6.5 for details on the ARFCN) |
– Observed time difference to GSM cell |
Check that not present |
Measured results on RACH |
Check that not present |
Additional Measured results |
Check that not present |
Event results |
Check that not present |
MEASUREMENT REPORT, if the UE doesn’t requires compressed mode (refer ICS/IXIT) (Step 1d and step 5a)
Information Element |
Value/remark |
Measurement identity |
Check to see if set to 15 |
Measured Results |
|
– CHOICE measurement |
Check to see if set to "Inter-RAT measured results list" |
– Inter-RAT measured result list |
|
– CHOICE system |
GSM |
– Measured GSM cells |
|
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
verified BSIC |
– Inter-RAT cell id |
Check that is set to 0 |
– Observed time difference to GSM cell |
Check that not present |
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Non verified BSIC |
– BCCH ARFCN |
Check that is set to the correct value according to the GSM band under test (see 3GPP 34.123-1 table 6.5 for details on the ARFCN) |
– Observed time difference to GSM cell |
Check that not present |
Measured results on RACH |
Check that not present |
Additional Measured results |
Check that not present |
Event results |
Check that not present |
MEASUREMENT REPORT, if the UE doesn’t require compressed mode (refer ICS/IXIT) (Step 1d and step 5a) (1.28Mcps TDD)
Information Element |
Value/remark |
Measurement identity |
Check to see if set to 15 |
Measured Results |
|
– CHOICE measurement |
Check to see if set to "Inter-RAT measured results list" |
– Inter-RAT measured result list |
|
– CHOICE system |
GSM |
– Measured GSM cells |
|
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Check to see if present |
– Observed time difference to GSM cell |
Check that not present |
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Non verified BSIC |
– BCCH ARFCN |
Check that is set to the correct value according to the GSM band under test (see 3GPP 34.123-1 table 6.5 for details on the ARFCN) |
– Observed time difference to GSM cell |
Check that not present |
Measured results on RACH |
Check that not present |
Additional Measured results |
Check that not present |
Event results |
Check that not present |
HANDOVER FROM UTRAN COMMAND-GSM
The contents of this message is identical to the HANDOVER FROM UTRAN COMMAND-GSM message specified in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Inter-system message |
|
– System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted as BIT STRING (1..512). The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 1 and that the indicated target channel for GSM FR does not exist in the GSM cell |
HANDOVER FROM UTRAN FAILURE
The contents of this message is identical to the HANDOVER FROM UTRAN FAILURE message specified in [9] TS 34.108 clause 9.
8.3.7.5.5 Test requirement
After step 4 the SS shall receive HANDOVER FROM UTRAN FAILURE message using the old UTRA configuration.
After step 5 the UE shall correctly report the GSM RSSI value.
8.3.7.6 Inter system handover from UTRAN/To GSM/Speech/Failure (L2 Establishment)
8.3.7.6.1 Definition
8.3.7.6.2 Conformance requirement
If the UE does not succeed to establish the connection to the other radio access technology , as is unable to obtain L2 establishment it shall
– resume the connection to UTRAN using the resources used before receiving the HANDOVER FROM UTRAN COMMAND message; and
– transmit the HANDOVER FROM UTRAN FAILURE message on uplink DCCH using AM RLC.
Reference(s)
3GPP TS 25.331 clause 8.3.7
TS 04.06 Clause 5.4.1.3
TS 04.08 Clause 3.1.5
8.3.7.6.3 Test purpose
To Test that the UE shall keep its old configuration and transmit a HANDOVER FROM UTRAN FAILURE message, which is set to "physical channel failure" in IE "Inter_RAT HO failure cause", when it receives a HANDOVER FROM UTRAN COMMAND and the connection to GSM for handover cannot be established due to failure in L2 establishment.
8.3.7.6.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51010-1 section 26.6.5.1 shall be referenced for the default parameters of cell 9.
UE: CC State U10 in cell 1
Related ICS/IXIT statement(s)
UE supports both GSM and UTRAN Radio Access Technologies,
UE supports GSM FR,
UE supports UTRAN AMR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480.
Foreseen final state of the UE
The UE is in CC state U10 on cell 1.
Test Procedure
The SS starts the UTRAN cell and brings the UE into call active state (CC state U10) with AMR. SS activates a dedicated GSM traffic channel then sends HANDOVER FROM UTRAN COMMAND indicating a dedicated channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. When the UE does not succeed in establishing the connection to the target radio access technology it shall revert back to UTRA configuration establish the UTRA physical channel(s) used at the time for reception of HANDOVER FROM UTRAN COMMAND transmit the HANDOVER FROM UTRAN FAILURE.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS brings the UE into UTRAN U10 state in cell 1 |
||
2 |
SS |
The SS configures cell 9 as a GSM cell with traffic channel. |
||
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: The target channel. |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
PHYSICAL INFORMATION |
Allows a proper transmission by the MS. Sent in unacknowledged mode as soon as the SS has detected a handover access. As soon as MS detects it then it stops T3124. On SS side T3105 could be started N times at the maximum as long as the step 8 is not performed |
|
10 |
|
SABM |
To establish L2 connection |
|
11 |
SS |
SS does not sent UA frame |
||
12 |
UE |
On T200 expiration, SS sends N200 times the SABM frame (steps 10) Then MS deactivates new channels and reactivates old UTRA resources it had before receiving the handover command |
||
13 |
|
HANDOVER FROM UTRAN FAILURE |
The SS receives the message on the old channel of UTRAN cell. Sent in acknowledge mode The cause in the IE "inter-RAT change failure" is set to "physical channel failure" |
Specific message contents
Same as the message contents of clause 8.3.7.1 for M = 3.
HANDOVER FROM UTRAN FAILURE
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Checked to see if it matches the same value used in the corresponding downlink HANDOVER FROM UTRAN COMMAND –GSM message |
Integrity check info |
|
– Message authentication code |
This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value. |
Inter-RAT handover failure |
|
-Inter-RAT handover failure cause |
physical channel failure |
Inter-system message |
Not Checked |
8.3.7.6.5 Test requirement
The SS shall receive HANDOVER FROM UTRAN FAILURE message on the old channel of the UTRAN cell.
8.3.7.7 Inter system handover from UTRAN/To GSM/Speech/Failure (L1 Synchronization)
8.3.7.7.1 Definition
8.3.7.7.2 Conformance requirement
If the UE does not succeed in establishing the connection to the target radio access technology, it shall:
1> revert back to the UTRA configuration;
1> establish the UTRA physical channel(s) used at the time for reception of HANDOVER FROM UTRAN COMMAND;
…
1> transmit the HANDOVER FROM UTRAN FAILURE message setting the information elements as specified below:
2> include the IE "RRC transaction identifier"; and
2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and
2> clear that entry;
2> set the IE "Inter-RAT handover failure" to "physical channel failure".
1> When the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layer for transmission:
2> the procedure ends.
Reference(s)
TS 25.331 Clause 8.3.7.5
8.3.7.7.3 Test purpose
To test that the UE reactivates its old configuration and transmit a HANDOVER FROM UTRAN FAILURE message, which is set to "physical channel failure" in IE "Inter-RAT Handover failure cause", when it receives a HANDOVER FROM UTRAN COMMAND and the connection to GSM for handover cannot be established due to failure in L1 Synchronization.
8.3.7.7.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 section 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports GSM FR,
– UE supports UTRAN AMR,
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810.
Foreseen final state of the UE
The UE is in CC state U10 on cell 1.
Test Procedure
The SS brings the UE into call active state (CC state U10). The SS activates a dedicated channel in the GSM cell, then sends HANDOVER FROM UTRAN COMMAND indicating a dedicated channel of the target GSM cell to the UE through DCCH using the UTRAN configuration. The UE receives the command, configures itself accordingly and sends the HANDOVER ACCESS burst. Upon receiving this burst, the SS turns off the dedicated channel indicated to the UE, so the UE cannot complete the handover. The SS checks that the UE reverts to the old UTRA configuration by checking that the UE transmits the HANDOVER FROM UTRAN FAILURE message to the SS via the old UTRAN configuration.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS brings the UE into UTRAN U10 state in cell 1. |
||
2 |
SS |
The SS configures a traffic channel on cell 9 (GSM cell). |
||
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: The target channel for GSM FR in GSM Cell. |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
SS |
The target GSM Traffic Channel is Switched off |
||
8 |
|
HANDOVER FROM UTRAN FAILURE |
The SS receives the message via the old UTRAN configuration. The cause in the IE "inter-RAT change failure" is set to "physical channel failure" |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
The contents of this message is identical to the HANDOVER FROM UTRAN COMMAND-GSM message specified in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Inter-system message |
|
– System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted as BIT STRING (1..512). The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 1 |
HANDOVER FROM UTRAN FAILURE
The contents of this message is identical to the HANDOVER FROM UTRAN FAILURE message specified in [9] TS 34.108 clause 9.
8.3.7.7.5 Test requirement
After step 7 the SS shall receive HANDOVER FROM UTRAN FAILURE message via the old UTRA configuration.
8.3.7.8 Inter system handover from UTRAN/To GSM/Speech/Failure (Invalid Inter-RAT message)
8.3.7.8.1 Definition
8.3.7.8.2 Conformance requirement
If the IE "Inter-RAT message" received within the HANDOVER FROM UTRAN COMMAND message does not include a valid inter RAT handover message in accordance with the protocol specifications for the target RAT, the UE shall perform procedure specific error handling as follows. The UE shall:
1> set the IE "failure cause" to the cause value "Inter-RAT protocol error";
1> include the IE "Inter-RAT message" in accordance with the specifications applicable to the other RAT;
1> transmit a HANDOVER FROM UTRAN FAILURE message on the uplink DCCH using AM RLC;
1> when the transmission of the HANDOVER FROM UTRAN FAILURE message has been confirmed by RLC:
2> continue with any ongoing processes and procedures as if the invalid HANDOVER FROM UTRAN COMMAND message has not been received;
2> and the procedure ends.
Reference
3GPP TS 25.331 clause 8.3.7.6
8.3.7.8.3 Test purpose
To Test that the UE shall keep its old configuration and transmit a HANDOVER FROM UTRAN FAILURE message, which is set to "Inter-RAT protocol error" in IE "Inter_RAT HO failure cause", when it receives a Handover From UTRAN message, with the IE "Inter-RAT message" received within the HANDOVER FROM UTRAN COMMAND message not including a valid inter RAT handover message in accordance with the protocol specifications for the target RAT.
8.3.7.8.4 Method of test
Initial conditions
System Simulator : 1 UTRAN cell.
UE : CC State U10 in cell 1
Related ICS/IXIT statement(s)
UE supports both GSM and UTRAN Radio Access Technologies,
UE supports GSM FR,
UE supports UTRAN AMR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480.
Foreseen final state of the UE
The UE is in CC state U10 on cell 1.
Test Procedure
The SS starts the UTRAN cell and brings the UE into call active state (CC state U10) with AMR. The SS then sends a HANDOVER FROM UTRAN COMMAND message not including a valid inter RAT handover message in accordance with the protocol specifications for the target RAT, to the UE through DCCH of the serving UTRAN cell. The UE receives the command and finds that the Inter Rat message is Invalid. The SS checks that the handover is failed by checking that the UE transmits the HANDOVER FROM UTRAN FAILURE message to the SS in UTRAN cell.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS brings the UE into UTRAN U10 state in cell 1 |
||
2 |
|
HandoverFromUTRAN Command-GSM |
Send on cell 1 (UTRAN cell) and the message carries an Invalid HANDOVER FROM UTRAN COMMAND -GSM |
|
3 |
|
HANDOVER FROM UTRAN FAILURE |
The SS receives the message on the old channel of UTRAN cell. |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Arbitrarily selects one integer between 0 to 3 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
Activation time |
Now |
RAB Info |
Not present |
Inter-system message |
|
– CHOICE System type |
GSM |
– Frequency Band |
GSM/DCS 1800 Band |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted and coded according to GSM specifications as Variable Length BIT STRING without Length Indicator. The first/ leftmost/ most significant bit of the bit string contains bit 8 of the first octet of the GSM message. The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Contains an Invalid Handover Command. |
HANDOVER FROM UTRAN FAILURE
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Checked to see if it matches the same value used in the corresponding downlink HANDOVER FROM UTRAN COMMAND –GSM message |
Integrity check info |
|
– Message authentication code |
This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value. |
Inter-RAT handover failure |
|
-Inter-RAT handover failure cause |
Inter-RAT protocol error |
Inter-system message |
Not checked |
8.3.7.8.5 Test requirement
In step 3 the SS shall receive HANDOVER FROM UTRAN FAILURE message on the old channel of the UTRAN cell.
8.3.7.9 Inter system handover from UTRAN/To GSM/Speech/Failure (Unsupported configuration)
8.3.7.9.1 Definition
8.3.7.9.2 Conformance requirement:
If:
…
– the UTRAN instructs the UE to use a non-supported configuration; or
…
the UE shall:
1> transmit a HANDOVER FROM UTRAN FAILURE message, setting the information elements as specified below:
2> include the IE "RRC transaction identifier"; and
2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and
2> clear that entry;
2> set the IE "Inter-RAT handover failure" to "configuration unacceptable";
2> when the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layers for transmission:
3> resume normal operation as if the invalid HANDOVER FROM UTRAN COMMAND message has not been received;
3> and the procedure ends.
Reference
3GPP TS 25.331 clause 8.3.7.8
8.3.7.9.3 Test purpose
To test that the UE shall keep its old configuration and transmit a HANDOVER FROM UTRAN FAILURE message, which is set to "configuration unacceptable" in IE "Inter-RAT Handover failure cause", when it receives a HANDOVER FROM UTRAN COMMAND message, with the IE "GSM message" containing a HANDOVER COMMAND message including a configuration not supported by the UE.
8.3.7.9.4 Method of test
Initial conditions
System Simulator: 1 UTRAN cell.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. Related
ICS/IXIT statement(s)
UE supports both GSM and UTRAN Radio Access Technologies,
UE supports GSM FR,
UE supports UTRAN AMR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810.
Foreseen final state of the UE
The UE is in CC state U10 on cell 1.
Test Procedure
The SS brings the UE into call active state (CC state U10) with AMR on the UTRAN cell. The SS then sends an HANDOVER FROM UTRAN COMMAND message including a configuration not supported by the UE in the HANDOVER COMMAND that is contained in the IE "GSM message", to the UE through DCCH using the UTRAN configuration. The UE receives the command and finds that the configuration given in Inter Rat message is not supported. The SS checks that the UE reverts to the old UTRA configuration by checking that the UE transmits the HANDOVER FROM UTRAN FAILURE message to the SS using the old UTRA configuration.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS brings the UE into UTRAN U10 state in cell 1 |
||
2 |
|
HANDOVER FROM UTRAN COMMAND -GSM |
Send using the UTRAN configuration and the message carries an unsupported configuration. |
|
3 |
|
HANDOVER FROM UTRAN FAILURE |
The SS receives the message via the old UTRAN configuration. |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
The contents of this message is identical to the HANDOVER FROM UTRAN COMMAND-GSM message specified in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
RAB_Info |
Not present |
Inter-system message |
|
– System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted as Variable Length BIT STRING without Length Indicator. The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the frequency band is set to a value not supported by the UE. |
HANDOVER FROM UTRAN FAILURE
The contents of this message is identical to the HANDOVER FROM UTRAN FAILURE message specified in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Inter-RAT handover failure |
|
-Inter-RAT handover failure cause |
configuration unacceptable |
8.3.7.9.5 Test requirement
After step 2 the SS shall receive a HANDOVER FROM UTRAN FAILURE message via the old UTRA configuration.
8.3.7.10 Inter system handover from UTRAN/To GSM/Speech/Failure (Reception by UE in CELL_FACH)
8.3.7.10.1 Definition
8.3.7.10.2 Conformance requirement
If the UE receives HANDOVER FROM UTRAN COMMAND while in CELL_FACH, the UE shall:
1> transmit a HANDOVER FROM UTRAN FAILURE message, setting the information elements as specified below:
2> include the IE "RRC transaction identifier"; and
2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and
2> clear that entry;
2> set the IE "Inter-RAT handover failure" to "protocol error", include IE "Protocol error information"; and
2> set the value of IE "Protocol error cause" to "Message not compatible with receiver state";
2> when the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layers for transmission:
3> resume normal operation as if the invalid HANDOVER FROM UTRAN COMMAND message has not been received;
3> and the procedure ends.
Reference
3GPP TS 25.331 clause 8.3.7.8a
8.3.7.10.3 Test purpose
The UE shall keep its old configuration when the UE receives a HANDOVER FROM UTRAN COMMAND message when in CELL_FACH state and then transmit a HANDOVER FROM UTRAN FAILURE message on the DCCH using AM RLC, which sets value "protocol error" in IE "Inter_RAT HO failure cause" and is set to "Message not compatible with receiver state" in IE "Protocol error cause".
8.3.7.10.4 Method of test
Initial conditions
System Simulator : 1 UTRAN Cell
UE : RRC State CS-DCCH_FACH (state 6-6) as specified in clause 7.4 of TS 34.108, on Cell 1
Related ICS/IXIT statement(s)
UE supports both GSM and UTRAN Radio Access Technologies,
UE supports GSM FR,
UE supports UTRAN AMR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480.
Foreseen final state of the UE
The UE is in RRC is in State CS-DCCH_FACH (state 6-6) as specified in clause 7.4 of TS 34.108, on cell 1.
Test Procedure
The SS starts GSM cell without activating any dedicated channel in the cell, then sends HANDOVER FROM UTRAN COMMAND indicating a dedicated channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. The UE receives the command and configures itself accordingly but cannot complete the handover. The SS checks that the handover is failed by checking that the UE transmits the HANDOVER FROM UTRAN FAILURE message to the SS in UTRAN cell.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS brings the UE into CS-DCCH_FACH (state 6-6) _FACH state in cell 1 |
||
2 |
|
HANDOVER FROM UTRAN COMMAND |
Send on cell 1 (UTRAN cell) and the message indicates: The target channel for GSM |
|
3 |
|
HANDOVER FROM UTRAN FAILURE |
The SS receives the message on the old channel of UTRAN cell. |
Specific message contents
Same as the message contents of clause 8.3.7.1 for M = 3.
HANDOVER FROM UTRAN FAILURE
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Checked to see if it matches the same value used in the corresponding downlink HANDOVER FROM UTRAN COMMAND –GSM message |
Integrity check info |
|
– Message authentication code |
This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value. |
Inter-RAT handover failure |
|
-Inter-RAT handover failure cause |
Protocol Error |
-Diagnostics Type |
Type1 |
-Protocol Error Cause |
Message Not Compatible With Receiver State |
Inter-system message |
Not Checked |
8.3.7.10.5 Test requirement
After step 2 the SS shall receive HANDOVER FROM UTRAN FAILURE message on the old channel of the UTRAN cell.
8.3.7.11 Inter system handover from UTRAN/To GSM/Speech/Failure (Invalid message reception)
8.3.7.11.1 Definition
8.3.7.11.2 Conformance requirement:
If the HANDOVER FROM UTRAN COMMAND message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall:
1> set the IE "RRC transaction identifier" in the HANDOVER FROM UTRAN FAILURE message to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Rejected transactions" in the variable TRANSACTIONS; and
1> clear that entry;
1> set the IE "failure cause" to the cause value "protocol error";
1> include the IE "Protocol error information" with contents set to the value of the variable PROTOCOL_ERROR_INFORMATION;
1> transmit a HANDOVER FROM UTRAN FAILURE message on the uplink DCCH using AM RLC;
1> when the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layers for transmission:
2> continue with any ongoing processes and procedures as if the invalid HANDOVER FROM UTRAN COMMAND message has not been received;
2> and the procedure ends.
Reference
3GPP TS 25.331 clause 8.3.7.6
8.3.7.11.3 Test purpose
The UE shall keep its old configuration when the UE receives a Handover From UTRAN message that cause the variable PROTOCOL_ERROR_REJECT to be set to TRUE. It shall then transmit a HANDOVER FROM UTRAN FAILURE message on the uplink DCCH. The IE "Protocol error information" shall contain an IE "Protocol error cause" set to " Message extension not comprehended ".
8.3.7.11.4 Method of test
Initial conditions
System Simulator : 1 UTRAN cell.
UE : CC State U10 in cell 1
Related ICS/IXIT statement(s)
UE supports both GSM and UTRAN Radio Access Technologies,
UE supports GSM FR,
UE supports UTRAN AMR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480.
Foreseen final state of the UE
The UE is in CC state U10 on cell 1.
Test Procedure
The SS starts the UTRAN cell and brings the UE into call active state (CC state U10) with AMR. The SS then sends an HANDOVER FROM UTRAN COMMAND message, which contains an unexpected critical message extension, to the UE through DCCH of the serving UTRAN cell. The SS checks that the handover is failed by checking that the UE transmits a HANDOVER FROM UTRAN FAILURE message on the uplink DCCH. The IE "Protocol error information" shall contain an IE "Protocol error cause" set to " Message extension not comprehended ".
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS brings the UE into UTRAN U10 state in cell 1 |
||
2 |
|
Handover From UTRAN Command |
Send on cell 1 (UTRAN cell) and the message is short in length to be decoded into a valid Handover From UTRAN command |
|
3 |
|
HANDOVER FROM UTRAN FAILURE |
The SS receives the message on the old channel of UTRAN cell. |
Specific message contents
HANDOVER FROM UTRAN COMMAND
Use the HANDOVER FROM UTRAN COMMAND message as defined in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/remark |
Critical extensions |
’FF’H |
HANDOVER FROM UTRAN FAILURE (Step 3)
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Checked to see if it matches the same value used in the corresponding downlink HANDOVER FROM UTRAN COMMAND message |
Integrity check info |
|
– Message authentication code |
This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value. |
Inter-RAT handover failure |
|
-Inter-RAT handover failure cause |
Protocol Error |
-Diagnostics Type |
Type1 |
-Protocol Error Cause |
Message extension not comprehended |
Inter-system message |
Not Checked |
8.3.7.11.5 Test requirement
In step 3 the SS shall receive HANDOVER FROM UTRAN FAILURE message in the UTRAN cell.
8.3.7.12 Inter system handover from UTRAN/To GSM/Speech/Failure (Physical channel Failure and Reversion Failure)
8.3.7.12.1 Definition
8.3.7.12.2 Conformance requirement
1. This section applies to R99 & Rel-4 releases:
If the UE does not succeed in establishing the connection to the target radio access technology, it shall:
1> revert back to the UTRA configuration;
1> establish the UTRA physical channel(s) used at the time for reception of HANDOVER FROM UTRAN COMMAND;
1> if the UE does not succeed to establish the UTRA physical channel(s):
2> perform a cell update procedure according to subclause 8.3.1 in TS 25.331with cause "Radio link failure";
2> when the cell update procedure has completed successfully:
3> proceed as below.
1> transmit the HANDOVER FROM UTRAN FAILURE message setting the information elements as specified below:
2> include the IE "RRC transaction identifier"; and
2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and
2> clear that entry;
2> set the IE "Inter-RAT handover failure" to "physical channel failure".
1> When the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layer for transmission:
2> the procedure ends.
2. This section applies from Rel-5 releases onwards:
If the UE does not succeed in establishing the connection to the target radio access technology, it shall:
1> revert back to the UTRA configuration;
1> if the CM_PATTERN_ACTIVATION_ABORTED flag is not set to TRUE:
2> establish the UTRA physical channel(s) (including HS-DSCH related channels) used at the time for reception of HANDOVER FROM UTRAN COMMAND;
2> perform the physical layer synchronisation procedure A as specified in [29] (FDD only);
2> after the establishment of the uplink physical channel, send DPCCH and no DPDCH according to [26] during the number of frames indicated in the IE "PC preamble" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE; and
2> then not send any data on signalling radio bearers RB0 to RB4 during the number of frames indicated in the IE "SRB delay" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE.
Reference
3GPP TS 25.331 clause 8.3.7.5
8.3.7.12.3 Test purpose
The UE shall perform a cell update when the UE fails to revert to the old configuration after the detection of physical channel failure in the target RAT cell as given in the HANDOVER FROM UTRAN COMMAND message. After the UE completes the cell update procedure, the UE shall transmit a HANDOVER FROM UTRAN FAILURE message on the DCCH using AM RLC, including IE "failure cause" set to "physical channel failure".
8.3.7.12.4 Method of test
Initial conditions
System Simulator: 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 section 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9.
SYSTEM INFORMATION BLOCK TYPE 1 (see specific message contents).
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
The ‘timer poll’ value in the SS RLC transmit entity should be set to 800 ms.
Related ICS/IXIT statement(s)
UE supports both GSM and UTRAN Radio Access Technologies,
UE supports GSM FR,
UE supports UTRAN AMR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810.
Foreseen final state of the UE
The UE is in CC state U10 on cell 1.
Test Procedure
The SS and brings the UE into call active state (CC state U10) with AMR on the UTRAN cell. The SS configures a target dedicated channel on the GSM cell. The SS sends a HANDOVER FROM UTRAN COMMAND indicating a dedicated channel of the target GSM cell to the UE through DCCH using the UTRAN configuration. The UE receives the command and configures itself accordingly but cannot complete the handover and wants to revert to the old configuration, but the UE cannot revert to the old configuration because the SS released the old configuration. The UE transmits a CELL UPDATE message on uplink CCCH with IE "Cell update cause" set to "radio link failure". The SS shall transmit CELL UPDATE CONFIRM message on downlink DCCH after receiving CELL UPDATE message. The UE transmits PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using AM RLC and subsequently transmits the HANDOVER FROM UTRAN FAILURE message to the SS using the new UTRA configuration, on the DCCH using AM RLC, setting the value of IE "failure cause" to " physical channel failure". In case of R99 or Rel-4, UE may transmit HANDOVER FROM UTRAN FAILURE message using uplink AM RLC and subsequently PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS brings the UE into UTRAN U10 state in cell 1 |
||
2 |
SS |
The SS configures a dedicated GSM FR channel on the GSM cell. |
||
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send using the UTRA configuration and the message indicates: the target channel for GSM FR. |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER COMMAND message that is contained within the HANDOVER FROM UTRAN COMMAND -GSM message |
||
4a |
SS |
SS removes the UTRAN physical channel (DPCH) allocated to the mobile to ensure UE will not be able to revert back to the old UTRAN configuration when handover failed |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. Upon receiving this burst, SS removes the target GSM Traffic Channel. As a result not only the handover will fail, but also the reversion to the old UTRA configuration. |
|
6 |
|
CELL UPDATE |
The value "radio link failure" shall be set in IE "Cell update cause". |
|
7 |
|
CELL UPDATE CONFIRM |
This message include IE "Physical channel information elements". |
|
8 |
The SS configures the dedicated physical channel according to the IE "Physical channel information elements" included in the CELL UPDATE CONFIRM message. |
|||
9 |
|
PHYSICAL CHANNEL RECONFIGURATION COMPLETE |
||
10 |
|
HANDOVER FROM UTRAN FAILURE |
The IE "failure cause" shall be set to "physical channel failure" |
|
Note: For R99 and Rel-4 UEs the messages in Steps 9 and 10 may be received in either order. |
Specific message contents
Same as the message contents of clause 8.3.7.1 for Execution 3.
System Information Block type 1 (FDD)
Use the default system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:
Information Element |
Value/remark |
– UE Timers and constants in connected mode |
|
– T312 |
2 |
CELL UPDATE (Step 6)
The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in TS 34.108, clause 9,with the following exceptions:
Information Element |
Value/remark |
U-RNTI |
|
– SRNC Identity |
Check to see if set to ‘0000 0000 0001’ |
– S-RNTI |
Check to see if set to ‘0000 0000 0000 0000 0001’ |
Cell Update Cause |
"radio link failure" |
CELL UPDATE CONFIRM (Step 7) (FDD)
The contents of CELL UPDATE CONFIRM message is identical as "CELL UPDATE CONFIRM message" as found in TS 34.108, clause 9,with the following exceptions:
Information Element |
Value/remark |
Version |
U-RNTI |
Same as CELL UPDATE message in step 3 |
|
RRC State indicator |
CELL_DCH |
|
CHOICE channel requirement |
Uplink DPCH info |
|
-UplinkDPCH Info |
Same as specified in “Contents of RADIO BEARER SETUP message: AM or UM” for condition A2 (Speech CS) in TS 34.108 clause 9.1 |
|
– DPCCH power offset |
-40 (-80 dB) |
|
– PC Preamble |
1 frame |
|
– SRB delay |
7 frames |
|
– Power Control Algorithm |
Algorithm1 |
|
– TPC step size |
0 (1 dB) |
|
– Scrambling code type |
Long |
|
– Scrambling code number |
0 (0 to 16777215) |
|
– Number of DPDCH |
Not Present(1) |
|
– spreading factor |
Reference to TS34.108 clause 6.10 Parameter Set |
|
– TFCI existence |
Reference to TS34.108 clause 6.10 Parameter Set |
|
– Number of FBI bit |
Reference to TS34.108 clause 6.10 Parameter Set |
|
– Puncturing Limit |
Reference to TS34.108 clause 6.10 Parameter Set |
|
Downlink information common for all radio links |
Same as specified in “Contents of RADIO BEARER SETUP message: AM or UM” for condition A2 (Speech CS) in TS 34.108 clause 9.1 |
|
CHOICE Mode |
FDD |
|
– Downlink DPCH info common for all RL |
||
– Timing indicator |
Initialise |
|
– CFN-targetSFN frame offset |
Not Present |
|
– Downlink DPCH power control information |
||
– DPC mode |
0 (single) |
|
– CHOICE mode |
FDD |
|
– Power offset PPilot-DPDCH |
0 |
|
– DL rate matching restriction information |
Not Present |
|
– Spreading factor |
Reference to TS34.108 clause 6.10 Parameter Set |
|
– Fixed or Flexible Position |
Reference to TS34.108 clause 6.10 Parameter Set |
|
– TFCI existence |
Reference to TS34.108 clause 6.10 Parameter Set |
|
– CHOICE SF |
Reference to TS34.108 clause 6.10 Parameter Set |
|
– DPCH compressed mode info |
Not Present |
|
– TX Diversity mode |
None |
|
– SSDT information |
Not Present |
R99 and Rel-4 only |
– Default DPCH Offset Value |
Arbitrary set to value 0..306688 by step of 512 |
|
Downlink information for each radio links |
||
– Primary CPICH info |
||
– Primary scrambling code |
100 |
|
– PDSCH with SHO DCH info |
Not Present |
R99 and Rel-4 only |
– PDSCH code mapping |
Not Present |
R99 and Rel-4 only |
– Downlink DPCH info for each RL |
||
– Primary CPICH usage for channel estimation |
Primary CPICH may be used |
|
– DPCH frame offset |
Set to value: Default DPCH Offset value (as currently stored in SS) mod 38400 |
|
– Secondary CPICH info |
Not Present |
|
– DL channelisation code |
||
– Secondary scrambling code |
2 |
|
– Spreading factor |
Reference to TS34.108 clause 6.10 Parameter Set |
|
– Code number |
SF-1(SF is reference to TS34.108 clause 6.10 Parameter Set) |
|
– Scrambling code change |
No change |
|
– TPC combination index |
0 |
|
– SSDT Cell Identity |
Not Present |
R99 and Rel-4 only |
– Closed loop timing adjustment mode |
Not Present |
|
– SCCPCH information for FACH |
Not Present |
R99 and Rel-4 only |
CELL UPDATE CONFIRM (Step 7) (3.84 Mcps TDD)
The contents of CELL UPDATE CONFIRM message is identical as "CELL UPDATE CONFIRM message" as found in TS34.108, clause 9, with the following exceptions:
Information Element |
Value/remark |
U-RNTI |
Same as CELL UPDATE message in step 3 |
RRC State indicator |
CELL_DCH |
Frequency info |
|
– CHOICE mode |
TDD |
– UARFCN (Nt) |
Reference to TS34.108 clause 5.1 Test frequencies |
Maximum allowed UL TX power |
30dBm |
CHOICE Mode |
TDD |
Downlink information for each radio links |
|
– Primary CCPCH info |
|
– CHOICE mode |
TDD |
– CHOICE TDD option |
3.84 Mcps TDD |
– CHOICE SyncCase |
Not Present |
– Cell Parameters ID |
Not Present |
– Block STTD indicator |
FALSE |
– Downlink DPCH info for each RL |
|
– CHOICE mode |
TDD |
– DL CCTrCh List |
|
– TFCS ID |
1 |
– Time info |
|
– Activation time |
Not Present (default) |
– Duration |
Not Present (default) |
– Common timeslot info |
Not Present (default) |
– Downlink DPCH timeslots and codes |
Not Present (default) |
– UL CCTrCH TPC List |
Not Present (default) |
CELL UPDATE CONFIRM (Step 7) (1.28 Mcps TDD)
The contents of CELL UPDATE CONFIRM message is identical as "CELL UPDATE CONFIRM message" as found in TS34.108, clause 9, with the following exceptions:
Information Element |
Value/remark |
U-RNTI |
Same as CELL UPDATE message in step 3 |
RRC State indicator |
CELL_DCH |
Frequency info |
|
– CHOICE mode |
TDD |
– UARFCN (Nt) |
Reference to TS34.108 clause 5.1 Test frequencies |
Maximum allowed UL TX power |
30dBm |
CHOICE Mode |
TDD |
Downlink information for each radio links |
|
– Primary CCPCH info |
|
– CHOICE mode |
TDD |
– CHOICE TDD option |
1.28 Mcps TDD |
– TSTD indicator |
FALSE |
– Cell Parameters ID |
Not Present |
– Block STTD indicator |
FALSE |
– Downlink DPCH info for each RL |
|
– CHOICE mode |
TDD |
– DL CCTrCh List |
|
– TFCS ID |
1 |
– Time info |
|
– Activation time |
Not Present (default) |
– Duration |
Not Present (default) |
– Common timeslot info |
Not Present (default) |
– Downlink DPCH timeslots and codes |
Not Present (default) |
– UL CCTrCH TPC List |
Not Present (default) |
CELL UPDATE CONFIRM (Step 7) (3.84 Mcps TDD)
The contents of CELL UPDATE CONFIRM message is identical as "CELL UPDATE CONFIRM message" as found in TS34.108, clause 9, with the following exceptions:
Information Element |
Value/remark |
U-RNTI |
Same as CELL UPDATE message in step 3 |
RRC State indicator |
CELL_DCH |
Frequency info |
|
– CHOICE mode |
TDD |
– UARFCN (Nt) |
Reference to TS34.108 clause 5.1 Test frequencies |
Maximum allowed UL TX power |
30dBm |
CHOICE Mode |
TDD |
Downlink information for each radio links |
|
– Primary CCPCH info |
|
– CHOICE mode |
TDD |
– CHOICE TDD option |
7.68 Mcps TDD |
– CHOICE SyncCase |
Not Present |
– Cell Parameters ID |
Not Present |
– Block STTD indicator |
FALSE |
– Downlink DPCH info for each RL |
|
– CHOICE mode |
TDD |
– DL CCTrCh List |
|
– TFCS ID |
1 |
– Time info |
|
– Activation time |
Not Present (default) |
– Duration |
Not Present (default) |
– Common timeslot info |
Not Present (default) |
– Downlink DPCH timeslots and codes |
Not Present (default) |
– UL CCTrCH TPC List |
Not Present (default) |
HANDOVER FROM UTRAN COMMAND
The contents of this message is identical to the HANDOVER FROM UTRAN COMMAND-GSM message specified in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Inter-system message |
|
– System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted as BIT STRING (1..512). The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 1 |
PHYSICAL CHANNEL RECONFIGURATION COMPLETE (Step 9)
Use the same message found in TS 34.108 clause 9, with the exceptions of the following IEs:
Information Element |
Value/remark |
Uplink counter synchronisation info |
Not Checked |
HANDOVER FROM UTRAN FAILURE (Step 10)
The contents of this message are identical to the HANDOVER FROM UTRAN FAILURE message specified in [9] TS 34.108 clause 9.
8.3.7.12.5 Test requirement
After step 5 the SS shall receive a CELL UPDATE message.
At step 9 the SS shall receive a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.
At step 10 the SS shall receive a HANDOVER FROM UTRAN FAILURE message via the new UTRA configuration.
Note: For R99 and Rel-4 UEs the messages in Steps 9 and 10 may be received in either order.
8.3.7.13 Inter system handover from UTRAN/To GSM/ success / call under establishment
8.3.7.13.1 Definition
8.3.7.13.2 Conformance requirement
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" |
Standard to apply |
Inter RAT Message |
GSM |
GSM TS 04.18, version 8.5.0 or later |
HANDOVER COMMAND |
cdma2000 |
TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later |
1> if the IE "System type" has the value "GSM":
2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain":
3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message.
NOTE: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1.
NOTE: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification.
….
Upon successfully completing the handover, UTRAN should:
1> release the radio connection; and
1> remove all context information for the concerned UE.
Upon successfully completing the handover, the UE shall:
1> if the USIM is present:
2> store the current START value for every CN domain in the USIM [50];
2> if the "START" stored in the USIM [50] for a CN domain is greater than or equal to the value "THRESHOLD" of the variable START_THRESHOLD:
3> delete the ciphering and integrity keys that are stored in the USIM for that CN domain;
3> inform the deletion of these keys to upper layers.
1> if the SIM is present:
2> store the current START value for every CN domain in the UE;
2> if the "START" stored in the UE for a CN domain is greater than or equal to the value "THRESHOLD" of the variable START_THRESHOLD:
3> delete the ciphering and integrity keys that are stored in the SIM for that CN domain;
3> inform the deletion of these keys to upper layers.
1> if there are any NAS messages with the IE "CN domain identity" set to "CS domain" for which the successful delivery of the INITIAL DIRECT TRANSFER message or UPLINK DIRECT TRANSFER message on signalling radio bearer RB3 or signalling radio bearer RB4 that have not yet been confirmed by RLC:
2> retransmit those NAS messages to the network on the newly established radio connection to the target radio access technology.
1> clear or set variables upon leaving UTRA RRC connected mode as specified in subclause 13.4.
NOTE: The release of the UMTS radio resources is initiated from the target RAT.
Reference
3GPP TS 25.331 clause 8.3.7.3, 8.3.7.4
8.3.7.13.3 Test purpose
To test that the UE supporting both GSM and UTRAN performs handover from UTRAN to the indicated channel of GSM target cell when the UE receives a HANDOVER FROM UTRAN COMMAND in call establishment phase.
To test that the UE continues the call in the GSM cell, after successful completion of the Handover.
8.3.7.13.4 Method of test
Initial conditions
System Simulator: 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010-1 26.6.5.1 section 40 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9 except the BCCH ARFCN for GSM 900 should be 18 and for GSM 1900 should be 646.
UE: CC State U0 (NULL state) in cell 1.
Related ICS/IXIT statement(s)
UE supports both GSM and UTRAN Radio Access Technologies,
UE supports GSM FR,
UE supports UTRAN AMR,
UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-850, GSM-PCS, GSM-710, GSM 750, T_GSM-810.
Foreseen final state of the UE
The UE is in CC state U0 (NULL) on cell 1.
Test Procedure
The SS activates the UTRAN cell and GSM Cell. The UE is triggered to initialise an MO speech call. During the call establishment phase, the SS is configured to not transmit the RLC Acknowledgment for SETUP message. SS configures a dedicated channel in GSM Cell, then sends the UE a HANDOVER FROM UTRAN COMMAND indicating the dedicated channel in the target GSM cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell. The SS checks that the MS correctly retransmits a CC SETUP message that was not acknowledged by UTRAN RLC Layer before the Handover, following completion of the handover to GSM cell.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
To trigger the UE to initialise an MO call |
||
2 |
|
SETUP |
SS does not Acknowledge it |
|
3 |
SS |
The SS starts the GSM cell and configure a dedicated channel SDCCH. |
||
4 |
|
HANDOVER FROM UTRAN COMMANDGSM |
Send via the UTRA configuration and the message indicates: the dedicated channel SDCCH. |
|
5 |
UE |
The UE accepts the handover command and switches to the GSM dedicated channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
6 |
|
HANDOVER ACCESS |
The SS receives this burst on the dedicated channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
HANDOVER ACCESS |
||
10 |
|
PHYSICAL INFORMATION |
||
11 |
Void |
|||
12 |
Void |
|||
13 |
|
HANDOVER COMPLETE |
The SS receives the message on the dedicated channel of GSM cell. |
|
14 |
-> |
SETUP |
The SS receives the message on the dedicated channel of GSM cell. |
|
15 |
<- |
CHANNEL RELEASE |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
The contents of this message is identical to the HANDOVER FROM UTRAN COMMAND-GSM message specified in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
RAB_info |
Not present |
Inter-system message |
|
– System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted as Variable Length BIT STRING without Length Indicator. The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 4 in clause 26.6.5.2 of GSM 51.010, except that the CHANNEL MODE IE is included with value = signalling only and the BCCH ARFCN for GSM 900 should be 18 and for GSM 1900 should be 646 |
8.3.7.13.5 Test requirement
At step 14 the SS shall receive SETUP message on the dedicated channel of the GSM cell.
8.3.7.14 Inter system handover from UTRAN/To GSM/Speech/Success (stop of HS-DSCH reception)
8.3.7.14.1 Definition and applicability
All UEs which support FDD or TDD, HS-PDSCH and GSM.
8.3.7.14.2 Conformance requirement
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
The UE shall:
- if HS-DSCH is configured for UTRA:
2> stop any HS-DSCH reception procedures;
2> clear any stored HS-PDSCH configuration;
2> act as if the IE "MAC-hs reset indicator" is received and set to TRUE;
2> release all HARQ resources;
2> remove any H-RNTI stored;
2> clear the variable H_RNTI;
2> set the variable HS_DSCH_RECEPTION to FALSE.
1> establish the connection to the target radio access technology, by using the contents of the IE "Inter-RAT message". This IE contains a message specified in another standard, as indicated by the IE "System type", and carries information about the candidate/ target cell identifier(s) and radio parameters relevant for the target radio access technology. The correspondence between the value of the IE "System type", the standard to apply and the message contained within IE "Inter RAT message" is shown in the following:
Value of the IE "System type" |
Standard to apply |
Inter RAT Message |
GSM |
GSM TS 04.18, version 8.5.0 or later, or 3GPP TS 44.018 |
HANDOVER COMMAND |
GERAN Iu |
3GPP TS 44.118 |
RADIO BEARER RECONFIGURATION |
cdma2000 |
TIA/EIA/IS-2000 or later, TIA/EIA/IS-833 or later, TIA/EIQ/IS-834 or later |
1> if the IE "System type" has the value "GSM" or "GERAN Iu":
2> if the IE "Frequency band" has the value "GSM /DCS 1800 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1800 band".
2> if the IE "Frequency band" has the value " GSM /PCS 1900 band used":
3> set the BAND_INDICATOR [45] to "ARFCN indicates 1900 band".
1> apply the "Inter RAT Message" according to the "standard to apply" in the table above.
1> if the IE "RAB information List" is included in the HANDOVER FROM UTRAN COMMAND message:
2> if the IE "RAB information List" includes one IE "RAB Info" with the IE "CN domain Identity" set to "CS domain":
3> connect upper layer entities corresponding to the indicated CS domain RAB to the radio resources indicated in the inter-RAT message.
NOTE1: In this version of the specification the maximum number of CS domain RABs which may be included in the IE "RAB information List" is limited to 1.
NOTE2: In handover to GERAN Iu mode, the RAB information is included in the RADIO BEARER RECONFIGURATION message specified in [53].
NOTE3: Requirements concerning the establishment of the radio connection towards the other radio access technology and the signalling procedure are outside the scope of this specification.
NOTE4: The UE may ignore the IE "NAS synchronisation indicator" if included in the HANDOVER FROM UTRAN COMMAND message;
NOTE5: The UE behaviour is undefined if the IE "Re-establishment timer" in the IE "RAB info" indicates a timer different from the timer currently configured for this RAB.
During compressed mode on the associated DPCH or F-DPCH, the following applies for the UE for transmission of HS-DPCCH and reception of HS-SCCH and HS-PDSCH:
- The UE shall neglect a HS-SCCH or HS-PDSCH transmission, if a part of the HS-SCCH or a part of the corresponding HS-PDSCH overlaps with a downlink transmission gap on the associated DPCH or F-DPCH. In this case, neither ACK, nor NACK shall be transmitted by the UE to respond to the corresponding downlink transmission.
- If a part of a HS-DPCCH slot allocated to HARQ-ACK overlaps with an uplink transmission gap on the associated DPCH, the UE shall use DTX on the HS-DPCCH in that HS-DPCCH slot.
- If in a HS-DPCCH sub-frame a part of the slots allocated for CQI information overlaps with an uplink transmission gap on the associated DPCH, the UE shall not transmit CQI information in that sub-frame.
- If a CQI report is scheduled in the current CQI field according to subclause 6A.1.2 paragraph (2), and the corresponding 3-slot reference period (as defined in subclause 6A.2) wholly or partly overlaps a downlink transmission gap, then the UE shall use DTX in the current CQI field and in the CQI fields in the next (N_cqi_transmit–1) subframes.
Reference(s)
TS 25.331 Clause 8.3.7.5.
TS 25.214 Clause 6A.3.
8.3.7.14.3 Test purpose
1. To test that the UE supporting both GSM and UTRAN hands over from a UTRAN serving cell to the indicated channel of GSM target cell when the UE is in the speech call active state, active PS RAB with HS-DSCH reception and receives an HANDOVER FROM UTRAN COMMAND.2. To verify that UE stops HS-DSCH reception after receiving the HANDOVER FROM UTRAN COMMAND.
3. For the UEs supporting compressed mode, to verify that the HS-DSCH reception has no impact on the GSM cells measurement when GSM compressed mode is activated.
8.3.7.14.4 Method of test
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 26.6.5.1 shall be referenced for the default parameters of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Related ICS/IXIT statement(s)
– UE supports both GSM and UTRAN Radio Access Technologies,
– UE supports PS+CS
– UE supports GSM AMR
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810
– UE supports compressed mode (FDD only).
Foreseen final state of the UE
The UE is in CC state U10 on cell 9.
Test Procedure
The SS brings the UE into call active state (CC state U10) with AMR with configuration (conversational/speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + interactive/ background UL: 384kbps, DL: (max bit rate depending on UE category) PS RAB + uplink:3.4 DL3.4 kbps SRBs). In case UE does not support data rate of 384kbps in UL, then 64kbps should be used in UL for the PS RAB. PS RAB is configured with HS-DSCH.
The SS sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to configure the compressed mode pattern sequence parameters. When the PHYSICAL CHANNEL RECONFIGURATION COMPLETE is received from the UE, the SS sends a MEASUREMENT CONTROL message indicating two GSM cells of which only one is actually configured. This message is used to provide measurement control parameters (GSM RSSI) to the UE and to start compressed mode for the measurement if required according to the UE capabilities. The UE replies according to request by sending MEASUREMENT REPORT messages periodically to SS (reporting period is 4000 ms).
The SS configures the appropriate traffic channel on the GSM cell, then sends HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel on the target GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS through GSM cell. SS receives GPRS SUSPENSION REQUEST from the UE.
SS disconnects the CS call and releases the RR connection.
Once RR connection is released, an RAU procedure is performed. To check that PDP context is active, SS sends MODIFY PDP CONTEXT REQUEST and assigns new QoS in GPRS cell. The UE may or may not accept the new QoS and replies to the SS accordingly.
For UEs where the PIXIT indicates support for the GSM/ DCS 1800 and/ or GSM/ PCS 1900 band, the whole test should be repeated to cover these frequencies in order to verify the correct handling of the IE "Frequency band".
Inter RAT handover is normally preceded by the configuration and activation of compressed mode (depending on UE capabilities/ PIXIT) and the configuration of inter- RAT measurements. The inter RAT handover is normally initiated by the SS upon receiving an event triggered measurement report. The verification of this functionality is covered by other subclauses.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS bring the UE into UTRAN U10 state and PS RAB with HS-DSCH active in cell 1. If the UE does not require compressed mode (refer ICS/IXIT), then go to step 1c. |
||
1a |
|
PHYSICAL CHANNEL RECONFIGURATION |
Compressed mode pattern sequence parameters are loaded to UE. |
|
1b |
|
PHYSICAL CHANNEL RECONFIGURATION COMPLETE |
||
1c |
|
MEASUREMENT CONTROL |
SS provides GSM RSSI measurement control parameters to UE. Compressed mode for GSM RSSI measurement is started if required as per UE capabilities. |
|
1d |
|
MEASUREMENT REPORT |
UE reports measurement results of GSM RSSI measurement to SS. |
|
2 |
SS |
The SS configures a traffic channel on cell 9 (GSM cell): for GSM AMR (M = 1); or |
||
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
PHYSICAL INFORMATION |
||
10 |
|
SABM |
||
11 |
|
UA |
||
12 |
|
HANDOVER COMPLETE |
The SS receives the message on the traffic channel of GSM cell. |
|
13 |
|
GPRS SUSPENSION REQUEST |
UE sends GPRS SUSPENSION REQUEST on FACCH. Suspension cause value is not checked |
|
14 |
|
CHANNEL RELEASE |
SS disconnects the CS call and releases the RR connection. The GPRS Resumption IE is included and is set to “resumption of GPRS services successfully acknowledged.” |
|
14a |
|
CHANNEL REQUEST |
The SS receives this burst on the RACH of cell 9(GSM cell). |
|
14b |
|
IMMEDIATE ASSIGNMENT |
Sent on AGCH. |
|
15 |
|
ROUTING AREA UPDATE REQUEST |
GMM “update type” = ‘combined RA/LA updating’ |
|
16 |
|
ROUTING AREA UPDATE ACCEPT |
GMM. P-TMSI is included |
|
17 |
|
ROUTING AREA UPDATE COMPLETE |
||
18 |
|
MODIFY PDP CONTEXT REQUEST |
SS requests the modification of a PDP context, with a new QoS (peak throughput is changed to ‘0011’) |
|
A19 |
|
MODIFY PDP CONTEXT ACCEPT |
UE behaviour type A: Accept the PDP context modification |
|
B19 |
|
DEACTIVATE PDP CONTEXT REQUEST |
UE behaviour type B: Initiate the PDP context deactivation. Cause set to ‘QoS not accepted’ |
|
B19a |
|
DEACTIVATE PDP CONTEXT ACCEPT |
UE behaviour type B: Accept the PDP context deactivation. |
|
B19b |
|
DETACH REQUEST |
UE behaviour type B: A non-auto attach UE may (optionally) send a Detach Request. The SS shall wait up to ‘T3390’ seconds for the Detach Request. |
|
B19c |
|
DETACH ACCEPT |
If the UE transmitted a Detach Request message in step B20b then the SS responds with a Detach Accept message. |
Specific message contents
PHYSICAL CHANNEL RECONFIGURATION (Step 1a)
Use the same message sub-type as in TS 34.108 titled "Speech in CS", with the following exceptions:
Information Element |
Value/remark |
Downlink information common for all radio links |
|
– DPCH compressed mode info |
|
– TGPSI |
1 |
– TGPS Status Flag |
Deactivate |
– TGCFN |
Not present |
– Transmission gap pattern sequence configuration parameters |
|
– TGMP |
GSM Carrier RSSI Measurement |
– TGPRC |
Infinity |
– TGSN |
4 |
– TGL1 |
7 |
– TGL2 |
Not present |
– TGD |
Undefined |
– TGPL1 |
12 |
– RPP |
Mode 0 |
– ITP |
Mode 0 |
CHOICE UL/DL Mode |
UL&DL or UL-only or DL-only (depends on UE’s Measurement capability) |
– Downlink compressed mode method |
SF/2 |
– Uplink compressed mode method |
HLS |
– Downlink frame type |
A |
– DeltaSIR1 |
20 (2.0) |
– DeltaSIRAfter1 |
10 (1.0) |
– DeltaSIR2 |
Not Present |
– DeltaSIR2After2 |
Not Present |
– N identify abort |
Not Present |
– T Reconfirm abort |
Not Present |
– TGPSI |
2 |
– TGPS Status Flag |
Deactivate |
– TGCFN |
Not present |
– Transmission gap pattern sequence configuration parameters |
|
– TGMP |
GSM Initial BSIC identification |
– TGPRC |
Infinity |
– TGSN |
4 |
– TGL1 |
7 |
– TGL2 |
Not present |
– TGD |
Undefined |
– TGPL1 |
8 |
– RPP |
Mode 0 |
– ITP |
Mode 0 |
CHOICE UL/DL Mode |
UL&DL or UL-only or DL-only (depends on UE’s Measurement capability) |
– Downlink compressed mode method |
SF/2 |
– Uplink compressed mode method |
HLS |
– Downlink frame type |
A |
– DeltaSIR1 |
20 (2.0) |
– DeltaSIRAfter1 |
10 (1.0) |
– DeltaSIR2 |
Not Present |
– DeltaSIR2After2 |
Not Present |
– N identify abort |
128 |
– T Reconfirm abort |
Not Present |
MEASUREMENT CONTROL (Step 1c)
Information Element |
Value/remark |
---|---|
Measurement Identity |
15 |
Measurement Command |
Setup |
Measurement Reporting Mode |
|
– Measurement Reporting Transfer Mode |
Acknowledged Mode RLC |
– Periodic Reporting / Event Trigger Reporting Mode |
Periodical reporting |
Additional measurements list |
Not Present |
CHOICE measurement type |
|
– inter-RAT measurement |
|
– inter-RAT measurement object list |
|
CHOICE Inter-RAT Cell Removal |
Remove all inter-RAT cells |
– New inter-RAT cells |
|
– inter-RAT cell id |
0 |
CHOICE Radio Access Technology |
GSM |
– Cell individual offset |
0 (0 dB) |
– Cell selection and re-selection info |
Not present |
– BSIC |
Value set to correspond with HANDOVER COMMAND IEs seen in TS 51.010 clause 26.6.5.1 M=2 |
– Band indicator |
GSM/DCS-1800 or GSM/PCS-1900 (dependent on band used) |
– BCCH ARFCN |
Value the same as HANDOVER COMMAND in TS 51.010 clause 26.6.5.1 M=2 (dependant on band used) |
– inter-RAT cell id |
1 |
CHOICE Radio Access Technology |
GSM |
– Cell individual offset |
0 (0 dB) |
– Cell selection and re-selection info |
Not present |
– BSIC |
BSIC2 |
– Band indicator |
GSM/DCS-1800 or GSM/PCS-1900 (dependent on band used) |
– BCCH ARFCN |
Value according to the GSM band under test (see 3GPP 34.123-1 table 6.5 for details on the ARFCN) |
– Cell for measurement |
Not present |
– inter-RAT measurement quantity |
|
– Measurement quantity for UTRAN quality estimate |
Not present |
CHOICE system |
GSM |
– Measurement quantity |
GSM carrier RSSI |
– Filter coefficient |
0 |
– BSIC verification required |
not required |
– inter-RAT reporting quantity |
|
UTRAN estimated quality |
FALSE |
CHOICE system |
GSM |
– Observed time difference to GSM cell reporting indicator |
FALSE |
– GSM carrier RSSI reporting indicator |
TRUE |
– Reporting cell status |
|
CHOICE reported cell |
|
– Reported cells within active set or within |
|
virtual active set or of the other RAT |
|
– Maximum number of reported cells |
6 |
CHOICE report criteria |
|
– Periodical reporting criteria |
|
– Amount of reporting |
Infinity |
– Reporting interval |
4000 |
Physical channel information elements |
|
– DPCH compressed mode status info |
If the UE requires compressed mode (refer ICS/IXIT), this IE is present and contains the IEs as follows. If the UE does not require compressed mode (refer ICS/IXIT), this IE is not present. |
– TGPS reconfiguration CFN |
(Current CFN + (256 – TTI/10msec))mod 256 |
– Transmission gap pattern sequence |
|
– TGPSI |
1 |
– TGPS status flag |
Activate |
– TGCFN |
(Current CFN + (256 – TTI/10msec))mod 256 |
– TGPSI |
2 |
– TGPS status flag |
Deactivate |
– TGCFN |
Not present |
MEASUREMENT REPORT, if the UE requires compressed mode (refer ICS/IXIT) (Step 1d)
Information Element |
Value/remark |
Measurement identity |
Check to see if set to 15 |
Measured Results |
|
– CHOICE measurement |
Check to see if set to "Inter-RAT measured results list" |
– Inter-RAT measured result list |
|
– CHOICE system |
GSM |
– Measured GSM cells |
|
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Check to see if present |
– Observed time difference to GSM cell |
Check that not present |
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Non verified BSIC |
– BCCH ARFCN |
Check that is set to the correct value according to the GSM band under test (see 3GPP 34.123-1 table 6.5 for details on the ARFCN) |
– Observed time difference to GSM cell |
Check that not present |
Measured results on RACH |
Check that not present |
Additional Measured results |
Check that not present |
Event results |
Check that not present |
MEASUREMENT REPORT, if the UE doesn’t requires compressed mode (refer ICS/IXIT) (Step 1d)
Information Element |
Value/remark |
Measurement identity |
Check to see if set to 15 |
Measured Results |
|
– CHOICE measurement |
Check to see if set to "Inter-RAT measured results list" |
– Inter-RAT measured result list |
|
– CHOICE system |
GSM |
– Measured GSM cells |
|
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
verified BSIC |
– Inter-RAT cell id |
Check that is set to 0 |
– Observed time difference to GSM cell |
Check that not present |
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Non verified BSIC |
– BCCH ARFCN |
Check that is set to the correct value according to the GSM band under test (see 3GPP 34.123-1 table 6.5 for details on the ARFCN) |
– Observed time difference to GSM cell |
Check that not present |
Measured results on RACH |
Check that not present |
Additional Measured results |
Check that not present |
Event results |
Check that not present |
MEASUREMENT REPORT (1.28Mcps TDD) (Step 1d)
Information Element |
Value/remark |
Measurement identity |
Check to see if set to 15 |
Measured Results |
|
– CHOICE measurement |
Check to see if set to "Inter-RAT measured results list" |
– Inter-RAT measured result list |
|
– CHOICE system |
GSM |
– Measured GSM cells |
|
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Check to see if present |
– Observed time difference to GSM cell |
Check that not present |
– GSM carrier RSSI |
Check to see if present |
CHOICE BSIC |
Non verified BSIC |
– BCCH ARFCN |
Check that is set to the correct value according to the GSM band under test (see 3GPP 34.123-1 table 6.5 for details on the ARFCN) |
– Observed time difference to GSM cell |
Check that not present |
Measured results on RACH |
Check that not present |
Additional Measured results |
Check that not present |
Event results |
Check that not present |
HANDOVER FROM UTRAN COMMAND-GSM
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Arbitrarily selects one integer between 0 to 3 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
Activation time |
now |
RAB Info |
|
– RAB identity |
0000 0001B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
– CN domain identity |
CS domain |
– NAS Synchronization Indicator |
Not present |
– Re-establishment timer |
Use T314 |
Inter-system message |
|
– CHOICE System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted and coded according to GSM specifications as Variable Length BIT STRING without Length Indicator. The first/ leftmost/ most significant bit of the bit string contains bit 8 of the first octet of the GSM message. The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 3 |
8.3.7.14.5 Test requirement
At step 1b the SS receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message indicating the successful download of the compressed mode parameters.
At step 1d the SS receives a MEASUREMENT REPORT message containing the measured results of the GSM cell.
At step 5 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has switched to the GSM cell.
At step 12 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
At step 15 SS receives ROUTING AREA UPDATE REQUEST message.
After step 18, SS should either receive DEACTIVATE PDP CONTEXT REQUEST message with cause as “QoS not accepted” or receive a MODIFY PDP CONTEXT ACCEPT message from UE.
8.3.7.15 Inter system handover from UTRAN/To GSM/Speech/Failure(stop of HS-DSCH reception)
8.3.7.15.1 Definition
8.3.7.15.2 Conformance requirement
If the UE does not succeed in establishing the connection to the target radio access technology, it shall:
1> revert back to the UTRA configuration;
NOTE: If configured for HS-DSCH while in UTRA, the UE will have still stored the IEs "Added or Reconfigured MAC-d flow" and "RB mapping Info".
…
1> transmit the HANDOVER FROM UTRAN FAILURE message setting the information elements as specified below:
2> include the IE "RRC transaction identifier"; and
2> set it to the value of "RRC transaction identifier" in the entry for the HANDOVER FROM UTRAN COMMAND message in the table "Accepted transactions" in the variable TRANSACTIONS; and
2> clear that entry;
2> set the IE "Inter-RAT handover failure" to "physical channel failure".
1> When the HANDOVER FROM UTRAN FAILURE message has been submitted to lower layer for transmission:
2> the procedure ends.
Reference(s)
TS 25.331 Clause 8.3.7.5.
8.3.7.15.3 Test purpose
To test that the UE reactivates the old configuration and uses this to transmit a HANDOVER FROM UTRAN FAILURE message to the network including IE "Inter-RAT Handover failure cause" which is set to "physical channel failure", when it receives an HANDOVER FROM UTRAN COMMAND and the connection to GSM for handover can not be established.
To verify that UE stops using the HS-PDSCH configuration after receiving the HANDOVER FROM UTRAN COMMAND.
8.3.7.15.4 Method of test
Initial conditions
System Simulator : 2 cells – Cell 1 is UTRAN, Cell 9 is GSM. GSM 51.010 clause 26.6.5.1 shall be referenced for the default parameters of cell 9.
UE: Idle state (state 2 or state 7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Related ICS/IXIT statement(s)
- UE supports both GSM and UTRAN Radio Access Technologies,
- UE supports both CS and PS
Foreseen final state of the UE
The UE is in CC state U10 on cell 1.
Test Procedure
The SS starts the UTRAN cell and brings the UE into call active state (CC state U10) with AMR with configuration [conversational/speech/uplink:12.2 DL:12.2 kbps/CS RAB + interactive/ background UL: 32kbps, DL 🙁 max bit rate depending on UE category) PS RAB + uplink:3.4 DL3.4 kbps SRBs]. PS RAB is configured with HS-DSCH. SS activates a dedicated GSM traffic channel then sends HANDOVER FROM UTRAN COMMAND indicating a dedicated channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. When the UE does not succeed in establishing the connection to the target radio access technology it shall revert back to UTRA configuration establish the UTRA physical channel(s) used at the time for reception of HANDOVER FROM UTRAN COMMAND transmit the HANDOVER FROM UTRAN FAILURE.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
UE |
The SS brings the UE into UTRAN U10 state and PS RAB with HS-DSCH active in cell 1. |
||
2 |
SS |
The SS configures a traffic channel on cell 9 (GSM cell). |
||
3 |
|
HANDOVER FROM UTRAN COMMAND-GSM |
Send on cell 1 (UTRAN cell) and the message indicates: The target channel for GSM FR in GSM Cell. |
|
4 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
5 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
6 |
|
HANDOVER ACCESS |
||
7 |
SS |
The target GSM Traffic Channel is Switched off |
||
8 |
|
HANDOVER FROM UTRAN FAILURE |
The SS receives the message via the old UTRAN configuration. The cause in the IE "inter-RAT change failure" is set to "physical channel failure" |
Specific message contents
HANDOVER FROM UTRAN COMMAND-GSM
The contents of this message is identical to the HANDOVER FROM UTRAN COMMAND-GSM message specified in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Inter-system message |
|
– System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
Single GSM message |
– Message |
GSM HANDOVER COMMAND formatted as BIT STRING (1..512). The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate or half rate version 1 |
HANDOVER FROM UTRAN FAILURE
The contents of this message is identical to the HANDOVER FROM UTRAN FAILURE message specified in [9] TS 34.108 clause 9.
8.3.7.15.5 Test requirement
After step 4 the SS shall receive HANDOVER FROM UTRAN FAILURE message using the old UTRA configuration. UE shall not resume HS-DSCH reception
8.3.7.16 Inter system handover from UTRAN/To GSM/Simultaneous CS and PS domain services/Success/TBF Establishment Success
8.3.7.16.1 Definition
8.3.7.16.2 Conformance requirement
The purpose of the inter-RAT handover procedure is to, under the control of the network, transfer a connection between the UE and UTRAN to another radio access technology (e.g. GSM). This procedure may be used in CELL_DCH state. This procedure may be used when no RABs are established or when the established RABs are only in the CS domain or when the established RABs are in both CS and PS domains
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
…
For a UE in CELL_DCH state using both CS and PS Domain services the Inter-RAT handover procedure is based on measurement reports from the UE but initiated from UTRAN.
The UE performs the Inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. When the UE has sent handover complete message to GSM / BSS the UE initiates a temporary block flow towards GPRS and sends a RA update request.
If the Inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode was successful the handover is considered as successful regardless if the UE was able to establish a temporary block flow or not towards GPRS.
In case of Inter-RAT handover failure the UE has the possibility to go back to UTRA RRC Connected Mode and re-establish the connection in the state it originated from
Reference(s)
TS 25.331 Clause 8.3.7, B.6.1
8.3.7.16.3 Test purpose
To test that in UTRAN cell when UE is in speech call active state and PS data call is established, UE performs handover to GSM RAT(cell not supporting DTM) after receiving HANDOVER FROM UTRAN COMMAND.
8.3.7.16.4 Method of test
Initial conditions
System Simulator: 2 cells – Cell 1 is UTRAN, Cell 9 is GPRS with BCCH. 51.010 clause 40.1.1 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9
Parameter |
Unit |
Cell 9 (GSM) |
Qsearch_I (TDD) |
dBm |
15 (never) |
UE: Registered Idle Mode on CS/PS (state 7) as specified in clause 7.4 of TS 34.108
Related ICS/IXIT statements
– UE supports both GSM and UTRAN Radio Access Technologies,
- UE supports UTRAN Conversational /Speech UL: 12.2kbps DL: 12.2 kbps /CS RAB+ Interactive or Background UL: 64kbps DL: 64kbps /PS RAB + uplink: 3.4 DL: 3.4 kbps SRBs
- UE supports UE operation mode A: PS and CS simultaneously
- UE supports GPRS operation mode class B
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810
Foreseen final state of the UE
UE is in packet Idle mode on cell 9
Test Procedure
The SS brings the UE into call active state (CC state U10) with conversational/speech /uplink: 12.2 DL: 12.2 kbps/CS RAB + UL: 3.4 DL: 3.4 kbps SRBs. During call active state, SS configures PS RAB with Interactive or Background/UL: 64 kbps DL: 64 kbps configuration. The SS configures an appropriate traffic channel on the GSM cell. SS sends a HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell. SS receives GPRS SUSPENSION REQUEST from the UE.
SS disconnects the CS call and releases the RR connection.
Once RR connection is released, an RAU procedure is performed. To check that PDP context is active, SS sends MODIFY PDP CONTEXT REQUEST and assigns new QoS in GPRS cell. The UE may or may not accept the new QoS and replies to the SS accordingly.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
The SS brings the UE into UTRAN U10 state in cell 1 with configuration: Conversational/Speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + uplink: 3.4 DL: 3.4 kbps SRBs |
||
2 |
|
SS executes Procedure P19 (clause 7.4.2.8.1.2) specified in TS 34.108 |
Session Setup is initiated from UE side. PS RAB configuration is Interactive/Background UL: 64 kbps DL: 64 kbps/PS RAB + UL: 3.4kbps DL: 3.4kbps SRBs |
|
3 |
SS |
The SS configures a traffic channel on cell 9 for GSM FR |
||
4 |
|
HANDOVER FROM UTRAN COMMAND |
Send on cell 1 (UTRAN cell) and the message indicates: the target channel for GSM |
|
5 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
6 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
HANDOVER ACCESS |
||
10 |
|
PHYSICAL INFORMATION |
||
11 |
|
SABM |
||
12 |
|
UA |
||
13 |
|
HANDOVER COMPLETE |
The SS receives the message on the traffic channel of GSM cell. |
|
14 |
|
GPRS SUSPENSION REQUEST |
UE sends GPRS SUSPENSION REQUEST on FACCH. Suspension cause value is not checked |
|
15 |
|
CHANNEL RELEASE |
SS disconnects the CS call and releases the RR connection. The GPRS Resumption IE is included and is set to “resumption of GPRS services successfully acknowledged.” |
|
15a |
|
CHANNEL REQUEST |
The SS receives this burst on the RACH of cell 9(GSM cell). |
|
15b |
|
IMMEDIATE ASSIGNMENT |
Sent on AGCH. |
|
16 |
|
ROUTING AREA UPDATE REQUEST |
GMM “update type” = ‘combined RA/LA updating’ |
|
17 |
|
ROUTING AREA UPDATE ACCEPT |
GMM. P-TMSI is included |
|
18 |
|
ROUTING AREA UPDATE COMPLETE |
||
19 |
|
MODIFY PDP CONTEXT REQUEST |
SS requests the modification of a PDP context, with a new QoS ( peak throughput is changed to ‘0011’) |
|
A20 |
|
MODIFY PDP CONTEXT ACCEPT |
UE behaviour type A: Accept the PDP context modification |
|
B20 |
|
DEACTIVATE PDP CONTEXT REQUEST |
UE behaviour type B: Initiate the PDP context deactivation. Cause set to ‘QoS not accepted’ |
|
B20a |
|
DEACTIVATE PDP CONTEXT ACCEPT |
UE behaviour type B: Accept the PDP context deactivation. |
|
B20b |
|
DETACH REQUEST |
UE behaviour type B: A non-auto attach UE may (optionally) send a Detach Request. The SS shall wait up to ‘T3390’ seconds for the Detach Request. |
|
B20c |
|
DETACH ACCEPT |
If the UE transmitted a Detach Request message in step B20b then the SS responds with a Detach Accept message. |
Specific message contents
HANDOVER FROM UTRAN COMMAND (step 4)
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Arbitrarily selects one integer between 0 to 3 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
Activation time |
Now |
RAB Info |
|
– RAB identity |
0000 0001B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
– CN domain identity |
CS domain |
– NAS Synchronization Indicator |
Not present |
– Re-establishment timer |
Use T314 |
Inter-system message |
|
– CHOICE System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
GSM message List |
– Message |
GSM HANDOVER COMMAND formatted and coded according to GSM specifications as BIT STRING (1..512). The first/ leftmost/ most significant bit of the bit string contains bit 8 of the first octet of the GSM message. The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND for M = 2 in clause 26.6.5.1 of GSM 51.010, except that the CHANNEL MODE IE is included with value = speech full rate |
8.3.7.16.5 Test requirements
At step 6 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has switched to the GSM cell.
At step 13 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
At step 16 SS receives ROUTING AREA UPDATE REQUEST message.
After step 19, SS should either receive DEACTIVATE PDP CONTEXT REQUEST message with cause as “QoS not accepted” or receive a MODIFY PDP CONTEXT ACCEPT message from UE.
8.3.7.17 Inter system handover from UTRAN/To GSM/DTM Support/Simultaneous CS and PS domain services/Success
8.3.7.17.1 Definition
8.3.7.17.2 Conformance requirement
The purpose of the inter-RAT handover procedure is to, under the control of the network, transfer a connection between the UE and UTRAN to another radio access technology (e.g. GSM). This procedure may be used in CELL_DCH state. This procedure may be used when no RABs are established or when the established RABs are only in the CS domain or when the established RABs are in both CS and PS domains
The UE shall be able to receive a HANDOVER FROM UTRAN COMMAND message and perform an inter-RAT handover, even if no prior UE measurements have been performed on the target cell.
…
For a UE in CELL_DCH state using both CS and PS Domain services the Inter-RAT handover procedure is based on measurement reports from the UE but initiated from UTRAN.
The UE performs the Inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. When the UE has sent handover complete message to GSM / BSS the UE initiates a temporary block flow towards GPRS and sends a RA update request.
If the Inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode was successful the handover is considered as successful regardless if the UE was able to establish a temporary block flow or not towards GPRS.
In case of Inter-RAT handover failure the UE has the possibility to go back to UTRA RRC Connected Mode and re-establish the connection in the state it originated from
…
The establishment of a packet resource is supported by procedures on the main DCCH when the mobile station is in dedicated mode. The procedures are only applicable to a mobile station supporting DTM with GPRS or EGPRS. The procedures are optional for the network.
These procedures constitute a complement to the corresponding procedures for temporary block flow establishment using CCCH or PCCCH while in idle mode defined in 3GPP TS 04.18 and 3GPP TS 04.60, respectively
…
While in dedicated mode, upper layers in the mobile station or in the network may request the transport of GPRS information transparently over the radio interface. This procedure is only applicable when:
– the information from upper layers is signalling information; and
– the GTTP length of the message is below the maximum indicated by the network.
In any other case, the RR procedures related to packet resource establishment while in dedicated mode apply.
The information from upper layers shall be carried inside the GTTP Information message. The GTTP Information message contains:
– the TLLI of the MS; and
– the LLC PDU.
The GTTP messages are sent using "normal" priority at the data link layer. Reference(s)
TS 25.331 Clause 8.3.7, B.6.1, TS 04.18 Clause 3.4.26
8.3.7.17.3 Test purpose
To verify that in UTRAN cell when UE (supporting DTM) is in speech call active state and PS data call is established, UE performs handover to GSM RAT after receiving HANDOVER FROM UTRAN COMMAND.
8.3.7.17.4 Method of test
Initial conditions
System Simulator: 2 cells – Cell 1 is UTRAN, Cell 9 is GPRS with BCCH. 51.010 clause 40.1.1 shall be referenced for the default parameters, and clause 26.6.5.1 shall be referenced for cell allocation of cell 9
DTM support is indicated in SI6 for cell 9. MAX_LAPDm is set to 111.
UE: Registered Idle Mode on CS/PS (state 7) as specified in clause 7.4 of TS 34.108
Related ICS/IXIT statements
– UE supports both GSM and UTRAN Radio Access Technologies,
- UE supports UTRAN Conversational /Speech UL: 12.2kbps DL: 12.2 kbps /CS RAB+ Interactive or Background UL: 64kbps DL: 64kbps /PS RAB + uplink: 3.4 DL: 3.4 kbps SRBs
- UE supports UE operation mode A: PS and CS simultaneously
- UE supports DTM
– UE supports GSM-P, GSM-E, GSM-DCS, GSM-450, GSM-480, GSM-PCS, GSM-850, GSM-710, GSM 750, T_GSM-810
Foreseen final state of the UE
UE is in CC state U10 and packet Idle mode on cell 9
Test Procedure
The SS brings the UE into call active state (CC state U10) with conversational/speech /uplink: 12.2 DL: 12.2 kbps/CS RAB + UL: 3.4 DL: 3.4 kbps SRBs. During call active state, SS configures PS RAB with Interactive or Background/UL: 64 kbps DL: 64 kbps configuration. The SS configures an appropriate traffic channel on the GSM cell. SS sends a HANDOVER FROM UTRAN COMMAND indicating the traffic channel of the target GSM cell to the UE through DCCH of the serving UTRAN cell. After the UE receives the command it shall configure itself accordingly and switch to the new channel of the GSM cell. The SS checks whether the handover is performed by checking that the UE transmits the HANDOVER COMPLETE message to the SS in GSM cell. The RAU procedure is performed.
To check that PDP context is active, SS sends MODIFY PDP CONTEXT REQUEST and assigns new QoS in GPRS cell. The UE may or may not accept the new QoS and replies to the SS accordingly.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
The SS brings the UE into UTRAN U10 state in cell 1 with configuration: Conversational/Speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + uplink: 3.4 DL: 3.4 kbps SRBs |
||
2 |
|
SS executes Procedure P19 (clause 7.4.2.8.1.2) specified in TS 34.108 |
Session Setup is initiated from UE side. PS RAB configuration is Interactive/Background UL: 64 kbps DL: 64 kbps/PS RAB + UL: 3.4kbps DL: 3.4kbps SRBs |
|
3 |
|
SS |
The SS configures a traffic channel on cell 9 for GSM FR |
|
4 |
|
HANDOVER FROM UTRAN COMMAND |
Send on cell 1 (UTRAN cell) and the message indicates: the target channel for GSM |
|
5 |
UE |
The UE accepts the handover command and switches to the GSM traffic channel specified in the HANDOVER FROM UTRAN COMMAND-GSM |
||
6 |
|
HANDOVER ACCESS |
The SS receives this burst on the traffic channel of cell 9 (GSM cell) It implies that the UE has switched to GSM cell. |
|
7 |
|
HANDOVER ACCESS |
||
8 |
|
HANDOVER ACCESS |
||
9 |
|
HANDOVER ACCESS |
||
10 |
|
PHYSICAL INFORMATION |
||
11 |
|
SABM |
||
12 |
|
UA |
||
13 |
|
HANDOVER COMPLETE |
The SS receives the message on the traffic channel of GSM cell. |
|
14 |
|
DTM INFORMATION |
MAX_LAPDm set to 111. |
|
15 |
|
GPRS INFORMATION |
Contains the ROUTING AREA UPDATE REQUEST message. |
|
16 |
|
GPRS INFORMATION |
Contains the ROUTING AREA UPDATE ACCEPT message, reallocating the UEs P-TMSI to C2345678Hex. |
|
17 |
|
GPRS INFORMATION |
Contains the ROUTING AREA UPDATE COMPLETE message. |
|
18 |
|
GPRS INFORMATION |
Contains the MODIFY PDP CONTEXT REQUEST to request the modification of a PDP context, with a new QoS ( peak throughput is changed to ‘0011’) |
|
A19 |
|
GPRS INFORMATION |
Contains the MODIFY PDP CONTEXT ACCEPT to accept the PDP Context modification. |
|
B19 |
|
GPRS INFORMATION |
Contains the DEACTIVATE PDP CONTEXT REQUEST. Cause set to ‘QoS not accepted’ |
|
B20 |
|
GPRS INFORMATION |
Contains the DEACTIVATE PDP CONTEXT ACCEPT to accept the PDP context deactivation. |
|
Steps B21-B22 are optional |
||||
B21 (Optional) |
|
GPRS INFORMATION |
Contains the DETACH REQUEST. This is sent optionally by a non-auto attach UE. behaviour type B: The SS shall wait up to ‘T3390’ seconds for the DETACH REQUEST. |
|
B22 (Optional) |
|
GPRS INFORMATION |
Contains the DETACH ACCEPT. |
NOTE: The UE follows either branch A or B after step 18
Specific message contents
HANDOVER FROM UTRAN COMMAND (step 4)
Information Element |
Value/remark |
Message Type |
|
RRC transaction identifier |
Arbitrarily selects one integer between 0 to 3 |
Integrity check info |
|
– Message authentication code |
SS calculates the value of MAC-I for this message and writes to this IE. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I. |
– RRC Message sequence number |
SS provides the value of this IE, from its internal counter. |
Activation time |
Now |
RAB Info |
|
– RAB identity |
0000 0001B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
– CN domain identity |
CS domain |
– NAS Synchronization Indicator |
Not present |
– Re-establishment timer |
Use T314 |
Inter-system message |
|
– CHOICE System type |
GSM |
– Frequency Band |
Set to "GSM/ PCS 1900" if GSM/ PCS 1900 is used in this test. Otherwise set to "GSM/DCS 1800 Band" |
– CHOICE GSM message |
GSM message List |
– Message |
GSM HANDOVER COMMAND formatted and coded according to GSM specifications as BIT STRING (1..512). The first/ leftmost/ most significant bit of the bit string contains bit 8 of the first octet of the GSM message. The contents of the HANDOVER COMMAND see next table. |
HANDOVER COMMAND
Same as the HANDOVER COMMAND in clause 26.6.5.1 of TS 3GPP 51.010-1. |
8.3.7.17.5 Test requirements
At step 6 the SS receives a handover access burst on the traffic channel of the GSM cell indicating that the UE has switched to the GSM cell.
At step 13 the SS receives a HANDOVER COMPLETE message indicating a successful handover to the GSM cell.
At step 15 SS receives ROUTING AREA UPDATE REQUEST message.
After step 18, SS should either receive DEACTIVATE PDP CONTEXT REQUEST message with cause as “QoS not accepted” or receive a MODIFY PDP CONTEXT ACCEPT message from UE