7.2.2 Unacknowledged mode

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

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

7.2.2.1 General information for UM tests

Two generic Radio Access Bearers are provided for UM tests.

The UM test RAB is set up using the Generic Procedure described in clause 7.1.3 of 3GPP TS 34.108, and with the default RAB replaced as follows:

– For UM 7-bit "Length Indicator" tests: the RB configuration described in 3GPP TS 34.108 clause 6.11.1 is used. For these tests, let UM_7_PayloadSize denote the RAB payload size in octets.

– For UM 15-bit "Length Indicator" tests: the RB configuration described in 3GPP TS 34.108 clause 6.11.2 is used. For these tests, let UM_15_PayloadSize denote the RAB payload size in octets.

The UM test RABs are used in all tests with the following exception:

– Tests that explicitly specify a different Radio Bearer configuration.

All other settings are the same.

The special "Length Indicator" indicating that an SDU begins in the first octet of a PDU, described in clause 9.2.2.8 in 3GPP TS 25.322 is not used in uplink or downlink except when explicitly stated in the corresponding test case.

7.2.2.2 Segmentation and reassembly / Selection of 7 or 15 bit "Length Indicators"

7.2.2.2.1 Definition

The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. The selection of the size of the "Length Indicator" fields used must follow the specified rules. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.2.2 Conformance requirement

Except for the predefined values reserved for special purposes and listed in TS 25.322 section 9.2.2.8 the "Length Indicator" shall:

– be set to the number of octets between the end of the RLC header and up to and including the last octet of an RLC SDU segment;

– be included in the PDUs that they refer to.

The size of the Length Indicator may be either 7 bits or 15 bits.

[…]

For UM:

– if the "largest UMD PDU size" is  l25 octets:

– 7-bit "Length Indicators" shall be used.

– else:

– 15-bit "Length Indicators" shall be used.

– between modifications of the "largest UMD PDU size", the size of the "Length Indicator" is the same for all UMD PDUs.

Reference(s)

TS 25.322 clauses 9.2.2.8 and 9.2.2.9.

7.2.2.2.3 Test purpose

To test that if the size of the largest PDU is  l25 octets, 7 bit indicators are used, otherwise, 15 bit indicators are used.

7.2.2.2.4 Method of test

Initial conditions

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 in clause 7.2.2.1.

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to 10 bytes.

Test procedure

a) The SS transmits an RLC SDU of size 10 bytes.

b) The SS checks the "Length Indicator" values and SDU size and contents in the RLC PDU returned on the uplink (assuming a 7-bit "Length Indicator" size). SS shall take into account presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel5 and later UE.

c) The SS releases the RB, and performs the Radio Bearer establishment procedure (clause 7.1.3 of TS 34.108) 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 15-bit "Length Indicator" tests in clause 7.2.2.1.

All other settings the same.

d) The SS transmits an RLC SDU of size 10 bytes.

e) The SS checks the "Length Indicator" values and SDU size and contents in the RLC PDU returned on the uplink (assuming a 15-bit "Length Indicator" size). SS shall take into account presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel5 and later UE.

f) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures for UM 7 bit LIs
2			DOWNLINK RLC PDU	10 byte SDU + padding
3			UPLINK RLC PDU	10 byte SDU + padding
4			RB RELEASE
5			RB ESTABLISHMENT	See generic procedures for UM 15 bit LIs (largest UMD PDU size > 125 bytes)
6			DOWNLINK RLC PDU	10 byte SDU + padding
7			UPLINK RLC PDU	10 byte SDU + padding
8			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.2.5 Test requirements

1. The UE shall send 7 bit "Length Indicators" with values that correctly indicate the end of the SDU received in step 3.

2. The UE shall send 15 bit "Length Indicators" with values that correctly indicate the end of the SDU received in step 7.

7.2.2.3 Segmentation and reassembly / 7-bit "Length Indicators" / Padding

7.2.2.3.1 Definition

The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.3.2 Conformance requirement

A "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU.

Except for the predefined values reserved for special purposes and listed in the tables below, the "Length Indicator" shall:

– be set to the number of octets between the end of the RLC header and up to and including the last octet of an RLC SDU segment;

– be included in the PDUs that they refer to.

[…]

For UM and AM RLC:

– if a 7 bit "Length Indicator" is used in a RLC PDU and one or more padding octets are present in the RLC PDU after the end of the last RLC SDU:

– indicate the presence of padding by including a "Length Indicator" with value "1111111" as the last "Length Indicator" in the PDU.

NOTE: After the "Length Indicator" indicating the presence of padding has been included in the RLC PDU, the length of the padding may be zero.

Reference(s)

TS 25.322 clauses 9.2.2.8 and 11.2.2.1.

7.2.2.3.3 Test purpose

