18.1.6 Combinations on DPCH, HS-PDSCH and E-DPDCH

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

18.1.6.1 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH

18.1.6.1.1 Conformance requirement

The UE shall be able to establish the UTRAN requested radio bearers within the UE’s signalled radio access capabilities.

The UE shall correctly transfer user data from peer to peer RLC entities according to the requested radio bearer configuration.

Reference(s)

3GPP TS 25.331, clause 8.2.1

3GPP TS 25.2xx series (Physical Layer)

3GPP TS 25.321 (MAC)

3GPP TS 25.322 (RLC)

18.1.6.1.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.2:

1. To verify that the UE is able to establish the radio bearer combination.

2. To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.

18.1.6.1.3 Method of test

The following parameters are specific for this test case:

Parameter

Value

MAC-hs receiver window size

16

HS-DSCH MAC-d PDU size

336

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

HS-DSCH Category

HS-PDSCH

Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum

TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

370

1

QPSK

12

2

6

512

336

370

1

QPSK

12

3

8

512

336

370

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

358

1

QPSK

8

8

6

1536

336

358

1

QPSK

8

9

8

2047

336

358

1

QPSK

8

10

4

2047

336

370

1

QPSK

8

11

6

1024

336

370

1

QPSK

8

12

8

1024

336

370

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size.

The generic test procedure in 14.1.4.1 is run for each sub-test. Testing of UE supporting UE E-DCH physical layer category 6 shall be performed in accordance to test parameters, sub-tests and test points for UE HS-DSCH physical layer category 6. Testing of UE supporting UE HS-DSCH physical layer category 13 to 15 shall be performed in accordance to test parameters, sub-tests and test points for UE HS-DSCH physical layer category 10.

Sub-tests:

Sub-test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(note 2)

Test data

size

(note 3)

1

1 to 6

5ms, Table 0

4

312

312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.1.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.1a Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH/ UL 16QAM

18.1.6.1a.1 Conformance requirement

The UE shall be able to establish the UTRAN requested radio bearers within the UE’s signalled radio access capabilities.

The UE shall correctly transfer user data from peer to peer RLC entities according to the requested radio bearer configuration.

Reference(s)

3GPP TS 25.331, clause 8.2.1

3GPP TS 25.2xx series (Physical Layer)

3GPP TS 25.321 (MAC)

3GPP TS 25.322 (RLC)

18.1.6.1a.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.2:

1. To verify that the UE is able to establish the radio bearer combination.

2. To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.

18.1.6.1a.3 Method of test

The following parameters are specific for this test case:

Parameter

Value

MAC-hs receiver window size

16

HS-DSCH MAC-d PDU size

336

E-DCH

Category

RLC Transmission window size

6

1536

HS-DSCH Category

HS-PDSCH

Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum

TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

370

1

QPSK

12

2

6

512

336

370

1

QPSK

12

3

8

512

336

370

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

358

1

QPSK

8

8

6

1536

336

358

1

QPSK

8

9

8

2047

336

358

1

QPSK

8

10

4

2047

336

370

1

QPSK

8

11

6

1024

336

370

1

QPSK

8

12

8

1024

336

370

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size.

The generic test procedure in 14.1.4.1 is run for each sub-test. Testing of UE supporting UE HS-DSCH physical layer category 13 to 15 shall be performed in accordance to test parameters, sub-tests and test points for UE HS-DSCH physical layer category 10.

Sub-tests:

Sub-test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(note 2 &4)

Test data

size

(note 3)

1

6

5ms, Table 0

8

7992

312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

NOTE 4: The UL RLC SDU size is calculated as 25*320-8= 7992, such that TB size 8455 corresponding to E-TFCI 103 will be selected. With PLnon-max = 0.84, [(8455+24[CRC] ) *3 [TC] ]= 25437 bits. 25437* PLnon-max =21367 , this guarantees as per algorithm in 25.222 clause 4.8.4.1,16QAM to be selected [2M2+2M4]

18.1.6.1a.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with first 312 bits equal to the content of the DL RLC SDU sent by the SS.

18.1.6.1b Interactive or background / UL:64 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (MIMO)

18.1.6.1b.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.1b.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.6.4 for the QPSK, 16QAM and MIMO case using the downlink enhanced Layer 2 configuration with Flexible RLC and MAC-ehs .

18.1.6.1b.3 Method of test

NOTE: The reference to UE Categories refers to the UE capability as signalled in the Rel-8 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.

The following parameters are specific for this test case:

Parameter

Value

Comments

Radio bearer

TS 34.108, clause 6.11.5.4.6.4 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs).

The generic test procedure in 18.1.1.7 is run for each sub-test for test execution 1 and 2.

Execution counter

Downlink Modulation Scheme (M1)

MIMO data flow#1

Downlink Modulation Scheme (M2)

MIMO data flow#2

MIMO

1

QPSK

QPSK

Yes

2

16QAM

16QAM

Yes

3

16QAM

QPSK

Yes

Uplink TFS:

TFI

RB5

(64 kbps, 20 ms TTI)

DCCH

TFS

TF0, bits

0x336

0x148

TF1, bits

1×336

1×148

TF2, bits

2×336

N/A

TF3, bits

3×336

N/A

TF4, bits

4×336

N/A

Uplink TFCS:

TFCI

(RB5, DCCH)

UL_TFC0

(TF0, TF0)

UL_TFC1

(TF1, TF0)

UL_TFC2

(TF2, TF0)

UL_TFC3

(TF3, TF0)

UL_TFC4

(TF4, TF0)

UL_TFC5

(TF0, TF1)

UL_TFC6

(TF1, TF1)

UL_TFC7

(TF2, TF1)

UL_TFC8

(TF3, TF1)

UL_TFC9

(TF4, TF1)

Sub-tests:

Sub-test

UE

Category

Number of HARQ processes

RLC Receiving window size

(note 1)

RLC Trans-mission window size

(note 1)

MAC-d PDU size
(bits)

Uplink TFCS

Under test

Implicitly tested

Restricted UL TFCIs

(note 2)

UL RLC SDU size

(bits)

(note 3)

1

25

12

2047

512

Flexible

UL_TFC1

UL_TFC0, UL_TFC5

UL_TFC0, UL_TFC1,

UL_TFC5,

UL_TFC6

RB5: 312

26

12

2047

512

27

12

2047

512

2

25

12

1024

1024

Flexible

UL_TFC2

UL_TFC0, UL_TFC5

UL_TFC0, UL_TFC1,

UL_TFC2,

UL_TFC5,

UL_TFC7

RB5: 632

26

12

1024

1024

27

12

1024

1024

3

25

16

2047

1024

Flexible

UL_TFC3

UL_TFC0, UL_TFC5

UL_TFC0, UL_TFC1,

UL_TFC3,

UL_TFC5,

UL_TFC8

RB5: 952

26

16

2047

1024

27

16

2047

1024

4

25

16

1024

1024

Flexible

UL_TFC4

UL_TFC0, UL_TFC5

UL_TFC0, UL_TFC1,

UL_TFC4,

UL_TFC5,

UL_TFC9

RB5: 1272

26

16

1024

1024

27

16

1024

1024

NOTE 1: The SS shall configure the RLC transmission and receiver window size depending on the UE category. The values are set to cope with the number of SDUs used in the sub-test and within the UE capabilities for the actual UE category under test.

NOTE 2: UL_TFC0, UL_TFC1 and UL_TFC5 are part of minimum set of TFCIs.

NOTE 3: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
RB5: The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

18.1.6.1b.4 Test requirements

See 18.1.1.7 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE transmitted transport format shall be

– for sub-test 1: TF1 (1×336).

– for sub-test 2: TF2 (2×336).

– for sub-test 3: TF3 (3×336).

– for sub-test 4: TF4 (4×336)

3. At step 18 and for each TFRC test point:
The UE shall for each radio bearer return the equal number RLC SDUs as sent by the SS in downlink. If the downlink RLC SDU size is less than the configured UL RLC SDU for the actual sub-test then the UE shall return RLC SDUs where the first bits of each SDU has the same content as the RLC SDUs sent by the SS in downlink. Otherwise the UE shall return RLC SDUs where the SDU has the same content as the first bits of the RLC SDUs sent by the SS in downlink.

NOTE: The generic test procedure as specified in 18.1.1.7 sends either 2 SDU or 8 SDUs depending on the transport block size under tests. For the case when the downlink SDU size is less than the configured UL SDU size then all data is returned otherwise the returned data is truncated.

18.1.6.1c Interactive or background / UL:64 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH (64QAM+MIMO)

18.1.6.1c.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.1c.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.6.4 for the 64QAM and MIMO case using the downlink enhanced Layer 2 configuration with Flexible RLC and MAC-ehs .

18.1.6.1c.3 Method of test

NOTE: The reference to UE Categories refers to the UE capability as signalled in the Rel-8 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.

The following parameters are specific for this test case:

Parameter

Value

Comments

Radio bearer

TS 34.108, clause 6.11.5.4.6.4 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs).

MAC-ehs receiver window size

16

RLC Transmission window size

See sub-test table

RLC Receiving window size

See sub-test table

The generic test procedure in 18.1.1.7 is run for each sub-test for test execution 1 and 2.

Execution counter

Downlink Modulation Scheme (M1)

MIMO data flow#1

Downlink Modulation Scheme (M2)

MIMO data flow#2

MIMO

1

64QAM

QPSK

Yes

2

64QAM

16QAM

Yes

3

64QAM

64QAM

Yes

Uplink TFS:

TFI

RB5

(64 kbps, 20 ms TTI)

DCCH

TFS

TF0, bits

0x336

0x148

TF1, bits

1×336

1×148

TF2, bits

2×336

N/A

TF3, bits

3×336

N/A

TF4, bits

4×336

N/A

Uplink TFCS:

TFCI

(RB5, DCCH)

UL_TFC0

(TF0, TF0)

UL_TFC1

(TF1, TF0)

UL_TFC2

(TF2, TF0)

UL_TFC3

(TF3, TF0)

UL_TFC4

(TF4, TF0)

UL_TFC5

(TF0, TF1)

UL_TFC6

(TF1, TF1)

UL_TFC7

(TF2, TF1)

UL_TFC8

(TF3, TF1)

UL_TFC9

(TF4, TF1)

Sub-tests:

Sub-test

UE

Category

RLC Receiving window size

(note 1)

RLC Trans-mission window size

(note 1)

MAC-d PDU size
(bits)

Uplink TFCS

