7.3.5 PDCP handover

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

7.3.5.1 Void

7.3.5.2 PDCP handover / Lossless handover / PDCP sequence number maintenance

7.3.5.2.1 Test Purpose (TP)

(1)

with {UE in E-UTRA RRC_CONNECTED state with default RB using RLC-AM}

ensure that {
when { UE is requested to make a lossless handover by SS }

then { UE retransmits the unacknowledged data}

}

7.3.5.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clause 5.2.1.1.

[TS 36.323, clause 5.2.1.1]

When upper layers request a PDCP re-establishment, the UE shall:

– reset the header compression protocol for uplink (if configured);

– apply the ciphering algorithm and key provided by upper layers during the re-establishment procedure;

– from the first PDCP SDU for which the successful delivery of the corresponding PDCP PDU has not been confirmed by lower layers, perform retransmission or transmission of all the PDCP SDUs already associated with PDCP SNs in ascending order of the COUNT values associated to the PDCP SDU prior to the PDCP re-establishment as specified below:

– perform header compression of the PDCP SDU (if configured) as specified in the subclause 5.5.4;

– perform ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in the subclause 5.6;

– submit the resulting PDCP Data PDU to lower layer

7.3.5.2.3 Test description

7.3.5.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18] and table 7.3.5.2.3. 3-2 for SR configuration.

7.3.5.2.3.2 Test procedure sequence

Table 7.3.5.2.3.2.0-1: Time instances of cell power level

Parameter

Unit

Cell 1

Cell 2

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

Table 7.3.5.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS creates 5 PDCP Data PDUs and the Next_PDCP_TX_SN is set to "0".

–

–

–

–

–

EXCEPTION: Step 2 and 3 A shall be repeated for k=0 to 1(increment=1).

–

–

–

–

2

The SS sends the PDCP Data PDU#k via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN = k.

After having sent a PDU, the SS set Next_PDCP_TX_SN= k+1.

<–

PDCP PDU DATA #k

–

–

3

The UE sends the PDCP Data PDU#k via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN = k.

Data is previously received data from PDU #k. (Note 1)

–>

PDCP PDU DATA #k

–

–

3A

Wait for the expiry of t-PollRetransmit

–

–

–

–

4

Configure SS not to allocate UL grant to the UE in Cell 1.

–

–

–

–

–

EXCEPTION: Step 5 shall be repeated for m=2 to 4 (increment=1).

–

–

5

The SS sends the PDCP Data PDU #m via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN =m.

After having sent a PDU, the SS set Next_PDCP_TX_SN = m+1.

<–

PDCP PDU DATA #m

–

–

5A

The SS changes Cell 2 parameters according to the row "T1" in table 7.3.5.2.3.2.0-1.

–

–

–

–

5B

Configure SS to allocate Default UL grant to the UE in Cell 2 (Note 2).

Note: These grants will be requested by the UE to send data after the handover

–

–

–

–

6

The SS requests UE to make a handover to Cell2 with the RRCConnectionReconfiguration message sent on Cell 1.

<–

RRCConnectionReconfiguration

–

–

7

SS assigns UL grant during the Random Access procedure to allow the UE to send only RRCConnectionReconfigurationComplete message.

–

–

–

–

8

The UE on Cell 2 transmits a RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

–

–

8A

The UE send PDCP Control PDUs via RLC-AM RB with the following content to the SS: D/C field = 0 (PDCP control PDU) and PDU Type =000, FMS field = 5.

–>

PDCP STATUS REPORT

–

–

8B

The SS generates a PDCP status report message and sends it to UE: D/C field = 0 (PDCP control PDU) and PDU Type =000, FMS field = 2.

<–

PDCP STATUS REPORT

–

–

8C

Configure SS to allocate Default UL grant to the UE in Cell 2

–

–

–

–

EXCEPTION: Step 9 shall be repeated for m=2 to 4 (increment=1).

–

–

–

–

9

Check: Does the UE send the PDCP Data PDU #m via RLC-AM RB with the following content to the SS:

D/C field = 1 (PDCP Data PDU) and PDCP SN = m?

Data is previously received data from PDU #m.

–>

PDCP PDU DATA #m

1

P

Note 1: The SS acknowledges the received data.

