5.5 Measurements

36.3313GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Protocol specificationRadio Resource Control (RRC)Release 15TS

5.5.1 Introduction

The UE reports measurement information in accordance with the measurement configuration as provided by E-UTRAN. E-UTRAN provides the measurement configuration applicable for a UE in RRC_CONNECTED by means of dedicated signalling, i.e. using the RRCConnectionReconfiguration or RRCConnectionResume message.

The UE can be requested to perform the following types of measurements:

– Intra-frequency measurements: measurements at the downlink carrier frequency(ies) of the serving cell(s).

– Inter-frequency measurements: measurements at frequencies that differ from any of the downlink carrier frequency(ies) of the serving cell(s).

– Inter-RAT measurements of NR frequencies.

– Inter-RAT measurements of UTRA frequencies.

– Inter-RAT measurements of GERAN frequencies.

– Inter-RAT measurements of CDMA2000 HRPD or CDMA2000 1xRTT or WLAN frequencies.

– CBR measurements.

– Sensing measurements.

The measurement configuration includes the following parameters:

1. Measurement objects: The objects on which the UE shall perform the measurements.

– For intra-frequency and inter-frequency measurements a measurement object is a single E-UTRA carrier frequency. Associated with this carrier frequency, E-UTRAN can configure a list of cell specific offsets, a list of ‘blacklisted’ cells and a list of ‘whitelisted’ cells. Blacklisted cells are not considered in event evaluation or measurement reporting.

– For inter-RAT NR measurements a measurement object is a single NR carrier frequency. Associated with this carrier frequency, E-UTRAN can configure a list of ‘blacklisted’ cells. Blacklisted cells are not considered in event evaluation or measurement reporting.

– For inter-RAT UTRA measurements a measurement object is a set of cells on a single UTRA carrier frequency.

– For inter-RAT GERAN measurements a measurement object is a set of GERAN carrier frequencies.

– For inter-RAT CDMA2000 measurements a measurement object is a set of cells on a single (HRPD or 1xRTT) carrier frequency.

– For inter-RAT WLAN measurements a measurement object is a set of WLAN identifiers and optionally a set of WLAN frequencies.

– For CBR measurements and sensing measurements a measurement object is a set of transmission resource pools for V2X sidelink communication.

NOTE 1: Some measurements using the above mentioned measurement objects, only concern a single cell, e.g. measurements used to report neighbouring cell system information, PCell UE Rx-Tx time difference, or a pair of cells, e.g. SSTD measurements between the PCell and the PSCell.

2. Reporting configurations: A list of reporting configurations where each reporting configuration consists of the following:

– Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be periodical or a single event description.

– Reporting format: The quantities that the UE includes in the measurement report and associated information (e.g. number of cells to report).

3. Measurement identities: A list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is used as a reference number in the measurement report.

4. Quantity configurations: One quantity configuration is configured per RAT type. The quantity configuration defines the measurement quantities and associated filtering used for all event evaluation and related reporting of that measurement type. One filter can be configured per measurement quantity, except for NR where the network may configure up to 2 sets of quantity configurations each comprising per measurement quantity seperate filters for cell and RS index measurement results. The quantity configuration set that applies for a given measurement is indicated within the NR measurement object.

5. Measurement gaps: Periods that the UE may use to perform measurements, i.e. no (UL, DL) transmissions are scheduled.

E-UTRAN only configures a single measurement object for a given frequency (except for WLAN and except for CBR measurements), i.e. it is not possible to configure two or more measurement objects for the same frequency with different associated parameters, e.g. different offsets and/ or blacklists. E-UTRAN may configure multiple instances of the same event e.g. by configuring two reporting configurations with different thresholds.

The UE maintains a single measurement object list, a single reporting configuration list, and a single measurement identities list. The measurement object list includes measurement objects, that are specified per RAT type, possibly including intra-frequency object(s) (i.e. the object(s) corresponding to the serving frequency(ies)), inter-frequency object(s) and inter-RAT objects. Similarly, the reporting configuration list includes E-UTRA and inter-RAT reporting configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be linked to a reporting configuration.

The measurement procedures distinguish the following types of cells:

1. The serving cell(s) – these are the PCell and one or more SCells, if configured for a UE supporting CA or DC. Likewise, NR serving cell(s) are the NR PCell, NR PSCell and NR SCells, if the UE is configured with MR-DC.

2. Listed cells – these are cells listed within the measurement object(s) or, for inter-RAT WLAN, the WLANs matching the WLAN identifiers configured in the measurement object or the WLAN the UE is connected to.

3. Detected cells – these are cells that are not listed within the measurement object(s) but are detected by the UE on the carrier frequency(ies) indicated by the measurement object(s) or, for inter-RAT WLAN, the WLANs not included in the measObjectWLAN but meeting the triggering requirements.

For E-UTRA, the UE measures and reports on the serving cell(s), listed cells, detected cells, transmission resource pools for V2X sidelink communication, and, for RSSI and channel occupancy measurements, the UE measures and reports on any reception on the indicated frequency. For inter-RAT NR, the UE measures and reports on detected cells and, if configured with MR-DC, on NR serving cell(s). For inter-RAT UTRA, the UE measures and reports on listed cells and optionally on cells that are within a range for which reporting is allowed by E-UTRAN. For inter-RAT GERAN, the UE measures and reports on detected cells. For inter-RAT CDMA2000, the UE measures and reports on listed cells. For inter-RAT WLAN, the UE measures and reports on listed cells.

NOTE 2: For inter-RAT UTRA and CDMA2000, the UE measures and reports also on detected cells for the purpose of SON.

NOTE 3: This specification is based on the assumption that typically CSG cells of home deployment type are not indicated within the neighbour list. Furthermore, the assumption is that for non-home deployments, the physical cell identity is unique within the area of a large macro cell (i.e. as for UTRAN).

Whenever the procedural specification, other than contained in clause 5.5.2, refers to a field it concerns a field included in the VarMeasConfig unless explicitly stated otherwise i.e. only the measurement configuration procedure covers the direct UE action related to the received measConfig.

5.5.2 Measurement configuration

5.5.2.1 General

E-UTRAN applies the procedure as follows:

– to ensure that, whenever the UE has a measConfig, it includes a measObject for each LTE serving frequency;

– to configure at most one measurement identity using a reporting configuration with the purpose set to reportCGI;

– for E-UTRA serving frequencies, set the EARFCN within the corresponding measObject according to the band as used for reception/ transmission;

– to configure at most one measurement identity using a reporting configuration with ul-DelayConfig;

– to configure at most one measurement identity using a reporting configuration with reportSFTD-Meas;

– to configure at most one MeasObjectNR with the same carrierFreq;

The UE shall:

1> if the received measConfig includes the measObjectToRemoveList:

2> perform the measurement object removal procedure as specified in 5.5.2.4;

1> if the received measConfig includes the measObjectToAddModList:

2> perform the measurement object addition/ modification procedure as specified in 5.5.2.5;

1> if the received measConfig includes the reportConfigToRemoveList:

2> perform the reporting configuration removal procedure as specified in 5.5.2.6;

1> if the received measConfig includes the reportConfigToAddModList:

2> perform the reporting configuration addition/ modification procedure as specified in 5.5.2.7;

1> if the received measConfig includes the quantityConfig:

2> perform the quantity configuration procedure as specified in 5.5.2.8;

1> if the received measConfig includes the measIdToRemoveList:

2> perform the measurement identity removal procedure as specified in 5.5.2.2;

1> if the received measConfig includes the measIdToAddModList:

2> perform the measurement identity addition/ modification procedure as specified in 5.5.2.3;

1> if the received measConfig includes the measGapConfig or measGapConfigPerCC-List:

2> perform the measurement gap configuration procedure as specified in 5.5.2.9;

1> if the received measConfig includes the measGapConfigDensePRS:

2> perform the measurement gap configuration procedure for RSTD measurements with dense PRS configuration as specified in 5.5.2.9a;

1> if the received measConfig includes the measGapSharingConfig:

2> perform the measurement gap sharing configuration procedure as specified in 5.5.2.12;

1> if the received measConfig includes the s-Measure:

2> set the parameter s-Measure within VarMeasConfig to the lowest value of the RSRP ranges indicated by the received value of s-Measure;

1> if the received measConfig includes the preRegistrationInfoHRPD:

2> forward the preRegistrationInfoHRPD to CDMA2000 upper layers;

1> if the received measConfig includes the speedStatePars:

2> set the parameter speedStatePars within VarMeasConfig to the received value of speedStatePars;

1> if the received measConfig includes the allowInterruptions:

2> set the parameter allowInterruptions within VarMeasConfig to the received value of allowInterruptions;

5.5.2.2 Measurement identity removal

The UE shall:

1> for each measId included in the received measIdToRemoveList that is part of the current UE configuration in VarMeasConfig:

2> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

2> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

NOTE: The UE does not consider the message as erroneous if the measIdToRemoveList includes any measId value that is not part of the current UE configuration.

5.5.2.2a Measurement identity autonomous removal

The UE shall:

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

2> if the associated reportConfig concerns an event involving a serving cell while the concerned serving cell is not configured; or

2> if the associated reportConfig concerns an event involving a WLAN mobility set while the concerned WLAN mobility set is not configured; or

2> if the associated reportConfig concerns an event involving a transmission resource pool for V2X sidelink communication while the concerned resource pool is not configured; or

