8.6.10 Inter-RAT Immediate MDT

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.6.10.1 Inter-RAT Immediate MDT / Reporting / Location information / Event B2

8.6.10.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and measurement with event B2 configured with includeLocationInfo included in the reportConfig }

ensure that {
when { Entry condition for event B2 is met and detailed location information that has not been reported is available }

then { UE sends MeasurementReport message with locationInfo included }

}

8.6.10.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.306, clause 4.3.13.2; TS 36.331, clauses 5.5.5 and 5.6.5.3. Unless otherwise stated these are Rel-11 requirements.

[TS 36.306, clause 4.3.13.2]

This parameter defines whether the UE is equipped with a standalone GNSS receiver that may be used to provide detailed location information in RRC measurement report and logged measurements in RRC_IDLE.

[TS 36.331, clause 5.5.5]

The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN.

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

…

1> if the includeLocationInfo is configured in the corresponding reportConfig for this measId and detailed location information that has not been reported is available, set the content of the locationInfo as follows:

2> include the locationCoordinates;

2> if available, include the gnss-TOD-msec;

[TS 36.331, clause 5.6.5.3]

Upon receiving the UEInformationRequest message, the UE shall:

…

1> if connEstFailReportReq is set to true and the UE has connection establishment failure information in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

2> set timeSinceFailure in VarConnEstFailReport to the time that elapsed since the last connection establishment failure in E-UTRA;

2> set the connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport;

2> set the connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport;

…

1> if the logMeasReport is included in the UEInformationResponse:

…

1> else:

2> submit the UEInformationResponse message to lower layers for transmission via SRB1;

8.6.10.1.3 Test description

8.6.10.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 7.

– 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’s positioning engine (e.g. standalone GNSS receiver) should be provided with any necessary stimulus to allow it to provide the position. This shall be done by use of the test function Update UE Location Information defined in TS 36.509 [25] , if supported by the UE according to pc_UpdateUE_LocationInformation. Otherwise, or in addition any other suitable method may also be used.

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

8.6.10.1.3.2 Test procedure sequence

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

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

Parameter

Unit

Cell 1

Cell 7

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

–

The power level values are such that entering conditions for event B2 are not satisfied.

CPICH Ec (UTRA FDD)

dBm/3.84MHz

–

-88

PCCPCH Ec (UTRA LCR TDD)

dBm/1.28 MHz

–

-88

T1

Cell-specific RS EPRE

dBm/15kHz

-84

–

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

CPICH Ec (UTRA FDD)

dBm/3.84MHz

–

-64

PCCPCH Ec (UTRA LCR TDD)

dBm/1.28 MHz

–

-64

Table 8.6.10.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup inter-RAT measurement with includeLocationInfo on Cell 1.

<–

RRCConnectionReconfiguration

–

–

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of inter-RAT measurement on Cell 1.

–>

RRCConnectionReconfigurationComplete

–

–

3

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

–

–

–

–

4

Check: Does the UE transmit a MeasurementReport message to report the event B2 for Cell 7 with locationInfo?

–>

MeasurementReport

1

P

8.6.10.1.3.3 Specific message contents

Table 8.6.10.1.3-0: Condition for specific message contents in Table 8.6.10.1.3.3-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.6.10.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.6.10.1.3.2-2)

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

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

Derivation Path: 36.508, Table 4.6.6-1, condition UTRAN

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

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

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f8

measObject[2]

MeasObjectUTRA-f8

}

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

1 entry

reportConfigId

IdReportConfig-B2-UTRA

reportConfig

ReportConfigInterRAT-B2-UTRA(-72, -76)

}

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

1 entry

measId

1

measObjectId[1]

IdMeasObject-f8

reportConfigId[1]

IdReportConfig-B2-UTRA

}

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 {

 

 

 

}

}

Table 8.6.10.1.3.3-2A: QuantityConfig (Table 8.6.10.1.3.3-1)

Derivation Path: 36.508, Table 4.6.6-3A, condition UTRAN

Information Element

Value/remark

Comment

Condition

