8.4.2 Inter-RAT handover UTRA to E-UTRA

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.4.2.1 Void

8.4.2.2 Inter-RAT handover / From UTRA PS to E-UTRA / Data

8.4.2.2.1 Test Purpose (TP)

(1)

with { UE in UTRA CELL_DCH(PS-DCCH+DTCH_DCH) state }

ensure that {

when { UE receives a HANDOVER FROM UTRAN COMMAND message including the eutra-Message }

then { UE transmits an RRCConnectionReconfigurationComplete message and enters E-UTRA RRC_CONNECTED state }

}

8.4.2.2.2 Conformance requirements

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

[TS 36.331, clause 5.4.2.3]

If the UE is able to comply with the configuration included in the RRCConnectionReconfiguration message, the UE shall:

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> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

1> set the C-RNTI to the value of the newUE-Identity;

1> for the target cell, apply the downlink bandwidth indicated by the dl-Bandwidth;

1> for the target cell, apply the uplink bandwidth indicated by (the absence or presence of) the ul-Bandwidth;

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

1> forward the nas-SecurityParamToEUTRA to the upper layers;

1> derive the KeNB key, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the indicated integrity protection algorithm and the KRRCint key immediately, i.e. the indicated 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;

1> configure lower layers to apply the indicated ciphering algorithm, the KRRCenc key and the KUPenc key immediately, i.e. the indicated 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 RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration;

1> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the configuration that do not require the UE to know the SFN of the target cell;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

2> enter E-UTRA RRC_CONNECTED, upon which the procedure ends;

8.4.2.2.3 Test description

8.4.2.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 5.

– System information combination 4 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 Registered, Idle mode (state 2) on Cell 1 (serving cell) according to [18].

8.4.2.2.3.2 Test procedure sequence

Table 8.4.2.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. Subsequent configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour description in Table 8.4.2.2.3.2-2.

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

Parameter

Unit

Cell 1

Cell 5

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

-90

The power level values are assigned to satisfy Threshx,high < Srxlevcell 5.

CPICH Ec (UTRA FDD)

dBm/3.84 MHz

-65

PCCPCH Ec (UTRA LCR TDD)

dBm/1.28 MHz

-65

T2

Cell-specific RS EPRE

dBm/15kHz

-70

The power level values are such that entering conditions for event 3a are satisfied.

CPICH Ec (UTRA FDD)

dBm/3.84 MHz

-85

PCCPCH Ec (UTRA LCR TDD)

dBm/1.28 MHz

-85

Table 8.4.2.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

Wait for 6 s for UE to receive system information.

1

The SS changes Cell 1 and Cell 5 level according to the row "T1" in table 8.4.2.2.3.2-1.

2

Generic test procedure in TS 36.508 subclause 6.4.2.8 is performed on Cell 5.

NOTE: The UE performs an RAU procedure and the RRC connection is released.

Exception: Steps 2Ba1 to 2Ba1b1 describe optional behaviour that depend on the UE capability.

2Aa1-2Aa3Aa6

Void

2Ba1

IF pc_IMS = TRUE THEN SS starts 6s timer

2Ba1a1-2Ba1a3a6

The procedure defined in TS 36.523-3 Table 10.1.2.1-2 Steps 1-4a6 is performed

2Ba1a4

SS releases RRC Connection

2Ba1a5

Stop 6s timer

2Ba1b1

The 6s timer expires

3-4

Void

4A-4E

Step 7 to 11 of test procedure in TS 34.123-1 subclause 12.9.14.4 is performed on Cell 5 using the UTRA reference radio bearer parameters and combination “UTRA PS RB” according to TS 36.508 subclause 4.8.3 and Table 4.8.3-1.

NOTE: The UE performs Network initiated RAB re-establishment in a UTRAN cell.

For UTRAN FDD, EXCEPTION: Steps 5a1 to 5a2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.

For UTRAN TDD, goto step8.

5a1

IF pc_UTRA_CompressedModeRequired THEN the SS transmits a PHYSICAL CHANNEL RECONFIGURATION message on Cell 5 including the DPCH compressed mode info.