2> if the associated reportConfig concerns an event involving reportSFTD-Meas set to pSCell while the nr-Config is not configured:

3> remove the measId from the measIdList within the VarMeasConfig;

3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

3> stop the periodical reporting timer if running, and reset the associated information (e.g. timeToTrigger) for this measId;

NOTE 1: The above UE autonomous removal of measId‘s applies only for measurement events A1, A2, A6, and also applies for events A3 and A5 if configured for PSCell and W2 and W3 and V1 and V2 and event involving reportSFTD-Meas set to pSCell, if configured.

NOTE 2: When performed during re-establishment, the UE is only configured with a primary frequency (i.e. the SCell(s) and WLAN mobility set are released, if configured).

5.5.2.3 Measurement identity addition/ modification

E-UTRAN applies the procedure as follows:

– configure a measId only if the corresponding measurement object, the corresponding reporting configuration and the corresponding quantity configuration, are configured;

The UE shall:

1> for each measId included in the received measIdToAddModList:

2> if an entry with the matching measId exists in the measIdList within the VarMeasConfig:

3> replace the entry with the value received for this measId;

2> else:

3> add a new entry for this measId within the VarMeasConfig;

2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

2> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

2> if the triggerType is set to periodical and the purpose is set to reportCGI in the reportConfig associated with this measId:

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

4> if the si-RequestForHO is included in the reportConfig associated with this measId:

5> if the UE is a category 0 UE according to TS 36.306 [5]:

6> start timer T321 with the timer value set to 190 ms for this measId;

5> else:

6> start timer T321 with the timer value set to 150 ms for this measId;

4> else:

5> start timer T321 with the timer value set to 1 second for this measId;

3> else if the measObject associated with this measId concerns UTRA:

4> if the si-RequestForHO is included in the reportConfig associated with this measId:

5> for UTRA FDD, start timer T321 with the timer value set to 2 seconds for this measId;

5> for UTRA TDD, start timer T321 with the timer value set to [1 second] for this measId;

4> else:

5> start timer T321 with the timer value set to 8 seconds for this measId;

3> else if the measObject associated with this measId concerns NR:

4> if the measObject associated with this measId concerns FR1:

5> start timer T321 with the timer value set to 2 seconds for this measId;

4> if the measObject associated with this measId concerns FR2:

5> start timer T321 with the timer value set to 16 seconds for this measId;

3> else:

4> start timer T321 with the timer value set to 8 seconds for this measId;

5.5.2.4 Measurement object removal

The UE shall:

1> for each measObjectId included in the received measObjectToRemoveList that is part of the current UE configuration in VarMeasConfig:

2> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

2> remove all measId associated with this measObjectId from the measIdList within the VarMeasConfig, if any;

2> if a measId is removed from the measIdList:

3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

3> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

NOTE: The UE does not consider the message as erroneous if the measObjectToRemoveList includes any measObjectId value that is not part of the current UE configuration.

5.5.2.5 Measurement object addition/ modification

The UE shall:

1> for each measObjectId included in the received measObjectToAddModList:

2> if an entry with the matching measObjectId exists in the measObjectList within the VarMeasConfig, for this entry:

3> reconfigure the entry with the value received for this measObject, except for the fields cellsToAddModList, blackCellsToAddModList, whiteCellsToAddModList, altTTT-CellsToAddModList, cellsToRemoveList, blackCellsToRemoveList, whiteCellsToRemoveList, altTTT-CellsToRemoveList, measSubframePatternConfigNeigh, measDS-Config, wlan-ToAddModList, wlan-ToRemoveList, tx-ResourcePoolToRemoveList and tx-ResourcePoolToAddList;

3> if the received measObject includes the cellsToRemoveList:

4> for each cellIndex included in the cellsToRemoveList:

5> remove the entry with the matching cellIndex from the cellsToAddModList;

3> if the received measObject includes the cellsToAddModList:

4> for each cellIndex value included in the cellsToAddModList:

5> if an entry with the matching cellIndex exists in the cellsToAddModList:

6> replace the entry with the value received for this cellIndex;

5> else:

6> add a new entry for the received cellIndex to the cellsToAddModList;

3> if the received measObject includes the blackCellsToRemoveList:

4> for each cellIndex included in the blackCellsToRemoveList:

5> remove the entry with the matching cellIndex from the blackCellsToAddModList;

NOTE 1: For each cellIndex included in the blackCellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the black list of cells only if all cell indexes containing it are removed.

3> if the received measObject includes the blackCellsToAddModList:

4> for each cellIndex included in the blackCellsToAddModList:

5> if an entry with the matching cellIndex is included in the blackCellsToAddModList:

6> replace the entry with the value received for this cellIndex;

5> else:

6> add a new entry for the received cellIndex to the blackCellsToAddModList;

3> if the received measObject includes the whiteCellsToRemoveList:

4> for each cellIndex included in the whiteCellsToRemoveList:

5> remove the entry with the matching cellIndex from the whiteCellsToAddModList;

NOTE 2: For each cellIndex included in the whiteCellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the white list of cells only if all cell indexes containing it are removed.

3> if the received measObject includes the whiteCellsToAddModList:

4> for each cellIndex included in the whiteCellsToAddModList:

5> if an entry with the matching cellIndex is included in the whiteCellsToAddModList:

6> replace the entry with the value received for this cellIndex;

5> else:

6> add a new entry for the received cellIndex to the whiteCellsToAddModList;

3> if the received measObject includes the altTTT-CellsToRemoveList:

4> for each cellIndex included in the altTTT-CellsToRemoveList:

5> remove the entry with the matching cellIndex from the altTTT-CellsToAddModList;

NOTE 3: For each cellIndex included in the altTTT-CellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the list of cells only if all cell indexes containing it are removed.

3> if the received measObject includes the altTTT-CellsToAddModList:

4> for each cellIndex value included in the altTTT-CellsToAddModList:

5> if an entry with the matching cellIndex exists in the altTTT-CellsToAddModList:

6> replace the entry with the value received for this cellIndex;

5> else:

6> add a new entry for the received cellIndex to the altTTT-CellsToAddModList;

3> if the received measObject includes measSubframePatternConfigNeigh:

4> set measSubframePatternConfigNeigh within the VarMeasConfig to the value of the received field

3> if the received measObject includes measDS-Config:

4> if measDS-Config is set to setup:

5> if the received measDS-Config includes the measCSI-RS-ToRemoveList:

6> for each measCSI-RS-Id included in the measCSI-RS-ToRemoveList:

7> remove the entry with the matching measCSI-RS-Id from the measCSI-RS-ToAddModList;

5> if the received measDS-Config includes the measCSI-RS-ToAddModList, for each measCSI-RS-Id value included in the measCSI-RS-ToAddModList:

6> if an entry with the matching measCSI-RS-Id exists in the measCSI-RS-ToAddModList:

7> replace the entry with the value received for this measCSI-RS-Id;

6> else:

7> add a new entry for the received measCSI-RS-Id to the measCSI-RS-ToAddModList;

5> set other fields of the measDS-Config within the VarMeasConfig to the value of the received fields;

5> perform the discovery signals measurement timing configuration procedure as specified in 5.5.2.10;

4> else:

5> release the discovery signals measurement configuration;

3> if the received measObject modifies fields other than cellsForWhichToReportSFTD:

4> for each measId associated with this measObjectId in the measIdList within the VarMeasConfig, if any:

5> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

5> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

3> if the received measObject includes the wlan-ToRemoveList:

4> for each WLAN-Identifiers included in the wlan-ToRemoveList:

5> remove the entry with the matching WLAN-Identifiers from the wlan-ToAddModList;

NOTE 3a: Matching of WLAN-Identifiers requires that all WLAN identifier fields should be same.

3> if the received measObject includes the wlan-ToAddModList:

4> for each WLAN-Identifiers included in the wlan-ToAddModList:

5> add a new entry for the received WLAN-Identifiers to the wlan-ToAddModList;

3> if the received measObject includes the tx-ResourcePoolToRemoveList:

4> for each transmission resource pool indicated in tx-ResourcePoolToRemoveList:

5> remove the entry with the matching identity of the transmission resource pool from the tx-ResourcePoolToAddList;

3> if the received measObject includes the tx-ResourcePoolToAddList:

4> for each transmission resource pool indicated in tx-ResourcePoolToAddList:

5> add a new entry for the received identity of the transmission resource pool to the tx-ResourcePoolToAddList;

2> else:

3> add a new entry for the received measObject to the measObjectList within VarMeasConfig;

NOTE 4: UE does not need to retain cellForWhichToReportCGI in the measObject after reporting cgi-Info.

5.5.2.6 Reporting configuration removal

The UE shall:

1> for each reportConfigId included in the received reportConfigToRemoveList that is part of the current UE configuration in VarMeasConfig:

2> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

2> remove all measId associated with the reportConfigId from the measIdList within the VarMeasConfig, if any;

2> if a measId is removed from the measIdList:

3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

3> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

NOTE: The UE does not consider the message as erroneous if the reportConfigToRemoveList includes any reportConfigId value that is not part of the current UE configuration.

5.5.2.7 Reporting configuration addition/ modification

The UE shall:

1> for each reportConfigId included in the received reportConfigToAddModList:

2> if an entry with the matching reportConfigId exists in the reportConfigList within the VarMeasConfig, for this entry:

3> reconfigure the entry with the value received for this reportConfig;

