8.9 Aerial UE communication

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.9.1 Aerial UE / UE has flight path information available / UE information

8.9.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and UE has flight path information available }

ensure that {

when { receiving UEInformationRequest message including flightPathInfoReport }

then { UE transmits UEInformationResponse messages with flightPathInfoReport}

}

8.9.1.2 Conformance requirements

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

[TS 36.331, clause 5.6.5.3]

Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:

1> if flightPathInfoReq field is present and the UE has flight path information available:

2> include the flightPathInfoReport and set it to include the list of waypoints along the flight path;

2> if the includeTimeStamp is set to TRUE:

3> set the field timeStamp to the time when UE intends to arrive to each waypoint if this information is available at the UE;

8.9.1.3 Test description

8.9.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

Preamble:

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

– The user shall programme into the UE a flightpath containing one waypoint. Note that the method for performing this programming is implementation specific.

8.9.1.3.2 Test procedure sequence

Table 8.9.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a UEInformationRequest message including flightPathInfoReport and TimeStamp set to TRUE on Cell 1.

<–

UEInformationRequest

2

Check: Does the UE transmit a UEInformationResponse message

with flightPathInfoReport and timestamp?

–>

UEInformationResponse

1

P

8.9.1.3.3 Specific message contents

Table 8.9.1.3.3-1: UEInformationRequest (step 1, Table 8.9.1.3.2-1)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-23A UEInformationRequest

Information Element

Value/remark

Comment

Condition

UEInformationRequest-r9 ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

ueInformationRequest-r9 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

idleModeMeasurementReq-r15

Not present

flightPathInfoReq-r15 SEQUENCE {

maxWayPointNumber-r15

1

includeTimeStamp-r15

true

}

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

}

Table 8.9.1.3.3-2: UEInformationResponse (step 2, Table 8.9.1.3.2-1)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-23B UEInformationResponse

Information Element

Value/remark

Comment

Condition

UEInformationResponse-r9 ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

ueInformationResponse-r9 SEQUENCE {

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension

Not checked

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

measResultListIdle-r15

Not checked

flightPathInfoReport-r15 SEQUENCE {

flightPath-r15 SEQUENCE {

1 entry

wayPointLocation-r15 SEQUENCE {

locationCoordinates-r10

Any allowed value

horizontalVelocity-r10

Not checked

gnss-TOD-msec-r10

Not checked

verticalVelocityInfo-r15

Not checked

}

timeStamp-r15

Any allowed value

}

nonCriticalExtension

Not checked

}

}

}

}

}

}

}

}

}

8.9.2 Aerial UE / Measurement configuration control and reporting / Event H1

8.9.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event H1 with event based periodical reporting }

ensure that {

when { Aerial UE height becomes bigger than the absolute treshold plus hysteresis }

then { UE sends MeasurementReport message at regular intervals while entering conditions for event H1 are satisfied }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and periodical measurement reporting triggered by event H1 ongoing}

ensure that {

when { Aerial UE height becomes lower than the absolute treshold minus hysteresis }

then { UE stops sending MeasurementReport message }

}

8.9.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.5.3, 5.5.4.1, 5.5.4.16 and 5.5.5.

