7.1.8 E-DCH MAC-is/i for RACH procedure

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

7.1.8.1 Release of common E-DCH resource when maximum resource allocation for E-DCH expires or uplink transmission ends for CCCH transmission

7.1.8.1.1 Definition and Applicability

All UEs which support E-DCH in CELL_FACH

7.1.8.1.2 Conformance Requirement

Extract from 25.321 11.2.2A:

The allocated common E-DCH resource shall be used by MAC to carry either only CCCH transmission or only DTCH/DCCH transmission, but not both.

The E-DCH enhanced physical random access transmission procedure is completed with release of the allocated common E-DCH resource, if one of the following conditions is fulfilled:

– If the UE according to subclause 8.5.4A in [7] failed to establish the physical channels, or if the criteria for radio link failure are met as specified in subclause 8.5.6 in [7], then the timer T2 is started. After the expiry of T2 a back off timer TBO1 is started. Back off timer TBO1 is set to an integer number NBO1 of 10 ms time intervals, randomly drawn within an interval 0  NBO1min  NBO1  NBO1max (with uniform distribution). NBO1min and NBO1max may be set equal when a fixed delay is desired, and even to zero when no delay other than the one due to persistency is desired. The procedure ends if timer TBO1 expires or the UE performs cell reselection while timer TBO1 is running, whatever occurs first. In case of a cell reselection, the timer TBO1 is stopped.

– In case of CCCH transmission, if the maximum E-DCH resource allocation for CCCH has been reached, then this triggers a CMAC-STATUS which informs the RRC about end of the Enhanced Uplink for CELL_FACH state and Idle mode.

– In case of CCCH transmission, if the transmission E-DCH Buffer status is 0 bytes, then the MAC-STATUS-Ind primitive indicates to RLC for each logical channel that no PDU shall be transferred to MAC. If the transmission E-DCH Buffer status is 0 bytes and no MAC-i PDUs are left for (re-)transmission in MAC, then this triggers a CMAC-STATUS which informs the RRC about the end of the Enhanced Uplink for CELL_FACH state and Idle mode.

– In case of DTCH/DCCH transmission, if no E-AGCH with UE’s E-RNTI has been received (through an E-RNTI-specific CRC attachment) within the maximum period for collision resolution phase, then this triggers a CMAC-STATUS which informs the RRC about the end of the Enhanced Uplink for CELL_FACH state and Idle mode. Then the timer T2 is started. After the expiry of T2 a back off timer TBO1 is started. Back off timer TBO1 is set to an integer number NBO1 of 10 ms time intervals, randomly drawn within an interval 0  NBO1min  NBO1  NBO1max (with uniform distribution). NBO1min and NBO1max may be set equal when a fixed delay is desired, and even to zero when no delay other than the one due to persistency is desired. The procedure ends when TBO1 expires.

– Explicit common E-DCH resource release:
In case of DTCH/DCCH transmission, if an E-AGCH with UE’s E-RNTI has been received (through an E-RNTI-specific CRC attachment) with absolute grant value set to ‘INACTIVE’, then this triggers a CMAC-STATUS which informs the RRC about end of the Enhanced Uplink for CELL_FACH state and Idle mode.

– Implicit release with E-DCH transmission continuation back off
Implicit resource release is enabled only if "E-DCH transmission continuation back off" is not set to "infinity".
If implicit resource release is enabled, then in case of DTCH/DCCH transmission, the timer Tb is set to "E-DCH transmission continuation back off" value, when TEBS is 0 byte and the last generated MAC-i PDU with higher layer data is provided with the PHY-data-REQ primitive to the physical layer for transmission.
If TEBS <> 0 byte is detected while timer Tb is running, then the timer is stopped and uplink data transmission on the common E-DCH resource continues.
If a MAC-ehs PDU is received while timer Tb is running, then the timer is re-started.
At expiry of timer Tb the MAC-STATUS-Ind primitive indicates to RLC for each logical channel that no PDUs shall be transferred to MAC. TEBS = 0 byte is reported to the Node B MAC as SI in a MAC-i PDU. If the "E-DCH transmission continuation back off" value is set to "0", then the SI should be transmitted with the MAC-i PDU carrying the last DCCH/DTCH data, given the serving grant is sufficient to carry the SI in the same MAC-i PDU together with the remaining DCCH/DTCH data. Otherwise, the empty buffer status report is transmitted separately with the next MAC-i PDU.
If after the expiry of timer Tb no MAC-i PDU is left in a HARQ process for (re-)transmission, then this triggers a CMAC-STATUS which informs the RRC about end of the Enhanced Uplink for CELL_FACH state and Idle mode.

Extract from 25.321 clause 11.8.1.4:

For each MAC-d flow, RRC configures MAC with a HARQ profile and a multiplexing list. Additionally, RRC configures MAC with a power offset for "Control-only" transmissions. This power offset and a maximum number of HARQ transmissions of 8 will be used to define a HARQ profile for “Control-only” transmissions which will be used, in case the Scheduling Information needs to be transmitted without any higher-layer data. The HARQ profile includes the power offset and maximum number of HARQ transmissions to use for this MAC-d flow. The multiplexing list identifies for each MAC-d flow(s), the other MAC-d flows from which data can be multiplexed in a transmission that uses the power offset included in its HARQ profile.

[..]

The E-TFC selection function shall provide this MAC-e PDU and transmission HARQ profile to the HARQ entity. The maximum number of HARQ transmissions and the power offset in this profile, shall be set respectively to the maximum of the Max Number of HARQ Transmissions of the HARQ profiles from all the MAC-d flows from which data is multiplexed into the transmission and to the Nominal Power Offset. The HARQ entity shall also be informed of whether the transmission includes Scheduling Information and whether this information is sent by itself or with higher-layer data.

[…]

if expiry of timer T300 occurs:

the UE shall:

1> check the value of V300; and

2> if V300 is equal to or smaller than N300:

…

3> set the IEs in the RRC CONNECTION REQUEST message according to TS 25.331 subclause 8.1.3.3;

…

3> submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink CCCH;

3> increment counter V300;

3> restart timer T300 when the MAC layer indicates success or failure to transmit the message.

…

2> if V300 is greater than N300:

3> enter idle mode.

3> consider the procedure to be unsuccessful;

3> Other actions the UE shall perform when entering idle mode from connected mode are specified in TS 25.331 subclause 8.5.2;

3> the procedure ends.

References(s)

TS 25.321 clause 11.2.2A , 11.8.1.4,

3GPP TS 25.331 clause 8.1.3.

7.1.8.1.3 Test purpose

1. To verify that UE releases common E-DCH resource when max resource allocation timer of E-DCH expires for CCCH transmission.

2. To verify that UE releases common E-DCH resource when uplink transmission ends for CCCH transmission.

7.1.8.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

