8.2.2 Radio resource reconfiguration

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.2.2.1 RRC connection reconfiguration / Radio resource reconfiguration / Success

8.2.2.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a radioResourceConfigDedicated with SRB, DRB, transport channel and physical channel reconfiguration }

then { UE reconfigures the data and signalling radio bearers and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.3.5.3, 5.3.10.1, 5.3.10.3, 5.3.10.4 and 5.3.10.6.

The following represent an extraction of the requirements relevant to the test purpose.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

  1. if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

1> else:

2> If the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.1]

The UE shall:

1> for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration (SRB reconfiguration):

2> reconfigure the RLC entity in accordance with the received rlc-Config;

2> reconfigure the DCCH logical channel in accordance with the received logicalChannelConfig;

[TS 36.331, clause 5.3.10.3]

1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration (DRB reconfiguration):

2> if the pdcp-Config is included:

3> reconfigure the PDCP entity in accordance with the received pdcp-Config;

2> if the rlc-Config is included:

3> reconfigure the RLC entity or entities in accordance with the received rlc-Config;

2> if the logicalChannelConfig is included:

3> reconfigure the DTCH logical channel in accordance with the received logicalChannelConfig;

NOTE: Removal and addition of the same drb-Identity in single radioResourceConfiguration is not supported.

[TS 36.331, clause 5.3.10.4]

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

1> reconfigure the physical channel configuration in accordance with the received physicalConfigDedicated;

8.2.2.1.3 Test description

8.2.2.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].

– The condition SRB2-DRB(2, 0) is used for step 8 in 4.5.3.3 according to [18].

8.2.2.1.3.2 Test procedure sequence

Table 8.2.2.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a radioResourceConfigDedicated with SRBs, DRB, transport channel and physical channel reconfiguration.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

3

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

1

8.2.2.1.3.3 Specific message contents

Table 8.2.2.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.1.3.2-1)

Derivation Path: 36.508 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-RECONFIG

}

}

}

}

Table 8.2.2.1.3.3-2: RadioResourceConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated ::= SEQUENCE {

srb-ToAddModList

SRB-ToAddModList-RECONFIG

TS 36.508 Table 4.6.3-22A

drb-ToAddModList

DRB-ToAddModList-RECONFIG

TS 36.508 Table 4.6.3-2A

drb-ToReleaseList

Not present

mac-MainConfig CHOICE {

explicitValue

MAC-MainConfig-RECONFIG

}

sps-Config

Not present

physicalConfigDedicated

PhysicalConfigDedicated-RECONFIG

}

Table 8.2.2.1.3.3-3: MAC-MainConfig-RECONFIG (Table 8.2.2.1.3.3-2)

Derivation Path: 36.508 table 4.8.2.1.5-1

Information Element

Value/remark

Comment

Condition

MAC-MainConfig ::= SEQUENCE {

ul-SCH-Config SEQUENCE {

periodicBSR-Timer

sf32

retxBSR-Timer

sf2560

}

phr-Config CHOICE {

setup SEQUENCE {

periodicPHR-Timer

sf1000

prohibitPHR-Timer

sf500

}

}

}

Table 8.2.2.1.3.3-4: PhysicalConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-2)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated ::= SEQUENCE {

pdsch-ConfigDedicated

PDSCH-ConfigDedicated-RECONFIG

pucch-ConfigDedicated

Not present

pusch-ConfigDedicated

Not present

uplinkPowerControlDedicated

Not present

tpc-PDCCH-ConfigPUCCH

Not present

tpc-PDCCH-ConfigPUSCH

Not present

cqi-ReportConfig

Not present

soundingRsUL-ConfigDedicated

Not present

antennaInfo CHOICE {

defaultValue

NULL

}

schedulingRequestConfig

Not present

}

Table 8.2.2.1.3.3-5: PDSCH-ConfigDedicated-RECONFIG (Table 8.2.2.1.3.3-4)

Derivation Path: 36.508 table 4.6.3-6

Information Element

Value/remark

Comment

Condition

PDSCH-ConfigDedicated ::= SEQUENCE {

p-a

dB1

}

8.2.2.2 RRC connection reconfiguration / SRB/DRB reconfiguration / Success

8.2.2.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing SRB reconfiguration }

then { UE reconfigures affected SRBs and sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing DRB reconfiguration }

then { UE reconfigures affected DRBs and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.1 and 5.3.10.3.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3>perform the Radio resource configuration procedure as specified in 5.3.10;

[TS 36.331, clause 5.3.10.1]

The UE shall:

1> for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration (SRB reconfiguration):

2> reconfigure the RLC entity in accordance with the received rlc-Config;

2> reconfigure the DCCH logical channel in accordance with the received logicalChannelConfig;

[TS 36.331, clause 5.3.10.3]

The UE shall:

1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration (DRB reconfiguration):

2> if the pdcp-Config is included:

3> reconfigure the PDCP entity in accordance with the received pdcp-Config;

2> if the rlc-Config is included:

3> reconfigure the RLC entity or entities in accordance with the received rlc-Config;

2> if the logicalChannelConfig is included:

3> reconfigure the DTCH logical channel in accordance with the received logicalChannelConfig;

NOTE: Removal and addition of the same drb-Identity in single radioResourceConfiguration is not supported.

8.2.2.2.3 Test Description

8.2.2.2.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].

– The condition SRB2-DRB(2, 0) is used for step 8 in 4.5.3.3 according to [8].

8.2.2.2.3.2 Test procedure sequence

Table 8.2.2.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRConnectionReconfiguration message containing a radioResourceConfigDedicated with SRB reconfiguration.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

3

SS transmits RRCConnectionReconfiguration message containing a radioResourceConfigDedicated with DRB reconfiguration.

<–

RRCConnectionReconfiguration

4

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

2

P

8.2.2.2.3.3 Specific message contents

Table 8.2.2.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.2.3.2-1)

Derivation Path: 36.508 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-SRBRECONFIG

}

}

}

}

Table 8.2.2.2.3.3-2: RadioResourceConfigDedicated-SRBRECONFIG (Table 8.2.2.2.3.3-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated ::= SEQUENCE {

srb-ToAddModList

SRB-ToAddModList-RECONFIG

TS 36.508 Table 4.6.3-22A

drb-ToAddModList

Not present

drb-ToReleaseList

Not present

mac-MainConfig

Not present

sps-Config

Not present

physicalConfigDedicated

Not present

}

Table 8.2.2.2.3.3-3: RRCConnectionReconfiguration (step 3, Table 8.2.2.2.3.2-1)

Derivation Path: 36.508 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-DRBRECONFIG

}

}

}

}

Table 8.2.2.2.3.3-4: RadioResourceConfigDedicated-DRBRECONFIG (Table 8.2.2.2.3.3-3)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated ::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList

DRB-ToAddModList-RECONFIG

TS 36.508 Table 4.6.3-2A

drb-ToReleaseList

Not present

mac-MainConfig

Not present

sps-Config

Not present

physicalConfigDedicated

Not present

}

Table 8.2.2.2.3.3-5: Void

Table 8.2.2.2.3.3-6: Void

8.2.2.3 CA / RRC connection reconfiguration / SCell addition/modification/release / Success

8.2.2.3.1 CA / RRC connection reconfiguration / SCell addition/modification/release / Success / Intra-band Contiguous CA

8.2.2.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with a SCell addition }

then { UE adds the new SCell, configures lower layers to consider the SCell to be in deactivated state and sends an RRCConnectionReconfigurationComplete message within 25 (FDD)/28 (TDD) subframes }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with SCell modification }

then { UE modifies the affected SCell dedicated configurations and sends an RRCConnectionReconfigurationComplete message }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToReleaseList with a sCellIndex equling to one of the current UE SCell configuration }

then { UE releases this SCell and sends an RRCConnectionReconfigurationComplete message within 25 (FDD)/28 (TDD) subframes }

}

8.2.2.3.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.3a, 5.3.10.3b and 11.2. Unless otherwise stated these are Rel-10 requirements.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3a]

The UE shall:

1> if the release is triggered by reception of the sCellToReleaseList:

2> for each sCellIndex value included in the sCellToReleaseList:

3> if the current UE configuration includes an SCell with value sCellIndex:

4> release the SCell;

1> if the release is triggered by RRC connection re-establishment:

2> release all SCells that are part of the current UE configuration;

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the received radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell;

2> configure lower layers to consider the SCell to be in deactivated state;

1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the received radioResourceConfigDedicatedSCell;

[TS 36.331, clause 11.2]

The UE performance requirements for RRC procedures are specified in the following table, by means of a value N:

N = the number of 1ms subframes from the end of reception of the E-UTRAN -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> E-UTRAN response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation) where N=20 (Ref. TS 36.331 Fig. 11.2-1).

8.2.2.3.1.3 Test Description

8.2.2.3.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

8.2.2.3.1.3.2 Test procedure sequence

Table 8.2.2.3.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-4

Void

5

The SS transmits an RRCConnectionReconfiguration message containing an sCellToAddModList with SCell Cell 3 addition.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message within 25 (FDD)/28 (TDD) subframes?

–>

RRCConnectionReconfigurationComplete

1

P

7

The SS transmits an RRCConnectionReconfiguration message containing an sCellToAddModList with SCell Cell 3 modification.

<–

RRCConnectionReconfiguration

8

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

2

P

9

Void

10

Void

11

The SS transmits an RRCConnectionReconfiguration message containing an sCellToReleaseList with an sCellIndex equalling to the Cell 3 cell index in the current UE configuration.

<–

RRCConnectionReconfiguration

12

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message within 25 (FDD)/28 (TDD) subframes?

–>

RRCConnectionReconfigurationComplete

3

P

13

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

1

Note 1: The SS is configured for RRC procedure delay testing according to TS 36.523-3 clause 7.12.1.

Note 2: 5 (FDD) / 8 (TDD) subframes is added on top of RRC processing delay requirement, because  UL grant is allocated for the next subframe after RRC procedure delay and because of transmission delay after UL grant. For TDD, consider the max 7 TTI transmission delay after UL grant.

8.2.2.3.1.3.3 Specific message contents

Table 8.2.2.3.1.3.3-0: Conditions for specific message contents
in Tables 8.2.2.3.1.3.3-2 and 8.2.2.3.1.3.3-3, 8.2.2.3.1.3.3-7, 8.2.2.3.1.3.3-8 and 8.2.2.3.1.3.3-11

Condition

Explanation

Uplink_CA

The UE supports carrier aggregation in UL under the test band.

Band > 64

If band > 64 is selected

Table 8.2.2.3.1.3.3-1: RRCConnectionReconfiguration (step 5, Table 8.2.2.3.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 8.2.2.3.1.3.3-2: SCellToAddMod-r10-f2-Add (Table 8.2.2.3.1.3.3-5)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.2.3.1.3.3-3: RadioResourceConfigCommonSCell-r10-f2 (Table 8.2.2.3.1.3.3-6)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 3

}

Ul-Configuration-r10

Not present

ul-Configuration-r10 SEQUENCE {

Uplink_CA

ul-FreqInfo-r10 SEQUENCE {

ul-Bandwidth-r10

Same uplink system bandwidth as used for Cell 3

optional

FDD

Not present

TDD

additionalSpectrumEmissionSCell-r10

Same additionalSpectrumEmission as used for Cell 3

}

}

}

Table 8.2.2.3.1.3.3-4: RadioResourceConfigDedicatedSCell-r10-f2 (Table 8.2.2.3.1.3.3-6)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10 SEQUENCE {

ul-Configuration-r10

Not present

ul-Configuration-r10 SEQUENCE {

Uplink_CA

antennaInfoUL-r10

Not present

pusch-ConfigDedicatedSCell-r10

Not present

uplinkPowerControlDedicatedSCell-r10

UplinkPowerControlDedicatedSCell-r10-DEFAULT

cqi-ReportConfigSCell-r10

CQI-ReportConfigSCell-r10-DEFAULT

soundingRS-UL-ConfigDedicated-r10

Not present

soundingRS-UL-ConfigDedicated-v1020

Not present

soundingRS-UL-ConfigDedicatedAperiodic-r10

Not present

}

}

}

Table 8.2.2.3.1.3.3-5: RRCConnectionReconfiguration (step 7, Table 8.2.2.3.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig SEQUENCE {

measGapConfig CHOICE {

release

NULL

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

SCellToAddMod-r10-f2-Mod

SCell modification for Cell 3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 8.2.2.3.1.3.3-6: SCellToAddMod-r10-f2-Mod (Table 8.2.2.3.1.3.3-9)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10

1

cellIdentification-r10

Not present

radioResourceConfigCommonSCell-r10

Not present

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2-Mod

pc_FeatrGrp_102

}

Table 8.2.2.3.1.3.3-7: RadioResourceConfigDedicatedSCell-r10-f2-Mod (Table 8.2.2.3.1.3.3-10)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10 SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

antennaInfo-r10 SEQUENCE {

antennaPortsCount

an2

}

crossCarrierSchedulingConfig-r10

Not present

csi-RS-Config-r10

Not present

pdsch-ConfigDedicated-r10

Not present

}

ul-Configuration-r10

Not present

ul-Configuration-r10 SEQUENCE {

Uplink_CA

antennaInfoUL-r10 SEQUENCE {

transmissionModeUL-r10

tm1

fourAntennaPortActivated-r10

Not present

OP setup

}

pusch-ConfigDedicatedSCell-r10

PUSCH-ConfigDedicated-DEFAULT

uplinkPowerControlDedicatedSCell-r10

Not present

cqi-ReportConfigSCell-r10

Not present

soundingRS-UL-ConfigDedicated-r10

Not present

SoundingRS-UL-ConfigDedicated-Mod

pc_FeatrGrp_113

soundingRS-UL-ConfigDedicated-v1020

Not present

SoundingRS-UL-ConfigDedicated-v1020-Mod

pc_FeatrGrp_113

soundingRS-UL-ConfigDedicatedAperiodic-r10

Not present

}

}

}

Table 8.2.2.3.1.3.3-8: SoundingRS-UL-ConfigDedicated-Mod (Table 8.2.2.3.1.3.3-11)

Derivation Path: 36.508, Table 4.6.3-22

Information Element

Value/remark

Comment

Condition

SoundingRS-UL-ConfigDedicated ::= CHOICE{

setup SEQUENCE {

srs-Bandwidth

bw3

srs-HoppingBandwidth

hbw3

freqDomainPosition

0

duration

TRUE

srs-ConfigIndex

7

transmissionComb

0

cyclicShift

cs0

}

}

Table 8.2.2.3.1.3.3-9: SoundingRS-UL-ConfigDedicated-v1020-Mod (Table 8.2.2.3.1.3.3-11)

Derivation Path: 36.331, clause 6.3.2

Information Element

Value/remark

Comment

Condition

SoundingRS-UL-ConfigDedicated-v1020 ::= SEQUENCE {

srs-AntennaPort-r10

an1

}

Table 8.2.2.3.1.3.3-10: RRCConnectionReconfiguration (step 11, Table 8.2.2.3.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10 SEQUENCE (SIZE (1..maxSCell-r10) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

SCell release for Cell 3

}

sCellToAddModList-r10

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

8.2.2.3.2 CA / RRC connection reconfiguration / SCell addition/modification/release / Success / Inter-band CA

8.2.2.3.2.1 Test Purpose (TP)

Same as TC 8.2.2.3.1 but applied to Inter-band CA case.

8.2.2.3.2.2 Conformance requirements

Same as TC 8.2.2.3.1 but applied to Inter-band CA case.

8.2.2.3.2.3 Test description

8.2.2.3.2.3.1 Pre-test conditions

Same as test case 8.2.2.3.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Inactive SCell according to [18] cl. 6.3.4

8.2.2.3.2.3.2 Test procedure sequence

Same as test case 8.2.2.3.1 with the following differences:

– CA configuration: Inter-band CA replaces Inter-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3.

8.2.2.3.3 CA / RRC connection reconfiguration / SCell addition/ modification/release / Success / Intra-band non-contiguous CA

The scope and description of the present TC is the same as test case 8.2.2.3.1 with the following differences:

– CA configuration Intra-band non-contiguous CA replaces Intra-band Contiguous CA

8.2.2.4 CA / RRC connection reconfiguration / SCell SI change / Success

8.2.2.4.1 CA / RRC connection reconfiguration / SCell SI change / Success / Intra-band Contiguous CA

8.2.2.4.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with SCell(s) configured }

ensure that {

when { UE receives an RRCConnectionReconfiguration message including sCellToReleaseList and sCellToAddModList with the same concerned SCell to release and add, and with the change of the relevant system information of the configured SCell }

then { UE first releases the concerned SCell and then adds the concerned SCell, configures lower layers to consider the concerned SCell to be in deactivated state and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.4.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.2.1.1, clauses 5.3.5.3, 5.3.10.3a and 5.3.10.3b.

[TS 36.331, clause 5.2.1.1]

The UE applies the system information acquisition and change monitoring procedures for the PCell only. For an SCell, E-UTRAN provides, via dedicated signalling, all system information relevant for operation in RRC_CONNECTED when adding the SCell. Upon change of the relevant system information of a configured SCell, E-UTRAN releases and subsequently adds the concerned SCell, which may be done with a single RRCConnectionReconfiguration message.

NOTE 2: E-UTRAN may configure via dedicated signalling different parameter values than the ones broadcast in the concerned SCell.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3a]

The UE shall:

1> if the release is triggered by reception of the sCellToReleaseList:

2> for each sCellIndex value included in the sCellToReleaseList:

3> if the current UE configuration includes an SCell with value sCellIndex:

4> release the SCell;

1> if the release is triggered by RRC connection re-establishment:

2> release all SCells that are part of the current UE configuration;

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the received radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell;

2> configure lower layers to consider the SCell to be in deactivated state;

1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the received radioResourceConfigDedicatedSCell;

8.2.2.4.1.3 Test Description

8.2.2.4.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

8.2.2.4.1.3.2 Test procedure sequence

Table 8.2.2.4.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList with Cell 3 as SCell addition.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an RRCConnectionReconfiguration message containing a sCellToReleaseList with a SCell release and a sCellToAddModList with a SCell addition for SCell relevant system information changes, the SCellIndex-r10 in both IEs indicate the same SCell as configured in step 1.

<–

RRCConnectionReconfiguration

4

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

8.2.2.4.1.3.3 Specific message contents

Table 8.2.2.4.1.3.3-0: Conditions for specific message contents
in Tables 8.2.2.3.1.3.3-2, 8.2.2.4.1.3.3-3, 8.2.2.4.1.3.3-4, 8.2.2.3.1.3.3-6 and 8.2.2.4.1.3.3-7

Condition

Explanation

Uplink_CA

The UE supports carrier aggregation in UL under the test band.

Band > 64

If band > 64 is selected

Table 8.2.2.4.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.4.1.3.2-1)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 8.2.2.4.1.3.3-2: SCellToAddMod-r10-f2-Add (Table 8.2.2.4.1.3.3-1)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.2.4.1.3.3-3: RadioResourceConfigCommonSCell-r10-f2 (Table 8.2.2.4.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 3

}

