7.2.2 Unacknowledged mode

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

7.2.2.1 UM RLC / Segmentation and reassembly / 5-bit SN / Framing info field

7.2.2.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 5 bit SN configured UMD PDU containing a FI field set to 00 }

then { UE correctly decodes the received UMD PDU }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 5 bit SN configured UMD PDU containing a FI field set to 01 }

then { UE correctly decodes the received UMD PDU }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 5 bit SN configured UMD PDU containing a FI field set to 11 }

then { UE correctly decodes the received UMD PDU }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 5 bit SN configured UMD PDU containing a FI field set to 10 }

then { UE correctly decodes the received UMD PDU }

}

7.2.2.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 6.2.1.3 and 6.2.2.6.

[TS 36.322, clause 6.2.1.3]

An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10 bit SN. When the 5 bit SN is configured, the length of the fixed part of the UMD PDU header is one byte. When the 10 bit SN is configured, the fixed part of the UMD PDU header is identical to the fixed part of the AMD PDU header, except for D/C, RF and P fields all being replaced with R1 fields. The extension part of the UMD PDU header is identical to the extension part of the AMD PDU header (regardless of the configured SN size).

[TS 36.322, clause 6.2.2.6]

Length: 2 bits.

The FI field indicates whether a RLC SDU is segmented at the beginning and/or at the end of the Data field. Specifically, the FI field indicates whether the first byte of the Data field corresponds to the first byte of a RLC SDU, and whether the last byte of the Data field corresponds to the last byte of a RLC SDU. The interpretation of the FI field is provided in Table 6.2.2.6-1.

Table 6.2.2.6-1: FI field interpretation

Value

Description

00

First byte of the Data field corresponds to the first byte of a RLC SDU.

Last byte of the Data field corresponds to the last byte of a RLC SDU.

01

First byte of the Data field corresponds to the first byte of a RLC SDU.

Last byte of the Data field does not correspond to the last byte of a RLC SDU.

10

First byte of the Data field does not correspond to the first byte of a RLC SDU.

Last byte of the Data field corresponds to the last byte of a RLC SDU.

11

First byte of the Data field does not correspond to the first byte of a RLC SDU.

Last byte of the Data field does not correspond to the last byte of a RLC SDU.

7.2.2.1.3 Test description

7.2.2.1.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.1.3.1-1 applicable for the configured UM DRB.

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

Table 7.2.2.1.3.1-1: RLC parameters

Uplink RLC

sn-FieldLength

size5

Downlink RLC

sn-FieldLength

size5

7.2.2.1.3.2 Test procedure sequence

Table 7.2.2.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits UMD PDU#1 containing a complete RLC SDU#1 (FI field = 00).

<–

UMD PDU#1

2

Check: Does the UE transmit RLC SDU#1?

–>

(RLC SDU#1)

1

P

3

The SS transmits UMD PDU#2 containing the first segment of RLC SDU#2 (FI field = 01).

<–

UMD PDU#2

4

The SS transmits UMD PDU#3 containing the second segment of RLC SDU#2 (FI field = 11).

<–

UMD PDU#3

5

The SS transmits UMD PDU#4 containing the last segment of RLC SDU#2 (FI field = 10).

<–

UMD PDU#4

6

Check: Does the UE transmit RLC SDU#2?

–>

(RLC SDU#2)

2,3,4

P

7.2.2.1.3.3 Specific message contents

None.

7.2.2.2 UM RLC / Segmentation and reassembly / 10-bit SN / Framing info field

7.2.2.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 10 bit SN configured UMD PDU containing a FI field set to 00 }

then { UE correctly decodes the received UMD PDU }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 10 bit SN configured UMD PDU containing a FI field set to 01 }

then { UE correctly decodes the received UMD PDU }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 10 bit SN configured UMD PDU containing a FI field set to 11 }

then { UE correctly decodes the received UMD PDU }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 10 bit SN configured UMD PDU containing a FI field set to 10 }

then { UE correctly decodes the received UMD PDU }

}

7.2.2.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 6.2.1.3 and 6.2.2.6.

[TS 36.322, clause 6.2.1.3]

An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10 bit SN. When the 5 bit SN is configured, the length of the fixed part of the UMD PDU header is one byte. When the 10 bit SN is configured, the fixed part of the UMD PDU header is identical to the fixed part of the AMD PDU header, except for D/C, RF and P fields all being replaced with R1 fields. The extension part of the UMD PDU header is identical to the extension part of the AMD PDU header (regardless of the configured SN size).

[TS 36.322, clause 6.2.2.6]

Length: 2 bits.

The FI field indicates whether a RLC SDU is segmented at the beginning and/or at the end of the Data field. Specifically, the FI field indicates whether the first byte of the Data field corresponds to the first byte of a RLC SDU, and whether the last byte of the Data field corresponds to the last byte of a RLC SDU. The interpretation of the FI field is provided in Table 6.2.2.6-1.

Table 6.2.2.6-1: FI field interpretation

Value

Description

00

First byte of the Data field corresponds to the first byte of a RLC SDU.

Last byte of the Data field corresponds to the last byte of a RLC SDU.

01

First byte of the Data field corresponds to the first byte of a RLC SDU.

Last byte of the Data field does not correspond to the last byte of a RLC SDU.

10

First byte of the Data field does not correspond to the first byte of a RLC SDU.

Last byte of the Data field corresponds to the last byte of a RLC SDU.

11

First byte of the Data field does not correspond to the first byte of a RLC SDU.

Last byte of the Data field does not correspond to the last byte of a RLC SDU.

7.2.2.2.3 Test description

7.2.2.2.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

7.2.2.2.3.2 Test procedure sequence

Table 7.2.2.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits UMD PDU#1 containing a complete RLC SDU#1 (FI field = 00).

<–

UMD PDU#1

2

Check: Does the UE transmit RLC SDU#1?

–>

(RLC SDU#1)

1

P

3

The SS transmits UMD PDU#2 containing the first segment of RLC SDU#2 (FI field = 01).

<–

UMD PDU#2

4

The SS transmits UMD PDU#3 containing the second segment of RLC SDU#2 (FI field = 11).

<–

UMD PDU#3

5

The SS transmits UMD PDU#4 containing the last segment of RLC SDU#2 (FI field = 10).

<–

UMD PDU#4

6

Check: Does the UE transmit RLC SDU#2?

–>

(RLC SDU#2)

2, 3, 4

P

7.2.2.2.3.3 Specific message contents

None.

7.2.2.3 UM RLC / Reassembly / 5-bit SN / LI value > PDU size

7.2.2.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives a 5 bit SN configured RLC PDU with Length Indicator value larger than RLC PDU size }

then { UE discards the RLC PDU }

}