QuantityConfig ::= SEQUENCE {

quantityConfigUTRA SEQUENCE {

measQuantityUTRA-FDD

cpich-RSCP

UTRA-FDD

measQuantityUTRA-TDD

pccpch-RSCP

UTRA-TDD

filterCoefficient

fc0

}

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 8.6.10.1.3.3-2B: MeasObjectUTRA-f8 (Table 8.6.10.1.3.3-2)

Derivation Path: 36.508, Table 4.6.6-3 MeasObjectUTRA-GENERIC(f8)

Information Element

Value/remark

Comment

Condition

MeasObjectUTRA -GENERIC(f8) ::= SEQUENCE {

carrierFreq

UTRA DL carrier frequency of the cell 7

cellsToAddModList CHOICE {

cellsToAddModListUTRA-FDD ::= SEQUENCE (SIZE (1.. maxCellMeas)) OF SEQUENCE {

UTRA-FDD

cellIndex[1]

1

physCellId[1]

physicalCellIdentity – Cell 7

}

cellsToAddModListUTRA-TDD ::= SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

UTRA-TDD

cellIndex[1]

1

physCellId[1]

physicalCellIdentity – Cell 7

}

}

}

Condition

Explanation

UTRA-FDD

UTRA FDD cell environment

UTRA-TDD

UTRA TDD cell environment

Table 8.6.10.1.3.3-2C: ReportConfigInterRAT-B2-UTRA (step 1, Table 8.6.1.10.3.3-2)

Derivation Path: 36.508, Table 4.6.6-8 ReportConfigInterRAT-B2-UTRA(-72, -76)

Information Element

Value/Remark

Comment

Condition

ReportConfigInterRAT::= SEQUENCE {

includeLocationInfo-r11

True

}

Table 8.6.10.1.3.3-3: MeasurementReport (step 4, Table 8.6.10.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE{

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

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 7

cgi-info[1]

Not present

measResult[1] SEQUENCE {

utra-RSCP

(-5..91)

}

}

}

locationInfo-r10 SEQUENCE {

locationCoordinates-r10 CHOICE {

ellipsoid-Point-r10

Any allowed value

ellipsoidPointWithAltitude-r10

Any allowed value

ellipsoidPointWithUncertaintyCircle-r11

Any allowed value

ellipsoidPointWithAltitudeAndUncertaintyEllipsoid-r11

Any allowed value

ellipsoidArc-r11

Any allowed value

polygon-r11

Any allowed value

}

horizontalVelocity-r10

Not present or ny allowed value

gnss-TOD-msec-r10

Any allowed value

}

}

}

}

}

}

8.6.10.2 Inter-RAT Immediate MDT / Reporting /Bluetooth measurement collection

8.6.10.2.1 Test Purpose (TP)

(1)

with { UE is in RRC_CONNECTED state and supports Bluetooth measurements and receives the ReportConfigEUTRA in RRCConnectionReconfiguration message with includeBT-Meas and measurement configured for event A2 and a Bluetooth beacon is included in BT-NameListConfig }

ensure that {

when { Entry condition for event A2 is met and Bluetooth measurement results that has not been reported is available }

then { UE sends MeasurementReport message with LogMeasResultListBT including Bluetooth measurement results corresponding to BT-NameListConfig included in includeBT-Meas }

}

(2)

with { UE is in RRC_CONNECTED state and supports Bluetooth measurements and receives the ReportConfigEUTRA in RRCConnectionReconfiguration message with includeBT-Meas and measurement configured for event A2 and a Bluetooth beacon is not included in BT-NameListConfig }

ensure that {

when { Entry condition for event A2 is met }

then { UE sends MeasurementReport message with LogMeasResultListBT not including Bluetooth measurement results of the Bluetooth beacon not included in BT-NameListConfig }

}

8.6.10.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.3 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]

If security has been activated successfully, 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 is configured in the corresponding reportConfig:

5> consider only the PCell to be applicable;

4> else if the reportSSTD-Meas is set to true in the corresponding reportConfig:

5> consider the PSCell to be applicable;

4> else if the eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> else if eventC1 or eventC2 is configured in the corresponding reportConfig; or if reportStrongestCSI-RSs is included in the corresponding reportConfig:

5> consider a CSI-RS resource on the associated frequency to be applicable when the concerned CSI-RS resource is included in the measCSI-RS-ToAddModList defined within the VarMeasConfig for this measId;

4> else if measRSSI-ReportConfig is configured in the corresponding reportConfig:

5> consider the resource indicated by the rmtc-Config on the associated frequency to be applicable;

4> else:

5> if useWhiteCellList is set to TRUE:

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

5> else:

6> 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;

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;

4> if the corresponding reportConfig includes alternativeTimeToTrigger and if the UE supports alternativeTimeToTrigger:

5> use the value of alternativeTimeToTrigger as the time to trigger instead of the value of timeToTrigger in the corresponding reportConfig for cells included in the altTTT-CellsToAddModList of the corresponding measObject;

…

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 for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the 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> 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 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>if the triggerType is set to event and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event:

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

3> if reportOnLeave is set to TRUE for the corresponding reporting configuration:

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

3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:

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

4> stop the periodical reporting timer for this measId, if running;

…

2> upon expiry of the periodical reporting timer for this measId:

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

The UE shall:

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

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

1> for this measurement, consider the primary or secondary cell that is configured on the frequency indicated in the associated measObjectEUTRA to be the serving cell;

Inequality A2-1 (Entering condition)

Inequality A2-2 (Leaving condition)

The variables in the formula are defined as follows:

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

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

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

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

Hys is 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> if the includeWLAN-Meas is configured in the corresponding reportConfig for this measId, set the measResults as follows:

2> if available, include the logMeasResultListWLAN, in order of decreasing RSSI for WLAN APs;

1> if the includeBT-Meas is configured in the corresponding reportConfig for this measId, set the measResults as follows:

2> if available, include the logMeasResultListBT, in order of decreasing RSSI for Bluetooth beacons;

…

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

8.6.10.2.3 Test description

8.6.10.2.3.1 Pre-test conditions

System Simulator:

  • Cell 1, Bluetooth beacon 1 (Cell 40) and Bluetooth beacon 2 (Cell 41)
  • Cell 40 and Cell 41 are configured as per 36.508 cl 4.4.9

UE:

None

Preamble:

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

8.6.10.2.3.2 Test procedure sequence

Table 8.6.10.2.3.2-1 illustrates the downlink power levels to be applied for Cell 1 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while row marked "T1"is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.6.10.2.3.2-1: Power levels

Parameter

Unit

Cell 1

Cell 40

(Bluetooth beacon 1)

Cell 41

(Bluetooth beacon 2)

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-70

Power level is such that Ms > Thresh + Hys

BeaconRSSI

dBm

-80

-50

T1

Cell-specific RS EPRE

dBm/15kHz

-96

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

BeaconRSSI

dBm

-80

-50

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

Table 8.6.10.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including measConfig to setup intra LTE measurement and reporting for event A2 with includeLocationInfo configured.

<–

RRCConnectionReconfiguration

–

–

2

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

–

–

3

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

–

–

–

–

4

Check: Does the UE transmit a MeasurementReport message to report event A2 with the LogMeasResultListBT including one entry (Bluetooth beacon 1) measurement result?

–>

MeasurementReport

1,2

P

8.6.10.2.3.3 Specific message contents

Table 8.6.10.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.6.10.2.3.2-2)

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

Table 8.6.10.2.3.3-2: MeasConfig (step 1, Table 8.6.10.2.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1

Information Element

Value/Remark

Comment

Condition

measConfig ::= SEQUENCE {

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

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

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

1 entry

reportConfigId[1]

IdReportConfig-A2

reportConfig[1]

ReportConfig-A2-H

}

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

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A2

}

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

1 entry

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.6.10.2.3.3-3: ReportConfig-A2-H (step 1, Table 8.6.10.2.3.2-2)

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

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

hysteresis

6

3 dB

}

}

reportAmount

r1

includeLocationInfo-r10

Not present

includeBT-Meas-r15 CHOICE {

setup SEQUENCE (SIZE (1..maxBT-Name-r15)) OF

1 entry

Bluetooth beacon 1

BT-Name-r15[1]

Set as per Table 4.4.9-1 of [18]

OCTET STRING (SIZE (1..248))

Refers to LOCAL NAME defined in Bluetooth specification

}

includeWLAN-Meas-r15

Not present

}

Table 8.6.10.2.3.3-4: MeasurementReport (step 4, Table 8.6.10.2.3.2-2)

Derivation path: 36.508 table clause 4.6.1 table 4.6.1-5

