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.7.8 Idle/inactive Measurements 5.7.9 Mobility history information 5.7.10 UE Information 5.7.12 IAB Other Information 5.7.13 RLM/BFD relaxation 5.7.14 UE Positioning Assistance Information 5.7.16 Application layer measurement reporting 5.7.17 Derivation of pathloss reference for TA validation of SRS for Positioning transmission and CG-SDT in RRC_INACTIVE
...

5.7.8 Idle/inactive Measurements |R16| p. 261

5.7.8.1 General p. 261

This procedure specifies the measurements to be performed and stored by a UE in RRC_IDLE and RRC_INACTIVE when it has an idle/inactive measurement configuration.

5.7.8.1a Measurement configuration p. 261

The purpose of this procedure is to update the idle/inactive measurement configuration.

The UE initiates this procedure while T331 is running and SDT procedure is not ongoing and one of the following conditions is met:

1 >

upon selecting a cell when entering RRC_IDLE or RRC-INACTIVE from RRC_CONNECTED or RRC_INACTIVE; or

1 >

upon update of system information (SIB4, or SIB11), e.g. due to intra-RAT cell (re)selection;

While in RRC_IDLE or RRC_INACTIVE, and T331 is running, the UE shall:

1 >

if VarMeasIdleConfig includes neither a measIdleCarrierListEUTRA nor a measIdleCarrierListNR received from the RRCRelease message:

2 >

if the UE supports idleInactiveEUTRA-MeasReport:

3 >

if the SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListEUTRA:

4 >

store or replace the measIdleCarrierListEUTRA of measIdleConfigSIB of SIB11 within VarMeasIdleConfig;

3 >

else:

4 >

remove the measIdleCarrierListEUTRA in VarMeasIdleConfig, if stored;

2 >

if the UE supports idleInactiveNR-MeasReport:

3 >

if SIB11 includes the measIdleConfigSIB and contains measIdleCarrierListNR:

4 >

store or replace the measIdleCarrierListNR of measIdleConfigSIB of SIB11 within VarMeasIdleConfig;

3 >

else:

4 >

remove the measIdleCarrierListNR in VarMeasIdleConfig, if stored;

1 >

for each entry in the measIdleCarrierListNR within VarMeasIdleConfig that does not contain an ssb-MeasConfig received from the RRCRelease message:

2 >

if there is an entry in measIdleCarrierListNR in measIdleConfigSIB of SIB11 that has the same carrier frequency and subcarrier spacing as the entry in the measIdleCarrierListNR within VarMeasIdleConfig and that contains ssb-MeasConfig:

3 >

delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;

3 >

store the SSB measurement configuration from SIB11 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;

2 >

else if there is an entry in interFreqCarrierFreqList of SIB4 with the same carrier frequency and subcarrier spacing as the entry in measIdleCarrierListNR within VarMeasIdleConfig:

3 >

delete the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;

3 >

store the SSB measurement configuration from SIB4 into nrofSS-BlocksToAverage, absThreshSS-BlocksConsolidation, smtc, ssb-ToMeasure, deriveSSB-IndexFromCell, and ss-RSSI-Measurement within ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig;

2 >

else:

3 >

remove the ssb-MeasConfig of the corresponding entry in the measIdleCarrierListNR within VarMeasIdleConfig, if stored;

1 >

perform measurements according to clause 5.7.8.2a.

5.7.8.2 Void

5.7.8.2a Performing measurements p. 262

When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in clause 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215.

While in RRC_IDLE or RRC_INACTIVE, and T331 is running and SDT procedure is not ongoing, the UE shall:

1 >

perform the measurements in accordance with the following:

2 >

if the VarMeasIdleConfig includes the measIdleCarrierListEUTRA and the SIB1 contains idleModeMeasurementsEUTRA:

3 >

for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig:

4 >

if UE supports NE-DC between the serving carrier and the carrier frequency indicated by carrierFreqEUTRA within the corresponding entry:

5 >

perform measurements in the carrier frequency and bandwidth indicated by carrierFreqEUTRA and allowedMeasBandwidth within the corresponding entry;

5 >

if the reportQuantitiesEUTRA is set to rsrq:

6 >

consider RSRQ as the sorting quantity;

5 >

else:

6 >

consider RSRP as the sorting quantity;

5 >

if the measCellListEUTRA is included:

6 >

consider cells identified by each entry within the measCellListEUTRA to be applicable for idle/inactive mode measurement reporting;

5 >

else:

6 >

consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting;

5 >

for all cells applicable for idle/inactive measurement reporting, derive measurement results for the measurement quantities indicated by reportQuantitiesEUTRA;

5 >

store the derived measurement results as indicated by reportQuantitiesEUTRA within the measReportIdleEUTRA in VarMeasIdleReport in decreasing order of the sorting quantity, i.e. the best cell is included first, as follows:

6 >

if qualityThresholdEUTRA is configured:

7 >

include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThresholdEUTRA;

6 >

else:

7 >

include the measurement results from all cells applicable for idle/inactive measurement reporting;

2 >

if the VarMeasIdleConfig includes the measIdleCarrierListNR and the SIB1 contains idleModeMeasurementsNR:

3 >

for each entry in measIdleCarrierListNR within VarMeasIdleConfig that contains ssb-MeasConfig:

4 >

if UE supports carrier aggregation or NR-DC between serving carrier and the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry:

5 >

perform measurements in the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry;

5 >

if the reportQuantities is set to rsrq:

6 >

consider RSRQ as the cell sorting quantity;

5 >

else:

6 >

consider RSRP as the cell sorting quantity;

5 >

if the measCellListNR is included:

6 >

consider cells identified by each entry within the measCellListNR to be applicable for idle/inactive measurement reporting;

5 >

else:

6 >

consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting;

5 >

for all cells applicable for idle/inactive measurement reporting, derive cell measurement results for the measurement quantities indicated by reportQuantities;

5 >

store the derived cell measurement results as indicated by reportQuantities for cells applicable for idle/inactive measurement reporting within measResultsPerCarrierListIdleNR in the measReportIdleNR in VarMeasIdleReport in decreasing order of the cell sorting quantity, i.e. the best cell is included first, as follows:

6 >

if qualityThreshold is configured:

7 >

include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold;

6 >

else:

7 >

include the measurement results from all cells applicable for idle/inactive measurement reporting;

5 >

if beamMeasConfigIdle is included in the associated entry in measIdleCarrierListNR and if UE supports idleInactiveNR-MeasBeamReport for the FR of the carrier frequency indicated by carrierFreq within the associated entry, for each cell in the measurement results:

6 >

derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215;

6 >

if the reportQuantityRS-Indexes is set to rsrq:

7 >

consider RSRQ as the beam sorting quantity;

6 >

else:

7 >

consider RSRP as the beam sorting quantity;

6 >

set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows:

7 >

include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;

6 >

if the includeBeamMeasurements is set to true:

7 >

include the beam measurement results as indicated by reportQuantityRS-Indexes;

2 >

if, as a result of the procedure in this clause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA:

3 >

store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport.

3 >

if the VarMeasIdleConfig includes the measIdleCarrierListNR and it contains an entry with carrierFreq set to the value of the serving frequency:

4 >

if beamMeasConfigIdle is included in that entry, and if the UE supports idleInactiveNR- MeasBeamReport for the FR of the serving cell:

5 >

derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215;

5 >

if the reportQuantityRS-Indexes is set to rsrq:

6 >

consider RSRQ as the beam sorting quantity;

5 >

else:

6 >

consider RSRP as the beam sorting quantity;

5 >

set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows:

6 >

include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included in SIB2 of serving cell, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation;

5 >

if the includeBeamMeasurements is set to true:

6 >

include the beam measurement results as indicated by reportQuantityRS-Indexes;

5.7.8.3 T331 expiry or stop p. 265

The UE shall:

1 >

if T331 expires or is stopped:

2 >

release the VarMeasIdleConfig.

5.7.8.4 Cell re-selection or cell selection while T331 is running p. 265

The UE shall:

1 >

if intra-RAT cell selection or reselection occurs while T331 is running:

2 >

if validityAreaList is configured in VarMeasIdleConfig:

3 >

if the serving frequency does not match with the carrierFreq of an entry in the validityAreaList; or

3 >

if the serving frequency matches with the carrierFreq of an entry in the validityAreaList, the validityCellList is included in that entry, and the physical cell identity of the serving cell does not match with any entry in validityCellList:

4 >

stop timer T331;

4 >

perform the actions as specified in clause 5.7.8.3, upon which the procedure ends.

1 >

else if inter-RAT cell selection or reselection occurs while T331 is running:

2 >

stop timer T331;

2 >

perform the actions as specified in clause 5.7.8.3;

5.7.9 Mobility history information |R16| p. 265

5.7.9.1 General p. 265

This procedure specifies how the mobility history information is stored by the UE, covering RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED.

5.7.9.2 Initiation p. 265

If the UE supports storage of mobility history information, the UE shall:

1 >

If the UE supports PSCell mobility history information and upon addition of a PSCell:

2 >

include an entry in visitedPSCellInfoList in variable VarMobilityHistoryReport possibly after performing the following, if necessary:

3 >

if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport:

4 >

for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport;

5 >

remove the oldest entry in the visitedPSCellInfoListReport;

3 >

else:

4 >

remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport;

2 >

for the included entry:

3 >

set the field timeSpent of the entry according to following:

4 >

if this is the first PSCell entry for the current PCell since entering the current PCell in RRC_CONNECTED:

5 >

include the entry as the time spent with no PSCell since entering the current PCell in RRC_CONNECTED;

4 >

else:

5 >

include the time spent with no PSCell since last PSCell release since entering the current PCell in RRC_CONNECTED;

1 >

If the UE supports PSCell mobility history information and upon change, or release of a PSCell while being connected to the current PCell:

2 >

include an entry in visitedPSCellInfoList of the variable VarMobilityHistoryReport possibly after performing the following, if necessary:

3 >

if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport:

4 >

for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport;

5 >

remove the oldest entry in the visitedPSCellInfoListReport;

3 >

else:

4 >

remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport;

2 >

for the included entry:

3 >

if the global cell identity of the previous PSCell is available:

4 >

include the global cell identity of that cell in the field visitedCellId of the entry;

3 >

else:

4 >

include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry;

3 >

set the field timeSpent of the entry as the time spent in the previous PSCell while being connected to the current PCell;

1 >

Upon change of suitable cell, consisting of PCell in RRC_CONNECTED (for NR or E-UTRA cell) or serving cell in RRC_INACTIVE (for NR cell) or in RRC_IDLE (for NR or E-UTRA cell), to another NR or E-UTRA cell, or when entering any cell selection' state from 'camped normally' state in NR or LTE or when entering 'any cell selection' state from a suitable cell in RRC_CONNECTED state in NR or LTE:

2 >

include an entry in visitedCellInfoList of the variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following:

3 >

if the global cell identity of the previous PCell/serving cell is available:

4 >

include the global cell identity of that cell in the field visitedCellId of the entry;

3 >

else:

4 >

include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry;

3 >

set the field timeSpent of the entry as the time spent in the previous PCell/serving cell;

3 >

if the UE supports PSCell mobility history information and if the UE continues to be connected to the same PSCell during the change of the PCell in RRC_CONNECTED; or

3 >

if the UE supports PSCell mobility history information and if the UE changes PSCell, or attempts to change PSCell but fails, at the same time as the change of the PCell in RRC_CONNECTED; or

3 >

if the UE supports PSCell mobility history information and if the PSCell is released at the same time as the change of the PCell in RRC_CONNECTED:

4 >

include an entry in visitedPSCellInfoList of the variable VarMobilityHistoryReport possibly after performing the following, if necessary:

5 >

if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport:

6 >

for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport;

7 >

remove the oldest entry in the visitedPSCellInfoListReport;

5 >

else:

6 >

remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport;

4 >

for the included entry:

5 >