ul-Configuration-r10

Not present

ul-Configuration-r10 SEQUENCE {

Uplink_CA

ul-FreqInfo-r10 SEQUENCE {

ul-Bandwidth-r10

Same uplink system bandwidth as used for Cell 3

optional

FDD

Not present

TDD

additionalSpectrumEmissionSCell-r10

Same additionalSpectrumEmission as used for Cell 3

}

}

}

Table 8.2.2.4.1.3.3-4: RadioResourceConfigDedicatedSCell-r10-f2 (Table 8.2.2.4.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10 SEQUENCE {

ul-Configuration-r10

Not present

ul-Configuration-r10 SEQUENCE {

Uplink_CA

antennaInfoUL-r10

Not present

pusch-ConfigDedicatedSCell-r10

Not present

uplinkPowerControlDedicatedSCell-r10

UplinkPowerControlDedicatedSCell-r10-DEFAULT

cqi-ReportConfigSCell-r10

CQI-ReportConfigSCell-r10-DEFAULT

soundingRS-UL-ConfigDedicated-r10

Not present

soundingRS-UL-ConfigDedicated-v1020

Not present

soundingRS-UL-ConfigDedicatedAperiodic-r10

Not present

}

}

}

Table 8.2.2.4.1.3.3-5: RRCConnectionReconfiguration (step 3, Table 8.2.2.4.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10 SEQUENCE (SIZE (1..maxSCell-r10) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

SCell release for Cell 3

}

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add-SIchange

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 8.2.2.4.1.3.3-6: SCellToAddMod-r10-f2-Add-SIchange (Table 8.2.2.4.1.3.3-5)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2-SIchange

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.2.4.1.3.3-7: RadioResourceConfigCommonSCell-r10-f2-SIchange (Table 8.2.2.4.1.3.3-6)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 3

antennaInfoCommon-r10 SEQUENCE {

antennaPortsCount

an1

}

}

ul-Configuration-r10

Not present

ul-Configuration-r10 SEQUENCE {

Uplink_CA

ul-FreqInfo-r10 SEQUENCE {

ul-Bandwidth-r10

Same uplink system bandwidth as used for Cell 3

optional

FDD

Not present

TDD

additionalSpectrumEmissionSCell-r10

Same additionalSpectrumEmission as used for Cell 3

}

}

}

8.2.2.4.2 CA / RRC connection reconfiguration / SCell SI change / Success / Inter-band CA

The scope and description of the present TC is the same as test case 8.2.2.4.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Inactive SCell according to [18] cl. 6.3.4

8.2.2.4.3 CA / RRC connection reconfiguration / SCell SI change / Success / Intra-band non-contiguous CA

The scope and description of the present TC is the same as test case 8.2.2.4.1 with the following differences:

– CA configuration Intra-band non-contiguous CA replaces Intra-band Contiguous CA

8.2.2.5 CA / RRC connection reconfiguration / SCell addition without UL / Success

8.2.2.5.1 CA / RRC connection reconfiguration / SCell addition without UL / Success / Intra-band Contiguous CA

8.2.2.5.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with SCell addition without UL carrier }

then { UE adds the new SCell and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.5.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.3b.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the received radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell;

2> configure lower layers to consider the SCell to be in deactivated state;

1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the received radioResourceConfigDedicatedSCell;

8.2.2.5.1.3 Test Description

8.2.2.5.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

8.2.2.5.1.3.2 Test procedure sequence

Table 8.2.2.5.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList with SCell Cell 3 addition without UL carrier.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

8.2.2.5.1.3.3 Specific message contents

Table 8.2.2.5.1.3.3-0: Condition for specific message contents in Table 8.2.2.5.1.3.3-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.2.5.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.5.1.3.2-1)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add

SCell addition for Cell 3 without UL carrier

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 8.2.2.5.1.3.3-2: SCellToAddMod-r10-f2-Add (Table 8.2.2.5.1.3.3-1)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.2.5.1.3.3-3: RadioResourceConfigCommonSCell-r10-f2 (Table 8.2.2.5.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 3

}

Ul-Configuration-r10

Not present

}

Table 8.2.2.5.1.3.3-4: RadioResourceConfigDedicatedSCell-r10-f2 (Table 8.2.2.5.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10 SEQUENCE {

ul-Configuration-r10

Not present

}

}

8.2.2.5.2 CA / RRC connection reconfiguration / SCell addition without UL / Success / Inter-band CA

The scope and description of the present TC is the same as test case 8.2.2.5.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

8.2.2.5.3 CA / RRC connection reconfiguration / SCell addition without UL / Success / Intra-band non-Contiguous CA

The scope and description of the present TC is the same as test case 8.2.2.5.1 with the following differences:

– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA

8.2.2.5a CA / RRC connection reconfiguration / TDD SCell addition without UL

8.2.2.5a.1 CA / RRC connection reconfiguration / TDD SCell addition without UL / SRS configuration / Periodic / multi-SRS switching

8.2.2.5a.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with a TDD SCell addition without UL carrier, and srs-SwitchFromServCellIndex is configured for the TDD SCell, and SoundingRS-UL-ConfigDedicated is configured for the TDD SCell for UL subframe as SRS trigger type 0.}

then { the UE transmit SRS on the TDD SCell periodically using the resource on UL subframe configured in SoundingRS-UL-ConfigDedicated }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList, and SoundingRS-UL-ConfigDedicated is configured for the TDD SCell for special subframe as SRS trigger type 0.}

then { the UE transmit SRS on the TDD SCell periodically using the resource on special subframe configured in SoundingRS-UL-ConfigDedicated }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList, and SoundingRS-UL-ConfigDedicated is configured for the TDD SCell for multi-symbols of special subframe as SRS trigger type 0.}

then { the UE transmit SRS on the TDD SCell periodically using the resource on multi-symbols of special subframe configured in SoundingRS-UL-ConfigDedicated }

}

8.2.2.5a.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.3b, TS 36.213, clause 8.2.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell, both included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> configure lower layers to consider the SCell to be in deactivated state;

2> for each measId included in the measIdList within VarMeasConfig:

3> if SCells are not applicable for the associated measurement; and

3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:

4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the radioResourceConfigDedicatedSCell, included either in the sCellToAddModList or in the sCellToAddModListSCG;

[TS 36.213, clause 8.2]

A UE shall transmit Sounding Reference Symbol (SRS) on per serving cell SRS resources based on two trigger types:

– trigger type 0: higher layer signalling

– trigger type 1: DCI formats 0/0A/0B/4/4A/4B/1A/6-0A/6-1A for FDD, TDD, and frame structure type 3 and DCI formats 2B/2C/2D/3B for TDD, and frame structure type 3.

A UE may be configured with SRS parameters for trigger type 0 and trigger type 1 on each serving cell. A BL/CE UE configured with CEModeB is not expected to be configured with SRS parameters for trigger type 0 and trigger type 1. The following SRS parameters are serving cell specific and semi-statically configurable by higher layers for trigger type 0 and for trigger type 1.

– Number of combs as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1, if configured

– srs-UpPtsAdd: two or four additional SC-FDMA symbols in UpPTS as defined in [11] for trigger type 0 and trigger type 1, if configured

– Transmission comb , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1

– Starting physical resource block assignment , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– duration: single or indefinite (until disabled), as defined in [11] for trigger type 0

– srs-ConfigIndex ISRS for SRS periodicity and SRS subframe offset , as defined in Table 8.2-1 and Table 8.2-2 for trigger type 0 and SRS periodicity and SRS subframe offset , as defined in Table 8.2-4 and Table 8.2-5 trigger type 1 for a serving cell that is not a LAA SCell

– SRS bandwidth , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– Frequency hopping bandwidth, , as defined in Subclause 5.5.3.2 of [3] for trigger type 0

– Cyclic shift , as defined in Subclause 5.5.3.1 of [3] for trigger type 0 and each configuration of trigger type 1

– Number of antenna ports for trigger type 0 and each configuration of trigger type 1

– SRS subframe for each configuration of trigger type 1 for a serving cell that is a LAA SCell and DCI format 4B

For a TDD serving cell,

– If the serving cell not configured for PUSCH/PUCCH transmission, or if the UE supports ce-srsEnhancement-r14

– For trigger type 0, the UE can be configured with more than one configuration of SoundingRS-UL-ConfigDedicatedUpPTsExt and/or SoundingRS-UL-ConfigDedicated, and the SRS parameters in each of the configurations shall be used.

– For trigger type 1, the UE can be configured with more than one configuration of SoundingRS-UL- ConfigDedicatedAperiodicUpPTsExt and/or SoundingRS-UL- ConfigDedicatedAperiodic, and the SRS parameters in each of the configurations shall be used.

For a TDD serving cell not configured for PUSCH/PUCCH transmission, and trigger type 1, a SRS request field [4] shall be included in DCI format 3B if the value of the higher layer parameter fieldTypeFormat3B is set to 3 or 4. If the UE is configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission, a single SRS request field is included in DCI format 3B for a set of the TDD serving cells without PUSCH/PUCCH transmission as given in Table 8.2-0C; otherwise one or more SRS request fields is included in DCI format 3B each corresponding to a TDD serving cell without PUSCH/PUCCH transmission as configured by higher layers. If the UE is configured with no more than 5 TDD serving cells without PUSCH/PUCCH transmission, and the UE does not support transmit antenna selection or multi-antenna transmission, the SRS request field [4] in DCI format 3B is 1-bit, 2-bits otherwise. For the 1-bit SRS request field [4] in DCI format 3B, a type 1 SRS is triggered if the value of the SRS request field is set to ‘1’ with SRS parameters, srs-ConfigApDCI-Format1a2b2c, configured by higher layer signalling. For the 2-bit SRS request field [4] in DCI format 3B, and UE configured with no more than 5 TDD serving cells without PUSCH/PUCCH transmission, the SRS request field indicates the SRS parameter set given in Table 8.1-1 with the three sets of SRS parameters, srs-ConfigApDCI-Format4, configured by higher layer signalling. For the 2-bit SRS request field [4] in Table 8.2-0C and DCI format 3B, and UE configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission, SRS parameters, srs-ConfigApDCI-Format1a2b2c, configured by higher layer signalling for the associated serving cell, is used if a type 1 SRS is triggered.

8.2.2.5a.1.3 Test description

8.2.2.5a.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

8.2.2.5a.1.3.2 Test procedure sequence

Table 8.2.2.5a.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList with SCell Cell 3 addition without UL carrier, and setup an SRS configuration on the last symbol of 4th subframe every radio frame in SCell Cell3.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

Check: Does the UE transmit SRS on the last symbol of 4th subframe every radio frame in SCell Cell3?

–>

SRS

1

P

4

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList to release the SRS configuration on 4th subframe and to setup an SRS configuration on the last symbol of the 1st UpPTS every radio frame in SCell Cell 3.

<–

RRCConnectionReconfiguration

5

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

6

Check: Does the UE transmit SRS on the last symbol of the 1st UpPTS every radio frame in SCell Cell3?

–>

SRS

2

P

7

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList to add a second SRS configuration on the second last symbol of the 1st UpPTS every radio frame in SCell Cell 3.

<–

RRCConnectionReconfiguration

8

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

9

Check: Does the UE transmit SRS on both 2 symbols of the 1st UpPTS every radio frame in SCell Cell3?

–>

SRS

3

P

8.2.2.5a.1.3.3 Specific message contents

Table 8.2.2.5a.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.5a.1.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.2.5a.1.3.3-2: SCellToAddMod-r10-DEFAULT (Table 8.2.2.5a.1.3.3-1)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D, condition SRS-Switching

Table 8.2.2.5a.1.3.3-3: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 8.2.2.5a.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-13A, condition SRS-Switching

Table 8.2.2.5a.1.3.3-4: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 8.2.2.5a.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A, condition SRS-Switching

Table 8.2.2.5a.1.3.3-5: SoundingRS-UL-ConfigDedicated-DEFAULT (Table 8.2.2.5a.1.3.3-4)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-22, condition TDD

Information Element

Value/remark

Comment

Condition

SoundingRS-UL-ConfigDedicated-DEFAULT ::= CHOICE {

setup SEQUENCE {

srs-ConfigIndex

18

INTEGER (0..1023) See Table 8.2-2 in TS 36.213

}

}

Table 8.2.2.5a.1.3.3-6: RRCConnectionReconfiguration (step 4, Table 8.2.2.5a.1.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.2.5a.1.3.3-7: SCellToAddMod-r10-DEFAULT (Table 8.2.2.5a.1.3.3-6)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D, condition SRS-Switching

Table 8.2.2.5a.1.3.3-8: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 8.2.2.5a.1.3.3-7)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-13A, condition SRS-Switching

Table 8.2.2.5a.1.3.3-9: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 8.2.2.5a.1.3.3-7)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A, condition SRS-Switching

Table 8.2.2.5a.1.3.3-10: SoundingRS-UL-ConfigDedicated-DEFAULT (Table 8.2.2.5a.1.3.3-9)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-22, condition TDD

Information Element

Value/remark

Comment

Condition

SoundingRS-UL-ConfigDedicated-DEFAULT ::= CHOICE {

setup SEQUENCE {

srs-ConfigIndex

16

INTEGER (0..1023) See Table 8.2-2 in TS 36.213

}

}

Table 8.2.2.5a.1.3.3-11: RRCConnectionReconfiguration (step 7, Table 8.2.2.5a.1.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.2.5a.1.3.3-12: SCellToAddMod-r10-DEFAULT (Table 8.2.2.5a.1.3.3-11)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D, condition SRS-Switching

Table 8.2.2.5a.1.3.3-13: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 8.2.2.5a.1.3.3-12)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-13A, condition SRS-Switching

Table 8.2.2.5a.1.3.3-14: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 8.2.2.5a.1.3.3-12)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A, condition SRS-Switching

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE {

soundingRS-UL-PeriodicConfigDedicatedList-r14 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

2 entries

soundingRS-UL-ConfigDedicated[1] CHOICE {

setup SEQUENCE {

srs-Bandwidth

bw0

srs-HoppingBandwidth

hbw0

freqDomainPosition

0

duration

TRUE

srs-ConfigIndex

15

Second last symbol of 1st UpPTS

transmissionComb

0

cyclicShift

cs0

}

soundingRS-UL-ConfigDedicated[2] CHOICE {

setup SEQUENCE {

srs-Bandwidth

bw0

srs-HoppingBandwidth

hbw0

freqDomainPosition

0

duration

TRUE

srs-ConfigIndex

16

Last symbol of 1st UpPTS

transmissionComb

0

cyclicShift

cs0

}

}

soundingRS-UL-PeriodicConfigDedicatedUpPTsExtList-r14

Not Present

soundingRS-UL-AperiodicConfigDedicatedList-r14

Not Present

soundingRS-UL-ConfigDedicatedApUpPTsExtList-r14

Not Present

}

8.2.2.5a.2 CA / RRC connection reconfiguration / TDD SCell addition without UL / SRS configuration / Aperiodic

8.2.2.5a.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with a TDD SCell addition without UL carrier, and srs-SwitchFromServCellIndex is configured for the TDD SCell, and SoundingRS-UL-AperiodicConfigDedicated is configured for the TDD SCell for UL subframe as SRS trigger type 1, and a SRS request is received in DCI 1A on the TDD SCell.}

then { the UE transmit SRS on the TDD SCell using the resource on UL subframe configured in SoundingRS-UL-AperiodicConfigDedicated }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex }

ensure that {

when { UE is configured with SoundingRS-UL-AperiodicConfigDedicated for the TDD SCell for UL subframe as SRS trigger type 1, and a SRS request is received in DCI 3B on the TDD SCell.}}

then { the UE transmit SRS on the TDD SCell using the resource on UL subframe configured in SoundingRS-UL-AperiodicConfigDedicated }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex }

ensure that {

when { UE is configured with SoundingRS-UL-AperiodicConfigDedicated for the TDD SCell for special subframe as SRS trigger type 1, and a SRS request is received in DCI 1A on the TDD SCell.}}

then { the UE transmit SRS on the TDD SCell using the resource on special subframe configured in SoundingRS-UL-AperiodicConfigDedicated }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex }

ensure that {

when { UE is configured with SoundingRS-UL-AperiodicConfigDedicated for the TDD SCell for special subframe as SRS trigger type 1, and a SRS request is received in DCI 3B on the TDD SCell.}}

then { the UE transmit SRS on the TDD SCell using the resource on special subframe configured in SoundingRS-UL-AperiodicConfigDedicated }

}

8.2.2.5a.2.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.3b, TS 36.213, clause 8.2.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell, both included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> configure lower layers to consider the SCell to be in deactivated state;

2> for each measId included in the measIdList within VarMeasConfig:

3> if SCells are not applicable for the associated measurement; and

3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:

4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the radioResourceConfigDedicatedSCell, included either in the sCellToAddModList or in the sCellToAddModListSCG;

[TS 36.213, clause 8.2]

A UE shall transmit Sounding Reference Symbol (SRS) on per serving cell SRS resources based on two trigger types:

– trigger type 0: higher layer signalling

– trigger type 1: DCI formats 0/0A/0B/4/4A/4B/1A/6-0A/6-1A for FDD, TDD, and frame structure type 3 and DCI formats 2B/2C/2D/3B for TDD, and frame structure type 3.

A UE may be configured with SRS parameters for trigger type 0 and trigger type 1 on each serving cell. A BL/CE UE configured with CEModeB is not expected to be configured with SRS parameters for trigger type 0 and trigger type 1. The following SRS parameters are serving cell specific and semi-statically configurable by higher layers for trigger type 0 and for trigger type 1.

– Number of combs as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1, if configured

– srs-UpPtsAdd: two or four additional SC-FDMA symbols in UpPTS as defined in [11] for trigger type 0 and trigger type 1, if configured

– Transmission comb , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1

– Starting physical resource block assignment , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– duration: single or indefinite (until disabled), as defined in [11] for trigger type 0