Note 2: SS transmit an UL grant of 72 bits (ITBS=2, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit only PDCP Status report.

7.3.5.2.3.3 Specific message contents

Table 7.3.5.2.3.3-1: RRCConnectionReconfiguration (step 6, Table 7.3.5.2.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 SEQUENCE {

MobilityControlInfo-HO

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

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 2

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

}

Table 7.3.5.2.3. 3-2: SchedulingRequest-Config (RRC Connection Reconfiguration, preamble Table 4.5.3.3-1: Step8)

Derivation Path: 36.508 Table 4.6.3-20

Information Element

Value/remark

Comment

Condition

dsr-TransMax

n64

7.3.5.3 PDCP handover / Non-lossless handover PDCP sequence number maintenance

7.3.5.3.1 Test Purpose (TP)

(1)

with {UE in E-UTRA RRC_CONNECTED state with bearer using RLC-UM}

ensure that {
when {UE is requested to make a non-lossless handover by SS}

then {UE transmits next PDCP Data PDU with SN value 0 }

}

7.3.5.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.2.1.2.

[TS 36.323, clause 5.2.1.2]

When upper layers request a PDCP re-establishment, the UE shall:

– reset the header compression protocol for uplink (if configured);

– set Next_PDCP_TX_SN, and TX_HFN to 0;

– apply the ciphering algorithm and key provided by upper layers during the re-establishment procedure;

– for each PDCP SDU already associated with a PDCP SN but for which a corresponding PDU has not previously been submitted to lower layers:

– consider the PDCP SDUs as received from upper layer;

– perform transmission of the PDCP SDUs in ascending order of the COUNT value associated to the PDCP SDU prior to the PDCP re-establishment, as specified in the subclause 5.1.1 without restarting the discard-Timer.

7.3.5.3.3 Test description

7.3.5.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2

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.3.5.3.3.2 Test procedure sequence

Table 7.3.5.3.3.2.0-1: Time instances of cell power level

Parameter

Unit

Cell 1

Cell 2

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

Table 7.3.5.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS creates 3 PDCP Data PDUs and the Next_PDCP_TX_SN is set to "0".

–

–

–

–

EXCEPTION: Step 2 and 3 shall be repeated for k=0 to 1 (increment=1).

2

The SS sends the PDCP Data PDU #k via RLC-UM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN = k.

After having sent a PDU, the SS set Next_PDCP_TX_SN= k+1.

<–

PDCP PDU DATA #k

–

–

3

The UE sends the PDCP Data PDU #k via RLC-UM RB with the following content to the SS:

D/C field = 1 (PDCP Data PDU) and PDCP SN = k.

Data is previously received data PDU #k.

–>

PDCP PDU DATA #k

3A

The SS changes Cell 2 parameters according to the row "T1" in table 7.3.5.3.3.2.0-1.

–

–

–

–

3B

Void

–

–

–

–

4

The SS requests UE to make a handover to Cell 2 with the RRCConnectionReconfiguration message.

<–

RRCConnectionReconfiguration

4A

SS assigns UL grant during the Random Access procedure to allow the UE to send only RRCConnectionReconfigurationComplete message.

–

–

–

–

5

The UE transmits a RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

–

5A

The SS assigns additional UL grant to allow the UE to send a PDCP status report

5B

The UE generates a PDCP status report following reestablishment of RLC-AM DRB

->

PDCP status report

5C

Configure SS to allocate Default UL grant to the UE in Cell 2

6

The SS sends the PDCP Data PDU #2 via RLC-UM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 2.

After having sent a PDU, the SS set Next_PDCP_TX_SN= k+1.

<–

PDCP PDU DATA #2

7

Check: Does the UE send the PDCP Data PDU #2 via RLC-UM RB with the following content back to the SS:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 0.

Data is previously received data PDU #2.

–>

PDCP PDU DATA #2

1

P

7.3.5.3.3 Specific message contents

Table 7.3.5.3.3-1: RRCConnectionReconfiguration (step 4, 7.3.5.3.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 SEQUENCE {

MobilityControlInfo-HO

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

radioResourceConfigDedicated

RadioResourceConfigDedicated-HO-MOD

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 2

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 7.3.5.3.3-2: RadioResourceConfigDedicated-HO-MOD (Table 7.3.5.3.3-1)

Derivation Path: 36.508 table 4.6.3-19

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-HO-MOD ::= SEQUENCE {

physicalConfigDedicated

PhysicalConfigDedicated-SR

}

Table 7.3.5.3.3-3: PhysicalConfigDedicated-SR (Table 7.3.5.3.3-2)

Derivation Path: 36.508, Table 4.8.2.1.6-1, condition RBC-HO

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

schedulingRequestConfig

SchedulingRequest-Config-DSR

}

Table 7.3.5.3.3-4: SchedulingRequest-Config-DSR (Table 7.3.5.3.3-3)

Derivation Path: 36.508, Table 4.6.3.-20

Information Element

Value/remark

Comment

Condition

SchedulingRequest-Config-DEFAULT ::= CHOICE {

setup SEQUENCE {

dsr-TransMax

n32

}

}

7.3.5.4 PDCP handover / Lossless handover / PDCP status report to convey the information on missing or acknowledged PDCP SDUs at handover

7.3.5.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with default RB used RLC-AM mode }

ensure that {
when { UE is requested to make a handover by SS }

then { UE creates a PDCP status report to SS}}

(2)

with { UE in E-UTRA RRC_CONNECTED state with default RB used RLC-AM mode }

ensure that {
when { UE is requested to make a handover by SS }

then { UE discards the corresponding PDCP PDU and PDCP SDU according to the PDCP status report from SS }}

7.3.5.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.3 and 5.4

[TS 36.323, clause 5.3.1]

When upper layers request a PDCP re-establishment, for radio bearers that are mapped on RLC AM, the UE shall:

– if the radio bearer is configured by upper layers to send a PDCP status report in the uplink, compile a status report as indicated below after processing the PDCP Data PDUs that are received from lower layers due to the re-establishment of the lower layers as specified in the subclause 5.2.2.1, and submit it to lower layers as the first PDCP PDU for the transmission, by:

– setting the FMS field to the PDCP SN of the first missing PDCP SDU;

– if there is at least one out-of-sequence PDCP SDU stored, allocating a Bitmap field of length in bits equal to the number of PDCP SNs from and not including the first missing PDCP SDU up to and including the last out-of-sequence PDCP SDUs, rounded up to the next multiple of 8;

– setting as ‘0’ in the corresponding position in the bitmap field for all PDCP SDUs that have not been received as indicated by lower layers, and optionally PDCP SDUs for which decompression have failed;

– indicating in the bitmap field as ‘1’ for all other PDCP SDUs.

[TS 36.323, clause 5.3.2]

When a PDCP status report is received in the downlink, for radio bearers that are mapped on RLC AM:

– for each PDCP SDU, if any, with the bit in the bitmap set to ‘1’, or with the associated COUNT value less than the COUNT value of the PDCP SDU identified by the FMS field, the successful delivery of the corresponding PDCP SDU is confirmed, and the UE shall process the PDCP SDU as specified in the subclause 5.4.

[TS 36.323, clause 5.4]

When the Discard_Timer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP status report, the UE shall discard the PDCP SDU along with the corresponding PDCP PDU. If the corresponding PDCP PDU has already been submitted to lower layers the discard is indicated to lower layers.

7.3.5.4.3 Test description

TC is applicable to:

– All UEs supporting E-UTRA.

7.3.5.4.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2

– ROHC is not used for headerCompression settings.

UE:

– UE in UE Loopback Activated test state (state 4) with default RB using RLC-AM in Cell 1 and table 7.3.5.4. 3.3-2 for SR configuration.

7.3.5.4.3.2 Test procedure sequence

Table 7.3.5.4.3.2-1: Time instances of cell power level

Parameter

Unit

Cell 1

Cell 2

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

Table 7.3.5.4.3.2-2: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Next_PDCP_TX_SN is set to "0". The SS creates 4 PDCP Data PDUs.

–

–

–

2

The SS sends the PDCP Data PDU #0 via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN =0.

The SS sets Next_PDCP_TX_SN = 1.

<–

PDCP DATA PDU #0

–

–

3

The UE sends a PDCP Data PDU #0 via RLC-AM RB with the following content back to the SS:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 0

data: previously received packet.

(Note 1)

–>

PDCP DATA PDU #0

–

–

4

The SS is configured on Cell 1 not to send RLC acknowledgements (RLC ACK s) to the UE.

4A

Configure SS not to allocate UL grant to the UE in Cell 1.

–

–

–

–

5

After 100 ms the SS sends the PDCP Data PDU #1 via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN =1.

The SS set Next_PDCP_TX_SN = 2.

<–

PDCP DATA PDU#1

5A

The SS waits for 60 ms and then allocates 1 UL grants (UL grant allocation type 2, Default UL Grant size) to enable UE to return PDCP Data PDU

<–

(UL grants)

–

–

6

The UE sends a PDCP Data PDU #1 via RLC-AM RB with the following content back to the SS:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 1

data: previously received packet.

–>

PDCP DATA PDU#1

6A

The SS changes Cell 2 parameters according to the row "T1" in table 7.3.5.4.3.2-1.

–

–

–

–

6B

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

–

–

–

–

7

The SS requests UE to make a handover to Cell2 with the RRCConnectionReconfiguration message sent on Cell1.

<–

RRCConnectionReconfiguration message.

–

–

7A

SS assigns UL grant during the Random Access procedure to allow the UE to send only RRCConnectionReconfigurationComplete message. (Note 3)

–

–

–

–

8

The UE transmits a RRCConnectionReconfigurationComplete message on Cell2.

–>

RRCConnectionReconfigurationComplete message.

–

–

8A

The SS generates a PDCP status report message and sends it to UE: D/C field = 0 (PDCP control PDU) and PDU Type =000, FMS field = 2.

<–

PDCP status report

–

–

8B

SS waits for 500 ms of ensure UE PDCP has discarded PDCP PDU and is ready to transmit PDCP status report and then assigns 1 UL grant (UL grant allocation type 3) of size 72 bits. (Note 2)

9

Check: Does the UE send PDCP Control PDUs via RLC-AM RB with the following content to the SS: D/C field = 0 (PDCP control PDU) and PDU Type =000, FMS field = 2.

–>

PDCP status report

1

P

10

Void

–

–

–

–

10A

Configure SS to allocate Default UL grant to the UE in Cell 2

–

–

–

–

EXCEPTION: Step 11 shall be repeated for k=2 to 3 (increment=1).

11

The SS sends the PDCP Data PDU #k via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN = k.

After having sent a PDU, the SS set Next_PDCP_TX_SN = k + 1.

<–

PDCP DATA PDU #k

–

–

12

Check: Does the UE send a PDCP Data PDU#2 via RLC-AM RB with the following content back to the SS:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 2

data: previously received packet.

–>

PDCP DATA PDU #2

2

P

13

Check: Does the UE send a PDCP Data PDU#3 via RLC-AM RB with the following content back to the SS:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 3

data: previously received packet.

–>

PDCP DATA PDU #3

2

P

Note 1: The SS sends RLC ACK to the UE

Note 2: SS transmit an UL grant of 72 bits (ITBS=2, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit only PDCP Status report.

Note 3: In case of CAT-M1 UEs an UL Grant of 56 bits will be provided to the UE. This is the same size as used in the regular RACH procedure.

7.3.5.4.3.3 Specific message contents

Table 7.3.5.4.3.3-1: RRCConnectionReconfiguration (Step 7, table 7.3.5.4.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo SEQUENCE {

MobilityControlInfo-HO

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

RadioResourceConfigDedicated-HO {

drb-ToAddModifyList {

PDCP-Configuration-DRB-AM {

discardTimer

infinity

rlc-AM SEQUENCE {

statusReportRequired

TRUE

}

}

}

}

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 2

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 7.3.5.4.3.3-2: SchedulingRequest-Config (RRC Connection Reconfiguration, preamble Table 4.5.3.3-1: Step8 and table 7.3.5.4.3.2-2, step 7)

Derivation Path: 36.508 Table 4.6.3-20

Information Element

Value/remark

Comment

Condition

dsr-TransMax

n64

7.3.5.5 PDCP handover / In-order delivery and duplicate elimination in the downlink

7.3.5.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with default RB using RLC-AM }

ensure that {
when { UE is requested to make a handover by SS }

then { UE achieves in-order delivery and duplicate elimination in the downlink }

}

7.3.5.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.323 clauses 5.1.2.1.2.

[TS 36.323, clause 5.1.2.1.2]

For DRBs mapped on RLC AM, at reception of a PDCP Data PDU from lower layers, the UE shall:

– if received PDCP SN – Last_Submitted_PDCP_RX_SN > Reordering_Window or 0 <= Last_Submitted_PDCP_RX_SN – received PDCP SN < Reordering_Window:

– if received PDCP SN > Next_PDCP_RX_SN:

– decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN – 1 and the received PDCP SN;

– else:

– decipher the PDCP PDU as specified in the subclause 5.6, using COUNT based on RX_HFN and the received PDCP SN;

– perform header decompression (if configured) as specified in the subclause 5.5.5;

– discard this PDCP SDU;

– else if Next_PDCP_RX_SN – received PDCP SN > Reordering_Window:

– increment RX_HFN by one;

– use COUNT based on RX_HFN and the received PDCP SN for deciphering the PDCP PDU;

– set Next_PDCP_RX_SN to the received PDCP SN + 1;

– else if received PDCP SN – Next_PDCP_RX_SN >= Reordering_Window:

– use COUNT based on RX_HFN – 1 and the received PDCP SN for deciphering the PDCP PDU;

– else if received PDCP SN >= Next_PDCP_RX_SN:

– use COUNT based on RX_HFN and the received PDCP SN for deciphering the PDCP PDU;

– set Next_PDCP_RX_SN to the received PDCP SN + 1;

– if Next_PDCP_RX_SN is larger than Maximum_PDCP_SN:

– set Next_PDCP_RX_SN to 0;

– increment RX_HFN by one;

– else if received PDCP SN < Next_PDCP_RX_SN:

– use COUNT based on RX_HFN and the received PDCP SN for deciphering the PDCP PDU;

– if the PDCP PDU has not been discarded in the above:

– perform deciphering and header decompression (if configured) for the PDCP PDU as specified in the subclauses 5.6 and 5.5.5, respectively;

– if a PDCP SDU with the same PDCP SN is stored:

– discard this PDCP SDU;

– else:

– store the PDCP SDU;

– if the PDCP PDU received by PDCP is not due to the re-establishment of lower layers:

– deliver to upper layers in ascending order of the associated COUNT value:

– all stored PDCP SDU(s) with an associated COUNT value less than the COUNT value associated with the received PDCP SDU;

– all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT value associated with the received PDCP SDU;

– set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers;

– else if received PDCP SN = Last_Submitted_PDCP_RX_SN + 1 or received PDCP SN = Last_Submitted_PDCP_RX_SN – Maximum_PDCP_SN:

– deliver to upper layers in ascending order of the associated COUNT value:

– all stored PDCP SDU(s) with consecutively associated COUNT value(s) starting from the COUNT value associated with the received PDCP SDU;

– set Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers.

7.3.5.5.3 Test description

7.3.5.5.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2

UE:

None.

Preamble:

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

7.3.5.5.3.2 Test procedure sequence

Table 7.3.5.5.3.2.0-1: Time instances of cell power level

Parameter

Unit

Cell 1

Cell 2

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

Table 7.3.5.5.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The Next PDCP_TX_SN is set to “0”. The SS creates a PDCP Data PDU#0.

–

–

–

–

2

The SS sends the PDCP Data PDU#0 via RLC-AM RB with the following content to the UE:

PDCP Data PDU #0 (

D/C field = 1 (PDCP Data PDU) and PDCP SN=0 )

(Note 1)

<–

PDCP DATA PDU#0

–

–

3

The UE transmits a PDCP Data PDU via RLC-AM RB with the following content back to the SS

D/C field = 1 (PDCP Data PDU) and PDCP SN=0

data: previously received packet in PDCP Data PDU#0

(Note 2)

–>

PDCP DATA PDU #0

–

–

4

Next_PDCP_TX_SN is set to 1.

The SS creates a PDCP Data PDU#1 (not transmitted).

–

–

–

–

5

The Next_PDCP_TX_SN is set to “2”. The SS creates a PDCP Data PDU #2.

–

–

–

–

6

The SS sends the PDCP Data PDU#2 via RLC-AM RB with the following content to the UE:

PDCP Data PDU#1;

D/C field = 1 (PDCP Data PDU) and PDCP SN=2

(Note 3)

<–

PDCP DATA PDU #2

–

–

7

Check: Does the UE transmit a PDCP DATA PDU#2?

–>

PDCP DATA PDU#2

1

F

7A

The SS changes Cell 2 parameters according to the row "T1" in table 7.3.5.5.3.2.0-1.

–

–

–

–

7B

Configure SS to allocate Default UL grant to the UE in Cell 2 (Note 6).

Note: These grants will be requested by the UE to send data after the handover

–

–

–

–

8

The SS requests UE to make a handover to Cell 2 with the RRCConnectionReconfiguration message.

<–

RRCConnectionReconfiguration

–

–

8A

SS assigns UL grant during the Random Access procedure to allow the UE to send only RRCConnectionReconfigurationComplete message.

–

–

–

–

9

The UE transmits a RRCConnectionReconfigurationComplete message in the new cell.

–>

RRCConnectionReconfigurationComplete

–

–

9A

The UE send PDCP Control PDUs via RLC-AM RB with the following content to the SS: D/C field = 0 (PDCP control PDU) and PDU Type =000, FMS field = 1, Bitmap = 0x80.

–>

PDCP STATUS REPORT

–

–

9B

The SS generates a PDCP status report message and sends it to UE: D/C field = 0 (PDCP control PDU) and PDU Type =000, FMS field = 1.

<–

PDCP STATUS REPORT

–

–

9C

Configure SS to allocate Default UL grant to the UE in Cell 2

–

–

–

–

10

The SS sends the PDCP Data PDU#0 via RLC-AM RB with the following content to the UE:

PDCP Data PDU #0(

D/C field = 1 (PDCP Data PDU) and PDCP SN=0)

(Note 4)

<–

PDCP DATA PDU #0

–

–

11

Check: Does the UE transmit PDCP Data PDU via RLC-AM RB with the following content back to the SS?

D/C field = 1 (PDCP Data PDU) and PDCP SN=0

data: previously received packet in PDCP Data PDU #0

–>

PDCP DATA PDU #0

1

F

12

The SS sends the PDCP Data PDU#1 via RLC-AM RB with the following content to the UE:

PDCP Data PDU#1 (

D/C field = 1 (PDCP Data PDU) and PDCP SN=1)

(Note 5)

<–

PDCP DATA PDU #1

–

–

13

Check: Does the UE transmit a PDCP Data PDU via RLC-AM RB with the following content back to the SS?

D/C field = 1 (PDCP Data PDU) and PDCP SN=1

data: previously received packet in PDCP Data PDU#1

–>

PDCP DATA PDU #1

1

P

14

Check: Does the UE transmit PDCP Data PDU via RLC-AM RB with the following content back to the SS?

D/C field = 1 (PDCP Data PDU) and PDCP SN=2

data: previously received packet in PDCP Data PDU#2

–>

PDCP DATA PDU #2

1

P

Note 1: PDCP Data PDU#0 is sent in RLC PDU#0: SN=0.

Note 2: The SS sends RLC ACK to the UE

Note 3: PDCP Data PDU #2 is sent in RLC PDU#2: SN=2

Note 4: PDCP Data PDU #0 is sent in RLC PDU#1: SN=1

Note 5: PDCP Data PDU #1 is sent in RLC PDU #2:SN = 2

Note 6: SS transmit an UL grant of 72 bits (ITBS=2, NPRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit only PDCP Status report.

7.3.5.5.3.3 Specific message contents

Table 7.3.5.5.3.3-1: RRCConnectionReconfiguration (Step 4, Table 7.3.5.5.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 SEQUENCE {

MobilityControlInfo-HO

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

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 2

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

7.3.5.6 PDCP handover / DAPS handover with key change / Status reporting / Intra-Frequency

7.3.5.6.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for DAPS handover with key change }

ensure that {

when { upper layers request uplink data switching during DAPS handover }

then { UE shall send a PDCP status report for the DAPS bearer }

}

7.3.5.6.2 Conformance requirements

[TS 36.323, clause 5.3.1]

When upper layers request a PDCP re-establishment or PDCP Data Recovery; or when PDCP status report is triggered by polling or periodic reporting; or when PDCP status report is triggered by WLAN Connection Status Reporting of temporary unavailability (suspended, see TS 36.331 [3]); or when upper layers request uplink data switching during DAPS handover, or when upper layers reconfigure the PDCP entity to release DAPS and daps-SourceRelease is configured in TS 36.331 [3], for radio bearers that are mapped on RLC AM, or when upper layers request uplink data switching during DAPS handover for radio bearers that are mapped on RLC UM, the UE shall:

– if the radio bearer is configured by upper layers to send a PDCP status report in the uplink (statusReportRequired, see TS 36.331 [3]) or the status report is triggered by PDCP status report polling or PDCP periodic status reporting or the status report is triggered by WLAN Connection Status Reporting of temporary unavailability (suspended, see TS 36.331 [3]) when wlan-SuspendTriggersStatusReport is configured, see TS 36.331 [3], compile a status report as indicated below after processing the PDCP Data PDUs that are received from lower layers due to the re-establishment of the lower layers as specified in the clause 5.2.2.1, and submit it to lower layers as the first PDCP PDU for the transmission, by:

– setting the FMS field to the PDCP SN of the first missing PDCP SDU;

– if there is at least one out-of-sequence PDCP SDU stored, allocating a Bitmap field of length in bits equal to the number of PDCP SNs from and not including the first missing PDCP SDU up to and including the last out-of-sequence PDCP SDUs, rounded up to the next multiple of 8, or up to and including a PDCP SDU for which the resulting PDCP Control PDU size is equal to 8188 bytes, whichever comes first;

– setting as ‘0’ in the corresponding position in the bitmap field for all PDCP SDUs that have not been received as indicated by lower layers, and optionally PDCP SDUs for which decompression have failed;

– indicating in the bitmap field as ‘1’ for all other PDCP SDUs.

7.3.5.6.3 Test description

7.3.5.6.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2.

UE:

– None.

Preamble:

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

7.3.5.6.3.2 Test procedure sequence

Table 7.3.5.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo containing rach-ConfigDedicated to order UE to perform non-contention based DAPS handover to Cell 2. DRB #1 is configured as DAPS bearer.

<–

RRCConnectionReconfiguration

–

–

2

The UE transmits an RRCConnectionReconfigurationComplete message in Cell 2.

–>

RRCConnectionReconfigurationComplete

–

–

3

Check: Does the UE send PDCP Control PDUs via RLC-AM RB with the following content to the SS: D/C field = 0 (PDCP control PDU) and PDU Type = 000, FMS field = 0?

–>

PDCP status report

1

P

4

The SS generates a PDCP status report message and sends it to UE: D/C field = 0 (PDCP control PDU) and PDU Type =000, FMS field = 0.

<–

PDCP status report

–

–

7.3.5.6.3.3 Specific message contents

Table 7.3.5.6.3.3-0: Conditions for specific message contents
in Table 7.3.5.6.3.3-2

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 7.3.5.6.3.3-1: RRCConnectionReconfiguration (step 1, Table 7.3.5.6.3.2-1)

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

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

securityConfigHO

SecurityConfigHO

}

}

}

}