3> for each measId associated with this reportConfigId included in the measIdList within the VarMeasConfig, if any:

4> remove the measurement reporting entry for this measId from in VarMeasReportList, if included;

4> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

2> else:

3> add a new entry for the received reportConfig to the reportConfigList within the VarMeasConfig;

5.5.2.8 Quantity configuration

The UE shall:

1> for each RAT for which the received quantityConfig includes parameter(s):

2> set the corresponding parameter(s) in quantityConfig within VarMeasConfig to the value of the received quantityConfig parameter(s);

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

2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

2> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;

5.5.2.9 Measurement gap configuration

The UE shall:

1> if measGapConfig is set to setup:

2> if a measurement gap configuration measGapConfig or measGapConfigPerCC-List is already setup, release the measurement gap configuration;

2> if the gapOffset in measGapConfig indicates a non-uniform gap pattern:

3> setup the measurement gap configuration indicated by the measGapConfig in accordance with the received gapOffset, i.e., the first subframe of the first gap of each non-uniform gap pattern occurs at an SFN and subframe meeting the following condition (SFN and subframe of MCG cells):

SFN mod T = FLOOR(gapOffset/10);

subframe = gapOffset mod 10;

with T = LMGRP/10 as defined in TS 36.133 [16];

2> else:

3> setup the measurement gap configuration indicated by the measGapConfig in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition (SFN and subframe of MCG cells):

SFN mod T = FLOOR(gapOffset/10);

subframe = gapOffset mod 10;

with T = MGRP/10 as defined in TS 36.133 [16];

2> if (NG)EN-DC is configured:

3> if the UE is configured with fr1-Gap set to TRUE:

4> apply the gap configuration for LTE serving cells and for NR serving cells on FR1;

3> else:

4> apply the gap configuration for all LTE and NR serving cells;

2> if mgta is set to TRUE, apply a timing advance value of 0.5ms to the gap occurrences calculated above according to TS 38.133 [84];

NOTE 1: The UE applies a single gap, which timing is relative to the MCG cells, even when configured with DC. In case of (NG)EN-DC, the UE may either be configured with a single (common) gap or with two separate gaps i.e. a first one for FR1 (configured by E-UTRA RRC) and a second one for FR2 (configured by NR RRC).

1> else if measGapConfig is set to release:

2> release the measurement gap configuration measGapConfig;

1> if measGapConfigPerCC-List is set to setup:

2> if a measurement gap configuration measGapConfig is already setup, release measGapConfig;

2> if measGapConfigToRemoveList is included:

3> for each ServCellIndex included in the measGapConfigToRemoveList:

4> release measGapConfigCC for the serving cell indicated by servCellId;

2> if measGapConfigToAddModList is included:

3> for each ServCellIndex included in the measGapConfigToAddModList:

4> store measGapConfigCC for the serving cell indicated by servCellId;

2> for each serving cell with stored measGapConfigCC indicating a non-uniform gap pattern, setup the measurement gap configuration indicated by the measGapConfigCC in accordance with the received gapOffset, i.e., the first subframe of the first gap of each non-uniform gap pattern occurs at an SFN and subframe meeting the following condition (SFN and subframe of MCG cells):

SFN mod T = FLOOR(gapOffset/10);

subframe = gapOffset mod 10;

with T = LMGRP/10 as defined in TS 36.133 [16];

2> for each serving cell with stored measGapConfigCC not indicating a non-uniform gap pattern, setup the measurement gap configuration indicated by the measGapConfigCC in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition (SFN and subframe of MCG cells):

SFN mod T = FLOOR(gapOffset/10);

subframe = gapOffset mod 10;

with T = MGRP/10 as defined in TS 36.133 [16];

NOTE 2: The UE applies gap timing relative to the MCG cells, even when configured with DC.

1> else (measGapConfigPerCC-List is set to release):

2> release the measurement gap configuration measGapConfigPerCC-List;

NOTE 3: When a SCell is released, the UE is not required to apply a per CC measurement gap configuration associated to the SCell.

5.5.2.9a Measurement gap configuration for RSTD measurements with dense PRS configuration

The UE shall:

1> if measGapConfigDensePRS is set to setup:

2> setup the measurement gap configuration indicated by the measGapConfigDensePRS in accordance with the received gapOffsetDensePRS, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition:

SFN mod T = FLOOR(gapOffsetDensePRS/10);

subframe = gapOffsetDensePRS mod 10;

with T = MGRP/10 as defined in TS 36.133 [16];

5.5.2.10 Discovery signals measurement timing configuration

The UE shall setup the discovery signals measurement timing configuration (DMTC) in accordance with the received dmtc-PeriodOffset, i.e., the first subframe of each DMTC occasion occurs at an SFN and subframe of the PCell meeting the following condition:

SFN mod T = FLOOR(dmtc-Offset/10);

subframe = dmtc-Offset mod 10;

with T = dmtc-Periodicity/10;

On the concerned frequency, the UE shall not consider discovery signals transmission in subframes outside the DMTC occasion for measurements including RRM measurements.

5.5.2.11 RSSI measurement timing configuration

The UE shall setup the RSSI measurement timing configuraton (RMTC) in accordance with the received rmtc-Period, rmtc-SubframeOffset if configured otherwise determined by the UE randomly, i.e. the first symbol of each RMTC occasion occurs at first symbol of an SFN and subframe of the PCell meeting the following condition:

SFN mod T = FLOOR(rmtc-SubframeOffset/10);

subframe = rmtc-SubframeOffset mod 10;

with T = rmtc-Period/10;

On the concerned frequency, the UE shall not consider RSSI measurements outside the configured RMTC occasion which lasts for measDuration for RSSI and channel occupancy measurements.

5.5.2.12 Measurement gap sharing configuration

The UE shall:

1> if measGapSharingConfig is set to setup:

2> if a measurement gap sharing configuration is already setup, release the measurement gap sharing configuration;

2> setup the measurement gap sharing configuration indicated by the measGapSharingConfig in accordance with the received measGapSharingScheme as defined in TS 36.133 [16];

NOTE: In case of (NG)EN-DC, the UE may either be configured with a single (common) gap sharing or with two separate gap sharing configurations, i.e. a first one for FR1 (configured by E-UTRA RRC) and a second one for FR2 (configured by NR RRC). For the case of per FR gap configuration, the gap sharing configured here (i.e. E-UTRA RRC) is applicable only for FR1 gap.

1> else:

2> release the measurement gap sharing configuration;

5.5.2.13 NR measurement timing configuration

The UE shall setup the first SS/PBCH block measurement timing configuration (SMTC) in accordance with the received periodicityAndOffset (providing Periodicity and Offset value for the following condition) in the MTC-SSB-NR configuration i.e., the first subframe of each SMTC occasion occurs at an SFN and subframe of the PCell meeting the following condition:

SFN mod T = FLOOR(Offset/10);

if the Periodicity is larger than sf5:

subframe = Offset mod 10;

else;

subframe = Offset or (Offset +5);

with T = CEIL(Periodicity/10).

On the concerned frequency, the UE shall not consider SS/PBCH block transmission in subframes outside the SMTC occasion which lasts for ssb-Duration for measurements including RRM measurements except for SFTD measurement (see TS 36.133 [16], clause 8.1.2.4.25.2 and 8.1.2.4.26.1).

5.5.3 Performing measurements

5.5.3.1 General

For all measurements, except for UE Rx–Tx time difference measurements, RSSI, UL PDCP Packet Delay per QCI measurement, channel occupancy measurements, CBR measurement, sensing measurement and except for WLAN measurements of Band, Carrier Info, Available Admission Capacity, Backhaul Bandwidth, Channel Utilization, and Station Count, the UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for evaluation of reporting criteria or for measurement reporting. When performing measurements on NR carriers, the UE derives the cell quality as specified in 5.5.3.3 and the beam quality as specified in 5.5.3.4.

The UE shall:

1> whenever the UE has a measConfig, perform RSRP and RSRQ measurements for each serving cell as follows:

2> for the PCell, apply the time domain measurement resource restriction in accordance with measSubframePatternPCell, if configured;

2> if the UE supports CRS based discovery signals measurement:

3> for each SCell in deactivated state, apply the discovery signals measurement timing configuration in accordance with measDS-Config, if configured within the measObject corresponding to the frequency of the SCell;

1> if the UE has a measConfig with rs-sinr-Config configured, perform RS-SINR (as indicated in the associated reportConfig) measurements as follows:

2> perform the corresponding measurements on the frequency indicated in the associated measObject using available idle periods or using autonomous gaps as necessary;

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

2> if the purpose for the associated reportConfig is set to reportCGI:

3> if the RAT indicated in the associated measObject is not NR:

4> if si-RequestForHO is configured for the associated reportConfig:

5> perform the corresponding measurements on the frequency and RAT indicated in the associated measObject using autonomous gaps as necessary;

4> else:

5> perform the corresponding measurements on the frequency and RAT indicated in the associated measObject using available idle periods or using autonomous gaps as necessary;

3> else:

4> perform the corresponding measurements on the NR frequency indicated in the associated measObject using available idle periods;

NOTE 1: If autonomous gaps are used to perform measurements, the UE is allowed to temporarily abort communication with all serving cell(s), i.e. create autonomous gaps to perform the corresponding measurements within the limits specified in TS 36.133 [16]. Otherwise, the UE only supports the measurements with the purpose set to reportCGI only if E-UTRAN has provided sufficient idle periods.