1. To test that the UE correctly segments a large SDU, includes a "Length Indicator" indicating padding in the RLC PDU carrying the last SDU segment, and adds padding at the end.

2. To test that the UE correctly deals with a 7-bit padding "Length Indicator" when present in a received PDU.

7.2.2.3.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to UM_7_PayloadSize + 1 bytes.

Test procedure

a) The SS transmits an RLC SDU of size UM_7_PayloadSize + 1 bytes. The second of the 2 PDUs sent shall contain a "Length Indicator" indicating the end of the SDU and the "Length Indicator" indicating that padding is present.

b) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the length and content of the received RLC SDU (assuming a 7-bit "Length Indicator" size). SS shall take into account presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel5 and later UE in the first PDU.

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1 & Padding
4			UPLINK RLC PDU	No LI. See Note 2
5			UPLINK RLC PDU	Check LIs and re-assembled SDU
6			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes. NOTE 2: SS shall take into account presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel5 and later UE.

7.2.2.3.5 Test requirements

1. The UE shall return two RLC PDUs. The first RLC PDU shall not include "Length Indicators". except for presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel5 and later UE. The second RLC PDU shall have a "Length Indicator" indicating the PDU contains an SDU boundary after octet 1 of the data field, and the second “Length Indicator” shall indicate that the remainder of the PDU contains padding.

2. The length and data content of the received SDU shall be the same as the transmitted SDU.

7.2.2.4 Segmentation and Reassembly / 7-bit "Length Indicators" / LI = 0

7.2.2.4.1 Definition

The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. A pre-defined "Length Indicator" value is used to indicate when a SDU ends coincident with the end of the previous PDU. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.4.2 Conformance requirement

A "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU.

Except for the predefined values reserved for special purposes and listed in TS 25.322 subclause 9.2.2.8, the "Length Indicator" shall:

– be set to the number of octets between the end of the RLC header and up to and including the last octet of an RLC SDU segment;

– be included in the PDUs that they refer to.

[…]

In the case where the end of the last segment of an RLC SDU exactly ends at the end of a PDU and there is no "Length Indicator" that indicates the end of the RLC SDU:

– if 7-bit "Length Indicator" is used:

– a "Length Indicator" with value "000 0000" shall be placed as the first "Length Indicator" in the following PDU;

[…]

For UM and AM RLC:

– if a 7 bit "Length Indicator" is used in a RLC PDU and one or more padding octets are present in the RLC PDU after the end of the last RLC SDU:

– indicate the presence of padding by including a "Length Indicator" with value "1111111" as the last "Length Indicator" in the PDU.

Reference(s)

TS 25.322 clause 9.2.2.8 and 11.2.2.1.

7.2.2.4.3 Test purpose

1. To test that where a SDU exactly fills a PDU, a "Length Indicator" of all 0’s is placed by the transmitter as the first "Length Indicator" in the next PDU.

2. To test that where a SDU exactly fills a PDU, the receiver accepts a "Length Indicator" of all 0’s, placed as the first "Length Indicator" in the next PDU.

7.2.2.4.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_7_PayloadSize bytes. For a Rel-5 and later UE , the UL SDU size shall be set to (UM_7_PayloadSize -1) bytes.

Test procedure

a) The SS transmits an RLC SDU of size 2 * UM_7_PayloadSize bytes.

b) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the length and content of the received RLC SDU (assuming a 7-bit "Length Indicator" size).

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1
4			DOWNLINK RLC PDU	LI=0 and padding
5			UPLINK RLC PDU	No LIs. See Note 2
6			UPLINK RLC PDU	Check Lis and re-assembled SDU
7			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes. NOTE 2: SS shall take into account presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel5 and later UE.

7.2.2.4.5 Test requirements

The UE shall return two RLC PDUs. The first RLC PDU shall not include "Length Indicators" except for presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel-5 and later UE.. The second RLC PDU shall have a "Length Indicator" indicating that the SDU exactly filled the previous UMD PDU, and a "Length Indicator" indicating that the remainder of the PDU contains padding.

For Rel99 UE, the length of the received SDU shall be UM_7_PayloadSize bytes, and the data content shall be the same as the first UM_7_PayloadSize bytes of the transmitted SDU.

For Rel-5 and later UEs , the length of the received SDU shall be (UM_7_PayloadSize-1) bytes, and the data content shall be the same as the first (UM_7_PayloadSize-1) bytes of the transmitted SDU.

7.2.2.5 Reassembly / 7-bit "Length Indicators" / Invalid LI value

7.2.2.5.1 Definition

The RLC segments and concatenates SDUs into UMD PDU according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of an invalid "Length Indicator" value has been specified. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.5.2 Conformance requirement

Upon delivery by the lower layer of an UMD PDU that contains a "Length Indicator" value specified to be reserved for UMD PDUs in this version of the protocol, the Receiver shall:

