21.3.12 CA / Start SC-PTM reception on PCell / Continue MBMS reception after swap of SCell and PCell

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

21.3.12.1 CA / Start SC-PTM reception on PCell / Continue SC-PTM reception after swap of SCell and PCell / Intra-band Contiguous CA

21.3.12.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC CONNECTED state with SC-PTM capable PCell and SCell activate and both broadcasting SIB15 and UE is interested to receive a SC-PTM service}

ensure that {

when { SIB15 indicates that the MBMS service is available on the frequency of the PCell }

then { UE starts SC-PTM reception on the Pcell }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with active PCell and SCell and ongoing SC-PTM reception on the PCell }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to reconfigure the SCell as PCell and the PCell as SCell and sends an RRCConnectionReconfigurationComplete message }

then { UE continues SC-PTM reception on the new SCell }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with active PCell and SCell and ongoing SC-PTM reception on the SCell }

ensure that {

when { UE receives an RRCConnectionReconfiguration message to reconfigure the SCell as PCell and the PCell as SCell and sends an RRCConnectionReconfigurationComplete message }

then { UE continues SC-PTM reception on the new PCell }

}

21.3.12.1.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.306, clause 4.3.5.2 and TS 36.331, clauses 5.8.5.3 and 5.8.5.3a. Unless otherwise stated these are Rel-13 requirements.

[TS 36.306, clause 4.3.5.2]

This field defines the carrier aggregation, MIMO and MBMS reception capabilities (via MBSFN or SC-PTM) supported by the UE for configurations with inter-band, intra-band non-contiguous, intra-band contiguous carrier aggregation and without carrier aggregation. For each band in a band combination the UE provides the supported CA bandwidth classes and the corresponding MIMO capabilities for downlink. The UE also has to provide the supported uplink CA bandwidth class and the corresponding MIMO capability for at least one band in the band combination. Applicability of provisioning uplink CA bandwidth class for each band in the band combinations is defined in TS 36.101 [6]. A MIMO capability applies to all carriers of a bandwidth class of a band in a band combination. For bandwidth classes that include multiple component carriers (i.e. bandwidth classes B, C, D and so on), the UE may also indicate a separate MIMO capability that applies to each individual carrier of a bandwidth class of a band in a band combination.

(…)

The UE that supports MBMS reception via MBSFN shall support MBMS reception via MBSFN on the PCell of MCG, and it may indicate support for MBMS reception via MBSFN on configured SCells (mbms-SCell) and for any cell that may be additionally configured as an SCell (mbms-NonServingCell) according to this field. The UE that supports MBMS reception via SC-PTM shall support MBMS reception via SC-PTM on the PCell of MCG, and it may indicate support for MBMS reception via SC-PTM on configured SCells (scptm-SCell) and for any cell that may be additionally configured as an SCell (scptm-NonServingCell) according to this field. The UE shall apply the system information acquisition and change monitoring procedure relevant for MBMS operation for these cells.

The UE indicating more than one frequency in the MBMSInterestIndication message as specified in TS 36.331 [5] shall support simultaneous reception of MBMS (via MBSFN or SC-PTM) on the indicated frequencies when the frequencies of the configured serving cells and the indicated frequencies belong to at least one band combination.

(…)

[TS 36.331, clause 5.8.5.3]

The UE shall:

1> consider a frequency to be part of the MBMS frequencies of interest if the following conditions are met:

2> at least one MBMS session the UE is receiving or interested to receive via an MRB is ongoing or about to start; and

NOTE 1: The UE may determine whether the session is ongoing from the start and stop time indicated in the User Service Description (USD), see 3GPP TS 36.300 [9] or 3GPP TS 26.346 [57].

2> for at least one of these MBMS sessions SystemInformationBlockType15 acquired from the PCell includes for the concerned frequency one or more MBMS SAIs as indicated in the USD for this session; and

NOTE 2: The UE considers a frequency to be part of the MBMS frequencies of interest even though E-UTRAN may (temporarily) not employ an MRB for the concerned session. I.e. the UE does not verify if the session is indicated on MCCH.

2> the UE is capable of simultaneously receiving the set of MBMS frequencies of interest, regardless of whether a serving cell is configured on each of these frequencies or not; and

2> the supportedBandCombination the UE included in UE-EUTRA-Capability contains at least one band combination including the set of MBMS frequencies of interest;

NOTE 3: Indicating a frequency implies that the UE supports SystemInformationBlockType13 acquisition for the concerned frequency i.e. the indication should be independent of whether a serving cell is configured on that frequency.

NOTE 4: When evaluating which frequencies it can receive simultaneously, the UE does not take into account the serving frequencies that are currently configured i.e. it only considers MBMS frequencies it is interested to receive.