UE: Idle state (state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE.

Test procedure

  1. SS transmits the PAGING TYPE 1 with cause BCCH modification.
  2. SS transmits the changed system information SIB 1 and SIB5 / SIB5 bis. UE updates the stored SIBs. The new SIB 5 / SIB5-bis contains the common E-DCH related information.
  3. SS transmits the PAGING TYPE 1 with cause terminating conversational call.
  4. SS receives RRC CONNECTION REQ on common E-DCH resource.
  5. SS transmits a negative HARQ acknowledgement.
  6. SS transmits a HARQ NACK for each received retransmission.
  7. The E-DCH resource allocation timer shall expire in UE side which would lead to release of the common E-DCH resource before the specified number of retransmissions.
  8. SS receives the RRC CONNECTION REQ sent by UE after the expiry of T300
  9. SS transmits a HARQ ACK for the received transmission.
  10. UE does not have to send any data ( MAC buffer empty ) which leads to release of the common E-DCH resource. As RRC CONNECTION SETUP is not sent by SS, the UE acquires a common E-DCH resource to transmit RRC CONNECTION REQUEST after expiry of T300.

NOTE 1: There should not be any transmission from UE for the period of T300 after the expiry of E-DCH resource allocation timer.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

ß

Paging Type 1

BCCH change ind

2

ß

SIB1 and SIB 5/ SIB5 bis

SS transmits E-DCH common information to UE

3

SS waits 5s (to ensure that the UE has time to read the new system information)

4

ß

Paging Type 1

SS starts to transmit this message on the PCCH at the correct paging occasion with cause “Terminating conversational call”

5

®

RRC CONNECTION REQ

UE starts the timer max-CCH-ResourceAllocation. SS starts (max CCCH ResourceAllocation timer) + 10%

6

ß

HARQ NACK

7

SS

SS sends a HARQ NACK for each received retransmission. Max –CCH Resource Allocation Timer in UE shall expire. SS checks that the number of UL HARQ re-transmissions shall be less than the mac-d-FlowMaxRetrans (as specified in the test case ). This is due to max-CCCH-ResourceAllocation timer < ( No of mac-d-FlowMaxRetrans * E-DCH TTI). SS check that the last retransmitted RRC CONNECTION REQUEST is sent before expiry of the timer (max CCCH ResourceAllocation timer) + 10% started in step 5.

8

®

RRC CONNECTION REQ

UE re-transmits after the expiry of T300. UE re-transmits after the expiry of T300. SS checks that UE perform Prach Preamble and Acquisition Indication reception procedure prior to acquiring common E-DCH resource and sending RRC CONNECTION REQ

9

ß

HARQ ACK

10

SS

SS does not respond with RRC CONNECTION SETUP

11

®

RRC CONNECTION REQ

UE re-transmits after the expiry of T300. SS checks that UE perform Prach Preamble and Acquisition Indication reception procedure prior to acquiring common E-DCH resource and sending RRC CONNECTION REQ

Specific Message Contents

PAGING TYPE 1 (Step 1)

Information Element

Value/remark

Message Type

Paging record list

Not Present

BCCH modification info

MIB Value Tag

Set to (Current MIB value tag + 1)

BCCH Modification time

Not Present

SYSTEM INFORMATION TYPE 1 (Step 2)

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

– UE Timers and constants in idle mode

-T300

8000 milliseconds

-N300

3

-T312

10 seconds

– N312

1

SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis (Step 2) (FDD)

Use the same message type found in clause 6.1 of TS 34.108, with condition B3 “Only for cells which configure common E-DCH and HS-DSCH reception in CELL_FACH”, with the following exception.

Information Element

Value/remark

– Common EDCH system information

– common-E-DCH-MAC-d-FlowList

– mac-d-FlowMaxRetrans

15

-CHOICE mode

FDD

– max-CCCH-ResourceAllocation

8 TTI (in the case of 10ms E-DCH TTI).

12 TTI (in the case of 2ms E-DCH TTI).

PAGING TYPE 1 (Step 4)

Information Element

Value/remark

Message Type

Paging record list

Only 1 entry

Paging record

– CHOICE Used paging identity

CN identity

– Paging Cause

Terminating Call with one of the supported services

– CN Domain Identity

PS Domain

– CHOICE UE Identity

Local P-TMSI

– Routing parameter

Same as registered P-TMSI

BCCH modification info

Not Present

7.1.8.1.5 Test requirements

1. At step 7 , SS checks that the number of UL HARQ retransmissions for RRC CONNECTION REQUEST is less than mac-d flow max number of retransmissions, specified in SIB5 due to expiry of CCCH resource allocation timer.

2. At step 11 , SS shall check the use of PRACH Preamble and Acquisition Indication procedure to acquire common E-DCH resource to send RRC CONNECTION REQUEST.

7.1.8.2 Activation of HS-DPCCH based on the received SIB5/SIB5bis information

7.1.8.2.1 Definition and Applicability

All UEs which support E-DCH in CELL_FACH

7.1.8.2.2 Conformance requirement

25.331 section 8.5.45

If variable READY_FOR_COMMON_EDCH is set to TRUE, then after selection of a common E-DCH resource configuration, the RRC in the UE shall configure MAC and the physical layer for E-DCH and HSDPA transmission, and the UE shall:

1> configure Uplink DPCH in accordance with the uplink DPCCH slot format 1 [26], the IE "Uplink DPCH code info" and IE "Uplink DPCH power control info";

1> if IE "ACK/NACK support on HS-DPCCH" is set to TRUE:

2> configure the HS-DPCCH in accordance with HS-DPCCH slot format [26], the HS-DPCCH code [28] and IE "Uplink DPCH power control info".

1> configure the common E-DCH MAC-d flows as described in subclause 8.6.5.24;

1> configure the UL E-DPCCH in accordance with the IE "E-DPCCH" configuration;

1> apply the TTI as signalled in the IE "E-DCH Transmission Time Interval" on the E-DPDCH;

1> use a redundancy version for each HARQ transmission as configured by the IE "HARQ RV Configuration";

1> use the same scrambling code for F-DPCH, E-RGCH, E-HICH and E-AGCH reception as configured for the Primary CPICH;

1> use a channelization code for F-DPCH reception as configured by IE "F-DPCH Code number";

1> configure F-DPCH in accordance with the F-DPCH slot format #0 [26];

1> apply the DPC_Mode=0 for F-DPCH according to [29];

1> configure the MAC with the stored IE "E-DPDCH" configuration and/or the information contained in IE "Scheduled Transmission configuration";

1> configure the E-HICH in accordance with the IE "E-HICH info" configuration;

1> configure the E-AGCH in accordance with the IE "E-AGCH info" configuration;

1> configure the E-RGCH in accordance with the IE "E-RGCH info" configuration if an E-RGCH configuration has been provided with the system information;

1> configure the radio link as the serving E-DCH radio link;

  1. determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46.

25.331 section 8.5.46

The variable COMMON_E_DCH_TRANSMISSION shall be set to TRUE only when all the following conditions are met:

1> the UE is in CELL_FACH state or Idle mode;

1> one radio link is configured as the serving E-DCH radio link, and for this radio link the UTRAN has configured the IE "E-HICH info" and the IE "E-AGCH info", and for 1.28Mcps TDD the IE "E-RUCCH Info" and "E-PUCH Info";

1> all logical channels are mapped to E-DCH, and for each of which there is:

  • 2> one E-DCH MAC-d flow is configured, i.e. the IEs "E-DCH MAC-d flow power offset", "E-DCH MAC-d flow maximum number of retransmissions", and for 1.28 Mcps TDD, the IEs "E-DCH MAC-d flow retransmission timer".

…..

For FDD, whenever the variable COMMON_E_DCH_TRANSMISSION is set to TRUE, the UE shall:

…..

1> if transmitting DCCH or DTCH data:

  • 2> if IE "ACK/NACK support on HS-DPCCH" is set to TRUE:
  • 3> after collision resolution provide ACK/NACK feedback in accordance with [29] in the physical layer on the serving HS-DSCH radio link, using the information in the IE "Uplink DPCH power control info";
  • 3> after collision resolution use the information for the channel quality indication (CQI) procedure in the physical layer on the serving HS-DSCH radio link if the IE "Measurement Feedback Info" has been provided with the common E-DCH resource.

25.321 clauses 11.6.22

[…]

The UE shall:

– if the New Data Indicator has been incremented compared to the value in the previous received transmission in this HARQ process or this is the first received transmission in the HARQ process:

– replace the data currently in the soft buffer for this HARQ process with the received data.

– if the Transport Block Size index value is equal to 111111 (FDD only):

– generate a positive acknowledgement (ACK) of the data in this HARQ process;

– discard the received data;

– assume that the data has been successfully decoded.

– if the New Data Indicator is identical to the value used in the previous received transmission in the HARQ process:

– if the Transport Block Size index value is equal to 111111 (FDD only):

– assume that the transport block size is identical to the last valid transport block size signalled for this HARQ process.

– if the data has not yet been successfully decoded:

– combine the received data with the data currently in the soft buffer for this HARQ process.

– if the data in the soft buffer has been successfully decoded and no error was detected:

– deliver the decoded MAC-hs PDU to the reordering entity;

– generate a positive acknowledgement (ACK) of the data in this HARQ process.

– else:

– generate a negative acknowledgement (NAK) of the data in this HARQ process;

– schedule the generated positive or negative acknowledgement for transmission and the time of transmission relative to the reception of data in a HARQ process is configured by upper layer.

Reference(s)

TS 25.331 section 8.5.45, section 8.5.46

TS 25.321 clauses 11.6.22

7.1.8.2.3 Test purpose

The purpose of the test case is to verify that UE configures the HS-DPCCH based on the common E-DCH information received in SIB5/SIB5bis .

7.1.8.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

UE: Idle state (state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE.

UE shall receive SIB5/SIB5bis with condition B3 “Only for cells which configure common E-DCH and HS-DSCH reception in CELL_FACH”.

Test Procedure

a) SS sends the PAGING TYPE 1 with cause “Terminating conversational call”

b) SS waits for RRC CONNECTION REQ message to arrive on E-DCH/CCCH.

c) SS transmits RRC CONNECTION SETUP

d) SS receives RRC CONNECTION SETUP COMPLETE message from UE

e) SS sends E- AGCH with UE specific E-RNTI to end collision resolution phase.

f) SS transmits UE CAPABILITY ENQUIRY message with CRC error

g) SS checks HARQ NACK on HS DPCCH for the message received at step g

h) SS transmits UE CAPABILITY ENQUIRY message without CRC error

i) SS checks HARQ ACK on HS DPCCH for the message received at step i

j) SS receives UE CAPABILITY INFORMATION

k) SS transmits UE CAPABILITY INFORMATION CONFIRM

Expected Sequence

Step

Direction

Message

Comments

UE

SS

1

ß

Paging Type 1

SS starts to transmit this message continuously on the PCCH at the correct paging occasion with cause “Terminating conversational call”

2

RRC CONNECTION REQ

3

ß

RRC CONNECTION SETUP

4

RRC CONNECTION SETUP COMPLETE

5

Absolute Grant

SS sends E-AGCH with serving grant 4 and with UE specific E-RNTI to end the collision resolution phase.

6

ß

UE CAPABILITY ENQUIRY

The SS sends this message over HS-DSCH with CRC error.

7

MAC-ehs negative acknowledgement.

UE sends a HARQ NACK for each received data on HS-DSCH on HS_DPCCH

8

ß

UE CAPABILITY ENQUIRY

Message sent on HS-DSCH with correct CRC.

9

MAC-ehs positive acknowledgement.

UE sends a HARQ ACK for each received data on HS-DSCH on HS_DPCCH

10

UE CAPABILITY INFORMATION

11

ß

UE CAPABILITY INFORMATION CONFIRM

Specific Message Contents

PAGING TYPE 1 (Step 1)

Information Element

Value/remark

Message Type

Paging record list

Only 1 entry

Paging record

– CHOICE Used paging identity

CN identity

– Paging Cause

Terminating Call with one of the supported services

– CN Domain Identity

PS Domain or CS Domain

– CHOICE UE Identity

Local (P)TMSI

– Routing parameter

