5.7 Other
38.3313GPPNRProtocol specificationRadio Resource Control (RRC)Release 17TS
5.7.1 DL information transfer
5.7.1.1 General
Figure 5.7.1.1-1: DL information transfer
The purpose of this procedure is to transfer NAS dedicated information from NG-RAN to a UE in RRC_CONNECTED or to a UE in RRC_INACTIVE during SDT, or to transfer F1-C related information from IAB Donor-CU to IAB-DU via the collocated IAB-MT in RRC_CONNECTED.
5.7.1.2 Initiation
The network initiates the DL information transfer procedure whenever there is a need to transfer NAS dedicated information, or F1-C related information to an IAB-node. The network initiates the DL information transfer procedure by sending the DLInformationTransfer message.
5.7.1.3 Reception of the DLInformationTransfer by the UE
Upon receiving DLInformationTransfer message, the UE shall:
1> if dedicatedNAS-Message is included:
2> forward dedicatedNAS-Message to upper layers.
1> if referenceTimeInfo is included:
2> calculate the reference time based on the time, referenceSFN and timeInfoType if it is included;
2> calculate the uncertainty of the reference time based on the uncertainty, if uncertainty is included;
2> inform upper layers of the reference time and, if uncertainty is included, of the uncertainty;
2> ignore all further referenceTimeInfo received in SIB9, if any.
1> if sib9Fallback is included:
2> apply referenceTimeInfo in SIB9.
1> if rxTxTimeDiff-gNB is included:
2> calculate the propagation delay based on the UE Rx-Tx time difference measurement and the received Rx-Tx time difference measurement at the gNB;
2> inform upper layers of the propagation delay.
1> if ta-PDC is set to activate:
2> inform upper layers of the propagation delay determined by the accumulated Timing Advance commands.
Upon receiving DLInformationTransfer message, the IAB-MT shall:
1> if dedicatedInfoF1c is included:
2> forward dedicatedInfoF1c to the collocated IAB-DU.
5.7.1a DL information transfer for MR-DC
5.7.1a.1 General
Figure 5.7.1a.1-1: DL information transfer MR-DC
The purpose of this procedure is to transfer RRC messages from the network to the UE over SRB3 (e.g. an NR RRC reconfiguration message including reconfigurationWithSync, an E-UTRA RRC connection reconfiguration message including mobilityControlInfo, an RRC connection release message, a MobilityFromNRCommand message, or a MobilityFromEUTRACommand message) during fast MCG link recovery.
5.7.1a.2 Initiation
The network initiates this procedure whenever there is a need to transfer an RRC message during fast MCG link recovery.
5.7.1a.3 Actions related to reception of DLInformationTransferMRDC message
Upon receiving the DLInformationTransferMRDC, the UE shall:
1> if the RRCReconfiguration message is included in dl-DCCH-MessageNR:
2> perform the RRC reconfiguration procedure according to 5.3.5.3;
1> else if the RRCRelease message is included in dl-DCCH-MessageNR:
2> perform the RRC release procedure according to 5.3.8;
1> else if the MobilityFromNRCommand message is included in the dl-DCCH-MessageNR:
2> perform the mobility from NR procedure according to 5.4.3.3;
1> else if the E-UTRA RRCConnectionReconfiguration message is included in dl-DCCH-MessageEUTRA:
2> perform the RRC connection reconfiguration procedure as specified in TS 36.331 [10], clause 5.3.5.4;
1> else if the E-UTRA RRCConnectionRelease message is included in dl-DCCH-MessageEUTRA:
2> perform the RRC connection release as specified in TS 36.331 [10], clause 5.3.8;
1> else if the MobilityFromEUTRACommand message is included in the dl-DCCH-MessageEUTRA:
2> perform the mobility from E-UTRA procedure as specified in TS 36.331 [10], clause 5.4.3.3;
5.7.2 UL information transfer
5.7.2.1 General
Figure 5.7.2.1-1: UL information transfer
The purpose of this procedure is to transfer NAS dedicated information from the UE to the network, or to transfer F1-C related information from IAB-DU to IAB Donor-CU via the collocated IAB-MT in RRC CONNECTED.
5.7.2.2 Initiation
A UE in RRC_CONNECTED or a UE in RRC_INACTIVE during SDT initiates the UL information transfer procedure whenever there is a need to transfer NAS dedicated information. The UE initiates the UL information transfer procedure by sending the ULInformationTransfer message. In addition, an IAB-MT in RRC CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer F1-C related information. When F1-C related information has to be transferred, the IAB-MT shall initiate the procedure only if SRB2 or split SRB2 is established.
5.7.2.3 Actions related to transmission of ULInformationTransfer message
The UE shall set the contents of the ULInformationTransfer message as follows:
1> if the upper layer provides NAS PDU:
2> set the dedicatedNAS-Message to include the information received from upper layers;
1> for the IAB-MT, if there is a need to transfer F1-C related information:
2> include the dedicatedInfoF1c;
1> submit the ULInformationTransfer message to lower layers for transmission, upon which the procedure ends.
5.7.2.4 Failure to deliver ULInformationTransfer message
The UE shall:
1> if AS security is not started and radio link failure occurs before the successful delivery of ULInformationTransfer messages has been confirmed by lower layers; or
1> if PDCP re-establishment or release/addition (e.g due to key refresh upon PCell or PSCell change, or RRC connection re-establishment, or failure of resume procedure initiated for SDT) occurs on an SRB on which ULInformationTransfer messages were submitted for transmission but successful delivery of these messages was not confirmed by lower layers:
2> inform upper layers about the possible failure to deliver the information contained in the concerned ULInformationTransfer messages, unless the messages only include dedicatedInfoF1c.
5.7.2a UL information transfer for MR-DC
5.7.2a.1 General
Figure 5.7.2a.1-1: UL information transfer MR-DC
The purpose of this procedure is to transfer MR-DC dedicated information from the UE to the network e.g. the NR or E-UTRA RRC MeasurementReport, FailureInformation, UEAssistanceInformation, RRCReconfigurationComplete, MCGFailureInformation, or IABOtherInformation message.
5.7.2a.2 Initiation
A UE in RRC_CONNECTED initiates the UL information transfer for MR-DC procedure whenever there is a need to transfer MR-DC dedicated information. I.e. the procedure is not used during an RRC connection reconfiguration involving NR or E-UTRA connection reconfiguration, in which case the MR DC information is piggybacked to the RRCReconfigurationComplete message, except in the case the UE executes an intra-SN CPC.
5.7.2a.3 Actions related to transmission of ULInformationTransferMRDC message
The UE shall set the contents of the ULInformationTransferMRDC message as follows:
1> if there is a need to transfer MR-DC dedicated information related to NR:
2> set the ul-DCCH-MessageNR to include the NR MR-DC dedicated information to be transferred (e.g., NR RRC MeasurementReport, UEAssistanceInformation, FailureInformation, RRCReconfigurationComplete, MCGFailureInformation, or IABOtherInformation message);
1> else if there is a need to transfer MR-DC dedicated information related to E-UTRA:
2> set the ul-DCCH-MessageEUTRA to include the E-UTRA MR-DC dedicated information to be transferred (e.g., E-UTRA RRC MeasurementReport, or MCGFailureInformation message);
1> submit the ULInformationTransferMRDC message to lower layers for transmission, upon which the procedure ends.
5.7.2b UL transfer of IRAT information
5.7.2b.1 General
Figure 5.7.2b.1-1: UL transfer of IRAT information
The purpose of this procedure is to transfer from the UE to NR MCG dedicated information terminated at the NR MCG but specified by another RAT e.g. the E-UTRA MeasurementReport message, the E-UTRA SidelinkUEInformation message or the E-UTRA UEAssistanceInformation message. The specific information transferred in this message is set in accordance with:
– the procedure specified in 5.6.10 of TS 36.331 [10] for E-UTRA UEAssistanceInformation message;
– the procedure specified in 5.10.2 of TS 36.331 [10] for E-UTRA SidelinkUEInformation message;
– the procedure specified in 5.5.5 of TS 36.331 [10] for E-UTRA MeasurementReport Message.
5.7.2b.2 Initiation
A UE in RRC_CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer dedicated inter-RAT information as specified in TS 36.331 [10].
5.7.2b.3 Actions related to transmission of ULInformationTransferIRAT message
The UE shall set the contents of the ULInformationTransferIRAT message as follows:
1> if there is a need to transfer dedicated LTE information related to V2X sidelink communications:
2> set the ul-DCCH-MessageEUTRA to include the V2X sidelink communication information to be transferred (e.g. the E-UTRA RRC MeasurementReport message, the E-UTRA RRC SidelinkUEInformation message, or the E-UTRA RRC UEAssistanceInformation message);
1> submit the ULInformationTransferIRAT message to lower layers for transmission, upon which the procedure ends;
5.7.3 SCG failure information
5.7.3.1 General
Figure 5.7.3.1-1: SCG failure information
The purpose of this procedure is to inform E-UTRAN or NR MN about an SCG failure the UE has experienced i.e. SCG radio link failure, beam failure of the PSCell while the SCG is deactivated, failure of SCG reconfiguration with sync, SCG configuration failure for RRC message on SRB3, SCG integrity check failure, and consistent uplink LBT failures on PSCell for operation with shared spectrum channel access.
5.7.3.2 Initiation
A UE initiates the procedure to report SCG failures when neither MCG nor SCG transmission is suspended and when one of the following conditions is met:
1> upon detecting radio link failure for the SCG, in accordance with clause 5.3.10.3;
1> upon detecting beam failure of the PSCell while the SCG is deactivated, in accordance with TS 38.321[3];
1> upon reconfiguration with sync failure of the SCG, in accordance with clause 5.3.5.8.3;
1> upon SCG configuration failure, in accordance with clause 5.3.5.8.2;
1> upon integrity check failure indication from SCG lower layers concerning SRB3.
Upon initiating the procedure, the UE shall:
1> if the procedure was not initiated due to beam failure of the PSCell while the SCG is deactivated:
2> suspend SCG transmission for all SRBs, DRBs and, if any, BH RLC channels;
2> reset SCG MAC;
1> stop T304 for the SCG, if running;
1> stop conditional reconfiguration evaluation for CPC or CPA, if configured;
1> if the UE is in (NG)EN-DC:
2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331 [10], clause 5.6.13a.
1> else:
2> initiate transmission of the SCGFailureInformation message in accordance with 5.7.3.5.
5.7.3.3 Failure type determination for (NG)EN-DC
The UE shall set the SCG failure type as follows:
1> if the UE initiates transmission of the SCGFailureInformationNR message due to T310 expiry:
2> set the failureType as t310-Expiry;
1> else if the UE initiates transmission of the SCGFailureInformationNR message due to T312 expiry:
2> set the failureType as any value and set the failureType-v1610 as t312-Expiry;
1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide reconfiguration with sync failure information for an SCG:
2> set the failureType as synchReconfigFailureSCG;
1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide random access problem indication from SCG MAC:
2> if the random access procedure was initiated for beam failure recovery:
3> set the failureType as randomAccessProblem and set the failureType-v1610 as beamFailureRecoveryFailure;
2> else:
3> set the failureType as randomAccessProblem;
1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide indication from SCG RLC that the maximum number of retransmissions has been reached:
2> set the failureType as rlc-MaxNumRetx;
1> else if the UE initiates transmission of the SCGFailureInformationNR message due to SRB3 integrity check failure:
2> set the failureType as srb3-IntegrityFailure;
1> else if the UE initiates transmission of the SCGFailureInformationNR message due to Reconfiguration failure of NR RRC reconfiguration message:
2> set the failureType as scg-reconfigFailure;
1> else if the UE initiates transmission of the SCGFailureInformationNR message due to consistent uplink LBT failures:
2> set the failureType as any value and set the failureType-v1610 as scg-lbtFailure;
1> else if connected as an IAB-node and the SCGFailureInformationNR is initiated due to the reception of a BH RLF indication on BAP entity from the SCG:
2> set the failureType as any value and set failureType-v1610 as bh-RLF.
1> else if the UE initiates transmission of the SCGFailureInformationNR message due to beam failure of the PSCell while the SCG is deactivated:
2> set the failureType as any value and set failureType-v1610 as beamFailure.
5.7.3.4 Setting the contents of MeasResultSCG-Failure
The UE shall set the contents of the MeasResultSCG-Failure as follows:
1> for each MeasObjectNR configured on NR SCG for which a measId is configured and measurement results are available:
2> include an entry in measResultPerMOList;
2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb:
3> set ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR;
2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs:
3> set refFreqCSI-RS to the value indicated by refFreqCSI-RS as included in the associated measurement object;
2> if a serving cell is associated with the MeasObjectNR:
3> set measResultServingCell to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14];
2> set the measResultNeighCellList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows;
3> ordering the cells with sorting as follows:
4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS;
4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR;
3> for each neighbour cell included:
4> include the optional fields that are available.
NOTE: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.
2> if available, set the locationInfo as in 5.3.3.7.:
5.7.3.5 Actions related to transmission of SCGFailureInformation message
The UE shall set the contents of the SCGFailureInformation message as follows:
1> if the UE initiates transmission of the SCGFailureInformation message due to T310 expiry:
2> set the failureType as t310-Expiry;
1> else if the UE initiates transmission of the SCGFailureInformation message due to T312 expiry:
2> set the failureType as other and set the failureType-v1610 as t312-Expiry;
1> else if the UE initiates transmission of the SCGFailureInformation message to provide reconfiguration with sync failure information for an SCG:
2> set the failureType as synchReconfigFailureSCG;
1> else if the UE initiates transmission of the SCGFailureInformation message to provide random access problem indication from SCG MAC:
2> if the random access procedure was initiated for beam failure recovery:
3> set the failureType as other and set the failureType-v1610 as beamFailureRecoveryFailure;
2> else:
3> set the failureType as randomAccessProblem;
1> else if the UE initiates transmission of the SCGFailureInformation message to provide indication from SCG RLC that the maximum number of retransmissions has been reached:
2> set the failureType as rlc-MaxNumRetx;
1> else if the UE initiates transmission of the SCGFailureInformation message due to SRB3 IP check failure:
2> set the failureType as srb3-IntegrityFailure;
1> else if the UE initiates transmission of the SCGFailureInformation message due to Reconfiguration failure of NR RRC reconfiguration message:
2> set the failureType as scg-reconfigFailure;
1> else if the UE initiates transmission of the SCGFailureInformation message due to consistent uplink LBT failures:
2> set the failureType as other and set the failureType-v1610 as scg-lbtFailure;
1> else if connected as an IAB-node and the SCGFailureInformation is initiated due to the reception of a BH RLF indication on BAP entity from the SCG:
2> set the failureType as other and set failureType-v1610 as bh-RLF;
1> else if the UE initiates transmission of the SCGFailureInformation message due to beam failure of the PSCell while the SCG is deactivated:
2> set the failureType as other and set failureType-v1610 as beamFailure;
1> include and set MeasResultSCG-Failure in accordance with 5.7.3.4;
1> for each MeasObjectNR configured by a MeasConfig associated with the MCG, and for which measurement results are available:
2> include an entry in measResultFreqList;
2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb:
3> set ssbFrequency in measResultFreqList to the value indicated by ssbFrequency as included in the MeasObjectNR;
2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs:
3> set refFreqCSI-RS in measResultFreqList to the value indicated by refFreqCSI-RS as included in the associated measurement object;
2> if a serving cell is associated with the MeasObjectNR:
3> set measResultServingCell in measResultFreqList to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14];
2> set the measResultNeighCellList in measResultFreqList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows;
3> ordering the cells with sorting as follows:
4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS;
4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR;
3> for each neighbour cell included:
4> include the optional fields that are available.
NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.
NOTE 2: Field measResultSCG-Failure is used to report available results for NR frequencies the UE is configured to measure by SCG RRC signalling.
1> if available, set the locationInfo as in 5.3.3.7.
1> if the UE supports SCG failure for mobility robustness optimization:
2> if the failureType is set to synchReconfigFailureSCG; or
2> if the failureType is set to randomAccessProblem and the SCG failure was declared while T304 was running:
3> set perRAInfoList to indicate the performed random access procedure related information as specified in 5.7.10.5.
3> set the failedPSCellId to the physical cell identity and carrier frequency of the target PSCell of the failed PSCell change;
3> set the previousPSCellId to the physical cell identity and carrier frequency of the source PSCell associated to the last received RRCReconfiguration message including reconfigurationWithSync for the SCG;
3> set the timeSCGFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync for the SCG until declaring the SCG failure;
2> else:
3> set the failedPSCellId to the physical cell identity and carrier frequency of the PSCell in which the SCG failure was declared;
3> if the last RRCReconfiguration message including the reconfigurationWithSync for the SCG was received to enter the PSCell in which the SCG failure was declared:
4> set the timeSCGFailure to the elapsed time since reception of the last RRCReconfiguration message including the reconfigurationWithSync for the SCG until declaring the SCG failure;
4> set the previousPSCellId to the physical cell identity and carrier frequency of the source PSCell associated to the last received RRCReconfiguration message including reconfigurationWithSync for the SCG;
The UE shall submit the SCGFailureInformation message to lower layers for transmission.
5.7.3a EUTRA SCG failure information
5.7.3a.1 General
Figure 5.7.3a.1-1: EUTRA SCG failure information
The purpose of this procedure is to inform NR MN about an SCG failure on E-UTRA SN the UE has experienced (e.g. SCG radio link failure, SCG change failure), as specified in TS 36.331 [10] clause 5.6.13.2.
5.7.3a.2 Initiation
A UE initiates the procedure to report EUTRA SCG failures when neither NR MCG nor EUTRA SCG transmission is suspended and in accordance with TS 36.331 [10] clause 5.6.13.2. Actions the UE shall perform upon initiating the procedure, other than related to the transmission of the SCGFailureInformationEUTRA message are specified in TS 36.331 [10] clause 5.6.13.2.
5.7.3a.3 Actions related to transmission of SCGFailureInformationEUTRA message
The UE shall set the contents of the SCGFailureInformationEUTRA message as follows:
1> include failureType within failureReportSCG-EUTRA and set it to indicate the SCG failure in accordance with TS 36.331 [10] clause 5.6.13.4;
1> include and set measResultSCG-FailureMRDC in accordance with TS 36.331 [10] clause 5.6.13.5;
1> for each EUTRA frequency the UE is configured to measure by measConfig for which measurement results are available:
2> set the measResultFreqListMRDC to include the best measured cells, ordered such that the best cell is listed first using RSRP to order if RSRP measurement results are available for cells on this frequency, otherwise using RSRQ to order if RSRQ measurement results are available for cells on this frequency, otherwise using SINR to order, and based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available;
NOTE: Field measResultSCG-FailureMRDC is used to report available results for E-UTRAN frequencies the UE is configured to measure by E-UTRA RRC signalling.
1> if available, set the locationInfo as in 5.3.3.7.:
The UE shall submit the SCGFailureInformationEUTRA message to lower layers for transmission.
5.7.3b MCG failure information
5.7.3b.1 General
Figure 5.7.3b.1-1: MCG failure information
The purpose of this procedure is to inform the network about an MCG failure the UE has experienced i.e. MCG radio link failure. A UE in RRC_CONNECTED, for which AS security has been activated with SRB2 and at least one DRB or multicast MRB setup or, for IAB, SRB2, may initiate the fast MCG link recovery procedure in order to continue the RRC connection without re-establishment.
5.7.3b.2 Initiation
A UE configured with split SRB1 or SRB3 initiates the procedure to report MCG failures when neither MCG nor SCG transmission is suspended, the SCG is not deactivated, t316 is configured, and when the following condition is met:
1> upon detecting radio link failure of the MCG, in accordance with 5.3.10.3, while T316 is not running.
Upon initiating the procedure, the UE shall:
1> stop timer T310 for the PCell, if running;
1> stop timer T312 for the PCell, if running;
1> suspend MCG transmission for all SRBs, DRBs, multicast MRBs, except SRB0, and, if any, BH RLC channels;
1> reset MCG MAC;
1> stop conditional reconfiguration evaluation for CHO, if configured;
1> stop conditional reconfiguration evaluation for CPC, if configured;
1> initiate transmission of the MCGFailureInformation message in accordance with 5.7.3b.4.
NOTE: The handling of any outstanding UL RRC messages during the initiation of the fast MCG link recovery is left to UE implementation.
5.7.3b.3 Failure type determination
The UE shall set the MCG failure type as follows:
1> if the UE initiates transmission of the MCGFailureInformation message due to T310 expiry:
2> set the failureType as t310-Expiry;
1> else if the UE initiates transmission of the MCGFailureInformation message due to T312 expiry:
2> set the failureType as t312-Expiry;
1> else if the UE initiates transmission of the MCGFailureInformation message to provide random access problem indication from MCG MAC:
2> if the random access procedure was initiated for beam failure recovery:
3> set the failureType as beamFailureRecoveryFailure;
2> else:
3> set the failureType as randomAccessProblem;
1> else if the UE initiates transmission of the MCGFailureInformation message to provide indication from MCG RLC that the maximum number of retransmissions has been reached:
2> set the failureType as rlc-MaxNumRetx:
1> else if the UE initiates transmission of the MCGFailureInformation message due to consistent uplink LBT failures on the MCG:
2> set the failureType as lbt-Failure;
1> else if connected as an IAB-node and the MCGFailureInformation message is initiated due to the reception of a BH RLF indication on BAP entity from the MCG:
2> set the failureType as bh-RLF.
5.7.3b.4 Actions related to transmission of MCGFailureInformation message
The UE shall set the contents of the MCGFailureInformation message as follows:
1> include and set failureType in accordance with 5.7.3b.3;
1> for each MeasObjectNR configured by a measConfig associated with the MCG, and for which measurement results are available:
2> include an entry in measResultFreqList;
2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb:
3> set ssbFrequency in measResultFreqList to the value indicated by ssbFrequency as included in the MeasObjectNR;
2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs:
3> set refFreqCSI-RS in measResultFreqList to the value indicated by refFreqCSI-RS as included in the associated measurement object;
2> if a serving cell is associated with the MeasObjectNR:
3> set measResultServingCell in measResultFreqList to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133 [14];
2> set the measResultNeighCellList in measResultFreqList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows;
3> ordering the cells with sorting as follows:
4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS;
4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR;
3> for each neighbour cell included:
4> include the optional fields that are available.
1> for each EUTRA frequency the UE is configured to measure by measConfig for which measurement results are available:
2> set the measResultFreqListEUTRA to include the best measured cells, ordered such that the best cell is listed first using RSRP to order the cells if RSRP measurement results are available for cells on this frequency, otherwise using RSRQ to order the cells if RSRQ measurement results are available for cells on this frequency, otherwise using SINR to order the cells, based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available;
1> for each UTRA-FDD frequency the UE is configured to measure by measConfig for which measurement results are available:
2> set the measResultFreqListUTRA-FDD to include the best measured cells, ordered such that the best cell is listed first using RSCP to order the cells if RSCP measurement results are available for cells on this frequency, otherwise using EcN0 to order the cells, based on measurements collected up to the moment the UE detected the failure, and for each cell that is included, include the optional fields that are available;
1> if the UE is in NR-DC:
2> include and set measResultSCG in accordance with 5.7.3.4;
1> if the UE is in NE-DC:
2> include and set measResultSCG–EUTRA in accordance with TS 36.331 [10] clause 5.6.13.5;
NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported.
NOTE 2: Field measResultSCG-Failure is used to report available results for NR frequencies the UE is configured to measure by SCG RRC signalling.
NOTE 3: Field measResultSCG-EUTRA is used to report available results for E-UTRAN frequencies the UE is configured to measure by E-UTRA RRC signalling.
1> if SRB1 is configured as split SRB and pdcp-Duplication is not configured:
2> if the primaryPath for the PDCP entity of SRB1 refers to the MCG:
3> set the primaryPath to refer to the SCG.
The UE shall:
1> start timer T316;
1> if SRB1 is configured as split SRB:
2> submit the MCGFailureInformation message to lower layers for transmission via SRB1, upon which the procedure ends;
1> else (i.e. SRB3 configured):
2> submit the MCGFailureInformation message to lower layers for transmission embedded in NR RRC message ULInformationTransferMRDC via SRB3 as specified in 5.7.2a.3.
5.7.3b.5 T316 expiry
The UE shall:
1> if T316 expires:
2> initiate the connection re-establishment procedure as specified in 5.3.7.
5.7.4 UE Assistance Information
5.7.4.1 General
Figure 5.7.4.1-1: UE Assistance Information
The purpose of this procedure is for the UE to inform the network of:
– its delay budget report carrying desired increment/decrement in the connected mode DRX cycle length, or;
– its overheating assistance information, or;
– its IDC assistance information, or;
– its preference on DRX parameters for power saving, or;
– its preference on the maximum aggregated bandwidth for power saving, or;
– its preference on the maximum number of secondary component carriers for power saving, or;
– its preference on the maximum number of MIMO layers for power saving, or;
– its preference on the minimum scheduling offset for cross-slot scheduling for power saving, or;
– its preference on the RRC state, or;
– configured grant assistance information for NR sidelink communication, or;
– its preference in being provisioned with reference time information, or;
– its preference for FR2 UL gap, or;
– its preference to transition out of RRC_CONNECTED state for MUSIM operation, or;
– its preference on the MUSIM gaps, or;
– its relaxation state for RLM measurements, or;
– its relaxation state for BFD measurements, or;
– availability of data and/or signalling mapped to radio bearers which are not configured for SDT, or;
– its preference for the SCG to be deactivated, or;
– indicate that the UE has uplink data to transmit for a DRB for which there is no MCG RLC bearer while the SCG is deactivated, or;
– change of its fulfilment status for RRM measurement relaxation criterion, or;
– service link (specified in TS 38.300 [2]) propagation delay difference between serving cell and neighbour cell(s).
5.7.4.2 Initiation
A UE capable of providing delay budget report in RRC_CONNECTED may initiate the procedure in several cases, including upon being configured to provide delay budget report and upon change of delay budget preference.
A UE capable of providing overheating assistance information in RRC_CONNECTED may initiate the procedure if it was configured to do so, upon detecting internal overheating, or upon detecting that it is no longer experiencing an overheating condition.
A UE capable of providing IDC assistance information in RRC_CONNECTED may initiate the procedure if it was configured to do so, upon detecting IDC problem if the UE did not transmit an IDC assistance information since it was configured to provide IDC indications, or upon change of IDC problem information.
A UE capable of providing its preference on DRX parameters of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a preference on DRX parameters and upon change of its preference on DRX parameters.
A UE capable of providing its preference on the maximum aggregated bandwidth of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum aggregated bandwidth preference and upon change of its maximum aggregated bandwidth preference.
A UE capable of providing its preference on the maximum number of secondary component carriers of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum number of secondary component carriers preference and upon change of its maximum number of secondary component carriers preference.
A UE capable of providing its preference on the maximum number of MIMO layers of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum number of MIMO layers preference and upon change of its maximum number of MIMO layers preference.
A UE capable of providing its preference on the minimum scheduling offset for cross-slot scheduling of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a minimum scheduling offset preference and upon change of its minimum scheduling offset preference.
A UE capable of providing assistance information to transition out of RRC_CONNECTED state may initiate the procedure if it was configured to do so, upon determining that it prefers to transition out of RRC_CONNECTED state, or upon change of its preferred RRC state.
A UE capable of providing configured grant assistance information for NR sidelink communication in RRC_CONNECTED may initiate the procedure in several cases, including upon being configured to provide traffic pattern information and upon change of traffic patterns.
A UE capable of providing an indication of its preference in being provisioned with reference time information may initiate the procedure upon being configured to provide this indication, or if it was configured to provide this indication and upon change of its preference.
A UE capable of providing an indication of its preference in FR2 UL gap may initiate the procedure if it was configured to do so, upon detecting the need of FR2 UL gap activation/deactivation.
A UE capable of providing MUSIM assistance information for gap preference may initiate the procedure if it was configured to do so, upon determining it needs the gaps, or upon change of the gap preference information.
A UE capable of providing MUSIM assistance information for leave indication may initiate the procedure if it was configured to do so upon determining that it needs to leave RRC_CONNECTED state.
A UE capable of relaxing its RLM measurements of a cell group in RRC_CONNECTED state shall initiate the procedure for providing an indication of its relaxation state for RLM measurements upon being configured to do so, and upon change of its relaxation state for RLM measurements in RRC_CONNECTED state.
A UE capable of relaxing its BFD measurements in serving cells of a cell group in RRC_CONNECTED shall initiate the procedure for providing an indication of its relaxation state for BFD measurements upon being configured to do so, and upon change of its relaxation state for BFD measurements in RRC_CONNECTED state.
A UE capable of SDT initiates this procedure when data and/or signalling mapped to radio bearers that are not configured for SDT becomes available during SDT (i.e. while SDT procedure is ongoing).
A UE capable of providing its preference for SCG deactivation may initiate the procedure if it was configured to do so, upon determining that it prefers or does no more prefer the SCG to be deactivated.
A UE that has uplink data to transmit for a DRB for which there is no MCG RLC bearer while the SCG is deactivated shall initiate the procedure.
A UE capable of providing an indication of fulfilment of the RRM measurement relaxation criterion in connected mode may initiate the procedure if it was configured to do so, upon change of its fulfilment status for RRM measurement relaxation criterion for connected mode.
A UE capable of providing service link propagation delay difference between serving cell and neighbour cell(s) shall initiate the procedure upon being configured to do so, and upon determining that service link propagation delay difference between serving cell and a neighbour cell has changed more than threshPropDelayDiff compared with the last reported value.
Upon initiating the procedure, the UE shall:
1> if configured to provide delay budget report:
2> if the UE did not transmit a UEAssistanceInformation message with delayBudgetReport since it was configured to provide delay budget report; or
2> if the current delay budget is different from the one indicated in the last transmission of the UEAssistanceInformation message including delayBudgetReport and timer T342 is not running:
3> start or restart timer T342 with the timer value set to the delayBudgetReportingProhibitTimer;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide a delay budget report;
1> if configured to provide overheating assistance information:
2> if the overheating condition has been detected and T345 is not running; or
2> if the current overheating assistance information is different from the one indicated in the last transmission of the UEAssistanceInformation message including overheatingAssistance and timer T345 is not running:
3> start timer T345 with the timer value set to the overheatingIndicationProhibitTimer;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide overheating assistance information;
1> if configured to provide IDC assistance information:
2> if the UE did not transmit a UEAssistanceInformation message with idc-Assistance since it was configured to provide IDC assistance information:
3> if on one or more frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself; or
3> if on one or more supported UL CA combination comprising of carrier frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself:
4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information;
2> else if the current IDC assistance information is different from the one indicated in the last transmission of the UEAssistanceInformation message:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information;
NOTE 1: The term "IDC problems" refers to interference issues applicable across several subframes/slots where not necessarily all the subframes/slots are affected.
NOTE 2: For the frequencies on which a serving cell or serving cells is configured that is activated, IDC problems consist of interference issues that the UE cannot solve by itself, during either active data exchange or upcoming data activity which is expected in up to a few hundred milliseconds.
For frequencies on which a SCell or SCells is configured that is deactivated, reporting IDC problems indicates an anticipation that the activation of the SCell or SCells would result in interference issues that the UE would not be able to solve by itself.
For a non-serving frequency, reporting IDC problems indicates an anticipation that if the non-serving frequency or frequencies became a serving frequency or serving frequencies then this would result in interference issues that the UE would not be able to solve by itself.
1> if configured to provide its preference on DRX parameters of a cell group for power saving:
2> if the UE has a preference on DRX parameters of the cell group and the UE did not transmit a UEAssistanceInformation message with drx-Preference for the cell group since it was configured to provide its preference on DRX parameters of the cell group for power saving; or
2> if the current drx-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including drx-Preference for the cell group and timer T346a associated with the cell group is not running:
3> start the timer T346a with the timer value set to the drx-PreferenceProhibitTimer of the cell group;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current drx-Preference;
1> if configured to provide its preference on the maximum aggregated bandwidth of a cell group for power saving:
2> if the UE has a preference on the maximum aggregated bandwidth of the cell group and the UE did not transmit a UEAssistanceInformation message with maxBW-Preference and/or maxBW-PreferenceFR2-2 for the cell group since it was configured to provide its preference on the maximum aggregated bandwidth of the cell group for power saving; or
2> if the current maxBW-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxBW-Preference and/or maxBW-PreferenceFR2-2for the cell group and timer T346b associated with the cell group is not running:
3> start the timer T346b with the timer value set to the maxBW-PreferenceProhibitTimer of the cell group;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current maxBW-Preference and/or maxBW-PreferenceFR2-2;
1> if configured to provide its preference on the maximum number of secondary component carriers of a cell group for power saving:
2> if the UE has a preference on the maximum number of secondary component carriers of the cell group and the UE did not transmit a UEAssistanceInformation message with maxCC-Preference for the cell group since it was configured to provide its preference on the maximum number of secondary component carriers of the cell group for power saving; or
2> if the current maxCC-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxCC-Preference for the cell group and timer T346c associated with the cell group is not running:
3> start the timer T346c with the timer value set to the maxCC-PreferenceProhibitTimer of the cell group;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current maxCC-Preference;
1> if configured to provide its preference on the maximum number of MIMO layers of a cell group for power saving:
2> if the UE has a preference on the maximum number of MIMO layers of the cell group and the UE did not transmit a UEAssistanceInformation message with maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2 for the cell group since it was configured to provide its preference on the maximum number of MIMO layers of the cell group for power saving; or
2> if the current maxMIMO-LayerPreference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2 for the cell group and timer T346d associated with the cell group is not running:
3> start the timer T346d with the timer value set to the maxMIMO-LayerPreferenceProhibitTimer of the cell group;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2;
1> if configured to provide its preference on the minimum scheduling offset for cross-slot scheduling of a cell group for power saving:
2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling of the cell group and the UE did not transmit a UEAssistanceInformation message with minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt for the cell group since it was configured to provide its preference on the minimum scheduling offset for cross-slot scheduling of the cell group for power saving; or
2> if the current minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt for the cell group and timer T346e associated with the cell group is not running:
3> start the timer T346e with the timer value set to the minSchedulingOffsetPreferenceProhibitTimer of the cell group;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt;
1> if configured to provide its release preference and timer T346f is not running:
2> if the UE determines that it would prefer to transition out of RRC_CONNECTED state; or
2> if the UE is configured with connectedReporting and the UE determines that it would prefer to revert an earlier indication to transition out of RRC_CONNECTED state:
3> start timer T346f with the timer value set to the releasePreferenceProhibitTimer;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the release preference;
1> if configured to provide configured grant assistance information for NR sidelink communication:
2> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide configured grant assistance information for NR sidelink communication;
1> if configured to provide preference in being provisioned with reference time information:
2> if the UE did not transmit a UEAssistanceInformation message with referenceTimeInfoPreference since it was configured to provide preference; or
2> if the UE’s preference changed from the last time UE initiated transmission of the UEAssistanceInformation message including referenceTimeInfoPreference:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide preference in being provisioned with reference time information.
1> if configured to provide its preference on FR2 UL gap:
2> if the UE did not transmit a UEAssistanceInformation message with ul-GapFR2-Preference since it was configured to provide its preference on FR2 UL gap information:
3> if the UE has a preference on FR2 UL gap activation/deactivation:
4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide FR2 UL gap preference;
2> else if the current FR2 UL gap preference is different from the one indicated in the last transmission of the UEAssistanceInformation message:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide FR2 UL gap preference.
1> if configured to provide MUSIM assistance information for leaving RRC_CONNECTED:
2> if the UE needs to leave RRC_CONNECTED state and the timer T346g is not running:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide MUSIM assistance information for leaving RRC_CONNECTED;
3> start the timer T346g with the timer value set to the musim-LeaveWithoutResponseTimer;
1> if configured to provide MUSIM assistance information for gap preference:
2> if the UE has a preference on the MUSIM gap(s) and the UE did not transmit a UEAssistanceInformation message with musim-GapPreferenceList since it was configured to provide MUSIM assistance information for gap preference; or
2> if the current musim-GapPreferenceList is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-GapPreferenceList and the timer T346h is not running:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current musim-GapPreferenceList;
3> start or restart the timer T346h with the timer value set to the musim-GapProhibitTimer.
NOTE 3: The UE does not need to initiate transmission of the UAI message if the difference between the current musim-GapPreferenceList and the last transmission of the UEAssistanceInformation message including musim-GapPreferenceList is only due to removal of an ended aperiodic gap.
1> if configured to provide the relaxation state of RLM measurements of a cell group and RLM measurement of the cell group is not stopped:
2> if the UE did not transmit a UEAssistanceInformation message with rlm-MeasRelaxationState since it was configured to provide the relaxation state of RLM measurements for the cell group; or
2> if the relaxation state of RLM measurements for the cell group is currently different from the relaxation state reported in the last transmission of the UEAssistanceInformation message including rlm-MeasRelaxationState of the cell group and timer T346j associated with the cell group is not running:
3> start timer T346j with the timer value set to the rlm-RelaxtionReportingProhibitTimer;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the relaxation state of RLM measurements of the cell group;
1> if configured to provide the relaxation state of BFD measurements of serving cells of a cell group and BFD measurement of the cell group is not stopped:
2> if the UE did not transmit a UEAssistanceInformation message with bfd-MeasRelaxationState since it was configured to provide the relaxation state of BFD measurements for the cell group; or
2> if the relaxation state of BFD measurements in any serving cell of the cell group is currently different from the relaxation state reported in the last transmission of the UEAssistanceInformation message including bfd-MeasRelaxationState of the cell group and timer T346k associated with the cell group is not running:
3> start timer T346k with the timer value set to the bfd-RelaxtionReportingProhibitTimer;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the relaxation state of BFD measurements of serving cells of the cell group.
1> if data and/or signalling mapped to radio bearers not configured for SDT becomes available during SDT (i.e. while SDT procedure is ongoing):
2> if the UE did not transmit a UEAssistanceInformation message with nonSDT-DataIndication since the initiation of the current resume procedure for SDT:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide nonSDT-DataIndication.
1> if configured to provide its preference for SCG deactivation and timer T346i is not running;
2> if the UE prefers the SCG to be deactivated and did not transmit a UEAssistanceInformation message with scg-DeactivationPreference since it was configured to provide its SCG deactivation preference; or
2> if the UE preference for SCG deactivation is different from the last indicated scg-DeactivationPreference:
3> start timer T346i with the timer value set to the scg-DeactivationPreferenceProhibitTimer;
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the UE preference for SCG deactivation;
1> if the SCG is deactivated, and,
1> the UE has uplink data to send for an SCG RLC entity while the UE previously did not have any uplink data to send for any SCG RLC entity:
2> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to indicate that the UE has uplink data to send for a DRB whose DRB-Identity is not included in any RLC-BearerConfig in the CellGroupConfig associated with the MCG.
1> if configured to send indications of RRM measurement relaxation criterion fulfilment:
2> if the criterion in 5.7.4.4 is met for a period of TSearchDeltaP-StationaryConnected:
3> if the UE did not transmit a UEAssistanceInformation message with rrm-MeasRelaxationFulfilment as true since it was configured to provide indications of RRM measurement relaxation criterion fulfilment; or
3> the last UEAssistanceInformation message indicated the criterion in 5.7.4.4 is not fulfilled with rrm-MeasRelaxationFulfilment as false:
4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to indicate that the criterion for RRM measurement relaxation for connected mode is fulfilled;
2> else:
3> if the last UEAssistanceInformation message indicated fulfilment of the criterion in 5.7.4.4 with rrm-MeasRelaxationFulfilment as true:
4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to indicate that the criterion for RRM measurement relaxation for connected mode is not fulfilled.
1> if configured to provide service link propagation delay difference between serving cell and neighbour cell(s);
2> if the UE did not transmit a UEAssistanceInformation message with propagationDelayDifference since it was configured to provide service link propagation delay difference between serving cell and neighbour cell(s); or
2> for any neighbour cell in neighCellInfoList, if the service link propagation delay difference between serving cell and the neighbour cell has changed more than threshPropDelayDiff since the last transmission of the UEAssistanceInformation message including propagationDelayDifference:
3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide service link propagation delay difference between serving cell and each neighbour cell included in the neighCellInfoList;
5.7.4.3 Actions related to transmission of UEAssistanceInformation message
The UE shall set the contents of the UEAssistanceInformation message as follows:
1> if transmission of the UEAssistanceInformation message is initiated to provide a delay budget report according to 5.7.4.2 or 5.3.5.3;
2> set delayBudgetReport to type1 according to a desired value;
1> if transmission of the UEAssistanceInformation message is initiated to provide overheating assistance information according to 5.7.4.2 or 5.3.5.3;
2> if the UE experiences internal overheating:
3> if the UE prefers to temporarily reduce the number of maximum secondary component carriers:
4> include reducedMaxCCs in the OverheatingAssistance IE;
4> set reducedCCsDL to the number of maximum SCells the UE prefers to be temporarily configured in downlink;
4> set reducedCCsUL to the number of maximum SCells the UE prefers to be temporarily configured in uplink;
3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR1:
4> include reducedMaxBW-FR1 in the OverheatingAssistance IE;
4> set reducedBW-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR1;
4> set reducedBW-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR1;
3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-1:
4> include reducedMaxBW-FR2 in the OverheatingAssistance IE;
4> set reducedBW-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-1;
4> set reducedBW-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-1;
3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-2:
4> include reducedMaxBW-FR2-2 in the OverheatingAssistance IE;
4> set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-2;
4> set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-2;
3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR1:
4> include reducedMaxMIMO-LayersFR1 in the OverheatingAssistance IE;
4> set reducedMIMO-LayersFR1-DL to the number of maximum MIMO layers of each serving cell operating on FR1 the UE prefers to be temporarily configured in downlink;
4> set reducedMIMO-LayersFR1-UL to the number of maximum MIMO layers of each serving cell operating on FR1 the UE prefers to be temporarily configured in uplink;
3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-1:
4> include reducedMaxMIMO-LayersFR2 in the OverheatingAssistance IE;
4> set reducedMIMO-LayersFR2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-1 the UE prefers to be temporarily configured in downlink;
4> set reducedMIMO-LayersFR2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-1 the UE prefers to be temporarily configured in uplink;
3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-2:
4> include reducedMaxMIMO-LayersFR2-2 in the OverheatingAssistance IE;
4> set reducedMIMO-LayersFR2-2-DL to the number of maximum MIMO layers of each serving cell operating on FR2 the UE prefers to be temporarily configured in downlink;
4> set reducedMIMO-LayersFR2-2-UL to the number of maximum MIMO layers of each serving cell operating on FR2 the UE prefers to be temporarily configured in uplink;
2> else (if the UE no longer experiences an overheating condition):
3> do not include reducedMaxCCs, reducedMaxBW-FR1, reducedMaxBW-FR2, reducedMaxBW-FR2-2, reducedMaxMIMO-LayersFR1, reducedMaxMIMO-LayersFR2 or reducedMaxMIMO-LayersFR2-2 in OverheatingAssistance IE;
1> if transmission of the UEAssistanceInformation message is initiated to provide IDC assistance information according to 5.7.4.2 or 5.3.5.3:
2> if there is at least one carrier frequency included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself:
3> include the field affectedCarrierFreqList with an entry for each affected carrier frequency included in candidateServingFreqListNR;
3> for each carrier frequency included in the field affectedCarrierFreqList, include interferenceDirection and set it accordingly;
2> if there is at least one supported UL CA combination comprising of carrier frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself:
3> include victimSystemType for each UL CA combination included in affectedCarrierFreqCombList;
3> if the UE sets victimSystemType to wlan or bluetooth:
4> include affectedCarrierFreqCombList with an entry for each supported UL CA combination comprising of carrier frequencies included in candidateServingFreqListNR, that is affected by IDC problems;
3> else:
4> optionally include affectedCarrierFreqCombList with an entry for each supported UL CA combination comprising of carrier frequencies included in candidateServingFreqListNR, that is affected by IDC problems;
NOTE 1: When sending an UEAssistanceInformation message to inform the IDC problems, the UE includes all IDC assistance information (rather than providing e.g. the changed part(s) of the IDC assistance information).
NOTE 2: Upon not anymore experiencing a particular IDC problem that the UE previously reported, the UE provides an IDC indication with the modified contents of the UEAssistanceInformation message (e.g. by not including the IDC assistance information in the idc-Assistance field).
1> if transmission of the UEAssistanceInformation message is initiated to provide drx-Preference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3:
2> include drx-Preference in the UEAssistanceInformation message;
2> if the UE has a preference on DRX parameters for the cell group:
3> if the UE has a preference for the long DRX cycle:
4> include preferredDRX-LongCycle in the DRX-Preference IE and set it to the preferred value;
3> if the UE has a preference for the DRX inactivity timer:
4> include preferredDRX-InactivityTimer in the DRX-Preference IE and set it to the preferred value;
3> if the UE has a preference for the short DRX cycle:
4> include preferredDRX-ShortCycle in the DRX-Preference IE and set it to the preferred value;
3> if the UE has a preference for the short DRX timer:
4> include preferredDRX-ShortCycleTimer in the DRX-Preference IE and set it to the preferred value;
2> else (if the UE has no preference on DRX parameters for the cell group):
3> do not include preferredDRX-LongCycle, preferredDRX-InactivityTimer, preferredDRX-ShortCycle and preferredDRX-ShortCycleTimer in the DRX-Preference IE;
1> if transmission of the UEAssistanceInformation message is initiated to provide maxBW-Preference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3:
2> include maxBW-Preference in the UEAssistanceInformation message;
2> if the UE has a preference on the maximum aggregated bandwidth for the cell group:
3> if the UE prefers to reduce the maximum aggregated bandwidth of FR1:
4> include reducedMaxBW-FR1 in the MaxBW-Preference IE;
4> set reducedBW-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR1 in the cell group;
4> set reducedBW-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR1 in the cell group;
3> if the UE prefers to reduce the maximum aggregated bandwidth of FR2-1:
4> include reducedMaxBW-FR2 in the MaxBW-Preference IE;
4> set reducedBW-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR2-1 in the cell group;
4> set reducedBW-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR2-1 in the cell group;
2> else (if the UE has no preference on the maximum aggregated bandwidth for the cell group):
3> do not include reducedMaxBW-FR1 and reducedMaxBW-FR2 in the MaxBW-Preference IE;
1> if transmission of the UEAssistanceInformation message is initiated to provide maxBW-PreferenceFR2-2 of a cell group for power saving according to 5.7.4.2 or 5.3.5.3:
2> include maxBW-PreferenceFR2-2 in the UEAssistanceInformation message;
3> if the UE prefers to reduce the maximum aggregated bandwidth of FR2-2:
4> include reducedMaxBW-FR2-2 in the MaxBW-PreferenceFR2-2 IE;
4> set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR2-2 in the cell group;
4> set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR2-2 in the cell group;
2> else (if the UE has no preference on the maximum aggregated bandwidth for the cell group):
3> do not include reducedMaxBW-FR2-2 in the MaxBW-PreferenceFR2-2 IE;
1> if transmission of the UEAssistanceInformation message is initiated to provide maxCC-Preference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3:
2> include maxCC-Preference in the UEAssistanceInformation message;
2> if the UE has a preference on the maximum number of secondary component carriers for the cell group:
3> include reducedMaxCCs in the MaxCC-Preference IE;
3> set reducedCCsDL to the number of maximum SCells the UE desires to have configured in downlink in the cell group;
3> set reducedCCsUL to the number of maximum SCells the UE desires to have configured in uplink in the cell group;
2> else (if the UE has no preference on the maximum number of secondary component carriers for the cell group):
3> do not include reducedMaxCCs in the MaxCC-Preference IE;
NOTE 3: The UE can implicitly indicate a preference for NR SCG release by reporting the maximum aggregated bandwidth preference for power saving of the cell group, if configured, as zero for both FR1 and FR2, and by reporting the maximum number of secondary component carriers for power saving of the cell group, if configured, as zero for both uplink and downlink.
1> if transmission of the UEAssistanceInformation message is initiated to provide maxMIMO-LayerPreference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3:
2> include maxMIMO-LayerPreference in the UEAssistanceInformation message;
2> if the UE has a preference on the maximum number of MIMO layers for the cell group:
3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR1:
4> include reducedMaxMIMO-LayersFR1 in the MaxMIMO-LayerPreference IE;
4> set reducedMIMO-LayersFR1-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR1 serving cell that the UE operates on in the cell group;
4> set reducedMIMO-LayersFR1-UL to the preferred maximum number of uplink MIMO layers of each FR1 serving cell that the UE operates on in the cell group;
3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR2-1:
4> include reducedMaxMIMO-LayersFR2 in the MaxMIMO-LayerPreference IE;
4> set reducedMIMO-LayersFR2-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR2-1 serving cell that the UE operates on in the cell group;
4> set reducedMIMO-LayersFR2-UL to the preferred maximum number of uplink MIMO layers of each FR2-1 serving cell that the UE operates on in the cell group;
2> else (if the UE has no preference on the maximum number of MIMO layers for the cell group):
3> do not include reducedMaxMIMO-LayersFR1 and reducedMaxMIMO-LayersFR2 in the MaxMIMO-LayerPreference IE;
1> if transmission of the UEAssistanceInformation message is initiated to provide maxMIMO LayerPreferenceFR2 2 of a cell group for power saving according to 5.7.4.2 or 5.3.5.3:
2> include maxMIMO-LayerPreferenceFR2-2 in the UEAssistanceInformation message;
2> if the UE has a preference on the maximum number of MIMO layers for the cell group for FR2-2:
3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR2 2:
4> include reducedMaxMIMO-LayersFR2-2 in the MaxMIMO-LayerPreferenceFR2 2 IE;
4> set reducedMIMO-LayersFR2-2-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR2-2 serving cell that the UE operates on in the cell group;
4> set reducedMIMO-LayersFR2-2-UL to the preferred maximum number of uplink MIMO layers of each FR2-2 serving cell that the UE operates on in the cell group;
2> else (if the UE has no preference on the maximum number of MIMO layers for the cell group):
3> do not include reducedMaxMIMO-LayersFR2-2 in the MaxMIMO-LayerPreferenceFR2-2 IE;
1> if transmission of the UEAssistanceInformation message is initiated to provide minSchedulingOffsetPreference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3:
2> include minSchedulingOffsetPreference in the UEAssistanceInformation message;
2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling for the cell group:
3> if the UE has a preference for the value of K0 (TS 38.214 [19], clause 5.1.2.1) for cross-slot scheduling with 15 kHz SCS:
4> include preferredK0-SCS-15kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0;
3> if the UE has a preference for the value of K0 for cross-slot scheduling with 30 kHz SCS:
4> include preferredK0-SCS-30kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0;
3> if the UE has a preference for the value of K0 for cross-slot scheduling with 60 kHz SCS:
4> include preferredK0-SCS-60kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0;
3> if the UE has a preference for the value of K0 for cross-slot scheduling with 120 kHz SCS:
4> include preferredK0-SCS-120kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0;
3> if the UE has a preference for the value of K2 (TS 38.214 [19], clause 6.1.2.1) for cross-slot scheduling with 15 kHz SCS:
4> include preferredK2-SCS-15kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2;
3> if the UE has a preference for the value of K2 for cross-slot scheduling with 30 kHz SCS:
4> include preferredK2-SCS-30kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2;
3> if the UE has a preference for the value of K2 for cross-slot scheduling with 60 kHz SCS:
4> include preferredK2-SCS-60kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2;
3> if the UE has a preference for the value of K2 for cross-slot scheduling with 120 kHz SCS:
4> include preferredK2-SCS-120kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2;
2> else (if the UE has no preference on the minimum scheduling offset for cross-slot scheduling for the cell group):
3> do not include preferredK0 and preferredK2 in the MinSchedulingOffsetPreference IE;
1> if transmission of the UEAssistanceInformation message is initiated to provide minSchedulingOffsetPreferenceExt of a cell group for power saving according to 5.7.4.2 or 5.3.5.3:
2> include minSchedulingOffsetPreferenceExt in the UEAssistanceInformation message;
2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling for the cell group for FR2-2:
3> include minSchedulingOffsetPreferenceExt in the UEAssistanceInformation message;
4> if the UE has a preference for the value of K0 (TS 38.214 [19], clause 5.1.2.1) for cross-slot scheduling with 480 kHz SCS:
5> include preferredK0-SCS-480kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K0;
4> if the UE has a preference for the value of K0 for cross-slot scheduling with 960 kHz SCS:
5> include preferredK0-SCS-960kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K0;
4> if the UE has a preference for the value of K2 for cross-slot scheduling with 480 kHz SCS:
5> include preferredK2-SCS-480kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K2;
4> if the UE has a preference for the value of K2 for cross-slot scheduling with 960 kHz SCS:
5> include preferredK2-SCS-960kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K2;
3> else (if the UE has no preference on the minimum scheduling offset for cross-slot scheduling for the cell group):
4> do not include preferredK0 and preferredK2 in the minSchedulingOffsetPreferenceExt IE;
1> if transmission of the UEAssistanceInformation message is initiated to provide a release preference according to 5.7.4.2 or 5.3.5.3:
2> include releasePreference in the UEAssistanceInformation message;
2> set preferredRRC-State to the desired RRC state on transmission of the UEAssistanceInformation message;
1> if transmission of the UEAssistanceInformation message is initiated to provide an indication of preference in being provisioned with reference time information according to 5.7.4.2 or 5.3.5.3:
2> if the UE has a preference in being provisioned with reference time information:
3> set referenceTimeInfoPreference to true;
2> else:
3> set referenceTimeInfoPreference to false.
1> if transmission of the UEAssistanceInformation message is initiated to provide preference on FR2 UL gap according to 5.7.4.2 or 5.3.5.3:
2> if the UE has a preference for FR2 UL gap configuration:
3> set ul-GapFR2-PatternPreference to the preferred FR2 UL gap pattern;
2> else (if the UE has no preference for the FR2 UL gap configuration):
3> do not include ul-GapFR2-PatternPreference in the UL-GapFR2-Preference IE.
1> if transmission of the UEAssistanceInformation message is initiated to provide MUSIM assistance information according to 5.7.4.2 or 5.3.5.3:
2> if the UE has a preference for MUSIM periodic gap(s):
3> include musim-GapPreferenceList with an entry for each periodic gap the UE prefers to be configured;
4> set musim-GapLength and musim-GapRepetitionAndOffset in the musim-GapInfo IE to the values of the length and the repetition/offset of the gap(s), respectively, the UE prefers to be configured with;
2> if the UE has a preference for MUSIM aperiodic gap:
3> include the field musim-GapPreferenceList, with one entry for the aperiodic gap the UE prefers to be configured;
4> include musim-GapLength in the musim-GapInfo IE and set it to the values of the length of the gap the UE prefers to be configured with;
4> optionally include musim-Starting-SFN-AndSubframe in the musim-GapInfo IE and set it to the starting SFN/subframe of the gap the UE prefers to be configured with;
2> if the UE has no longer preference for the periodic/aperiodic gaps:
3> do not include musim-GapPreferenceList in the musim-Assistance IE;
2> if UE has a preference to leave RRC_CONNECTED state:
3> set musim-PreferredRRC-State to the preferred RRC state.
1> if transmission of the UEAssistanceInformation message is initiated to provide the relaxation state of RLM measurements of a cell group according to 5.7.4.2:
2> if the UE performs RLM measurement relaxation on the cell group according to TS 38.133 [14]:
3> set the rlm-MeasRelaxationState to true;
2> else:
3> set the rlm-MeasRelaxationState to false;
1> if transmission of the UEAssistanceInformation message is initiated to provide the relaxation state of BFD measurements of a cell group:
2> for each serving cell of the cell group:
3> if the UE performs BFD measurement relaxation on this serving cell according to TS 38.133 [14]:
4> set the n-th bit of bfd-MeasRelaxationState to ‘1’, where n is equal to the servCellIndex value + 1 of the serving cell;
3> else:
4> set the n-th bit of bfd-MeasRelaxationState to ‘0’, where n is equal to the servCellIndex value + 1 of the serving cell.
1> if transmission of the UEAssistanceInformation message is initiated to indicate availability of data mapped to radio bearers not configured for SDT according to 5.7.4.2:
2> include the nonSDT-DataIndication in the UEAssistanceInformation message;
2> include and set the resumeCause according to the information received from the upper layers, if provided.
1> if transmission of the UEAssistanceInformation message is initiated to provide an indication of preference for SCG deactivation according to 5.7.4.2:
2> include scg-DeactivationPreference in the UEAssistanceInformation message;
2> set the scg-DeactivationPreference to scgDeactivationPreferred if the UE prefers the SCG to be deactivated, otherwise set it to noPreference;
1> if transmission of the UEAssistanceInformation message is initiated to provide an indication that the UE has uplink data related to a deactivated SCG according to 5.7.4.2:
2> include uplinkData in the UEAssistanceInformation message.
1> if transmission of the UEAssistanceInformation message is initiated to provide an indication about whether the criterion for RRM relaxation for connected mode is fulfilled or not fulfilled:
2> if the criterion for RRM measurement relaxation for connected mode is fulfilled:
3> set the rrm-MeasRelaxationFulfilment to true;
2> else:
3> set the rrm-MeasRelaxationFulfilment to false.
1> if transmission of the UEAssistanceInformation message is initiated to provide the service link propagation delay difference between serving cell and neighbour cell(s) according to 5.7.4.2;
2> include the propagationDelayDifference for each neighbour cell in the neighCellInfoList;
The UE shall set the contents of the UEAssistanceInformation message for configured grant assistance information for NR sidelink communication:
1> if configured to provide configured grant assistance information for NR sidelink communication:
2> include the sl-UE-AssistanceInformationNR;
NOTE 4: It is up to UE implementation when and how to trigger configured grant assistance information for NR sidelink communication.
The UE shall:
1> if the procedure was triggered to provide configured grant assistance information for NR sidelink communication by an NR RRCReconfiguration message that was embedded within an E-UTRA RRCConnectionReconfiguration:
2> submit the UEAssistanceInformation to lower layers via SRB1, embedded in E-UTRA RRC message ULInformationTransferIRAT as specified in TS 36.331 [10], clause 5.6.28;
1> else if the procedure was triggered to provide UE preference for SCG deactivation or to indicate that the UE with a deactivate SCG has uplink data to send on a DRB for which there is no MCG RLC bearer:
2> submit the UEAssistanceInformation via SRB1 to lower layers for transmission;
1> else if the UE is in (NG)EN-DC:
2> if SRB3 is configured and the SCG is in activated state:
3> submit the UEAssistanceInformation message via SRB3 to lower layers for transmission;
2> else:
3> submit the UEAssistanceInformation message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10].
1> else if the UE is in NR-DC:
2> if the UE assistance configuration that triggered this UE assistance information is associated with the SCG:
3> if SRB3 is configured and the SCG is in activated state:
4> submit the UEAssistanceInformation message via SRB3 to lower layers for transmission;
3> else:
4> submit the UEAssistanceInformation message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3;
2> else:
3> submit the UEAssistanceInformation message via SRB1 to lower layers for transmission;
1> else:
2> submit the UEAssistanceInformation message to lower layers for transmission.
5.7.4.3a Setting the contents of OverheatingAssistance IE
The UE shall set the contents of OverheatingAssistance IE if initiated to provide overheating assistance indication for SCG in (NG)EN-DC according to clause 5.6.10.3 as specified in TS 36.331 [10]:
1> if the UE prefers to temporarily reduce the number of maximum secondary component carriers for SCG:
2> include reducedMaxCCs in the OverheatingAssistance IE;
2> set reducedCCsDL to the number of maximum SCells of the SCG the UE prefers to be temporarily configured in downlink;
2> set reducedCCsUL to the number of maximum SCells of the SCG the UE prefers to be temporarily configured in uplink;
1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR1 for SCG:
2> include reducedMaxBW-FR1 in the OverheatingAssistance IE;
2> set reducedBW-FR1-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR1 of the SCG;
2> set reducedBW-FR1-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR1 of the SCG;
1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-1 for SCG:
2> include reducedMaxBW-FR2 in the OverheatingAssistance IE;
2> set reducedBW-FR2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-1 of the SCG;
2> set reducedBW-FR2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-1 of the SCG;
1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-2 for SCG:
2> include reducedMaxBW-FR2-2 in the OverheatingAssistance IE;
2> set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-2 of the SCG;
2> set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-2 of the SCG;
1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR1 for SCG:
2> include reducedMaxMIMO-LayersFR1 in the OverheatingAssistance IE;
2> set reducedMIMO-LayersFR1-DL to the number of maximum MIMO layers of each serving cell operating on FR1 of the SCG the UE prefers to be temporarily configured in downlink;
2> set reducedMIMO-LayersFR1-UL to the number of maximum MIMO layers of each serving cell operating on FR1 of the SCG the UE prefers to be temporarily configured in uplink;
1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-1 for SCG:
2> include reducedMaxMIMO-LayersFR2 in the OverheatingAssistance IE;
2> set reducedMIMO-LayersFR2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-1 of the SCG the UE prefers to be temporarily configured in downlink;
2> set reducedMIMO-LayersFR2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-1 of the SCG the UE prefers to be temporarily configured in uplink;
1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-2 for SCG:
2> include reducedMaxMIMO-LayersFR2-2 in the OverheatingAssistance IE;
2> set reducedMIMO-LayersFR2-2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-2 of the SCG the UE prefers to be temporarily configured in downlink;
2> set reducedMIMO-LayersFR2-2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-2 of the SCG the UE prefers to be temporarily configured in uplink;
5.7.4.4 Relaxed measurement criterion for a stationary RedCap UE
The relaxed measurement criterion for a stationary UE is met when:
– (SS-RSRPRefStationaryConnected – SS-RSRP) < SSearchDeltaP-StationaryConnected,
Where:
– SS-RSRP = current L3 RSRP measurement of the PCell based on SSB (dB).
– SS-RSRPRefStationaryConnected = reference SS-RSRP value of the PCell (dB), set as follows:
– at the end of RRC reconfiguration procedure as specified in 5.3.5.3, when rrm-MeasRelaxationReportingConfig is included in the RRCReconfiguration message; or
– after MAC successfully completes a Random Access procedure after applying a reconfigurationWithSync in spCellConfig while stationary criterion is configured; or
– if (SS-RSRP – SS-RSRPRefStationaryConnected) > 0; or
– if the relaxed measurement criterion has not been met for TSearchDeltaP-StationaryConnected:
– UE shall set the value of SS-RSRPRefStationaryConnected to the current SS-RSRP value of the serving cell.
5.7.4a Void
5.7.5 Failure information
5.7.5.1 General
Figure 5.7.5.1-1: Failure information
The purpose of this procedure is to inform the network about a failure detected by the UE.
5.7.5.2 Initiation
A UE initiates the procedure when there is a need inform the network about a failure detected by the UE. In particular, the UE initiates the procedure when the following condition is met:
1> upon detecting failure for an RLC bearer, in accordance with 5.3.10.3;
1> upon detecting DAPS handover failure, in accordance with 5.3.5.8.3;
Upon initiating the procedure, the UE shall:
1> initiate transmission of the FailureInformation message as specified in 5.7.5.3;
5.7.5.3 Actions related to transmission of FailureInformation message
The UE shall:
1> if initiated to provide RLC failure information, set FailureInfoRLC-Bearer as follows:
2> set logicalChannelIdentity to the logical channel identity of the failing RLC bearer;
2> set cellGroupId to the cell group identity of the failing RLC bearer;
2> set the failureType as rlc-failure;
1> if initiated to provide DAPS failure information, set FailureInfoDAPS as follows:
2> set the failureType as daps-failure;
1> if used to inform the network about a failure for an MCG RLC bearer or DAPS failure information:
2> submit the FailureInformation message to lower layers for transmission via SRB1;
1> else if used to inform the network about a failure for an SCG RLC bearer:
2> if SRB3 is configured;
3> submit the FailureInformation message to lower layers for transmission via SRB3;
2> else;
3> if the UE is in (NG)EN-DC:
4> submit the FailureInformation message via E-UTRA SRB1 embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10].
3> else if the UE is in NR-DC:
4> submit the FailureInformation message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3.
5.7.6 DL message segment transfer
5.7.6.1 General
Figure 5.7.6.1-1: DL message segment transfer
The purpose of this procedure is to transfer segments of DL DCCH messages from the network to the UE.
NOTE: The segmentation of DL DCCH message is only applicable to RRCReconfiguration and RRCResume messages in this release.
5.7.6.2 Initiation
The network initiates the DL Dedicated Message Segment transfer procedure whenever the encoded RRC message PDU exceeds the maximum PDCP SDU size. The network initiates the DL Dedicated Message Segment transfer procedure by sending the DLDedicatedMessageSegment message.
5.7.6.3 Reception of DLDedicatedMessageSegment by the UE
Upon receiving DLDedicatedMessageSegment message, the UE shall:
1> store the segment included in rrc-MessageSegmentContainer;
1> if all segments of the message have been received:
2> assemble the message from the received segments and process the message according to 5.3.5.3 for the RRCReconfiguration message or 5.3.13.4 for the RRCResume message;
2> discard all segments.
5.7.7 UL message segment transfer
5.7.7.1 General
Figure 5.7.7.1-1: UL message segment transfer
The purpose of this procedure is to transfer segments of UL DCCH messages from UE to a NG-RAN in RRC_CONNECTED.
NOTE: The segmentation of UL DCCH message is only applicable to UECapabilityInformation and MeasurementReportAppLayer in this release.
5.7.7.2 Initiation
A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met:
1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and
1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323 [5];
Upon initiating the procedure, the UE shall:
1> initiate transmission of the ULDedicatedMessageSegment message as specified in 5.7.7.3;
5.7.7.3 Actions related to transmission of ULDedicatedMessageSegment message
The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 38.323 [5]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows:
1> F or each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment;
1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber;
1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:
2> set the rrc-MessageSegmentType to lastSegment;
1> else:
2> set the rrc-MessageSegmentType to notLastSegment;
1> submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.
5.7.8 Idle/inactive Measurements
5.7.8.1 General
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
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 5.7.8.2a.
5.7.8.2 Void
5.7.8.2a Performing measurements
When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 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 [9].
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 [9];
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 [9];
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;
NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133 [14] are met for measurement reporting.
NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signaling is different from the SSB configuration broadcasted in the serving cell, if any.
NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation.
NOTE 4: When idleModeMeasVoiceFallback is included in SIB5, UE may decide to measure and report idle/inactive measurements for EUTRA carrier frequencies included in SIB5 even if it does not support NE-DC between the serving carrier and the EUTRA carrier frequencies.
5.7.8.3 T331 expiry or stop
The UE shall:
1> if T331 expires or is stopped:
2> release the VarMeasIdleConfig.
NOTE: It is up to UE implementation whether to continue idle/inactive measurements according to SIB11 and SIB4 configurations or according to E-UTRA SIB5 and E-UTRA SIB24 configurations as specified in TS 36.331 [10] upon inter-RAT cell reselection to E-UTRA, after T331 has expired or stopped.
5.7.8.4 Cell re-selection or cell selection while T331 is running
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 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 5.7.8.3;
5.7.9 Mobility history information
5.7.9.1 General
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
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 or SCG failure 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 or upon declaring failure in a PSCell (SCG RLF or SCG HOF) 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:
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) 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 or secondary cell radio link failure since entering the previous PCell in RRC_CONNECTED:
7> include the time spent with no PSCell since last PSCell release or secondary cell radio link failure 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 or secondary cell radio link failure since entering the current PCell in RRC_CONNECTED:
5> include the time spent with no PSCell since last PSCell release or SCG radio link failure 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
5.7.10.1 General
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
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
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 [26] and has radio link failure information or handover failure information available in VarRLF-Report of TS 36.331 [10] and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331 [10]:
3> set timeSinceFailure in VarRLF-Report of TS 36.331 [10] 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 [10];
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 [10];
3> discard the rlf-Report from VarRLF-Report of TS 36.331 [10] 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 or secondary cell radio link failure 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> 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 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
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 [23]) 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 corresponding random-access procedure was performed on an SCell of MCG:
5> set the spCellId to the global cell identity of the PCell;
4> if the corresponding random-access procedure was performed on an SCell of SCG:
5> set the spCellId to the global cell identity of the PSCell;
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.
NOTE 1: The UE does not log the RA information in the RA report if the triggering event of the random access is consistent UL LBT on SpCell as specified in TS 38.321 [6].
5.7.10.5 RA information determination for RA report and RLF report
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 [3]:
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 [3];
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 [6] 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.
NOTE 1: Void.
5.7.10.6 Actions for the successful handover report determination
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 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
5.7.12.1 General
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
Upon initiation of the procedure, the IAB-MT shall:
1> initiate transmission of the IABOtherInformation message in accordance with 5.7.12.3;
5.7.12.3 Actions related to transmission of IABOtherInformation message
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 [10];
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
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 [14] 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 [14] when the relaxed measurement criterion for good serving cell quality is met.
5.7.13.1 Relaxed measurement criterion for low mobility
The relaxed measurement criterion for UE with low mobility in RRC_CONNECTED is fulfilled when:
– (SS-RSRPRef – SS-RSRP) < SSearchDeltaP-Connected,
Where:
– SS-RSRP = current L3 RSRP measurement of the SpCell based on SSB (dB).
– SS-RSRPRef = 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-RSRPRef) > 0, or
– If the relaxed measurement criterion has not been met for TSearchDeltaP-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
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 Qin+XdB, wherein
– Qin is specified in clause 8.1 of TS 38.133 [14].
– 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 Qin+XdB, wherein
– Q in is specified in clause 8.1 of TS 38.133 [14].
– X is the parameter offset in goodServingCellEvaluationBFD.
5.7.14 UE Positioning Assistance Information
5.7.14.1 General
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 [73].
5.7.14.2 Initiation
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 5.7.14.3 to provide the association.
5.7.14.3 Actions related to transmission of UEPositioningAssistanceInfo message
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
5.7.16.1 General
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
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 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 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;
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 [5]:
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
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 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 [24];
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 [24].