if the global cell identity of the PSCell (in case the UE continues to be connected to the same PSCell) or the previous PSCell (in case the UE changes PSCell, or attempts to change PSCell but fails, or in case PSCell is released) is available:

6 >

include the global cell identity of that cell in the field visitedCellId of the entry;

5 >

else:

6 >

include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry;

5 >

set the field timeSpent of the entry as the time spent in the PSCell, while being connected to previous PCell;

3 >

if the UE supports PSCell mobility history information and if the UE was not configured with a PSCell at the time of change of PCell in RRC_CONNECTED:

4 >

include an entry in visitedPSCellInfoList after performing the following, if necessary;

5 >

if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport:

6 >

for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport;

7 >

remove the oldest entry in the visitedPSCellInfoListReport;

5 >

else:

6 >

remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport;

4 >

for the included entry:

5 >

set the field timeSpent of the entry as the time without PSCell according to the following:

6 >

if the UE experienced a PSCell release since entering the previous PCell in RRC_CONNECTED:

7 >

include the time spent with no PSCell since last PSCell release since entering the previous PCell in RRC_CONNECTED;

6 >

else:

7 >

include the time spent with no PSCell since entering the previous PCell in RRC_CONNECTED;

3 >

if the UE supports PSCell mobility history information and if visitedPSCellInfoList exists in VarMobilityHistoryReport:

4 >

include visitedPSCellInfoList in VarMobilityHistoryReport in the visitedPSCellInfoListReport within the entry of the visitedCellInfoList associated to the latest PCell entry;

4 >

remove visitedPSCellInfoList from the variable VarMobilityHistoryReport;

1 >

if the UE supports PSCell mobility history information and upon entering 'camped normally' state in NR (in RRC_IDLE or RRC_INACTIVE) or E-UTRA (in RRC_IDLE) while previously in RRC_CONNECTED state NR or LTE while not connected to a PSCell:

2 >

include an entry in visitedPSCellInfoList after performing the following, if necessary;

3 >

if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport:

4 >

for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport;

5 >

remove the oldest entry in the visitedPSCellInfoListReport;

3 >

else:

4 >

remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport;

2 >

for the included entry:

3 >

set the field timeSpent of the entry as the time without PSCell according to the following:

4 >

if the UE experienced a PSCell release since entering the current PCell in RRC_CONNECTED:

5 >

include the time spent with no PSCell since last PSCell release after entering the current PCell in RRC_CONNECTED;

4 >

else:

5 >

include the time spent with no PSCell since entering the current PCell in RRC_CONNECTED;

1 >

upon entering 'camped normally' state in NR (in RRC_IDLE or RRC_INACTIVE) or E-UTRA (in RRC_IDLE) while previously in 'any cell selection' state or 'camped on any cell' state in NR or LTE:

2 >

include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following:

3 >

set the field timeSpent of the entry as the time spent in 'any cell selection' state and/or 'camped on any cell' state in NR or LTE.

5.7.10 UE Information |R16| p. 268

5.7.10.1 General p. 268

Reproduction of 3GPP TS 38.331, Fig. 5.7.10.1-1: UE information procedure

Figure 5.7.10.1-1: UE information procedure

The UE information procedure is used by the network to request the UE to report information.

5.7.10.2 Initiation p. 269

The network initiates the procedure by sending the UEInformationRequest message. The network should initiate this procedure only after successful security activation.

5.7.10.3 Reception of the UEInformationRequest message p. 269

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

1 >

if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell:

2 >

set the measResultIdleEUTRA in the UEInformationResponse message to the value of measReportIdleEUTRA in the VarMeasIdleReport, if available;

2 >

set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available;

2 >

discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1 >

if the logMeasReportReq is present and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

2 >

if VarLogMeasReport includes one or more logged measurement entries, set the contents of the logMeasReport in the UEInformationResponse message as follows:

3 >

include the absoluteTimeStamp and set it to the value of absoluteTimeInfo in the VarLogMeasReport;

3 >

include the traceReference and set it to the value of traceReference in the VarLogMeasReport;

3 >

include the traceRecordingSessionRef and set it to the value of traceRecordingSessionRef in the VarLogMeasReport;

3 >

include the tce-Id and set it to the value of tce-Id in the VarLogMeasReport;

3 >

include the logMeasInfoList and set it to include one or more entries from the VarLogMeasReport starting from the entries logged first, and for each entry of the logMeasInfoList that is included, include all information stored in the corresponding logMeasInfoList entry in VarLogMeasReport;

3 >

if the VarLogMeasReport includes one or more additional logged measurement entries that are not included in the logMeasInfoList within the UEInformationResponse message:

4 >

include the logMeasAvailable;

4 >

if bt-LocationInfo is included in locationInfo of one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList within the UEInformationResponse message:

5 >

include the logMeasAvailableBT;

4 >

if wlan-LocationInfo is included in locationInfo of one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList within the UEInformationResponse message:

5 >

include the logMeasAvailableWLAN;

1 >

if ra-ReportReq is set to true and the UE has random access related information available in VarRA-Report and if the RPLMN is included in plmn-IdentityList stored in VarRA-Report:

2 >

set the ra-ReportList in the UEInformationResponse message to the value of ra-ReportList in VarRA-Report;

2 >

discard the ra-ReportList from VarRA-Report upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1 >

if rlf-ReportReq is set to true:

2 >

if the UE has radio link failure information or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

3 >

set timeSinceFailure in VarRLF-Report to the time that elapsed since the last radio link failure or handover failure in NR;

3 >

set the rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report;

3 >

discard the rlf-Report from VarRLF-Report upon successful delivery of the UEInformationResponse message confirmed by lower layers;

2 >

else if the UE is capable of cross-RAT RLF reporting as defined in TS 38.306 and has radio link failure information or handover failure information available in VarRLF-Report of TS 36.331 and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331:

3 >

set timeSinceFailure in VarRLF-Report of TS 36.331 to the time that elapsed since the last radio link failure or handover failure in EUTRA;

3 >

set failedPCellId-EUTRA in the rlf-Report in the UEInformationResponse message to indicate the PCell in which RLF was detected or the source PCell of the failed handover in the VarRLF-Report of TS 36.331;