Same as registered P-TMSI

BCCH modification info

Not Present

RRC CONNECTION REQUEST (Step 2)

Information Element

Value/remark

Message Type

Initial UE Identity

Same as the IMSI stored in the TEST USIM card, or the registered P-TMSI

Establishment Cause

Checked to see if set to one of the supported originating call types

Protocol Error Indicator

Checked to see if set to "FALSE"

Measured Results on RACH

Checked to see if it is absent

7.1.8.2.5 Test Requirement

1. At step 6 and step 8 , SS checks the Nack/Ack on HS-DPCCH channel

7.1.8.3 DTCH/DCCH transmission – implicit common E-DCH resource release without receiving E-AGCH

7.1.8.3.1 Definition and applicability

Applicable for all UEs supporting Enhanced UL in Cell_FACH.

7.1.8.3.2 Conformance Requirement

[..]

  • In case of DTCH/DCCH transmission, if no E-AGCH with UE’s E-RNTI has been received (through an E-RNTI-specific CRC attachment) within the maximum period for collision resolution phase, then this triggers a CMAC-STATUS which informs the RRC about the end of the Enhanced Uplink for CELL_FACH state and Idle mode.

[..]

  • If the UE is sending DTCH or DCCH data, the UE shall release the common E-DCH resource under following conditions:

– the maximum period for collision resolution is reached and no E-AGCH with the UE’s E-RNTI (through an E-RNTI specific CRC attachment) has been reached;

[..]

Reference(s)

TS 25.321 clause 11.2.2A, 11.8.1.9

7.1.8.3.3 Test purpose

1. To verify that the UE releases E-DCH resources when no valid E-AGCH is received and allocates E-DCH resources when a valid E-AGCH is received.

7.1.8.3.4 Method of test

Initial conditions

UE is in Enhanced CELL_FACH state with DTCH/DCCH on common E-DCH / HS-DSCH.

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 9.1 using condition “AM Packet to Enhanced CELL_FACH from Enhanced CELL_FACH in PS with SRBs mapped on common E-DCH/HS-DSCH”.

The radio bearer is placed in UE loop-back mode 1 with the UL SDU size set to 40 bytes.

System Simulator

1 cell, default parameters, Ciphering Off

Test procedure

a) Void

b) The SS sends 15 RLC SDU of size 40 bytes on the downlink.

c) The SS allocates common E-DCH resource.

d) The SS does not transmit a grant on the E-AGCH thereby causing the UE to implicitly release the allocated E-DCH resources after expiry of collision resolution phase.

e) The SS checks that UE initiates a PRACH preamble and Acquisition Indication for a new common E-DCH channel which is used to loop back the data. SS checks the loop back data.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

Void

1a

Void

2

RLC SDU

SS sends 15 RLC SDU of size 40 bytes on the downlink

3

UE acquires common E-DCH resource

Preamble transmission to use common E-DCH resource and

SS acknowledges the RACH transmission

4

SS does not send E-AGCH

5

Wait for T = 15TTI

SS monitors data transmissions while waiting for the collision resolution phase to end.

6

UE acquires common E-DCH resource

UE initiates a PRACH preamble and Acquisition Indication for a new common E-DCH channel which is used to loop back the data

7

Absolute Grant

SS sends E-AGCH with serving grant 4

8

RLC SDU

SS receives and checks loop back data on common E-DCH

Specific Message Contents

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions

Contents of System Information Block type 1

Information Element

Value/Remark

– UE Timers and constants in connected mode

-N300

0

PRACH power offset info, PRACH info, and PRACH partitioning in System Information Block type 5/System Information Block type 5bis

System Information Block type 5/System Information Block type 5bis

Information Element

Value/Remark

– Primary CCPCH info

Not Present

– PRACH system information list

– PRACH system information

-PRACH info

– CHOICE mode

FDD

– Available Sub Channel number

‘1111 1111 1111’B

-PRACH partitioning

– Access Service Class

2 Access Service Classes

– ASC Setting

– CHOICE mode

FDD

– Available signature Start Index

0 (ASC#0)

– Available signature End Index

7 (ASC#0)

– Assigned Sub-channel Number

‘0001’B

The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number

– ASC Setting

– CHOICE mode

FDD

– Available signature Start Index

0 (ASC#1)

– Available signature End Index

7 (ASC#1)

– Assigned Sub-channel Number

‘0010’B

The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number

-PRACH power offset

– Preamble Retrans Max

5

– RACH transmission parameters

– Mmax

1

– Common EDCH System Info

– Maximum period for collision resolution phase

8TTI

– E-DCH transmission continuation back off

infinity

– Initial serving grant value

4

7.1.8.3.5 Test requirements

  1. At step 6, the UE initiate a PRACH preamble and Acquisition Indication.
  2. At step 8, the SS shall receive at least one loopback RLC PDU.

7.1.8.4 DTCH/DCCH transmission – explicit common E-DCH resource release by E-AGCH

7.1.8.4.1 Definition and applicability

Applicable for all UEs supporting Enhanced UL in Cell_FACH.

7.1.8.4.2 Conformance Requirement

[..]

– Explicit common E-DCH resource release:
In case of DTCH/DCCH transmission, if an E-AGCH with UE’s E-RNTI has been received (through an E-RNTI-specific CRC attachment) with absolute grant value set to ‘INACTIVE’, then this triggers a CMAC-STATUS which informs the RRC about end of the Enhanced Uplink for CELL_FACH state and Idle mode.

[..]

– If the UE is sending DTCH or DCCH data, the UE shall release the common E-DCH resource under following conditions:

– an E-AGCH is received with a common E-DCH resource release command (INACTIVE) (explicit common E-DCH resource release);

[..]

Reference(s)

TS 25.321 clause 11.2.2A, 11.8.1.9

7.1.8.4.3 Test purpose

1. To verify that the UE releases E-DCH resources when a valid E-AGCH is received with a common E-DCH resource release command (INACTIVE).

7.1.8.4.4 Method of test

Initial conditions

UE is in Enhanced CELL_FACH state with DTCH/DCCH on common E-DCH / HS-DSCH.

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 9.1 using condition “AM Packet to Enhanced CELL_FACH from Enhanced CELL_FACH in PS with SRBs mapped on common E-DCH/HS-DSCH”.

The radio bearer is placed in UE loop-back mode 1 with the UL SDU size set to 10 bytes.

System Simulator

1 cell, default parameters, Ciphering Off

Test procedure

a) UE has common E-DCH resource and allocated E-RNTI to allow data transmission on DTCH. SS sends absolute grant with value of 4 which is sufficient for the UE to transmit data.

b) The SS sends 1 RLC SDU of size 10 bytes on the downlink.

c) The SS receives looped back data on the common E-DCH channel.

d) SS sends Explicit Release on E-AGCH to release the common E-DCH resource.

e) The SS sends 1 RLC SDU of size 10 bytes on the downlink.

f) The SS checks that original common E-DCH channel has been explicitly released by checking that UE initiates a PRACH preamble and Acquisition Indication for a new common E-DCH channel which is used to loop back the data. SS checks the loop back data.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

UE has common E-DCH with E-RNTI allocated. The user plane RAB uses DTCH transmission.

1a

Absolute Grant

Serving Grant value 4

2

RLC SDU

SS sends 1 RLC SDU of size 10 bytes on the downlink

3

RLC SDU

SS receives and checks loop back data on common E-DCH

4

Absolute grant set to INACTIVE

The SS explicitly instructs the UE to release the E-DCH resources

5

RLC SDU

SS sends 1 RLC SDU of size 10 bytes on the downlink

6

<->

UE acquires common E-DCH resource

SS first checks that UE perform Prach Preamble prior to acquiring common E-DCH resource. UE shall then loop back the data using DTCH transmission on common E-DCH

7

RLC SDU

SS receives and checks loop back data on common E-DCH

Specific Message Contents

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions

Contents of System Information Block type 1

Information Element

Value/Remark

– UE Timers and constants in connected mode

-N300

0

System Information Block type 5/System Information Block type 5bis

Information Element

Value/Remark

– Primary CCPCH info

Not Present

– PRACH system information list

– PRACH system information

-PRACH info

– CHOICE mode

FDD

– Available Sub Channel number

‘1111 1111 1111’B

-PRACH partitioning

– Access Service Class

2 Access Service Classes

– ASC Setting

– CHOICE mode

FDD

– Available signature Start Index

