7.2.3 Acknowledged 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.3.1 General information for AM tests

Two generic Radio Access Bearers are provided for AM tests.

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

– For AM 7-bit "Length Indicator" tests: the RB configuration described in 3G TS 34.108 clause 6.11.3 is used. For these tests, let AM_7_PayloadSize denote the RAB payload size in octets.

– For AM 15-bit "Length Indicator" tests: the RB configuration described in 3G TS 34.108 clause 6.11.4 is used. For these tests, let AM_15_PayloadSize denote the RAB payload size in octets.

Unless specified in individual test cases, the default RLC settings are given in table 7.2/1.

Table 7.2/1: RLC Parameters for AM testing

Uplink RLC
Transmission RLC discard
Max DAT retransmissions
Max_DAT	4
Transmission window size	128
Timer_RST	500
Max_RST	4
Polling info
Timer_poll_prohibit	disabled
Timer_poll	disabled
Poll_PU	disabled
Poll_SDU	disabled
Last transmission PDU poll	TRUE
Last retransmission PDU poll	TRUE
Poll_Window	disabled
Timer_poll_periodic	disabled
Downlink RLC
In-sequence delivery	TRUE
Receiving window size	128
Timer_Status_Prohibit	disabled
Timer_EPC	disabled
Missing PDU Indicator	TRUE
Timer_STATUS_periodic	disabled

The AM 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.

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

7.2.3.2.1 Definition

The RLC segments and concatenates SDUs into PDUs according to the PDU size configured by RRC. "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.3.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 AM:

– if the "AMD PDU size" is  l26 octets:

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

– else:

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

– the size of the "Length Indicator" is always the same for all AMD PDUs, for one RLC entity.

Reference(s)

TS 25.322 clauses 9.2.2.8 and 9.2.2.9.

7.2.3.2.3 Test purpose

To test that if the configured AMD PDU size is  l26 octets, 7 bit "Length Indicators" are used in transmitted AMD PDUs, otherwise, 15 bit "Length Indicators" are used.

7.2.3.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 AM 7-bit "Length Indicator" tests in clause 7.2.3.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. The PDU carrying this SDU is transmitted with a poll for status.

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).

c) The SS releases the RB.

The SS 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 AM 15-bit "Length Indicator" tests in clause 7.2.3.1.

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Transmission window size	16
Downlink RLC
Receiving window size	16

All other settings are the same.

d) The SS transmits an RLC SDU of size 10 bytes. The PDU carrying this SDU is transmitted with a poll for status.

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).

f) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures for AM 7 bit LIs
2			DOWNLINK RLC PDU	10 byte SDU + padding + poll
3			UPLINK RLC PDU	10 byte SDU + piggy-backed status + poll
3a			STATUS PDU	If piggy-backed status is not used in 3
4			STATUS PDU
5			RB RELEASE
6			RB ESTABLISHMENT	See generic procedures for AM 15 bit LIs (AMD PDU size > 126 bytes)
7			DOWNLINK RLC PDU	10 byte SDU + padding + poll
8			UPLINK RLC PDU	10 byte SDU + piggy-backed status + poll
8a			STATUS PDU	If piggy-backed status is not used in 7
9			STATUS PDU
10			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.3.2.5 Test requirements

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

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

7.2.3.3 Segmentation and Reassembly / 7-bit "Length Indicators" / Padding or Piggy-backed Status

7.2.3.3.1 Definition

The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. "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.3.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.

Predefined values of the "Length Indicator" are used to indicate padding. The values that are reserved for special purposes are listed in the tables below depending on the size of the "Length Indicator". Only predefined "Length Indicator" values can refer to the padding space. These values shall only be placed after all other "Length Indicators" for a PDU.

STATUS PDUs can be piggybacked on the AMD PDU by using part or all of the padding space. A predefined "Length Indicator" shall be used to indicate the presence of a piggybacked STATUS PDU. This "Length Indicator" replaces the padding "Length Indicator". The piggybacked STATUS PDU shall be appended immediately following the PDU data. When only part of the padding space is used, the end of the piggybacked STATUS PDU is indicated by one of the SUFI fields NO_MORE or ACK. Thus no additional "Length Indicator" is required to show that there is still padding in the AMD PDU.

[…]

Sender shall:

– when RLC SDUs are received from upper layers:

– segment the RLC SDUs into AMD PDUs where the fixed PDU size is configured by upper layer;

– set a "Length Indicator" field for each SDU that ends in the AMD PDU according to subclause 9.2.2.8;

[…]

The Receiver may:

– if STATUS PDU(s) to be sent fit into padding octets in AMD PDU(s) to be sent:

– piggyback a STATUS PDU on the AMD PDU to be sent.

Submission of a piggybacked STATUS PDU in an AMD PDU to the lower layer follows the same rules as an ordinary STATUS PDU.

Reference(s)

TS 25.322 clauses 9.2.2.8, 11.3.2 and 11.5.2.1.

7.2.3.3.3 Test purpose

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

2. To test that a large SDU is received correctly, whether or not it has piggy-backed status at the end.

7.2.3.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 AM_7_PayloadSize + 1 bytes.

Test procedure

a) The SS transmits an RLC SDU (SDU1) of size AM_7_PayloadSize + 1bytes, and polls the receiver for status.

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 transmits another RLC SDU (SDU2) of size AM_7_PayloadSize + 1 bytes, and includes piggy-backed status in the second of the 2 PDUs sent. The SS also polls the receiver for status.

d) 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).

e) 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 +poll + Padding
4			UPLINK RLC PDU	No LI
5			UPLINK RLC PDU	Poll, Check LIs and re-assembled SDU
5a			STATUS PDU	If piggy-backed status is not used in 5
6			DOWNLINK RLC PDU	SDU 2
7			DOWNLINK RLC PDU	SDU 2 + poll + piggy-backed status
8			UPLINK RLC PDU	No LI
9			UPLINK RLC PDU	Poll, Check LIs and re-assembled SDU
9a			STATUS PDU	If piggy-backed status is not used in 9
10			STATUS PDU
11			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.3.3.5 Test requirements

1. In steps 4 and 5, the UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second shall have a "Length Indicator" indicating the PDU contains an SDU boundary after octet 1 of the data field, and the second shall indicate either that the remainder of the PDU contains padding, or that it contains a piggy-backed status PDU.

2. In steps 8 and 9, the UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second shall have a "Length Indicator" indicating the PDU contains an SDU boundary after octet 1 of the data field, and the second shall indicate either that the remainder of the PDU contains padding, or that it contains a piggy-backed status PDU.

3. The length and data content of all received SDUs shall be the same as the transmitted SDUs.

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

7.2.3.4.1 Definition

The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. A pre-defined "Length Indicator" value is used to indicate when an SDUs 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.3.4.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.

[…]

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.3.2.1.

7.2.3.4.3 Test purpose

1. To test that where an SDU exactly fills a PDU, an "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 SDU.

7.2.3.4.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 AM_7_PayloadSize bytes.

Test procedure

a) The SS transmits an RLC SDU of size 2 * AM_7_PayloadSize bytes. The SS polls the receiver for status in the last RLC PDU sent.

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 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, poll and padding
5			UPLINK RLC PDU	No Lis
6			UPLINK RLC PDU	(Poll) Check Lis and re-assembled SDU
6a			STATUS PDU	If piggy-backed status is not used in 6
7			STATUS PDU
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.3.4.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 that the SDU exactly filled the previous PDU, and a "Length Indicator" indicating either that the remainder of the PDU contains padding, or that it contains a piggy-backed STATUS PDU.

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

7.2.3.5 Reassembly / 7-bit "Length Indicators" / Reserved LI value

7.2.3.5.1 Definition

The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. "Length Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of a reserved "Length Indicator" value is specified in the conformance requirement below. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate.

7.2.3.5.2 Conformance requirement

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

– ignore that AMD PDU.

[…]

Length: 7 bits

Bit	Description
1111100	UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol).
1111101	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.3.4.6.

7.2.3.5.3 Test purpose

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

7.2.3.5.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Downlink RLC
Missing PDU Indicator	FALSE

These settings apply to both the uplink and downlink DTCH.

Test procedure

a) The SS transmits three concatenated RLC SDUs of size AM_7_PayloadSize + 1 bytes. In the second PDU, the SS sets the value of the first "Length Indicator" to correctly indicate the end of SDU1 and adds a second erroneous "Length Indicator" with value 1111100. In the third PDU for transmission, the SS sets the value of the "Length Indicator" to 1111101.

b) The SS waits to receive a status report 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 #0	SDU 1
3			DOWNLINK RLC PDU #1	SDU 1 + SDU 2, good LI, LI = 1111100
4			DOWNLINK RLC PDU #2	SDU 2 + SDU 3, LI = 1111101
5			DOWNLINK RLC PDU #3	SDU 3 + poll
6			STATUS PDU	Nack PDUs 1 and 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.3.5.5 Test requirements

1. The UE shall return a STATUS PDU indicating that PDUs with sequence numbers 1 and 2 were not received.

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

7.2.3.6.1 Definition

The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. "Length Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of an invalid "Length Indicator" value where the value is too large is specified in the conformance requirement below. Incorrect operation of segmentation, concatenation, or coding of "Length Indicator" will result in failure of the UE to communicate.

7.2.3.6.2 Conformance requirement

If the "Length Indicator" of an AMD 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 subclause 9.2.2.8, the Sender shall:

– ignore that AMD PDU.

Reference(s)

TS 25.322 clause 11.3.4.5.

7.2.3.6.3 Test purpose

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

7.2.3.6.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Downlink RLC
Missing PDU Indicator	FALSE

These settings apply to both the uplink and downlink DTCH.

Test procedure

a) The SS transmits three RLC SDUs of size AM_7_PayloadSize + 1bytes. 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 AM_7_PayloadSize (decimal).

b) The SS checks the "Length Indicator" values in the RLC PDUs returned on the uplink, and checks the content of the received STATUS PDU (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 #0	SDU 1
3			DOWNLINK RLC PDU #1	SDU 1 & SDU 2
4			DOWNLINK RLC PDU #2	SDU 2 & SDU 3, with bad LI
5			DOWNLINK RLC PDU #3	SDU 3, poll and padding
6			STATUS PDU	Nack PDU #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.3.6.5 Test requirements

The UE shall return a STATUS PDU indicating that the PDU with sequence number 2 was not received.

7.2.3.7 Segmentation and Reassembly / 15-bit "Length Indicators" / Padding or Piggy-backed Status

7.2.3.7.1 Definition

The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. "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.3.7.2 Conformance requirement

The "Length Indicator" is used to indicate, each time, the end of an SDU occurs in the PU. The "Length Indicator" points out the number of octets between the end of the last "Length Indicator" field and up to and including the octet at the end of an SDU segment

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 LIs. A padding "Length Indicator" must be placed after any "Length Indicators" for a PDU.

Upon reception of a SDU, RLC shall segment the SDU to fit into the fixed size of a PDU. The segments are inserted in the data field of a PDU. A "Length Indicator" shall be added to each PDU that includes a border of an SDU, i.e. if a PDU does not contain a "Length Indicator", the SDU continues in the next PDU. The length indicator indicates where the border occurs in the PDU. The data after the indicated border can be either a new SDU, padding or piggybacked information. If padding or piggybacking is added another "Length Indicator" shall be added unless the padding size is one octet for PDUs with 15-bit "Length Indicators", see clauses 9.2.2.8 and 9.2.2.9.

Reference(s)

TS 25.322 clauses 9.2.2.8 and 11.3.2.1.2.

7.2.3.7.3 Test purpose

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

2. To test that a large SDU is received correctly, whether or not it has piggy-backed status at the end.

7.2.3.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 AM_15_PayloadSize + 1bytes.

Test procedure

a) The SS transmits an RLC SDU (SDU1) of size AM_15_PayloadSize + 1 bytes, and polls the receiver for status.

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 transmits another RLC SDU (SDU2) of size AM_15_PayloadSize + 1 bytes, and includes piggy-backed status in the second of the 2 PDUs sent. The SS also polls the receiver for status.

d) 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).

e) 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 +poll + Padding
4			UPLINK RLC PDU	No LI
5			UPLINK RLC PDU	Poll, Check LIs and re-assembled SDU
5a			STATUS PDU	If piggy-backed status is not used in 5
6			DOWNLINK RLC PDU	SDU 2
7			DOWNLINK RLC PDU	SDU 2 + poll + piggy-backed status
8			UPLINK RLC PDU	No LI
9			UPLINK RLC PDU	Poll, Check LIs and re-assembled SDU
9a			STATUS PDU	If piggy-backed status is not used in 9
10			STATUS PDU
11			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.3.7.5 Test requirements

1. In steps 4 and 5, the UE shall return two RLC PDUs. The first shall not include any "Length Indicators". The second shall have a "Length Indicator" indicating the PDU contains an SDU boundary after octet 1 of the data field, and the second shall indicate either that the remainder of the PDU contains padding, or that it contains a piggy-backed status PDU.

2. In steps 8 and 9, the UE shall return two RLC PDUs. The first shall not include any "Length Indicators". The second shall have a "Length Indicator" indicating the PDU contains an SDU boundary after octet 1 of the data field, and the second shall indicate either that the remainder of the PDU contains padding, or that it contains a piggy-backed status PDU.

3. The length and data content of all received SDUs shall be the same as the transmitted SDUs.

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

7.2.3.8.1 Definition

The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. 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.3.8.2 Conformance requirement

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

Reference(s)

TS 25.322 clause 11.3.2.1.

7.2.3.8.3 Test purpose

1. To test that where an 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 a "Length Indicator" of all 0’s is the first "Length Indicator" in the next PDU, the receiver correctly reassembles the SDU.

7.2.3.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 AM_15_PayloadSize bytes.

Test procedure

a) The SS transmits an RLC SDU of size 2 * AM_15_PayloadSize bytes. The SS polls the receiver for status in the last RLC PDU sent.

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, poll and padding
5			UPLINK RLC PDU	No Lis
6			UPLINK RLC PDU	(Poll) Check Lis and re-assembled SDU
6a			STATUS PDU	If piggy-backed status is not used in 6
7			STATUS PDU
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.3.8.5 Test requirements

The UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second shall have a "Length Indicator" indicating that the SDU exactly filled the previous PDU, and a "Length Indicator" indicating either that the remainder of the PDU contains padding, or that it contains a piggy-backed STATUS PDU.

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

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

7.2.3.9.1 Definition

The RLC segments and concatenates SDUs into AMD PDUs according to the PDU size configured by RRC. A pre-defined "Length Indicator" value is used to indicate when an SDUs ends one octet short of 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.3.9.2 Conformance requirement

In the case where the last segment of an RLC SDU is one octet short of exactly filling the last RLC PU, 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.3.9.3 Test purpose

1. To test that where the UE transmits an SDU, which is one byte short of filling a PDU, a "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 a "Length Indicator" indicating that an SDU ended one byte short of the end of the previous PDU.