3> try to acquire the global cell identity of the cell indicated by the cellForWhichToReportCGI in the associated measObject by acquiring the relevant system information from the concerned cell;

3> if an entry in the cellAccessRelatedInfoList includes the selected PLMN, acquire the relevant system information from the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is an E-UTRAN cell:

4> try to acquire the CSG identity, if the CSG identity is broadcast in the concerned cell;

4> try to acquire the trackingAreaCode in the concerned cell;

4> try to acquire the list of additional PLMN Identities, as included in the plmn-IdentityList, if multiple PLMN identities are broadcast in the concerned cell;

4> if cellAccessRelatedInfoList is included, use trackingAreaCode and plmn-IdentityList from the entry of cellAccessRelatedInfoList containing the selected PLMN;

4> if the includeMultiBandInfo is configured:

5> try to acquire the freqBandIndicator in the SystemInformationBlockType1of the concerned cell;

5> try to acquire the list of additional frequency band indicators, as included in the multiBandInfoList, if multiple frequency band indicators are included in the SystemInformationBlockType1of the concerned cell;

5> try to acquire the freqBandIndicatorPriority, if the freqBandIndicatorPriority is included in the SystemInformationBlockType1of the concerned cell;

4> if cellAccessRelatedInfoList-5GC is broadcast in the concerned cell and the UE is E-UTRA/5GC capable:

5> try to acquire the cellAccessRelatedInfoList-5GC;

NOTE 2: The ‘primary’ PLMN is part of the global cell identity.

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a UTRAN cell:

4> try to acquire the LAC, the RAC and the list of additional PLMN Identities, if multiple PLMN identities are broadcast in the concerned cell;

4> try to acquire the CSG identity, if the CSG identity is broadcast in the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a GERAN cell:

4> try to acquire the RAC in the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a CDMA2000 cell and the cdma2000-Type included in the measObject is typeHRPD:

4> try to acquire the Sector ID in the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a CDMA2000 cell and the cdma2000-Type included in the measObject is type1XRTT:

4> try to acquire the BASE ID, SID and NID in the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated MeasObject is an NR cell:

4> if the indicated cell is broadcasting SIB1 (see TS 38.213 [88], clause 13):

5> try to acquire the plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode (if available), ran-AreaCode (if available) and cellIdentity for each entry of the plmn-IdentityInfoList;

5> try to acquire the frequencyBandList, if multiple frequency bands are broadcasted in the concerned cell;

2> if the ul-DelayConfig is configured for the associated reportConfig:

3> ignore the measObject;

3> configure the PDCP layer to perform UL PDCP Packet Delay per QCI measurement;

2> else:

3> if a measurement gap configuration is setup; or

3> if the UE does not require measurement gaps to perform the concerned measurements:

4> if s-Measure is not configured; or

4> if the UE is not in NE-DC and the PCell RSRP, after layer 3 filtering, is lower than s-Measure; or

4> if the UE is in NE-DC and the PSCell RSRP, after layer 3 filtering, is lower than s-Measure; or

4> if the associated measObject concerns NR; or

4> if measDS-Config is configured in the associated measObject:

5> if the UE supports CSI-RS based discovery signals measurement; and

5> if the eventId in the associated reportConfig is set to eventC1 or eventC2, or if reportStrongestCSI-RSs is set to true in the associated reportConfig:

6> perform the corresponding measurements of CSI-RS resources on the frequency indicated in the concerned measObject, applying the discovery signals measurement timing configuration in accordance with measDS-Config in the concerned measObject;

6> if reportCRS-Meas is set to true in the associated reportConfig, perform the corresponding measurements of neighbouring cells on the frequencies indicated in the concerned measObject as follows:

7> for neighbouring cells on the primary frequency, apply the time domain measurement resource restriction in accordance with measSubframePatternConfigNeigh, if configured in the concerned measObject;

7> apply the discovery signals measurement timing configuration in accordance with measDS-Config in the concerned measObject;

5> else:

6> perform the corresponding measurements of neighbouring cells on the frequencies and RATs indicated in the concerned measObject as follows:

7> for neighbouring cells on the primary frequency, apply the time domain measurement resource restriction in accordance with measSubframePatternConfigNeigh, if configured in the concerned measObject;

7> if the UE supports CRS based discovery signals measurement, apply the discovery signals measurement timing configuration in accordance with measDS-Config, if configured in the concerned measObject;

4> if the ue-RxTxTimeDiffPeriodical is configured in the associated reportConfig:

5> perform the UE Rx–Tx time difference measurements on the PCell;

4> if the reportSSTD-Meas is set to true or pSCell in the associated reportConfig:

5> perform SSTD measurements between the PCell and the PSCell;

4> if the reportSFTD-Meas is set to pSCell in the associated reportConfig:

5> perform SFTD measurements between the PCell and the NR PSCell;

4> if the reportSFTD-Meas is set to neighborCells in the associated reportConfig:

5> perform SFTD measurements between the PCell and NR cell(s) on the frequency indicated in the associated measObject;

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

5> perform the RSSI and channel occupancy measurements on the frequency indicated in the associated measObject;

2> perform the evaluation of reporting criteria as specified in 5.5.4;

The UE capable of CBR measurement when configured to transmit non-P2X related V2X sidelink communication shall:

1> if in coverage on the frequency used for V2X sidelink communication transmission as defined in TS 36.304 [4], clause 11.4; or

1> if the concerned frequency is included in v2x-InterFreqInfoList in RRCConnectionReconfiguration or in v2x-InterFreqInfoList within SystemInformationBlockType21 or SystemInformationBlockType26:

2> if the UE is in RRC_IDLE:

3> if the concerned frequency is the camped frequency:

4> perform CBR measurement on the pools in v2x-CommTxPoolNormalCommon and v2x-CommTxPoolExceptional if included in SystemInformationBlockType21;

3> else if v2x-CommTxPoolNormal or v2x-CommTxPoolExceptional is included in v2x-InterFreqInfoList for the concerned frequency within SystemInformationBlockType21 or SystemInformationBlockType26:

4> perform CBR measurement on pools in v2x-CommTxPoolNormal and v2x-CommTxPoolExceptional in v2x-InterFreqInfoList for the concerned frequency in SystemInformationBlockType21 or SystemInformationBlockType26;

3> else if the concerned frequency broadcasts SystemInformationBlockType21:

4> perform CBR measurement on pools in v2x-CommTxPoolNormalCommon and v2x-CommTxPoolExceptional if included in SystemInformationBlockType21 broadcast on the concerned frequency;

2> if the UE is in RRC_CONNECTED:

3> if tx-ResourcePoolToAddList is included in VarMeasConfig:

4> perform CBR measurements on each resource pool indicated in tx-ResourcePoolToAddList;

3> if the concerned frequency is the PCell’s frequency:

4> perform CBR measurement on the pools in v2x-CommTxPoolNormalDedicated or v2x-SchedulingPool if included in RRCConnectionReconfiguration, v2x-CommTxPoolExceptional if included in SystemInformationBlockType21 for the concerned frequency and v2x-CommTxPoolExceptional if included in mobilityControlInfoV2X;

3> else if v2x-CommTxPoolNormal, v2x-SchedulingPool or v2x-CommTxPoolExceptional is included in v2x-InterFreqInfoList for the concerned frequency within RRCConnectionReconfiguration:

4> perform CBR measurement on pools in v2x-CommTxPoolNormal, v2x-SchedulingPool, and v2x-CommTxPoolExceptional if included in v2x-InterFreqInfoList for the concerned frequency in RRCConnectionReconfiguration;

3> else if the concerned frequency broadcasts SystemInformationBlockType21:

4> perform CBR measurement on pools in v2x-CommTxPoolNormalCommon and v2x-CommTxPoolExceptional if included in SystemInformationBlockType21 for the concerned frequency;

1> else:

2> perform CBR measurement on pools in v2x-CommTxPoolList in SL-V2X-Preconfiguration for the concerned frequency;

The UE capable of sensing measurement, with commTxResources set to scheduled, shall:

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

2> if measSensing-Config is configured in the associated measObject

3> perform the sensing measurement in accordance with TS 36.213 [23] on the pools of v2x-SchedulingPool and also indicated in tx-ResourcePoolToAddList in the associated measObject, using sensingSubchannelNumber, sensingPeriodicity, sensingReselectionCounter and sensingPriority.

NOTE 3: The s-Measure defines when the UE is required to perform measurements. The UE is however allowed to perform measurements also when the PCell RSRP (or PSCell RSRP, if the UE is in NE-DC) exceeds s-Measure, e.g., to measure cells broadcasting a CSG identity following use of the autonomous search function as defined in TS 36.304 [4].

NOTE 4: The UE may not perform the WLAN measurements it is configured with e.g. due to connection to another WLAN based on user preferences as specified in TS 23.402 [75] or due to turning off WLAN.

5.5.3.2 Layer 3 filtering

The UE shall:

1> for each measurement quantity that the UE performs measurements according to 5.5.3.1:

NOTE 1: This does not include quantities configured solely for UE Rx-Tx time difference, SSTD measurements and RSSI, channel occupancy measurements, WLAN measurements of Band, Carrier Info, Available Admission Capacity, Backhaul Bandwidth, Channel Utilization, and Station Count, CBR measurement, sensing measurement and UL PDCP Packet Delay per QCI measurement i.e. for those types of measurements the UE ignores the triggerQuantity and reportQuantity.

