3GPP TSG RAN WG1 Meeting #120-bis                                R1-2501739  
Wuhan, China, April 7th – 11th, 2025
Agenda item:		9.3.2
Source:	MediaTek Inc.
Title:	Discussion on SBFD Random Access Operation
Document for:		Discussion and Decision

Conclusion
In this contribution, we discussed issues related to random access operation on SBFD symbols.
Providing all the parameters in rach-ConfigCommon in the additional RACH configuration will increase signalling overhead.
With Option 2 of PRACH resource selection for PRACH initial attempt all SBFD-aware UEs follow a predefined set of rules for resource selection.
Option 2 of PRACH resource selection for PRACH transmission re-attempt has more flexibility compared to Option 1 and Option 3.

For RACH configuration Option 2, do not provide all parameters in rach-ConfigCommon in the additional RACH configuration.
If a parameter is not provided in the additional RACH configuration, UE uses the corresponding parameter in the legacy RACH configuration 
FFS which parameters are included in the additional RACH configuration
For initial PRACH transmission attempt in one random access procedure, support Option 2 of PRACH resource selection for both RACH configuration Option 1 with Alt 1-1 and RACH configuration Option 2. 
Option 2: Select one type between legacy-ROs and additional-ROs based on certain specified/configured conditions/prioritizations.
For PRACH transmission re-attempt in one random access procedure, support Option 2 of PRACH resource selection for both RACH configuration Option 1 with Alt 1-1 and RACH configuration Option 2.
Option 2: First use ROs of the same type as the earlier PRACH transmission for a certain number of times, and if certain conditions are met, then use ROs of the other type for the rest of the random access procedure.
When a SBFD-aware UE switches from one RO type to another RO type in PRACH transmission re-attempt in one RACH procedure, support Alt-2
•	Alt-2: Reset the power ramping.
•	The same behaviour applies for both RACH configuration Option 1 and Option 2.

3GPP TSG RAN WG1 #120b			R1-2501753
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.3.2
Source: 	LG Electronics
Title: 	Discussion on SBFD random access operation
Document for:	Discussion and decision

Summary
In this contribution, we discussed on the subband non-overlapping full duplex. 
Observation 1: While RAN2 is under discussion to decide specific conditions and relevant parameters for RO type selection and switching, RAN1 could still continue working on those conditions and mechanisms, including potential parameters to stay aligned with RAN2’s progress, especially for PRACH transmission re-attempt. 
Observation 2: Currently based on some agreements in RAN1 and RAN2, different threshold related parameters are being considered for PRACH repetition number selection procedure. 
Certain specified/configured conditions/prioritizations (e.g., rsrp-ThresholdMsg1- ROtype) for RO type selection in single PRACH transmission by RAN2 discussion.
e.g., rsrp-ThresholdMsg1-RepetitionNum2/4/8 for legacy-RO, rsrp-ThresholdMsg1-RepetitionNum2/4/8_SBFD for additional-RO, respectively to select repetition number in multiple PRACH transmission by RAN1 agreement.
Observation 3: When switching into other type of RO group, further discussion may need to clarify repetition number to be applied if Alt.2 is determined. 
For example, a certain PRACH repetition number to allow RO group switching is configured as 4.

Observation 4: In PRACH power control of RACH configuration Option 2, it is decided to use two separated RACH configurations for legacy-ROs and additional-ROs in RAN1#116 so that it is natural to have in any form of additional rach-ConfigCommon.
Observation 5: With purpose introducing RACH configuration Option 2 under coverage limited circumstance, when SBFD aware UE chooses additional-ROs with long preamble format for initial transmission, switching into legacy-ROs is not likely to increase chances for successful PRACH transmission. Resetting the power ramping counter restarts power ramping counting from the beginning only to delay the entire SBFD random access procedure.
Observation 6: Depending on location the UL subband and initial UL BWP, all or partial UL useable PRBs could be out of addressable range of frequency domain resource allocation for Msg3 in SBFD symbols.
Observation 7: In case it turns out that further power compensation is necessary for the Msg3 PUSCH transmit power control, remaining power offset can be adjusted by TPC command in RAR UL grant or DCI format.
Observation 8: With the same preamble formats not excluded, overlapping ROs may have the same RA-RNTI, and gNB may not distinguish whether the preamble is associated with legacy RACH configuration or additional RACH configuration in case of those collisions.

Proposal 1: For PRACH transmission re-attempt, for a certain number of times to switch into other type of ROs, either a new parameter corresponding to the specific/configured number of re-attempts or existing parameter (e.g. maxtrans_SBFD or preambleTransMax) should be considered.
Proposal 2: RAN1 to have common understanding how to select RO group type and its repetition number. Alt-1 is preferred.
Alt-1: RO type is selected first based on certain specified/configured conditions/prioritizations under RAN2 discussion, then apply legacy procedure to choose PRACH repetition number with rsrp-ThresholdMsg1-RepetitionNumX parameters in selected RO type based on RAN1 agreement.
The SBFD-aware UE selects between SBFD RO and legacy RO before selecting a set of Random Access resources.
Alt-2: RO type and repetition number could be simultaneously selected based on rsrp-ThresholdMsg1-RepetitionNum2/4/8 and rsrp-ThresholdMsg1-RepetitionNum2/4/8_SBFD based on RAN1 agreement.
If two RO types are selected simultaneously, one of RO type is selected based on certain specified/configured conditions/prioritizations under RAN2 discussion.
Proposal 3: For SBFD aware UE, consider the following options for RO group type switching if the earlier RO group fails:
Alt. 1: Always use the RO group of the same type (i.e., legacy-RO group or additional-RO group) with increased PRACH repetition number as the earlier RO group for the rest of the random access procedure.
Alt. 2: First use RO group of the same type as the earlier PRACH transmission for up to a certain PRACH repetition number, then switch to use RO group of the other type for the rest of the random access procedure.
Same concept in RO type switching for RACH re-attempt
Proposal 4: For RACH configuration Option 1, support Alt-1.
Alt-1: Shared ssb-SharedRO-MaskIndex configuration for Additional-ROs and Legacy-ROs. 
Proposal 5: For PRACH power control of RACH configuration Option 1, use additional power control parameter with corresponding existing parameter.
The additional power control parameter corresponding existing parameters are at least, preambleTransMax_SBFD in rach-ConfigGeneric.
Proposal 6: For PRACH power control of RACH configuration Option 2, use separate power control parameters configured with RACH-ConfigCommonSBFD-r19 which is newly defined for additional-RO in Rel.19.
Proposal 7: When a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure for RACH configuration Option 1 and Option 2, support Alt-1
Alt-1: Increase the power ramping counter.
FFS whether to introduce a power offset to compensate the power ramping difference for RACH configuration Option 2.
Proposal 8: Introduce a power offset to compensate the power ramping difference for RACH configuration Option 2.
Proposal 9: For definition of UL usable PRBs for Msg3 PUSCH transmission in SBFD symbols, support the following:
if the active UL BWP is the initial UL BWP, UL usable PRBs are determined as intersection between SBFD UL subband and the initial UL BWP, 
else if the active UL BWP is not the initial UL BWP, UL usable PRBs are determined as intersection between SBFD UL subband and the active UL BWP.
Proposal 10: For determining the frequency domain resource allocation for Msg3 PUSCH transmission in SBFD symbols, the RB numbering starts from the first RB of the UL usable PRBs.
Proposal 11: For determining the frequency domain resource allocation for Msg3 PUSCH transmission in SBFD symbols, either of two alternatives is preferred.
Alt 1: the maximum number of RBs for frequency domain resource allocation equals the number of UL usable PRB
Alt 2: the maximum number of RBs for frequency domain resource allocation equals min (number of UL usable PRB, number of RBs in the initial UL BWP)
Proposal 12: Considering no restriction on the combination of RO type of the latest PRACH transmission and the symbol type of following Msg3 PUSCH transmission, separate msg3-DeltaPreamble/deltaPreamble for additional RO (e.g., ) should be supported in RACH configuration Option 1.
Proposal 13: RAN1 to make a decision whether msg3-DeltaPreamble/deltaPreamble (if supported) depends on Msg3 PUSCH symbol type in Alt-1 or RO type used for latest PRACH transmission in Alt 2 for msg3 PUSCH power control in RACH configuration Option 1. 
Alt 2 is preferred.
Proposal 14: For determination of the Msg3 PUSCH transmission power and when separate preambleReceivedTargetPower for additional-ROs is configured for RACH configuration Option 2. 
preambleReceivedTargetPower related to the RO type should be used for calculation of latest PRACH transmission power for Msg3 transmit power control.
Proposal 15: RAN1 not to consider supporting a separate initial BWP for SBFD aware UEs.
Proposal 16: RAN1 to consider enhancement on Table 9.2.1-1 (PUCCH resource sets before dedicated PUCCH resource configuration) to secure configuration flexibility for in SBFD symbols. 
Proposal 17: With two separate RACH configurations in RACH configuration Option 2, same or different preamble formats by each PRACH configuration index can be configured by gNB. (i.e., one for legacy RACH configuration, one for additional RACH configuration).
Proposal 18: RAN 1 to decide how to interpret the parameter msg1-FrequencyStart in RACH configuration Option 2. 
In case the parameter msg1-FrequencyStart is reused in legacy RACH configuration, it is reinterpreted as the frequency offset of lowest RO in frequency domain with respective to the lowest PRB of UL usable PRBs, consistent with RACH configuration Option 1. 
In case the parameter msg1-FrequencyStart is used in additional RACH configuration, a separate parameter msg1-FrequencyStart indicates the frequency offset of lowest RO in frequency domain with respective to the lowest PRB of UL usable PRBs.

3GPP TSG RAN WG1 #120bis		R1-2501804
Wuhan, China, April 7th – 11th, 2025

Source:	vivo
Title:	Discussion on random access for Rel-19 SBFD
Agenda Item:	9.3.2
Document for:	Discussion and Decision

Conclusion
In this contribution, we make discussions on random access for Rel-19 SBFD and have the following observations and proposals. 

Proposal 1: For RACH configuration Option 1, shared ssb-SharedRO-MaskIndex configuration for Additional-ROs and Legacy-ROs is preferred.
Proposal 2: When a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure for RACH configuration Option 1 and Option 2, the power ramping counter increases. A power offset is introduced to compensate the power ramping difference for RACH configuration Option 2.
Proposal 3: For determination of the Msg3 PUSCH transmission power and when separate preambleReceivedTargetPower for additional-ROs is configured for RACH configuration Option 2.
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.

Proposal 4: The RB numbering starts from the first RB of the UL usable PRBs for Msg3 PUSCH transmission and the maximum number of RBs for frequency domain resource allocation equals the min {size of UL usable PRBs for Msg3 PUSCH transmission, number of RBs in the initial UL BWP}.
Proposal 5: For SBFD-aware UEs, support separate configuration of p0-nominal for Msg4 HARQ-ACK PUCCH in SBFD symbols.

