5.5 Measurements
38.3313GPPNRProtocol specificationRadio Resource Control (RRC)Release 17TS
5.5.1 Introduction
The network may configure an RRC_CONNECTED UE to perform measurements. The network may configure the UE to report them in accordance with the measurement configuration or perform conditional reconfiguration evaluation in accordance with the conditional reconfiguration. The measurement configuration is provided by means of dedicated signalling i.e. using the RRCReconfiguration or RRCResume.
The network may configure the UE to perform the following types of measurements:
– NR measurements;
– Inter-RAT measurements of E-UTRA frequencies;
– Inter-RAT measurements of UTRA-FDD frequencies;
– NR sidelink measurements of L2 U2N Relay UEs.
The network may configure the UE to report the following measurement information based on SS/PBCH block(s):
– Measurement results per SS/PBCH block;
– Measurement results per cell based on SS/PBCH block(s);
– SS/PBCH block(s) indexes.
The network may configure the UE to report the following measurement information based on CSI-RS resources:
– Measurement results per CSI-RS resource;
– Measurement results per cell based on CSI-RS resource(s);
– CSI-RS resource measurement identifiers.
The network may configure the UE to perform the following types of measurements for NR sidelink and V2X sidelink:
– CBR measurements.
The network may configure the UE to report the following CLI measurement information based on SRS resources:
– Measurement results per SRS resource;
– SRS resource(s) indexes.
The network may configure the UE to report the following CLI measurement information based on CLI-RSSI resources:
– Measurement results per CLI-RSSI resource;
– CLI-RSSI resource(s) indexes.
The network may configure the UE to report the following Rx-Tx time difference measurement information based on CSI-RS for tracking or PRS:
– UE Rx-Tx time difference measurement result.
The measurement configuration includes the following parameters:
1. Measurement objects: A list of objects on which the UE shall perform the measurements.
– For intra-frequency and inter-frequency measurements a measurement object indicates the frequency/time location and subcarrier spacing of reference signals to be measured. Associated with this measurement object, the network may configure a list of cell specific offsets, a list of ‘exclude-listed’ cells and a list of ‘allow-listed’ cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting. Allow-listed cells are the only ones applicable in event evaluation or measurement reporting.
– The measObjectId of the MO which corresponds to each serving cell is indicated by servingCellMO within the serving cell configuration.
– For inter-RAT E-UTRA measurements a measurement object is a single E-UTRA carrier frequency. Associated with this E-UTRA carrier frequency, the network can configure a list of cell specific offsets and a list of ‘exclude-listed’ cells. Exclude-listed cells are not applicable in event evaluation or measurement reporting.
– For inter-RAT UTRA-FDD measurements a measurement object is a set of cells on a single UTRA-FDD carrier frequency.
– For NR sidelink measurements of L2 U2N Relay UEs, a measurement object is a single NR sidelink frequency to be measured.
– For CBR measurement of NR sidelink communication, a measurement object is a set of transmission resource pool(s) on a single carrier frequency for NR sidelink communication.
– For CBR measurement of NR sidelink discovery, a measurement object is a set of discovery dedicated resource pool(s) or transmission resource pool(s) also used for NR sidelink discovery on a single carrier frequency for NR sidelink discovery.
– For CLI measurements a measurement object indicates the frequency/time location of SRS resources and/or CLI-RSSI resources, and subcarrier spacing of SRS resources to be measured.
2. Reporting configurations: A list of reporting configurations where there can be one or multiple reporting configurations per measurement object. Each measurement 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.
– RS type: The RS that the UE uses for beam and cell measurement results (SS/PBCH block or CSI-RS).
– Reporting format: The quantities per cell and per beam that the UE includes in the measurement report (e.g. RSRP) and other associated information such as the maximum number of cells and the maximum number beams per cell to report.
In case of conditional reconfiguration, each configuration consists of the following:
– Execution criteria: The criteria the UE uses for conditional reconfiguration execution.
– RS type: The RS that the UE uses for obtaining beam and cell measurement results (SS/PBCH block-based or CSI-RS-based), used for evaluating conditional reconfiguration execution condition.
3. Measurement identities: For measurement reporting, 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 also included in the measurement report that triggered the reporting, serving as a reference to the network. For conditional reconfiguration triggering, one measurement identity links to exactly one conditional reconfiguration trigger configuration. And up to 2 measurement identities can be linked to one conditional reconfiguration execution condition.
4. Quantity configurations: The quantity configuration defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement. For NR measurements, the network may configure up to 2 quantity configurations with a reference in the NR measurement object to the configuration that is to be used. In each configuration, different filter coefficients can be configured for different measurement quantities, for different RS types, and for measurements per cell and per beam.
5. Measurement gaps: Periods that the UE may use to perform measurements.
A UE in RRC_CONNECTED maintains a measurement object list, a reporting configuration list, and a measurement identities list according to signalling and procedures in this specification. The measurement object list possibly includes NR measurement object(s), CLI measurement object(s), inter-RAT objects, and L2 U2N Relay objects. Similarly, the reporting configuration list includes NR, inter-RAT, and L2 U2N Relay 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 NR serving cell(s) – these are the SpCell and one or more SCells.
2. Listed cells – these are cells listed within the measurement object(s).
3. Detected cells – these are cells that are not listed within the measurement object(s) but are detected by the UE on the SSB frequency(ies) and subcarrier spacing(s) indicated by the measurement object(s).
For NR measurement object(s), the UE measures and reports on the serving cell(s)/serving Relay UE (for L2 U2N Remote UE), listed cells and/or detected cells. For inter-RAT measurements object(s) of E-UTRA, the UE measures and reports on listed cells and detected cells and, for RSSI and channel occupancy measurements, the UE measures and reports on the configured resources on the indicated frequency. For inter-RAT measurements object(s) of UTRA-FDD, the UE measures and reports on listed cells. For CLI measurement object(s), the UE measures and reports on configured measurement resources (i.e. SRS resources and/or CLI-RSSI resources). For L2 U2N Relay object(s), the UE measures and reports on the serving NR cell(s), as well as the discovered L2 U2N Relay UEs.
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.
In NR-DC, the UE may receive two independent measConfig:
– a measConfig, associated with MCG, that is included in the RRCReconfiguration message received via SRB1; and
– a measConfig, associated with SCG, that is included in the RRCReconfiguration message received via SRB3, or, alternatively, included within a RRCReconfiguration message embedded in a RRCReconfiguration message received via SRB1.
In this case, the UE maintains two independent VarMeasConfig and VarMeasReportList, one associated with each measConfig, and independently performs all the procedures in clause 5.5 for each measConfig and the associated VarMeasConfig and VarMeasReportList, unless explicitly stated otherwise.
The configurations related to CBR measurements are only included in the measConfig associated with MCG.
The configurations related to Rx-Tx time difference measurement are only included in the measConfig associated with MCG.
5.5.2 Measurement configuration
5.5.2.1 General
The network applies the procedure as follows:
– to ensure that, whenever the UE has a measConfig associated with a CG, it includes a measObject for the SpCell and for each NR SCell of the CG to be measured;
– to configure at most one measurement identity across all CGs using a reporting configuration with the reportType set to reportCGI;
– to configure at most one measurement identity per the node hosting PDCP entity using a reporting configuration with the ul-DelayValueConfig;
– to configure at most one measurement identity per the node hosting PDCP entity using a reporting configuration with the ul-ExcessDelayConfig;
– to ensure that, in the measConfig associated with a CG:
– for all SSB based measurements there is at most one measurement object with the same ssbFrequency;
– an smtc1 included in any measurement object with the same ssbFrequency has the same value and that an smtc2 included in any measurement object with the same ssbFrequency has the same value and that an smtc3list included in any measurement object with the same ssbFrequency has the same value and that an smtc4list included in any measurement object with the same ssbFrequency has the same value;
– to ensure that all measurement objects configured in this specification and in TS 36.331 [10] with the same ssbFrequency have the same ssbSubcarrierSpacing;
– to ensure that, if a measurement object associated with the MCG has the same ssbFrequency as a measurement object associated with the SCG:
– for that ssbFrequency, the measurement window according to the smtc1 configured by the MCG includes the measurement window according to the smtc1 configured by the SCG, or vice-versa, with an accuracy of the maximum receive timing difference specified in TS 38.133 [14].
– if both measurement objects are used for RSSI measurements, bits in measurementSlots in both objects corresponding to the same slot are set to the same value. Also, the endSymbol is the same in both objects.
– to ensure that, if a measurement object has the same ssbFrequency as a measurement object configured in TS 36.331 [10]:
– for that ssbFrequency, the measurement window according to the smtc configured in TS 36.331 [10] includes the measurement window according to the smtc1 configured in TS 38.331, or vice-versa, with an accuracy of the maximum receive timing difference specified in TS 38.133 [14].
– if both measurement objects are used for RSSI measurements, bits in measurementSlots in both objects corresponding to the same slot are set to the same value. Also, the endSymbol is the same in both objects.
– when the UE is in NE-DC, NR-DC, or NR standalone, to configure at most one measurement identity across all CGs using a reporting configuration with the reportType set to reportSFTD;
For CSI-RS resources, the network applies the procedure as follows:
– to ensure that all CSI-RS resources configured in each measurement object have the same center frequency, (startPRB+floor(nrofPRBs/2))
– to ensure that the total number of CSI-RS resources configured in each measurement object does not exceed the maximum number specified in TS 38.214 [19].
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:
2> perform the measurement gap configuration procedure as specified in 5.5.2.9;
1> if the received measConfig includes the measGapSharingConfig:
2> perform the measurement gap sharing configuration procedure as specified in 5.5.2.11;
1> if the received measConfig includes the s-MeasureConfig:
2> if s-MeasureConfig is set to ssb-RSRP, set parameter ssb-RSRP of s-MeasureConfig within VarMeasConfig to the threshold value of the RSRP indicated by the received value of s-MeasureConfig which is derived as specified in 6.3.2;
2> else, set parameter csi-RSRP of s-MeasureConfig within VarMeasConfig to the threshold value of the RSRP indicated by the received value of s-MeasureConfig which is derived as specified in 6.3.2.
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 or timer T322, 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.3 Measurement identity addition/modification
The network 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 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;
NOTE 1: If the measId associated with reportConfig for conditional reconfiguration is modified, the conditions are considered to be not fulfilled as specified in 5.3.5.13.4.
2> if the reportType 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 useAutonomousGaps is included in the reportConfig associated with this measId:
5> start timer T321 with the timer value set to 200 ms for this measId;
4> else:
5> start timer T321 with the timer value set to 1 second for this measId;
3> if the measObject associated with this measId concerns NR:
4> if the measObject associated with this measId concerns FR1:
5> if the useAutonomousGaps is included in the reportConfig associated with this measId:
6> if the UE is a RedCap UE with 1 Rx branch
7> start timer T321 with the timer value set to 3 seconds for this measId;
6> else
7> start timer T321 with the timer value set to 2 seconds for this measId;
5> else:
6> 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> if the useAutonomousGaps is included in the reportConfig associated with this measId:
6> if the UE is a RedCap UE with 1 Rx branch
7> start timer T321 with the timer value set to 6 seconds for this measId;
6> else
7> start timer T321 with the timer value set to 5 seconds for this measId;
5> else:
6> start timer T321 with the timer value set to 16 seconds for this measId.
2> if the reportType is set to reportSFTD in the reportConfigNR associated with this measId and the drx-SFTD-NeighMeas is included:
3> if the measObject associated with this measId concerns FR1:
4> start timer T322 with the timer value set to 3 seconds for this measId;
3> if the measObject associated with this measId concerns FR2:
4> start timer T322 with the timer value set to 24 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 measObjectList 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 or timer T322, whichever 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, excludedCellsToAddModList, allowedCellsToAddModList, cellsToRemoveList, excludedCellsToRemoveList, allowedCellsToRemoveList, tx-PoolMeasToRemoveList, tx-PoolMeasToAddModList, ssb-PositionQCL-CellsToRemoveList, and ssb-PositionQCL-CellsToAddModList;
3> if the received measObject includes the cellsToRemoveList:
4> for each physCellId included in the cellsToRemoveList:
5> remove the entry with the matching physCellId from the cellsToAddModList;
3> if the received measObject includes the cellsToAddModList:
4> for each physCellId value included in the cellsToAddModList:
5> if an entry with the matching physCellId exists in the cellsToAddModList:
6> replace the entry with the value received for this physCellId;
5> else:
6> add a new entry for the received physCellId to the cellsToAddModList;
3> if the received measObject includes the excludedCellsToRemoveList:
4> for each pci-RangeIndex included in the excludedCellsToRemoveList:
5> remove the entry with the matching pci-RangeIndex from the excludedCellsToAddModList;
NOTE 1: For each pci-RangeIndex included in the excludedCellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the exclude-list of cells only if all PCI ranges containing it are removed.
3> if the received measObject includes the excludedCellsToAddModList:
4> for each pci-RangeIndex included in the excludedCellsToAddModList:
5> if an entry with the matching pci-RangeIndex is included in the excludedCellsToAddModList:
6> replace the entry with the value received for this pci-RangeIndex;
5> else:
6> add a new entry for the received pci-RangeIndex to the excludedCellsToAddModList;
3> if the received measObject includes the allowedCellsToRemoveList:
4> for each pci-RangeIndex included in the allowedCellsToRemoveList:
5> remove the entry with the matching pci-RangeIndex from the allowedCellsToAddModList;
NOTE2: For each pci-RangeIndex included in the allowedCellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the allow-list of cells only if all PCI ranges containing it are removed.
3> if the received measObject includes the allowedCellsToAddModList:
4> for each pci-RangeIndex included in the allowedCellsToAddModList:
5> if an entry with the matching pci-RangeIndex is included in the allowedCellsToAddModList:
6> replace the entry with the value received for this pci-RangeIndex;
5> else:
6> add a new entry for the received pci-RangeIndex to the allowedCellsToAddModList
3> for each measId associated with this measObjectId in the measIdList within the VarMeasConfig, if any:
4> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;
4> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId;
3> if the received measObject includes the tx-PoolMeasToRemoveList:
4> for each transmission resource pool indicated in tx-PoolMeasToRemoveList:
5> remove the entry with the matching identity of the transmission resource pool from the tx-PoolMeasToAddModList;
3> if the received measObject includes the tx-PoolMeasToAddModList:
4> for each transmission resource pool indicated in tx-PoolMeasToAddModList:
5> if an entry with the matching identity of the transmission resource pool exists in the tx-PoolMeasToAddModList:
6> replace the entry with the value received for this transmission resource pool;
5> else:
6> add a new entry for the received identity of the transmission resource pool to the tx-PoolMeasToAddModList;
3> if the received measObject includes the ssb-PositionQCL-CellsToRemoveList:
4> for each physCellId included in the ssb-PositionQCL-CellsToRemoveList:
5> remove the entry with the matching physCellId from the ssb-PositionQCL-CellsToAddModList;
3> if the received measObject includes the ssb-PositionQCL-CellsToAddModList:
4> for each physCellId included in the ssb-PositionQCL-CellsToAddModList:
5> if an entry with the matching physCellId exists in the ssb-PositionQCL-CellsToAddModList:
6> replace the entry with the value received for this physCellId;
5> else:
6> add a new entry for the received physCellId to the ssb-PositionQCL-CellsToAddModList;
2> else:
3> add a new entry for the received measObject to the measObjectList within VarMeasConfig.
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 or timer T322, 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 the VarMeasReportList, if included;
4> stop the periodical reporting timer or timer T321 or timer T322, 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 or timer T322, 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 gapFR1 is set to setup:
2> if an FR1 measurement gap configuration configured by gapFR1 is already setup, release the FR1 measurement gap configuration;
2> setup the FR1 measurement gap configuration indicated by the gapFR1 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 mod T = FLOOR(gapOffset/10);
subframe = gapOffset mod 10;
with T = MGRP/10 as defined in TS 38.133 [14];
2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences);
1> else if gapFR1 is set to release:
2> release the FR1 measurement gap configuration configured by gapFR1;
1> if gapFR2 is set to setup:
2> if an FR2 measurement gap configuration configured by gapFR2 is already setup, release the FR2 measurement gap configuration;
2> setup the FR2 measurement gap configuration indicated by the gapFR2 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 mod T = FLOOR(gapOffset/10);
subframe = gapOffset mod 10;
with T = MGRP/10 as defined in TS 38.133 [14];
2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences);
1> else if gapFR2 is set to release:
2> release the FR2 measurement gap configuration configured by gapFR2;
1> if gapUE is set to setup:
2> if a per UE measurement gap configuration configured by gapUE is already setup, release the per UE measurement gap configuration;
2> setup the per UE measurement gap configuration indicated by the gapUE 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 mod T = FLOOR(gapOffset/10);
subframe = gapOffset mod 10;
with T = MGRP/10 as defined in TS 38.133 [14];
2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences);
1> else if gapUE is set to release:
2> release the per UE measurement gap configuration configured by gapUE.
1> for each measGapId included in the received gapToReleaseList:
2> release the measurement gap configuration associated with the measGapId;
1> for each measPosPreConfigGapId included in the received posMeasGapPreConfigToReleaseList:
2> release the measurement gap configuration associated with the measPosPreConfigGapId;
1> for each GapConfig received in gapToAddModList:
2> setup measurement gap configuration indicated by the GapConfig 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 mod T = FLOOR(gapOffset/10);
subframe = gapOffset mod 10;
with T = MGRP/10 as defined in TS 38.133 [14];
2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences);
2> apply the measurement gap as per UE measurement gap, FR1 measurement gap, or FR2 measurement gap according to the gapType indicated by the GapConfig;
2> associate the measurement gap with the measGapId indicated by the GapConfig;
2> if gapSharing in the GapConfig is present:
3> setup the gap sharing configuration for the measurement gap in accordance with the received gapSharing as defined in TS 38.133 [14];
2> else:
3> release the gap sharing configuration (if configured) for the measurement gap;
1> for each PosGapConfig received in PosMeasGapPreConfigToAddModList:
2> if a measurement gap configuration associated with the measPosPreConfigGapId indicated by the PosGapConfig is already setup:
3> release the measurement gap configuration;
2> setup measurement gap configuration indicated by the PosGapConfig 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 mod T = FLOOR(gapOffset/10);
subframe = gapOffset mod 10;
with T = MGRP/10 as defined in TS 38.133 [14];
2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences);
2> configure the measurement gap as indicated by gapType;
1> for each FR1, FR2, and per UE measurement gap that is setup:
2> if the measurement gap is configured by GapConfig and preConfigInd-r17 in the corresponding GapConfig is present:
3> determine whether the measurement gap is activated or not according to TS 38.133 [14];
2> else if the measurement gap is configured by PosGapConfig:
3> consider the measurement gap to be deactivated;
2> else:
3> consider the measurement gap to be activated.
NOTE 1: For FR2 gap configuration with synchronous CA, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the refServCellIndicator is used in the gap calculation. Otherwise, the SFN and subframe of a serving cell on FR2 frequency is used in the gap calculation
NOTE 2: For FR1 gap or per UE gap configuration, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the refServCellIndicator in is used in the gap calculation. Otherwise, the SFN and subframe of the PCell is used in the gap calculation.
NOTE 3: For FR2 gap configuration with asynchronous CA, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the refServCellIndicator and refFR2ServCellAsyncCA is used in the gap calculation. Otherwise, the SFN and subframe of a serving cell on FR2 frequency indicated by the refFR2ServCellAsyncCA is used in the gap calculation
5.5.2.10 Reference signal measurement timing configuration
The UE shall setup the first SS/PBCH block measurement timing configuration (SMTC) in accordance with the received periodicityAndOffset parameter (providing Periodicity and Offset value for the following condition) in the smtc1 configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell 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).
If smtc2 is present, for cells indicated in the pci-List parameter in smtc2 in the same MeasObjectNR, the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received periodicity parameter in the smtc2 configuration and use the Offset (derived from parameter periodicityAndOffset) and duration parameter from the smtc1 configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition.
If smtc2-LP is present, for cells indicated in the pci-List parameter in smtc2-LP in the same frequency (for intra frequency cell reselection) or different frequency (for inter frequency cell reselection), the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received periodicity parameter in the smtc2-LP configuration and use the Offset (derived from parameter periodicityAndOffset) and duration parameter from the smtc configuration for that frequency. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell or serving cell (for cell reselection) meeting the above condition.
If smtc3list is present, for cells indicated in the pci-List parameter in each SSB-MTC3 element of the list in the same MeasObjectNR, the IAB-MT shall setup an additional SS block measurement timing configuration in accordance with the received periodicityAndOffset parameter (using same condition as smtc1 to identify the SFN and the subframe for SMTC occasion) in each SSB-MTC3 configuration and use the duration and ssb-ToMeasure parameters from each SSB-MTC3 configuration.
If smtc4list is present, for cells indicated in the pci-List parameter in each SSB-MTC4 element of the list in the same MeasObjectNR, the UE shall setup an additional SS/PBCH block measurement timing configuration (SMTC) in accordance with the received Offset parameter in the smtc4 configuration and use the periodicity (derived from parameter periodicityAndOffset) and duration parameter from the smtc1 configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition.
On the indicated ssbFrequency, the UE shall not consider SS/PBCH block transmission in subframes outside the SMTC occasion for RRM measurements based on SS/PBCH blocks and for RRM measurements based on CSI-RS except for SFTD measurement (see TS 38.133 [14], clause 9.3.8).
5.5.2.10a RSSI measurement timing configuration
The UE shall setup the RSSI measurement timing configuration (RMTC) in accordance with the received rmtc-Periodicity and, if configured, with rmtc-SubframeOffset i.e. the first symbol of each RMTC occasion occurs at first symbol of an SFN and subframe of the NR SpCell meeting the following condition:
SFN mod T = FLOOR(rmtc-SubframeOffset/10);
subframe = rmtc-SubframeOffset mod 10;
with T = rmtc-Periodicity/10;
On the frequency configured by rmtc-Frequency, the UE shall not consider RSSI measurements outside the configured RMTC occasion which lasts for measDurationSymbols for RSSI and channel occupancy measurements.
The UE derives the RSSI measurement duration from a combination of measDurationSymbols and ref-SCS-CP. At least for RSSI measurement confined within the active DL BWP, the UE performs RSSI measurement using the numerology of the active DL BWP during the derived measurement duration. Otherwise, the numerology used by the UE for measurements is up to UE implementation. If configured, the UE performs RSSI measurements on a bandwidth in accordance with the received rmtc-Bandwidth.
5.5.2.11 Measurement gap sharing configuration
The UE shall:
1> if gapSharingFR1 is set to setup:
2> if an FR1 measurement gap sharing configuration configured by gapSharingFR1 is already setup:
3> release the FR1 measurement gap sharing configuration configured by gapSharingFR1;
2> setup the FR1 measurement gap sharing configuration indicated by the measGapSharingConfig in accordance with the received gapSharingFR1 as defined in TS 38.133 [14];
1> else if gapSharingFR1 is set to release:
2> release the FR1 measurement gap sharing configuration configured by gapSharingFR1;
1> if gapSharingFR2 is set to setup:
2> if an FR2 measurement gap sharing configuration configured by gapSharingFR2 is already setup:
3> release the FR2 measurement gap sharing configuration configured by gapSharingFR2;
2> setup the FR2 measurement gap sharing configuration indicated by the measGapSharingConfig in accordance with the received gapSharingFR2 as defined in TS 38.133 [14];
1> else if gapSharingFR2 is set to release:
2> release the FR2 measurement gap sharing configuration configured by gapSharingFR2.
1> if gapSharingUE is set to setup:
2> if a per UE measurement gap sharing configuration configured by gapSharingUE is already setup:
3> release the per UE measurement gap sharing configuration configured by gapSharingUE;
2> setup the per UE measurement gap sharing configuration indicated by the measGapSharingConfig in accordance with the received gapSharingUE as defined in TS 38.133 [14];
1> else if gapSharingUE is set to release:
2> release the per UE measurement gap sharing configuration configured by gapSharingUE.
5.5.3 Performing measurements
5.5.3.1 General
An RRC_CONNECTED UE shall derive cell measurement results by measuring one or multiple beams associated per cell as configured by the network, as described in 5.5.3.3. For all cell measurement results, except for RSSI, and CLI measurement results in RRC_CONNECTED, the UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for evaluation of reporting criteria, measurement reporting or the criteria to trigger conditional reconfiguration execution. For cell measurements, the network can configure RSRP, RSRQ, SINR, RSCP or EcN0 as trigger quantity. For CLI measurements, the network can configure SRS-RSRP or CLI-RSSI as trigger quantity. For cell and beam measurements, reporting quantities can be any combination of quantities (i.e. only RSRP; only RSRQ; only SINR; RSRP and RSRQ; RSRP and SINR; RSRQ and SINR; RSRP, RSRQ and SINR; only RSCP; only EcN0; RSCP and EcN0), irrespective of the trigger quantity, and for CLI measurements, reporting quantities can be either SRS-RSRP or CLI-RSSI. For conditional reconfiguration execution, the network can configure up to 2 quantities, both using same RS type. The UE does not apply the layer 3 filtering as specified in 5.5.3.2 to derive the CBR measurements. The UE does not apply the layer 3 filtering as specified in 5.5.3.2 to derive the Rx-Tx time difference measurements.
The network may also configure the UE to report measurement information per beam (which can either be measurement results per beam with respective beam identifier(s) or only beam identifier(s)), derived as described in 5.5.3.3a. If beam measurement information is configured to be included in measurement reports, the UE applies the layer 3 beam filtering as specified in 5.5.3.2. On the other hand, the exact L1 filtering of beam measurements used to derive cell measurement results is implementation dependent.
The UE shall:
1> whenever the UE has a measConfig, perform RSRP and RSRQ measurements for each serving cell for which servingCellMO is configured as follows:
2> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains an rsType set to ssb and ssb-ConfigMobility is configured in the measObject indicated by the servingCellMO:
3> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains a reportQuantityRS-Indexes and maxNrofRS-IndexesToReport and contains an rsType set to ssb:
4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on SS/PBCH block, as described in 5.5.3.3a;
3> derive serving cell measurement results based on SS/PBCH block, as described in 5.5.3.3;
2> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains an rsType set to csi-rs and CSI-RS-ResourceConfigMobility is configured in the measObject indicated by the servingCellMO:
3> if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains a reportQuantityRS-Indexes and maxNrofRS-IndexesToReport and contains an rsType set to csi-rs:
4> derive layer 3 filtered RSRP and RSRQ per beam for the serving cell based on CSI-RS, as described in 5.5.3.3a;
3> derive serving cell measurement results based on CSI-RS, as described in 5.5.3.3;
1> for each serving cell for which servingCellMO is configured, if the reportConfig associated with at least one measId included in the measIdList within VarMeasConfig contains SINR as trigger quantity and/or reporting quantity:
2> if the reportConfig contains rsType set to ssb and ssb-ConfigMobility is configured in the servingCellMO:
3> if the reportConfigcontains a reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:
4> derive layer 3 filtered SINR per beam for the serving cell based on SS/PBCH block, as described in 5.5.3.3a;
3> derive serving cell SINR based on SS/PBCH block, as described in 5.5.3.3;
2> if the reportConfig contains rsType set to csi-rs and CSI-RS-ResourceConfigMobility is configured in the servingCellMO:
3> if the reportConfigcontains a reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:
4> derive layer 3 filtered SINR per beam for the serving cell based on CSI-RS, as described in 5.5.3.3a;
3> derive serving cell SINR based on CSI-RS, as described in 5.5.3.3;
1> for each measId included in the measIdList within VarMeasConfig:
2> if the reportType for the associated reportConfig is set to reportCGI and timer T321 is running:
3> if useAutonomousGaps is configured for the associated reportConfig:
4> perform the corresponding measurements on the frequency and RAT indicated in the associated measObject using autonomous gaps as necessary;
3> else:
4> perform the corresponding measurements on the frequency and RAT indicated in the associated measObject using available idle periods;
3> if the cell indicated by reportCGI field for the associated measObject is an NR cell and that indicated cell is broadcasting SIB1 (see TS 38.213 [13], clause 13):
4> try to acquire SIB1 in the concerned cell;
3> if the cell indicated by reportCGI field is an E-UTRA cell:
4> try to acquire SystemInformationBlockType1 in the concerned cell;
2> if the ul-DelayValueConfig is configured for the associated reportConfig:
3> ignore the measObject;
3> for each of the configured DRBs, configure the PDCP layer to perform corresponding average UL PDCP packet delay measurement per DRB;
2> if the ul-ExcessDelayConfig is configured for the associated reportConfig:
3> ignore the measObject;
3> for each of the configured DRBs, configure the PDCP layer to perform corresponding UL PDCP Excess Packet Delay delay measurement according to the configured threshold per DRB;
2> if the reportType for the associated reportConfig is periodical, eventTriggered; or
2> if the reportType for the associated reportConfig is condTriggerConfig and the measId is indicated in the condExecutionCond or in the condExecutionCondSCG associated to a condReconfigId in VarConditionalReconfig:
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-MeasureConfig is not configured, or
4> if s-MeasureConfig is set to ssb-RSRP and the NR SpCell RSRP based on SS/PBCH block, after layer 3 filtering, is lower than ssb-RSRP, or
4> if s-MeasureConfig is set to csi-RSRP and the NR SpCell RSRP based on CSI-RS, after layer 3 filtering, is lower than csi-RSRP:
5> if the measObject is associated to NR and the rsType is set to csi-rs:
6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:
7> derive layer 3 filtered beam measurements only based on CSI-RS for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;
6> derive cell measurement results based on CSI-RS for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3;
5> if the measObject is associated to NR and the rsType is set to ssb:
6> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are configured:
7> derive layer 3 beam measurements only based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in 5.5.3.3a;
6> derive cell measurement results based on SS/PBCH block for the trigger quantity and each measurement quantity indicated in reportQuantityCell using parameters from the associated measObject, as described in 5.5.3.3;
5> if the measObject is associated to E-UTRA:
6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject, as described in 5.5.3.2;
5> if the measObject is associated to UTRA-FDD:
6> perform the corresponding measurements associated to neighbouring cells on the frequencies indicated in the concerned measObject, as described in 5.5.3.2;
5> if the measObject is associated to L2 U2N Relay UE:
6> perform the corresponding measurements associated to candidate Relay UEs on the frequencies indicated in the concerned measObject, as described in 5.5.3.4;
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> if the reportType for the associated reportConfig is set to reportSFTD and the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than one:
3> if the reportSFTD-Meas is set to true:
4> if the measObject is associated to E-UTRA:
5> perform SFTD measurements between the PCell and the E-UTRA PSCell;
5> if the reportRSRP is set to true;
6> perform RSRP measurements for the E-UTRA PSCell;
4> else if the measObject is associated to NR:
5> perform SFTD measurements between the PCell and the NR PSCell;
5> if the reportRSRP is set to true;
6> perform RSRP measurements for the NR PSCell based on SSB;
3> else if the reportSFTD-NeighMeas is included:
4> if the measObject is associated to NR:
5> if the drx-SFTD-NeighMeas is included:
6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated measObject using available idle periods;
5> else:
6> perform SFTD measurements between the PCell and the NR neighbouring cell(s) detected based on parameters in the associated measObject;
5> if the reportRSRP is set to true:
6> perform RSRP measurements based on SSB for the NR neighbouring cell(s) detected based on parameters in the associated measObject;
2> if the reportType for the associated reportConfig is cli-Periodical or cli-EventTriggered:
3> perform the corresponding measurements associated to CLI measurement resources indicated in the concerned measObjectCLI;
2> perform the evaluation of reporting criteria as specified in 5.5.4, except if reportConfig is condTriggerConfig.
NOTE 1: The evaluation of conditional reconfiguration execution criteria is specified in 5.3.5.13.
The UE capable of Rx-Tx time difference measurement when configured with measObjectRxTxDiff shall:
1> perform the corresponding Rx-Tx time difference measurements associated with downlink reference signals indicated in the concerned measObjectRxTxDiff.
The UE capable of CBR measurement when configured to transmit NR sidelink communication/discovery shall:
1> If the frequency used for NR sidelink communication/discovery is included in sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12:
2> if the UE is in RRC_IDLE or in RRC_INACTIVE:
3> if configured with NR sidelink communication and the cell chosen for NR sidelink communication provides SIB12 which includes sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency; or
3> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides SIB12 which includes sl-TxPoolSelectedNormal or sl-TxPoolExceptional but does not include sl-DiscTxPoolSelected for the concerned frequency:
4> perform CBR measurement on pool(s) in sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency in SIB12;
3> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides SIB12 which includes sl-DiscTxPoolSelected for the concerned frequency:
4> perform CBR measurement on pools in sl-DiscTxPoolSelected and sl-TxPoolExceptional for the concerned frequency in SIB12;
2> if the UE is in RRC_CONNECTED:
3> if tx-PoolMeasToAddModList is included in VarMeasConfig:
4> perform CBR measurements on each transmission resource pool indicated in the tx-PoolMeasToAddModList;
3> if sl-DiscTxPoolSelected, sl-TxPoolSelectedNormal, sl-TxPoolScheduling or sl-TxPoolExceptional is included in sl-ConfigDedicatedNR for the concerned frequency within RRCReconfiguration:
4> perform CBR measurement on pool(s) in sl-DiscTxPoolSelected, sl-TxPoolSelectedNormal, sl-TxPoolScheduling and sl-TxPoolExceptional if included in sl-ConfigDedicatedNR for the concerned frequency within RRCReconfiguration;
3> else:
4> if configured with NR sidelink communication and the cell chosen for NR sidelink communication provides SIB12 which includes sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency; or
4> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides SIB12 which includes sl-TxPoolSelectedNormal or sl-TxPoolExceptional but does not provide sl-DiscTxPoolSelected for the concerned frequency:
5> perform CBR measurement on pool(s) in sl-TxPoolSelectedNormal or sl-TxPoolExceptional for the concerned frequency in SIB12;
4> if configured with NR sidelink discovery and the cell chosen for NR sidelink discovery provides SIB12 which includes sl-DiscTxPoolSelected for the concerned frequency:
5> perform CBR measurement on pools in sl-DiscTxPoolSelected and sl-TxPoolExceptional for the concerned frequency in SIB12;
1> else:
2> if configured with NR sidelink communication and sl-TxPoolSelectedNormal or sl-TxPoolExceptional is included in SidelinkPreconfigNR for the concerned frequency; or
2> if configured with NR sidelink discovery and sl-TxPoolSelectedNormal or sl-TxPoolExceptional is included in SidelinkPreconfigNR but sl-DiscTxPoolSelected is not included in SidelinkPreconfigNR for the concerned frequency:
3> perform CBR measurement on pool(s) in sl-TxPoolSelectedNormal or sl-TxPoolExceptional in SidelinkPreconfigNR for the concerned frequency.
2> if configured with NR sidelink discovery and sl-DiscTxPoolSelected is included in SidelinkPreconfigNR for the concerned frequency:
3> perform CBR measurement on pools in sl-DiscTxPoolSelected and sl-TxPoolExceptional if included in SidelinkPreconfigNR;
NOTE 2: In case the configurations for NR sidelink communication and CBR measurement are acquired via the E-UTRA, configurations for NR sidelink communication in SIB12, sl-ConfigDedicatedNR within RRCReconfiguration used in this clause are provided by the configurations in SystemInformationBlockType28, sl-ConfigDedicatedForNR within RRCConnectionReconfiguration as specified in TS 36.331[10], respectively.
NOTE 3: If a UE that is configured by upper layers to transmit V2X sidelink communication is configured by NR with transmission resource pool(s) and the measurement objects concerning V2X sidelink communication (i.e. by sl-ConfigDedicatedEUTRA-Info), it shall perform CBR measurement as specified in clause 5.5.3 of TS 36.331 [10], based on the transmission resource pool(s) and the measurement object(s) concerning V2X sidelink communication configured by NR.
NOTE 4: For V2X sidelink communication, each of the CBR measurement results is associated with a resource pool, as indicated by the poolReportId (see TS 36.331 [10]), that refers to a pool as included in sl-ConfigDedicatedEUTRA-Info or SIB13.
5.5.3.2 Layer 3 filtering
The UE shall:
1> for each cell measurement quantity, each beam measurement quantity, each sidelink measurement quantity as needed in clause 5.8.10, for each CLI measurement quantity that the UE performs measurements according to 5.5.3.1, and for each candidate L2 U2N Relay UE measurement quantity according to 5.5.3.4:
2> filter the measured result, before using for evaluation of reporting criteria or for measurement reporting, by the following formula:
Fn = (1 – a)*Fn-1 + a*Mn
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 for MeasObjectNR, a = 1/2(ki/4), where ki is the filterCoefficient for the corresponding measurement quantity of the i:th QuantityConfigNR in quantityConfigNR-List, and i is indicated by quantityConfigIndex in MeasObjectNR; for other measurements, a = 1/2(k/4), where k is the filterCoefficient for the corresponding measurement quantity received by the quantityConfig; for UTRA-FDD, a = 1/2(k/4), where k is the filterCoefficient for the corresponding measurement quantity received by quantityConfigUTRA-FDD in the QuantityConfig;
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 X ms; The value of X is equivalent to one intra-frequency L1 measurement period as defined in TS 38.133 [14] assuming non-DRX operation, and depends on frequency range.
NOTE 1: If k is set to 0, no layer 3 filtering is applicable.
NOTE 2: 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 3: The filter input rate is implementation dependent, to fulfil the performance requirements set in TS 38.133 [14]. For further details about the physical layer measurements, see TS 38.133 [14].
NOTE 4: For CLI-RSSI measurement, it is up to UE implementation whether to reset filtering upon BWP switch.
5.5.3.3 Derivation of cell measurement results
The network may configure the UE in RRC_CONNECTED to derive RSRP, RSRQ and SINR measurement results per cell associated to NR measurement objects based on parameters configured in the measObject (e.g. maximum number of beams to be averaged and beam consolidation thresholds) and in the reportConfig (rsType to be measured, SS/PBCH block or CSI-RS).
The network may configure the UE in RRC_IDLE or in RRC_INACTIVE to derive RSRP and RSRQ measurement results per cell associated to NR carriers based on parameters configured in measIdleCarrierListNR within VarMeasIdleConfig for measurements performed according to 5.7.8.2a.
The UE shall:
1> for each cell measurement quantity to be derived based on SS/PBCH block:
2> if nrofSS-BlocksToAverage is not configured in the associated measObject in RRC_CONNECTED or in the associated entry in measIdleCarrierListNR within VarMeasIdleConfig in RRC_IDLE/RRC_INACTIVE; or
2> if absThreshSS-BlocksConsolidation is not configured in the associated measObject in RRC_CONNECTED or in the associated entry in measIdleCarrierListNR within VarMeasIdleConfig in RRC_IDLE/RRC_INACTIVE; or
2> if the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation:
3> derive each cell measurement quantity based on SS/PBCH block as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [9];
2> else:
3> derive each cell measurement quantity based on SS/PBCH block as the linear power scale average of the highest beam measurement quantity values above absThreshSS-BlocksConsolidation where the total number of averaged beams shall not exceed nrofSS-BlocksToAverage, and where each beam measurement quantity is described in TS 38.215 [9];
2> if in RRC_CONNECTED, apply layer 3 cell filtering as described in 5.5.3.2;
1> for each cell measurement quantity to be derived based on CSI-RS:
2> consider a CSI-RS resource to be applicable for deriving cell measurements when the concerned CSI-RS resource is included in the csi-rs-CellMobility including the physCellId of the cell in theCSI-RS-ResourceConfigMobility in the associated measObject;
2> if nrofCSI-RS-ResourcesToAverage in the associated measObject is not configured; or
2> if absThreshCSI-RS-Consolidation in the associated measObject is not configured; or
2> if the highest beam measurement quantity value is below or equal to absThreshCSI-RS-Consolidation:
3> derive each cell measurement quantity based on applicable CSI-RS resources for the cell as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [9];
2> else:
3> derive each cell measurement quantity based on CSI-RS as the linear power scale average of the highest beam measurement quantity values above absThreshCSI-RS-Consolidation where the total number of averaged beams shall not exceed nrofCSI-RS-ResourcesToAverage;
2> apply layer 3 cell filtering as described in 5.5.3.2.
5.5.3.3a Derivation of layer 3 beam filtered measurement
The UE shall:
1> for each layer 3 beam filtered measurement quantity to be derived based on SS/PBCH block;
2> derive each configured beam measurement quantity based on SS/PBCH block as described in TS 38.215[9], and apply layer 3 beam filtering as described in 5.5.3.2;
1> for each layer 3 beam filtered measurement quantity to be derived based on CSI-RS;
2> derive each configured beam measurement quantity based on CSI-RS as described in TS 38.215 [9], and apply layer 3 beam filtering as described in 5.5.3.2.
5.5.3.4 Derivation of L2 U2N Relay UE measurement results
A UE may be configured by network to derive NR sidelink measurement results of serving L2 U2N Relay UE or candidate L2 U2N Relay UEs associated to the measurement objects configured in the measObjectRelay.
The UE shall:
1> for each L2 U2N Relay UE measurement quantity to be derived:
2> derive the corresponding measurement quantity based on DMRS as described in TS 38.215 [9] of the L2 U2N Relay UE associated to the NR sidelink frequency indicated in the concerned measObjectRelay;
2> apply layer 3 filtering as described in 5.5.3.2;
5.5.4 Measurement report triggering
5.5.4.1 General
If AS 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 reportType set to eventTriggered or periodical:
3> if the corresponding measObject concerns NR:
4> if the corresponding reportConfig includes measRSSI-ReportConfig:
5> consider the resource indicated by the rmtc-Config on the associated frequency to be applicable;
4> if the eventA1 or eventA2 is configured in the corresponding reportConfig:
5> consider only the serving cell to be applicable;
4> if the eventA3 or eventA5 is configured in the corresponding reportConfig:
5> if a serving cell is associated with a measObjectNR and neighbours are associated with another measObjectNR, consider any serving cell associated with the other measObjectNR to be a neighbouring cell as well;
4> if the eventX2 is configured in the corresponding reportConfig:
5> consider only the serving L2 U2N Relay UE to be applicable;
4> if corresponding reportConfig includes reportType set to periodical; or
4> for measurement events other than eventA1, eventA2, eventD1 or eventX2:
5> if useAllowedCellList is set to true:
6> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is included in the allowedCellsToAddModList defined within the VarMeasConfig for this measId;
5> else:
6> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is not included in the excludedCellsToAddModList defined within the VarMeasConfig for this measId;
3> else if the corresponding measObject concerns E-UTRA:
4> if eventB1 or eventB2 is configured in the corresponding reportConfig:
5> consider a serving cell, if any, on the associated E-UTRA frequency as neighbour cell;
4> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the excludedCellsToAddModListEUTRAN defined within the VarMeasConfig for this measId;
3> else if the corresponding measObject concerns UTRA-FDD:
4> if eventB1-UTRA-FDD or eventB2-UTRA-FDD is configured in the corresponding reportConfig; or
4> if corresponding reportConfig includes reportType set to periodical:
5> 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;
3> else if the corresponding measObject concerns L2 U2N Relay UE:
4> if eventY1-Relay or eventY2-Relay is configured in the corresponding reportConfig; or
4> if corresponding reportConfig includes reportType set to periodical:
5> consider any L2 U2N Relay UE fulfilling upper layer criteria detected on the associated frequency to be applicable for this measId;
2> else if the corresponding reportConfig includes a reportType set to reportCGI:
3> consider the cell detected on the associated measObject which has a physical cell identity matching the value of the cellForWhichToReportCGI included in the corresponding reportConfig within the VarMeasConfig to be applicable;
2> else if the corresponding reportConfig includes a reportType set to reportSFTD:
3> if the corresponding measObject concerns NR:
4> if the reportSFTD-Meas is set to true:
5> consider the NR PSCell to be applicable;
4> else if the reportSFTD-NeighMeas is included:
5> if cellsForWhichToReportSFTD is configured in the corresponding reportConfig:
6> consider any NR neighbouring cell detected on the associated measObjectNR which has a physical cell identity that is included in the cellsForWhichToReportSFTD to be applicable;
5> else:
6> consider up to 3 strongest NR neighbouring cells detected based on parameters in the associated measObjectNR to be applicable when the concerned cells are not included in the excludedCellsToAddModList defined within the VarMeasConfig for this measId;
3> else if the corresponding measObject concerns E-UTRA:
4> if the reportSFTD-Meas is set to true:
5> consider the E-UTRA PSCell to be applicable;
2> else if the corresponding reportConfig includes a reportType set to cli-Periodical or cli-EventTriggered:
3> consider all CLI measurement resources included in the corresponding measObject to be applicable;
2> else if the corresponding reportConfig includes a reportType set to rxTxPeriodical:
3> consider all Rx-Tx time difference measurement resources included in the corresponding measObject to be applicable;
2> if the corresponding reportConfig concerns the reporting for NR sidelink communication/discovery (i.e. reportConfigNR-SL):
3> consider the transmission resource pools indicated by the tx-PoolMeasToAddModList defined within the VarMeasConfig for this measId to be applicable;
2> if the reportType is set to eventTriggered 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 useT312 is set to true in reportConfig for this event:
4> if T310 for the corresponding SpCell is running; and
4> if T312 is not running for corresponding SpCell:
5> start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;
3> initiate the measurement reporting procedure, as specified in 5.5.5;
2> else if the reportType is set to eventTriggered 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 useT312 is set to true in reportConfig for this event:
4> if T310 for the corresponding SpCell is running; and
4> if T312 is not running for corresponding SpCell:
5> start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR;
3> initiate the measurement reporting procedure, as specified in 5.5.5;
2> if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event:
3> remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId;
3> if reportOnLeave is set to true for the corresponding reporting configuration:
4> initiate the measurement reporting procedure, as specified in 5.5.5;
3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:
4> remove the measurement reporting entry within the VarMeasReportList for this measId;
4> stop the periodical reporting timer for this measId, if running;
2> if the reportType is set to eventTriggered 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 L2 U2N Relay UEs 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 L2 U2N Relay UE 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 L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId;
3> initiate the measurement reporting procedure, as specified in 5.5.5;
2> else if the reportType is set to eventTriggered 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 L2 U2N Relay UEs not included in the relaysTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent L2 U2N Relay UE triggers the event):
3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;
3> include the concerned L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId;
3> initiate the measurement reporting procedure, as specified in 5.5.5;
2> else if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the L2 U2N Relay UEs included in the relaysTriggeredList 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 L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId;
3> if reportOnLeave is set to true for the corresponding reporting configuration:
4> initiate the measurement reporting procedure, as specified in 5.5.5;
3> if the relaysTriggeredList 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> else if the reportType is set to eventTriggered 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> else if the reportType is set to eventTriggered 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 reportType is set to eventTriggered 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) in 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> else if the reportType is set to eventTriggered and if the eventId is set to eventD1 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> else if the reportType is set to eventTriggered and if the eventId is set to eventD1 and if the leaving condition applicable for this event is fulfilled for the associated VarMeasReport within the VarMeasReportList for this measId during timeToTrigger defined within the VarMeasConfig for this event:
3> if reportOnLeave is set to true for the corresponding reporting configuration:
4> initiate the measurement reporting procedure, as specified in 5.5.5;
3> remove the measurement reporting entry within the VarMeasReportList for this measId;
3> stop the periodical reporting timer for this measId, if running;
NOTE 1: Void.
2> if reportType is set to periodical 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 corresponding reportConfig includes measRSSI-ReportConfig:
4> 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;
3> else if the corresponding reportConfig includes the ul-DelayValueConfig:
4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity;
3> else if the corresponding reportConfig includes the ul-ExcessDelayConfig:
4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity(ies) according to the configured threshold per DRB identity(ies);
3> else if the reportAmount exceeds 1:
4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell or for the serving L2 U2N Relay UE (if the UE is a L2 U2N Remote UE);
3> else (i.e. the reportAmount is equal to 1):
4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells, or for the NR SpCell and for the strongest L2 U2N Relay UEs among the applicable L2 U2N Relay UEs; or initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the serving L2 U2N Relay UE and for the strongest cell among the applicable cells (if the UE is a L2 U2N Remote UE);
2> if, in case the corresponding reportConfig concerns the reporting for NR sidelink communication/discovery, reportType is set to periodical 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 after the quantity to be reported becomes available for the NR SpCell and CBR measurement results become available;
2> if the reportType is set to cli-EventTriggered 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 CLI measurement resources 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 CLI measurement 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 CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId;
3> initiate the measurement reporting procedure, as specified in 5.5.5;
2> else if the reportType is set to cli-EventTriggered 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 CLI measurement resources not included in the cli-TriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent CLI measurement resource triggers the event):
3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;
3> include the concerned CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId;
3> initiate the measurement reporting procedure, as specified in 5.5.5;
2> if the reportType is set to cli-EventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the CLI measurement resources included in the cli-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 CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId;
3> if reportOnLeave is set to true for the corresponding reporting configuration:
4> initiate the measurement reporting procedure, as specified in 5.5.5;
3> if the cli-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 reportType is set to cli-Periodical 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 after the quantity to be reported becomes available for at least one CLI measurement resource;
2> if reportType is set to rxTxPeriodical 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;
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 corresponding reportConfig includes a reportType is set to reportSFTD:
3> if the corresponding measObject concerns NR:
4> if the drx-SFTD-NeighMeas is included:
5> if the quantity to be reported becomes available for each requested pair of PCell and NR cell:
6> stop timer T322;
6> initiate the measurement reporting procedure, as specified in 5.5.5;
4> else
5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for each requested pair of PCell and NR cell or the maximal measurement reporting delay as specified in TS 38.133 [14];
3> else if the corresponding measObject concerns E-UTRA:
4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the pair of PCell and E-UTRA PSCell or the maximal measurement reporting delay as specified in TS 38.133 [14];
2> if reportType is set to reportCGI:
3> if the UE acquired the SIB1 or SystemInformationBlockType1 for the requested cell; or
3> if the UE detects that the requested NR cell is not transmitting SIB1 (see TS 38.213 [13], clause 13):
4> stop timer T321;
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> initiate the measurement reporting procedure, as specified in 5.5.5;
2> upon the expiry of 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.
2> upon the expiry of T322 for this measId:
3> initiate the measurement reporting procedure, as specified in 5.5.5.
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 NR serving cell corresponding to the associated measObjectNR associated with this event.
Inequality A1-1 (Entering condition)
Ms – Hys > Thresh
Inequality A1-2 (Leaving condition)
Ms + Hys < Thresh
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 reportConfigNR for this event).
Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigNR 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 serving cell indicated by the measObjectNR associated to this event.
Inequality A2-1 (Entering condition)
Ms + Hys < Thresh
Inequality A2-2 (Leaving condition)
Ms – Hys > Thresh
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 reportConfigNR for this event).
Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within reportConfigNR 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 SpCell)
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> use the SpCell for Mp, Ofp and Ocp.
NOTE 1: The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR.
Inequality A3-1 (Entering condition)
Mn + Ofn + Ocn – Hys > Mp + Ofp + Ocp + Off
Inequality A3-2 (Leaving condition)
Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off
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 measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR 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 SpCell, not taking into account any offsets.
Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell).
Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).
Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR 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.
NOTE 2: The definition of Event A3 also applies to CondEvent A3.
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)
Mn + Ofn + Ocn – Hys > Thresh
Inequality A4-2 (Leaving condition)
Mn + Ofn + Ocn + Hys < Thresh
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 measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).
Ocn is the measurement object specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to 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 reportConfigNR for this event).
Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigNR 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.
NOTE: The definition of Event A4 also applies to CondEvent A4.
5.5.4.6 Event A5 (SpCell 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> use the SpCell for Mp.
NOTE 1: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell.
Inequality A5-1 (Entering condition 1)
Mp + Hys < Thresh1
Inequality A5-2 (Entering condition 2)
Mn + Ofn + Ocn – Hys > Thresh2
Inequality A5-3 (Leaving condition 1)
Mp – Hys > Thresh1
Inequality A5-4 (Leaving condition 2)
Mn + Ofn + Ocn + Hys < Thresh2
The variables in the formula are defined as follows:
Mp is the measurement result of the NR SpCell, not taking into account any offsets.
Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to 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 reportConfigNR for this event).
Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigNR for this event).
Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigNR 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.
Thresh1is expressed in the same unit as Mp.
Thresh2 is expressed in the same unit as Mn.
NOTE 2: The definition of Event A5 also applies to CondEvent A5.
5.5.4.7 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 corresponding to the measObjectNR associated to this event to be the serving cell.
NOTE: The reference signal(s) of the neighbour(s) and the reference signal(s) of the SCell are both indicated in the associated measObjectNR.
Inequality A6-1 (Entering condition)
Mn + Ocn – Hys > Ms + Ocs + Off
Inequality A6-2 (Leaving condition)
Mn + Ocn + Hys < Ms + Ocs + Off
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 the associated measObjectNR), 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 the associated measObjectNR), 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 reportConfigNR for this event).
Off is the offset parameter for this event (i.e. a6-Offset as defined within reportConfigNR 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.8 Event B1 (Inter RAT neighbour becomes better than threshold)
The UE shall:
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)
Mn + Ofn + Ocn – Hys > Thresh
Inequality B1-2 (Leaving condition)
Mn + Ofn + Ocn + Hys < Thresh
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.
Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra-Q-OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the neighbour inter-RAT cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the frequency of the neighbour inter-RAT cell).
Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the measObjectEUTRA corresponding to the neighbour inter-RAT 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 reportConfigInterRAT for this event).
Thresh is the threshold parameter for this event (i.e. b1-ThresholdEUTRA as defined within reportConfigInterRAT for this event, b1-ThresholdUTRA-FDD as defined for UTRA-FDD within reportConfigInterRAT for this event).
Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.
Ofn, Ocn, Hys are expressed in dB.
Thresh is expressed in the same unit as Mn.
5.5.4.9 Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2)
The UE shall:
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)
Mp + Hys < Thresh1
Inequality B2-2 (Entering condition 2)
Mn + Ofn + Ocn – Hys > Thresh2
Inequality B2-3 (Leaving condition 1)
Mp – Hys > Thresh1
Inequality B2-4 (Leaving condition 2)
Mn + Ofn + Ocn + Hys < Thresh2
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.
Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra-Q-OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the inter-RAT neighbour cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the frequency of the neighbour inter-RAT cell).
Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the measObjectEUTRA corresponding to the neighbour inter-RAT 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 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-Threshold2EUTRA as defined within reportConfigInterRAT for this event, b2-Threshold2UTRA-FDD as defined for UTRA-FDD within reportConfigInterRAT for this event).
Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR.
Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell.
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.10 Event I1 (Interference becomes higher than threshold)
The UE shall:
1> consider the entering condition for this event to be satisfied when condition I1-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition I1-2, as specified below, is fulfilled.
Inequality I1-1 (Entering condition)
Mi – Hys > Thresh
Inequality I1-2 (Leaving condition)
Mi+ Hys < Thresh
The variables in the formula are defined as follows:
Mi is the measurement result of the interference, not taking into account any offsets.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).
Thresh is the threshold parameter for this event (i.e. i1-Threshold as defined within reportConfigNR for this event).
Mi, Thresh are expressed in dBm.
Hys is expressed in dB.
5.5.4.11 Event C1 (The NR sidelink channel busy ratio is above a 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:
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 reportConfigNR-SL for this event).
Thresh is the threshold parameter for this event (i.e. c1-Threshold as defined within reportConfigNR-SL for this event).
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.12 Event C2 (The NR sidelink channel busy ratio is below a threshold)
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;
Inequality C2-1 (Entering condition)
Inequality C2-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 reportConfigNR-SL for this event).
Thresh is the threshold parameter for this event (i.e. c2-Threshold as defined within reportConfigNR-SL for this event).
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.13 Void
5.5.4.14 Void
5.5.4.15 Event D1
The UE shall:
1> consider the entering condition for this event to be satisfied when both condition D1-1 and condition D1-2, as specified below, are fulfilled;
1> consider the leaving condition for this event to be satisfied when condition D1-3 or condition D1-4, i.e. at least one of the two, as specified below, are fulfilled;
Inequality D1-1 (Entering condition 1)
Inequality D1-2 (Entering condition 2)
Inequality D1-3 (Leaving condition 1)
Inequality D1-4 (Leaving condition 2)
The variables in the formula are defined as follows:
Ml1 is the UE location, represented by the distance between UE and a reference location parameter for this event (i.e. referenceLocation1 as defined within reportConfigNR for this event), not taking into account any offsets.
Ml2 is the UE location, represented by the distance between UE and a reference location parameter for this event (i.e. referenceLocation2 as defined within reportConfigNR for this event), not taking into account any offsets.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event).
Thresh1 is the threshold for this event defined as a distance, configured with parameter distanceThreshFromReference1, from a reference location configured with parameter referenceLocation1 within reportConfigNR for this event.
Thresh2 is the threshold for this event defined as a distance, configured with parameter distanceThreshFromReference2, from a reference location configured with parameter referenceLocation2 within reportConfigNR for this event.
Ml1 is expressed in meters.
Ml2 is expressed in the same unit as Ml1.
Hys is expressed in the same unit as Ml1.
Thresh1 is expressed in the same unit as Ml1.
Thresh2 is expressed in the same unit as Ml1.
NOTE: The definition of Event D1 also applies to CondEvent D1.
5.5.4.16 CondEvent T1
The UE shall:
1> consider the entering condition for this event to be satisfied when condition T1-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition T1-2, as specified below, is fulfilled;
Inequality T1-1 (Entering condition)
Inequality T1-2 (Leaving condition)
The variables in the formula are defined as follows:
Mt is the time measured at UE.
Thresh1 is the threshold parameter for this event (i.e. t1-Threshold as defined within reportConfigNR for this event).
Duration is the duration parameter for this event (i.e. duration as defined within reportConfigNR for this event).
Mt is expressed in ms.
Thresh1 is expressed in the same unit as Mt.
Duration is expressed in the same unit as Mt.
5.5.4.17 Event X1 (Serving L2 U2N Relay UE becomes worse than threshold1 and NR Cell becomes better than threshold2)
The UE shall:
1> consider the entering condition for this event to be satisfied when both condition X1-1 and condition X1-2, as specified below, are fulfilled;
1> consider the leaving condition for this event to be satisfied when condition X1-3 or condition X1-4, i.e. at least one of the two, as specified below, is fulfilled;
Inequality X1-1 (Entering condition 1)
Mr + Hys < Thresh1
Inequality X1-2 (Entering condition 2)
Mn + Ofn + Ocn – Hys > Thresh2
Inequality X1-3 (Leaving condition 1)
Mr – Hys > Thresh1
Inequality X1-4 (Leaving condition 2)
Mn + Ofn + Ocn + Hys < Thresh2
The variables in the formula are defined as follows:
Mr is the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets.
Mn is the measurement result of the NR cell, not taking into account any offsets.
Ofn is the measurement object specific offset of the reference signal of the NR cell (i.e. offsetMO as defined within measObjectNR corresponding to the NR cell).
Ocn is the cell specific offset of the NR cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the NR cell), and set to zero if not configured for the cell.
Hys is the hysteresis parameter for this event.
Thresh1 is the threshold parameter for this event (i.e. x1-Threshold1-Relay as defined within reportConfigNR for this event).
Thresh2 is the threshold parameter for this event (i.e. x1-Threshold2 as defined within reportConfigNR for this event).
Mr is expressed in dBm.
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.
Thresh1 is expressed in the same unit as Mr.
Thresh2 is expressed in the same unit as Mn.
5.5.4.18 Event X2 (Serving L2 U2N Relay UE becomes worse than threshold)
The UE shall:
1> consider the entering condition for this event to be satisfied when condition X2-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition X2-2, as specified below, is fulfilled;
Inequality X2-1 (Entering condition)
Mr + Hys < Thresh
Inequality X2-2 (Leaving condition)
Mr – Hys > Thresh
The variables in the formula are defined as follows:
Mr is the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets.
Hys is the hysteresis parameter for this event.
Thresh is the threshold parameter for this event (i.e. x2-Threshold-Relay as defined within reportConfigNR for this event).
Mr is expressed in dBm.
Hys are expressed in dB.
Thresh is expressed in the same unit as Mr.
5.5.4.19 Event Y1 (PCell becomes worse than threshold1 and candidate L2 U2N Relay UE becomes better than threshold2)
The UE shall:
1> consider the entering condition for this event to be satisfied when both condition Y1-1 and condition Y1-2, as specified below, are fulfilled;
1> consider the leaving condition for this event to be satisfied when condition Y1-3 or condition Y1-4, i.e. at least one of the two, as specified below, is fulfilled;
Inequality Y1-1 (Entering condition 1)
Mp + Hys < Thresh1
Inequality Y1-2 (Entering condition 2)
Mr– Hys > Thresh2
Inequality Y1-3 (Leaving condition 1)
Mp – Hys > Thresh1
Inequality Y1-4 (Leaving condition 2)
Mr + Hys < Thresh2
The variables in the formula are defined as follows:
Mp is the measurement result of the PCell, not taking into account any offsets.
Mr is the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets.
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. y1-Threshold1 as defined within reportConfigInterRAT for this event).
Thresh2 is the threshold parameter for this event (i.e. y1-Threshold2-Relay as defined within reportConfigInterRAT for this event).
Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ and SINR.
Mr is expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE.
Hys are expressed in dB.
Thresh1 is expressed in the same unit as Mp.
Thresh2 is expressed in the same unit as Mr.
5.5.4.20 Event Y2 (Candidate L2 U2N Relay UE becomes better than threshold)
The UE shall:
1> consider the entering condition for this event to be satisfied when condition Y2-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition Y2-2, as specified below, is fulfilled;
Inequality Y2-1 (Entering condition)
Mr– Hys > Thresh2
Inequality Y2-2 (Leaving condition)
Mr + Hys < Thresh2
The variables in the formula are defined as follows:
Mr is the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets.
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. y2-Threshold-Relay as defined within reportConfigInterRAT for this event).
Mr is expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE.
Hys are expressed in dB.
Thresh is expressed in the same unit as Mr.
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 the network. The UE shall initiate this procedure only after successful AS 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> for each serving cell configured with servingCellMO:
2> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:
3> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available:
4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;
2> else:
3> if SSB based serving cell measurements are available:
4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;
3> else if CSI-RS based serving cell measurements are available:
4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;
1> set the servCellId within measResultServingMOList to include each NR serving cell that is configured with servingCellMO, if any;
1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:
2> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2;
1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:
2> for each measObjectId referenced in the measIdList which is also referenced with servingCellMO, other than the measObjectId corresponding with the measId that triggered the measurement reporting:
3> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:
4> set the measResultBestNeighCell within measResultServingMOList to include the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR;
4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:
5> for each best non-serving cell included in the measurement report:
6> include beam measurement information according to the associated reportConfig as described in 5.5.5.2;
1> if the reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5, or eventB1, or eventB2:
2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG:
3> set the measResultServFreqListEUTRA-SCG to include an entry for each E-UTRA SCG serving frequency with the following:
4> include carrierFreq of the E-UTRA serving frequency;
4> set the measResultServingCell to include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG;
4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:
5> set the measResultServFreqListEUTRA-SCG to include within measResultBestNeighCell the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;
1> if reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5:
2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG:
3> set the measResultServFreqListNR-SCG to include for each NR SCG serving cell that is configured with servingCellMO, if any, the following:
4> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType:
5> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available according to the measurement configuration associated with the SCG:
6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report;
4> else:
5> if SSB based serving cell measurements are available according to the measurement configuration associated with the SCG:
6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB;
5> else if CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG:
6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS;
4> if results for the serving cell derived based on SSB are included:
5> include the ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR of the serving cell;
4> if results for the serving cell derived based on CSI-RS are included:
5> include the refFreqCSI-RS to the value indicated by refFreqCSI-RS as included in the MeasObjectNR of the serving cell;
4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:
5> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;
4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas:
5> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig:
6> set the measResultBestNeighCellListNR within measResultServFreqListNR-SCG to include one entry with the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR, where availability is considered according to the measurement configuration associated with the SCG;
7> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport:
8> for each best non-serving cell included in the measurement report:
9> include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG;
1> if the measRSSI-ReportConfig is configured within the corresponding reportConfig for this measId:
2> set the rssi-Result to the linear 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 the channelOccupancyThreshold within all the sample values in the reportInterval;
1> if the UE is acting as L2 U2N Remote UE:
2> set the sl-MeasResultServingRelay in accordance with the following:
3> set the cellIdentity to include the cellAccessRelatedInfo contained in the discovery message received from the serving L2 U2N Relay UE;
3> set the sl-RelayUE-Identity to include the Source L2 ID of the serving L2 U2N Relay;
3> set the sl-MeasResult to include the SL-RSRP of the serving L2 U2N Relay UE;
NOTE 1: In case of no data transmission from L2 U2N Relay UE to L2 U2N Remote UE, it is left to UE implementation whether to use SL-RSRP or SD-RSRP when setting the sl-MeasResultServingRelay of the serving L2 U2N Relay UE.
1> if there is at least one applicable neighbouring cell or candidate L2 U2N Relay UE to report:
2> if the reportType is set to eventTriggered or periodical:
3> if the measurement report concerns the candidate L2 U2N Relay UE:
4> set the sl-MeasResultsCandRelay in measResultNeighCells to include the best candidate L2 U2N Relay UEs up to maxReportCells in accordance with the following:
5> if the reportType is set to eventTriggered:
6> include the L2 U2N Relay UEs included in the relaysTriggeredList as defined within the VarMeasReportList for this measId;
5> else:
6> include the applicable L2 U2N Relay UEs for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;
5> for each L2 U2N Relay UE that is included in the sl-MeasResultsCandRelay:
6> set the cellIdentity to include the cellAccessRelatedInfo contained in the discovery message received from the concerned L2 U2N Relay UE;
6> set the sl-RelayUE-Identity to include the Source L2 ID of the concerned L2 U2N Relay UE;
6> set the sl-MeasResult to include the SD-RSRP of the concerned L2 U2N Relay UE;
5> for each included L2 U2N Relay UE, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:
6> set the sl-MeasResult to include the quantity(ies) indicated in the reportQuantityRelay within the concerned reportConfigRelay in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best L2 U2N Relay UE is included first;
3> else:
4> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following:
5> if the reportType is set to eventTriggered and eventId is not set to eventD1:
6> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId;
5> else:
6> 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;
5> for each cell that is included in the measResultNeighCells, include the physCellId;
5> if the reportType is set to eventTriggered or periodical:
6> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows:
7> if the measObject associated with this measId concerns NR:
8> if rsType in the associated reportConfig is set to ssb:
9> set resultsSSB-Cell within the measResult to include the SS/PBCH block based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;
9> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2;
8> else if rsType in the associated reportConfig is set to csi-rs:
9> set resultsCSI-RS-Cell within the measResult to include the CSI-RS based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;
9> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2;
7> if the measObject associated with this measId concerns E-UTRA:
8> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfigInterRAT in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;
7> if the measObject associated with this measId concerns UTRA-FDD and if ReportConfigInterRAT includes the reportQuantityUTRA-FDD:
8> set the measResult to include the quantity(ies) indicated in the reportQuantityUTRA-FDD within the concerned reportConfigInterRAT in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first;
2> else:
3> if the cell indicated by cellForWhichToReportCGI is an NR cell:
4> if plmn-IdentityInfoList of the cgi-Info for the concerned cell has been obtained:
5> include the plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode (if available), trackingAreaList (if available), ranac (if available), cellIdentity and cellReservedForOperatorUse for each entry of the plmn-IdentityInfoList;
5> include frequencyBandList if available;
5> for each PLMN-IdentityInfo in plmn-IdentityInfoList:
6> if the gNB-ID-Length is broadcast:
7> include gNB-ID-Length;
4> if nr-CGI-Reporting-NPN is supported by the UE and npn-IdentityInfoList of the cgi-Info for the concerned cell has been obtained:
5> include the npn-IdentityInfoList including npn-IdentityList, trackingAreaCode, ranac (if available), cellIdentity and cellReservedForOperatorUse for each entry of the npn-IdentityInfoList;
5> for each NPN-IdentityInfo in NPN-IdentityInfoList:
6> if the gNB-ID-Length is broadcast:
7> include gNB-ID-Length;
5> include cellReservedForOtherUse if available;
4> else if MIB indicates the SIB1 is not broadcast:
5> include the noSIB1 including the ssb-SubcarrierOffset and pdcch-ConfigSIB1 obtained from MIB of the concerned cell;
3> if the cell indicated by cellForWhichToReportCGI is an E-UTRA cell:
4> if all mandatory fields of the cgi-Info-EPC for the concerned cell have been obtained:
5> include in the cgi-Info-EPC the fields broadcasted in E-UTRA SystemInformationBlockType1 associated to EPC;
4> if the UE is E-UTRA/5GC capable and all mandatory fields of the cgi-Info-5GC for the concerned cell have been obtained:
5> include in the cgi-Info-5GC the fields broadcasted in E-UTRA SystemInformationBlockType1 associated to 5GC;
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> include the freqBandIndicator;
5> if the cell broadcasts the multiBandInfoList, include the multiBandInfoList;
5> if the cell broadcasts the freqBandIndicatorPriority, include the freqBandIndicatorPriority;
1> if the corresponding measObject concerns NR:
2> if the reportSFTD-Meas is set to true within the corresponding reportConfigNR for this measId:
3> set the measResultSFTD-NR in accordance with the following:
4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;
4> if the reportRSRP is set to true;
5> set rsrp-Result to the RSRP of the NR PSCell derived based on SSB;
2> else if the reportSFTD-NeighMeas is included within the corresponding reportConfigNR for this measId:
3> for each applicable cell which measurement results are available, include an entry in the measResultCellListSFTD-NR and set the contents as follows:
4> set physCellId to the physical cell identity of the concerned NR neighbour cell.
4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;
4> if the reportRSRP is set to true:
5> set rsrp-Result to the RSRP of the concerned cell derived based on SSB;
1> else if the corresponding measObject concerns E-UTRA:
2> if the reportSFTD-Meas is set to true within the corresponding reportConfigInterRAT for this measId:
3> set the measResultSFTD-EUTRA in accordance with the following:
4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;
4> if the reportRSRP is set to true;
5> set rsrpResult-EUTRA to the RSRP of the EUTRA PSCell;
1> if average uplink PDCP delay values are available:
2> set the ul-PDCP-DelayValueResultList to include the corresponding average uplink PDCP delay values;
1> if PDCP excess delay measurements are available:
2> set the ul-PDCP-ExcessDelayResultList to include the corresponding PDCP excess delay measurements;
1> if the includeCommonLocationInfo is configured in the corresponding reportConfig for this measId and detailed location information that has not been reported is available, set the content of commonLocationInfo of the locationInfo as follows:
2> include the locationTimestamp;
2> include the locationCoordinate, if available;
2> include the velocityEstimate, if available;
2> include the locationError, if available;
2> include the locationSource, if available;
2> if available, include the gnss-TOD-msec,
1> if the coarseLocationRequest is set to true in the corresponding reportConfig for this measId:
2> include coarseLocationInfo, if available;
1> if the includeWLAN-Meas is configured in the corresponding reportConfig for this measId, set the wlan-LocationInfo of the locationInfo in the measResults as follows:
2> if available, include the LogMeasResultWLAN, in order of decreasing RSSI for WLAN APs;
1> if the includeBT-Meas is configured in the corresponding reportConfig for this measId, set the BT-LocationInfo of the locationInfo in the measResults as follows:
2> if available, include the LogMeasResultBT, in order of decreasing RSSI for Bluetooth beacons;
1> if the includeSensor-Meas is configured in the corresponding reportConfig for this measId, set the sensor-LocationInfo of the locationInfo in the measResults as follows:
2> if available, include the sensor-MeasurementInformation;
2> if available, include the sensor-MotionInformation;
1> if there is at least one applicable transmission resource pool for NR sidelink communication/discovery (for measResultsSL):
2> set the measResultsListSL to include the CBR measurement results in accordance with the following:
3> if the reportType is set to eventTriggered:
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> if the corresponding measObject concerns NR sidelink communication/discovery, then for each transmission resource pool to be reported:
4> set the sl-poolReportIdentity to the identity of this transmission resource pool;
4> set the sl-CBR-ResultsNR to the CBR measurement results on PSSCH and PSCCH of this transmission resource pool provided by lower layers, if available;
NOTE 1: Void.
1> if there is at least one applicable CLI measurement resource to report:
2> if the reportType is set to cli-EventTriggered or cli-Periodical:
3> set the measResultCLI to include the most interfering SRS resources or most interfering CLI-RSSI resources up to maxReportCLI in accordance with the following:
4> if the reportType is set to cli-EventTriggered:
5> if trigger quantity is set to srs-RSRP i.e. i1-Threshold is set to srs-RSRP:
6> include the SRS resource included in the cli-TriggeredList as defined within the VarMeasReportList for this measId;
5> if trigger quantity is set to cli-RSSI i.e. i1-Threshold is set to cli-RSSI:
6> include the CLI-RSSI resource included in the cli-TriggeredList as defined within the VarMeasReportList for this measId;
4> else:
5> if reportQuantityCLI is set to srs-rsrp:
6> include the applicable SRS resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;
5> else:
6> include the applicable CLI-RSSI resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset;
4> for each SRS resource that is included in the measResultCLI:
5> include the srs-ResourceId;
5> set srs-RSRP-Result to include the layer 3 filtered measured results in decreasing order, i.e. the most interfering SRS resource is included first;
4> for each CLI-RSSI resource that is included in the measResultCLI:
5> include the rssi-ResourceId;
5> set cli-RSSI-Result to include the layer 3 filtered measured results in decreasing order, i.e. the most interfering CLI-RSSI resource is included first;
1> if there is at least one applicable UE Rx-Tx time difference measurement to report:
2> set measResultRxTxTimeDiff to the latest measurement result;
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 reportType is set to periodical or cli-Periodical or rxTxPeriodical:
3> remove the entry within the VarMeasReportList for this measId;
3> remove this measId from the measIdList within VarMeasConfig;
1> if the measurement reporting was configured by a sl-ConfigDedicatedNR received within the RRCConnectionReconfiguration:
2> submit the MeasurementReport message to lower layers for transmission via SRB1, embedded in E-UTRA RRC message ULInformationTransferIRAT as specified TS 36.331 [10], clause 5.6.28;
1> else if the UE is in (NG)EN-DC:
2> if SRB3 is configured and the SCG is not deactivated:
3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;
2> else:
3> submit the MeasurementReport message via E-UTRA embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10].
1> else if the UE is in NR-DC:
2> if the measurement configuration that triggered this measurement report is associated with the SCG:
3> if SRB3 is configured and the SCG is not deactivated:
4> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends;
3> else:
4> submit the MeasurementReport message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3;
2> else:
3> submit the MeasurementReport message via SRB1 to lower layers for transmission, upon which the procedure ends;
1> else:
2> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends.
5.5.5.2 Reporting of beam measurement information
For beam measurement information to be included in a measurement report the UE shall:
1> if reportType is set to eventTriggered:
2> consider the trigger quantity as the sorting quantity if available, otherwise RSRP as sorting quantity if available, otherwise RSRQ as sorting quantity if available, otherwise SINR as sorting quantity;
1> if reportType is set to periodical:
2> if a single reporting quantity is set to true in reportQuantityRS-Indexes;
3> consider the configured single quantity as the sorting quantity;
2> else:
3> if rsrp is set to true;
4> consider RSRP as the sorting quantity;
3> else:
4> consider RSRQ as the sorting quantity;
1> set rsIndexResults to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes or CSI-RS indexes in order of decreasing sorting quantity as follows:
2> if the measurement information to be included is based on SS/PBCH block:
3> include within resultsSSB-Indexes the index associated to the best beam for that SS/PBCH block sorting quantity and if absThreshSS-BlocksConsolidation is included in the VarMeasConfig for the measObject associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;
3> if includeBeamMeasurements is set to true, include the SS/PBCH based measurement results for the quantities in reportQuantityRS-Indexes for each SS/PBCH block index;
2> else if the beam measurement information to be included is based on CSI-RS:
3> include within resultsCSI-RS-Indexes the index associated to the best beam for that CSI-RS sorting quantity and, if absThreshCSI-RS-Consolidation is included in the VarMeasConfig for the measObject associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above absThreshCSI-RS-Consolidation;
3> if includeBeamMeasurements is set to true, include the CSI-RS based measurement results for the quantities in reportQuantityRS-Indexes for each CSI-RS index.
5.5.5.3 Sorting of cell measurement results
The UE shall determine the sorting quantity according to parameters of the reportConfig associated with the measId that triggered the reporting:
1> if the reportType is set to eventTriggered:
2> for an NR cell, consider the quantity used in the aN-Threshold (for eventA1, eventA2 and eventA4) or in the a5-Threshold2 (for eventA5) or in the aN-Offset (for eventA3 and eventA6) as the sorting quantity;
2> for an E-UTRA cell, consider the quantity used in the bN-ThresholdEUTRA as the sorting quantity;
2> for an UTRA-FDD cell, consider the quantity used in the bN-ThresholdUTRA-FDD as the sorting quantity;
2> for a candidate L2 U2N Relay UE, consider the yN-Threshold2-Relay as the sorting quantity;
1> if the reportType is set to periodical:
2> determine the sorting quantity according to reportQuantityCell for an NR cell, and according to reportQuantity for an E-UTRA cell, as below:
3> if a single quantity is set to true:
4> consider this quantity as the sorting quantity;
3> else:
4> if rsrp is set to true;
5> consider RSRP as the sorting quantity;
4> else:
5> consider RSRQ as the sorting quantity;
2> determine the sorting quantity according to reportQuantityUTRA-FDD for UTRA-FDD cell, as below:
3> if a single quantity is set to true:
4> consider this quantity as the sorting quantity;
3> else:
4> consider RSCP as the sorting quantity.
2> for a candidate L2 U2N Relay UE, consider the reportQuantityRelay as the sorting quantity;
5.5.6 Location measurement indication
5.5.6.1 General
Figure 5.5.5.1-1: Location measurement indication
The purpose of this procedure is to indicate to the network that the UE is going to start/stop location related measurements towards E-UTRA or NR (eutra-RSTD, nr-RSTD, nr-UE-RxTxTimeDiff, nr-PRS-RSRP) which require measurement gaps or start/stop detection of subframe and slot timing towards E-UTRA (eutra-FineTimingDetection) which requires measurement gaps. UE shall initiate this procedure only after successful AS security activation.
NOTE: It is a network decision to configure the measurement gap.
5.5.6.2 Initiation
The UE shall:
1> if and only if upper layers indicate to start performing location measurements towards E-UTRA or NR or start subframe and slot timing detection towards E-UTRA, and the UE requires measurement gaps for these operations while measurement gaps are either not configured or not sufficient:
2> if preconfigured measurement gaps for positioning are configured and the UE considers that at least one of the preconfigured measurement gaps for positioning is sufficient for the location measurement when activated:
3> trigger the lower layers to initiate the measurement gap activation request using UL MAC CE as specified in TS 38.321 [6];
2> else:
3> initiate the procedure to indicate start as specified in clause 5.5.6.3;
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 of the target RAT if the provided measurement gaps are insufficient.
NOTE 1a: When indication is received from upper layers for performing location measurement and there is pre-configured measurement gap configured (not preconfigured measurement gap for positioning), the UE considers this preconfigured measurement gap to be not sufficient if the measurement gap is not considered to be always activated according to clause 9.1.7.2 of TS 38.133 [14].
1> if and only if upper layers indicate to stop performing location measurements towards E-UTRA or NR or stop subframe and slot timing detection towards E-UTRA:
2> if there is no activated preconfigured measurement gap for positioning:
3> initiate the procedure to indicate stop as specified in 5.5.6.3.
2> else if there is activated preconfigured measurement gap for positioning:
3> trigger the lower layers to deactivate all the activated measurement gap(s) for positioning as specified in TS 38.321 [6].
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.6.3 Actions related to transmission of LocationMeasurementIndication message
The UE shall set the contents of LocationMeasurementIndication message as follows:
1> if the procedure is initiated to indicate start of location related measurements:
2> if the procedure is initiated for RSTD measurements towards E-UTRA:
3> set the measurementIndication to the eutra-RSTD according to the information received from upper layers;
2> else if the procedure is initiated for positioning measurement towards NR:
3> set the measurementIndication to the nr-PRS-Measurement according to the information received from upper layers;
1> else if the procedure is initiated to indicate stop of location related measurements:
2> set the measurementIndication to the value release;
1> if the procedure is initiated to indicate start of subframe and slot timing detection towards E-UTRA:
2> set the measurementIndication to the value eutra-FineTimingDetection;
1> else if the procedure is initiated to indicate stop of subframe and slot timing detection towards E-UTRA:
2> set the measurementIndication to the value release;
1> submit the LocationMeasurementIndication message to lower layers for transmission, upon which the procedure ends.