8.2.3 Radio Bearer Release
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
8.2.3.1 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success
8.2.3.1.1 Definition
–
8.2.3.1.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message; or
it shall:
1> perform the physical layer synchronisation procedure as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the UE shall:
1> if the IE "Uplink DPCH Info" is absent, not change its current UL Physical channel configuration;
1> if the IE "Downlink information for each radio link" is absent, not change its current DL Physical channel configuration.
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements as specified below. The UE shall:
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
8.2.3.1.3 Test purpose
To confirm that the UE releases the existing radio bearer according to a RADIO BEARER RELEASE message.
8.2.3.1.4 Method of test
Initial Condition
System Simulator: 1 cell.
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.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message to the UE. The UE releases the radio access bearer and transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
||
2 |
|
RADIO BEARER RELEASE COMPLETE |
Release the radio bearer. |
|
3 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE
None.
8.2.3.1.5 Test requirement
After step 2 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.1a Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (TDD Only)
8.2.3.1a.1 Definition
The features and operation of UpPCH shifting have been introduced to core specification (TS 25.331 clause 8.6.6.26) for LCR TDD.
8.2.3.1a.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message; or
it shall:
1> perform the physical layer synchronisation procedure as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the UE shall:
1> if the IE "Uplink DPCH Info" is absent, not change its current UL Physical channel configuration;
1> if the IE "Downlink information for each radio link" is absent, not change its current DL Physical channel configuration.
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements as specified below. The UE shall:
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
8.2.3.1a.3 Test purpose
To confirm that the UE releases the existing radio bearer according to a RADIO BEARER RELEASE message.
8.2.3.1a.4 Method of test
Initial Condition
System Simulator: 1 cell.
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.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message to the UE. The UE releases the radio access bearer and transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
||
2 |
|
RADIO BEARER RELEASE COMPLETE |
Release the radio bearer. |
|
3 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
System Information Block type 3 (TDD)
Information Element |
Value/remark |
Version |
– SIB4 Indicator |
TRUE |
|
– Cell identity |
0000 0000 0000 0000 0000 0000 0100B |
|
– Cell selection and re-selection info |
||
– Mapping info |
Not present |
|
– Cell selection and reselection quality measure |
(no data) |
|
– CHOICE mode |
TDD |
|
– Sintrasearch |
10 dB |
|
– Sintersearch |
10 dB |
|
– SsearchHCS |
Not present |
|
– RAT List |
Not present |
|
– Qrxlevmin |
-103 dBm |
|
– Qhyst1s |
0 dB |
|
– Treselections |
0 seconds |
|
– HCS Serving cell information |
Not present |
|
– Maximum allowed UL TX power |
30dBm |
|
– Cell Access Restriction |
||
– Cell barred |
Not barred |
|
– Intra-frequency cell re-selection indicator |
Not present |
|
– Tbarred |
Not present |
|
– Cell Reserved for operator use |
Not reserved |
|
– Cell Reservation Extension |
Not reserved |
|
– Access Class Barred List |
||
– Access Class Barred0 |
Not barred |
|
– Access Class Barred1 |
Not barred |
|
– Access Class Barred2 |
Not barred |
|
– Access Class Barred3 |
Not barred |
|
– Access Class Barred4 |
Not barred |
|
– Access Class Barred5 |
Not barred |
|
– Access Class Barred6 |
Not barred |
|
– Access Class Barred7 |
Not barred |
|
– Access Class Barred8 |
Not barred |
|
– Access Class Barred9 |
Not barred |
|
– Access Class Barred10 |
Not barred |
|
– Access Class Barred11 |
Not barred |
|
– Access Class Barred12 |
Not barred |
|
– Access Class Barred13 |
Not barred |
|
– Access Class Barred14 |
Not barred |
|
– Access Class Barred15 |
Not barred |
|
– Domain Specific Access Restriction Parameters For PLMN Of MIB |
Not present |
REL-6 |
– Domain Specific Access Restriction For Shared Network |
Not present |
REL-6 |
-v4b0NonCriticalExtensions |
||
-sysInfoType3-v4b0ext |
||
– mapping-LCR |
22 |
|
RADIO BEARER RELEASE(Setp 1)
Use the same message sub-type titled in [9] TS 34.108 clause 9 with the following exception:
Information Element |
Value/Remarks |
Deleted TrCH information list |
A1,A2, A3,A4, A5, A6,A7, A8 |
radioBearerSetup-r4-add-ext |
|
radioBearerSetup-r4-TDD128-add-ext |
|
UpPCHpositionInfo |
22 |
8.2.3.1a.5 Test requirement
After step 2 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.2 Void
8.2.3.3 Void
8.2.3.4 Void
8.2.3.5 Void
8.2.3.6 Void
8.2.3.7 Radio Bearer Release for transition from CELL_DCH to CELL_FACH: Success
8.2.3.7.1 Definition
8.2.3.7.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message; or
it shall:
1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:
2> perform the physical layer synchronisation procedure A as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If after state transition the UE enters CELL_FACH state, the UE shall, after the state transition:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
1> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD):
2> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Cell reselection";
2> when the cell update procedure completed successfully:
3> if the UE is in CELL_PCH or URA_PCH state:
4> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Uplink data transmission";
4> proceed as below.
1> select PRACH according to TS 25.331 subclause 8.5.17;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the contents of the variable C_RNTI is empty:
2> perform a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Cell reselection";
2> when the cell update procedure completed successfully:
3> if the UE is in CELL_PCH or URA_PCH state:
4> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Uplink data transmission";
4> proceed as below.
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements as specified below. The UE shall:
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
8.2.3.7.3 Test purpose
To confirm that the UE release the existing the radio bearer according to a RADIO BEARER RELEASE message.
8.2.3.7.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: PS-DTCH+DCCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message to the UE. The UE releases the radio access bearer and transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
SS releases the radio bearer in the fashion specified in the message and allocate common channel resources to carry the remaining radio bearers. |
|
2 |
The UE selects PRACH and S-CCPCH indicated in SIB5/SIB5bis and SIB6 after entering CELL FACH state. The UE shall release dedicated channels, and reconfigure the remaining radio bearers using the common channel. |
|||
3 |
|
RADIO BEARER RELEASE COMPLETE |
||
4 |
|
CALL C.2 |
If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 1)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9 with the following exception:
Information Element |
Value/remark |
New C-RNTI |
0000 0000 0000 0001B |
8.2.3.7.5 Test requirement
After step 2 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.8 Radio Bearer Release for transition from CELL_DCH to CELL_FACH: Success (Cell re-selection)
8.2.3.8.1 Definition
8.2.3.8.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message; or
it shall:
1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:
2> perform the physical layer synchronisation procedure A as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If after state transition the UE enters CELL_FACH state, the UE shall, after the state transition:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304
1> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD):
2> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Cell reselection";
1> select PRACH according to TS 25.331 subclause 8.5.17;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the contents of the variable C_RNTI is empty:
2> perform a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Cell reselection";
2> when the cell update procedure completed successfully:
3> if the UE is in CELL_PCH or URA_PCH state:
4> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Uplink data transmission";
If the CELL UPDATE CONFIRM message:
– does not include "RB information elements"; and
– does not include "Transport channel information elements"; and
– does not include "Physical channel information elements"; and
– includes "CN information elements"; or
– includes the IE "Ciphering mode info"; or
– includes the IE "Integrity protection mode info"; or
– includes the IE "New C-RNTI"; or
– includes the IE "New U-RNTI":
the UE shall:
1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements as specified below. The UE shall:
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.3.1.7.
8.2.3.8.3 Test purpose
To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE message after the UE completes a cell update procedure.
8.2.3.8.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108.
NOTE: The ‘timer poll’ value in the SS RLC transmit entity should be set to 800 ms.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message to request the UE to transit from CELL_DCH to CELL_FACH. The UE initiates the cell update procedure because the UE cannot detect the specified cell in this message. The UE transmits a CELL UPDATE message on uplink CCCH with IE "Cell update cause" set to "cell reselection". The SS shall transmit a CELL UPDATE CONFIRM message on downlink DCCH after receiving CELL UPDATE message. The UE then transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the DCCH using AM RLC. The UE transmits a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
Void |
|||
2 |
Void |
|||
3 |
|
RADIO BEARER RELEASE |
Assigned the transition from CELL_DCH to CELL_FACH |
|
4 |
|
CELL UPDATE |
The value "cell reselection" shall be set in IE "cell update cause". |
|
5 |
|
CELL UPDATE CONFIRM |
See message content. |
|
6 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
||
7 |
|
RADIO BEARER RELEASE COMPLETE |
||
8 |
|
CALL C.2 |
If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 3) (FDD)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Downlink information for each radio links |
|
– Primary CPICH info |
|
– Primary scrambling code |
150 |
RADIO BEARER RELEASE (Step 3) (TDD)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Downlink information for each radio links |
|
– Primary CCPCH info |
|
– Cell parameters ID |
4 |
CELL UPDATE (Step 4)
The contents of CELL UPDATE message is identical as "Contents of CELL UPDATE message" as found in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Cell Update Cause |
"cell reselection" |
CELL UPDATE CONFIRM (Step 5)
Use the same message type found in clause [9] TS 34.108 clause 9, with the following exceptions.
Information Element |
Value/Remarks |
New C-RNTI |
‘1010 1010 1010 1010’ |
UTRAN MOBILITY INFORMATION CONFIRM (Step 6)
Only the message type is checked.
8.2.3.8.5 Test requirement
After step 3 the UE shall transmit a CELL UPDATE message on the CCCH with IE "Cell update cause" set to "cell reselection".
After step 5 UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the DCCH using AM RLC.
After step 6 UE shall transmit a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC.
8.2.3.9 Radio Bearer Release for transition from CELL_FACH to CELL_DCH: Success
8.2.3.9.1 Definition
8.2.3.9.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message; or
it shall:
1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:
2> perform the physical layer synchronisation procedure A as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If after state transition the UE enters CELL_DCH state, the UE shall, after the state transition:
1> remove any C-RNTI from MAC;
1> clear the variable C_RNTI.
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements as specified below. The UE shall:
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
8.2.3.9.3 Test purpose
To confirm that an UE, in state CELL_FACH, releases the radio access bearers using common physical channel. After the release, it shall access the affected radio bearers on the DPCH.
8.2.3.9.4 Method of test
Initial Condition
System Simulator: 1 cell.
SYSTEM INFORMATION BLOCK TYPE 1 (see specific message contents).
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RELEASE message to the UE. In this message, SS commands the UE to release radio access bearers on common physical channel. At the same time, SS allocates DPCH to support the affected radio bearers. The UE shall release the indicated radio access bearers and transmit a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
||
2 |
UE shall release the radio access bearers carried by common physical channel. |
|||
3 |
|
RADIO BEARER RELEASE COMPLETE |
||
4 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
System Information Block type 1 (FDD)
Use the default system information block with the same type specified in clause 6.1 of TS 34.108, with the following exceptions:
Information Element |
Value/remark |
– UE Timers and constants in connected mode |
|
– T312 |
2 |
RADIO BEARER RELEASE (Step 1)
Use the same message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in [9] TS 34.108 clause 9.
8.2.3.9.5 Test requirement
After step 2 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message using the dedicated physical channel allocated.
8.2.3.10 Void
8.2.3.11 Radio Bearer Release for transition from CELL_FACH to CELL_DCH: Failure (Physical channel failure and successful reversion to old configuration)
8.2.3.11.1 Definition
8.2.3.11.2 Conformance requirement
When a physical dedicated channel establishment is initiated by the UE, the UE shall start a timer T312 and wait for layer 1 to indicate N312 "in sync" indications. On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset.
If the timer T312 expires before the physical channel is established, the UE shall consider this as a "physical channel establishment failure".
…
If the received message caused the UE to be in CELL_DCH state and the UE failed to establish the dedicated physical channel(s) indicated in the received message the UE shall:
1> revert to the configuration prior to the reception of the message (old configuration);
1> if the old configuration does not include dedicated physical channels (CELL_FACH state):
2> select a suitable UTRA cell according to TS 25.304;
1> transmit a failure response message as specified in TS 25.331 subclause 8.2.2.9, 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 received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
2> clear that entry;
2> set the IE "failure cause" to "physical channel failure".
1> set the variable ORDERED_RECONFIGURATION to FALSE;
1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.
…
The UE shall:
1> in case of reception of a RADIO BEARER RELEASE message:
…
2> transmit a RADIO BEARER RELEASE FAILURE as response message on the DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.7, 8.2.2.9, 8.5.4.
8.2.3.11.3 Test purpose
To confirm that the UE reverts to the old configuration and transmits a RADIO BEARER RELEASE FAILURE message on the DCCH using AM RLC if the UE fails to release the radio bearers in accordance with the specified settings in RADIO BEARER RELEASE message before T312 timer expires.
8.2.3.11.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_FACH state. SS then send a MEASUREMENT CONTROL message to UE. The UE shall perform periodical traffic volume measurement according to this message and then transmit MEASUREMENT REPORT message back to SS. The SS transmits a RADIO BEARER RELEASE message and keeps its current physical channel configuration. The UE is expected to encounter a failure while releasing the radio bearer. After T312 timer expires, the UE shall revert to the old radio bearer configuration, so the UE transmits a RADIO BEARER RELEASE FAILURE message on the DCCH using AM RLC which is set to "physical channel failure" in IE "failure cause". UE shall continue its traffic volume measurement and send MEASUREMENT REPORT messages back to SS periodically.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
0a |
|
MEASUREMENT CONTROL |
SS requests UE to perform periodical traffic volume measurement. |
|
0b |
|
MEASUREMENT REPORT |
||
1 |
|
RADIO BEARER RELEASE |
||
2 |
The SS does not configure the specified L1. |
|||
3 |
|
RADIO BEARER RELEASE FAILURE |
After T312 expiry the UE fails to release a radio bearer and reverts to the old configuration. |
|
4 |
|
MEASUREMENT REPORT |
Specific Message Contents
MEASUREMENT CONTROL (Step 0a)
Use the MEASUREMENT CONTROL message as defined in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/Remark |
Version |
Measurement Identity |
1 |
|
Measurement Command |
Setup |
|
Measurement reporting mode |
||
– Measurement Report Transfer Mode |
Acknowledged mode RLC |
|
– Periodical Reporting / Event Trigger Reporting Mode |
Periodical Reporting |
|
Additional measurement list |
Not Present |
|
CHOICE measurement type |
Traffic Volume Measurement |
|
– Traffic volume measurement object list |
||
– Uplink transport channel type |
RACHorCPCH |
R99 and Rel-4 |
RACH |
Rel-5 |
|
– UL Target Transport Channel ID |
Not Present |
|
– Traffic volume measurement quantity |
||
– Measurement quantity |
RLC Buffer Payload |
|
– Traffic volume reporting quantity |
||
– RLC Buffer Payload for each RB |
True |
|
– Average of RLC Buffer Payload for each RB |
False |
|
– Variance of RLC Buffer Payload for each RB |
False |
|
– Measurement validity |
||
– UE state |
All states |
|
– CHOICE Reporting criteria |
Periodical Reporting Criteria |
|
– Amount of reporting |
Infinity |
|
– Reporting interval |
8000 |
|
DPCH compressed mode status |
Not Present |
MEASUREMENT REPORT (Step 0b and 4)
Check to see if the same message type found in [9] TS 34.108 Clause 9 is received, with the following exceptions and the order in which the RBs are reported is not checked:
Information Element |
Value/Remarks |
Measurement identity |
1 |
Measured Results |
|
– CHOICE measurement |
Traffic volume measured results list |
– Traffic volume measurement results |
|
– RB identity |
1 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
– RB identity |
2 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
– RB identity |
3 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
– RB identity |
4 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
– RB identity |
20 |
– RLC buffer payload |
Check to see if this IE is present |
– RLC buffer payload average |
Check to see if this IE is absent |
– RLC buffer payload variance |
Check to see if this IE is absent |
Measured results on RACH |
Check to see if this IE is absent |
Additional measured results |
Check to see if this IE is absent |
Event results |
Check to see if this IE is absent |
RADIO BEARER RELEASE (Step 1)
Use the message sub-type titled "Packet to CELL_DCH from CELL_FACH in PS" in Clause 9 of TS 34.108.
RADIO BEARER RELEASE FAILURE (Step 2)
The contents of RADIO BEARER RELEASE FAILURE message in this test case is the same as the RADIO BEARER RELEASE FAILURE message as found in Clause 9 of TS 34.108, with the following exceptions:
Information Element |
Value/remark |
Failure cause |
Physical channel failure |
8.2.3.11.5 Test requirement
After step 0a, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH, reporting the RLC buffer payload of each RBs mapped on RACH at every 8s interval.
After step 2 the UE shall transmit a RADIO BEARER RELEASE FAILURE message on the DCCH using AM RLC, setting the value "physical channel failure" in IE "failure cause".
After step 3, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH, reporting the RLC buffer payload of each RBs mapped on RACH at every 8s interval.
8.2.3.12 Void
8.2.3.13 Void
8.2.3.14 Void
8.2.3.15 Radio Bearer Release for transition from CELL_FACH to CELL_FACH: Success
8.2.3.15.1 Definition
8.2.3.15.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message; or
it shall:
1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:
2> perform the physical layer synchronisation procedure A as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If the UE was in CELL_FACH state upon reception of the reconfiguration message and remains in CELL_FACH state, the UE shall:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency;
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements as specified below. The UE shall:
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
If the IE "RAB information to reconfigure" is included then the UE shall:
1> if the entry for the radio access bearer identified by the IE "CN domain identity" together with the IE "RAB Identity" in the variable ESTABLISHED_RABS already exists:
…
1> else:
2> set the variable INVALID_CONFIGURATION to TRUE.
If the variable INVALID_CONFIGURATION is set to TRUE the UE shall:
1> keep the configuration existing before the reception of the message;
1> transmit a failure response message, setting the information elements as specified below:
2> include the IE "RRC transaction identifier"; and
3> set it to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
3> clear that entry.
2> set the IE "failure cause" to "invalid configuration".
1> set the variable INVALID_CONFIGURATION to FALSE;
1> continue with any ongoing processes and procedures as if the reconfiguration message was not received.
The procedure ends.
…
1> in case of reception of a RADIO BEARER RECONFIGURATION message:
2> if the radio bearer reconfiguration procedure affects several radio bearers:
3> (may) include the identities of the radio bearers for which the procedure would have been successful into the RADIO BEARER RECONFIGURATION FAILURE message.
2> transmit a RADIO BEARER RECONFIGURATION FAILURE as response message on the DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.6.4.2a, 8.2.2.11, 8.2.2.9.
8.2.3.15.3 Test purpose
To confirm that the UE releases the existing the radio bearer(s) according to the RADIO BEARER RELEASE message.
8.2.3.15.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_FACH state. The SS transmits a RADIO BEARER RELEASE message to the UE. The UE releases the radio access bearer and transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
||
2 |
Void |
|||
3 |
|
RADIO BEARER RELEASE COMPLETE |
||
4 |
|
RADIO BEARER RECONFIGURATION |
The IE "RAB information to reconfigure" is included with the same RAB identity as was released with the RADIO BEARER RELEASE message. |
|
5 |
|
RADIO BEARER RECONFIGURATION FAILURE |
The UE responds with failure, in case the RB is properly removed |
|
6 |
|
CALL C.2 |
If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE
Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9.
RADIO BEARER RECONFIGURATION (Step 4)
The contents of RADIO BEARER RECONFIGURATION message in this test case is identical to the message sub-type title "Packet to CELL_FACH from CELL_FACH in PS" as found in clause 9 of TS 34.108 with the following exceptions:
Information Element |
Value/remark |
Version |
---|---|---|
Message Type |
||
RRC transaction identifier |
Arbitrarily selects an integer between 0 and 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. |
|
Integrity protection mode info |
Not Present |
|
Ciphering mode info |
Not Present |
|
Activation time |
Now |
|
New U-RNTI |
Not Present |
|
New C-RNTI |
Not Present |
|
RRC State indicator |
CELL_FACH |
|
UTRAN DRX cycle length coefficient |
Not Present |
|
CN information info |
Not Present |
|
URA identity |
Not Present |
|
RAB information to reconfigure list |
||
– RAB information to reconfigure |
(AM DTCH for PS domain) |
|
– RAB identity |
0000 0101B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
|
– CN domain identity |
PS domain |
|
– NAS Synchronization Indicator |
0101B The first/ leftmost bit of the bit string contains the most significant bit of the NAS Synchronisation Indicator. |
|
RB information to reconfigure list |
TS 25.331 specifies that "Although this IE is not always required, need is MP to align with ASN.1". |
|
– RB information to reconfigure |
(Dummy) |
|
– RB identity |
1 |
|
– PDCP info |
Not Present |
|
– PDCP SN info |
Not Present |
|
– RLC info |
Not Present |
|
– RB mapping info |
Not Present |
|
– RB stop/continue |
Not Present |
|
RB information to be affected list |
Not Present |
|
UL Transport channel information for all transport channels |
Not Present |
|
Deleted TrCH information list |
Not Present |
|
Added or Reconfigured TrCH information list |
Not Present |
|
CHOICE mode |
Not Present |
|
Deleted DL TrCH information list |
Not Present |
|
Added or Reconfigured DL TrCH information list |
Not Present |
|
Maximum allowed UL TX power |
Not Present |
|
CHOICE channel requirement |
Not Present |
|
CHOICE Mode |
FDD |
|
– Downlink PDSCH information |
Not Present |
R99 and Rel-4 only |
Downlink information common for all radio links |
Not Present |
RADIO BEARER RECONFIGURATION FAILURE (step 5)
The contents of RADIO BEARER RECONFIGURATION FAILURE message in this test case is the same as the RADIO BEARER RECONFIGURATION FAILURE message as found in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/remark |
Failure cause |
Invalid configuration |
8.2.3.15.5 Test requirement
After step 1 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message using AM RLC on the common physical channel.
After step 4, UE shall transmit a RADIO BEARER RECONFIGURATION FAILURE message to verify that the RAB is properly removed.
8.2.3.16 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (Subsequently received)
8.2.3.16.1 Definition
8.2.3.16.2 Conformance requirement
If the IE "RRC transaction identifier" is included in a received message, the UE shall perform the actions below. The UE shall:
If the received message is any of the messages:
– RADIO BEARER RELEASE; or
…
the UE shall:
2> if the variable ORDERED_RECONFIGURATION is set to TRUE; or
2> if the variable CELL_UPDATE_STARTED is set to TRUE; or
2> if the table "Accepted transactions" in the variable TRANSACTIONS contains an entry with an IE "Message Type" set to ACTIVE SET UPDATE; or
2> if the received message contains a protocol error according to TS 25.331 clause 9 causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE:
3> if the IE "RRC transaction identifier" of the received message is identical to the "RRC transaction identifier" stored for the same "Message Type" as the received message in the table "Accepted transactions" in the variable TRANSACTIONS:
4> ignore the transaction; and
4> continue with any ongoing processes and procedures as the message was not received;
4> and end the procedure.
3> else:
…
Reference
3GPP TS 25.331 clause 8.6.3.11.
8.2.3.16.3 Test purpose
To confirm that if the UE receives a new RADIO BEARER RELEASE message before the UE releases the radio bearer according to a previous RADIO BEARER RELEASE message it ignore the new RADIO BEARER RELEASE message and configures according to the previous RADIO BEARER RELEASE message received.
8.2.3.16.4 Method of test
Initial Condition
System Simulator: 1 cell.
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.
Test Procedure
The UE is in CELL_DCH state. When the SS transmits a RADIO BEARER RELEASE message to the UE before the UE releases the radio access bearer, the UE ignores the second RADIO BEARER RELEASE message and releases the radio bearer according to the previous RADIO BEARER RELEASE message received. Finally, the UE shall transmit RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
For FDD, the SS sets its UL scrambling code number to "1". |
|
2 |
|
RADIO BEARER RELEASE |
Message sent before the expiry of "activation time" specified in message in step 1. For FDD, the IE "Scrambling code number" is set to "2". For TDD the code combination assigned is different from that assigned in stage 1. |
|
3 |
|
RADIO BEARER RELEASE COMPLETE |
The UE ignores the RADIO BEARER RELEASE message in step 2 and release radio bearer according to the RADIO BEARER RELEASE message in step 1. |
|
4 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 1) (FDD)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/remark |
RRC transaction identifier |
0 |
Activation Time |
[256+Current CFN-[current CFN mod 8 + 8 ]]MOD 256 |
– Uplink DPCH Info |
|
– Scrambling code number |
1 |
RADIO BEARER RELEASE (Step 1) (TDD)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/remark |
RRC transaction identifier |
0 |
Activation Time |
[256+Current CFN-[current CFN mod 8 + 8 ]]MOD 256 |
Uplink DPCH timeslots and codes |
|
– First timeslot code list |
Assigned by SS |
RADIO BEARER RELEASE (Step 2) (FDD)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/remark |
RRC transaction identifier |
0 |
Activation Time |
Not Present |
– Uplink DPCH Info |
|
– Scrambling code number |
2 |
RADIO BEARER RELEASE (Step 2) (TDD)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Speech in CS" or "Non speech in CS" or "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/remark |
RRC transaction identifier |
0 |
Activation Time |
Not Present |
– Uplink DPCH timeslots and codes |
|
– First timeslot code list |
A different code combination to that used in step 1. |
8.2.3.16.5 Test requirement
After step 2 the UE shall transmit an RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC.
8.2.3.17 Radio Bearer Release for transition from CELL_FACH to CELL_DCH: Success (Subsequently received)
8.2.3.17.1 Definition
8.2.3.17.2 Conformance requirement
If the IE "RRC transaction identifier" is included in a received message, the UE shall perform the actions below. The UE shall:
If the received message is any of the messages:
– RADIO BEARER RELEASE; or
…
the UE shall:
2> if the variable ORDERED_RECONFIGURATION is set to TRUE; or
2> if the variable CELL_UPDATE_STARTED is set to TRUE; or
2> if the table "Accepted transactions" in the variable TRANSACTIONS contains an entry with an IE "Message Type" set to ACTIVE SET UPDATE; or
2> if the received message contains a protocol error according to TS 25.331 clause 9 causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE:
3> if the IE "RRC transaction identifier" of the received message is identical to the "RRC transaction identifier" stored for the same "Message Type" as the received message in the table "Accepted transactions" in the variable TRANSACTIONS:
4> ignore the transaction; and
4> continue with any ongoing processes and procedures as the message was not received;
4> and end the procedure.
3> else:
Reference
3GPP TS 25.331 clause 8.6.3.11.
8.2.3.17.3 Test purpose
To confirm that if the UE receives a new RADIO BEARER RELEASE message before the UE releases the radio bearer according to a previous RADIO BEARER RELEASE message, it ignores the new RADIO BEARER RELEASE message and configures according to the previous RADIO BEARER RELEASE message received.
8.2.3.17.4 Method of test
Initial Condition
System Simulator: 1 cell.
SYSTEM INFORMATION BLOCK TYPE 1 (see specific message contents).
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_FACH state. When the SS transmits a RADIO BEARER RELEASE message to the UE before the UE releases the radio access bearer, the UE ignores the second RADIO BEARER RELEASE message and releases the radio bearers according to the previous RADIO BEARER RELEASE message received. Finally, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC. SS calls for generic procedure C.3 2 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
For FDD, the SS sets its UL scrambling code to "1". |
|
2 |
|
RADIO BEARER RELEASE |
For TDD the IE "Secondary scrambling code" is set to "2". For TDD, the code combination assigned is different from that assigned in stage 1. |
|
3 |
|
RADIO BEARER RELEASE COMPLETE |
The UE ignores the RADIO BEARER RELEASE message in step 2 and release radio bearers according to the RADIO BEARER RELEASE message in step 1. |
|
4 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
System Information Block type 1 (FDD)
Use the default system information block with the same type specified in clause 6.1 of TS 34.108, with the following exceptions:
Information Element |
Value/remark |
– UE Timers and constants in connected mode |
|
– T312 |
2 |
RADIO BEARER RELEASE (Step 1) (FDD)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Packet to CELL_DCH from CELL_FACH in PS" found in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
RRC transaction identifier |
0 |
Activation Time Info |
Not present |
– Uplink DPCH Info |
|
– Scrambling code number |
1 |
RADIO BEARER RELEASE (Step 1) (TDD)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
RRC transaction identifier |
0 |
Activation Time Info |
[256+Current CFN-[current CFN mod 8 + 8 ]]MOD 256 |
Uplink DPCH timeslots and codes |
|
– First timeslot code list |
Assigned by SS |
RADIO BEARER RELEASE (Step 2) (FDD)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Packet to CELL_DCH from CELL_FACH in PS" found in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
RRC transaction identifier |
0 |
Activation Time |
Not Present |
– Uplink DPCH Info |
|
– Scrambling code number |
2 |
RADIO BEARER RELEASE (Step 2) (TDD)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type title "Packet to CELL_DCH from CELL_FACH in PS" found in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
RRC transaction identifier |
0 |
Activation Time |
Not Present |
– Uplink DPCH timeslots and codes |
|
– First timeslot code list |
A different code combination to that used in step 1. |
8.2.3.17.5 Test requirement
After step 2 the UE shall transmit an RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC.
8.2.3.18 Radio Bearer Release from CELL_DCH to CELL_PCH: Success
8.2.3.18.1 Definition
8.2.3.18.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message; or
it shall:
1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:
2> perform the physical layer synchronisation procedure A as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If after state transition the UE enters CELL_PCH or URA_PCH state, the UE shall, after the state transition and transmission of the response message:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:
2> set the variable INVALID_CONFIGURATION to TRUE.
…
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements as specified below. The UE shall:
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
If the new state is CELL_PCH, the response message shall be transmitted using the old configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration message, and the UE shall:
1> when RLC has confirmed the successful transmission of the response message:
…
2> enter the new state (CELL_PCH);
…
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
8.2.3.18.3 Test purpose
To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE before entering CELL_PCH state after it received a RADIO BEARER RELEASE message and released its radio access bearers.
8.2.3.18.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message. The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC and enters into CELL_PCH state. SS calls for generic procedure C.4 to check that UE is in CELL_PCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
||
2 |
|
RADIO BEARER RELEASE COMPLETE |
The UE sends this message before it completes state transition. |
|
2a |
Void |
SS sends the L2 ack on the RADIO BEARER RELEASE COMPLETE message and then waits 5 seconds to allow the UE to read system information before the next step. Note: The SS should continue to keep the dedicated channel configuration during the time when the L2 ack is sent to the UE. |
||
3 |
|
CALL C.4 |
If the test result of C.4 indicates that UE is in CELL_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 1) (FDD)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9 with following exceptions:
Information Element |
Value/remark |
RRC State Indicator UTRAN DRX cycle length coefficient |
CELL_PCH 3 |
Downlink information for each radio link |
|
– Primary CPICH info |
|
– Primary scrambling code |
100 |
RADIO BEARER RELEASE (Step 1) (TDD)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9 with following exceptions:
Information Element |
Value/remark |
RRC State Indicator UTRAN DRX cycle length coefficient |
CELL_PCH 3 |
Downlink information for each radio links |
|
– Primary CCPCH info |
|
-Cell parameters ID |
4 |
8.2.3.18.5 Test requirement
After step 1 the UE transmits a RADIO BEARER RELEASE COMPLETE message on uplink DCCH using AM RLC.
8.2.3.19 Radio Bearer Release from CELL_DCH to URA_PCH: Success
8.2.3.19.1 Definition
8.2.3.19.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message; or
it shall:
1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:
2> perform the physical layer synchronisation procedure A as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If after state transition the UE enters CELL_PCH or URA_PCH state, the UE shall, after the state transition and transmission of the response message:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in TS 25.331 subclause 8.6.3.2.
1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:
2> set the variable INVALID_CONFIGURATION to TRUE.
…
1> if the UE enters URA_PCH state, and after cell selection the criteria for URA update caused by "URA reselection" according to TS 25.331 subclause 8.3.1 is fulfilled:
2> initiate a URA update procedure according to TS 25.331 subclause 8.3.1 using the cause "URA reselection";
2> when the URA update procedure is successfully completed:
3> the procedure ends.
The UE shall transmit a response message as specified in TS 25.331 subclause 8.2.2.4, setting the information elements as specified below. The UE shall:
1> set the IE "RRC transaction identifier" to the value of "RRC transaction identifier" in the entry for the received message in the table "Accepted transactions" in the variable TRANSACTIONS; and
1> clear that entry;
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
If the new state is URA_PCH, the response message shall be transmitted using the old configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration message, and the UE shall:
1> when RLC has confirmed the successful transmission of the response message:
…
2> enter the new state (URA_PCH);
…
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4.
8.2.3.19.3 Test purpose
To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE before entering URA_PCH state after it received a RADIO BEARER RELEASE message and released its radio bearers.
8.2.3.19.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: PS-DCCH+DTCH_DCH (state 6-10) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_DCH state. The SS transmits a RADIO BEARER RELEASE message. The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC and enters into URA_PCH state. SS calls for generic procedure C.5 to check that UE is in URA_PCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
||
2 |
|
RADIO BEARER RELEASE COMPLETE |
The UE sends this message before it completes state transition. |
|
2a |
Void |
SS sends the L2 ack on the RADIO BEARER RELEASE COMPLETE message and then waits 5 seconds to allow the UE to read system information before the next step. Note: The SS should continue to keep the dedicated channel configuration during the time when the L2 ack is sent to the UE. |
||
3 |
|
CALL C.5 |
If the test result of C.5 indicates that UE is in URA_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 1) (FDD)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9 with following exceptions:
Information Element |
Value/remark |
RRC State Indicator |
URA_PCH |
UTRAN DRX cycle length coefficient |
3 |
Downlink information for each radio link |
|
– Primary CPICH info |
|
– Primary scrambling code |
100 |
RADIO BEARER RELEASE (Step 1) (TDD)
Information Element |
Value/remark |
RRC State Indicator |
URA_PCH |
UTRAN DRX cycle length coefficient |
3 |
Downlink information for each radio links |
|
– Primary CCPCH info |
|
-Cell parameters ID |
4 |
8.2.3.19.5 Test requirement
After step 1 the UE transmits a RADIO BEARER RELEASE COMPLETE message to the UE on uplink DCCH using AM RLC.
8.2.3.20 Radio Bearer Release for transition from CELL_DCH to CELL_FACH (Frequency modification): Success
8.2.3.20.1 Definition
8.2.3.20.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If after state transition the UE enters CELL_FACH state, the UE shall, after the state transition:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS5.304.
1> if the received reconfiguration message included the IE "Primary CPICH info"), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" :
2> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Cell reselection";
2> when the cell update procedure completed successfully:
3> if the UE is in CELL_PCH or URA_PCH state:
4> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Uplink data transmission";
4> proceed as below.
1> select PRACH according to TS 25.331 subclause 8.5.17;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> use the transport format set given in system information;
1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2> ignore that IE and stop using DRX.
1> if the contents of the variable C_RNTI is empty:
2> perform a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Cell reselection";
2> when the cell update procedure completed successfully:
3> if the UE is in CELL_PCH or URA_PCH state:
4> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "Uplink data transmission";
4> proceed as below.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC, using the new configuration after the state transition.
1> the procedure ends.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
8.2.3.20.3 Test purpose
- To confirm that the UE transits from CELL_DCH to CELL_FACH according to the RADIO BEARER RELEASE message.
- To confirm that the UE transmits RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC on a common physical channel in a different frequency.
8.2.3.20.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.2.3.20
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
T0 |
T1 |
T0 |
T1 |
||
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
CPICH Ec |
dBm/3.84MHz |
-55 |
-85 |
Off |
-55 |
Table 8.2.3.20 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.2.3.20. The SS and UE execute procedure P3 or P5. Next The SS and the UE execute procedure P7 or P9 and then execute procedure P11 or P13. The SS switches its downlink transmission power settings to columns "T1" transmits a RADIO BEARER RELEASE message with no IE "Frequency info" to the UE. The UE releases the radio access bearer and moves into cell 6. The UE transmits CELL UPDATE message with IE "Cell update cause" set to "cell reselection". SS then transmit CELL UDPATE CONFIRM with IE "New C_RNTI". The UE shall respond with an UTRAN MOBILITY INFORMATION CONFIRM message, and then transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC. The SS calls for generic procedure C.2 to check that UE is in CELL_FACH 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 |
|||
1a |
|
SS executes procedure P3 (clause 7.4.2.1.2) or P5 (clause 7.4.2.2.2) specified in TS 34.108. |
||
1b |
|
SS executes procedure P7 (clause 7.4.2.3.2) or P9 (clause 7.4.2.4.2) specified in TS 34.108. |
||
1c |
|
SS executes procedure P11 (clause 7.4.2.5.2) or P13 (clause 7.4.2.6.2) specified in TS 34.108. |
||
2 |
The SS switches its downlink transmission power settings to columns "T1" in table 8.2.3.20. |
|||
3 |
Void |
|||
4 |
|
RADIO BEARER RELEASE |
Not including frequency information. |
|
5 |
|
CELL UPDATE |
The IE "Cell update cause" is set to "cell reselection". |
|
6 |
|
CELL UPDATE CONFIRM |
Including the IE" New C-RNTI" |
|
7 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
||
8 |
|
RADIO BEARER RELEASE COMPLETE |
||
9 |
|
CALL C.2 |
If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 4)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" or "Non speech to CELL_FACH from CELL_DCH in CS" or "Speech to CELL_FACH from CELL_DCH in CS" in [9] TS 34.108 clause 9 with the following exception:
Information Element |
Value/remark |
Frequency info |
|
Downlink information for each radio link |
Not present |
CELL UPDATE (Step 5)
The contents of CELL UPDATE message are identical as "Contents of CELL UPDATE message" as found in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Cell Update Cause |
"cell reselection" |
CELL UPDATE CONFIRM (Step 6)
The contents of CELL UPDATE CONFIRM message are identical as "CELL UPDATE CONFIRM message" as found in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
New C-RNTI |
0000 0000 0000 0001B |
UTRAN MOBILITY UPDATE CONFIRM (Step 7)
The contents of UTRAN MOBILITY UPDATE CONFIRM message are identical as "UTRAN MOBILITY UPDATE CONFIRM message" as found in [9] TS 34.108 clause 9.
8.2.3.20.5 Test requirement
After step 4 the UE shall transmit a CELL UPDATE message on the CCCH in cell 6.
After step 6 the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the DCCH using AM RLC in cell 6.
After step 7 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC in cell 6.
After step 8 the UE shall be in CELL_FACH state of cell 6.
8.2.3.21 Radio Bearer Release from CELL_DCH to CELL_PCH (Frequency modification): Success
8.2.3.21.1 Definition
8.2.3.21.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
…
1> enter a state according to TS 25.331 subclause 8.6.3.3.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE on the uplink DCCH using AM RLC.
If after state transition the UE enters CELL_PCH state from CELL_DCH state, the UE shall, after the state transition and transmission of the response message:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
2> if the UE finds a suitable UTRA cell on that frequency:
3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD):
4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";
4> proceed as below.
2> else, if the UE can not find a suitable UTRA cell on that frequency but it finds a suitable UTRA cell on another frequency:
3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";
3> proceed as below.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
2> if the UE finds a suitable UTRA cell on the current frequency:
3> if the received reconfiguration message included the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD), and the UE selects another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info" (for FDD) or "Primary CCPCH info" (for TDD):
4> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";
4> proceed as below.
2> else, if the UE can not find a suitable UTRA cell on the current frequency but it finds a suitable UTRA cell on another frequency:
3> initiate a cell update procedure according to subclause 8.3.1 using the cause "Cell reselection";
3> proceed as below.
1> prohibit periodical status transmission in RLC;
1> remove any C-RNTI from MAC;
1> clear the variable C_RNTI;
1> start timer T305 using its initial value if timer T305 is not running and if periodical update has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity" in the variable TIMERS_AND_CONSTANTS;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in TS 25.331 subclause 8.6.3.2.
…
If the new state is CELL_PCH or URA_PCH, the response message shall be transmitted using the old configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration message, and the UE shall:
1> when RLC has confirmed the successful transmission of the response message:
…
2> enter the new state (CELL_PCH or URA_PCH, respectively);
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
8.2.3.21.3 Test purpose
- To confirm that the UE transmits RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC.
- To confirm that the UE transits from CELL_DCH to CELL_PCH according to the RADIO BEARER RELEASE message.
- To confirm that the UE releases the radio access bearer and selects a common physical channel in a different frequency indicated by SS.
8.2.3.21.4 Method of test
Initial Condition
System Simulator: 2 cells–Cells 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.2.3.21
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
T0 |
T1 |
T0 |
T1 |
||
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
CPICH Ec |
dBm/3.84MHz |
-55 |
-85 |
Off |
-55 |
Table 8.2.3.21 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 in cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.2.3.21. The SS and UE execute procedure P3 or P5. Next The SS and the UE execute procedure P7 or P9 and then execute procedure P11 or P13. The SS switches its downlink transmission power settings to columns "T1" and then transmits a RADIO BEARER RELEASE message with no IE "Frequency info". The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC and enters CELL_PCH state of cell 6, then the UE shall transmit CELL UPDATE procedure with IE "Cell update cause" set to "cell reselection", to complete the procedure. The SS calls for generic procedure C.4 to check that UE is in CELL_PCH 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 |
|||
1a |
|
SS executes procedure P3 (clause 7.4.2.1.2) or P5 (clause 7.4.2.2.2) specified in TS 34.108. |
||
1b |
|
SS executes procedure P7 (clause 7.4.2.3.2) or P9 (clause 7.4.2.4.2) specified in TS 34.108. |
||
1c |
|
SS executes procedure P11 (clause 7.4.2.5.2) or P13 (clause 7.4.2.6.2) specified in TS 34.108. |
||
2 |
The SS switches its downlink transmission power settings to columns "T1" in table 8.2.3.21. |
|||
3 |
|
Void |
||
4 |
|
RADIO BEARER RELEASE |
Not including new frequency information. |
|
5 |
|
RADIO BEARER RELEASE COMPLETE |
The UE sends this message before it completes state transition. UE sends this message in cell 1. |
|
5a |
Void |
SS sends the L2 ack on the RADIO BEARER RELEASE COMPLETE message. Note: The SS should continue to keep the dedicated channel configuration during the time when the L2 ack is sent to the UE. |
||
6 |
|
CELL UPDATE |
The IE "Cell update cause" is set to "cell reselection". |
|
7 |
|
CELL UPDATE CONFIRM |
IE "RRC State Indicator" is set to "CELL_PCH". |
|
8 |
The SS waits for 5 s. |
|||
9 |
|
CALL C.4 |
If the test result of C.4 indicates that UE is in CELL_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 4)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_DCH in PS" or "Non speech to CELL_FACH from CELL_DCH in CS" or "Speech to CELL_FACH from CELL_DCH in CS" in [9] TS 34.108 clause 9, with following exceptions:
Information Element |
Value/remark |
RRC State Indicator |
CELL_PCH |
UTRAN DRX cycle length coefficient |
3 |
Frequency info |
Not Present |
Downlink information for each radio link |
Not Present |
CELL UPDATE (Step 6)
The contents of CELL UPDATE message are identical as "Contents of CELL UPDATE message" as found in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/remark |
Cell Update Cause |
"cell reselection" |
CELL UPDATE CONFIRM (Step 7)
The contents of CELL UPDATE CONFIRM message are identical as "CELL UPDATE CONFIRM message" as found in [9] TS 34.108 clause 9, with the following exceptions:
Information Element |
Value/remark |
RRC State indicator |
CELL_PCH |
UTRAN DRX cycle length coefficient |
3 |
8.2.3.21.5 Test requirement
After step 4 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on uplink DCCH using AM RLC in cell 1.
After step 5 the UE shall transmit a CELL UPDATE message on the CCCH with IE "Cell update cause" set to "cell reselection" in cell 6.
After step 8 the UE shall be in CELL_PCH state in cell 6.
8.2.3.22 Radio Bearer Release for transition from CELL_FACH to CELL_PCH: Success
8.2.3.22.1 Definition
8.2.3.22.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
1> enter a state according to TS 25.331 subclause 8.6.3.3.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE on the uplink DCCH using AM RLC, using the old configuration before the state transition.
If after state transition the UE enters CELL_PCH state, the UE shall, after the state transition and transmission of the response message:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
1> prohibit periodical status transmission in RLC;
1> remove any C-RNTI from MAC;
1> clear the variable C_RNTI;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in TS 25.331 subclause 8.6.3.2.
1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:
2> keep the configuration existing before the reception of the message and transmit a failure response message as specified in TS 25.331subclause 8.2.2.9
1> if the UE enters CELL_PCH state from CELL_FACH state, and the received reconfiguration message included the IE "Primary CPICH info", and the UE selected another cell than indicated by this IE:
2> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "cell reselection";
2> when the cell update procedure is successfully completed:
3> the procedure ends.
Reference
3GPP TS 25.331 clause 8.2.2, 8.3, 8.5 and 8.6.
8.2.3.22.3 Test purpose
1. To confirm that the UE transmits RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC.
2. To confirm that the UE transits from CELL_FACH to CELL_PCH according to the RADIO BEARER RELEASE message.
3. To confirm that the UE releases the radio access bearer and selects a common physical channel.
8.2.3.22.4 Method of test
Initial Condition
System Simulator: 1 cell– Cell 1 is active.
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_FACH state of cell 1. The SS transmits a RADIO BEARER RELEASE message. The UE shall release all radio access bearer and enter CELL_PCH state after it transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC. Upon completion of the procedure, the SS calls for generic procedure C.4 to check that UE is in CELL_PCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
The UE is in CELL_FACH state of cell 1. |
|||
2 |
|
RADIO BEARER RELEASE |
||
3 |
|
RADIO BEARER RELEASE COMPLETE |
The UE transmits this message on uplink DCCH using AM RLC. |
|
4 |
The SS waits for 5 s. |
|||
5 |
|
CALL C.4 |
If the test result of C.4 indicates that UE is in CELL_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 2)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9 with following exceptions:
Information Element |
Value/remark |
RRC State Indicator |
CELL_PCH |
UTRAN DRX cycle length coefficient |
3 |
8.2.3.22.5 Test requirement
After step 2 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on uplink DCCH using AM RLC.
After step 4 the UE shall be in CELL_PCH state in cell 1.
8.2.3.23 Radio Bearer Release for transition from CELL_FACH to URA_PCH: Success
8.2.3.23.1 Definition
8.2.3.23.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
1> enter a state according to TS 25.331 subclause 8.6.3.3.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE on the uplink DCCH using AM RLC, using the old configuration before the state transition.
If after state transition the UE enters URA_PCH state, the UE shall, after the state transition and transmission of the response message:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
1> prohibit periodical status transmission in RLC;
1> remove any C-RNTI from MAC;
1> clear the variable C_RNTI;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in TS5.331 subclause 8.6.3.2.
1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:
2> keep the configuration existing before the reception of the message and transmit a failure response message as specified in TS 25.331subclause 8.2.2.9
1> if the UE enters URA_PCH state, and after cell selection the criteria for URA update caused by "URA reselection" according to TS5.331 subclause 8.3.1 is fulfilled:
2> initiate a URA update procedure according to TS 25.331 subclause 8.3.1 using the cause "URA reselection";
2> when the URA update procedure is successfully completed:
3> the procedure ends.
Reference
3GPP TS 25.331 clause 8.2.2, 8.3, 8.5 and 8.6.
8.2.3.23.3 Test purpose
1. To confirm that the UE transmits RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC.
2. To confirm that the UE transits from CELL_FACH to URA_PCH according to the RADIO BEARER RELEASE message.
3. To confirm that the UE releases the radio access bearer and selects a common physical channel.
8.2.3.23.4 Method of test
Initial Condition
System Simulator: 1 cell– Cell 1 is active.
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
The UE is in CELL_FACH state of cell 1. The SS transmits a RADIO BEARER RELEASE message. The UE shall release all radio access bearers and enter URA_PCH state after it transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC. Upon completion of the procedure, the SS calls for generic procedure C.5 to check that UE is in URA_PCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
The UE is in CELL_FACH state of cell 1. |
|||
2 |
|
RADIO BEARER RELEASE |
||
3 |
|
RADIO BEARER RELEASE COMPLETE |
The UE transmits this message on uplink DCCH using AM RLC. |
|
4 |
The SS waits for 5 s. |
|||
5 |
|
CALL C.5 |
If the test result of C.5 indicates that UE is in URA_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 2)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9 with following exceptions:
Information Element |
Value/remark |
RRC State Indicator |
URA_PCH |
UTRAN DRX cycle length coefficient |
3 |
NOTE: It is to be noted that IE “URA identity” is not included in this message, for the purpose of wider test coverage. The scenario in which IE “URA identity” is included, is tested in other test cases.
8.2.2.23.5 Test requirement
After step 2 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on uplink DCCH using AM RLC.
After step 4 the UE shall be in URA_PCH state.
8.2.3.24 Radio Bearer Release for transition from CELL_DCH to CELL_DCH (Frequency modification): Success
8.2.3.24.1 Definition
8.2.3.24.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:
2> perform the physical layer synchronisation procedure A as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE shall then:
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the UE shall:
1> if the IE "Uplink DPCH Info" is absent, not change its current UL Physical channel configuration;
1> if the IE "Downlink information for each radio link" is absent, not change its current DL Physical channel configuration.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
8.2.3.24.3 Test purpose
1. To confirm that the UE transits from CELL_DCH to CELL_DCH according to the RADIO BEARER RELEASE message.
2. To confirm that the UE transmits RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC on a dedicated physical channel in a different frequency.
8.2.3.24.4 Method of test
Initial Condition
System Simulator: 2 cells–Cell 1 is active and cell 6 is inactive.
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.
Test Procedure
Table 8.2.3.24
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
T0 |
T1 |
T0 |
T1 |
||
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
CPICH Ec |
dBm/3.84MHz |
-55 |
-72 |
Off |
-72 |
Table 8.2.3.24 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. SS switches the power settings from columns "T0" to "T1", whenever the description in multi-cell condition specifies 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.2.3.24. The SS switches its downlink transmission power settings to columns "T1" and transmits a RADIO BEARER RELEASE message including IE "Frequency info" set to frequency information of cell 6 and IE "Primary CPICH info" set to Primary Scrambling Code which is assigned to P-CPICH of cell 6. The UE shall select cell 6 and release the radio access bearer after receiving this message, and then remain in CELL_DCH state. The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC after it completes reconfiguration according to received RADIO BEARER RELEASE message. Upon completion of the procedure, the SS calls for generic procedure C.3 to check that UE is in CELL_DCH 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 initial state of 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.2.3.24. |
|||
2 |
The SS switches its downlink transmission power settings to columns "T1" in table 8.2.3.24. |
|||
3 |
|
RADIO BEARER RELEASE |
Including IE "Frequency info" set to frequency information of cell 6 and IE "Primary CPICH info" set to Primary Scrambling Code assigned to P-CPICH of cell 6. |
|
4 |
The UE select cell 6. |
|||
5 |
|
RADIO BEARER RELEASE COMPLETE |
The UE sends this message on a dedicated physical channel in cell 6. |
|
6 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 3)
The contents RADIO BEARER RELEASE message in this test case is identical the message sub-type indicated by "Packet to CELL_DCH from CELL_DCH in PS" or "Speech in CS" or "Non speech in CS" in [9] TS 34.108 clause 9, with the following exception:
Information Element |
Value/remark |
Frequency info |
|
– UARFCN uplink(Nu) |
Same uplink UARFCN as used for cell 6 |
– UARFCN downlink(Nd) |
Same downlink UARFCN as used for cell 6 |
Downlink information for each radio links |
|
– Primary CPICH info |
|
– Primary Scrambling Code |
Set to same code as used for cell 6 |
8.2.3.24.5 Test requirement
After step 4 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC in cell 6.
After step 5 the UE shall be in CELL_DCH state in cell 6.
8.2.3.25 Radio Bearer Release for transition from CELL_DCH to URA_PCH (Frequency modification): Success
8.2.3.25.1 Definition
8.2.3.25.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
1> enter a state according to TS 25.331 subclause 8.6.3.3.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE on the uplink DCCH using AM RLC, using the old configuration before the state transition.
If after state transition the UE enters URA_PCH state, the UE shall, after the state transition and transmission of the response message:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
1> prohibit periodical status transmission in RLC;
1> remove any C-RNTI from MAC;
1> clear the variable C_RNTI;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in TS 25.331 subclause 8.6.3.2.
1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:
2> keep the configuration existing before the reception of the message and transmit a failure response message as specified in TS 25.331subclause 8.2.2.9
1> if the UE enters URA_PCH state, and after cell selection the criteria for URA update caused by "URA reselection" according to TS 25.331 subclause 8.3.1 is fulfilled:
2> initiate a URA update procedure according to TS 25.331 subclause 8.3.1 using the cause "URA reselection";
2> when the URA update procedure is successfully completed:
3> the procedure ends.
…
If the new state is URA_PCH, the response message shall be transmitted using the old configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration message, and the UE shall:
1> when RLC has confirmed the successful transmission of the response message:
…
2> enter the new state (URA_PCH);
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
8.2.3.25.3 Test purpose
1. To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC.
2. To confirm that the UE transits from CELL_DCH to URA_PCH according to the RADIO BEARER RELEASE message.
3. To confirm that the UE releases radio access bearer, dedicated physical channel and selects a common physical channel in a different frequency.
8.2.3.25.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.2.3.25
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
T0 |
T1 |
T0 |
T1 |
||
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
CPICH Ec |
dBm/3.84MHz |
-55 |
-85 |
Off |
-55 |
Table 8.2.3.25 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.2.3.25. SS requests operator to make an outgoing call. The SS and UE execute procedure P3 or P5. Next The SS and the UE execute procedure P7 or P9 and then execute procedure P11 or P13. The SS switches its downlink transmission power settings to columns "T1" and transmits a RADIO BEARER RELEASE message including no IE "Frequency info". The UE shall transmit a RADIO BEARER RELEASE COMPLETE message using AM RLC and enter URA_PCH state of cell 6. Upon completion of the procedure, the SS calls for generic procedure C.5 to check that UE is in URA_PCH 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 SS has configured its downlink transmission power setting according to columns "T0" in table 8.2.3.25. SS requests operator to make an outgoing call. |
|||
2 |
SS executes procedure P3 (clause 7.4.2.1.2) or P5 (clause 7.4.2.2.2) specified in TS 34.108. |
|||
3 |
SS executes procedure P7 (clause 7.4.2.3.2) or P9 (clause 7.4.2.4.2) specified in TS 34.108. |
|||
4 |
SS executes procedure P11 (clause 7.4.2.5.2) or P13 (clause 7.4.2.6.2) specified in TS 34.108. |
|||
5 |
The SS switches its downlink transmission power settings to columns "T1" in table 8.2.3.25. |
|||
6 |
|
RADIO BEARER RELEASE |
Not including IE "Frequency info" and IE "Primary CPICH info" |
|
7 |
|
RADIO BEARER RELEASE COMPLETE |
UE transmit this message on the dedicated physical channel in cell 1 |
|
8 |
Void |
SS sends the L2 ack on the RADIO BEARER RELEASE COMPLETE message and then waits for 5 s to allow the UE to read system information before the next step. Note: The SS should continue to keep the dedicated channel configuration during the time when the L2 ack is sent to the UE. |
||
9 |
|
CALL C.5 |
If the test result of C.5 indicates that UE is in URA_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 6)
Use the same message sub-type titled "Speech to CELL_FACH from CELL_DCH in CS" or "Non speech to CELL_FACH from CELL_DCH in CS" or "Packet to CELL_FACH from CELL_DCH in PS" in [9] TS 34.108 clause 9 with following exceptions:
Information Element |
Value/remark |
RRC State Indicator |
URA_PCH |
UTRAN DRX cycle length coefficient |
3 |
Frequency info |
Not present |
Downlink information for each radio link |
Not present |
8.2.3.25.5 Test requirement
After step 6 the UE shall transmits a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC in cell 1.
After step 8 the UE shall be in URA_PCH state in cell 6.
8.2.3.26 Radio Bearer Release for transition from CELL_FACH to CELL_PCH (Frequency modification): Success
8.2.3.26.1 Definition
8.2.3.26.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
1> enter a state according to TS 25.331 subclause 8.6.3.3.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE on the uplink DCCH using AM RLC, using the old configuration before the state transition.
If after state transition the UE enters CELL_PCH state, the UE shall, after the state transition and transmission of the response message:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
1> prohibit periodical status transmission in RLC;
1> remove any C-RNTI from MAC;
1> clear the variable C_RNTI;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in TS 25.331 subclause 8.6.3.2.
1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:
2> keep the configuration existing before the reception of the message and transmit a failure response message as specified in TS 25.331subclause 8.2.2.9
1> if the UE enters CELL_PCH state from CELL_FACH state, and the received reconfiguration message included the IE "Primary CPICH info" , and the UE selected another cell than indicated by this IE:
2> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "cell reselection";
2> when the cell update procedure is successfully completed:
3> the procedure ends.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
8.2.3.26.3 Test purpose
1. To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC.
2. To confirm that the UE transits from CELL_FACH to CELL_PCH according to the RADIO BEARER RELEASE message.
3. To confirm that the UE releases radio access bearer and selects a common physical channel in a different frequency.
8.2.3.26.4 Method of test
Initial Condition
System Simulator: 2 cells – Cell 1 is active and cell 6 is inactive
UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
Table 8.2.3.26
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
T0 |
T1 |
T0 |
T1 |
||
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
CPICH Ec |
dBm/3.84MHz |
-55 |
-72 |
Off |
-55 |
Table 8.2.3.26 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 1. The SS shall transmit a RADIO BEARER RELEASE message on downlink DCCH using UM RLC, . The UE shall transmit a RADIO BEARER RELEASE COMPLETE message using AM RLC. The SS shall acknowledge the RADIO BEARER RELEASE COMPLETE message and then switches its downlink transmission power settings to columns “T1”. . Upon completion of the procedure, the SS waits for 5 seconds and calls for generic procedure C.4 in cell 6 to check that UE is in CELL_PCH 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 |
Void |
|||
2 |
Void |
|||
3 |
Void |
|||
4 |
Void |
|||
5 |
Void |
|||
6 |
|
RADIO BEARER RELEASE |
This message is sent on RB 1. IE "Frequency info" and IE "Primary CPICH info" set to that of cell 6. |
|
7 |
|
RADIO BEARER RELEASE COMPLETE |
After SS acknowledges this message, SS switches its downlink transmission power settings to columns "T1" in table 8.2.3.26. |
|
8 |
The SS waits for 5 s. |
|||
9 |
|
CALL C.4 |
(In cell 6) If the test result of C.4 indicates that UE is in CELL_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 6)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9 with following exceptions:
Information Element |
Value/remark |
RRC State Indicator |
CELL_PCH |
UTRAN DRX cycle length coefficient |
3 |
Frequency info |
|
– CHOICE mode |
FDD |
– UARFCN uplink (Nu) |
Not present |
– UARFCN downlink (Nd) |
Set to the frequency of cell 6 |
Downlink information for each radio link |
|
– Primary CPICH Info |
|
– Primary scrambling code |
Set to same code as used for cell 6 |
8.2.3.26.5 Test requirement
After step 6 the UE shall transmits a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC in cell 1.
After step 8 the UE shall be in CELL_PCH state in cell 6.
8.2.3.27 Radio Bearer Release for transition from CELL_FACH to URA_PCH (Frequency modification): Success
8.2.3.27.1 Definition
8.2.3.27.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
1> enter a state according to TS 25.331 subclause 8.6.3.3.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE on the uplink DCCH using AM RLC, using the old configuration before the state transition.
If after state transition the UE enters URA_PCH state, the UE shall, after the state transition and transmission of the response message:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency.
1> if the IE "Frequency info" is not included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304.
1> prohibit periodical status transmission in RLC;
1> remove any C-RNTI from MAC;
1> clear the variable C_RNTI;
1> select Secondary CCPCH according to TS 25.331 subclause 8.5.19;
1> if the IE "UTRAN DRX cycle length coefficient" is included in the same message:
2> use the value in the IE "UTRAN DRX Cycle length coefficient" for calculating Paging occasion and PICH Monitoring Occasion as specified in TS 25.331 subclause 8.6.3.2.
1> if the IE "UTRAN DRX cycle length coefficient" is not included in the same message:
2> keep the configuration existing before the reception of the message and transmit a failure response message as specified in TS 25.331subclause 8.2.2.9.
1> if the UE enters URA_PCH state, and after cell selection the criteria for URA update caused by "URA reselection" according to TS 25.331 subclause 8.3.1 is fulfilled:
2> initiate a URA update procedure according to TS 25.331 subclause 8.3.1 using the cause "URA reselection";
2> when the URA update procedure is successfully completed:
3> the procedure ends.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
8.2.3.27.3 Test purpose
- To confirm that the UE transmits a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC.
- To confirm that the UE transits from CELL_FACH to URA_PCH according to the RADIO BEARER RELEASE message.
- To confirm that the UE releases radio access bearer and selects a common physical channel in a different frequency.
8.2.3.27.4 Method of test
Initial Condition
System Simulator: 2 cells–Cell 1 is active and cell 6 is inactive UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108.
Test Procedure
Table 8.2.3.27
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
T0 |
T1 |
T0 |
T1 |
||
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
CPICH Ec |
dBm/3.84MHz |
-55 |
-72 |
Off |
-55 |
Table 8.2.3.27 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 on cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.2.3.27. The SS transmits a RADIO BEARER RELEASE including IE "Frequency info" and not including IE "Primary CPICH info". The UE shall transmit a RADIO BEARER RELEASE COMPLETE message using AM RLC and the SS shall switch its downlink power settings to columns “T1”. The UE enters URA_PCH state of cell 6. Upon completion of the procedure, the SS calls for generic procedure C.5 to check that UE is in URA_PCH 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 |
Void |
|||
2 |
Void |
|||
3 |
Void |
|||
4 |
Void |
|||
5 |
Void |
|||
6 |
|
RADIO BEARER RELEASE |
Including IE "Frequency info" and not including IE "Primary CPICH info" |
|
7 |
|
RADIO BEARER RELEASE COMPLETE |
UE transmit this message on the common physical channel in cell 1. The SS switches its downlink transmission power settings to columns "T1" in table 8.2.3.27. |
|
8 |
The SS waits for 5 s. |
|||
9 |
|
CALL C.5 |
If the test result of C. 5 indicates that UE is in URA_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 6)
Use the same message sub-type titled "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9 with following exceptions:
Information Element |
Value/remark |
RRC State Indicator |
URA_PCH |
UTRAN DRX cycle length coefficient |
3 |
URA identity |
URA-ID 1 |
Frequency info |
|
– UARFCN uplink(Nu) |
Same uplink UARFCN as used for cell 6 |
– UARFCN downlink(Nd) |
Same downlink UARFCN as used for cell 6 |
8.2.3.27.5 Test requirement
After step 6 the UE shall transmits a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC in cell 1.
After step 7 the UE shall be in URA_PCH state in cell 6.
8.2.3.28 Radio Bearer Release for transition from CELL_FACH to CELL_FACH (Frequency modification): Success
8.2.3.28.1 Definition
8.2.3.28.2 Conformance requirement
If the UE receives:
-a RADIO BEARER RELEASE message;
it shall:
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
1> enter a state according to TS 25.331 subclause 8.6.3.3.
If the UE was in CELL_FACH state upon reception of the reconfiguration message and remains in CELL_FACH state, the UE shall:
1> if the IE "Frequency info" is included in the received reconfiguration message:
2> select a suitable UTRA cell according to TS 25.304 on that frequency;
2> if the received reconfiguration message included the IE "Primary CPICH info", and the UE selected another cell than indicated by this IE or the received reconfiguration message did not include the IE "Primary CPICH info":
3> initiate a cell update procedure according to TS 25.331 subclause 8.3.1 using the cause "cell reselection";
3> when the cell update procedure completed successfully:
4> proceed as below.
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
Reference
3GPP TS 25.331 clause 8.2.2, 8.5 and 8.6.
8.2.3.28.3 Test purpose
1. To confirm that the UE transits from CELL_FACH to CELL_FACH according to the RADIO BEARER RELEASE message.
2. To confirm that the UE transmits RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC on a common physical channel in a different frequency.
8.2.3.28.4 Method of test
Initial Condition
System Simulator: 2 cells – Cell 1 is active and cell 6 is inactive.
UE: "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".
Test Procedure
Table 8.2.3.28
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
T0 |
T1 |
T0 |
T1 |
||
UTRA RF Channel Number |
Mid Range Test Frequency |
High Range Test Frequency |
|||
CPICH Ec |
dBm/3.84MHz |
-55 |
-72 |
Off |
-55 |
Table 8.2.3.28 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_FACH state of cell 1 and the SS has configured its downlink transmission power setting according to columns "T0" in table 8.2.3.28. SS requests operator to make an outgoing call. The SS and UE execute procedure P6. Next The SS and the UE execute procedure P10 and then execute procedure P14. The SS switches its downlink transmission power settings to columns "T1" and transmits a RADIO BEARER RELEASE message including IE "Frequency info" set to frequency information of cell 6 and no IE "Primary CPICH info". The UE shall select cell 6 and initiates CELL UPDATE procedure with IE "Cell update cause" set to "cell reselection" . The UE shall transmit a RADIO BEARER RELEASE COMPLETE message using AM RLC after it completes reconfiguration according to the received RADIO BEARER RELEASE message. Upon completion of the procedure, the SS calls for generic procedure C.2 to check that UE is in CELL_FACH 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 SS has configured its downlink transmission power setting according to columns "T0" in table 8.2.3.28. SS requests operator to make an outgoing call. |
|||
2 |
|
SS executes procedure P6 (clause 7.4.2.2.2) specified in TS 34.108. |
||
3 |
|
SS executes procedure P10 (clause 7.4.2.4.2) specified in TS 34.108. |
||
4 |
|
SS executes procedure P14 (clause 7.4.2.6.2) specified in TS 34.108. |
||
5 |
The SS switches its downlink transmission power settings to columns "T1" in table 8.2.3.28. |
|||
6 |
|
RADIO BEARER RELEASE |
Including IE "Frequency info" set to frequency information of cell 6 and no IE "Primary CPICH info" set to Primary Scrambling Code |
|
7 |
|
CELL UPDATE |
The IE "Cell update cause" is set to "cell reselection". |
|
8 |
|
CELL UPDATE CONFIRM |
Including the IE" New C-RNTI" |
|
9 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
||
10 |
|
RADIO BEARER RELEASE COMPLETE |
The UE sends this message on a common physical channel in cell 6. |
|
11 |
ßà |
CALL C.2 |
If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (Step 6)
The contents of RADIO BEARER RELEASE message in this test case are identical the message sub-type indicated by "Packet to CELL_FACH from CELL_FACH in PS" in [9] TS 34.108 clause 9, with the following exception:
Information Element |
Value/remark |
Frequency info |
|
– UARFCN uplink(Nu) |
Same uplink UARFCN as used for cell 6 |
– UARFCN downlink(Nd) |
Same downlink UARFCN as used for cell 6 |
CELL UPDATE (Step 7)
The contents of CELL UPDATE message are identical as "Contents of CELL UPDATE message" as found in [9] TS 34.108 clause 9 with the following exceptions:
Information Element |
Value/remark |
Cell Update Cause |
"cell reselection" |
CELL UPDATE CONFIRM (Step 8)
The contents of CELL UPDATE CONFIRM message are identical as "CELL UPDATE CONFIRM message" as found in [9] TS 34.108 clause 9. with the following exceptions:
Information Element |
Value/remark |
New C-RNTI |
0000 0000 0000 0001B |
UTRAN MOBILITY UPDATE CONFIRM (Step 9)
The contents of UTRAN MOBILITY UPDATE CONFIRM message is identical as "UTRAN MOBILITY UPDATE CONFIRM message" as found in [9] TS 34.108 clause 9.
8.2.3.28.5 Test requirement
After step 6 the UE shall transmit a CELL UPDATE message on the CCCH in cell 6.
After step 8 the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the DCCH using AM RLC in cell 6.
After step 9 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message on the DCCH using AM RLC in cell 6.
After step 10 the UE shall be in CELL_FACH state in cell 6.
8.2.3.29 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Associated with signalling connection release during simultaneous PS and CS call
8.2.3.29.1 Definition
8.2.3.29.2 Conformance requirement
If the UE receives:
– a RADIO BEARER RELEASE message:
it shall:
1> set the variable ORDERED_RECONFIGURATION to TRUE;
1> if the UE will enter the CELL_DCH state from any state other than CELL_DCH state at the conclusion of this procedure:
2> perform the physical layer synchronisation procedure A as specified in TS 25.214;
1> act upon all received information elements as specified in TS 25.331 subclause 8.6, unless specified in the following and perform the actions below.
The UE may first release the physical channel configuration used at reception of the reconfiguration message. The UE shall then:
…
1> enter a state according to TS 25.331 subclause 8.6.3.3.
…
If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the UE shall:
1> if the IE "Uplink DPCH Info" is absent:
2> not change its current UL Physical channel configuration.1> in TDD:
2> if "Primary CCPCH Info" is included indicating a new target cell and "New C-RNTI" is not specified:
3> remove any C-RNTI from MAC;
3> clear the variable C_RNTI.
…
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE message as response message on the uplink DCCH using AM RLC.
….
If the IE "Signalling Connection release indication" is present in a message, the UE shall:
1> if all radio access bearers for the CN domain identified with the value of the IE "Signalling Connection release indication" would have been released in the variable ESTABLISHED_RABS after processing of the received message:
2> indicate release of the signalling connection identified with the value of the IE "Signalling Connection release indication" to the upper layers;
2> remove the signalling connection identified with the value of the IE "Signalling Connection release indication" from the variable ESTABLISHED_SIGNALLING_CONNECTIONS.
Reference
3GPP TS 25.331 clause 8.2.2.3, 8.2.2.4, 8.6.1.3.
8.2.3.29.3 Test purpose
To confirm that the UE releases the existing radio access bearer and signalling connection according to a RADIO BEARER RELEASE message.
8.2.3.29.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: CS-DCCH+DTCH_DCH (state 6-9) as specified in clause 7.4 of TS 34.108
Test Procedure
The UE is in CELL_DCH state of cell 1. The UE initiates a session setup to establish a PS signalling connection. Then UE and SS establish a PS session while the CS call is still active. The SS transmits a DISCONNECT message to release a CS domain signalling connection. After the CC procedure, SS transmit a RADIO BEARER RELEASE message which includes IE "Signalling Connection release indication" set to "CS domain" and new configuration for remained service to the UE. The UE shall configure the specified channel and transmit a RADIO BEARER RELEASE COMPLETE message on the uplink DCCH using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
The initial state of UE is in CELL_DCH state of cell 1. |
|||
2 |
|
INITIAL DIRECT TRANSFER (SERVICE REQUEST) |
GMM (PS Session setup is initiated from the UE side.) |
|
3 |
|
DOWNLINK DIRECT TRANSFER (AUTHENTICATION AND CIPHERING REQUEST) |
GMM |
|
4 |
|
UPLINK DIRECT TRANSFER (AUTHENTICATION AND CIPHERING RESPONSE) |
GMM |
|
5 |
|
SECURITY MODE COMMAND |
||
6 |
|
SECURITY MODE COMPLETE |
||
7 |
|
UPLINK DIRECT TRANSFER (ACTIVATE PDP CONTEXT REQUEST) |
SM |
|
8 |
|
RADIO BEARER SETUP |
||
9 |
|
RADIO BEARER SETUP COMPLETE |
||
10 |
|
DOWNLINK DIRECT TRANSFER (ACTIVATE PDP CONTEXT ACCEPT) |
SM |
|
11 |
|
DOWNLINK DIRECT TRANSFER (DISCONNECT) |
CC |
|
12 |
|
UPLINK DIRECT TRANSFER (RELEASE) |
CC |
|
13 |
|
DOWNLINK DIRECT TRANSFER (RELEASE COMPLETE) |
CC |
|
14 |
|
RADIO BEARER RELEASE |
Including IE "signalling connection release indication" set to "CS domain" |
|
15 |
|
RADIO BEARER RELEASE COMPLETE |
||
16 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE (STEP 14)
The contents of RADIO BEARER RELEASE message in this test case is identical to the message sub-type titled as "Non speech in CS" or "Speech in CS" as found in Clause 9 of TS 34.108, with the following exceptions
Information Element |
Value/remark |
---|---|
Signalling Connection release indication |
|
– CN domain identity |
CS domain |
8.2.3.29.5 Test requirement
After step 14 the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.30 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (stop of HS-DSCH reception)
8.2.3.30.1 Definition and applicability
All UEs which support FDD or TDD and HS-PDSCH.
8.2.3.30.2 Conformance requirement
If the UE receives a message in which presence is needed for the IE "Activation time", and the value is other than the default value "Now", the UE shall:
1> at the activation time T:
2> for an HS-DSCH related reconfiguration caused by the received message:
3> select the HS-SCCH subframe boundary immediately before the first HS-SCCH subframe, which entirely falls within the 10 ms frame following T;
3> start using, at that HS-SCCH subframe boundary, the new HS-DSCH configuration in the received message, replacing any old HS-DSCH configuration.
2> for an HS-DSCH related reconfiguration in 3.84 Mcps TDD or 7.68 Mcps TDD caused by the received message:
3> start using, at activation time T, the new HS-DSCH configuration in the received message, replacing any old HS-DSCH configuration.
2> for actions, other than a physical channel reconfiguration, caused by the received message:
3> perform the actions for the information elements in the received message as specified elsewhere.
NOTE: In FDD an "HS-DSCH related reconfiguration" includes, in particular, reconfigurations that need to be time-aligned with the 2ms subframe of the HS-SCCH, HS-PDSCH and/or HS-DPCCH. For example, start and stop of HS-SCCH reception and serving HS-DSCH cell change.
The variable HS_DSCH_RECEPTION shall be set to "TRUE" only when all the following conditions are met:
1> the UE is in CELL_DCH state;
1> the variable H_RNTI is set;
1> the UE has a stored IE "HS-SCCH info";
1> for FDD:
2> one of the radio links in the active set is configured as the serving HS-DSCH radio link;
2> the UE has stored the following IEs:
– IE "Measurement Feedback Info";
– IE "Uplink DPCH Power Control Info" including stored ACK, NACK and Ack-NACK Repetition factor;
– IE "HARQ info".
1> for 3.84 Mcps TDD or 7.68 Mcps TDD, the UE has stored the IE "HS-PDSCH Timeslot Configuration" and either of the following conditions are met:
2> a dedicated physical channel is allocated to the UE in the downlink;
2> the UE has stored Dhs-sync.
1> for 1.28 Mcps TDD, the UE has stored the following IE:
– IE "HS-PDSCH Midamble Configuration".
1> there is at least one RB mapped to HS-DSCH;
1> at least for one of the RB’s mapped to HS-DSCH, there is at least one MAC-hs queue (including the IE "MAC-d PDU size Info") configured for the concerning MAC-d flow;
NOTE: To enable or disable HS-DSCH reception, the UTRAN has the possibility to add/remove the concerning HS-DSCH related RB mapping options, add/remove the concerning MAC-d flows or, for FDD, add/remove the serving HS-DSCH radio link, for TDD add/remove H-RNTI upon hard handover.
If any of the above conditions is not met and the variable HS_DSCH_RECEPTION is set to TRUE, the UE shall:
1> set the variable HS_DSCH_RECEPTION to FALSE;
1> stop any HS_SCCH reception procedures;
1> stop any HS-DSCH reception procedures;
1> clear the variable H_RNTI and remove any stored H-RNTI;
1> act as if the IE "MAC-hs reset indicator" is received and set to TRUE;
1> release all HARQ resources;
1> no long consider any radio link to be the HS-DSCH serving radio link.
NOTE: If configured for HS-DSCH and not explicitly indicated as being cleared, the UE will have still stored the IEs "HARQ info", "Added or Reconfigured MAC-d flow", "RB mapping Info" and "Downlink HS-PDSCH information".
Whenever the variable HS_DSCH_RECEPTION is set to TRUE, the UE shall:
1> perform HS_SCCH reception procedures according to the stored HS-SCCH configuration as stated in:
2> subclause 8.6.6.33 for the IE "HS-SCCH Info".
1> perform HS-DSCH reception procedures according to the stored HS-PDSCH configuration as stated in:
2> subclause 8.6.3.1b for the IE "H-RNTI";
2> subclause 8.6.5.6b for the IE "HARQ info";
2> subclause 8.6.6.34 for the IE "Measurement Feedback Info".
Whenever the variable HS_DSCH_RECEPTION is set to FALSE, the UE shall:
1> not perform HS_SCCH reception procedures;
1> not perform HS-DSCH reception procedures.
…
Reference
3GPP TS 25.331 clause8.5.25, 8.6.3.1
8.2.3.30.3 Test purpose
To confirm that the UE releases a radio bearer mapped to HS-DSCH according to the received RADIO BEARER RELEASE message.
8.2.3.30.4 Method of test
Initial Condition
System Simulator: 1 cell
UE: PS_DCCH_DTCH_HS_DSCH (state 6-17) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports FDD or TDD
– UE supports HS-PDSCH
Test Procedure
The UE is in CELL_DCH state with a radio bearer mapped on HS-DSCH established. The SS transmits a RADIO BEARER RELEASE message to the UE . This message requests the release of the radio access bearer mapped to HS-DSCH. After the UE receives this message, it releases the radio access bearer. Finally the UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
||
2 |
|
RADIO BEARER RELEASE COMPLETE |
||
3 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER RELEASE
Use the same message as specified for "Packet to CELL_DCH from CELL_DCH / HS-DSCH in PS" in 34.108.
8.2.3.30.5 Test requirements
After step 1, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.30a Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (stop of HS-DSCH reception) ( In a different frequency band)
8.2.3.30a.1 Definition and applicability
Same conformance requirement as in clause 8.2.3.30 except that UE is support for different frequency band for TDD.
8.2.3.30a.2 Conformance requirement
Same conformance requirement as in clause 8.2.3.30.
8.2.3.30a.3 Test purpose
Same conformance requirement as in clause 8.2.3.30 except that UE can work in different frequency bands.
8.2.3.30a.4 Method of test
Same conformance requirement as in clause 8.2.3.30 except for Expected sequence
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
RADIO BEARER RELEASE |
||
2 |
|
RADIO BEARER RELEASE COMPLETE |
||
3 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
8.2.3.30a.5 Test requirements
Same conformance requirement as in clause 8.2.3.30.
8.2.3.31 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (With active HS-DSCH reception)
8.2.3.31.1 Definition and applicability
All UEs which support FDD or TDD and HS-PDSCH and simultaneous CS domain speech or transparent CS data services and PS services.
8.2.3.31.2 Conformance requirement
If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the UE shall:
1> if the IE "Uplink DPCH Info" is absent, not change its current UL Physical channel configuration;
1> if "DPCH frame offset" is included for one or more RLs in the active set:
2> use its value to determine the beginning of the DPCH frame in accordance with the following:
3> if the received IE "DPCH frame offset" is across the value range border compared to the DPCH frame offset currently used by the UE:
4> consider it to be a request to adjust the timing with 256 chips across the frame border (e.g. if the UE receives value 0 while the value currently used is 38144 consider this as a request to adjust the timing with +256 chips).
3> if after taking into account value range borders, the received IE "DPCH frame offset" corresponds to a request to adjust the timing with a step exceeding 256 chips:
4> set the variable INVALID_CONFIGURATION to TRUE.
3> and the procedure ends.
2> adjust the radio link timing accordingly.
…
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
…
If IE "Timing indication" has the value "initialise", UE shall:
1> execute the Timing Re-initialised hard handover procedure by following the procedure indicated in the subclause relevant to the procedure chosen by the UTRAN.
…
If the UE receives a message in which presence is needed for the IE "Activation time", and the value is other than the default value "Now", the UE shall:
1> at the activation time T:
2> for an HS-DSCH related reconfiguration caused by the received message:
3> select the HS-SCCH subframe boundary immediately before the first HS-SCCH subframe, which entirely falls within the 10 ms frame following T;
3> start using, at that HS-SCCH subframe boundary, the new HS-DSCH configuration in the received message, replacing any old HS-DSCH configuration.
2> for actions, other than a physical channel reconfiguration, caused by the received message:
3> perform the actions for the information elements in the received message as specified elsewhere.
NOTE: An "HS-DSCH related reconfiguration" includes, in particular, reconfigurations that need to be time-aligned with the 2ms subframe of the HS-SCCH, HS-PDSCH and/or HS-DPCCH. For example, start and stop of HS-SCCH reception and serving HS-DSCH cell change.
Reference
3GPP TS 25.331 clause 8.2.2, 8.3.5.1.2, 8.6.3.1
8.2.3.31.3 Test purpose
To confirm that the UE releases a radio bearer according to the received RADIO BEARER RELEASE message while keeping HS-DSCH reception active for a second radio bearer mapped to HS-DSCH.
8.2.3.31.4 Method of test
Initial Condition
System Simulator: 1 cell
UE: PS-DCCH DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports FDD or TDD
– UE supports HS-PDSCH
– UE supports CS domain speech or transparent CS data services and PS services.
Test Procedure
The UE is in cell 1 with only signalling radio bearers established. A PS radio bearer is established mapped to HS-DSCH with HS-DSCH reception activated. Then, a CS radio bearer is established.
The SS transmits a RADIO BEARER RELEASE message to the UE. This message requests the release of the radio bearer mapped to DCH. After the UE receives this message, it releases this radio bearer but keeps the radio bearer mapped to HS-DSCH and continues HS-DSCH reception. Finally the UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC.
SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
SS establishes a PS RAB mapped to HS-DSCH. See below for contents of the RADIO BEARER SETUP message. |
||
2 |
|
SS establishes a CS RAB. |
||
3 |
|
RADIO BEARER RELEASE |
||
4 |
|
RADIO BEARER RELEASE COMPLETE |
The UE releases the CS radio bearer mapped to DCH but keeps the PS radio bearer mapped to HS-DSCH and continues HS-DSCH reception |
|
5 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 1)
Use the same message as specified for " Packet to CELL_DCH / HS-DSCH from CELL_DCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
RAB information for setup |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A10, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
Added or Reconfigured UL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A10, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
Added or Reconfigured DL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A10. |
RADIO BEARER RELEASE (Step 3)(FDD)
Use the same message as specified for “Speech in CS” or "Non speech in CS" in 34.108 except for the following.
Information Element |
Value/remark |
Version |
Added or Reconfigured UL TrCH information |
Not Present |
|
Added or Reconfigured DL TrCH information |
Not Present |
|
Frequency info |
Not present |
|
Maximum allowed UL TX power |
Not present |
|
Downlink information for each radio link list |
||
– Downlink information for each radio link |
||
– Choice mode |
FDD |
|
– Primary CPICH info |
||
– Primary scrambling code |
Ref. to the Default setting in TS 34.108 clause 6.1 (FDD) |
|
– Cell ID |
Not Present |
|
– Serving HS-DSCH radio link indicator |
TRUE |
|
– 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 |
3 |
|
– Spreading factor |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– Code number |
0 |
|
– 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 |
RADIO BEARER RELEASE (Step 3) ( 1.28 Mcps TDD)
Use the same message as specified for “Speech in CS” or "Non speech in CS" in 34.108 except for the following.
Information Element |
Value/remark |
Version |
Added or Reconfigured UL TrCH information |
Not Present |
|
Added or Reconfigured DL TrCH information |
Not Present |
|
Frequency info |
Not present |
|
Maximum allowed UL TX power |
Not present |
8.2.3.31.5 Test requirements
After step 3, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.31a Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (With active HS-DSCH reception) (TDD only)
8.2.3.31a.1 Definition and applicability
All UEs which support TDD and HS-PDSCH and simultaneous CS domain speech or transparent CS data services and PS services.
8.2.3.31a.2 Conformance requirement
If the UE was in CELL_DCH state upon reception of the reconfiguration message and remains in CELL_DCH state, the UE shall:
1> if the IE "Uplink DPCH Info" is absent, not change its current UL Physical channel configuration;
1> if "DPCH frame offset" is included for one or more RLs in the active set:
2> use its value to determine the beginning of the DPCH frame in accordance with the following:
3> if the received IE "DPCH frame offset" is across the value range border compared to the DPCH frame offset currently used by the UE:
4> consider it to be a request to adjust the timing with 256 chips across the frame border (e.g. if the UE receives value 0 while the value currently used is 38144 consider this as a request to adjust the timing with +256 chips).
3> if after taking into account value range borders, the received IE "DPCH frame offset" corresponds to a request to adjust the timing with a step exceeding 256 chips:
4> set the variable INVALID_CONFIGURATION to TRUE.
3> and the procedure ends.
2> adjust the radio link timing accordingly.
…
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
…
If IE "Timing indication" has the value "initialise", UE shall:
1> execute the Timing Re-initialised hard handover procedure by following the procedure indicated in the subclause relevant to the procedure chosen by the UTRAN.
…
If the UE receives a message in which presence is needed for the IE "Activation time", and the value is other than the default value "Now", the UE shall:
1> at the activation time T:
2> for an HS-DSCH related reconfiguration caused by the received message:
3> select the HS-SCCH subframe boundary immediately before the first HS-SCCH subframe, which entirely falls within the 10 ms frame following T;
3> start using, at that HS-SCCH subframe boundary, the new HS-DSCH configuration in the received message, replacing any old HS-DSCH configuration.
2> for actions, other than a physical channel reconfiguration, caused by the received message:
3> perform the actions for the information elements in the received message as specified elsewhere.
NOTE: An "HS-DSCH related reconfiguration" includes, in particular, reconfigurations that need to be time-aligned with the 2ms subframe of the HS-SCCH, HS-PDSCH and/or HS-DPCCH. For example, start and stop of HS-SCCH reception and serving HS-DSCH cell change.
Reference
3GPP TS 25.331 clause 8.2.2, 8.3.5.1.2, 8.6.3.1
8.2.3.31a.3 Test purpose
To confirm that the UE releases a radio bearer according to the received RADIO BEARER RELEASE message while keeping HS-DSCH reception active for a second radio bearer mapped to HS-DSCH.
8.2.3.31a.4 Method of test
Initial Condition
System Simulator: 1 cell configures three carriers, one primary carrier with two secondary carriers.
UE: PS-DCCH DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports TDD
– UE supports HS-PDSCH
– UE supports CS domain speech or transparent CS data services and PS services.
Test Procedure
The UE is in cell 1 with only signalling radio bearers established. A PS radio bearer is established mapped to HS-DSCH with HS-DSCH reception activated. Then, a CS radio bearer is established.
The SS transmits a RADIO BEARER RELEASE message to the UE. This message requests the release of the radio bearer mapped to DCH. After the UE receives this message, it releases this radio bearer but keeps the radio bearer mapped to HS-DSCH and continues HS-DSCH reception. Finally the UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC.
SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
SS establishes a PS RAB mapped to HS-DSCH. See below for contents of the RADIO BEARER SETUP message. |
||
2 |
|
SS establishes a CS RAB. |
||
3 |
|
RADIO BEARER RELEASE |
||
4 |
|
RADIO BEARER RELEASE COMPLETE |
The UE releases the CS radio bearer mapped to DCH but keeps the PS radio bearer mapped to HS-DSCH and continues HS-DSCH reception |
|
5 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 1)
Use the same message as specified for " Packet to CELL_DCH / HS-DSCH from CELL_DCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
RAB information for setup |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A10, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
Added or Reconfigured UL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A10, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
Added or Reconfigured DL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A10. |
RadioBearerSetup-r5-TDD128-add-ext-IEs |
|
-frequencyInfo |
Secondary carrier frequency |
-UpPCHpositionInfo |
22 |
RADIO BEARER RELEASE (Step 3) ( 1.28 Mcps TDD)
Use the same message as specified for “Speech in CS” or "Non speech in CS" in 34.108 except for the following.
Information Element |
Value/remark |
Version |
Added or Reconfigured UL TrCH information |
Not Present |
|
Added or Reconfigured DL TrCH information |
Not Present |
|
Frequency info |
Not present |
|
Maximum allowed UL TX power |
Not present |
|
RadioBearerRelease-r5-TDD128-add-ext-IEs |
||
-frequencyInfo |
Secondary carrier frequency |
|
-UpPCHpositionInfo |
22 |
8.2.3.31a.5 Test requirements
After step 3, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.32 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (Timing re-initialised hard handover to another frequency, with active HS-DSCH reception)
8.2.3.32.1 Definition and applicability
All UEs which support FDD or TDD and HS-PDSCH and simultaneous CS domain speech or transparent CS data services and PS services.
8.2.3.32.2 Conformance requirement
In case the procedure was triggered by reception of a RADIO BEARER RELEASE message, the UE shall:
1> transmit a RADIO BEARER RELEASE COMPLETE as response message on the uplink DCCH using AM RLC.
…
If the UE receives a message in which presence is needed for the IE "Activation time", and the value is other than the default value "Now", the UE shall:
1> at the activation time T:
2> for an HS-DSCH related reconfiguration caused by the received message:
3> select the HS-SCCH subframe boundary immediately before the first HS-SCCH subframe, which entirely falls within the 10 ms frame following T;
3> start using, at that HS-SCCH subframe boundary, the new HS-DSCH configuration in the received message, replacing any old HS-DSCH configuration.
2> for actions, other than a physical channel reconfiguration, caused by the received message:
3> perform the actions for the information elements in the received message as specified elsewhere.
NOTE: An "HS-DSCH related reconfiguration" includes, in particular, reconfigurations that need to be time-aligned with the 2ms subframe of the HS-SCCH, HS-PDSCH and/or HS-DPCCH. For example, start and stop of HS-SCCH reception and serving HS-DSCH cell change.
Reference
3GPP TS 25.331 clause 8.2.2, 8.6.3.1
8.2.3.32.3 Test purpose
To confirm that the UE releases a radio bearer according to the received RADIO BEARER RELEASE message while keeping HS-DSCH reception active for a second radio bearer mapped to HS-DSCH.
8.2.3.32.4 Method of test
Initial Condition
System Simulator: 2 cells–Cells 1 and 6 are active.
UE: PS-DCCH DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports FDD or TDD
– UE supports HS-PDSCH
– UE supports CS domain speech or transparent CS data services and PS services
Test Procedure
The UE is in cell 1 with only signalling radio bearers established. A PS radio bearer is established mapped to HS-DSCH with HS-DSCH reception activated. Then, a CS radio bearer is established.
The SS transmits a RADIO BEARER RELEASE message to the UE. This message requests the release of the CS radio bearer mapped to DCH as well as a timing re-initialised interfrequency hard handover to cell 6. After the UE receives this message, it releases this radio bearer but keeps the radio bearer mapped to HS-DSCH and continues HS-DSCH reception. Finally the UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC in cell 6.
SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
|
SS establishes a PS RAB mapped to HS-DSCH. See below for contents of the RADIO BEARER SETUP message. |
||
2 |
|
SS establishes a CS RAB. |
||
3 |
|
RADIO BEARER RELEASE |
||
4 |
|
RADIO BEARER RELEASE COMPLETE |
The UE releases the CS radio bearer mapped to DCH but keeps the PS radio bearer mapped to HS-DSCH and continues HS-DSCH reception |
|
5 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 1)
Use the same message as specified for " Packet to CELL_DCH / HS-DSCH from CELL_DCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
RAB information for setup |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
Added or Reconfigured UL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
Added or Reconfigured DL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
RADIO BEARER RELEASE (Step 3) (FDD)
Use the same message as specified for “Speech in CS” or "Non speech in CS" in 34.108 except for the following.
Information Element |
Value/remark |
Version |
---|---|---|
New H-RNTI |
‘0101 0101 0101 0101’ |
|
Added or Reconfigured UL TrCH information |
Not Present |
|
Added or Reconfigured DL TrCH information |
Not Present |
|
Frequency info |
||
– UARFCN uplink(Nu) |
Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21] |
|
– UARFCN downlink(Nd) |
Same downlink UARFCN as used for cell 6 |
|
Maximum allowed UL TX power |
Not present |
|
CHOICE channel requirement |
Uplink DPCH info |
|
– Uplink DPCH power control info |
||
– DPCCH power offset |
-40 (-80 dB) |
|
– PC Preamble |
1 frame |
|
– SRB delay |
7 frames |
|
– Power Control Algorithm |
Algorithm1 |
|
– TPC step size |
0 (1 dB) |
|
– ACK |
6 |
|
– NACK |
6 |
|
– Ack-Nack repetition factor |
2 |
|
– Scrambling code type |
Long |
|
– Scrambling code number |
0 (0 to 16777215) |
|
– Number of DPDCH |
Not Present(1) |
|
– spreading factor |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– TFCI existence |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– Number of FBI bit |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– Puncturing Limit |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
Downlink HS-PDSCH Information |
||
– HS-SCCH Info |
||
– CHOICE mode |
FDD |
|
– DL Scrambling Code |
||
– HS-SCCH Channelisation Code Information |
||
– HS-SCCH Channelisation Code |
7 |
|
– Measurement Feedback Info |
||
– CHOICE mode |
FDD |
|
– Measurement Power Offset |
12 (6 dB) |
|
– CQI Feedback cycle, k |
4 ms |
|
– CQI repetition factor |
1 |
|
– CQI |
5 (corresponds to 0dB in relative power offset) |
|
– CHOICE mode |
FDD (no data) |
|
Downlink information common for all radio links |
||
– Downlink DPCH info common for all RL |
||
– Timing indication |
Initialise |
|
– CFN-targetSFN frame offset |
0 |
|
– Downlink DPCH power control information |
Not Present |
|
– Downlink rate matching restriction information |
Not Present |
|
– Spreading factor |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– Fixed or flexible position |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– TFCI existence |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– CHOICE SF |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– DPCH compressed mode info |
Not present |
|
– TX Diversity mode |
Not Present |
|
– SSDT information |
Not Present |
R99 and Rel-4 only |
– Default DPCH Offset Value |
Arbitrary set to value 0..306688 by step of 512 |
|
– MAC-hs reset indicator |
TRUE |
|
Downlink information for each radio link list |
||
– Downlink information for each radio link |
||
– Choice mode |
FDD |
|
– Primary CPICH info |
||
– Primary scrambling code |
Set to the scrambling code for cell 6 |
|
– Cell ID |
Not Present |
|
– Serving HS-DSCH radio link indicator |
TRUE |
|
– 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 |
3 |
|
– Spreading factor |
Reference to TS 34.108 clause 6.10 Parameter Set |
|
– Code number |
0 |
|
– 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 |
RADIO BEARER RELEASE (Step 3) (1.28Mcps TDD)
Use the same message as specified for “Speech in CS” or "Non speech in CS" in 34.108 except for the following.
Information Element |
Value/remark |
Version |
---|---|---|
New H-RNTI |
‘0101 0101 0101 0101’ |
|
Added or Reconfigured UL TrCH information |
Not Present |
|
Added or Reconfigured DL TrCH information |
Not Present |
|
Frequency info |
||
– Choice mode |
TDD |
|
– UARFCN (Nt) |
Same UARFCN as used for cell 6 |
|
Maximum allowed UL TX power |
Not present |
|
CHOICE channel requirement |
Uplink DPCH info |
|
– Uplink DPCH power control info |
||
– CHOICE mode |
TDD |
|
– CHOICE TDD option |
1.28 Mcps TDD |
|
– PRXPDPCHdes |
-80dB |
|
– CHOICE UL OL PC info |
Individually Signalled |
|
– CHOICE TDD option |
1.28 Mcps TDD |
|
– TPC step size |
1dB |
|
– Primary CCPCH Tx Power |
20 |
|
Downlink HS-PDSCH Information |
||
– HS-SCCH Info |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9 |
|
– Measurement Feedback Info |
||
– CHOICE mode |
TDD (no data) |
|
– CHOICE mode |
TDD |
|
– CHOICE TDD option |
1.28 Mcps TDD |
|
– HS-PDSCH Midamble Configuration |
||
– Midamble Allocation Mode |
Default midamble |
|
– Midamble Configuration |
8 |
|
– Midamble Shift |
Not present |
|
Downlink information common for all radio links |
||
– Downlink DPCH info common for all RL |
||
– Timing indication |
Initialise |
|
– CFN-targetSFN frame offset |
0 |
|
– Downlink DPCH power control information |
Not Present |
|
– Choice mode |
TDD |
|
– Choice TDD Option |
1.28 Mcps TDD |
|
– TSTD indicator |
FALSE |
R99 and Rel-4 only |
– Default DPCH Offset Value |
Arbitrary set to value 0..306688 by step of 512 |
|
– MAC-hs reset indicator |
TRUE |
|
Downlink information for each radio link list |
||
– Downlink information for each radio link |
||
– Choice mode |
TDD |
|
– Primary CCPCH info |
||
– Choice mode |
TDD |
|
– Choice TDD Option |
1.28 Mcps TDD |
|
– TSTD indicator |
FALSE |
|
– Cell parameters ID |
Ref. to the Default setting for cell 6 in TS 34.108 clause 6.1 (TDD) |
|
– SCTD indicator |
FALSE |
8.2.3.32.5 Test requirements
After step 3, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message using AM RLC in cell 6.
8.2.3.33 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (stop of HS-DSCH reception with frequency modification)
8.2.3.33.1 Definition and applicability
All UEs which support FDD or TDD and HS-PDSCH and simultaneous CS domain speech or transparent CS data services and PS services.
8.2.3.33.2 Conformance requirement
The variable HS_DSCH_RECEPTION shall be set to "TRUE" only when all the following conditions are met:
1> the UE is in CELL_DCH state;
1> the variable H_RNTI is set;
1> the UE has a stored IE "HS-SCCH info";
1> for FDD:
2> one of the radio links in the active set is configured as the serving HS-DSCH radio link;
2> the UE has stored the following IEs:
– IE "Measurement Feedback Info";
– IE "Uplink DPCH Power Control Info" including stored ACK, NACK and Ack-NACK Repetition factor;
– IE "HARQ info".
1> for 3.84 Mcps TDD or 7.68 Mcps TDD, the UE has stored the IE "HS-PDSCH Timeslot Configuration" and either of the following conditions are met:
2> a dedicated physical channel is allocated to the UE in the downlink;
2> the UE has stored Dhs-sync.
1> for 1.28 Mcps TDD, the UE has stored the following IE:
– IE "HS-PDSCH Midamble Configuration".
1> there is at least one RB mapped to HS-DSCH;
1> at least for one of the RB’s mapped to HS-DSCH, there is at least one MAC-hs queue (including the IE "MAC-d PDU size Info") configured for the concerning MAC-d flow;
NOTE: To enable or disable HS-DSCH reception, the UTRAN has the possibility to add/remove the concerning HS-DSCH related RB mapping options, add/remove the concerning MAC-d flows or, for FDD, add/remove the serving HS-DSCH radio link.
If any of the above conditions is not met and the variable HS_DSCH_RECEPTION is set to TRUE, the UE shall:
1> set the variable HS_DSCH_RECEPTION to FALSE;
1> stop any HS_SCCH reception procedures;
1> stop any HS-DSCH reception procedures;
1> clear the variable H_RNTI and remove any stored H-RNTI;
1> act as if the IE "MAC-hs reset indicator" is received and set to TRUE;
1> release all HARQ resources;
1> no long consider any radio link to be the HS-DSCH serving radio link.
NOTE: If configured for HS-DSCH and not explicitly indicated as being cleared, the UE will have still stored the IEs "HARQ info", "Added or Reconfigured MAC-d flow", "RB mapping Info" and "Downlink HS-PDSCH information".
…
Whenever the variable HS_DSCH_RECEPTION is set to FALSE, the UE shall:
1> not perform HS_SCCH reception procedures;
1> not perform HS-DSCH reception procedures.
Reference
3GPP TS 25.331 clauses 8.5.25.
8.2.3.33.3 Test purpose
To confirm that the UE stops HS-DSCH reception when UE releases PS RAB according to the received RADIO BEARER RELEASE message.
8.2.3.33.4 Method of test
Initial Condition
System Simulator: 2 cells – Cell 1 is active and cell 6 is inactive
UE: PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports FDD or TDD
– UE supports HS-PDSCH
– UE supports CS domain speech or transparent CS data services and PS service
Test Procedure
The UE is in CELL_DCH state and only signalling radio bearers have been established. SS initiates P25 to make the UE to move to state 6-17 as specified in TS 34.108 clause 7.4. The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH established. The SS initiates P24 to set up CS RAB.
Then SS transmits a RADIO BEARER RELEASE message to the UE. The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
0 |
|
P25 |
See below for the specific message content used in RADIO BEARER SETUP message. (Step 0) |
|
1 |
|
P24 |
SS establishes CS RAB. |
|
2 |
|
RADIO BEARER RELEASE |
SS releases PS RAB. |
|
3 |
|
RADIO BEARER RELEASE COMPLETE |
||
4 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 0)
Use the same message as specified for " Packet to CELL_DCH / HS-DSCH from CELL_DCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
RAB information for setup |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
Added or Reconfigured UL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
Added or Reconfigured DL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
RADIO BEARER RELEASE (Step 2) (FDD)
Use the same message as specified for "Packet to CELL_DCH from CELL_DCH / HS-DSCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
Deleted UL TrCH Information |
|
– Uplink transport channel type |
DCH |
– Transport channel identity |
4 |
Added or Reconfigured UL TrCH information |
Not Present |
Deleted DL TrCH Information |
|
– Downlink transport channel type |
DCH |
– Transport channel identity |
9 |
Added or Reconfigured DL TrCH information |
Not Present |
Frequency info |
|
– UARFCN uplink (Nu) |
Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21] |
– UARFCN downlink (Nd) |
Same downlink UARFCN as used for cell 6 |
Downlink information for each radio links |
|
– Primary CPICH info |
|
– Primary Scrambling Code |
350 |
– DPCH frame offset |
The Value is calculated based on internal SS timing difference |
RADIO BEARER RELEASE (Step 2) (1.28Mcps TDD)
Use the same message as specified for "Packet to CELL_DCH from CELL_DCH / HS-DSCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
Deleted UL TrCH Information |
|
– Uplink transport channel type |
DCH |
– Transport channel identity |
4 |
Added or Reconfigured UL TrCH information |
Not Present |
Deleted DL TrCH Information |
|
– Downlink transport channel type |
DCH |
– Transport channel identity |
9 |
Added or Reconfigured DL TrCH information |
Not Present |
Frequency info |
|
– Choice mode |
TDD |
– UARFCN (Nt) |
Same UARFCN as used for cell 6 |
Downlink information for each radio link |
|
– Choice mode |
TDD |
– Primary CCPCH info |
|
– Choice mode |
TDD |
– Choice TDD Option |
1.28 Mcps TDD |
– TSTD indicator |
FALSE |
– Cell parameters ID |
Same Cell parameters ID as used for cell 6 |
– SCTD indicator |
FALSE |
8.2.3.33.5 Test requirements
After step 2, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.34 Radio Bearer Release for transition from CELL_DCH to CELL_FACH: Success (stop of HS-DSCH reception with frequency modification)
8.2.3.34.1 Definition and applicability
All UEs which support FDD or TDD and HS-PDSCH and simultaneous CS domain speech or transparent CS data services and PS services.
8.2.3.34.2 Conformance requirement
If after state transition the UE leaves CELL_DCH state, the UE shall, after the state transition:
1> stop any HS-DSCH reception procedures according to the stored HS-PDSCH configuration;
1> clear any stored HS-PDSCH configuration;
1> remove any H-RNTI stored;
1> clear the variable H_RNTI;
1> set the variable HS_DSCH_RECEPTION to FALSE.
Reference
3GPP TS 25.331 clauses 8.2.2.3.
8.2.3.34.3 Test purpose
To confirm that the UE stops HS-DSCH reception when UE releases CS RAB according to the received RADIO BEARER RELEASE message.
8.2.3.34.4 Method of test
Initial Condition
System Simulator: 2 cells – Cell 1 is active and cell 6 is inactive
UE: PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports FDD or TDD
– UE supports HS-PDSCH
– UE supports CS domain speech or transparent CS data services and PS services
Test Procedure
Table 8.2.3.34
Parameter |
Unit |
Cell 1 |
Cell 6 |
||
T0 |
T1 |
T0 |
T1 |
||
UTRA RF Channel Number |
Mid Range Test Frequency (f1) |
High Range Test Frequency (f2) |
|||
CPICH Ec(FDD) |
dBm/3.84MHz |
-60 |
-70 |
-70 |
-60 |
P-CCPCH RSCP (TDD) |
dBm |
-60 |
-70 |
-70 |
-60 |
Table 8.2.3.34 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution.
The SS has configured its downlink transmission power settings according to columns "T0" in table 8.2.3.34. The UE is in CELL_DCH state and only signalling radio bearers have been established. SS initiates P25 to make the UE to move to state 6-17 as specified in TS 34.108 clause 7.4. The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH established. The SS initiates P24 to set up CS RAB.
Then SS switches its downlink transmission power settings to columns "T1" and transmits a RADIO BEARER RELEASE message to the UE. The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC. SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
0 |
|
P25 |
See below for the specific message content used in RADIO BEARER SETUP message (Step0). |
|
1 |
|
P24 |
SS establishes CS RAB |
|
1a |
SS |
The SS switches its downlink transmission power settings to columns "T1" in table 8.2.3.34. |
||
2 |
|
RADIO BEARER RELEASE |
SS releases CS RAB. |
|
3 |
|
RADIO BEARER RELEASE COMPLETE |
||
4 |
|
CALL C.2 |
If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 0)
Use the same message as specified for " Packet to CELL_DCH / HS-DSCH from CELL_DCH in PS" in 34.108.Use the same message as specified for " Packet to CELL_DCH / HS-DSCH from CELL_DCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
RAB information for setup |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
Added or Reconfigured UL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
Added or Reconfigured DL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A9, except for the following |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
RADIO BEARER RELEASE (Step 2) (FDD)
Use the same message as specified for "Speech to CELL_FACH from CELL_DCH in CS" or "Non speech to CELL_FACH from CELL_DCH in CS" in 34.108, except for the following:
Information Element |
Value/remark |
Frequency info |
|
– UARFCN uplink (Nu) |
This IE should be present, if the default duplex distance defined for the operating frequency band is not used |
– UARFCN downlink (Nd) |
Same downlink UARFCN as used for cell 6 |
RADIO BEARER RELEASE (Step 2) (1.28 Mcps TDD)
Use the same message as specified for "Speech to CELL_FACH from CELL_DCH in CS" or "Non speech to CELL_FACH from CELL_DCH in CS" in 34.108, except for the following:
Information Element |
Value/remark |
Frequency info |
|
– Choice mode |
TDD |
– UARFCN (Nt) |
Same UARFCN as used for cell 6 |
8.2.3.34.5 Test requirements
After step 2, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.35 Radio Bearer Release for transition from CELL_DCH to CELL_PCH: Success (stop of HS-DSCH reception)
8.2.3.35.1 Definition and applicability
All UEs which support FDD or TDD, HS-PDSCH and simultaneous CS domain speech or transparent CS data services and PS services.
8.2.3.35.2 Conformance requirement
If the new state is CELL_PCH, the response message shall be transmitted using the old configuration before the state transition, but the new C-RNTI shall be used if the IE "New C-RNTI" was included in the received reconfiguration message, and the UE shall:
1> when RLC has confirmed the successful transmission of the response message:
…
- enter the new state (CELL_PCH);
…
If the UE receives a message in which presence is needed for the IE "Activation time", and the value is other than the default value "Now", the UE shall:
1> at the activation time T:
2> for an HS-DSCH related reconfiguration caused by the received message:
3> select the HS-SCCH subframe boundary immediately before the first HS-SCCH subframe, which entirely falls within the 10 ms frame following T;
3> start using, at that HS-SCCH subframe boundary, the new HS-DSCH configuration in the received message, replacing any old HS-DSCH configuration.
2> for actions, other than a physical channel reconfiguration, caused by the received message:
3> perform the actions for the information elements in the received message as specified elsewhere.
NOTE: An "HS-DSCH related reconfiguration" includes, in particular, reconfigurations that need to be time-aligned with the 2ms subframe of the HS-SCCH, HS-PDSCH and/or HS-DPCCH. For example, start and stop of HS-SCCH reception and serving HS-DSCH cell change.
…
The variable HS_DSCH_RECEPTION shall be set to "TRUE" only when all the following conditions are met:
1> the UE is in CELL_DCH state;
1> the variable H_RNTI is set;
1> the UE has a stored IE "HS-SCCH info";
1> the UE has a stored IE "HARQ info";
1> for FDD:
2> one of the radio links in the active set is configured as the serving HS-DSCH radio link;
2> the UE has stored the following IEs:
– IE "Measurement Feedback Info";
– IE "Uplink DPCH Power Control Info" including stored ACK, NACK and Ack-NACK Repetition factor;
1> for 1.28 Mcps TDD, the UE has stored the following IE:
– IE "HS-PDSCH Midamble Configuration".
…
Whenever the variable HS_DSCH_RECEPTION is set to TRUE, the UE shall:
1> perform HS_SCCH reception procedures according to the stored HS-SCCH configuration as stated in:
2> subclause 8.6.6.33 for the IE "HS-SCCH Info".
1> perform HS-DSCH reception procedures according to the stored HS-PDSCH configuration as stated in:
2> subclause 8.6.3.1b for the IE "H-RNTI";
2> subclause 8.6.5.6b for the IE "HARQ info";
2> subclause 8.6.6.34 for the IE "Measurement Feedback Info".
Reference
3GPP TS 25.331 clauses 8.2.2.4, 8.6.3.1,8.5.25
8.2.3.35.3 Test purpose
To confirm that the UE releases CS bearer and stops receiving the HS-DSCH reception according to the received RADIO BEARER RELEASE message.
8.2.3.35.4 Method of test
Initial Condition
System Simulator: 1 cell.
UE: PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports FDD or TDD
– UE supports HS-PDSCH
– UE supports both CS domain speech or transparent CS data services and PS services
Test Procedure
The UE is in CELL_DCH state and only signalling radio bearers have been established. SS initiates P25 to make the UE to move to state 6-17 as specified in TS 34.108 clause 7.4. The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH established. The SS initiates P24 to set up CS RAB.
Then SS transmits a RADIO BEARER RELEASE message to the UE. This message requests to release CS bearer and CS Signalling Connection, stop receiving the HS-DSCH reception and move to CELL_PCH state. After the UE receives this message, it configures them. Finally the UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC. SS calls for generic procedure C.4 to check that UE is in CELL_PCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
1 |
ßà |
P25 |
See below for the specific message content used in RADIO BEARER SETUP message (Step 1) |
|
2 |
ßà |
P24 |
SS establishes CS RAB. |
|
3 |
ß |
RADIO BEARER RELEASE |
SS releases CS RAB and CS Signalling Connection |
|
4 |
à |
RADIO BEARER RELEASE COMPLETE |
||
5 |
ßà |
CALL C.4 |
If the test result of C.4 indicates that UE is in CELL_PCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 1)
Use the same message as specified for “Packet to CELL_DCH /HS-DSCH from CELL_DCH in PS ” in TS 34.108, except for the followings;
Information Element |
Value/remark |
RAB information for setup |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A10. |
– UL Transport channel identity |
4(speech) or 2(other cs services) |
Added or Reconfigured DL TrCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A10. |
– UL Transport channel identity |
4(speech) or 2(other cs services) |
RADIO BEARER RELEASE (Step 3)(FDD)
Use the same message as specified for “Speech to CELL_FACH from CELL_DCH in CS” or "Non Speech to CELL_FACH from CELL_DCH in CS" in TS 34.108, except for the followings;
Information Element |
Value/remark |
Activation time |
Not present |
RRC state indicator |
CELL_PCH |
UTRAN DRX cycle length coefficient |
3 |
Signalling Connection release indication |
CS domain |
Frequency info |
Not present |
Downlink information for each radio link list |
|
– Primary CPICH info |
|
– Primary scrambling code |
100 |
RADIO BEARER RELEASE (Step 3) ( 1.28 Mcps TDD)
Use the same message as specified for “Speech to CELL_FACH from CELL_DCH in CS” or "Non Speech to CELL_FACH from CELL_DCH in CS" in TS 34.108, except for the followings;
Information Element |
Value/remark |
Activation time |
Not present |
RRC state indicator |
CELL_PCH |
UTRAN DRX cycle length coefficient |
3 |
Signalling Connection release indication |
CS domain |
Frequency info |
Not present |
Downlink information for each radio link list |
|
– Downlink information for each radio link |
|
– CHOICE mode |
TDD |
– Cell parameters ID |
Set to the Cell parameters ID for cell 1 |
8.2.3.35.5 Test requirements
After step 3, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.36 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (frequency modification, stop of E-DCH transmission)
8.2.3.36.1 Definition and applicability
All UEs which support FDD and speech and HS-PDSCH and E-DCH or all UEs which support TDD and HS-PDSCH and E-PUCH.
8.2.3.36.2 Conformance requirement
The variable E_DCH_TRANSMISSION shall be set to "TRUE" only when all the following conditions are met:
1> the UE is in CELL_DCH state;
1> the variable E_RNTI includes either the Primary E-RNTI or the Secondary E-RNTI or both the Primary and the Secondary E-RNTI;
1> For FDD:
2> the UE has stored the following IEs:
– IE "E-DCH Transmission Time Interval";
– IE "HARQ info for E-DCH";
– IE "E-DCH information", including the IE "E-DPCCH info" and the IE "E-DPDCH info".
– one of the radio links in the active set is configured as the serving E-DCH radio link, and for this radio link the UTRAN has configured the IE "E-HICH configuration" and the IE "E-AGCH info".
1> For TDD:
2> for non-scheduled transmission, the UE has stored the following IEs:
– IE "HARQ info for E-DCH";
– IE "E-DCH information", including the IE "E-PUCH info";
– IE "Non-scheduled transmission grant info";
2> for scheduled transmission, the UE has stored the following IEs:
– IE "HARQ info for E-DCH";
– IE "E-DCH information", including the IE "E-RUCCH info" and the IE "E-PUCH info";
– IE "E-HICH info";
– IE "E-AGCH info".
1> there is at least one logical channel mapped to E-DCH for which:
2> the corresponding E-DCH MAC-d flow is configured, i.e. the IEs "E-DCH MAC-d flow power offset" and "E-DCH MAC-d flow maximum number of retransmissions", and the transmission grant type are configured.
If any of the above conditions is not met and the variable E_DCH_TRANSMISSION is set to TRUE, the UE shall:
1> set the variable E_DCH_TRANSMISSION to FALSE;
1> stop any E-AGCH, E-HICH and E-RGCH reception procedures;
1> For FDD:
2> stop any E-RGCH reception procedures.
1> For FDD:
2> stop any E-DPCCH and E-DPDCH transmission procedures.
1> For TDD:
2> stop any E-RUCCH and E-PUCH transmission procedures.
1> clear the variable E_RNTI;
1> release all E-DCH HARQ resources;
1> no longer consider any radio link to be the serving E-DCH radio link.
Whenever the variable E_DCH_TRANSMISSION is set to TRUE, the UE shall:
1>For FDD:
2> perform E_AGCH reception procedures according to the stored E_AGCH configuration as stated in:
3> subclause 8.6.3.14 for the IE "New Primary E-RNTI" and the IE "New Secondary E-RNTI".
2> perform E-HICH reception procedures for all radio links in the E-DCH active set;
2> perform E-RGCH reception procedures for all radio links in the active set for which an E-RGCH configuration has been provided;
2> perform E-DPCCH transmission procedures according to the stored E-DPCCH configuration as stated in:
3> subclause 8.6.6.37 for the IE "E-DPCCH Info".
2> perform E-DPDCH transmission procedures according to the stored E-DPDCH configuration as stated in:
3> subclause 8.6.5.16 for the IE "E-DCH Transmission Time Interval";
3> subclause 8.6.5.17 for the IE "HARQ info for E-DCH";
3> subclause 8.6.6.37 for the IE "E-DPDCH Info".
2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Non-scheduled transmission grant info" is configured shall:
3> obey the scheduling and size restrictions as specified for that MAC-d flow (see subclause 8.6.5.18).
2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Scheduled transmission grant info" is configured shall:
3> be performed in accordance with the received scheduling grant on E-AGCH/E-RGCH (see [15]); and
3> obey the scheduling restrictions as specified for scheduled transmissions (see subclause 8.6.6.37).
1>For TDD:
2> if scheduled transmission is configured, perform E-AGCH reception procedures according to the stored E_AGCH configuration as stated in:
3> subclause 8.6.3.14 for the IE "New Primary E-RNTI".
2> Perform E-HICH reception;
2> for 3.84/7.68 Mcps TDD, perform E-RUCCH transmission procedures according to the stored E-RUCCH configuration as stated in:
3> subclause 8.6.6.37 for the IE "E-RUCCH Info".
2> for 1.28 Mcps TDD, if scheduled transmission is configured, perform E-RUCCH transmission procedure according to the stored PRACH configuration (see [60]) and the stored E-RUCCH configuration as stated in:
3> subclause 8.6.6.37 for the IE "E-RUCCH Info".
NOTE 1: The PRACH configuration is signalled directly to the UE in "E-RUCCH Info" IE in case of E-DCH serving cell change.
2> Perform E-PUCH transmission procedures according to the stored E-PUCH configuration as stated in:
3> subclause 8.6.6.37 for the IE "E-PUCH Info".
2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Non-scheduled transmission grant info" is configured shall:
3> obey the scheduling and size restrictions as specified for that MAC-d flow (see subclause 8.6.5.18).
2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Scheduled transmission grant info" is configured shall:
3> be performed in accordance with the received scheduling grant on E-AGCH (see [15]); and
3> obey the scheduling restrictions as specified for scheduled transmissions (see subclause 8.6.6.37).
2> obtain and format the appropriate information on E-UCCH (see [15]). For 1.28 Mcps TDD, when performing transmission on signalling radio bearer before RAB has been established, the UE shall use the lowest E-DCH capability category, as specified in [35], to signal the UL control information on E-UCCH.
NOTE 2: For 1.28 Mcps TDD, when performing transmission on signalling radio bearer before RAB has been established, UTRAN should use the lowest E-DCH capability category when performing configuration, scheduling and reading the control information on E-UCCH, as it is not possible for Node B to be aware of the UE’s E-DCH capability category during this period.
Whenever the variable E_DCH_TRANSMISSION is set to FALSE, the UE shall:
1> not perform E-AICH, E-HICH and E-RGCH reception procedures;
1> not perform E-DPCCH and E-DPDCH transmission procedures.
Reference
3GPP TS 25.331 clause 8.5.28
8.2.3.36.3 Test purpose
To confirm that the UE releases a radio bearer mapped on E-DCH / HS-DSCH and stops E-DCH transmission / HS-DSCH reception according to the received RADIO BEARER RELEASE message with frequency modification.
8.2.3.36.4 Method of test
Initial Condition
System Simulator: 2 cells–Cells 1 and 6 are active.
UE: PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports FDD or TDD
– UE supports CS speech
– UE supports HS-PDSCH
– UE supports E-DPDCH(FDD) or E-PUCH (1.28Mcps TDD)
Test Procedure
The UE is in CELL_DCH state and only signalling radio bearers have been established. SS initiates P26 to make the UE to move to state 6-18 as specified in TS 34.108 clause 7.4. The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH and E-DCH established. The SS initiates P24 to set up CS speech RAB.
Then SS transmits a RADIO BEARER RELEASE message to the UE. The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
0 |
|
P26 |
See below for the specific message content used in RADIO BEARER SETUP message. (Step 0) |
|
1 |
|
P24 |
SS establishes CS speech RAB. |
|
2 |
|
RADIO BEARER RELEASE |
SS releases PS RAB. |
|
3 |
|
RADIO BEARER RELEASE COMPLETE |
||
4 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 0) (FDD)
Use the same message as specified for "Packet to CELL_DCH / E-DCH / HS-DSCH using three multiplexing options (3/3) and SRBs mapped on DCH/DCH" in 34.108, except for the following.
Information Element |
Value/remark |
– RAB information for setup |
|
– RB mapping info |
|
– Information for each multiplexing option |
3 RBMuxOptions |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– Logical channel identity |
Not Present |
– CHOICE RLC size list |
Configured |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
– DL DSCH Transport channel identity |
Not Present |
– DL HS-DSCH MAC-d flow identity |
Not Present |
– Logical channel identity |
Not Present |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
E-DCH |
– Logical channel identity |
10 |
– E-DCH MAC-d flow identity |
2 |
– DDI |
5 |
– RLC PDU size list |
1 RLC PDU size |
– RLC PDU size |
336 bits |
– Include in scheduling info |
TRUE |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
HS-DSCH |
– DL DCH Transport channel identity |
Not Present |
– DL DSCH Transport channel identity |
Not Present |
– DL HS-DSCH MAC-d flow identity |
0 |
– Logical channel identity |
Not Present |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
RACH |
– UL Transport channel identity |
Not Present |
– Logical channel identity |
10 |
– CHOICE RLC size list |
Explicit list |
– RLC size index |
Reference to clause 6 Parameter Set |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
FACH |
– DL DCH Transport channel identity |
Not Present |
– DL DSCH Transport channel identity |
Not Present |
– Logical channel identity |
10 |
Added or Reconfigured UL TrCH information |
1 E-DCH added, 1 DCH added, 1 DCH reconfigured |
– Uplink transport channel type |
E-DCH |
– CHOICE UL parameters |
E-DCH |
– E-DCH Transmission Time Interval |
10 ms |
– HARQ info for E-DCH |
|
– HARQ RV Configuration |
rvtable |
– Added or reconfigured E-DCH MAC-d flow |
|
– E-DCH MAC-d flow identity |
2 |
– E-DCH MAC-d flow power offset |
0 |
– E-DCH MAC-d flow maximum number of retransmissions |
7 |
– E-DCH MAC-d flow multiplexing list |
Not Present |
– CHOICE transmission grant type |
Scheduled grant info |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– TFS |
|
– CHOICE Transport channel type |
Dedicated transport channels |
– Dynamic Transport format information |
|
– RLC Size |
Reference to clause 6.10 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.10 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.10 Parameter Set |
– Type of channel coding |
Reference to clause 6.10 Parameter Set |
– Coding Rate |
Reference to clause 6.10 Parameter Set |
– Rate matching attribute |
Reference to clause 6.10 Parameter Set |
– CRC size |
Reference to clause 6.10 Parameter Set |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
5 |
– TFS |
|
– CHOICE Transport channel type |
|
– Dynamic Transport format information |
|
– RLC Size |
Reference to clause 6.10 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.10 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.10 Parameter Set |
– Type of channel coding |
Reference to clause 6.10 Parameter Set |
– Coding Rate |
Reference to clause 6.10 Parameter Set |
– Rate matching attribute |
Reference to clause 6.10 Parameter Set |
– CRC size |
Reference to clause 6.10 Parameter Set |
Added or Reconfigured DL TrCH information |
3 TrCHs (DCH for DCCH and DCH plus HS-DSCH for DTCH) |
– Downlink transport channel type |
DCH |
– DL Transport channel identity |
10 |
– CHOICE DL parameters |
Same as UL |
– Uplink transport channel type |
DCH |
– UL TrCH identity |
5 |
– DCH quality target |
|
– BLER Quality value |
-20 (-2.0) |
– Downlink transport channel type |
DCH |
– DL Transport channel identity |
9 |
– CHOICE DL parameters |
Explicit |
– TFS |
|
– CHOICE Transport channel type |
Dedicated transport channel |
– Dynamic transport format information |
|
– RLC Size |
Reference to clause 6.10 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Dynamic transport format information |
|
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.10 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.10 Parameter Set |
– Type of channel coding |
Reference to clause 6.10 Parameter Set |
– Coding Rate |
Reference to clause 6.10 Parameter Set |
– Rate matching attribute |
Reference to clause 6.10 Parameter Set |
– CRC size |
Reference to clause 6.10 Parameter Set |
– DCH quality target |
|
– BLER Quality value |
-20 (-2.0) |
– Downlink transport channel type |
HS-DSCH |
– DL Transport channel identity |
Not Present |
– CHOICE DL parameters |
HS-DSCH |
– HARQ Info |
|
– Number of Processes |
Reference to clause 6.10.2.4.5 Parameter Set |
– CHOICE Memory Partitioning |
Implicit |
– Added or reconfigured MAC-d flow |
|
– MAC-hs queue to add or reconfigure list |
(one queue) |
– MAC-hs queue Id |
0 |
– MAC-d Flow Identity |
0 |
– T1 |
50 |
– MAC-hs window size |
16 |
– MAC-d PDU size Info |
|
– MAC-d PDU size |
336 |
– MAC-d PDU size index |
0 |
– MAC-hs queue to delete list |
Not Present |
– DCH quality target |
Not Present |
RADIO BEARER SETUP (Step 0)( 1.28Mcps TDD)
Use the same message as specified for "Packet to CELL_DCH / E-DCH / HS-DSCH using three multiplexing options (3/3) and SRBs mapped on DCH/DCH" in 34.108, except for the following.
Information Element |
Value/remark |
– RAB information for setup |
|
– RB mapping info |
|
– Information for each multiplexing option |
3 RBMuxOptions |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– Logical channel identity |
Not Present |
– CHOICE RLC size list |
Configured |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
– DL DSCH Transport channel identity |
Not Present |
– DL HS-DSCH MAC-d flow identity |
Not Present |
– Logical channel identity |
Not Present |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
E-DCH |
– Logical channel identity |
10 |
– E-DCH MAC-d flow identity |
2 |
– DDI |
5 |
– RLC PDU size list |
1 RLC PDU size |
– RLC PDU size |
336 bits |
– Include in scheduling info |
TRUE |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
HS-DSCH |
– DL DCH Transport channel identity |
Not Present |
– DL DSCH Transport channel identity |
Not Present |
– DL HS-DSCH MAC-d flow identity |
0 |
– Logical channel identity |
Not Present |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
RACH |
– UL Transport channel identity |
Not Present |
– Logical channel identity |
10 |
– CHOICE RLC size list |
Explicit list |
– RLC size index |
Reference to clause 6 Parameter Set |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
FACH |
– DL DCH Transport channel identity |
Not Present |
– DL DSCH Transport channel identity |
Not Present |
– Logical channel identity |
10 |
Added or Reconfigured UL TrCH information |
1 E-DCH added, 1 DCH added, 1 DCH reconfigured |
– Uplink transport channel type |
E-DCH |
– CHOICE UL parameters |
E-DCH |
– E-DCH Transmission Time Interval |
5 ms |
– HARQ info for E-DCH |
|
– HARQ RV Configuration |
rvtable |
– Added or reconfigured E-DCH MAC-d flow |
|
– E-DCH MAC-d flow identity |
2 |
– E-DCH MAC-d flow power offset |
0 |
– E-DCH MAC-d flow maximum number of retransmissions |
7 |
– E-DCH MAC-d flow multiplexing list |
Not Present |
– CHOICE transmission grant type |
Scheduled grant info |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– TFS |
|
– CHOICE Transport channel type |
Dedicated transport channels |
– Dynamic Transport format information |
|
– RLC Size |
Reference to clause 6.11 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.11 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.11 Parameter Set |
– Type of channel coding |
Reference to clause 6.11 Parameter Set |
– Coding Rate |
Reference to clause 6.11 Parameter Set |
– Rate matching attribute |
Reference to clause 6.11 Parameter Set |
– CRC size |
Reference to clause 6.11 Parameter Set |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
5 |
– TFS |
|
– CHOICE Transport channel type |
|
– Dynamic Transport format information |
|
– RLC Size |
Reference to clause 6.11 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.11 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.11 Parameter Set |
– Type of channel coding |
Reference to clause 6.11 Parameter Set |
– Coding Rate |
Reference to clause 6.11 Parameter Set |
– Rate matching attribute |
Reference to clause 6.11 Parameter Set |
– CRC size |
Reference to clause 6.11 Parameter Set |
Added or Reconfigured DL TrCH information |
3 TrCHs (DCH for DCCH and DCH plus HS-DSCH for DTCH) |
– Downlink transport channel type |
DCH |
– DL Transport channel identity |
10 |
– CHOICE DL parameters |
Same as UL |
– Uplink transport channel type |
DCH |
– UL TrCH identity |
5 |
– DCH quality target |
|
– BLER Quality value |
-20 (-2.0) |
– Downlink transport channel type |
DCH |
– DL Transport channel identity |
9 |
– CHOICE DL parameters |
Explicit |
– TFS |
|
– CHOICE Transport channel type |
Dedicated transport channel |
– Dynamic transport format information |
|
– RLC Size |
Reference to clause 6.11 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Dynamic transport format information |
|
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.11 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.11 Parameter Set |
– Type of channel coding |
Reference to clause 6.11 Parameter Set |
– Coding Rate |
Reference to clause 6.11 Parameter Set |
– Rate matching attribute |
Reference to clause 6.11 Parameter Set |
– CRC size |
Reference to clause 6.11 Parameter Set |
– DCH quality target |
|
– BLER Quality value |
-20 (-2.0) |
– Downlink transport channel type |
HS-DSCH |
– DL Transport channel identity |
Not Present |
– CHOICE DL parameters |
HS-DSCH |
– HARQ Info |
|
– Number of Processes |
Reference to clause 6.11.2.4.5 Parameter Set |
– CHOICE Memory Partitioning |
Implicit |
– Added or reconfigured MAC-d flow |
|
– MAC-hs queue to add or reconfigure list |
(one queue) |
– MAC-hs queue Id |
0 |
– MAC-d Flow Identity |
0 |
– T1 |
50 |
– MAC-hs window size |
16 |
– MAC-d PDU size Info |
|
– MAC-d PDU size |
336 |
– MAC-d PDU size index |
0 |
– MAC-hs queue to delete list |
Not Present |
– DCH quality target |
Not Present |
RADIO BEARER RELEASE (Step 2) (FDD)
Use the same message as specified for "Packet to CELL_DCH from CELL_DCH / HS-DSCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
Deleted UL TrCH Information |
|
– Uplink transport channel type |
DCH |
– Transport channel identity |
4 |
Added or Reconfigured UL TrCH information |
Not Present |
Deleted DL TrCH Information |
|
– Downlink transport channel type |
DCH |
– Transport channel identity |
9 |
Added or Reconfigured DL TrCH information |
Not Present |
Frequency info |
|
– UARFCN uplink (Nu) |
Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21] |
– UARFCN downlink (Nd) |
Same downlink UARFCN as used for cell 6 |
– CHOICE channel requirement |
Uplink DPCH info |
– Scrambling code number |
Set to the same code number as used for cell 6 |
Downlink information for each radio links |
|
– Primary CPICH info |
|
– Primary Scrambling Code |
Set to the same code as used for cell 6 |
RADIO BEARER RELEASE (Step 2)( 1.28Mcps TDD)
Use the same message as specified for "Packet to CELL_DCH from CELL_DCH / HS-DSCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
Deleted UL TrCH Information |
|
– Uplink transport channel type |
DCH |
– Transport channel identity |
4 |
Added or Reconfigured UL TrCH information |
Not Present |
Deleted DL TrCH Information |
|
– Downlink transport channel type |
DCH |
– Transport channel identity |
9 |
Added or Reconfigured DL TrCH information |
Not Present |
Frequency info |
|
– CHOICE mode |
TDD |
– UARFCN (Nt) |
Same UARFCN as used for cell 6 |
Downlink information per radio link list |
1 radio link |
Downlink information for each radio link |
|
– Choice mode |
TDD |
– Primary CCPCH info |
|
– Cell parameters ID |
Set to the same as cell 6 |
8.2.3.36.5 Test requirements
After step 2, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.36a Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (frequency modification, stop of E-DCH transmission, in the multi-frequency network environment, for 1.28Mcps TDD only)
8.2.3.36a.1 Definition and applicability
All UEs which support 1.28Mcps TDD and HS-PDSCH and E-PUCH.
8.2.3.36a.2 Conformance requirement
The variable E_DCH_TRANSMISSION shall be set to "TRUE" only when all the following conditions are met:
1> the UE is in CELL_DCH state;
1> the variable E_RNTI includes either the Primary E-RNTI or the Secondary E-RNTI or both the Primary and the Secondary E-RNTI;
1> For FDD:
2> the UE has stored the following IEs:
– IE "E-DCH Transmission Time Interval";
– IE "HARQ info for E-DCH";
– IE "E-DCH information", including the IE "E-DPCCH info" and the IE "E-DPDCH info".
– one of the radio links in the active set is configured as the serving E-DCH radio link, and for this radio link the UTRAN has configured the IE "E-HICH configuration" and the IE "E-AGCH info".
1> For TDD:
2> for non-scheduled transmission, the UE has stored the following IEs:
– IE "HARQ info for E-DCH";
– IE "E-DCH information", including the IE "E-PUCH info";
– IE "Non-scheduled transmission grant info";
2> for scheduled transmission, the UE has stored the following IEs:
– IE "HARQ info for E-DCH";
– IE "E-DCH information", including the IE "E-RUCCH info" and the IE "E-PUCH info";
– IE "E-HICH info";
– IE "E-AGCH info".
1> there is at least one logical channel mapped to E-DCH for which:
2> the corresponding E-DCH MAC-d flow is configured, i.e. the IEs "E-DCH MAC-d flow power offset" and "E-DCH MAC-d flow maximum number of retransmissions", and the transmission grant type are configured.
If any of the above conditions is not met and the variable E_DCH_TRANSMISSION is set to TRUE, the UE shall:
1> set the variable E_DCH_TRANSMISSION to FALSE;
1> stop any E-AGCH, E-HICH and E-RGCH reception procedures;
1> For FDD:
2> stop any E-RGCH reception procedures.
1> For FDD:
2> stop any E-DPCCH and E-DPDCH transmission procedures.
1> For TDD:
2> stop any E-RUCCH and E-PUCH transmission procedures.
1> clear the variable E_RNTI;
1> release all E-DCH HARQ resources;
1> no longer consider any radio link to be the serving E-DCH radio link.
Whenever the variable E_DCH_TRANSMISSION is set to TRUE, the UE shall:
1>For FDD:
2> perform E_AGCH reception procedures according to the stored E_AGCH configuration as stated in:
3> subclause 8.6.3.14 for the IE "New Primary E-RNTI" and the IE "New Secondary E-RNTI".
2> perform E-HICH reception procedures for all radio links in the E-DCH active set;
2> perform E-RGCH reception procedures for all radio links in the active set for which an E-RGCH configuration has been provided;
2> perform E-DPCCH transmission procedures according to the stored E-DPCCH configuration as stated in:
3> subclause 8.6.6.37 for the IE "E-DPCCH Info".
2> perform E-DPDCH transmission procedures according to the stored E-DPDCH configuration as stated in:
3> subclause 8.6.5.16 for the IE "E-DCH Transmission Time Interval";
3> subclause 8.6.5.17 for the IE "HARQ info for E-DCH";
3> subclause 8.6.6.37 for the IE "E-DPDCH Info".
2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Non-scheduled transmission grant info" is configured shall:
3> obey the scheduling and size restrictions as specified for that MAC-d flow (see subclause 8.6.5.18).
2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Scheduled transmission grant info" is configured shall:
3> be performed in accordance with the received scheduling grant on E-AGCH/E-RGCH (see [15]); and
3> obey the scheduling restrictions as specified for scheduled transmissions (see subclause 8.6.6.37).
1>For TDD:
2> if scheduled transmission is configured, perform E-AGCH reception procedures according to the stored E_AGCH configuration as stated in:
3> subclause 8.6.3.14 for the IE "New Primary E-RNTI".
2> Perform E-HICH reception;
2> for 3.84/7.68 Mcps TDD, perform E-RUCCH transmission procedures according to the stored E-RUCCH configuration as stated in:
3> subclause 8.6.6.37 for the IE "E-RUCCH Info".
2> for 1.28 Mcps TDD, if scheduled transmission is configured, perform E-RUCCH transmission procedure according to the stored PRACH configuration (see [60]) and the stored E-RUCCH configuration as stated in:
3> subclause 8.6.6.37 for the IE "E-RUCCH Info".
NOTE 1: The PRACH configuration is signalled directly to the UE in "E-RUCCH Info" IE in case of E-DCH serving cell change.
2> Perform E-PUCH transmission procedures according to the stored E-PUCH configuration as stated in:
3> subclause 8.6.6.37 for the IE "E-PUCH Info".
2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Non-scheduled transmission grant info" is configured shall:
3> obey the scheduling and size restrictions as specified for that MAC-d flow (see subclause 8.6.5.18).
2> inclusion of MAC-d PDU’s in a MAC-e or MAC-i PDU for logical channels belonging to a MAC-d flow for which the IE "Scheduled transmission grant info" is configured shall:
3> be performed in accordance with the received scheduling grant on E-AGCH (see [15]); and
3> obey the scheduling restrictions as specified for scheduled transmissions (see subclause 8.6.6.37).
2> obtain and format the appropriate information on E-UCCH (see [15]). For 1.28 Mcps TDD, when performing transmission on signalling radio bearer before RAB has been established, the UE shall use the lowest E-DCH capability category, as specified in [35], to signal the UL control information on E-UCCH.
NOTE 2: For 1.28 Mcps TDD, when performing transmission on signalling radio bearer before RAB has been established, UTRAN should use the lowest E-DCH capability category when performing configuration, scheduling and reading the control information on E-UCCH, as it is not possible for Node B to be aware of the UE’s E-DCH capability category during this period.
Whenever the variable E_DCH_TRANSMISSION is set to FALSE, the UE shall:
1> not perform E-AICH, E-HICH and E-RGCH reception procedures;
1> not perform E-DPCCH and E-DPDCH transmission procedures.
…
If, after completion of the procedure, the UE will be in CELL_DCH state, the UE shall:
1> for FDD, 3.84 Mcps TDD and 7.68 Mcps TDD, if the IE "Frequency info" is included; or
1> for 1.28 Mcps TDD, if the IE "Frequency info" is included and the "Second Frequency info" is not included:
2> if the frequency is different from the currently used frequency:
3> store and use the frequency indicated by the IE "Frequency Info";
3> if the received message is used to perform a Timing-maintained hard handover (see subclause 8.3.5.2),and IE "Timing maintained Synchronization indicator" is included:
4> not perform any physical layer synchronisation procedure (FDD only);
3> else:
4> perform the physical layer synchronisation procedure A as specified in [29] (FDD only).
2> if the frequency is the same as the currently used frequency:
3> continue to use the currently used frequency;
3> perform the physical layer synchronisation procedure A as specified in [29] (FDD only).
1> for 1.28 Mcps TDD, if both the IE "Frequency info" and the IE "Second Frequency info" are included:
2> the frequency in IE "Frequency info" is used as the primary frequency, and the frequency in IE "Second
Frequency info" is used as the secondary frequency;
2> store the primary frequency;
2> if the secondary frequency is different with the currently used frequency:
3> store and use the secondary frequency.
2> if the secondary frequency is the same as the currently used frequency:
3> continue to use the currently used frequency.
1> if the IE "Frequency info" is not included and the UE has a currently used frequency:
2> continue to use the currently used frequency;
…
If the IE "Second Frequency info" is included, the UE shall:
1> act as specified in section 8.6.6.1.
If the IE "FPACH Frequency info" is included, the UE shall:
1> store the FPACH frequency indicated in the IE "FPACH Frequency info".
If the IE "UpPCH Position Info" is included:
1> store and use the UpPCH position indicated by the IE "UpPCH Position Info ". The calculation of the uplink access position is described in [33].
If the IE "UpPCH Position Info" is not included:
1> use the UpPTS as the default UpPCH position.
Reference
3GPP TS 25.331 clause 8.5.28, 8.6.6.1,8.6.6.43.
8.2.3.36a.3 Test purpose
To confirm that the UE releases a radio bearer mapped on E-DCH / HS-DSCH and stops E-DCH transmission / HS-DSCH reception according to the received RADIO BEARER RELEASE message with frequency modification in the multi-frequency network environment.
8.2.3.36a.4 Method of test
Initial Condition
System Simulator:
2 cells
– Cell 1 is active, 3 frequency (one is primary frequency, others are secondary frequency)
– Cell 6 is inactive, 1 frequency
UE: PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports TDD
– UE supports CS speech
– UE supports HS-PDSCH
– UE supports E-PUCH (1.28Mcps TDD)
Test Procedure
The UE is in CELL_DCH state and only signalling radio bearers have been established at the primary frequency of cell 1. SS initiates P26 to make the UE to move to state 6-18 as specified in TS 34.108 clause 7.4. The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH and E-DCH established at one secondary frequency of cell 1. The SS initiates P24 to set up CS speech RAB.
Then SS transmits a RADIO BEARER RELEASE message to the UE. The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC. SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
0 |
|
P26 |
See below for the specific message content used in RADIO BEARER SETUP message. (Step 0) |
|
1 |
|
P24 |
SS establishes CS speech RAB. |
|
2 |
|
RADIO BEARER RELEASE |
SS releases PS RAB. |
|
3 |
|
RADIO BEARER RELEASE COMPLETE |
||
4 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 0)
Use the same message as specified for "Packet to CELL_DCH / E-DCH / HS-DSCH using three multiplexing options (3/3) and SRBs mapped on DCH/DCH" in 34.108, except for the following.
Information Element |
Value/remark |
– RAB information for setup |
|
– RB mapping info |
|
– Information for each multiplexing option |
3 RBMuxOptions |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– Logical channel identity |
Not Present |
– CHOICE RLC size list |
Configured |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
DCH |
– DL DCH Transport channel identity |
9 |
– DL DSCH Transport channel identity |
Not Present |
– DL HS-DSCH MAC-d flow identity |
Not Present |
– Logical channel identity |
Not Present |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
E-DCH |
– Logical channel identity |
10 |
– E-DCH MAC-d flow identity |
2 |
– DDI |
5 |
– RLC PDU size list |
1 RLC PDU size |
– RLC PDU size |
336 bits |
– Include in scheduling info |
TRUE |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
HS-DSCH |
– DL DCH Transport channel identity |
Not Present |
– DL DSCH Transport channel identity |
Not Present |
– DL HS-DSCH MAC-d flow identity |
0 |
– Logical channel identity |
Not Present |
– RLC logical channel mapping indicator |
Not Present |
– Number of uplink RLC logical channels |
1 |
– Uplink transport channel type |
RACH |
– UL Transport channel identity |
Not Present |
– Logical channel identity |
10 |
– CHOICE RLC size list |
Explicit list |
– RLC size index |
Reference to clause 6 Parameter Set |
– MAC logical channel priority |
8 |
– Downlink RLC logical channel info |
|
– Number of downlink RLC logical channels |
1 |
– Downlink transport channel type |
FACH |
– DL DCH Transport channel identity |
Not Present |
– DL DSCH Transport channel identity |
Not Present |
– Logical channel identity |
10 |
Added or Reconfigured UL TrCH information |
1 E-DCH added, 1 DCH added, 1 DCH reconfigured |
– Uplink transport channel type |
E-DCH |
– CHOICE UL parameters |
E-DCH |
– E-DCH Transmission Time Interval |
5 ms |
– HARQ info for E-DCH |
|
– HARQ RV Configuration |
rvtable |
– Added or reconfigured E-DCH MAC-d flow |
|
– E-DCH MAC-d flow identity |
2 |
– E-DCH MAC-d flow power offset |
0 |
– E-DCH MAC-d flow maximum number of retransmissions |
7 |
– E-DCH MAC-d flow multiplexing list |
Not Present |
– CHOICE transmission grant type |
Scheduled grant info |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
4 |
– TFS |
|
– CHOICE Transport channel type |
Dedicated transport channels |
– Dynamic Transport format information |
|
– RLC Size |
Reference to clause 6.11 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.11 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.11 Parameter Set |
– Type of channel coding |
Reference to clause 6.11 Parameter Set |
– Coding Rate |
Reference to clause 6.11 Parameter Set |
– Rate matching attribute |
Reference to clause 6.11 Parameter Set |
– CRC size |
Reference to clause 6.11 Parameter Set |
– Uplink transport channel type |
DCH |
– UL Transport channel identity |
5 |
– TFS |
|
– CHOICE Transport channel type |
|
– Dynamic Transport format information |
|
– RLC Size |
Reference to clause 6.11 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.11 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.11 Parameter Set |
– Type of channel coding |
Reference to clause 6.11 Parameter Set |
– Coding Rate |
Reference to clause 6.11 Parameter Set |
– Rate matching attribute |
Reference to clause 6.11 Parameter Set |
– CRC size |
Reference to clause 6.11 Parameter Set |
Added or Reconfigured DL TrCH information |
3 TrCHs (DCH for DCCH and DCH plus HS-DSCH for DTCH) |
– Downlink transport channel type |
DCH |
– DL Transport channel identity |
10 |
– CHOICE DL parameters |
Same as UL |
– Uplink transport channel type |
DCH |
– UL TrCH identity |
5 |
– DCH quality target |
|
– BLER Quality value |
-20 (-2.0) |
– Downlink transport channel type |
DCH |
– DL Transport channel identity |
9 |
– CHOICE DL parameters |
Explicit |
– TFS |
|
– CHOICE Transport channel type |
Dedicated transport channel |
– Dynamic transport format information |
|
– RLC Size |
Reference to clause 6.11 Parameter Set |
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
– Dynamic transport format information |
|
– Transmission Time Interval |
Not Present |
– Number of Transport blocks |
Reference to clause 6.11 Parameter Set |
– CHOICE Logical channel list |
All |
– Semi-static Transport Format information |
|
– Transmission time interval |
Reference to clause 6.11 Parameter Set |
– Type of channel coding |
Reference to clause 6.11 Parameter Set |
– Coding Rate |
Reference to clause 6.11 Parameter Set |
– Rate matching attribute |
Reference to clause 6.11 Parameter Set |
– CRC size |
Reference to clause 6.11 Parameter Set |
– DCH quality target |
|
– BLER Quality value |
-20 (-2.0) |
– Downlink transport channel type |
HS-DSCH |
– DL Transport channel identity |
Not Present |
– CHOICE DL parameters |
HS-DSCH |
– HARQ Info |
|
– Number of Processes |
Reference to clause 6.11.2.4.5 Parameter Set |
– CHOICE Memory Partitioning |
Implicit |
– Added or reconfigured MAC-d flow |
|
– MAC-hs queue to add or reconfigure list |
(one queue) |
– MAC-hs queue Id |
0 |
– MAC-d Flow Identity |
0 |
– T1 |
50 |
– MAC-hs window size |
16 |
– MAC-d PDU size Info |
|
– MAC-d PDU size |
336 |
– MAC-d PDU size index |
0 |
– MAC-hs queue to delete list |
Not Present |
– DCH quality target |
Not Present |
Frequency info |
|
– CHOICE mode |
TDD |
– UARFCN downlink (Nd) |
Set to the primary frequency of cell 1 |
Multi-frequency Info |
|
– Second Frequency Info |
Same as one secondary frequency of cell 1 |
– FPACH Frequency Info |
Not present |
– UpPCH Position Info |
Not present |
RADIO BEARER RELEASE (Step 2)
Use the same message as specified for "Packet to CELL_DCH from CELL_DCH / HS-DSCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
Deleted UL TrCH Information |
|
– Uplink transport channel type |
DCH |
– Transport channel identity |
4 |
Added or Reconfigured UL TrCH information |
Not Present |
Deleted DL TrCH Information |
|
– Downlink transport channel type |
DCH |
– Transport channel identity |
9 |
Added or Reconfigured DL TrCH information |
Not Present |
Frequency info |
|
– CHOICE mode |
TDD |
– UARFCN (Nt) |
Same UARFCN as used for cell 6 |
Multi-frequency Info |
Not Present |
Downlink information per radio link list |
1 radio link |
Downlink information for each radio link |
|
– Choice mode |
TDD |
– Primary CCPCH info |
|
– Cell parameters ID |
Set to the same as cell 6 |
8.2.3.36a.5 Test requirements
After step 2, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.
8.2.3.37 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (frequency modification, stop of discontinuous uplink transmission)
8.2.3.37.1 Definition
All UEs, which support FDD, UL DTX.
8.2.3.37.2 Conformance requirement
The variable DTX_DRX_STATUS shall be set to TRUE only when all the following conditions are met:
1> the UE is in CELL_DCH state;
1> both variables HS_DSCH RECEPTION and E_DCH_TRANSMISSION are set to TRUE;
1> no DCH transport channel is configured;
1> the variable DTX_DRX_PARAMS is set;
1> the UE has received the IE "DTX-DRX timing information".
If any of the above conditions is not met and the variable DTX_DRX_STATUS is set to TRUE, the UE shall:
1> set the variable DTX_DRX_STATUS to FALSE;
1> clear the variable DTX_DRX_PARAMS;
1> stop DTX-DRX mode related activities.
If variable DTX_DRX_STATUS is set to true and the serving HS-DSCH cell was changed as a result of the received message the UE shall instruct the physical layer to consider HS-SCCH orders were never received.
Whenever the variable DTX_DRX_STATUS is set to TRUE after receiving this message and the value of IE "DTX-DRX timing information" included in this message is not "Continue", the UE shall:
1> if the variable DTX_DRX_STATUS was set to TRUE before receiving this message:
2> re-configure the physical layer to perform discontinuous uplink DPCCH transmission and enable discontinuous downlink reception operations according to the variable DTX_DRX_PARAMS at the CFN corresponding to the frame boundary that is offset by the value of the IE "Enabling Delay" from the frame boundary where uplink transmission starts with new configuration;
2> let the MAC layer continue with the current restriction on E-DCH transmission and monitoring of absolute and relative grant channels from the frame boundary where the uplink transmission starts with the new configuration and for the duration of the IE "Enabling Delay".
1> else:
2> perform discontinuous uplink DPCCH transmission and enable discontinuous downlink reception operations by configuring the physical layer according to the variable DTX_DRX_PARAMS at the CFN corresponding to the frame boundary that is offset by the value of the IE "Enabling Delay" from the frame boundary where uplink transmission starts with new configuration.
- configure the MAC layer to start restricting E-DCH transmissions and monitor absolute and relative grant channels at the CFN corresponding to the frame boundary that is offset by the value of IE "Enabling Delay" from the frame boundary where uplink transmission starts with new configuration taking into account the IEs "UE DTX DRX Offset", "MAC DTX Cycle", "MAC Inactivity Threshold" and "Inactivity Threshold for UE Grant Monitoring".
…
If the IE "DTX-DRX timing information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:
1> if the CHOICE "timing" is set to "New timing":
2> store the contents of the IE in the variable DTX_DRX_PARAMS.
1> determine the value for the DTX_DRX_STATUS variable and take the corresponding actions as described in subclause 8.5.34.
…
If the IE "DTX–DRX information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:
1> store the contents of the IE in the variable DTX_DRX_PARAMS;
1> determine the value for the DTX_DRX_STATUS variable and take the corresponding actions as described in subclause 8.5.34;
1> if the value of the IE "UE DTX cycle 2" is not an integer multiple of the value of the IE "UE DTX cycle 1"; or
1> if the value of the IE "UE DTX cycle 2" is not an integer multiple or a divisor of the value of the IE "CQI Feedback cycle, k"; or
1> if the value of the IE "UE DPCCH burst 1" is greater than the value of the IE "UE DTX cycle 1"; or
1> if the value of the IE "UE DPCCH burst 2" is greater than the value of the IE "UE DTX cycle 2"; or
1> if the IE "UE DTX long preamble length" is set to 4 or 15 slots and the value of the IE "Inactivity Threshold for UE DTX cycle 2" is less than 4 TTIs (for 10ms E-DCH TTI) or 8 TTIs (for 2ms E-DCH TTI); or
1> if the IE "UE DRX cycle" is not an integer multiple or a divisor of the value of the IE "UE DTX cycle 1"; or
1> if the IE "DRX Information" is included in this message while the IE "DTX information" is not included in this message; or
1> if the value of the IE "UE DTX cycle 1" is not an integer multiple or a divisor of the value of the IE "MAC DTX cycle":
2> the UE behaviour is unspecified.
Reference
3GPP TS 25.331 clause 8.5.34, 8.6.6.38, 8.6.6.39
8.2.3.37.3 Test purpose
To confirm that the UE releases a radio bearer mapped on E-DCH / HS-DSCH and stops discontinuous uplink transmission according to the received RADIO BEARER RELEASE message with frequency modification.
8.2.3.37.4 Method of test
Initial Condition
System Simulator: 2 cells–Cells 1 and 6 are active.
UE: PS-DCCH_DCH (state 6-7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT statement(s)
– UE supports FDD
– UE supports discontinuous uplink transmission.
Test Procedure
The UE is in CELL_DCH state and only signalling radio bearers mapped on E-DCH/HS-DSCH have been established. SS initiates P26 and transmits a RADIO BEARER SETUP message to the UE. This message requests the establishment of a radio bearer with RB mapping to HS-DSCH and E-DCH, with UL DTX configured. After the UE receives this message, it establishes a radio bearer and maps it to the HS-DSCH and E-DCH. The UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC. The UE is in CELL_DCH state and has a radio bearer mapped on HS-DSCH and E-DCH with DTX and, if supported, DRX active.
Then SS transmits a RADIO BEARER RELEASE message to the UE. The UE transmits a RADIO BEARER RELEASE COMPLETE message using AM RLC.
SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
0 |
|
P26 |
See below for the specific message content used in RADIO BEARER SETUP message. (Step 0) |
|
0a |
SS |
The SS waits to allow sufficient time for DTX cycle 2 to be active, and CQI DTX Timer to expire, and then verifies that the time between 11 consecutive CQI indications is 320ms if 2ms TTI is used, or 400ms if 10ms TTI is used (i.e. duration of 10 consecutive DTX cycle 2). |
||
1 |
|
RADIO BEARER RELEASE |
SS releases PS RAB. |
|
2 |
|
RADIO BEARER RELEASE COMPLETE |
||
Void |
||||
4 |
|
CALL C.3 |
If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails. |
Specific Message Contents
RADIO BEARER SETUP (Step 0)
The contents of RADIO BEARER SETUP message in this test case are identical to the message sub-type indicated by "Packet to CELL_DCH / E-DCH / HS-DSCH with DTX/DRX using one multiplexing option (1/1) and SRBs mapped on E-DCH/HS-DSCH”.
RADIO BEARER RELEASE (Step 1)
Use the same message as specified for "Packet to CELL_DCH from CELL_DCH / HS-DSCH in PS" in 34.108, except for the following:
Information Element |
Value/remark |
New H-RNTI |
‘1010 1010 1010 1010’ |
New Primary E-RNTI |
‘1010 1010 1010 1010’ |
Deleted UL TrCH Information |
|
– Uplink transport channel type |
E-DCH |
– E-DCH MAC-d flow identity |
2 |
Added or Reconfigured UL TrCH information |
Not Present |
Deleted DL TrCH Information |
|
– Downlink transport channel type |
HS-DSCH |
– DL HS-DSCH MAC-d flow identity |
0 |
Added or Reconfigured DL TrCH information |
Not Present |
Frequency info |
|
– UARFCN uplink (Nu) |
Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21] |
– UARFCN downlink (Nd) |
Same downlink UARFCN as used for cell 6 |
– CHOICE channel requirement |
Uplink DPCH info |
– Scrambling code number |
Set to the same code number as used for cell 6 |
E-DCH info |
Use the message as specified in A20 condition of RB setup message |
Downlink HS-PDSCH Information |
Use the message as specified in A20 condition of RB setup message |
Downlink information common for all radio links – Downlink F-DPCH info common for all RL – Timing Indication – Timing maintained Synchronization indicator |
Use the message as specified in A20 condition of RB setup message except the following Maintain Not Present |
– MAC-hs reset indicator |
TRUE |
Downlink information for each radio links |
Use the message as specified in A20 condition of RB setup message expect the following |
– Primary CPICH info |
|
– Primary Scrambling Code |
Set to the same code as used for cell 6 |
8.2.3.37.5 Test requirements
At step 2, the UE shall transmit a RADIO BEARER RELEASE COMPLETE message.