– srs-ConfigIndex ISRS for SRS periodicity and SRS subframe offset , as defined in Table 8.2-1 and Table 8.2-2 for trigger type 0 and SRS periodicity and SRS subframe offset , as defined in Table 8.2-4 and Table 8.2-5 trigger type 1 for a serving cell that is not a LAA SCell

– SRS bandwidth , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– Frequency hopping bandwidth, , as defined in Subclause 5.5.3.2 of [3] for trigger type 0

– Cyclic shift , as defined in Subclause 5.5.3.1 of [3] for trigger type 0 and each configuration of trigger type 1

– Number of antenna ports for trigger type 0 and each configuration of trigger type 1

– SRS subframe for each configuration of trigger type 1 for a serving cell that is a LAA SCell and DCI format 4B

For a TDD serving cell,

– If the serving cell not configured for PUSCH/PUCCH transmission, or if the UE supports ce-srsEnhancement-r14

– For trigger type 0, the UE can be configured with more than one configuration of SoundingRS-UL-ConfigDedicatedUpPTsExt and/or SoundingRS-UL-ConfigDedicated, and the SRS parameters in each of the configurations shall be used.

– For trigger type 1, the UE can be configured with more than one configuration of SoundingRS-UL- ConfigDedicatedAperiodicUpPTsExt and/or SoundingRS-UL- ConfigDedicatedAperiodic, and the SRS parameters in each of the configurations shall be used.

For trigger type 1 and DCI format 4/4A/4B three sets of SRS parameters, srs-ConfigApDCI-Format4, are configured by higher layer signalling. The 2-bit SRS request field [4] in DCI format 4/4A/4B indicates the SRS parameter set given in Table 8.1-1. For trigger type 1 and DCI format 0/0A/0B /6-0A, a single set of SRS parameters, srs-ConfigApDCI-Format0, is configured by higher layer signalling. For trigger type 1 and DCI formats 1A/2B/2C/2D/6-1A, a single common set of SRS parameters, srs-ConfigApDCI-Format1a2b2c, is configured by higher layer signalling. For a serving cell that is not a LAA SCell, the SRS request field is 1 bit [4] for DCI formats 0/1A/2B/2C/2D/6-0A/6-1A, with a type 1 SRS triggered if the value of the SRS request field is set to ‘1’. For a serving cell that is a LAA SCell, the SRS timing offset field is 3 bits [4] for DCI formats 1A/2B/2C/2D, with a type 1 SRS triggered if the value of the SRS timing offset field is not set to ‘000’. The SRS request field is 1 bit [4] for DCI formats 0A, with a type 1 SRS triggered if the value of the SRS request field is set to ‘1’. The 2-bit SRS request field [4] in DCI format 0B indicates the type 1 SRS triggering and PUSCH subframe (as determined in Subclause 8.0) with SRS as given in Table 8.2-0A.

For a TDD serving cell not configured for PUSCH/PUCCH transmission, and trigger type 1, a SRS request field [4] shall be included in DCI format 3B if the value of the higher layer parameter fieldTypeFormat3B is set to 3 or 4. If the UE is configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission, a single SRS request field is included in DCI format 3B for a set of the TDD serving cells without PUSCH/PUCCH transmission as given in Table 8.2-0C; otherwise one or more SRS request fields is included in DCI format 3B each corresponding to a TDD serving cell without PUSCH/PUCCH transmission as configured by higher layers. If the UE is configured with no more than 5 TDD serving cells without PUSCH/PUCCH transmission, and the UE does not support transmit antenna selection or multi-antenna transmission, the SRS request field [4] in DCI format 3B is 1-bit, 2-bits otherwise. For the 1-bit SRS request field [4] in DCI format 3B, a type 1 SRS is triggered if the value of the SRS request field is set to ‘1’ with SRS parameters, srs-ConfigApDCI-Format1a2b2c, configured by higher layer signalling. For the 2-bit SRS request field [4] in DCI format 3B, and UE configured with no more than 5 TDD serving cells without PUSCH/PUCCH transmission, the SRS request field indicates the SRS parameter set given in Table 8.1-1 with the three sets of SRS parameters, srs-ConfigApDCI-Format4, configured by higher layer signalling. For the 2-bit SRS request field [4] in Table 8.2-0C and DCI format 3B, and UE configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission, SRS parameters, srs-ConfigApDCI-Format1a2b2c, configured by higher layer signalling for the associated serving cell, is used if a type 1 SRS is triggered.

8.2.2.5a.2.3 Test description

8.2.2.5a.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

8.2.2.5a.2.3.2 Test procedure sequence

Table 8.2.2.5a.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList with SCell Cell 3 addition without UL carrier, and setup an aperiodic SRS configuration on the last symbol of 4th and 9th subframe of every radio frame in SCell Cell3.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an SRS request by using DCI format 1A on 1st subframe in one radio frame in SCell Cell3.

<–

DCI: (DCI Format 1A defined in TS 36.508 Table 4.3.6.1.3-1 with following exceptions: RBA()= 5, = 5, SRS request = ‘1’.)

4

Check: Does the UE transmit SRS on the last symbol of 9th subframe in the same radio frame in SCell Cell3?

–>

SRS

1

P

5

The SS transmits an SRS request by using DCI format 3B on 1st subframe in one radio frame in SCell Cell3.

<–

DCI: (DCI Format 3B defined in TS 36.508 Table 4.3.6.1.6A-1)

6

Check: Does the UE transmit SRS on the last symbol of 9th subframe in the same radio frame in SCell Cell3?

–>

SRS

2

P

7

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList to change the SRS configuration to the last symbol of the 2 UpPTSs every radio frame in SCell Cell 3.

<–

RRCConnectionReconfiguration

8

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

9

The SS transmits an SRS request by using

DCI format 1A on 1st subframe in one radio frame in SCell Cell3.

<–

DCI: (DCI Format 1A defined in TS 36.508 Table 4.3.6.1.3-1 with following exceptions: RBA()= 5, = 5, SRS request = ‘1’.)

10

Check: Does the UE transmit SRS on last symbol of the 2nd UpPTS in the same radio frame in SCell Cell3?

–>

SRS

3

P

11

The SS transmits an SRS request by using

DCI format 3B on 1st subframe in one radio frame in SCell Cell3.

<–

DCI: (DCI Format 3B defined in TS 36.508 Table 4.3.6.1.6A-1)

12

Check: Does the UE transmit SRS on last symbol of the 2nd UpPTS in the same radio frame in SCell Cell3?

–>

SRS

4

P

8.2.2.5a.2.3.3 Specific message contents

Table 8.2.2.5a.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.5a.2.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.2.5a.2.3.3-2: SCellToAddMod-r10-DEFAULT (Table 8.2.2.5a.2.3.3-1)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D, condition SRS-Switching

Table 8.2.2.5a.2.3.3-3: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 8.2.2.5a.2.3.3-2)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-13A, condition SRS-Switching

Table 8.2.2.5a.2.3.3-4: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 8.2.2.5a.2.3.3-2)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A, condition SRS-Switching

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE {

soundingRS-UL-AperiodicConfigDedicatedList-r14 SEQUENCE {

1 entry

soundingRS-AperiodicSet-r14[1] SEQUENCE {

srs-CC-SetIndexList-r14

Not present

soundingRS-UL-ConfigDedicatedAperiodic-r14 CHOICE {

setup SEQUENCE {

srs-ConfigIndexAp-r10

13

4th and 9th subframe every radio frame

srs-ConfigApDCI-Format4-r10

Not present

srs-ActivateAp-r10 CHOICE {

setup SEQUENCE {

srs-ConfigApDCI-Format0-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

srs-ConfigApDCI-Format1a2b2c-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

}

}

}

}

}

}

}

Table 8.2.2.5a.2.3.3-5: RRCConnectionReconfiguration (step 7, Table 8.2.2.5a.2.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.2.5a.2.3.3-6: SCellToAddMod-r10-DEFAULT (Table 8.2.2.5a.2.3.3-5)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D, condition SRS-Switching

Table 8.2.2.5a.2.3.3-7: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 8.2.2.5a.2.3.3-6)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-13A, condition SRS-Switching

Table 8.2.2.5a.2.3.3-8: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 8.2.2.5a.2.3.3-6)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A, condition SRS-Switching

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE {

soundingRS-UL-AperiodicConfigDedicatedList-r14 SEQUENCE {

1 entry

soundingRS-AperiodicSet-r14[1] SEQUENCE {

srs-CC-SetIndexList-r14

Not present

soundingRS-UL-ConfigDedicatedAperiodic-r14 CHOICE {

setup SEQUENCE {

srs-ConfigIndexAp-r10

11

Last symbol of every UpPTS

srs-ConfigApDCI-Format4-r10

Not present

srs-ActivateAp-r10 CHOICE {

setup SEQUENCE {

srs-ConfigApDCI-Format0-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

srs-ConfigApDCI-Format1a2b2c-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

}

}

}

}

}

}

}

8.2.2.5a.3 CA / RRC connection reconfiguration / TDD SCell addition without UL / SRS configuration / Collision handling / Priority

8.2.2.5a.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED }

ensure that {

when { UE in configured with SRS trigger type 0 in PCell, and UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with a TDD SCell addition without UL carrier, and srs-SwitchFromServCellIndex is configured for the TDD SCell, and SoundingRS-UL-ConfigDedicated is configured for the TDD SCell for UL subframe as SRS trigger type 0, and the SRS transmission in PCell overlaps in the same symbol with SRS transmission in TDD SCell }

then { the UE transmit SRS in TDD SCell, but doesn’t transmit SRS in PCell }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex }

ensure that {

when { UE receives a MAC PDU retransmission for DRB in PCell, and corresponding HARQ-ACK transmission overlaps in the same symbol with the SRS transmission in TDD SCell }

then { the UE transmit HARQ-ACK in PCell, but doesn’t transmit SRS in TDD SCell }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex }

ensure that {

when { UE receives UL grant triggering the aperiodic CSI reporting in PCell, and corresponding CSI reporting overlaps in the same symbol with the SRS transmission type 0 in TDD SCell }

then { the UE transmit aperiodic CSI reporting in PCell, but doesn’t transmit SRS in TDD SCell }

}

8.2.2.5a.3.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.3b, TS 36.213, clause 8.2.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell, both included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> configure lower layers to consider the SCell to be in deactivated state;

2> for each measId included in the measIdList within VarMeasConfig:

3> if SCells are not applicable for the associated measurement; and

3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:

4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the radioResourceConfigDedicatedSCell, included either in the sCellToAddModList or in the sCellToAddModListSCG;

[TS 36.213, clause 8.2]

A UE shall transmit Sounding Reference Symbol (SRS) on per serving cell SRS resources based on two trigger types:

– trigger type 0: higher layer signalling

– trigger type 1: DCI formats 0/0A/0B/4/4A/4B/1A/6-0A/6-1A for FDD, TDD, and frame structure type 3 and DCI formats 2B/2C/2D/3B for TDD, and frame structure type 3.

A UE may be configured with SRS parameters for trigger type 0 and trigger type 1 on each serving cell. A BL/CE UE configured with CEModeB is not expected to be configured with SRS parameters for trigger type 0 and trigger type 1. The following SRS parameters are serving cell specific and semi-statically configurable by higher layers for trigger type 0 and for trigger type 1.

– Number of combs as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1, if configured

– srs-UpPtsAdd: two or four additional SC-FDMA symbols in UpPTS as defined in [11] for trigger type 0 and trigger type 1, if configured

– Transmission comb , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1

– Starting physical resource block assignment , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– duration: single or indefinite (until disabled), as defined in [11] for trigger type 0

– srs-ConfigIndex ISRS for SRS periodicity and SRS subframe offset , as defined in Table 8.2-1 and Table 8.2-2 for trigger type 0 and SRS periodicity and SRS subframe offset , as defined in Table 8.2-4 and Table 8.2-5 trigger type 1 for a serving cell that is not a LAA SCell

– SRS bandwidth , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– Frequency hopping bandwidth, , as defined in Subclause 5.5.3.2 of [3] for trigger type 0

– Cyclic shift , as defined in Subclause 5.5.3.1 of [3] for trigger type 0 and each configuration of trigger type 1

– Number of antenna ports for trigger type 0 and each configuration of trigger type 1

– SRS subframe for each configuration of trigger type 1 for a serving cell that is a LAA SCell and DCI format 4B

For a TDD serving cell,

– If the serving cell not configured for PUSCH/PUCCH transmission, or if the UE supports ce-srsEnhancement-r14

– For trigger type 0, the UE can be configured with more than one configuration of SoundingRS-UL-ConfigDedicatedUpPTsExt and/or SoundingRS-UL-ConfigDedicated, and the SRS parameters in each of the configurations shall be used.

– For trigger type 1, the UE can be configured with more than one configuration of SoundingRS-UL- ConfigDedicatedAperiodicUpPTsExt and/or SoundingRS-UL- ConfigDedicatedAperiodic, and the SRS parameters in each of the configurations shall be used.

For trigger type 1 and DCI format 4/4A/4B three sets of SRS parameters, srs-ConfigApDCI-Format4, are configured by higher layer signalling. The 2-bit SRS request field [4] in DCI format 4/4A/4B indicates the SRS parameter set given in Table 8.1-1. For trigger type 1 and DCI format 0/0A/0B /6-0A, a single set of SRS parameters, srs-ConfigApDCI-Format0, is configured by higher layer signalling. For trigger type 1 and DCI formats 1A/2B/2C/2D/6-1A, a single common set of SRS parameters, srs-ConfigApDCI-Format1a2b2c, is configured by higher layer signalling. For a serving cell that is not a LAA SCell, the SRS request field is 1 bit [4] for DCI formats 0/1A/2B/2C/2D/6-0A/6-1A, with a type 1 SRS triggered if the value of the SRS request field is set to ‘1’. For a serving cell that is a LAA SCell, the SRS timing offset field is 3 bits [4] for DCI formats 1A/2B/2C/2D, with a type 1 SRS triggered if the value of the SRS timing offset field is not set to ‘000’. The SRS request field is 1 bit [4] for DCI formats 0A, with a type 1 SRS triggered if the value of the SRS request field is set to ‘1’. The 2-bit SRS request field [4] in DCI format 0B indicates the type 1 SRS triggering and PUSCH subframe (as determined in Subclause 8.0) with SRS as given in Table 8.2-0A.

For a TDD serving cell not configured for PUSCH/PUCCH transmission, and trigger type 1, a SRS request field [4] shall be included in DCI format 3B if the value of the higher layer parameter fieldTypeFormat3B is set to 3 or 4. If the UE is configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission, a single SRS request field is included in DCI format 3B for a set of the TDD serving cells without PUSCH/PUCCH transmission as given in Table 8.2-0C; otherwise one or more SRS request fields is included in DCI format 3B each corresponding to a TDD serving cell without PUSCH/PUCCH transmission as configured by higher layers. If the UE is configured with no more than 5 TDD serving cells without PUSCH/PUCCH transmission, and the UE does not support transmit antenna selection or multi-antenna transmission, the SRS request field [4] in DCI format 3B is 1-bit, 2-bits otherwise. For the 1-bit SRS request field [4] in DCI format 3B, a type 1 SRS is triggered if the value of the SRS request field is set to ‘1’ with SRS parameters, srs-ConfigApDCI-Format1a2b2c, configured by higher layer signalling. For the 2-bit SRS request field [4] in DCI format 3B, and UE configured with no more than 5 TDD serving cells without PUSCH/PUCCH transmission, the SRS request field indicates the SRS parameter set given in Table 8.1-1 with the three sets of SRS parameters, srs-ConfigApDCI-Format4, configured by higher layer signalling. For the 2-bit SRS request field [4] in Table 8.2-0C and DCI format 3B, and UE configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission, SRS parameters, srs-ConfigApDCI-Format1a2b2c, configured by higher layer signalling for the associated serving cell, is used if a type 1 SRS is triggered.

If a UE is not configured with multiple TAGs and the UE is not configured with the parameter srs-UpPtsAdd for trigger type 1, or if a UE is not configured with multiple TAGs and the UE is not configured with more than one serving cell of different CPs, the UE shall not transmit SRS whenever SRS transmission on any serving cells and PUCCH transmission carrying HARQ-ACK and/or positive SR using normal PUCCH format as defined in Subclauses 5.4.1 and 5.4.2A of [3] happen to coincide in the same subframe.

For a TDD serving cell d not configured for PUSCH/PUCCH transmission, denote as s0(d) the corresponding serving cell whose UL transmissions may be interrupted as signalled by srs-SwitchFromServCellIndex. Define the set S(d)= {s0(d)… sN-1(d)} as the set of serving cells that meet the all the following conditions:

– {s0(d)… sN-1(d)} are in the same band as s0(d).

– {s0(d)… sN-1(d)} have the same CP as s0(d).

– {s0(d)… sN-1(d)} are in the same TAG as s0(d).

The following prioritization rules shall be applied when transmitting SRS over serving cell d when the simultaneous transmission of SRS and other signal/channel would result in uplink transmissions beyond the UE’s indicated uplink carrier aggregation capability included in the UE-EUTRA-Capability [12]:

– If PUSCH/PUCCH transmission carrying HARQ-ACK/positive SR/RI/PTI/CRI and/or PRACH on a serving cell in set S(d) overlaps in the same symbol with the SRS transmission (including any interruption due to uplink or downlink RF retuning time [10]) on serving cell d, then the UE shall not transmit SRS. Otherwise,

– if PUSCH transmission carrying aperiodic CSI on a serving cell in set S(d) overlaps in the same symbol with the SRS transmission (including any interruption due to uplink or downlink RF retuning time [10]) in serving cell d, and if the SRS transmission is a type 0 SRS transmission, then the UE shall not transmit the type 0 SRS. Otherwise,

– if PUSCH transmission on a serving cell in set S(d) overlaps in more than one symbol with the SRS transmission (including any interruption due to uplink or downlink RF retuning time [10]) in serving cell d, then the UE shall drop the PUSCH transmission. If PUCCH/SRS transmission on a serving cell in set S(d) overlaps in the same symbol with the SRS transmission (including any interruption due to uplink or downlink RF retuning time [10]) on serving cell d, the UE shall drop the PUCCH/SRS transmission.

8.2.2.5a.3.3 Test description

8.2.2.5a.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

8.2.2.5a.3.3.2 Test procedure sequence

Table 8.2.2.5a.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message.

The RRCConnectionReconfiguration contains sCellToAddModList with SCell Cell 3 addition without UL carrier, and setup a periodic SRS configuration on the last symbol of 4th subframe of every radio frame in SCell Cell 3.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