[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 RRCConnectionReconfiguration message includes the measConfig:

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

[TS 36.331, clause 5.5.4.1]

The UE shall:

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

2> if the triggerType is set to event and if the eventId is set to eventH1 or eventH2 and if the entering condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled during timeToTrigger defined within the VarMeasConfig for this event:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

NOTE 2: The UE does not stop the periodical reporting with triggerType set to ‘event’ or to ‘periodical’ while the corresponding measurement is not performed due to the serving cell RSRP being equal to or better than s-Measure or due to the measurement gap not being setup.

[TS 36.331, clause 5.5.4.16]

The UE shall:

1> consider the entering condition for this event to be satisfied when condition H1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition H1-2, as specified below, is fulfilled;

Inequality H1-1 (Entering condition)

Inequality H1-2 (Leaving condition)

The variables in the formula are defined as follows:

Ms is the Aerial UE height, not taking into account any offsets.

Hys is the hysteresis parameter (i.e. h1-Hysteresis as defined within ReportConfigEUTRA) for this event.

Thresh is the reference threshold parameter for this event given in MeasConfig(i.e. heightThreshRef as defined within MeasConfig).

Offset is the offset value to heightThreshRef to obtain the absolute threshold for this event. (i.e. h1-ThresholdOffset as defined within ReportConfigEUTRA)

Ms is expressed in meters.

Thresh is expressed in the same unit as Ms.

[TS 36.331, clause 5.5.5]

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultServCell to include the quantities of serving cell;

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId;

2> start the periodical reporting timer with the value of reportInterval as defined within the reportConfig for this measId;

1> if the triggerType is set to event; and if eventId is set to eventH1 or eventH2:

2> set the heightUE to include the altitude of the UE;

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

1> else:

2> if the triggerType is set to periodical:

3> remove the entry within the VarMeasReportList for this measId;

3> remove this measId from the measIdList within VarMeasConfig;

1> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.

8.9.2.3 Test description

8.9.2.3.1 Pre-test conditions

System Simulator:

– Cell 1

– 1 GNSS simulator

UE:

None.

Preamble:

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

8.9.2.3.2 Test procedure sequence

Table 8.9.2.3.2-1 illustrates the simulated aerial height above sea level 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 8.9.2.3.2-1: Simulated aerial height

Time

Parameter

Unit

Value

(Note 2)

Remark

(Note 1)

T0

Simulated aerial height above sea level (Ms)

m

500

Simulated aerial height above sea level (Ms) is such that entry condition for event H1 is not satisfied:

Ms – Hys – Offset < Thresh

T1

680

Simulated aerial height above sea level (Ms) is such that entry condition for event H1 is satisfied:

Ms – Hys – Offset > Thresh

T2

480

Simulated aerial height above sea level (Ms) is such that exit condition for event H1 is satisfied:

Ms + Hys – Offset < Thresh

Note 1: Value of Hys and Offset correspond to values of h1-Hysteresis-15 and h1-ThresholdOffset-r15 in Table 8.9.2.3.3-3. Value of Thresh corresponds to value of heightThreshRef-r15 in Table 8.9.2.3.3-2.

Note 2: An allowance of +/-90m has been used to generate the aerial height values. This allowance takes into account both the UE measurement accuracy and the test tolerances in the simulation.

Table 8.9.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

00

Trigger the UE to reset UTC time in order that the UE accepts the time generated by the GNSS simulator and also uses only GNSS for position calculation in the subsequent test procedure, as defined in TS 36.509 [25] clause 5.5.3.

NOTE: The UTC time reset may be performed by MMI or AT command (+CUTCR).

0

SS configures the GNSS simulator for step 1 of Scenario #1 as defined in TS 36.508 [18] Table 4.12.2-1 to simulate a location with the height above sea level given for time T0 in Table 8.9.2.3.2-1.

1

SS transmits a RRCConnectionReconfiguration message including MeasConfig to setup intra E-UTRAN measurement and reporting for event H1.

<–

RRCConnectionReconfiguration

2

The UE transmits a RCConnectionReconfigrationComplete message.

–>

RRCConnectionReconfigurationComplete

3

SS configures GNSS simulator for step 2 of Scenario #1 as defined in TS 36.508 [18] Table 4.12.2-1 to simulate the UE altitude moving to a height above sea level given for time T1 in Table 8.9.2.3.2-1.

4

Check: Does the UE transmit a MeasurementReport message to report event H1 with the measured aerial height value?

–>

MeasurementReport

1

P

EXCEPTION: Step 5 below is repeated until 3 MeasurementReport messages are received from the UE.

5

Check: Does the UE transmit a MeasurementReport message to report event H1 with the measured aerial height value?

–>

MeasurementReport

1

P

6

SS configures GNSS simulator for step 4 of Scenario #1 as defined in TS 36.508 [18] Table 4.12.2-1 to simulate the UE altitude moving to a height above sea level given for time T2 in Table 8.9.2.3.2-1.

7

Wait and ignore MeasurementReport messages for 50 s (as detailed in TS 36.508 [18] Table 4.12.2-1) to allow simulated change of aerial height value to be measured by the UE.

8

Check: Does the UE attempt to transmit an uplink message within the next 10s?

2

F

8.9.2.3.3 Specific message contents

Table 8.9.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.9.2.3.2-2)

Derivation Path: TS 36.508 clause 4.6.1, Table 4.6.1-8 RRCConnectionReconfiguration

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

MeasConfig-DEFAULT

}

}

}

}

Table 8.9.2.3.3-2: MeasConfig-DEFAULT (step 1, Table 8.9.2.3.2-2)

Derivation Path: TS 36.508, clause 4.6.6 Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig-DEFAULT ::= CHOICE {

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{

reportConfigId[1]

IdReportConfig-H1

reportConfig[1]

reportConfigEUTRA-H1

}

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

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-H1

}

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

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

heightThreshRef-r15 CHOICE {

Setup

3 (480m)

}

}

Table 8.9.2.3.3-3: reportConfigEUTRA-H1 (step 1, Table 8.9.2.3.2-2)

Derivation path: TS 36.508 clause 4.6.6 table 4.6.6-15 ReportConfigEUTRA-H1

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

eventID CHOICE {

eventH1-r15 SEQUENCE {

h1-ThresholdOffset-r15

50 (100m)

h1-Hysteresis-15

10 (10m)

}

}

}

}

reportAmount

Infinity

}

Table 8.9.2.3.3-4: MeasurementReport (steps 4 and 5, Table 8.9.2.3.2-2)

Derivation path: 36.508 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 {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {}

Not present

heightUE-r15

(-400..8880)

}

}

}

}

}

8.9.3 Aerial UE / Measurement configuration control and reporting / Event H2

8.9.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event H2 with event based periodical reporting }

ensure that {

when { Aerial UE height becomes lower than the absolute treshold minus hysteresis }

then { UE sends MeasurementReport message at regular intervals while entering conditions for event H2 are satisfied }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and periodical measurement reporting triggered by event H2 ongoing}

ensure that {

when { Aerial UE height becomes higher than the absolute treshold plus hysteresis }

then { UE stops sending MeasurementReport message }

}

8.9.3.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.3.5.3, 5.5.4.1, 5.5.4.17 and 5.5.5.