<–

PHYSICAL CHANNEL RECONFIGURATION

5a2

The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on Cell 5.

–>

PHYSICAL CHANNEL RECONFIGURATION COMPLETE

6-7

Void

8

The SS transmits a MEASUREMENT CONTROL message to setup inter-RAT measurement on Cell 5.

<–

MEASUREMENT CONTROL

9

The SS changes Cell 1 and Cell 5 level according to the row "T2" in table 8.4.2.2.3.2-1.

10

The UE transmits a MEASUREMENT REPORT message on Cell 5 including the E-UTRA event results.

–>

MEASUREMENT REPORT

11

The SS transmits a HANDOVER FROM UTRAN COMMAND message on Cell 5.

<–

HANDOVER FROM UTRAN COMMAND

12

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 1 using the security key derived from the new KeNB?

–>

RRCConnectionReconfigurationComplete

1

P

12A

Generic test procedure in TS 36.508 subclause 6.4.2.10 is performed on Cell 1.

NOTE: The UE performs tracking area updating procedure without ISR and security reconfiguration after successful completion of handover from UTRA.

13-19

Void

EXCEPTION: Steps 19Aa1 to 19Aa9 describe optional behaviour that depend on the UE capability

19Aa1-19Aa2b1

The procedure defined in TS 36.508 subclause 4.5A.3 Steps 10a2a1-10a2b1 is performed

20

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.4.2.2.3.3 Specific message contents

Table 8.4.2.2.3.3-1: Void