7.2.3.9.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 AM_15_PayloadSize – 1bytes.

Test procedure

a) The SS transmits an RLC SDU of size (2 * AM_15_PayloadSize) – 1 bytes. The SS polls the receiver for status in the last RLC PDU sent.

b) The SS checks the "Length Indicator" values of 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, poll and padding
5			UPLINK RLC PDU	No LIs
6			UPLINK RLC PDU	(Poll) Check LIs and re-assembled SDU
6a			STATUS PDU	If piggy-backed status is not used in 6
7			STATUS PDU
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.3.9.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 an "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 AM_15_PayloadSize – 1 bytes, and the data content shall be the same as the first AM_15_PayloadSize – 1 bytes of the transmitted SDU.

7.2.3.10 Reassembly / 15-bit "Length Indicators" / Reserved LI value

7.2.3.10.1 Definition

The RLC segments and concatenates SDUs into AMD PDU according to the PDU size configured by RRC. "Length Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of a reserved LI 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.3.10.2 Conformance requirement

Upon reception of an AMD PDU that contains "Length Indicator" value "111111111111100" or "111111111111101": PDUs with this coding will be discarded by this version of the protocol.

Reference(s)

TS 25.322 clause 9.2.2.8.

7.2.3.10.3 Test purpose

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

7.2.3.10.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Downlink RLC
Missing PDU Indicator	FALSE

These settings apply to both the uplink and downlink DTCH.

Test procedure

a) The SS transmits three RLC SDUs of size AM_15_PayloadSize + 1 bytes. In the second PDU, the SS sets the value of the "Length Indicator" to 111111111111100. In the third PDU for transmission, the SS sets the value of the second (padding) "Length Indicator" to 111111111111101.

b) The SS waits to receive a status report 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 #0	SDU 1
3			DOWNLINK RLC PDU #1	SDU 1 + SDU 2, LI = 111111111111100
4			DOWNLINK RLC PDU #2	SDU 2+ SDU 3, LI = 111111111111101
5			DOWNLINK RLC PDU #3	SDU 3 + poll
6			STATUS PDU	Nack PDUs 1 and 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.3.10.5 Test requirements

1. The UE shall return a STATUS PDU indicating that PDUs with sequence numbers 1 and 2 were incorrectly received.

2. No uplink SDUs shall be received.

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

7.2.3.11.1 Definition

The RLC segments and concatenates SDUs into PDUs according to the PDU size configured by RRC. "Length Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of an invalid LI 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.3.11.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.

Reference(s)

TS 25.322 clause 11.3.4.5.

7.2.3.11.3 Test purpose

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

7.2.3.11.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Downlink RLC
Missing PDU Indicator	FALSE

These settings apply to both the uplink and downlink DTCH.

Test procedure

a) The SS transmits three RLC SDUs of size AM_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 Indicators" to be AM_15_PayloadSize + 1 (decimal).

b) The SS checks the "Length Indicator" values of the RLC PDUs returned on the uplink, and checks the content of the received STATUS PDUs (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 #0	SDU 1
3			DOWNLINK RLC PDU #1	SDU 1 & SDU 2
4			DOWNLINK RLC PDU #2	SDU 2 & SDU 3, with bad LI
5			DOWNLINK RLC PDU #4	SDU 3, poll and padding
6			STATUS PDU	Nack PDU #2
7			RB RELEASE	Optional step

7.2.3.11.5 Test requirements

The UE shall indicate that the PDU with sequence number 2 was not received.

7.2.3.12 Correct use of Sequence Numbering

7.2.3.12.1 Definition

Peer RLC entities use sequence numbering to detect missing PDUs, and for flow control purposes. Incorrect operation of sequence numbering will result in failure of the UE to communicate.

7.2.3.12.2 Conformance requirement

This sub-clause describes the state variables used in AM and UM in order to specify the peer-to-peer protocol. All state variables are non-negative integers. UMD and AMD PDUs are numbered by modulo integer sequence numbers (SN) cycling through the field: 0 to 212 – 1 for AM … . All arithmetic operations contained in the present document on VT(S), VT(A), VT(MS), VR(R), VR(H) and VR(MR) are affected by the AM modulus. … . When performing arithmetic comparisons of state variables or Sequence number values a modulus base shall be used. This modulus base is subtracted (within the appropriate field) from all the values involved and then an absolute comparison is performed. At the Sender, VT(A) … shall be assumed to be the modulus base in AM … . At the Receiver, VR(R) … shall be assumed to be the modulus base in AM … .

The RLC shall maintain the following state variables in the Sender.

a) VT(S) – Send state variable.

This state variable contains the "Sequence Number" of the next AMD PDU to be transmitted for the first time (i.e. excluding retransmitted PDUs). It shall be updated after the aforementioned AMD PDU is transmitted or after transmission of a MRW SUFI which includes SN_MRW_LENGTH >VT(S) (see subclause 11.6). The initial value of this variable is 0.

[…]

If the AMD PDU is transmitted for the first time, the Sender shall:

– set the "Sequence Number" field equal to VT(S);

Reference(s)

TS 25.322, clauses 9.4 and 11.3.2.1.

7.2.3.12.3 Test purpose

1. To verify that the UE transmits the first PDU with the Sequence Number field equal to 0.

2. To verify that the UE increments the Sequence Number field according to the number of PDUs transmitted.

3. To verify that the UE wraps the Sequence Number after transmitting the 2¹²-1th PDU.

4. To verify that the UE receiver accepts PDUs with SNs that wrap around every 2¹²-1th PDU.

7.2.3.12.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 AM 7-bit "Length Indicator" tests in clause 7.2.3.1.

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Polling info
Poll_PDU	64
Transmission window size	128
Downlink RLC
Receiving window size	128

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) – 1 bytes.

Test procedure

a) The SS sends 2049 RLC SDUs to the UE, each of (2 * AM_7_PayloadSize) – 1 bytes. The SS polls for status on each 64^th RLC PDU and the last PDU transmitted

b) When the SS received an uplink PDU with the P bit set to 1, the SS transmits a STATUS PDU acknowledging all the RLC PDUs received so far.

c) The SS checks the sequence numbers of the RLC PDUs it receives in the uplink

d) The SS checks the content of the SDUs it receives from the UE.

e) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU #1
3			DOWNLINK RLC PDU #2
			…	Transmission of DOWNLINK PDUs continues
4			UPLINK RLC PDU#1	SN should be set to 0
5			UPLINK RLC PDU#2	SN should be set to 1
			…	Transmission of DOWNLINK PDUs continues to SN = 63
6			DOWNLINK RLC PDU #64	Poll
7			UPLINK STATUS PDU
			…	Transmission of DOWNLINK PDUs continues, polling every 64^th PDU, to SN = 4094
8			DOWNLINK RLC PDU #4096
9			DOWNLINK RLC PDU #4097	SN=0
10			DOWNLINK RLC PDU #4098	SN=1, Poll
10a			UPLINK RLC PDUs	UE transmission of UPLINK RLC PDUs continues, polling every 64^th PDU, to SN=4094. On poll, SS acknowledge all received PDUs.
10b			Void
10c			UPLINK RLC PDU#4096	SN = 4095, Poll (cause: Poll_PDU=64)
10d			STATUS PDU	ACK SN up to 4095
10e			Void
11			Void
12			UPLINK RLC PDU#4097	SN should be set to 0
13			UPLINK RLC PDU#4098	SN should be set to 1, Poll
14			DOWNLINK STATUS PDU
15			RB RELEASE	Optional step
NOTE: 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.3.12.5 Test requirements

1. The first PDU received shall have the SN field set to 0. The second PDU shall have the SN field set to 1, and the 4 097^th PDU shall have the SN field set to 0.

2. The size and data content of the received SDUs shall match those of the transmitted SDUs.

7.2.3.13 Control of Transmit Window

7.2.3.13.1 Definition

This test is to check that the UE is able to correctly control its RLC transmission window. Correct operation of RLC windowing is critical for acknowledged mode operation.

7.2.3.13.2 Conformance requirement

VT(MS) – Maximum Send state variable.

This state variable contains the "Sequence Number" of the first AMD PDU that can be rejected by the peer Receiver, VT(MS) = VT(A) + VT(WS). This value represents the upper edge of the transmission window. The transmitter shall not transmit AMD PDUs with "Sequence Number"VT(MS) unless VT(S)  VT(MS). In that case, the AMD PDU with "Sequence Number" = VT(S) – 1 can also be transmitted. VT(MS) shall be updated when VT(A) or VT(WS) is updated.

The initial value of this variable is Configured_Tx_Window_size.

… The receiver is always allowed to change the Tx window size of the peer entity during a connection, but the minimum and the maximum allowed value is given by RRC configuration. The Rx window of the receiver is not changed.

Reference(s)

TS 25.322, clauses 9.2.2.11.3 and 9.4.

7.2.3.13.3 Test purpose

To verify that the UE does not transmit PDUs with sequence numbers outside of the transmit window, except the PDU with SN=VT(S)-1, even when the transmit window size is changed by the receiver.

7.2.3.13.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC	First run	Second run
Transmission window size	16	128

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Related IXIT statement

UE support for either RLC SDU Buffering OR RLC SDU Discard.

Test procedure

Let W be the size of the transmit window.

The length of all transmitted SDUs is set to AM_7_PayloadSize – 1 bytes.

a) The SS transmits W+1 RLC SDUs to the UE.

b) The SS checks the RLC SDUs received on the uplink, but does not reply to poll requests from the UE, or transmit STATUS PDUs for any other reason.

c) After confirming that the UE has stopped transmitting new RLC SDUs for at least (2*W*TTI) ms, the SS transmits a STATUS PDU acknowledging all the RLC PDUs received so far. The SS transmits W+1 additional RLC SDUs to the UE.

d) The SS again checks the RLC SDUs received on the uplink, but does not reply to poll requests from the UE, or transmit further STATUS PDUs for any other reason.

e) After confirming that the UE has again stopped transmitting new RLC SDUs for at least (2*W*TTI) ms, the SS transmits a STATUS PDU acknowledging all the RLC PDUs received so far, and containing a WINDOW command to reduce the UE transmit window size (W) to half its initial size. The SS transmits W/2+1 additional RLC SDUs to the UE (where W is the original window size).

f) The SS checks the RLC SDUs received on the uplink, but does not reply to poll requests from the UE, or transmit STATUS PDUs for any other reason.

g) After confirming that the UE has stopped transmitting new RLC SDUs for at least (2*W*TTI) ms, the SS transmits a STATUS PDU acknowledging all the RLC PDUs received so far. The SS transmits W/2+1 additional RLC SDUs to the UE (where W is the original window size).

h) The SS checks the RLC SDUs received on the uplink.

i) The SS may optionally release the radio bearer.

NOTE: Window arithmetic is carried out modulo 4096.

The test procedure is run with the window transmit window size set to 16, and the repeated with the transmit window size set to 128.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 2
4			DOWNLINK RLC PDU	SDU 3
5			DOWNLINK RLC PDU	SDU 4
6			…	SS continues to transmit RLC SDUs
7			DOWNLINK RLC PDU	SDU W+1

8			UPLINK RLC PDU	SDU 1
9			UPLINK RLC PDU	SDU 2
10			…	SS continues to receive RLC SDUs
11			UPLINK RLC PDU	SDU W + poll
12				No new transmissions from UE
13			STATUS PDU
13a			DOWNLINK RLC PDUs	SDU W+2
13b			…	SS continues to transmit RLC SDUs
13c			DOWNLINK RLC PDUs	SDU 2W+2
14			UPLINK RLC PDU	SDU W+1 (SDU buffered), or W+2 (SDU W+1 discarded, see note 3)
15			UPLINK RLC PDU	Next SDU
16			…	SS continues to receive RLC SDUs
17			UPLINK RLC PDU	SDU 2W+poll (SDU buffered), or SDU 2W+1+poll (SDU W+1 discarded, see note 3)
18				No new transmissions from UE
19			STATUS PDU	WINDOW = W/2
19a			DOWNLINK RLC PDUs	SDU 2W+3
19b			…	SS continues to transmit RLC SDUs
19c			DOWNLINK RLC PDUs	SDU 2W + W/2 + 3
20			UPLINK RLC PDU	SDU 2W+1 (SDU buffered), or 2W+3 (SDU 2W+2 discarded, see note 3)
21			UPLINK RLC PDU	Next SDU
22			…	SS continues to receive RLC SDUs
23			UPLINK RLC PDU	SDU 2W+W/2+poll (SDU buffered), or SDU 2W+W/2+2+poll (SDU 2W+2 discarded, see note 3)
24				No new transmissions from UE
25			STATUS PDU
25a			DOWNLINK RLC PDUs	SDU 2W + W/2 + 4
25b			…	SS continues to transmit RLC SDUs
25c			DOWNLINK RLC PDUs	SDU 3W + 4
26			UPLINK RLC PDU	SDU 2W+W/2+1 (SDU buffered), or 2W+W/2+4 (SDU 2W+W/2+3 discarded, see note 3)
27			UPLINK RLC PDU	Next SDU
28			…	SS continues to receive RLC SDUs
29			UPLINK RLC PDU	SDU 3W+poll (SDU buffered), or SDU 3W+3+poll (SDU 2W+W/2+3 discarded, see note 3)
30			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: The polls in step 11, 17, 23 and 29 are transmitted as the last PDU in buffer trigger is set to TRUE and the transmitted PDU is the last PDU in the transmitter window, see TS 25.322 clause 9.7.1. NOTE 3: TS 25.322 does not specify the UE behaviour when transmission buffer is full. Thus, depending on UE implementation, the uplink AM entity may or may not discard AM RLC PDUs received from upper layer (e.g. from UE test loop function) when transmission buffer is full. The SS need to take this into consideration when comparing SS sent SDUs in downlink with the UE returned SDUs in uplink.

7.2.3.13.5 Test requirements

From steps 8 to 11, the SDU contents reassembled from the uplink shall match those of the first W transmitted SDUs.

At step 12 there shall be no further transmission on the uplink DTCH whilst the SS is waiting, except for any repeats of SDUs from 1 to W.

After step 13, the UE shall resume transmission of the next W SDUs. The contents of these SDUs shall match those of SDUs W+1 to 2*W (SDU buffered, see note 3), or W+2 to 2*W+1 (SDU W+1 discarded, see note 3), sent on the downlink.

At step 18 there shall be no further transmission on the uplink DTCH whilst the SS is waiting, except for any repeats of SDUs from W+1 to 2*W or W+2 to 2*W+1.

After step 19, the UE shall resume transmission of the next W/2 SDUs. The contents of these SDUs shall match those of SDUs 2*W+1 to 2*W+W/2 (SDU buffered, see note 3), or 2*W+3 to 2*W+W/2+2 (SDU 2W+2 discarded, see note 3), sent on the downlink.