3GPP TSG RAN WG1 Meeting #120-bis	                                                               R1-2501844
Wuhan, China, April 7th –April 11th 2025


Agenda Item:	9.3.2
Source:	TCL 
Title:	Discussion on SBFD random access operation
Document for:	Discussion and Decision 

Conclusion
In this contribution we discussed random access operation in SBFD symbols for both RRC and connected states, and idle/inactive states, and made the following observations and proposals.  

Observation 1: The following parameters have a direct impact on the UL power control of PRACH transmission in SBFD symbols: 
PreambleReceivedTargetPower 
PowerRampingStep
PowerRampingStepHighPriorit 
DeltaPreamble
PCMAX

Observation 2: For RACH configuration option 2, if no enhancements are made to prach-ConfiguationIndex, it will indicate the slots configured as UL by tdd-UL-DL-ConfigCommon.

Observation 3: By using the existing specification table (Table 9.2.1-1 in TS 38.213) for the transmission of HARQ-ACK of Msg4/MsgB in SBFD symbols, the PUCCH for HARQ-ACK of Msg4/MsgB will be located outside of the frequency resources of the UL subband.

Observation 4: When POs mapped to the SBFD symbols, UEs configured with UL subbands may not be able to receive the paging message, which can potentially degrade the performance of paging the UEs in SBFD symbols.

Observation 5: The Type-1 random access procedure may increase the latency of the random access procedure and fail to meet the objectives of random access in SBFD symbols.

Proposal 1: For the additional ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigCommon, the msg1-FrequencyStart of the additional RO can be reinterpreted as msg1-FrequencyStart + RB offset, where the RB offset is the number of RBs between the lowest legacy RO and the lowest additional RO. 

Proposal 2: For msg3 PUSCH FH in SBFD symbols, if the 2nd hop is based on the size of UL usable PRBs in table 8.3-1 is, it may necessary to change the threshold values (from 50 PRBs) to:
16 or 17 PRBs in case of DUD subband pattern 
25 in case of DU or UD subband pattern

Proposal 3: For the determination of Msg3 PUSCH transmission power in SBFD symbols, consider the configuration of the following parameters separately:
PreambleReceivedTargetPower
msg3-DeltaPreamble/deltaPreamble
msg3-alpha

Proposal 4: Define a new table for "cell-specific PUCCH resource common" that can be used for the transmission of HARQ-ACK for Msg4/MsgB in SBFD symbols.

Proposal 5: To define a new table for the cell-specific PUCCH used for HARQ-ACK transmission of Msg4/MsgB in SBFD symbols, the following options can be considered:
Option 1: Consider the starting RB of the UL subband as a starting point and keep the existing RB offset values in table 9.2.1-1 in TS 38.213.
Option 2: Introduce new RB offset values in a new table to align and position the cell –specific PUCCH within the bandwidth of the UL subband. 


Proposal 6: For cell-specific PUCCH in SBFD symbols, consider a separate intra-slot frequency hopping (intra-SlotFH) configuration in PUCCH-configCommon. 

Proposal 7: RAN1 to study Paging enhancement in the SBFD symbols. 

Proposal 8: RAN1 to reconsider supporting the Type-2 random access procedure for SBFD symbols, as it effectively reduces the latency challenges inherent in the Type-1 procedure in SBFD symbols.

3GPP TSG RAN WG1 #120bis			R1-2501866
Wuhan, China, April 7th – 11th, 2025
Agenda item:	9.3.2
Source: 	Spreadtrum, UNISOC
Title: 	Discussion on SBFD random access operation
Document for:	Discussion and decision

Conclusion
In this contribution, we made the following proposals.
When after certain (configured) number of times of RACH attempt in SBFD RACH occasions, UE switch to legacy RACH occasions, the target power is:
Power ramping counter should continue increasing after additional RO switches to legacy RO.
The power ramping step size follows the legacy RO configuration after switching
After switching, the target power level follow the 4-step RACH formula plus an offset, where the offset is 
OFFSET = (N -1) × (PREAMBLE_POWER_RAMPING_STEP(additional-RO)  -  PREAMBLE_POWER_RAMPING_STEP(legacy-RO))
N is the power ramping counter when switching back to legacy RO
For RACH configuration Option 1 with Alt 1-1, separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs.
For determination of the Msg3 PUSCH transmission power and when separate preambleReceivedTargetPower for additional-ROs is configured for RACH configuration Option 2
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols..
New msg3-Alpha is introduced for SBFD symbols for MSG3 PUSCH.
For determining the frequency domain resource allocation for Msg3 PUSCH transmission in SBFD symbols, the RB numbering starts from the first RB of the UL usable PRBs and the maximum number of RBs for frequency domain resource allocation equals the number of RBs in the initial UL BWP.

3GPP TSG RAN WG1 #120bis                                                R1-2501908
Wuhan, China, April 7th – 11th, 2025

Source:	ZTE Corporation, Sanechips
Title:	Discussion on SBFD random access operation
Agenda item:	9.3.2
Document for:	Discussion and Decision
 

Conclusion
According to the discussion above, we have the following observations and proposals.
SBFD random access operation in RRC CONNECTED mode
Observation 1: If an RO is configured in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon, reinterpretation of parameter msg1-FrequencyStart with respective to the lowest PRB of UL usable PRBs may render the RO invalid because it is outside the range of UL usable PRBs.
Proposal 1: For RACH configuration Option 1, for determination of lowest RO of additional-ROs in SBFD symbols, the parameter msg1-FrequencyStart in rach-ConfigCommon is reinterpreted as the frequency offset of lowest RO in frequency domain with respective to the lowest PRB of UL usable PRBs ONLY if there is no legacy RO configured in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon. 
Proposal 2: For RACH configuration Option 1, the RO validation determination for SBFD aware UEs can be performed according to the following steps, 
Firstly, legacy valid ROs are determined based on legacy RO validation rule. 
Secondly, additional valid ROs are obtained within all configured ROs in SBFD symbols according to the new RO validation rule.
Proposal 3: Regarding power control mechanism of RACH transmission reattempt after RO resource type switching for RACH configuration Option 1 and Option 2, 
Increase the power ramping counter and a power offset parameter, e.g., POWER_OFFSET_RA, can be introduced to compensate the difference in previous power ramping for determining the value of PREAMBLE_RECEIVED_TARGET_POWER. 
For RACH configuration Option 2, POWER_OFFSET_RA is set to (PREAMBLE_POWER_RAMPING_COUNTER – 1) × (PREAMBLE_POWER_RAMPING_STEP_SBFD – PREAMBLE_POWER_RAMPING_STEP). 
For RACH configuration Option 1, the value of POWER_OFFSET_RA is set to zero.
Observation 2: According to the existing rules(i.e., Alt-2), the Msg3 FDRA range determined in SBFD symbols on the non-initial UL BWP may not overlap with the UL subband. 
Proposal 4: For determining the frequency domain resource allocation for the Msg3 PUSCH transmission in SBFD symbols, the RB numbering starts from the first RB of the UL usable PRBs and the maximum number of RBs for frequency domain resource allocation equals the min {size of UL usable PRBs, number of RBs in the initial UL BWP}. 
Observation 3: The MSB(s) of the frequency domain resource allocation information is used to indicate the frequency offset for 2nd hop, which will seriously affect the scheduling flexibility of Msg3 PUSCH. 
Proposal 5: For frequency domain resource allocation of the Msg3 PUSCH transmission within the UL usable PRBs, the following method should be supported,
For initial transmission: the number of bits actually utilized for frequency domain resource allocation can be determined based on the size of UL usable PRBs and these bits occupy the LSBs of the 14 bits FDRA field. The MSB(s) of the 14 bits FDRA field can be employed for indicating the frequency offset for the 2nd hop. 
For retransmission: the FDRA field size is determined according to the size of the initial UL BWP. The number of bits actually utilized for frequency domain resource allocation can be determined based on the size of UL usable PRBs and these bits occupy the LSBs of the FDRA field. The MSB(s) of the FDRA field can be employed for indicating the frequency offset for the 2nd hop.
Proposal 6: For Msg3 PUSCH power control, 
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols; preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols. 
Support separated msg3-DeltaPreamble/deltaPreamble configurations for Msg3 PUSCH transmission when msg3-PUSCH and PRACH are transmitted over different types of resources.
Proposal 7: Support separated msg3-DeltaPreamble/deltaPreamble configurations for Msg3 PUSCH transmission when msg3-PUSCH and PRACH are transmitted over different types of resources.
Proposal 8: About configuring PRACH mask index for additional ROs under Option 1, Alt-2 is supported. 
Alt-2: Separated ssb-SharedRO-MaskIndex configurations for additional ROs and legacy ROs. 
SBFD random access operation in RRC IDLE/INACTIVE mode
Observation 4: Some cell common downlink signals/channels are transmitted within the frequency range of CORESET#0, e.g., SSB, SI message and paging, etc. 
Proposal 9: For avoiding impact the reception of cell common transmissions by legacy UEs, the following options can be considered for determining the UL usable PRBs for SBFD RACH operation in RRC IDLE/INACTIVE mode, 
Option 1: A separate initial BWP is configured to SBFD UEs for avoiding overlapping between UL subband and CORESET#0.
Option 2: If the UL subband overlaps with some frequency domain resources of the CORESET#0, puncturing based solution is supported for DL cell common transmissions.
RRC parameters
Proposal 10: Endorse the following RRC parameters for RACH configuration Option 1:
Proposal 10: Endorse the following RRC parameters for RACH configuration Option 1:

Proposal 11: Parameters in rach-ConfigCommon except for rsrp-ThresholdSSB-SUL can be included in the additional RACH configuration for RACH configuration Option 2. If a parameter is not provided in the additional RACH configuration, UE uses the corresponding parameter in the legacy RACH configuration.

 

3GPP TSG RAN WG1 #120bis			R1-2501929
Wuhan, China, April 7th – 11th, 2025
                                    
Agenda Item:	9.3.2
Source:	InterDigital, Inc.
Title:	On SBFD random access operation
Document for:	Discussion and Decision

