7.1.3 Priority handling between data flows of one UE

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

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

7.1.3.1 Priority handling between data flows of one UE

7.1.3.1.1 Definition and applicability

7.1.3.1.2 Conformance requirement

When selecting between the Transport Format Combinations in the given Transport FormatCombination Set, priorities of the data flows to be mapped onto the corresponding Transport Channels can be taken into account.

The chosen TFC shall be selected from within the set of valid TFCs and shall satisfy the following criteria in the order in which they are listed below:

1. No other TFC shall allow the transmission of more highest priority data than the chosen TFC.

2. No other TFC shall allow the transmission of more data from the next lower priority logical channels. Apply this criterion recursively for the remaining priority levels.

3. No other TFC shall have a lower bit rate than the chosen TFC.

The above rules for TFC selection in the UE shall apply to DCH, and the same rules shall apply for TF selection on RACH.

Reference(s)

TS 25.301 clause 5.3.1.2.

TS 25.321, clause 11.4.

7.1.3.1.3 Test purpose

To verify that the UE prioritise signalling compared to data on a lower priority logical channel.

7.1.3.1.4 Method of test

Initial conditions

System Simulator:

– 1 cell, default parameters, Ciphering Off.

User Equipment:

– The UE shall operate under normal test conditions, Ciphering Off.

– The Test-USIM shall be inserted.

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed, with all the parameters as specified in the procedure, with the exception that the default Radio Access Bearer is replaced with the RAB defined for UM 7-bit "Length Indicator" tests described in 3G TS 34.108 clause 6.11.1 is used.

For radio bearer setup the following settings shall be used in both CS and PS mode:

Re-establishment Timer: useT314
MAC logical channel priority: 7
UL Logical Channel Identity:7
DL Logical Channel Identity:7

Let UM_7_PayloadSize denote the RAB payload size in octets.

Related ICS/IXIT Statement(s)

None

Test procedure

a The SS transmits a TRANSPORT FORMAT COMBINATION CONTROL message using AM_RLC on the DCCH, which indicates that only transport format minimum set is allowed on the uplink for DCH transport channel on the DTCH. I.e. the restricted uplink transport format set shall be (DCCH, UM RLC 7 bit LI RB)=(TF0, TF0), (TF1, TF0) and (TF0, TF1).

b The SS closes the test loop using UE test loop mode 1 with the UL SDU size set to (UM_7_PayloadSize * 25) – 2 bytes. See note 1.

c. The SS transmits a MEASUREMENT CONTROL message requesting periodic reporting with a period of 250ms.

d. The SS sends one RLC SDUs of size floor (UM_7_PayloadSize) – 1 bytes to the UE. The UE is expected to loop this data back in one RLC SDU, segmented into a total of 25 RLC PDUs.

e. The SS waits until data is returned in uplink.

f. The SS checks that the UE transmits alternating measurement reports and data.

NOTE 1: Having UE to return 25 PDUs corresponds to 25*TTI (40 ms) = 1 second of continuous data transmission. SDU size shall be (UM_7_PayloadSize * 25) – 2 to account for presence of Special “Length Indicator” indicating “beginning of an SDU” in the first PDU for a Rel5 and later UE and presence of Special “Length Indicator” indicating end of SDU in the last PDU. As the periodic measurement interval is 250ms this will guarantee that data transmission will be interrupted by transmission of measurement reports in uplink.

Expected sequence

Step	Direction				Message	Comments
	UE		SS