Check: Does the UE transmit SRS in PCell Cell 1 on the last symbol of 4th subframe in radio frame k1? (Note 1)

–>

SRS

1

F

4

Check: Does the UE transmit SRS in SCell Cell 3 on the last symbol of 4th subframe in radio frame k1? (Note 1)

–>

SRS

1

P

5

The SS indicates a new transmission on PDCCH and transmits a MAC PDU (containing an RLC PDU) in PCell Cell 1 on 10th subframe of radio frame k2, with content set so that UE could not successfully decode the data from its soft buffer.

<–

MAC PDU

6

Check: Does the UE transmit a HARQ NACK in PCell Cell 1 on 4th subframe of radio frame k2+1?

–>

HARQ NACK

2

P

7

Check: Does the UE transmit SRS on the last symbol of 4th subframe of radio frame k2+1 in SCell Cell3?

–>

SRS

2

F

8

After 1 second of step 5, the SS sends an UL grant to trigger aperiodic CSI reporting in PCell Cell 1 on 10th subframe of radio frame k3.

<–

(UL Grant)

9

Check: Does the UE perform aperiodical CQI reporting in PCell Cell 1 on 4th subframe of radio frame k3+1?

–>

(CQI)

3

P

10

Check: Does the UE transmit SRS on the last symbol of 4th subframe of radio frame k3+1 in SCell Cell3?

–>

SRS

3

F

Note 1: Radio frame k1 is randomly selected after step 2.

8.2.2.5a.3.3.3 Specific message contents

Table 8.2.2.5a.3.3.3-1: RRCConnectionReconfiguration (Preamble)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 ::= SEQUENCE {

radioResourceConfigDedicated ::= SEQUENCE {

physicalConfigDedicated ::= SEQUENCE {

soundingRS-UL-ConfigDedicated ::= CHOICE {

setup SEQUENCE {

srs-ConfigIndex

5

See Table 8.2-1 in TS 36.213

FDD

13

INTEGER (0..1023) See Table 8.2-2 in TS 36.213

TDD

}

}

}

}

}

}

}

}

Table 8.2.2.5a.3.3.3-2: RRCConnectionReconfiguration (step 1, Table 8.2.2.5a.3.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.2.5a.3.3.3-3: SCellToAddMod-r10-DEFAULT (Table 8.2.2.5a.3.3.3-2)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D, condition SRS-Switching

Table 8.2.2.5a.3.3.3-4: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 8.2.2.5a.3.3.3-3)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-13A, condition SRS-Switching

Table 8.2.2.5a.3.3.3-5: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 8.2.2.5a.3.3.3-3)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A, condition SRS-Switching

Table 8.2.2.5a.3.3.3-6: SoundingRS-UL-ConfigDedicated-DEFAULT (Table 8.2.2.5a.3.3.3-5)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-22, condition TDD

Information Element

Value/remark

Comment

Condition

SoundingRS-UL-ConfigDedicated-DEFAULT ::= CHOICE {

setup SEQUENCE {

srs-ConfigIndex

18

INTEGER (0..1023) See Table 8.2-2 in TS 36.213

}

}

8.2.2.5a.4 CA / RRC connection reconfiguration / TDD SCell addition without UL / SRS configuration / Collision handling / flexible SRS transmitting

8.2.2.5a.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with a TDD SCell without UL carrier and configured with srs-SwitchFromServCellIndex }

ensure that {

when { UE is configured with soundingRS-FlexibleTiming-r14 and UE is configured with SoundingRS-UL-AperiodicConfigDedicated for the TDD SCell for UL subframe as SRS trigger type 1, and a SRS request is received in DCI 3B on the TDD SCell, and the SRS transmission in subframe n+k happens to overlap with a HARQ-ACK transmission }

then { the UE transmit SRS in a later subframe n+k+l, where l=max(5, TSRS,1) }

}

8.2.2.5a.4.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.3b, TS 36.213, clause 8.2.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell, both included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> configure lower layers to consider the SCell to be in deactivated state;

2> for each measId included in the measIdList within VarMeasConfig:

3> if SCells are not applicable for the associated measurement; and

3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:

4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the radioResourceConfigDedicatedSCell, included either in the sCellToAddModList or in the sCellToAddModListSCG;

[TS 36.213, clause 8.2]

A UE shall transmit Sounding Reference Symbol (SRS) on per serving cell SRS resources based on two trigger types:

– trigger type 0: higher layer signalling

– trigger type 1: DCI formats 0/0A/0B/4/4A/4B/1A/6-0A/6-1A for FDD, TDD, and frame structure type 3 and DCI formats 2B/2C/2D/3B for TDD, and frame structure type 3.

A UE may be configured with SRS parameters for trigger type 0 and trigger type 1 on each serving cell. A BL/CE UE configured with CEModeB is not expected to be configured with SRS parameters for trigger type 0 and trigger type 1. The following SRS parameters are serving cell specific and semi-statically configurable by higher layers for trigger type 0 and for trigger type 1.

– Number of combs as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1, if configured

– srs-UpPtsAdd: two or four additional SC-FDMA symbols in UpPTS as defined in [11] for trigger type 0 and trigger type 1, if configured

– Transmission comb , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1

– Starting physical resource block assignment , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– duration: single or indefinite (until disabled), as defined in [11] for trigger type 0

– srs-ConfigIndex ISRS for SRS periodicity and SRS subframe offset , as defined in Table 8.2-1 and Table 8.2-2 for trigger type 0 and SRS periodicity and SRS subframe offset , as defined in Table 8.2-4 and Table 8.2-5 trigger type 1 for a serving cell that is not a LAA SCell

– SRS bandwidth , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– Frequency hopping bandwidth, , as defined in Subclause 5.5.3.2 of [3] for trigger type 0

– Cyclic shift , as defined in Subclause 5.5.3.1 of [3] for trigger type 0 and each configuration of trigger type 1

– Number of antenna ports for trigger type 0 and each configuration of trigger type 1

– SRS subframe for each configuration of trigger type 1 for a serving cell that is a LAA SCell and DCI format 4B

For a TDD serving cell,

– If the serving cell not configured for PUSCH/PUCCH transmission, or if the UE supports ce-srsEnhancement-r14

– For trigger type 0, the UE can be configured with more than one configuration of SoundingRS-UL-ConfigDedicatedUpPTsExt and/or SoundingRS-UL-ConfigDedicated, and the SRS parameters in each of the configurations shall be used.

– For trigger type 1, the UE can be configured with more than one configuration of SoundingRS-UL- ConfigDedicatedAperiodicUpPTsExt and/or SoundingRS-UL- ConfigDedicatedAperiodic, and the SRS parameters in each of the configurations shall be used.

For trigger type 1 and DCI format 4/4A/4B three sets of SRS parameters, srs-ConfigApDCI-Format4, are configured by higher layer signalling. The 2-bit SRS request field [4] in DCI format 4/4A/4B indicates the SRS parameter set given in Table 8.1-1. For trigger type 1 and DCI format 0/0A/0B /6-0A, a single set of SRS parameters, srs-ConfigApDCI-Format0, is configured by higher layer signalling. For trigger type 1 and DCI formats 1A/2B/2C/2D/6-1A, a single common set of SRS parameters, srs-ConfigApDCI-Format1a2b2c, is configured by higher layer signalling. For a serving cell that is not a LAA SCell, the SRS request field is 1 bit [4] for DCI formats 0/1A/2B/2C/2D/6-0A/6-1A, with a type 1 SRS triggered if the value of the SRS request field is set to ‘1’. For a serving cell that is a LAA SCell, the SRS timing offset field is 3 bits [4] for DCI formats 1A/2B/2C/2D, with a type 1 SRS triggered if the value of the SRS timing offset field is not set to ‘000’. The SRS request field is 1 bit [4] for DCI formats 0A, with a type 1 SRS triggered if the value of the SRS request field is set to ‘1’. The 2-bit SRS request field [4] in DCI format 0B indicates the type 1 SRS triggering and PUSCH subframe (as determined in Subclause 8.0) with SRS as given in Table 8.2-0A.

For a TDD serving cell not configured for PUSCH/PUCCH transmission, and trigger type 1, a SRS request field [4] shall be included in DCI format 3B if the value of the higher layer parameter fieldTypeFormat3B is set to 3 or 4. If the UE is configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission, a single SRS request field is included in DCI format 3B for a set of the TDD serving cells without PUSCH/PUCCH transmission as given in Table 8.2-0C; otherwise one or more SRS request fields is included in DCI format 3B each corresponding to a TDD serving cell without PUSCH/PUCCH transmission as configured by higher layers. If the UE is configured with no more than 5 TDD serving cells without PUSCH/PUCCH transmission, and the UE does not support transmit antenna selection or multi-antenna transmission, the SRS request field [4] in DCI format 3B is 1-bit, 2-bits otherwise. For the 1-bit SRS request field [4] in DCI format 3B, a type 1 SRS is triggered if the value of the SRS request field is set to ‘1’ with SRS parameters, srs-ConfigApDCI-Format1a2b2c, configured by higher layer signalling. For the 2-bit SRS request field [4] in DCI format 3B, and UE configured with no more than 5 TDD serving cells without PUSCH/PUCCH transmission, the SRS request field indicates the SRS parameter set given in Table 8.1-1 with the three sets of SRS parameters, srs-ConfigApDCI-Format4, configured by higher layer signalling. For the 2-bit SRS request field [4] in Table 8.2-0C and DCI format 3B, and UE configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission, SRS parameters, srs-ConfigApDCI-Format1a2b2c, configured by higher layer signalling for the associated serving cell, is used if a type 1 SRS is triggered.

For a serving cell that is not a LAA SCell, a non-BL/CE UE configured for type 1 triggered SRS transmission on serving cell c upon detection of a positive SRS request in subframe/slot n of serving cell c shall commence SRS transmission in the first subframe satisfying , and

if the positive SRS request in PDCCH/SPDCCH with DCI format 7-0A/7-1A is detected in slot n,for TDD

if the UE is configured with higher layer parameter shortProcessingTime and the corresponding PDCCH with DCI format other than DCI format 7-0A/7-1A is in the UE-specific search space,

otherwise, and

for TDD serving cell c with and for FDD serving cell c,

for TDD serving cell c with

where for FDD serving cell c is the subframe index within the frame , for TDD serving cell c, if the UE is configured with the parameter srs-UpPtsAdd for trigger type 1, is defined in Table 8.2-6; otherwise is defined in Table 8.2-3. For a TDD serving cell not configured for PUSCH/PUCCH transmission and the positive SRS request detected in PDCCH/EPDCCH scheduling PDSCH and the UE configured with soundingRS-FlexibleTiming-r14 by higher layer signalling, if the SRS transmission (including any interruption due to uplink or downlink RF retuning time [10]) in the first subframe happens to overlap with a HARQ-ACK transmission for any serving cell, the UE shall commence SRS transmission in subframe n + k + l, where l = max( 5, ).

8.2.2.5a.4.3 Test description

8.2.2.5a.4.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

8.2.2.5a.4.3.2 Test procedure sequence

Table 8.2.2.5a.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList with SCell Cell 3 addition without UL carrier, and setup an aperiodic SRS configuration on the last symbol of 3rd and 8th subframe of every radio frame in SCell Cell3.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits DCI format 1A on 1st subframe in one radio frame in SCell Cell3, and a MAC PDU is transmitted. The corresponding HARQ-ACK is expected to be in 8th subframe.

<–

DCI: (DCI Format 1A defined in TS 36.508 Table 4.3.6.1.3-1 with following exceptions: RBA()= 5, = 5, SRS request = ‘0’.)

4

The SS transmits an SRS request by using DCI format 3B on 2nd subframe in the same radio frame in SCell Cell3. The corresponding SRS transmission is expected to be in 8th subframe.

DCI: (DCI Format 3B defined in TS 36.508 Table 4.3.6.1.6A-1)

5

Check: Does the UE transmit SRS on the last symbol of 8th subframe in the same radio frame in SCell Cell3?

–>

SRS

1

F

6

Check: Does the UE transmit SRS on the last symbol of 3rd subframe in the next radio frame in SCell Cell3?

–>

SRS

1

P

8.2.2.5a.4.3.3 Specific message contents

Table 8.2.2.5a.4.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.5a.4.3.2-1)

Derivation Path: TS 36.508 clause 4.6.1 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.2.5a.4.3.3-2: SCellToAddMod-r10-DEFAULT (Table 8.2.2.5a.4.3.3-1)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D, condition SRS-Switching

Table 8.2.2.5a.4.3.3-3: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 8.2.2.5a.4.3.3-2)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-13A, condition SRS-Switching

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10-DEFAULT ::= SEQUENCE {

ul-Configuration-r14 SEQUENCE {

SRS-Switching

soundingRS-FlexibleTiming-r14

TRUE

}

}

Table 8.2.2.5a.4.3.3-4: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 8.2.2.5a.4.3.3-2)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A, condition SRS-Switching

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE {

soundingRS-UL-AperiodicConfigDedicatedList-r14 SEQUENCE {

1 entry

soundingRS-AperiodicSet-r14[1] SEQUENCE {

srs-CC-SetIndexList-r14

Not present

soundingRS-UL-ConfigDedicatedAperiodic-r14 CHOICE {

setup SEQUENCE {

srs-ConfigIndexAp-r10

12

3rd and 8th subframe every radio frame

srs-ConfigApDCI-Format4-r10

Not present

srs-ActivateAp-r10 CHOICE {

setup SEQUENCE {

srs-ConfigApDCI-Format0-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

srs-ConfigApDCI-Format1a2b2c-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

}

}

}

}

}

}

}

8.2.2.6 RRC connection reconfiguration/ UE Assistance Information

8.2.2.6.1 RRC connection reconfiguration/ UE Assistance Information/power preference indication setup and release

8.2.2.6.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and it is not configured to provide power preference indications }

ensure that {

when { UE is caused to send UEAssistanceInformation message indicating "normal" }

then { the UE does not transmit a UEAssistanceInformation message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and it is configured to provide power preference indications with T340 set to 0s}

ensure that {

when { UE prefers a configuration primarily optimised for power saving and sends the message UEAssistanceInformation}

then { the UE includes powerPrefIndication set to lowPowerConsumption in the message UEAssistanceInformation }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state and it is configured to provide power preference indications and it has previously sent UEAssistanceInformation message indicating "lowPowerConsumption" }

ensure that {

when { UE is caused to send UEAssistanceInformation message indicating "lowPowerConsumption" }

then { the UE does not transmit a UEAssistanceInformation message with powerPrefIndication set to lowPowerConsumption }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state and it is configured to provide power preference indications }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing a otherConfig that includes the powerPrefIndicationConfig set to Release }

then { the UE does not transmit any more UEAssistanceInformation message }

8.2.2.6.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.10.9, 5.6.10.2, 5.6.10.3 and 6.3.6. Unless otherwise stated these are Rel-11 requirements.

[TS 36.331, clause 5.3.10.9]

The UE shall:

1> if the received otherConfig includes the powerPrefIndicationConfig:

2> if powerPrefIndicationConfig is set to setup:

3> consider itself to be configured to provide power preference indications in accordance with 5.6.10;

2> else:

3> consider itself not to be configured to provide power preference indications;

[TS 36.331, clause 5.6.10.2]

A UE capable of providing power preference indications in RRC_CONNECTED may initiate the procedure in several cases including upon being configured to provide power preference indications and upon change of power preference.

Upon initiating the procedure, the UE shall:

1> if configured to provide power preference indications:

2> if the UE did not transmit a UEAssistanceInformation message since it was configured to provide power preference indications; or

2> if the current power preference is different from the one indicated in the last transmission of the UEAssistanceInformation message and timer T340 is not running:

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

[TS 36.331, clause 5.6.10.3]

The UE shall set the contents of the UEAssistanceInformation message:

1> if the UE prefers a configuration primarily optimised for power saving:

2> set powerPrefIndication to lowPowerConsumption;

1> else:

2> start or restart timer T340 with the timer value set to the powerPrefIndicationTimer;

2> set powerPrefIndication to normal;

The UE shall submit the UEAssistanceInformation message to lower layers for transmission.

[TS 36.331, clause 6.3.6]

powerPrefIndicationTimer

Prohibit timer for Power Preference Indication reporting. Value in seconds. Value s0 means prohibit timer is set to 0 second or not set, value s0dot5 means prohibit timer is set to 0.5 second, value s1 means prohibit timer is set to 1 second and so on.

8.2.2.6.1.3 Test Description

8.2.2.6.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

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

8.2.2.6.1.3.2 Test procedure sequence

Table 8.2.2.6.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause the UE to send UEAssistanceInformation message indicating "normal".

(Note 2)

2

Check: Does the UE send a UEAssistanceInformation message within the next 20s?

–>

UEAssistanceInformation

1

F

3

The SS transmits an RRCConnectionReconfiguration message containing a otherConfig includes the powerPrefIndicationConfig set to Setup

<–

RRCConnectionReconfiguration

4

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

4A

The SS starts Timer T340

EXCEPTION: Steps 4Ba1 to 4Bb1 describes a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens.

4Ba1

The UE transmits a UEAssistanceInformation message.

–>

UEAssistanceInformation

4Ba2

Wait for the Timer T340 Expiry to ensure that T340 timer has expired on the device.

4Bb1

The SS waits for the T340 expiry

5

Cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption".

(Note 1)

6

Check: Does the UE transmit a UEAssistanceInformation message with powerPrefIndication set to lowPowerConsumption?

–>

UEAssistanceInformation

2

P

7

Cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption".

(Note 1)

8

Check: Does the UE send a UEAssistanceInformation message within the next 20s?

–>

UEAssistanceInformation

3

F

9

The SS transmits an RRCConnectionReconfiguration message containing a otherConfig includes the powerPrefIndicationConfig set to Release.

<–

RRCConnectionReconfiguration

10

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

11

Cause the UE to send UEAssistanceInformation message indicating "normal".

(Note 2)

12

Check: Does the UE send a UEAssistanceInformation message within the next 20s?

–>

UEAssistanceInformation

4

F

13

Cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption".

(Note 1)

14

Check: Does the UE send a UEAssistanceInformation message within the next 20s?

–>

UEAssistanceInformation

4

F

Note 1: This indication may be triggered with the AT command +CEPPI/+CNMPSD or any alternative way.

Note 2: This indication may be triggered with the AT command +CEPPI or any alternative way.

8.2.2.6.1.3.3 Specific message contents

Table 8.2.2.6.1.3.3-1: RRCConnectionReconfiguration (Steps 3 and 9, Table 8.2.2.6.1.3.2-1)

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