Conclusion
In this contribution, we discussed issues on random access procedures in SBFD systems. From the discussions, we made following observations and proposals:
[2.2.1 Power ramping in switching between SBFD and non-SBFD ROs]
Observation 1. In determining the power ramping value after switching between legacy-ROs and additional-ROs, using Alt-2 based on resetting the power ramping could result in latency in the random-access procedure.
Proposal 1. In determining the power ramping value after switching between legacy-ROs and additional-ROs, do not support Alt-2.
Proposal 2. In determining the power ramping value after switching between legacy-ROs and additional-ROs, support Alt-1.
Consider calibrating the power ramping counter after switching, based on power ramping step before switching, power ramping counter before switching, and the power ramping step after switching.
[2.2.2 Mask index indication in additional-ROs]
Observation 2. The mask index specific to additional-ROs can be used for configuring limitations on selecting ROs based on different conditions, such as PRACH UL power.
Observation 3. Performance of received PDSCH signal in an SBFD slot is impacted by the location of a RO within the UL sub-band. The closer the RO is to the edge of the UL sub-band, the greater the degradation, in terms of BLER, to the PDSCH signal in the DL sub-band.
Observation 4. SBFD-aware UEs may need to fallback to use legacy-ROs, for example due to PRACH power limitations in FDM-ed additional-ROs in SBFD symbols.
Proposal 3. In configuring ssb-SharedRO-MaskIndex, support Alt-2 on separate PRACH mask index indications for additional ROs and legacy ROs.
Proposal 4. If separate PRACH mask index indications for additional ROs and legacy ROs is supported, support indicating limitations on using the FDM-ed ROs in association with PRACH UL power thresholds.
Proposal 5. For SBFD-aware UEs support additional condition(s) for RO selection in FDM-ed ROs in SBFD symbols.
[2.2.3	UL Power Control Parameters]
Proposal 6. Support configuring different PRACH power control parameters in addition to preambleReceivedTargetPower, including preambleTransMax and PcMax, for PRACH transmission in legacy-ROs and additional-ROs.
[2.2.5 Early Indication of support for SBFD]
Observation 5. During random access procedure, the SBFD-aware UE can indicate its capability and support for SBFD operation via Msg3.
Proposal 7. Support early indication for SBFD-aware UE in RRC-Idle/Inactive modes to indicate UE’s  support of SBFD operation as part of random-access, for example, via
Indication as part of Msg3. 
[2.3 Random Access Operation in RRC-IDLE/INACTIVE mode]
Observation 6. During cell selection or initial access, the SBFD-aware UE in RRC-IDLE/INACTIE mode could check cells’ information on supporting SBFD operation, so that UE could prioritize cells with SBFD operation.
Observation 7. During cell selection, the SBFD-aware UE can determine to connect to the selected cell based on SBFD or non-SBFD operation according to the measured received power and potential CLI. This prevents latency and ping-ponging affects.
Proposal 8. In cell selection or initial access, support indicating cells’ support on SBFD operation (e.g., in SIB1) to be used for cell ranking by SBFD-aware UEs. 
Proposal 9. Support prioritization rules for selecting the cells that support SBFD operation based on RSRP or potential CLI, during initial access or cell selection procedures for SBFD-aware UEs in RRC-IDLE/INACTIVE modes. 
[2.4 Performance analysis for repetition based PRACH transmissions across SBFD symbols]
Observation 8. PRACH preamble repetition in SBFD symbols enhances RACH detection performance in both contention-based and contention-free RACH occasions, where the RACH detection performance improves as the number of PRACH repetition occasions increases.
Proposal 10. Support PRACH repetition in SBFD symbols, for both contention-based and contention-free RACH occasions.

3GPP TSG RAN WG1 #120bis		R1-2501990
Wuhan, China, April 7th – 11th, 2025

Source:	CATT
Title:	Discussion on SBFD random access operation
Agenda Item:	9.3.2
Document for:	Decision

Conclusion
In this contribution, we share our views on SBFD random access operation. The proposals are summarized as follows:
Proposal 1: For RACH configuration Option 1, separate ssb-SharedRO-MaskIndex can be configured for additional ROs and legacy ROs.
If ssb-SharedRO-MaskIndex configured for additional ROs is absent, reuse ssb-SharedRO-MaskIndex configured for legacy ROs.
Proposal 2: SBFD aware UE increases the power ramping counter when switching RO type in PRACH transmission re-attempt in one RACH procedure for RACH configuration Option 1 and Option 2.
Introduce a power offset to compensate the power difference for RACH configuration Option 2, e.g. POWER_OFFSET_SBFD=(PREAMBLE_POWER_RAMPING_COUNTER-1)*(PREAMBLE_POWER_RAMPING_STEP_SBFD - PREAMBLE_POWER_RAMPING_STEP)
Proposal 3: For determination of the Msg3 PUSCH transmission power and when separate preambleReceivedTargetPower for additional-ROs is configured for RACH configuration Option 2
preambleReceivedTargetPower configured for legacy RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional RO is used if Msg3 PUSCH is transmitted in SBFD symbols.
Proposal 4: No need to configure separate msg3-DeltaPreamble/deltaPreamble for Msg3 PUSCH transmitted in SBFD symbols and non-SBFD symbols.
Proposal 5: TPC Command in RAR can be used to adjust the Msg3 PUSCH transmission power in both SBFD symbols and non-SBFD symbols.
Proposal 6: It is necessary to clarify that the agreements on the determination of frequency offset for Msg3 PUSCH are applied for Msg3 PUSCH in SBFD symbols only.

3GPP TSG RAN WG1 #120-bis							R1-2502014
Wuhan, China, April 7th – 11th, 2025

Source: 	Tejas Networks
Title: 	Discussion on SBFD random access operation
Agenda Item:	9.3.2
Document for: 	Discussion and Decision

Conclusion
Proposal 1: Use the existing association period between SS/PBCH block and PRACH occasion mentioned in TS38.213 to SBFD slots as well.
Proposal 2: No new rule is required for SBFD RO to SS/PBCH mapping pattern in RRC_CONNECTED mode.
Proposal 3: We prefer Alt-1 (shared configuration) over Alt-2(separate configuration) for Option 1, as Alt- 1 is simple to implement and got less configuration complexity.
Proposal 4: Introduce separate  parameters as an offset-based configuration through RRC signaling.
Proposal 5: Introduce a power offset compensation mechanism for PRACH re-attempts when switching RO types.
Proposal 6: Delegate the definition of detailed conditions and prioritization, including switching criteria, to RAN2 for finalization.
Proposal 7: For FR1, introduce new parameter “time offset to RACH subframe” to determine the subframe number for ROs in SBFD symbols and time offset will have granularity of slot.
Proposal 8: Indicate valid RO created by the additional RACH configuration using bit map with bit packer. 
Proposal 9: Consider repetition pattern and invalid RO in non SBFD symbols to have a shortened bit map.
Proposal 10: Alt-3 (bit map with bit packer) is preferred option compared to other options, as the valid ROs are clearly indicated by the base station in the additional RACH configuration.
Proposal 11: Separate ‘ssb-SharedRO-MaskIndex’ configurations for Additional-ROs and Legacy-ROs should be supported for Option 2 as it offers flexibility.
Proposal 12: If the RACH is initiated in the SBFD slots, the available Slot counting for MSG3 PUSCH repetition will count only SBFD slots.
Proposal 13: For Msg3 PUSCH transmission in SBFD symbols, adopt the Alt-1 approach, wherein: 
RB numbering starts from the first RB of the initial UL usable PRBs.
The maximum number of RBs for FDRA shall be set equal to the number of RBs in the initial UL BWP.
Proposal 14: For RACH Configuration Option 2, apply the ‘preambleReceivedTargetPower’ associated with the respective RACH configuration (legacy or additional) based on whether Msg3 PUSCH transmission occurs in non-SBFD or SBFD symbols. 
Proposal 15: preambleReceivedTargetPower, msg3-DeltaPreamble/deltaPreamble and TPC Command in RAR are required for MSG3 in SBFD symbols.
Proposal 16: For SBFD operation, Msg3 PUSCH transmission shall be scheduled in the same symbol type (SBFD or non-SBFD) as the associated PRACH preamble (Msg1) transmission.
Proposal 17: Reinterpret initial UL BWP   as initial UL usable PRBs   for cell specific PUCCH transmission in SBFD symbols and reuse the Table 9.2.1-1 in TS 38.213 for determining PUCCH resource sets in SBFD symbols.

Proposal 18: To determine the lowest PRB indies of the PUCCH transmission in the first hop and second hop in SBFD symbols, reinterpreting initial UL BWP  as initial UL usable PRBs .
Proposal 19: Support SDT along with 4 step and 2 step RACH in SBFD symbols.

3GPP TSG RAN WG1 #120bis		                         R1-2502021
Wuhan, China, April 7th – 11st, 2025
Agenda Item:	9.3.2
Source:	China Telecom
Title:	Discussion on SBFD random access operation 
Document for:	Discussion and Decision

Conclusions
In this contribution, we discuss SBFD random access operation and have following proposals:
Proposal 1:  When a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure for RACH configuration Option 1 and Option 2, Alt-1 is supported, i.e., increase the power ramping counter.
Proposal 2: SSB-RO mapping cycle is determined separately for legacy RO and additional RO. And indexing of the PRACH occasion is separately indicated by the mask index value for legacy RO and additional RO.
Proposal 3: For RACH configuration Option 1, separate ssb-SharedRO-MaskIndex configurations are supported for Additional-ROs and Legacy-ROs, i.e., Alt-2 is supported.

TDoc file reading error

3GPP TSG RAN WG1 #120bis		     	R1-2502085
Wuhan, China, April 7th – 11th, 2025

Source:	NEC
Title:	Discussion on random access for subband non-overlapping full duplex
Agenda Item:	9.3.2
Document for: 	Discussion and Decision

Conclusion 
In this contribution, we discussed SBFD for NR duplex operation. Observations and Proposals are summarized as follows: 
Proposal 1:
For RACH configuration Option 1 and Option 2 about power ramping when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure,
Support Alt-1: Increase the power ramping counter.
Proposal 2: 
For SBFD-aware UEs and CFRA triggered by BFR or SI request, support one of the following for UE to determine the RO resource
New table can be defined for SBFD aware UE to determine the RO resource of SSB for PRACH transmission on SBFD symbols 
New column is added in PRACH Mask Index/msgA-SSB-SharedRO-MaskIndex/ssb-SharedRO-MaskIndex values table for SBFD aware UE to determine the RO resource of SSB for PRACH transmission on SBFD symbols 
gNB configure the applied symbol type (SBFD symbol or non-SBFD symbol or both) or RO Type for CFRA
Proposal 3:
For Msg3 PUSCH enhancements, the following aspects can be supported.
The definition of UL usable PRBs for Msg3 PUSCH transmission can be the PRB number part or whole within the UL subband.
PUSCH repetition transmission can across SBFD symbols and non-SBFD symbols if legacy RO is selected for Msg1 transmission
Proposal 4:
The aspects below should be considered for SDT enhancements on SBFD symbols:
PUSCH allocation/configuration in the UL subband of SBFD symbols
Valid PO determination on SBFD symbols
The PO mapping relationship with SSB for PO in SBFD symbols 
Proposal 5: 
Study paging enhancement on SBFD symbols.
Proposal 6:
 For failed PRACH attempts in SBFD slots, the UE will wait for dedicated UL slots to re-attempt PRACH. 