1		<–		ACTIVATE RB TEST MODE (DCCH)		TC
2		–>		ACTIVATE RB TEST MODE COMPLETE (DCCH)		TC
3		<–		RADIO BEARER SETUP (DCCH)		RRC
4		–>		RADIO BEARER SETUP COMPLETE (DCCH)		RRC
4a		<–		TRANSPORT FORMAT COMBINATION CONTROL (DCCH)		RRC Transport format combinations is limited to transport format minimum set (DCCH, AM RLC 7 bit LI RB)=(TF0, TF0), (TF1, TF0) and (TF0, TF1).
5		<–		CLOSE UE TEST LOOP (DCCH)		TC UE test mode 1 with UL RLC SDU size parameter set to achieve UE to transmit 25 PDUs in uplink.
6		–>		CLOSE UE TEST LOOP COMPLETE (DCCH)		TC
7		–		Void
8		<–		MEASUREMENT CONTROL (DCCH)		SS sends a MEASUREMENT CONTROL message requesting periodic reporting at 250 ms interval.
9		<–		Downlink RLC PDU		SS sends a SDU fit into one PDU.
10		–>		Uplink RLC PDUs		SS starts receiving RLC PDUs from the UE on the UM RLC RB
11		–>		MEASUREMENT REPORT (DCCH)		SS checks that at least one MEASUREMENT REPORT message is received within 500 ms (=2 x reporting interval)
12		–>		Uplink RLC PDUs		SS checks that UE resumes returning RLC PDUs from the UE on the UM RLC RB

7.1.3.1.5 Test requirements

1. After step 10 the UE shall transmit a MEASUREMENT REPORT message within 500 ms.

2. After step 11 the UE shall resume data transmission.

7.1.3.2 TFC Selection

7.1.3.2.1 Definition and applicability

All UEs

7.1.3.2.2 Conformance requirement

Before selecting a TFC, i.e. at every boundary of the shortest TTI, or prior to each transmission on PRACH the set of valid TFCs shall be established. All TFCs in the set of valid TFCs shall:

1. belong to the TFCS.

1a. not be restricted by higher layer signalling (e.g. TFC Control, see [7]).

2. not be in the Blocked state.

3. be compatible with the RLC configuration.

4. not require RLC to produce padding PDUs (see [6] for definition).

5. not carry more bits than can be transmitted in a TTI (e.g. when compressed mode by higher layer scheduling is used and the presence of compressed frames reduces the number of bits that can be transmitted in a TTI using the Minimum SF configured).

[…]

The chosen TFC shall be selected from within the set of valid TFCs and shall satisfy the following criteria in the order in which they are listed below:

1. No other TFC shall allow the transmission of more highest priority data than the chosen TFC.

2. No other TFC shall allow the transmission of more data from the next lower priority logical channels. Apply this criterion recursively for the remaining priority levels.

3. No other TFC shall have a lower bit rate than the chosen TFC.

In FDD mode the above rules for TFC selection in the UE shall apply to DCH, and the same rules shall apply for TF selection on RACH.

[…]

Reference(s)

TS 25.301 clause 5.3.1.2.

TS 25.321, clause 11.4.

7.1.3.2.3 Test purpose

1. To verify that the UE supports a TFCS that does not allow simultaneous transmission of max data rate on all transport channels.

2. To verify that the UE selects a TFC according to the rule that no other TFC shall allow the transmission of more highest priority data than the chosen TFC.

3. To verify that the UE selects a TFC according to the rule that no other TFC shall allow the transmission of more data from the next lower priority logical channels.

7.1.3.2.4 Method of test

Initial conditions

System Simulator:

– 1 cell, default parameters, Ciphering Off.

User Equipment:

– The UE shall operate under normal test conditions, Ciphering Off.

– The Test-USIM shall be inserted.

RRC Connection Setup procedure is executed with the following exception for SRB 2

Parameter	Value
Polling Info
– Timer poll prohibit	500

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed, with all the parameters as specified in the procedure, with the following exceptions:

A radio bearer configuration for "Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL:16 DL:64 kbps / PS RAB + UL:13.6 DL:13.6 kbps SRBs for DCCH" is configured. This is a modified version of the radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.1.58 (FDD) clause 6.10.3.4.1.58 (3.85 Mcps TDD) for "Streaming / unknown / UL:16 DL:64 kbps / PS RAB + Interactive or background / UL: 8 DL: 8 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH" RAB with the following modifications:

NOTE This radio bearer configuration has been selected to provide for a representative test scenario for how UTRAN configures the TFCS such that the data rate can be increased on one transport channel when there is no (or low) activity on the other transport channels, e.g. to provide for improved signalling performance (13.6 kbps) when there is no data transmitted.

Uplink Transport channel parameters for Streaming / unknown / UL:16 kbps / PS RAB