0 (ASC#0)

– Available signature End Index

7 (ASC#0)

– Assigned Sub-channel Number

‘0001’B

The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number

– ASC Setting

– CHOICE mode

FDD

– Available signature Start Index

0 (ASC#1)

– Available signature End Index

7 (ASC#1)

– Assigned Sub-channel Number

‘0010’B

The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number

-PRACH power offset

– Preamble Retrans Max

5

– RACH transmission parameters

– Mmax

1

– Common EDCH System Info

– Maximum period for collision resolution phase

8TTI

– E-DCH transmission continuation back off

infinity

7.1.8.4.5 Test requirements

At step 3, the SS shall receive the loopback PDU.

At step 7, the SS shall receive the loopback PDU on E-DCH resource used other than step 3.

7.1.8.5 RACH procedure with both normal AIs and extended AIs (using E-AICH).

7.1.8.5.1 Definition and Applicability

All UEs which support E-DCH in CELL_FACH

7.1.8.5.2 Conformance Requirement

Extract from 25.211 5.3.3.7.

The use of acquisition indicators is described in [5]. The meaning of acquisition indicators depends on whether a UE sends an access preamble signature corresponding to a PRACH message or corresponding to an E-DCH transmission. Furthermore, if a UE sends an access preamble signature corresponding to an E-DCH transmission, the meaning of the acquisition indicator depends on whether EAI is configured or not. The following rules apply for one PRACH preamble scrambling code. If multiple PRACH preamble scrambling codes are defined in a cell, then for each of them the following rules are used independently.

– If the UE sends an access preamble signature corresponding to a PRACH message, then;

– if an Acquisition Indicator is set to +1, it represents a positive acknowledgement,

– if an Acquisition Indicator is set to -1, it represents a negative acknowledgement.

– If the UE sends an access preamble signature corresponding to an E-DCH transmission, then;

– if the corresponding Acquisition Indicator is set to +1, it represents a positive acknowledgement and the associated default E-DCH resource configuration is allocated to the UE,

– if the corresponding Acquisition Indicator is set to -1 and EAI is not configured, then it represents a negative acknowledgement,

– if the corresponding Acquisition Indicator is set to -1 and EAI is configured, then the UE detects which one of the Extended Acquisition Indicator signatures is present.

Extract from 25.331 clause 8.1.3.9 (for RRC CONNECTION REJECT)

2> if V300 is greater than N300:

3> enter idle mode;

3> perform the actions specified in TS 25.331 subclause 8.5.2 when entering idle mode from connected mode;

3> consider the RRC establishment procedure to be unsuccessful;

3> the procedure ends.

References(s)

TS 25.211 5.3.3.7 , TS 25.331 clause 8.1.3.9

7.1.8.5.3 Test purpose

The purpose of the test case is to verify that UE successfully completes raching procedure when E-AICH is not configured and when E-AICH is configured.

7.1.8.5.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

UE: Idle state (state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE.

Test procedure

  1. SS transmits the PAGING TYPE 1 with cause BCCH modification.
  2. SS transmits the changed system information SIB1 and SIB5 / SIB5bis. UE updates the stored SIBs. The new SIB 5 / SIB5-bis contains the common E-DCH related information ( E-AIs not supported ).
  3. SS transmits the PAGING TYPE 1 with cause Terminating Interactive Call.
  4. The SS measures the preamble signature used
  5. The SS responds with a negative acquisition indicator on the AICH.
  6. The SS monitors the RACH channel for 10 seconds to ensure that no further RACH accesses occur.
  7. The SS transmits the PAGING TYPE 1 with cause Terminating Interactive Call.
  8. The SS measures the preamble signature used .
  9. The SS responds with a positive acquisition indicator on the AICH.
  10. UE transmits RRC CONNECTION REQ using the common E-DCH resources allocated.
  11. The SS responds with RRC CONNECTION REJECT to avoid any HARQ retransmission and to bring the UE to Idle mode.
  12. SS transmits the PAGING TYPE 1 with cause BCCH modification.
  13. SS transmits the changed system information SIB5 / SIB5bis. UE updates the stored SIBs. The new SIB 5 / SIB5-bis contain the common E-DCH related information (E-AIs supported).
  14. SS transmits the PAGING TYPE 1 with cause Terminating Interactive Call.
  15. The SS measures the preamble signature used.
  16. The SS responds with a negative acquisition indicator on the AICH.
  17. The SS responds with acquisition indicator on the E-AICH with index to use common E-DCH resource.
  18. UE transmits RRC CONNECTION REQ using the common E-DCH resources allocated.
  19. The SS responds with RRC CONNECTION REJECT to avoid any HARQ retransmission and to bring the UE to Idle mode.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

ß

Paging Type 1

BCCH change ind

2

ß

SIB1 and SIB 5/ SIB5bis

SS transmits E-DCH common information to UE with E-AIs NOT supported

3

SS

SS waits 5s (to ensure that the UE has time to read the new system information)

4

ß

Paging Type 1

SS starts to transmit this message on the PCCH at the correct paging occasion with cause “Terminating Interactive Call”

5

Access Preamble

6

ß

AICH = NEG ACQUISITION IND

7

SS

Wait for T = 10s

SS monitors for RACH access attempts

8

ß

Paging Type 1

SS starts to transmit this message continuously on the PCCH at the correct paging occasion with cause “Terminating Interactive Call”

9

Access Preamble

10

ß

AICH = POS ACQUISITION IND

Use default common E-DCH resource

11

RRC CONNECTION REQ

12

ß

RRC CONNECTION REJECT

IE "wait time" set to 0 to bring the UE to idle mode.

13

Paging Type 1

BCCH change ind

14

SS

SIB 5/ SIB5bis

SS transmits E-DCH common information to UE with E-AIs supported

15

SS

SS waits 5s (to ensure that the UE has time to read the new system information)

16

ß

Paging Type 1

SS starts to transmit this message continuously on the PCCH at the correct paging occasion with cause “Terminating Interactive Call”

17

Access Preamble

18

ß

AICH = NEG ACQUISITION IND

19

ß

E-AICH = Index to common E-DCH resource

20

RRC CONNECTION REQ

21

ß

RRC CONNECTION REJECT

IE "wait time" set to 0 to bring the UE to idle mode.

Specific Message Contents

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions

PAGING TYPE 1 (Step 1, Step 13 )

Information Element

Value/remark

Message Type

Paging record list

Not Present

BCCH modification info

MIB Value Tag

Set to (Current MIB value tag + 1)

BCCH Modification time

Not Present

SYSTEM INFORMATION TYPE 1 (Step 2)

Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions:

Information Element

Value/Remark

– UE Timers and constants in connected mode

-N300

0

SYSTEM INFORMATION BLOCK TYPE 5/SYSTEM INFORMATION BLOCK TYPE 5bis (Step 2) (FDD)

Use the same message type found in clause 6.1 of TS 34.108 with condition B3 “Only for cells which configure common E-DCH and HS-DSCH reception in CELL_FACH”, with the following exception.

Information Element

Value/remark

– Common EDCH system information

-PRACH-PreambleForEnhancedUplink

– e-ai-Indication

FALSE

– Common E-DCH Resource Configuration Information List

1 E-DCH resource

– S-offset

0

– F-DPCH Code number

12

– E-RGCH Information

– Signature Sequence

0

– RG combination index

0

– E-HICH Info

– Channelisation Code

4

– Signature Sequence

1

– Uplink DPCH Code Info

– ul-DPCCHscramblingCodeType

Long

– ul-DPCCHscramblingCode

10

PAGING TYPE 1 (Step 4, Step 8 and Step 13)

Information Element

Value/remark

Message Type

Paging record list

Only 1 entry

Paging record

– CHOICE Used paging identity

CN identity

– Paging Cause

Terminating Call with one of the supported services

– CN Domain Identity

PS Domain

– CHOICE UE Identity

Local (P)TMSI

– Routing parameter

Same as registered P-TMSI

BCCH modification info

Not Present

SYSTEM INFORMATION BLOCK TYPE 5/SYSTEM INFORMATION BLOCK TYPE 5bis (Step 14) (FDD)

Use the same message type found in clause 6.1 of TS 34.108 with condition B3 “Only for cells which configure common E-DCH and HS-DSCH reception in CELL_FACH”, with the following exception.

Information Element

Value/remark

– Common EDCH system information

-PRACH-PreambleForEnhancedUplink

– e-ai-Indication

TRUE

– Common E-DCH Resource Configuration Information List

1 E-DCH resource

– S-offset

0

– F-DPCH Code number

12

– E-RGCH Information

– Signature Sequence

0

– RG combination index

0

– E-HICH Info

– Channelisation Code

4

– Signature Sequence

1

– Uplink DPCH Code Info

– ul-DPCCHscramblingCodeType

Long

– ul-DPCCHscramblingCode

10

RRC CONNECTION REJECT (Step 12, Step 21)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element

Value/remark

Initial UE Identity

Same as the type and value defined in RRC CONNECTION REQUEST message (step 5)

Reject Cause

Congestion

Wait time

0 second

7.1.8.5.5 Test requirements

1. At step 7, SS checks UE does not try for RACH access after transmitting AICH = NEG ACQUISITION IND.

2. At step 11, SS shall receive RRC CONNECTION REQ sent by UE after transmitting AICH = POS ACQUISITION IND (with Index to default common E-DCH resource ) at step 10.

3. At step 20 , SS shall receive RRC CONNECTION REQ after transmitting AICH = NEG ACQUISITION IND at step 18 and E-AICH = Index to common E-DCH resource at step 19.

7.1.8.6 DTCH/DCCH transmission – Implicit release with E-DCH transmission continuation backoff – Timer Based

7.1.8.6.1 Definition and applicability

Applicable for all UEs supporting Enhanced UL in Cell_FACH.

7.1.8.6.2 Conformance Requirement

[..]

  • Implicit release with E-DCH transmission continuation backoff
    Implicit resource release is enabled only if "E-DCH transmission continuation back off" is not set to "infinity".
    If implicit resource release is enabled, then in case of DTCH/DCCH transmission, the timer Tb is set to "E-DCH transmission continuation back off" value, when TEBS is 0 byte and the last generated MAC-i PDU with higher layer data is provided with the PHY-data-REQ primitive to the physical layer for transmission.
    If TEBS <> 0 byte is detected while timer Tb is running, then the timer is stopped and uplink data transmission on the common E-DCH resource continues.
    If a MAC-ehs PDU is received while timer Tb is running, then the timer is re-started.
    If the "E-DCH transmission continuation back off" value is set to "0" or if timer Tb expires the MAC-STATUS-Ind primitive indicates to RLC for each logical channel that no PDUs shall be transferred to MAC. TEBS = 0 byte is reported to the Node B MAC as SI in a MAC-i PDU. If the "E-DCH transmission continuation back off" value is set to "0", then the SI shall be transmitted with the MAC-i PDU carrying the last DCCH/DTCH data, given the serving grant is sufficient to carry the SI in the same MAC-i PDU together with the remaining DCCH/DTCH data. Otherwise, the empty buffer status report is transmitted separately with the next MAC-i PDU.
    CMAC-STATUS-Ind which informs the RRC about the Enhanced Uplink in CELL_FACH state and Idle mode process termination is triggered when the empty buffer status has been reported and no MAC-i PDU is left in any HARQ process for (re-)transmission.

[..]

When "E-DCH transmission continuation back off" is set to "infinity", the Scheduling Information with empty buffer status report shall be transmitted with the MAC-i PDU carrying the last DCCH/DTCH data, given the serving grant is sufficient to carry the SI in the same MAC-i PDU together with the remaining DCCH/DTCH data. Otherwise, the Scheduling Information with empty buffer status report is transmitted separately with the next MAC-i PDU.

[..]

If the UE is sending DTCH or DCCH data, the UE shall release the common E-DCH resource under following conditions:

[..]

– "E-DCH transmission continuation back off" is not set to "infinity", the empty buffer status (TEBS = 0 byte) has been reported and no MAC-i PDU is left in a HARQ process for (re-)transmission.

[..]

Reference(s)

TS 25.321 clause 11.2.2A, 11.8.1.6, 11.8.1.9

7.1.8.6.3 Test purpose

1. To verify that the UE releases E-DCH resources implicitly only if “E-DCH transmission continuation backoff is not set to “infinity”.

2. To verify that, when “E-DCH transmission continuation backoff is set to “infinity” and all data have been sent, the UE send the Scheduling Information with empty buffer status report in the same MAC-i PDU carrying the last DCCH/DTCH data.

7.1.8.6.4 Method of test

Initial conditions

System Simulator

1 cell, default parameters, Ciphering Off

User Equipment:

SS shall broadcast SIB5/SIB5bis with Common E-DCH/HS-DSCH information with specific message content given below.

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 9.1 using condition “AM Packet to Enhanced CELL_FACH from Enhanced CELL_FACH in PS with SRBs mapped on common E-DCH/HS-DSCH”.

UE is in Enhanced CELL_FACH state with DTCH/DCCH on common E-DCH / HS-DSCH.

The radio bearer is placed in UE loop-back mode 1 with the UL SDU size set to 10 bytes.

Test procedure

a) UE has common E-DCH resource and allocated E-RNTI to allow data transmission on DTCH. SS sends absolute grant with value of 4 which is sufficient for the UE to transmit data.

b) The SS sends 1 RLC SDU of size 10 bytes on the downlink.

c) The SS receives looped back data on the common E-DCH channel.

NOTE: Data should be looped back before E-DCH-transmission continuation back off period expires.

d) The SS waits sufficient time for the “E-DCH transmission continuation back off” period to expire after loop back data transfer.

e) The SS sends 1 RLC SDU of size 10 bytes on the downlink.