3GPP TSG RAN WG1 #120bis	R1-2502122
Wuhan, China, April 7th – 11th
Agenda item:	9.3.2
Source: 	Fujitsu
Title:	Discussion on SBFD random access operation
Document for:		Discussion and decision

Conclusion
According to the discussions above, we have the following proposals. 
Proposal 1: For SBFD aware UEs, for the PUSCH scheduled by RAR and the Msg3 PUSCH retransmission scheduled by DCI format 0_0 with CRC scrambled with TC-RNTI on a non-initial UL BWP, to extend the range of addressable usable PRBs in SBFD symbols, the RB numbering for RIV provided in the FDRA field in the RAR/DCI starts from the first RB of UL usable PRBs for the active UL BWP.
UE does not expect that the PRBs for the PUSCH transmission in SBFD symbols to be overlapped with PRBs outside UL usable PRBs for the active UL BWP.
Proposal 2: For SBFD aware UEs, for the PUSCH scheduled by RAR, to extend the range of addressable usable PRBs in SBFD symbols, truncate/insert bits in the FDRA field in the RAR according to the size of UL usable PRBs for the active UL BWP.
Proposal 3: For SBFD aware UEs, for Msg3 PUSCH transmission and PUSCH scheduled by RAR in CFRA (i.e. PUSCH scheduled by RAR UL grant and Msg3 PUSCH retransmission), reuse Table 8.3-1 in TS 38.213 for determination of the frequency offset for the 2nd hop in SBFD symbols based on the size of UL usable PRBs for the active UL BWP.
Proposal 4: For RACH configuration Option 2, the Msg3 PUSCH transmission power is determined in the same way as that of RACH configuration Option 1. 
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols.
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.
Proposal 5: For separate power control for Msg3 PUSCH on non-SBFD symbols and SBFD symbols, the following separate power control parameters are supported. 
The first set of parameters including msg3-DeltaPreamble/deltaPreamble and msg3-Alpha is configured for Msg3 PUSCH on non-SBFD symbols. The second set of parameters including msg3-DeltaPreamble-SBFD/deltaPreamble-SBFD and msg3-Alpha-SBFD is configured for Msg3 PUSCH on SBFD symbols.
If a parameter in the second set is not configured, the corresponding parameter in the first set is used for Msg3 PUSCH on SBFD symbols.
A parameter in the second set is configured under the same parent RRC IE of the corresponding parameter in the first set.
Proposal 6: For PUCCH (conveying HARQ-ACK for Msg4), separate p0-nominal-SBFD for SBFD symbols is supported. 
p0-nominal-SBFD is optionally configured in PUCCH-ConfigCommon (the parent RRC IE of the legacy p0-nominal).
If p0-nominal-SBFD is configured, the legacy p0-nominal is used for PUCCH in non-SBFD symbols, and p0-nominal-SBFD is used for PUCCH in SBFD symbols.
If p0-nominal-SBFD is not configured, the legacy p0-nominal is used for both PUCCH in non-SBFD symbols and PUCCH in SBFD symbols.

3GPP TSG RAN WG1 #120bis			R1-2502158 
Wuhan, China, April 7th – 11th, 2025

Source: 	CMCC
Title:	Discussion on SBFD random access operation
Agenda item:	9.3.2
Document for:	Discussion & Decision
1	

Conclusions
In this contribution, we discussed random access operation in SBFD, and the following proposals are made.
Proposal 1. For RACH configuration Option 1 with Alt 1-1, for determination of lowest RO of additional-ROs in SBFD symbols, the parameter msg1-FrequencyStart in rach-ConfigCommon is reinterpreted as the frequency offset of lowest RO in frequency domain with respective to the lowest PRB of UL usable PRBs ONLY if there is no legacy-RO configured in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon and the lowest PRB of the UL usable PRBs is not PRB 0.
Proposal 2. For both RACH configuration Option 1 and Option 2, when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure, support Alt-1: Increase the power ramping counter
Also introduce a power offset to compensate the power ramping difference for RACH configuration Option 2, e.g., POWER_OFFSET_AdditionalRO = (PREAMBLE_POWER_RAMPING_COUNTER– 1) × (PREAMBLE_POWER_RAMPING_STEP_AdditionalRO – PREAMBLE_POWER_RAMPING_STEP)
Which PREAMBLE_POWER_RAMPING_STEP is the parameter configured for legacy_ROs, PREAMBLE_POWER_RAMPING_STEP_AdditionalRO is the parameter configured for additional_ROs.
Proposal 3. For RACH configuration Option 1, Alt-1: shared ssb-SharedRO-MaskIndex configuration is applied for Additional-ROs and Legacy-ROs under the same FeatureCombinationPreambles configuration.
Proposal 4. For determining the frequency domain resource allocation for Msg3 PUSCH transmission in SBFD symbols, the RB numbering starts from the first RB of the UL usable PRBs and the maximum number of RBs for frequency domain resource allocation equals the number of RBs in the initial UL BWP.
Proposal 5. For RACH configuration Option 1, the same msg3-DeltaPreamble/deltaPreamble configuration is used for Msg3 PUSCH transmission in non-SBFD symbols and SBFD symbols.
Proposal 6. For determination of the Msg3 PUSCH transmission power for RACH configuration Option 2:
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols;
legacy msg3-DeltaPreamble/deltaPreamble is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
additional msg3-DeltaPreamble/deltaPreamble is used if Msg3 PUSCH is transmitted in SBFD symbols.
Proposal 7. For determination of of Msg3 PUSCH transmission power:
For RACH configuration Option 1, reuse the legacy rule.
For RACH configuration Option 2, reuse the legacy rule which:
powerRampingStep/powerRampingStepHighPriority configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols; 
powerRampingStep/powerRampingStepHighPriority configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.
Proposal 8. For SBFD aware UEs, support separate configuration of p0-nominal for SBFD symbols.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502242
Wuhan, China, April 7 – 11, 2025

Agenda Item:	9.3.2
Source:	Huawei, HiSilicon
Title:	On subband full duplex random access operation
Document for:	Discussion and Decision

Conclusion
With the discussion above, we have the following observations and proposals.
Observation 1: PRACH transmission over different FDMed ROs result in different levels of UE-to-UE CLI and gNB-to-gNB CLI, i.e., the FDMed ROs that are farther away from PDSCH results in less CLI while the FDMed ROs closer to PDSCH resources results in the stronger CLI, which implies that separate target PRACH receive power, maximum transmission power for different FDMed ROs in SBFD symbols are beneficial.

Proposal 1: For RACH configuration Option 1, support shared ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs.
Proposal 2: When a SBFD-aware UE switches from additional-ROs to legacy-ROs or from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure for RACH configuration Option 1 and Option 2, the power ramping counter is incremented by 1 and a power offset is applied to compensate the power ramping difference
Additional-ROs to legacy-ROs: POWER_OFFSET = PREAMBLE_POWER_RAMPING_COUNTER – 1) × (PREAMBLE_POWER_RAMPING_STEP_ADDITIONAL_RO – PREAMBLE_POWER_RAMPING_STEP)
Legacy-ROs to additional-ROs (if supported): POWER_OFFSET = (PREAMBLE_POWER_RAMPING_COUNTER – 1) × (PREAMBLE_POWER_RAMPING_STEP – PREAMBLE_POWER_RAMPING_STEP_ADDITIONAL_RO)
Proposal 3: For RACH configuration Option 1, the maximum transmission power for PRACH can be configured for the additional-ROs.
Proposal 4: For RACH configuration Option 2, for the support of separate power control of PRACH transmission in additional-ROs and legacy-ROs 
Introduce a new parameter to limit the maximum transmission power for PRACH in additional-ROs
Support separate powerRampingStep, preambleTransMax for additional-ROs
Proposal 5: For RACH configuration Option 2, introduce more candidate values for preambleTransMax and powerRampingStep, if they can be separately configurated for additional-ROs
Add {n1, n2} into the candidate values of preambleTransMax
Add {dB8, dB10, dB12} into the candidate values of powerRampingStep
Proposal 6: For RACH configuration Option 2, support separate power control for different FDMed additional-ROs by configuring separate parameter sets for different FDMed additional-ROs, including preambleReceivedTargetPower and preamble maximum output power.
Proposal 7: A separate parameter msg3-DeltaPreamble which defines the power offset between Msg3 PUSCH and RACH preamble transmission in the additional-ROs is supported.
Proposal 8: For determination of the Msg3 PUSCH transmission power and when separate preambleReceivedTargetPower for additional-ROs is configured for RACH configuration Option 2
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.

3GPP TSG RAN WG1 #120bis                                    R1-2502278
Wuhan, China, April 7th – 11th, 2025

Source:	OPPO
Title:	Discussion on SBFD random access operation
Agenda Item:	9.3.2
Document for:	Discussion and Decision

Conclusions
This contribution concludes with the following observations and proposals:
Observation 1: For the power ramping when UE switches RO type in one PRACH procedure, Alt-1 may be beneficial from perspective of reducing latency of random access procedure.
Observation 2: For the power ramping when UE switches RO type in one PRACH procedure, Alt-2 may be beneficial from perspective of interference management.
Proposal 1: For the power ramping when UE switches RO type in one PRACH procedure, Alt-1 with introducing a power offset to compensate the power ramping difference for RACH configuration option 2 is slightly preferred.
Proposal 2: For determination of the Msg3 PUSCH transmission power and when separate preambleReceivedTargetPower for additional-ROs is configured for RACH configuration Option 2: 
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.
Observation 3: For RACH configuration option 1, considering that preambleReceivedTargetPower has already been agreed to be separately configured for additional RO and legacy RO to cope with different CLI levels in SBFD symbols and non-SBFD symbols and same PRACH format would be used for both legacy RO and additional RO, so it is not necessary to separate configure msg3-DeltaPreamble/deltaPreamble for Msg3 PUSCH in SBFD symbols and non-SBFD symbols.
Proposal 2: For RACH configuration option 2, support separate configuration of msg3-DeltaPreamble/deltaPreamble for Msg3 PUSCH in SBFD symbols and non-SBFD symbols.
Proposal 3: Support to separate configure msg3-Alpha for Msg3 PUSCH in SBFD symbols and non-SBFD symbols.
Proposal 4: For the closed loop power control parameter of Msg3 PUSCH, RAN1 needs to discuss how to use the to determine the Msg3 PUSCH transmission power in case of the RO type of at least one PRACH attempt and the symbol type of Msg3 PUSCH do not correspond.
Proposal 5: For determination of the Msg3 PUSCH transmission power when separate power ramping step for legacy RO and additional RO is configured, use the corresponding power ramping step based on the symbol type of Msg3 PUSCH transmission to determine total power ramp-up , specifically,
If Msg3 PUSCH is transmitted in non-SBFD symbols, the total power ramp-up to determine Msg 3 PUSCH transmission power ;
If Msg3 PUSCH is transmitted in SBFD symbols, the total power ramp-up to determine Msg 3 PUSCH transmission power .
Proposal 6: For determining the frequency domain resource allocation for Msg3 PUSCH transmission in SBFD symbols, support Alt-1: the RB numbering starts from the first RB of the UL usable PRBs, and the maximum number of RBs for frequency domain resource allocation equals to size of UL usable PRB.

