Content for TS 38.331 Word version: 18.0.0

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

5.7 Other 5.7.1 DL information transfer 5.7.1a DL information transfer for MR-DC 5.7.2 UL information transfer 5.7.2a UL information transfer for MR-DC 5.7.2b UL transfer of IRAT information 5.7.3 SCG failure information 5.7.3a EUTRA SCG failure information 5.7.3b MCG failure information 5.7.3c Indirect path failure information
...

5.7 Other p. 284

5.7.1 DL information transfer p. 284

5.7.1.1 General p. 284

Reproduction of 3GPP TS 38.331, Fig. 5.7.1.1-1: DL information transfer

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

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

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.

1 >

if clockQualityDetailsLevel is included:

2 >

if eventID-TSS is included:

3 >

if VarEventID has an entry with a storedEventID value:

4 >

replace the storedEventID value within VarEventID with the eventID-TSS value received with clockQualityDetailsLevel;

3 >

else:

4 >

add a new entry of storedEventID within the VarEventID with a value set as the one of eventID-TSS value received with clockQualityDetailsLevel;

2 >

if the VarGnbID has an entry with a storedGnbID value:

3 >

replace the storedGnbID value within VarGnbID with the gNB identity value received within SIB1;

2 >

else:

3 >

add a new entry of storedGnbID within the VarGnbID with the gNB identity value received within SIB1.

2 >

forward clockQualityDetailsLevel to upper layers.

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

5.7.1a.1 General p. 285

Reproduction of 3GPP TS 38.331, Fig. 5.7.1a.1-1: DL information transfer MR-DC

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

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

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

1 >

else if the RRCRelease message is included in dl-DCCH-MessageNR:

2 >

perform the RRC release procedure according to clause 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 clause 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 clause 5.3.5.4 of TS 36.331;

1 >

else if the E-UTRA RRCConnectionRelease message is included in dl-DCCH-MessageEUTRA:

2 >

perform the RRC connection release as specified in clause 5.3.8 of TS 36.331;

1 >

else if the MobilityFromEUTRACommand message is included in the dl-DCCH-MessageEUTRA:

2 >

perform the mobility from E-UTRA procedure as specified in clause 5.4.3.3 of TS 36.331;

5.7.2 UL information transfer p. 286

5.7.2.1 General p. 286

Reproduction of 3GPP TS 38.331, Fig. 5.7.2.1-1: UL information transfer

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 in RRC_CONNECTED or in RRC_INACTIVE during SDT, 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 p. 286

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

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

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

5.7.2a.1 General p. 287

Reproduction of 3GPP TS 38.331, Fig. 5.7.2a.1-1: UL information transfer MR-DC

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

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

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

5.7.2b.1 General p. 287

Reproduction of 3GPP TS 38.331, Fig. 5.7.2b.1-1: UL transfer of IRAT information

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 clause 5.6.10 of TS 36.331 for E-UTRA UEAssistanceInformation message;
the procedure specified in clause 5.10.2 of TS 36.331 for E-UTRA SidelinkUEInformation message;
the procedure specified in clause 5.5.5 of TS 36.331 for E-UTRA MeasurementReport Message.

5.7.2b.2 Initiation p. 288

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.

5.7.2b.3 Actions related to transmission of ULInformationTransferIRAT message p. 288

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

5.7.3.1 General p. 288

Reproduction of 3GPP TS 38.331, Fig. 5.7.3.1-1: SCG failure information

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

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;

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, CPA, or subsequent CPAC, if configured;

1 >

stop conditional reconfiguration evaluation for each CHO configuration that includes condExecutionCondPSCell, if configured;

1 >

if the UE is in (NG)EN-DC:

2 >

initiate transmission of the SCGFailureInformationNR message as specified in clause 5.6.13a of TS 36.331.

1 >

else:

2 >

initiate transmission of the SCGFailureInformation message in accordance with clause 5.7.3.5.

5.7.3.3 Failure type determination for (NG)EN-DC p. 289

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

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;

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.

1 >

if available, set the locationInfo as in clause 5.3.3.7 according to the otherConfig associated with the NR SCG.

5.7.3.5 Actions related to transmission of SCGFailureInformation message p. 290

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

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 >

if the UE supports SCG failure information for mobility robustness optimization for conditional PSCell change or addition, for each neighbour cell, if any, included in measResultListNR in measResultFreqList:

4 >

if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the secondaryCellGroup in the MCG VarConditionalReconfig (for CPA or inter-SN CPC in NR-DC) or SCG VarConditionalReconfig (for intra-SN CPC) at the moment of the detected SCG failure (radio link failure at PSCell or PSCell change or addition failure):

5 >

if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of SCG failure; or

5 >

if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of SCG failure:

6 >

set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time;

6 >

set timeBetweenEvents to the elapsed time between the point in time of fulfilling the condition in choConfig that was fulfilled first in time, and the point in time of fulfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled;

3 >

for each neighbour cell included:

4 >

include the optional fields that are available.

1 >

if available, set the locationInfo as in clause 5.3.3.7 according to the otherConfig associated with the NR MCG.

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 clause 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, if available;

3 >

set the timeSCGFailure to the elapsed time since the last execution of 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 the last execution of RRCReconfiguration message including the reconfigurationWithSync for the SCG until declaring the SCG failure;

4 >

1 >

release successPSCell-Config configured by the source PSCell, if available.

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

5.7.3a EUTRA SCG failure information p. 293

5.7.3a.1 General p. 293

Reproduction of 3GPP TS 38.331, Fig. 5.7.3a.1-1: EUTRA SCG failure information

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 clause 5.6.13.2 of TS 36.331.