[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 RRCConnectionReconfiguration message includes the measConfig:

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

[TS 36.331, clause 5.5.4.1]

The UE shall:

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

2> if the triggerType is set to event and if the eventId is set to eventH1 or eventH2 and if the entering condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled during timeToTrigger defined within the VarMeasConfig for this event:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

NOTE 2: The UE does not stop the periodical reporting with triggerType set to ‘event’ or to ‘periodical’ while the corresponding measurement is not performed due to the serving cell RSRP being equal to or better than s-Measure or due to the measurement gap not being setup.

[TS 36.331, clause 5.5.4.17]

The UE shall:

1> consider the entering condition for this event to be satisfied when condition H2-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition H2-2, as specified below, is fulfilled;

Inequality H2-1 (Entering condition)

Inequality H2-2 (Leaving condition)

The variables in the formula are defined as follows:

Ms is the Aerial UE height, not taking into account any offsets.

Hys is the hysteresis parameter (i.e. h2-Hysteresis as defined within ReportConfigEUTRA) for this event.

Thresh is the reference threshold parameter for this event given in MeasConfig(i.e. heightThreshRef as defined within MeasConfig).

Offset is the offset value to heightThreshRef to obtain the absolute threshold for this event. (i.e. h2-ThresholdOffset as defined within ReportConfigEUTRA)

Ms is expressed in meters.

Thresh is expressed in the same unit as Ms.

[TS 36.331, clause 5.5.5]

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultServCell to include the quantities of serving cell;

1> if there is at least one applicable neighbouring cell to report:

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId;

2> start the periodical reporting timer with the value of reportInterval as defined within the reportConfig for this measId;

1> if the triggerType is set to event; and if eventId is set to eventH1 or eventH2:

2> set the heightUE to include the altitude of the UE;

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

1> else:

2> if the triggerType is set to periodical:

3> remove the entry within the VarMeasReportList for this measId;

3> remove this measId from the measIdList within VarMeasConfig;

1> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.

8.9.3.3 Test description

8.9.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

– 1 GNSS simulator

UE:

None.

Preamble:

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

8.9.3.3.2 Test procedure sequence

Table 8.9.3.3.2-1 illustrates the simulated aerial height above sea level 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 8.9.3.3.2-1: Simulated aerial height

Time

Parameter

Unit

Value

(Note 2)

Remark

(Note 1)

T0

Simulated aerial height above sea level (Ms)

m

490

Simulated aerial height above sea level (Ms) is such that entry condition for event H2 is not satisfied:

Ms + Hys – Offset > Thresh

T1

310

Simulated aerial height above sea level (Ms) is such that entry condition for event H2 is satisfied:

Ms + Hys – Offset < Thresh

T2

510

Simulated aerial height above sea level (Ms) is such that exit condition for event H2 is satisfied:

Ms – Hys – Offset > Thresh

Note 1: Value of Hys and Offset correspond to values of h2-Hysteresis-15 and h2-ThresholdOffset-r15 in Table 8.9.3.3.3-3. Value of Thresh corresponds to value of heightThreshRef-r15 in Table 8.9.3.3.3-2.

Note 2: An allowance of +/-90m has been used to generate the aerial height values. This allowance takes into account both the UE measurement accuracy and the test tolerances in the simulation.

Table 8.9.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

SS configures the GNSS simulator for step 1 of Scenario #1 as defined in TS 36.508 [18] Table 4.12.2-1 to simulate a location with the height above sea level given for time T0 in Table 8.9.3.3.2-1.

1

SS transmits an RRCConnectionReconfiguration message including MeasConfig to setup intra E-UTRAN measurement and reporting for event H2.

<–

RRCConnectionReconfiguration

2

The UE transmits an RCConnectionReconfigrationComplete message.

–>

RRCConnectionReconfigurationComplete

3

SS configures GNSS simulator for step 2 of Scenario #1 as defined in TS 36.508 [18] Table 4.12.2-1 to simulate the UE altitude moving to a height above sea level given for time T1 in Table 8.9.3.3.2-1.

4

Check: Does the UE transmit a MeasurementReport message to report event H2 with the measured aerial height value?

–>

MeasurementReport

1

P

EXCEPTION: Step 5 below is repeated until 3 MeasurementReport messages are received from the UE.

5

Check: Does the UE transmit a MeasurementReport message to report event H2 with the measured aerial height value?

–>

MeasurementReport

1

P

6

SS configures GNSS simulator for step 4 of Scenario #1 as defined in TS 36.508 [18] Table 4.12.2-1 to simulate the UE altitude moving to a height above sea level given for time T2 in Table 8.9.3.3.2-1.

7

Wait and ignore MeasurementReport messages for 50 s (as detailed in TS 36.508 [18] Table 4.12.2-1) to allow simulated change of aerial height value to be measured by the UE.

8

Check: Does the UE attempt to transmit an uplink message within the next 10s?

2

F

8.9.3.3.3 Specific message contents

Table 8.9.3.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.9.3.3.2-2)

Derivation Path: TS 36.508 clause 4.6.1, Table 4.6.1-8 RRCConnectionReconfiguration

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

MeasConfig-DEFAULT

}

}

}

}

Table 8.9.3.3.3-2: MeasConfig-DEFAULT (step 1, Table 8.9.3.3.2-2)