3GPP TSG RAN WG1 #120bis		R1-2502316
Wuhan, China, April 7th – 11th, 2025

Agenda Item: 	9.3.2
Source: 	Sony 
Title: 	SBFD RACH operations
Document for: 	Discussion / decision

Conclusion
In this contribution, we discuss some operations issues on PRACH in SBFD, and we observe the following:
Observation 1: Having common PRACH parameters for the two separate PRACH configurations in PRACH configuration Option 2 for SBFD would reduce configuration flexibility.  If the motivation of having some common PRACH parameters is to reduce RRC signalling, then PRACH configuration Option 1 can be used.
Observation 2: FDRA range of the RAR and DCI 0_0 may not be able to schedule Msg3 within the UL useable RBs in SBFD OFDM symbols of an active BWP.



We therefore propose the following:
Proposal 1: For PRACH configuration Option 2 (i.e., Use two separate PRACH configurations, including one legacy RACH configuration and one additional PRACH configuration), all the parameters currently in rach-ConfigCommon are included in the additional PRACH configuration.
Proposal 2: For determining the frequency domain resource allocation for Msg3 PUSCH transmission in SBFD symbols, the RB numbering starts from the first RB of the UL usable PRBs and the maximum number of RBs for frequency domain resource allocation equals the number of RBs in the initial UL BWP (i.e. Alt 1).

3GPP TSG RAN WG1 #120bis	R1-2502366
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.3.2
Source:	Samsung
Title:	Random access on SBFD resources
Document for:	Discussion

Conclusion
In this contribution, we made the following proposals:

Proposal 1: For RACH configuration Option 1, for power ramping when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in a PRACH transmission re-attempt in one RACH procedure, support:
Alt-1: Increase the power ramping counter
Proposal 2: For RACH configuration Option 2, the association period and association pattern period of additional ROs are configured an integer multiple of the association period and association pattern period of the legacy ROs.
Proposal 3: For RACH configuration Option 2, support separate power control parameters for the PRACH transmission and UE power ramping behavior in additional-ROs and legacy-ROs:
preambleReceivedTargetPower
powerRampingStep
preamble maximum output power
preambleTransMax
powerRampingStepHighPriority
Proposal 4: For RACH configuration Option 2, for power ramping when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in a PRACH transmission re-attempt in one RACH procedure, support:
Alt-1: Increase the power ramping counter
Proposal 5: For RACH configuration Option 1, support:
Alt-2: Separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs
Proposal 6: The existing RACH Msg.2 (RAR) reception procedure is reused for random access in SBFD symbols.
Proposal 7: For determining the frequency domain resource allocation for Msg.3 PUSCH transmission in SBFD symbols, the RB numbering starts from the first RB of the UL usable PRBs and the maximum number of RBs for frequency domain resource allocation equals the number of RBs in the initial UL BWP.
Proposal 8: For determination of the Msg.3 PUSCH transmission power, the same rule is applied to RACH configuration option 2. 
Proposal 9: For determination of the Msg.3 PUSCH transmission power, RAN1 to decide whether or not to use  when the used RO type and symbol type of the Msg.3 PUSCH are different (as in Case 2 or 3). For example, 
PREAMBLE_POWER_RAMPING_COUNTER can be reused regardless of the used RO types or
PREAMBLE_POWER_RAMPING_COUNTER is reset
Proposal 10: For support of separate open-loop power control on SBFD symbols for PUCCH corresponding to Msg.4 reception, support separate configuration of p0-nominal on SBFD symbols for both RACH configuration options.
Proposal 11: For SBFD-aware UEs in RRC_IDLE mode, support an Early Indication mechanism.
Proposal 12: For SBFD-aware UEs in RRC_IDLE mode, L3-based Early Indication is supported as baseline.

3GPP TSG RAN WG1 #120bis		  R1-2502404
Wuhan, China, April 7th – 11th, 2025

Source:	Panasonic
Title: 	Discussion on SBFD random access operation
Agenda Item:		9.3.2
Document for:	Discussion

Conclusion
In this contribution, we made the following proposals. 
Proposal 1: For power ramping for legacy-ROs and additional-ROs, support the following.
For RACH configuration Option 1, apply Alt-1.
For RACH configuration Option 2, 
if the same preamble format is configured for legacy-ROs and additional-ROs, apply Alt-1.
if different preamble formats are configured for legacy-ROs and additional-ROs, apply Alt-2.
Proposal 2: For Msg3 PUSCH transmission power for RACH configuration Option 2, support the following (i.e., same as RACH configuration Option 1).
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.
Proposal 3: For ssb-SharedRO-MaskIndex configuration for RACH configuration Option 1, support Alt-1.

3GPP TSG RAN WG1 #120-bis	R1-2502406  
Wuhan, China, April 07 – April 11, 2025

Agenda item:		   9.3.2
Source:	Nokia, Nokia Shanghai Bell
Title:	SBFD random access operation
Document for:		Discussion and Decision

Conclusion
In this contribution, the following observations are noted:
Observation 1 For Option 2, some parameters configuring the legacy ROs and the additional ROs can have the same values.
Observation 2 For RACH configuration Option 2, considering only two separate preambleReceivedTargetPowers, one for the legacy RO and one for the additional RO, will result in a biased Msg3 PUSCH power in case the preambleReceivedTargetPowers are selected for Msg3 PUSCH power based on Msg3 symbol type.
Observation 3 For RACH configuration Option 2, considering only two separate preambleReceivedTargetPowers, one for the legacy RO and one for the additional RO, will result in a biased Msg3 PUSCH power in case the preambleReceivedTargetPowers are selected for Msg3 PUSCH power based on Msg1 RO type.
In addition, the following are proposed:
Proposal 1 For Option 2, in case the legacy ROs and the additional ROs have the same value for one of the RACH configuration mandatory parameters. Only the legacy RACH configuration will be configured with this parameter.
Proposal 2 For Option 2, in case the SBFD aware UEs did not receive a dedicated mandatory parameter in the additional RACH configuration, the SBFD-aware UEs determine this dedicated parameter from the legacy RACH configuration.
Proposal 3 For determination of the Msg3 PUSCH transmission power and when separate preambleReceivedTargetPower for additional-ROs is configured for RACH configuration Option 2:
-	preambleReceivedTargetPower configured for legacy-RO plus a parameter δ are used if Msg3 PUSCH is transmitted in non-SBFD symbols and Msg1 is transmitted on legacy RO.
-	preambleReceivedTargetPower configured for additional-RO minus a parameter δ are used if Msg3 PUSCH is transmitted in SBFD symbols and Msg1 is transmitted on additional RO.
- δ is an additional power parameter configured by the NW.
Proposal 4 For RACH configuration Option 1 and Option 2, support separate configuration of msg1-RepetitionTimeOffsetROGroup and preambleTransMax-Msg1-Repetition for PRACH transmission with preamble repetitions within additional-ROs and PRACH transmission with preamble repetitions within legacy-ROs.

3GPP TSG-RAN WG1 Meeting #120-bis	R1-2502421
Wuhan, P. R. China, April 7th – 11th 2025

Agenda Item:	9.3.2
Source:	Ericsson
Title:	SBFD random access operation
Document for:	Discussion, Decision

Conclusion
In the previous sections we made the following observations: 
Observation 1	PCMAX not only affects PRACH but also other UL signals and channels why a change in PCMAX must not be done without considering the consequences of these other signals and channels.
Observation 2	PRACH is an infrequent transmission and any change in PCMAX will have negligible effect on UE-to-UE CLI compared to other, more frequent UL transmissions.
Observation 3	RAN2 has agreed to support fallback, implying UE have already attempted transmitting PRACH with different RO types, i.e., no additional preambleTransMax is necessary.
Observation 4	Legacy RACH provides ample transition time both before and after a PRACH preamble transmission. Additional transition margins are not necessary.
Observation 5	There is no need to define a separate RA-RNTI for additional ROs.
Observation 6	Allowing the UE to freely choose from both legacy ROs and additional RO for CFRA triggered by PDCCH order would result in unnecessary resource overhead to uncertain benefit.
Observation 7	In a range limited PRACH, where the path delay and not power is the limiting factor, a shared power ramping counter between different PRACH formats with different range properties may increase power too much and may cause the gNB receiver to saturate.
Observation 8	Reusing the repetition counter for different preamble formats with different preambleReceivedTargetPower configurations will reduce PRACH capacity.
Observation 9	Reusing the repetition counter or performing frequent switching between RO types in a capacity constrained network will reduce PRACH capacity.
Observation 10	A UE may apply PRACH repetitions and RO type switching within one RACH procedure.
Observation 11	Using the preambleReceivedTargetPower corresponding to the symbol type of Msg3 will result in a bias corresponding to the difference between the two preambleReceivedTargetPowers in case Msg1 and Msg3 are transmitted in different symbol types.
Observation 12	There is an ambiguity in the Msg3 mode of operation for an SBFD-aware UE performing RA in a legacy RO.
Observation 13	During random access with a legacy RO, an SBFD-aware UE scheduled with PUCCH in flexible symbols that are configured with an SBFD UL subband will have an ambiguous interpretation of the lowest PRB indices to use.

Based on the discussion in the previous sections we propose the following:
Proposal 1	No SBFD-specific instances of PCMAX or preambleTransMax are introduced.
Proposal 2	For Option 1, use a common ssb-SharedRO-MaskIndex configurations for additional ROs and legacy ROs (Alt. 1).
Proposal 3	Indexing of additional ROs is performed separately from legacy ROs following legacy indexing rules.
Proposal 4	Legacy collision rules and DL/UL guard periods apply to cross-symbol-type ROs.
Proposal 5	Power ramping is reset when switching RO type (Alt. 2).
Proposal 6	Different RO types use separate power ramping increments.
Proposal 7	Support CFRA/CBRA triggered by PDCCH order to indicate which RO type to use (i.e., legacy RO or additional RO).
Proposal 8	A UE use separate repetition counters for each RO type.
Proposal 9	For the additional RACH configuration (Option 2), a separate msg3DeltaPreamble is configured and any difference in Msg3 transmit power arising from different Msg3 symbol types is managed by the closed loop power control in RAR, i.e., δmsg2.
Proposal 10	An SBFD-aware UE transmitting Msg1 in legacy RO is not expected to operate in SBFD when transmitting Msg3.
Proposal 11	During random access, an SBFD-aware UE scheduled with PUCCH in flexible symbols that are configured with an SBFD UL subband operates according to legacy.
Proposal 12	Support separate p0-nominal for Msg4 HARQ ACK in SBFD symbols.
Proposal 13	Update RRC parameter list to also include the updated interpretation of msg1-FrequencyStart, i.e., offset of lowest PRACH transmission occasion in frequency domain with respective to the lowest PRB of the UL usable PRBs.
Proposal 14	Include preambleReceivedTargetPowerSBFD in RACH-ConfigCommon.
Proposal 15	Include sbfd-RACHTypeIndication into RACH-ConfigDedicated and BeamFailure- RecoveryConfig.
 