Table 8.2.2.6.1.3.3-2: OtherConfig-r9 (step 3, Table 8.2.2.6.1.3.2-1)

Derivation Path: 36.508, Table 4.6.3-28 condition Setup

Information Element

Value/remark

Comment

Condition

OtherConfig-r9 SEQUENCE {

   PowerPrefIndicationConfig-r11 CHOICE {

     setup SEQUENCE {

powerPrefIndicationTimer-r11

s0

}

}

}

Table 8.2.2.6.1.3.3-1A: UEAssistanceInformation (Step 4B a1, Table 8.2.2.6.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-26 condition Normal

Table 8.2.2.6.1.3.3-2: UEAssistanceInformation (Step 6, Table 8.2.2.6.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-26 condition Low_Power

Table 8.2.2.6.1.3.3-3: OtherConfig-r9 (Step 9, Table 8.2.2.6.1.3.2-3)

Derivation Path: 36.508, Table 4.6.3-28 condition Release

8.2.2.6.2 RRC connection reconfiguration/ UE Assistance Information/power preference indication release on connection re-establishment

8.2.2.6.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state & configured to provide power preference indication }

ensure that {

when { RRC Connection re-establishment procedure is initiated }

then { UE shall stop T340 }

}

(2)

with { UE in E-UTRA RRC_Connected state & configured to provide power preference indication }

ensure that {

when { RRC Connection re-establishment procedure is initiated }

then { UE shall release the powerPrefIndicationConfig }

}

8.2.2.6.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.6.10.1, 5.6.10.2, 5.6.10.3 and 5.3.7.2. Unless otherwise stated these are Rel-11 requirements.

[TS 36.331 clause 5.6.10.1]

Figure 5.6.10.1-1: UE Assistance Information

The purpose of this procedure is to inform E-UTRAN of the UE’s power saving preference. Upon configuring the UE to provide power preference indications E-UTRAN may consider that the UE does not prefer a configuration primarily optimised for power saving until the UE explicitly indicates otherwise.

[TS 36.331 clause 5.6.10.2]

A UE capable of providing power preference indications in RRC_CONNECTED may initiate the procedure in several cases including upon being configured to provide power preference indications and upon change of power preference.

Upon initiating the procedure, the UE shall:

1> if configured to provide power preference indications:

2> if the UE did not transmit a UEAssistanceInformation message since it was configured to provide power preference indications; or

2> if the current power preference is different from the one indicated in the last transmission of the UEAssistanceInformation message and timer T340 is not running:

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

[TS 36.331 clause 5.6.10.3]

The UE shall set the contents of the UEAssistanceInformation message:

1> if the UE prefers a configuration primarily optimised for power saving:

2> set powerPrefIndication to lowPowerConsumption;

1> else:

2> start or restart timer T340 with the timer value set to the powerPrefIndicationTimer;

2> set powerPrefIndication to normal;

The UE shall submit the UEAssistanceInformation message to lower layers for transmission.

[TS 36.331 clause 5.3.7.2]

The UE shall only initiate the procedure when AS security has been activated. The UE initiates the procedure when one of the following conditions is met:

1> upon detecting radio link failure, in accordance with 5.3.11; or

1> upon handover failure, in accordance with 5.3.5.6; or

1> upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or

1> upon integrity check failure indication from lower layers; or

1> upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5;

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> start timer T311;

1> suspend all RBs except SRB0;

1> reset MAC;

1> release the SCell(s), if configured, in accordance with 5.3.10.3a;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> release powerPrefIndicationConfig, if configured and stop timer T340, if running;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> release obtainLocationConfig, if configured;

1> release idc-Config, if configured;

1> release measSubframePatternPCell, if configured;

1> if connected as an RN and configured with an RN subframe configuration:

2> release the RN subframe configuration;

1> perform cell selection in accordance with the cell selection process as specified in TS 36.304 [4];

8.2.2.6.2.3 Test description

8.2.2.6.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 & Cell 2.

– System information combination 2 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA Cell 1.

UE:

– None.

Preamble:

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

8.2.2.6.2.3.2 Test procedure sequence

Table 8.2.2.6.2.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1", and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.2.6.2.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M3) satisfy exit condition for event A3 (M3 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M3) satisfy entry condition for event A3 (M3 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

-85

"Off"

The power level values are assigned to satisfy SrxlevCell 2 < 0 such that selecting Cell 1 is guaranteed

(NOTE 1).

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.2.6.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

Cause the UE to send UEAssistanceInformation message indicating "normal".

(Note 2)

1

The SS transmits an RRCConnectionReconfiguration message to setup intra frequency measurement on Cell 1 & to configure power preference indication.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

2A

SS Starts Timer T340

EXCEPTION: Steps 2Ba1 to 2Bb1 describes a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens.

2Ba1

The UE transmits a UEAssistanceInformation message.

–>

UEAssistanceInformation

2Ba2

Wait for the Timer T340 Expiry to ensure that T340 timer has expired on the device.

2Bb1

The SS Waits for the T340 Timer Expiry.

3

Cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption". (Note1).

4

UE transmits UEAssistanceInformation message with powerPrefIndication IE set to lowPowerConsumption.

–>

UEAssistanceInformation

5

Cause the UE to send UEAssistanceInformation message indicating "normal"(Note2).

6

UE transmits UEAssistanceInformation message with powerPrefIndication IE set to normal and starts timer T340 with the timer value set to the powerPrefIndicationTimer.

–>

UEAssistanceInformation

7

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

8

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 2.

–>

MeasurementReport

9

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 10 the steps specified in Table 8.2.2.6.2.3.2-3 should take place.

10

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

11

The UE releases the configured powerPrefIndicationConfig, stops timer T340 and transmit an RRCConnectionReestablishmentRequest message on Cell 1.

–>

RRCConnectionReestablishmentRequest

12

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 1.

<–

RRCConnectionReestablishment

13

The UE transmits an RRCConnectionReestablishmentComplete message on Cell 1.

–>

RRCConnectionReestablishmentComplete

14

Cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption". (Note1).

15

Check: Does the UE transmit UEAssistanceInformation message within the next 20s? (Note 3).

–>

UEAssistanceInformation

2

F

16

The SS transmits an RRCConnectionReconfiguration message to resume existing radio bearer on Cell 1 & to configure power preference indication.

<–

RRCConnectionReconfiguration

17

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

17A

SS Starts Timer T340

EXCEPTION: Steps 17Ba1 to 17Bb1 describes a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens.

17Ba1

The UE transmits a UEAssistanceInformation message.

–>

UEAssistanceInformation

17Ba2

Wait for the Timer T340 Expiry to ensure that T340 timer has expired on the device.

17Bb1

The SS Waits for the T340 Timer Expiry.

18

Cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption". (Note1).

19

Check: Does the UE transmit UEAssistanceInformation message with powerPrefIndication IE set to lowPowerConsumption? (Note 4).

–>

UEAssistanceInformation

1

P

Note 1: This indication may be triggered with the AT command +CEPPI/+CNMPSD or any alternative way.

Note 2: This indication may be triggered with the AT command +CEPPI or any alternative way.

Note 3: This is a negative check for TP2 to make sure that the UE has released the configured powerPrefIndicationConfig at step 11.

Note 4: The total time to execute step 6 – step 19 should be less than the T340 timer value powerPrefIndicationTimer configured at step 1 and started at step 6. This is to make sure that timer T340 has been stopped successfully at step 11 and only then UE will initiate UEAssistanceInformation message with powerPrefIndication IE set to lowPowerConsumption at step 19.

Table 8.2.2.6.2.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 2.

2

The SS does not respond.

8.2.2.6.2.3.3 Specific message contents

Table 8.2.2.6.2.3.3-0: Condition for specific message contents in Table 8.2.2.6.2.3.3-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.2.6.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.6.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, conditions MEAS & OtherConfig

Table 8.2.2.6.2.3.3-2: MeasConfig (Table 8.2.2.6.2.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0[1]

Same downlink EARFCN as used for f1

}

}

}

Table 8.2.2.6.2.3.3-3: OtherConfig-r9 (Table 8.2.2.6.2.3.3-1)

Derivation Path: 36.508, Table 4.6.3-28 condition Setup

Information Element

Value/remark

Comment

Condition

OtherConfig-r9 SEQUENCE {

   PowerPrefIndicationConfig-r11 CHOICE {

     setup SEQUENCE {

powerPrefIndicationTimer-r11

s600

}

}

}

Table 8.2.2.6.2.3.3-4: UEAssistanceInformation (step 4, 15, 17Ba1 & 19, Table 8.2.2.6.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-26 condition Low_Power

Information Element

Value/remark

Comment

Condition

powerPreferenceIndication-r11

lowPowerConsumption

Table 8.2.2.6.2.3.3-5: UEAssistanceInformation (step 2 Ba1 & 6, Table 8.2.2.6.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-26 condition Normal

Information Element

Value/remark

Comment

Condition

powerPreferenceIndication-r11

normal

Table 8.2.2.6.2.3.3-6: MeasurementReport (step 8, Table 8.2.2.6.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPcell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.2.6.2.3.3-7: RRCConnectionReconfiguration (step 9, Table 8.2.2.6.2.3.2-2)

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

Table 8.2.2.6.2.3.3-8: MobilityControlInfo (8.2.2.6.2.3.3-7)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

Table 8.2.2.6.2.3.3-9: RRCConnectionReestablishmentRequest (step 11, Table 8.2.2.6.2.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

handoverFailure

}

}

}

Table 8.2.2.6.2.3.3-10: RRCConnectionReestablishmentComplete (step 13, Table 8.2.2.6.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-11

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishmentComplete ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionReestablishmentComplete-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

Table 8.2.2.6.2.3.3-11: RRCConnectionReconfiguration (step 16, Table 8.2.2.6.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8 & condition OtherConfig

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-HO

}

}

}

}

Table 8.2.2.6.2.3.3-12: OtherConfig-r9 (Table 8.2.2.6.2.3.3-11)

Derivation Path: 36.508, Table 4.6.3-28, condition Setup

Information Element

Value/remark

Comment

Condition

OtherConfig-r9 SEQUENCE {

PowerPrefIndicationConfig-r11 CHOICE {

setup SEQUENCE {

powerPrefIndicationTimer-r11

s10

}

}

}

8.2.2.6.3 RRC connection reconfiguration/ UE Assistance Information/T340 running

8.2.2.6.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and T340 is running }

ensure that {

when { UE is caused to send UEAssistanceInformation message }

then { the UE does not transmit a UEAssistanceInformation message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and the UE has received a new value for powerPrefIndicationTimer}

ensure that {

when { UE is caused to send UEAssistanceInformation message indicating "lowPowerConsumption" after T340 expired }

then { the UE does transmits a UEAssistanceInformation message with powerPrefIndication set to lowPowerConsumption}

}

8.2.2.6.3.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.6.10.2 and 5.6.10.3. Unless otherwise stated these are Rel-11 requirements.

[TS 36.331, clause 5.6.10.2]

A UE capable of providing power preference indications in RRC_CONNECTED may initiate the procedure in several cases including upon being configured to provide power preference indications and upon change of power preference.

Upon initiating the procedure, the UE shall:

1> if configured to provide power preference indications:

2> if the UE did not transmit a UEAssistanceInformation message since it was configured to provide power preference indications; or

2> if the current power preference is different from the one indicated in the last transmission of the UEAssistanceInformation message and timer T340 is not running:

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

[TS 36.331, clause 5.6.10.3]

The UE shall set the contents of the UEAssistanceInformation message:

1> if the UE prefers a configuration primarily optimised for power saving:

2> set powerPrefIndication to lowPowerConsumption;

1> else:

2> start or restart timer T340 with the timer value set to the powerPrefIndicationTimer;

2> set powerPrefIndication to normal;

The UE shall submit the UEAssistanceInformation message to lower layers for transmission.

8.2.2.6.3.3 Test Description

8.2.2.6.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

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

8.2.2.6.3.3.2 Test procedure sequence

Table 8.2.2.6.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

Cause the UE to send UEAssistanceInformation message indicating "normal".

(Note 2)

1

The SS transmits an RRCConnectionReconfiguration message containing a otherConfig includes the powerPrefIndicationConfig set to Setup

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

2A

SS starts Timer T340

EXCEPTION: Steps 2Ba1 to 2Bb1 describes a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens.

2Ba1

The UE transmits a UEAssistanceInformation message.

–>

UEAssistanceInformation

2Ba2

Wait for the T340 Timer Expiry to ensure that T340 timer has expired on the device side.

2Bb1

SS waits for the T340 Timer Expiry.

3

Cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption".

(Note 1)

4

The UE transmits a UEAssistanceInformation message with powerPrefIndication set to lowPowerConsumption.

–>

UEAssistanceInformation

5

Cause the UE to send UEAssistanceInformation message indicating "normal".

(Note 2)

6

The UE transmits a UEAssistanceInformation message with powerPrefIndication set to normal.

The UE starts T340.

–>

UEAssistanceInformation

7

Before T340 expires, cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption".

(Note 1)

8

Check: Does the UE send a UEAssistanceInformation message before T340 expires?

–>

UEAssistanceInformation

1

F

9-10

Void

EXCEPTION: Steps 10Aa1 describes a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens.

10Aa1

The UE transmits a UEAssistanceInformation message within 5s with powerPrefIndication set to lowPowerConsumption

–>

UEAssistanceInformation

11

The SS transmits an RRCConnectionReconfiguration message containing a otherConfig includes the powerPrefIndicationConfig set to Setup and a new value for powerPrefIndicationTimer.

<–

RRCConnectionReconfiguration

12

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

12A

SS starts Timer T340

EXCEPTION: Steps 12Ba1 to 12Bb1 describes a transaction that depends on the UE behaviour; the "lower case letter" identifies a step sequence that takes place if a specific behaviour happens.

12Ba1

The UE transmits a UEAssistanceInformation message.

–>

UEAssistanceInformation

12Ba2

Wait for the T340 Timer Expiry to ensure that T340 timer has expired on the device side.

12Bb1

SS Waits for the T340 Timer Expiry

13

Cause the UE to send UEAssistanceInformation message indicating "normal".

(Note 2)

14

The UE transmits a UEAssistanceInformation message with powerPrefIndication set to normal. The UE starts T340.

Start timer T=300s(this is the same value as the powerPrefIndicationTimer value set in Step 1).

–>

UEAssistanceInformation

15

After T340 expires but before T expires cause the UE to send UEAssistanceInformation message indicating "lowPowerConsumption".

(Note 1)

16

Check: Does the UE send a UEAssistanceInformation message with powerPrefIndication set to lowPowerConsumption?

–>

UEAssistanceInformation

2

P

Note 1: This indication may be triggered with the AT command +CEPPI/+CNMPSD or any alternative way.

Note 2: This indication may be triggered with the AT command +CEPPI or any alternative way.

8.2.2.6.3.3.3 Specific message contents

Table 8.2.2.6.3.3.3-1: RRCConnectionReconfiguration (Steps 1 and 11 Table 8.2.2.6.3.3.2-1)

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

Table 8.2.2.6.3.3.3-2: OtherConfig-r9 (Step 1, Table 8.2.2.6.3.3.2-1)

Derivation Path: 36.508, Table 4.6.3-28 condition Setup

Information Element

Value/remark

Comment

Condition

OtherConfig-r9 SEQUENCE {

PowerPrefIndicationConfig-r11 CHOICE {

setup SEQUENCE {

powerPrefIndicationTimer-r11

s300

}

}

}

Table 8.2.2.6.3.3.3-3: UEAssistanceInformation (Steps 4, 10 and 12Ba1 Table 8.2.2.6.3.3.2-1)

Derivation Path: 36.508, Table 4.6.1-26 condition Low_Power

Table 8.2.2.6.3.3.3-4: UEAssistanceInformation (Steps 2 Ba1, 6 and 14, Table 8.2.2.6.3.3.2-1)

Derivation Path: 36.508, Table 4.6.1-26 condition Normal

Table 8.2.2.6.3.3.3-5: OtherConfig-r9 (Step 11, Table 8.2.2.6.3.3.2-1)

Derivation Path: 36.508, Table 4.6.3-28 condition Setup

Information Element

Value/remark

Comment

Condition

OtherConfig-r9 SEQUENCE {

PowerPrefIndicationConfig-r11 CHOICE {

setup SEQUENCE {

powerPrefIndicationTimer-r11

s30

}

}

}

8.2.2.6.4 Void
8.2.2.6.5 Void
8.2.2.6.6 Void

8.2.2.7 CA / RRC connection reconfiguration / sTAG addition/modification/release / Success

8.2.2.7.1 CA / RRC connection reconfiguration / sTAG addition/modification/release / Success / Intra-band Contiguous CA

8.2.2.7.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing stag-ToAddModList with a sTAG addition and sCellToAddModList with a SCell addition which is associated with the new sTAG }

then { UE adds the new SCell and associates it with the new sTAG, sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing stag-ToAddModList with a sTAG modification }

then { UE modifies the affected sTAG dedicated configurations and sends an RRCConnectionReconfigurationComplete message }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToReleaseList with a sCellIndex equalling to one of the current UE SCell configuration and stag-ToReleaseList to release the empty sTAG after the last SCell is removed from this sTAG }

then { UE releases this SCell and sTAG and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.7.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.3a, 5.3.10.4 and 6.3.2. Unless otherwise stated these are Rel-11 requirements.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

NOTE 3: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an outstanding acknowledgment of the SecurityModeComplete message.

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.3a]

The UE shall:

1> if the release is triggered by reception of the sCellToReleaseList:

2> for each sCellIndex value included in the sCellToReleaseList:

3> if the current UE configuration includes an SCell with value sCellIndex:

4> release the SCell;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig other than stag-ToReleaseList and stag-ToAddModList;

1> if the received mac-MainConfig includes the stag-ToReleaseList:

2> for each STAG-Id value included in the stag-ToReleaseList that is part of the current UE configuration:

3> release the STAG indicated by STAG-Id;

1> if the received mac-MainConfig includes the stag-ToAddModList:

2> for each stag-Id value included in stag-ToAddModList that is not part of the current UE configuration (STAG addition):

3> add the STAG, corresponding to the stag-Id, in accordance with the received timeAlignmentTimerSTAG;

2> for each stag-Id value included in stag-ToAddModList that is part of the current UE configuration (STAG modification):

3> reconfigure the STAG, corresponding to the stag-Id, in accordance with the received timeAlignmentTimerSTAG;

[TS 36.331, clause 6.3.2]

