Content for TS 38.331 Word version: 17.4.0

1… 4… 5… 5.2.2.4… 5.3… 5.3.3… 5.3.5… 5.3.5.5… 5.3.5.6… 5.3.5.7… 5.3.5.13… 5.3.6… 5.3.8… 5.3.13… 5.3.14… 5.4… 5.5… 5.5.3… 5.5.4… 5.5.5… 5.5a… 5.7… 5.7.4… 5.7.8… 5.8… 5.8.9… 5.8.10… 5.8.11… 5.9… 6… 6.2.2… 6-2-2-25… 6.3… 6.3.2… 6-3-2-27… 6-3-2-49… 6-3-2-73… 6-3-2-95… 6-3-2-108… 6-3-2-134… 6-3-2-162… 6-3-2-188… 6-3-2-213… 6-3-2-243… 6-3-2-271… 6-3-2-297… 6.3.3… 6-3-3-25… 6-3-3-51… 6.3.4… 6.3.5… 6-3-5-25… 6.3.6… 6.4… 7… 9… 11… A… A.4… B…

5.5.5 Measurement reporting 5.5.5.1 General 5.5.5.2 Reporting of beam measurement information 5.5.5.3 Sorting of cell measurement results 5.5.6 Location measurement indication 5.5.6.1 General 5.5.6.2 Initiation 5.5.6.3 Actions related to transmission of LocationMeasurementIndication message
...

5.5.5 Measurement reporting p. 209

5.5.5.1 General p. 209

Reproduction of 3GPP TS 38.331, Fig. 5.5.5.1-1: Measurement reporting

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 clause 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 clause 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 clause 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 measResultNeighCellListNR 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 clause 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;

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

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 in clause 5.6.28 of TS 36.331;

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.

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 clause 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 p. 218

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 p. 218

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 p. 219

5.5.6.1 General p. 219

Reproduction of 3GPP TS 38.331, Fig. 5.5.6.1-1: Location measurement indication

Figure 5.5.6.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.

5.5.6.2 Initiation p. 219

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 and posMG-Request 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;

2 >

else:

3 >

initiate the procedure to indicate start as specified in clause 5.5.6.3;

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 >

if there is previously triggered UL MAC CE transmission for the measurement gap activation for positioning:

4 >

indicate to the lower layers to cancel the triggered UL MAC CE transmission for the measurement gap activation as specified in TS 38.321;

3 >

else:

4 >

initiate the procedure to indicate stop as specified in clause 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.

5.5.6.3 Actions related to transmission of LocationMeasurementIndication message p. 220

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.