8.1.3 RRC Connection Release
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
8.1.3.1 RRC Connection Release in CELL_DCH state: Success
8.1.3.1.1 Definition
8.1.3.1.2 Conformance requirement
1. The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH. Furthermore this procedure can interrupt any ongoing procedures with the UE in the above listed states.
When the UE receives the first RRC CONNECTION RELEASE message, it shall:
…
– in state CELL_DCH:
– initialise the counter V308 to zero;
…
– submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using UM RLC on the DCCH to the UTRAN;
…
– start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio interface.
2. When in state CELL_DCH and the timer T308 expires, the UE shall:
– increment V308 by one;
– if V308 is equal to or smaller than N308:
– retransmit the RRC CONNECTION RELEASE COMPLETE message, without incrementing "Uplink RRC Message sequence number" for signalling radio bearer RB1 in the variable INTEGRITY_PROTECTION_INFO;
– if V308 is greater than N308:
– release all its radio resources;
…
– enter idle mode;
– perform the actions specified in TS 25.331 clause 8.5.2 when entering idle mode;
– and the procedure ends.
Reference
3GPP TS 25.331 clause 8.1.4.3, 8.1.4.6
8.1.3.1.3 Test purpose
To verify:
1. that the UE when receiving an RRC CONNECTION RELEASE message transmits N308+1 RRC CONNECTION RELEASE COMPLETE messages before release of radio resources and entering into idle mode
2. that the time between UE transmissions of the RRC CONNECTION RELEASE COMPLETE message is equal to the value of the T308 timer.
8.1.3.1.4 Method of test
Initial Condition
System Simulator: 1 cell
UE: CELL_DCH state (state 6-1 or state 6-3) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE
Test Procedure
The UE is brought to the CELL_DCH state by prompting the operator to initiate an outgoing call. After the DCCH is established, on reception of (CM) service request message from the UE, the SS will Send CM Service Reject message (for state 6-1) or Service Reject message (for state 6-3) to complete the (CM) service Request procedure. After the UE is brought into the stable state, SS transmits an RRC CONNECTION RELEASE message to the UE to disconnect the connection. SS then waits for the UE to transmit an RRC CONNECTION RELEASE COMPLETE message using unacknowledged mode. SS checks to see if UE re-transmit this message at each expiry of T308 timer and if N308+1 RRC CONNECTION RELEASE COMPLETE message have been received. SS calls for generic procedure C.1 to check that UE is in Idle Mode state.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The UE is in the CELL_DCH state after a successful RRC connection establishment by virtue of the operator making an outgoing call. |
|||
|
2 |
|
RRC CONNECTION RELEASE |
SS disconnect the connection established. The value in IE "N308" is arbitrarily chosen from 1 to 8. |
|
|
3 |
|
RRC CONNECTION RELEASE COMPLETE |
SS waits for the arrival of N308 + 1 such message with an interval time of T308, using unacknowledged mode. |
|
|
4 |
SS verifies that the UE release its L2 signalling radio bearer and dedicated resources and enters idle mode. |
|||
|
5 |
|
CALL C.1 |
If the test result of C.1 indicates that UE is in Idle Mode state, the test passes, otherwise it fails. |
|
Specific Message Content
RRC CONNECTION RELEASE (Step 2)
Use the same message type found in clause 9 of TS 34.108, with the following exceptions:
|
Information Element |
Value/remark |
|
N308 |
Arbitrarily chosen between 1 and 8 |
8.1.3.1.5 Test requirement
After step 2 the UE shall transmit N308 + 1 RRC CONNECTION RELEASE COMPLETE messages. The time between the transmissions shall be equal to the T308 timer value.
After step 3 the UE shall initiate the release of the L2 signalling radio bearer and dedicated resources and enter idle mode.
8.1.3.2 RRC Connection Release using on DCCH in CELL_FACH state: Success
8.1.3.2.1 Definition
8.1.3.2.2 Conformance requirement
The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH. Furthermore this procedure can interrupt any ongoing procedures with the UE in the above listed states.
When the UE receives the first RRC CONNECTION RELEASE message; and
1> if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable U_RNTI; or
1> if the message is received on DCCH:
the UE shall:
…
1> in state CELL_FACH:
2> if the RRC CONNECTION RELEASE message was received on the DCCH:
3> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Accepted transactions" in the variable TRANSACTIONS;
3> submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using AM RLC on the DCCH to the UTRAN.
3> when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been confirmed by the lower layers:
4> release all its radio resources; and
4> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers; and
4> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS;
4> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
4> clear the variable ESTABLISHED_RABS;
4> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to upper layers;
4> enter idle mode;
4> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode.
3> and the procedure ends.
…
Reference
3GPP TS 25.331 clause 8.1.4.3.
8.1.3.2.3 Test purpose
To confirm that the UE releases the L2 signalling radio bearer and resources and goes back to the idle state after it receives an RRC CONNECTION RELEASE message on downlink DCCH from the SS. It shall transmit an RRC CONNECTON RELEASE COMPLETE message using acknowledged mode on uplink DCCH to the SS.
8.1.3.2.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: CELL_FACH state (state 6-2 or state 6-4) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Test Procedure
The UE is brought to an initial state of CELL_FACH. After the successful establishment of the RRC connection, on reception of (CM) service request message from the UE, the SS will send CM Service Reject message (for state 6-2) or Service Reject message (for state 6-4) to complete the (CM) service Request procedure. After the UE is brought into the stable state, the SS transmits an RRC CONNECTION RELEASE message to the UE to disconnect the radio link. When the UE receives this message the UE transmits an RRC CONNECTION RELEASE COMPLETE message using acknowledged mode to the SS. Finally, SS checks that the UE performs proper release of all radio resources and then goes back to idle mode.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The UE is brought to the CELL_FACH state. |
|||
|
2 |
|
RRC CONNECTION RELEASE |
SS sends this message using unacknowledged mode RLC operations on the uplink DCCH. |
|
|
3 |
|
RRC CONNECTION RELEASE COMPLETE |
The UE transmits this message using acknowledged mode. |
|
|
4 |
The UE releases L2 signalling radio bearer and radio resources. Then the UE goes to idle mode. |
|||
Specific Message Contents
None.
8.1.3.2.5 Test requirement
After step 2 the UE shall transmit an RRC CONNECTION RELEASE COMPLETE message using acknowledged mode then it shall receive a response for this message from the SS-RLC.
After step 3 the UE shall release its L2 signalling radio bearers and radio resources, and then it shall go back to idle mode.
8.1.3.3 RRC Connection Release using on CCCH in CELL_FACH state: Success
8.1.3.3.1 Definition
8.1.3.3.2 Conformance requirement
The UE shall receive and act on an RRC CONNECTION RELEASE message in states CELL_DCH and CELL_FACH. Furthermore this procedure can interrupt any ongoing procedures with the UE in the above listed states.
When the UE receives the first RRC CONNECTION RELEASE message; and
1> if the message is received on the CCCH, and IE "U-RNTI" is present and has the same value as the variable U_RNTI; or
1> if the message is received on DCCH:
the UE shall:
…
1> in state CELL_FACH:
…
2> if the RRC CONNECTION RELEASE message was received on the CCCH:
3> release all its radio resources;
3> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to the upper layers;
3> clear any entry for the RRC CONNECTION RELEASE message in the tables "Accepted transactions" and "Rejected transactions" in the variable TRANSACTIONS;
3> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
3> clear the variable ESTABLISHED_RABS;
3> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to upper layers;
3> enter idle mode;
3> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode;
3> and the procedure ends.
Reference
3GPP TS 25.331 clause 8.1.4.3.
8.1.3.3.3 Test purpose
To confirm that the UE releases all its radio resources upon the reception of a RRC CONNECTION RELEASE message on the downlink CCCH, without transmitting RRC CONNECTION RELEASE COMPLETE message on the uplink.
8.1.3.3.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: CELL_FACH state (state 6-2 or state 6-4) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Test Procedure
The UE is brought to an initial state of CELL_FACH. After the successful establishment of the RRC connection, on reception of (CM) service request message from the UE, the SS will send CM Service Reject message (for state 6-2) or Service Reject message (for state 6-4) to complete the (CM) service Request procedure. After the UE is brought into the stable state, the SS transmits an RRC CONNECTION RELEASE message on the downlink CCCH. The UE shall terminate the RRC connection and release all radio resources allocated to it. SS monitors the uplink DCCH and CCCH to verify that no transmission is detected. SS calls for generic procedure C.1 to check that UE is in Idle Mode state.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The UE is brought to the CELL_FACH state. |
|||
|
2 |
|
RRC CONNECTION RELEASE |
SS transmits this message with the contents identical to that found in TS 34.108 clause 9 on downlink CCCH. |
|
|
3 |
SS waits for a period equivalent to 60 seconds. The UE shall not send any response message on uplink direction during this period. It shall release the radio resources allocated and return to idle mode. |
|||
|
4 |
|
CALL C.1 |
If the test result of C.1 indicates that UE is in Idle Mode state, the test passes, otherwise it fails. |
|
Specific Message Contents
None.
8.1.3.3.5 Test requirement
After step 2 the UE shall release all its radio resources, return to idle mode, without transmitting RRC CONNECTION RELEASE COMPLETE message on the uplink direction.
8.1.3.4 RRC Connection Release in CELL_FACH state: Failure
8.1.3.4.1 Definition
8.1.3.4.2 Conformance requirement
When acknowledged mode was used and RLC does not succeed in transmitting the RRC CONNECTION RELEASE COMPLETE message, the UE shall:
1> release all its radio resources;
1> indicate the release of the established signalling connections (as stored in the variable ESTABLISHED_SIGNALLING_CONNECTIONS) and established radio access bearers (as stored in the variable ESTABLISHED_RABS) to upper layers;
1> clear the variable ESTABLISHED_SIGNALLING_CONNECTIONS;
1> clear the variable ESTABLISHED_RABS;
1> enter idle mode;
1> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode;
1> and the procedure ends.
Reference
3GPP TS 25.331 clause 8.1.4.9.
8.1.3.4.3 Test purpose
To confirm that the UE releases all its radio resources and enters idle mode when the UE does not succeed in transmitting the RRC CONNECTION RELEASE COMPLETE message using acknowledged mode to the SS (i.e. the UE-RLC does not receive an acknowledgement for the transmission of the RRC CONNECTION RELEASE COMPLETE message from SS).
8.1.3.4.4 Method of test
Initial Condition
System Simulator: 1 cell
UE: CELL_FACH state (state 6-2 or state 6-4) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE
Test Procedure
At the start of the test, the UE is brought to CELL_FACH state. When the RRC connection has been established, on reception of (CM) service request message from the UE, the SS will send CM Service Reject message (for state 6-2) or Service Reject message (for state 6-4) to complete the (CM) service Request procedure. After the UE is brought into the stable state, the SS transmits an RRC CONNECTION RELEASE message to the UE to disconnect the radio link. When the UE receives this message the UE transmits an RRC CONNECTION RELEASE COMPLETE message using acknowledged mode to the SS. The SS ignores the message and does not transmit an RLC STATUS PDU to acknowledge this message. SS checks to see that UE continues to release all its radio resources and then enters idle mode.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The UE is brought into CELL_FACH state by asking the operator to perform an outgoing call attempt. |
|||
|
2 |
|
RRC CONNECTION RELEASE |
SS ask to disconnect the radio link |
|
|
3 |
|
RRC CONNECTION RELEASE COMPLETE |
The UE transmits this message using acknowledged mode. The SS shall not transmit an RLC STATUS PDU to acknowledge this message. |
|
|
4 |
SS checks to make sure that UE releases all its radio resources and enters idle mode. |
|||
|
5 |
|
CALL C.1 |
If the test result of C.1 indicates that UE is in Idle Mode state, the test passes, otherwise it fails. |
|
Specific Message Contents
None
8.1.3.4.5 Test requirement
After step 3 the UE shall release its L2 signalling radio bearers and radio resources then it shall go to idle mode.
8.1.3.5 RRC Connection Release in CELL_FACH state: Invalid message
8.1.3.5.1 Definition
8.1.3.5.2 Conformance requirement
If the RRC CONNECTION RELEASE message contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to TS 25.331 clause 9, and if the "protocol error cause" in PROTOCOL_ERROR_INFORMATION is set to any cause value except "ASN.1 violation or encoding error", the UE shall perform procedure specific error handling as follows:
The UE shall:
1> ignore any IE(s) causing the error but treat the rest of the RRC CONNECTION RELEASE message as normal according to TS 25.331 subclause 8.1.4.3, with an addition of the following actions:
2> if the RRC CONNECTION RELEASE message was received on the DCCH:
3> set the IE "RRC transaction identifier" in the RRC CONNECTION RELEASE COMPLETE message to the value of "RRC transaction identifier" in the entry for the RRC CONNECTION RELEASE message in the table "Rejected transactions" in the variable TRANSACTIONS;
3> include the IE "Error indication" in the RRC CONNECTION RELEASE COMPLETE message with:
4> the IE "Failure cause" set to the cause value "Protocol error"; and
4> the IE "Protocol error information" set to the value of the variable PROTOCOL_ERROR_INFORMATION.
…
If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, containing an undefined critical message extension, the UE shall:
1> set the variable PROTOCOL_ERROR_REJECT to TRUE;
1> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Message extension not comprehended";
1> if the IE "Message Type" of the received message is not present in the table "Rejected transactions" in the variable TRANSACTIONS:
2> store the IE "Message type" of the received message in the table "Rejected transactions" in the variable TRANSACTIONS; and
2> set the IE "RRC transaction identifier" to zero in that table entry.
1> perform procedure specific error handling according to TS 25.331 clause 8.
Reference
3GPP TS 25.331 clause 8.1.4 and 9.3b.
8.1.3.5.3 Test purpose
When the UE receives an invalid RRC CONNECTION RELEASE message on the downlink DCCH, it shall transmit an RRC CONNECTION RELEASE COMPLETE message that includes the appropriate error cause on the uplink DCCH.
8.1.3.5.4 Method of test
Initial Condition
System Simulator: 1 cell
UE: CELL_FACH state (state 6-2 or state 6-4) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE.
Test Procedure
The UE is initially in CELL FACH state. on reception of (CM) service request message from the UE, the SS will Send CM Service Reject message (for state 6-2) or Service Reject message (for state 6-4) to complete the (CM) service Request procedure. After the UE is brought into the stable state, the SS transmits an RRC CONNECTION RELEASE message containing an unexpected critical message extension on the DCCH to request the UE to disconnect the RRC connection. The UE shall transmit an RRC CONNECTION RELEASE COMPLETE message on the uplink DCCH, which includes the IE "Error indication". This IE shall contain the "Protocol error information" IE which in turn contains the IE “Protocol error cause” set to "Message extension not comprehended". Upon completion of the procedure, the SS calls for generic procedure C.1 to check that UE is in IDLE state.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
Void |
|||
|
2 |
Void |
|||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
Void |
|||
|
6 |
Void |
|||
|
7 |
Void |
|||
|
8 |
|
RRC CONNECTION RELEASE |
See specific message contents for this message |
|
|
9 |
|
RRC CONNECTION RELEASE COMPLETE |
See specific message contents for this message This message is sent using acknowledged mode. |
|
|
10 |
Void |
|||
|
11 |
Void |
|||
|
12 |
Void |
|||
|
13 |
ßà |
CALL C.1 |
If the test result of C.1 indicates that UE is in IDLE state, the test passes, otherwise it fails. |
|
Specific Message Contents
RRC CONNECTION RELEASE (Step 8)
This message must be recognised by the UE as an RRC CONNECTION RELEASE message. However, it shall be constructed (see TS 25.331 clause 10.1.1) such that the UE will detect critical extensions not defined for the protocol release supported by the UE:
|
Information Element |
Value/remark |
|
Message Type |
|
|
RRC transaction identifier |
Arbitrarily selects an integer between 0 and 3 |
|
Integrity check info |
Not present |
|
Critical extensions |
’FF’H |
RRC CONNECTION RELEASE COMPLETE (Step 9)
Check to see if the same message type found in clause 9 of TS 34.108 is received, with the following exceptions:
|
Information Element |
Value/remark |
|
Error indication |
|
|
– Failure cause |
‘Protocol error’ |
|
– Protocol error information |
|
|
– CHOICE diagnostics type |
Protocol error cause |
|
– Protocol error cause |
Check to see if set to ‘Message extension not comprehended’ |
8.1.3.5.5 Test requirement
After step 8 the UE shall transmit an RRC CONNECTION RELEASE COMPLETE message which includes the appropriate cause values in IE "Protocol error information".
After step 12 the UE shall be in IDLE state.
8.1.3.6 RRC Connection Release in CELL_DCH state (Frequency modification): Success
8.1.3.6.1 Definition
8.1.3.6.2 Conformance requirement
If the UE first receives an RRC CONNECTION RELEASE message in CELL_DCH state, it shall:
– initialize the counter V308 to zero;
– submit an RRC CONNECTION RELEASE COMPLETE message to the lower layers for transmission using UM RLC on the DCCH to the UTRAN;
– start timer T308 when the RRC CONNECTION RELEASE COMPLETE message is sent on the radio interface.
If the timer T308 expires, the UE shall:
– increment V308 by one;
– if V308 is equal to or smaller than N308:
– retransmit the RRC CONNECTION RELEASE COMPLETE message;
– if V308 is greater than N308:
– release all its radio resources;
– enter idle mode;
– perform cell-selection according to TS 25.304;
– procedure end;
Reference
3GPP TS 25.331 clause 8.1.4.
8.1.3.6.3 Test purpose
To confirm that when the UE receives an RRC CONNECTION RELEASE message the UE transmits N308+1 RRC CONNECTION RELEASE COMPLETE messages using UM on DCCH.
To confirm that the UE enters into idle mode with performing cell-selection and selecting new cell configured by SS.
8.1.3.6.4 Method of test
Initial Condition
System Simulator: 2 cells–Cell 1 is active and cell 6 is inactive
UE: CS-DCCH+DTCH_DCH (state 6-9) or PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE
Specific Message Content
For system information block 11 for Cell 1 (gives IE’s which are different from defaults given in 34.108 sec 6.1) to be transmitted before idle update preamble.
System Information Block type 11
Use same message sub-clause 6.1 of TS 34.108, with following exception:
|
Information Element |
Value/remark |
|
– SIB12 indicator |
FALSE |
|
– Intra-frequency measurement system information |
Not Present |
|
– Inter-frequency measurement system information |
|
|
– Inter-frequency cell info list |
|
|
– New inter-frequency cell id |
|
|
– Inter frequency cell id |
6 |
|
– Frequency info |
|
|
– CHOICE mode |
FDD |
|
– UARFCN uplink(Nu) |
Not present Absence of this IE is equivalent to apply the default duplex distance defined for the operating frequency according to 25.101 |
|
– UARFCN downlink(Nd) |
Reference to table 6.1.2 of TS 34.108 for Cell 6 |
|
– Cell info |
|
|
– Cell individual offset |
Not Present |
|
– Reference time difference to cell |
Not present |
|
– Read SFN indicator |
FALSE |
|
– CHOICE mode |
FDD |
|
– Primary CPICH info |
|
|
– Primary scrambling code |
Refer to clause titled "Default settings for cell No.6 (FDD)" in clause 6.1.4 of TS 34.108 |
|
– Primary CPICH Tx power |
Not present |
|
– Cell Selection and Re-selection Info |
|
|
– Qoffset1s,n |
0dB |
|
– Qoffset2s,n |
Not present |
|
– Maximum allowed UL TX power |
Reference to table 6.1.1 |
|
– HCS neighbouring cell information |
Not present |
|
– CHOICE mode |
FDD |
|
– Qqualmin |
Reference to table 6.1.1 |
|
– Qrxlevmin |
Reference to table 6.1.1 |
|
– Cells for measurement |
Not present |
System Information Block type 11 (TDD)
Use same message sub-clause 6.1 of TS 34.108, with following exception:
|
Information Element |
Value/remark |
|
– SIB12 indicator |
FALSE |
|
– Intra-frequency measurement system information |
Not Present |
|
– Inter-frequency measurement system information |
|
|
– Inter-frequency cell info list |
|
|
– New inter-frequency cell id |
|
|
– Inter frequency cell id |
4 |
|
– Frequency info |
|
|
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Reference to TS 34.108 for Cell 4 |
|
– Cell info |
|
|
– Cell individual offset |
Not Present |
|
– Reference time difference to cell |
Not present |
|
– Read SFN indicator |
FALSE |
|
– CHOICE mode |
TDD |
|
– Primary CCPCH info |
Reference clause 6.1,TS 34.108,Default settings for cell 4 |
|
– Cell parameters ID |
Reference clause 6.1,TS 34.108,Default settings for cell 4 |
|
– Primary CPICH TX power |
Not present |
|
– Timeslot list |
Not present |
|
– Cell Selection and Re-selection Info |
Not present For neighbouring cell, if HCS is not used and all the parameters in cell selection and re-selection info are Default value, this IE is absent. |
|
– Qoffset1s,n |
0dB |
|
– Maximum allowed UL TX power |
Reference to table 6.1.6, TS 34.108 |
|
– HCS neighbouring cell information |
Not present |
|
– CHOICE mode |
TDD |
|
– Qrxlevmin |
Reference to table 6.1.6, TS 34.108 |
|
– Cells for measurement |
Not present |
Test Procedure
Table 8.1.3.6
|
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
|
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
|
CPICH Ec (FDD) |
dBm/3.84MHz |
-55 |
-55 |
Off |
-55 |
|
P-CCPCH RSCP (TDD) |
dBm |
-55 |
-55 |
Off |
-55 |
Table 8.1.3.6 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. SS switches the power settings between columns "T0" and "T1", whenever the description in multi-cell condition specifies a reverse in the transmission power settings for cell 1 and cell 6.
The UE is in CELL_DCH state of cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.1.3.6. The SS switches its downlink transmission power settings to columns "T1". The SS modify contents of SIB3 in cell 6. The SS transmits an RRC CONNECTION RELEASE message. After the SS transmits an RRC CONNECTION RELEASE message to the UE, the SS waits for the UE to transmit RRC CONNECTION RELEASE COMPLETE messages using UM on DCCH and checks to see if N308+1 such messages has been received. The UE leaves connected mode and enters idle mode in cell 1. The UE shall perform cell reselection and camp on cell 6 after reading the system information. The SS calls for generic procedure C.1 to check that UE is in Idle state.
NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The UE is in the CELL_DCH state of cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.1.3.6. |
|||
|
2 |
The SS switches its downlink transmission power settings to columns "T1" in table 8.1.3.6. |
|||
|
3 |
Void |
|||
|
4 |
Void |
|||
|
5 |
|
System Information Block type 3 |
The SS modifies SIB 3 in cell 1 to indicate that the cell is barred. |
|
|
6 |
The SS waits for 5 s. |
|||
|
7 |
|
RRC CONNECTION RELEASE |
||
|
8 |
|
RRC CONNECTION RELEASE COMPLETE |
The SS waits for the arrival of N308+1 such messages send on UM RLC. |
|
|
9 |
The UE releases signalling radio bearer and dedicated resources. Then the UE goes to idle mode in cell 1. |
|||
|
10 |
The UE select s cell 6 and camp on it. |
|||
|
11 |
The SS waits for 15 s after receiving the last RRC CONNECTION RELEASE COMPLETE message. |
|||
|
12 |
|
CALL C.1 |
If the test result of C.1 indicates that UE is in idle mode state, the test passes, otherwise it fails. |
|
Specific Message Content
System Information Block type 3 (Step 5)
Use the same message type found in clause 6.1 of TS 34.108, with the following exceptions:
|
Information Element |
Value/remark |
|
– Cell Access Restriction |
|
|
– Cell barred |
Barred |
|
– Intra-frequency cell re-selection indicator |
Not allowed |
|
– Tbarred |
10[s] |
|
– Cell Reserved for operator use |
Not reserved |
|
– Cell Reservation Extension |
Not reserved |
|
– Access Class Barred List |
|
|
– Access Class Barred0 |
barred |
|
– Access Class Barred1 |
barred |
|
– Access Class Barred2 |
barred |
|
– Access Class Barred3 |
barred |
|
– Access Class Barred4 |
barred |
|
– Access Class Barred5 |
barred |
|
– Access Class Barred6 |
barred |
|
– Access Class Barred7 |
barred |
|
– Access Class Barred10 |
barred |
|
– Access Class Barred11 |
barred |
|
– Access Class Barred12 |
barred |
|
– Access Class Barred13 |
barred |
|
– Access Class Barred14 |
barred |
|
– Access Class Barred15 |
barred |
RRC CONNECTION RELEASE (Step 6)
Use the same message type found in clause 9 of TS 34.108, with the following exceptions:
|
Information Element |
Value/remark |
|
N308 |
Arbitrarily chosen between 1 and 8 |
8.1.3.6.5 Test requirement
After step 6 the UE shall start to transmit N308 + 1 times RRC CONNECTION RELEASE COMPLETE messages using UM on DCCH.
After step 11 the UE shall be in Idle mode in cell 6.
8.1.3.7 RRC Connection Release in CELL_FACH state (Frequency modification): Success
8.1.3.7.1 Definition
8.1.3.7.2 Conformance requirement
When the UE receives the first RRC CONNECTION RELEASE message
the UE shall:
1> in state CELL_FACH:
2> if the RRC CONNECTION RELEASE message was received on the DCCH:
3> when the successful transmission of the RRC CONNECTION RELEASE COMPLETE message has been confirmed by the lower layers:
4> release all its radio resources; and
4> indicate the release of the established signalling connections; and
4> pass the value of the IE "Release cause" received in the RRC CONNECTION RELEASE message to upper layers;
4> enter idle mode;
4> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode.
- 3> and the procedure ends.
Reference
3GPP TS 25.331 clause 8.1.4.
8.1.3.7.3 Test purpose
To confirm that when the UE receives an RRC CONNECTION RELEASE message, the UE releases signalling radio bearer and its radio resources and goes back to the idle.
To confirm that the UE enters into idle mode with by performing cell-selection and selecting other cell than the UE selecting cell in connected mode.
8.1.3.7.4 Method of test
Initial Condition
System Simulator: 2 cells – Cell 1 is active and cell 6 is inactive
UE: "Registered idle mode on CS" (state 2) or "Registered idle mode on PS" (state 3) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN domain supported by the UE If the UE supports both CS and PS domains, the initial UE state shall be "Registered idle mode on CS/PS" (state 7).
Test Procedure
Table 8.1.3.7
|
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
|
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
|
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-60 |
off |
-60 |
|
P-CCPCH RSCP (TDD) |
dBm |
-60 |
-60 |
off |
-60 |
Table 8.1.3.7 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. SS switches the power settings between columns "T0" and "T1", whenever the description in multi-cell condition specifies a reverse in the transmission power settings for cell 1 and cell 6.
The UE is in idle mode of cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.1.3.7. SS request operator to make an outgoing call. The SS and UE execute procedure P4 or P6. Next The SS and the UE execute procedure P8 or P10. The SS switches its downlink transmission power settings to columns "T1" and then modifies SIB 3 to indicate that cell 1 is barred. The SS transmits an RRC CONNECTION RELEASE message on DCCH. The UE shall transmit an RRC CONNECTION RELEASE COMPLETE message using AM on DCCH and try to enter idle mode state in cell 1. On selecting cell 1 the UE reads system information block 3 and is aware that cell 1 is barred cell. Hence the UE selects cell 6 and camp on cell 6. Upon completion of the procedure, the SS calls for generic procedure C.1 to check that UE is in idle mode.
NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
The UE is in the CELL_FACH state of cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.1.3.7. SS requests operator to make an outgoing call. |
|||
|
2 |
SS executes procedure P4 (clause 7.4.2.1.2) or P6 (clause 7.4.2.2.2) specified in TS 34.108. |
|||
|
3 |
SS executes procedure P8 (clause 7.4.2.3.2) or P10 (clause 7.4.2.4.2) specified in TS 34.108. |
|||
|
4 |
The SS switches its downlink transmission power settings to columns "T1" in table 8.1.3.7. |
|||
|
5 |
|
System Information Block type 3 |
The SS modifies SIB 3 in cell 1 to indicate that the cell is barred. |
|
|
6 |
The SS waits for 5 s |
|||
|
7 |
|
RRC CONNECTION RELEASE |
||
|
8 |
|
RRC CONNECTION RELEASE COMPLETE |
||
|
9 |
The SS waits for 5s |
|||
|
10 |
|
CALL C.1 |
If the test result of C.1 indicates that UE is in idle mode, the test passes, otherwise it fails. |
|
Specific Message Content
System Information Block type 3 (Step 5)
Use the same message type found in clause 6 of TS 34.108, with the following exceptions:
|
Information Element |
Value/remark |
|
– Cell Access Restriction |
|
|
– Cell barred |
Barred |
|
– Intra-frequency cell re-selection indicator |
Not allowed |
|
– Tbarred |
10[s] |
|
– Cell Reserved for operator use |
Not reserved |
|
– Cell Reservation Extension |
Not reserved |
|
– Access Class Barred List |
|
|
– Access Class Barred0 |
barred |
|
– Access Class Barred1 |
barred |
|
– Access Class Barred2 |
barred |
|
– Access Class Barred3 |
barred |
|
– Access Class Barred4 |
barred |
|
– Access Class Barred5 |
barred |
|
– Access Class Barred6 |
barred |
|
– Access Class Barred7 |
barred |
|
– Access Class Barred10 |
barred |
|
– Access Class Barred11 |
barred |
|
– Access Class Barred12 |
barred |
|
– Access Class Barred13 |
barred |
|
– Access Class Barred14 |
barred |
|
– Access Class Barred15 |
barred |
8.1.3.7.5 Test requirement
After step 3 the UE shall transmit RRC CONNECTION RELEASE COMPLETE messages using AM on DCCH.
After step 9 the UE shall be in idle mode of cell 6.
8.1.3.8 Void
8.1.3.9 RRC Connection Release in CELL_DCH state (Network Authentication Failure): Success
8.1.3.9.1 Definition
8.1.3.9.2 Conformance requirement
1. TS 25.331
If the upper layers request the release of the RRC connection, the UE shall:
1> release all its radio resources;
1> enter idle mode;
1> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2;
1> if the UE was in CELL_DCH state prior to entering idle mode:
2> consider all cells that were in the active set prior to entering idle mode to be barred according to [4]; and
2> consider the barred cells as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred".
2. TS 24.008
Following a UMTS authentication challenge, the MS may reject the core network on the grounds of an incorrect AUTN parameter (see 3GPP TS 33.102). This parameter contains two possible causes for authentication failure:
….
SQN failure:
If the MS considers the SQN (supplied by the core network in the AUTN parameter) to be out of range, it shall send a AUTHENTICATION FAILURE message to the network, with the reject cause ‘Synch failure’ and a re-synchronization token AUTS provided by the SIM (see 3GPP TS 33.102). The MS shall then follow the procedure described in clause 4.3.2.6 (d) of TS 24.008.
….
Authentication failure (reject cause ‘synch failure’):
The MS shall send an AUTHENTICATION FAILURE message, with reject cause ‘synch failure,’ to the network and start the timer T3216.
….
If the timer T3216 expires, then the MS shall behave as described in clause 4.3.2.6.1 of TS 24.008.
Reference
3GPP TS 25.331 clause 8.1.4a.
3GPP TS 24.008 clause 4.3.2.5.1, 4.3.2.6
8.1.3.9.3 Test purpose
To confirm that when the upper layers request the release of the RRC connection, the UE releases signalling radio bearer and its radio resources and goes back to idle mode.
To confirm that the UE enters idle mode, bars the cell for a period Tbarred and hence performs cell-selection to another (non-barred) cell.
8.1.3.9.4 Method of test
Initial Condition
System Simulator: 3 cells – Cell 1, 2 and 3 are active.
UE: "CS-DCCH+DTCH_DCH" (state 6-9) or " PS-DCCH+DTCH_DCH " (state 6-10) in cell 1 as specified in clause 7.4 of TS 34.108, depending on the CN domain supported by the UE.
Test Procedure
Table 8.1.3.9 illustrates the downlink power to be applied for the 3 cells at various time instants of the test execution. Column marked "T0" denotes the initial conditions, while columns marked "T1" are to be applied subsequently. The exact instants on which these values shall be applied are described in the text in this clause.
Table 8.1.3.9
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
Cell 3 |
|||
|
T0 |
T1 |
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Mid Range Test Frequency |
Mid Range Test Frequency |
Mid Range Test Frequency |
||||
|
CPICH Ec |
dBm/3.84 MHz |
-60 |
-60 |
-85 |
-62 |
-85 |
-65 |
|
PCCPCH RSCP |
dBm |
-60 |
-60 |
-85 |
-62 |
-85 |
-65 |
SS switches the downlink transmission power of the 3 cells to the columns "T1" in Table 8.1.3.9. UE transmits a MEASUREMENT REPORT message which includes the primary scrambling code for cell 2 and 3 according to IE "Intra-frequency event identity", which is set to ‘1a’ for FDD mode in the SYSTEM INFORMATION BLOCK TYPE 11. For FDD, in steps 2 and 3, after the MEASUREMENT REPORT message is received, the SS configures the new radio link to be added from cell 2 and then the SS transmits to the UE in cell 1 an ACTIVE SET UPDATE message which includes IE "Radio Link Addition Information", indicating the addition of cell 2 into the active set, on DCCH using AM RLC.
When the UE receives this message, the UE shall configure layer 1 to begin reception without affecting the current uplink and downlink activities of existing radio links. The UE shall transmit an ACTIVE SET UPDATE COMPLETE message to the SS on the uplink DCCH using AM RLC.
The SS transmits a DOWNLINK DIRECT TRANSFER message. This message contains a NAS message (AUTHENTICATION REQUEST for CS domain or AUTHENTICATION AND CIPHERING REQUEST for PS domain) and an invalid SQN. The UE shall transmit an UPLINK DIRECT TRANSFER message using AM on DCCH. After SS acknowledges the UPLINK DIRECT TRANSFER message, SS shall wait for T3216 or T3320 to expire in the UE. The UE shall then deem that the network has failed the authentication check, release the RRC connection, enter idle mode, bar cell 1 and 2 and perform cell re- selection. Then SS wait for 5 s. SS transmits PAGING TYPE 1 message. The UE shall respond with RRC CONNECTION REQUEST message in cell 3. SS then transmit RRC CONNECTION REJECT message back to UE. SS then waits for Tbarred to expire (22 minutes) before SS execute generic procedure C.1 in cell 1 to check that UE is in idle mode in cell 1.
NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
|
MEASUREMENT REPORT |
See specific message contents for this message. This step will be only applicable for FDD. |
|
|
2 |
|
ACTIVE SET UPDATE |
The SS transmit this message on downlink DCCH using AM RLC which includes IE "Radio Link Addition Information" for cell 2. This step will be only applicable for FDD. |
|
|
3 |
|
ACTIVE SET UPDATE COMPLETE |
The UE adds the radio link in cell 2. This step will be only applicable for FDD. |
|
|
4 |
|
DOWNLINK DIRECT TRANSFER |
Depending on supported CN domain, AUTHENTICATION AND CIPHERING REQUEST message (PS domain) or AUTHENTICATION REQUEST (CS domain) message is embedded in DOWNLINK DIRECT TRANSFER message. An invalid SQN is provided in this message. |
|
|
5 |
|
UPLINK DIRECT TRANSFER |
After SS acknowledged this message, SS waits for T3216 or T3320 to expire. |
|
|
6 |
The SS waits for 5s |
|||
|
7 |
|
PAGING TYPE 1 |
||
|
8 |
|
RRC CONNECTION REQUEST |
SS checks that the UE sends this message in cell 3 |
|
|
9 |
|
RRC CONNECTION REJECT |
||
|
10 |
SS waits 22 minutes for Tbarred to expire. |
|||
|
11 |
|
CALL C.1 |
SS execute this generic procedure in cell 1. If the test result of C.1 indicates that UE is in idle mode, the test passes, otherwise it fails. |
|
Specific Message Content
MEASUREMENT REPORT (Step 1) (FDD)
Note1: UE may send the Measured Results for Cell 1, 2 and 3 in any order.
Note2: UE may include the Cell Measurement Event Results for cell 3.
|
Information Element |
Value/remark |
|
Message Type |
|
|
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. |
|
– 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. |
|
Measurement identity |
1 |
|
Measured Results |
|
|
– Intra-frequency measured results |
|
|
– Cell measured results |
|
|
– Cell Identity |
Checked that this IE is absent |
|
– SFN-SFN observed time difference |
Checked that this IE is absent |
|
– Cell synchronisation information |
Checked that this IE is absent |
|
– Primary CPICH info |
|
|
– Primary scrambling code |
Refer to clause titled "Default settings for cell No.1 (FDD)" in clause 6.1 of TS 34.108 |
|
– CPICH Ec/N0 |
Checked that this IE is absent |
|
– CPICH RSCP |
Checked that this IE is present |
|
– Pathloss |
Checked that this IE is absent |
|
– Cell measured results |
|
|
– Cell Identity |
Checked that this IE is absent |
|
– SFN-SFN observed time difference |
Checked that this IE is absent |
|
– Cell synchronisation information |
Checked that this IE is present and includes IE COUNT-C-SFN frame difference |
|
– Primary CPICH info |
|
|
– Primary scrambling code |
Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1 of TS 34.108 |
|
– CPICH Ec/N0 |
Checked that this IE is absent |
|
– CPICH RSCP |
Checked that this IE is present |
|
– Pathloss |
Checked that this IE is absent |
|
– Cell measured results |
|
|
– Cell Identity |
Checked that this IE is absent |
|
– SFN-SFN observed time difference |
Checked that this IE is absent |
|
– Cell synchronisation information |
Checked that this IE is present and includes IE COUNT-C-SFN frame difference |
|
– Primary CPICH info |
|
|
– Primary scrambling code |
Refer to clause titled "Default settings for cell No.3 (FDD)" in clause 6.1 of TS 34.108 |
|
– CPICH Ec/N0 |
Checked that this IE is absent |
|
– CPICH RSCP |
Checked that this IE is present |
|
– Pathloss |
Checked that this IE is absent |
|
Measured results on RACH |
Checked that this IE is absent |
|
Additional measured results |
Checked that this IE is absent |
|
Event results |
|
|
– Intra-frequency measurement event results |
|
|
– Intra-frequency event identity |
1a |
|
– Cell measurement event results |
|
|
– Primary CPICH info |
|
|
– Primary scrambling code |
Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1 of TS 34.108 |
|
– Primary scrambling code |
Refer to clause titled "Default settings for cell No.3 (FDD)" in clause 6.1 of TS 34.108 |
ACTIVE SET UPDATE (Step 2) (FDD only)
The message to be used in this test is defined in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
Version |
|
Radio link addition information |
||
|
– Primary CPICH Info |
||
|
– Primary Scrambling Code |
Set to same code as assigned for cell 2 |
|
|
– Downlink DPCH info for each RL |
||
|
– CHOICE mode |
FDD |
|
|
– Primary CPICH usage for channel estimation |
P-CPICH can be used. |
|
|
– DPCH frame offset |
Calculated value from Cell synchronisation information |
|
|
– Secondary CPICH info |
Not Present |
|
|
– DL channelization code |
This IE is repeated for all existing downlink DPCHs allocated to the UE |
|
|
– Secondary scrambling code |
1 |
|
|
– Spreading factor |
Refer to TS 34.108 clause 6.10.2.4 "Typical radio parameter sets" |
|
|
– Code Number |
For each DPCH, assign the same code number in the current code given in cell 1. |
|
|
– Scrambling code change |
Not Present |
|
|
– TPC Combination Index |
0 |
|
|
– SSDT Cell Identity |
Not Present |
R99 and Rel-4 only |
|
– Close loop timing adjustment mode |
Not Present |
|
|
– TFCI Combining Indicator |
FALSE |
|
|
– SCCPCH information for FACH |
Not Present |
R99 and Rel-4 only |
ACTIVE SET UPDATE COMPLETE (Step 3) (FDD only)
Only the message type of this message is checked.
DOWNLINK DIRECT TRANSFER (Step 4)
Use the same message sub-type as found in TS 34.108 clause 9, with the following exceptions.
|
Information Element |
Value/remark |
|
CN domain identity |
CS domain or PS domain |
|
NAS message |
AUTHENTICATION REQUEST (CS domain) or AUTHENTICATION AND CIPHERING REQUEST (PS domain) with an invalid SQN value. |
UPLINK DIRECT TRANSFER (Step 5)
|
Information Element |
Value/remark |
|
Message Type |
|
|
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. |
|
CN domain identity |
CS domain or PS domain |
|
NAS message |
AUTHENTICATION FAILURE(CS domain) or AUTHENTICATION AND CIPHERING FAILURE (PS domain) |
|
Measured results on RACH |
Not checked |
8.1.3.9.5 Test requirement
At step 1 the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH using AM RLC.
After step 2 the UE shall transmit an ACTIVE SET UPDATE COMPLETE message on the uplink DCCH.
After step 4 the UE shall transmit an UPLINK DIRECT TRANSFER messages using AM on DCCH.
After step 7, the UE shall transmit RRC CONNECTION REQUEST message using TM RLC on CCCH in cell 3.
After step 10 the UE shall be in idle mode in cell 1.