2> filter the measured result, before using for evaluation of reporting criteria or for measurement reporting, by the following formula:

where

Mn is the latest received measurement result from the physical layer;

Fn is the updated filtered measurement result, that is used for evaluation of reporting criteria or for measurement reporting;

Fn-1 is the old filtered measurement result, where F0 is set to M1 when the first measurement result from the physical layer is received; and

except for NR, a = 1/2(k/4), where k is the filterCoefficient for the corresponding measurement quantity received by the quantityConfig; for NR, a = 1/2(ki/4), where ki is the filterCoefficient for the corresponding measurement quantity of the i:th QuantityConfigNR in quantityConfigNRList, and i is indicated by quantityConfigSet in MeasObjectNR;

2> adapt the filter such that the time characteristics of the filter are preserved at different input rates, observing that the filterCoefficient k assumes a sample rate equal to 200 ms;

NOTE 2: If k is set to 0, no layer 3 filtering is applicable.

NOTE 3: The filtering is performed in the same domain as used for evaluation of reporting criteria or for measurement reporting, i.e., logarithmic filtering for logarithmic measurements.

NOTE 4: The filter input rate is implementation dependent, to fulfil the performance requirements set in TS 36.133 [16]. For further details about the physical layer measurements, see TS 36.133 [16].

5.5.3.3 Derivation of NR cell quality

The UE shall:

1> if the associated measObject includes maxRS-IndexCellQual; and

1> if there are multiple detected NR-SS beams associated to the cell; and

1> if threshRS-Index is configured and if for more than one of the NR-SS beams the measured result exceeds this threshold:

2> consider the cell quality to be the linear average of the power values of the, up to maxRS-IndexCellQual, best of the detected NR-SS beams exceeding threshRS-Index;

1> else:

2> consider the cell quality to be the measurement result of the detected NR-SS beam, associated to the cell, with the highest measurement result;

5.5.3.4 Derivation of NR beam quality

The UE shall:

1> consider the beam quality to be the value resulting after layer 3 filtering, as specified in 5.5.3.2, of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [89];

5.5.4 Measurement report triggering

5.5.4.1 General

If security has been activated successfully, the UE shall:

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

2> if the corresponding reportConfig includes a purpose set to reportStrongestCellsForSON:

3> consider any neighbouring cell detected on the associated frequency to be applicable;

2> else if the corresponding reportConfig includes a purpose set to reportCGI:

3> consider any neighbouring cell detected on the associated frequency/ set of frequencies (GERAN) which has a physical cell identity matching the value of the cellForWhichToReportCGI included in the corresponding measObject within the VarMeasConfig to be applicable;

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 set to true 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;

3> else if the corresponding measObject concerns UTRA or CDMA2000:

4> consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is included in the cellsToAddModList defined within the VarMeasConfig for this measId (i.e. the cell is included in the white-list);

NOTE 0: The UE may also consider a neighbouring cell on the associated UTRA frequency to be applicable when the concerned cell is included in the csg-allowedReportingCells within the VarMeasConfig for this measId, if configured in the corresponding measObjectUTRA (i.e. the cell is included in the range of physical cell identities for which reporting is allowed).

3> else if the corresponding measObject concerns GERAN:

4> consider a neighbouring cell on the associated set of frequencies to be applicable when the concerned cell matches the ncc-Permitted defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns WLAN:

4> consider a WLAN on the associated set of frequencies, as indicated by carrierFreq or on all WLAN frequencies when carrierFreq is not present, to be applicable if the WLAN matches all WLAN identifiers of at least one entry within wlan-Id-List for this measId;

3> else if the corresponding measObject concerns NR:

4> if the reportSFTD-Meas is set to pSCell in the corresponding reportConfigInterRAT:

5> consider the PSCell to be applicable;

4> else if the reportSFTD-Meas is set to neighborCells in the corresponding reportConfigInterRAT:

5> if cellsForWhichToReportSFTD is configured in the corresponding measObjectNR:

6> consider any neighbouring NR cell on the associated frequency that is included in cellsForWhichToReportSFTD to be applicable;

5> else:

6> consider up to 3 strongest neighbouring NR cells detected on the associated frequency to be applicable when the concerned cells are not included in the blackCellsToAddModList defined within the VarMeasConfig for this measId;

4> else:

5> if the eventB1 or eventB2 is configured in the corresponding reportConfig:

6> consider a serving cell, if any, on the associated NR frequency as neighbouring cell;

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 tx-ResourcePoolToAddList is configured in the measObject, and if the corresponding reportConfig includes a purpose set to sidelink or includes eventV1 or eventV2:

3> consider the transmission resource pools indicated by the tx-ResourcePoolToAddList defined within the VarMeasConfig for this measId to be applicable;

2> if the corresponding reportConfig includes a purpose set to reportLocation:

3> consider only the PCell to be applicable;

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 set to true 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 set to true 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 numberOfTriggeringCells:

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 or if a6-ReportOnLeave is set to TRUE or if a4-a5-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> if the triggerType is set to event 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 CSI-RS resources for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include an measurement reporting entry for this measId (i.e. a first CSI-RS resource 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 CSI-RS resource(s) in the csi-RS-TriggeredList defined within the VarMeasReportList for this measId;

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

2> if the triggerType is set to event 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 CSI-RS resources not included in the csi-RS-TriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (i.e. a subsequent CSI-RS resource triggers the event):

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

3> include the concerned CSI-RS resource(s) in the csi-RS-TriggeredList defined within the VarMeasReportList for this measId;

3> 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 CSI-RS resources included in the csi-RS-TriggeredList 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 CSI-RS resource(s) in the csi-RS-TriggeredList defined within the VarMeasReportList for this measId;

3> if c1-ReportOnLeave is set to TRUE for the corresponding reporting configuration or if c2-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 csi-RS-TriggeredList 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> if the triggerType is set to event 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 transmission resource pools for all measurements taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include an measurement reporting entry for this measId (a first transmission resource pool 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 transmission resource pool(s) in the poolsTriggeredList defined within the VarMeasReportList for this measId;

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

2> if the triggerType is set to event 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 transmission resource pools not included in the poolsTriggeredList for all measurements taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent transmission resource pool triggers the event):

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

3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the VarMeasReportList for this measId;

3> 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 applicable transmission resource pools included in the poolsTriggeredList defined within the VarMeasReportList for this measId for all measurements taken during timeToTrigger defined within the VarMeasConfig for this event:

3> remove the concerned transmission resource pool(s) from the poolsTriggeredList defined within the VarMeasReportList for this measId;

3> if the poolsTriggeredList 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> 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;

2> if measRSSI-ReportConfig is included and if a (first) measurement result is available:

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 immediately when RSSI sample values are reported by the physical layer after the first L1 measurement duration;

2> else if the purpose is included and set to reportStrongestCells, reportStrongestCellsForSON, reportLocation sidelink or sensing and if a (first) measurement result is available:

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> if the purpose is set to reportStrongestCells and reportStrongestCSI-RSs is set to FALSE:

4> if the triggerType is set to periodical and the corresponding reportConfig includes the ul-DelayConfig:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided by lower layers;

4> else if the corresponding measurement object concerns WLAN:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the PCell and for the applicable WLAN(s);

4> else if the reportAmount exceeds 1:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the PCell;

4> else (i.e. the reportAmount is equal to 1):

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the PCell and for the strongest cell among the applicable cells, or becomes available for the pair of PCell and the PSCell in case of SSTD measurements, or becomes available for each requested pair of PCell and NR cell or the maximal measurement reporting delay as specified in TS 36.133 [16], clause 8.17.2.3 in case of SFTD measurements;

3> if the purpose is set to reportLocation, sidelink or sensing:

4> if the purpose is set to reportLocation:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after both the quantity to be reported for the PCell and the location information become available;

4> else if the purpose is set to sidelink:

5> initiate the measurement reporting procedure as specified in 5.5.5 immediately after both the quantity to be reported for the PCell and the CBR measurement result become available;

4> else if the purpose is set to sensing:

5> initiate the measurement reporting procedure as specified in 5.5.5 immediately after both the quantity to be reported for the PCell and the sensing measurement result become available;

3> else if the purpose is not set to reportStrongestCells or reportStrongestCSI-RSs is set to true:

4> initiate the measurement reporting procedure, as specified in 5.5.5, when it has determined the strongest cells on the associated frequency;

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

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

2> if the purpose is included and set to reportCGI:

3> if the UE acquired the information needed to set all fields of cgi-Info for the requested cell; or

3> if the UE detects that the requested NR cell is not transmitting SIB1:

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

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

4> stop timer T321;

4> 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 (or PSCell RSRP, if the UE is in NE-DC) 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].

5.5.4.2 Event A1 (Serving becomes better than threshold)

The UE shall:

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

1> consider the leaving condition for this event to be satisfied when condition A1-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 A1-1 (Entering condition)

Inequality A1-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 reportConfigEUTRA for this event).

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

Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

5.5.4.3 Event A2 (Serving becomes worse than threshold)

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 reportConfigEUTRA for this event).

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

Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

5.5.4.4 Event A3 (Neighbour becomes offset better than PCell/ PSCell)

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.

5.5.4.5 Event A4 (Neighbour becomes better than threshold)

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 and RS-SINR.

Ofn, Ocn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

5.5.4.6 Event A5 (PCell/ PSCell becomes worse than threshold1 and neighbour becomes better than threshold2)