7.2.2.3.2 Conformance requirements

See TS 36.322 clauses 6.2.2.5 and 5.5.1

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.5.1 and 6.2.2.5.

[TS 36.322, clause 5.5.1]

When an RLC entity receives an RLC PDU that contains reserved or invalid values, the RLC entity shall:

– discard the received PDU.

[TS 36.322, clause 6.2.2.5]

Length: 11 bits.

The LI field indicates the length in bytes of the corresponding Data field element present in the RLC data PDU delivered/received by an UM or an AM RLC entity. The first LI present in the RLC data PDU header corresponds to the first Data field element present in the Data field of the RLC data PDU, the second LI present in the RLC data PDU header corresponds to the second Data field element present in the Data field of the RLC data PDU, and so on. The value 0 is reserved.

7.2.2.3.3 Test description

7.2.2.3.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.3.3.1-1 applicable for the configured UM DRB.

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

Table 7.2.2.3.3.1-1: RLC parameters

Uplink RLC

sn-FieldLength

size5

Downlink RLC

sn-FieldLength

size5

7.2.2.3.3.2 Test procedure sequence

Table 7.2.2.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: the behaviour described in table 7.2.2.3.3.2-2 runs in parallel with steps 1 to 5 below.

1

The SS transmits UMD PDU#1 containing first segment of RLC SDU#1.

<–

UMD PDU#1 (SN=0)

2

The SS transmits UMD PDU#2 containing last segment of RLC SDU#1 and first segment of RLC SDU#2.

<–

UMD PDU#2 (SN=1)

3

The SS transmits UMD PDU#3 containing last segment of RLC SDU#2, first segment of RLC SDU#3 and with Length Indicator that points beyond the end of the UMD PDU#3.

<–

UMD PDU#3 (SN=2)

4

The SS transmits UMD PDU#4 containing last segment of RLC SDU#3.

<–

UMD PDU#4 (SN=3)

5

The SS transmits UMD PDU#5 containing RLC SDU#4.

<–

UMD PDU#5 (SN=4)

Table 7.2.2.3.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits RLC SDU#1.

–>

(RLC SDU#1)

2

Check: Does the UE transmit RLC SDU#2?

–>

(RLC SDU#2)

1

F

3

Check: Does the UE transmit RLC SDU#3?

–>

(RLC SDU#3)

1

F

4

The UE transmits RLC SDU#4.

–>

(RLC SDU#4)

7.2.2.3.3.3 Specific message contents

None.

7.2.2.4 UM RLC / Reassembly / 10-bit SN / LI value > PDU size

7.2.2.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives an RLC PDU with Length Indicator value larger than RLC PDU size }

then { UE discards the RLC PDU }

}

7.2.2.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.5.1.

[TS 36.322, clause 5.5.1]

When an RLC entity receives an RLC PDU that contains reserved or invalid values, the RLC entity shall:

– discard the received PDU.

7.2.2.4.3 Test description

7.2.2.4.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

7.2.2.4.3.2 Test procedure sequence

Table 7.2.2.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The behaviour described in table 7.2.2.4.3.2-2 runs in parallel with steps 1 to 5 below.

1

The SS transmits UMD PDU#1 containing first segment of RLC SDU#1.

<–

UMD PDU#1 (SN=0)

2

The SS transmits UMD PDU#2 containing last segment of RLC SDU#1 and first segment of RLC SDU#2.

<–

UMD PDU#2 (SN=1)

3

The SS transmits UMD PDU#3 containing last segment of RLC SDU#2, first segment of RLC SDU#3 and with Length Indicator that points beyond the end of the RLC PDU#3.

<–

UMD PDU#3 (SN=2)

4

The SS transmits UMD PDU#4 containing last segment of RLC SDU#3.

<–

UMD PDU#4 (SN=3)

5

The SS transmits UMD PDU#5 containing RLC SDU#4.

<–

UMD PDU#5 (SN=4)

Table 7.2.2.4.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE transmit RLC SDU#1?

–>

(RLC SDU#1)

1

P

2

Check: Does the UE transmit RLC SDU#2?

–>

(RLC SDU#2)

1

F

3

Check: Does the UE transmit RLC SDU#3?

–>

(RLC SDU#3)

1

F

4

Check: Does the UE transmit RLC SDU#4?

–>

(RLC SDU#4)

1

P

7.2.2.4.3.3 Specific message contents

None.

7.2.2.5 UM RLC / Correct use of sequence numbering

7.2.2.5.1 UM RLC / 5-bit SN / Correct use of sequence numbering

7.2.2.5.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE transmits the first PDU }

then { UE sets the sequence Number field equal to 0 }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE transmits subsequent PDUs }

then { SN incremented by 1 for each PDU transmitted }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state and an UM RLC DRB is configured using 5 bit SN }

ensure that {

when { UE transmits more than 32 PDUs }

then { UE wraps the Sequence Number after transmitting the 32 PDU }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state and an UM RLC DRB is configured using 5 bit SN }

ensure that {

when { more than 32 PDUs are sent to UE }

then { UE accepts PDUs with SNs that wrap around every 32 PDU }

}

7.2.2.5.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause 5.1.2.1.1, 5.1.2.2, 6.2.1.3, 6.2.2.3 and 7.1.

[TS 36.322, clause 5.1.2.1.1]

When delivering a new UMD PDU to lower layer, the transmitting UM RLC entity shall:

– set the SN of the UMD PDU to VT(US), and then increment VT(US) by one.

[TS 36.322, clause 5.1.2.2]

The receiving UM RLC entity shall maintain a reordering window according to state variable VR(UH) as follows:

– a SN falls within the reordering window if (VR(UH) – UM_Window_Size) <= SN < VR(UH);

– a SN falls outside of the reordering window otherwise.

When receiving an UMD PDU from lower layer, the receiving UM RLC entity shall:

– either discard the received UMD PDU or place it in the reception buffer (see sub clause 5.1.2.2.2);

– if the received UMD PDU was placed in the reception buffer:

– update state variables, reassemble and deliver RLC SDUs to upper layer and start/stop t-Reordering as needed (see sub clause 5.1.2.2.3);

When an UMD PDU with SN = x is received from lower layer, the receiving UM RLC entity shall:

– if VR(UR) < x < VR(UH) and the UMD PDU with SN = x has been received before; or

– if (VR(UH) – UM_Window_Size) <= x < VR(UR):

– discard the received UMD PDU;

– else:

– place the received UMD PDU in the reception buffer.

When an UMD PDU with SN = x is placed in the reception buffer, the receiving UM RLC entity shall:

– if x falls outside of the reordering window:

– update VR(UH) to x + 1;

– reassemble RLC SDUs from any UMD PDUs with SN that falls outside of the reordering window, remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if VR(UR) falls outside of the reordering window:

– set VR(UR) to (VR(UH) – UM_Window_Size);

– if the reception buffer contains an UMD PDU with SN = VR(UR):

– update VR(UR) to the SN of the first UMD PDU with SN > current VR(UR) that has not been received;

– reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

[TS 36.322, clause 6.2.1.3]

An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10 bit SN. When the 5 bit SN is configured, the length of the fixed part of the UMD PDU header is one byte. When the 10 bit SN is configured, the fixed part of the UMD PDU header is identical to the fixed part of the AMD PDU header, except for D/C, RF and P fields all being replaced with R1 fields. The extension part of the UMD PDU header is identical to the extension part of the AMD PDU header (regardless of the configured SN size).

[TS 36.322, clause 6.2.2.3]

The SN field indicates the sequence number of the corresponding UMD…The sequence number is incremented by one for every UMD…

[TS 36.322, clause 7.1]

All state variables and all counters are non-negative integers.

All state variables related to UM data transfer can take values from 0 to [2[sn-FieldLength] – 1]. All arithmetic operations contained in the present document on state variables related to UM data transfer are affected by the UM modulus (i.e. final value = [value from arithmetic operation] modulo 2[sn-FieldLength].

When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.

VR(UH) – UM_Window_Size shall be assumed as the modulus base at the receiving side of an UM RLC entity. This modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. (VR(UH) – UM_Window_Size) <= SN < VR(UH) is evaluated as [(VR(UH) – UM_Window_Size) – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength] <= [SN – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength] < [VR(UH) – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength]).

Each transmitting UM RLC entity shall maintain the following state variables:

a) VT(US)

This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU. It is initially set to 0, and is updated whenever the UM RLC entity delivers an UMD PDU with SN = VT(US).

Each receiving UM RLC entity shall maintain the following state variables:

a) VR(UR) – UM receive state variable

This state variable holds the value of the SN of the earliest UMD PDU that is still considered for reordering. It is initially set to 0.

b) VR(UX) – UM t-Reordering state variable