MAC-MainConfig field descriptions

stag-Id

Indicates the TAG of an SCell, see TS 36.321 [6]. If the field is not configured for an SCell (e.g. absent in MAC-MainConfigSCell), the SCell is part of the PTAG.

stag-ToAddModList, stag-ToReleaseList

Used to configure one or more STAGs. E-UTRAN ensures that a STAG contains at least one SCell with configured uplink. If, due to SCell release a reconfiguration would result in an ‘empty’ TAG, E-UTRAN includes release of the concerned TAG.

timeAlignmentTimerSTAG

Indicates the value of the time alignment timer for an STAG, see TS 36.321 [6].

8.2.2.7.1.3 Test Description

8.2.2.7.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell3 is the SCell to be added.

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

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

8.2.2.7.1.3.2 Test procedure sequence

Table 8.2.2.7.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing stag-ToAddModList with a sTAG addition and sCellToAddModList with SCell Cell 3 addition which is associated with the added sTAG.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

3

The SS transmits an RRCConnectionReconfiguration message containing a stag-ToAddModList with timeAlignmentTimerSTAG-r11 modification.

<–

RRCConnectionReconfiguration

4

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

2

P

5

The SS transmits an RRCConnectionReconfiguration message containing an sCellToReleaseList with an sCellIndex equalling to the Cell 3 cell index in the current UE configuration and stag-ToReleaseList-r11 with STAG-Id equalling to the stag-id with which the Cell 3 is associated.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

3

P

7

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

1

8.2.2.7.1.3.3 Specific message contents

Table 8.2.2.7.1.3.3-0: Conditions for specific message contents
in Tables 8.2.2.7.1.3.3-2, 8.2.2.7.1.3.3-3, 8.2.2.7.1.3.3-7, 8.2.2.7.1.3.3-8 and 8.2.2.7.1.3.3-11

Condition

Explanation

Uplink_CA

The UE supports carrier aggregation in UL under the test band.

Band > 64

If band > 64 is selected

Table 8.2.2.7.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.7.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8, condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig SEQUENCE {

stag-ToAddModList-r11 SEQUENCE (SIZE (1..maxSTAG-r11)) OF SEQUENCE {

stag-Id-r11[1]

1

timeAlignmentTimerSTAG-r11[1]

Infinity

}

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 8.2.2.7.1.3.3-2: SCellToAddMod-r10-f2-Add (Table 8.2.2.7.1.3.3-1)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.2.7.1.3.3-3: RadioResourceConfigCommonSCell-r10-f2 (Table 8.2.2.7.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A, condition UL CA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 3

}

ul-Configuration-r10 SEQUENCE {

ul-FreqInfo-r10 SEQUENCE {

ul-Bandwidth-r10

Same uplink system bandwidth as used for Cell 3

FDD

Not present

TDD

additionalSpectrumEmissionSCell-r10

Same additionalSpectrumEmission as used for Cell 3

}

}

}

Table 8.2.2.7.1.3.3-4: RadioResourceConfigDedicatedSCell-r10-f2 (Table 8.2.2.7.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

physicalConfigDedicatedSCell-r10

PhysicalConfigDedicatedSCell-r10-DEFAULT

mac-MainConfigSCell-r11 SEQUENCE {

stag-Id-r11

1

}

}

Table 8.2.2.7.1.3.3-5: RRCConnectionReconfiguration (step 3, Table 8.2.2.7.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig SEQUENCE {

stag-ToAddModList-r11 SEQUENCE (SIZE (1..maxSTAG-r11)) OF SEQUENCE {

stag-Id-r11[1]

1

timeAlignmentTimerSTAG-r11[1]

sf750

}

}

}

}

}

}

}

Table 8.2.2.7.1.3.3-6: RRCConnectionReconfiguration (step 5, Table 8.2.2.7.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig SEQUENCE {

stag-ToReleaseList-r11 SEQUENCE (SIZE (1..maxSTAG-r11)) OF SEQUENCE {

stag-Id-r11[1]

1

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10 SEQUENCE (SIZE (1..maxSCell-r10) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

SCell release for Cell 3

}

sCellToAddModList-r10

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

8.2.2.7.2 CA / RRC connection reconfiguration / sTAG addition/modification/release / Success / Inter-band CA

The scope and description of the present TC is the same as test case 8.2.2.7.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Inactive SCell according to [18] cl. 6.3.4

8.2.2.7.3 CA / RRC connection reconfiguration / sTAG addition/modification/release / Success / Intra-band non-contiguous CA

The scope and description of the present TC is the same as test case 8.2.2.7.1 with the following differences:

– CA configuration: Intra-band non-contiguous CA replaces Intra-band Contiguous CA

8.2.2.8 RRC connection reconfiguration / SIB1 information / Success

8.2.2.8.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing SIB1 information with a change of TAI}

then { UE reads the SIB1 information and sends an RRCConnectionReconfigurationComplete message followed by TRACKING AREA UPDATE REQUEST message to update the registration of the actual tracking area }

}

8.2.2.8.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.2.2.7, and 5.3.5.3. Unless otherwise stated these are Rel-11 requirements

[TS 36.331, clause 5.2.2.7]

Upon receiving the SystemInformationBlockType1 either via broadcast or via dedicated signalling, the UE shall:

1> if in RRC_CONNECTED while T311 is not running, and the UE supports multi-band cells as defined by bit 31 in featureGroupIndicators:

2> disregard the freqBandIndicator and multiBandInfoList, if received, while in RRC_CONNECTED;

2> forward the cellIdentity to upper layers;

2> forward the trackingAreaCode to upper layers;

1> else:

2> if the frequency band indicated in the freqBandIndicator is part of the frequency bands supported by the UE; or

2> if the UE supports multiBandInfoList, and if one or more of the frequency bands indicated in the multiBandInfoList are part of the frequency bands supported by the UE:

3> forward the cellIdentity to upper layers;

3> forward the trackingAreaCode to upper layers;

2> else:

3> consider the cell as barred in accordance with TS 36.304 [4]; and

3> perform barring as if intraFreqReselection is set to notAllowed, and as if the csg-Indication is set to FALSE;

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:

2> perform the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

8.2.2.8.3 Test Description

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

Table 8.2.2.8.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

The SS stops transmitting SIB1 information on Cell 1.

1

The SS transmits an RRConnectionReconfiguration message containing SIB1 information.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

3

Check: Does UE transmit a TRACKING AREA UPDATE REQUEST message to update the registration of the actual tracking area?

–>

RRC: ULInformationTransfer

NAS: TRACKING AREA UPDATE REQUEST

1

P

4

SS responds with TRACKING AREA UPDATE ACCEPT message.

<–

RRC: DLInformationTransfer

NAS: TRACKING AREA UPDATE ACCEPT

5

The UE send a TRACKING AREA UPDATE COMPLETE message.

–>

RRC: ULInformationTransfer

NAS: TRACKING AREA UPDATE COMPLETE

6

The SS resumes transmitting SIB1 information.

8.2.2.8.3.3 Specific message contents

Table 8.2.2.8.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.8.3.2-1)

Derivation Path: 36.508 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

systemInfomationBlockType1Dedicated-r11

systemInfomationBlockType1

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

}

Table 8.2.2.8.3.3-2: SystemInformationBlockType1 (Table 8.2.2.8.3.3-1 and step 6, Table 8.2.2.8.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2-3

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1 ::= SEQUENCE {

cellAccessRelatedInfo SEQUENCE {

trackingAreaCode

TAC =2

}

}

8.2.2.9 Dual Connectivity / RRC connection reconfiguration

8.2.2.9.1 RRC connection reconfiguration / PSCell addition and SCG release / SCG / DRB

8.2.2.9.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing SCG-Configuration-r12 with radioResourceConfigDedicatedSCG, drb-ToAddModListSCG and the drb-Identity is not part of the current UE configuration }

then { UE configures the PSCell and sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing SCG-Configuration-r12 with release }

then { UE reconfigures affected DRBs and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.9.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.10, 5.3.10.11 and 5.3.10.3a1.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.10]

1> if the received scg-Configuration is set to release:

2> release the entire SCG configuration, except for the DRB configuration (i.e. as configured by drb-ToAddModListSCG);

2> stop timer T313, if running;

2> stop timer T307, if running;

1> else:

2> if the received scg-ConfigPartSCG includes the radioResourceConfigDedicatedSCG:

3> reconfigure the dedicated radio resource configuration for the SCG as specified in 5.3.10.11;

[TS 36.331, clause 5.3.10.11]

The UE shall:

1> if the received radioResourceConfigDedicatedSCG includes the drb-ToAddModListSCG:

2> for each drb-Identity value included in the drb-ToAddModListSCG perform the DC specific DRB addition or reconfiguration as specified in 5.3.10.3a1

[TS 36.331, clause 5.3.10.3a1]

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> if drb-ToAddModListSCG is received and includes the drb-Identity value; and drb-Identity value is not part of the current UE configuration (i.e. DC specific DRB establishment):

2> else (i.e. add SCG DRB):

3> establish a PDCP entity and configure it with the current SCG security configuration and in accordance with the pdcp-Config included in drb-ToAddModListSCG;

3> establish an SCG RLC entity or entities and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

2> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

8.2.2.9.1.3 Test Description

8.2.2.9.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, and Cell 10 is the PSCell.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1 and Cell 10.

UE:

None.

Preamble:

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

8.2.2.9.1.3.2 Test procedure sequence

Table 8.2.2.9.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a SCG-Configuration-r12 with PSCell-r12. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

2A

The UE transmits an ULInformationTransfer message containing the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.

–>

ULInformationTransfer

3

SS transmits RRCConnectionReconfiguration message containing a SCG-Configuration-r12 with release. RRCConnectionReconfiguration message contains the DEACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message

<–

RRCConnectionReconfiguration

4

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

2

P

5

The UE transmits an ULInformationTransfer message containing the DEACTIVATE EPS BEARER CONTEXT ACCEPT message.

–>

ULInformationTransfer

8.2.2.9.1.3.3 Specific message contents

Table 8.2.2.9.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.9.1.3.2-1)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8, condition PSCell_Add_SCG_DRB

Table 8.2.2.9.1.3.3-2: RRCConnectionReconfiguration (step 3, Table 8.2.2.9.1.3.2-1)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8, condition PSCell_Release

8.2.2.9.2 RRC connection reconfiguration / PSCell addition and SCG release / Split DRB

8.2.2.9.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing SCG-Configuration-r12 with radioResourceConfigDedicatedSCG, drb-ToAddModListSCG, drb-ToAddModList including a drb-Identity not part of the current UE configuration }

then { UE configures the PSCell and sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing SCG-Configuration-r12 with release when the current UE configuration includes split DRBs}

then { UE reconfigures affected DRBs and sends an RRCConnectionReconfigurationComplete message }

}

8.2.2.9.2.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.10, 5.3.10.11 and 5.3.10.3a1.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.10]

1> if the received scg-Configuration is set to release:

2> release the entire SCG configuration, except for the DRB configuration (i.e. as configured by drb-ToAddModListSCG);

2> stop timer T313, if running;

2> stop timer T307, if running;

1> else:

2> if the received scg-ConfigPartSCG includes the radioResourceConfigDedicatedSCG:

3> reconfigure the dedicated radio resource configuration for the SCG as specified in 5.3.10.11;

[TS 36.331, clause 5.3.10.11]

The UE shall:

1> if the received radioResourceConfigDedicatedSCG includes the drb-ToAddModListSCG:

2> for each drb-Identity value included in the drb-ToAddModListSCG perform the DC specific DRB addition or reconfiguration as specified in 5.3.10.3a1

[TS 36.331, clause 5.3.10.3a1]

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> if drb-ToAddModListSCG is received and includes the drb-Identity value; and drb-Identity value is not part of the current UE configuration (i.e. DC specific DRB establishment):

2> if drb-ToAddModList is received and includes the drb-Identity value (i.e. add split DRB):

3> establish a PDCP entity and configure it with the current MCG security configuration and in accordance with the pdcp-Config included in drb-ToAddModList;

3> establish an MCG RLC entity and an MCG DTCH logical channel in accordance with the rlc-Config, logicalChannelIdentity and logicalChannelConfig included in drb-ToAddModList;

3> establish an SCG RLC entity and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

8.2.2.9.2.3 Test Description

8.2.2.9.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, and Cell 10 is the PSCell.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1 and Cell 10.

UE:

None.

Preamble:

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

8.2.2.9.2.3.2 Test procedure sequence

Table 8.2.2.9.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a SCG-Configuration-r12 with drb-ToAddModList and PSCell-r12. RRCConnectionReconfiguration message contains the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

2A

The UE transmits an ULInformationTransfer message containing the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message.

–>

ULInformationTransfer

3

SS transmits RRCConnectionReconfiguration message containing a SCG-Configuration-r12 with release. RRCConnectionReconfiguration message contains the DEACTIVATE EPS BEARER CONTEXT REQUEST message

<–

RRCConnectionReconfiguration

4

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

2

P

5

The UE transmits an ULInformationTransfer message containing the DEACTIVATE EPS BEARER CONTEXT ACCEPT message.

–>

ULInformationTransfer

8.2.2.9.2.3.3 Specific message contents

Table 8.2.2.9.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.9.2.3.2-1)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8, condition PSCell_Add_Split_DRB

Table 8.2.2.9.2.3.3-2: RRCConnectionReconfiguration (step 3, Table 8.2.2.9.2.3.2-1)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8, condition PSCell_Release

8.2.2.9.3 RRC connection reconfiguration / SCG change without handover / SCG DRB to MCG DRB and SCG DRB modification

8.2.2.9.3.1 Test Purpose (TP)

(1)

With { UE in connected mode with SCG activated with one MCG DRB and two SCG DRBs established }

ensure that {

when { UE is receiving a RRCConnectionReconfiguration message including the IE scg-Configuration to change one of the SCG DRBs on the PSCell to a MCG DRB on the PCell }
then { UE responds with a RRCConnectionReconfigurationComplete message }

}

(2)

With { UE in connected mode with SCG activated with one MCG DRB and two SCG DRBs established has performed a SCH changing one of the SCG DRBs on the PSCell to a MCG DRB on the PCell }

ensure that {

when { uplink data are submitted for transmission on the MCG/SCG DRBs }
then { UE transmits the uplink data on the MCG/SCG DRBs respectively }

}

8.2.2.9.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.3, 5.3.10.10 and 5.3.10.12. Unless otherwise stated these are Rel-12 requirements.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.10]

The UE shall:

1> if the received scg-Configuration is set to release or includes the mobilityControlInfoSCG (i.e. SCG release/ change):

2> if mobilityControlInfo is not received (i.e. SCG release/ change without HO):

3> reset SCG MAC, if configured;

3> for each drb-Identity value that is part of the current UE configuration:

4> if the DRB indicated by drb-Identity is an SCG DRB:

5> re-establish the PDCP entity and the SCG RLC entity or entities;

4> if the DRB indicated by drb-Identity is a split DRB:

5> perform PDCP data recovery and re-establish the SCG RLC entity;

4> if the DRB indicated by drb-Identity is an MCG DRB; and

4> drb-ToAddModListSCG is received and includes the drb-Identity value, while for this entry drb-Type is included and set to scg (i.e. MCG to SCG):

5> re-establish the PDCP entity and the MCG RLC entity or entities;

3> configure lower layers to consider the SCG SCell(s), except for the PSCell, to be in deactivated state;

NOTE 2: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

[TS 36.331, clause 5.3.10.12]

The UE shall:

1> for each split or SCG DRBs that is part of the current configuration:

2> if the corresponding drb-Identity value is included in the received drb-ToAddModList; and:

2> if the corresponding drb-Identity value is not included in the received drb-ToAddModListSCG (i.e. reconfigure split, split to MCG or SCG to MCG):

3> perform the DC specific DRB addition or reconfiguration as specified in 5.3.10.3a1;

8.2.2.9.3.3 Test description

8.2.2.9.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, and Cell 10 is the PSCell.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1 and Cell 10.

UE:

Preamble:

– The UE is in state DC MCG/SCG DRB Loopback Activated (state 6A) on Cell 1 and Cell 10 according to [18]
UE has 4 DRBs configured. DRB 1(Default bearer, not used in the test sequence) , DRB 2(dedicated bearer) as MCG DRB’s and DRB 3(dedicated bearer) as SCG#1 bearer, DRB 4 (dedicated bearer) as SCG#2 bearer.

8.2.2.9.3.3.2 Test procedure sequence

Table 8.2.2.9.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to change of one of the SCG DRBs to a MCG DRB.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

3

The SS transmits one IP packet to the UE on all the 3 DRB’s.

<–

IP packet

4

Check: Does the UE loops back the IP packet on each of 3 DRB’s?

–>

IP packet

2

P

8.2.2.9.3.3.3 Specific message contents

Table 8.2.2.9.3.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.9.3.3.2-1)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-DRB-Mod

}

}

}

}

Table 8.2.2.9.3.3.3-2: RadioResourceConfigDedicated-DRB-Mod (Table 8.2.2.9.3.3.3-1)

Derivation Path: 36.508, Clause 4.6.3, Table 4.6.3-27

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-DRB ::= SEQUENCE {

drb-ToAddModList

DRB-ToAddModList-RECONFIG-toMCG

}

Table 8.2.2.9.3.3.3-3: DRB-ToAddModList-RECONFIG-toMCG (Table 8.2.2.9.3.3.3-2)

Derivation Path: 36.508, Clause 4.6.3, Table 4.6.3-2A

Information Element

Value/remark

Comment

Condition

DRB-ToAddModList ::= SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {

1 Entry

eps-BearerIdentity

Not present

drb-Identity

7

Same as the DRB ID configured for SCG DRB in preamble

pdcp-Config

Not present

rlc-Config

Not present

logicalChannelIdentity

Not present

logicalChannelConfig

Not present

drb-TypeChange-r12

toMCG

}

8.2.2.9.4 Void
8.2.2.9.5 Void

8.2.2.10 eIMTA / RRC connection reconfiguration / Radio resource reconfiguration / Success

8.2.2.10.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message and successfully completes the RRC Connection Reconfiguration procedure and has data available for transmission }

then { UE use the DRB configured by network side and transfer the data}

}

8.2.2.10.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.3.5.3, 5.3.10.0 and 5.3.10.6.

The following represent an extraction of the requirements relevant to the test purpose.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

1> else:

2> If the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.10.0]

The UE shall:

1> if the received radioResourceConfigDedicated includes the physicalConfigDedicated:

2> reconfigure the physical channel configuration as specified in 5.3.10.6.

