14.6.6g Streaming / unknown / UL:128 DL: [guaranteed 128, max bit rate depending on UE category] with Fixed RLC and MAC-ehs / PS RAB + Interactive or background / UL:128 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: combination of 16QAM, Dual-Carrier and MIMO

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

14.6.6g.1 Conformance requirement

See 14.6.1.1.

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

14.6.6g.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 Streaming / unknown / UL:128 DL: [guaranteed 128, max bit rate depending on UE category] with Fixed RLC and MAC-ehs / PS RAB is referred to as RB5. The Interactive or background / UL:128 DL: [max bit rate depending on UE category] with Flexible RLC and MAC-ehs / PS RAB is referred to as RB6.

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

Parameter	Value	Comments
Radio bearer	TS 34.108, clause 6.10.2.4.5.6 using downlink MAC-d flow parameters according to Alt 2 (Fixed RLC and MAC-ehs) for RB5 and using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) for RB6.
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

16QAM

Uplink TFS:

	TFI	RB5 (Streaming 128 kbps, 20ms)	RB6 (I/B 128 kbps, 20ms)	DCCH
TFS	TF0, bits	0x656	0x336	0x148
	TF1, bits	1×656	1×336	1×148
	TF2, bits	2×656	2×336	N/A
	TF3, bits	4×656	4×336	N/A
	TF4, bits	N/A	8×336	N/A

Uplink TFCS:

TFCI	(RB5 + RB6, DCCH)
UL_TFC0	(TF0, TF0, TF0)
UL_TFC1	(TF1, TF0, TF0)
UL_TFC2	(TF2, TF0, TF0)
UL_TFC3	(TF3, TF0, TF0)
UL_TFC4	(TF0, TF1, TF0)
UL_TFC5	(TF1, TF1, TF0)
UL_TFC6	(TF2, TF1, TF0)
UL_TFC7	(TF3, TF1, TF0)
UL_TFC8	(TF0, TF2, TF0)
UL_TFC9	(TF1, TF2, TF0)
UL_TFC10	(TF2, TF2, TF0)
UL_TFC11	(TF3, TF2, TF0)
UL_TFC12	(TF0, TF3, TF0)
UL_TFC13	(TF1, TF3, TF0)
UL_TFC14	(TF2, TF3, TF0)
UL_TFC15	(TF3, TF3, TF0)
UL_TFC16	(TF0, TF4, TF0)
UL_TFC17	(TF1, TF4, TF0)
UL_TFC18	(TF2, TF4, TF0)
UL_TFC19	(TF3, TF4, TF0)
UL_TFC20	(TF0, TF0, TF1)
UL_TFC21	(TF1, TF0, TF1)
UL_TFC22	(TF2, TF0, TF1)
UL_TFC23	(TF3, TF0, TF1)
UL_TFC24	(TF0, TF1, TF1)
UL_TFC25	(TF1, TF1, TF1)
UL_TFC26	(TF2, TF1, TF1)
UL_TFC27	(TF3, TF1, TF1)
UL_TFC28	(TF0, TF2, TF1)
UL_TFC29	(TF1, TF2, TF1)
UL_TFC30	(TF2, TF2, TF1)
UL_TFC31	(TF3, TF2, TF1)
UL_TFC32	(TF0, TF3, TF1)
UL_TFC33	(TF1, TF3, TF1)
UL_TFC34	(TF2, TF3, TF1)
UL_TFC35	(TF3, TF3, TF1)
UL_TFC36	(TF0, TF4, TF1)
UL_TFC37	(TF1, TF4, TF1)
UL_TFC38	(TF2, TF4, TF1)
UL_TFC39	(TF3, TF4, TF1)

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

Sub-tests:

The principle used to select sub-tests has been to cover all uplink and downlink TFS for the Streaming + Interactive Background PS radio bearer. The Streaming UL:128 kbps + Interactive Background UL:128 kbps radio bearer (RB5+RB6) have 40 transport format combinations. As the transport formats where RB5, RB6 or DCCH has no data (TF0 for RB5, RB6 or DCCH) is considered as implicitly tested when the transport format combinations with data is tested then no specific sub-tests for those transport format combinations have been specified.

Sub-tes	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	RB5: 656 RB6: Flexible	UL_TFC19	UL_TFC0, UL_TFC3, UL_TFC16, UL_TFC20	UL_TFC0, UL_TFC1, UL_TFC3, UL_TFC4, UL_TFC16, UL_TFC19, UL_TFC20, UL_TFC21, UL_TFC24, UL_TFC39	RB5: 2552 RB6: 2552	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, UL_TFC4 and UL_TFC20 are part of minimum set of TFCIs. Also the transport format combinations UL_TFC21 and UL_TFC24 using TF1 on either RB5 or RB6 and TF1 on DCCH has been included in the allowed TFCs as those could happen during the sub-test. NOTE 3: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. RB5 and RB6: 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 make the UE to return one RLC SDU per UL TTI. NOTE 4: The test data size for RB5 and RB6 is dependent on the actual TFRC test point, see the generic test procedure in 14.1.3.5a.

Sub-tes

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)

25 to 28

2047

1024

RB5: 656

RB6: Flexible

UL_TFC19

UL_TFC0,

UL_TFC3,

UL_TFC16,

UL_TFC20

UL_TFC0,

UL_TFC1,

UL_TFC3,

UL_TFC4,

UL_TFC16,

UL_TFC19,

UL_TFC20,

UL_TFC21,

UL_TFC24,

UL_TFC39

RB5: 2552

RB6: 2552

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, UL_TFC4 and UL_TFC20 are part of minimum set of TFCIs. Also the transport format combinations UL_TFC21 and UL_TFC24 using TF1 on either RB5 or RB6 and TF1 on DCCH has been included in the allowed TFCs as those could happen during the sub-test.

NOTE 3: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs.
RB5 and RB6: 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 make the UE to return one RLC SDU per UL TTI.

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

14.6.6g.4 Test requirements

See 14.1.3.5a for definition of the referenced step numbers.

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 actual sub-test.

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 4 SDU or 16 SDUs depending on the transport block size under tests.