This state variable holds the value of the SN following the SN of the UMD PDU which triggered t-Reordering.

c) VR(UH) – UM highest received state variable

This state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received UMD PDUs, and it serves as the higher edge of the reordering window. It is initially set to 0.

7.2.2.5.1.3 Test description

7.2.2.5.1.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.5.1.3.1-1 applicable for the configured UM DRB with PDCP Data PDUs using 7 bit SN length.

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

Table 7.2.2.5.1.3.1-1: RLC parameters

Uplink RLC

sn-FieldLength

size5

Downlink RLC

sn-FieldLength

size5

7.2.2.5.1.3.2 Test procedure sequence

Table 7.2.2.5.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

EXCEPTION: Step 3 to 4 is executed 31 times.

1

The SS transmits an UMD PDU. SN equals 0.

<–

UMD PDU

2

Check: Does the UE transmit an UMD PDU with SN = 0?

–>

UMD PDU

1

P

3

The SS transmits an UMD PDU. SN equals 1 and is incremented for each PDU transmitted.

<–

UMD PDU

4

Check: Does the UE transmit an UMD PDU with SN increased by 1 compared with the previous one?

–>

UMD PDU

2

P

5

The SS transmits an UMD PDU. SN equals 0.

<–

UMD PDU

6

Check: Does the UE transmit an UMD PDU with SN=0?

–>

UMD PDU

3, 4

P

7.2.2.5.1.3.3 Specific message contents

None.

7.2.2.5.2 UM RLC / 10-bit SN / Correct use of sequence numbering

7.2.2.5.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE transmits the first PDU }

then { UE sets the Sequence Number field equal to 0 }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE transmits subsequent PDUs }

then { SN incremented by 1 for each PDU transmitted }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state and an UM RLC DRB is configured using 10 bit SN }

ensure that {

when { UE transmits more than 1024 PDUs }

then { UE wraps the Sequence Number after transmitting the 1024 PDU }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state and an UM RLC DRB is configured using 10 bit SN }

ensure that {

when { more than 1024 PDUs are sent to UE }

then { UE accepts PDUs with SNs that wrap around every 1024 PDU }

}

7.2.2.5.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause 5.1.2.1.1, 5.1.2.2, 6.2.1.3, 6.2.2.3 and 7.1.

[TS 36.322, clause 5.1.2.1.1]

When delivering a new UMD PDU to lower layer, the transmitting UM RLC entity shall:

– set the SN of the UMD PDU to VT(US), and then increment VT(US) by one.

[TS 36.322, clause 5.1.2.2]

The receiving UM RLC entity shall maintain a reordering window according to state variable VR(UH) as follows:

– a SN falls within the reordering window if (VR(UH) – UM_Window_Size) <= SN < VR(UH);

– a SN falls outside of the reordering window otherwise.

When receiving an UMD PDU from lower layer, the receiving UM RLC entity shall:

– either discard the received UMD PDU or place it in the reception buffer (see sub clause 5.1.2.2.2);

– if the received UMD PDU was placed in the reception buffer:

– update state variables, reassemble and deliver RLC SDUs to upper layer and start/stop t-Reordering as needed (see sub clause 5.1.2.2.3);

When an UMD PDU with SN = x is received from lower layer, the receiving UM RLC entity shall:

– if VR(UR) < x < VR(UH) and the UMD PDU with SN = x has been received before; or

– if (VR(UH) – UM_Window_Size) <= x < VR(UR):

– discard the received UMD PDU;