At step 24 there shall be no further transmission on the uplink DTCH whilst the SS is waiting, except for any repeats of SDUs from 2*W+1 to 2*W+W/2 or 2*W+3 to 2*W+W/2+2.

After step 25, the UE shall resume transmission of the next W/2 SDUs. The contents of these SDUs shall match those of SDUs 2*W+W/2+1 to 3*W (SDU buffered, see note 3), or 2*W+W/2+4 to 3*W+3 (SDU 2W+W/2+3 discarded, see note 3), sent on the downlink.

7.2.3.14 Control of Receive Window

7.2.3.14.1 Definition

This test is to check that the UE is able to correctly control its RLC receive window. Correct operation of RLC windowing is critical for acknowledged mode operation.

This test applies to all UE.

7.2.3.14.2 Conformance requirement

Upon reception of an AMD PDU with "Sequence Number" outside the interval VR(R)SN<VR(MR), the Receiver shall:

– discard the AMD PDU;

– if the "polling bit" in the discarded AMD PDU is set to "1":

– initiate the STATUS PDU transfer procedure.

Reference(s)

TS 25.322, clause 11.3.4.2.

7.2.3.14.3 Test purpose

To verify that the UE discards PDUs with sequence numbers outside the upper boundary of the receive window.

7.2.3.14.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC	First run	Second run
Transmission window size	8	128
Downlink RLC
Missing PDU Indicator	FALSE	FALSE
Receiving window size	8	128

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Test procedure

Let W be the size of the receive window.

The length of all transmitted SDUs is set to AM_7_PayloadSize – 1 bytes.

a) The SS transmits W RLC SDUs to the UE, polling only on the last RLC PDU.

b) The SS checks the RLC SDUs received on the uplink, responding to poll requests with acknowledgements. Then after receiving the STATUS PDU from the UE it transmits a further RLC SDU with the poll bit set. The SS sets the sequence number for the associated RLC PDU above the top of the receive window, for example, 2*W.

c) The SS receives a STATUS PDU from the UE.

d) The SS transmits a further RLC SDU with the sequence number set to the value of the next sequence number within the receive window.

e) The SS checks the RLC SDUs received on the uplink.

f) The SS may optionally release the radio bearer.

This test case is run once for the default receive window size (8) and again with the receive window size set to 128.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			RB ESTABLISHMENT	See generic procedures
2			DOWNLINK RLC PDU	SDU 1, SN = 0
3			DOWNLINK RLC PDU	SDU 2, SN = 1
4			…	SS continues to transmit RLC SDUs
5			DOWNLINK RLC PDU	SDU W + Poll, SN = W-1
6			STATUS PDU
7			UPLINK RLC PDU	SDU 1
8			UPLINK RLC PDU	SDU 2
9			…	UE continues to transmit RLC SDUs
10			UPLINK RLC PDU	SDU W, Poll
10a			STATUS PDU
11			DOWNLINK RLC PDU	SDU W+1, SN = 2W, Poll
11a			STATUS PDU
12			DOWNLINK RLC PDU	SDU W+2, SN = W
13			UPLINK RLC PDU	SDU W+2
14			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.3.14.5 Test requirements

1. The SS shall receive back SDUs 1 to W, and SDU W + 2 only. No other SDUs shall be looped back.

2. The SS shall receive a STATUS PDU in step 11a. SN=2W shall not be indicated as received in the STATUS PDU. Negative acknowledgements shall not be indicated for SN=W to 2W-1 either.

7.2.3.15 Polling for status / Last PDU in transmission queue

7.2.3.15.1 Definition

This case tests that the UE will poll for a status request on the last PDU in its transmission queue when that mode is enabled. Incorrect operation of polling will cause degradation of service, or at worst service failure.

7.2.3.15.2 Conformance requirement

Last PDU in buffer.

When an AMD PDU to be transmitted for the first time is submitted to lower layer, the Sender shall:

– if the AMD PDU is the last AMD PDU scheduled for transmission according to subclause 11.3.2 (i.e. no data received from upper layer remains to be segmented into AMD PDUs); or

– if the AMD PDU is the last AMD PDU that is allowed to transmit according to subclause 11.3.2.2:

– trigger a poll for this AMD PDU

….

– AMD PDUs are only allowed to transmit:

– if the AMD PDU has a "Sequence Number" < VT(MS); or

– if the AMD PDU has a "Sequence Number" equal to VT(S)-1; and

– if the AMD PDU is not restricted to be transmitted by the local suspend function, see 3GPP TS 25.322 subclause 9.7.5.

…

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see 3GPP TS 25.322 subclause 9.7.1):

– if polling is not prohibited, see subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

TS 25.322 clause 11.3.2.1.1, 9.7.1 and 11.3.2.

7.2.3.15.3 Test purpose

1. To verify that a poll is performed when only one PDU is available for transmission, and the poll prohibit timer function is not used.

2. To verify that a poll is performed when only one PDU is available for transmission, and the poll prohibit timer function is used, but inactive.

7.2.3.15.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC	First run	Second run
Polling info
Timer_poll_prohibit	disabled	200
Last transmission PDU poll	TRUE	TRUE
Last retransmission PDU poll	FALSE	FALSE

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) – 1 bytes.

Test procedure

a) The SS transmits an RLC SDU of length (4 * AM_7_PayloadSize) – 1bytes to the UE.

b) The SS checks the uplink RLC PDUs for a poll for status flag.

c) The SS may optionally release the radio bearer.

The test is repeated using the RLC parameters given in the Second run column of the configuration table for the initial conditions.

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	SDU 1
5			DOWNLINK RLC PDU	SDU 1 + Poll
6			STATUS PDU
7			UPLINK RLC PDU	SDU 1
8			UPLINK RLC PDU	SDU 1 + Poll
9			STATUS PDU
10			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.3.15.5 Test requirements

The Poll bit shall be set in the AMD PDU header of the PDU returned in step 8. The poll bit shall not be set in the AMD PDU header of other PDUs.

7.2.3.16 Polling for status / Last PDU in retransmission queue

7.2.3.16.1 Definition

This case tests that the UE will poll for a status request on the last PDU in its retransmission queue when that mode is enabled. Incorrect operation of polling will cause degradation of service, or at worst service failure.

7.2.3.16.2 Conformance requirement

Last PDU in Retransmission buffer.

When a retransmitted AMD PDU is submitted to lower layer, the Sender shall:

– if the AMD PDU is the last AMD PDU scheduled for retransmission according to subclause 11.3.2; or

– if the AMD PDU is the last of the AMD PDUs scheduled for retransmission that are allowed to transmit according to subclause 11.3.2.2:

– trigger a poll for this AMD PDU

….

– AMD PDUs are only allowed to transmit:

– if the AMD PDU has a "Sequence Number" < VT(MS); or

– if the AMD PDU has a "Sequence Number" equal to VT(S)-1; and

– if the AMD PDU is not restricted to be transmitted by the local suspend function, see 3GPP TS 25.322 subclause 9.7.5.

…

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see 3GPP TS 25.322 subclause 9.7.1):

– if polling is not prohibited, see subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

25.322 clause 11.3.2.1.1, 9.7.1 and 11.3.2.

7.2.3.16.3 Test purpose

1. To verify that a poll is performed when only one PDU is available for retransmission, and the poll prohibit timer function is not used.

2. To verify that a poll is performed when only one PDU is available for retransmission, and the poll prohibit timer function is used, but inactive.

7.2.3.16.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC	First run	Second run
Polling info
Timer_poll_prohibit	disabled	200
Last transmission PDU poll	FALSE	FALSE
Last retransmission PDU poll	TRUE	TRUE

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) – 1 bytes.

Test procedure

a) The SS transmits an RLC SDU of length (4 * AM_7_PayloadSize) – 1 bytes to the UE.

b) The SS checks the uplink RLC PDUs for a poll for status flag.

c) The SS transmits a STATUS PDU negatively acknowledging the first uplink RLC PDU as missing.

d) The SS waits for the RLC PDU to be retransmitted and then checks the uplink RLC PDU for a poll for status flag.

e) The SS may optionally release the radio bearer.

The test is repeated using the RLC parameters given in the Second run column of the configuration table for the initial conditions.

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	SDU 1
5			DOWNLINK RLC PDU	SDU 1 + Poll
6			STATUS PDU
7			UPLINK RLC PDU	SDU 1, SN=0
8			UPLINK RLC PDU	SDU 1, SN=1
9			STATUS PDU	NAK: SN=0
10	…			Wait for retransmission
11			UPLINK RLC PDU	SDU 1, SN=0 + Poll
12			STATUS PDU
13			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.3.16.5 Test requirements

The Poll bit shall be set in the AMD PDU header of the PDU returned in step 11. The poll bit shall not be set in the AMD PDU header of other PDUs.

7.2.3.17 Polling for status / Poll every Poll_PDU PDUs

7.2.3.17.1 Definition

This case tests that the UE will poll for a status request every Poll_PDU PDUs when that mode is enabled. Incorrect operation of polling will cause degradation of service, or at worst service failure.

7.2.3.17.2 Conformance requirement

VT(PDU).

This state variable is used when the "poll every Poll_PDU PDU" polling trigger is configured. It shall be incremented by 1 for each AMD PDU that is transmitted including both new and retransmitted AMD PDUs. When it becomes equal to the value Poll_PDU, a new poll shall be transmitted and the state variable shall be set to zero.

The initial value of this variable is 0.

Poll_PDU.

This protocol parameter indicates how often the transmitter shall poll the Receiver in the case where "polling every Poll_PDU PDU" is configured by upper layers. It represents the upper limit for the state variable VT(PDU). When VT(PDU) equals the value Poll_PDU a poll shall be transmitted to the peer entity.

Every Poll_PDU PDU.

The Sender triggers the Polling function for every Poll_PDU PDU. Both retransmitted and new AMD PDUs shall be counted.

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see subclause 9.7.1):

– if polling is not prohibited, see subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

TS 25.322 clauses 9.4, 9.6, 11.3.2.1.1 and 9.7.1.

7.2.3.17.3 Test purpose

1. To verify that a poll is performed when VT(PDU) reaches Poll_PDU.

2. To verify VT(PDU) is incremented for both new and retransmitted PDUs.

7.2.3.17.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Polling info
Poll_PDU	4
Last transmission PDU poll	FALSE
Last retransmission PDU poll	FALSE

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Test procedure

Let the value of Poll_PDU be P:

a) The SS sends 3 * P – 2 RLC SDUs of size AM_7_PayloadSize – 1 bytes to the UE in PDUs with sequence numbers that are contiguous, starting from zero.

b) The SS checks the sequence numbers and polling bits of the RLC PDUs returned on the uplink.

c) The SS sends a STATUS PDU negatively acknowledging two RLC PDUs with a sequence numbers of already received PDUs. The other PDUs are acknowledged as received correctly.

d) The SS checks the sequence numbers and polling bits of the RLC SDUs returned on the uplink.

e) The SS terminates the connection.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			DOWNLINK RLC PDU	SDU 1
2			DOWNLINK RLC PDU	SDU 2
3			…	SS continues to transmit RLC SDUs
4			DOWNLINK RLC PDU	SDU 3P – 2

5			UPLINK RLC PDU	SDU 1, SN=0
6			UPLINK RLC PDU	SDU 2, SN=1
7			…	SS continues to receive RLC SDUs
8			UPLINK RLC PDU	SDU P, Poll
9			STATUS PDU	NAK SN=0 and SN=1
10			UPLINK RLC PDU	SDU 1, SN=0
11			UPLINK RLC PDU	SDU 2, SN=1
12			UPLINK RLC PDU	SDU P+1
13			…	SS continues to receive RLC SDUs
14			UPLINK RLC PDU	SDU 2P – 2, Poll
15			…	SS continues to receive RLC SDUs
16			UPLINK RLC PDU	SDU 3P – 2, Poll
17			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: Due to retransmissions it is not possible to determine the exact PDU that a poll is received on. i.e. A poll may be received on a retransmitted PDU or a PDU transmitted for the first time.

7.2.3.17.5 Test requirements

The SS shall receive a poll for status every Poll_PDU RLC PDUs sent on the uplink.

7.2.3.18 Polling for status / Poll every Poll_SDU SDUs

7.2.3.18.1 Definition

This case tests that the UE will poll for a status request every Poll_SDU SDUs when that mode is enabled. Incorrect operation of polling will cause degradation of service, or at worst service failure.

7.2.3.18.2 Conformance requirement

VT(SDU).

This state variable is used when the "poll every Poll_SDU SDU" polling trigger is configured. It shall be incremented by 1 for a given SDU when the AMD PDUs carrying the first segment of this SDU is scheduled to be transmitted for the first time. When it becomes equal to the value Poll_SDU a new poll shall be transmitted and the state variable shall be set to zero. The "Polling bit" shall be set to "1" in the first transmission of the AMD PDU that contains the “Length Indicator” indicating the end of the SDU.

The initial value of this variable is 0.

Poll_SDU.

This protocol parameter indicates how often the transmitter shall poll the Receiver in the case where "polling every Poll_SDU SDU" is configured by upper layers. It represents the upper limit for state variable VT(SDU). When VT(SDU) equals the value Poll_SDU a poll shall be transmitted to the peer entity.

Every Poll_SDU SDU.

The Sender triggers the Polling function for every Poll_SDU SDU. The poll shall be triggered for the first transmission of the AMD PDU that contains the “Length Indicator” indicating the end of the SDU.

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see TS 25.322 subclause 9.7.1):

– if polling is not prohibited, see TS 25.322 subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

TS 25.322 clauses 9. 4, 9.6, 9.7.1 and 11.3.2.1.1.

7.2.3.18.3 Test purpose

1. To verify that a poll is performed when VT(SDU) reaches Poll_ SDU.

2. To verify that the poll is sent in the last PDU of the SDU.

7.2.3.18.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 AM 7-bit "Length Indicator" tests in clause 7.2.3.1.

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Polling info
Last transmission PDU poll	FALSE
Poll_SDU	1

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) – 1 bytes.

Let the value of Poll_SDU be P.

a) The SS sends 2 * P RLC SDUs of size AM_7_PayloadSize – 1 bytes to the UE in PDUs with sequence numbers that are contiguous, starting from zero.

b) The SS checks the sequence numbers and polling bits of the RLC SDUs returned on the uplink.

c) The SS terminates the connection.

The test is repeated with Poll_SDU set to 16.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1
2			DOWNLINK RLC PDU	SDU 2
3			…	SS continues to transmit RLC SDUs
4			DOWNLINK RLC PDU	SDU 2P