The UE shall:

1> consider the entering condition for this event to be satisfied when both condition 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;

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

2> use the PSCell for Mp;

1> else:

2> use the PCell for Mp;

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 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:

Mp is the measurement result of the PCell/ PSCell, 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, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ofn, Ocn, Hys are expressed in dB.

Thresh1 is expressed in the same unit as Mp.

Thresh2 is expressed in the same unit as Mn.

5.5.4.6a Event A6 (Neighbour becomes offset better than SCell)

The UE shall:

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

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

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

NOTE: The neighbour(s) is on the same frequency as the SCell i.e. both are on the frequency indicated in the associated measObject.

Inequality A6-1 (Entering condition)

Inequality A6-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.

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.

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

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

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. a6-Offset as defined within reportConfigEUTRA for this event).

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

Ocn, Ocs, Hys, Off are expressed in dB.

5.5.4.7 Event B1 (Inter RAT neighbour becomes better than threshold)

The UE shall:

1> for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;

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

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

Inequality B1-1 (Entering condition)

Inequality B1-2 (Leaving condition)

The variables in the formula are defined as follows:

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. For CDMA 2000 measurement result, pilotStrength is divided by -2.

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

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

Thresh is the threshold parameter for this event (i.e. b1-Threshold as defined within reportConfigInterRAT for this event). For CDMA2000, b1-Threshold is divided by -2.

Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

5.5.4.8 Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2)

The UE shall:

1> for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;

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

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

Inequality B2-1 (Entering condition 1)

Inequality B2-2 (Entering condition 2)

Inequality B2-3 (Leaving condition 1)

Inequality B2-4 (Leaving condition 2)

The variables in the formula are defined as follows:

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

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. For CDMA2000 measurement result, pilotStrength is divided by -2.

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

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

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

Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2 as defined within reportConfigInterRAT for this event). For CDMA2000, b2-Threshold2 is divided by -2.

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

Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Hys are expressed in dB.

Thresh1 is expressed in the same unit as Mp.

Thresh2 is expressed in the same unit as Mn.

5.5.4.9 Event C1 (CSI-RS resource becomes better than threshold)

The UE shall:

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

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

Inequality C1-1 (Entering condition)

Inequality C1-2 (Leaving condition)

The variables in the formula are defined as follows:

Mcr is the measurement result of the CSI-RS resource, not taking into account any offsets.

Ocr is the CSI-RS specific offset (i.e. csi-RS-IndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the CSI-RS resource), and set to zero if not configured for the CSI-RS resource.

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. c1-Threshold as defined within reportConfigEUTRA for this event).

Mcr, Thresh are expressed in dBm.

Ocr, Hys are expressed in dB.

5.5.4.10 Event C2 (CSI-RS resource becomes offset better than reference CSI-RS resource)

The UE shall:

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

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

NOTE: The CSI-RS resource(s) that triggers the event is on the same frequency as the reference CSI-RS resource, i.e. both are on the frequency indicated in the associated measObject.

Inequality C2-1 (Entering condition)

Inequality C2-2 (Leaving condition)

The variables in the formula are defined as follows:

Mcr is the measurement result of the CSI-RS resource, not taking into account any offsets.

Ocr is the CSI-RS specific offset of the CSI-RS resource (i.e. csi-RS-IndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the CSI-RS resource), and set to zero if not configured for the CSI-RS resource.

Mref is the measurement result of the reference CSI-RS resource (i.e. c2-RefCSI-RS as defined within reportConfigEUTRA for this event), not taking into account any offsets.

Oref is the CSI-RS specific offset of the reference CSI-RS resource (i.e. csi-RS-IndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the reference CSI-RS resource), and is set to zero if not configured for the reference CSI-RS resource.

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. c2-Offset as defined within reportConfigEUTRA for this event).

Mcr, Mref are expressed in dBm.

Ocr, Oref, Hys, Off are expressed in dB.

5.5.4.11 Event W1 (WLAN becomes better than a threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when wlan-MobilitySet within VarWLAN-MobilityConfig does not contain any entries and condition W1-1, as specified below, is fulfilled;

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

Inequality W1-1 (Entering condition)

Inequality W1-2 (Leaving condition)

The variables in the formula are defined as follows:

Mn is the measurement result of WLAN(s) configured in the measurement object, not taking into account any offsets.

Hys is the hysteresis parameter for this event.

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

Mn is expressed in dBm.

Hys is expressed in dB.

Thresh is expressed in the same unit as Mn.

5.5.4.12 Event W2 (All WLAN inside WLAN mobility set becomes worse than threshold1 and a WLAN outside WLAN mobility set becomes better than threshold2)

The UE shall:

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

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

Inequality W2-1 (Entering condition 1)

Inequality W2-2 (Entering condition 2)

Inequality W2-3 (Leaving condition 1)

Inequality W2-4 (Leaving condition 2)

The variables in the formula are defined as follows:

Ms is the measurement result of WLAN(s) which matches all WLAN identifiers of at least one entry within wlan-MobilitySet in VarWLAN-MobilityConfig, not taking into account any offsets.

Mn is the measurement result of WLAN(s) configured in the measurement object which does not match all WLAN identifiers of any entry within wlan-MobilitySet in VarWLAN-MobilityConfig, not taking into account any offsets.

Hys is the hysteresis parameter for this event.

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

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

Mn, Ms are expressed in dBm.

Hys is expressed in dB.

Thresh1 is expressed in the same unit as Ms.

Thresh2 is expressed in the same unit as Mn.

5.5.4.13 Event W3 (All WLAN inside WLAN mobility set becomes worse than a threshold)

The UE shall:

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

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

Inequality W3-1 (Entering condition)

Inequality W3-2 (Leaving condition)

The variables in the formula are defined as follows:

Ms is the measurement result of WLAN(s) which matches all WLAN identifiers of at least one entry within wlan-MobilitySet in VarWLAN-MobilityConfig, not taking into account any offsets.

Hys is the hysteresis parameter for this event.

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

Ms is expressed in dBm.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

5.5.4.14 Event V1 (The channel busy ratio is above a threshold)

The UE shall:

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

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

Inequality V1-1 (Entering condition)

Inequality V1-2 (Leaving condition)

The variables in the formula are defined as follows:

Ms is the measurement result of channel busy ratio of the transmission resource pool, not taking into account any offsets.

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. v1-Threshold as defined within ReportConfigEUTRA).

Ms is expressed in decimal from 0 to 1 in steps of 0.01.

Hys is expressed is in the same unit as Ms.

Thresh is expressed in the same unit as Ms.

5.5.4.15 Event V2 (The channel busy ratio is below a threshold)

The UE shall:

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

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

Inequality V2-1 (Entering condition)

Inequality V2-2 (Leaving condition)

The variables in the formula are defined as follows:

Ms is the measurement result of channel busy ratio of the transmission resource pool, not taking into account any offsets.

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. v2-Threshold as defined within ReportConfigEUTRA).

Ms is expressed in decimal from 0 to 1 in steps of 0.01.

Hys is expressed is in the same unit as Ms.

Thresh is expressed in the same unit as Ms.

5.5.4.16 Event H1 (The Aerial UE height is above a threshold)

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.

5.5.4.17 Event H2 (The Aerial UE height is below a threshold)

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.

5.5.5 Measurement reporting

5.5.5.1 General

Figure 5.5.5.1-1: Measurement reporting

The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN. The UE shall initiate this procedure only after successful security activation.

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 measResultPCell to include the quantities of the PCell;

1> set the measResultServFreqList to include for each E-UTRA SCell that is configured, if any, within measResultSCell the quantities of the concerned SCell, if available according to performance requirements in TS 36.133 [16], except if purpose for the reportConfig associated with the measId that triggered the measurement reporting is set to reportLocation;

1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:

2> for each E-UTRA serving frequency for which measObjectId is referenced in the measIdList, other than the frequency corresponding with the measId that triggered the measurement reporting:

3> set the measResultServFreqList to include within measResultBestNeighCell the physCellId and the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

1> if the triggerType is set to event; and if the corresponding measObject concerns NR; and if eventId is set to eventB1-NR or eventB2-NR; or

1> if the triggerType is set to event; and if eventId is set to eventA3 or eventA4 or eventA5:

2> if purpose for the reportConfig or reportConfigInterRAT associated with the measId that triggered the measurement reporting is set to a value other than reportLocation:

3> set the measResultServFreqListNR to include for each NR serving frequency that the UE is configured to measure according to TS 38.331 [82], if any, the following:

4> set measResultSCell to include the available results of the NR serving cell, as specified in 5.5.5.2;

4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas and if eventId is set to eventA3 or eventA4 or eventA5:

5> set measResultBestNeighCell to include the available results, as specified in 5.5.5.2, of the non-serving cell with the highest sorting quantity determined as specified in 5.5.5.3;

3> for each (serving or neighbouring) cell for which the UE reports results according to the previous, additionally include available beam results according to the following:

4> if maxReportRS-Index is configured, set measResultRS-IndexList to include available results, as specified in 5.5.5.2, of up to maxReportRS-Index beams, ordered based on the quantity determined as specified in 5.5.5.3;

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 1: 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;

6> sort the included cells in order of decreasing triggerQuantity, i.e. the best cell is included first;

5> if the measObject associated with this measId concerns NR:

6> set the measResultCell to include the quantity(ies) indicated in the reportQuantityCellNR within the concerned reportConfig;