– else:

– place the received UMD PDU in the reception buffer.

When an UMD PDU with SN = x is placed in the reception buffer, the receiving UM RLC entity shall:

– if x falls outside of the reordering window:

– update VR(UH) to x + 1;

– reassemble RLC SDUs from any UMD PDUs with SN that falls outside of the reordering window, remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if VR(UR) falls outside of the reordering window:

– set VR(UR) to (VR(UH) – UM_Window_Size);

– if the reception buffer contains an UMD PDU with SN = VR(UR):

– update VR(UR) to the SN of the first UMD PDU with SN > current VR(UR) that has not been received;

– reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

[TS 36.322, clause 6.2.1.3]

An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10 bit SN. When the 5 bit SN is configured, the length of the fixed part of the UMD PDU header is one byte. When the 10 bit SN is configured, the fixed part of the UMD PDU header is identical to the fixed part of the AMD PDU header, except for D/C, RF and P fields all being replaced with R1 fields. The extension part of the UMD PDU header is identical to the extension part of the AMD PDU header (regardless of the configured SN size).

[TS 36.322, clause 6.2.2.3]

The SN field indicates the sequence number of the corresponding UMD…The sequence number is incremented by one for every UMD…

[TS 36.322, clause 7.1]

All state variables and all counters are non-negative integers.

All state variables related to UM data transfer can take values from 0 to [2[sn-FieldLength]– 1]. All arithmetic operations contained in the present document on state variables related to UM data transfer are affected by the UM modulus (i.e. final value = [value from arithmetic operation] modulo 2[sn-FieldLength]).

When performing arithmetic comparisons of state variables or SN values, a modulus base shall be used.

VR(UH) – UM_Window_Size shall be assumed as the modulus base at the receiving side of an UM RLC entity. This modulus base is subtracted from all the values involved, and then an absolute comparison is performed (e.g. (VR(UH) – UM_Window_Size) <= SN < VR(UH) is evaluated as [(VR(UH) – UM_Window_Size) – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength] <= [SN – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength] < [VR(UH) – (VR(UH) – UM_Window_Size)] modulo 2[sn-FieldLength]).

Each transmitting UM RLC entity shall maintain the following state variables:

a) VT(US)

This state variable holds the value of the SN to be assigned for the next newly generated UMD PDU. It is initially set to 0, and is updated whenever the UM RLC entity delivers an UMD PDU with SN = VT(US).

Each receiving UM RLC entity shall maintain the following state variables:

a) VR(UR) – UM receive state variable

This state variable holds the value of the SN of the earliest UMD PDU that is still considered for reordering. It is initially set to 0.

b) VR(UX) – UM t-Reordering state variable

This state variable holds the value of the SN following the SN of the UMD PDU which triggered t-Reordering.

c) VR(UH) – UM highest received state variable

This state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received UMD PDUs, and it serves as the higher edge of the reordering window. It is initially set to 0.

7.2.2.5.2.3 Test description

7.2.2.5.2.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– UE is in state Loopback Activated (state 4) according to [18] with PDCP Data PDUs using 12 bit SN length.

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

7.2.2.5.2.3.2 Test procedure sequence

Table 7.2.2.5.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

EXCEPTION: Steps 3 to 4 are executed 1023 times.

1

The SS transmits an UMD PDU. SN equals 0.

<–

UMD PDU

2

Check: Does the UE transmit an UMD PDU with SN = 0?

–>

UMD PDU

1

P

3

The SS transmits an UMD PDU. SN equals 1 and is incremented for each PDU transmitted.

<–

UMD PDU

4

Check: Does the UE transmit an UMD PDU with SN increased by 1 compared with the previous one?

–>

UMD PDU

2

P

5

The SS transmits an UMD PDU. SN equals 0.

<–

UMD PDU

6

Check: Does the UE transmit an UMD PDU with SN=0?

–>

UMD PDU

3, 4

P

7.2.2.5.2.3.3 Specific message contents

None.

7.2.2.6 UM RLC / Concatenation, segmentation and reassembly

7.2.2.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { The UE has multiple RLC SDUs in the transmission buffer that fits into the available UMD PDU size }

then { The UE concatenates the RLC SDUs in the transmission buffer into one UMD PDU and transmits it}

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { The UE receives UMD PDUs containing concatenated RLC SDUs}

then { The UE reassembles the RLC SDUs in accordance with the Framing Info and Length Indicators indicated in UMD PDUs }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { The UE has RLC SDU in the transmission buffer that does not fit into the available UMD PDU size }

then { The UE segments the RLC SDU in accordance with the Framing Info and Length Indicators indicated in UMD PDUs }

}

7.2.2.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause 4.2.1.2.2, 4.2.1.2.3, 4.4, 6.2.1.3 and 6.2.2.6.

[TS 36.322, clause 4.2.1.2.2]

When a transmitting UM RLC entity forms UMD PDUs from RLC SDUs, it shall:

– segment and/or concatenate the RLC SDUs so that the UMD PDUs fit within the total size of RLC PDU(s) indicated by lower layer at the particular transmission opportunity notified by lower layer;

– include relevant RLC headers in the UMD PDU.

[TS 36.322, clause 4.2.1.2.3]

When a receiving UM RLC entity receives UMD PDUs, it shall:

– reassemble RLC SDUs from the reordered UMD PDUs (not accounting for RLC PDUs for which losses have been detected) and deliver the RLC SDUs to upper layer in ascending order of the RLC SN;

[TS 36.322, clause 4.4]

The following functions are supported by the RLC sub layer:

– concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer);

[TS 36.322, clause 6.2.1.3]

UMD PDU consists of a Data field and an UMD PDU header.

UMD PDU header consists of a fixed part (fields that are present for every UMD PDU) and an extension part (fields that are present for an UMD PDU when necessary). The fixed part of the UMD PDU header itself is byte aligned and consists of a FI, an E and a SN. The extension part of the UMD PDU header itself is byte aligned and consists of E(s) and LI(s).

An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10 bit SN. When the 5 bit SN is configured, the length of the fixed part of the UMD PDU header is one byte. When the 10 bit SN is configured, the fixed part of the UMD PDU header is identical to the fixed part of the AMD PDU header, except for D/C, RF and P fields all being replaced with R1 fields. The extension part of the UMD PDU header is identical to the extension part of the AMD PDU header (regardless of the configured SN size).