5			UPLINK RLC PDU	SDU 1 Expanded to (2 * AM_7_PayloadSize) – 1 bytes by test function
6			UPLINK RLC PDU
7			…	SS continues to receive RLC SDUs
8			UPLINK RLC PDU	SDU P, Poll
9			STATUS PDU
10			UPLINK RLC PDU	SDU P+1 Expanded to (2 * AM_7_PayloadSize) – 1 bytes by test function
11			UPLINK RLC PDU
12			…	SS continues to receive RLC SDUs
13			UPLINK RLC PDU	SDU 2P, Poll
14			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.3.18.5 Test requirements

The UE shall return uplink PDUs that contain polls for status in sequence numbers 2 * P – 1 and 4 * P – 1. No other PDUs shall poll for status.

7.2.3.19 Polling for status / Timer triggered polling (Timer_Poll_Periodic)

7.2.3.19.1 Definition

This case tests that the UE will poll for a status request every Timer_Poll_Periodic ms when that mode is enabled. Incorrect operation of polling will cause degradation of service, or at worst service failure.

7.2.3.19.2 Conformance requirement

This timer shall only be used when "timer based polling" is configured by upper layers. The value of the timer is signalled by upper layers. The timer shall be started when the RLC entity is created. When the timer expires, the RLC entity shall:

– restart the timer;

– if AMD PDUs are available for transmission or retransmission (not yet acknowledged):

– trigger a poll.

[…]

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see TS 25.322 subclause 9.7.1):

– if polling is not prohibited, see TS 25.322 subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

TS 25.322 clauses 9.5, 9.7.1 and 11.3.2.1.1.

7.2.3.19.3 Test purpose

1. To verify that the UE polls the SS in the next PDU to be transmitted or retransmitted each time the Timer_Poll_Periodic timer expires.

2. To verify that if there is no PDU to be transmitted or retransmitted, the timer is restarted, but no poll is sent.

7.2.3.19.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC	First run	Second run
Polling info
Last retransmission PDU poll	FALSE	FALSE
Last transmission PDU poll	FALSE	FALSE
Timer_poll_periodic	500	2000

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (AM_7_PayloadSize * ceil(T/(5*TTI))) – 1 bytes.

Test procedure

Let T be the value of Timer_Poll_Periodic:

a) The SS waits for at least 2*T ms before starting any transmissions, and monitors the uplink.

b) The SS sends five RLC SDUs of size floor (AM_7_PayloadSize/5) – 1 bytes to the UE. The SDUs are concatenated five SDUs to one PDU. The UE is expected to loop this data back in five RLC SDUs, segmented into a total of at least ceil(T/TTI) RLC PDUs.

c) The SS checks that at least one RLC PDU is received on the uplink with the P bit set and records the arrival time of the last RLC PDU received with the P bit set (T₁) . The SS does not send any STATUS PDUs in response to these poll requests.

d) The SS continues to receive RLC PDUs until all of the data has been received.

e) The SS waits for the UE to retransmit an RLC PDU in order to transmit a poll (this may be the PDU with SN VT(S) – 1, or a PDU that has not been acknowledged). The SS checks that the P bit is set, and records the arrival time (T₂).

f) The SS responds with a STATUS PDU acknowledging all received PDUs.

g) The SS waits for 2*T ms to ensure that no further polls are received from the UE.

h) Void

i) The SS may optionally release the radio bearer.

The Test is repeated using the parameters specified for the second run.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1, SDU2, SDU 3, SDU 4, SDU 5, SN=0
2			UPLINK RLC PDU	PDU 1, SN=0
3			UPLINK RLC PDU	PDU 2, SN=1
4			–	SS continues to receive RLC PDUs
5			UPLINK RLC PDU	Poll: Note T₁
6			–	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SN = ceil(T/TTI) – 1
8			UPLINK RLC PDU	Retransmission of VT(S)-1 or unacknowledged PDU in order to transmit a poll. Poll: Note T₂.
9			STATUS PDU	Normal
10	–		–	SS monitors uplink for 2*T ms
11			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.3.19.5 Test requirements

1. No PDUs shall be received from the UE for 2*T ms before step 1.

2. Time T₂– T₁ shall be T.

3. No PDUs shall be received from the UE for 2*T ms after step 9.

7.2.3.20 Polling for status / Polling on Poll_Window% of transmission window

7.2.3.20.1 Definition

This case tests that the UE will poll for a status request when it has reached Poll_Window% of the transmission window, when that mode is enabled. Incorrect operation of polling will cause degradation of service, or at worst service failure.

This test applies to all UE.

7.2.3.20.2 Conformance requirement

1. A poll is triggered for each AMD PDU when JPoll_Window, where J is the window transmission percentage defined by

where the constant 4096 is the modulus for AM described in 3GPP TS 25.322 subclause 9.4 and VT(S) is the value of the variable before the AMD PDU is submitted to lower layer.

2. The Polling function is used by the Sender to request the peer RLC entity for a status report. The "Polling bit" in the AMD PDU indicates the poll request. There are several triggers for initiating the Polling function. Which of the triggers shall be used is configured by upper layers for each RLC entity. The following triggers can be configured:

…….

6) Window based.

The Sender triggers the Polling function when the condition described in subclause 9.6 d) ("Poll_Window") is fulfilled.

3. The Sender shall:

– if a poll has been triggered by one or several poll triggers (see subclause 9.7.1):

– if polling is not prohibited, see subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1".

Reference

25.322 clauses 9.6, 9.7.1 and 11.3.2.1.1.

7.2.3.20.3 Test purpose

To verify that the UE polls the SS when the window based polling condition J >= Poll_Window is fulfilled.

7.2.3.20.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Polling info
Last transmission PDU poll	FALSE
Poll_Window	50
Transmission window size	8
Downlink RLC
Receiving window size	8

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Test procedure

Let W be the size of the transmission window.

a) The SS transmits (W/2) + 2 RLC SDUs of size AM_7_PayloadSize – 1 bytes.

b) The SS checks the sequence number of the first three uplink PDUs received with the P bit set.

c) The SS sends another RLC SDU of size AM_7_PayloadSize – 1 bytes.

d) The SS checks the sequence number of the next uplink PDU received with the P bit set.

e) The SS waits until no more new PDUs are received.

f) The SS sends a STATUS PDU acknowledging the received RLC PDUs with SN = 0 through W/2, followed by two further RLC SDUs.

g) The SS checks the sequence number of the next uplink PDU received with the P bit set.

h) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			DOWNLINK RLC PDU	SDU 1
2			…	SS continues to transmit RLC SDUs
3			DOWNLINK RLC PDU	SDU W/2+2
4			UPLINK RLC PDU	SDU 1, SN=0
5			UPLINK RLC PDU	SDU 2, SN=1
6			…	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SN = W/2-1, Poll
7a			UPLINK RLC PDU	SN = W/2, Poll
7b			UPLINK RLC PDU	SN = W/2 +1, Poll
8			DOWNLINK RLC PDU	SDU W/2 + 3
9			UPLINK RLC PDU	SN = W/2 + 2, Poll
9a				SS waits 10 TTI periods to ensure no more new PDUs are received
10			STATUS PDU	ACK SN 0 to W/2 (UE sets VT(A) to W/2+1)
11			DOWNLINK RLC PDU	SDU W/2 + 4
12			DOWNLINK RLC PDU	SDU W/2 + 5
13			UPLINK RLC PDU	SN = W/2+3
14			UPLINK RLC PDU	SN = W/2+4, Poll
15			RB RELEASE	Optional step
NOTE: 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.3.20.5 Test requirements

The SS shall receive RLC PDUs with the P bit set in PDUs with sequence numbers of 3, 4, 5, 6 and 8. No other PDUs shall have their P bits set.

7.2.3.21 Polling for status / Operation of Timer_Poll timer / Timer expiry

7.2.3.21.1 Definition

This case tests that the UE will retransmit a poll for status if it does not receive a STATUS PDU within Timer_Poll ms after a poll for status is transmitted. Incorrect operation of polling will cause degradation of service, or possible service failure.

7.2.3.21.2 Conformance requirement

Timer_Poll.

This timer shall only be used when so configured by upper layers. The value of the timer is signalled by upper layers. In the UE this timer shall be started when the successful or unsuccessful transmission of an AMD PDU containing a poll is indicated by lower layer. In UTRAN it should be started when an AMD PDU containing a poll is submitted to lower layer. If x is the value of the state variable VT(S) after the poll was submitted to lower layer, the timer shall be stopped upon receiving:

– positive acknowledgements for all the AMD PDUs with "Sequence Number" up to and including x – 1; or

– a negative acknowledgement for the AMD PDU with "Sequence Number" = x – 1.

If the timer expires and no STATUS PDU fulfilling the criteria above has been received:

– the Receiver shall be polled once more;

– the timer shall be restarted; and

– the new value of VT(S) shall be saved.

If a new poll is sent when the timer is active, the timer shall be restarted at the time specified above, and the value of VT(S) shall be saved.

[…]

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see subclause 9.7.1):

– if polling is not prohibited, see subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

TS 25.322 clauses 11.3.2.1.1 and 11.3.4.1.

7.2.3.21.3 Test purpose

To verify that if the timer expires and no STATUS PDU containing an acknowledgement or negative acknowledgement of the AMD PDUs up to that which triggered the timer has been received, the receiver is polled once more.

7.2.3.21.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC	First run	Second run
Transmission window size	256	256
Polling info
Last transmission PDU poll	FALSE	FALSE
Timer_poll	600	1000
Timer_Poll_Periodic	2000	2000

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Test procedure

Let T be the value of the Timer_Poll_Periodic timer.

a) The SS transmits at least 2 * T / TTI SDUs of size AM_7_PayloadSize – 1 bytes.

b) The SS receives PDUs from the UE, and notes the time on receiving the first PDU with the P bit set, but does not respond. This time will be recorded as T_1.

c) The SS continues to receive PDUs from the UE and notes the time on receipt of the next PDU with the P bit set. This time will be recorded as T₂.

d) The SS continues to receive PDUs from the UE until all transmitted PDUs have been received. The SS responds to any PDU received with the P bit set by transmitting a STATUS PDU containing an acknowledgement of the AMD PDUs received.

e) The SS acknowledges the last Poll PDU from the UE.

f) The SS may optionally release the radio bearer.

The test case is run once for each set of initial RLC parameters.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1
2			…	SS continues to transmit RLC SDUs
3			DOWNLINK RLC PDU	SDU ceil(2T/TTI)
4			UPLINK RLC PDU	SDU 1
5			UPLINK RLC PDU	SDU 2
6			…	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SN = n , Poll: Note T₁ (First PDU with P bit set)
8			UPLINK RLC PDU	SN = n+1
9			…	SS continues to receive RLC PDUs
9a	SS			No STATUS PDUs are sent by the SS between steps 7 and 10.
10			UPLINK RLC PDU	Poll: Note T₂ (Next PDU with P bit set)
11			…	SS continues to receive PDUs, acknowledging with STATUS PDUs when polled until all PDUs have been received and acknowledged
12			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: The SN value “n” identifies the current RLC sequence number of the first UL PDU with the Poll Bit set. This value is for informative purposes only

7.2.3.21.5 Test requirements

For the first run, the measured time T₂– T₁ shall be 600 ms.

For the second run, the measured time T₂– T₁ shall be 1000 ms.

7.2.3.22 Polling for status / Operation of Timer_Poll timer / Stopping Timer_Poll timer

7.2.3.22.1 Definition

This case tests that the UE will stop the Timer_Poll timer if it receives a STATUS PDU within Timer_Poll ms after a poll for status is transmitted. Incorrect operation of polling will cause degradation of service, or possible service failure.

7.2.3.22.2 Conformance requirement

Timer_Poll.

– positive acknowledgements for all the AMD PDUs with "Sequence Number" up to and including x – 1; or

– a negative acknowledgement for the AMD PDU with "Sequence Number" = x – 1.

If the timer expires and no STATUS PDU fulfilling the criteria above has been received:

– the Receiver shall be polled once more;

– the timer shall be restarted; and

– the new value of VT(S) shall be saved.

If a new poll is sent when the timer is active, the timer shall be restarted at the time specified above, and the value of VT(S) shall be saved.

[…]

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see subclause 9.7.1):

– if polling is not prohibited, see subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

TS 25.322 clause 9.5.

7.2.3.22.3 Test purpose

To verify that the Timer_Poll timer is stopped when receiving a STATUS PDU that acknowledges all AMD PDUs with SN up to and including VT(S)-1 at the time the poll was transmitted.

7.2.3.22.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC	First run	Second run
Tx_Window_Size	256	256
Polling info
Last transmission PDU poll	FALSE	FALSE
Timer_poll	500	1000
Timer_Poll_Periodic	2000	2000

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Test procedure

Let T be the value of the Timer_Poll_Periodic timer.

a) The SS transmits at least 2 * T / TTI SDUs of size AM_7_PayloadSize – 1 bytes.

b) The SS receives PDUs from the UE, and notes the time on receiving the first PDU with the P bit set. This time will be recorded as T_1.

c) The SS sends a STATUS PDU acknowledging all the PDUs up to and including the PDU carrying the poll request.

d) The SS continues to receive PDUs from the UE and notes the time on receipt of the next PDU with the P bit set. This time will be recorded as T₂.

e) The SS continues to receive PDUs from the UE until all transmitted PDUs have been received. The SS responds to any PDU received with the P bit set by transmitting a STATUS PDU containing an acknowledgement of the AMD PDUs received.

f) The SS acknowledges the last Poll PDU from the UE.

g) The SS may optionally release the radio bearer.

The test case is run once for each set of initial RLC parameters.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1
2			…	SS continues to transmit RLC SDUs
3			DOWNLINK RLC PDU	SDU ceil(2T/TTI)
4			UPLINK RLC PDU	SDU 1
5			UPLINK RLC PDU	SDU 2
6			…	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SN = n , Poll: Note T₁ (First PDU with the P bit set).
8			STATUS PDU	ACK SN= 0 to SN =n
9			UPLINK RLC PDU	SN = n +1
10			…	SS continues to receive RLC PDUs
11			UPLINK RLC PDU	Poll: Note T₂ (Next PDU with the P bit set)
12			…	SS continues to receive PDUs, acknowledging with Status PDUs when polled until all PDUs have been received and acknowledged
13			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: The SN value “n” identifies the current RLC sequence number of the first UL PDU with the Poll Bit set. This value is for informative purposes only

7.2.3.22.5 Test requirements

For both execution runs, the measured time T₂– T₁ shall be 2000 ms.

7.2.3.23 Polling for status / Operation of Timer_Poll timer / Restart of the Timer_Poll timer

7.2.3.23.1 Definition

This case tests that the UE will restart the Timer_Poll timer if another poll request is transmitted whilst the timer is running. Incorrect operation of polling will cause degradation of service, or possible service failure.

This test applies to all UE.

7.2.3.23.2 Conformance requirement

Timer_Poll.

– positive acknowledgements for all the AMD PDUs with "Sequence Number" up to and including x – 1; or

– a negative acknowledgement for the AMD PDU with "Sequence Number" = x – 1.