f) The SS checks that original common E-DCH channel has been implicitly released by checking that UE initiates a PRACH preamble and Acquisition Indication for a new common E-DCH channel which is used to loop back the data. SS checks the loop back data.

g) SS checks that all the data is looped back on common E-DCH channel.

h) SS sends Explicit Release on E-AGCH to release the common E-DCH resource.

i) The SS commences required actions for acquisition indication and assignment of a common E-DCH resource for RACH preamble phase.

j) The SS issues an absolute grant on E-AGCH with the UE’s E-RNTI and a signalling value of 4 during the collision resolution phase to allow the UE to transmit data. SS ensure that E-AGCH is received by UE within Maximum period for collision resolution time interval.

k) UE performs PRACH preamble and Acquisition Indication for a common E-DCH resource allocation.

l) After 120TTI, the SS checks that common E-DCH has not been released by checking that there is still transmission on UL DPCCH assigned to that resource.

m) After 120TTI, the SS checks that common E-DCH has not been released by checking that data can be looped back on the existing common E-DCH without PRACH preamble and AICH procedure for acquiring a common E-DCH resource. The SS also checks that the UE includes the SI with TEBS=0 in the same MAC-i PDU together with the DCCH/DTCH data.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

UE has common E-DCH with E-RNTI allocated. The user plane RAB uses DTCH transmission.

1a

Absolute Grant

Serving Grant 4

2

RLC SDU

SS sends 1 RLC SDU of size 10 bytes on the downlink

3

RLC SDU

SS receives and checks loop back data on common E-DCH

4

Wait for “E-DCH transmission continuation back off” expiry

SS should check that UL DPCCH is maintained by the UE until “E-DCH transmission continuation back off” expiry

5

RLC SDU

SS sends another 1 RLC SDU of size 10 bytes

6

<->

UE acquires common E-DCH resource

SS checks that UE perform PRACH Preamble prior to acquiring common E-DCH resource.

6a

Absolute Grant

Serving Grant 4

6b

RLC SDU

SS receives and checks loop back data on common E-DCH

7

Absolute Grant

SS sends Explicit Release on E-AGCHcommand

8

System Information change indication

SS modified system information by setting “E-DCH transmission continuation back off” period to “infinity”

9

RLC SDU

SS sends 1 RLC SDU of size 10 bytes on the downlink

10

<->

UE acquires common E-DCH resource

SS first checks that UE perform Prach Preamble prior to acquiring common E-DCH resource. UE shall then loop back the data using DTCH transmission on common E-DCH

10a

Absolute Grant

Serving Grant 4

11

RLC SDU

SS receives and checks loop back data on common E-DCH

12

WAIT for 120 TTI

SS waits for the maximum setting of the “E-DCH transmission continuation back off” to end

12a

Absolute Grant

Serving Grant 4

13

RLC SDU

SS sends 1 RLC SDU of size 10 bytes on the downlink

14

RLC SDU

UE shall loop back the data and a SI with TEBS=0 in the same MAC-I PDU on the existing common E-DCH without PRACH preamble and AICH procedure for acquiring a common E-DCH resource

Specific Message Contents

Use the same message type found in clause 6.1.1 of TS 34.108, with SIB5 configured for common E-DCH / HS-DSCH, with the following exceptions.

System Information Block type 5/System Information Block type 5bis

Information Element

Value/Remark

– Primary CCPCH info

Not Present

– PRACH system information list

– PRACH system information

-PRACH info

– CHOICE mode

FDD

– Available Sub Channel number

‘1111 1111 1111’B

-PRACH partitioning

– Access Service Class

2 Access Service Classes

– ASC Setting

– CHOICE mode

FDD

– Available signature Start Index

0 (ASC#0)

– Available signature End Index

7 (ASC#0)

– Assigned Sub-channel Number

‘0001’B

The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number

– ASC Setting

– CHOICE mode

FDD

– Available signature Start Index

0 (ASC#1)

– Available signature End Index

7 (ASC#1)

– Assigned Sub-channel Number

‘0010’B

The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number

-PRACH power offset

– Preamble Retrans Max

5

– RACH transmission parameters

– Mmax

1

– Common EDCH System Info

– Maximum period for collision resolution phase

8TTI

– E-DCH transmission continuation back off

80TTI

7.1.8.6.5 Test requirements

– at step 6a, UE shall perform PRACH preamble and receive Acquisition Indication before looping back data on allocated common E-DCH resource.

– at step 14 UE shall loop back data and a SI with TEBS=0 in the same MAC-I PDU on existing common E-DCH resource without PRACH preamble and Acquisition Indication procedure.

7.1.8.6a DTCH/DCCH transmission – Implicit release with E-DCH transmission continuation backoff value set to “0”

7.1.8.6a.1 Definition and applicability

Applicable for all UEs supporting Enhanced UL in Cell_FACH.

7.1.8.6a.2 Conformance Requirement

[..]

– Implicit release with E-DCH transmission continuation backoff
Implicit resource release is enabled only if "E-DCH transmission continuation back off" is not set to "infinity".
If implicit resource release is enabled, then in case of DTCH/DCCH transmission, the timer Tb is set to "E-DCH transmission continuation back off" value, when TEBS is 0 byte and the last generated MAC-i PDU with higher layer data is provided with the PHY-data-REQ primitive to the physical layer for transmission.
If TEBS <> 0 byte is detected while timer Tb is running, then the timer is stopped and uplink data transmission on the common E-DCH resource continues.
If a MAC-ehs PDU is received while timer Tb is running, then the timer is re-started.
If the "E-DCH transmission continuation back off" value is set to "0" or if timer Tb expires the MAC-STATUS-Ind primitive indicates to RLC for each logical channel that no PDUs shall be transferred to MAC. TEBS = 0 byte is reported to the Node B MAC as SI in a MAC-i PDU. If the "E-DCH transmission continuation back off" value is set to "0", then the SI shall be transmitted with the MAC-i PDU carrying the last DCCH/DTCH data, given the serving grant is sufficient to carry the SI in the same MAC-i PDU together with the remaining DCCH/DTCH data. Otherwise, the empty buffer status report is transmitted separately with the next MAC-i PDU.
CMAC-STATUS-Ind which informs the RRC about the Enhanced Uplink in CELL_FACH state and Idle mode process termination is triggered when the empty buffer status has been reported and no MAC-i PDU is left in any HARQ process for (re-)transmission.

[..]

If the UE is sending DTCH or DCCH data, the UE shall release the common E-DCH resource under following conditions:

[..]

– "E-DCH transmission continuation back off" is not set to "infinity", the empty buffer status (TEBS = 0 byte) has been reported and no MAC-i PDU is left in a HARQ process for (re-)transmission.

[..]

Reference(s)

TS 25.321 clause 11.2.2A, 11.8.1.9

7.1.8.6a.3 Test purpose

1. To verify that, when “E-DCH transmission continuation back off" value is set to "0" and UE has resources to transmit all remaining data and a SI, the UE transmit a SI with TEBS=0 in a MAC-i PDU together with the remaining DCCH/DTCH data.

2. To verify that, when “E-DCH transmission continuation back off" value is set to "0" and UE has not resources to transmit all remaining data and a SI, the UE transmit a SI with TEBS=0 separately with the next MAC-i PDU.

7.1.8.6a.4 Method of test

Initial conditions

System Simulator

1 cell, default parameters, Ciphering Off

SS shall broadcast SIB5/SIB5bis with Common E-DCH/HS-DSCH information with specific message content given below.

User Equipment:

UE is in Enhanced CELL_FACH state with DTCH/DCCH on common E-DCH / HS-DSCH.

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 9.1 using condition “AM Packet to Enhanced CELL_FACH from Enhanced CELL_FACH in PS with SRBs mapped on common E-DCH/HS-DSCH”.

The radio bearer is placed in UE loop-back mode 1 configured to return UL RLC SDUs of the same size as the received DL RLC SDUs.

Test procedure

a) UE has common E-DCH resource and allocated E-RNTI to allow data transmission on DTCH. SS sends absolute grant with value of 30.

b) The SS sends 1 RLC SDU of size 12 bytes on the downlink.

c) The UE has enough resources to transmit all data and SI with TEBS=0. The SS receives looped back data and a SI with TEBS=0 in the same MAC-i PDU on the common E-DCH channel.

d1) After UE has received the HARQ ACK then is the UE performing an implicit release.