An UMD PDU header consists of an extension part only when more than one Data field elements are present in the UMD PDU, in which case an E and a LI are present for every Data field element except the last. Furthermore, when an UMD PDU header consists of an odd number of LI(s), four padding bits follow after the last LI.

Figure 6.2.1.3-1: UMD PDU with 5 bit SN (No LI)

Figure 6.2.1.3-2: UMD PDU with 10 bit SN (No LI)

Figure 6.2.1.3-3: UMD PDU with 5 bit SN (Odd number of LIs, i.e. K = 1, 3, 5, …)

Figure 6.2.1.3-4: UMD PDU with 5 bit SN (Even number of LIs, i.e. K = 2, 4, 6, …)

Figure 6.2.1.3-5: UMD PDU with 10 bit SN (Odd number of LIs, i.e. K = 1, 3, 5, …)

Figure 6.2.1.3-6: UMD PDU with 10 bit SN (Even number of LIs, i.e. K = 2, 4, 6, …)

[TS 36.322, clause 6.2.2.6]

Length: 2 bits.

The FI field indicates whether a RLC SDU is segmented at the beginning and/or at the end of the Data field. Specifically, the FI field indicates whether the first byte of the Data field corresponds to the first byte of a RLC SDU, and whether the last byte of the Data field corresponds to the last byte of a RLC SDU. The interpretation of the FI field is provided in Table 6.2.2.6-1.

Table 6.2.2.6-1: FI field interpretation

Value

Description

00

First byte of the Data field corresponds to the first byte of a RLC SDU.

Last byte of the Data field corresponds to the last byte of a RLC SDU.

01

First byte of the Data field corresponds to the first byte of a RLC SDU.

Last byte of the Data field does not correspond to the last byte of a RLC SDU.

10

First byte of the Data field does not correspond to the first byte of a RLC SDU.

Last byte of the Data field corresponds to the last byte of a RLC SDU.

11

First byte of the Data field does not correspond to the first byte of a RLC SDU.

Last byte of the Data field does not correspond to the last byte of a RLC SDU.

7.2.2.6.3 Test description

7.2.2.6.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

7.2.2.6.3.2 Test procedure sequence

Table 7.2.2.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS does not allocate any uplink grant.

2

The SS transmits UMD PDU#1. This PDU carries SDU#1 with size of 50 bytes.

<–

UMD PDU#1 (RLC SDU#1)

3

The SS transmits UMD PDU#2. This PDU carries SDU#2 with size of 50 bytes.

<–

UMD PDU#2 (RLC SDU#2)

4

SS transmits UL grants to enable UE to return RLC SDU#1 and RLC SDU#2 both in one UMD PDU.

<–

(UL grants)

5

Check: Does UE transmit RLC SDU#1 and RLC SDU#2 within UMD PDU with FI field set to ‘00’, E field in the fixed part set to ‘1’, first E field in the extension part set to ‘0’ and first LI field set to 50 bytes?

–>

UMD PDU#1 (RLC SDU#1 and RLC SDU#2)

1

P

5A

The SS does not allocate any uplink grant.

6

SS transmits an UMD PDU#3 including RLC SDU#3 and RLC SDU#4 each with size of 50 bytes. Header of UMD PDU#3 contains FI=’00’, E=’1’, SN=2, E1=’0’, LI1=’50’.

<–

UMD PDU#3 (RLC SDU#3 and RLC SDU#4)

7

The SS waits for 60 ms and then allocates 2 UL grants (UL grant allocation type 2) with a time spacing of 10 ms to enable UE to return each RLC SDU in one UMD PDU.

(Note 1)

<–

(UL grants)

8

Check: Does UE transmit RLC SDU#3 within an UMD PDU with FI field set to ‘00’ and E field in the fixed part set to ‘0’?

–>

UMD PDU#3 (RLC SDU#3)

2

P

9

Check: Does UE transmit RLC SDU#4 within an UMD PDU with FI field set to ‘00’ and E field in the fixed part set to ‘0’?

–>

UMD PDU#4 (RLC SDU#4)

2

P

10

The SS transmits UMD PDU#4. This PDU carries SDU#5 with size of 50 bytes.

<–

UMD PDU#4 (RLC SDU#5)

11

The SS waits for 60 ms and then allocates 2 UL grants (UL grant allocation type 2) with a time spacing of 10 ms to enable UE to return RLC SDU#5 in two UMD PDUs.

(Note 1)

<–

(UL grants)

12

Check: Does UE transmit 1st part of RLC SDU#5 within UMD PDU#5 with FI field set to ‘01’ and E field in the fixed part set to ‘0’?

–>

UMD PDU#5

3

P

13

Check: Does UE transmit last part of RLC SDU#5 within an UMD PDU#6 with FI field set to ‘10’and E field in the fixed part set to ‘0’?

–>

UMD PDU#6

3

P

Note 1: The SS transmits UL grant to the UE at every 10 ms to provide the necessary time division of the UE DL receptions and UL transmissions for UE operating in FDD type B half-duplex mode. See TS 36.523-3 sub-clause 7.26 for scheduling pattern for type B half-duplex FDD UE.

7.2.2.6.3.3 Specific message contents

None.

7.2.2.7 UM RLC / In sequence delivery of upper layer PDUs without residual loss of RLC PDUs / Maximum re-ordering delay below t-Reordering

7.2.2.7.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC_CONNECTED state }

ensure that {

when { UE receives missing PDUs whose SN is within the reordering window before t-Reordering has expired }

then { RLC reassembles and reorders the UMD PDUs and delivers them to the upper layer in sequence }

}

7.2.2.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause 5.1.2.2.

[TS 36.322, clause 5.1.2.2]

The receiving UM RLC entity shall maintain a reordering window according to state variable VR(UH) as follows:

– a SN falls within the reordering window if (VR(UH) – UM_Window_Size) <= SN < VR(UH);

– a SN falls outside of the reordering window otherwise.

When receiving an UMD PDU from lower layer, the receiving UM RLC entity shall:

– either discard the received UMD PDU or place it in the reception buffer (see sub clause 5.1.2.2.2);

– if the received UMD PDU was placed in the reception buffer:

– update state variables, reassemble and deliver RLC SDUs to upper layer and start/stop t-Reordering as needed (see sub clause 5.1.2.2.3);