Table 7.3.5.6.3.3-2: MobilityControlInfo (Table 7.3.5.6.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 2

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 2

Band 24 High range

}

radioResourceConfigCommon

RadioResourceConfigCommon-DEFAULT

rach-ConfigDedicated

Rach-ConfigDedicated-DEFAULT

}

Table 7.3.5.6.3.3-3: RadioResourceConfigCommon-DEFAULT (Table 7.3.5.6.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

rach-ConfigCommon

RACH-ConfigCommon-DEFAULT

}

Table 7.3.5.6.3.3-4: RadioResourceConfigDedicated (Table 7.3.5.6.3.3-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 7.3.5.6.3.3-5: DRB-ToAddMod-DEFAULT (Table 7.3.5.6.3.3-4)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

1

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Not Present

logicalChannelConfig

Not Present

daps-HO-r16

TRUE

}

Table 7.3.5.6.3.3-6: SecurityConfigHO (Table 7.3.5.6.3.3-1)

Derivation Path: 36.508, Table 4.6.4-1

Information Element

Value/remark

Comment

Condition

SecurityConfigHO ::= SEQUENCE {

handoverType CHOICE {

intraLTE SEQUENCE {

keyChangeIndicator

TRUE

}

}

}

7.3.5.7 PDCP handover / DAPS handover with key change / Status reporting / Inter-Frequency

7.3.5.7.1 Test Purpose (TP)

Same as 7.3.5.6.1.

7.3.5.7.2 Conformance requirements

Same as 7.3.5.6.2.

7.3.5.7.3 Test description

7.3.5.7.3.1 Pre-test conditions

Same as 7.3.5.6.3.1 with the following changes:

System Simulator:

– Cell 1 is the serving cell and Cell 3 is the neighbour inter-frequency cell of Cell 1.

7.3.5.7.3.2 Test procedure sequence

Same as 7.3.5.6.3.2.

7.3.5.7.3.3 Specific message contents

Same as 7.3.5.6.3.3.