Derivation Path: TS 36.508, clause 4.6.6 Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig-DEFAULT ::= CHOICE {

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{

reportConfigId[1]

IdReportConfig-H2

reportConfig[1]

reportConfigEUTRA-H2

}

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

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-H2

}

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

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

heightThreshRef-r15 CHOICE {

Setup

2 (180m)

}

}

Table 8.9.3.3.3-3: reportConfigEUTRA-H2 (step 1, Table 8.9.3.3.2-2)

Derivation path: TS 36.508 clause 4.6.6 table 4.6.6-15 ReportConfigEUTRA-H1

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

eventID CHOICE {

eventH2-r15 SEQUENCE {

h2-ThresholdOffset-r15

115 (230m)

h2-Hysteresis-15

10 (10m)

}

}

}

}

reportAmount

infinity

}

Table 8.9.3.3.3-4: MeasurementReport (steps 4 and 5, Table 8.9.3.3.2-2)

Derivation path: 36.508 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 {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {}

Not present

heightUE-r15

(-400..8880)

}

}

}

}

}

8.9.4 Aerial UE / Measurement configuration control and reporting / numberOfTriggeringCells configured / Event A3

8.9.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A3 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {

when { Entry condition for event A3 is not satisfied as the number of cells meeting the criteria is less than numberOfTriggeringCells }

then { UE does not send MeasurementReport message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A3 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {

when { Entry condition for event A3 is satisfied as the number of cells meeting the criteria is same or more than numberOfTriggeringCells }

then { UE sends MeasurementReport message at regular intervals }

}

8.9.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.5.3, 5.5.4.1, 5.5.4.4 and 5.5.5. Unless otherwise stated these are Rel-15 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 RRCConnectionReconfiguration message includes the measConfig:

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

[TS 36.331, clause 5.5.4.1]

The UE shall:

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

2> else:

3> if the corresponding measObject concerns E-UTRA:

4> if the ue-RxTxTimeDiffPeriodical, eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> else:

5> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

2> if the triggerType is set to event and if the corresponding reportConfig includes numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig:

3> If the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event):

4> include a measurement reporting entry within the VarMeasReportList for this measId;

3> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCell:

4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> else:

4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

4> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCells:

5> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

5> initiate the measurement reporting procedure, as specified in 5.5.5;

2> upon expiry of the T321 for this measId:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

NOTE 2: The UE does not stop the periodical reporting with triggerType set to event or to periodical while the corresponding measurement is not performed due to the PCell RSRP being equal to or better than s-Measure or due to the measurement gap not being setup.

[TS 36.331, clause 5.5.4.4]

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled;

1> if usePSCell of the corresponding reportConfig is set to true:

2> use the PSCell for Mp, Ofp and Ocp;

1> else:

2> use the PCell for Mp, Ofp and Ocp;

NOTE The cell(s) that triggers the event is on the frequency indicated in the associated measObject which may be different from the frequency used by the PCell/ PSCell.

Inequality A3-1 (Entering condition)

Inequality A3-2 (Leaving condition)

The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Mp is the measurement result of the PCell/ PSCell, not taking into account any offsets.

Ofp is the frequency specific offset of the frequency of the PCell/ PSCell (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the PCell/ PSCell).

Ocp is the cell specific offset of the PCell/ PSCell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the PCell/ PSCell), and is set to zero if not configured for the PCell/ PSCell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigEUTRA for this event).

Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.

[TS 36.331, clause 5.5.5]

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultServCell to include the quantities of serving cell;

1> if there is at least one applicable neighbouring cell to report:

2> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

3> if the triggerType is set to ‘event‘:

4> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

3> else:

4> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

NOTE: The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency) depends on the measurement configuration i.e. the reportInterval. The related performance requirements are specified in TS 36.133 [16].

3> for each cell that is included in the measResultNeighCells, include the physCellId;

3> if the triggerType is set to ‘event‘; or the purpose is set to ‘reportStrongestCells‘ or to ‘reportStrongestCellsForSON‘:

4> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

5> if the measObject associated with this measId concerns E-UTRA:

6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfig in order of decreasing triggerQuantity, i.e. the best cell is included first;

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

1> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends;

8.9.4.3 Test description

8.9.4.3.1 Pre-test conditions

System Simulator:

– Cell 1, Cell 2 and Cell 4.

– Cell 1 is the serving cell.

– Cell 2 and Cell 4 are intra-frequency neighbour cells of Cell 1.

– System information combination 2 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.9.4.3.2 Test procedure sequence

Table 8.9.4.3.2-1 illustrates the downlink power levels to be applied for Cell 1, Cell 2 and Cell 4 at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while rows marked "T1", "T2" and "T3" 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.9.4.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

(DL only)

Cell 4

(DL only)

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

-91

Power levels are such that entry condition for event A3 is not satisfied for both the Cells.

Mn2 + Ofn2 + Ocn2 + Hys < Ms + Ofs + Ocs + Off

and Mn4 + Ofn4 + Ocn4 + Hys < Ms + Ofs + Ocs + Off

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-91

Power levels are such that entry condition for event A3 is satisfied only for Cell 2:

Mn2 + Ofn2 + Ocn2 – Hys > Ms + Ofs + Ocs + Off

and Mn4 + Ofn4 + Ocn4 + Hys < Ms + Ofs + Ocs + Off

