8.5.5 RACS / UL Message Segment transfer

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

8.5.5.1 RACS / UL Message Segment transfer / UECapabilityInformation / Success

8.5.5.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a UECapabilityEnquiry message with rrc-SegAllowed-r16 enabled }

then { UE successfully segments UECapabilityInformation message at RRC layer and sends ULDedicatedMessageSegment messages with rrc-MessageSegmentType set accordingly for the first and last segment and rrc-MessageSegmentContainer containing the segments of UECapabilityInformation message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and having received UECapabilityEnquiry message with rrc-segAllowed-r16 enabled and having transmitted the firstSegment of UECapabilityInformation message within the ULDedicatedMessageSegment message }

ensure that {

when { UE detects radio link failure on expiry of timer T310 }

then { UE successfully completes RRC re-establishment procedure and discards the remaining segments of UECapabilityInformation message }

}

8.5.5.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.6.3, 5.6.22.2, 5.6.22.3 and 5.3.7.2. Unless otherwise stated these are Rel-16 requirements.

[TS 36.331, clause 5.6.3]

The UE shall:

1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 36.323 [8]:

2> initiate the UL message segment transfer procedure as specified in clause 5.6.22;

1> else:

2> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.6.22.2]

A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met:

1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and

1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 36.323 [8];

Upon initiating the procedure, the UE shall:

  1. initiate transmission of the ULDedicatedMessageSegment message as specified in 5.6.22.3;

[TS 36.331, clause 5.6.22.3]

The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 36.323 [8]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows:

1> For each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment;

1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber;

1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:

2> set the rrc-MessageSegmentType to lastSegment;

1> else:

2> set the rrc-MessageSegmentType to notLastSegment;

1> submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.

[TS 36.331, clause 5.3.7.2]

Upon initiation of the procedure, the UE shall:

1> if UE is not configured with conditionalReconfiguration:

2> release uplinkDataCompression, if configured;

2> suspend all RBs, including RBs configured with NR PDCP, except SRB0;

2> reset MAC;

8.5.5.1.3 Test description

8.5.5.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) according to [18].

8.5.5.1.3.2 Test procedure sequence

Table 8.5.5.1.3.2-1: Power levels

Parameter

Unit

Cell 1

T1

Cell-specific RS RPRE

dBm/15kHz

“Off”

T2

Cell-specific RS RPRE

dBm/15kHz

-85

Table 8.5.5.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a UECapabilityEnquiry message including eutra to enquire max capability and with rrc-segAllowed-r16 set to enabled.

<–

UECapabilityEnquiry

EXCEPTION: Steps 2a1 to 2b7 describe behaviour that depends on the size of UEs capability container; the "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message.

IF UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then step 2a1 will be performed else steps 2b1 to 2b7 will be performed.

EXCEPTION: Step 2a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the ULDedicatedMessageSegment message indicate rrc-MessageSegmentType-r16 = lastSegment.

2a1

Check: Does the UE send segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message?

NOTE: The SS shall ensure that the concatenated segments decode into a valid UECapabilityInformation message (specific capability content is not checked).

–>

ULDedicatedMessageSegment

1

P

2b1

The UE sends UECapabilityInformation Message.

–>

UECapabilityInformation

3a1-4a11

Void

2b2

The SS transmits a SET UL MESSAGE REQUEST message.

<–

SET UL MESSAGE REQUEST

2b3

The UE transmits a SET UL MESSAGE RESPONSE message.

–>

SET UL MESSAGE RESPONSE

2b4

The SS transmits a UECapabilityEnquiry message with rrc-segAllowed-r16 set to enabled.

<–

UECapabilityEnquiry

EXCEPTION: Step 2b5 is repeated a maximum of 2 times.

2b5

Check: Does the UE send segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message?

NOTE: The SS shall ensure that the concatenated segments decode into a valid UECapabilityInformation message (specific capability content is not checked).

–>

ULDedicatedMessageSegment

1

P

2b6