If the timer expires and no STATUS PDU fulfilling the criteria above has been received:

– the Receiver shall be polled once more;

– the timer shall be restarted; and

– the new value of VT(S) shall be saved.

If a new poll is sent when the timer is active, the timer shall be restarted at the time specified above, and the value of VT(S) shall be saved.

[…]

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see subclause 9.7.1):

– if polling is not prohibited, see subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

TS 25.322 clause 9.5.

7.2.3.23.3 Test purpose

To verify that if a new poll is sent when the timer is running it is restarted.

7.2.3.23.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Polling info
Last retransmission PDU poll	FALSE
Last transmission PDU poll	FALSE
Timer_poll	600
Poll_Window	60
Poll_PDU	16
Transmit window size	32

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Test procedure

Let T be the value of the Timer_Poll timer.

a) The SS starts transmission of ceil(Tx_Window_Size * 60%) numbers of SDUs of size AM_7_PayloadSize – 1bytes.

b) Whilst transmitting, the SS receives PDUs from the UE, until it receives the second PDU with the P bit set. This time is recorded as T₁. (Note: poll due to Poll_Window).

c) Void.

d) Void.

e) The SS waits until a PDU is received with the poll bit set and notes the time when it was received. This time is recorded as T₂.

f) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			DOWNLINK RLC PDU	SDU 1
2			…	SS continues to transmit RLC SDUs
3			DOWNLINK RLC PDU	SDU ceil(Tx_Window_Size * 60%)
4			UPLINK RLC PDU	SDU 1
5			UPLINK RLC PDU	SDU 2
6			…	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SN = poll_PDU – 1, 1^st Poll, Timer_Poll started
8			Void
9			Void
10			UPLINK RLC PDU	SS continues to receive RLC PDUs
11			UPLINK RLC PDU	SN= ceil(Tx_Window_Size * 60%)-1, 2^nd Poll, Timer_Poll restarted. Note T1
12			Void
13			Void
14			Void
15			UPLINK RLC PDU	SS waits for reception of PDU with poll bit set, 3^rd Poll, Timer_Poll expired. Note T₂
16			RB RELEASE	Optional step
NOTE: 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.3.23.5 Test requirements

The measured time T₂– T₁ shall be 600 ms.

7.2.3.24 Polling for status / Operation of timer Timer_Poll_Prohibit

7.2.3.24.1 Definition

This case tests that the UE will not send a poll request within Timer_Poll_Prohibit ms of a previous poll request when this mode of operation is enabled. Incorrect operation of polling will cause degradation of service, or possible service failure.

7.2.3.24.2 Conformance requirement

The timers defined in this subclause are normative. The timers shall be considered active from the time they are started until the time they either expire or are stopped.

b) Timer_Poll_Prohibit.

This timer shall only be used when so configured by upper layers. It is used to prohibit transmission of polls within a certain period. The value of the timer is signalled by upper layers.

In the UE this timer shall be started when the successful or unsuccessful transmission of an AMD PDU containing a poll is indicated by lower layer. In UTRAN it should be started when an AMD PDU containing a poll is submitted to lower layer.

From the time a poll is triggered until the timer expires, polling is prohibited. If another poll is triggered while polling is prohibited, its transmission shall be delayed until the timer expires (see subclause 9.7.1). Only one poll shall be transmitted when Timer_Poll_Prohibit expires even if several polls were triggered in the meantime. This timer shall not be affected by the reception of STATUS PDUs.

When Timer_Poll_Prohibit is not configured by upper layers, polling is never prohibited.

The Sender shall:

– if a poll has been triggered by one or several poll triggers (see subclause 9.7.1):

– if polling is not prohibited, see subclause 9.5:

– set the "Polling bit" in the AMD PDU header to "1";

– otherwise:

– set the "Polling bit" in the AMD PDU header to "0".

Reference

TS 25.322 clauses 9.5, 9.7.1 and 11.3.2.1.1.

7.2.3.24.3 Test purpose

1. To verify that no poll is transmitted if one or several polls are triggered when the Timer_Poll_Prohibit timer is active and has not expired.

2. To verify that the UE polls only once after Timer_Poll_Prohibit expires even though triggered several times during the prohibit time.

7.2.3.24.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Transmission RLC discard
MaxDAT	15
Polling info
Timer_poll_prohibit	500
Last transmission PDU poll	FALSE
Poll_PDU	2
Poll_Window	50
Transmission window size	32
Downlink RLC
Receiving window size	128

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Test procedure

Let T be the value of the Timer_Poll_Prohibit timer.

a) The SS starts transmission of at least (2*Poll_PDU) + ceil(T / TTI) SDUs of size AM_7_PayloadSize – 1 bytes.

b) Whilst transmitting, the SS receives PDUs from the UE, and notes the time on receiving the first PDU with the P bit set. This time will be recorded as T_1.

c) The SS does not respond to the poll request.

d) The SS continues to receive PDUs from the UE and notes the time on receipt of the next PDU with the P bit set. This time will be recorded as T₂.

e) The SS waits for at least Timer_Poll_Prohibit to acknowledge any last Poll PDU from the UE.

f) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1
2			…	SS continues to transmit RLC SDUs
3			DOWNLINK RLC PDU	SDU (2*Poll_PDU)+ ceil(T/TTI)
4			UPLINK RLC PDU	SDU 1
5			UPLINK RLC PDU	SDU 2
6			…	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SN = Poll_PDU – 1, Poll: Note T₁
8			…	SS continues to receive RLC PDUs
9			Void
10			UPLINK RLC PDU	SN = (Transmission Window Size / 2) – 1, No Poll
11			…	SS continues to receive RLC PDUs
12			UPLINK RLC PDU	SN = Poll_PDU + ceil(T/TTI) – 1, Poll: Note T₂
12a			…	SS continues to receive RLC PDUs acknowledging with STATUS PDUs when polled until all PDUs have been received and acknowledged
13			RB RELEASE	Optional step
NOTE: 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.3.24.5 Test requirements

1. The measured time T₂– T₁ shall be Timer_poll_prohibit ms.

2. After step 12 no further poll shall be received from the UE for the next Timer_poll_prohibit ms.

7.2.3.25 Receiver Status Triggers / Detection of missing PDUs

7.2.3.25.1 Definition

This case tests that the UE transmits a status report whenever it detects that a PDU is missing, if this mode of operation is enabled. Incorrect operation of status reporting will cause degradation of service, or possible service failure.

7.2.3.25.2 Conformance requirement

Detection of missing PDU(s).

If the Receiver detects one or several missing AMD PDUs it shall trigger the transmission of a status report to the Sender.

Reference

TS 25.322 clause 9.7.2.

7.2.3.25.3 Test purpose

To verify that a status report is transmitted if there are one or more missing PDUs.

7.2.3.25.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

Test procedure

a) The SS transmits 7 SDUs, each of size AM_7_PayloadSize – 1 bytes, in PDUs with consecutive sequence numbers starting from 0, followed by 5 SDUs in PDUs with consecutive sequence numbers starting from 8, followed by an SDU in a PDU with a sequence number of 15.

b) While transmitting, the SS monitors the uplink for STATUS PDUs.

c) The SS may optionally release the radio bearer

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SN = 0
2			…	SS continues to transmit RLC SDUs
3			DOWNLINK RLC PDU	SN = 6
4			DOWNLINK RLC PDU	SN = 8
5			STATUS PDU	SN = 7 missing
6			DOWNLINK RLC PDU
7			…	SS continues to transmit RLC SDUs
8			DOWNLINK RLC PDU	SN = 12
9			DOWNLINK RLC PDU	SN = 15
10			STATUS PDU	SN = 7, 13, 14 missing
11			RB RELEASE	Optional step
NOTE: 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.3.25.5 Test requirements

A STATUS PDU shall be received from the UE after step 4, indicating that the PDU with sequence number 7 was missing.

A STATUS PDU shall be received from the UE after step 9, indicating that the PDUs with sequence numbers 7, 13 and 14 were missing.

7.2.3.26 Receiver Status Triggers / Operation of timer Timer_Status_Periodic

7.2.3.26.1 Definition

This case tests that the UE transmits a status report every Timer_Status_Periodic ms when this mode of operation is enabled. Incorrect operation of status reporting will cause degradation of service, or possible service failure.

7.2.3.26.2 Conformance requirement

This timer shall only be used when timer based status reporting is configured by upper layers.

This timer shall be started when the RLC entity is created. When the timer expires the transmission of a status report shall be triggered and the timer shall be restarted.

Reference

TS 25.322 clauses 9.5, 9.7.2 and 11.5.2.

7.2.3.26.3 Test purpose

To verify that a status report is transmitted each time the Timer_Status_Periodic timer expires.

7.2.3.26.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Downlink RLC
Timer_STATUS_periodic	400

These settings apply to both the uplink and downlink DTCH.

Test procedure

Let T be the value of the Timer_STATUS_periodic timer.

a) The SS starts transmission of at least ceil(2 * T / TTI) SDUs of size AM_7_PayloadSize – 1 bytes.

b) The SS waits to receive a STATUS PDU and notes the time. This time will be recorded as T₁.

c) The SS waits to receive a second STATUS PDU and notes the time. This time will be recorded as T₂.

d) The SS waits for at least Timer_Status_Periodic to receive any last STATUS PDU from the UE.

e) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1
2			…	SS continues to transmit RLC SDUs
3			DOWNLINK RLC PDU	SDU m
4			STATUS PDU	Note T₁
5			DOWNLINK RLC PDU
6			…	SS continues to transmit RLC SDUs
7			DOWNLINK RLC PDU	SDU m + ceil(T/TTI)
8			STATUS PDU	Note T₂
9			Void
10			STATUS PDU	SS may receive STATUS PDUs
11			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.3.26.5 Test requirements

The measured time T₂– T₁ shall be 400 ms.

7.2.3.27 Receiver Status Triggers / Operation of timer Timer_Status_Prohibit

7.2.3.27.1 Definition

This case tests that the UE does not transmit a status report more often than every Timer_Status_Prohibit ms when this mode of operation is enabled. Incorrect operation of status reporting will cause degradation of service, or possible service failure.

7.2.3.27.2 Conformance requirement

In the UE, this timer shall be started when the successful or unsuccessful transmission of the last STATUS PDU of an acknowledgement status report is indicated by lower layer

[…]

When a status report is triggered the Receiver shall:

– if transmission of status reports is not prohibited by any of the functions "STATUS prohibit" or "EPC mechanism":

– assemble and transmit the status report to the Sender, as specified in subclauses TS 25.322 11.5.2.2 and 11.5.2.3.

– otherwise (if the status report is prohibited by at least one of the functions "STATUS prohibit" or "EPC mechanism"):

[…]

– if ACK, LIST, BITMAP, or RLIST SUFIs are required in the status report:

– delay sending these SUFIs until the prohibit function terminates.

[…]

Upon expiry of the timer Timer_Status_Prohibit […], the Receiver shall:

– if at least one status report was triggered during the time the transmission of a status reports was prohibited that could not be transmitted due to prohibition; and

– if transmission of a status reports is no longer prohibited by any of the functions "STATUS prohibit" or "EPC mechanism":

– transmit one status report to the Sender, using the procedure described in subclause TS 25.322 11.5.2.3.

Reference

TS 25.322 clause 9.7.2.

7.2.3.27.3 Test purpose

1. To verify that a status report is not transmitted while the Timer_Status_Prohibit timer is active.

2. To verify that only one status report is sent on the expiry of the Timer_Status_Prohibit timer if several triggers occur while it is active.

7.2.3.27.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Downlink RLC
Timer_Status_Prohibit	500
Timer_STATUS_periodic	200

These settings apply to both the uplink and downlink DTCH.

Test procedure

Let T_pro be the value of the Timer_Status_Prohibit timer, and T_per be the value of the Timer_Status_Periodic timer.

a) The SS starts transmission of at least ceil(2 * T_pro / TTI) + ceil(T_per/TTI) SDUs of size AM_7_PayloadSize – 1 bytes.

b) Whilst transmitting, the SS monitors the uplink for a STATUS PDU and notes the time. This time will be recorded as T₁.

c) The SS sets the P bit in one of the next floor(T_pro/TTI) PDUs transmitted on the downlink.

d) The SS waits to receive a second STATUS PDU and notes the time. This time will be recorded as T₂.

e) The SS waits for at least Timer_Status_Prohibit to receive any last STATUS PDU from the UE.

f) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1
2			…	SS continues to transmit RLC SDUs
3			DOWNLINK RLC PDU	SDU m
4			STATUS PDU	Note T₁
5			DOWNLINK RLC PDU	Poll
6			…	SS continues to transmit RLC PDUs
7			DOWNLINK RLC PDU	SDU m + ceil(T_pro / TTI)
8			STATUS PDU	Note T₂
9			Void
10			STATUS PDU	SS may receive STATUS PDUs
11			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.3.27.5 Test requirements

1. The measured time T₂– T₁ shall be 500 ms.

2. Only one STATUS PDU shall be received in step 8 after (T1 + Tpro) and before (T1 + 2*Tpro).

7.2.3.28 Status reporting / Abnormal conditions / Reception of LIST SUFI with Length set to zero

7.2.3.28.1 Definition

Peer RLCs use STATUS PDUs to manage flow control and retransmission. On a STATUS report PDU with an invalid LIST SUFI the RLC must behave as specified. Incorrect behaviour may result in degradation of QoS, or failure of the UE to communicate.

7.2.3.28.2 Conformance requirement

The List super-field

The List Super-Field consists of a type identifier field (LIST), a list length field (LENGTH) and a list of LENGTH number of pairs as shown in figure 9.11 below:

Type = LIST

LENGTH

SN₁

L₁

SN₂

L₂

…

SN_LENGTH

L_LENGTH

Figure 9.11: The List fields in a STATUS PDU

LENGTH

Length: 4 bits

The number of (SN_i, L_i)-pairs in the super-field of type LIST. The value "0000" is invalid and the list is discarded.

Reference

TS 25.322 clause 9.2.2.11.4.

7.2.3.28.3 Test purpose

To verify that if a STATUS PDU is received with a LIST SUFI and the LENGTH field is set to "0000" that the list is discarded.

7.2.3.28.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Polling info
Poll_PDU	4

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (3 * Poll_PDU * AM_7_PayloadSize) – 1 bytes.

Test procedure

a) The SS sends an SDU of size (AM_7_PayloadSize) – 1.

b) The SS monitors the received (looped back) PDUs for a poll request.

c) The SS responds to the poll request by transmitting a STATUS PDU with a LIST SUFI. The list contains an indication that two PDUs were not received, but has the length field set to "0000".

d) The SS continues to monitor the received PDUs to verify that none are retransmitted.

e) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1 (start)
2			…	SS continues to transmit RLC PDUs
3			DOWNLINK RLC PDU	SDU 1 (end)
4			UPLINK RLC PDU	SDU 1 (start)
5			UPLINK RLC PDU
6			…	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SN = Poll_PDU – 1, Poll
8			STATUS PDU	LIST(LENGTH = "0000", SN = 1, SN = 2)
9			…	SS continues to receive RLC PDUs
10			UPLINK RLC PDU	Poll
11			STATUS PDU	Normal reply
12			…	SS continues to receive RLC PDUs
13			UPLINK RLC PDU	SDU 1 (end)
14			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.3.28.5 Test requirements

No RLC PDUs shall be retransmitted by the UE.

7.2.3.29 Timer based discard, with explicit signalling / Expiry of Timer_Discard

7.2.3.29.1 Definition

This case tests that when the transmission of an SDU exceeds a time limit, the SDU is discarded by the sender, and the discard is signalled to the receiver. SDU discard is used to keep network delays within limits, and incorrect operation will effect the quality of service.

7.2.3.29.2 Conformance requirement

If the transmission time exceeds a predefined value for a SDU in acknowledged mode RLC, this SDU is discarded in the transmitter and a Move Receiving Window (MRW) command is sent to the receiver so that AMD PDUs carrying that SDU are discarded in the receiver and the receiver window is updated accordingly.

This procedure is initiated by the sender when the following conditions are fulfilled … Timer based SDU discard with explicit signalling is used, and Timer_Discard expires for an SDU.

This status report is sent even if the ‘STATUS prohibit’ is used and the timer ‘Timer_Status_Prohibit’ is active.

The STATUS PDUs have higher priority than data PDUs.

Reference

TS 25.322 clauses 9.7.3.1, 11.3.4.3.1 and 11.6.

7.2.3.29.3 Test purpose

1. To verify that if the transmission time for an SDU exceeds Timer_Discard, the SDU is discarded in the transmitter and the MRW procedure is invoked.

2. …

7.2.3.29.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Transmission RLC discard
Timer based with explicit signalling
Timer_MRW	500
Timer_Discard	1000
MAX_MRW	4

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize – 1 bytes.

Test procedure

a) The SS sends at least 2 RLC SDUs of size AM_7_PayloadSize – 1bytes.

b) The SS notes the time that the first RLC PDU is received on the uplink. This time will be recorded as T₁.

c) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU, negatively acknowledging the RLC PDU with sequence number 0, and positively acknowledging all other RLC PDUs received.

d) The SS monitors received STATUS PDUs for the presence of a MRW SUFI, noting the time it was received. This time will be recorded as T₂.

e) The SS responds to the MRW command with a correct MRW_ACK.

f) Void.

g) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1
2			DOWNLINK RLC PDU	SDU 2
3			UPLINK RLC PDU	SDU 1: Note T₁
4			…	SS continues to receive RLC PDUs
5			UPLINK RLC PDU	SDU 2 + Poll
6			STATUS PDU	NAK SN=0
7			…	SS continues to receive RLC PDU with SN=0 + Poll
8			…	STATUS PDU, SS continues to NAK PDU with SN=0
9			STATUS PDU	MRW Command: Note T₂
10			STATUS PDU	MRW_ACK
11			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.3.29.5 Test requirements

1. The measured time T₂– T₁ shall be 1000 ms.

2. The STATUS PDU received in step 9 shall contain a MRW SUFI indicating that the first three PDUs shall be discarded, and that the data indicated in the fourth PDU by the first LI shall also be discarded.

7.2.3.29a Timer based discard, with explicit signalling / Expiry of Timer_Discard when Timer_STATUS_prohibit is active

7.2.3.29a.1 Definition

This case tests that when the transmission of an SDU exceeds a time limit, the SDU is discarded by the sender, and the discard is signalled to the receiver while the Timer_STATUS_Prohibit is active. SDU discard is used to keep network delays within limits, and incorrect operation will effect the quality of service.

This test applies to all UE.

7.2.3.29a.2 Conformance requirement

Upon expiry of Timer_Discard the sender shall initiate the SDU discard with explicit signalling procedure.

This status report is sent even if the ‘STATUS prohibit’ is used and the timer ‘Timer_Status_Prohibit’ is active.

The STATUS PDUs have higher priority than data PDUs.

Reference

TS 25.322 clauses 9.7.3.1, 11.3.4.3.1 and 11.6.

7.2.3.29a.3 Test purpose

…
To verify that the MRW procedure status report is sent even if the ‘STATUS prohibit’ is used and the timer ‘Timer_Status_Prohibit’ is active.

7.2.3.29a.4 Method of test

TBD

7.2.3.29a.5 Test requirements

TBD

7.2.3.30 Timer based discard, with explicit signalling / Obsolete MRW_ACK

7.2.3.30.1 Definition

This case tests the ability of the receiving AM RLC entity to handle obsolete information that can be received during a failure of the SDU discard procedure. SDU discard is used to keep network delays within limits, and incorrect operation will effect the quality of service.

7.2.3.30.2 Conformance requirement

If Timer_MRW expires before the discard procedure is terminated, the MRW SUFI shall be retransmitted, VT(MRW) is incremented by one and Timer_MRW restarted. MRW SUFI shall be exactly the same as previously transmitted even though some new SDUs would have been discarded during the running of the Timer_MRW.

The received MRW_ACK shall be discarded in the following cases.

1. …

2. If the SN_ACK field in the received MRW_ACK < SN_MRW_LENGTH in the transmitted MRW SUFI.

3. If the SN_ACK field in the received MRW_ACK is equal to the SN_MRW_LENGTH in the transmitted MRW SUFI and the N field in the received MRW_ACK is not equal to the N_LENGTH field in the transmitted MRW SUFI

4. If the SN_ACK field in the received MRW_ACK > SN_MRW_LENGTH in the transmitted MRW SUFI and the N field in the received MRW_ACK is not equal to zero.

Reference

TS 25.322 clauses 11.6.5 and 11.6.6.3.

7.2.3.30.3 Test purpose

1. To verify that the MRW SUFI is retransmitted if Timer_MRW expires before a valid MRW_ACK is received.

2. To verify that the MRW_ACK is discarded if the SN_ACK field < SN_MRW_LENGTH.

3. To verify that the MRW_ACK is discarded if the N field is not equal to N_LENGTH transmitted in the MRW SUFI.

4. To verify that the MRW_ACK is discarded if the N field is not zero and the SN_ACK field > SN_MRW_LENGTH in the transmitted MRW SUFI.

7.2.3.30.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Transmission RLC discard
MaxDAT Retransmissions
MaxDAT	40
Timer_MRW	500
MAX_MRW	4

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to AM_7_PayloadSize – 1bytes.

Test procedure

a) The SS sends at least 2 RLC SDUs of size AM_7_PayloadSize – 1bytes.

b) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU, negatively acknowledging the RLC PDU with sequence number 0, and positively acknowledging all other RLC PDUs received.

c) The SS monitors received STATUS PDUs for the presence of a MRW SUFI, noting the time it was received. This time will be recorded as T₁.

d) The SS responds to the MRW command with an MRW_ACK with the SN_ACK field set to SN_MRW_LENGTH – 1.

e) The SS monitors received STATUS PDUs for another MRW SUFI, noting the time it was received. This time will be recorded as T₂.

f) The SS responds to the MRW command with an MRW_ACK with the SN_ACK field set to SN_MRW_LENGTH, and the N field set to (N_LENGTH + 1) modulo 4.

g) The SS monitors received STATUS PDUs for another MRW SUFI, noting the time it was received. This time will be recorded as T₃.

h) The SS responds to the MRW command with an MRW_ACK with the SN_ACK field set to SN_MRW_LENGTH+ 1, and the N field set to 1.

i) The SS monitors received STATUS PDUs for another MRW SUFI.

j) The SS responds to the MRW command with a correct MRW_ACK.

k) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			DOWNLINK RLC PDU	SDU 1
2			DOWNLINK RLC PDU	SDU 2
3			UPLINK RLC PDU	SDU 1
4			UPLINK RLC PDU	SDU 2 + Poll
5			STATUS PDU	NAK SN=0
6			…	SS continues to receive RLC PDU with SN=0 + Poll
7			…	STATUS PDU, SS continues to NAK PDU with SN=0
8			STATUS PDU	MRW Command: Note T₁
9			STATUS PDU	MRW_ACK, SN_ACK = SN_MRW_LENGTH – 1
10			STATUS PDU	MRW Command: Note T₂
11			STATUS PDU	MRW_ACK, N field = (N_LENGTH + 1) modulo 4
12			STATUS PDU	MRW Command: Note T₃
13			STATUS PDU	MRW_ACK, SN_ACK = SN_MRW_LENGTH + 1, N field = 1
14			STATUS PDU	MRW Command
15			STATUS PDU	MRW_ACK
16			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.3.30.5 Test requirements

1. The measured time T₂– T₁ shall be 500 ms.

2. The measured time T₃– T₂ shall be 500 ms.

3. The STATUS PDUs received in steps 8, 10, 12 and 14 shall contain an identical MRW SUFI.

7.2.3.31 Timer based discard, with explicit signalling / Failure of MRW procedure

7.2.3.31.1 Definition

This case tests that if a failure occurs during the signalling of an SDU discard to the receiver, the retransmission protocol operates correctly. SDU discard is used to keep network delays within limits, and incorrect operation will effect the quality of service.

7.2.3.31.2 Conformance requirement

If VT(MRW) = MaxMRW, the Sender shall:

– terminate the SDU discard with explicit signalling procedure;

– stop the timer Timer_MRW if it was started;

– initiate the RLC RESET procedure (see clause 11.4).

If Timer_MRW expires before the discard procedure is terminated, the Sender shall:

– increment VT(MRW) by one;

– if VT(MRW)<MaxMRW:

– set the MRW SUFI as previously transmitted (even if additional SDUs were discarded in the mean-time);

– include the MRW SUFI in a new status report (if other SUFIs are included, their contents shall be updated);

– transmit the status report by either including it in a STATUS PDU or piggybacked in an AMD PDU;

– restart Timer_MRW for this discard procedure;

– else (if VT(MRW) = MaxMRW):

– perform the actions specified in subclause 11.6.4a.

Reference

TS 25.322 clause 11.6.4a, 11.6.5.

7.2.3.31.3 Test purpose

1. To verify that when the number of retransmissions of a MRW command reaches MaxMRW, an error indication is passed to RRC and RESET procedure is initiated.

7.2.3.31.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Transmission RLC discard
Timer based with explicit signalling
Timer_MRW	500
Timer_Discard	500
Max_MRW	4
Polling info
Poll_PDU	2

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1with the UL SDU size set to (2 * AM_7_PayloadSize) – 1bytes.

Test procedure

a) The SS sends 4 RLC SDUs of size (2 * AM_7_PayloadSize) – 1bytes.

b) The SS checks the RLC PDUs received on the uplink and responds to all poll requests as follows: While the VR(H) is 4 or less, with a STATUS PDU, negatively acknowledging the RLC PDU with sequence number 0, and positively acknowledging all other RLC PDUs received. While the VR(H) is greater than 4, a STATUS PDU negatively acknowledging RLC PDUs with sequence numbers 0 and 4, and positively acknowledging all others.

c) The SS monitors received STATUS PDUs for the presence of an MRW SUFI, noting the time it was received. This time will be recorded as T₁.

d) The SS makes no response, but monitors for the next STATUS PDU containing an MRW SUFI, noting the time it was received. This time will be recorded as T₂.

e) The SS sends a STATUS PDU with an MRW_ACK indicating the discard of SDU 1 moving VR(R) to 4.

f) The SS monitors for further STATUS PDUs containing an MRW SUFI, or for a RESET PDU. The SS records the number of STATUS PDUs it received with MRW SUFI before it received the RESET PDU.

g) The SS checks any RLC SDUs reassembled from the uplink.

h) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			DOWNLINK RLC PDU	SDU 1
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 2
4			…	SS continues to send RLC PDUs
5			DOWNLINK RLC PDU	SDU 4
6			UPLINK RLC PDU	SDU 1
7			…	SS continues to receive RLC PDUs
8			UPLINK RLC PDU	Poll
9			STATUS PDU	NAK SN=0
10			…	SS continues to receive RLC PDUs
11			UPLINK RLC PDU	Poll
12			STATUS PDU	NAK SN=0, 4
13			…	SS continues to receive RLC PDUs
14			STATUS PDU	MRW Command: Note T₁
15			STATUS PDU	MRW Command: Note T₂
16			STATUS PDU	MRW_ACK indicating VR(R) = 4
17			STATUS PDU	MRW Command, discard SDU 3
18			STATUS PDU	MRW Command
19			STATUS PDU	MRW Command
20			STATUS PDU	MRW Command
21			RESET PDU
22			RESET ACK PDU
23			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.3.31.5 Test requirements

The measured time T₂– T₁ shall be 500 ms.

After step 17, the SS shall detect 3 repeats of the MRW command sent in step 17 before a RESET PDU is sent.

7.2.3.32 SDU discard after MaxDAT-1 number of transmissions

7.2.3.32.1 Definition

This case tests that if a PDU is unsuccessfully transmitted MaxDAT-1 times, the SDU it carries, and therefore all other associated PDUs, are discarded by the transmitter and receiver. This mode of SDU discard is used to minimize data loss, and incorrect operation will effect the quality of service.

7.2.3.32.2 Conformance requirement

1. There shall be one VT(DAT) for each PDU and each shall be incremented every time the corresponding AMD PDU is scheduled to be transmitted. The initial value of this variable is 0.

2. If the number of times an AMD PDU is scheduled for transmission reaches MaxDAT, the Sender shall:

– discard all SDUs segments of which are contained in the AMD PDU; and

– utilise explicit signalling to inform the Receiver according to clause 11.6.

3. If VT(DAT) = MaxDAT, the Sender shall:

– if "No_discard after MaxDAT number of transmissions" is configured:

….

– if "SDU discard after MaxDAT number of transmissions" is configured:

– initiate the "SDU discard with explicit signalling" procedure for the corresponding SDU, see subclause 11.6.

4. Upon initiation of the SDU discard with explicit signalling procedure, the Sender shall:

…..

– if "SDU discard after MaxDAT number of transmissions" is configured:

– discard all SDUs that have segments in AMD PDUs with "Sequence Number" SN inside the interval VT(A)  SN  X, where X is the value of the "Sequence Number" of the AMD PDU with VT(DAT)  MaxDAT.

– discard all AMD PDUs including segments of the discarded SDUs, unless they also carry a segment of a SDU whose timer has not expired;

– if more than 15 discarded SDUs are to be informed to the Receiver (see subclause 11.6.2.2):

….

– otherwise (less than or equal to 15 discarded SDUs are to be informed to the Receiver):

– assemble an MRW SUFI with the discard information of the SDUs.

– schedule and submit to lower layer a STATUS PDU/piggybacked STATUS PDU containing the MRW SUFI;