– ignore that UMD PDU.

[…]

Length: 7 bits

Bit	Description
1111101	Reserved (PDUs with this coding will be discarded by this version of the protocol).
1111110	AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS PDU. UMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol).

Reference(s)

TS 25.322 clause 9.2.2.8 and 11.2.4.1.

7.2.2.5.3 Test purpose

To test that PDUs with invalid "Length indicator" ‘111 1110’ are discarded by the receiving RLC.

7.2.2.5.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into loop-back mode 1with the UL SDU size set to UM_7_PayloadSize + 1 bytes.

Test procedure

a) The SS transmits two RLC SDUs of size UM_7_PayloadSize + 1 bytes. In the third PDU for transmission, the SS sets the value of the second (padding) LI to 1111110.

b) The SS checks the "Length Indicator" sizes and values of any RLC PDUs returned on the uplink, and checks for the presence of any received RLC SDUs. SS shall take into account presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel-5 and later UE in the first PDU

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1 & SDU 2
4			DOWNLINK RLC PDU	SDU 2 and invalid LI (=11111110)
5			UPLINK RLC PDU	SDU 1
6			UPLINK RLC PDU	SDU 1: Check Lis and re-assembled SDU
7			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.5.5 Test requirements

The UE shall return two RLC PDUs. The first RLC PDU shall not include any "Length Indicators" except for presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel-5 and later UE. The second RLC PDU shall have a "Length Indicator" indicating the end of the SDU, and a padding "Length Indicator".

The length and data content of the received SDU shall be the same as the first transmitted SDU. The second SDU shall not be returned.

7.2.2.6 Reassembly / 7-bit "Length Indicators" / LI value > PDU size

7.2.2.6.1 Definition

The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of an invalid "Length Indicator" value has been specified. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.6.2 Conformance requirement

If the "Length Indicator" of an UMD PDU has a value that is larger than the PDU size – RLC header size and is not one of the predefined values listed in the table of TS 25.322 subclause 9.2.2.8, the Receiver shall:

– ignore the UMD PDU.

[…]

Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall:

– update VR(US) according to each received UMD PDU (see TS 25.322 subclause 9.4);

– if the updating step of VR(US) is not equal to one (i.e. one or more UMD PDUs are missing):

– discard the SDUs that have segments in the missing UMD PDUs.

Reference(s)

TS 25.322 clauses 11.2.4.2 and 11.2.3.

7.2.2.6.3 Test purpose

To test that PDUs with "Length Indicators" that point beyond the end of the PDU are ignored by the receiving RLC entity.

7.2.2.6.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_7_PayloadSize + 1 bytes.

Test procedure

a) The SS transmits three RLC SDUs of size UM 7 PayloadSize + 1 bytes. All the SDUs are concatenated or segmented over successive RLC PDUs. In the third PDU for transmission, the SS sets value of the "Length Indicator" to be UM_7_PayloadSize (decimal).

b) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the length and content of the received RLC SDUs (assuming a 7-bit "Length Indicator" size). . SS shall take into account presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel-5 and later UE in the first PDU

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1 & SDU 2
4			DOWNLINK RLC PDU	SDU 2 & SDU 3, with bad LI
5			DOWNLINK RLC PDU	SDU 3 and padding
6			UPLINK RLC PDU	SDU 1
7			UPLINK RLC PDU	SDU 1 and padding: Check LIs and re-assembled SDU
8			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.6.5 Test requirements

The UE shall return two RLC PDUs. The first RLC PDU shall not include "Length Indicators" except for presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel-5 and later UE. The second RLC PDU shall have a LI indicating the end of an SDU and an "Length Indicator" indicating that the remainder of the PDU contains padding.

The length and data content of the received SDU should be the same as the first transmitted SDU. No further SDUs or PDUs should be received.

7.2.2.7 Reassembly / 7-bit "Length Indicators" / First data octet LI

7.2.2.7.1 Definition

The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length indicators" are added to allow correct reconstruction of SDUs. A special "Length Indicator" is defined to indicate that the start of an SDU is coincident with the start of the PDU. The special "Length Indicator" is needed to avoid discarding of an SDU when the first received PDU has a sequence number different from zero. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.7.2 Conformance requirement

1. "Length Indicator" = 1111100, UMD PDU: The first data octet in this RLC PDU is the first octet of a RLC SDU.

2. Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall:

…

– if the special "Length Indicator" "1111 100" or "1111 1111 1111 100" is the first "Length Indicator" of a UMD PDU received on the downlink:

– consider the first data octet in this UMD PDU as the first octet of an RLC SDU.

Reference(s)

1. TS 25.322 clause 9.2.2.8.

2. TS 25.322 clause 11.2.3.

7.2.2.7.3 Test purpose