Under test

Implicitly tested

Restricted UL TFCIs

(note 2)

UL RLC SDU size

(bits)

(note 3)

Test data size (bits)

(note 4)

1

28,29 and 30

2047

1024

Flexible

UL_TFC4

UL_TFC0, UL_TFC5

UL_TFC0, UL_TFC1,

UL_TFC4,

UL_TFC5,

UL_TFC9

RB5: 1272

See note 4

NOTE 1: The values are set to cope with the number of SDUs used in the sub-test and within the UE capabilities for the actual UE category under test.

NOTE 2: UL_TFC0, UL_TFC1 and UL_TFC5 are part of minimum set of TFCIs.

NOTE 3: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
RB5: The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return one complete UL RLC SDU per UL TTI.

NOTE 4: The test data size and number of DL RLC SDUs for RB5 is dependent on the actual TFRC test point, see the generic test procedure in 18.1.1.7.

18.1.6.1c.4 Test requirements

See 18.1.1.7 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE transmitted transport format shall be

– for sub-test 1: TF4 (4×336)

3. At step 18 and for each TFRC test point:
The UE shall for each radio bearer return the equal number RLC SDUs as sent by the SS in downlink. If the downlink RLC SDU size is less than the configured UL RLC SDU for the actual sub-test then the UE shall return RLC SDUs where the first bits of each SDU has the same content as the RLC SDUs sent by the SS in downlink. Otherwise the UE shall return RLC SDUs where the SDU has the same content as the first bits of the RLC SDUs sent by the SS in downlink.

NOTE: The generic test procedure as specified in 18.1.1.7 sends either 2 SDU or 8 SDUs depending on the transport block size under tests.

18.1.6.2 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL DCH

18.1.6.2.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.2.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.3:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.

18.1.6.2.3 Method of test

See 18.1.6.1.3.

18.1.6.2.4 Test requirements

See 18.1.6.1.4.

18.1.6.3 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH

18.1.6.3.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.3.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.4:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.

18.1.6.3.3 Method of test

See 18.1.6.1.3.

18.1.6.3.4 Test requirements

See 18.1.6.1.4.

18.1.6.3a Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] with Flexible RLC, MAC-ehs and MAC-i/is / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH with MAC-ehs and MAC-i/is

18.1.6.3a.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.3a.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.3 and for the case when Flexible RLC and MAC-i/is is configured:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.

18.1.6.3a.3 Method of test

NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-7 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.

NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.

The following parameters are specific for this test case:

Parameter

Value

Radio bearer

TS 34.108, clause 6.11.5.4.7.3 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-i/is) and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4.

MAC-ehs receiver window size

16

HS-DSCH MAC-d PDU size

336

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

HS-DSCH Category

HS-PDSCH

Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum

TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

368

1

QPSK

12

2

6

512

336

368

1

QPSK

12

3

8

512

336

368

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

368

1

QPSK

9

8

6

1536

336

368

1

QPSK

9

9

8

1536

336

368

1

QPSK

9

10

4

2047

336

376

1

QPSK

9

11

6

2047

336

376

1

QPSK

9

12

8

2047

336

376

1

QPSK

9

13

4

2560

336

392

1

QPSK

9

14

6

2560

336

392

1

QPSK

9

15

8

2560

336

392

1

QPSK

9

16

4

2047

336

384

1

QPSK

9

17

6

2047

336

384

1

QPSK

9

18

8

2047

336

384

1

QPSK

9

19

4

3072

336

360

1

QPSK

8

20

6

3072

336

360

1

QPSK

8

21

8

3072

336

360

1

QPSK

8

22

4

3584

336

376

1

QPSK

8

23

6

3584

336

376

1

QPSK

8

24

8

3584

336

376

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size is bigger than the “Minimum TBS” that equals maximum MAC-d PDU size under test + the MAC-ehs header size (24 bits).

The generic test procedure in 18.1.1.6 is run for each sub-test.

Sub-tests:

Sub-test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL MAC-d PDU size under test

DL MAC-d PDU size under test

UL RLC SDU size

(note 2)

Test data

size

(note 3)

1

1 to 6

5ms

4

Flexible

Flexible

320

320

NOTE 1: E-DCH TTI and E-TFCI table according to TS 25.321 Annex BC.1.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to UL RLC payload size. This will enable the UE to return the data within one UL TTI (“Use special value of HE field” is configured).

NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size.

18.1.6.3a.4 Test requirements

See 14.1.4.1b for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.4.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.4.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.5:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH in combination with the possible TFCI of the conversional speech radio bearer.

18.1.6.4.3 Method of test

The following parameters are specific for this test case:

Uplink TFS:

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

DCCH

TFS

TF0, bits

1×0

0x103

0x60

0x148

TF1, bits

1×39

1×103

1×60

1×148

TF2, bits

1×81

N/A

N/A

N/A

Uplink TFCS:

TFCI

(RB5, RB6, RB7, DCCH)

UL_TFC0

(TF0, TF0, TF0, TF0)

UL_TFC1

(TF1, TF0, TF0, TF0)

UL_TFC2

(TF2, TF1, TF1, TF0)

UL_TFC3

(TF0, TF0, TF0, TF1)

UL_TFC4

(TF1, TF0, TF0, TF1)

UL_TFC5

(TF2, TF1, TF1, TF1)

Downlink TFS:

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

DCCH

TFS

TF0, bits

1×0

0x103

0x60

0x148

TF1, bits

1×39

1×103

1×60

1×148

TF2, bits

1×81

N/A

N/A

N/A

Downlink TFCS:

TFCI

(RB5, RB6, RB7, DCCH)

DL_TFC0

(TF0, TF0, TF0, TF0)

DL_TFC1

(TF1, TF0, TF0, TF0)

DL_TFC2

(TF2, TF1, TF1, TF0)

DL_TFC3

(TF0, TF0, TF0, TF1)

DL_TFC4

(TF1, TF0, TF0, TF1)

DL_TFC5

(TF2, TF1, TF1, TF1)

Parameter

Value

MAC-hs receiver window size

16

HS-DSCH MAC-d PDU size

336

E-DCH Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

HS-DSCH Category

HS-PDSCH

Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum

TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

370

1

QPSK

12

2

6

512

336

370

1

QPSK

12

3

8

512

336

370

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

358

1

QPSK

8

8

6

1536

336

358

1

QPSK

8

9

8

2047

336

358

1

QPSK

8

10

4

2047

336

370

1

QPSK

8

11

6

1024

336

370

1

QPSK

8

12

8

1024

336

370

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size.

The generic test procedure in 14.1.4.1 is run for each sub-test.

Sub-tests:

Sub-test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

DCH

UL RLC SDU size

(note 3)

Test data

size

(note 4)

DL TFCS

Under test

UL

TFCS

Under test

Implicitly tested

Restricted UL TFCIs

(note 2)

1

1 to 6

5ms, Table 0

4

DL_TFC1

UL_TFC1

DL_TFC0,

DL_TFC3,

UL_TFC0,

UL_TFC3

UL_TFC0, UL_TFC1,

UL_TFC2,

UL_TFC3,

UL_TFC4

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB5: 39

RB6: No data

RB7: No data

RB8: 312

2

1 to 6

5ms, Table 0

4

DL_TFC2

UL_TFC2

DL_TFC0,

DL_TFC3,

UL_TFC0,

UL_TFC3

UL_TFC0, UL_TFC1,

UL_TFC2,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB5: 81

RB6: 103

RB7: 60

RB8: 312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: UL_TFC0, UL_TFC1, UL_TFC2 and UL_TFC3 are part of minimum set of TFCIs.

NOTE 3: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 4: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.4.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At steps 17 to 20 the UE transmitted transport format shall be within the set of restricted TFCIs as specified for the sub-test.

3. At step 18 and for each radio bearer where test data is sent in downlink the UE shall return a RLC SDU with same content as sent in downlink. For radio bearers where no data is sent in downlink then no data shall be received in uplink.

18.1.6.5 Streaming or interactive or background / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL DCH

18.1.6.5.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.5.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.7:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.

18.1.6.5.3 Method of test

The first Streaming or background or interactive / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5 and the second Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6.

The following parameters are specific for this test case and RB5 and RB6:

Parameter

Value

MAC-hs receiver window size

16

HS-DSCH MAC-d PDU size

336

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

HS-DSCH Category

HS-PDSCH

Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum

TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

370

1

QPSK

12

2

6

512

336

370

1

QPSK

12

3

8

512

336

370

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

358

1

QPSK

8

8

6

1536

336

358

1

QPSK

8

9

8

2047

336

358

1

QPSK

8

10

4

2047

336

370

1

QPSK

8

11

6

1024

336

370

1

QPSK

8

12

8

1024

336

370

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size.

The generic test procedure in 14.1.4.1 is run for each sub-test.

Sub-tests:

Sub-test

E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(note 2)

Test data

size

(note 2)

1

1 to 6

5ms, Table 0

4

RB5:312

RB6:312

RB5:312

RB6:312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.5.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU on RB5 and RB6 with same content as sent in downlink.

18.1.6.6 Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.6.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.6.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.8.

18.1.6.6.3 Method of test

The following parameters are specific for this test case:

Parameter

Value

MAC-hs receiver window size

16

RLC Transmission window size

See sub-test table

RLC Receiving window size

See sub-test table

UL parameters:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Downlink TFS:

TFI

RB5

(384 kbps, 10ms)

DCCH

TFS

TF0, bits

0x336

0x148

TF1, bits

1×336

1×148

TF2, bits

2×336

N/A

TF3, bits

4×336

N/A

TF4, bits

8×336

N/A

TF5, bits

12×336

N/A

Downlink TFCS:

TFCI

(RB5, DCCH)

DL_TFC0

(TF0, TF0)

DL_TFC1

(TF1, TF0)

DL_TFC2

(TF2, TF0)

DL_TFC3

(TF3, TF0)

DL_TFC4

(TF4, TF0)

DL_TFC5

(TF5, TF0)

DL_TFC6

(TF0, TF1)

DL_TFC7

(TF1, TF1)

DL_TFC8

(TF2, TF1)

DL_TFC9

(TF3, TF1)

DL_TFC10

(TF4, TF1)

DL_TFC11

(TF5, TF1)

Sub-tests:

The principle used to select sub-tests has been to cover all downlink Interactive Background and Streaming radio bearer.

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1

1 to 6

5ms, Table 0

4

RB5: 312

RB5: 312

2

DL_TFC2

1 to 6