T2

Cell-specific RS EPRE

dBm/15kHz

-85

-91

-79

Power levels are such that entry condition for event A3 is satisfied only for Cell 4:

Mn2 + Ofn2 + Ocn2 + Hys < Ms + Ofs + Ocs + Off

and Mn4 + Ofn4 + Ocn4 – Hys > Ms + Ofs + Ocs + Off

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-79

Power levels are such that entry condition for event A3 is satisfied for both Cell 2 and Cell 4:

Mn2 + Ofn2 + Ocn2 – Hys > Ms + Ofs + Ocs + Off

and Mn4 + Ofn4 + Ocn4 – Hys > Ms + Ofs + Ocs + Off

Table 8.9.4.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

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

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

Check: Does the UE transmit a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP value for Cell 2 and/or Cell 4 within next 10s?

–>

MeasurementReport

1

F

4

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

5

Check: Does the UE transmit a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP value for Cell 2 within next 10s?

–>

MeasurementReport

1

F

6

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

7

Check: Does the UE transmit a MeasurementReport message on Cell 1, with the measured RSRP value for Cell 4 within next 10s?

–>

MeasurementReport

1

F

8

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

EXCEPTION: Step 9 below is repeated until 4 MeasurementReport messages are received from the UE

9

Check: Does the UE transmit a MeasurementReport message on Cell 1, with the measured RSRP value for Cell 2 and Cell 4?

–>

MeasurementReport

2

P

8.9.4.3.3 Specific message contents

Table 8.9.4.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.9.4.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8 with condition MEAS

Table 8.9.4.3.3-2: MeasConfig (step 1, Table 8.9.4.3.2-2)

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]

1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

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

1 entry

reportConfigId[1]

3

reportConfig[1]

ReportConfigEUTRA-A3-RECONF

}

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

1 entry

measId[1]

1

measObjectId[1]

1

reportConfigId[1]

3

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

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

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

intraFreq-CE-NeedForGaps

For UE having set pc_intraFreq-CE-Need ForGaps to TRUE.

Table 8.9.4.3.3-3: ReportConfigEUTRA-A3 (step 1, Table 8.9.4.3.2-2)

Derivation Path: 36.508, Table 4.6.6-6AA, Condition Aerial UE

Information Element

Value/remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

maxReportCells

2

reportAmount

r4

}

Table 8.9.4.3.3-4: MeasurementReport (step 9, Table 8.9.4.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

measResultServCell SEQUENCE {

Report Cell 1

rsrpResult

(52..97)

rsrqResult

(23..34)

}

measResultNeighCells CHOICE {

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

2 entries

Report Cell 2 and Cell 4

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(52..97)

rsrqResult

(23..34)

additionalSI-Info-r9

Not present

}

physCellId[2]

PhysicalCellIdentity of Cell 4

cgi-Info[2]

Not present

measResult[2] SEQUENCE {

rsrpResult

(52..97)

rsrqResult

(23..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

}

}

}

}

}

8.9.4a Aerial UE / Measurement configuration control and reporting / numberOfTriggeringCells configured / Event A3 (Inter-frequency measurement)

8.9.4a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and inter-frequency measurement configured for event A3 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {

when { Entry condition for event A3 is not satisfied as the number of cells meeting the criteria is less than numberOfTriggeringCells }

then { UE does not send MeasurementReport message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and inter-frequency measurement configured for event A3 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {

when { Entry condition for event A3 is satisfied as the number of cells meeting the criteria is same or more than numberOfTriggeringCells }

then { UE sends MeasurementReport message at regular intervals }

}

8.9.4a.2 Conformance requirements

Same as test case 8.9.4 with the following differences:

[TS 36.331, clause 5.5.4.1]

The UE shall:

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

2> else:

3> if the corresponding measObject concerns E-UTRA:

4> else:

5> for events involving a serving cell on one frequency and neighbours on another frequency, consider the serving cell on the other frequency as a neighbouring cell;

8.9.4a.3 Test description

8.9.4a.3.1 Pre-test conditions

Same as test case 8.9.4 with the following differences:

– Cells configuration: Cell 3 replaces Cell 2, Cell 6 replaces Cell 4

8.9.4a.3.2 Test procedure sequence

Same as test case 8.9.4 with the following differences:

– Cells configuration: Cell 3 replaces Cell 2, Cell 6 replaces Cell 4

8.9.4a.3.3 Specific message contents

Same as test case 8.9.4 with the following differences:

– In Table 8.9.4.3.3.-4: Cell 3 replaces Cell 2, Cell 6 replaces Cell 4

Table 8.9.4a.3.3-1: MeasConfig (step 1, Table 8.9.4a.3.2-2)

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{

2 entries

measObjectId[1]

1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

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

1 entry

reportConfigId[1]

3

reportConfig[1]

ReportConfigEUTRA-A3-RECONF

}

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

1 entry

measId[1]

1

measObjectId[1]

2

reportConfigId[1]

3

}

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

2 entries

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

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

8.9.5 Aerial UE / Measurement configuration control and reporting / numberOfTriggeringCells configured / Event A4

8.9.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A4 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {

when { Entry condition for event A4 is not satisfied as the number of cells meeting the criteria is less than numberOfTriggeringCells }

then { UE does not send MeasurementReport message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A4 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {

when { Entry condition for event A4 is satisfied as the number of cells meeting the criteria is same or more than numberOfTriggeringCells }

then { UE sends MeasurementReport message at regular intervals }

}

8.9.5.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.5.3, 5.5.4.1, 5.5.4.5 and 5.5.5. Unless otherwise stated these are Rel-15 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 RRCConnectionReconfiguration message includes the measConfig:

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

[TS 36.331, clause 5.5.4.1]

The UE shall:

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

2> else:

3> if the corresponding measObject concerns E-UTRA:

4> if the ue-RxTxTimeDiffPeriodical, eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> else:

5> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

2> if the triggerType is set to event and if the corresponding reportConfig includes numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig:

3> If the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event):

4> include a measurement reporting entry within the VarMeasReportList for this measId;

3> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCell:

4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> else:

4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

4> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCells:

5> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

5> initiate the measurement reporting procedure, as specified in 5.5.5;

2> upon expiry of the T321 for this measId:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

NOTE 2: The UE does not stop the periodical reporting with triggerType set to event or to periodical while the corresponding measurement is not performed due to the PCell RSRP being equal to or better than s-Measure or due to the measurement gap not being setup.

[TS 36.331, clause 5.5.4.5]

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled;

Inequality A4-1 (Entering condition)

Inequality A4-2 (Leaving condition)

The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigEUTRA for this event).

Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ.

Ofn, Ocn, Hys are expressed in dB.

Thresh is expressed in the same unit as Ms.

[TS 36.331, clause 5.5.5]

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultServCell to include the quantities of serving cell;

1> if there is at least one applicable neighbouring cell to report:

2> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

3> if the triggerType is set to ‘event‘:

4> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

3> else:

4> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

NOTE: The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency) depends on the measurement configuration i.e. the reportInterval. The related performance requirements are specified in TS 36.133 [16].