6> if maxReportRS-Index and reportQuantityRS-IndexNR are configured, set measResultRS-IndexList to include the result of the best beam if threshRS-Index is included in the VarMeasConfig for the corresponding measObject, and the remaining beams whose quantity is above threshRS-Index, up to maxReportRS-Index beams in total:

7> order beams based on the sorting quantity determined as specified in 5.5.5.3;

7> for each included beam:

8> include ssbIndex;

8> if reportRS-IndexResultsNR is set to TRUE, for each quantity indicated, include the corresponding measurement result in measResultSSB-Index for each ssb-Index;

6> sort the included cells in order of decreasing sorting quantity determined as specified in 5.5.5.3;

5> if the measObject associated with this measId concerns UTRA FDD and if ReportConfigInterRAT includes the reportQuantityUTRA-FDD:

6> set the measResult to include the quantities indicated by the reportQuantityUTRA-FDD in order of decreasing measQuantityUTRA-FDD within the quantityConfig, i.e. the best cell is included first;

5> if the measObject associated with this measId concerns UTRA FDD and if ReportConfigInterRAT does not include the reportQuantityUTRA-FDD; or

5> if the measObject associated with this measId concerns UTRA TDD, GERAN or CDMA2000:

6> set the measResult to the quantity as configured for the concerned RAT within the quantityConfig in order of either decreasing quantity for UTRA and GERAN or increasing quantity for CDMA2000 pilotStrength, i.e. the best cell is included first;

3> else if the purpose is set to reportCGI and the corresponding measObject concerns a RAT other than NR:

4> if the mandatory present fields of the cgi-Info for the cell indicated by the cellForWhichToReportCGI in the associated measObject have been obtained:

5> if the includeMultiBandInfo is configured:

6> include the freqBandIndicator;

6> if the cell broadcasts the multiBandInfoList, include the multiBandInfoList;

6> if the cell broadcasts the freqBandIndicatorPriority, include the freqBandIndicatorPriority;

5> if the cell broadcasts a CSG identity:

6> include the csg-Identity;

6> include the csg-MemberStatus and set it to member if the cell is a CSG member cell;

5> if the si-RequestForHO is configured within the reportConfig associated with this measId:

6> include the cgi-Info containing all the fields other than the plmn-IdentityList that have been successfully acquired;

6> include, within the cgi-Info, the field plmn-IdentityList in accordance with the following:

7> if the cell is a CSG member cell, determine the subset of the PLMN identities, starting from the second entry of PLMN identities in the broadcast information, that meet the following conditions:

a) equal to the RPLMN or an EPLMN; and

b) the CSG whitelist of the UE includes an entry comprising of the concerned PLMN identity and the CSG identity broadcast by the cell;

7> if the subset of PLMN identities determined according to the previous includes at least one PLMN identity, include the plmn-IdentityList and set it to include this subset of the PLMN identities;

7> if the cell is a CSG member cell, include the primaryPLMN-Suitable if the primary PLMN meets conditions a) and b) specified above;

7> if the cell does not broadcast csg-Identity and the UE is capable of reporting the plmn-IdentityList from cells not broadcasting csg-Identity:

8> include in the plmn-IdentityList the list of identities starting from the second entry of PLMN identities in the broadcast information;

5> else:

6> include the cgi-Info containing all the fields that have been successfully acquired and in accordance with the following:

7> include in the plmn-IdentityList the list of identities starting from the second entry of PLMN Identities in the broadcast information;

4> if the cellAccessRelatedInfoList-5GC has been acquired:

5> include cgi-Info-5GC;

NOTE 1a: The UE may include the cgi-Info-5GC even when the N1 mode is disabled.

3> else if the purpose is set to reportCGI and the corresponding measObject concerns NR RAT:

4> if the Cell information of cgi-Info for the cell indicated by the cellForWhichToReportCGI in the associated measObject has been obtained:

5> include plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode (if available), ran-AreaCode (if available) and cellIdentity for each entry of the plmn-IdentityInfoList;

5> include frequencyBandList if broadcasted;

4> else if MIB associated with the concerned measObject indicates that SIB1 is not broadcast:

5> include the noSIB1 field;

1> for the cells included according to the previous (i.e. covering the PCell, the SCells, the best non-serving cells on serving frequencies as well as neighbouring EUTRA cells) include results according to the extended RSRQ if corresponding results are available according to the associated performance requirements defined in TS 36.133 [16];

1> if there is at least one applicable CSI-RS resource to report:

2> set the measResultCSI-RS-List to include the best CSI-RS resources up to maxReportCells in accordance with the following:

3> if the triggerType is set to event:

4> include the CSI-RS resources included in the csi-RS-TriggeredList as defined within the VarMeasReportList for this measId;

3> else:

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

