14.6.1h Interactive or background / UL:64 DL: [max bit rate depending on UE category] with Flexible RLC and MAC-ehs PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH / DL: 16QAM, Dual-Cell and MIMO

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

14.6.1h.1 Conformance requirement

See 14.6.1.1.

14.6.1h.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.10.2.4.5.1 for the 16QAM, MIMO and Dual-Cell case using the downlink enhanced Layer 2 configuration with Flexible RLC and MAC-ehs .

14.6.1h.3 Method of test

NOTE: The reference to UE Categories refers to the UE capability as signalled in the Rel-9 IE “HS-DSCH physical layer category extension 3”. 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.10.2.4.5.1 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs).

MAC-ehs receiver window size

64

precodingWeight2

00

25.212, Table 14A

RLC Transmission window size

See sub-test table

RLC Receiving window size

See sub-test table

Execution counter

Dual-Cell#1

Dual-Cell#2

Number of HARQ processes

Downlink Modulation Scheme (M1)

For Cell#1 data flow#1

Downlink Modulation Scheme (M2)

For Cell#1 data flow#2

Downlink Modulation Scheme (M3)

For Cell#2 data flow#1

Downlink Modulation Scheme (M4)

For Cell#2 data flow#2

1

16QAM

16QAM

16QAM

16QAM

12

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)

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

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

25 to 28

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 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 th data within one UL TTI.

NOTE 4: The test data size for RB5 is dependent on the actual TFRC test point, see the generic test procedure in 14.1.3.5a.

14.6.1h.4 Test requirements

See 14.1.3.5a 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 TF1 (1×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 14.1.3.5a 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.