Higher layer	RAB/Signalling RB		RAB
RLC	Logical channel type		DTCH
	RLC mode		AM
	Payload sizes, bit		320
	Max data rate, bps		16000
	AMD PDU header, bit		16
MAC	MAC header, bit		0
	MAC multiplexing		N/A
Layer 1	TrCH type		DCH
	TB sizes, bit		336
	TFS	TF0, bits	0x336
		TF1, bits	1×336
	TTI, ms		20
	Coding type		TC
	CRC, bit		16
	Max number of bits/TTI after channel coding		1068
	Uplink: Max number of bits/radio frame before rate matching		534
	RM attribute		135-175

Uplink Transport channel parameters for Interactive or background / UL:16 kbps / PS RAB

Higher layer	RAB/Signalling RB		RAB
RLC	Logical channel type		DTCH
	RLC mode		AM
	Payload sizes, bit		320
	Max data rate, bps		16000
	AMD PDU header, bit		16
MAC	MAC header, bit		0
	MAC multiplexing		N/A
Layer 1	TrCH type		DCH
	TB sizes, bit		336
	TFS	TF0, bits	0x336
		TF1, bits	1×336
		TF2, bits	2×336
	TTI, ms		40
	Coding type		TC
	CRC, bit		16
	Max number of bits/TTI after channel coding		2124
	Uplink: Max number of bits/radio frame before rate matching		531
	RM attribute		135-175

Uplink Transport channel parameters for UL:13.6 kbps SRBs for DCCH

Higher layer	RAB/signalling RB		SRB#1	SRB#2	SRB#3	SRB#4
	User of Radio Bearer		RRC	RRC	NAS_DT High prio	NAS_DT Low prio
RLC	Logical channel type		DCCH	DCCH	DCCH	DCCH
	RLC mode		UM	AM	AM	AM
	Payload sizes, bit		136	128	128	128
	Max data rate, bps		13600	12800	12800	12800
	AMD/UMD PDU header, bit		8	16	16	16
MAC	MAC header, bit		4	4	4	4
	MAC multiplexing		4 logical channel multiplexing
Layer 1	TrCH type		DCH
	TB sizes, bit		148 (alt 0, 148)
	TFS	TF0, bits	0x148 (alt 1×0)
		TF1, bits	1×148
		TF2, bits	2×148
		TF3, bits	4×148
	TTI, ms		40
	Coding type		CC 1/3
	CRC, bit		16
	Max number of bits/TTI before rate matching		~2064
	Uplink: Max number of bits/radio frame before rate matching		~516
	RM attribute		155-185

Uplink TFCS

TFCS size

TFCS

(Streaming RAB, Interactive RAB, DCCH)=

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

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

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

Uplink Physical channel parameters (FDD)

DPCH Uplink	Min spreading factor	32
	Max number of DPDCH data bits/radio frame	1200
	Puncturing Limit	1.0

Uplink Physical channel parameters (3.84Mcps TDD)

DPCH Uplink	Midamble	512 chips
	Codes and time slots	SF8 x 1 code x 1 time slot + SF16 x 1code x 1 time slot
	Max. Number of data bits/radio frame	696 bits
	TFCI code word	16 bits
	TPC	2 bits
	Puncturing Limit	0.72 (alt. 0.68)

Downlink Transport channel parameters for Streaming / unknown / DL:64 kbps / PS RAB

Higher layer	RAB/Signalling RB		RAB
RLC	Logical channel type		DTCH
	RLC mode		AM
	Payload sizes, bit		640
	Max data rate, bps		64000
	AM PDU header, bit		16
MAC	MAC header, bit		0
	MAC multiplexing		N/A
Layer 1	TrCH type		DCH
	TB sizes, bit		656
	TFS	TF0, bits	0x656
		TF1, bits	1×656
		TF2, bits	2×656
		TF3, bits	4×656
	TTI, ms		40
	Coding type		TC
	CRC, bit		16
	Max number of bits/TTI after channel coding		8076
	RM attribute		125-165

Downlink Transport channel parameters for Interactive or background / DL:64 kbps / PS RAB

