Section: 5.7.10.5 RA information determination
Content: The UE shall, for the last successfully completed or last failed random-access procedure, 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[ NR; Medium Access Control (MAC) protocol specification ]  [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[ NR; Medium Access Control (MAC) protocol specification ]  [3]; 2> if the configuration for the random access msgA-TransMax was configured in RACH-ConfigDedicated for this random access procedure, and raPurpose 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> if one or more of the features including RedCap and/or Slicing and/or SDT and/or MSG3 repetition are applicable for this random-access procedure as specified in clause 5.1.1b of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]: 2> set the triggeredFeatureCombination to indicate all the features triggering this random-access procedure as below: 3> if this random-access procedure is triggered by RedCap, includes redCap; 3> if this random-access procedure is triggered by SDT, includes smallData; 3> if this random-access procedure is triggered by Msg3 repetition, includes msg3-Repetitions; 3> if this random-access procedure is triggered by slicing, set nsag to the NSAG ID applied in the random-access procedure and set the triggered-S-NSSAI-List to include all the S-NSSAI(s) associated to the slices triggering the access attempt in the random-access procedure; 2> if the value of used feature or combination of features is different from the triggeredFeatureCombination: 3> set the usedFeatureCombination to indicate one or more features of FeatureCombination associated to the random-access resource used in the random-access procedure as below: 4> if RedCap is part of the used FeatureCombination, include redCap; 4> if SDT is part of the used FeatureCombination, include smallData; 4> if Msg3 repetition is part of the used FeatureCombination, include msg3-Repetitions; 4> if NSAG(s) is part of the used FeatureCombination, set NSAG-List to include the NSAG-ID(s) configured for the used FeatureCombination; 1> if the random-access procedure is initiated for SDT and the SDT transmission was failed: 3> include the sdt-Failed; 1> set the parameters associated to the successive random-access attempts associated to the selected beam 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> if all preamble transmissions for the successive random-access attempts associated to this SS/PBCH block were blocked by LBT: 4> include allPreamblesBlocked; 3> else: 4> if LBT failure indication was received from lower layers for the last random-access preamble transmission attempt in the SS/PBCH block associated to the ssb-Index, before changing the SS/PBCH block for random access preamble transmission: 5> include lbt-Detected; 3> for each random-access attempt performed on the random-access resource, except the random-access attempts for which LBT failure indication was received from lower layers, 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[ NR; Medium Access Control (MAC) protocol specification ]  [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; 3> if all preamble transmissions for the successive random-access attempts associated to this CSI-RS were blocked by LBT: 4> include allPreamblesBlocked; 3> else: 4> if LBT failure indication was received from lower layers for the last random-access preamble transmission attempt in the CSI-RS associated to the csi-RS-Index, before changing the CSI-RS for random access preamble transmission: 5> include lbt-Detected; 1> if at least one LBT failure indication has been received from lower layers during the random-access procedure: 2> set the numberOfLBTFailures to indicate the total number of random-access attempts for which LBT failure indications have been received from lower layers in the random-access procedure. The UE shall, for all the BWPs in which consistent LBT failures are triggered and not cancelled at the moment of successful RA completion or for all the BWPs in which consistent LBT failures are detected prior the RLF/HOF, set the below parameters in attemptedBWP-InfoList in the chronological order of BWP selection: 1> set the locationAndBandwidth and subcarrierSpacing associated to the UL BWP. NOTE 1: Void. NOTE 2: If allPreamblesBlocked is included, it is left to UE implementation how to set the numberOfPreamblesSentOnSSB-r16, numberOfPreamblesSentOnCSI-RS-r16 and the perRAAttemptInfoList-r16.