To test that a UE in unacknowledged mode correctly handles a received RLC PDU with a 7-bit "Length Indicator" having its value equal to the special "Length Indicator" value 1111100 when the sequence number of the first received PDU is different from zero.

7.2.2.7.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to 12 bytes.

Test procedure

a) The SS transmits a RLC SDU of size 12 bytes in a PDU which has the ‘First Data Octet LI’ as the first "Length Indicator" in the PDU.

b) The SS waits until the SDU has been received back from the UE, and then transmits another SDU of 12 bytes in a PDU which has the ‘First Data Octet LI’ as the first "Length Indicator" in the PDU.

c) The SS waits until this SDU has been received back from the UE.

c) The SS may optionally release the radio bearer.

NOTE: The SS sends PDUs in downlink starting at sequence number 10.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU, SN 10	SDU 1 with LI = 1111100
3			…	Wait for loopback
4			UPLINK RLC PDU	SDU 1. See Note 2
5			DOWNLINK RLC PDU, SN 11	SDU 2 with LI = 1111100
6			UPLINK RLC PDU	SDU 2. See Note 2
7			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes. NOTE 2: SS shall take into account presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel5 and later UE.

7.2.2.7.5 Test requirements

1. The UE shall return two RLC PDUs.

2. The length and data content of each received SDU shall be the same as the transmitted SDU.

7.2.2.8 Segmentation and reassembly / 15-bit "Length Indicators" / Padding

7.2.2.8.1 Definition

The RLC segments and concatenates SDUs into UMD PDU according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.8.2 Conformance requirement

A PDU that has unused space, to be referred to as padding, shall use a "Length Indicator" to indicate that this space is used as padding unless the padding size is one octet for PDUs with 15-bit "Length Indicators". A padding "Length Indicator" must be placed after any "Length Indicators" for a PU.

One "Length Indicator" field shall be included for each end of a SDU that the PDU includes. The "Length Indicator" shall be set equal to the number of octets between the end of the header fields and the end of the segment. If padding is needed, another "Length Indicator" field set to only 1’s shall be added unless the padding size is one octet for PDUs with 15-bit "Length Indicators".

Reference(s)

TS 25.322 clauses 9.2.2.8 and 11.2.2.1.

7.2.2.8.3 Test purpose

1. To test that the UE correctly segments a large SDU and padding is added at the end.

2. To test that the UE correctly deals with a 15-bit padding "Length Indicator" when present in a received PDU.

7.2.2.8.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to UM_15_PayloadSize + 1 bytes.

Test procedure

a) The SS transmits an RLC SDU of size UM_15_PayloadSize + 1 bytes. The second of the 2 PDUs sent shall contain a "Length Indicator" indicating the end of the SDU and the "Length Indicator" indicating that padding is present.

b) The SS checks the "Length Indicator" values in the RLC PDU returned on the uplink, and checks the length and content of the received RLC SDU (assuming a 15-bit "Length Indicator" size).

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1 & Padding
4			UPLINK RLC PDU	No LI
5			UPLINK RLC PDU	Check LIs and re-assembled SDU
6			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.8.5 Test requirements

1. The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have a "Length Indicator" indicating the PDU contains a SDU boundary after octet 1 of the data field, and the second shall indicate that the remainder of the PDU contains padding.

2. The length and data content of the received SDU shall be the same as the transmitted SDU.

7.2.2.9 Segmentation and Reassembly / 15-bit "Length Indicators" / LI = 0

7.2.2.9.1 Definition

The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. A pre-defined "Length Indicator" value is used to indicate when an SDUs ends coincident with the end of the previous PU. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.9.2 Conformance requirement

If the PDU is exactly filled with the last segment of a SDU and there is no room for an "Length Indicator" field, a "Length Indicator" field set to all 0’s shall be included as the first "Length Indicator" in the following PDU.

Reference(s)

TS 25.322 clause 11.2.2.1.

7.2.2.9.3 Test purpose

1. To test that where a SDU exactly fills a PDU, a "Length Indicator" of all 0’s is placed by the transmitter as the first "Length Indicator" in the next PDU.

2. To test that where an SDU exactly fills a PDU, and an "Length Indicator" of all 0’s is the first "Length Indicator" in the next PDU, the receiver correctly reassembles the PDU.

7.2.2.9.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_15_PayloadSize bytes.

Test procedure

a) The SS transmits an RLC SDU of size 2 * UM_15_PayloadSize bytes.

b) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the length and content of the received RLC SDU (assuming a 15-bit "Length Indicator" size).

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1
4			DOWNLINK RLC PDU	LI=0 and padding
5			UPLINK RLC PDU	No Lis
6			UPLINK RLC PDU	Check LIs and re-assembled SDU
7			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.9.5 Test requirements

The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have an "Length Indicators" indicating that the SDU exactly filled the previous UMD PDU, and a "Length Indicators" indicating that the remainder of the PDU contains padding.