NOTE 5: The set of MBMS frequencies of interest includes at most one frequency for a given physical frequency. The UE only considers a physical frequency to be part of the MBMS frequencies of interest if it supports at least one of the bands indicated for this physical frequency in SystemInformationBlockType1 (for serving frequency) or SystemInformationBlockType15 (for neighbouring frequencies). In this case, E-UTRAN may assume the UE supports MBMS reception on any of the bands supported by the UE (i.e. according to supportedBandCombination).

[TS 36.331, clause 5.8.5.3a]

The UE shall:

1> consider a MBMS service to be part of the MBMS services of interest if the following conditions are met:

2> the UE is SC-PTM capable; and

2> the UE is receiving or interested to receive this service via an SC-MRB; and

2> one session of this service is ongoing or about to start; and

2> one or more MBMS SAIs in the USD for this service is included in SystemInformationBlockType15 acquired from the PCell for a frequency belonging to the set of MBMS frequencies of interest, determined according to 5.8.5.3.

21.3.12.1.3 Test Description

21.3.12.1.3.1 Pre-test conditions

System Simulator:

– 2 E-UTRA cells. Cell 1 is the PCell, Cell3 is an inactive SCell to be added according to [18] cl. 6.3.4.

– SCPTMConfiguration message as defined in TS 36.508 [18] Table 4.6.1-18a is transmitted on Cell 1.

– System information combination 26 as defined in TS 36.508[18] clause 4.4.3.1 is used in Cell 1.

– System information combination 3 as defined in TS 36.508[18] clause 4.4.3.1 is used in Cell 3.

UE:

– The UE is configured to receive MBMS services.

– The UE has in the signalled IE “supportedBandCombination” indicated support of the CA configuration for the frequency of Cell 1.

– The UE is capable to receiving SCPTM on SCell.

Preamble:

– UE is in state Loopback Activated (State 4) with UE TEST LOOP MODE F on Cell 1 according to [18].

– The UE is made interested in receiving a MBMS service with MBMS Service ID=1 associated with the MBMS SAI (1) broadcasted in SCPTMConfiguration.

– The UE is made aware that the MBMS service is active.

21.3.12.1.3.2 Test procedure sequence

Table 21.3.12.1.3.2-1 illustrates the downlink power levels to be applied for Cell 1 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while rows 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 21.3.12.1.3.2-1: Power levels

Parameter

Unit

Cell 1

Cell 3

Remark

T0

-70

-96

Power level for Cell 1 is such that Ms > Thresh + Hys

T1

Cell-specific RS EPRE

dBm/15kHz

-96

-70

Power level for Cell 1 is such that entry condition for event A2 is satisfied Ms + Hys < Thresh

T2

-70

-96

Power level for Cell 3 is such that exit condition for event A2 is satisfied Ms > Thresh + Hys

Note: The total tolerance used is the sum of downlink signal level uncertainty (TS 36.508 clause 6.2.2.1) and absolute UE measurement accuracy (TS 36.133 clause 9).

Table 21.3.12.1.3.2-2: 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 on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

3

The SS transmits a Paging message including a systemInfoModification for Cell1.

<–

Paging

4

From the beginning of the next modification period the SS starts broadcast of SystemInformationBlockType15 according to system information combination 28 as defined in TS 36.508[18] clause 4.4.3.1 on Cell 1 and according to system information combination 18 as defined in TS 36.508[18] clause 4.4.3.1 on Cell 3. SystemInformationBlockType15 on Cell 1 is including mbms-SAI-IntraFreqList-r11 list indicating MBMS SAI=1. SystemInformationBlockType15 on Cell 3 is including mbms-SAI-InterFreqList-r11 list for the frequency of Cell 1 indicating MBMS SAI=1.

<–

SystemInformationBlockType15

5

The UE transmits a MBMSInterestIndication message.

–>

MBMSInterestIndication

6

Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration message

Exception; Step 7 is repeated 5 times

7

The SS transmits 2 MBMS Packets on the SC-MTCH.

<–

MBMS Packets

8

The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message on Cell 1.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

9

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

10

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 9 greater than zero?

(Note: This verifies that UE has received MBMS packets on the PCell providing the MBMS service and started SC-PTM reception)

1

P

11

SS transmits an RRCConnectionReconfiguration message including measConfig to setup intra LTE measurement and reporting for event A2 on Cell 1.

<–

RRCConnectionReconfiguration

12

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

13

SS re-adjusts the cell-specific reference signal level according to row "T1" in table 21.3.12.1.3.2-1.

14

UE transmits a MeasurementReport message to report event A2 for Cell 1