Information Element

Value/Remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

Report Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

logMeasResultListBT-r15 SEQUENCE (SIZE (1..maxBT-IdReport-r15)) OF SEQUENCE {

1 entry

Report Bluetooth beacon 1

bt-Addr-r15

Bluetooth public address of Bluetooth beacon 1

BIT STRING (SIZE (48))

rssi-BT-r15

Any allowed value

INTEGER (-128..127)

}

logMeasResultListWLAN-r15

Not Checked

}

}

}

}

}

8.6.10.3 Inter-RAT Immediate MDT / Reporting /WLAN measurement collection

8.6.10.3.1 Test Purpose (TP)

(1)

with { UE is in RRC_CONNECTED state and supports WLAN measurements and receives the ReportConfigEUTRA in RRCConnectionReconfiguration message with includeWLAN-Meas and measurement configured for event A2 and a WLAN node is included in WLAN-NameListConfig}

ensure that {

when { Entry condition for event A2 is met and WLAN measurement results that has not been reported is available }

then { UE sends MeasurementReport message with LogMeasResultListWLAN including WLAN measurement results corresponding to WLAN-NameListConfig included in includeWLAN-Meas }

}

(2)

with { UE is in RRC_CONNECTED state and supports WLAN measurements and receives the ReportConfigEUTRA in RRCConnectionReconfiguration message with includeWLAN-Meas and measurement configured for event A2 and a WLAN node is not included in WLAN-NameListConfig }

ensure that {

when { Entry condition for event A2 is met }

then { UE sends MeasurementReport message with LogMeasResultListWLAN not including WLAN measurement results of the WLAN node not included in WLAN-NameListConfig }

}

8.6.10.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.3 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]

If security has been activated successfully, 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 is configured in the corresponding reportConfig:

5> consider only the PCell to be applicable;

4> else if the reportSSTD-Meas is set to true in the corresponding reportConfig:

5> consider the PSCell to be applicable;

4> else if the eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> else if eventC1 or eventC2 is configured in the corresponding reportConfig; or if reportStrongestCSI-RSs is included in the corresponding reportConfig:

5> consider a CSI-RS resource on the associated frequency to be applicable when the concerned CSI-RS resource is included in the measCSI-RS-ToAddModList defined within the VarMeasConfig for this measId;

4> else if measRSSI-ReportConfig is configured in the corresponding reportConfig:

5> consider the resource indicated by the rmtc-Config on the associated frequency to be applicable;

4> else:

5> if useWhiteCellList is set to TRUE:

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

5> else:

6> 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;

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;

4> if the corresponding reportConfig includes alternativeTimeToTrigger and if the UE supports alternativeTimeToTrigger:

5> use the value of alternativeTimeToTrigger as the time to trigger instead of the value of timeToTrigger in the corresponding reportConfig for cells included in the altTTT-CellsToAddModList of the corresponding measObject;

…

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 for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the 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> 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 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> if the triggerType is set to event and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event:

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

3> if reportOnLeave is set to TRUE for the corresponding reporting configuration:

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

3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:

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

4> stop the periodical reporting timer for this measId, if running;

…

2> upon expiry of the periodical reporting timer for this measId:

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

The UE shall:

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

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

1> for this measurement, consider the primary or secondary cell that is configured on the frequency indicated in the associated measObjectEUTRA to be the serving cell;

Inequality A2-1 (Entering condition)

Inequality A2-2 (Leaving condition)

The variables in the formula are defined as follows:

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

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

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

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

Hys is 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> if the includeWLAN-Meas is configured in the corresponding reportConfig for this measId, set the measResults as follows:

2> if available, include the logMeasResultListWLAN, in order of decreasing RSSI for WLAN APs;

1> if the includeBT-Meas is configured in the corresponding reportConfig for this measId, set the measResults as follows:

2> if available, include the logMeasResultListBT, in order of decreasing RSSI for Bluetooth beacons;

…

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

8.6.10.3.3 Test description

8.6.10.3.3.1 Pre-test conditions

System Simulator:

  • Cell 1, WLAN AP 1 (Cell 27) and WLAN AP 2 (Cell 27b)
  • Cell 27 and Cell27b are configured as per 36.508 cl 4.4.8 with the OFFLOAD condition