Table 8.4.2.2.3.3-2: SystemInformationBlockType6 for Cell 1 (preamble, Table 8.4.2.2.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType6 ::= SEQUENCE {

carrierFreqListUTRA-FDD SEQUENCE (SIZE (1..maxUTRA-FDD-Carrier)) OF SEQUENCE {

UTRA-FDD

carrierFreq[n]

Same downlink UARFCN as used for Cell 5

cellReselectionPriority[n]

5

p-MaxUTRA[1]

0

}

carrierFreqListUTRA-TDD SEQUENCE (SIZE (1..maxUTRA-TDD-Carrier)) OF SEQUENCE {

The same number of entries as the configured UTRA TDD carriers

UTRA-TDD

carrierFreq[1]

Same downlink ARFCN as used for Cell 5

cellReselectionPriority[n]

5

p-MaxUTRA[n]

0

}

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 8.4.2.2.3.3-3: Void

Table 8.4.2.2.3.3-4: Void

Table 8.4.2.2.3.3-5: HANDOVER FROM UTRAN COMMAND (step 11, Table 8.4.2.2.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-2

Table 8.4.2.2.3.3-6: RRCConnectionReconfiguration (Table 8.4.2.2.3.3-5)

Derivation Path: 36.508, Table 4.6.1-8, condition HO-TO-EUTRA(1,0)

Table 8.4.2.2.3.3-7: MobilityControlInfo (Table 8.4.2.2.3.3-5)

Derivation Path: 36.508, 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.

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 1.

Band 24 High range

}

carrierFreq

Not present

Band > 64

carrierBandwidth SEQUENCE {

dl-Bandwidth

Downlink system bandwidth under test.

ul-Bandwidth

Uplink Bandwidth under test.

FDD

ul-Bandwidth

Not present

TDD

}

additionalSpectrumEmission

1

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

Band > 64

If band > 64 is selected

Band 24 High range

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

Table 8.4.2.2.3.3-8: SecurityConfigHO (Table 8.4.2.2.3.3-5)

Derivation Path: 36.508, Table 4.6.4-1

Information Element

Value/remark

Comment

Condition

SecurityConfigHO ::= SEQUENCE {

handoverType CHOICE {

interRAT SEQUENCE {

securityAlgorithmConfig SEQUENCE {

cipheringAlgorithm

Set according to PIXIT parameter for default ciphering protection algorithm

integrityProtAlgorithm

Set according to PIXIT parameter for default integrity algorithm

}

nas-SecurityParamToEUTRA

Octets 1 to 4 are arbitrarily selected.

Bits 1 to 3 of octet 5 are set according to PIXIT parameter for default integrity protection algorithm.

Bits 5 to 7 of octet 5 are set according to PIXIT parameter for default ciphering algorithm.

Bits 1 to 3 of octet 6 are arbitrarily selected between ‘000’B and ‘110’B, different from the valid NAS key set identifier of the UE if such a value exists.

Bit 4 of octet 6 is set to 1.

Octets 1 to 4 include the NonceMME value.

Bits 1 to 3 of octet 5 include the Type of integrity protection algorithm

Bits 5 to 7 of octet 5 include the Type of ciphering algorithm.

Bits 1 to 4 of octet 6 include the NAS key set identifier.

}

}

}

Table 8.4.2.2.3.3-9: MEASUREMENT CONTROL (step 8, Table 8.4.2.2.3.2-2)

Derivation Path: 36.508, clause 4.7B.1-3

Information Element

Value/remark

Comment

Condition

– Inter-RAT measurement quantity

– Measurement quantity for UTRAN quality estimate

– Filter coefficient

0

– CHOICE mode

FDD

– Measurement quantity

CPICH RSCP

– CHOICE system

E-UTRA

– Measurement quantity

RSRP

– Filter coefficient

0

– Inter-RAT reporting quantity

– UTRAN estimated quality

FALSE

– CHOICE system

E-UTRA

– Reporting quantity

both

– Reporting cell status

Not present

– CHOICE report criteria

Inter-RAT measurement reporting criteria

– Parameters required for each event

1 entry

– Inter-RAT event identity

3a

– Threshold own system

-66

– W

0

– Threshold other system

-80

– Hysteresis

0

– Time to trigger

10 ms

– Reporting cell status

– CHOICE reported cell

Report cells within active set or within virtual active set or of the other RAT

– Maximum number of reported cells

2

Table 8.4.2.2.3.3-10: System Information Block type 19 for Cell 5 (preamble, Table 8.4.2.2.3.2-2)

Derivation Path: 36.508 clause 4.4.4.1, Table 4.4.4.1-1

Information Element

Value/remark

Comment

Condition

SysInfoType19 ::= SEQUENCE {

utra-PriorityInfoList SEQUENCE {

utra-ServingCell SEQUENCE {

Priority

5

higher priority than E-UTRA

}

}

}

8.4.2.3 Void

8.4.2.4 Inter-RAT handover / From UTRA HSPA to E-UTRA / Data

8.4.2.4.1 Test Purpose (TP)

(1)

with { UE in UTRA CELL_DCH(PS-DCCH+DTCH_HS-DSCH) state }

ensure that {

when { UE receives a HANDOVER FROM UTRAN COMMAND message including the eutra-Message }

then { UE transmits an RRCConnectionReconfigurationComplete message and enters E-UTRA RRC_CONNECTED state }

}

8.4.2.4.2 Conformance requirements

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

[TS 36.331, clause 5.4.2.3]

If the UE is able to comply with the configuration included in the RRCConnectionReconfiguration message, the UE shall:

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> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

1> set the C-RNTI to the value of the newUE-Identity;

1> for the target cell, apply the downlink bandwidth indicated by the dl-Bandwidth;

1> for the target cell, apply the uplink bandwidth indicated by (the absence or presence of) the ul-Bandwidth;

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

1> forward the nas-SecurityParamToEUTRA to the upper layers;

1> derive the KeNB key, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the indicated integrity protection algorithm and the KRRCint key immediately, i.e. the indicated 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;

1> configure lower layers to apply the indicated ciphering algorithm, the KRRCenc key and the KUPenc key immediately, i.e. the indicated 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 RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration;

1> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the configuration that do not require the UE to know the SFN of the target cell;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

2> enter E-UTRA RRC_CONNECTED, upon which the procedure ends;

8.4.2.4.3 Test description

8.4.2.4.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 5.

– System information combination 4 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 Registered, Idle mode (state 2) on Cell 1 (serving cell) according to [18].

8.4.2.4.3.2 Test procedure sequence

Table 8.4.2.4.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. Subsequent configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour description in Table 8.4.2.4.3.2-2.

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

Parameter

Unit

Cell 1

Cell 5

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

-90

The power level values are assigned to satisfy Threshx,high < Srxlevcell 5.

CPICH Ec (UTRA FDD)

dBm/3.84 MHz

-65

PCCPCH Ec(UTRA LCR TDD)

dBm/1.28 MHz

-65

T2

Cell-specific RS EPRE

dBm/15kHz

-70

The power level values are such that entering conditions for event 3a are satisfied.

CPICH Ec (UTRA FDD)

dBm/3.84 MHz

-85

PCCPCH Ec (UTRA LCR TDD)

dBm/1.28 MHz

-85

Table 8.4.2.4.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 1 and Cell 5 level according to the row "T1" in table 8.4.2.4.3.2-1.

2

Generic test procedure in TS 36.508 subclause 6.4.2.8 is performed on Cell 5.

NOTE: The UE performs an RAU procedure and the RRC connection is released.

Exception: Steps 2Aa1 to 2Aa1b1 describe optional behaviour that depend on the UE capability.

2Aa1

IF pc_IMS = TRUE THEN SS starts 6s timer

2Aa1a1-2Aa1a3a6

The procedure defined in TS 36.523-3 Table 10.1.2.1-2 Steps 1-4a6 is performed

2Aa1a4

SS releases RRC Connection

2Aa1a5

Stop 6s timer

2Aa1b1

The 6s timer expires

3-4

Void

4A-4E

Step 7 to 11 of test procedure in TS 34.123-1 subclause 12.9.14.4 is performed on Cell 5 using the UTRA reference radio bearer parameters and combination “UTRA HSDPA RB” according to TS 36.508 subclause 4.8.3 and Table 4.8.3-1.

NOTE: The UE performs Network initiated RAB re-establishment in a UTRAN cell.

UTRAN FDD: EXCEPTION: Steps 5a1 to 5a2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.

UTRAN TDD : go to step 8

5a1

IF pc_UTRA_CompressedModeRequired THEN the SS transmits a PHYSICAL CHANNEL RECONFIGURATION message on Cell 5 including the DPCH compressed mode info.

<–

PHYSICAL CHANNEL RECONFIGURATION

5a2

The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on Cell 5.

–>

PHYSICAL CHANNEL RECONFIGURATION COMPLETE

6-7

Void

8

The SS transmits a MEASUREMENT CONTROL message to setup inter-RAT measurement on Cell 5.

<–

MEASUREMENT CONTROL

9

The SS changes Cell 1 and Cell 5 level according to the row "T2" in table 8.4.2.4.3.2-1.

10

The UE transmits a MEASUREMENT REPORT message on Cell 5 including the E-UTRA event results.

–>

MEASUREMENT REPORT

11

The SS transmits a HANDOVER FROM UTRAN COMMAND message on Cell 5.

<–

HANDOVER FROM UTRAN COMMAND

12

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 1 using the security key derived from the new KeNB?

–>

RRCConnectionReconfigurationComplete

1

P

12A

Generic test procedure in TS 36.508 subclause 6.4.2.10 is performed on Cell 1.

NOTE: The UE performs tracking area updating procedure without ISR and security reconfiguration after successful completion of handover from UTRA.

13-19

Void

EXCEPTION: Steps 19Aa1 to 19Aa9 describe optional behaviour that depend on the UE capability

19Aa1-19Aa2b1

The procedure defined in TS 36.508 subclause 4.5A.3 Steps 10a2a1-10a2b1 is performed

20

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.4.2.4.3.3 Specific message contents

Table 8.4.2.4.3.3-1: Void

Table 8.4.2.4.3.3-2: SystemInformationBlockType6 for Cell 1 (preamble, Table 8.4.2.4.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType6 ::= SEQUENCE {

carrierFreqListUTRA-FDD SEQUENCE (SIZE (1..maxUTRA-FDD-Carrier)) OF SEQUENCE {

UTRA-FDD

carrierFreq[n]

Same downlink UARFCN as used for Cell 5

cellReselectionPriority[n]

5

p-MaxUTRA[n]

0

}

carrierFreqListUTRA-TDD SEQUENCE (SIZE (1..maxUTRA-TDD-Carrier)) OF SEQUENCE {

UTRA-TDD

carrierFreq[n]

Same downlink UARFCN as used for Cell 5

cellReselectionPriority[n]

5

p-MaxUTRA[n]

0

}

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 8.4.2.4.3.3-3: Void

Table 8.4.2.4.3.3-4: Void

Table 8.4.2.4.3.3-5: HANDOVER FROM UTRAN COMMAND (step 11, Table 8.4.2.4.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-2

Table 8.4.2.4.3.3-6: RRCConnectionReconfiguration (Table 8.4.2.4.3.3-5)

Derivation Path: 36.508, Table 4.6.1-8, condition HO-TO-EUTRA(1,0)

Table 8.4.2.4.3.3-7: MobilityControlInfo (Table 8.4.2.4.3.3-5)

Derivation Path: 36.508, 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.

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 1.

Band 24 High range

}

carrierFreq

Not present

Band > 64

carrierBandwidth SEQUENCE {

dl-Bandwidth

Downlink system bandwidth under test.

ul-Bandwidth

Uplink Bandwidth under test.

FDD

ul-Bandwidth

Not present

TDD

}

additionalSpectrumEmission

1

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

Band > 64

If band > 64 is selected

Band 24 High range

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

Table 8.4.2.4.3.3-8: SecurityConfigHO (Table 8.4.2.4.3.3-5)

Derivation Path: 36.508, Table 4.6.4-1

Information Element

Value/remark

Comment

Condition

SecurityConfigHO ::= SEQUENCE {

handoverType CHOICE {

interRAT SEQUENCE {

securityAlgorithmConfig SEQUENCE {

cipheringAlgorithm

Set according to PIXIT parameter for default ciphering protection algorithm

integrityProtAlgorithm

Set according to PIXIT parameter for default integrity algorithm

}

nas-SecurityParamToEUTRA

Octets 1 to 4 set to 11223344.

Bits 1 to 3 of octet 5 are set according to PIXIT parameter for default integrity protection algorithm.

Bits 5 to 7 of octet 5 are set according to PIXIT parameter for default ciphering algorithm.

Bits 1 to 3 of octet 6 are set to the NAS key set identifier of the current security context.

Bit 4 of octet 6 is set to 1.

Octets 1 to 4 include the NonceMME value and are arbitrarily selected.

Bits 1 to 3 of octet 5 include the Type of integrity protection algorithm

Bits 5 to 7 of octet 5 include the Type of ciphering algorithm.

Bits 1 to 4 of octet 6 include the NAS key set identifier.

}

}

}

Table 8.4.2.4.3.3-9: PHYSICAL CHANNEL RECONFIGURATION (step 5a1, Table 8.4.2.4.3.2-2)

Derivation Path: 34.108 clause 9.1.1 (PHYSICAL CHANNEL RECONFIGURATION message)

Information Element

Value/remark

– CHOICE mode

FDD

– DPCH compressed mode info

– TGPSI

1

– TGPS Status Flag

deactivate

– TGCFN

Not Present

– Transmission gap pattern sequence configuration parameters

– TGMP

FDD Measurement

– TGPRC

Infinity

– TGSN

8

– TGL1

10

– TGL2

Not Present

– TGD

270

– TGPL1

12

– TGPL2

Not Present

– RPP

mode 0

– ITP

mode 0

– CHOICE UL/DL Mode

UL and DL, UL only, or DL only, depending on UE capability

– Downlink compressed mode method

SF/2 or Not present depending on UE capability

– Uplink compressed mode method

Higher Layer Scheduling or Not Present depending on UE capability

– Downlink frame type

B

– DeltaSIR1

20 (2.0)

– DeltaSIRAfter1

10 (1.0)

– DeltaSIR2

Not Present

– DeltaSIRAfter2

Not Present

– N identify abort

Not Present

– T Reconfirm abort

Not Present

Table 8.4.2.4.3.3-10: System Information Block type 19 for Cell 5 (preamble, Table 8.4.2.4.3.2-2)

Derivation Path: 36.508 clause 4.4.4.1, Table 4.4.4.1-1

Information Element

Value/remark

Comment

Condition

SysInfoType19 ::= SEQUENCE {

utra-PriorityInfoList SEQUENCE {

utra-ServingCell SEQUENCE {

Priority

5

higher priority than E-UTRA

}

}

}

8.4.2.5 Void

8.4.2.6 Void

8.4.2.7 CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell addition

8.4.2.7.1 CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell addition / Intra-band Contiguous CA

8.4.2.7.1.1 Test Purpose (TP)

(1)

with { UE in UTRA CELL_DCH(PS-DCCH+DTCH_HS-DSCH) state }

ensure that {

when { UE receives a HANDOVER FROM UTRAN COMMAND message including the eutra-Message with RRCConnectionReconfiguration including the sCellToAddModList }

then { UE transmits an RRCConnectionReconfigurationComplete message and enters E-UTRA RRC_CONNECTED state with both PCell and SCell }

}

8.4.2.7.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: Reference TS 36.331 clause 5.4.2.3, and 5.3.10.3b]

[TS 36.331, clause 5.4.2.3]

If the UE is able to comply with the configuration included in the RRCConnectionReconfiguration message, the UE shall:

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> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target PCell;

1> set the C-RNTI to the value of the newUE-Identity;

1> for the target PCell, apply the downlink bandwidth indicated by the dl-Bandwidth;

1> for the target PCell, apply the uplink bandwidth indicated by (the absence or presence of) the ul-Bandwidth;

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> perform the radio resource configuration procedure as specified in 5.3.10;

1> forward the nas-SecurityParamToEUTRA to the upper layers;

1> derive the KeNB key, as specified in TS 33.401 [32];

1> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the indicated integrity protection algorithm and the KRRCint key immediately, i.e. the indicated 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;

1> configure lower layers to apply the indicated ciphering algorithm, the KRRCenc key and the KUPenc key immediately, i.e. the indicated 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 as specified in 5.3.10.3b;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:

2> perform the proximity indication configuration in accordance with the received reportProximityConfig;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and plmn-Identity stored in VarRLF-Report is equal to the RPLMN:

3> include rlf-InfoAvailable;

2> if the UE has logged measurements available for E-UTRA and plmn-Identity stored in VarLogMeasReport is equal to the RPLMN:

3> include the logMeasAvailable;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration;

1> if the RRCConnectionReconfiguration message does not include rlf-TimersAndConstants set to setup:

2> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

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 1: 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> enter E-UTRA RRC_CONNECTED, upon which the procedure ends;

NOTE 2: 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.

[TS 36.331, clause 5.3.10b]

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.4.2.7.1.3 Test description

8.4.2.7.1.3.1 Pre-test conditions

System Simulator:

– Cell 5 is UTRAN Cell

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

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

– System information combination 9 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 Registered, Idle mode (state 2) on Cell 1 according to [18].

8.4.2.7.1.3.2 Test procedure sequence

Table 8.4.2.7.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. Subsequent configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour description in Table 8.4.2.7.1.3.2-2.

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

Parameter

Unit

Cell 1

Cell 3

Cell 5

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

-90

-90

The power level values are assigned to satisfy Threshx,high < Srxlevcell 5.

CPICH Ec (UTRA FDD)

dBm/3.84 MHz

-65

PCCPCH Ec(UTRA LCR TDD)

dBm/1.28 MHz

-65

T2

Cell-specific RS EPRE

dBm/15kHz

-70

-70

The power level values are such that entering conditions for event 3a are satisfied.

CPICH Ec (UTRA FDD)

dBm/3.84 MHz

-85

PCCPCH Ec (UTRA LCR TDD)

dBm/1.28 MHz

-85

Table 8.4.2.7.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 5, Cell 1 and Cell 3 level according to the row "T1" in table 8.4.2.7.1.3.2-1.

2

Generic test procedure in TS 36.508 subclause 6.4.2.8 is performed on Cell 5.

NOTE: The UE performs an RAU procedure and the RRC connection is released.

Exception: Steps 2Aa1 to 2Aa1b1 describe optional behaviour that depend on the UE capability.

2Aa1

IF pc_IMS = TRUE THEN SS starts 6s timer

2Aa1a1-2Aa1a3a6

The procedure defined in TS 36.523-3 Table 10.1.2.1-2 Steps 1-4a6 is performed

2Aa1a4

SS releases RRC Connection

2Aa1a5

SS Stops 6s timer

2Aa1b1

The 6s timer expires

3-7

Step 7 to 11 of test procedure in TS 34.123-1 subclause 12.9.14.4 is performed on Cell 5 using the UTRA reference radio bearer parameters and combination “UTRA HSDPA RB” according to TS 36.508 subclause 4.8.3 and Table 4.8.3-1.

NOTE: The UE performs Network initiated RAB re-establishment in a UTRAN cell.

EXCEPTION: Steps 8a1 to 8a2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported.

8a1

IF pc_FDD AND pc_UTRA_CompressedModeRequired THEN the SS transmits a PHYSICAL CHANNEL RECONFIGURATION message on Cell 5 including the DPCH compressed mode info.

<–

PHYSICAL CHANNEL RECONFIGURATION

8a2

The UE transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message on Cell 5.

–>

PHYSICAL CHANNEL RECONFIGURATION COMPLETE

9

The SS transmits a MEASUREMENT CONTROL message to setup inter-RAT measurement on Cell 5.

<–

MEASUREMENT CONTROL

10

The SS changes Cell 5, Cell 1 and Cell 3 level according to the row "T2" in table 8.4.2.7.1.3.2-1.

11

The UE transmits a MEASUREMENT REPORT message on Cell 5 including the E-UTRA event results.

–>

MEASUREMENT REPORT

12

The SS transmits a HANDOVER FROM UTRAN COMMAND message on Cell 5.

<–

HANDOVER FROM UTRAN COMMAND

13

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the successful completion of the handover and SCell addition of Cell 3?

–>

RRCConnectionReconfigurationComplete

1

P

13A – 13H

Step 1 to 8 of test procedure in TS36.508 Table 6.4.2.10-1 is performed on Cell1

EXCEPTION: Steps 13Ia1 to 13Ia2b1 describe optional behaviour if UE sends IMS deregistration at steps 2Aa1 to 2Aa1b1

13Ia1-13Ia2b1

The procedure defined in TS 36.508 subclause 4.5A.3 Steps 10a1-10a2b1 is performed

14

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

1

8.4.2.7.1.3.3 Specific message contents

Table 8.4.2.7.1.3.3-0: Conditions for specific message contents
in Tables 8.4.2.7.1.3.3-5 and 8.4.2.7.1.3.3-7

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.4.2.7.1.3.3-1: SystemInformationBlockType6 for Cell 1 (preamble, Table 8.4.2.7.1.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType6 ::= SEQUENCE {

carrierFreqListUTRA-FDD SEQUENCE (SIZE (1..maxUTRA-FDD-Carrier)) OF SEQUENCE {

UTRA-FDD

carrierFreq[n]

Same downlink UARFCN as used for Cell 5

cellReselectionPriority[n]

5

p-MaxUTRA[1]

0

}

carrierFreqListUTRA-TDD SEQUENCE (SIZE (1..maxUTRA-TDD-Carrier)) OF SEQUENCE {

The same number of entries as the configured UTRA TDD carriers

UTRA-TDD

carrierFreq[1]

Same downlink ARFCN as used for Cell 5

cellReselectionPriority[n]

5

p-MaxUTRA[n]

0

}

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 8.4.2.7.1.3.3-2: MEASUREMENT CONTROL (step 9, Table 8.4.2.7.1.3.2-2)

Derivation Path: 36.508, clause 4.7B.1-3

Information Element

Value/remark

Comment

Condition

– Inter-RAT measurement quantity

– Measurement quantity for UTRAN quality estimate

– Filter coefficient

0

– CHOICE mode

FDD

– Measurement quantity

CPICH RSCP

– CHOICE system

E-UTRA

– Measurement quantity

RSRP

– Filter coefficient

0

– Inter-RAT reporting quantity

– UTRAN estimated quality

FALSE

– CHOICE system

E-UTRA

– Reporting quantity

both

– Reporting cell status

Not present

– CHOICE report criteria

Inter-RAT measurement reporting criteria

– Parameters required for each event

1 entry

– Inter-RAT event identity

3a

– Threshold own system

-66

– W

0

– Threshold other system

-55

– Hysteresis

0

– Time to trigger

10 ms

– Reporting cell status

– CHOICE reported cell

Report cells within active set or within virtual active set or of the other RAT

– Maximum number of reported cells

2

Table 8.4.2.7.1.3.3-3: HANDOVER FROM UTRAN COMMAND (step 12, Table 8.4.2.7.1.3.2-2)

Derivation Path: 36.508, Table 4.7B.1-2

Table 8.4.2.7.1.3.3-4: RRCConnectionReconfiguration (Table 8.4.2.7.1.3.3-3)

Derivation Path: 36.508, Table 4.6.1-8, condition HO-TO-EUTRA(1,0) and SCell_AddMod

Table 8.4.2.7.1.3.3-5: MobilityControlInfo (Table 8.4.2.7.1.3.3-4)

Derivation Path: 36.508, 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

carrierBandwidth SEQUENCE {

dl-Bandwidth

Downlink system bandwidth under test.

ul-Bandwidth

Uplink Bandwidth under test.

FDD

ul-Bandwidth

Not present

TDD

}

additionalSpectrumEmission

1

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

Table 8.4.2.7.1.3.3-6: SecurityConfigHO (Table 8.4.2.7.1.3.3-4)

Derivation Path: 36.508, Table 4.6.4-1

Information Element

Value/remark

Comment

Condition

SecurityConfigHO ::= SEQUENCE {

handoverType CHOICE {

interRAT SEQUENCE {

securityAlgorithmConfig SEQUENCE {

cipheringAlgorithm

Set according to PIXIT parameter for default ciphering protection algorithm

integrityProtAlgorithm

Set according to PIXIT parameter for default integrity algorithm

}

nas-SecurityParamToEUTRA

Octets 1 to 4 are arbitrarily selected.

Bits 1 to 3 of octet 5 are set according to PIXIT parameter for default integrity protection algorithm.

Bits 5 to 7 of octet 5 are set according to PIXIT parameter for default ciphering algorithm.

Bits 1 to 3 of octet 6 are arbitrarily selected between ‘000’B and ‘110’B, different from the valid NAS key set identifier of the UE if such a value exists.

Bit 4 of octet 6 is set to 1.

Octets 1 to 4 include the NonceMME value.

Bits 1 to 3 of octet 5 include the Type of integrity protection algorithm

Bits 5 to 7 of octet 5 include the Type of ciphering algorithm.

Bits 1 to 4 of octet 6 include the NAS key set identifier.

}

}

}

Table 8.4.2.7.1.3.3-7: SCellToAddMod-r10-f2 (Table 8.4.2.7.1.3.3-4)

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

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.4.2.7.1.3.3-8: RadioResourceConfigCommonSCell-r10-f2 (Table 8.4.2.7.1.3.3-7)

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

}

}

8.4.2.7.2 CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell addition / Inter-band CA

The scope and description of the present TC is the same as test case 8.4.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.4.2.7.3 CA / RRC connection reconfiguration / Handover UTRAN to E-UTRAN/ Success / SCell addition / Intra-band non-contiguous CA

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

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