3> for each cell that is included in the measResultNeighCells, include the physCellId;

3> if the triggerType is set to ‘event‘; or the purpose is set to ‘reportStrongestCells‘ or to ‘reportStrongestCellsForSON‘:

4> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

5> if the measObject associated with this measId concerns E-UTRA:

6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfig in order of decreasing triggerQuantity, i.e. the best cell is included first;

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

1> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends;

8.9.5.3 Test description

8.9.5.3.1 Pre-test conditions

System Simulator:

– Cell 1, Cell 2 and Cell 4.

– Cell 1 is the serving cell.

– Cell 2 and Cell 4 are intra-frequency neighbour cells of Cell 1.

– System information combination 2 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.9.5.3.2 Test procedure sequence

Table 8.9.5.3.2-1 illustrates the downlink power levels to be applied for Cell 1, Cell 2 and Cell 4 at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while rows marked "T1", "T2" and "T3" 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.9.5.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

(DL only)

Cell 4

(DL only)

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-97

-97

Power levels are such that entry condition for event A4 is not satisfied for both the Cells.

Mn2 + Ofn2 + Ocn2 – Hys < Thresh

and Mn4 + Ofn4 + Ocn4 – Hys < Thresh

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-97

Power levels are such that entry condition for event A4 is satisfied only for Cell 2:

Mn2 + Ofn2 + Ocn2 – Hys > Thresh

and Mn4 + Ofn4 + Ocn4 – Hys < Thresh

T2

Cell-specific RS EPRE

dBm/15kHz

-85

-97

-79

Power levels are such that entry condition for event A4 is satisfied only for Cell 4:

Mn2 + Ofn2 + Ocn2 – Hys < Thresh

and Mn4 + Ofn4 + Ocn4 – Hys > Thresh

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-79

Power levels are such that entry condition for event A4 is satisfied for both Cell 2 and Cell 4:

Mn2 + Ofn2 + Ocn2 – Hys > Thresh

and Mn4 + Ofn4 + Ocn4 – Hys > Thresh

Table 8.9.5.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

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

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

Check: Does the UE transmit a MeasurementReport message on Cell 1 to report event A4 with the measured RSRP value for Cell 2 and/or Cell 4 within next 10s?

–>

MeasurementReport

1

F

4

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

5

Check: Does the UE transmit a MeasurementReport message on Cell 1 to report event A4 with the measured RSRP value for Cell 2 within next 10s?

–>

MeasurementReport

1

F

6

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

7

Check: Does the UE transmit a MeasurementReport message on Cell 1, with the measured RSRP value for Cell 4 within next 10s?

–>

MeasurementReport

1

F

8

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

EXCEPTION: Step 9 below is repeated until 4 MeasurementReport messages are received from the UE

9

Check: Does the UE transmit a MeasurementReport message on Cell 1, with the measured RSRP value for Cell 2 and Cell 4?

–>

MeasurementReport

2

P

8.9.5.3.3 Specific message contents

Table 8.9.5.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.9.5.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8 with condition MEAS

Table 8.9.5.3.3-2: MeasConfig (step 1, Table 8.9.5.3.2-2)

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]

1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

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

1 entry

reportConfigId[1]

6

reportConfig[1]

ReportConfigEUTRA-A4-RECONF

}

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

1 entry

measId[1]

1

measObjectId[1]

1

reportConfigId[1]