The length of the received SDU shall be UM_15_PayloadSize bytes, and the data content shall be the same as the first UM_15_PayloadSize bytes of the transmitted SDU.

7.2.2.10 Segmentation and reassembly / 15-bit "Length Indicators" / One octet short LI

7.2.2.10.1 Definition

The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. A pre-defined "Length Indicator" value is used to indicate when an SDUs ends one octet short of the end of the previous PDU. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.10.2 Conformance requirement

In the case where the last segment of an RLC SDU is one octet short of exactly filling the last RLC PDU, and 15-bit "Length Indicators" are used, the next "Length Indicator" shall be placed as the first "Length Indicator" in the next PDU and have value "Length Indicator"=111 1111 1111 1011.

In the case where a PDU contains a 15-bit "Length Indicator" indicating that an SDU ends with one octet left in the PDU, the last octet of this PDU shall be ignored and shall not be filled with the first octet of the next SDU data.

Reference(s)

TS 25.322 clause 9.2.2.8.

7.2.2.10.3 Test purpose

1. To test that where the UE transmits an SDU, which is one byte short of filling a PDU, an "Length Indicator" indicating one byte short is placed as the first "Length Indicator" in the next PDU.

2. To test that where the UE correctly handles a received PDU containing an "Length Indicator" indicating that an SDU ended one byte short of the end of the previous PDU.

7.2.2.10.4 Method of test

Initial conditions

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS34.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 15-bit "Length Indicator" tests in clause 7.2.2.1.

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to UM_15_PayloadSize – 1bytes.

Test procedure

a) The SS transmits an RLC SDU of size (2 * UM_15_PayloadSize) – 1 bytes.

b) The SS checks the "Length Indicator" sizes and values in the RLC PDUs returned on the uplink, and checks the length and content of the received RLC SDU (assuming a 15-bit "Length Indicator" size).

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1
4			DOWNLINK RLC PDU	LI=111 1111 1111 1011 and padding
5			UPLINK RLC PDU	No LIs
6			UPLINK RLC PDU	Check LIs and re-assembled SDU
7			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.10.5 Test requirements

1. The UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second shall have 2 "Length Indicators". The first "Length Indicator" shall be a "Length Indicator" indicating that the SDU was one byte short of filling the previous PDU, and the second shall be a "Length Indicator" indicating that the remainder of the PDU contains padding.

2. The length of the received SDU shall be UM_15_PayloadSize – 1bytes, and the data content shall be the same as the first UM_15_PayloadSize – 1 bytes of the transmitted SDU.

7.2.2.11 Reassembly / 15-bit "Length Indicators" / Invalid LI value

7.2.2.11.1 Definition

7.2.2.11.2 Conformance requirement

Upon delivery by the lower layer of an UMD PDU that contains a "Length Indicator" value specified to be reserved for UMD PDUs in this version of the protocol, the Receiver shall:

– ignore that UMD PDU.;

Length: 15bits

Bit	Description
111111111111110	AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS PDU. UMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol).

Reference(s)

TS 25.322 clause 11.2.4.1, 9.2.2.8.

7.2.2.11.3 Test purpose

To test that PDUs with invalid "Length Indicators" are discarded by the receiving RLC.

7.2.2.11.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_15_PayloadSize + 1 bytes.

Test procedure

a) The SS transmits two RLC SDUs of size UM_15_PayloadSize + 1 bytes. In the third PDU for transmission, the SS sets the value of the second (padding) LI to 111111111111110.

b) The SS checks the "Length Indicator" sizes and values of any RLC PDUs returned on the uplink, and checks for the presence of any received RLC SDUs.

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1 & SDU 2
4			DOWNLINK RLC PDU	SDU 2 and invalid LI (=111111111111110)
5			UPLINK RLC PDU	SDU 1
6			UPLINK RLC PDU	SDU 1: Check Lis and re-assembled SDU
7			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.11.5 Test requirements

The UE shall return two RLC PDUs. The first shall not include any "Length Indicators". The second shall have a "Length Indicator" indicating the end of the SDU, and a padding "Length Indicator".

The length and data content of the received SDU shall be the same as the first transmitted SDU. The second SDU shall not be returned.

7.2.2.12 Reassembly / 15-bit "Length Indicators" / LI value > PDU size

7.2.2.12.1 Definition

7.2.2.12.2 Conformance requirement

If the "Length Indicator" of a PDU has a value that is larger than the PDU size – the number of octets containing "Length Indicators" in the PDU – 1 and is not one of the predefined values listed in the table of 3GPP TS 25.322 clause 9.2.2.8, the PDU shall be discarded and treated as a missing PDU.

If a PDU with sequence number < VR(US) is missing then all SDUs that have segments in this PDU shall be discarded.

Reference(s)