–>

MeasurementReport

15

The SS transmits an RRCConnectionReconfiguration message containing to reconfigure the PCell as SCell and the SCell as PCell

<–

RRCConnectionReconfiguration

16

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

17

Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration message on SCell (Cell 1)

Exception; Step 18 is repeated 5 times

18

The SS transmits 2 MBMS Packets on the SC-MTCH.

<–

MBMS Packets.

19

The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message on Cell 3.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

20

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

21

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 16 greater than the number reported in step 9?

(Note: This verifies that UE continue to receive MBMS packets on Cell 1 after being reconfigured as SCell)

2

P

22

SS transmits an RRCConnectionReconfiguration message on Cell 3 including measConfig to setup intra LTE measurement and reporting for event A2 on Cell 3.

<–

RRCConnectionReconfiguration

23

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

24

SS re-adjusts the cell-specific reference signal level according to row "T2" in table 21.3.12.1.3.2-1.

25

UE transmits a MeasurementReport message to report event A2 for Cell 3

–>

MeasurementReport

26

The SS transmits an RRCConnectionReconfiguration message containing to reconfigure the PCell as SCell and the SCell as PCell

<–

RRCConnectionReconfiguration

27

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

28

Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration message on PCell (Cell 1)

Exception: Step 29 is repeated 5 times

29

The SS transmits 2 MBMS Packets on the SC-MTCH on Cell 1.

<–

MBMS Packets.

30

The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message on Cell 1

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

31

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

32

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 31 greater than the number reported in step 20?

(Note: This verifies that UE continues to receive MBMS packets on Cell 1 after being reconfigured as PCell)

3

P

21.3.12.1.3.3 Specific message contents

Table 21.3.12.1.3.3-0: Conditions for specific message contents
in Tables 21.3.12.1.3.3-4, 21.3.12.1.3.3-5, 21.3.12.1.3.3-6, 21.3.12.1.3.3-9, 21.3.12.1.3.3-13, 21.3.12.1.3.3-14 21.3.12.1.3.3-15, 21.3.12.1.3.3-16, 21.3.12.1.3.3-18, 21.3.12.1.3.3-22, 21.3.12.1.3.3-23 21.3.12.1.3.3-24 and 21.3.12.1.3.3-25

Condition

Explanation

Uplink_CA

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

Band > 64

This condition applies if the band number is bigger than 64.

Table 21.3.12.1,3.3-1: SystemInformationBlockType15 for Cell 1 (from step 4 and all subsequent steps, Table 21.3.12.1.3.2-2)

Derivation Path: 36.508 table 4.4.3.3-14, condition SCPTM_intraFreq.

Table 21.3.12.1.3.3-2: SystemInformationBlockType15 for Cell 3 (from step 4 and all subsequent steps, Table 21.3.12.1.3.2-2)

Derivation Path: 36.508 table 4.4.3.3-14, condition SCPTM_interFreq.

SystemInformationBlockType15 ::= SEQUENCE {

mbms-SAI-IntraFreq-r11 SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) }

Not present

mbms-SAI-InterFreqList-r11[1] SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE {

1 entry

dl-CarrierFreq-r11

Downlink EARFCN for Cell 1, see [18] table 6.3.1.2-1.

mbms-SAI-List-r11[1] SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) }

1

1 entry

INTEGER (0..65535)

}

}

Table 21.3.12.1.3.3-3: RRCConnectionReconfiguration (step 1, Table 21.3.12.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

Not present

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 21.3.12.1.3.3-4: SCellToAddMod-r10-f2-Add (Table 21.3.12.1.3.3-3)

Derivation Path: 36.508 clause 4.6. 3 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

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

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2

}

Table 21.3.12.1.3.3-5: RadioResourceConfigCommonSCell-r10-f2 (Table 21.3.12.1.3.3-4)

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 21.3.12.1.3.3-6: RadioResourceConfigDedicatedSCell-r10-f2 (Table 21.3.12.1.3.3-4)

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 21.3.12.1.3.3-7: MBMSInterestIndication (step 5, Table 21.3.12.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-4AC condition SC-PTM

Information Element

Value/remark

Comment

Condition

criticalExtensions CHOICE {

c1 CHOICE{

mbms-FreqList-r11[1] SEQUENCE (SIZE (1..maxFreqMBMS-r11)) OF { INTEGER (0..maxEARFCN2) }

Same EARFCN as used for Cell 1

INTEGER (0..maxEARFCN2)

}

}

Table 21.3.12.1.3.3-8: RRCConnectionReconfiguration (step 11, Table 21.3.12.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 21.3.12.1.3.3-9: MeasConfig (Table 21.3.12.1.3.3-8)

Derivation path: 36.508 clause 4.6.6 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-A2

reportConfig[1]

ReportConfigEUTRA-A2-H

}

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

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A2

}

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

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f 1

}

}

}