When an UMD PDU with SN = x is received from lower layer, the receiving UM RLC entity shall:

– if VR(UR) < x < VR(UH) and the UMD PDU with SN = x has been received before; or

– if (VR(UH) – UM_Window_Size) <= x < VR(UR):

– discard the received UMD PDU;

– else:

– place the received UMD PDU in the reception buffer.

When an UMD PDU with SN = x is placed in the reception buffer, the receiving UM RLC entity shall:

– if x falls outside of the reordering window:

– update VR(UH) to x + 1;

– reassemble RLC SDUs from any UMD PDUs with SN that falls outside of the reordering window, remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if VR(UR) falls outside of the reordering window:

– set VR(UR) to (VR(UH) – UM_Window_Size);

– if the reception buffer contains an UMD PDU with SN = VR(UR):

– update VR(UR) to the SN of the first UMD PDU with SN > current VR(UR) that has not been received;

– reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if t-Reordering is running:

– if VR(UX) <= VR(UR); or

– if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH)::

– stop and reset t-Reordering;

– if t-Reordering is not running (includes the case when t-Reordering is stopped due to actions above):

– if VR(UH) > VR(UR):

– start t-Reordering;

– set VR(UX) to VR(UH).

7.2.2.7.3 Test description

7.2.2.7.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble

– UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.7.3.1-1 applicable for the configured UM DRB.

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

Table 7.2.2.7.3.1-1: RLC parameters

Downlink RLC

t-Reordering

ms200

Test procedure sequence

Table 7.2.2.7.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an UMD PDU. This PDU carries SDU#1. SN equals 0.

<–

UMD PDU#1

2

The UE transmits RLC SDU#1.

–>