[TS 36.331, clause 5.3.10.6]

The UE shall:

  1. reconfigure the physical channel configuration in accordance with the received physicalConfigDedicated;

8.2.2.10.3 Test description

8.2.2.10.3.1 Pre-test conditions

System Simulator:

– Cell 1(TDD)

UE:

None.

Preamble:

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

8.2.2.10.3.2 Test procedure sequence

Table 8.2.2.10.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits the PDCP data on the change subframe to the UE.

<–

PDCP Data

4

Check: Does the UE loops back the PDCP data?

–>

PDCP Data

1

P

8.2.2.10.3.3 Specific message contents

Table 8.2.2.10.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.2.10.3.2-1)

Derivation Path: 36.508 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-eIMTA-DEFAULT

}

}

}

}

Table 8.2.2.10.3.3-2: RadioResourceConfigDedicated-eIMTA-DEFAULT (Table 8.2.2.10.3.3-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-eIMTA-DEFAULT ::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList

Not present

drb-ToReleaseList

Not present

mac-MainConfig

Not present

sps-Config

Not present

physicalConfigDedicated

PhysicalConfigDedicated- eIMTA

}

Table 8.2.2.10.3.3-3: PhysicalConfigDedicated-eIMTA (Table 8.2.2.10.3.3-2)

Derivation Path: 36.508 table 4.8.2.1.6-1A ,condition eIMTA

8.2.2.11 Short Processing Time / SRS configuration / Aperiodic

8.2.2.11.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when {UE receives an RRCConnectionReconfiguration message with SoundingRS-UL-AperiodicConfigDedicated configured for UL subframe as SRS trigger type 1, and a SRS request is triggered via DCI 1A }

then {UE performs SRS transmission using the resource on UL subframe configured in SoundingRS-UL-AperiodicConfigDedicated }

}

8.2.2.11.2 Conformance requirements

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

[TS 36.213, clause 8.2]A UE shall transmit Sounding Reference Symbol (SRS) on per serving cell SRS resources based on two trigger types:

– trigger type 0: higher layer signalling

– trigger type 1: DCI formats 0/0A/0B/4/4A/4B/1A/6-0A/6-1A for FDD, TDD, and frame structure type 3 and DCI formats 2B/2C/2D/3B for TDD, and frame structure type 3, and DCI format 7-0A/7-0B/7-1E/7-1F/7-1G for TDD if the UE is configured by higher layers for SRS triggering via DCI format 7-0A and has indicated the capability srs-DCI7-Triggering-FS2-r15 and the UE is configured for SRS triggering with srs-DCI7-TriggeringConfig-r15.

A UE may be configured with SRS parameters for trigger type 0 and trigger type 1 on each serving cell. A BL/CE UE configured with CEModeB is not expected to be configured with SRS parameters for trigger type 0 and trigger type 1. The following SRS parameters are serving cell specific and semi-statically configurable by higher layers for trigger type 0 and for trigger type 1.

– Number of combs as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1, if configured

– srs-UpPtsAdd: two or four additional SC-FDMA symbols in UpPTS as defined in [11] for trigger type 0 and trigger type 1, if configured

– Transmission comb , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1

– Starting physical resource block assignment , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– duration: single or indefinite (until disabled), as defined in [11] for trigger type 0

– srs-ConfigIndex ISRS for SRS periodicity and SRS subframe offset , as defined in Table 8.2-1 and Table 8.2-2 for trigger type 0 and SRS periodicity and SRS subframe offset , as defined in Table 8.2-4 and Table 8.2-5 trigger type 1 for a serving cell that is not a LAA SCell

– SRS bandwidth , as defined in Subclause 5.5.3.2 of [3] for trigger type 0 and each configuration of trigger type 1 for a serving cell that is not a LAA SCell. For a serving cell that is a LAA SCell, .

– Frequency hopping bandwidth, , as defined in Subclause 5.5.3.2 of [3] for trigger type 0

– Cyclic shift , as defined in Subclause 5.5.3.1 of [3] for trigger type 0 and each configuration of trigger type 1

– Number of antenna ports for trigger type 0 and each configuration of trigger type 1

– SRS subframe for each configuration of trigger type 1 for a serving cell that is a LAA SCell and DCI format 4B

For a TDD serving cell,

– If the serving cell not configured for PUSCH/PUCCH transmission, or if the UE supports ce-srsEnhancement-r14

– For trigger type 0, the UE can be configured with more than one configuration of SoundingRS-UL-ConfigDedicatedUpPTsExt and/or SoundingRS-UL-ConfigDedicated, and the SRS parameters in each of the configurations shall be used. The UE is not expected to receive more than one SRS configuration indicating SRS transmission on multiple symbols in different subframes within a half frame.

– For trigger type 1, the UE can be configured with more than one configuration of SoundingRS-UL- ConfigDedicatedAperiodicUpPTsExt and/or SoundingRS-UL- ConfigDedicatedAperiodic, and the SRS parameters in each of the configurations shall be used. The UE is not expected to receive more than one SRS configuration indicating SRS transmission on multiple symbols in different subframes within a half frame.

– Otherwise

– For trigger type 0, if SoundingRS-UL-ConfigDedicatedUpPTsExt is configured, the SRS parameters in SoundingRS-UL-ConfigDedicatedUpPTsExt shall be used; otherwise, SoundingRS-UL-ConfigDedicated shall be used.

– For trigger type 1, if SoundingRS-UL-ConfigDedicatedAperiodicUpPTsExt is configured, the SRS parameters in SoundingRS-UL-ConfigDedicatedAperiodicUpPTsExt shall be used; otherwise, SoundingRS-UL-ConfigDedicatedAperiodic shall be used.

For trigger type 1 and DCI format 4/4A/4B/7-0B three sets of SRS parameters, srs-ConfigApDCI-Format4, are configured by higher layer signalling. The 2-bit SRS request field [4] in DCI format 4/4A/4B/7-0B indicates the SRS parameter set given in Table 8.1-1. For trigger type 1 and DCI format 0/0A/0B /6-0A/7-0A, a single set of SRS parameters, srs-ConfigApDCI-Format0, is configured by higher layer signalling. For trigger type 1 and DCI formats 1A/2B/2C/2D/6-1A/7-1E/7-1F/7-1G, a single common set of SRS parameters, srs-ConfigApDCI-Format1a2b2c, is configured by higher layer signalling. For a serving cell that is not a LAA SCell, the SRS request field is 1 bit [4] for DCI formats 0/1A/2B/2C/2D/6-0A/6-1A/7-0A/7-1E/7-1F/7-1G, with a type 1 SRS triggered if the value of the SRS request field is set to ‘1’. For a serving cell that is a LAA SCell, the SRS timing offset field is 3 bits [4] for DCI formats 1A/2B/2C/2D, with a type 1 SRS triggered if the value of the SRS timing offset field is not set to ‘000’. The SRS request field is 1 bit [4] for DCI formats 0A, with a type 1 SRS triggered if the value of the SRS request field is set to ‘1’. The 2-bit SRS request field [4] in DCI format 0B indicates the type 1 SRS triggering and PUSCH subframe (as determined in Subclause 8.0) with SRS as given in Table 8.2-0A.

For a serving cell that is not a LAA SCell, a 1-bit SRS request field shall be included in DCI formats 0/1A for frame structure type 1 and 0/1A/2B/2C/2D for frame structure type 2 if the UE is configured with SRS parameters for DCI formats 0/1A/2B/2C/2D by higher-layer signalling. A 1-bit SRS request field shall be included in DCI format 7-0A for frame structure type 2 if the UE is configured with SRS parameters srs-ConfigApDCI-Format0 and srs-DCI7-TriggeringConfig-r15 by higher-layer signalling. A 1-bit SRS request field shall be included in DCI formats 7-1E/7-1F/7-1G for frame structure type 2 if the UE is configured with SRS parameters srs-ConfigApDCI-Format1a2b2c and srs-DCI7-TriggeringConfig-r15 by higher-layer signalling. A 1-bit SRS request field shall be included in DCI formats 6-0A/6-1A, the value of which is reserved if the UE is not configured with SRS parameters for DCI formats 6-0A/6-1A by higher layer signalling.

Table 8.1-1: SRS request value for trigger type 1 in DCI format 4/4A/4B/7-0B

Value of SRS request field

Description

’00’

No type 1 SRS trigger

’01’

The 1st SRS parameter set configured by higher layers

’10’

The 2nd SRS parameter set configured by higher layers

’11’

The 3rd SRS parameter set configured by higher layers

Table 8.2-0A: SRS request value for trigger type 1 in DCI format 0B

Value of SRS request field

Description

’00’

No type 1 SRS trigger

’01’

Type 1 SRS trigger and first scheduled PUSCH subframe

’10’

Type 1 SRS trigger and second scheduled PUSCH subframe

’11’

Type 1 SRS trigger and last scheduled PUSCH subframe

Table 8.2-0C: SRS request value for trigger type 1 in DCI format 3B and for UE configured with more than 5 TDD serving cells without PUSCH/PUCCH transmission

Value of SRS request field

Description

’00’

No type 1 SRS trigger for a 1st set of serving cells configured by higher layers

’01’

Type 1 SRS trigger for a 2nd set of serving cells configured by higher layers

’10’

Type 1 SRS trigger for a 3rd set of serving cells configured by higher layers

’11’

Type 1 SRS trigger for a 4th set of serving cells configured by higher layers

For a serving cell that is not a LAA SCell, a non-BL/CE UE configured for type 1 triggered SRS transmission on serving cell c upon detection of a positive SRS request in subframe n, slot 2n or slot 2n+1 of serving cell c shall commence SRS transmission in the first subframe satisfying , and

if the positive SRS request in PDCCH/SPDCCH with DCI format 7-0A/7-1A is detected in slot 2n or slot 2n+1, for TDD

if the UE is configured with higher layer parameter shortProcessingTime and the corresponding PDCCH with CRC scrambled by C-RNTI with DCI format other than DCI format 7-0A/7-0B/7-1E/7-1F/7-1G is in the UE-specific search space,

otherwise, and

for TDD serving cell c with and for FDD serving cell c,

for TDD serving cell c with

where for FDD serving cell c is the subframe index within the frame , for TDD serving cell c, if the UE is configured with the parameter srs-UpPtsAdd for trigger type 1, is defined in Table 8.2-6; otherwise is defined in Table 8.2-3.

Table 8.2-3: for TDD

subframe index n

0

1

2

3

4

5

6

7

8

9

1st symbol of UpPTS

2nd symbol of UpPTS

1st symbol of UpPTS

2nd symbol of UpPTS

in case UpPTS length of 2 symbols

0

1

2

3

4

5

6

7

8

9

in case UpPTS length of 1 symbol

1

2

3

4

6

7

8

9

8.2.2.11.3 Test description

8.2.2.11.3.1 Pre-test conditions

System Simulator:

  • Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 8.2.2.11.3.3-1

UE:

  • None

Preamble:

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

8.2.2.11.3.2 Test procedure sequence

Table 8.2.2.11.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup an aperiodic SRS configuration on the last symbol of 4th and 9th subframe of every radio frame.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an SRS request by using DCI format 1A on 1st subframe in one radio frame.

<–

DCI: (DCI Format 1A defined in TS 36.508 Table 4.3.6.1.3-1 with following exceptions: RBA()= 5, = 5, SRS request = ‘1’.)

4

Check: Does the UE transmit SRS on the last symbol of the 4th subframe in the same radio frame?

–>

SRS

1

P

5

Check: Does the UE transmit SRS on the last symbol of the 9th subframe in the same radio frame?

–>

SRS

1

F

8.2.2.11.3.3 Specific Message Contents

Table 8.2.2.11.3.3-1: PhysicalConfigDedicated-DEFAULT (step1, Table 8.2.2.11.3.2-1)

Derivation Path: 36.508 Table 4.8.2.1.6-1

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

PhysicalConfigDedicatedSTTI-r15 ::= SEQUENCE {

shortProcessingTime-r15

TRUE

}

soundingRS-UL-AperiodicConfigDedicatedList-r14 SEQUENCE {

1 entry

soundingRS-AperiodicSet-r14[1] SEQUENCE {

srs-CC-SetIndexList-r14

Not present

soundingRS-UL-ConfigDedicatedAperiodic-r14 CHOICE {

setup SEQUENCE {

srs-ConfigIndexAp-r10

5

4th and 9th subframe every radio frame

FDD

13

4th and 9th subframe every radio frame

TDD

srs-ConfigApDCI-Format4-r10

Not present

srs-ActivateAp-r10 CHOICE {

setup SEQUENCE {

srs-ConfigApDCI-Format0-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

srs-ConfigApDCI-Format1a2b2c-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

}

}

}

}

}

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

8.2.2.12 Short TTI / SRS configuration / TDD / Aperiodic

8.2.2.12.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when {UE receives an RRCConnectionReconfiguration message with srs-DCI7-TriggeringConfig-r15 and SoundingRS-UL-AperiodicConfigDedicated configured for UL slot as SRS trigger type 1, and a SRS request is triggered via DCI 7-0A on the TDD Cell }

then {UE performs SRS transmission on the TDD Cell using the resource on UL slot configured in SoundingRS-UL-AperiodicConfigDedicated }

}

8.2.2.12.2 Conformance requirements

Same conformance requirement as in clause 8.2.2.11.2.

8.2.2.12.3 Test description

8.2.2.12.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

– None.

Preamble:

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

8.2.2.12.3.2 Test procedure sequence

Table 8.2.2.12.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup an aperiodic SRS configuration on the last symbol of 3rd and 8th subframe of every radio frame.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an SRS request by using DCI format 7-0A on slot 0 of the 1st subframe in one radio frame.

<–

DCI: (DCI Format 7-0A defined in TS 36.508 Table 4.3.6.1.3-13 with following exceptions: RBA()= 5, = 5, SRS request = ‘1’.)

4

Check: Does the UE transmit SRS on the last symbol of the 3rd subframe in the same radio frame?

–>

SRS

1

P

5

Check: Does the UE transmit SRS on the last symbol of the 8th subframe in the same radio frame?

–>

SRS

1

F

8.2.2.12.3.3 Specific Message Contents

Table 8.2.2.12.3.3-1: PhysicalConfigDedicated-DEFAULT (step1, Table 8.2.2.12.3.2-1)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with condition Short-TTI

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

PhysicalConfigDedicatedSTTI-r15 ::= CHOICE{

srs-DCI7-TriggeringConfig-r15

TRUE

}

soundingRS-UL-AperiodicConfigDedicatedList-r14 SEQUENCE {

1 entry

soundingRS-AperiodicSet-r14[1] SEQUENCE {

srs-CC-SetIndexList-r14

Not present

soundingRS-UL-ConfigDedicatedAperiodic-r14 CHOICE {

setup SEQUENCE {

srs-ConfigIndexAp-r10

12

3th and 8th subframe every radio frame

srs-ConfigApDCI-Format4-r10

Not present

srs-ActivateAp-r10 CHOICE {

setup SEQUENCE {

srs-ConfigApDCI-Format0-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

srs-ConfigApDCI-Format1a2b2c-r10 SEQUENCE {

srs-AntennaPortAp-r10

an1

srs-BandwidthAp-r10

bw0

freqDomainPositionAp-r10

0

transmissionCombAp-r10

0

cyclicShiftAp-r10

cs0

}

}

}

}

}

}

}

}

8.2.2.13 CA / RRC connection reconfiguration / SCell addition in dormant mode / Success

8.2.2.13.1 CA / RRC connection reconfiguration / SCell addition in dormant mode / Success / Intra-band Contiguous CA

8.2.2.13.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with a SCell addition and sCellState indicates dormant }

then { UE adds the new SCell, configures lower layers to consider the SCell to be in dormant state and sends an RRCConnectionReconfigurationComplete message and report CQI/PMI/RI/PTI/CRI for the SCell according to the periodicity indicated by cqi-ReportPeriodicSCell-r15 }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing mobilityControlInfo and sCellToAddModList with SCell addition and sCellState indicates dormant }

then { UE adds the new SCell, configures lower layers to consider the SCell to be in dormant state and sends an RRCConnectionReconfigurationComplete message and report CQI/PMI/RI/PTI/CRI for the SCell according to the periodicity indicated by cqi-ReportPeriodicSCell-r15 }

}

8.2.2.13.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.5.4, 5.3.10.3b and 11.2.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> else:

2> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> stop timer T370, if running;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

NOTE 1a: It is up to UE implementation when to stop the uplink transmission/ downlink reception with the source cell(s) to initiate re-tuning for connection to the target cell, as specified in TS 36.133 [16], if makeBeforeBreak is configured.

1> reset MCG MAC and SCG MAC, if configured;

1> release uplinkDataCompression, if configured;

1> re-establish PDCP for all RBs configured with pdcp-config that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

NOTE 2a: At handover the pdcp-reestablish flag will be set for all RBs configured with NR PDCP in nr-RadioBearerConfig TS 38.331 [82] which will cause the PDCP entity to be re-established also for these RBs.

1> re-establish MCG RLC and SCG RLC, if configured, for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the securityConfigHO (without suffix) is included in the RRCConnectionReconfiguration:

2> else:

3> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

NOTE 2b: If the UE needs to update the S-KeNB key as specified in 5.3.10.10, the UE updates the S-KeNB after updating the KeNB key.

2> store the nextHopChainingCount value;

2> else:

3> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

3> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

2> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

2> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> perform the measurement related actions as specified in 5.5.6.1;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure; or

1> if MAC indicates the successful reception of a PDCCH transmission addressed to C-RNTI and if rach-Skip is configured:

2> stop timer T304;

2> release rach-Skip;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell, except for BL UEs or UEs in CE when sameSFN-Indication is not present in mobilityControlInfo.

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell, both included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> else if sCellState is configured for the SCell and indicates dormant:

3> configure lower layers to consider the SCell to be in dormant state;

[TS 36.331, clause 11.2]

The UE performance requirements for RRC procedures are specified in the following table, by means of a value N:

N = the number of 1ms subframes from the end of reception of the E-UTRAN -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> E-UTRAN response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation) where N=20 (Ref. TS 36.331 Fig. 11.2-1).

8.2.2.13.1.3 Test Description

8.2.2.13.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell3 is the SCell to be added.

– Cell 3 is active SCell according to [18] cl. 6.3.4.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

– None.

Preamble:

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

8.2.2.13.1.3.2 Test procedure sequence

Table 8.2.2.13.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.2.13.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that camping on Cell 1 is guarantee.

T1

Cell-specific RS EPRE

dBm/15kHz