UE:

None

Preamble:

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

8.6.10.3.3.2 Test procedure sequence

Table 8.6.10.3.3.2-1 illustrates the downlink power levels to be applied for Cell 1 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while row marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.6.10.3.3.2-1: Power levels

Parameter

Unit

Cell 1

Cell 27

(WLAN AP1)

Cell 27b

(WLAN AP2)

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-70

Power level is such that Ms > Thresh + Hys

BeaconRSSI

dBm

-60

-50

T1

Cell-specific RS EPRE

dBm/15kHz

-96

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

BeaconRSSI

dBm

-60

-50

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

Table 8.6.10.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including measConfig to setup intra LTE measurement and reporting for event A2 with includeLocationInfo configured.

<–

RRCConnectionReconfiguration

–

–

2

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

–

–

3

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

–

–

–

–

4

Check: Does the UE transmit a MeasurementReport message to report event A2 with the LogMeasResultListWLAN including one entry (WLAN AP 1) measurement result?

–>

MeasurementReport

1,2

P

8.6.10.3.3.3 Specific message contents

Table 8.6.10.3.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.6.10.3.3.2-2)

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

The specific message content for the SystemInformationBlockType17 message in Table 8.6.10.3.3.3-1A.

Table 8.6.10.3.3.3-1A: SystemInformationBlockType17 (Preamble and all steps of Table 8.6.10.3.3.2-2

Derivation Path: 36.508 table 4.4.3.3-15

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType17-r12 ::= SEQUENCE {

wlan-OffloadInfoPerPLMN-List-r12 [1] SEQUENCE (SIZE (1..maxPLMN-r11)) OF {

1 Entry

wlan-OffloadConfigCommon-r12

WLAN-OffloadConfig-DEFAULT

wlan-Id-List-r12 [1] SEQUENCE (SIZE (1..maxWLAN-Id-r12)) OF {

2 Entry

wlan-Identifiers[1] SEQUENCE{

ssid-r12[1]

Set as per Table 4.4.8-1

OCTET STRING (SIZE (1..32))

Service Set Identifier (SSID) defined in IEEE 802.11-2012

bssid-r12[1]

Not present

hessid-r12[1]

Not present

}

wlan-Identifiers[2] SEQUENCE{

ssid-r12[2]

Set as per Table 4.4.8-2

OCTET STRING (SIZE (1..32))

Service Set Identifier (SSID) defined in IEEE 802.11-2012

bssid-r12[2]

Not present

hessid-r12[2]

Not present

}

}

}

lateNonCriticalExtension

Not present

}

Table 8.6.10.3.3.3-2: MeasConfig (step 1, Table 8.6.10.3.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1

Information Element

Value/Remark

Comment

Condition

measConfig ::= SEQUENCE {

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

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

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

1 entry

reportConfigId[1]

IdReportConfig-A2

reportConfig[1]

ReportConfig-A2-H

}

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

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A2

}

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

1 entry

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.6.10.3.3.3-3: ReportConfig-A2-H (step 1, Table 8.6.10.3.3.2-2)

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

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

hysteresis

6

3 dB

}

}

maxReportCells

2

includeWLAN-Meas-r15 CHOICE {

setup SEQUENCE ( SIZE (1..maxWLAN-Name-r15)) OF

1 entry

WLAN AP 1

WLAN-Name-r15[1]

Set the value as per Cell 27

OCTET STRING (SIZE (1..32))

Refers to Service Set Identifier (SSID) defined in IEEE 802.11-2012

..}

}

Table 8.6.10.3.3.3-4: MeasurementReport (step 4, Table 8.6.10.3.3.2-2)

Derivation path: 36.508 table clause 4.6.1 table 4.6.1-5

Information Element

Value/Remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

Report Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

logMeasResultListWLAN-r15 SEQUENCE (SIZE (1..maxWLAN-Id-Report-r14)) OF SEQUENCE {

1 entry

Report WLAN AP1

wlan-Identifiers-r15[1] SEQUENCE {

ssid-r12

ssid for WLAN AP 1

bssid-r12

Not present

hessid-r12

Not present

}

rssiWLAN-r15[1]

Any allowed value

rtt-WLAN-r15[1]

Any allowed value

}

}

}

}

}

}