….

Reference

TS 25.322 clauses 9.4, 9.7.3.3, 11.3.3a and 11.6.

7.2.3.32.3 Test purpose

1. To verify that if VT(DAT) = MaxDAT for any PDU the sender initiates the SDU discard with explicit signalling procedure.

7.2.3.32.4 Method of test

Initial conditions

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) – 1 bytes.

Test procedure

a) The SS sends 2 RLC SDUs of size (2 * AM_7_PayloadSize) – 1 bytes.

b) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU negatively acknowledging the RLC PDU with sequence number 0, and positively acknowledging all other RLC PDUs received.

c) The SS monitors received STATUS PDUs for the presence of an MRW SUFI.

d) The SS responds with a STATUS PDU containing a valid MRW_ACK SUFI.

e) The SS checks any RLC SDUs reassembled from the uplink.

f) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			DOWNLINK RLC PDU	SDU 1
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 2
4			DOWNLINK RLC PDU	SDU 2
5			UPLINK RLC PDU	SDU 1
6			…	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SDU 2, Poll
8			STATUS PDU	NAK SN=0
9			UPLINK RLC PDU	Retransmit SN=0, Poll
10			STATUS PDU	NAK SN=0
11			UPLINK RLC PDU	Retransmit SN=0, Poll
12			STATUS PDU	NAK SN=0
13			Void
14			Void
15			STATUS PDU	MRW Command
16			STATUS PDU	MRW_ACK
17			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.3.32.5 Test requirements

The uplink RLC PDU with sequence number 0 shall be retransmitted twice, then the SS shall detect a STATUS PDU with an MRW command.

7.2.3.33 Operation of the RLC Reset procedure / UE Originated

7.2.3.33.1 Definition

This case tests that when the maximum number of retransmissions is exceeded, the UE initiates and performs the RLC Reset procedure. Incorrect operation of this procedure may cause loss of service.

7.2.3.33.2 Conformance requirement

The Sender shall:

– if one of the following triggers is detected:

1) "No_Discard after MaxDAT number of transmissions" is configured and VT(DAT) equals the value MaxDAT (see TS 25.322 subclause 9.7.3.4);

…

– stop transmitting any AMD PDU or STATUS PDU;

– increment VT(RST) by 1;

– if VT(RST) = MaxRST:

– the Sender may submit to the lower layer a RESET PDU;

– perform the actions specified in TS 25.322 subclause 11.4.4a.

– else (if VT(RST) < MaxRST):

– submit a RESET PDU to the lower layer;

– start the timer Timer_RST.

NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC reset procedure until the end of the next TTI.

When a reset procedure has been initiated it can only be ended upon reception of a RESET ACK PDU with the same RSN value as in the corresponding RESET PDU, or upon request of re-establishment or release from upper layer, a reset procedure is not interrupted by the reception of a RESET PDU from the peer entity.

[…]

The Sender shall:

– set the HFNI field to the currently highest used HFN (DL HFN when the RESET PDU is sent by UTRAN or UL HFN when the RESET PDU is sent by the UE);

– set the RSN field to the sequence number of the RESET PDU. The sequence number of the first RESET PDU after the AM entity is established or re-established shall be "0". This sequence number is incremented every time a new RESET PDU is transmitted, but not when a RESET PDU is retransmitted.

[…]

Upon reception of a RESET ACK PDU, the Sender shall:

– if the Sender has already transmitted a RESET PDU which has not been yet acknowledged by a RESET ACK PDU:

– if the received RSN value is the same as the one in the corresponding RESET PDU:

– set the HFN value (DL HFN when the RESET ACK PDU is received in UE or UL HFN when the RESET ACK PDU is received in UTRAN) to the HFNI field of the received RESET ACK PDU;

– reset the state variables described in subclause 9.4 to their initial values;

– stop all the timers described in subclause 9.5;

– reset configurable parameters to their configured values;

– discard all RLC PDUs in the receiving side of the AM RLC entity;

– discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity;

– increase with one the UL HFN and DL HFN, and the updated HFN values shall be used for the first transmitted and received AMD PDUs after the reset procedure;

– otherwise (if the received RSN value is not the same as the one in the corresponding RESET PDU):

– discard the RESET ACK PDU;

– otherwise (if the Sender has not transmitted a RESET PDU which has not been yet acknowledged by a RESET ACK PDU):

– discard the RESET ACK PDU.

NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC SDUs discard in the transmitting side until the end of the next TTI.

[…]

If Timer_RST expires before the reset procedure is terminated, the Sender shall:

– increment VT(RST) by one;

– if VT(RST)<MaxRST:

– set the RESET PDU as previously transmitted (even if additional SDUs were discarded in the mean-time);

– transmit RESET PDU;

– restart Timer_RST.

Reference

TS 25.322 clause 11.4.2, 11.4.2.1, 11.4.4, 11.4.5.1.

7.2.3.33.3 Test purpose

1. To verify that the Reset procedure is initiated when the maximum number of retransmissions has been exceeded (Reset trigger condition 1) in subclause 11.4.2 of 3GPP TS 25.322 (R1999).

2. To verify that the sender resets state variables to their initial value and resets configurable parameters to their configured value.

3. To verify that RSN is updated correctly.

4. To verify operation of Timer_RST.

7.2.3.33.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Transmission RLC discard
No discard
Max_DAT	4

These settings apply to both the uplink and downlink DTCH.

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) – 1 bytes.

Test procedure

a) The SS sends 2 RLC SDUs of size (2 * AM_7_PayloadSize) – 1 bytes.

c) The SS notes the time that the RESET PDU is received. This time will be recorded as T₁. The SS notes the value of the RSN bit.

d) The SS makes no response, and notes the time that the next RESET PDU is received. This time will be recorded as T₂. The SS notes the value of the RSN bit.

e) The SS sends a RESET ACK PDU with the RSN bit set to the same value as received in the RESET PDU received in step d).

f) The SS sends an RLC SDU of size (2 * AM_7_PayloadSize) – 1bytes. The data contents of this RLC SDU shall be different from the contents of the RLC SDUs sent in procedure step a) above.

g) The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a STATUS PDU negatively acknowledging the RLC PDU with sequence number 0, and positively acknowledging all other RLC PDUs received.

h) The SS notes the value of the RSN bit of the RESET PDU received.

i) The SS sends a RESET ACK PDU with the RSN bit set to the value received in the RESET PDU in step c (the incorrect value).

j) The SS waits to receive another RESET PDU and checks the RSN bit.

k) The SS sends a RESET ACK PDU with the correct RSN bit.

l) The SS checks any RLC SDU received on the uplink.

m) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			DOWNLINK RLC PDU	SDU 1
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 2
4			DOWNLINK RLC PDU	SDU 2
5			UPLINK RLC PDU	SDU 1
6			…	SS continues to receive RLC PDUs
7			UPLINK RLC PDU	SDU, Poll The Poll may appear in returned PDU for either SDU 1 or 2
8			STATUS PDU	NAK SN=0
9			UPLINK RLC PDU	Retransmit PDU SN=0, Poll
10			STATUS PDU	NAK SN=0
11			UPLINK RLC PDU	Retransmit PDU SN=0, Poll
12			STATUS PDU	NAK SN=0
13			Void
14			Void
15			RESET PDU	Note T₁
16			RESET PDU	Note T_2, check RSN
17			RESET ACK PDU
18			DOWNLINK RLC PDU	SDU 3
19			DOWNLINK RLC PDU	SDU 3
20			UPLINK RLC PDU	SDU 3, check PDU has SN=0
21			UPLINK RLC PDU	SDU 3, Poll
22			STATUS PDU	NAK SN=0
23			UPLINK RLC PDU	Retransmit SN=0, Poll
24			STATUS PDU	NAK SN=0
25			UPLINK RLC PDU	Retransmit SN=0, Poll
26			STATUS PDU	NAK SN=0
27			Void
28			Void
29			RESET PDU	Check RSN
30			RESET ACK PDU	RSN = 0
31			RESET PDU	Check RSN
32			RESET ACK PDU	RSN = 1
33			RB RELEASE	Optional step
NOTE: 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.3.33.5 Test requirements

1. The measured time T₂– T₁ shall be 500 ms.

2. In steps 20 to 21 the SS shall receive an RLC SDU with contents that match the third RLC SDU sent to the UE. The first RLC PDU containing that SDU shall have sequence number 0.

3. The RSN bit of the first and second RESET PDUs received shall be set to 0. The RSN bit of the third and fourth RESET PDU shall be set to 1.

7.2.3.34 Operation of the RLC Reset procedure / UE Terminated

7.2.3.34.1 Definition

This case tests that the UE responds correctly to the RLC Reset procedure initiated by the network. Incorrect operation of this procedure may cause loss of service.

7.2.3.34.2 Conformance requirement

Upon reception of a RESET PDU the Receiver shall:

– if the RSN value in the RESET PDU is the same as the RSN value in the last received RESET PDU:

– either only submit a RESET ACK PDU to the lower layer with the contents set exactly as in the last transmitted RESET ACK PDU (i.e., in this case the RLC entity is not reset); or

– perform the actions specified below as if the RSN value was different from the RSN value in the last received RESET PDU.

– otherwise, if the RESET PDU is the first RESET PDU received since the entity was (re-)established or the RSN value is different from the RSN value in the last received RESET PDU:

– submit a RESET ACK PDU to the lower layer with the content set as specified in subclause 11.4.3.1;

– reset the state variables described in subclause 9.4 except VT(RST) to their initial values;

– stop all the timers described in subclause 9.5 except Timer_RST;

– reset configurable parameters to their configured values;

– discard all RLC PDUs in the receiving side of the AM RLC entity;

– discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity;

– set the HFN (DL HFN when the RESET PDU is received in UE or UL HFN when the RESET PDU is received in UTRAN) equal to the HFNI field in the received RESET PDU;

– increase with one the UL HFN and DL HFN, and the updated HFN values shall be used for the first transmitted and received AMD PDUs after the reset procedure.

NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC SDUs discard in the transmitting side of the AM RLC entity until the end of the next TTI.

Reference

TS 25.322 clause 11.4.3.

7.2.3.34.3 Test purpose

1. To verify that upon reception of a RESET PDU the receiver responds with a RESET ACK PDU.

2. To verify that the receiver resets its state variables to their initial value and resets configurable parameters to their configured value.

7.2.3.34.4 Method of test

Initial conditions

The following RLC parameter values are used in place of the values in clause 7.2.3.1:

Uplink RLC
Transmission RLC discard
No discard
MaxDAT	4

These settings apply to both the uplink and downlink DTCH.

Test procedure

a) The SS sends 2 RLC SDUs of size (2 * AM_7_PayloadSize) – 1 bytes, and polls on the last PDU sent.

b) The SS checks the STATUS PDUs received on the uplink until both SDUs have been acknowledged.

c) The SS transmits a RESET PDU.

d) The SS monitors the uplink for a RESET ACK PDU.

e) The SS sends an RLC SDU of size (2 * AM_7_PayloadSize) – 1 bytes, and polls on the last PDU sent.

f) The SS checks for STATUS PDUs received on the uplink until the SDU has been acknowledged.

g) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			DOWNLINK RLC PDU	SDU 1
2			DOWNLINK RLC PDU	SDU 1
3			DOWNLINK RLC PDU	SDU 2
4			DOWNLINK RLC PDU	SDU 2, poll
5			STATUS PDU	ACK SN=0, 1, 2 and 3
6			RESET PDU
7			RESET ACK PDU
8			DOWNLINK RLC PDU	SDU 3
9			DOWNLINK RLC PDU	SDU 3, poll
10			STATUS PDU	ACK SN=0 and 1
11			RB RELEASE	Optional step
NOTE: 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.3.34.5 Test requirements

1. The SS shall receive a RESET ACK PDU in step 7.

2. The SS shall receive a STATUS PDU in step 10 acknowledging for the third RLC SDU transmitted with PDUs starting at SN=0.

7.2.3.35 Reconfiguration of RLC parameters by upper layers

7.2.3.35.1 Definition

This case verifies the UE behaviour after a reconfiguration of RLC parameters on an established RLC AM entity.

7.2.3.35.2 Conformance requirement

Upon reception of the IE "RLC Info", the UE shall:

1> configure the transmitting and receiving RLC entities in the UE for that radio bearer accordingly;

1> if the IE "Polling info" is present in the IE "RLC info":

2> for each present IE in the IE "Polling info":

3> configure RLC to use the corresponding function according to the value of the IE.

2> for each absent IE in the IE "Polling info":

3> configure RLC to not use the corresponding function.

1> if the IE "Polling info" is absent:

2> configure RLC to not use the polling functionality.

1> if the IE "Downlink RLC STATUS info" is present in the IE "RLC info" (this IE is present for AM RLC):

2> for each present IE in the IE "Downlink RLC STATUS info":

3> configure RLC to use the corresponding function according to value of the IE.

a) Timer_Poll.

f) Timer_Status_Prohibit.

This timer shall only be used when so configured by upper layers. It is meant to prohibit the Receiver from sending consecutive acknowledgement status reports. A status report is an acknowledgement status report if it contains any of the SUFIs LIST, BITMAP, RLIST or ACK. The value of the timer is signalled by upper layers.

In the UE, this timer shall be started when the successful or unsuccessful transmission of the last STATUS PDU of an acknowledgement status report is indicated by lower layer.

Reference

TS 25.331 clause 8.6.4.9, 25.322 clause 9.5.

7.2.3.35.3 Test purpose

To verify that the UE starts to use the new set of RLC parameters when an already established AM RLC radio bearer is reconfigured.

7.2.3.35.4 Method of test

Initial conditions

The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (AM_7_PayloadSize) – 1 bytes.

Test procedure

a) After establishing the radio bearer with default settings, SS reconfigures RLC parameters for an AM RLC entity by sending a RADIO BEARER RECONFIGURATION RRC message to the UE.

b) Let T_poll be the value of the Timer_Poll_Periodic timer, T_pro the value of the Timer_Status_Prohibit timer, and T_per the value of the Timer_Status_Periodic timer.

c) The SS transmits at least 2 * T_poll / TTI SDUs of size AM_7_PayloadSize – 1 bytes.

d) Whilst transmitting, the SS monitors the uplink for a STATUS PDU and notes the time. This time will be recorded as T₁.

e) The SS sets the P bit in one of the next floor(T_pro/TTI) PDUs transmitted on the downlink.

f) The SS waits to receive a second STATUS PDU and notes the time. This time will be recorded as T₂.

g) The SS receives PDUs from the UE, and notes the time on receiving the first PDU with the P bit set, but does not respond. This time will be recorded as T_3.

h) The SS continues to receive PDUs from the UE and notes the time on receipt of the next PDU with the P bit set. This time will be recorded as T₄.