3GPP TSG RAN WG1 #120	bis                             R1- 2502439
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.3.2
Source: 	Xiaomi
Title:	Discussion on SBFD random access operation
Document for:	Decision

Conclusion 
In this contribution, we provide our views on SBFD operation to support random access in SBFD symbols. We have the following proposals:
For RACH configuration Option 1 with Alt 1-1, for determination of lowest RO of additional-ROs in SBFD symbols, the parameter msg1-FrequencyStart in rach-ConfigCommon is reinterpreted as the frequency offset of lowest RO in frequency domain with respective to the lowest PRB of UL usable PRBs ONLY if there is no legacy ROs configured in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon.
For RACH configuration Option 1, for support of separate power control parameters for PRACH transmission in additional-ROs and legacy-ROs, do not support separate preamble maximum output power  and preambleTransMax for additional-ROs.
It can be up to RAN2 to decide whether to support separate preambleTransMax for additional-ROs from RACH procedure perspective.
For RACH configuration Option 1, adopt Alt-1.
Alt-1: Shared ssb-SharedRO-MaskIndex configuration for Additional-ROs and Legacy-ROs.
For power ramping when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure for RACH configuration Option 1 and Option 2, Alt-2 is supported.
-	Alt-2: Reset the power ramping counter.
For determining the frequency domain resource allocation for Msg3 PUSCH transmission in SBFD symbols, Alt 2 is supported.
Alt-2: no enhancement
Support separate configurations of preambleReceivedTargetPower for additional-ROs and legacy-ROs in both legacy RACH configuration and additional RACH configuration for RACH configuration Option 2.
For determination of the Msg3 PUSCH transmission power and when separate configurations of preambleReceivedTargetPower for additional-ROs and legacy-ROs are configured for RACH configuration Option 2
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.
Do not support separate msg3-DeltaPreamble/deltaPreamble for additional-ROs for RACH configuration Option 1 and Option 2.
For SBFD-aware UEs, support separate configuration of msg3-Alpha for SBFD symbols.
For determination of the Msg3 PUSCH transmission power and when separate msg3-Alpha for SBFD symbols is configured
msg3-Alpha configured for non-SBFD symbols is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
msg3-Alpha configured for SBFD symbols is used if Msg3 PUSCH is transmitted in SBFD symbols.
For SBFD-aware UEs, support separate configuration of p0-nominal for SBFD symbols.
For determination of the transmission power of PUCCH with HARQ-ACK for Msg4 and when separate p0-nominal for SBFD symbols is configured
p0-nominal configured for non-SBFD symbols is used if PUCCH with HARQ-ACK for Msg4 is transmitted in non-SBFD symbols;
p0-nominal configured for SBFD symbols is used if PUCCH with HARQ-ACK for Msg4 is transmitted in SBFD symbols.

3GPP TSG RAN WG1 Meeting #120bis                                                                 R1-2502494
Wuhan, China, 7th – 11th April, 2025
Agenda item:         9.3.2
Title:	Discussion on SBFD random access operation 
Release:	Rel-19		
Source:	Korea Testing Laboratory
Document for:	Discussion
1. 

Conclusion
In this contribution, we provided our viewpoints.
Observation 1: When a UE switches from SBFD-based additional-ROs to legacy-ROs, continuing power ramping may lead to excessive transmit power and increased interference. Given that SBFD already enables low-latency access, resetting the ramping counter upon RO-type switching can provide a better trade-off between access reliability and system-wide stability.

Proposal 1:  The power ramping counter shall be reset when a UE switches between RO types—i.e., from additional-ROs (SBFD symbols) to legacy-ROs (non-SBFD symbols), or vice versa—within the same RACH procedure, the power ramping counter shall be reset.
Observation 2: Symbol-type-based power control for Msg3 enables better alignment with uplink conditions in SBFD operation, but additional CLI mitigation requires separate msg3-DeltaPreamble/deltaPreamble configuration for SBFD and non-SBFD symbols.
Proposal 2: To further enhance CLI mitigation, it is necessary to support separate configuration of msg3-DeltaPreamble/deltaPreamble for SBFD and non-SBFD symbols, enabling symbol-type-specific baseline power offset control in addition to TPC-based fine-tuning.
Observation 3: For RACH Option 2, aligning Msg3 preambleReceivedTargetPower with the Msg3 symbol type ensures consistent power control, effective CLI mitigation, and alignment with Option 1
Proposal 3 : For RACH Configuration Option 2, it is proposed to apply the preambleReceivedTargetPower in  for Msg3 PUSCH, as already defined for Option 1.
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.

Observation 4: For SBFD-aware UEs, Alt-2 with separate PRACH mask configurations improves RO type selection. To avoid ambiguity in non-DCI CFRA, RRC-based RO type indication is preferred over table-based methods, offering more flexibility and simpler implementation.

Observation 5: In CFRA scenarios without DCI signaling, ambiguity exists in determining the RO type (legacy or additional), and explicit indication via RRC is required to enable robust and interference-aware RO selection for SBFD-aware UEs.

Proposal 4: Adopt Alt-2 (i.e., separate PRACH mask index configuration for legacy-ROs and additional-ROs) as the baseline approach. Furthermore, it is proposed to complement Alt-2 with explicit RO type indication via RRC signaling.
4. 

3GPP TSG RAN WG1 #120bis				 	   R1-2502509
Wuhan, China, April 7th – 11th, 2025

Source: 	ETRI
Title: 	SBFD random access operation
Agenda Item:	9.3.2
Document for:	Discussion

Conclusion
We address our view about supporting random access for SBFD operations.
Proposal 1: Duplex type switching resets power ramp-up for Msg1 transmissions (Alt-2).
Proposal 2: Support to configuration between 1) repetition factor is increased in the same duplex type or 2) fallback to legacy set of ROs before repetition factor is increased.
Proposal 3: For Option1, separate mask index should be applied (Alt-2).
Proposal 4: For Option 2, any open loop power control parameter set can be used for corresponding duplex type, i.e., target power for legacy RO is used if Msg3 is on non-SBFD symbols; and target power for additoinal RO is used if Msg3 in on SBFD symbols.
Proposal 5: For both options, increasing ramping counter during a duplex type change (Alt-1) is preferred.
Proposal 6: Before dedicated PUCCH resources are configured, support HARQ-ACK repetition as Configuration 1.
Proposal 7: Support additional power offset for Msg4 HARQ-ACK to compensate duplex type change between Msg1 and Msg4 PUCCH.
Proposal 8: A single power offset of Msg3 and of Msg4 UCI can be applied.

3GPP TSG RAN WG1#120bis                           R1- 2502541
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.3.2
Source:	Transsion Holdings
Title:	Discussion on SBFD random access operation
Document for:	Discussion and decision

Conclusion
In this contribution, we focus on the SBFD random access operation, including including random access in Connected mode. Based on the discussion in section 2, we provide the following proposals:
Proposal 1: When a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure for RACH configuration Option 1 and Option 2, reset the power ramping.
Proposal 2: For RACH configuration Option 1, support Alt-1: Shared ssb-SharedRO-MaskIndex configuration for Additional-ROs and Legacy-ROs. 
Proposal 3: For PRACH resource selection for SBFD aware UEs, the gNB can enable the SBFD-aware UE to use additional RO resources by RRC signaling.

3GPP TSG RAN WG1 #120bis                                                 R1-2502557
Wuhan, China, April 7th – 11th, 2025


Source: Google
Title:	On SBFD random access operation
Document for: Discussion and Decision

Conclusion
In this contribution, we have presented several proposals to share our views on the random access in SBFD operation for UEs in RRC_CONNECTED mode and UEs in RRC_IDLE/INACTIVE mode:

Extend the solution of Option 1 to Option 2 for the determination of the Msg3 PUSCH transmission power when separate preambleReceivedTargetPower for additional-ROs is configured. 

Support the same power control offset msg3-DeltaPreamble for Msg3 PUSCH, for both SBFD symbols and non-SBFD symbols and for both Option 1 and Option 2. 

For power ramping, support Alt-1 for both the switching from additional-ROs to legacy-ROs and the switching from legacy-ROs to additional-ROs and for both Option 1 and Option 2:
Alt-1: Increase the power ramping counter.


Intorudce a power offset POWER-OFFSET-SBFD to compensate for the power ramping difference for RACH configuration Option 2:
Alt-1:  POWER-OFFSET-SBFD is configured as part of additional RACH configuration 
Alt-2: POWER-OFFSET-SBFD is determined by the UE as the difference between the preamble power ramping for additional RO and legacy RO

For RACH configuration Option 1, support Separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs.


If a parameter is not provided in the additional RACH configuration, UE uses the corresponding parameter in the legacy RACH configuration with restrictions on the set of parameters to inherit from rach-ConfigCommon

3GPP TSG RAN WG1 #120bis	R1-2502568

Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.3.2
Source: 	Lenovo
Title: 	SBFD random access operation
Document for:	Discussion and Decision

Conclusion
In summary, we have following observations and proposals for SBFD random access operation:
Proposal 1: RACH configuration Option 2 could be enabled or disabled by the existence of the additional RACH configuration.
Proposal 2: If one of two options between Option 1 with Alt 1-1 and RACH configuration Option 2 is enabled from gNB side, a UE supporting the other option should fallback to legacy UE’s behaviour.
Proposal 3: For RACH configuration Option 1 with Alt 1-1, for determination of lowest RO of additional-ROs in SBFD symbols, the parameter msg1-FrequencyStart in rach-ConfigCommon is reinterpreted as the frequency offset of lowest RO in frequency domain with respective to the lowest PRB of UL usable PRBs ONLY if there is no legacy-RO configured in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon.
Proposal 4: For option 2 (i.e., Use two separate RACH configurations, including one legacy RACH configuration and one additional RACH configuration), all the parameters currently in rach-ConfigCommon should be kept. 
Proposal 5: For SBFD-aware UEs and both RACH configuration Option 1 with Alt 1-1 and RACH configuration Option 2, for initial PRACH transmission re-attempt in one random access procedure, support the following option 3 for PRACH transmission re-attempt in one random access procedure:
Option 3: Independently select legacy-ROs or additional-ROs for each PRACH transmission re-attempt in one random access procedure
Proposal 6: For power ramping when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure for RACH configuration Option 1 and Option 2, support following alternatives:
Alt-1: Increase the power ramping counter for RACH configuration option 1.
Alt-2: Reset the power ramping for RACH configuration option 2.Observation 1: Some side-information at network, like location of hotspot areas can be utilized to obtain more efficient RA configurations in SBFD UL subband and limit impact of inter-UE CLI. 
Proposal 7: RAN1 to discuss solutions to limit impact of inter-UE CLI that may occur due to RA operations in SBFD UL subband. 