3 >

set the measResult-RLF-Report-EUTRA in the rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report of TS 36.331;

3 >

discard the rlf-Report from VarRLF-Report of TS 36.331 upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1 >

if connEstFailReportReq is set to true and the UE has connection establishment failure or connection resume failure information in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList:

2 >

set timeSinceFailure in VarConnEstFailReport to the time that elapsed since the last connection establishment failure or connection resume failure in NR;

2 >

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

2 >

if the UE supports multiple CEF report:

3 >

for each connEstFailReport in the connEstFailReportList in VarConnEstFailReportList:

4 >

set timeSinceFailure to the time that elapsed since the associated connection establishment failure or connection resume failure in NR;

2 >

for each connEstFailReport in the connEstFailReportList in the UEInformationResponse message, set the value to the value of connEstFailReport in VarConnEstFailReport in VarConnEstFailReportList;

2 >

discard the connEstFailReport from VarConnEstFailReport and VarConnEstFailReportList upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1 >

if the mobilityHistoryReportReq is set to true:

2 >

include the mobilityHistoryReport and set it to include visitedCellInfoList from VarMobilityHistoryReport;

2 >

include in the mobilityHistoryReport an entry for the current PCell, possibly after removing the oldest entry if required, and set its fields as follows:

3 >

set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current PCell:

3 >

set field timeSpent to the time spent in the current PCell;

3 >

if the UE supports PSCell mobility history information and if visitedPSCellInfoList is present in VarMobilityHistoryReport:

4 >

for the newest entry of the PCell in the mobilityHistoryReport, include visitedPSCellInfoList from VarMobilityHistoryReport;

4 >

if the UE is configured with a PSCell:

5 >

for the newest entry of the PCell in the mobilityHistoryReport, include the current PSCell information in the visitedPSCellInfoListReport, possibly after removing the oldest PSCell entry of a PCell in the mobilityHistoryReport, if required, and set its fields as follows:

6 >

set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current PSCell:

6 >

set field timeSpent to the time spent in the current PSCell while being connected to the current PCell;

4 >

else:

5 >

for the newest entry of the PCell in the mobilityHistoryReport, include a new entry in the visitedPSCellInfoListReport, possibly after removing the oldest PSCell entry of a PCell in the mobilityHistoryReport, if required, and set its fields as follows:

6 >

set field timeSpent to the time spent without PSCell in the current PCell since last PSCell release since connected to the current PCell in RRC_CONNECTED;

3 >

else if the UE supports PSCell mobility history information:

4 >

if the UE is configured with a PSCell:

5 >

6 >

set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current PSCell:

6 >

set field timeSpent to the time spent in the current PSCell while being connected to the current PCell;

4 >

else:

5 >

6 >

set field timeSpent to the time spent without PSCell in the current PCell since connected to the current PCell in RRC_CONNECTED;

1 >

if the successHO-ReportReq is set to true and if the UE has successful handover related information available in VarSuccessHO-Report and if the RPLMN is included in the plmn-IdentityList stored in VarSuccessHO-Report:

2 >

if the successHO-Report in the VarSuccessHO-Report concerns a DAPS handover and if a PDCP PDU has been received from the source cell of the concerned HO and a non-duplicated PDCP PDU has been received from the target cell of the concerned HO:

3 >

set upInterruptionTimeAtHO in VarSuccessHO-Report to include the time elapsed between the time of arrival of the last PDCP PDU received from the source cell of the concerned handover and the time of arrival of the first non-duplicate PDCP PDU received from the target cell of the concerned handover, as measured at the time of arrival of the first non-duplicate PDCP PDU received from the target cell;

2 >

set the successHO-Report in the UEInformationResponse message to the value of successHO-Report in the VarSuccessHO-Report, if available;

2 >

discard the VarSuccessHO-Report upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1 >

if the coarseLocationRequest is set to true:

2 >

include coarseLocationInfo, if available;

1 >

if the logMeasReport is included in the UEInformationResponse:

2 >

submit the UEInformationResponse message to lower layers for transmission via SRB2;

2 >

discard the logged measurement entries included in the logMeasInfoList from VarLogMeasReport upon successful delivery of the UEInformationResponse message confirmed by lower layers;

1 >

else:

2 >

submit the UEInformationResponse message to lower layers for transmission via SRB1.

5.7.10.4 Actions upon successful completion of a random-access procedure or on completion of a request of on-demand system information p. 272

Upon successfully performing random-access procedure initialized with 4-step or 2-step RA type, or upon failed or successfully completed on-demand system information acquisition procedure in RRC_IDLE or RRC_INACTIVE state, the UE shall:

1 >

if the RPLMN or the PLMN selected by upper layers (see TS24.501 [23]) from the PLMN(s) included in the plmn-IdentityList in SIB1 is not included in plmn-IdentityList stored in a non-empty VarRA-Report:

2 >

clear the information included in VarRA-Report;

1 >

if the number of RA-Report entries stored in the ra-ReportList in VarRA-Report is less than maxRAReport:

2 >

if the number of PLMN entries in plmn-IdentityList stored in VarRA-Report is less than maxPLMN; or

2 >

if the number of PLMN entries in plmn-IdentityList stored in VarRA-Report is equal to maxPLMN and the list of EPLMNs is subset of or equal to the plmn-IdentityList stored in VarRA-Report:

3 >

append the following contents associated to the successfully completed random-access procedure or the failed or successfully completed on-demand system information acquisition procedure as a new entry in the VarRA-Report:

4 >

if the list of EPLMNs has been stored by the UE:

5 >

set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN) without exceeding the limit of maxPLMN;

4 >

else:

5 >

set the plmn-Identity, in plmn-IdentityList, to the PLMN selected by upper layers (see TS 24.501) from the PLMN(s) included in the plmn-IdentityInfoList in SIB1;

4 >

set the cellId to the global cell identity and the tracking area code, if available, otherwise to the physical cell identity and carrier frequency of the cell in which the corresponding random-access preamble was transmitted;

4 >

if the UE supports spCell ID indication:

5 >

if the corresponding random-access procedure was performed on an SCell of MCG:

6 >

set the spCellId to the global cell identity of the PCell;

5 >

if the corresponding random-access procedure was performed on an SCell of SCG; or

5 >

if the corresponding random-access procedure was performed on PSCell:

6 >

set the spCellId to the global cell identity of the PSCell, if available, otherwise, set the spCellId to the global cell identity of the PCell;

4 >

set the raPurpose to include the purpose of triggering the random-access procedure;

4 >

set the ra-InformationCommon as specified in clause 5.7.10.5.

The UE may discard the random access report information, i.e. release the UE variable VarRA-Report, 48 hours after the last successful random access procedure or the failed or successfully completed on-demand system information acquisition procedure related information is added to the VarRA-Report.

5.7.10.5 RA information determination p. 273

The UE shall set the content in ra-InformationCommon as follows:

1 >

set the absoluteFrequencyPointA to indicate the absolute frequency of the reference resource block associated to the random-access resources used in the random-access procedure;

1 >

set the locationAndBandwidth and subcarrierSpacing associated to the UL BWP of the random-access resources used in the random-access procedure;

1 >

if contention based random-access resources are used in the random-access procedure:

2 >

set the msgA_RO-FrequencyStart and msgA-RO-FDM and msgA-SubcarrierSpacing associated to the 2 step random- access resources if used in the random-access procedure;

2 >

if msgA-SubcarrierSpacing associated to the 2 step random-access resources used in the random-access procedure is available:

3 >

set the msgA-SubcarrierSpacing associated to the 2 step random-access resources used in the random-access procedure;

2 >

else if only 2 step random-access resources are available in the UL BWP used in the random-access procedure:

3 >

set the msgA-SCS-From-prach-ConfigurationIndex to the subcarrier spacing as derived from the msgA-PRACH-ConfigurationIndex used in the 2-step random-access procedure;

2 >

else:

3 >

set the msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure;

2 >

set the msg1-FrequencyStart associated to the 4 step random-access resources if used in the random-access procedure, and if its value is different from the value of msgA-RO-FrequencyStart if it is included in the ra-InformationCommon;

2 >

set the msg1-FDM associated to the 4 step random-access resources if used in the random-access procedure, and if its value is different from the value of msgA-RO-FDMCFRA if it is included in the ra-InformationCommon;

2 >

if msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure is available, and if its value is different from the value of msgA-SubcarrierSpacing if it is included in the ra-InformationCommon:

3 >

set the msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure;

2 >

else:

3 >

set the msg1-SCS-From-prach-ConfigurationIndex to the subcarrier spacing as derived from the prach-ConfigurationIndex used in the 4-step random-access procedure, and if its value is different from the value of msgA-SCS-From-prach-ConfigurationIndex if it is included in the ra-InformationCommon;

1 >

if contention free random-access resources are used in the random-access procedure:

2 >

set the msg1-FrequencyStartCFRA and msg1-FDMCFRA associated to the 4 step random-access resources if used in the random-access procedure;

2 >

if msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure is available:

3 >

set the msg1-SubcarrierSpacingCFRA associated to the 4 step random-access resources used in the random-access procedure;

2 >

else:

3 >

set the msg1-SCS-From-prach-ConfigurationIndexCFRA to the subcarrier spacing as derived from the prach-ConfigurationIndex used in the 4 step random-access procedure;

2 >

set the msgA-RO-FrequencyStartCFRA and msgA-RO-FDMCFRA associated to the 2 step contention free random access resources if used in the random-access procedure;

2 >

set the msgA-MCS, the nrofPRBs-PerMsgA-PO, the msgA-PUSCH-TimeDomainAllocation, the frequencyStartMsgA-PUSCH, the nrofMsgA-PO-FDM associated to the 2 step random-access resources if used in the random-access procedure;

2 >

if msgA-SubcarrierSpacing associated to the 2 step random-access resources used in the random-access procedure is available:

3 >

set the msgA-SubcarrierSpacing associated to the 2 step random-access resources used in the random-access procedure;

2 >

else if only 2 step random-access resources are available in the UL BWP used in the random-access procedure:

3 >

set the msgA-SCS-From-prach-ConfigurationIndex to the subcarrier spacing as derived from the msgA-PRACH-ConfigurationIndex used in the 2-step random-access procedure;

2 >

else:

3 >

set the msg1-SubcarrierSpacing associated to the 4 step random-access resources used in the random-access procedure;

1 >

if the random access procedure is initialized with RA_TYPE set to 2-stepRA as described in TS 38.321:

2 >

set the dlPathlossRSRP to the measeured RSRP of the DL pathloss reference obtained at the time of RA_Type selection stage of the initialization of the RA procedure as captured in TS 38.321;

2 >

if the configuration for the random access msgA-TransMax was configured in RACH-ConfigDedicated for this random access procedure, and ra-Purpose is set to reconfigurationWithSync:

3 >

set msgA-TransMax to the value of msgA-TransMax in RACH-ConfigDedicated;

2 >

else if msgA-TransMax was configured in RACH-ConfigCommonTwoStepRA:

3 >

set msgA-TransMax to the value of msgA-TransMax in RACH-ConfigCommonTwoStepRA;

2 >

set the msgA-PUSCH-PayloadSize to the size of the overall payload available in the UE buffer at the time of initiating the 2 step RA procedure;

1 >

if the purpose of the random access procedure is to request on-demand system information (i.e., if the raPurpose is set to requestForOtherSI or msg3RequestForOtherSI):

2 >

set the intendedSIBs to indicate the SIB(s) the UE wanted to receive as a result of the SI request;

2 >

set the ssbsForSI-Acquisition to indicate the SSB(s) used to receive the SI message;

2 >

if the on-demand system information acquisition was successful:

3 >

set the onDemandSISuccess to true;

1 >

set the parameters associated to individual random-access attempt in the chronological order of attempts in the perRAInfoList as follows:

2 >

if the random-access resource used is associated to a SS/PBCH block, set the associated random-access parameters for the successive random-access attempts associated to the same SS/PBCH block for one or more random-access attempts as follows:

3 >

set the ssb-Index to include the SS/PBCH block index associated to the used random-access resource;

3 >

set the numberOfPreamblesSentOnSSB to indicate the number of successive random-access attempts associated to the SS/PBCH block;

3 >

for each random-access attempt performed on the random-access resource, include the following parameters in the chronological order of the random-access attempt:

4 >

if the random-access attempt is performed on the contention based random-access resource and if raPurpose is not equal to 'requestForOtherSI', include contentionDetected as follows:

5 >

if contention resolution was not successful as specified in TS 38.321 for the transmitted preamble:

6 >

set the contentionDetected to true;

5 >

else:

6 >

set the contentionDetected to false;

4 >

if the random access attempt is a 2-step random access attempt:

5 >

if fallback from 2-step random access to 4-step random access occurred during the random access attempt:

6 >

set fallbackToFourStepRA to true;

4 >

if the random-access attempt is performed on the contention based random-access resource; or

4 >

if the random-access attempt is performed on the contention free random-access resource and if the random-access procedure was initiated due to the PDCCH ordering:

5 >

if the random access attempt is a 4-step random access attempt and the SS/PBCH block RSRP of the SS/PBCH block corresponding to the random-access resource used in the random-access attempt is above rsrp-ThresholdSSB; or

5 >

if the random access attempt is a 2-step random access attempt and the SS/PBCH block RSRP of the SS/PBCH block corresponding to the random-access resource used in the random-access attempt is above msgA-RSRP-ThresholdSSB:

6 >

set the dlRSRPAboveThreshold to true;

5 >

else:

6 >

set the dlRSRPAboveThreshold to false;

2 >

else if the random-access resource used is associated to a CSI-RS, set the associated random-access parameters for the successive random-access attempts associated to the same CSI-RS for one or more random-access attempts as follows:

3 >

set the csi-RS-Index to include the CSI-RS index associated to the used random-access resource;

3 >

set the numberOfPreamblesSentOnCSI-RS to indicate the number of successive random-access attempts associated to the CSI-RS.

5.7.10.6 Actions for the successful handover report determination |R17| p. 275

The UE shall for the PCell:

1 >

if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync; or

1 >

if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or

1 >

if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync; or

1 >

if sourceDAPS-FailureReporting is included in the successHO-Config before executing the last reconfiguration with sync and is set to true and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

2 >

store the successful handover information in VarSuccessHO-Report and determine the content in VarSuccessHO-Report as follows:

3 >

clear the information included in VarSuccessHO-Report, if any;

3 >

set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN);

3 >

set the c-RNTI to the C-RNTI assigned by the target PCell of the handover;

3 >

for the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied:

4 >

set the sourceCellID in sourceCellInfo to the global cell identity and tracking area code, if available, of the source PCell;

4 >

set the sourceCellMeas in sourceCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the source PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message;

4 >

set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PCell collected up to the moment the UE sends RRCReconfigurationComplete message;

4 >

if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

5 >

set the rlf-InSourceDAPS in sourceCellInfo to true;

3 >

for the target PCell indicated in the last applied RRCReconfiguration message including reconfigurationWithSync:

4 >

set the targetCellID in targetCellInfo to the global cell identity and tracking area code, if available, of the target PCell;

4 >

set the targetCellMeas in targetCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PCell based on the available SSB and CSI-RS measurements collected up to the moment the UE sends RRCReconfigurationComplete message;

4 >

set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PCell collected up to the moment the UE sends RRCReconfigurationComplete message;

4 >

if the last applied RRCReconfiguration message including reconfigurationWithSync was included in the stored condRRCReconfig:

5 >

set the timeSinceCHO-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PCell and the reception of the last conditionalReconfiguration including the condRRCReconfig of the target PCell in the source PCell;

3 >

if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconfiguration message including the reconfigurationWithSync, is greater than thresholdPercentageT304 if included in the successHO-Config received before executing the last reconfiguration with sync:

4 >

set t304-cause in shr-Cause to true;

4 >

set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PCell, as specified in clause 5.7.10.5;

3 >

if the ratio between the value of the elapsed time of the timer T310 and the configured value of the T310 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT310 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync:

4 >

set t310-cause in shr-Cause to true;

3 >

if the T312 associated to the measurement identity of the target cell was running at the time of initiating the execution of the reconfiguration with sync procedure and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the T312 timer, configured while the UE was connected to the source PCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312 included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync:

4 >

set t312-cause in shr-Cause to true;

3 >

if sourceDAPS-FailureReporting included in the successHO-Config if configured by the source PCell before executing the last reconfiguration with sync is set to true, and if the last executed handover was a DAPS handover and if an RLF occurred at the source PCell during the DAPS handover while T304 was running:

4 >

set sourceDAPS-Failure in shr-Cause to true;

3 >

for each of the measObjectNR, configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied:

4 >

if measurements are available for the measObjectNR:

5 >

if the SS/PBCH block-based measurement quantities are available:

6 >

set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message;

6 >

for each neighbour cell included, include the optional fields that are available;

5 >

if the CSI-RS measurement quantities are available:

6 >

set the measResultListNR in measResultNeighCells to include all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE sends the RRCReconfigurationComplete message;

6 >

for each neighbour cell included, include the optional fields that are available;

3 >

for each of the measObjectEUTRA, configured by the source PCell in which the last RRCReconfiguration message including reconfigurationWithSync was applied:

4 >

if measurements are available for the measObjectEUTRA:

5 >

set the measResultListEUTRA in measResultNeighCells to include the best measured cells ordered such that the cell with highest RSRP is listed first if RSRP measurement results are available, otherwise the cell with highest RSRQ is listed first, based on measurements collected up to the moment the UE sends the RRCReconfigurationComplete message;

5 >

for each neighbour cell included, include the optional fields that are available;

3 >

for each of the neighbour cells included in measResultNeighCells:

4 >

if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration configured by the source PCell, in which the last RRCReconfiguration message including reconfigurationWithSync was applied:

5 >

set the choCandidate to true in measResultNR;