-91

-85

Power levels are such that entry condition for event A3 (measId 1) is satisfied:

Table 8.2.2.13.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing an sCellToAddModList with SCell Cell 3 addition and sCellState indicates dormant.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell addition of Cell 3 in dormant mode.

–>

RRCConnectionReconfigurationComplete

3

Check: Does UE report CQI/PMI/RI/PTI/CRI on Cell 3 for the next 400 ms?

(CSI)

1

P

4

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup event A3 reporting configuration.

<–

RRCConnectionReconfiguration

5

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

6

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

7

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

8

The SS transmits an RRCConnectionReconfiguration message with mobilityControlInfo on Cell 1 to order the UE to perform handover to Cell 3 and sCellToAddModList with SCell Cell 1 addition and sCellState indicates dormant.

<–

RRCConnectionReconfiguration

9

UE transmits an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the handover and SCell addition of Cell 1 in dormant mode.

–>

RRCConnectionReconfigurationComplete

10

Check: Does UE report CQI/PMI/RI/PTI/CRI on Cell 1 for next 400 ms?

(CSI)

2

P

8.2.2.13.1.3.3 Specific message contents

Table 8.2.2.13.1.3.3-1: Conditions for specific message contents

Condition

Explanation

Uplink_CA

The UE supports carrier aggregation in UL under the test band.

Band > 64

If band > 64 is selected

Table 8.2.2.13.1.3.3-2: RRCConnectionReconfiguration (step 1, Table 8.2.2.13.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-DormantSCell

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToAddModListExt-v1430

SCellToAddModListExt-v1430-DormantSCell

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.2.13.1.3.3-3: RadioResourceConfigDedicated-DormantSCell (Table 8.2.2.13.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AAA RadioResourceConfigDedicated-SCell_AddMod

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-SCell_AddMod ::= SEQUENCE {

physicalConfigDedicated

PhysicalConfigDedicated- DormantSCell

}

Table 8.2.2.13.1.3.3-4: PhysicalConfigDedicated-DormantSCell (Table 8.2.2.13.1.3.3-3)

Derivation Path: 36.508 clause 4.8.2 table 4.8.2.1.6-1 PhysicalConfigDedicated-DEFAULT

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

cqi-ReportConfigSCell-r15

CQI-ReportConfigSCell-r15-DormantSCell

}

Table 8.2.2.13.1.3.3-5: CQI-ReportConfigSCell-r15-DormantSCell (Table 8.2.2.13.1.3.3-4)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

CQI-ReportConfigSCell-r15-DormantSCell ::= SEQUENCE {

cqi-ReportPeriodicSCell-r15 CHOICE {

setup SEQUENCE {

cqi-pmi-ConfigIndexDormant-r15

37

FDD

cqi-pmi-ConfigIndexDormant-r15

36

TDD

ri-ConfigIndexDormant-r15

805

csi-SubframePatternDormant-r15

Not present

cqi-FormatIndicatorDormant-r15

Not present

}

}

}

Table 8.2.2.13.1.3.3-6: SCellToAddMod-r10-f2-Add (Table 8.2.2.13.1.3.3-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.2.13.1.3.3-7: RadioResourceConfigCommonSCell-r10-f2 (Table 8.2.2.13.1.3.3-6)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 3

}

}

Table 8.2.2.13.1.3.3-8: RadioResourceConfigDedicatedSCell-r10-f2 (Table 8.2.2.13.1.3.3-6)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA

Table 8.2.2.13.1.3.3-9: SCellToAddModListExt-v1430-Dormant (Table 8.2.2.13.1.3.3-2)

Derivation Path: 36.331 clause

Information Element

Value/remark

Comment

Condition

SCellToAddModListExt-v1430 ::= SEQUENCE (SIZE (1..maxSCell-r13)) OF SEQUENCE {

1 entry

sCellState-r15

dormant

}

Table 8.2.2.13.1.3.3-10: RRCConnectionReconfiguration (step 4, Table 8.2.2.13.1.3.2-2)

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

Table 8.2.2.13.1.3.3-11: MeasConfig (Table 8.2.2.13.1.3.3-7)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

3 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

Cell 1

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

Cell 3

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.2.13.1.3.3-12: MeasurementReport (step 7, Table 8.2.2.13.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults ::= SEQUENCE {

measId

1

measResultPCell ::= SEQUENCE {

Report Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

physicalCellId of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10 SEQUENCE (SIZE (1..maxServCell-r10)) OF SEQUENCE {

servFreqId-r10

1

measResultSCell-r10 SEQUENCE {

Cell 3

rsrpResultSCell-r10

(0..97)

rsrqResultSCell-r10

(0..34)

}

}

}

}

}

}

}

Table 8.2.2.13.1.3.3-13: RRCConnectionReconfiguration (step 8, Table 8.2.2.13.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated-DormantSCell

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10 SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

SCellIndex-r10[1]

1

}

sCellToAddModList-r10

SCellToAddMod-r10-f1-Add

SCell addition for Cell 1

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToAddModListExt-v1430

SCellToAddModListExt-v1430-DormantSCell

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.2.13.1.3.3-14: MobilityControlInfo (Table 8.2.2.13.1.3.3-13)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.2.13.1.3.3-15: RadioResourceConfigDedicated-DormantSCell (Table 8.2.2.13.1.3.3-13)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AAA RadioResourceConfigDedicated-SCell_AddMod

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-SCell_AddMod ::= SEQUENCE {

physicalConfigDedicated

PhysicalConfigDedicated- DormantSCell

}

Table 8.2.2.13.1.3.3-16: PhysicalConfigDedicated-DormantSCell (Table 8.2.2.13.1.3.3-15)

Derivation Path: 36.508 clause 4.8.2 table 4.8.2.1.6-1 PhysicalConfigDedicated-DEFAULT

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

cqi-ReportConfigSCell-r15

CQI-ReportConfigSCell-r15-DormantSCell

}

Table 8.2.2.13.1.3.3-17: CQI-ReportConfigSCell-r15-DormantSCell (Table 8.2.2.13.1.3.3-16)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

CQI-ReportConfigSCell-r15-DormantSCell ::= SEQUENCE {

cqi-ReportPeriodicSCell-r15 CHOICE {

setup SEQUENCE {

cqi-pmi-ConfigIndexDormant-r15

37

FDD

cqi-pmi-ConfigIndexDormant-r15

36

TDD

ri-ConfigIndexDormant-r15

805

csi-SubframePatternDormant-r15

Not present

cqi-FormatIndicatorDormant-r15

Not present

}

}

}

Table 8.2.2.13.1.3.3-18: SCellToAddMod-r10-f1-Add (Table 8.2.2.13.1.3.3-13)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

cellIdentification-r10[1] SEQUENCE {

physCellId-r10[1]

Physical Cell Identity of Cell 1

dl-CarrierFreq-r10[1]

Same downlink EARFCN as used for Cell 1

dl-CarrierFreq-r10[1]

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10[1]

RadioResourceConfigCommonSCell-r10-f1

dl-CarrierFreq-v1090[1]

Same downlink EARFCN as used for Cell 1

Band > 64

}

Table 8.2.2.13.1.3.3-19: RadioResourceConfigCommonSCell-r10-f1 (Table 8.2.2.13.1.3.3-18)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 1

}

}

8.2.2.14 CA / RRC connection reconfiguration / SCell addition in activated mode / Success

8.2.2.14.1 CA / RRC connection reconfiguration / SCell addition in activated mode / Success / Intra-band Contiguous CA

8.2.2.14.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing sCellToAddModList with a SCell addition and sCellState indicates activated }

then { UE adds the new SCell, configures lower layers to consider the SCell to be in activated state and sends an RRCConnectionReconfigurationComplete message and starts monitoring PDCCH on added SCell }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing mobilityControlInfo and sCellToAddModList with SCell addition and sCellState indicates activated }

then { UE adds the new SCell, configures lower layers to consider the SCell to be in activated state and sends an RRCConnectionReconfigurationComplete message and starts monitoring PDCCH on added SCell }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing mobilityControlInfo and sCellState indicates activated }

then { UE maintains the current SCell in activated state and sends an RRCConnectionReconfigurationComplete message and keeps monitoring PDCCH on SCell }

}

8.2.2.14.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.3, 5.3.5.4 and 5.3.10.3b.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> else:

2> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> stop timer T370, if running;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

NOTE 1a: It is up to UE implementation when to stop the uplink transmission/ downlink reception with the source cell(s) to initiate re-tuning for connection to the target cell, as specified in TS 36.133 [16], if makeBeforeBreak is configured.

1> reset MCG MAC and SCG MAC, if configured;

1> release uplinkDataCompression, if configured;

1> re-establish PDCP for all RBs configured with pdcp-config that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

NOTE 2a: At handover the pdcp-reestablish flag will be set for all RBs configured with NR PDCP in nr-RadioBearerConfig TS 38.331 [82] which will cause the PDCP entity to be re-established also for these RBs.

1> re-establish MCG RLC and SCG RLC, if configured, for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the securityConfigHO (without suffix) is included in the RRCConnectionReconfiguration:

2> else:

3> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

NOTE 2b: If the UE needs to update the S-KeNB key as specified in 5.3.10.10, the UE updates the S-KeNB after updating the KeNB key.

2> store the nextHopChainingCount value;

2> else:

3> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

3> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

2> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

2> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> perform the measurement related actions as specified in 5.5.6.1;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure; or

1> if MAC indicates the successful reception of a PDCCH transmission addressed to C-RNTI and if rach-Skip is configured:

2> stop timer T304;

2> release rach-Skip;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell, except for BL UEs or UEs in CE when sameSFN-Indication is not present in mobilityControlInfo.

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell, both included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> if sCellState is configured for the SCell and indicates activated:

3> configure lower layers to consider the SCell to be in activated state;

8.2.2.14.1.3 Test Description

8.2.2.14.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell3 is the SCell to be added and Cell 6 is .neighbouring PCell

– Cell 3 is active SCell according to [18] cl. 6.3.4.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

– None.

Preamble:

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

8.2.2.14.1.3.2 Test procedure sequence

Table 8.2.2.14.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.2.14.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Cell 6

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

-97

The power level values are such that camping on Cell 1 is guarantee.

T1

Cell-specific RS EPRE

dBm/15kHz

-91

-85

-97

The power level values are such that camping on Cell 3 is guarantee.

T2

Cell-specific RS EPRE

dBm/15kHz

-91

-97

-85

The power level values are such that camping on Cell 6 is guarantee.

Table 8.2.2.14.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing an sCellToAddModList with SCell Cell 3 addition and sCellState indicates activated.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell addition of Cell 3 in activated mode.

–>

RRCConnectionReconfigurationComplete

3

100 ms after step 3, the SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

4

Check: Does the UE transmit a Scheduling Request on PUCCH

–>

(SR)

1

P

5

The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1

<–

(UL Grant)

6

The UE transmit a MAC PDU containing the loop back PDU corresponding to step 3

–>

MAC PDU

7

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 6

<–

MAC PDU (CC1)

8

The SS changes Cell1, Cell 3 and Cell 6 parameters according to the row "T1" in table 8.2.2.14.1.3.2-1.

9

The SS transmits an RRCConnectionReconfiguration message with mobilityControlInfo on Cell 1 to order the UE to perform handover to Cell 3 and sCellToAddModList with SCell Cell 1 addition and sCellState indicates activated.

<–

RRCConnectionReconfiguration

10

UE transmits an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the handover and SCell addition of Cell 1 in activated mode.

–>

RRCConnectionReconfigurationComplete

11

100 ms after step 13, the SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

12

Check: Does the UE transmit a Scheduling Request on PUCCH

–>

(SR)

2

P

13

The SS sends an UL grant suitable for transmitting loop back PDU on Cell 3

<–

(UL Grant)

14

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 11

–>

MAC PDU

15

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 14

<–

MAC PDU (CC1)

16

The SS changes Cell1, Cell 3 and Cell 6 parameters according to the row "T2" in table 8.2.2.14.1.3.2-1.

17

The SS transmits an RRCConnectionReconfiguration message with mobilityControlInfo on Cell 3 to order the UE to perform handover to Cell 6 and maintaining SCell Cell 1 and sCellState indicates activated.

<–

RRCConnectionReconfiguration

18

UE transmits an RRCConnectionReconfigurationComplete message on Cell 6 to confirm the successful completion of the handover and maintaining SCell Cell 1 in activated mode.

–>

RRCConnectionReconfigurationComplete

19

100 ms after step 25, the SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU )

<–

MAC PDU (CC2)

20

Check: Does the UE transmit a Scheduling Request on PUCCH

–>

(SR)

3

P

21

The SS sends an UL grant suitable for transmitting loop back PDU on Cell 6

<–

(UL Grant)

22

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 19

–>

MAC PDU

23

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 22

<–

MAC PDU (CC1)

8.2.2.14.1.3.3 Specific message contents

Table 8.2.2.14.1.3.3-1: Conditions for specific message contents

Condition

Explanation

Uplink_CA

The UE supports carrier aggregation in UL under the test band.

Band > 64

If band > 64 is selected

Table 8.2.2.14.1.3.3-2: RRCConnectionReconfiguration (step 1, Table 8.2.2.14.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-ActivatedSCell

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToAddModListExt-v1430

SCellToAddModListExt-v1430-ActivatedSCell

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.2.14.1.3.3-3: RadioResourceConfigDedicated-ActivatedSCell (Table 8.2.2.14.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AAA RadioResourceConfigDedicated-SCell_AddMod

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-ActivatedSCell ::= SEQUENCE {

mac-MainConfig

MAC-MainConfig-ActivatedSCell

}

Table 8.2.2.14.1.3.3-4: MAC-MainConfig-ActivatedSCell (Table 8.2.2.14.1.3.3-3)

Derivation Path: 36.508 clause 4.8.2 table 4.8.2.1.5-1 MAC-MainConfig-RBC condition DRX_L

Information Element

Value/remark

Comment

Condition

MAC-MainConfig ActivatedSCell::= SEQUENCE {

timeAlignmentTimerDedicated

Infinity

mac-MainConfig-v1020 SEQUENCE {

sCellDeactivationTimer-r10

rf32

}

}

Table 8.2.2.14.1.3.3-5: SCellToAddMod-r10-f2-Add (Table 8.2.2.14.1.3.3-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.2.14.1.3.3-6: RadioResourceConfigCommonSCell-r10-f2 (Table 8.2.2.14.1.3.3-5)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 3

}

}

Table 8.2.2.14.1.3.3-7: RadioResourceConfigDedicatedSCell-r10-f2 (Table 8.2.2.14.1.3.3-5)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA

Table 8.2.2.14.1.3.3-8: SCellToAddModListExt-v1430-ActivatedSCell (Table 8.2.2.14.1.3.3-2)

Derivation Path: 36.331 clause

Information Element

Value/remark

Comment

Condition

SCellToAddModListExt-v1430-ActivatedSCell ::= SEQUENCE (SIZE (1..maxSCell-r13)) OF SEQUENCE {

1 entry

sCellState-r15

activated

}

Table 8.2.2.14.1.3.3-9: RRCConnectionReconfiguration (step 9, Table 8.2.2.14.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated-ActivatedSCell

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10 SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

SCellIndex-r10[1]

1

}

sCellToAddModList-r10

SCellToAddMod-r10-f1-Add

SCell addition for Cell 1

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToAddModListExt-v1430

SCellToAddModListExt-v1430-ActivatedSCell

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.2.14.1.3.3-10: MobilityControlInfo (Table 8.2.2.14.1.3.3-9)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.2.14.1.3.3-11: RadioResourceConfigDedicated-ActivatedSCell (Table 8.2.2.14.1.3.3-9)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AAA RadioResourceConfigDedicated-SCell_AddMod

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-SCell_AddMod ::= SEQUENCE {

mac-MainConfig

MAC-MainConfig-ActivatedSCell

}

Table 8.2.2.14.1.3.3-12: MAC-MainConfig-ActivatedSCell (Table 8.2.2.14.1.3.3-11)

Derivation Path: 36.508 clause 4.8.2 table 4.8.2.1.5-1 MAC-MainConfig-RBC condition DRX_L

Information Element

Value/remark

Comment

Condition

MAC-MainConfig-ActivatedSCell ::= SEQUENCE {

timeAlignmentTimerDedicated

Infinity

mac-MainConfig-v1020 SEQUENCE {

sCellDeactivationTimer-r10

rf32

}

}

Table 8.2.2.14.1.3.3-13: SCellToAddMod-r10-f1-Add (Table 8.2.2.14.1.3.3-9)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

cellIdentification-r10[1] SEQUENCE {

physCellId-r10[1]

Physical Cell Identity of Cell 1

dl-CarrierFreq-r10[1]

Same downlink EARFCN as used for Cell 1

dl-CarrierFreq-r10[1]

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10[1]

RadioResourceConfigCommonSCell-r10-f1

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f1

dl-CarrierFreq-v1090[1]

Same downlink EARFCN as used for Cell 1

Band > 64

}

Table 8.2.2.14.1.3.3-14: RadioResourceConfigCommonSCell-r10-f1 (Table 8.2.2.14.1.3.3-13)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 1

}

}

Table 8.2.2.14.1.3.3-15: RadioResourceConfigDedicatedSCell-r10-f1 (Table 8.2.2.14.1.3.3-13)

Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA

Table 8.2.2.14.1.3.3-16: SCellToAddModListExt-v1430-ActivatedSCell (Table 8.2.2.14.1.3.3-9)

Derivation Path: 36.331 clause

Information Element

Value/remark

Comment

Condition

SCellToAddModListExt-v1430-ActivatedSCell ::= SEQUENCE (SIZE (1..maxSCell-r13)) OF SEQUENCE {

1 entry

sCellState-r15

activated

}

Table 8.2.2.14.1.3.3-17: RRCConnectionReconfiguration (step 17, Table 8.2.2.14.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 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 {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToAddModListExt-v1430

SCellToAddModListExt-v1430-ActivatedSCell

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.2.14.1.3.3-18: MobilityControlInfo (Table 8.2.2.14.1.3.3-17)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 6

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 6

}

}

Table 8.2.2.14.1.3.3-19: SCellToAddModListExt-v1430-ActivatedSCell (Table 8.2.2.14.1.3.3-17)

Derivation Path: 36.331 clause

Information Element

Value/remark

Comment

Condition

SCellToAddModListExt-v1430-ActivatedSCell ::= SEQUENCE (SIZE (1..maxSCell-r13)) OF SEQUENCE {

1 entry

sCellState-r15

activated

}