i) The SS may optionally release the radio bearer.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			RADIO BEARER RECONFIGURATION	RRC
2			RADIO BEARER RECONFIGURATION COMPLETE	RRC
3			DOWNLINK RLC PDU	SDU 1
4			…	SS continues to transmit RLC SDUs
5			DOWNLINK RLC PDU	SDU m
6			STATUS PDU	Note T₁
7			DOWNLINK RLC PDU	Poll
8			…	SS continues to transmit RLC PDUs
9			DOWNLINK RLC PDU	SDU m + ceil(T_pro / TTI)
10			STATUS PDU	Note T₂
11			DOWNLINK RLC PDU	SDU ceil(2T_poll/TTI)
12			UPLINK RLC PDU	SDU 1
13			UPLINK RLC PDU	SDU 2
14			…	SS continues to receive RLC PDUs
15			UPLINK RLC PDU	SN = ceil(T_poll/TTI), First Poll: Note T₃
16			UPLINK RLC PDU	SN = ceil(T_poll/TTI)+1
17			…	SS continues to receive RLC PDUs
18			UPLINK RLC PDU	Second Poll: Note T₄
18a			STATUS PDU
18b			…	SS continues to receive PDUs, acknowledging with STATUS PDUs when polled until all PDUs have been received and acknowledged
19			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.

Specific message contents

RADIO BEARER RECONFIGURATION (step 1)

The default RADIO BEARER RECONFIGURATION message as defined in TS 34.108 is used, except for the following:

RB information to reconfigure list
– RB information to reconfigure
– RB identity	Referring to the radio bearer defined for AM 7-bit "Length Indicator" tests in clause 7.2.3.1.
– Downlink RLC Info
– Timer_Status_Prohibit	500
– Timer_STATUS_periodic	200
– Uplink RLC Info
– Polling info
– Last retransmission PDU poll	FALSE
– Last transmission PDU poll	FALSE
– Timer_poll	600
– Timer_Poll_Periodic	1000

7.2.3.35.5 Test requirements

The measured time T₂– T₁ shall be 500 ms.

The measured time T₄– T₃ shall be 600 ms.

7.2.3.36 Flexible handling of RLC PDU sizes for AM RLC

7.2.3.36.1 Definition

When flexible “RLC PDU size” is configured in downlink, RLC SDUs are segmented if the SDU is larger than the maximum RLC PDU size. Concatenation may be performed up to the maximum RLC PDU size. If flexible RLC PDU size is configured, the downlink AMD PDU size is variable up to the maximum RLC PDU size.

7.2.3.36.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

[…]

This two-bit [Header extension type (HE)] field indicates if the next octet is data or a "Length Indicator" and E bit.

Value	Description
00	The succeeding octet contains data
01	The succeeding octet contains a length indicator and E bit
10	If “Use special value of the HE field” is configured, the succeeding octet contains data and the last octet of the PDU is the last octet of an SDU. Otherwise, this coding is reserved (PDUs with this coding will be discarded by this version of the protocol).
11	Reserved (PDUs with this coding will be discarded by this version of the protocol).

[…]

if "flexible RLC PDU size" has been configured (only applicable for UTRAN in downlink):

– segment, and if possible concatenate the RLC SDUs into AMD PDUs with a size not larger than the maximum RLC PDU size.

– set a "Length Indicator" field for each SDU that ends in the AMD PDU according to subclause 9.2.2.8, except for the SDUs where the end of the SDU has been indicated by the HE field according to subclause 9.2.2.7;

[…]

Upon reception of an AMD PDU, the Receiver shall:

[…]

– reassemble the received AMD PDUs into RLC SDUs;

– if "In-Sequence Delivery" is configured:

– deliver the RLC SDUs in-sequence (i.e. in the same order as the RLC SDUs were originally transmitted by the peer entity) to upper layers through the AM-SAP

Reference(s)

TS 25.322 clauses 9.2.2.8, 11.3.2 and 11.3.3.

7.2.3.36.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 is SDU reassembled correctly and delivered to higher layers

7.2.3.36.4 Method of test

Initial conditions

No specific as included in the test procedure (steps a and b) for each test execution

Downlink length indicators of size 15 shall be used

Test procedure

Table 7.2.3.36.4.1 Max_RLC_PDU_size values for different test executions

Test execution	1	2	3
Max_RLC_PDU_size [octets]	90	300	1500

Let Max_RLC_PDU_size be equal to the value for execution 1 in table 7.2.3.36.4.1.

a) 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.10.2.4.5.1 (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) configured according to alt3 (Flexible RLC + MAC-ehs) .

b) 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.

c) The SS transmits two RLC SDUs of size 40 octets. The SDUs are sent in two separate RLC PDUs. The SS sets the HE field to “10”. No length indicators are used.

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

e) The SS transmits two RLC SDUs of size 80 octets. The SDUs are segmented and/or concatenated into successive RLC PDUs where no RLC PDU is larger than Max_RLC_PDU_size. A length indicator is used to indicate the end of each SDU.

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

g) The SS transmits two RLC SDUs of size 320 octets. The SDUs are segmented into successive RLC PDUs where no RLC PDU is larger than Max_RLC_PDU_size. In the RLC PDU containing the last data octet of an RLC SDU the SS sets the HE field to “10”.

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

i) For test execution 1 skip steps j) and k). See Note 1

j) The SS transmits two RLC SDUs of size 1500 octets. The SDUs are segmented into successive RLC PDUs where no RLC PDU is larger than Max_RLC_PDU_size. In the RLC PDU containing the last data octet of an RLC SDU the SS sets the HE field to “10”.

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

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

m) Repeat steps a) to k) for the different values of Max_RLC_PDU_size parameter according to table 7.2.3.36.4.1 (test execution 2 and 3).

NOTE 1 The test steps using RLC SDU size of 1500 octets is skipped for test execution 1 as the maximum number of reordering SDUs per TTI (26) would otherwise have been exceeded.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures,
2			Close UE test loop
3			DOWNLINK RLC PDUs (SDU1, SDU2)	DL RLC SDU size = 40 Octets The number of RLC PDUs depends on the test run. All PDUs are transmitted in the same TTI. NOTE 2.
4			UPLINK RLC PDUs (SDU1, SDU2)	The SS checks length and content of received RLC SDUs. The number of received RLC PDUs depends on the test run
5			DOWNLINK RLC PDUs (SDU1, SDU2)	DL RLC SDU size = 80 Octets The number of RLC PDUs depends on the test run. All PDUs are transmitted in the same TTI. NOTE 2.
6			UPLINK RLC PDUs (SDU1, SDU2)	The SS checks length and content of received RLC SDUs. The number of received RLC PDUs depends on the test run
7			DOWNLINK RLC PDUs (SDU1, SDU2)	DL RLC SDU size = 320 Octets The number of RLC PDUs depends on the test run. All PDUs are transmitted in the same TTI. NOTE 2.
8			UPLINK RLC PDUs (SDU1, SDU2)	The SS checks length and content of received RLC SDUs. The number of received RLC PDUs depends on the test run
9				For test execution 1 skip steps 10 and 11
10			DOWNLINK RLC PDUs (SDU1, SDU2)	DL RLC SDU size = 1500 Octets The number of RLC PDUs depends on the test run. All PDUs are transmitted in the same TTI. NOTE 2.
11			UPLINK RLC PDUs (SDU1, SDU2)	The SS checks length and content of received RLC SDUs. The number of received RLC PDUs depends on the test run
12			Open UE test loop
13			RB RELEASE
14				Repeat steps 1 to 13 for test execution 2 and 3
NOTE 1: The Expected Sequence shown is informative. The number of transmitted RLC PDUs in downlink and uplink varies with the test run. 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: Depending upon the UE category and the number of bits of an HS-DSCH transport block to be transmitted more than one TTI may be required. This will be done respecting table 5.1a of 3GPP TS 25.306. The HS-DSCH TB table size as provided in the bit aligned table of 3GPP TS 25.321 Annex A will be used.

7.2.3.36.5 Test requirements

For each execution of the test procedure:

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

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

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

4. For test execution 2 and 3: In steps 11, the UE shall return two RLC SDUs with the same size and content as the transmitted SDUs

7.2.3.37 RLC PDU Size Adaptation in Uplink

7.2.3.37.1 Definition and applicability

Applicable for all UEs supporting MAC-i/is.

7.2.3.37.2 Conformance Requirement

[..]

For the Unacknowledged mode data and Acknowledged mode data, if MAC-i/is has been configured on the uplink:

– 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.

[..]

Reference(s)

TS 25.322 clause 9.2.2.9

7.2.3.37.3 Test purpose

1. To verify that the UE adapts the RLC PDU size according to the current radio conditions and current grant.

7.2.3.37.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off

User Equipment:

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.10.2.4.6.1 configured according to Alt 3 (Flexible RLC + MAC-i/is ).

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7(LCH 1)	1	1	RB25

The following parameter is specific for this test case:

Parameter	Value
E-DCH TTI	10 ms

The UE is placed into UE test loop mode 1 with the UL SDU size for LCH 1 set to (1500-2) octets.

Test procedure

The UE is configured with one logical channel LCH 1 mapped to MAC-d flow 1.

The SS has not issued a scheduled grant for E-DCH on MAC-d flow 1 (LCH 1)
The SS transmits 1 SDU of size 1498 bytes on LCH 1
The SS waits for an SI to be received indicating that there is data available on LCH 1.
The SS issues an absolute grant with signalling value 5.
The SS receives data from LCH 1 and checks that the RLC PDU size is maximum possible for the grant allowed.
After receiving 4 RLC PDUs, the SS reduces the absolute grant to signalling value of 4.
The SS counts the number of received RLC PDUs on LCH1 which are of the maximum possible size for the previous grant (5). This number should be less than or equal to 5.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	ß		1 RLC SDU on LCH 1	SDU size is 1498 bytes
2	à		SI indicating data on LCH 1
3	ß		Absolute grant allowing the UE to transmit on LCH 1	Signalling value 5 Note: Grant is sent on a specific activation time (i.e ACT_CFN_Step3 = (8+Current CFN) MOD 256)
4	à		RLC PDU on LCH 1
5	ß		Reduces the absolute grant allowing the UE to transmit on LCH 1	Signalling Value 4 Note: Grant is sent on a specific activation time (i.e ACT_CFN_Step5 = (4+ACT_CFN_Step3) MOD 256)
6	à		RLC PDUs on LCH 1
7	ß		Removal of absolute grant	Signalling value 1

Specific Message Contents

None

7.2.3.37.5 Test requirements

1. In step 4, the SS shall receive RLC PDUs of the maximum possible size for the absolute grant (value 5) allowed.

2. In step 6, the SS shall receive between 0 and 5 RLC PDUs on LCH1 of the maximum possible size for the previous grant (5) allowed to cater for the pre-generation of RLC PDUs by the UE for transmission in a later TTI. All other RLC PDUs shall be of the maximum possible size for the current absolute grant (value 4) allowed.

7.2.3.38 Flexible handling of RLC PDU sizes for AM RLC in uplink

7.2.3.38.1 Definition

If flexible RLC PDU size is configured in uplink, RLC SDUs are segmented and/or concatenated to create RLC PDUs larger than or equal to the Minimum UL RLC PDU size and smaller than or equal to the largest UL AMD PDU size. If data to be transmitted is not enough to create an AMD PDU of the minimum size, it is allowed to create an AMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU 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.3.38.2 Conformance requirement

– if "Flexible RLC PDU size" is configured:

[…]

– in uplink, the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field at least up to the Minimum UL RLC PDU size. It is allowed to concatenate up to the largest UL AMD PDU size for Acknowledged mode data and largest UMD PDU size for Unacknowledged mode data. The "Length Indicator" field is used to point the borders between RLC SDUs (see subclause 9.2.2.8).

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

– if the UE pre-generates RLC PDUs for transmission in a later 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.

[…]

– if "flexible RLC PDU size" has been configured:

– the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field at least up to the Minimum UL RLC PDU size. If data to be transmitted is not enough to create an AMD PDU of the minimum size, it is allowed to create an AMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size.

Reference(s)

TS 25.322 clauses 4.2.1.3.1, 9.2.2.9 and 11.3.2.

7.2.3.38.3 Test purpose

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

7.2.3.38.4 Method of test

Initial conditions

The following parameters are specific for this test case:

Parameter	Value
Minimum UL RLC PDU size	320 bit
Largest UL RLC PDU size	640 bit

a) 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.10.2.4.6.1 configured according to Alt 3 (Flexible RLC + MAC-i/is ) with MAC-d flow#1 configured for scheduled transmissions.

b) The radio bearer is placed into UE test loop mode 1 and configured to return UL RLC SDUs of size 80 octets

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

d) The SS transmits 4 RLC SDUs of size 80 octets. RLC PDUs are created by adding an AMD header (the SDUs are not segmented or concatenated). In each RLC PDU the HE field is set to “10”.

e) The SS waits for a SI to be received.

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

g) The SS checks the content of the received RLC SDUs, the size of the AMD PDUs.

h) The SS removes the scheduling grant for the UE.

i) The SS transmits 4 RLC SDUs of size 80 octets. RLC PDUs are created by adding an AMD header (the SDUs are not segmented or concatenated). In each RLC PDU the HE field is set to “10”

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

k) The SS checks the content of the received RLC SDUs and the size of the AMD PDUs.

l) The SS opens the UE test loop and releases the radio bearer.

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

NOTE 2: Signalled absolute grant of 5 enable the UE to transmit a maximum MAC-i PDU size of 752 bits (10ms TTI, Reference E-TFCI=11 Signalled power offset=4), which is larger than the configured “Largest UL RLC PDU size” of 640 bits.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1			RB ESTABLISHMENT	See generic procedures,
2			Close UE test loop
3			DOWNLINK RLC PDU (SDUs)	SN=0,1,2,3, RLC SDU size = 80 Octets.
4			SI indicating data
5			Absolute grant	Grant value 3.
6			UPLINK RLC PDU (SDUs)	The SS checks the content of received RLC SDUs and the size of the AMD PDUs.
7			Absolute grant	Grant value 1, removal of SG.
8			DOWNLINK RLC PDU (SDUs)	SN=4,5,6,7, RLC SDU size = 80 Octets.
9			SI indicating data
10			Absolute grant	Grant value 5.
11			UPLINK RLC PDU (SDUs)	The SS checks the content of received RLC SDUs and the size of the AMD PDUs.
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.3.38.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 size of all AMD PDUs, except the final AMD PDU, shall be equal to “Minimum UL RLC PDU size”. The size of the last AMD PDU can be less than or equal to the "Minimum UL RLC PDU size".

2. In step 11, the UE shall return 4 RLC SDUs with the same content as the transmitted SDUs. The size of the fist AMD PDU shall be equal to “Largest UL RLC PDU size”, the subsequent AMD PDUs shall be between minimum UL PDU size and Largest UL RLC PDU size, and the last AMD PDU shall be less than the Largest UL RLC_PDU size.