TS 25.322 clauses 11.2.4.2 and 11.2.3.

7.2.2.12.3 Test purpose

To test that PDUs with "Length Indicators" that point beyond the end of the PDU are ignored by the receiving RLC entity.

7.2.2.12.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into loop-back mode 1 with the UL SDU size set to UM_15_PayloadSize + 1bytes.

Test procedure

a) The SS transmits three RLC SDUs of size UM_15_PayloadSize + 1 bytes. All the SDUs are concatenated or segmented over successive RLC PDUs. In the third PDU for transmission, the SS sets value of the "Length Indicator" to be UM_15_PayloadSize + 1 (decimal).

b) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the length and content of the received RLC SDUs (assuming a 15-bit "Length Indicator" size).

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 1 & SDU 2
4			DOWNLINK RLC PDU	SDU 2 & SDU 3, with bad LI
5			DOWNLINK RLC PDU	SDU 3 and padding
6			UPLINK RLC PDU	SDU 1
7			UPLINK RLC PDU	SDU 1 and padding: Check LIs and re-assembled SDU
8			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.12.5 Test requirements

The UE shall return two RLC PDUs. The first shall not include any "Length Indicators". The second shall have a "Length Indicator" indicating the end of an SDU and a "Length Indicator" indicating that the remainder of the PDU contains padding.

The length and data content of the received SDU shall be the same as the first transmitted SDU. No further SDUs or PDUs shall be received.

7.2.2.13 Reassembly / 15-bit "Length Indicators" / First data octet LI

7.2.2.13.1 Definition

The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. A special LI is defined to indicate that the start of on SDU is coincident with the start of the PDU. The special LI is needed to avoid discarding of an SDU when the first received PDU has a sequence number different from zero. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.2.13.2 Conformance requirement

"Length Indicators" = 111111111111100, UMD PDU: The first data octet in this RLC PDU is the first octet of a RLC SDU.

Reference(s)

TS 25.322 clause 9.2.2.8.

7.2.2.13.3 Test purpose

To test that a UE in unacknowledged mode correctly handles a received RLC PDU with a 15-bit "Length Indicator" having its value equal to the special LI value 111111111111100 when the sequence number of the first received PDU is different from zero.

7.2.2.13.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to 150 bytes.

Test procedure

a) The SS transmits a RLC SDU of size 150 bytes in a PDU which has the ‘First Data Octet LI’ as the first "Length Indicator" in the PDU.

b) The SS waits until the SDU has been received back from the UE, and then transmits another SDU of 150 bytes in a PDU which has the ‘First Data Octet LI’ as the first "Length Indicator" in the PDU.

c) The SS waits until this SDU has been received back from the UE.

c) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1 with LI = 111111111111100
3			…	Wait for loopback
4			UPLINK RLC PDU	SDU 1
5			DOWNLINK RLC PDU	SDU 2 with LI = 111111111111100
6			UPLINK RLC PDU	SDU 2
7			RB RELEASE	Optional step
NOTE 1: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.13.5 Test requirements

1. The UE shall return two RLC PDUs.

2. The length and data content of each received SDU shall be the same as the transmitted SDU.

7.2.2.14 Flexible handling of RLC PDU sizes for UM RLC in downlink

7.2.2.14.1 Definition

When UM RLC is mapped to MAC-ehs (downlink only) the RLC PDU size can have arbitrary size (integer number of octets). The network can choose to segment the SDUs into smaller RLC PDUs or select the RLC PDU size to exactly fit the SDU size.

7.2.2.14.2 Conformance requirement

Unless the "Extension bit" indicates that a UMD PDU contains a complete SDU which is not segmented, concatenated or padded, or the HE field indicates that an AMD PDU contains the last octet of the RLC SDU, a "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU

[…]

The interpretation of this [E bit] bit depends on RLC mode and higher layer configuration:

– In the UMD PDU, the "Extension bit" in the first octet has either the normal E-bit interpretation or the alternative E-bit interpretation depending on higher layer configuration. The "Extension bit" in all the other octets always has the normal E-bit interpretation.

– In the AMD PDU, the "Extension bit" always has the normal E-bit interpretation.

Normal E-bit interpretation:

Bit	Description
0	The next field is data, piggybacked STATUS PDU or padding
1	The next field is Length Indicator and E bit

Alternative E-bit interpretation:

Bit	Description
0	The next field is a complete SDU, which is not segmented, concatenated or padded.
1	The next field is Length Indicator and E bit

[…]

If one or more SDUs have been scheduled for transmission according to subclause 11.2.2, the Sender shall:

– inform the lower layer of the number and size of SDUs scheduled for transmission;

– segment, and if possible concatenate the SDUs according to the PDU sizes indicated by the lower layer (see subclause 9.2.2.9);

[…]

– reassemble the received UMD PDUs into RLC SDUs;