6

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

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

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.9.5.3.3-3: ReportConfigEUTRA-A4 (-88) (step 1, Table 8.9.5.3.2-2)

Derivation Path: 36.508, Table 4.6.6-6AA, Conditions NOT RSRQ, Aerial UE

Information Element

Value/remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

maxReportCells

2

reportAmount

r4

}

Table 8.9.5.3.3-4: MeasurementReport (step 9, Table 8.9.5.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

measResultServCell SEQUENCE {

Report Cell 1

rsrpResult

(52..97)

rsrqResult

(23..34)

}

measResultNeighCells CHOICE {

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

2 entries

Report Cell 2 and Cell 4

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(52..97)

rsrqResult

(23..34)

additionalSI-Info-r9

Not present

}

physCellId[2]

PhysicalCellIdentity of Cell 4

cgi-Info[2]

Not present

measResult[2] SEQUENCE {

rsrpResult

(52..97)

rsrqResult

(23..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

}

}

}

}

}

8.9.5a Aerial UE / Measurement configuration control and reporting / numberOfTriggeringCells configured / Event A4 (inter-frequency measurements)

8.9.5a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and inter-frequency measurement configured for event A4 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {

when { Entry condition for event A4 is not satisfied as the number of cells meeting the criteria is less than numberOfTriggeringCells }

then { UE does not send MeasurementReport message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and inter-frequency measurement configured for event A4 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {

when { Entry condition for event A4 is satisfied as the number of cells meeting the criteria is same or more than numberOfTriggeringCells }

then { UE sends MeasurementReport message at regular intervals }

}

8.9.5a.2 Conformance requirements

Same as test case 8.9.5 with the following differences:

[TS 36.331, clause 5.5.4.1]

The UE shall:

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

2> else:

3> if the corresponding measObject concerns E-UTRA:

4> else:

5> for events involving a serving cell on one frequency and neighbours on another frequency, consider the serving cell on the other frequency as a neighbouring cell;

8.9.5a.3 Test description

8.9.5a.3.1 Pre-test conditions

Same as test case 8.9.5 with the following differences:

– Cells configuration: Cell 3 replaces Cell 2, Cell 6 replaces Cell 4

8.9.5a.3.2 Test procedure sequence

Same as test case 8.9.5 with the following differences:

– Cells configuration: Cell 3 replaces Cell 2, Cell 6 replaces Cell 4

8.9.5a.3.3 Specific message contents

Same as test case 8.9.5 with the following differences:

– In Table 8.9.5.3.3.-4: Cell 3 replaces Cell 2, Cell 6 replaces Cell 4

Table 8.9.5a.3.3-1: MeasConfig (step 1, Table 8.9.5.3.2-2)

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{

2 entries

measObjectId[1]

1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

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

1 entry

reportConfigId[1]

6

reportConfig[1]

ReportConfigEUTRA-A4-RECONF

}

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

1 entry

measId[1]

1

measObjectId[1]

2

reportConfigId[1]

6

}

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

2 entries

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

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

8.9.6 Aerial UE / Measurement configuration control and reporting / numberOfTriggeringCells configured / Event A5

8.9.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A5 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {
when { Entry condition for event A5 is not satisfied as the number of cells meeting the criteria is less than numberOfTriggeringCells }

then { UE does not send MeasurementReport message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and measurement configured for event A5 with event based periodical reporting and reportconfig includes numberOfTriggeringCells }

ensure that {
when { Entry condition for event A5 is satisfied as the number of cells meeting the criteria is same or more than numberOfTriggeringCells }

then { UE sends MeasurementReport message at regular intervals }

}

8.9.6.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.5.3, 5.5.4.1, 5.5.4.6 and 5.5.5. Unless otherwise stated these are Rel-15 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 RRCConnectionReconfiguration message includes the measConfig:

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

[TS 36.331, clause 5.5.4.1]

The UE shall:

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

2> else:

3> if the corresponding measObject concerns E-UTRA:

4> if the ue-RxTxTimeDiffPeriodical, eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> else:

5> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

2> if the triggerType is set to event, and if the corresponding reportConfig does not include numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the event):

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> if the UE supports T312 and if useT312 is included for this event and if T310 is running:

4> if T312 is not running:

5> start timer T312 with the value configured in the corresponding measObject;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to event and if the corresponding reportConfig includes numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig:

3> If the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event):

4> include a measurement reporting entry within the VarMeasReportList for this measId;

3> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCell:

4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

3> else:

4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;

4> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCells:

5> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

5> initiate the measurement reporting procedure, as specified in 5.5.5;

2> upon expiry of the T321 for this measId:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

NOTE 2: The UE does not stop the periodical reporting with triggerType set to event or to periodical while the corresponding measurement is not performed due to the PCell RSRP being equal to or better than s-Measure or due to the measurement gap not being setup.

NOTE 3: If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered and periodical triggered measurements until the Active Time, which is defined in TS 36.321 [6].

[TS 36.331, clause 5.5.4.6]

The UE shall:

1> consider the entering condition for this event to be satisfied when both conditions A5-1 and condition A5-2, as specified below, are fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least one of the two, as specified below, is fulfilled;

Inequality A5-1 (Entering condition 1)

Inequality A5-2 (Entering condition 2)