5ms, Table 0

4

RB5: 632

RB5: 632

3

DL_TFC3

1 to 6

5ms, Table 0

4

RB5: 1912

RB5: 1272

4

DL_TFC4

1 to 6

5ms, Table 0

4

RB5: 2552

RB5: 2552

5

DL_TFC5

1 to 6

5ms, Table 0

4

RB5: 3832

RB5: 3832

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.6.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.7 Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.7.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.7.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.9.

18.1.6.7.3 Method of test

The following parameters are specific for this test case:

Parameter

Value

MAC-hs receiver window size

16

RLC Transmission window size

See sub-test table

RLC Receiving window size

See sub-test table

UL parameters:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Downlink TFS:

TFI

RB5

(128 kbps, 20ms)

DCCH

TFS

TF0, bits

0x336

0x148

TF1, bits

1×336

1×148

TF2, bits

2×336

N/A

TF3, bits

4×336

N/A

TF4, bits

8×336

N/A

Downlink TFCS:

TFCI

(RB5, DCCH)

DL_TFC0

(TF0, TF0)

DL_TFC1

(TF1, TF0)

DL_TFC2

(TF2, TF0)

DL_TFC3

(TF3, TF0)

DL_TFC4

(TF4, TF0)

DL_TFC5

(TF0, TF1)

DL_TFC6

(TF1, TF1)

DL_TFC7

(TF2, TF1)

DL_TFC8

(TF3, TF1)

Sub-tests:

The principle used to select sub-tests has been to cover all downlink Interactive Background and Streaming radio bearer.

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1

1 to 6

5ms, Table 0

4

RB5: 312

RB5: 312

2

DL_TFC2

1 to 6

5ms, Table 0

4

RB5: 632

RB5: 632

3

DL_TFC3

1 to 6

5ms, Table 0

4

RB5: 1912

RB5: 1272

4

DL_TFC4

1 to 6

5ms, Table 0

4

RB5: 2552

RB5: 2552

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.7.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.8 Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.8.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.8.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.10.

18.1.6.8..3 Method of test

The following parameters are specific for this test case:

Parameter

Value

MAC-hs receiver window size

16

RLC Transmission window size

See sub-test table

RLC Receiving window size

See sub-test table

UL parameters:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Downlink TFS:

TFI

RB5

(64 kbps, 20ms)

DCCH

TFS

TF0, bits

0x336

0x148

TF1, bits

1×336

1×148

TF2, bits

2×336

N/A

TF3, bits

3×336

N/A

TF4, bits

4×336

N/A

Downlink TFCS:

TFCI

(RB5, DCCH)

DL_TFC0

(TF0, TF0)

DL_TFC1

(TF1, TF0)

DL_TFC2

(TF2, TF0)

DL_TFC3

(TF3, TF0)

DL_TFC4

(TF4, TF0)

DL_TFC5

(TF0, TF1)

DL_TFC6

(TF1, TF1)

DL_TFC7

(TF2, TF1)

DL_TFC8

(TF3, TF1)

Sub-tests:

The principle used to select sub-tests has been to cover all downlink Interactive Background and Streaming radio bearer.

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1

1 to 6

5ms, Table 0

4

RB5: 312

RB5: 312

2

DL_TFC2

1 to 6

5ms, Table 0

4

RB5: 632

RB5: 632

3

DL_TFC3

1 to 6

5ms, Table 0

4

RB5: 952

RB5: 952

4

DL_TFC4

1 to 6

5ms, Table 0

4

RB5: 1272

RB5: 1272

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.8.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.9 Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 32 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.9.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.9.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause . 6.11.5.4.7.11

18.1.6.9..3 Method of test

The following parameters are specific for this test case:

Parameter

Value

MAC-hs receiver window size

16

RLC Transmission window size

See sub-test table

RLC Receiving window size

See sub-test table

UL parameters:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Downlink TFS:

TFI

RB5

(64 kbps, 20ms)

DCCH

TFS

TF0, bits

0x336

0x148

TF1, bits

1×336

1×148

TF2, bits

2×336

N/A

Downlink TFCS:

TFCI

(RB5, DCCH)

DL_TFC0

(TF0, TF0)

DL_TFC1

(TF1, TF0)

DL_TFC2

(TF2, TF0)

DL_TFC3

(TF0, TF1)

DL_TFC4

(TF1, TF1)

DL_TFC5

(TF2, TF1)

Sub-tests:

The principle used to select sub-tests has been to cover all downlink Interactive Background and Streaming radio bearer.

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1

1 to 6

5ms, Table 0

4

RB5: 312

RB5: 312

2

DL_TFC2

1 to 6

5ms, Table 0

4

RB5: 632

RB5: 632

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.9.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.10 Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 64 kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.10.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.10.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.12 .

18.1.6.10..3 Method of test

The following parameters are specific for this test case:

Parameter

Value

MAC-hs receiver window size

16

RLC Transmission window size

See sub-test table

RLC Receiving window size

See sub-test table

UL parameters:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Downlink TFS:

TFI

RB5 +RB6

(64 kbps, 20ms)

DCCH

TFS

TF0, bits

0x340

0x148

TF1, bits

1×340

1×148

TF2, bits

2×340

N/A

TF3, bits

3×340

N/A

TF4, bits

4×340

N/A

Downlink TFCS:

TFCI

(RB5+RB6, DCCH)

DL_TFC0

(TF0, TF0)

DL_TFC1

(TF1, TF0)

DL_TFC2

(TF2, TF0)

DL_TFC3