3GPP TSG RAN WG1 #120bis	                             R1- 2502577
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.3.2
Source:         Fainity 
Title:	Discussion on SBFD random access remaining aspects
Document for:	Decision

Conclusion 
In this contribution, we provide our views on SBFD random access remaining aspects and we have the following proposals:
Proposal 1: A unified alternative is applied for different RACH configuration options and switching cases.
Proposal 2: Support reset the power ramping after switching RO types as unified solution.
Proposal 3: gNB can configure power offset in both option 1 and option 2.
Proposal 4: Support separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs.

3GPP TSG RAN WG1 #120bis			R1-2502603
Wuhan, China, April 7th – 11th, 2025

Agenda Item:	9.3.2
Source:	Apple
Title:	Views on SBFD random access operation
Document for:	Discussion/Decision

Conclusion
In this contribution, we provided our views on random access operation in the SBFD sub-band. Our proposals are as follows:
Proposal 1: For RACH configuration Option 1, support separate preambleTransMax for PRACH  transmission in SBFD symbols.
Proposal 2: When SBFD-aware UE switchs from additonal-RO to legacy-RO, the power offset is applied to determine the PREAMBLE_RECEIVED_TARGET_POWER. The power offset include the preambleReceivedTargetPower difference and power ramping step difference between additional-RO and legacy-RO.
POWER_OFFSET_SBFD= SBFD_preambleReceivedTargetPower–preambleReceivedTargetPower +(N– 1) × (SBFD_PREAMBLE_POWER_RAMPING_STEP – PREAMBLE_POWER_RAMPING_STEP)
Where N is the power ramping counter when switching to legacy-RO
For RACH configuration Option1, SBFD_PREAMBLE_POWER_RAMPING_STEP equals to PREAMBLE_POWER_RAMPING_STEP
Proposal 3:  For determination of the Msg3 PUSCH transmission power for RACH configuration Option 2 
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.
Proposal 4: For RACH configuration Option1, ssb-SharedRO-MaskIndex configuration is shared for Additional-ROs and Legacy-ROs.

3GPP TSG RAN WG1 #120bis			R1-2502657
Wuhan, China, April 7th – 11th, 2025

Source:	Sharp
Title:	SBFD random access aspects
Agenda Item:	9.3.2
Document for:	Discussion and Decision
Random access procedures
Power ramping counter when fallback happens
The following agreement has been made for power ramping counter at RAN1#120 meeting [1].

Channel condition is different in SBFD symbols and non-SBFD symbols. That was the reason why we have agreed different power control parameters for each RO type. Therefore, reusing the same power ramping counter when fallback happens is not preferred. For example, if fallback to legacy RO happens when X PRACH attempts failed in SBFD symbols, the UE needs to ramp up the PRACH power by X in non-SBFD symbols even though it is the very first attempt in non-SBFD symbols.
Therefore, we prefer Alt-2 of resetting the power ramping counter. On the other hand, we are also OK with Alt-1 if the power offset to compensate the power ramping difference was also agreed, which is equivalent to Alt-2. Thus, our proposal is like follows.
Proposal 1: Support either Alt-2 of resetting the power ramping counter or Alt-1 with power offset to compensate the power ramping difference.
There is another discussion point regarding power ramping counter. The following conclusion in [1] is related to this.

As in the conclusion, there is no restriction on the combination of RO type of the latest PRACH transmission and symbol type of the following Msg3 PUSCH transmission. This conclusion suggests a scenario where msg3 transmission in non-SBFD symbols is scheduled before PRACH fallback to non-SBFD symbols happens as described in Figure 1. In this case, as in the same logic as above, the power ramping counter maintained for SBFD symbols should not be applied to the msg3 transmission. Therefore, we propose the following.
Proposal 2: Before PRACH fallback to non-SBFD symbols happens, the power ramping counter is assumed zero for msg3 scheduled in non-SBFD symbols.


Figure 1: An example flow diagram showing multiple PRACH and mgs3 attempts in SBFD and non-SBFD symbols
Msg3 PUSCH scheduling
Potential enhancements have been discussed at the last meeting. The proposed enhancements discussed was to make the RB numbering starting from the first RB of the UL usable PRBs. Figure 2 shows an example in which the proposed enhancement is effective. In Figure 2, the active BWP is wideband from f1 to f5, the UL subband is at the middle from f3 to f4, and initial UL BWP is at the lower edge from f0 to f2.

Figure 2: The active BWP is wideband from f1 to f5, the UL subband is at the middle from f3 to f4, and initial UL BWP is at the lower edge from f0 to f2
This case falls into the condition that initial UL BWP does not include all the RBs in the active UL BWP. Therefore, the schedulable RB range for msg3 as in legacy is only within f1 to f1+f2-f0 according to TS38,.213, copied and highlighted below.
TS 38.213V15.15.0

The proponent of the enhancement discusses that in such a case the UE cannot be scheduled msg3 in the UL subband due to the limitation of the legacy specification. That is why they propose to update the start of RB numbering from the first RB of the active UL BWP to the first RB of the UL subband.
However, first of all, why such a configuration needs to be provided is unclear. In our understanding, there is no issues if the gNB configures the initial UL BWP to include the UL subband. Why we need such a configuration like in Figure 2 where the initial UL BWP is completely outside of the UL subband should be clarified first.
Furthermore, the enhancement will cause another issue, as described in Figure 3. In Figure 3, the active BWP is the initial UL BWP from f2 to f4, the UL subband is at the middle from f1 to f3, and the other UE-specific wideband UL BWP is from f0 to f5. In this case, since the initial UL BWP is active, the RB numbering starts from the starting RB of the initial UL BWP and the maximum number of RBs schedulable for msg3 is the size of the initial UL BWP. If the proposed enhancement is taken, the scheduled RB range is from f1 to f1+f4-f2, which is completely outside of the initial UL BWP which is active. 

Figure 3: The active BWP is the initial UL BWP from f2 to f4, the UL subband is at the middle from f1 to f3, and the other UE-specific wideband UL BWP is from f0 to f5
In summary, we think it’s better to keep the legacy FDRA procedure for SBFD. Furthermore, potential issues should be solved by gNB configuration.
Proposal 3: No enhancements for msg3 PUSCH FDRA.
Proposal 4: Conclude that the gNB can configure an initial UL BWP properly to include the UL subband in the initial UL BWP.
Remaining issues on RACH configuration Option 1
PRACH mask index
The following agreement has been made for PRACH mask index at RAN1#120 meeting [1].

In our understanding, PRACH mask indexing is given per mapping cycle of consecutive PRACH occasions with the same SSB index. Therefore, dependency on SSB-to-RO mapping is clear. Considering that SSB-to-RO mapping is performed separately for additional and legacy ROs, mask index should also be separate.
Proposal 5: Support Alt-2 for PRACH mask index (i.e., separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs).
Feature combination configurations
For Option 1, feature combination preambles should also be separately configured for Additional-ROs and Legacy-ROs considering that Additional-ROs will not support RedCap devices. For example, in a serving cell, if the BS wants to operate with RedCap and SBFD, it should configure feature combination preambles only for Legacy-ROs. Reserving feature combination preambles for RedCap UEs in Additional-ROs is not meaningful since in our understanding, SBFD is not supported for RedCap UEs in Rel-19.
Proposal 6: Feature combination preamble configurations are provided separately for Additional-ROs and Legacy-ROs for RACH configuration Option 1.
Conclusion
In this contribution, we have the following proposals:
Proposal 1: Support either Alt-2 of resetting the power ramping counter or Alt-1 with power offset to compensate the power ramping difference.
Proposal 2: Before PRACH fallback to non-SBFD symbols happens, the power ramping counter is assumed zero for msg3 scheduled in non-SBFD symbols.
Proposal 3: No enhancements for msg3 PUSCH FDRA.
Proposal 4: Conclude that the gNB can configure an initial UL BWP properly to include the UL subband in the initial UL BWP.
Proposal 5: Support Alt-2 for PRACH mask index (i.e., separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs).
Proposal 6: Feature combination preamble configurations are provided separately for Additional-ROs and Legacy-ROs for RACH configuration Option 1.
References
RAN1 chairman’s note RAN1#120, February 2025

TDoc file conclusion not found

3GPP TSG RAN WG1 #120bis			                 R1-2502669
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.3.2
Source: 	Kookmin University
Title: 	Discussion on SBFD random access operation
Document for:	Discussion and Decision

Conclusions
In this contribution, the remaining issues on the random access procedures for SBFD were discussed. The following proposals were made:

Proposal 1: For SBFD-aware UEs and RACH configuration Option 1, the frequency domain re-interpretation is not applied to the legacy ROs in SBFD symbols configured with ‘flexible’ by tdd-UL-DL-ConfigurationCommon. 

Proposal 2: For RACH configuration Option 1, support the following Alt-2:
Alt-2: Separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs.

Proposal 3: For RACH configuration Option 2, all parameters in rach-ConfigCommon can be configured in the additional RACH configuration. 

Proposal 4: RAN1 to conclude that the explicit indication for additional-RO or legacy-RO is not supported for CBRA triggered by PDCCH order.

Proposal 5: For CFRA triggered by PDCCH order, the explicit indication for additional-RO or legacy-RO is invalid if SUL is indicated.

Proposal 6: When a SBFD-aware UE switches from additional-ROs to legacy-ROs in PRACH transmission re-attempt in one RACH procedure, the followings are supported:
For RACH configuration Option 1, increase the power ramping counter.
For RACH configuration Option 2, reset the power ramping counter if different types of preamble format is configured for legacy ROs and additional RO, otherwise, increase the power ramping counter.

Proposal 7: For determining the frequency domain resource allocation for Msg3 PUSCH transmission in SBFD symbols, the following Alt-2 is supported:
-	Alt-2: no enhancement

Proposal 8: For determination of the Msg3 PUSCH transmission power and when separate preambleReceivedTargetPower for additional-ROs is configured for RACH configuration Option 2 
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.

Proposal 9: Support separate msg3-DeltaPreamble/deltaPreamble configuration for Msg3 PUSCH transmission in non-SBFD symbols and SBFD-symbols. 