The SS transmits a SET UL MESSAGE REQUEST message.

<–

SET UL MESSAGE REQUEST

2b7

The UE transmits a SET UL MESSAGE RESPONSE message.

–>

SET UL MESSAGE RESPONSE

3

SS stops regular grant transmission upon scheduling request.

4

The SS transmits a UECapabilityEnquiry message to enquire max capability and with rrc-segAllowed-r16 set to enabled.

<–

UECapabilityEnquiry

5

The SS transmits periodic grant from 15 (FDD)/18 (TDD) subframes after successful completion of step 4 to schedule PUSCH till the ULDedicatedMessageSegment at step 6 is received.

6

The UE sends 1st segment of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message.

–>

ULDedicatedMessageSegment

7

The SS changes Cell 1 parameters according to the row "T1" in table 8.5.5.1.3.2-1 in order that the radio link quality of Cell 1 is degraded.

8

Wait for T310 to expire

9

The SS changes Cell 1 parameters according to the row "T2" in table 8.5.5.1.3.2-1.

10

The UE sends an RRCConnectionReestablishmentRequest message on Cell 1.

–>

RRCConnectionReestablishmentRequest

11

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation on Cell 1.

<–

RRCConnectionReestablishment

12

The UE transmits an

RRCConnectionReestablishmentComplete message on Cell 1?

–>

RRCConnectionReestablishmentComplete

13

SS resumes regular UL grant transmission.

14

Check: Upon successful completion of RRC re-establishment procedure, does the UE discards remaining segments of UECapabilityInformation message and does not send any ULDedicatedMessageSegment message in the next 5 seconds?

2

P

8.5.5.1.3.3 Specific message contents

Table 8.5.5.1.3.3-1: UECapabilityEnquiry (steps 1, 2b4, 4, Table 8.5.5.1.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-22

Information Element

Value/remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF RAT TYPE {

RAT-Type [1]

eutra

}

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension

Not present

nonCriticalExtension SEQUENCE {

requestedFrequencyBands-r11 SEQUENCE {

n entries, where n is

equal to UE supported

bands or 16 if number of

UE supported bands

exceeds 16.

FreqBandIndicator-r11 [1]

px_ePrimaryFrequencyBand

E-UTRA primary frequency band under test.

FreqBandIndicator-r11 [k]

For k=2 to n set to value

different from values set

in preceding entries

FreqBandIndicator-r11

[1] to FreqBandIndicatorr11 [k-1]

Frequency bands supported by UE. Any value β such that pc_eBandβ_Supp is TRUE

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rrc-SegAllowed-r16

enabled

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.5.5.1.3.3-2: ULDedicatedMessageSegment (steps 2a1, 2b5 and step 6, Table 8.5.5.1.3.2-2)

Derivation Path: 36.508 [18], Table 4.6.1-22A

Information Element

Value/remark

Comment

Condition

ULDedicatedMessageSegment-r16 ::= SEQUENCE {

criticalExtensions CHOICE {

ulDedicatedMessageSegment-r16 SEQUENCE {

segmentNumber-r16

0 for first segment, and incremented by 1 for each subsequent segment

rrc-MessageSegmentContainer-r16

Not Checked

OCTET STRING including a segment of the encoded DL DCCH message

rrc-MessageSegmentType-r16

notLastSegment for all segments except the last segment.

lastSegment for the last segment

lateNonCriticalExtension

Not present

nonCriticalExtension

Not present

}

}

}

Table 8.5.5.1.3.3-3: RRCConnectionReestablishmentRequest (step 11, Table 8.5.5.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-13

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishmentRequest ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionReestablishmentRequest-r8 SEQUENCE {

ue-Identity SEQUENCE {

c-RNTI

the value of the C-RNTI of the UE

physCellId

PhysicalCellIdentity of Cell 1

shortMAC-I

The same value as the 16 least significant bits of the XMAC-I value calculated by SS

}

reestablishmentCause

otherFailure

}

}

}