(RLC SDU#1)

2A

The SS does not allocate any uplink grant.

3

The SS transmits an UMD PDU. This PDU contains the last part of SDU#4. SN equals 3. The UE starts t-Reordering.

<–

UMD PDU#4

4

The SS transmits an UMD PDU. This PDU contains the last part of SDU#3, and the 1st part of SDU#4. SN equals 2.

<–

UMD PDU#3

5

The SS transmits an UMD PDU. This PDU carries SDU#2 and the 1st part of SDU#3. SN equals 1.

(Note 1)

<–

UMD PDU#2

5A

The SS waits for 60 ms and then allocates 3 UL grants (UL grant allocation type 2) with a time spacing of 10 ms of size enough for the UE to loop back one SDU in one UMD PDU.

6

Check: Does the UE transmit RLC SDU#2?

–>

(RLC SDU#2)

1

P

7

Check: Does the UE transmit RLC SDU#3?

–>

(RLC SDU#3)

1

P

8

Check: Does the UE transmit RLC SDU#4?

–>

(RLC SDU#4)

1

P

Note 1: The UE stops t-Reordering, reassembles UMD PDUs and delivers RLC SDU#2, RLC SDU#3 and RLC SDU#4 to the upper layer in sequence.

Note 2: The SS transmits UL grant to the UE at every 10 ms to provide the necessary time division of the UE DL receptions and UL transmissions for UE operating in FDD type B half-duplex mode. See TS 36.523-3 sub-clause 7.26 for scheduling pattern for type B half-duplex FDD UE.

7.2.2.7.3.3 Specific message contents

None.

7.2.2.8 UM RLC / In sequence delivery of upper layer PDUs without residual loss of RLC PDUs / Maximum re-ordering delay exceeds t-Reordering

7.2.2.8.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { a PDU is received out of order after t-Reordering has expired }

then { UE discards the corresponding PDU and delivers all correctly received RLC SDUs to upper layer in the correct order }

}

7.2.2.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.1.2.2.2, 5.1.2.2.3 and 5.1.2.2.4.

[TS 36.322, clause 5.1.2.2.2]

When an UMD PDU with SN = x is received from lower layer, the receiving UM RLC entity shall:

– if VR(UR) < x < VR(UH) and the UMD PDU with SN = x has been received before; or

– if (VR(UH) – UM_Window_Size) <= x < VR(UR):

– discard the received UMD PDU;

– else:

– place the received UMD PDU in the reception buffer.

[TS 36.322, clause 5.1.2.2.3]

When an UMD PDU with SN = x is placed in the reception buffer, the receiving UM RLC entity shall:

– if x falls outside of the reordering window:

– update VR(UH) to x + 1;

– reassemble RLC SDUs from any UMD PDUs with SN that falls outside of the reordering window, remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if VR(UR) falls outside of the reordering window:

– set VR(UR) to (VR(UH) – UM_Window_Size);

– if the reception buffer contains an UMD PDU with SN = VR(UR):

– update VR(UR) to the SN of the first UMD PDU with SN > current VR(UR) that has not been received;

– reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if t-Reordering is running:

– if VR(UX) <= VR(UR); or

– if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH):

– stop and reset t-Reordering;

– if t-Reordering is not running (includes the case when t-Reordering is stopped due to actions above):

– if VR(UH) > VR(UR):

– start t-Reordering;

– set VR(UX) to VR(UH).

[TS 36.322, clause 5.1.2.2.4]

When t-Reordering expires, the receiving UM RLC entity shall:

– update VR(UR) to the SN of the first UMD PDU with SN >= VR(UX) that has not been received;

– reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if VR(UH) > VR(UR):

– start t-Reordering;

– set VR(UX) to VR(UH).

7.2.2.8.3 Test description

7.2.2.8.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.8.3.1-1 applicable for the configured UM DRB.

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

Table 7.2.2.8.3.1-1: RLC parameters

Downlink RLC

t-Reordering

ms200

7.2.2.8.3.2 Test procedure sequence

Table 7.2.2.8.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits RLC PDU#1 containing first segment of RLC SDU#1.

<–

UMD PDU#1

2

The SS does not transmit RLC PDU#2 containing last segment of RLC SDU#1.

3

The SS transmits RLC PDU#3 containing RLC SDU#2. Note T1

<–

UMD PDU#3

3A

Check 1: Does the UE transmit RLC SDU#2 after t-Reordering (200 ms) expiry?

Note T2

Check 2: Is (T2 – T1) > t-reordering? (Note 1)

–>

(RLC SDU#2)

1

P

3B

The SS transmits RLC PDU#2 containing last segment of RLC SDU#1.

<–

UMD PDU#2

4

Check: Does the UE transmit RLC SDU#1 within 100 ms?

–>

(RLC SDU#1)

1

F

Note 1: It is assumed that, at expiry of t-reordering, reassembling RLC SDUs from any UMD PDUs with SN < updated VR(UR), removal of  RLC headers when doing so and delivering the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before and sending the looped back RLC SDU will not take more than 60ms.

7.2.2.8.3.3 Specific message contents

None.

7.2.2.9 UM RLC / In sequence delivery of upper layer PDUs with residual loss of RLC PDUs / Maximum re-ordering delay exceeds t-Reordering

7.2.2.9.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE detects that RLC PDUs constructing different RLC SDUs are lost }

then { UE delivers all received RLC SDUs to upper layer in the correct order }

}

7.2.2.9.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.1.2.2.2, 5.1.2.2.3 and 5.1.2.2.4.

[TS 36.322, clause 5.1.2.2.2]

When an UMD PDU with SN = x is received from lower layer, the receiving UM RLC entity shall:

– if VR(UR) < x < VR(UH) and the UMD PDU with SN = x has been received before; or

– if (VR(UH) – UM_Window_Size) <= x < VR(UR):

– discard the received UMD PDU;

– else:

– place the received UMD PDU in the reception buffer.

[TS 36.322, clause 5.1.2.2.3]

When an UMD PDU with SN = x is placed in the reception buffer, the receiving UM RLC entity shall:

– if x falls outside of the reordering window:

– update VR(UH) to x + 1;

– reassemble RLC SDUs from any UMD PDUs with SN that falls outside of the reordering window, remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if VR(UR) falls outside of the reordering window:

– set VR(UR) to (VR(UH) – UM_Window_Size);

– if the reception buffer contains an UMD PDU with SN = VR(UR):

– update VR(UR) to the SN of the first UMD PDU with SN > current VR(UR) that has not been received;

– reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if t-Reordering is running:

– if VR(UX) <= VR(UR); or

– if VR(UX) falls outside of the reordering window and VR(UX) is not equal to VR(UH):

– stop and reset t-Reordering;

– if t-Reordering is not running (includes the case when t-Reordering is stopped due to actions above):

– if VR(UH) > VR(UR):

– start t-Reordering;

– set VR(UX) to VR(UH).

[TS 36.322, clause 5.1.2.2.4]

When t-Reordering expires, the receiving UM RLC entity shall:

– update VR(UR) to the SN of the first UMD PDU with SN >= VR(UX) that has not been received;

– reassemble RLC SDUs from any UMD PDUs with SN < updated VR(UR), remove RLC headers when doing so and deliver the reassembled RLC SDUs to upper layer in ascending order of the RLC SN if not delivered before;

– if VR(UH) > VR(UR):

– start t-Reordering.;

– set VR(UX) to VR(UH).

7.2.2.9.3 Test description

7.2.2.9.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.9.3.1-1 applicable for the configured UM DRB.

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

Table 7.2.2.9.3.1-1: RLC parameters

Downlink RLC

t-Reordering

ms200

7.2.2.9.3.2 Test procedure sequence

Table 7.2.2.9.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits UMD PDU#1 containing first segment of RLC SDU#1.

<–

UMD PDU#1

2

The SS does not transmit UMD PDU#2 containing last segment of RLC SDU#1.

3

The SS transmits UMD PDU#3 containing first segment of RLC SDU#2.

<–

UMD PDU#3

4

The SS transmits UMD PDU#4 containing last segment of RLC SDU#2.

<–

UMD PDU#4

5

The SS transmits UMD PDU#5 containing first segment of RLC SDU#3.

<–

UMD PDU#5

6

The SS does not transmit UMD PDU#6 containing last segment of RLC SDU#3.

7

The SS transmits UMD PDU#7 containing first segment of RLC SDU#4.

<–

UMD PDU#7

8

The SS transmits UMD PDU#8 containing last segment of RLC SDU#4.

<–

UMD PDU#8

9

Wait for 200 ms to ensure that t-Reordering for the UMD PDU#2 expires.

10

Check: Does the UE transmit RLC SDU#2?

–>

(RLC SDU#2)

1

P

11

Wait for 200 ms to ensure that t-Reordering for the UMD PDU#6 expires.

12

Check: Does the UE transmit RLC SDU#4?

–>

(RLC SDU#4)

1

P

7.2.2.9.3.3 Specific message contents

None.

7.2.2.10 UM RLC / Duplicate detection of RLC PDUs

7.2.2.10.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC_CONNECTED state }

ensure that {

when { UE receives duplicate UMD PDUs }

then { UE discards the duplicate UMD PDUs }

}

(2)

with { UE in E-UTRAN RRC_CONNECTED state }

ensure that {

when { UE receives UMD PDUs whose SN is within the reordering window and duplicate UMD PDUs }

then { UE discards the duplicate UMD PDUs }

}

7.2.2.10.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause 4.2.1.2.3 and 5.1.2.2.2.

[TS 36.322, clause 4.2.1.2.3]

When a receiving UM RLC entity receives UMD PDUs, it shall:

– detect whether or not the UMD PDUs have been received in duplication, and discard duplicated UMD PDUs;

– reorder the UMD PDUs if they are received out of sequence;

– detect the loss of UMD PDUs at lower layers and avoid excessive reordering delays;

– reassemble RLC SDUs from the reordered UMD PDUs (not accounting for RLC PDUs for which losses have been detected) and deliver the RLC SDUs to upper layer in ascending order of the RLC SN;

[TS 36.322, clause 5.1.2.2.2]

When an UMD PDU with SN = x is received from lower layer, the receiving UM RLC entity shall:

– if VR(UR) < x < VR(UH) and the UMD PDU with SN = x has been received before; or

– if (VR(UH) – UM_Window_Size) <= x < VR(UR):

– discard the received UMD PDU;

7.2.2.10.3 Test description

7.2.2.10.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.2.2.10.3.1-1.

Table 7.2.2.10.3.1-1: RLC settings

Parameter

Value

t-Reordering

ms100

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

7.2.2.10.3.2 Test procedure sequence

Table 7.2.2.10.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an UMD PDU. This PDU carries SDU#1. SN equals 0.

<–

UMD PDU#1

2

The UE transmits RLC SDU#1.

–>

(RLC SDU#1)

3

The SS transmits an UMD PDU. This PDU carries SDU#1. SN equals 0.

<–

UMD PDU#1

4

Check: Does the UE transmit RLC SDU#1?

–>

(RLC SDU#1)

1

F

5

The SS transmits an UMD PDU. This PDU contains SDU#2 and the 1st part of SDU# 3. SN equals 1.

<–

UMD PDU#2

6

The UE transmit RLC SDU#2.

–>

(RLC SDU#2)

7

The SS transmits an UMD PDU. This PDU contains SDU#2 and the 1st part of SDU#3. SN equals 1.

<–

UMD PDU#2

8

Check: Does the UE transmit RLC SDU#2?

–>

(RLC SDU#2)

1

F

9

The SS transmits an UMD PDU. This PDU contains the last part of SDU#3. SN equals 2.

<–

UMD PDU#3

10

The UE transmits RLC SDU#3.

–>

(RLC SDU#3)

10A

The SS ignores scheduling requests and does not allocate any uplink grant.

10B

The SS enables the indication of scheduling requests till step 15.

11

After 100 ms the SS transmits an UMD PDU. This PDU carries SDU#5. SN equals 4.

<–

UMD PDU#5

12

The SS transmits an UMD PDU. This PDU carries SDU#6. SN equals 5.

<–

UMD PDU#6

13

The SS transmits an UMD PDU. This PDU contains the last part of SDU#3. SN equals 2.

<–

UMD PDU#3

14

Check: Does the UE transmit scheduling request before transmission of UMD PDU at step 15?

–>

(SR)

2

F

15

After 75 ms from step 11 the SS transmits an UMD PDU. This PDU carries SDU#4. SN equals 3.

<–

UMD PDU#4

15A

The SS waits for 60 ms and then allocates 1 UL grant of size enough for the UE to loop back 3 RLC SDU in one UMD PDU

<–

(UL Grant)

16

SS receives SDU#4, SDU#5 and SDU#6 in a single PDU

–>

(RLC SDU#4, RLC SDU#5 and RLC SDU#6)

1,2

P

17

Void

18

Void

7.2.2.10.3.3 Specific message contents

None.

7.2.2.11 UM RLC / RLC re-establishment procedure

7.2.2.11.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { RLC re-establishment is performed upon request by RRC }

then { The UE discards all UMD PDUs where no RLC SDUs can be reassembled }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { RLC re-establishment is performed upon request by RRC }

then { The UE resets variable VT(US), VR(UH) and VR(UR) to its initial value }

}

7.2.2.11.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.322, clause 4.2.1.2.3 and 5.4.

[TS 36.322, clause 4.2.1.2.3]

At the time of RLC re-establishment, the receiving UM RLC entity shall:

– if possible, reassemble RLC SDUs from the UMD PDUs that are received out of sequence and deliver them to upper layer;

– discard any remaining UMD PDUs that could not be reassembled into RLC SDUs;

– initialize relevant state variables and stop relevant timers.

[TS 36.322, clause 5.4]

RLC re-establishment is performed upon request by RRC, and the function is applicable for AM, UM and TM RLC entities.

When RRC indicates that an RLC entity should be re-established, the RLC entity shall:

– if it is a receiving UM RLC entity:

– when possible, reassemble RLC SDUs from UMD PDUs with SN < VR(UH), remove RLC headers when doing so and deliver all reassembled RLC SDUs to upper layer in ascending order of the RLC SN, if not delivered before;

– discard all remaining UMD PDUs;

– reset all state variables to their initial values.

7.2.2.11.3 Test description

7.2.2.11.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– UE is in Loopback Activated state (state 4) according to TS 36.508 clause 4.5 [18] with the exceptions listed in table 7.2.2.11.3.1-1 applicable for the configured UM DRB.

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

Table 7.2.2.11.3.1-1: RLC parameters

Downlink RLC

t-Reordering

ms200

7.2.2.11.3.2 Test procedure sequence

Table 7.2.2.11.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits UMD PDU#1. Header of UMD PDU#1 contains SN=0. This PDU carries RLC SDU#1.

<–

UMD PDU#1

2

The UE transmits RLC SDU#1.

–>

(RLC SDU#1)

3

The SS transmits UMD PDU#2. Header of UMD PDU#2 contains SN=1. This PDU carries the 1st segment of SDU#2.

<–

UMD PDU#2

4

SS performs a RRC Connection Reconfiguration procedure including the mobilityControlInfo IE in RRCConnectionReconfiguration triggering RLC re-establishment.

5

The SS transmits UMD PDU#3. Header of UMD PDU#3 contains SN=2. This PDU carries the last segment of RLC SDU#2. The UE starts t-Reordering.

<–

UMD PDU#3

6

Check: Does the UE transmit RLC SDU#2?

–>

(RLC SDU#2)

1

F

7

300 ms (1.5 * t-Reordering) after step 5 the SS transmits UMD PDU#4. Header of UMD PDU#4 contains SN=3. This PDU carries RLC SDU#3.

<–

UMD PDU#4

8

The UE transmit RLC SDU#3. Header of UMD PDU carrying RLC SDU#3 contains SN=0.

–>

(RLC SDU#3)

9

The SS transmits UMD PDU#5. Header of UMD PDU#5 contains SN=4. This PDU carries RLC SDU#4.

<–

UMD PDU#5

10

The UE transmits RLC SDU#4. Header of UMD PDU carrying RLC SDU#4 contains SN=1.

–>

(RLC SDU#4)

11

SS performs a RRC Connection Reconfiguration procedure including the MobilityControlInfo IE in RRCConnectionReconfiguration triggering RLC re-establishment.

12

The SS transmits UMD PDU#6. Header of UMD PDU#6 contains SN=0. This PDU carries RLC SDU#5.

<–

UMD PDU#6

13

Check 1: Does the UE transmit RLC SDU#5? Check 2: Does header of UMD PDU carrying RLC SDU#5 contain SN=0?

–>

(RLC SDU#5)

2

P

Specific message contents

Table 7.2.2.11.3.3-1: RRCConnectionReconfiguration (step 4 and step 11, Table 7.2.2.11.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 1

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 7.2.2.11.3.3-2: MobilityControlInfo (step 4 and step 11, Table 7.2.2.11.3.2-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq

Not present

}