Higher Layer	RAB/Signalling RB		RAB
RLC	Logical channel type		DTCH
	RLC mode		AM
	Payload sizes, bit		320
	Max data rate, bps		64000
	AMD PDU header, bit		16
MAC	MAC header, bit		0
	MAC multiplexing		N/A
Layer 1	TrCH type		DCH
	TB sizes, bit		336
	TFS	TF0, bits	0x336
		TF1, bits	1×336
		TF2, bits	2×336
		TF3, bits	4×336
		TF4, bits	8×336
	TTI, ms		40
	Coding type		TC
	CRC, bit		16
	Max number of bits/TTI after channel coding		8460
	RM attribute		135-175

Downlink Transport channel parameters for DL:13.6 kbps SRBs for DCCH

Higher layer	RAB/signalling RB		SRB#1	SRB#2	SRB#3	SRB#4
	User of Radio Bearer		RRC	RRC	NAS_DT High prio	NAS_DT Low prio
RLC	Logical channel type		DCCH	DCCH	DCCH	DCCH
	RLC mode		UM	AM	AM	AM
	Payload sizes, bit		136	128	128	128
	Max data rate, bps		13600	12800	12800	12800
	AMD/UMD PDU header, bit		8	16	16	16
MAC	MAC header, bit		4	4	4	4
	MAC multiplexing		4 logical channel multiplexing
Layer 1	TrCH type		DCH
	TB sizes, bit		148 (alt 0, 148) (note)
	TFS	TF0, bits	0x148 (alt 1×0) (note)
		TF1, bits	1×148
		TF2, bits	2×148
		TF3, bits	4×148

	TTI, ms		40
	Coding type		CC 1/3
	CRC, bit		16
	Max number of bits/TTI before rate matching		2064
	RM attribute		155-230
NOTE: alternative parameters enable the measurement "transport channel BLER" in the UE.

Downlink TFCS

TFCS size

TFCS

((Streaming RAB, Interactive RAB, DCCH)=

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

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

(TF0,TF2,TF0), (TF0,TF3,TF0), (TF0,TF4,TF0),

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

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

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

Downlink Physical channel parameters (FDD)

DPCH Downlink	DTX position		Flexible
	Spreading factor		32
	DPCCH	Number of TFCI bits/slot	8
		Number of TPC bits/slot	4
		Number of Pilot bits/slot	8
	DPDCH	Number of data bits/slot	140
	DPDCH	Number of data bits/frame	2100

Downlink Physical channel parameters (3.84 Mcps TDD)

DPCH Downlink	Midamble	256 chips
	Codes and time slots	SF16 x 6 codes x 1 time slot
	Max. Number of data bits/radio frame	1640 bits
	TFCI code word	16 bits
	Puncturing limit	0.64

The logical channel priorities are set according to the following:

Radio Bearer	Logical Channel Priority
RB1 (DCCH)	3
RB2 (DCCH)	3
RB3 (DCCH)	4
RB4 (DCCH)	5
RB 5 (streaming/unknown)	2
RB 6 (Interactive/ background)	7

Let PayloadSize denote the RAB payload size in octets.

Related ICS/IXIT Statement(s)

None

Test procedure

In the following, the Streaming/ unknown radio bearer is denoted RB 5, the Interactive/ background radio bearer is denoted RB 6, the payload size for RB5 is denoted RB5_PayloadSize and the payload size for RB6 is denoted RB6_PayloadSize.

a) The SS closes the test loop using UE test loop mode 1 with the UL SDU size set to (RB5_PayloadSize * 25) – 1 bytes for RB5 and to (RB6_PayloadSize * 25) – 1 bytes for RB6. See note 1.

b) The SS transmits a MEASUREMENT CONTROL message requesting periodic reporting with a period of 250ms.

c) The SS sends two RLC SDUs of size floor ( RB6_PayloadSize) – 1 bytes to the UE on RB 6. The UE is expected to loop this data back in two RLC SDUs, segmented into a total of 50 RLC PDUs.

d) The SS checks that data is returned in uplink

e) The SS waits until a measurement report is received and checks that the UE transmits the measurement report and data on RB6 simultaneously using a TFC that maximises the data rate for the SRB.