NOTE 2: The reliability of the report (i.e. the certainty it contains the strongest CSI-RS resources 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 CSI-RS resource that is included in the measResultCSI-RS-List:

4> include the measCSI-RS-Id;

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

5> set the csi-RSRP-Result to include the quantity indicated in the reportQuantity within the concerned reportConfig in order of decreasing triggerQuantityCSI-RS, i.e. the best CSI-RS resource is included first;

4> if reportCRS-Meas is set to true within the associated reportConfig, and the cell indicated by physCellId of this CSI-RS resource is not a serving cell:

5> set the measResultNeighCells to include the cell indicated by physCellId of this CSI-RS resource, and include the physCellId;

5> set the rsrpResult to include the RSRP of the concerned cell, if available according to performance requirements in TS 36.133 [16];

5> set the rsrqResult to include the RSRQ of the concerned cell, if available according to performance requirements in TS 36.133 [16];

1> if the ue-RxTxTimeDiffPeriodical is configured within the corresponding reportConfig for this measId;

2> set the ue-RxTxTimeDiffResult to the measurement result provided by lower layers;

2> set the currentSFN;

1> if the measRSSI-ReportConfig is configured within the corresponding reportConfig for this measId:

2> set the rssi-Result to the average of sample value(s) provided by lower layers in the reportInterval;

2> set the channelOccupancy to the rounded percentage of sample values which are beyond to the channelOccupancyThreshold within all the sample values in the reportInterval;

1> if uplink PDCP delay results are available:

2> set the ul-PDCP-DelayResultList to include the uplink PDCP delay results available;

1> if the includeLocationInfo is configured in the corresponding reportConfig for this measId or if purpose for the reportConfig associated with the measId that triggered the measurement reporting is set to reportLocation; 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, except if purpose for the reportConfig associated with the measId that triggered the measurement reporting is set to reportLocation;

2> include the verticalVelocityInfo, if available;

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> if the reportSSTD-Meas is set to true or pSCell within the corresponding reportConfig for this measId:

2> set the measResultSSTD to the measurement results provided by lower layers;

1> if the reportSFTD-Meas is set to neighborCells or pSCell within the corresponding reportConfigInterRAT for this measId, for each applicable cell for which results are available:

2> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;

2> if the ss-rsrp in the reportQuantityCellNR is set to TRUE within the corresponding reportConfigInterRAT for this measId:

3> include rsrpResult set to the RSRP of the concerned cell;

1> if there is at least one applicable transmission resource pool to report:

2> set the measResultListCBR to include the CBR measurement results in accordance with the following:

3> if the triggerType is set to event:

4> include the transmission resource pools included in the poolsTriggeredList as defined within the VarMeasReportList for this measId;

3> else:

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

3> for each transmission resource pool to be reported:

4> set the poolIdentity to the poolReportId of this transmission resource pool;

4> if adjacencyPSCCH-PSSCH is set to TRUE for this transmission resource pool:

5> set the cbr-PSSCH to the CBR measurement result on PSSCH and PSCCH of this transmission resource pool provided by lower layers;

4> else:

5> set the cbr-PSSCH to the CBR measurement result on PSSCH of this transmission resource pool provided by lower layers if available;

5> set the cbr-PSCCH to the CBR measurement result on PSCCH of this transmission resource pool provided by lower layers if available;

2> set the measResultSensing to include the sensing measurement results in accordance with the following:

3> include the applicable transmission resource pools for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;

3> for each transmission resource pool to be reported:

4> set the sensingResult to the sensing measurement results provided by the lower layers;

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> if the measured results are for CDMA2000 HRPD:

2> set the preRegistrationStatusHRPD to the UE’s CDMA2000 upper layer’s HRPD preRegistrationStatus;

1> if the measured results are for CDMA2000 1xRTT:

2> set the preRegistrationStatusHRPD to FALSE;

1> if the measured results are for WLAN:

2> set the measResultListWLAN to include the quantities within the quantityConfigWLAN for up to maxReportCells WLAN(s), determined according to the following:

3> include WLAN the UE is connected to, if any;

3> if reportAnyWLAN is set to TRUE:

4> consider WLAN with any WLAN identifiers to be applicable for measurement reporting;

3> else:

4> consider only WLANs which do not match all WLAN identifiers of any entry within wlan-MobilitySet in VarWLAN-MobilityConfig to be applicable for measurement reporting;

3> include applicable WLAN in order of decreasing WLAN RSSI, i.e. the best WLAN is included first;

2> for each included WLAN:

3> set wlan-Identifiers to include all WLAN identifiers that can be acquired for the WLAN measured;

3> set connectedWLAN to TRUE if the UE is connected to the WLAN measured;

3> if reportQuantityWLAN exists within the ReportConfigInterRAT within the VarMeasConfig for this measId:

4> if bandRequestWLAN is set to TRUE:

5> set bandWLAN to include WLAN band of the WLAN measured;

4> if carrierInfoRequestWLAN is set to TRUE:

5> set carrierInfoWLAN to include WLAN carrier information of the WLAN measured if it can be acquired;

4> if availableAdmissionCapacityRequestWLAN is set to TRUE:

5> set the measResult to include avaiableAdmissionCapacityWLAN if it can be acquired;

4> if backhaulDL-BandwidthRequestWLAN is set to TRUE:

5> set the measResult to include backhaulDL-BandwidthWLAN if it can be acquired;

4> if backhaulUL-BandwidthRequestWLAN is set to TRUE:

5> set the measResult to include backhaulUL-BandwidthWLAN if it can be acquired;

4> if channelUtilizationRequestWLAN is set to TRUE:

5> set the measResult to include channelUtilizationWLAN if it can be acquired;

4> if stationCountRequestWLAN is set to TRUE:

5> set the measResult to include stationCountWLAN if it can be acquired;

1> if the UE is configured with NE-DC:

2> submit the MeasurementReport message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in TS 38.331 [82].

1> else:

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

5.5.5.2 Determination of available NR measurement results

When configured to report measurement results of the serving and the best neighbouring cells on NR serving frequencies, the UE shall consider NR measurement results to be available as follows:

1> only SSB based results are available and only if configured to measure these for the concerned serving frequency;

1> for the serving cell:

2> include cell quantities RSRP and RSRQ while SINR is included if the UE is configured to measure this quantity on an NR frequency, possibly different from the concerned serving frequency, but only if configured by NR measConfig:

2> include beam results and beam quantities if the UE is configured to measure these on an NR frequency, possibly different from the concerned serving frequency, but only if configured by NR measConfig;

1> for a neighbouring cell:

2> include cell quantities, beam results and beam quantities if the UE is configured to measure these on an NR frequency, possibly different from the concerned serving frequency, but only if configured by NR measConfig.

1> filter available results according to the applicable field in NR quantityConfig:

5.5.5.3 Selection of NR sorting quality

When configured to report the best cells or beams, the UE shall determine the quantity that is used to order and select as follows:

1> for cells on the frequency associated with the measId that triggered the measurement reporting, if the reportTrigger is set to event, consider the quantity used in bN-ThresholdYNR to be the sorting quantity;

1> for other cases, determine the sorting quantity as follows:

2> consider the following quantities as candidate sorting quantities:

3> for cells on the frequency associated with the measId that triggered the measurement reporting (for a triggerType set to periodical):

4> the quantities defined by reportQuantityCellNR, when used for sorting cells;

4> the quantities defined by reportQuantityRS-IndexNR, when used for sorting beams;

3> for cells, serving or non-serving (i.e. within reportAddNeighMeas), on NR serving frequencies other than the one associated with the measId triggering reporting:

4> the available quantities of available NR measurement results as specified in 5.5.5.2;

2> if there is a single candidate sorting quantity;

3> consider the concerned quantity to be the sorting quantity;

2> else:

3> if RSRP is one of the candidate sorting quantities;

4> consider RSRP to be the sorting quantity;

3> else:

4> consider RSRQ to be the sorting quantity;

5.5.6 Measurement related actions

5.5.6.1 Actions upon handover and re-establishment

E-UTRAN applies the handover procedure as follows:

– when performing the handover procedure, as specified in 5.3.5.4, ensure that a measObjectId corresponding to each handover target serving frequency is configured as a result of the procedures described in this clause and in 5.3.5.4;

– when changing the band while the physical frequency remains unchanged, E-UTRAN releases the measObject corresponding to the source frequency and adds a measObject corresponding to the target frequency (i.e. it does not reconfigure the measObject);

E-UTRAN applies the re-establishment procedure as follows:

– when performing the connection re-establishment procedure, as specified in 5.3.7, ensure that a measObjectId corresponding each target serving frequency is configured as a result of the procedure described in this clause and the subsequent connection reconfiguration procedure immediately following the re-establishment procedure;

– in the first reconfiguration following the re-establishment when changing the band while the physical frequency remains unchanged, E-UTRAN releases the measObject corresponding to the source frequency and adds a measObject corresponding to the target frequency (i.e. it does not reconfigure the measObject);

The UE shall:

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

2> if the triggerType is set to periodical:

3> remove this measId from the measIdList within VarMeasConfig:

1> if the procedure was triggered due to a handover or successful re-establishment and the procedure involves a change of primary frequency, update the measId values in the measIdList within VarMeasConfig as follows:

2> if a measObjectId value corresponding to the target primary frequency exists in the measObjectList within VarMeasConfig:

3> for each measId value in the measIdList:

4> if the measId value is linked to the measObjectId value corresponding to the source primary frequency:

5> link this measId value to the measObjectId value corresponding to the target primary frequency;

4> else if the measId value is linked to the measObjectId value corresponding to the target primary frequency:

5> link this measId value to the measObjectId value corresponding to the source primary frequency;

2> else:

3> remove all measId values that are linked to the measObjectId value corresponding to the source primary frequency;

1> remove all measurement reporting entries within VarMeasReportList;

1> stop the periodical reporting timer or timer T321, whichever one is running, as well as associated information (e.g. timeToTrigger) for all measId;

1> release the measurement gaps (configured by E-UTRA RRC), if activated;

NOTE 1: If the UE requires measurement gaps to perform inter-frequency or inter-RAT measurements, the UE resumes the inter-frequency and inter-RAT measurements after the E-UTRAN has setup the measurement gaps.

NOTE 2: In this procedure, the UE may or may not release the measGapSharingConfig.

5.5.6.2 Speed dependant scaling of measurement related parameters

The UE shall adjust the value of the following parameter configured by the E-UTRAN depending on the UE speed: timeToTrigger. The UE shall apply 3 different levels, which are selected as follows:

The UE shall:

1> perform mobility state detection using the mobility state detection as specified in TS 36.304 [4] with the following modifications:

2> counting handovers instead of cell reselections;

2> applying the parameter applicable for RRC_CONNECTED as included in speedStatePars within VarMeasConfig;

1> if high mobility state is detected:

2> use the timeToTrigger value multiplied by sf-High within VarMeasConfig;

1> else if medium mobility state is detected:

2> use the timeToTrigger value multiplied by sf-Medium within VarMeasConfig;

1> else:

2> no scaling is applied;

5.5.7 Inter-frequency RSTD measurement indication

5.5.7.1 General

Figure 5.5.7.1-1: Inter-frequency RSTD measurement indication

The purpose of this procedure is to indicate to the network that the UE is going to start/stop OTDOA inter-frequency RSTD measurements which require measurement gaps as specified in TS 36.133 [16], clause 8.1.2.6. The procedure is also used to indicate to the network that the UE is going to start/stop OTDOA intra-frequency RSTD measurements which require measurement gaps. This procedure is also used to indicate to the network the measurement gap that the category M1 or M2 UE prefers to perform RSTD measurements with dense PRS configuration, as specified in TS 36.133 [16], Table 8.1.2.1-3.

NOTE: It is a network decision to configure the measurement gap.

5.5.7.2 Initiation

The UE shall:

1> if and only if upper layers indicate to start performing inter-frequency RSTD measurements and the UE requires measurement gaps for these measurements while measurement gaps are either not configured or not sufficient:

2> initiate the procedure to indicate start;

NOTE 1: The UE verifies the measurement gap situation only upon receiving the indication from upper layers. If at this point in time sufficient gaps are available, the UE does not initiate the procedure. Unless it receives a new indication from upper layers, the UE is only allowed to further repeat the procedure in the same PCell once per frequency if the provided measurement gaps are insufficient.

1> if and only if upper layers indicate to stop performing inter-frequency RSTD measurements:

2> initiate the procedure to indicate stop;

NOTE 2: The UE may initiate the procedure to indicate stop even if it did not previously initiate the procedure to indicate start.

5.5.7.3 Actions related to transmission of InterFreqRSTDMeasurementIndication message

The UE shall set the contents of InterFreqRSTDMeasurementIndication message as follows:

1> if the procedure is initiated to indicate start or stop of inter-frequency RSTD measurements:

2> set the rstd-InterFreqIndication as follows:

3> if the procedure is initiated to indicate start of inter-frequency RSTD measurements:

4> set the rstd-InterFreqInfoList according to the information received from upper layers;

4> for category M1 or M2 UE, if the procedure is initated to indicate the measurement gap that the UE prefers to perform RSTD measurements with dense PRS configuration:

5> set the measPRS-Offset-r15 according to the UE preference;

3> else if the procedure is initiated to indicate stop of inter-frequency RSTD measurements:

4> set the rstd-InterFreqIndication to the value stop;

1> else:

2> set the rstd-InterFreqIndication as follows:

3> if the procedure is initiated to indicate start of intra-frequency RSTD measurements:

4> set the carrierFreq in the rstd-InterFreqInfoList to the carrier frequency of the serving cell;

4> for category M1 or M2 UE, if the procedure is initated to indicate the measurement gap that the UE prefers to perform RSTD measurements with dense PRS configuration:

5> set the measPRS-Offset-r15 according to the UE preference;

3> else if the procedure is initiated to indicate stop of intra-frequency RSTD measurements:

4> set the rstd-InterFreqIndication to the value stop;

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