Table 21.3.12.1.3.3-10: ReportConfigEUTRA-A2-H (Table 21.3.12.1.3.3-9)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-5 ReportConfigEUTRA-A2(-83)

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

hysteresis

6

3 dB

}

}

}

Table 21.3.12.1.3.3-11: MeasurementReport (step 14, Table 21.3.12.1.3.2-2)

Derivation path: 36.508 table clause 4.6.1 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 {}

Not present

measResultServFreqList-r10 SEQUENCE {}

Not checked

}

}

}

}

}

Table 21.3.12.1.3.3-12: RRCConnectionReconfiguration (step 15, Table 21.3.12.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-f1-Add

SCell addition for Cell 1

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 21.3.12.1.3.3-13: MobilityControlInfo (Table 21.3.12.1.3.3-12)

Derivation Path: clause 4.6.5 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

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3.

}

}

Table 21.3.12.1.3.3-14: SCellToAddMod-r10-f1-Add (Table 21.3.12.1.3.3-12)

Derivation Path: 36.508 clause 4.6. 3 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

Physical Cell Identity of Cell 1

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 1

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 1

Band > 64

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f1

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f1

}

Table 21.3.12.1.3.3-15: RadioResourceConfigCommonSCell-r10-f1 (Table 21.3.12.1.3.3-14)

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

}

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 1

optional

FDD

Not present

TDD

additionalSpectrumEmissionSCell-r10

Same additionalSpectrumEmission as used for Cell 1

}

}

}

Table 21.3.12.1.3.3-16: RadioResourceConfigDedicatedSCell-r10-f1 (Table 21.3.12.1.3.3-14)

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 21.3.12.1.3.3-17: RRCConnectionReconfiguration (step 22, Table 21.3.12.1.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 21.3.12.1.3.3-18: MeasConfig (Table 21.3.12.1.3.3-17)

Derivation path: 36.508 clause 4.6.6 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-A2

reportConfig[1]

ReportConfigEUTRA-A2-H

}

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

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A2

}

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

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Table 21.3.12.1.3.3-19: ReportConfigEUTRA-A2-H (Table 21.3.12.1.3.3-18)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-5 ReportConfigEUTRA-A2(-83)

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

hysteresis

6

3 dB

}

}

}

Table 21.3.12.1.3.3-20: MeasurementReport (step 25, Table 21.3.12.1.3.2-2)

Derivation path: 36.508 table clause 4.6.1 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 3

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {}

Not present

measResultServFreqList-r10 SEQUENCE {}

Not checked

}

}

}

}

}

Table 21.3.12.1.3.3-21: RRCConnectionReconfiguration (step 26, Table 21.3.12.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 1

}

sCellToAddModList-r10

SCellToAddMod-r10-f2-Add

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 21.3.12.1.3.3-22: MobilityControlInfo (Table 21.3.12.1.3.3-21)

Derivation Path: clause 4.6.5 table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 1

}

carrierFreq

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1.

}

}

Table 21.3.12.1.3.3-23: SCellToAddMod-r10-f2-Add (Table 21.3.12.1.3.3-21)

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 {

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

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

radioResourceConfigCommonSCell-r10

RadioResourceConfigCommonSCell-r10-f2

radioResourceConfigDedicatedSCell-r10

RadioResourceConfigDedicatedSCell-r10-f2

}

Table 21.3.12.1.3.3-24: RadioResourceConfigCommonSCell-r10-f2 (Table 21.3.12.1.3.3-23)

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 21.3.12.1.3.3-25: RadioResourceConfigDedicatedSCell-r10-f2 (Table 21.3.12.1.3.3-23)

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

}

}

}

21.3.12.2 CA / Start SC-PTM reception on PCell / Continue SC-PTM reception after swap of SCell and PCell / Inter-band CA

21.3.12.2.1 Test Purpose (TP)

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

21.3.12.2.2 Conformance requirements

Same as TC 21.3.12.1.

21.3.12.2.3 Test description

21.3.12.2.3.1 Pre-test conditions

Same as test case 21.3.12.1 with the following differences:

– Cells configuration: Cell 10 replaces Cell 3

21.3.12.2.3.2 Test procedure sequence

Same as test case 21.3.12.1 with the following differences:

– Cells configuration: Cell 10 replaces Cell 3.

21.3.12.2.3.3 Specific message contents

Same as test case 21.3.12.1 with the following differences:

– Cells configuration: Cell 10 replaces Cell 3.