(TF3,TF0

DL_TFC4

(TF4,TF0)

DL_TFC5

(TF0,TF1)

DL_TFC6

(TF1,TF1)

DL_TFC7

(TF2,TF1)

DL_TFC8

(TF3,TF1)

DL_TFC9

(TF4,TF1)

Sub-tests:

The principle used to select sub-tests has been to cover all downlink Interactive Background and Streaming radio bearer.

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1

1 to 6

5ms, Table 0

4

RB5: 312

RB5: 312

2

DL_TFC2

1 to 6

5ms, Table 0

4

RB5: 632

RB5: 632

3

DL_TFC3

1 to 6

5ms, Table 0

4

RB5: 952

RB5: 952

4

DL_TFC4

1 to 6

5ms, Table 0

4

RB5: 1272

RB5: 1272

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.10.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.11 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.11.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.11.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.13.

18.1.6.11.3 Method of test

UL parameters:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Uplink TFS:

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

DCCH

TFS

TF0, bits

1×0

0x103

0x60

0x148

TF1, bits

1×39

1×103

1×60

1×148

TF2, bits

1×81

N/A

N/A

N/A

Uplink TFCS:

TFCI

(RB5, RB6, RB7, DCCH)

UL_TFC0

(TF0, TF0, TF0, TF0)

UL_TFC1

(TF1, TF0, TF0, TF0)

UL_TFC2

(TF2, TF1, TF1, TF0)

UL_TFC3

(TF0, TF0, TF0, TF1)

UL_TFC4

(TF1, TF0, TF0, TF1)

UL_TFC5

(TF2, TF1, TF1, TF1)

Downlink TFS:

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

RB8

(384 kbps, 10 ms)

DCCH

TFS

TF0, bits

1×0

0x103

0x60

0x336

0x148

TF1, bits

1×39

1×103

1×60

1×336

1×148

TF2, bits

1×81

N/A

N/A

2×336

N/A

TF3, bits

N/A

N/A

N/A

4×336

N/A

TF4, bits

N/A

N/A

N/A

8×336

N/A

TF5, bits

N/A

N/A

N/A

12×336

N/A

Downlink TFCS:

TFCI

(RB5, RB6, RB7, RB8, DCCH)

DL_TFC0

(TF0, TF0, TF0, TF0, TF0)

DL_TFC1

(TF1, TF0, TF0, TF0, TF0)

DL_TFC2

(TF2, TF1, TF1, TF0, TF0)

DL_TFC3

(TF0, TF0, TF0, TF1, TF0)

DL_TFC4

(TF1, TF0, TF0, TF1, TF0)

DL_TFC5

(TF2, TF1, TF1, TF1, TF0)

DL_TFC6

(TF0, TF0, TF0, TF2, TF0)

DL_TFC7

(TF1, TF0, TF0, TF2, TF0)

DL_TFC8

(TF2, TF1, TF1, TF2, TF0)

DL_TFC9

(TF0, TF0, TF0, TF3, TF0)

DL_TFC10

(TF1, TF0, TF0, TF3, TF0)

DL_TFC11

(TF2, TF1, TF1, TF3, TF0)

DL_TFC12

(TF0, TF0, TF0, TF4, TF0)

DL_TFC13

(TF1, TF0, TF0, TF4, TF0)

DL_TFC14

(TF2, TF1, TF1, TF4, TF0)

DL_TFC15

(TF0, TF0, TF0, TF5, TF0)

DL_TFC16

(TF1, TF0, TF0, TF5, TF0)

DL_TFC17

(TF2, TF1, TF1, TF5, TF0)

DL_TFC18

(TF0, TF0, TF0, TF0, TF1)

DL_TFC19

(TF1, TF0, TF0, TF0, TF1)

DL_TFC20

(TF2, TF1, TF1, TF0, TF1)

DL_TFC21

(TF0, TF0, TF0, TF1, TF1)

DL_TFC22

(TF1, TF0, TF0, TF1, TF1)

DL_TFC23

(TF2, TF1, TF1, TF1, TF1)

DL_TFC24

(TF0, TF0, TF0, TF2, TF1)

DL_TFC25

(TF1, TF0, TF0, TF2, TF1)

DL_TFC26

(TF2, TF1, TF1, TF2, TF1)

DL_TFC27

(TF0, TF0, TF0, TF3, TF1)

DL_TFC28

(TF1, TF0, TF0, TF3, TF1)

DL_TFC29

(TF2, TF1, TF1, TF3, TF1)

DL_TFC30

(TF0, TF0, TF0, TF4, TF1)

DL_TFC31

(TF1, TF0, TF0, TF4, TF1)

DL_TFC32

(TF2, TF1, TF1, TF4, TF1)

DL_TFC33

(TF0, TF0, TF0, TF5, TF1)

DL_TFC34

(TF1, TF0, TF0, TF5, TF1)

DL_TFC35

(TF2, TF1, TF1, TF5, TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC19

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB5: 39

RB6: No data

RB7: No data

RB8: No data

2

DL_TFC2,

DL_TFC20

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB5: 81

RB6: 103

RB7: 60

RB8: No data

3

DL_TFC3,

DL_TFC21

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB5: No data

RB6: No data

RB7: No data

RB8: 312

4

DL_TFC4,

DL_TFC22

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB5: 39

RB6: No data

RB7: No data

RB8: 312

5

DL_TFC5,

DL_TFC23

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB5: 81

RB6: 103

RB7: 60

RB8: 312

6

DL_TFC6,

DL_TFC24

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 632

RB5: No data

RB6: No data

RB7: No data

RB8: 632

7

DL_TFC7,

DL_TFC25

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 632

(note 3)

RB5: 39

RB6: No data

RB7: No data

RB8: 632

8

DL_TFC8,

DL_TFC26

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 632

RB5: 81

RB6: 103

RB7: 60

RB8: 632

9

DL_TFC9,

DL_TFC27

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 1272

RB5: No data

RB6: No data

RB7: No data

RB8: 1272

10

DL_TFC10,

DL_TFC28

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 1272

RB5: 39

RB6: No data

RB7: No data

RB8: 1272

11

DL_TFC11,

DL_TFC29

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 1272

RB5: 81

RB6: 103

RB7: 60

RB8: 1272

12

DL_TFC12,

DL_TFC30

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 2552

RB5: No data

RB6: No data

RB7: No data

RB8: 2552

13

DL_TFC13,

DL_TFC31

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 2552

RB5: 39

RB6: No data

RB7: No data

RB8: 2552

14

DL_TFC14,

DL_TFC32

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 2552

RB5: 81

RB6: 103

RB7: 60

RB8: 2552

15

DL_TFC15,

DL_TFC33

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 3832

RB5: No data

RB6: No data

RB7: No data

RB8: 3832

16

DL_TFC16,

DL_TFC34

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 3832

RB5: 39

RB6: No data

RB7: No data

RB8: 3832

17

DL_TFC17,

DL_TFC35

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 3832

RB5: 81

RB6: 103

RB7: 60

RB8: 3832

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.11.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.12 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.12.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.12.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.14.

18.1.6.12.3 Method of test

UL parameters for E-DCH:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Uplink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x148

TF1, bits

1×39

1×103

1×60

1×148

TF2, bits

1×81

N/A

N/A

N/A

Uplink TFCS:

TFCI

(RB5, RB6, RB7, DCCH)

UL_TFC0

(TF0, TF0, TF0, TF0)

UL_TFC1

(TF1, TF0, TF0, TF0)

UL_TFC2

(TF2, TF1, TF1, TF0)

UL_TFC3

(TF0, TF0, TF0, TF1)

UL_TFC4

(TF1, TF0, TF0, TF1)

UL_TFC5

(TF2, TF1, TF1, TF1)

Downlink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

RB8

(64 kbps,

20 ms TTI)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x336

0x148

TF1, bits

1×39

1×103

1×60

1×336

1×148

TF2, bits

1×81

N/A

N/A

2×336

N/A

TF3, bits

N/A

N/A

N/A

3×336

N/A

TF4, bits

N/A

N/A

N/A

4×336

N/A

Downlink TFCS:

TFCI

(RB5, RB6, RB7, RB8, DCCH)

DL_TFC0

(TF0, TF0, TF0, TF0, TF0)

DL_TFC1

(TF1, TF0, TF0, TF0, TF0)

DL_TFC2

(TF2, TF1, TF1, TF0, TF0)

DL_TFC3

(TF0, TF0, TF0, TF1, TF0)

DL_TFC4

(TF1, TF0, TF0, TF1, TF0)

DL_TFC5

(TF2, TF1, TF1, TF1, TF0)

DL_TFC6

(TF0, TF0, TF0, TF2, TF0)

DL_TFC7

(TF1, TF0, TF0, TF2, TF0)

DL_TFC8

(TF2, TF1, TF1, TF2, TF0)

DL_TFC9

(TF0, TF0, TF0, TF3, TF0)

DL_TFC10

(TF1, TF0, TF0, TF3, TF0)

DL_TFC11

(TF2, TF1, TF1, TF3, TF0)

DL_TFC12

(TF0, TF0, TF0, TF4, TF0)

DL_TFC13

(TF1, TF0, TF0, TF4, TF0)

DL_TFC14

(TF2, TF1, TF1, TF4, TF0)

DL_TFC15

(TF0, TF0, TF0, TF0, TF1)

DL_TFC16

(TF1, TF0, TF0, TF0, TF1)

DL_TFC17

(TF2, TF1, TF1, TF0, TF1)

DL_TFC18

(TF0, TF0, TF0, TF1, TF1)

DL_TFC19

(TF1, TF0, TF0, TF1, TF1)

DL_TFC20

(TF2, TF1, TF1, TF1, TF1)

DL_TFC21

(TF0, TF0, TF0, TF2, TF1)

DL_TFC22

(TF1, TF0, TF0, TF2, TF1)

DL_TFC23

(TF2, TF1, TF1, TF2, TF1)

DL_TFC24

(TF0, TF0, TF0, TF3, TF1)

DL_TFC25

(TF1, TF0, TF0, TF3, TF1)

DL_TFC26

(TF2, TF1, TF1, TF3, TF1)

DL_TFC27

(TF0, TF0, TF0, TF4, TF1)

DL_TFC28

(TF1, TF0, TF0, TF4, TF1)

DL_TFC29

(TF2, TF1, TF1, TF4, TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC16

1 to 6

5ms, Table 0

4

UL_TFC0, UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

2

DL_TFC2,

DL_TFC17

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC2,

UL_TFC3

RB5: 81

RB6: 103

RB7: 60

RB8: 312

3

DL_TFC3,

DL_TFC18

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

4

DL_TFC4,

DL_TFC19

1 to 6

5ms, Table 0

4

UL_TFC0, UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

5

DL_TFC5,

DL_TFC20

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3, UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

6

DL_TFC6,

DL_TFC21

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1

RB5: 39

RB6: 103

RB7: 60

RB8: 632

7

DL_TFC7,

DL_TFC22

1 to 6

5ms, Table 0

4

UL_TFC0, UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 632

8

DL_TFC8,

DL_TFC23

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3, UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 632

9

DL_TFC9,

DL_TFC24

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 952

10

DL_TFC10,

DL_TFC25

1 to 6

5ms, Table 0

4

UL_TFC0, UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 952

RB9: 952

11

DL_TFC11,

DL_TFC26

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 952

12

DL_TFC12,

DL_TFC27

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 1272

13

DL_TFC13,

DL_TFC28

1 to 6

5ms, Table 0

4

UL_TFC0, UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 1272

14

DL_TFC14,

DL_TFC29

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 1272

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.12.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.13 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 64 kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 64 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.13.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.13.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.15.

18.1.6.13.3 Method of test

UL parameters for E-DCH:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Uplink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x148

TF1, bits

1×39

1×103

1×60

1×148

TF2, bits

1×81

N/A

N/A

N/A

Uplink TFCS:

TFCI

(RB5, RB6, RB7, DCCH)

UL_TFC0

(TF0, TF0, TF0, TF0)

UL_TFC1

(TF1, TF0, TF0, TF0)

UL_TFC2

(TF2, TF1, TF1, TF0)

UL_TFC3

(TF0, TF0, TF0, TF1)

UL_TFC4

(TF1, TF0, TF0, TF1)

UL_TFC5

(TF2, TF1, TF1, TF1)

Downlink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

RB8 + RB9

(64 kbps,

20 ms TTI)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x340

0x148

TF1, bits

1×39

1×103

1×60

1×340

1×148

TF2, bits

1×81

N/A

N/A

2×340

N/A

TF3, bits

N/A

N/A

N/A

3×340

N/A

TF4, bits

N/A

N/A

N/A

4×340

N/A

Downlink TFCS:

TFCI

(RB5, RB6, RB7, RB8 + RB9, DCCH)

DL_TFC0

(TF0, TF0, TF0, TF0, TF0)

DL_TFC1

(TF1, TF0, TF0, TF0, TF0)

DL_TFC2

(TF2, TF1, TF1, TF0, TF0)

DL_TFC3

(TF0, TF0, TF0, TF1, TF0)

DL_TFC4

(TF1, TF0, TF0, TF1, TF0)

DL_TFC5

(TF2, TF1, TF1, TF1, TF0)

DL_TFC6

(TF0, TF0, TF0, TF2, TF0)

DL_TFC7

(TF1, TF0, TF0, TF2, TF0)

DL_TFC8

(TF2, TF1, TF1, TF2, TF0)

DL_TFC9

(TF0, TF0, TF0, TF3, TF0)

DL_TFC10

(TF1, TF0, TF0, TF3, TF0)

DL_TFC11

(TF2, TF1, TF1, TF3, TF0)

DL_TFC12

(TF0, TF0, TF0, TF4, TF0)

DL_TFC13

(TF1, TF0, TF0, TF4, TF0)

DL_TFC14

(TF2, TF1, TF1, TF4, TF0)

DL_TFC15

(TF0, TF0, TF0, TF0, TF1)

DL_TFC16

(TF1, TF0, TF0, TF0, TF1)

DL_TFC17

(TF2, TF1, TF1, TF0, TF1)

DL_TFC18

(TF0, TF0, TF0, TF1, TF1)

DL_TFC19

(TF1, TF0, TF0, TF1, TF1)

DL_TFC20

(TF2, TF1, TF1, TF1, TF1)

DL_TFC21

(TF0, TF0, TF0, TF2, TF1)

DL_TFC22

(TF1, TF0, TF0, TF2, TF1)

DL_TFC23

(TF2, TF1, TF1, TF2, TF1)

DL_TFC24

(TF0, TF0, TF0, TF3, TF1)

DL_TFC25

(TF1, TF0, TF0, TF3, TF1)

DL_TFC26

(TF2, TF1, TF1, TF3, TF1)

DL_TFC27

(TF0, TF0, TF0, TF4, TF1)

DL_TFC28

(TF1, TF0, TF0, TF4, TF1)

DL_TFC29

(TF2, TF1, TF1, TF4, TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC16

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

RB5: 39

RB6: No data

RB7: No data

RB8: No data

RB9: No data

2

DL_TFC2,

DL_TFC17

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

RB5: 81

RB6: 103

RB7: 60

RB8: No data

RB9: No data

3

DL_TFC3,

DL_TFC18

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

RB5: No data

RB6: No data

RB7: No data

RB8: 312

RB9: No data

4

DL_TFC4,

DL_TFC19

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: No data

5

DL_TFC5,

DL_TFC20

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: No data

6

DL_TFC6,

DL_TFC21

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 632

RB9: 632

RB5: No data

RB6: No data

RB7: No data

RB8: 632

RB9: No data

7

DL_TFC7,

DL_TFC22

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 632

RB9: 632

RB5: 39

RB6: No data

RB7: No data

RB8: 632

RB9: No data

8

DL_TFC8,

DL_TFC23

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 632

RB9: 632

RB5: 81

RB6: 103

RB7: 60

RB8: 632

RB9: No data

9

DL_TFC9,

DL_TFC24

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 952

RB9: 952

RB5: No data

RB6: No data

RB7: No data

RB8: 952

RB9: No data

10

DL_TFC10,

DL_TFC25

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 952

RB9: 952

RB5: 39

RB6: No data

RB7: No data

RB8: 952

RB9: No data

11

DL_TFC11,

DL_TFC26

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 952

RB9: 952

RB5: 81

RB6: 103

RB7: 60

RB8: 952

RB9: No data

12

DL_TFC12,

DL_TFC27

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 1272

RB9: 1272

RB5: No data

RB6: No data

RB7: No data

RB8: 1272

RB9: No data

13

DL_TFC13,

DL_TFC28

1 to 6

5ms, Table 0

4

RB5: 39

RB6: 103

RB7: 60

RB8: 1272

RB9: 1272

RB5: 39

RB6: No data

RB7: No data

RB8: 1272

RB9: No data

14

DL_TFC14,

DL_TFC29

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 1272

RB9: 1272

RB5: 81

RB6: 103

RB7: 60

RB8: 1272

RB9: No data

15

DL_TFC14,

DL_TFC29

1 to 6

5ms, Table 0

4

RB5: 81

RB6: 103

RB7: 60

RB8: 1272

RB9: 1272

RB5: 81

RB6: 103

RB7: 60

RB8: No data

RB9: 1272

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.13.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink

18.1.6.14 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / UL: [max bit rate depending on UE category and TTI] DL: 64 kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.14.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.14.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.16.

18.1.6.14.3 Method of test

UL parameters for E-DCH:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Uplink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x148

TF1, bits

1×39

1×103

1×60

1×148

TF2, bits

1×81

N/A

N/A

N/A

Uplink TFCS:

TFCI

(RB5, RB6, RB7, DCCH)

UL_TFC0

(TF0, TF0, TF0, TF0)

UL_TFC1

(TF1, TF0, TF0, TF0)

UL_TFC2

(TF2, TF1, TF1, TF0)

UL_TFC3

(TF0, TF0, TF0, TF1)

UL_TFC4

(TF1, TF0, TF0, TF1)

UL_TFC5

(TF2, TF1, TF1, TF1)

Downlink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

RB8

(64 kbps s,

20ms TTI)

RB9

(8kbps,

40ms TTI)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x336

0x336

0x148

TF1, bits

1×39

1×103

1×60

1×336

1×336

1×148

TF2, bits

1×81

N/A

N/A

2×336

N/A

N/A

TF3, bits

N/A

N/A

N/A

3×336

N/A

N/A

TF4, bits

N/A

N/A

N/A

4×336

N/A

N/A

Downlink TFCS:

TFCI

(RB5, RB6, RB7, RB8, RB9, DCCH)

DL_TFC0

(TF0, TF0, TF0, TF0, TF0, TF0)

DL_TFC1

(TF1, TF0, TF0, TF0, TF0, TF0)

DL_TFC2

(TF2, TF1, TF1, TF0, TF0, TF0)

DL_TFC3

(TF0, TF0, TF0, TF1, TF0, TF0)

DL_TFC4

(TF1, TF0, TF0, TF1, TF0, TF0)

DL_TFC5

(TF2, TF1, TF1, TF1, TF0, TF0)

DL_TFC6

(TF0, TF0, TF0, TF2, TF0, TF0)

DL_TFC7

(TF1, TF0, TF0, TF2, TF0, TF0)

DL_TFC8

(TF2, TF1, TF1, TF2, TF0, TF0)

DL_TFC9

(TF0, TF0, TF0, TF3, TF0, TF0)

DL_TFC10

(TF1, TF0, TF0, TF3, TF0, TF0)

DL_TFC11

(TF2, TF1, TF1, TF3, TF0, TF0)

DL_TFC12

(TF0, TF0, TF0, TF4, TF0, TF0)

DL_TFC13

(TF1, TF0, TF0, TF4, TF0, TF0)

DL_TFC14

(TF2, TF1, TF1, TF4, TF0, TF0)

DL_TFC15

(TF0, TF0, TF0, TF0, TF1, TF0)

DL_TFC16

(TF1, TF0, TF0, TF0, TF1, TF0)

DL_TFC17

(TF2, TF1, TF1, TF0, TF1, TF0)

DL_TFC18

(TF0, TF0, TF0, TF1, TF1, TF0)

DL_TFC19

(TF1, TF0, TF0, TF1, TF1, TF0)

DL_TFC20

(TF2, TF1, TF1, TF1, TF1, TF0)

DL_TFC21

(TF0, TF0, TF0, TF2, TF1, TF0)

DL_TFC22

(TF1, TF0, TF0, TF2, TF1, TF0)

DL_TFC23

(TF2, TF1, TF1, TF2, TF1, TF0)

DL_TFC24

(TF0, TF0, TF0, TF3, TF1, TF0)

DL_TFC25

(TF1, TF0, TF0, TF3, TF1, TF0)

DL_TFC26

(TF2, TF1, TF1, TF3, TF1, TF0)

DL_TFC27

(TF0, TF0, TF0, TF4, TF1, TF0)

DL_TFC28

(TF1, TF0, TF0, TF4, TF1, TF0)

DL_TFC29

(TF2, TF1, TF1, TF4, TF1, TF0)

DL_TFC30

(TF0, TF0, TF0, TF0, TF0, TF1)

DL_TFC31

(TF1, TF0, TF0, TF0, TF0, TF1)

DL_TFC32

(TF2, TF1, TF1, TF0, TF0, TF1)

DL_TFC33

(TF0, TF0, TF0, TF1, TF0, TF1)

DL_TFC34

(TF1, TF0, TF0, TF1, TF0, TF1)

DL_TFC35

(TF2, TF1, TF1, TF1, TF0, TF1)

DL_TFC36

(TF0, TF0, TF0, TF2, TF0, TF1)

DL_TFC37

(TF1, TF0, TF0, TF2, TF0, TF1)

DL_TFC38

(TF2, TF1, TF1, TF2, TF0, TF1)

DL_TFC39

(TF0, TF0, TF0, TF3, TF0, TF1)

DL_TFC40

(TF1, TF0, TF0, TF3, TF0, TF1)

DL_TFC41

(TF2, TF1, TF1, TF3, TF0, TF1)

DL_TFC42

(TF0, TF0, TF0, TF4, TF0, TF1)

DL_TFC43

(TF1, TF0, TF0, TF4, TF0, TF1)

DL_TFC44

(TF2, TF1, TF1, TF4, TF0, TF1)

DL_TFC45

(TF0, TF0, TF0, TF0, TF1, TF1)

DL_TFC46

(TF1, TF0, TF0, TF0, TF1, TF1)

DL_TFC47

(TF2, TF1, TF1, TF0, TF1, TF1)

DL_TFC48

(TF0, TF0, TF0, TF1, TF1, TF1)

DL_TFC49

(TF1, TF0, TF0, TF1, TF1, TF1)

DL_TFC50

(TF2, TF1, TF1, TF1, TF1, TF1)

DL_TFC51

(TF0, TF0, TF0, TF2, TF1, TF1)

DL_TFC52

(TF1, TF0, TF0, TF2, TF1, TF1)

DL_TFC53

(TF2, TF1, TF1, TF2, TF1, TF1)

DL_TFC54

(TF0, TF0, TF0, TF3, TF1, TF1)

DL_TFC55

(TF1, TF0, TF0, TF3, TF1, TF1)

DL_TFC56

(TF2, TF1, TF1, TF3, TF1, TF1)

DL_TFC57

(TF0, TF0, TF0, TF4, TF1, TF1)

DL_TFC58

(TF1, TF0, TF0, TF4, TF1, TF1)

DL_TFC59

(TF2, TF1, TF1, TF4, TF1, TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC31

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB8: 312

2

DL_TFC2,

DL_TFC32

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC2,

UL_TFC3

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB8: 312

3

DL_TFC3, DL_TFC33

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

4

DL_TFC4,

DL_TFC34

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

5

DL_TFC5,

DL_TFC35

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

6

DL_TFC6,

DL_TFC36

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

7

DL_TFC7,

DL_TFC37

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

8

DL_TFC8,

DL_TFC38

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

9

DL_TFC9,

DL_TFC39

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

10

DL_TFC10,

DL_TFC40

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

11

DL_TFC11,

DL_TFC41

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

12

DL_TFC12,

DL_TFC42

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

13

DL_TFC13,

DL_TFC43

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

14

DL_TFC14,

DL_TFC44

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 632

RB9: 312

15

DL_TFC15,

DL_TFC45

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

16

DL_TFC16,

DL_TFC46

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC1

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

17

DL_TFC17,

DL_TFC47

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

18

DL_TFC18,

DL_TFC48

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

19

DL_TFC19,

DL_TFC49

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC1

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

20

DL_TFC20,

DL_TFC50

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

21

DL_TFC21,

DL_TFC51

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

22

DL_TFC22,

DL_TFC52

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC1

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

23

DL_TFC23,

DL_TFC53

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

24

DL_TFC24,

DL_TFC54

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

25

DL_TFC25,

DL_TFC55

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC1

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

26

DL_TFC26,

DL_TFC56

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

27

DL_TFC27,

DL_TFC57

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

28

DL_TFC28,

DL_TFC58

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC1

RB5: 39

RB6: 103

RB7: 60

RB8: 312

RB9: 312

29

DL_TFC29,

DL_TFC59

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.14.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.15 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / UL: [max bit rate depending on UE category and TTI] DL: 32 kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.15.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.15.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.17.

18.1.6.15.3 Method of test

UL parameters for E-DCH:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Uplink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x148

TF1, bits

1×39

1×103

1×60

1×148

TF2, bits

1×81

N/A

N/A

N/A

Uplink TFCS:

TFCI

(RB5, RB6, RB7, DCCH)

UL_TFC0

(TF0, TF0, TF0, TF0)

UL_TFC1

(TF1, TF0, TF0, TF0)

UL_TFC2

(TF2, TF1, TF1, TF0)

UL_TFC3

(TF0, TF0, TF0, TF1)

UL_TFC4

(TF1, TF0, TF0, TF1)

UL_TFC5

(TF2, TF1, TF1, TF1)

Downlink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

RB8

(32 kbps s,

40ms TTI)

RB9

(8kbps,

40ms TTI)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x336

0x336

0x148

TF1, bits

1×39

1×103

1×60

1×336

1×336

1×148

TF2, bits

1×81

N/A

N/A

2×336

N/A

N/A

TF3,its

N/A

N/A

N/A

3×336

N/A

N/A

TF4,its

N/A

N/A

N/A

4×336

N/A

N/A

Downlink TFCS:

TFCI

(RB5, RB6, RB7, RB8,RB9 DCCH)

DL_TFC0

(TF0,TF0,TF0,TF0,TF0,TF0)

DL_TFC1

(TF1,TF0,TF0,TF0,TF0,TF0)

DL_TFC2

(TF2,TF1,TF1,TF0,TF0,TF0)

DL_TFC3

(TF0,TF0,TF0,TF1,TF0,TF0)

DL_TFC4

(TF1,TF0,TF0,TF1,TF0,TF0)

DL_TFC5

(TF2,TF1,TF1,TF1,TF0,TF0)

DL_TFC6

(TF0,TF0,TF0,TF2,TF0,TF0)

DL_TFC7

(TF1,TF0,TF0,TF2,TF0,TF0)

DL_TFC8

(TF2,TF1,TF1,TF2,TF0,TF0)

DL_TFC9

(TF0,TF0,TF0,TF0,TF1,TF0)

DL_TFC10

(TF1,TF0,TF0,TF0,TF1,TF0)

DL_TFC11

(TF2,TF1,TF1,TF0,TF1,TF0)

DL_TFC12

(TF0,TF0,TF0,TF1,TF1,TF0)

DL_TFC13

(TF1,TF0,TF0,TF1,TF1,TF0)

DL_TFC14

(TF2,TF1,TF1,TF1,TF1,TF0)

DL_TFC15

(TF0,TF0,TF0,TF2,TF1,TF0)

DL_TFC16

(TF1,TF0,TF0,TF2,TF1,TF0)

DL_TFC17

(TF2,TF1,TF1,TF2,TF1,TF0)

DL_TFC18

(TF0,TF0,TF0,TF0,TF0,TF1)

DL_TFC19

(TF1,TF0,TF0,TF0,TF0,TF1)

DL_TFC20

(TF2,TF1,TF1,TF0,TF0,TF1)

DL_TFC21

(TF0,TF0,TF0,TF1,TF0,TF1)

DL_TFC22

(TF1,TF0,TF0,TF1,TF0,TF1)

DL_TFC23

(TF2,TF1,TF1,TF1,TF0,TF1)

DL_TFC24

(TF0,TF0,TF0,TF2,TF0,TF1)

DL_TFC25

(TF1,TF0,TF0,TF2,TF0,TF1)

DL_TFC26

(TF2,TF1,TF1,TF2,TF0,TF1)

DL_TFC27

(TF0,TF0,TF0,TF0,TF1,TF1)

DL_TFC28

(TF1,TF0,TF0,TF0,TF1,TF1)

DL_TFC29

(TF2,TF1,TF1,TF0,TF1,TF1)

DL_TFC30

(TF0,TF0,TF0,TF1,TF1,TF1)

DL_TFC31

(TF1,TF0,TF0,TF1,TF1,TF1)

DL_TFC32

(TF2,TF1,TF1,TF1,TF1,TF1)

DL_TFC33

(TF0,TF0,TF0,TF2,TF1,TF1)

DL_TFC34

(TF1,TF0,TF0,TF2,TF1,TF1)

DL_TFC35

(TF2,TF1,TF1,TF2,TF1,TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC18

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: No data

RB9: No data

2

DL_TFC2,

DL_TFC19

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC2,

UL_TFC3

RB5: 81

RB6: 103

RB7: 60

RB8: No data

RB9: No data

3

DL_TFC3,

DL_TFC20

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: 312

RB9: No data

4

DL_TFC4,

DL_TFC21

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: No data

5

DL_TFC5,

DL_TFC22

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: No data

6

DL_TFC6,

DL_TFC23

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: 312

RB9: No data

7

DL_TFC7,

DL_TFC24

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: No data

8

DL_TFC8,

DL_TFC25

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: No data

9

DL_TFC9,

DL_TFC26

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: No data

RB9: 312

10

DL_TFC10,

DL_TFC27

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: No data

RB9: 312

11

DL_TFC11,

DL_TFC28

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: No data

RB9: 312

12

DL_TFC12,

DL_TFC29

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: 312

RB9: 312

13

DL_TFC13,

DL_TFC30

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: 312

14

DL_TFC14,

DL_TFC31

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

15

DL_TFC15,

DL_TFC32

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: 632

RB9: 312

16

DL_TFC16,

DL_TFC33

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC1

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: 312

17

DL_TFC17,

DL_TFC35

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.15.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink

18.1.6.16 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming / UL: [max bit rate depending on UE category and TTI] DL: 16 kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.16.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.16.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.18.

18.1.6.16.3 Method of test

UL parameters for E-DCH:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Uplink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x148

TF1, bits

1×39

1×103

1×60

1×148

TF2, bits

1×81

N/A

N/A

N/A

Uplink TFCS:

TFCI

(RB5, RB6, RB7, DCCH)

UL_TFC0

(TF0, TF0, TF0, TF0)

UL_TFC1

(TF1, TF0, TF0, TF0)

UL_TFC2

(TF2, TF1, TF1, TF0)

UL_TFC3

(TF0, TF0, TF0, TF1)

UL_TFC4

(TF1, TF0, TF0, TF1)

UL_TFC5

(TF2, TF1, TF1, TF1)

Downlink TFS:

TFI

RB5

(RAB subflow #1)

RB6

(RAB subflow #2)

RB7

(RAB subflow #3)

RB8

(16 kbps tti 40ms )

RB9

(8 kbps tti 40ms )

DCCH

TFS

TF0, bits

0x81

0x103

0x60

0x336

0x336

0x148

TF1, bits

1×39

1×103

1×60

1×336

1×336

1×148

TF2, bits

1×81

N/A

N/A

2×336

N/A

N/A

Downlink TFCS:

TFCI

(RB5, RB6, RB7, RB8,RB9 DCCH)

DL_TFC0

(TF0,TF0,TF0,TF0,TF0,TF0)

DL_TFC1

(TF1,TF0,TF0,TF0,TF0,TF0)

DL_TFC2

(TF2,TF1,TF1,TF0,TF0,TF0)

DL_TFC3

(TF0,TF0,TF0,TF1,TF0,TF0)

DL_TFC4

(TF1,TF0,TF0,TF1,TF0,TF0)

DL_TFC5

(TF2,TF1,TF1,TF1,TF0,TF0)

DL_TFC6

(TF0,TF0,TF0,TF2,TF0,TF0)

DL_TFC7

(TF1,TF0,TF0,TF2,TF0,TF0)

DL_TFC8

(TF2,TF1,TF1,TF2,TF0,TF0)

DL_TFC9

(TF0,TF0,TF0,TF0,TF1,TF0)

DL_TFC10

(TF1,TF0,TF0,TF0,TF1,TF0)

DL_TFC11

(TF2,TF1,TF1,TF0,TF1,TF0)

DL_TFC12

(TF0,TF0,TF0,TF1,TF1,TF0)

DL_TFC13

(TF1,TF0,TF0,TF1,TF1,TF0)

DL_TFC14

(TF2,TF1,TF1,TF1,TF1,TF0)

DL_TFC15

(TF0,TF0,TF0,TF2,TF1,TF0)

DL_TFC16

(TF1,TF0,TF0,TF2,TF1,TF0)

DL_TFC17

(TF2,TF1,TF1,TF2,TF1,TF0)

DL_TFC18

(TF0,TF0,TF0,TF0,TF0,TF1)

DL_TFC19

(TF1,TF0,TF0,TF0,TF0,TF1)

DL_TFC20

(TF2,TF1,TF1,TF0,TF0,TF1)

DL_TFC21

(TF0,TF0,TF0,TF1,TF0,TF1)

DL_TFC22

(TF1,TF0,TF0,TF1,TF0,TF1)

DL_TFC23

(TF2,TF1,TF1,TF1,TF0,TF1)

DL_TFC24

(TF0,TF0,TF0,TF2,TF0,TF1)

DL_TFC25

(TF1,TF0,TF0,TF2,TF0,TF1)

DL_TFC26

(TF2,TF1,TF1,TF2,TF0,TF1)

DL_TFC27

(TF0,TF0,TF0,TF0,TF1,TF1)

DL_TFC28

(TF1,TF0,TF0,TF0,TF1,TF1)

DL_TFC29

(TF2,TF1,TF1,TF0,TF1,TF1)

DL_TFC30

(TF0,TF0,TF0,TF1,TF1,TF1)

DL_TFC31

(TF1,TF0,TF0,TF1,TF1,TF1)

DL_TFC32

(TF2,TF1,TF1,TF1,TF1,TF1)

DL_TFC33

(TF0,TF0,TF0,TF2,TF1,TF1)

DL_TFC34

(TF1,TF0,TF0,TF2,TF1,TF1)

DL_TFC35

(TF2,TF1,TF1,TF2,TF1,TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC18

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: No data

RB9: No data

2

DL_TFC2,

DL_TFC19

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC2,

UL_TFC3

RB5: 81

RB6: 103

RB7: 60

RB8: No data

RB9: No data

3

DL_TFC3,

DL_TFC20

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: 312

RB9: No data

4

DL_TFC4,

DL_TFC21

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: No data

5

DL_TFC5,

DL_TFC22

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: No data

6

DL_TFC6,

DL_TFC23

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: 312

RB9: No data

7

DL_TFC7,

DL_TFC24

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: No data

8

DL_TFC8,

DL_TFC25

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: No data

9

DL_TFC9,

DL_TFC26

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: No data

RB9: 312

10

DL_TFC10,

DL_TFC27

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: No data

RB9: 312

11

DL_TFC11,

DL_TFC28

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: No data

RB9: 312

12

DL_TFC12,

DL_TFC29

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: 312

RB9: 312

13

DL_TFC13,

DL_TFC30

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC1,

UL_TFC3

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: 312

14

DL_TFC14,

DL_TFC31

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

15

DL_TFC15,

DL_TFC32

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3

RB5: No data

RB6: No data

RB7: No data

RB8: 632

RB9: 312

16

DL_TFC16,

DL_TFC33

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC1

RB5: 39

RB6: No data

RB7: No data

RB8: 312

RB9: 312

17

DL_TFC17,

DL_TFC35

1 to 6

5ms, Table 0

4

UL_TFC0,

UL_TFC3,

UL_TFC5

RB5: 81

RB6: 103

RB7: 60

RB8: 312

RB9: 312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.16.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.17 Streaming / UL: [max bit rate depending on UE category and TTI] DL: 64 kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.17.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.17.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.19.

18.1.6.17.3 Method of test

UL parameters for E-DCH:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Downlink TFS:

TFI

RB5

(64 kbps TTI 40ms)

RB6

(8 kbps TTI 40ms) )

DCCH

TFS

TF0, bits

0x656

0x336

0x148

TF1, bits

1×656

1×336

1×148

TF2, bits

2×656

N/A

N/A

TF3, bits

4×656

N/A

N/A

Downlink TFCS:

TFCI

(RB5,RB6 DCCH)

DL_TFC0

(TF0,TF0,TF0)

DL_TFC1

(TF1,TF0,TF0)

DL_TFC2

(TF2,TF0,TF0)

DL_TFC3

(TF3,TF0,TF0)

DL_TFC4

(TF0,TF1,TF0)

DL_TFC5

(TF2,TF1,TF0)

DL_TFC6

(TF2,TF1,TF0)

DL_TFC7

(TF3,TF1,TF0),

DL_TFC8

(TF0,TF0,TF1)

DL_TFC9

(TF1,TF0,TF1)

DL_TFC10

(TF2,TF0,TF1

DL_TFC11

(TF3,TF0,TF1)

DL_TFC12

(TF0,TF1,TF1)

DL_TFC13

(TF1,TF1,TF1)

DL_TFC14

(TF2,TF1,TF1),

DL_TFC15

(TF3,TF1,TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC9

1 to 6

5ms, Table 0

4

RB5: 640

RB6: No data

RB5: 640

RB6: No data

2

DL_TFC2,

DL_TFC10

1 to 6

5ms, Table 0

4

RB5: 1296

RB6: No data

RB5: 1296

RB6: No data

3

DL_TFC3,

DL_TFC11

1 to 6

5ms, Table 0

4

RB5: 2608

RB6: No data

RB5: 2608

RB6: No data

4

DL_TFC4,

DL_TFC12

1 to 6

5ms, Table 0

4

RB5: No data

RB6: 312

RB5: No data

RB6: 312

5

DL_TFC13

1 to 6

5ms, Table 0

4

RB5: 640

RB6: 312

RB5: 640

RB6: 312

6

DL_TFC6

1 to 6

5ms, Table 0

4

RB5: 1296

RB6: 312

RB5: 1296

RB6: 312

7

DL_TFC7

1 to 6

5ms, Table 0

4

RB5: 2608

RB6: 312

RB5: 2608

RB6: 312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.17.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink

18.1.6.18 Streaming / UL: [max bit rate depending on UE category and TTI] DL: 32 kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.18.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.18.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.20.

18.1.6.18.3 Method of test

UL parameters for E-DCH:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Downlink TFS:

TFI

RB5

(32 kbps TTI 20ms)

RB6

(8 kbps TTI 40ms) )

DCCH

TFS

TF0, bits

0x336

0x336

0x148

TF1, bits

1×336

1×336

1×148

TF2, bits

2×336

N/A

N/A

Downlink TFCS:

TFCI

(RB5,RB6 DCCH)

DL_TFC0

(TF0, TF0,TF0)

DL_TFC1

(TF1, TF0,TF0)

DL_TFC2

(TF2, TF0,TF0)

DL_TFC3

(TF0, TF1,TF0)

DL_TFC4

(TF1, TF1,TF0)

DL_TFC5

(TF2, TF1,TF0)

DL_TFC6

(TF0, TF0,TF1)

DL_TFC7

(TF1, TF0,TF1)

DL_TFC8

(TF2, TF0,TF1)

DL_TFC9

(TF0, TF1,TF1)

DL_TFC10

(TF1, TF1,TF1)

DL_TFC11

(TF2, TF1,TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC7

1 to 6

5ms, Table 0

4

RB5: 312

RB6: No data

RB5: 312

RB6: No data

2

DL_TFC2,

DL_TFC8

1 to 6

5ms, Table 0

4

RB5: 312

RB6: No data

RB5: 632

RB6: No data

3

DL_TFC3,

DL_TFC9

1 to 6

5ms, Table 0

4

RB5: No data

RB6: 312

RB5: No data

RB6: 312

4

DL_TFC4

DL_TFC11

1 to 6

5ms, Table 0

4

RB5: 312

RB6: 312

RB5: 612

RB6: 312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.18.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink

18.1.6.19 Streaming / UL: [max bit rate depending on UE category and TTI] DL: 16 kbps / PS RAB + Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH

18.1.6.19.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.19.2 Test purpose

To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.21.

18.1.6.19.3 Method of test

UL parameters for E-DCH:

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

Downlink TFS:

TFI

RB5

(16 kbps TTI 20ms)

RB6

(8 kbps TTI 40ms) )

DCCH

TFS

TF0, bits

0x336

0x336

0x148

TF1, bits

1×336

1×336

1×148

Downlink TFCS:

TFCI

(RB5,RB6 DCCH)

DL_TFC0

(TF0, TF0,TF0)

DL_TFC1

(TF1, TF0,TF0)

DL_TFC2

(TF0, TF1,TF0)

DL_TFC3

(TF1, TF1,TF0)

DL_TFC4

(TF0, TF0,TF1)

DL_TFC5

(TF1, TF0,TF1)

DL_TFC6

(TF0, TF1,TF1)

DL_TFC7

(TF1, TF1,TF1)

Sub-tests:

Sub-test

Downlink TFCS

Under test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL RLC SDU size

(bits)

(note 2)

Test data size

(bits)

(note 3)

1

DL_TFC1,

DL_TFC5

1 to 6

5ms, Table 0

4

RB5: 312

RB6: No data

RB5: 312

RB6: No data

2

DL_TFC2,

DL_TFC6

1 to 6

5ms, Table 0

4

RB5: No data

RB6:312

RB5: No data

RB6: 312

3

DL_TFC3,

DL_TFC7

1 to 6

5ms, Table 0

4

RB5: 312

RB6: 312

RB5: 312

RB6: 312

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to N*UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks for the UL transport format under test. This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested.

18.1.6.19.4 Test requirements

See 14.1.4.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink

18.1.6.20 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH for enhanced uplink/downlink in CELL_FACH

18.1.6.20.1 Conformance requirement

Conformance requirement

See 18.1.6.1

18.1.6.20.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.4:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to common E-DCH in CELL_FACH.

18.1.6.20.3 Method of test

NOTE 1: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-7 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.

NOTE 2: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.

The following parameters are specific for this test case:

Parameter

Value

Radio bearer

TS 34.108, clause 6.11.5.4.7.4 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-i/is) and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4.

MAC-ehs receiver window size

16

HS-DSCH MAC-d PDU size

336

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

HS-DSCH Category

HS-PDSCH Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

370

1

QPSK

12

2

6

512

336

370

1

QPSK

12

3

8

512

336

370

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

358

1

QPSK

8

8

6

1536

336

358

1

QPSK

8

9

8

2047

336

358

1

QPSK

8

10

4

2047

336

370

1

QPSK

8

11

6

1024

336

370

1

QPSK

8

12

8

1024

336

370

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size.

The generic test procedure in 18.1.1.9 is run for each sub-test.

Sub-tests:

Sub-test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL MAC-d PDU size under test

DL MAC-d PDU size under test

UL RLC SDU size

(note 2)

Test data

size

(note 3)

1

1 to 6

5ms

4

Flexible

Flexible

320

320

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to UL RLC payload size. This will enable the UE to return the data within one UL TTI (“Use special value of HE field” is configured).

NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size.

18.1.6.20.4 Test requirements

See 14.1.5.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.20a Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on common E-DCH and HS-DSCH for enhanced CELL_FACH with DRX configured

18.1.6.20a.1 Conformance requirement

Conformance requirement

See 18.1.6.1

18.1.6.20a.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.4:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer corresponding to Enhanced DRX reception pattern by UE when transport channel is mapped to common E-DCH in CELL_FACH.

18.1.6.20a.3 Method of test

NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.

NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.

The following parameters are specific for this test case:

Parameter

Value

Radio bearer

TS 34.108, clause 6.11.5.4.7.4 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-i/is) and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4.

MAC-ehs receiver window size

16

HS-DSCH MAC-d PDU size

336

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

HS-DSCH Category

HS-PDSCH

Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum

TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

370

1

QPSK

12

2

6

512

336

370

1

QPSK

12

3

8

512

336

370

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

358

1

QPSK

8

8

6

1536

336

358

1

QPSK

8

9

8

2047

336

358

1

QPSK

8

10

4

2047

336

370

1

QPSK

8

11

6

1024

336

370

1

QPSK

8

12

8

1024

336

370

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size.

The generic test procedure in 18.1.1.9 is run for each sub-test.

Sub-tests:

Sub-test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL MAC-d PDU size under test

DL MAC-d PDU size under test

UL RLC SDU size

(note 2)

Test data

size

(note 3)

1

1 to 6

5ms

4

Flexible

Flexible

320

320

NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to UL RLC payload size. This will enable the UE to return the data within one UL TTI (“Use special value of HE field” is configured).

NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size.

Specific Message Contents

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

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

Information Element

Value/remark

HS-DSCH DRX in CELL_FACH Information 1.28 Mcps TDD

-T321

200ms

– DRX cycleFACH

4

– Rx burstFACH

1

18.1.6.20a.4 Test requirements

See 14.1.5.1 for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.

18.1.6.21 Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps with Flexible RLC and MAC-ehs / PS RAB + Streaming or Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] with Fixed RLC and MAC-ehs / PS RAB + UL:[max bit rate depending on UE category and TTI] DL: :[max bit rate depending on UE category] SRBs for DCCH on E-DCH and SRBs with Fixed RLC and MAC-ehs on HS-DSCH / UL: QPSK and DL: QPSK

18.1.6.21.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.21.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.22 for the case for the QPSK and non-MIMO case using the downlink enhanced Layer 2 configuration with MAC-ehs and Fixed and Flexible RLC configured:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.

18.1.6.21.3 Method of test

NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.

NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.

The Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5 and the Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6

The following parameters are specific for this test case and RB5 and RB6:

Parameter

Value

Radio bearer

TS 34.108, clause 6.11.5.4.7.22 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) for RB5; using downlink MAC-d flow parameters according to Alt 2 (Fixed RLC and MAC-ehs) for RB6; and using Alt 2 (Fixed RLC and MAC-ehs) for the SRB#1 to SRB#4.

MAC-ehs receiver window size

16

Alternative E-bit interpretation

TRUE

RB5: HS-DSCH MAC-d PDU size

See sub-test table

RB6: HS-DSCH MAC-d PDU size

336

RB5: DL UM RLC LI size

7

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

HS-DSCH Category

HS-PDSCH Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

368

1

QPSK

12

2

6

512

336

368

1

QPSK

12

3

8

512

336

368

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

368

1

QPSK

9

8

6

1536

336

368

1

QPSK

9

9

8

1536

336

368

1

QPSK

9

10

4

2047

336

376

1

QPSK

9

11

6

2047

336

376

1

QPSK

9

12

8

2047

336

376

1

QPSK

9

13

4

2560

336

392

1

QPSK

9

14

6

2560

336

392

1

QPSK

9

15

8

2560

336

392

1

QPSK

9

16

4

2047

336

384

1

QPSK

9

17

6

2047

336

384

1

QPSK

9

18

8

2047

336

384

1

QPSK

9

19

4

3072

336

360

1

QPSK

8

20

6

3072

336

360

1

QPSK

8

21

8

3072

336

360

1

QPSK

8

22

4

3584

336

376

1

QPSK

8

23

6

3584

336

376

1

QPSK

8

24

8

3584

336

376

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size is bigger than the “Minimum TBS” that equals maximum MAC-d PDU size under test + the MAC-ehs header size (24 bits).

The generic test procedure in 18.1.1.6 is run for each sub-test.

Sub-tests:

Sub-test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL MAC-d PDU size under test

DL MAC-d PDU size under test

UL RLC SDU size

(note 2)

Test data

size

(note 3)

1

1 to 6

5ms

4

RB5:96

RB6:336

RB5:Flexible

RB6:336

RB5:80

RB6:312

RB5:96

RB6:312

2

1 to 6

5ms

4

RB5:112

RB6:336

RB5:Flexible

RB6:336

RB5:96

RB6:312

RB5:96

RB6:312

3

1 to 6

5ms

4

RB5:144

RB6:336

RB5:Flexible

RB6:336

RB5:128

RB6:312

RB5:128

RB6:312

4

1 to 6

5ms

4

RB5:160

RB6:336

RB5:Flexible

RB6:336

RB5:144

RB6:312

RB5:144

RB6:312

5

1 to 6

5ms

4

RB5:176

RB6:336

RB5:Flexible

RB6:336

RB5:160

RB6:312

RB5:160

RB6:312

6

1 to 6

5ms

4

RB5:192

RB6:336

RB5:Flexible

RB6:336

RB5:176

RB6:312

RB5:176

RB6:312

7

1 to 6

5ms

4

RB5:208

RB6:336

RB5:Flexible

RB6:336

RB5:192

RB6:312

RB5:208

RB6:312

8

1 to 6

5ms

4

RB5:224

RB6:336

RB5:Flexible

RB6:336

RB5:208

RB6:312

RB5:208

RB6:312

9

1 to 6

5ms

4

RB5:288

RB6:336

RB5:Flexible

RB6:336

RB5:272

RB6:312

RB5:280

RB6:312

10

1 to 6

5ms

4

RB5:296

RB6:336

RB5:Flexible

RB6:336

RB5:280

RB6:312

RB5:280

RB6:312

11

1 to 6

5ms

4

RB5:312

RB6:336

RB5:Flexible

RB6:336

RB5:296

RB6:312

RB5:328

RB6:312

12

1 to 6

5ms

4

RB5:344

RB6:336

RB5:Flexible

RB6:336

RB5:328

RB6:312

RB5:328

RB6:312

NOTE 1: E-DCH TTI and E-TFCI table according to TS 25.321 Annex BC.1.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to UL RLC payload size minus 8 bits (size of 7 bit length indicator and expansion bit). This will enable the UE to return the data within one UL TTI.

NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size minus 8 bits (size of 7 bit length indicator and expansion bit).

18.1.6.21.4 Test requirements

See 14.1.4.1a for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU on RB5 and RB6 with same content as sent in downlink. For the case the returned UL RLC SDU size under test is smaller than the sent DL RLC SDU size then the payload of the received UL RLC SDU shall have the same content as the first N bits of the DL RLC SDU payload, where N equals the payload size of the UL RLC SDU.

18.1.6.22 Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps with Flexible RLC, MAC-ehs and MAC-i/is / PS RAB + Streaming or Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] with Fixed RLC, MAC-ehs and MAC-i/is / PS RAB + UL:[max bit rate depending on UE category and TTI] DL: :[max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH with MAC-ehs and MAC-i/is / UL: QPSK and DL: QPSK

18.1.6.22.1 Conformance requirement

See 18.1.6.1.1.

18.1.6.22.2 Test purpose

For the reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.7.22 for the case QPSK and non-MIMO case when MAC-ehs and MAC-i/is and the mix of Fixed and Flexible RLC is configured:

1. To verify that the UE is able to establish the radio bearer combination.

2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.

18.1.6.22.3 Method of test

NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.

NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.

The Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5 and the Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6

The following parameters are specific for this test case and RB5 and RB6:

Parameter

Value

Radio bearer

TS 34.108, clause 6.11.5.4.7.22 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 2 (Flexible RLC and MAC-i/is) for RB5; using downlink MAC-d flow parameters according to Alt 2 (Fixed RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 2 (Fixed RLC and MAC-i/is) for RB6; and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4.

MAC-ehs receiver window size

16

RB5: Alternative E-bit interpretation

TRUE

RB5: HS-DSCH MAC-d PDU size

See sub-test table

RB6: HS-DSCH MAC-d PDU size

336

E-DCH

Category

RLC Transmission window size

1

512

2

512

3

512

4

512

5

1536

6

1536

HS-DSCH Category

HS-PDSCH Number of HARQ processes

RLC Receiving window size

HS-PDSCH TFRC

(note 1)

Max MAC-d PDU size

Minimum TBS

Number of MAC-d PDUs

Modulation scheme

TFRI

1

4

512

336

368

1

QPSK

12

2

6

512

336

368

1

QPSK

12

3

8

512

336

368

1

QPSK

12

4

4

512

336

360

1

QPSK

9

5

6

512

336

360

1

QPSK

9

6

8

512

336

360

1

QPSK

9

7

4

1536

336

368

1

QPSK

9

8

6

1536

336

368

1

QPSK

9

9

8

1536

336

368

1

QPSK

9

10

4

2047

336

376

1

QPSK

9

11

6

2047

336

376

1

QPSK

9

12

8

2047

336

376

1

QPSK

9

13

4

2560

336

392

1

QPSK

9

14

6

2560

336

392

1

QPSK

9

15

8

2560

336

392

1

QPSK

9

16

4

2047

336

384

1

QPSK

9

17

6

2047

336

384

1

QPSK

9

18

8

2047

336

384

1

QPSK

9

19

4

3072

336

360

1

QPSK

8

20

6

3072

336

360

1

QPSK

8

21

8

3072

336

360

1

QPSK

8

22

4

3584

336

376

1

QPSK

8

23

6

3584

336

376

1

QPSK

8

24

8

3584

336

376

1

QPSK

8

NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size is bigger than the “Minimum TBS” that equals maximum MAC-d PDU size under test + the MAC-ehs header size (24 bits).

The generic test procedure in 18.1.1.6 is run for each sub-test.

Sub-tests:

Sub-test

Applicable E-DCH

Category

E-DPDCH TTI and E-TFCI Table

(note 1)

E-DPDCH Number of HARQ processes

UL MAC-d PDU size under test

DL MAC-d PDU size under test

UL RLC SDU size

(note 2)

Test data

size

(note 3)

1

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:88

RB6:320

RB5:104

RB6:320

2

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:104

RB6:320

RB5:104

RB6:320

3

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:136

RB6:320

RB5:136

RB6:320

4

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:152

RB6:320

RB5:152

RB6:320

5

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:168

RB6:320

RB5:168

RB6:320

6

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:184

RB6:320

RB5:184

RB6:320

7

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:200

RB6:320

RB5:216

RB6:320

8

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:216

RB6:320

RB5:216

RB6:320

9

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:280

RB6:320

RB5:288

RB6:320

10

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:288

RB6:320

RB5:288

RB6:320

11

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:304

RB6:320

RB5:336

RB6:320

12

1 to 6

5ms

4

RB5:Flexible

RB6:336

RB5:Flexible

RB6:336

RB5:336

RB6:320

RB5:336

RB6:320

NOTE 1: E-DCH TTI and E-TFCI table according to TS 25.321 Annex BC.1.

NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
The UL RLC SDU size is set to UL RLC payload size to be tested.. This will enable the UE to return the data within one UL TTI (“Alternative E-bit interpretation” is configured for RB5 (UM) and “Use special value of HE field” is configured for RB6 (AM)). The selected UL RLC SDU sizes for the flexible case (RB5) are the same as specified for the UL fixed case (Alt 1) of the reference radio bearer configuration in TS 34.108, clause 6.11.5.4.7.22 (88, 104, 136, 152, 168, 184, 200, 216, 280, 288, 304 and 336).

NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size. The selected DL test data sizes for RB5 are the same as specified for the DL fixed case (Alt 2) of the reference radio bearer configuration in TS 34.108, clause 6.11.5.4.7.22 (104, 136, 152, 168, 184, 216, 288 and 336).

18.1.6.22.4 Test requirements

See 14.1.4.1b for definition of step 12 and step 18.

1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.

2. At step 18 the UE shall return a RLC SDU on RB5 and RB6 with same content as sent in downlink. For the case the returned UL RLC SDU size under test is smaller than the sent DL RLC SDU size then the payload of the received UL RLC SDU shall have the same content as the first N bits of the DL RLC SDU payload, where N equals the payload size of the UL RLC SDU.