NOTE 1: UE is performing an implicit release as “E-DCH transmission continuation back off" value is set to "0" in broadcasted SIB5 and all data have been transmitted.

d2) The SS sends 1 RLC SDU of size 12 bytes on the downlink.

e) The SS checks that original common E-DCH channel has been implicitly released by checking that UE initiates a PRACH preamble and Acquisition Indication for a new common E-DCH channel which is used to loop back the data. SS sends absolute grant with value of 10 allowing UE to return data only.

NOTE 2: An absolute grant of 10 corresponds to AG Index 5, E-TFCI = 1. TBS = 120 bits. With 24 bits for MAC-i/is header of 24 bits this allows 96 bits for data (12 bytes).

f) The SS receives looped back data only in a MAC-i PDU on the common E-DCH channel.

g) The SS receives a MAC-i PDU with SI with TEBS=0 on the common E-DCH channel.

h) After UE has received the HARQ ACK then is the UE performing an implicit release.

NOTE 3: UE is performing an implicit release as “E-DCH transmission continuation back off" value is set to "0" in broadcasted SIB5 and all data have been transmitted.

i) The SS sends 1 RLC SDU of size 12 bytes on the downlink.

j) The SS checks that original common E-DCH channel has been implicitly released by checking that UE initiates a PRACH preamble and Acquisition Indication for a new common E-DCH channel which is used to loop back the data. SS sends absolute grant with value of 30 allowing UE to return data and SI on the same MAC-i PDU.

k) The UE has enough resources to transmit all data and SI with TEBS=0. The SS receives looped back data and a SI with TEBS=0 in the same MAC-i PDU on the common E-DCH channel.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

UE has common E-DCH with E-RNTI allocated. The user plane RAB uses DTCH transmission.

2

Absolute Grant

Serving Grant 30.

(Note 1)

3

RLC SDU

SS sends 1 RLC SDU of size 12 bytes on the downlink

4

RLC SDU

SS checks that UE transmits the loop back data and a SI with TEBS=0 in the same MAC-i PDU on the common E-DCH

5

HARQ ACK

SS acknowledge the received RLC SDU and wait 100 ms for UE to release the resources

6

RLC SDU

SS sends 1 RLC SDU of size 12 bytes

7

<->

UE acquires common E-DCH resource

SS checks that UE perform PRACH Preamble prior to acquiring common E-DCH resource.

8

Absolute Grant

Serving Grant 10.

(Note 2)

9

RLC SDU

SS receives and checks loop back data on the common E-DCH. The SS checks that no SI is received.

10

SI

SS checks that the UE transmit a MAC-I PDU with TEBS=0.

11

HARQ ACK

SS acknowledge the received SI and wait 100 ms for UE to release the resources

12

RLC SDU

SS sends 1 RLC SDU of size 12 bytes

13

<->

UE acquires common E-DCH resource

SS checks that UE perform PRACH Preamble prior to acquiring common E-DCH resource.

14

Absolute Grant

Serving Grant 30.

(Note 1)

15

RLC SDU

SS receives and checks loop back data and a SI with TEBS=0 in the same MAC-i PDU on the common E-DCH.

Note 1: Grant value of 30 guarantees that UE have common resources to be able to transmit remaining data and the scheduling information in the same TTI.

Note 2: Grant value of 10 guarantees that UE have common resources to be able to transmit remaining data only causing the scheduling information to be sent in next TTI.

Specific Message Contents

Use the same message type found in clause 6.1.1 of TS 34.108, with SIB5 configured for common E-DCH / HS-DSCH, with the following exceptions.

System Information Block type 5/System Information Block type 5bis

Information Element

Value/Remark

– Primary CCPCH info

Not Present

– PRACH system information list

– PRACH system information

-PRACH info

– CHOICE mode

FDD

– Available Sub Channel number

‘1111 1111 1111’B

-PRACH partitioning

– Access Service Class

2 Access Service Classes

– ASC Setting

– CHOICE mode

FDD

– Available signature Start Index

0 (ASC#0)

– Available signature End Index

7 (ASC#0)

– Assigned Sub-channel Number

‘0001’B

The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number

– ASC Setting

– CHOICE mode

FDD

– Available signature Start Index

0 (ASC#1)

– Available signature End Index

7 (ASC#1)

– Assigned Sub-channel Number

‘0010’B

The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number

-PRACH power offset

– Preamble Retrans Max

5

– RACH transmission parameters

– Mmax

1

– Common EDCH System Info

– Maximum period for collision resolution phase

8TTI

– E-DCH transmission continuation back off

0TTI

7.1.8.6a.5 Test requirements

– At step 4 the UE shall include data and a SI with TEBS=0 in the same MAC-i PDU.

– At step 7, UE shall perform PRACH preamble and receive Acquisition Indication before looping back data on allocated common E-DCH resource.

– At step 10, UE shall send a MAC-I PDU including a SI with TEBS=0

– At step 13, UE shall perform PRACH preamble and receive Acquisition Indication before looping back data on allocated common E-DCH resource.

7.1.8.7 Physical Channel Failure for EUL in CELL-FACH during initial access preamble

7.1.8.7.1 Definition and Applicability

All UEs which support E-DCH in CELL_FACH

7.1.8.7.2 Conformance Requirement

– If the UE according to subclause 8.5.4A in [7] failed to establish the physical channels, or if the criteria for radio link failure are met as specified in subclause 8.5.6 in [7], then the timer T2 is started. After the expiry of T2 a backoff timer TBO1 is started. Backoff timer TBO1 is set to an integer number NBO1 of 10 ms time intervals, randomly drawn within an interval 0  NBO1min  NBO1  NBO1max (with uniform distribution). NBO1min and NBO1max may be set equal when a fixed delay is desired, and even to zero when no delay other than the one due to persistency is desired. The procedure ends if timer TBO1 expires or the UE performs cell reselection while timer TBO1 is running, whatever occurs first. In case of a cell reselection, the timer TBO1 is stopped.

[…]

When the physical channel establishment for Enhanced Uplink in CELL_FACH state and Idle mode is initiated by the UE, the UE shall considered the physical channel being immediately established.

If the physical layer considers the post-verification of procedure AA failed [29, section 4.3.2.3A], the UE shall consider this as a "physical channel failure".

NOTE: The criteria defined in this subclause only apply in case the UE performs synchronisation procedure AA (FDD only).

[…]

d) The UE shall start transmission on uplink at the time defined for the Enhanced Uplink in CELL_FACH state and IDLE mode in [1] and shall use a post-verification period for confirming the establishment of the downlink physical channel as follows: During the first 40 ms period of the first phase of the downlink synchronisation procedure the UE shall control its transmitter according to a downlink F-DPCH quality criterion as follows:

– When the UE estimates the F-DPCH quality over the first 40 ms period of the first phase of the downlink synchronisation status evaluation to be worse than a threshold Qin, the UE shall shut its transmitter off and consider post-verification failed. Qin is defined implicitly by the relevant tests in [7].

If the post-verification has failed, the UE shall not transmit on uplink and await higher layer orders.

[…]

TS 25.321 11.2.2A , Figure 11.2.2A-2

TS 25.331 8.5.4A

TS 25.214 4.3.2.3A

7.1.8.7.3 Test purpose

To verify that UE detects physical channel failure in the RACH preamble procedure for enhanced uplink in CELL_FACH and ends that access attempt.

7.1.8.7.4 Method of test

Initial conditions

Test case shall be attempted on E-DCH TTI 10msec, irrespective of the device E-DCH category.

System Simulator:

1 cell, default parameters, Ciphering Off.

SS shall broadcast SIB5/SIB5bis with condition B3 “Only for cells which configure common E-DCH and HS-DSCH reception in CELL_FACH”.

User Equipment:

UE: Idle state (state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE.

Test procedure

a) SS does not send F-DPCH.

b) SS transmits the PAGING TYPE 1 with cause terminating conversational call.

c) UE sends an access preamble.

d) SS responds with positive E-AI but does not send F-DPCH.