3 >

if available, set the locationInfo as in clause 5.3.3.7;

1 >

release successHO-Config configured by the source PCell and thresholdPercentageT304 if configured by the target PCell.

The UE may discard the successful handover information, i.e., release the UE variable VarSuccessHO-Report, 48 hours after the last successful handover information is added to the VarSuccessHO-Report.

5.7.12 IAB Other Information |R16| p. 278

5.7.12.1 General p. 278

Reproduction of 3GPP TS 38.331, Fig. 5.7.12.1-1: IAB Other Information procedure

Figure 5.7.12.1-1: IAB Other Information procedure

The IAB Other Information procedure is used by IAB-MT to request the IAB-donor-CU to allocate IP address or inform the IAB-donor-CU of the IP address for the collocated IAB-DU.

5.7.12.2 Initiation p. 278

Upon initiation of the procedure, the IAB-MT shall:

1 >

initiate transmission of the IABOtherInformation message in accordance with clause 5.7.12.3;

5.7.12.3 Actions related to transmission of IABOtherInformation message p. 279

The IAB-MT shall set the contents of IABOtherInformation message as follows:

1 >

if the procedure is used to request IP addresses:

2 >

if IPv4 addresses are requested:

3 >

set the iab-IPv4-AddressNumReq to the number of IPv4 addresses requested per specific usage;

2 >

if IPv6 addresses or IPv6 address prefixes are requested:

3 >

if IPv6 addresses are requested:

4 >

set the iab-IPv6-AddressNumReq to the number of IPv6 addresses requested per specific usage;

3 >

else if IPv6 address prefixes are requested:

4 >

set the iab-IPv6-AddressPrefixReq to true per specific usage;

1 >

if the procedure is used to report IP addresses:

2 >

if IPv4 addresses are reported:

3 >

include iPv4-Address in iab-IPv4-AddressReport, and for each IP address included:

4 >

if IPv4 addresses are used for F1-C traffic:

5 >

include these addresses in f1-C-Traffic-IP-Address.

4 >

if IPv4 addresses are used for F1-U traffic:

5 >

include these addresses in f1-U-Traffic-IP-Address.

4 >

if IPv4 address are used for non-F1 traffic:

5 >

include these addresses in non-f1-Traffic-IP-Address.

4 >

if IPv4 addresses are used for all traffic:

5 >

include these addresses in all-Traffic-IAB-IP-Address.

2 >

if IPv6 addresses or IPv6 address prefixes are reported:

3 >

if IPv6 addresses are reported:

4 >

include iPv6-Address in iab-IPv6-AddressReport, and for each IP address included;

5 >

if IPv6 addresses are used for F1-C traffic:

6 >

include these addresses in f1-C-Traffic-IP-Address.

5 >

if IPv6 addresses are used for F1-U traffic:

6 >

include these addresses in f1-U-Traffic-IP-Address.

5 >

if IPv6 addresses are used for non-F1 traffic:

6 >

include these addresses in non-f1-Traffic-IP-Address.

5 >

if IPv6 addresses are used for all traffic:

6 >

include these addresses in all-Traffic-IAB-IP-Address.

3 >

else if IPv6 address prefixes are reported:

4 >

include these iPv6-Prefix in iab-IPv6-PrefixReport, and for each IP address prefix included;

5 >

if this IPv6 address prefix is used for F1-C traffic:

6 >

include this prefix in f1-C-Traffic-IP-Address.

5 >

if this IPv6 address prefix is used for F1-U traffic:

6 >

include this prefix in f1-U-Traffic-IP-Address.

5 >

if this IPv6 address prefix is used for non-F1 traffic:

6 >

include this prefix in non-f1-Traffic-IP-Address.

5 >

if this IPv6 address prefix is used for all traffic:

6 >

include this prefix in all-Traffic-IAB-IP-Address.

1 >

if the IAB-MT is in (NG)EN-DC, or

1 >

if the IAB-MT is in NR-DC and the IAB Other Information procedure is towards the IAB-donor-CU in the SN:

2 >

if SRB3 is configured:

3 >

submit the IABOtherInformation message via SRB3 to lower layers for transmission;

2 >

else if the IAB-MT is in (NG)EN-DC:

3 >

submit the IABOtherInformation message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331;

2 >

else:

3 >

submit the IABOtherInformation message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3;

1 >

else:

2 >

submit the IABOtherInformation message to lower layers for transmission.

5.7.13 RLM/BFD relaxation |R17| p. 280

In case both low mobility criterion and good serving cell criterion are configured for RLM/BFD relaxation, the UE is allowed to perform RLM and/or BFD relaxation according to requirements specified in TS 38.133 when both relaxed measurement criterion for low mobility and relaxed measurement criterion for good serving cell quality are met.

In case only the good serving cell quality criterion is configured for RLM/BFD relaxation, the UE is allowed to perform RLM and/or BFD relaxation according to requirements specified in TS 38.133 when the relaxed measurement criterion for good serving cell quality is met.

5.7.13.1 Relaxed measurement criterion for low mobility p. 280

The relaxed measurement criterion for UE with low mobility in RRC_CONNECTED is fulfilled when:

(SS-RSRP_Ref - SS-RSRP) <S_{SearchDeltaP-Connected},

Where:

SS-RSRP = current L3 RSRP measurement of the SpCell based on SSB (dB).
SS-RSRP_Ref = reference L3 RSRP measurement of the SpCell based on SSB (dB), set as follows:
After receiving low mobility criterion configuration, or
After MAC of the CG successfully completes a Random Access procedure after applying a reconfigurationWithSync in spCellConfig of the CG while low mobility criterion is configured, or
If (SS-RSRP - SS-RSRP_Ref) > 0, or
If the relaxed measurement criterion has not been met for T_{SearchDeltaP-Connected}:
- The UE shall set the value of SS-RSRPRef to the current SS-RSRP value of the SpCell.

5.7.13.2 Relaxed measurement criterion for good serving cell quality p. 281

The relaxed measurement criterion of good serving cell quality for RLM is fulfilled when the downlink radio link quality on the configured RLM-RS resource is evaluated to be better than the threshold Q_in+XdB, wherein