Inequality A5-3 (Leaving condition 1)

Inequality A5-4 (Leaving condition 2)

The variables in the formula are defined as follows:

Ms is the measurement result of the serving cell, not taking into account any offsets.

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigEUTRA for this event).

Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigEUTRA for this event).

Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ.

Ofn, Ocn, Hys are expressed in dB.

Thresh1 is expressed in the same unit as Ms.

Thresh2 is expressed in the same unit as Mn.

[TS 36.331, clause 5.5.5]

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultServCell to include the quantities of serving cell;

1> if there is at least one applicable neighbouring cell to report:

2> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:

3> if the triggerType is set to ‘event‘:

4> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;

3> else:

4> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

NOTE: The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency) depends on the measurement configuration i.e. the reportInterval. The related performance requirements are specified in TS 36.133 [16].

3> for each cell that is included in the measResultNeighCells, include the physCellId;

3> if the triggerType is set to ‘event‘; or the purpose is set to ‘reportStrongestCells‘ or to ‘reportStrongestCellsForSON‘:

4> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:

5> if the measObject associated with this measId concerns E-UTRA:

6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfig in order of decreasing triggerQuantity, i.e. the best cell is included first;

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId:

2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId;

1> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends;

8.9.6.3 Test description

8.9.6.3.1 Pre-test conditions

System Simulator:

– Cell 1, Cell 2 and Cell 4.

– Cell 1 is the serving cell.

– Cell 2 and Cell 4 are intra-frequency neighbour cells of Cell 1.

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

Table 8.9.6.3.2-1 illustrates the downlink power levels to be applied for Cell 1, Cell 2 and Cell 4 at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while rows marked "T1", "T2" and "T3" 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.9.6.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Cell 4

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-65

-97

-97

Power levels are such that no cell satisfies entry condition for event A5:

Ms – Hys > Thresh1 and Mn1 + Ofn + Ocn + Hys < Thresh2 and Mn2 + Ofn + Ocn + Hys < Thresh2

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-97

-79

Power levels are such that Cell 1 and Cell 4 satisfy but Cell 2 does not satisfy the entry condition for event A5:

Ms – Hys < Thresh1 and Mn1 + Ofn + Ocn + Hys < Thresh2 and Mn2 + Ofn + Ocn + Hys > Thresh2

T2

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-97

Power levels are such that Cell1 and Cell 2 satisfy but Cell 4 does not satisfy the entry condition for event A5:

Ms – Hys < Thresh1 and Mn1 + Ofn + Ocn + Hys > Thresh2 and Mn2 + Ofn + Ocn + Hys < Thresh2

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-79

Power levels are such that all 3 cells satisfy the entry condition for event A5:

Ms + Hys < Thresh1 and Mn1 + Ofn + Ocn – Hys > Thresh2 and Mn2 + Ofn + Ocn – Hys > Thresh2

Table 8.9.6.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

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

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

Check: Does the UE transmit a MeasurementReport message on Cell 1 to report event A5 with the measured RSRP value for Cell 2 and/or Cell 4 within next 10s?

–>

MeasurementReport

1

F

4

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

5

Check: Does the UE transmit a MeasurementReport message on Cell 1 to report event A5 with the measured RSRP value for Cell 4 within next 10s?

–>

MeasurementReport

1

F

6

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

7

Check: Does the UE transmit a MeasurementReport message on Cell 1 to report event A5 with the measured RSRP value for Cell 2 within next 10s?

–>

MeasurementReport

1

F

8

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

EXCEPTION: Step 9 below is repeated until 4 MeasurementReport messages are received from the UE

9

Check: Does the UE transmit a MeasurementReport message on Cell 1 to report event A5 with the measured RSRP value for Cell 2 and Cell 4?

–>

MeasurementReport

2

P

8.9.6.3.3 Specific message contents

Table 8.9.6.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.9.6.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8 with condition MEAS

Table 8.9.6.3.3-2: MeasConfig (step 1, Table 8.9.6.3.2-2)

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]

1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

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

1 entry

reportConfigId[1]

7

reportConfig[1]

ReportConfigEUTRA-A5

}

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

1 entry

measId[1]

1

measObjectId[1]

1

reportConfigId[1]

7

}

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

Band > 64

    measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.9.6.3.3-3: ReportConfigEUTRA-A5 (-76, -88) (step 1, Table 8.9.6.3.2-2)

Derivation Path: 36.508, Table 4.6.6-6AB, Conditions NOT RSRQ, Aerial UE

Information Element

Value/remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

maxReportCells

2

reportAmount

r4

}

Table 8.9.6.3.3-4: MeasurementReport (step 9, Table 8.9.6.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

measResultServCell SEQUENCE {

Report Cell 1

rsrpResult

(52..97)

rsrqResult

(23..34)

}

measResultNeighCells CHOICE {

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

2 entries

Report Cell 2,

Cell 4

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(52..97)

rsrqResult

(23..34)

additionalSI-Info-r9

Not present

}

physCellId[2]

PhysicalCellIdentity of Cell 4

cgi-Info[1]

Not present

measResult[2] SEQUENCE {

rsrpResult

(52..97)

rsrqResult

(23..34)

additionalSI-Info-r9

}

}

}

measResultForECID-r9

Not present

}

}

}

}

}