e) UE detects Physical channel failure

f) UE should end the RACH attempt

g) UE waits for T2 expiry (10ms) + Tbo1 expiry (<= UE shall not attempt another RACH transmission while in waiting for the timer to expire.)

h) UE takes 40 ms to detect the Physical Channel failure at step (d ) after SS has stopped F-DPCH transmission. During this period the UE is not allowed to transmit on uplink, since the additional e-dch transmission back off is set to 5, which means ( (1+5)*10msec tti = 60 msec). Therefore the SS shall not receive the uplink RLC SDU. As in the MAC layer, the check for physical channel failure is done after the data is passed to the physical layer, MAC considers the RRC Connection Request sent although it is actually lost at the physical layer.

i) UE then sends another access preamble. The preamble should be triggered by MAC upon receiving RRC connection request from RRC after T300 expiry.

j) SS responds with E-AI and sends F-DPCH as per normal RACH attempt.

k) The UE sends an RRC connection request

l) SS sends RRC Connection Reject to terminate the procedure

Expected sequence

Step

Direction

Message

Comments

UE

SS

SS does not transmit F-DPCH.

1

ß

Paging Type 1

SS starts to transmit this message on the PCCH at the correct paging occasion with cause “Terminating Interactive Call”

2

Access Preamble

3

ß

AICH = POS ACQUISITION IND

4

SS waits for for the expiry of T300 (minus tolerances) and checks that UE shall not send any RLC PDUs or perform a new Access Preamble.

UE takes 40 ms to detect the physcial channel failure, but due to the value of “Additional E-DCH transmission back off”, no E-DPDCH transmissiong is allowed for 60 ms, therefore the UE will not transmit any RLC PDU or perform a new Access Preamble until the expiry of T300

4a

Void

4b

SS establishes the required physical channels including F-DPCH as per normal enhanced RACH preamble procedure

5

Access Preamble

UE initiates new PRACH preamble attempt after the expiry of T300

6

ß

AICH = POS ACQUISITION IND

7

<->

UE acquires common E-DCH resource

8

RRC CONNECTION REQ

Establishment cause=”Terminating Interactive call”

9

ß

RRC CONNECTION REJECT

IE "wait time" set to 0 to bring the UE to idle mode.

Specific Message Contents

RRC CONNECTION REJECT (Step 9)

Use the same message type found in clause 9 of TS 34.108, with the following exception.

Information Element

Value/remark

Initial UE Identity

Same as the type and value defined in RRC CONNECTION REQUEST message (step 8)

Reject Cause

Congestion

Wait time

0 second

7.1.8.7.5 Test requirements

1. At step 5, SS checks that UE sends another preamble.

2. At step 8 , UE should send an RRC Connection Request.

7.1.8.8 Radio Link Failure for Enhanced UL in CELL-FACH with DTCH/DCCH active

7.1.8.8.1 Definition and Applicability

All UEs which support E-DCH in CELL_FACH

7.1.8.8.2 Conformance Requirement

For FDD, in CELL_FACH state and Idle mode, in conjunction with the Enhanced Uplink in CELL_FACH state, after receiving an indication from layer 1 that physical layer transmission stopped caused by an DL out-of-synchronisation, the UE shall:

1> consider it as a "Radio link failure".

[…]

The E-DCH enhanced physical random access transmission procedure is completed with release of the allocated common E-DCH resource, if one of the following conditions is fulfilled:

– If the UE according to subclause 8.5.4A in [7] failed to establish the physical channels, or if the criteria for radio link failure are met as specified in subclause 8.5.6 in [7], then the timer T2 is started. After the expiry of T2 a backoff timer TBO1 is started. Backoff timer TBO1 is set to an integer number NBO1 of 10 ms time intervals, randomly drawn within an interval 0  NBO1min  NBO1  NBO1max (with uniform distribution). NBO1min and NBO1max may be set equal when a fixed delay is desired, and even to zero when no delay other than the one due to persistency is desired. The procedure ends if timer TBO1 expires or the UE performs cell reselection while timer TBO1 is running, whatever occurs first. In case of a cell reselection, the timer TBO1 is stopped.

[…]

References(s)

TS 25.331 8.5.6

TS 25.321 11.2.2A

7.1.8.8.3 Test purpose

To verify that UE releases common E-DCH resource in the event of radio link failure when DTCH/DCCH is active in Enhanced CELL_FACH state.

7.1.8.8.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

System Information Block type 5 (FDD)

Use the default parameter values for the system information block 5 with the same type specified in clause

6.1.0b of TS 34.108 for common E-DCH and HS-DSCH reception in CELL_FACH, with the following exceptions:

Information Element

Value/Remark

– Common EDCH System Info

– E-DCH transmission continuation back off

Infinity

User Equipment:

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed with all the parameters as specified in the procedure, with the exception that the default Radio Bearer is replaced with the RB according to clause 6.10.2.4.6.3 using condition A29 with RB mapping to HS-DSCH and E-DCH. The MAC-d flow of the user plane RB is configured for scheduled transmissions. The logical channel, transport channel and common MAC-d flow identities are set to:

Logical Channel ID

MAC-d flow (UL)

Priority

Comment

7 (LCH1)

2

8

RB25

Note: The RAB combination also includes SRBs on E-DCH on MAC-d flow 1 which is not used in the testcase

The UE is placed into UE test loop mode 1 with the UL SDU size set to 39 octets for RB25

Test procedure

  1. SS transmits 1 SDU of size 40 bytes
  2. SS waits until data is received and checks that all the data is received. SS checks that there is no RACH preamble prior to data loopback because UE has common E-DCH resource
  3. SS stops F-DPCH transmission for 5 seconds. This should be sufficient time for UE to detect Radio Link Failure
  4. SS transmits 1 SDU of size 40 bytes
  5. UE shall acquire common E-DCH resource as SS resumes F-DPCH following positive AI. SS waits until data is received and checks that all the data is received. SS checks that there is RACH preamble prior to data loopback
  6. SS opens the test loop and releases the radio bearer

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

RB ESTABLISHMENT

See generic procedures, UE has acquired common E-DCH resource and uses this for UL transmission.

2

Close UE test loop

2a

Absolute Grant

Serving Grant 4

3

DOWNLINK RLC SDU

SDU size = 40 Octets

4

UPLINK RLC SDU

The SS checks length and content of the received RLC SDUs. SS checks that there is no RACH preamble prior to data loopback on common E-DCH resource.

5

SS stops F-DPCH transmission

6

Wait 5 seconds. This time is sufficient for UE to detect Radio Link failure and release common E-DCH resource

7

DOWNLINK RLC SDU

SDU size = 40 Octets

8

<->

UE acquires common E-DCH resource

SS checks for preamble PRACH and sets up the necessary channels, including the resumption of F-DPCH transmission, and takes the steps necessary for UE to acquire common E-DCH resource

8a

Absolute Grant

Serving Grant 4

9

UPLINK RLC SDU

The SS checks length and content of the received RLC SDUs.

10

OPEN UE TEST LOOP PROCEDURE

11

RB RELEASE

7.1.8.8.5 Test requirements

– at step 4, the UE shall return 1 SDU with the same content as the transmitted SDU on common E-DCH resource without RACH preamble.

– at step 8, UE shall send RACH preamble.

– t step 9 the UE shall return 1 SDU with the same content as the transmitted SDU on common E-DCH resource.

7.1.8.9 CCCH transmission E-DCH access, the UL transmission within the Scheduling Windows

7.1.8.9.1 Definition and Applicability

1.28Mcps TDD UEs which support E-DCH in CELL_FACH

7.1.8.9.2 Conformance Requirement

Extract from 25.331 8.5.46:

For 1.28 Mcps TDD, whenever the variable COMMON_E_DCH_TRANSMISSION is set to TRUE, the UE shall:

1> if CCCH message is submitted for transmission on the uplink and if the variable E_RNTI is not set:

2> select a common E-RNTI according to subclause 8.5.50;

2> perform E-RUCCH transmission procedure, using the selected common E-RNTI as UE identity;

2> use the selected common E-RNTI as UE identity in the E-AGCH reception procedure in the physical layer in the common E-RNTI scheduling window according to subclause 8.5.50.

1> else:

2> perform E-RUCCH transmission procedure according to the stored PRACH configuration (see [60]), using the value stored in the variable E_RNTI as UE identity;

2> use the value stored in the variable E_RNTI as UE identity in the E-AGCH reception procedure in the physical layer.

1> perform E-HICH reception procedures for the serving E-DCH radio link;

1> perform E-PUCH transmission procedures according to the stored E-PUCH configuration;

1> perform the inclusion of MAC-d PDUs and MAC-c PDUs in a MAC-i PDU for logical channels belonging to the MAC-d flows in accordance with the received scheduling grant on E-AGCH (see [15]).

NOTE: For 1.28 Mcps TDD, when performing E-DCH transmission in CELL_FACH state and Idle mode, the UE shall use the tables of transport block size for the E-DCH physical layer category 3 as specified in [15].