Proposal 10: For determining ΔPrampup for Msg3 PUSCH power control, RAN1 to consider the following cases:
Case #1) SBFD-aware UE transmits preamble in legacy ROs only.
Case #2) SBFD-aware UE transmits preamble in additional ROs and legacy ROs.
when a SBFD-aware UE switches form additional-ROs to legacy-ROs
Case #3) SBFD-aware UE transmits preamble in additional ROs only.
Case #4) SBFD-aware UE transmits preamble in legacy ROs and additional ROs.
when a SBFD-aware UE switches form legacy-ROs to additional-ROs (if supported)

Proposal 11: For SBFD-aware UEs, support separate configuration of p0-nominal for SBFD and non-SBFD symbols.

Proposal 12. For msg2/msg4 PDSCH, the solutions made in AI 9.3.1 are reused.

3GPP TSG RAN WG1 #120bis			R1-2502764
Wuhan, China, April 7th – 11th, 2025

Source:	NTT DOCOMO, INC.
Title:	Discussion on SBFD random access operation
Agenda Item:	9.3.2
Document for: 	Discussion and Decision		

Conclusion
In this contribution, we discussed SBFD operation for random access. We have the following observations and proposals:
Proposal 1: For RACH configuration option 1 and option 2, at least for the case of switching from additional-RO to legacy-RO, support Alt 1.
Alt-1: Increase the power ramping counter.
A power offset to compensate the power ramping difference for RACH configuration is supported for Option 2.

Proposal 2: If multiple PRACH repetitions are transmitted in the first RACH attempt, the following two alternatives should be further discussed:
Alt 1: Not support RO type switching during RACH re-attempts.
Alt 2: For multiple PRACH repetitions on additional-ROs in first RACH attempt, after a certain number of RACH failure attempts, UE can switch to PRACH repetitions on legacy-ROs. 
FFS PRACH repetition number after RO type switching.

Proposal 3: For RACH configuration Option 1, support separate ssb-SharedRO-MaskIndex configurations for additional-ROs and legacy-ROs.

Proposal 4: When separate configurations of preambleReceivedTargetPower for additional-RO and legacy-RO are configured, unified solution is applied to determine which preambleReceivedTargetPower to be used, for RACH configuration option 1 and option 2.
preambleReceivedTargetPower configured for legacy-RO is used if Msg3 PUSCH is transmitted in non-SBFD symbols;
preambleReceivedTargetPower configured for additional-RO is used if Msg3 PUSCH is transmitted in SBFD symbols.

TDoc file reading error

3GPP TSG RAN WG1 #120bis			R1- 2502837
Wuhan, China, April 7th – 11th, 2025
Agenda item:	9.3.2
Source: 	Qualcomm Incorporated
Title: 	SBFD Random Access Operation
Document for:	Discussion/Decision

Conclusion
In this contribution, we provide our views on SBFD random access operation with following observations and proposals:
Proposal 1:  For PRACH configuration option 1, when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure, support Alt-1 where UE increase the power ramping counter.
UE selects the preambleReceivedTargetPower based on the corresponding RO-type.

Proposal 2:  For PRACH configuration option 1, when a feature combination is configured using preamble partitioning of the RACH-ConfigCommon, support Alt-1 using shared Shared ssb-SharedRO-MaskIndex configuration for Additional-ROs and Legacy-ROs
Proposal 3:  RAN1 to discuss transition timeline of SBFD-aware UE switching from SBFD to non-SBFD mode for preamble transmission in a valid RO starting in SBFD symbols and ending in non-SBFD symbols. 
Proposal 4:  For PRACH configuration option 2, when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure, support Alt-1 where UE increment the power ramping counter.
UE selects the PRACH power control parameters {preambleReceivedTargetPower,powerRampingStep} based on the RO-type of the PRACH transmission.
When the UE switches/fallback to the other RO-type, a power offset given by the difference between the two quantities of preamble power step sizes is added.


Proposal 5: The 1-bit field in the DCI of PDCCH order to explicitly indicated to use additional-RO or legacy-RO is applicable for CBRA triggered by PDCCH order. 
The existence of the 1-bit bitfield in the PDCCH order is configured by higher-layer parameter.
The UE follows the legacy behavior and select the legacy-ROs in case this bit is not present in the DCI.

Proposal 6: The UL/DL usable PRBs for SBFD-aware UL/DL transmissions/reception in the initial (or active) UL/DL BWPs are determined as intersection between cell-specific UL/DL subband and the initial (or active) UL/DU BWP in SBFD symbols.
SBFD-aware can be configured with separate initial UL/DL BPWs with non-aligned center frequency. 

Proposal 7: no enhancement for determining the frequency domain resource allocation for Msg3 PUSCH transmission scheduled by RAR UL grant in SBFD symbols.
Proposal 8: The number of repetitions, K, is determined similar to legacy based on whether the higher-layer parameter numberOfMsg3-RepetitionsList is configured and is determined based on the 2 MSB of MCS bitfield
Proposal 9: For determination of the Msg3 PUSCH transmission power when UE is provided with separate PRACH configurations for SBFD RA, i.e PRACH configuration option 2, the preambleReceivedTargetPower of the latest PRACH transmission is used for msg3 PUSCH power control. 
A separate msg3-DeltaPreamble for msg3 PUSCH transmission in SBFD symbols

Proposal 10:  For both PRACH configurations, when a SBFD-aware UE switches from additional-ROs to legacy-ROs and from legacy-ROs to additional-ROs (if supported) in PRACH transmission re-attempt in one RACH procedure,  corresponds to the combined power ramp-up across the two RO types. 

Proposal 11:  Support separate power control parameters for common PUCCH transmission in SBFD symbols and non-SBFD symbols by having separate configuration of p0-nominal. 

3GPP TSG RAN WG1 #120bis			R1-2502926
Wuhan, China, April 7th – 11th, 2025

Source:	WILUS Inc.
Title:	Discussion on SBFD random access operation
Agenda item:	9.3.2
Document for:	Discussion/Decision

Conclusion
In this contribution, we discussed SBFD random access operation of UEs and summarize our views as the following:
Proposal 1: When applying the reinterpretation of msg1-FrequencyStart for RACH configuration Option 1 with Alt 1-1, it seems unnecessary to further optimize by adding additional condition in the previous agreement which is reinterpreted as the frequency offset of lowest RO in frequency domain with respective to the lowest PRB of UL usable PRBs.
Proposal 2: Regardless of which RACH configuration option is used (i.e., RACH configuration Option 1 with Alt 1-1 or RACH configuration Option 2) is used, the starting symbol for PRACH slot should be also reinterpreted as the starting symbol of the semi-statically configured UL subband in the time domain.
Proposal 3: For RACH configuration Option 2, it may be advisable to include parameters such as msg1-FrequencyStart, msg1-FDM, ssb-perRACH-OccasionAndCB-PreamblesPerSSB, which require reinterpretation in Option 1, and prach-ConfigurationIndex for configuring RO resources in the time domain in the additional RACH configuration.
Proposal 4: For RACH configuration Option 1, we propose to support the legacy SSB to RO mapping rule for validated ROs within UL subband for Rel-19 SBFD aware UEs. This should consider BW size differences between RO’s BW size of UL subband and legacy RO’s BW size for non-SBFD aware UEs.
Proposal 5: For RACH configuration Option 1, we propose to have separate SSB index to RO mapping for validated additional ROs in SBFD symbols for SBFD aware UEs, regardless of being configured as downlink or flexible by tdd-UL-DL-ConfigurationCommon.
Proposal 6: Regardless of the RACH configuration option applied, in addition to the agreed conditions at RAN1#118 and RAN1#118-bis, which relate to the Ngap required for the validation of additional ROs after the last DL non-SBFD symbol and/or after the latest SSB symbol, we propose to further discuss the additional condition for the validation of additional ROs.
Additional condition: A valid RO starts at least Ngap symbols after a last SBFD symbol with DL reception for a given UE.
Proposal 7: Regardless of which RACH configuration option (i.e., RACH configuration Option 1 with Alt 1-1 or RACH configuration Option 2) is used, we support Option 2 (i.e., Select one type between legacy-ROs and additional-ROs based on certain specified/configured conditions/prioritizations) for initial PRACH transmission attempt in one random access procedure for SBFD-aware UEs.
Proposal 8: Regardless of which RACH configuration option is used, we support Option 2 (i.e., First use ROs of the same type as the earlier PRACH transmission for a certain number of times, and if certain conditions are met, then use ROs of the other type for the rest of the random access procedure) for PRACH transmission re-attempt in one random access procedure.
Proposal 9: We support to have separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs (i.e., Alt-2)
Proposal 10: RAN1 needs to further discuss the PRACH power ramping and whether/how to increase power ramping counter during PRACH re-attempts.
It may be desirable not to perform power ramping and to leave the power ramping counter unchanged or to reset the power ramping as initial ramping counter when transmitting PRACH in a valid RO with a different symbol type for PRACH re-attempt transmission.
At least for RACH configuration Option 1, it seems beneficial to reset the power ramping when a SBFD-aware UE switches to different types of ROs in PRACH transmission re-attempt in one RACH procedure

3GPP TSG RAN WG1 #120bis																						R1-2503016
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.3.2
Source: 	Moderator (CMCC)	
Title: 	Summary#1 on SBFD random access operation
Document for:	Discussion/decision

Conclusion
There is no consensus in RAN1 to support Type-2 random access procedure (2-step RACH) in SBFD symbols for SBFD-aware UEs.

Agreement
For RACH configuration Option 1, down-select from the following two alternatives:
Alt-1: Shared ssb-SharedRO-MaskIndex configuration for Additional-ROs and Legacy-ROs. 
Alt-2: Separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs. 

3GPP TSG RAN WG1 #120bis																						R1-2503017
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.3.2
Source: 	Moderator (CMCC)	
Title: 	Summary#2 on SBFD random access operation
Document for:	Discussion/decision

Conclusion
There is no consensus in RAN1 to support Type-2 random access procedure (2-step RACH) in SBFD symbols for SBFD-aware UEs.

Agreement
For RACH configuration Option 1, down-select from the following two alternatives:
Alt-1: Shared ssb-SharedRO-MaskIndex configuration for Additional-ROs and Legacy-ROs. 
Alt-2: Separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs. 

3GPP TSG RAN WG1 #120bis																						R1-2503018
Wuhan, China, April 7th – 11th, 2025

Agenda item:	9.3.2
Source: 	Moderator (CMCC)	
Title: 	Summary#3 on SBFD random access operation
Document for:	Discussion/decision

Conclusion
There is no consensus in RAN1 to support Type-2 random access procedure (2-step RACH) in SBFD symbols for SBFD-aware UEs.

Agreement
For RACH configuration Option 1, down-select from the following two alternatives:
Alt-1: Shared ssb-SharedRO-MaskIndex configuration for Additional-ROs and Legacy-ROs. 
Alt-2: Separate ssb-SharedRO-MaskIndex configurations for Additional-ROs and Legacy-ROs.