f) The SS waits until the UE has looped back all data

g) The SS sends two RLC SDUs of size floor ( RB5_PayloadSize) – 1 bytes to the UE on RB 5. The UE is expected to loop this data back in two RLC SDUs, segmented into a total of 50 RLC PDUs.

h) The SS sends two RLC SDUs of size floor (RB6_PayloadSize) – 1 bytes to the UE on RB 6. The UE is expected to loop this data back in two RLC SDUs, segmented into a total of 50 RLC PDUs.

i) The SS checks that data is returned in uplink on RB5 and RB6 simultaneously.

j) The SS waits until a measurement report is received and checks that during the reception of the measurement report, at least once data is also received on RB5 simultaneously, but not on RB6.

NOTE 1. Having UE to return 50 PDUs corresponds to 50*TTI (20 ms) = 1 second of continuous data transmission. As the periodic measurement interval is 250ms this will guarantee that data transmission will be interrupted by transmission of measurement reports in uplink. To keep the uplink SDU size below the limit (1500 octets) of the Max SDU size parameter associated with PDP context establishment then two downlink PDUs is used to generate the 50 uplink PDUs (uplink SDU size= 1000 octets).

Expected sequence

Step	Direction				Message	Comments
	UE		SS
1		<–		ACTIVATE RB TEST MODE (DCCH)		TC
2		–>		ACTIVATE RB TEST MODE COMPLETE (DCCH)		TC
3		<–		RADIO BEARER SETUP (DCCH)		RRC
4		–>		RADIO BEARER SETUP COMPLETE (DCCH)		RRC
5		<–		CLOSE UE TEST LOOP (DCCH)		TC UE test mode 1 with UL RLC SDU size parameter for RB5 and RB6 set to achieve UE to transmit 50 PDUs in uplink.
6		–>		CLOSE UE TEST LOOP COMPLETE (DCCH)		TC
7		<–		MEASUREMENT CONTROL (DCCH)		SS sends a MEASUREMENT CONTROL message requesting periodic reporting at 250 ms interval.
8		<–		2 x Downlink RLC PDU on RB6		SS sends two SDUs fit into two PDUs on RB6.
9		–>		Uplink RLC PDUs		SS starts receiving RLC PDUs from the UE on RB6
10		–>		MEASUREMENT REPORT (DCCH)		SS checks that at least one MEASUREMENT REPORT message is received within 500 ms (=2 x reporting interval) simultaneous with RB 6 data.
11		–>		Uplink RLC PDUs		SS checks that UE continues returning RLC PDUs on RB6
12		<–		2 x Downlink RLC PDU on RB5		SS sends two SDUs fit into two PDUs on RB5.
13		<–		2 x Downlink RLC PDU on RB6		SS sends two SDUs fit into two PDUs on RB6.
14		–>		Uplink RLC PDUs		SS starts receiving RLC PDUs from the UE on RB5 and RB6
15		–>		MEASUREMENT REPORT (DCCH) and simultaneous data on RB5 and RB6		SS checks that at least one MEASUREMENT REPORT message is received within 500 ms (=2 x reporting interval) simultaneous with RB 5 data but not on RB6 [Note 1].
16		–>		Uplink RLC PDUs		SS continues receiving RLC PDUs from the UE on RB5 and RB6

7.1.3.2.5 Test requirements

1. After step 8 the UE shall loopback data on RB6 using the transport format that carries the maximum amount of data (2 PDUs per TTI)

2. After step 10 the UE shall transmit a MEASUREMENT REPORT message within 500 ms.

3. After step 10 and during the reception of the MEASUREMENT REPORT message, data shall also be received on RB6

4. After step 13, the UE shall loopback data simultaneously on RB5 and RB6 using a TFC that carries data for both transport channels.

5. After step 15 the UE shall transmit a MEASUREMENT REPORT message within 500 ms

6. After step 15 and during the reception of the MEASUREMENT REPORT, the UE shall at least once simultaneously transmit data on RB5 but not on RB6 [Note 1].

NOTE 1: Due to the complexity of test case implementation, the SS verifies at least once that the UE transmits one Measurement report simultaneously with data on RB5 but not on RB6.