5.7.3a.2 Initiation p. 293

A UE initiates the procedure to report EUTRA SCG failures when neither NR MCG nor EUTRA SCG transmission is suspended and in accordance with clause 5.6.13.2 of TS 36.331. Actions the UE shall perform upon initiating the procedure, other than related to the transmission of the SCGFailureInformationEUTRA message are specified in clause 5.6.13.2 of TS 36.331.

5.7.3a.3 Actions related to transmission of SCGFailureInformationEUTRA message p. 293

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

1 >

include and set measResultSCG-FailureMRDC in accordance with clause 5.6.13.5 of TS 36.331;

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;

1 >

if available, set the locationInfo as in clause 5.3.3.7.:

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

5.7.3b MCG failure information p. 294

5.7.3b.1 General p. 294

Reproduction of 3GPP TS 38.331, Fig. 5.7.3b.1-1: MCG failure information

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

In case of MR-DC, 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; or

In case of MP, a MP remote UE configured with split SRB1 initiates the procedure to report direct path failures when neither MCG (i.e. direct path) nor indirect path transmission is suspended, t316 is configured, and when the following condition is met:

1 >

upon detecting radio link failure of the MCG, in accordance with clause 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 or subsequent CPAC, if configured;

1 >

initiate transmission of the MCGFailureInformation message in accordance with clause 5.7.3b.4.

5.7.3b.3 Failure type determination p. 294

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

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

1 >

include and set failureType in accordance with clause 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;

2 >

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

1 >

if the UE is in NE-DC:

2 >

include and set measResultSCG-EUTRA in accordance with clause 5.6.13.5 of TS 36.331;

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 clause 5.7.2a.3.

5.7.3b.5 T316 expiry p. 296

The UE shall:

1 >

if T316 expires:

2 >

initiate the connection re-establishment procedure as specified in clause 5.3.7.

5.7.3c Indirect path failure information p. 297

5.7.3c.1 General p. 297

Reproduction of 3GPP TS 38.331, Fig. 5.7.3c.1-1: Indirect path failure information

Figure 5.7.3c.1-1: Indirect path failure information

The purpose of this procedure is to inform NR RAN about an indirect path failure the MP remote UE has experienced.

5.7.3c.2 Initiation p. 297

In case of MP, a MP remote UE initiates the procedure to report indirect path failures when neither MCG nor indirect path transmission is suspended and when one of the following conditions is met:

1 >

upon detecting a SL indirect path failure resulting from sidelink radio link failure on the PC5 unicast link or receiption of NotificationMessageSidelink from the L2 U2N Relay UE indicating Uu failure, or indirect path addition/change failure in accordance with clause 5.3.5.17.2.3; or

1 >

upon detecting a N3C indirect path failure, including N3C connection failure or Uu failure of the relay UE with N3C indirect path;

Upon initiating the procedure, the UE shall:

1 >

if the procedure was initiated to report SL indirect path failure:

2 >

reset the sidelink specific MAC of this destination;

2 >

stop T421 if running;

1 >

suspend indirect path transmission for all SRBs and DRBs;

1 >

initiate transmission of the IndirectPathFailureInformation message in accordance with clause 5.7.3c.4;

5.7.3c.3 Failure type determination p. 297

The L2 U2N Remote UE configured with SL indirect path shall set the indirect path failure type as follows:

1 >

if the UE initiates transmission of the IndirectPathFailureInformation message due to T421 expiry in accordance with clause 5.3.5.16.1.3:

2 >

set the failureTypeIndirectPath as t421-Expiry;

1 >

else if the UE initiates transmission of the IndirectPathFailureInformation message due to reception of the NotificationMessageSidelink including indicationType, in accordance with clause 5.8.9.10.4:

2 >

set the failureTypeIndirectPath as the value in indicationType received from NotificationMessageSidelink;

1 >

else if the UE initiates transmission of the IndirectPathFailureInformation message due to sidelink radio link failure in accordance with clause 5.8.9.3:

2 >

set the failureTypeIndirectPath as sl-Failure;

1 >

if the target L2 U2N Relay UE (i.e., the UE indicated by sl-IndirectPathRelayUE-Identity in the received sl-IndirectPathAddChange) changes its serving PCell to a different cell from the target cell (i.e. the cell indicated by sl-IndirectPathCellIdentity in the received sl-IndirectPathAddChange) before path addition or change:

2 >

set the failureTypeIndirectPath as indirectPathAddChangeFailure;

The N3C remote UE shall set the indirect path failure type as follows:

1 >

if the UE initiates transmission of the IndirectPathFailureInformation message due to N3C connection failure:

2 >

set the failureTypeIndirectPath as n3c-Failure;

1 >

else if the UE initiates transmission of the IndirectPathFailureInformation message due to Uu radio link failure on N3C indirect path:

2 >

set the failureTypeIndirectPath as relayUE-Uu-RLF;

5.7.3c.4 Actions related to transmission of IndirectPathFailureInformation message p. 298

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

1 >

set the failureTypeIndirectPath in accordance with clause 5.7.3c.3;

1 >

if the procedure was initiated to report SL indirect path failure:

2 >

set the sl-MeasResultServingRelay to include the measurement result for serving L2 U2N Relay UE if available;

2 >

for each measObjectRelay included MeasConfig, and for which measurement results are available:

3 >

include an entry in sl-MeasResultsCandRelay;

1 >

else if the procedure was initiated to report N3C indirect path failure;

2 >

include n3c-relayUE-InfoList to report relay UE information with non-3GPP connection(s) if available;

1 >

submit the IndirectPathFailureInformation message to lower layers for transmission.