…

When the IE "Common E-RNTI Information" is included in System Information Block type 5, and if the UE is in CELL_FACH state or Idle mode, and if the variable E_RNTI is not set, UE shall use a common E-RNTI for CCCH transmission (i.e. the common E-RNTI identifies the initial access, including RRC connection request and cell update after cell re-selection):

1> configure the MAC layer with the information in the IE(s) "Common E-RNTI information";

1> when a CCCH message is to be sent, and if the variable E_RNTI is not set, the MAC layer operates as follows:

2> select an E-RUCCH;

2> select the instance of the IE(s) "Common E-RNTI information" which is related to the selected E-RUCCH;

2> select a common E-RNTI which is related to the selected E-RUCCH according to the following procedure:

3> compile a list of candidate common E-RNTI group from the selected instance of the IE(s) "Common E-RNTI information" in the order of appearance in System Information Block type 5, and select a common E-RNTI group from the list of candidate Common E-RNTI groups based on the E-RUCCH transmission occasion:

"Index of selected Common E-RNTI group" = SFNE-RUCCH mod K, for TTI of E-RUCCH = 10ms;

or "Index of selected Common E-RNTI group" = SFN’E-RUCCH mod K, for TTI of E-RUCCH = 5ms;

Where K is the number of E-RNTI groups related to the E-RUCCH; SFNE-RUCCH or SFN’E-RUCCH is the frame or sub-frame on which the E-RUCCH shall be sent [33].

3> select a common E-RNTI randomly amongst the candidate the candidate E-RNTIs in the selected group.

2> use the value of the selected common E-RNTI as UE identity in current E-RUCCH transmission, and in the E-AGCH reception within the common E-RNTI scheduling window which is of K frames or K sub-frames length.

References(s)

3GPP TS 25.331 clause 8.5.46, 8.5.50.

7.1.8.9.3 Test purpose

The purpose of the test case is to verify support of CCCH transmission E-DCH with common E-RNTI.

7.1.8.9.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE.

Test procedure

  1. SS transmits the PAGING TYPE 1 with cause BCCH modification.
  2. SS transmits the changed system information SIB5 / SIB5 bis. UE updates the stored SIBs. The new SIB 5 / SIB5-bis contains the common E-DCH related information.
  3. SS transmits the PAGING TYPE 1 with cause terminating conversational call.
  4. SS receives E-RUCCH
  5. SS transmits a AGCH.
  6. SS receives the RRC CONNECTION REQ sent by UE
  7. SS transmits a RRC CONNECTION REJECT.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

ß

Paging Type 1

BCCH change ind

2

ß

SIB1 and SIB 5/ SIB5 bis

SS transmits E-DCH common information to UE

3

SS waits 5s (to ensure that the UE has time to read the new system information)

4

ß

Paging Type 1

SS starts to transmit this message continuously on the PCCH at the correct paging occasion with cause “Terminating conversational call”

5

®

E-RUCCH

SS checks UE use correct common E-RNTI.

6

ß

AGCH

7

®

RRC CONNECTION REQ

8

ß

RRC CONNECTION REJECT

Specific Message Contents

PAGING TYPE 1 (Step 1)

Information Element

Value/remark

Message Type

Paging record list

Not Present

BCCH modification info

MIB Value Tag

Set to (Current MIB value tag + 1)

BCCH Modification time

Not Present

SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis (Step 2)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element

Value/remark

– Common EDCH system information

-CHOICE Mode

TDD

– CHOICE TDD option

1.28 Mcps TDD

– CCCH transmission info

– Common E-RNTI info

– Common E-RNTI information

– Starting E-RNTI

‘1111 1010 1010 1010′

– Number of group

4

– Number of E-RNTI per group

1

PAGING TYPE 1 (Step 3)

Information Element

Value/remark

Message Type

Paging record list

Only 1 entry

Paging record

– CHOICE Used paging identity

CN identity

– Paging Cause

Terminating Call with one of the supported services

– CN Domain Identity

Supported Domain (PS Domain or CS Domain)

– CHOICE UE Identity

Local (P)TMSI

– Routing parameter

Same as registered TMSI or P-TMSI

BCCH modification info

Not Present

7.1.8.9.5 Test requirements

1. At step 5 , SS checks UE use correct common E-RNTI.

7.1.8.10 DTCH/DCCH transmission with E-RUCCH access for dedicated control signalling or dedicated user data when dedicated E-RNTI is allocated

7.1.8.10.1 Definition and Applicability

1.28Mcps TDD UEs which support E-DCH in CELL_FACH

7.1.8.10.2 Conformance Requirement

Extract from 25.331 8.5.46:

For 1.28 Mcps TDD, whenever the variable COMMON_E_DCH_TRANSMISSION is set to TRUE, the UE shall:

1> if CCCH message is submitted for transmission on the uplink and if the variable E_RNTI is not set:

2> select a common E-RNTI according to subclause 8.5.50;

2> perform E-RUCCH transmission procedure, using the selected common E-RNTI as UE identity;

2> use the selected common E-RNTI as UE identity in the E-AGCH reception procedure in the physical layer in the common E-RNTI scheduling window according to subclause 8.5.50.

1> else:

2> perform E-RUCCH transmission procedure according to the stored PRACH configuration (see [60]), using the value stored in the variable E_RNTI as UE identity;

2> use the value stored in the variable E_RNTI as UE identity in the E-AGCH reception procedure in the physical layer.

1> perform E-HICH reception procedures for the serving E-DCH radio link;

1> perform E-PUCH transmission procedures according to the stored E-PUCH configuration;

1> perform the inclusion of MAC-d PDUs and MAC-c PDUs in a MAC-i PDU for logical channels belonging to the MAC-d flows in accordance with the received scheduling grant on E-AGCH (see [15]).

NOTE: For 1.28 Mcps TDD, when performing E-DCH transmission in CELL_FACH state and Idle mode, the UE shall use the tables of transport block size for the E-DCH physical layer category 3 as specified in [15].

References(s)

3GPP TS 25.331 clause 8.5.46.

7.1.8.10.3 Test purpose

The purpose of the test case is to verify support of DTCH/DCCH transmission with E-RUCCH access for dedicated control signalling or dedicated user data when dedicated E-RNTI is allocated

7.1.8.10.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108 with a dedicated E-RNTI is allocated.

Test procedure

a) The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.5.4.7.2 using condition A11 as specified in clause 9.1 of TS 34.108.. See note 1.

b) The SS closes the test loop using UE test loop mode 1 and configuring the UL RLC SDU size to be equal to the received DL SDU size (i.e. not setting the UL RLC SDU size parameter).

c) The SS transmits one RLC SDU of size 320 bits,

d) The SS waits for an E-RUCCHwith SI to be received that indicates that the one RLC SDU is available for transmission (can be identified from the content of the SI)

e) The SS issues an absolute grant that allows the UE to send

f) The SS waits until data is received and verifies that the looped back SDU has correct content

g) The SS opens the UE test loop.

h) The SS release the radio bearer.

i) The SS may optionally deactivate the radio bearer test mode.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

<–

SYSTEM INFORMATION (BCCH)

Broadcast

2

<–

PAGING TYPE 1 (PCCH)

Paging (PS domain, P-TMSI)

3

–>

RRC CONNECTION REQUEST (CCCH)

RRC

4

<–

RRC CONNECTION SETUP (CCCH)

RRC

5

–>

RRC CONNECTION SETUP COMPLETE (DCCH)

RRC

6

–>

SERVICE REQUEST (DCCH)

GMM

7

<–

SECURITY MODE COMMAND

RRC see note 1

8

–>

SECURITY MODE COMPLETE

RRC see note 1

9

<–

ACTIVATE RB TEST MODE (DCCH)

TC

10

–>

ACTIVATE RB TEST MODE COMPLETE (DCCH)

TC

11

<–

RADIO BEARER SETUP (DCCH)

RRC. For the PS radio bearer the ‘pdcp info’ IE shall be omitted.

12

–>

RADIO BEARER SETUP COMPLETE (DCCH)

RRC

13

<–

CLOSE UE TEST LOOP (DCCH)

TC

UE test mode 1 with no "LB Setup RB IE#k" parameter set (UE shall return an UL RLC SDU with the same size as the received RLC SDU in downlink)

14

–>

CLOSE UE TEST LOOP COMPLETE (DCCH)

TC

15

SS

The SS creates one RLC SDU

16

<–

DOWNLINK RLC SDU#1

Send test data. The MAC-ehs PDU contains 4 RLC SDUs

17

à

E-RUCCH with SI indicating 1 RLC SDU

This can be verified from the indicated Total E-DCH Buffer Status (TEBS)

18

<–

Absolute grant allowing the UE to transmit at maximum bit rate.

19

–>

UPLINK RLC SDU

The SS checks that the content of the received UL RLC SDU is correct

20

<–

OPEN UE TEST LOOP (DCCH)

TC

21

–>

OPEN UE TEST LOOP COMPLETE (DCCH)

TC

22

RB RELEASE

RRC

23

<–

DEACTIVATE RB TEST MODE

TC

Optional step

24

–>

DEACTIVATE RB TEST MODE COMPLETE

TC

Optional step

Note 1: In addition to activate integrity protection Step 6 and Step 7 are inserted in order to stop T3317 timer in the UE, which starts after transmitting SERVICE REQUEST message.

7.1.8.10.5 Test requirements

1. At step 19 , SS checks UE send correct RLC SDU.