– submit the RLC SDUs to upper layers through the UM-SAP.

Reference(s)

TS 25.322 clauses 9.2.2.8, 11.2.2 and 11.2.3.

7.2.2.14.3 Test purpose

1. To test that a large SDU is correctly received for varying RLC PDU sizes up to the maximum RLC PDU size

2. To test that a segmented SDU is reassembled correctly and delivered to higher layers

7.2.2.14.4 Method of test

Initial conditions

The following parameters are specific for this test case:

Parameter	Value
DL UM RLC LI size	15
Alternative E-bit interpretation	TRUE

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed, with all the parameters as specified in the procedure, with the exception that the default Radio Bearer is replaced with the RB according to 34.108 clause 6.11.4j.1..

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

Test procedure

a) The SS transmits one RLC SDU of size 20 octets. An RLC PDU is created by adding a one octet UMD header (the SDU is not segmented or concatenated). In the RLC PDU the E field is set to “0”.

b) The SS checks the length and content of the received RLC SDUs

c) The SS transmits one RLC SDU of size 80 octets. An RLC PDU is created by adding a one octet UMD header (the SDU is not segmented or concatenated). In the RLC PDU the E field is set to “0”.

d) The SS checks the length and content of the received RLC SDUs

e) The SS transmits one RLC SDU of size 1500 octets. An RLC PDU is created by adding a one octet UMD header (the SDU is not segmented or concatenated). In the RLC PDU the E field is set to “0”.

f) The SS checks the length and content of the received RLC SDUs

g) The SS transmits one RLC SDU of size 240 octets. The SDU is segmented into successive RLC PDUs of size 2-3, 43, 83 and 103 octets including a one octet UMD header and a length indicator in each RLC PDU.

h) The SS checks the length and content of the received RLC SDUs

i) The SS opens the UE test loop and release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures,
2			Close UE test loop
3			DOWNLINK RLC PDU (SDU1)	SN=0, RLC SDU size = 20 Octets
4			UPLINK RLC PDU (SDU1)	The SS checks length and content of received RLC SDU.
5			DOWNLINK RLC PDU (SDU2)	SN=1, RLC SDU size = 80 Octets
6			UPLINK RLC PDU (SDU2)	The SS checks length and content of received RLC SDU.
7			DOWNLINK RLC PDU (SDU3)	SN=2, RLC SDU size = 1500 Octets
8			UPLINK RLC PDU (SDU3)	The SS checks length and content of received RLC SDU.
9			DOWNLINK RLC PDUs (SDU4)	SN= 3,4,5,6, RLC SDU size = 240 Octets.
10			UPLINK RLC PDU (SDU4)	The SS checks length and content of received RLC SDU.
11			Open UE test loop
12			RB RELEASE
NOTE 1: The Expected Sequence shown is informative. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.14.5 Test requirements

For each execution of the test procedure:

1. In steps 4, the UE shall return one RLC SDU with the same size and content as the transmitted SDU

2. In steps 6, the UE shall return one RLC SDU with the same size and content as the transmitted SDU

3. In steps 8, the UE shall return one RLC SDU with the same size and content as the transmitted SDU

4. In steps 10, the UE shall return one RLC SDU with the same size and content as the transmitted SDU

7.2.2.15 Flexible handling of RLC PDU sizes for UM RLC in uplink

7.2.2.15.1 Definition

When UM RLC is mapped to MAC-i/is (uplink only) the RLC PDU size can have arbitrary size (integer number of octets) as long as the size is between the configured minimum and maximum size. For each transmission the RLC entity constructs an RLC PDU with a size that matches the size indicated by the MAC layer.

7.2.2.15.2 Conformance requirement

The transmitting UM RLC entity segments the RLC SDU into UMD PDUs of appropriate size, if the RLC SDU is larger than the length of available space in the UMD PDU. The size of the UMD PDUs after segmentation and/or concatenation shall be smaller than or equal to the largest UL UMD PDU size. If MAC-i/is has been configured, the size of the UMD PDUs after segmentation and/or concatenation shall be larger than or equal to the Minimum UL RLC PDU size.

[..]

– in uplink, if MAC-i/is has been configured:

– if the UE pre-generates RLC PDUs for transmission in a later TTI:

– provided that the UE has sufficient amount of data available for transmission, the size of the data field of the RLC PDU shall be chosen so that each RLC PDU to be multiplexed to the MAC-i/is PDU matches the maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) for the current TTI.

– RLC PDUs may only be pre-generated if the amount of data in outstanding pre-generated RLC PDUs for this logical channel is less than or equal to four times the maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) for the current TTI.

– else:

– the size of the data field of the RLC PDU shall be chosen so that the RLC PDU size matches the data requested for this logical channel by the current E-TFC selection.

[…]

For UM uplink:

– if the "largest UL UMD PDU size" is  125 octets:

– 7-bit "Length Indicators" shall be used.

– else:

– 15-bit "Length Indicators" shall be used.

[…]

If one or more SDUs have been scheduled for transmission according to subclause 11.2.2, the Sender shall:

– inform the lower layer of the number and size of SDUs scheduled for transmission;

– segment, and if possible concatenate the SDUs according to the PDU sizes indicated by the lower layer (see subclause 9.2.2.9);

Reference(s)

TS 25.322 clauses 4.2.1.2.1, 9.2.2.8 and 11.2.2.2.

7.2.2.15.3 Test purpose

1. To test that SDUs are correctly concatenated/segmented into RLC PDUs not smaller than “Minimum UL PDU size” (unless there is no other data in the buffer) and not larger than “largest UL UMD PDU size”

2. To test that the size of the RLC PDU is adapted to the size of the issued grant

3. To test that the size of the Length Indicator field is correctly selected based on the maximum PDU size

7.2.2.15.4 Method of test

Initial conditions

The following parameters are specific for this test case:

Parameter	Value
Minimum UL PDU size	320 bit (Note 1)
Largest UL UMD PDU size	640 bit (Note 1)
Alternative E-bit interpretation	TRUE
Note 1: The actual value is (IE value * 8) + 16

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 exceptions that the default Radio Bearer is replaced with the RB according to 34.108 clause 6.11.4k.1 (Flexible RLC + MAC-i/is) and that the MAC-d flow#1 of the RB in 34.108 clause 6.11.4k.1 is configured for scheduled transmissions.

The UE is placed into UE test loop mode 1 with the UL SDU size set to 80 octets.

Test procedure

a) The SS has not issued any grant to the UE for E-DCH

b) The SS transmits 4 RLC SDUs of size 80 octets. RLC PDUs are created by adding a one octet UMD header (the SDUs are not segmented or concatenated). In each RLC PDU the E field is set to “0”.

c) The SS waits for an SI

d) The SS issues an absolute grant correspondent to a Maximum allowed RLC PDU size below the configured “Minimum UL PDU size” (signalling value 3). See note 1.

e) The SS checks the content of the received RLC SDUs and size of the received RLC PDUs;

f) The SS removes the scheduling grant for the UE

g) The SS transmits 4 RLC SDUs of size 80 octets. RLC PDUs are created by adding a one octet UMD header (the SDUs are not segmented or concatenated). In each RLC PDU the E field is set to “0”.

h) The SS issues an absolute grant correspondent to a Maximum allowed RLC PDU size above the configured “Largest UL UMD PDU size” (signalling value 5). See note 2.

i) The SS checks the content of the received RLC SDUs and size of the received RLC PDUs

j) The SS opens the UE test loop and release the radio bearer.

NOTE 1: Signalled absolute grant of 3 enable the UE to transmit a maximum RLC PDU size of 235 bits (10ms TTI, Reference E-TFCI=11 Signalled power offset=4), which is less than the configured “Minimum UL PDU size” of 320 bits.

NOTE 2: Signalled absolute grant of 5 together with mentioned reference E-TFCI for 2/10 ms TTI, SS allocates enough resources for the UE to transmit RLC PDU which is not larger than the configured with E_TFCI-50(2ms TTI) and E_TFCI-45(10ms TTI) “Largest UL PDU size” of 656bits.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures,
2			Close UE test loop
3			DOWNLINK RLC PDUs	SN=0,1,2,3, RLC SDU size = 80 Octets
4			SI indicating data
5			Absolute grant	Grant value 3
6			UPLINK RLC PDUs	The SS checks length and content of received RLC SDUs.
7			Absolute grant	Grant value 1, removal of SG
8			DOWNLINK RLC PDUs	SN=4,5,6,7, RLC SDU size = 80 Octets
9			SI indicating data
10			Absolute grant	Grant value 5
11			UPLINK RLC PDUs	The SS checks length and content of received RLC SDUs.
12			Open UE test loop
13			RB RELEASE
NOTE 1: The Expected Sequence shown is informative. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes.

7.2.2.15.5 Test requirements

For each execution of the test procedure:

1. In step 6, the UE shall return 4 RLC SDUs with the same content as the transmitted SDUs. The RLC PDU size of the first three RLC PDUs shall be equal to “minimum UL PDU size”. The size of the LI field in the RLC header shall be 7 bit.

2. In step 11, the UE shall return 4 RLC SDUs with the same content as the transmitted SDUs. The RLC PDU size of the first RLC PDU shall be equal to “Largest UL UMD PDU size”, the subsequent RLC PDUs shall be between minimum UL PDU size and Largest UL UMD PDU size, and the last PDU shall be less than the Largest UL UMD PDU size. The size of the LI field in the RLC header shall be 7 bit.