Q_in is specified in clause 8.1 of TS 38.133.
X is the parameter offset in goodServingCellEvaluationRLM.
The relaxed measurement criterion of good serving cell quality for BFD is fulfilled when the downlink radio link quality on the configured BFD-RS resource is evaluated to be better than the threshold Q_in+XdB, wherein
Q_in is specified in clause 8.1 of TS 38.133.
X is the parameter offset in goodServingCellEvaluationBFD.

5.7.14 UE Positioning Assistance Information |R17| p. 281

5.7.14.1 General p. 281

Reproduction of 3GPP TS 38.331, Fig. 5.7.14.1-1: UE Positioning Assistance Information procedure

Figure 5.7.14.1-1: UE Positioning Assistance Information procedure

The UE Positioning Assistance Information procedure is used by UE to report the UE Positioning Assistance Information. The UE reports the association between UL-SRS resources for positioning and the UE Tx TEG ID as defined in TS 38.305.

5.7.14.2 Initiation p. 281

A UE capable of providing the association between UL SRS Resource for positioning and UE Tx TEG ID in RRC_CONNECTED may initiate the procedure upon being configured to provide this association information.

Upon initiation of the procedure, the UE shall:

1 >

initiate transmission of the UEPositioningAssistanceInfo message in accordance with clause 5.7.14.3 to provide the association.

5.7.14.3 Actions related to transmission of UEPositioningAssistanceInfo message p. 281

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

1 >

if ue-TxTEG-RequestUL-TDOA-Config in RRCReconfiguration message is configured with periodicReporting:

2 >

for all the association changes store ue-TxTEG-Association corresponding to each ue-TxTEG-ID with nr-TimeStamp;

2 >

include the results in ue-TxTEG-AssociationList in the UEPositioningAssistanceInfo message on expiry of each configured period;

2 >

optionally include one ue-TxTEG-TimingErrorMarginValue for each UEPositioningAssistanceInfo message;

1 >

else if ue-TxTEG-RequestUL-TDOA-Config in RRCReconfiguration message is configured with oneShot:

2 >

identify the ue-TxTEG-Association corresponding to each ue-TxTEG-ID with nr-TimeStamp;

2 >

include the results in ue-TxTEG-AssociationList in the UEPositioningAssistanceInfo message only one time;

2 >

optionally include one ue-TxTEG-TimingErrorMarginValue for each UEPositioningAssistanceInfo message.

The UE shall submit the UEPositioningAssistanceInfo message to lower layers for transmission.

5.7.15 Void

5.7.16 Application layer measurement reporting |R17| p. 282

5.7.16.1 General p. 282

Reproduction of 3GPP TS 38.331, Fig. 5.7.16.1-1: Application layer measurement reporting

Figure 5.7.16.1-1: Application layer measurement reporting

The purpose of this procedure is to send application layer measurement reports to the network.

5.7.16.2 Initiation p. 282

A UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when configured with application layer measurement, i.e. when appLayerMeasConfig and SRB4 have been configured by the network.

Upon initiating the procedure, the UE shall:

1 >

for each measConfigAppLayerId received from upper layers:

2 >

if the UE AS has received application layer measurement report container from upper layers which has not been transmitted; and

2 >

if the application layer measurement reporting has not been suspended for the measConfigAppLayerId associated with the application layer measurement report container according to clause 5.3.5.13d:

3 >

set the measReportAppLayerContainer in the MeasurementReportAppLayer message to the received value in the application layer measurement report container;

2 >

set the measConfigAppLayerId in the MeasurementReportAppLayer message to the value of the measConfigAppLayerId received together with application layer measurement report information;

2 >

if session start or stop information has been received from upper layers for the measConfigAppLayerId:

3 >

set the appLayerSessionStatus in the MeasurementReportAppLayer message to the received value of session start or stop information;

2 >

if RAN visible application layer measurement report has been received from upper layers:

3 >

for each appLayerBufferLevel value in the received RAN visible application layer measurement report:

4 >

set the appLayerBufferLevel values in the appLayerBufferLevelList in the MeasurementReportAppLayer message to the buffer level values received from the upper layer in the order with the first appLayerBufferLevel value set to the newest received buffer level value, the second appLayerBufferLevel value set to the second newest received buffer level value, and so on until all the buffer level values received from the upper layer have been assigned or the maximum number of values have been set according to appLayerBufferLevel, if configured;

3 >

set the playoutDelayForMediaStartup in the MeasurementReportAppLayer message to the received value of playout delay for media startup in the RAN visible application layer measurement report, if any;

3 >

for each PDU session ID value indicated in the received RAN visible application layer measurement report, if any:

4 >

set the PDU-SessionID field in the pdu-SessionIdList in the MeasurementReportAppLayer message to the indicated PDU session ID value;

1 >

if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323:

2 >

if the RRC message segmentation is enabled based on the field rrc-SegAllowed received in appLayerMeasConfig:

3 >

initiate the UL message segment transfer procedure as specified in clause 5.7.7;

2 >

else:

3 >

discard the RRC message;

1 >

else:

2 >

submit the MeasurementReportAppLayer message to lower layers for transmission upon which the procedure ends.

5.7.17 Derivation of pathloss reference for TA validation of SRS for Positioning transmission and CG-SDT in RRC_INACTIVE |R17| p. 283

Upon request from lower layer for pathloss reference derivation for TA validation for SRS for Positioning transmission or CG-SDT in RRC_INACTIVE, the UE shall:

1 >

acquire SIB2, if stored version is invalid;

1 >

if nrofSS-BlocksToAverage or absThreshSS-BlocksConsolidation is not present or if absThreshSS-BlocksConsolidation is present and the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation:

2 >

derive the downlink pathloss reference RSRP for TA validation as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215;

1 >

else:

2 >

derive the downlink pathloss reference RSRP for TA validation as the linear average of the power values of up to nrofSS-BlocksToAverage of the highest beam measurement quantity values above absThreshSS-BlocksConsolidation, where each beam measurement quantity is described in TS 38.215.