3GPP TSG-RAN WG1 Meeting #121	R1-2503261
St Julian’s, Malta, May 19 – 23, 2025

Agenda Item:	9.3.1
Source:	Huawei, HiSilicon
Title:	On subband full duplex design
Document for:	Discussion and Decision

Conclusions
In this contribution, we provide our views on evaluation on NR duplex evolution with following proposals:
Observation 1: In half-duplex CA case, a UE will first handle the potential intra-carrier link direction collisions for the configured severing cells. After resolving this, the UE continues to handle potential inter-carrier link direction collision, including determination of reference cell(s) and collision handling among configured serving cells.
Proposal 1: UE-specific configuration on frequency locations of SBFD subbands is not supported in Rel-19.
Proposal 2: The guard period between SBFD symbols and non-SBFD symbols is implicitly provided by the gNB.
Proposal 3: If a UE is scheduled with a PDSCH across two DL subbands in SBFD symbols, the UE shall assume the PRG size is equal to 2 PRBs.
Proposal 4: The following existing restriction is relaxed for SBFD-aware UEs in SBFD symbols.
A UE is not expected to handle the case where PDSCH DM-RS REs are overlapping, even partially, with any RE(s) not available for PDSCH.
Proposal 5: For CSI processing timeline in SBFD symbols to process the CSI-RS across two DL subbands, if the associated CSI report is for L1 beam reporting, clarify whether both the beam reporting time and beam switching time KBl need to be scaled by the factor of 2 if UE indicates the support of “Scale the CSI processing timeline Z/Z’ by factor of 2 and keep the same CPU counting as legacy.
Proposal 6: For a CSI-RS resource which overlaps with SBFD subband boundaries, only CSI-RS resources within DL subband(s) are valid for an SBFD-aware UE.
Proposal 7: Support separate PCMAX,c configurations for SBFD symbols and non-SBFD symbols.
Proposal 8: Support separate PHR reporting for SBFD symbols and non-SBFD symbols based on the scheme defined for mTRP.
Proposal 9: For PUSCH repetition type-A across SBFD symbols and non-SBFD symbols in different slots where each repetition has either all SBFD or all non-SBFD symbols (i.e., Configuration 2), and for multi-PUSCH scheduled by a single DCI across SBFD symbols and non-SBFD symbols, where each PUSCH within a slot has either all SBFD or all non-SBFD symbols (i.e., Configuration 2), if the frequency resource allocation of any PUSCH transmission in SBFD symbols is outside the UL usable PRBs, UE falls back to Configuration 1 and transmit PUSCH only in non-SBFD symbols.
Proposal 10: For SPS HARQ-ACK transmission with PUCCH repetition when UE is configured with Configuration 1 for the UL BWP and if the PUCCH carries SPS HARQ-ACK only
The valid symbol type for SPS HARQ-ACK transmission is determined by the first PUCCH transmission occasion of the PUCCH repetitions
The first PUCCH transmission occasion is postponed to the next slot if it is mapped to both SBFD and non-SBFD symbols.
The valid symbol type can be different for different SPS HARQ-ACK transmission with PUCCH repetitions
Proposal 11: For a CSI report associated with aperiodic CSI-RS, the valid symbol type for CSI derivation for aperiodic CSI-RS resources for the CSI report is explicitly configured. 
When the aperiodic CSI-RS resources are triggered in a slot consists both SBFD symbols and non-SBFD symbols, only CSI-RS transmission occasions within the valid symbol types are used for CSI derivation.
When the aperiodic CSI-RS resources are triggered in a slot consists only SBFD symbols or only non-SBFD symbols, the valid symbol type is ignored and all CSI-RS transmission occasions are used for CSI derivation.
Proposal 12: For non-SBFD symbols, current HD CA collision handling mechanism can be reused directly without modifications.
Proposal 13: In the procedure of HD CA collision handling, a SBFD symbol is regarded as a flexible symbol regardless of whether it is indicated as downlink by tdd-UL-DL-ConfigurationCommon.
Proposal 14: In the procedure of HD CA collision handling, for a SBFD symbol, the active cell configured with SBFD operation is determined as the reference cell if the UE is configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH or receive PDCCH, PDSCH or CSI-RS on the symbol in this cell.

3GPP TSG RAN WG1 #121	R1-2503327
St Julian’s, Malta, May 19th - 23th , 2025

Title: 	Discussion on transmission, reception and measurement procedures for SBFD operation
Source: 	ZTE Corporation, Sanechips
Agenda item:	9.3.1
Document for:	Discussion/Decision 

Conclusion
In this contribution, we provide our analysis for subband non-overlapping full duplex for possible solutions with the following proposals and observations.
SBFD configuration
Proposal 1: Explicit indication is NOT supported for the guard periods between SBFD and non-SBFD symbols. 
UE behavior and procedures in SBFD symbols and/or non-SBFD symbols 
Proposal 2: For PUSCH repetition Type B with Configuration 1, a nominal repetition is first segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols, and then the symbol type of the first actual repetition occasion in the actual repetitions is determined as the valid symbol of the PUSCH repetition Type B.
UE drops an actual repetition if the actual repetition is in the invalid symbol type. 
Proposal 3: For an SBFD aware UE, for PUSCH repetition Type B, a non-SBFD symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is considered as an invalid symbol for PUSCH repetition Type B transmission. 
Proposal 4: In SBFD symbols, the maximum number of partial PRGs reported by a UE can be 2 or 4.
If two DL subbands are configured and value 2 is reported by the UE, a PDSCH transmission is valid as long as it only contains up to 2 partial PRGs, no matter the partial PRG are caused by the boundary of BWP as legacy or it is caused by the boundary of DL subband.
Otherwise, a PDSCH transmission is valid no matter which and how many partial PRGs the PDSCH contains.
FFS whether the number of scheduled partial PRGs can exceed the capability value reported by the UE.

Observation 1: For PDSCH scheduled by a DCI format in CSS, FDRA Type 1 and PRG size of 2 PRBs are used. 
Observation 2: For PDSCH scheduled by a DCI format in CSS, if the number of PRBs for TBS determination is based on the assigned PRBs within DL usable PRBs only, legacy UEs will not be able to successfully receive the broadcast PDSCH.  
Proposal 5: For frequency domain resource allocation Type 1 for PDSCH in a single slot scheduled by DCI format in CSS, support the following: 
Only the assigned PRBs within DL usable PRBs are considered to be valid for PDSCH. Assigned PRBs that fall outside DL usable PRBs are considered to be invalid.  
Existing RB indexing and VRB-to-PRB mapping are reused.
Down-select one of the following options. 
Option 1: The number of PRBs for TBS determination is based on the assigned PRBs as legacy. The invalid PRBs are punctured.
Option 2: The number of PRBs for TBS determination is based on the assigned PRBs within DL usable PRBs only. VRB-to-PRB mapping is always disabled and a UE does not expect that the PDSCH is scheduled out of the DL usable PRBs
No impact on DMRS sequence generation.
DMRS sequence mapped to the RBs outside the DL usable PRBs are punctured.
When an assigned PRG overlaps with the subband boundary, only the PRBs within DL usable PRBs are considered to be valid for PDSCH reception. 
Proposal 6: For frequency resource allocation Type 1 for PDSCH or PUSCH in a single slot by DCI based scheduling (without repetition or TBoMS), 
When an assigned RB group overlaps with the subband boundary, only the PRBs within DL usable PRBs are considered to be valid for PDSCH reception and only the PRBs within UL usable PRBs are considered to be valid for PUSCH transmission.
SBFD aware UE does not expect to be assigned with an RB group for PDSCH which is fully outside DL usable PRBs or an RB group for PUSCH which is fully outside UL usable PRBs.
The number of PRBs for TBS determination is based on the assigned PRBs within DL usable PRBs only and assigned PRBs within UL usable PRBs only for PDSCH and PUSCH respectively.
Note: the RB group is the indication granularity K or P of RA type 1 for PDSCH or PUSCH in TS 38.214. 
Observation 3: The MSB(s) of the FDRA RA type 1 is used to indicate the frequency offset for 2nd hop, which will seriously affect the scheduling flexibility of PUSCH with Configuration 1 in SBFD symbols. 
Proposal 7: For PUSCH transmission in a single slot or multiple slots with Configuration 1, if SBFD symbol is valid symbol type for PUSCH (including at least DG PUSCH, type 2 CG PUSCH), the following method should be supported for RA type 1,
The number of bits of the FDRA field is determined based on the size of the active UL BWP. 
The MSB(s) of the FDRA field is employed for indicating the frequency offset for the 2nd hop. 
The LSBs of the FDRA field utilized for frequency domain resource indication are determined based on the size of UL usable PRBs. 
The remaining bits of the FDRA field are set to 0 if any.
Proposal 8: For PDCCH transmitted at least in CORESET 0, RAN1 further discuss the following two options. 
Option 1: CORESET 0 is allowed to be across subband boundary. FFS details. 
Option 2: A separate initial BWP is configured for SBFD aware UEs, and no enhancement to CORESET 0 is pursued, i.e., CORESET 0 shall be contained within the DL useable PRBs. 
Proposal 9: For type 1 HARQ-ACK codebook, support the following operation for SBFD.
For the type 1 HARQ-ACK codebook generated for at least one DG PDSCH, a candidate PDSCH across SBFD symbols and non-SBFD symbols within a slot is excluded.
For the type 1 HARQ-ACK codebook generated only for SPS PDSCHs, an SPS PDSCH occasion across SBFD symbols and non-SBFD symbols within a slot, or an SPS PDSCH occasion in the invalid symbol type if Configuration 1 is provided, is not provided with HARQ-ACK information. 
Proposal 10: The parameter maxCodeRate in PUCCH-FormatConfig should be configured separately for SBFD symbols and non-SBFD symbols.
Proposal 11: For collision handling in SBFD symbols for SBFD aware UEs, Option 3 is supported.
Step 1: Resolving the collision as in legacy, if any. 
Step 2: Resolving SBFD specific collision between transmissions/receptions and unusable resources, if any.
Observation 4: UL transmission in UL subband within a DL symbol cannot be cancelled by the DCI format 2_4. 

Interaction between SBFD operation and Rel-16~19 features  
Proposal 12: RAN1 needs to further discuss whether any optimization is needed for each of the Rel-16~Rel-19 features. 
Multi-Carrier SBFD Operation
Proposal 13: For SBFD operation in half-duplex CA scenario, the existing directional collision handling for half-duplex TDD CA is reused by treating SBFD symbols as flexible symbols.

3GPP TSG RAN WG1 #121	                                           R1-2503355
St Julian’s, Malta, May 19th – 23th, 2025

Source:	vivo
Title:	Remaining issues on Rel-19 SBFD operation
Agenda Item:	9.3.1
Document for:	Discussion and Decision

Conclusion
For separate SRS-ResourceSets configurations for SBFD symbols and non-SBFD symbols for a given usage, frequency hopping counter for an SRS resource is calculated as legacy.

Agreement
Separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols is applicable for usage set to 'beamManagement'.
The total number of SRS-ResourceSets applicable for usage set to 'beamManagement’ is the same as legacy.

An occasion mapped to both SBFD symbols and non-SBFD symbols
Agreement
For a physical channel/signal occasion mapped to SBFD and non-SBFD symbols within a slot,
For PUSCH repetition type A with available slot counting, A-SRS with available slot counting, TBoMS and PUCCH repetitions, UE postpones a transmission if the transmission occasion is mapped to SBFD and non-SBFD symbols within a slot.
For CG PUSCH with neither TBoMS nor PUSCH repetition type A with available slot counting, SPS PDSCH, P/SP SRS, P/SP CSI-RS, P/SP PUCCH, SP-CSI on PUSCH, PUSCH repetition type A without available slot counting, multi-PUSCH/PDSCH scheduled by a single DCI, and PDSCH repetitions, UE drops a transmission/reception if the transmission/reception occasion is mapped to SBFD and non-SBFD symbols within a slot.

Agreement:
For PUSCH repetition type B, adopt Option 1.
Option 1: A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols.

Collision handling

3GPP TSG RAN WG1 #121		 	R1-2503415
St Julian’s, Malta, May 19 – 23, 2025

Source:	NEC
Title:	Discussion on subband non-overlapping full duplex Tx/Rx and measurement operations
Agenda Item:	9.3.1
Document for: 	Discussion and Decision

Conclusion 
In this contribution, we discussed SBFD for NR duplex operation. Observations and Proposals are summarized as follows: 
Observation 1 Even if the timing alignment offset for UL transmission is set as 0 for the UL transmissions in the SBFD symbol, gNB may not get sufficient margin to switch from UL in SBFD to DL in the next symbol.
Observation 2 In Option-B, which symbol type is used by UE to perform CSI-RS measurements is not clear. UE may make CSI-RS measurement during regular DL symbol and determine the CSI corresponding to SBFD symbol by only considering the CSI-RS frequency resources for CSI report which overlap with DL subband frequency resources.
Observation 3 Option-A allows UE to report accurate representation of the SBFD symbols considering UE-to-UE CLI. Option-B can enable lower signaling overhead where CSI-RS may not be required to be transmitted during both DL and SBFD symbols.

Proposal 1:
Specify SBFD-specific timing alignment offset to mitigate inter-symbol interference.
A guard period may need to be defined before and/or after the UL transmission in an SBFD symbol to allow sufficient margin time for UL to/from DL transition.
Proposal 2:
For transient period Case B and C, the UE regards any guard/blanked SBFD symbol as invalid.
Proposal 3:
Support of separate frequency resource configurations for CORESET in SBFD symbols and non-SBFD symbols for UE-specific search space. 
Proposal 4:
Discuss the UE behavior for selecting the CORESET configuration for PDCCH monitoring in a slot consisting of SBFD and DL-only symbols. 
Proposal 5:
SBFD-aware UEs shall not expect the CORESET associated with common search space to have resources outside the DL subband in an SBFD symbol.
Proposal 6:
Confirm the working assumption with the following modification. For frequency resource allocation for CSI-RS across downlink subbands for SBFD-aware UEs, support one contiguous CSI-RS resource allocation with non-contiguous CSI-RS resource derived by excluding frequency resources outside DL usable PRBs.
No impact on CSI-RS sequence generation.
CSI-RS sequence mapping is applied to CSI-RS resources within DL usable PRBs only (effectively, this is same as the case when the CSI-RS sequence mapped to the RBs outside the DL usable PRBs are punctured).
RAN1 to further study the impact on CSI processing timeline in SBFD symbols to process the CSI-RS across the two DL subbands.
Proposal 7:
UE should only include the reporting quantities (e.g., CSI/PMI) associated with the DL subband resources when the corresponding CSI measurements are performed during the SBFD symbol.
Proposal 8:
Support Option-B (in addition to Option-A) for CSI report associated with periodic/semi-persistent CSI-RS.
Proposal 9:
In Option-B for CSI report associated with periodic/semi-persistent CSI-RS, UE may determine the CSI report corresponding to the SBFD symbols by performing CSI-RS measurement during non-SBFD DL symbol.
Proposal 10:
Available slot counting method for SRS repetition under configuration 2 should be enhanced.
Proposal 11: 
Additional PDCCH monitoring occasions to send DCI for paging on SBFD symbols can be considered.
Proposal 12: 
When determining RSRP threshold values, the current status of SBFD of neighbouring cells need to be considered in order to accurately select the appropriate values. 
Proposal 13: 
Set the maximum number of switching times from uplink-downlink or downlink-uplink to 2 times per SBFD slot.
Proposal 14: 
Allow UE to have dedicated SBFD configurations for half-duplex CA
Proposal 15: 
Power allocation for MC scenarios will be prioritized to SBFD cells.
Proposal 16: 
SBFD and DC can be configured simultaneously if SBFD is only limited to one cell within the DC pair. 

3GPP TSG RAN WG1 #121			R1-2503424
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	9.3.1
Source: 	LG Electronics
Title: 	Discussion on SBFD TX/RX/measurement procedures
Document for:	Discussion and decision

Summary
In this contribution, we discussed on the subband non-overlapping full duplex. Based on the discussion, we obtained following proposals.

1. Time/Frequency location indication of SBFD subbands
1.1) Semi-static indication of time location of SBFD subbands
Proposal 1: For the starting slot/symbol and/or the ending slot/symbol of SBFD symbols within TDD-UL-DL pattern period,
When the starting slot/symbol of SBFD symbols are not configured, the default position of the starting slot/symbol is the same as the first symbol within the TDD-UL-DL pattern period.
When the ending slot/symbol of SBFD symbols are not configured, the default position of the ending slot/ symbol is the same as the position of the last symbol among the DL and/or Flexible symbols indicated by TDD-UL-DL-ConfigCommon.
Proposal 2: Explicitly configure a guard period for Case C (i.e., the transition from DL in a non-SBFD symbol to an SBFD symbol) and the related behavior of an SBFD-aware UE.

1.2) Semi-static indication of frequency location of SBFD subbands
Proposal 3:  Support additional UE specific configuration on frequency location of SBFD subband.

2. SBFD Tx/Rx/Measurement procedure
2.1) Transmission and reception behaviors on SBFD subbands
Proposal 4: For PUSCH with repetition type A based on available slot counting and for PUCCH repetition, if a physical channel occasion mapped to SBFD and non-SBFD symbols within a slot, the UE postpones transmissions in the slot.
Proposal 5: For PUSCH repetition type B with Configuration 1, support UE drops an actual repetition if the actual repetition is in the invalid symbol type.

2.3) Physical channels/signals and procedure across SBFD and non-SBFD symbols
Proposal 6: To support joint channel estimation when PUSCH/PUCCH repetition is transmitted across SBFD symbols and non-SBFD symbols in different slots, the boundary between SBFD symbols and non-SBFD symbols is included in the semi-static event used for determining the actual TDW.

2.4) Configuration for SRS, PUCCH and PUSCH on SBFD and non-SBFD symbols
Proposal 7: In case of configuration 2, when no separate configuration of starting PRB and second hop PRB for SBFD symbol is provided, PUCCH transmissions for the pucch-ResourceId is not expected in SBFD symbols.

Proposal 8: For UCI multiplexing on PUSCH, separate configuration of betaOffsets is supported for SBFD and non-SBFD symbols.

2.5) Collision handling between DL reception in DL subband(s) and UL transmission in UL subband
Proposal 9: To avoid the collision between UL transmission and UL/DL switching time before and after reception of SSB symbols, specify a UE behavior considering on Rx-Tx switching time and Tx-Rx switching time between UL signal/channel and SSB symbols 

TDoc file unavailable

3GPP TSG RAN WG1 #121			R1-2503512
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	9.3.1
Source: 	Spreadtrum, UNISOC
Title: 		Discussion on SBFD TX/RX/measurement procedures
Document for:	Discussion and decision

Conclusion
In this contribution, we made the following observations and proposal.
Only cell-specific configuration on frequency location of SBFD subbands is supported within a TDD carrier.
Explicit indication of transition periods between SBFD and non-SBFD symbols is not supported.
If transient period is reserved in the whole channel bandwidth, invalid symbol for SBFD->UL(non-SBFD) switching needs to be indicated.
Two new RRC parameter can be introduced to indicate the invalid symbol for SBFD->UL(non-SBFD) switchin and DL(non-SBFD)->SBFD switching.
For PUSCH repetition type B, segmentation around boundary of SBFD symbols and non-SBFD symbols is supported with either Configuration 1/2.
For PUSCH repetition Type B with Configuration 1, UE drops an actual repetition if the actual repetition is in the invalid symbol type.
For frequency resource allocation Type 1 with RBG for PDSCH or PUSCH in a single slot by DCI format 0_2/0_3/1_2/1_3 based scheduling (without repetition or TBoMS), 
When an allocated RBG overlaps with the subband boundary, only the PRBs within DL usable PRBs are considered to be assigned for PDSCH reception and only the PRBs within UL usable PRBs are considered to be assigned for PUSCH transmission.
Allocated RBGs that fall outside DL usable PRBs are considered to be not assigned and should not be used for PDSCH resource mapping. 
The number of PRBs of a CSI-RS resource within each DL subband should be ≥ , where   is the number of DL usable PRBs in one DL subband.
For dynamic determination of the precoding bundling for a PDSCH, the condition for determining wideband or narrowband depends on whether the number of scheduled PRBs is larger than half of the size of intersection between active DL BWP and DL subband where the PDSCH is located.
Assigned PRBs in PDSCH scheduled by DCI format 1_0 in CSS are all inside DL usable PRBs by scheduling.
For PDSCH resource mapping, there can be two alternatives for the symbol type of NZP CSI-RS:
Alt 1: UE assume P/SP NZP CSI-RS receptions is configuration 2.
Alt 2: The valid symbol type of CSI-RS resource is same as the valid symbol type for CSI derivation of associated CSI report.
For PUSCH transmissions with Configuration 2, in case PUSCH frequency hopping is enabled, starting PRB of the first hop for PUSCH repetitions/transmissions in SBFD symbols is determined according to Equation 1-C2 as agreed for PUSCH repetitions/transmissions in SBFD symbols without frequency hopping.
For SBFD-aware UEs, for CSI report associated with periodic/semi-persistent CSI-RS, at least, across SBFD symbols and non-SBFD symbols in different slots (each CSI-RS resource within a slot has either all SBFD or all non-SBFD symbols), support Option A and B.
For Option A, it introduces occasions used for a CSI report, CSI-RS transmission occasions within SBFD symbols or non-SBFD symbols
For Option B, it defines a new type of sub-configuration, corresponding to CSI-RS transmission occasions subset within SBFD symbols or non-SBFD symbols
The valid CLI reference resource slot should comprises at least one higher layer configured SBFD or flexible symbol and not fall within a configured measurement gap.
For a CORESET and a search space configured that the MOs of the search space occur in both SBFD and non-SBFD symbols and the associated CORESET overlaps the boundary of DL usable PRBs in SBFD symbols
No enhancements for SBFD-aware UEs in Rel-19.
It is up to gNB to avoid the PDCCH candidate overlap with the boundary of DL usable PRBs in SBFD symbols
Separate configurations of availableSlotOffsetList for SRS Resource Sets in SBFD and non-SBFD symbols is supported.
Whether to support separate configurations of p-Max for SBFD and non-SBFD symbols is up to RAN4.
Whether to apply separate UE power class for SBFD and non-SBFD symbols needs further discussion. 
Only the PRBs within UL usable PRBs are used to calculate the  PUSCH transmit power.
For PUSCH repetition type B, whether   is a number of symbols for norminal repetition or actual repetition needs further discussion.
Support separate beam/spatial relations for SBFD and non-SBFD symbols for single-TRP scenario for both UL and DL.
Introduce a new MAC CE to indicate separate TCI state for SBFD symbol and non-SBFD symbol
No RRC impact
For the case of UL power control is not associated within TCI state, support a first and a second UL PC parameter settings for PUSCH/PUCCH/SRS configured in BWP-UplinkDedicated.
Support separate PHR reporting associated with UL transmissions in SBFD symbols and non-SBFD symbols.
Support separate FH offsets for actual PUSCH repetition in SBFD symbols and non-SBFD symbols respectively.
For determining starting RB for an actual repetition in SBFD symbol within the n-th nominal repetition  is given by:

Where 
For PUSCH transmissions with Configuration 2, 
RB offset is the frequency hopping offset for actual PUSCH repetition in SBFD symbols
For SBFD operation in half-duplex CA scenario, the existing directional collision handling for half-duplex TDD CA is reused by treating SBFD symbols as flexible symbols.
Confirm the following working assumption:
For SSB symbols configured with SBFD subbands, 
-	Option 1: The SSB symbols configured with SBFD subbands are SBFD symbols. Only DL receptions within DL usable PRBs are allowed for SBFD aware UEs.
-	Note: The SSB block is assumed to be within DL subband
For collision handling in SBFD symbols for SBFD aware UEs,
Step 1: Resolving SBFD specific collision between transmissions/receptions and unusable resources (e.g. invalid symbol type for Configuration 1, Tx/Rx occasion mapped to SBFD and non-SBFD symbols etc.) , if any.
Step 2: Resolving the collision as in legacy, if any.
Step 3: Resolving the DL reception vs. UL transmission collisions within SBFD symbols

3GPP TSG RAN WG1 #121	     R1-2503563
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	9.3.1
Source:	Samsung
Title:	SBFD operation and procedures
Document for:	Discussion
1. 

Conclusion 
This contribution discussed the SBFD operation design and following observations and proposals are given:
Observation 1. Support for radio link monitoring by the UE on SBFD and non-SBFD slots is critical Rel-19 functionality to prevent higher layer interruptions from premature RLF declaration by the UE 

Observation 2. RLF detection by the UE using only the SSBs as NLR-RLM RadioLinkMonitoringRS is not sufficient to support RLM for all SBFD antenna configuration options

Proposal 1. Confirm the cell-specific configuration on frequency location of SBFD subbands. 
UE-specific frequency domain location of SBFD subbands is not necessary 
Proposal 2. In case of CSI-RS across the two DL subbands, consider to double the counting of active resources and active ports for the CSI-RS.
Proposal 3. In case of a CSI-RS across the two DL subbands, the frequency domain resources of the CSI-RS consists of 2 parts in different DL subbands. 
At least for CSI acquisition, the number of PRBs for each of the 2 parts is ≥ , where  is the number of PRBs of DL subband which includes the associated part of the CSI-RS
Proposal 4. Adopt the following text proposal for TS38.214
Proposal 5. If the valid symbol type for CSI derivation for periodic/semi-persistent CSI-RS resources for the CSI report is configured, the valid downlink slot associated with CSI reference resource for the CSI report is defined as follows:
A slot comprises at least one higher layer configured downlink or flexible symbol, where the symbol is with the same symbol type as the configured valid symbol type; and
The slot does not fall within a configured measurement gap for that UE
Proposal 6. Adopt the following text proposal for TS38.214
Proposal 7. If the timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "Configured", and if the valid symbol type for CSI derivation for periodic/semi-persistent CSI-RS resources for the CSI report is configured,
The most recent occasion of the periodic/semi-persistent CSI-RS resource for channel measurement for CSI derivation is within the symbols with the same symbol type as the configured valid symbol type

Proposal 8. If the timeRestrictionForInterferenceMeasurements in CSI-ReportConfig is set to "Configured", and if the valid symbol type for CSI derivation for periodic/semi-persistent CSI-RS resources for the CSI report is configured,
The most recent occasion of periodic/semi-persistent CSI-IM and/or NZP CSI-RS for interference measurement for CSI derivation is within the symbols with the same symbol type as the configured valid symbol type
Proposal 9. Adopt the following text proposal for TS38.214

Proposal 10. Adopt the following text proposal for TS38.214

Proposal 11. For non-codebook based PUSCH transmission, in case of a periodic or semi-persistent associated CSI-RS for an SRS-ResourceSet
UE calculate the precoder used for the transmission of SRS based on measurement of CSI-RS in the same symbol type as the symbol type for the SRS-ResourceSet.
Proposal 12. For non-codebook based PUSCH transmission, an aperiodic associated CSI-RS for an SRS-ResourceSet is located at the first available slot which is no earlier than the slot with the scheduling DCI.
A slot is defined as an available slot if the symbols of the CSI-RS in the slot are of the same symbol type as the symbol type for the SRS-ResourceSet.
Proposal 13. In case of prb-BundlingType=staticBundling and bundleSize=wideband, UE may assume the PRG size is equal to 2 when the scheduled PRBs overlap with two DL subbands in SBFD symbol.
Proposal 14. In case of prb-BundlingType=dynamicBundling and bundleSizeSet1= n2-wideband or n4-wideband, if PRB bundling size indicator field indicates ‘1’, the DL subband size can be used for PRG size determination, instead of DL BWP size.
Proposal 15. RAN1 to discuss whether to count the determination of value PRBs within DL usable PRBs towards the maximum number of RateMatchPattern(s) per serving cell or BWP or introduce a separate UE capability.
Proposal 16. For type-1 HARQ-ACK codebook, if a PDSCH candidate overlaps with both SBFD symbols and non-SBFD symbols, the PDSCH candidate is excluded.
Proposal 17. Send a LS to RAN4 that separate maximum configured output power for SBFD/non-SBFD slots should be supported, e.g., using Options 1 or 2 as a starting point.
Option 1: one/same RRC signaled p-max value but use of a new/additional SBFD slot specific delta offset
Option 2: two separate RRC signaled p-max values, e.g., legacy p-max for non-SBFD, and new/additional for the SBFD slots.
Proposal 18. For the single TRP scenario, for separate UL power control of PUSCH transmissions in SBFD symbols and non-SBFD symbols, support separate PHR Type 1 reporting.
Proposal 19. Support the following orders for collision handling (Option 2) with the following update
Step 1: Resolving SBFD specific collision between PUCCH with repetitions/PUSCH transmissions and unusable resources, if any.
Step 2: Resolving the collision as in legacy, if any. 
Step 3: Resolving SBFD specific collision between transmissions/receptions and unusable resources, if any.
Proposal 20. For half-duplex CA case, SBFD symbol is considered as flexible symbol. 
Proposal 21. For intra-band CA case, the valid symbol type for CSI derivation can be configured in CSI-ReportConfig, where the CSI-ResourceConfig associated with the CSI-ReportConfig is in a serving cell which is the same or different from the serving cell for the TDD carrier for SBFD operation.
Proposal 22. For radio link monitoring by the UE with SBFD, support Option 2a:
SSB-based or CSI-RS-based resources configured as RadioLinkMonitoringRS across SBFD and non-SBFD symbols can be used for the same RLM/BFD/CBD measurement
Single radio link quality evaluation/indication using SSB or CSI-RS resources with offset value or new/additional BLER configuration for SBFD symbols

3GPP TSG RAN WG1 #121			R1-2503623 St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.3.1
Source:	InterDigital, Inc.
Title:	Discussion on SBFD TX/RX/measurement procedures
Document for:	Discussion and Decision

Conclusion
In this contribution, we discussed issues on SBFD Tx, Rx, measurement procedures, including SBFD operation with CA, implicit guard periods between different symbol types, SBFD operation in SSB symbols, and extending SBFD beyond Rel-19 for flexibility and scalability. From the discussions, we made following observations and proposals:
[2.1	SBFD operation with CA]
Observation 1. The agreement on supporting SBFD operation on one TDD carrier implies that the Rel-19 SBFD feature is limited to one carrier among multiple carriers if the UE is configured with CA.
Proposal 1. In consideration of such limited scope and timeframe in Rel-19, it is not justified to further optimize UE behaviors in combination with the half-duplex CA case, where the UE does not expect to be scheduled simultaneously with SBFD operation which violates the half-duplex CA constraint.
[2.2	On implicit quard periods between different symbol types]
Observation 2. The issues in UL/DL timing alignment (between UL/DL SBs) in SBFD slots could result in slot collision issues for one UE perspective and possible dropping of respective slots, especially for back-to-back scheduling cases between DL and UL. 
Observation 3. The slot collision issue due to non-zero TA from UL transmission in UL subband in SBFD configuration could increase the inter-slot and inter-subband interference including other UEs, specifically on the DL symbols scheduled in the previous slot.
Observation 4. The slot collision issue and the time misalignment due to non-zero TA for an UL transmission in UL subband in an SBFD configuration could affect the legacy UE that is configured to receive critical DL signals such as SSB, CORESET#0, or DMRS close to the end of a preceding DL slot.
Proposal 2. Support implicit guard periods to handle the slot collision and time misalignment issues due to non-zero TA for a scheduled UL Tx in an SBFD slot, right after the legacy ‘D’ slot back-to-back, e.g., including which channel direction the UE can prioritize and UE reporting on a minimum PUSCH starting symbol to aid gNB’s scheduling. 
[2.3	SBFD operation in SSB symbols]
Observation 5. In case the SBFD operation is not supported in SSB symbols, the SBFD objectives such as UL coverage enhancement and latency reduction are affected and degraded.
Observation 6. The UL transmission from SBFD-aware UEs in an adjacent cell in an SBFD symbol that coincides with SSB transmission in a serving cell degrades the SSB reception performance for the UEs in the serving cell.
Proposal 3. Support mechanisms for collision handling between coincidence of UL transmission in a serving-cell cell and SSB transmission in a neighbour cell, when information on the SSBs of the neighbour cell is configured.
[2.4	On extending SBFD beyond Rel-19 for flexibility and scalability]
Observation 7. Flexible adaptation (for e.g., dynamic fallback of SBFD slots) for SBFD can result in improved performance over semi-statically fixed DL/UL resource configuration.
Proposal 4. Further study on how to enhance SBFD performance beyond Rel-19 for improved flexibility and scalability, in consideration of dynamic and future-proof full duplex design approach, impacting to DL/UL performance trade-off depending on parameter adjustments.

3GPP TSG RAN WG1 Meeting #121                                                                     R1-2503629
St Julian’s, Malta, May 19 – May 23 2025

Agenda Item:	9.3.1 
Source:	TCL 
Title:	Discussion SBFD TX/RX/measurement procedures 
Document for:	Discussion and Decision 

Conclusion
In this contribution, we discussed separate, UE specific time/frequency configuration of SBFD subbands, guard period between SBFD and non-SBFD symbols, separate FH and separate p-Max for SRS, PUCCH, and PUSCH in SBFD symbols. We made the following observations and proposals.
Observation 1: UE-specific configurations for the time and frequency locations of SBFD subbands would unnecessarily increase signaling overhead. 
Observation 2: The transition time between SBFD and non-SBFD operations may only be necessary on the gNB side and can be handled through gNB implementation.

Proposal 1: UE-specific configurations for the time and frequency locations of SBFD subbands is not supported for Rel-19.
Proposal 2: The explicit configuration of a guard period between SBFD and non-SBFD symbols is not necessary to define and it can be determined based on gNB implementation.
Proposal 3: Consider separate startingPRB and secondHopPRB within a PUCCH-resoruceId for PUCCH FH in SBFD and non-SBFD symbols.  
Proposal 4: Support separate configurations of p-Max for SBFD and non-SBFD symbols.

3GPP TSG RAN WG1 #121   							              R1-2503706
Malta, MT, May 19th – 23rd, 2025

Source: 	Tejas Networks
Title: 	Discussion for SBFD TX/RX/ measurement procedures
Agenda Item:	9.3.1
Document for: 	Discussion and Decision

Conclusion
These are observations and proposals on SBFD Tx Rx measurement procedures.

Proposal 1: Guard symbols required for the transition from non-SBFD symbols to SBFD symbols must be placed exclusively in the SBFD slots.
Proposal 2: Consider the following options to handle inter slot interference:
Option 1: Use two timing advance offsets for UL transmission, one for SBFD symbols and another one for non SBFD symbols
Option 2: Atleast first uplink subband symbol is considered as guard symbol, either by SBFD frame structure configuration, RRC configuration or by sending DCI
   Option 3: Shortening the first uplink symbol by mapping alternate subcarriers.  

Proposal 3: UE specific guard band is not required in SBFD operation.
Proposal 4: The existing behaviour of UE i.e., transmission within valid symbols for actual repetition can be extended to SBFD symbols for PUSCH repetition Type B.
Proposal 5: Consider precoding bundling as wideband, when the number of scheduled PRBs is larger than half of the size of the DL usable PRBs.
Proposal 6: SSB symbols that are configured within SBFD subbands shall be treated as SBFD symbols.
If a UE is required to monitor an SSB in SBFD symbols, only DL receptions within DL usable PRBs are allowed for SBFD aware UEs.
If a UE is not required to monitor an SSB in SBFD symbols , then Uplink transmissions in the uplink subband is allowed. 
	Note: The SSB block is assumed to be within DL subband
Proposal 7: It is proposed to support Option 1, wherein the UE determines the link direction based on the configured and scheduled transmissions/receptions, applies collision handling procedures as applicable, and takes into account any explicit link direction indication received from the gNB.
Proposal 8: When the gNB needs to indicate the link direction, it can be done via Downlink Control Information (DCI) or through a Medium Access Control - Control Element (MAC-CE).

Proposal 9: For collision handling in SBFD symbols for SBFD aware UEs, Option 1 is preferred over other approaches as it is simple to implement.
Proposal 10: More discussion is required in RAN1 to indicate short message in SBFD.
Proposal 11: Consider one of the solutions as a starting point to solve missing short message occasions:
Option 1: Increase PDCCH monitoring occasions
Option 2: Link indication is required to indicate short message.
Option 3: Paging occasions falls only on downlink slots.
  
 

3GPP TSG RAN WG1 #121	R1-2503731
St Julian’s, Malta, May 19th – May 23th, 2025

Agenda item:		9.3.1
Source:		Ofinno
Title:			Discussion on SBFD TX RX measurement
Document for:	Discussion and Decision

Conclusion
This contribution has discussed the remaining issues related to the physical layer aspects of SBFD TX/RX/measurement procedure. The following are our observations and proposals: 
Proposal 1. RAN1 to conclude that there is no UE-specific indication of SBFD subband frequency location.
Proposal 2. NRB in PTRS frequency density and location of PDSCH/PUSCH in section 5.1.6.3 in TS 38.214 and section 7.4.1.2.2 in TS 38.211 is computed based on assigned PRBs within DL usable PRBs. 
-	 is the number of assigned resource blocks within DL/UL subbands on SBFD symbols or the number of scheduled resource blocks otherwise. 
Proposal 3.  in PUSCH power control in section 7.1.1 in TS 38.213 is computed based on assigned PRBs within UL usable PRBs. 
 is the bandwidth of the PUSCH resource assignment within a UL usable PRBs on SBFD symbols, or within UL BWP otherwise. 
Proposal 4.  in section 6.3.2.4.1.1 in TS38.212 is computed based on assigned PRBs within UL usable PRBs. 
 is the assigned bandwidth of the PUSCH transmission within UL usable PRBs on SBFD symbols or the scheduled BWP of the PUSCH transmission within UL BWP otherwise, expressed as a number of subcarriers. 
Observation 1. Current scheduled bandwidth (NRB, , ) of PUSCH/PDSCH for the following cases are based on number of PRBs scheduled by DCI or semi-static configuration regardless of actual number of PRBs used (or without considering usable DL/UL PRBs). 
NRB in PTRS frequency density and location of PDSCH/PUSCH
 in transmission power determination of PUSCH
 in PUSCH rate matching (the number of coded modulation symbols per layer determination)
Proposal 5. The assigned bandwidth of PUSCH/PDSCH is the number of transmitted/received PRBs within UL/DL usable PRBs, and it is used to determine:
NRB in PTRS frequency density and location of PDSCH/PUSCH
 in transmission power determination of PUSCH
 in PUSCH rate matching (the number of coded modulation symbols per layer determination)
Proposal 6. Introduce a new UE capability for rate-matching of PDSCH around unusable PRBs to support SPS PDSCH across SBFD and non-SBFD symbols.
Proposal 7. For SBFD-aware UE with configuration 2, UE changes frequency hops across the SBFD boundary and starts a next frequency hopping interval, when DMRS bundling is enabled with inter-slot frequency hopping.
Proposal 8. Separate configuration of PCMAX for SBFD and non-SBFD symbols is not supported.
Proposal 9. Extend the UL power control configuration within unified TCI states to BWP-UplinkDedicated to support separate UL power control when UL power control is not associated within unified TCI state.
Proposal 10. Separate TCI states for SBFD and non-SBFD symbols for both UL and DL is configured to support separate UL power control.
Proposal 11. To support separate TCI states for SBFD and non-SBFD symbols for separate power control, down-select from the following for UE to distinguish TCI state for SBFD symbols and non-SBFD symbols:
Option 1: Indication via RRC signalling (e.g., configuration of two separate lists of TCI states for SBFD and non-SBFD symbols, or a bit field indicating which of a pair of TCI states is for SBFD symbols).
Option 2: Indication via TCI state activation/deactivation MAC CE (e.g., additional field in MAC CE per codepoint to indicate which of the pair of activated TCI states is for SBFD symbols).
Option 3: Default rule (e.g., first TCI state or TCI state with the lowest TCI state ID is for SBFD symbols). 
Proposal 12. UE expects that PUCCH resources configured by the multi-CSI-PUCCH-ResourceList to have the same valid symbol type, i.e., UE expects both of resources are within SBFD symbols or non-SBFD symbols for the configuration 1. 
Proposal 13. For Configuration 1, when P/SP CSI reports are configured with valid symbol types and when multi-CSI-PUCCH-ResourceList is configured:
If the resoruces indicated by multi-CSI-PUCCH-ResourceList have the same symbol type to multiplexed CSI reports, the UE follow a legacy procedure in multiplexing.
If only one resource of multi-CSI-PUCCH-ResourceList has the same symbol type, use the resource, and drop excessive UCIs if necessary.
If both resources do not have the same sybol type, drop the CSI reports.
Proposal 14. Revise the agreement as follows.
Support SBFD operation on one or multiple TDD carrier in multi-carrier scenario.
Proposal 15. In handling a half-duplex CA with a SBFD operation, select from one of the following for reference cell determination on symbol overlapping with SBFD symbol of a cell:
Option 1. UE does not perform reference cell determination if a cell is enabled with a SBFD operation.
Option 2. UE determines a reference cell from cell(s) based on configured RRC signallings (e.g., CSI-RS, PDCCH, PDSCH, SRS, PUCCH, PUSCH, PRACH).
Proposal 16. To support intra-band carrier aggregation with SBFD, relax TDD configuration and dynamic UL collision as follows:
If a symbol is configured as downlink by TDD configuration on a reference cell and that symbol is not an SBFD symbol of another cell in the same frequency band, the UE does not expect dynamic UL transmission scheduling on the other cell in that symbol
If a symbol is configured as downlink by TDD configuration on a reference cell and that symbol is an SBFD symbol of other cell in the same frequency band, the UE may expect dynamic UL transmission scheduling on the other cell in that symbol.
Proposal 17. SBFD is supported with LTM.
Proposal 18. Enhance configurations (e.g., SBFD configuration, CSI report configurations) of LTM candidate cells to support SBFD operation of the candidate cells.  

3GPP TSG RAN WG1 Meeting #121																R1- 2503759
St. Julian’s, Malta, May 19th –23rd, 2025

Agenda item:		9.3.1
Title:						Discussion on SBFD Tx/Rx/measurement procedures 
Source:				Fraunhofer HHI, Fraunhofer IIS
Document for:		Discussion

Conclusions
The following proposals have been made in this document:
Proposal 1: Configuration 1 is considered as the default configuration if no configuration is provided.
Proposal 2: For SRS in SBFD symbols, the associated CSI-RS and the RS associated with spatial relation info should be in an SBFD symbol. For SRS in non-SBFD symbols, the associated CSI-RS and the RS associated with spatial relation info should be in a non-SBFD symbol.

Proposal 3: For SRS usage set to 'antennaSwitching', an SRS resource set is not explicitly associated with either SBFD or non-SBFD symbols. The valid symbol type for each SRS resource is explicitly or implicitly determined by the UE.

Proposal 4: For SPS and CG, indication or determination of different MCS values are supported for SBFD and non-SBFD symbols in different slots.
Proposal 5: For SPS PDSCH in configuration 2, the UE drops the reception of SPS in SBFD symbols if the DL usable resources are lesser than a threshold.
Proposal 6: For PUSCH DMRS bundling, DMRS bundling across both SBFD and non-SBFD symbols is avoided.
Proposal 7: For SBFD operation on one TDD carrier in a multi-carrier scenario, the existing directional collision handling for half-duplex TDD CA is reused by treating SBFD symbols as flexible symbols.

3GPP TSG RAN WG1 #121 		R1-2503790
St Julian’s, Malta, May 19th – 23th, 2025

Source:	CATT
Title:	Discussion on 	SBFD TX/RX/measurement procedures
Agenda Item:	9.3.1
Document for:	Discussion and Decision

Conclusion
In this contribution, we discuss SBFD TX/RX/measurement procedures and give the following observation and proposals.
Observation 1: If Rel-18 NES CSI reporting framework is reused for CSI reporting for different symbols types, only one NZP CSI-RS resource can be configured in the resource set for interference measurement.
Proposal 1: No explicit indication of transition period between SBFD and non-SBFD symbols.
Proposal 2: Update the following agreement made in RAN1#120-bis in red:
Agreement
For PUSCH repetition Type B with Configuration 1:
Alt 2:
For type 2 CG PUSCH, the valid symbol type for type 2 CG PUSCH is determined based on the symbol type of the first symbol of the first nominal actual repetition associated with activation DCI.
For dynamically scheduled PUSCH, the valid symbol type is determined based on the symbol type of the first symbol of the first nominal actual repetition occasion indicated by scheduling DCI.
FFS: UE drops an actual repetition if the actual repetition is in the invalid symbol type.
Proposal 3: For CSI-RS resources does not associated with a CSI report, CSI-RS resources across SBFD symbols and non-SBFD symbols can be supported from RAN1 perspective.
Proposal 4: For CSI report associated with CSI-RS instances occur in both SBFD symbols and non-SBFD symbols in different slots, support Option A and Option B.
For Option B, the following enhancements can be supported:
The first sub-configuration is for non-SBFD symbols and the second sub-configuration is for SBFD symbols;
Support two NZP CSI-RS resources in the resource set for interference measurement in one CSI-ReportConfig.
Proposal 5: For a single TRP scenario, support separate UL power control based on unified TCI state framework.
Proposal 6: For separate PUCCH power control parameters for SBFD and non-SBFD symbols, if unified TCI state is configured and UL power control parameters are not configured within unified TCI state, separate UL power control parameters for SBFD symbols and non-SBFD symbols can be configured in UL BWP associated with unified TCI state.
Proposal 7: For a single TRP scenario, in case gNB only configures UL power control parameters for one symbol type, the other symbol type should use the same UL power control parameters.
Proposal 8: For the following cases, if symbol type is not configured, non-SBFD symbol is applied by default.
Case 1: For configuration 1, the valid symbol type is configured by RRC for configured transmissions/receptions.
Case 2: The valid symbol type for SRS resources in the SRS resource set is configured by RRC. 
Case 3: For a CSI report associated with periodic/semi-persistent CSI-RS, the valid symbol type for CSI derivation is configured in CSI-ReportConfig.
Proposal 9: If link direction indication is not supported nor provided for a SBFD symbol, cell-specifically configured DL reception defined in collision Case 3 refers to PDCCH in Type-0/0A/0B/1/2 CSS set.
Proposal 10: Confirm the following working assumption.
Working Assumption
For SSB symbols configured with SBFD subbands, 
Option 1: The SSB symbols configured with SBFD subbands are SBFD symbols. Only DL receptions within DL usable PRBs are allowed for SBFD aware UEs.
Note: The SSB block is assumed to be within DL subband
Proposal 11: For SBFD aware UEs, adopt the following for collision handling order:
Step 1: Resolving SBFD specific collision between transmissions/receptions and unusable resources (e.g. invalid symbol type for Configuration 1, Tx/Rx occasion mapped to SBFD and non-SBFD symbols etc.) , if any.
Step 2: Resolving the collision as in legacy, if any. 
Proposal 12: For SBFD operation on one TDD carrier in multi-carrier scenario, half-duplex CA should be supported.
Proposal 13: If half-duplex CA with SBFD operation on one TDD carrier is supported, the same mechanism defined in Rel-16 half-duplex CA can be reused by treating SBFD symbols as flexible symbols.

3GPP TSG RAN WG1 #121                                  R1-2503827
St Julian’s, Malta, 19 - 23 May, 2025

Source: 	CMCC
Title:	Discussion on SBFD TX/RX/measurement procedures
Agenda item:	9.3.1
Document for:	Discussion & Decision

Conclusions
In this contribution, we discuss the transmission, reception and measurement procedure of SBFD aware UEs in SBFD symbols and the following proposals are made.
Proposal 1: Support not to configure a valid symbol type for CSI-RS based RLM/BFD/CBD measurement, i.e., CSI-RS resources across SBFD and non-SBFD symbols can be used for the same RLM/BFD/CBD measurement.
Proposal 2: For uplink power control for PUSCH/PUCCH/SRS/PRACH transmissions in SBFD symbols and non-SBFD symbols, don’t support separate configurations of maximum output power .
Proposal 3: For separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols for a given usage, support the following:
For aperiodic SRS with available slot counting, separate availableSlotOffsetLists can be configured in SRS-ResourceSets for SBFD symbols and non-SBFD symbols.
Proposal 4: For separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols for a given usage, confirm the working assumption in red texts made in RAN1#119 meeting.
Proposal 5: For PUSCH inter-slot frequency hopping in SBFD symbols and when pusch-DMRS-Bundling is enabled:
Separate pusch-FrequencyHopping-Interval can be configured for SBFD symbols and non-SBFD symbols respectively.
Proposal 6: For separate frequency configurations for SBFD symbols and non-SBFD symbols in the same PUCCH-Resource,
if the PUCCH frequency resource in SBFD symbols overlaps with RB outside UL usable PRBs, the PUCCH transmission is dropped
frequency hopping for PUCCH transmissions in SBFD symbols is disabled when no separate configuration of secondHopPRB is provided for SBFD symbols
Proposal 7: When UE performs inter-slot PUCCH frequency hopping in Configuration 2, further consider two options:
The even and odd slot number is counted separately for SBFD symbols and non-SBFD symbols.
The even and odd slot number is counted jointly regardless of SBFD symbols or non-SBFD symbols.
Proposal 8: For the configuration of PUCCH in SBFD symbols and non-SBFD symbols:
When PUCCH DMRS bundling is enabled, separate pucch-FrequencyHoppingInterval can be configured in SBFD symbols and non-SBFD symbols respectively.
Proposal 9: For collision handling in SBFD symbols for SBFD aware UEs, support the following option:
Option 1: 
Step 1: Resolving SBFD specific collision between transmissions/receptions and unusable resources (e.g. invalid symbol type for Configuration 1, Tx/Rx occasion mapped to SBFD and non-SBFD symbols etc.), if any.
Step 2: Resolving the collision as in legacy, if any, i.e.,
First resolve the overlapping issue between PUCCH and/or PUSCH transmissions, as specified in Clause 9 in TS 38.213.
Then resolve the collisions issues between DL reception in DL subband(s) and UL transmission in UL subband in a SBFD symbol.
Proposal 10: For SSB symbols configured with SBFD subbands, confirm the following working assumption made in RAN1#118bis meeting.
Working Assumption
For SSB symbols configured with SBFD subbands, 
Option 1: The SSB symbols configured with SBFD subbands are SBFD symbols. Only DL receptions within DL usable PRBs are allowed for SBFD aware UEs.
Note: The SSB block is assumed to be within DL subband
Proposal 11: In multi-carrier scenario with SBFD supported on one or more TDD cell(s), for a UE indicating the half-duplex CA capability, the legacy half-duplex CA collision handling rule can be reused by treating the SBFD symbols as flexible symbols in the cell(s) with SBFD operation.

3GPP TSG RAN WG1 #121			R1-2503879
St Julian’s, Malta, May 19th – 23rd, 2025

Source: 	     Xiaomi
Title:                  Discussion on reception and transmission procedure for SBFD operation
Agenda item:    9.3.1
Document for:  Decision 

Conclusion 
In this contribution, we provide our views on subband non-overlapping full duplex with following proposals.
Proposal 1: Explicit indication of transition periods between SBFD and non-SBFD symbols is not supported.
Proposal 2: For PUSCH repetition Type B with Configuration 1, UE drops an actual repetition if the actual repetition is in the invalid symbol type.
Proposal 3: A transmission in invalid symbol type for Configuration 1 and a transmission mapped to SBFD and non-SBFD symbols are dropped or postponed before resolving overlapping PUCCH and/or PUSCH. 
Proposal 4: For SBFD operation in half-duplex CA scenario, the existing directional collision handling for half-duplex TDD CA is reused by treating SBFD symbols as flexible symbols.

3GPP TSG-RAN WG1 Meeting #121	R1-2503970
St Julian's, Malta, 19th – 23th May, 2025

Agenda item:	9.3.1
Source: 	Kookmin University
Title: 	Discussion on SBFD TX/RX/measurement procedures
Document for:	Discussion and Decision

Conclusions
In this contribution, the remaining issues on the TX/RX/measurement procedures for SBFD were discussed. The following proposals were made:

Proposal 1: For dynamic determination of the precoding bundling for a PDSCH, the condition for determining wideband or narrowband depends on whether the number of scheduled PRBs is larger than half of the DL subband size where the PDSCH is allocated.

Proposal 2: For PUSCH inter-slot frequency hopping in SBFD symbols and non-SBFD symbols and when pusch-DMRS-Bundling is enabled, the starting RB during slot  is given by:


 is the current slot number within a system radio frame.
 is the number of UL usable PRBs.
 is the starting PRB index of the first PUSCH hop with reference to the start of UL active BWP.
RBoffset is the frequency hopping offset for PUSCH in non-SBFD symbols.

Proposal 3: For PUSCH repetition Type B with Configuration 1, UE drops an actual repetition if the actual repetition is in the in valid symbol type.

Proposal 4: When A-SRS is triggered for multiple SRS resource sets configured with different symbol types, the indicated SRS resources in both SBFD and non-SBFD symbols are transmitted when UE supports configuration 2 as capability.

Proposal 5. Valid symbol type configured for periodic/semi-persistent CSI-RS is applied for IMRs.

Proposal 6. Valid symbol type for aperiodic CSI-RS is determined by the symbol type of the first occasion indicated by DCI.

Proposal 7: From RAN1 perspective, explicit indication of transition periods between SBFD and non-SBFD symbols is not supported.

Proposal 8: Confirm the following working assumption:
Working Assumption
For SSB symbols configured with SBFD subbands, 
- Option 1: The SSB symbols configured with SBFD subbands are SBFD symbols. Only DL receptions within DL usable PRBs are allowed for SBFD aware UEs.
Note: The SSB block is assumed to be within DL subband

3GPP TSG RAN WG1 #121		R1-2504009
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Panasonic
Title:	Discussion on SBFD TX/RX/measurement procedures
Agenda Item: 		9.3.1
Document for:	Discussion

Conclusion
In this contribution, we made the following observations and proposals. 
Proposal 1: Not support explicit indication of guard periods.
Proposal 2: Send LS to RAN4 regarding the necessity of UE-specific guard band.
Proposal 3: For a physical channel/signal occasion mapped to SBFD and non-SBFD symbols within a slot, UE doesn’t expect to receive a DCI that is scheduling a single slot transmission or reception across SBFD and non-SBFD symbols in a slot.
Proposal 4: Support DMRS bundling in SBFD symbols at least for the case where an actual TDW is not across SBFD and non-SBFD symbols. FFS for the case where an actual TDW is across SBFD and non-SBFD symbols.
Proposal 5: Support separate configurations of p-Max for a slot containing SBFD symbol.
Proposal 6: For collision handling order in SBFD symbol, UE resolves overlapping PUCCH/PUSCH transmissions before SBFD specific collision handling between transmissions/receptions and unusable resources.
Proposal 7: For half-duplex CA case, reuse the legacy collision handling rules by treating as if SBFD symbol is indicated as flexible symbol.

3GPP TSG RAN WG1 #121			R1-2504044
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:		9.3.1
Source:	China Telecom
Title:	Remaining issues on SBFD TX/RX/measurement procedures
Document for:		Discussion

Conclusion
In this contribution, our views are provided on SBFD subbands time frequency location indication and TX/RX/measurement procedures for SBFD aware UE.
Based on the discussion, we have following proposals:
Proposal 1: UE-specific configuration on frequency location of SBFD subbands does not need to be specified. 
Proposal 2: For cell-specific frequency locations configuration of SBFD UL subband and DL subband(s) respectively each SCS configuration in SCS-SpecificCarrierList,
The indicated frequency locations of SBFD UL subband and DL subband(s) for each SCS should result into one continuous UL subband and one or two DL subbands from the cell perspective.
The configured UL subband for one SCS is not expected to be overlapped with configured DL subband for another SCS.

Proposal 3: The resource not available for PDSCH resource mapping is also not available for PUSCH resource mapping for SBFD-aware UEs and PUSCH is rate matched around the unavailable resource, considering RB symbol level granularity unavailable resource configured by RateMatchPattern(s) and RE level granularity LTE CRS and ZP CSI-RS unavailable resource.
Proposal 4: Discuss whether it is allowed the scheduled number of partial PRGs for a UE exceeds its reported capability about the maximum supported partial PRG number in SBFD symbols, considering the following options:
Option 1：An SBFD aware UE does not expect the scheduled number of partial PRGs to exceed its reported maximum supported partial PRG capability in SBFD symbols.
Option 2：When the scheduled number of partial PRGs is more than the UE capability on the maximum supported value, the UE can select the usable partial PRGs based on its capability according to a predefined rule.
Proposal 5: For PUSCH repetition Type B with Configuration 1, UE drops an actual repetition if the actual repetition is in the invalid symbol type.
Proposal 6: For an SBFD aware UE, a symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and it configured as an SBFD symbol is NOT considered as an invalid symbol for PUSCH repetition Type B transmission.
Proposal 7: For PUSCH FH across SBFD and non-SBFD symbols using configured FH interval, support to configure a FH interval respectively for each TDD-UL-DL pattern when two TDD-UL-DL patterns are configured to reduce the kinds of the consecutive slots number with the same PUSCH frequency location. 
Proposal 8: For PUCCH FH across SBFD and non-SBFD symbols using configured FH interval, consider the FH interval counting only the UL usable slots to reduce the kinds of the consecutive slots number with the same PUCCH frequency location. 
Proposal 9: For a CORESET and a USS configured that the MOs of the search space occur in both SBFD and non-SBFD symbols and the associated CORESET overlaps the boundary of DL usable PRBs in SBFD symbols for SBFD-aware UE, UE does not monitor a PDCCH candidate if it is mapped to one or more REs that overlap with REs outside DL usable PRBs in SBFD symbols.

3GPP TSG RAN WG1 #121	R1-2504087
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda item:	9.3.1
Source: 	Fujitsu
Title:	Discussion on SBFD TX/RX/measurement procedures
Document for:		Discussion and decision

Conclusion
According to the discussions above, we have the following proposals. 
SBFD configuration
Proposal 1: Do not support UE-specific configuration of SBFD subbands.
Proposal 2: UE determines SBFD/non-SBFD symbols for active DL/UL BWPs with NCP or ECP based on the SBFD/non-SBFD symbols configured with respect to referenceSubcarrierSpacing in TDD-UL-DL-ConfigCommon. For the active DL/UL BWP:
a symbol overlapping with only SBFD symbol or only non-SBFD symbol for referenceSubcarrierSpacing is considered as an SBFD symbol or a non-SBFD symbol, respectively.
a symbol overlapping with an SBFD symbol and a non-SBFD symbol for referenceSubcarrierSpacing is considered as (down-select from the following options):
Option 1: an SBFD symbol.
Option 2: a non-SBFD symbol.
Option 3: a gap between SBFD symbols and non-SBFD symbols.
Separate power control
Proposal 3: Support separate maximum output power for SBFD symbols and non-SBFD symbols.
An additional parameter is used to determine the maximum output power for SBFD symbols.
Proposal 4: To support per symbol-type closed-loop power control for PUSCH transmissions or PUCCH transmissions scheduled by a DCI format, two TPC commands can be included in the DCI format.
When the DCI format includes two TPC commands, each TPC command applies for each closed-loop power control respectively.
Proposal 5: In SBFD operation, for PUSCH repetition Type B, the UE determines transmission power per actual repetition (instead of nominal repetition in the legacy).
Proposal 6: Support separate PHRs for SBFD symbols and non-SBFD symbols.
Resue twoPHRmode and introduce new MAC CEs to support the separate PHRs.
PDSCH/PUSCH
Proposal 7: To determine HARQ process ID for multi-PUSCH scheduled by a single DCI or multi-PUSCH configured grant, 
In Configuration 1, 
If the valid symbol type is SBFD symbols, HARQ process ID is not allocated to a PUSCH overlapping with a non-SBFD symbol or a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.
If the valid symbol type is non-SBFD symbols, HARQ process ID is not allocated to a PUSCH overlapping with an SBFD symbol, or a non-SBFD symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.
In Configuration 2, 
HARQ process ID is not allocated to a PUSCH overlapping with a non-SBFD symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst, and is not allocated to a PUSCH across SBFD symbols and non-SBFD symbols.
Proposal 8: To determine HARQ process ID for multi-PDSCH scheduled by a single DCI, 
In Configuration 1, 
If the valid symbol type is SBFD symbols, HARQ process ID is not allocated to a PDSCH overlapping with a non-SBFD symbol.
If the valid symbol type is non-SBFD symbols, HARQ process ID is not allocated to a PDSCH overlapping with an SBFD symbol, or a non-SBFD symbol that is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
In Configuration 2, 
HARQ process ID is not allocated to a PDSCH overlapping with a non-SBFD symbol that is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and is not allocated to a PDSCH across SBFD symbols and non-SBFD symbols.
Proposal 9: For PDSCH selection in case of multiple PDSCHs in a slot, the UE determines if more than one SPS PDSCH are in a slot after excluding SPS PDSCH(s) according to the following rules:
In Configuration 1, 
If the valid symbol type is SBFD symbols, excluding a PDSCH overlapping with a non-SBFD symbol.
If the valid symbol type is non-SBFD symbols, excluding a PDSCH overlapping with an SBFD symbol, or a non-SBFD symbol that is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
In Configuration 2, 
Excluding a PDSCH overlapping with a non-SBFD symbol that is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or a PDSCH across SBFD symbols and non-SBFD symbols.
Proposal 10: For PUSCH repetition Type B, 
A non-SBFD symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is considered as an invalid symbol.
If numberOfInvalidSymbolsForDL-UL-Switching is configured, numberOfInvalidSymbolsForDL-UL-Switching symbol(s) after the last non-SBFD symbol that is indicated as downlink in each consecutive set of all symbols that are indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are considered as invalid symbol(s).
Proposal 11: For UCI multiplexing on PUSCH, separate β offset values can be supported to determine the number of UCI REs for SBFD symbols and non-SBFD symbols.
SRS
Proposal 12: For each SRS resource set with usage set to 'nonCodebook', the associated CSI-RS shares the same symbol type as the SRS resource set.
CA
Proposal 13: For half-duplex CA, if the SBFD cell is determined as the reference cell of a symbol, the symbol is configured as
downlink, or uplink, as indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated if the symbol is not an SBFD symbol
uplink, if the symbol is a flexible or SBFD symbol and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH on the symbol
downlink, if the symbol is a flexible or SBFD symbol and the UE is configured to receive PDCCH, PDSCH or CSI-RS on the symbol.

3GPP TSG RAN WG1 #121		R1-2504097
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item:	9.3.1
Source:	HONOR
Title:	Discussion on SBFD TX/RX/measurement procedures
Document for:	Discussion and Decision

Conclusions
In this contribution, we provide our views on SBFD TX/RX/measurement procedures with the following observations and proposals.
Proposal 1: Don’t support UE-specific configuration on frequency locations of SBFD subbands.
Proposal 2: Limit the number of Tx/Rx transitions the UE can perform within a time period.
Proposal 3: For SBFD operation in half-duplex CA, reuse the legacy collision handling rules by treating SBFD symbols as flexible symbols.
Proposal 4: For collision handling in SBFD symbols for SBFD-aware UEs, SBFD-specific collision between transmissions/receptions and unusable resources is handled first followed by legacy collision handling.
Proposal 5: The dynamic determination of wideband or narrowband precoding bundling is based on the scheduled PRBs and the size of active DL BWP as legacy.
Proposal 6: For SPS PDSCHs, PDSCH repetitions, and multi-PDSCHs, when the scheduled PRBs in a repetition/PDSCH are contiguous in non-SBFD symbols but the valid PRBs in a repetition/PDSCH are non-contiguous in SBFD symbols, UE does not expect that the PRG size is indicated as wideband.
Proposal 7: When the number of scheduled partial PRGs exceeds the maximum number of supported partial PRGs in SBFD symbols, use predefined rules to determine which partial PRGs are valid.

3GPP TSG RAN WG1 #121	R1-2504121  
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda item:		9.3.1
Source:				Nokia, Nokia Shanghai Bell
Title:					On SBFD TX/RX/measurement procedures
Document for:		Discussion and Decision

Conclusion
In this contribution we have provided our views regarding the required signaling to support SBFD operation, as well as UE transmission, reception and measurement behaviors. The following observations and proposals have been made: 
Proposal 1:	The working assumption in RAN1 #116 agreement for cell specific configuration of frequency location of SBFD subband should be confirmed.
Proposal 2:	In addition to cell-specific configuration of DL and UL subbands, signaling of UE-specific configuration can be supported, e.g. to configure some UEs to operate with larger guardband due to poorer filtering capabilities or different UE-UE CLI conditions compared guardband of gNB.
Proposal 3:	Signaling of the SBFD time and frequency configuration via RRC dedicated signaling can be considered, additionally to signaling in SIB, to support dual connectivity or carrier aggregation with SBFD carriers.
Proposal 4:	RAN1 should finalize the LS on UE-specific guardband and send to RAN4.
Observation 1:	On the location of the UE transient period, RAN1 TS 38.211 specifies a maximum requirement for UE Tx-Rx and Rx-Tx transition time. It is the responsibility of the gNB scheduler and configuration to ensure that the specified requirement is respected for each UE Tx-Rx and Rx-Tx transition.
Observation 2:	The use of flexible symbols for indicating UE Rx-Tx transitions is not captured in NR specifications. Nevertheless, this seems to be the de-facto assumption in today’s NR TDD product implementations.
Observation 3:	It is not properly justified to introduce explicit indication of transient period for the transition between DL to SBFD symbols considering that, within the SBFD symbols, the UE may also switch between UL and DL at any SBFD symbol based on gNB configured/scheduled transmissions/receptions.
Proposal 5:	RAN1 does not specify explicit indication of transient period for the transition between DL to SBFD symbols.
Proposal 6:	If RAN1 agrees to support explicit indication of transient period for the transition between DL to SBFD symbols, RAN1 shall also discuss the UE UL-DL switching behaviour within SBFD symbols considering that explicit indication of link direction in SBFD symbols is not supported.
Observation 4:	The TDD UL-DL pattern (provided via TDD-UL-DL-ConfigCommon) has typically a short periodicity of 1..5 ms, while some reference signals (e.g. SSB or CSI-RS for tracking) are transmitted with much larger periodicity (e.g. 20 .. 160 ms). The SBFD time-domain configuration shall allow SBFD operation in the majority of the time slots, while still allow some ‘sparse’ slots to operate as legacy/DL-only manner.
Proposal 7:	The periodic UL-DL pattern configuration can be complemented with additional cell-specific signaling that can change the configuration or format for one or some slots.
Observation 5:	On collisions between configured SSB and UL transmission, limiting the SSB block/CORESET0 to be within DL subband in Option 1 have significant drawbacks, e.g. it prevents SBFD operation in FR2 carriers of 100 MHz bandwidth, or even 200 MHz considering raster size of 17.28 MHz, or FR1 with limited bandwidth as 20/30/40MHz. Also, it limits the flexibility for placing the SSB according to operator-specific preferences.
Observation 6:	On collisions between configured SSB and UL transmission, transitions between SBFD and non-SBFD operation are not only for Option 2, but also apply to Option 1 considering that it is desirable to transmit the SSBs using all the antenna elements of the gNB antenna panel. This allows the SSB signals to reach the cell-edge and keep the SSB transmissions unchanged as compared to legacy TDD operation.
Proposal 8:	On collisions between configured SSB and UL transmission, RAN1 to revert the working assumption reached RAN1#118bis and adopt Option 2 instead (a slot consisting of SSB symbols is considered as a full DL slot)
Proposal 9:	RAN1 can also discuss some compromise solution, e.g. on which case Option 1 is selected and on which case Option 2 is selected.
Proposal 10:	For collision handling order, support Option 1 discussed in RAN1#120 as a conclusion (i.e. without additional impact). The UE first drops signals in invalid symbol type due to Configuration 1 (or dropping of Tx/Rx occasion mapped to SBFD and non-SBFD symbols), and then performs collision handling as in legacy (if any).
Observation 7:	From UE point of view, the number of transitions between Tx (UL) and Rx (DL) within the TDD pattern period is determined based on the configured/scheduled transmissions/receptions for the UE. The number of actual transitions between Tx and Rx within the TDD pattern period can be the same, smaller or larger than the transitions between SBFD- and non-SBFD symbols indicated via the SBFD time-domain configuration.
Observation 8:	Current specifications do not have any restriction in terms of number of number Tx-Rx transitions for operation in flexible symbols. Some slot formats in TS 38.213, Table 11.1.1-1 allow D->U->D->U within ONE slot.
Proposal 11:	RAN1 does not specify any limit regarding the number of Tx-Rx transitions the UE can perform within a time period (e.g. slot or TDD UL-DL pattern period). It is up to the gNB to ensure that the Tx-Rx switching time is respected, and that the overhead due to such Tx-Rx switching time is kept to a reasonable level.
Proposal 12:	For PUSCH repetition Type B with Configuration 1, UE drops an actual repetition if the actual repetition is in the invalid symbol type.
Proposal 13:	For PUSCH repetition Type B, the interpretation of numberOfInvalidSymbolsForDL-UL-Switching is unchanged.
Observation 9:	Without the definition of length (and take into account the non-contiguous allocated resources), it’s not straightforward to specify the location of the non-contiguous allocated resources in SBFD symbols for RA Type 0.
Proposal 14:	For PRBs determination in SBFD symbols for RA Type 0, RAN1 to adopt the text in the draft CR and remove the square brackets.
Proposal 15:	TBS determination for PUSCH, RAN1 to adopt the text in the draft CR and remove the square brackets.
Proposal 16:	SBFD UE should have different PDCCH resources in SBFD and non-SBFD symbols/slots. Search space for same PDCCH format(s) should be corresponding to different frequency resources, i.e. CORESET, on different slot types.
Observation 10:	Some PDCCH candidates, e.g. with aggregation level 4/8/16, may be disrupted as they overlap with UL subband/guard band.
Observation 11:	Different number of PDCCH candidates are available in SBFD and non-SBFD slots.
Proposal 17:	Only the available/non-disrupted PDCCH candidates can be considered in PDCCH detection, in both SBFD and non-SBFD slots.
Observation 12:	RAN1 has agreed that the configuration of a valid symbol type is not applicable to CSI-RS configured for RLM/BFD.
Observation 13:	Performing RLM/BFD across different symbol types may entail significant changes to the RLM procedure, thresholds, and/or counters. Simplified solution is preferred given the limited time remaining for the current Rel-19 work item.
Proposal 18:	The configuration of CSI-RS for RLM/BFD is limited to one symbol type. The UE does not expect to be configured with CSI-RS for RLM/BFD that occurs in different symbol types.
Observation 14:	Allowing PUCCH transmission triggered by a SPS PDSCH reception to be valid in both SBFD and non-SBFD symbol types prevents the use of SPS PDSCH with short periodicities.
Proposal 19:	RAN1 to discuss whether to support configuring a valid symbol type for PUCCH corresponding to SPS PDSCH HARQ-ACK in order to support SPS PDSCH with short periodicities in SBFD operation.
Proposal 20:	If no separate configuration is provided for SBFD symbols, PUCCH transmissions in SBFD symbols for the pucch-ResourceId is not expected.
Observation 15:	RAN1 has already agreed to support separate open-loop power control parameters (p0, alpha) for SBFD and non-SBFD symbols for PUSCH, PUCCH, SRS and PRACH transmissions
Observation 16:	Limiting of the UE’s maximum output power can be done according to gNB scheduling taking into account corresponding p0 and alpha parameters as well as the reported Power Headroom (PHR) from the UE.
Observation 17:	Reducing the UE transmission power negatively impacts the UL coverage which goes against the main motivation of SBFD.
Proposal 21:	RAN1 does not consider separate configurations of PCMAX for SBFD and non-SBFD symbols in Release 19.

3GPP TSG RAN WG1 #121	R1-2504136
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	9.3.1
Source: 	ETRI
Title:	Discussion on SBFD TX/RX/measurement procedures
Document for:	Discussion/Decision

Conclusion
In this contribution, ETRI’s views on SBFD were shown and the following observation and proposals were made:
Observation 1. A CSI-ReportConfig for CQI report should be linked to two or three Resource Settings:
The first Resource Setting is for channel measurement from NZP CSI-RS (CMR)
The second or third Resource Setting is for interference measurement from CSI-IM/ZP CSI-RS or NZP CSI-RS (IMR)
Observation 2. CQI reporting for SBFD DL subbands is an essential feature to enable SBFD
Hence, UE behaviours for both CMR and IMR on SBFD and non-SBFD symbols should be clear.
Observation 3. Agreements and TPs on valid symbol type for CSI derivation so far are limited to the followings, only:
(NZP) CSI-RS, i.e., not explicitly covering CSI-IM
Semi-persistent or periodic CSI-RS, i.e., not covering aperiodic CSI-RS

Observation 4. The following UE behaviours are missing for SBFD DL subband CQI report:
Valid symbol type of IMR for CSI derivation
Valid symbol type of aperiodic CSI-RS for CSI derivation

Proposal 1. RAN1 to apply/extend the previous agreements on valid symbol type of CSI-RS for CSI derivation to the following cases as well:
Valid symbol type of IMR for CSI derivation
Valid symbol type of aperiodic CSI-RS for CSI derivation
Proposal 2. For a CSI report associated with periodic/semi-persistent CSI-RS, the valid symbol type for CSI derivation configured in CSI-ReportConfig applies for all CMRs and IMRs associated with the CSI report
Proposal 3. For a CSI report associated with periodic/semi-persistent CSI-RS, the valid symbol type for CSI derivation configured in CSI-ReportConfig applies for CSI reference resource associated with the CSI report
If the valid symbol type configured by the CSI report is SBFD symbols, only the REs on SBFD symbols and DL usable PRBs in the corresponding CSI reference resource shall be used for TBS determination of the CSI report
Proposal 4. For a CSI report associated with aperiodic CSI-RS,
the valid symbol type for CSI derivation determined by the symbol type of the first measurement occasion among the all CMRs and IMRs associated with the CSI report
the same valid symbol type applies for all CMRs, IMRs, and CSI reference resource associated with the CSI report
if the valid symbol type is SBFD symbols, only the REs on SBFD symbols and DL usable PRBs in the corresponding CSI reference resource shall be used for TBS determination of the CSI report
Proposal 5. A SBFD-aware UE reports a CSI, only if all of the corresponding CSI reference resource, CMRs, and IMRs is in the valid symbol type of the CSI report.
Otherwise, the CSI report is dropped.
Proposal 6. For CSI report associated with the CSI-RS across two DL subbands,
Option 1: the number of wideband CQI is one for a given CSI reference resource
Without further RAN1 agreements, we believe that the option 1 shall be assumed
Option 2: the number of wideband CQI can be up to two for a given CSI reference resource. (One wideband CQI per DL subband)
Proposal 7. For CSI report associated with the CSI-RS across two DL subbands,
Option 1: the same value of  is applied for all DL subbands.
Without further RAN1 agreements, we believe that the option 1 shall be assumed
Option 2: different values of  are applied across different DL subbands.

3GPP TSG RAN WG1#121                              R1- 2504174
St Julian’s, Malta, May 19th - 23rd, 2025

Agenda Item:	9.3.1
Source:	Transsion Holdings
Title:	Discussion on SBFD operation
Document for:	Discussion and decision

Conclusion
In this contribution, we focus on the SBFD operation, including the semi-static indication of time and frequency location of SBFD subbands to UEs, the Tx/Rx/measurement procedures and CSI measurements and reporting. Based on the discussion in section 2, we provide the following proposals:
Proposal 1: Guard period between the last non-SBFD DL symbol and the first symbol of UL subband is needed.
Proposal 2: The method to generate guard period at least include:
Alt 1: guard period between the last non-SBFD DL symbol and the first symbol of UL subband should be located within the SBFD symbol.
Alt 2: the UE does not expect uplink channel and/or signal transmission over the first X symbols in the uplink subband of the SBFD symbol
Proposal 3: For dynamic determination of the precoding bundling for a PDSCH, when the bundling size indicator bitfield in the DCI indicates ‘1’ and first set configured with two values as ‘n4-wideband’ or ‘n2-wideband’, the condition for determining wideband or narrowband depends on whether the number of scheduled PRBs is larger than half of the size of the DL usable PRBs
Proposal 4: The issue of the RBs within UL subband cannot be indicated by fallback DCI should be studied.
Proposal 5: An offset that is applied to the start of the RB allocation indicated by the fallback DCI should be introduced.
Proposal 6: for UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols in different slots, the configurations are provided per UE per serving cell basis.
Proposal 7: For configuration 1, the exclusion of SPS PDSCH transmission in the invalid symbol type should be applied before SPS PDSCH transmission collision handling.
Proposal 8: For configuration 1, if HARQ-ACK bundling operation is configured, the following methods can be applied:
Alt 1: Excluding PDSCH in invalid symbol type before applying the binary AND operation.
Alt 2: Generating ACK for the PDSCH in invalid symbol type.
Proposal 9: For CSI report associated with periodic/semi-persistent CSI-RS, support Option A.
Proposal 10: For periodic and semi-persistent CSI-RS, the CSI-RS transmissions in invalid symbol types should be dropped.

3GPP TSG RAN WG1 #121                                                                                         R1-2504209
St Julian’s, Malta, May 19th – 23th, 2025

Source:	OPPO
Title:	Discussion on SBFD Tx/Rx/measurement procedures
Agenda Item:	9.3.1
Document for:	Discussion and Decision

Conclusions
In this contribution, we discuss the potential enhancements on SBFD TX/RX/measurement procedures with the following observations and proposals:
Proposal 1: For the case that PDSCH is scheduled with contiguous PRBs in SBFD symbols, for dynamic determination of the precoding bundling, when DCI bitfield (bundling size indicator) indicates ‘1’ and first set configured with two values as ‘n4-wideband’ or ‘n2-wideband’, the condition for determining wideband or narrowband depends on whether the number of scheduled PRBs is larger than half of the size of the corresponding part of DL usable PRB.
Proposal 2: UE does not expect to be configured to report subband CSI reporting corresponding to a CSI subband which fully overlaps with UL subband and/or guard band.
Proposal 3: It is not necessary to restrict the number of PRBs of a CSI-RS resource within each DL subband to be greater than the minimum between 24 PRBs and the size of the corresponding DL usable PRBs.
Proposal 4: For an SBFD aware UE, for PUSCH repetition Type B, a non-SBFD symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is considered as an invalid symbol for PUSCH repetition Type B transmission.
Proposal 5: For PUSCH repetition Type B with Configuration 1: UE drops an actual repetition if the actual repetition is in the invalid symbol type.
Proposal 6: For support of separate configurations for SBFD symbols and non-SBFD symbols in the same PUCCH-Resources, support separate configurations of nrofSymbols and nrofPRBs for SBFD symbols and non-SBFD symbols.
Proposal 7: It is not necessary to support separate configurations of p-Max for SBFD and non-SBFD symbols.
Proposal 8: For collision handling in SBFD symbols for SBFD aware UEs, support option 1 with no additional RAN1 specification imapct:
Step 1: Resolving SBFD specific collision between transmissions/receptions and unusable resources (e.g. invalid symbol type for Configuration 1, Tx/Rx occasion mapped to SBFD and non-SBFD symbols etc.), if any.
Step 2: Resolving the collision as in legacy, if any. 
Note: No additional RAN1 specification impact is expected.

3GPP TSG RAN WG1 #121	    R1-2504286

St Julian’s, Malta, May19th – 23rd, 2025

Agenda item:	9.3.1
Source: 	Lenovo
Title: 	SBFD TX/RX Measurement Procedures
Document for:	Discussion and Decision
Discussions on remaining issues
Remaining issue 1: Collision handling in half-duplex CA
In RAN1#120 meeting, the following agreement was reached to support SBFD operation on one TDD carrier in multi-carrier scenario.

Regarding the FFS, the existing directional collision handling for half-duplex TDD CA does not consider scenario when at least one cell is configured with SBFD operations, where an UL subband is configured on DL and/or flexible symbols and a SBFD-aware UE can be scheduled with either DL reception or UL transmission on those symbols. For collision handling across cells in half-duplex TDD CA, we support treating SBFD symbols as flexible symbol and reuse the existing directional collision handling, which is a sufficient and a straightforward approach with less spec impact. 
For SBFD operation in half-duplex CA scenario, the existing directional collision handling for half-duplex TDD CA are reused by treating SBFD symbols as flexible symbols.

Remaining issue 2: Wideband PRG of PDSCH
In RAN1#118 meeting, it was concluded that “If PRG is determined as wideband, UE does not expect to be scheduled with non-contiguous PRBs in SBFD symbols”.

If prb-BundlingType=staticBundling and ‘wideband PRG’ is configured, the above conclusion implies that only one DL subband can be utilized for PDSCH reception.  On the other hand, if prb-BundlingType=dynamicBundling, the PRG size is determined based on a 1-bit PRB bundling size indicator in a DCI format, the number of scheduled PRBs, and DL BWP size. If PRB bundling size indicator indicates ‘0’, the PRG size is determined from ‘bundleSizeSet2’. Otherwise, the PRG size is determined from ‘bundleSizeSet1’. If ‘bundleSizeSet1’ includes ‘n2-wideband’ or ‘n4-wideband’, then the ‘wideband PRG’ is determined only if the number of scheduled PRBs exceeds half of DL BWP PRBs. With DUD SBFD configuration, even if a PDSCH spans all the PRBs in one DL subband, the ‘wideband PRG’ cannot be used, since the number of PRBs in one DL subband may not exceed half PRBs of DL BWP. To address this issue, the following proposal from the last meeting can be supported.  
Support the following “Proposed Agreement” from RAN1#120bis meeting. 

Remaining issue 3: Separate configurations of p-Max
In RAN1#120bis meeting, the following proposal regarding support of separate configurations of p-Max for SBFD and non-SBFD symbols was discussed, but with no agreement. In our view, this proposal is beneficial, and we believe that it is necessary to defined two different maximum power level for SBFD and non-SBFD symbols. 

Support separate configurations of p-Max for SBFD and non-SBFD symbols.
Remaining issue 4: PDSCH with fdmschemeB
In legacy, when fdmschemeB is configured for a UE, for wideband case, the PDSCH occasion corresponding to first TCI state is located at the first half PRBs of the allocated resource, and the PDSCH occasion corresponding to second TCI state is located at the remaining allocated PRBs. When the allocated resource is overlapping with UL subband, the PRBs number for each TCI state should be decided. For example, the invalid RPBs in UL subband could be excluded firstly, then the PDSCH occasion corresponding to first TCI state is located at the first half valid PRBs of the allocated PRBs, and the PDSCH occasion corresponding to second TCI state is located at the remaining valid RRBs of the allocated PRBs. For PRG(s) with size of 2 and 4, whether the invalid PRG should be indexed to determine the PDSCH occasion corresponding to each TCI state should also be determined.
For SBFD-aware UEs configured with fdmschemeB and two TCI states for a PDSCH transmission, if the allocated resource overlaps with SBFD UL subband boundary, the actual PRBs for each PDSCH occasion corresponding to each TCI state should be determined.
Remaining issue 5: Radio link monitoring 
In Section 5 of 38.213, the radio link monitoring procedures is specified, as copied below, where UE indicates “out-of-sync” to higher layers when the radio link quality is worse than the Qout threshold for all radio link monitoring resources, and “in-sync” when the radio link quality is better than the Qin threshold for any radio link monitoring resource. Similar mechanism is used for beam failure detection.

It has been supported that frequency resource allocation for a configured CSI-RS resource could across downlink subbands for SBFD-aware UEs, and the actual CSI-RS resource allocation with non-contiguous CSI-RS resource is derived by excluding frequency resources outside DL usable PRBs. For a CSI report associated with P/SP CSI-RS, the valid symbol type for CSI derivation for P/SP CSI-RS resources for the CSI report is explicitly configured. Only CSI-RS transmission occasions within the valid symbol types are used for CSI derivation. 
For BFD or RLM, similar method could be used for the configured CSI-RS for measurement. Thus, two measurement results corresponding to two symbol type could be derived based on the configured CSI-RS. As for which should be used, there could be two methods. For the first method, only one measurement result should be used, thus gNB could configure the valid symbol type used for measurement and compare the measurement result to the configured Qout. The second method is to use both measurement results, thus gNB could configure separate Qout threshold for SBFD symbols and non-SBFD symbols to account for different radio link quality and interference situations between the two symbol types. 
For SBFD-aware UEs, the valid symbol type used for measurement or separate Q thresholds for SBFD symbols and non-SBFD symbols should be provided for RLM or BFD. 
Conclusions
In summary, we propose the followings for Rel-19 NR subband non-overlapping full duplex operation:
For SBFD operation in half-duplex CA scenario, the existing directional collision handling for half-duplex TDD CA are reused by treating SBFD symbols as flexible symbols.

Support the following “Proposed Agreement” from RAN1#120bis meeting. 
Proposed Agreement: For dynamic determination of the precoding bundling for a PDSCH, when DCI bitfield (bundling size indicator) indicates ‘1’ and first set configured with two values as ‘n4-wideband’ or ‘n2-wideband’, the condition for determining wideband or narrowband depends on whether the number of scheduled PRBs is larger than half of the size of intersection between active DL BWP and DL subband in which the PDSCH is located.

Support separate configurations of p-Max for SBFD and non-SBFD symbols.

For SBFD-aware UEs configured with fdmschemeB and two TCI states for a PDSCH transmission, if the allocated resource overlaps with SBFD UL subband boundary, the actual PRBs for each PDSCH occasion corresponding to each TCI state should be determined.

For SBFD-aware UEs, the valid symbol type used for measurement or separate Q thresholds (Qout and Qin) for SBFD symbols and non-SBFD symbols should be provided for RLM or BFD. 

TDoc file conclusion not found

3GPP TSG RAN WG1 Meeting #121                                                 	   R1-2504289
St. Julians, Malta, May 19th – 23rd, 2025

Agenda item:	9.3.1
Source:	Charter Communications
Title:	Discussion on SBFD Tx/Rx/measurement procedures
Document for:	Discussion/Decision

Conclusions
Based on the discussion in the previous section we propose the following:

Proposal 1: Adjust the transmit power equations in SBFD symbols/slots for different UL channels and UL reference signals by considering the interference level observed at the input of the receiver at gNB.  Update all the UE Tx power equations in 38.213 [3].

Proposal 2: Interference level is signalled to the SBFD aware UEs either in ConfiguredGrantConfig or in P0-PUSCH-AlphaSet. 

Proposal 3: Reduce or back-off the maximum UE transmit power in the SBFD symbols/slots to limit UE-to-UE CLI in the adjacent legacy TDD networks.  gNB will signal either a separate maximum UE transmit power to UE for SBFD symbols/slots () or back off value(s) (X dB) to the UE which will be used to back off maximum UE transmit power during SBFD symbols/slots.

Proposal 4: Write an LS to RAN4 to specify the maximum UE transmit power for UL transmissions in the SBFD symbols/slots to limit the UE-to-UE CLI.

Observation 1: If it were possible for SRS configurations to be exchanged between gNBs then victim UEs served by some gNB could potentially identify any aggressor UE(s) served by some neighboring gNB, whereby the latter could potentially limit the maximum transmit power of said identified UE(s). 

Observation 2: The current WID [2] challenges the exchange of SRS configuration information between gNBs, whereby precluding the victim UE from constructively identifying aggressor UE(s) served by some neighboring gNB.

Observation 3: To enhance the coverage in SBFD networks during SBFD symbols/slots with reduced maximum UE transmit power, cell edge UEs may use repeated transmissions to reach their anchor gNBs, perhaps with a TDD pattern that provisioned contiguous SBFD symbols/slots (i.e., with appropriated UL resources), so as to make repetitions on the UL possible.

Observation 4: If some of the cell-edge UEs with reduced maximum transmit power and repeated transmissions are not able to reach the anchor cells during SBFD symbols/slots then those UEs will be scheduled during legacy UL symbols/slots.  In this case the coverage of the SBFD network will be no worse than that of a legacy TDD network.

Observation 5: Reducing the power of an aggressor UE will alleviate UE-to-UE CLI experienced by the victim, while repetitions scheduled during SBFD symbols/slots—aimed to compensate for higher pathloss at the cell-edge—do not preclude latency advantage of SBFD with respect to legacy TDD.  Likewise, those UEs relegated to legacy UL TDD slots are naturally expected to not experience worse coverage than legacy TDD.

3GPP TSG RAN WG1 #121                                                                     R1- 2504315	
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	9.3.1
Source:	Apple Inc.
Title:	Remaining issues on SBFD TX/RX/measurement procedures
Document for:	Discussion/Decision

Conclusion
In this contribution, we provided our views on remaining issues related to UE TX/RX/measurement procedures for SBFD operation at the gNB. Based on what we discussed, the following proposals are made:
Proposal 1: Support transient time at the beginning of SBFD duration, with the candidate values for transient time are {1, 2, 3} symbols in TDD band numerology. 

Proposal 2: Do not support separate configurations of PCMAX, or p-max for SBFD and non-SBFD symbols

Proposal 3: Support separate PHR reports associated to SBFD and non-SBFD, when separate UL power control parameters for SBFD symbols and non-SBFD symbol is indicated through the same unified TCI state.

Proposal 4: For a type-1 CG-PUSCH and Configuration 2, ConfiguredGrantConfig may include a pair of parameters for MCS, (mcsAndTBS, mcsAndTBS2) where the second value indicates the parameter for CG-PUSCH transmission in SBFD slot.  

Proposal 5: For Configuration 2 and type-2 CG PUSCH or SPS-PDSCH, or multi-grant PUSCH/PDSCH, DCI indicates a MCS which is applied to non-SBFD occasions, while a RRC configured offset to the MCS indicated by DCI is applied to SBFD occasions.

Proposal 6: A SBFD-aware UE does not expect a SBFD symbol to be configured as UL or DL symbol in TDD slot configuration via TDD-UL-DL-ConfigDedicated.

3GPP TSG RAN WG1 #121			   R1-2504391
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda item:	9.3.1
Source: 	Qualcomm Incorporated
Title: 	SBFD Transmission, Reception and Measurement Procedures
Document for:	Discussion/Decision

Conclusion
In this contribution, we provided our views on SBFD transmission, reception and measurements procedures with following proposals:
Proposal 1: Confirm the working assumption on cell-specific SBFD frequency indication with the following updates.
Send an LS to RAN4 on the feasibility and use-case of SBFD-aware guardband and single DL subband.
Proposal 2: For collision handling order, UE determine overlapping PUCCH/PUSCH transmission before SBFD specific collision between transmissions/receptions.
Proposal 3: For UE reporting handle half-duplex CA with one or more carrier supporting SBFD operation, SBFD symbol is treated as flexible symbol. 
link direction in the SBFD symbol is determined based on configured/scheduled transmissions/receptions and collision handling (if any). 
For intra-band CA, UE doesn’t expect to a symbol to be indicated as uplink on cell and as SBFD symbol on another cell.
SBFD specific collision between transmissions/receptions are resolved before handling collision between configured/scheduled transmission/reception between reference cell and other cells.

Proposal 4: Support semi-static configuration of the locations and lengths of transition/guard periods between SBFD and non-SBFD symbols. The configurations can be UE-specific based on UE capability reporting of required transition periods between SBFD and non-SBFD symbols.
Proposal 5: For dynamic determination of the precoding bundling, when DCI bitfield (bundling size indicator) indicates ‘1’ and first set configured with two values as ‘n4-wideband’ or ‘n2-wideband’, the condition for determining wideband or narrowband depends on whether the number scheduled PRBs larger than half of the size of the DL subband 

Proposal 6: For PUSCH repetition Type B, when UE is provided with configuration #1, UE transmit actual repetitions only in the valid symbol type, i.e. UE drops an actual repetitions in the invalid symbol type. 
Proposal 7: When UE is provided with configuration #1 where the transmissions/receptions are restricted to SBFD symbols only or non-SBFD symbols only, transmissions/receptions occasions in invalid symbol type and transmissions/receptions occasions across SBFD and non-SBFD symbols in a slot are excluded for the following:
HARQ process ID for multiple PUSCHs/PDCSHs scheduled by single DCI
HARQ process ID for multiple CG-PUSCH occasions in a CG-period
UE procedure for reporting UTO-UCI of valid CG TOs.

Proposal 8: When UE is not provided semi-statically with valid symbol type for SRS, CSI-ReportConfig and PUCCH resource carrying P/SP CSI or SR, then default assumption is non-SBFD symbol as valid symbol type.
Proposal 9: for RA type 0 of PUSCH transmissions with Configuration, RAN1 to clarify whether RBG(s) in SBFD symbols should be aligned with the RBG(s) grid or not. 
Proposal 10: For PUSCH repetition with inter-slot frequency hopping in SBFD symbols and when pusch-DMRS-Bundling is enabled, the start RB in SBFD symbols is determined as following:

For configuration #1, the start-RB (is by startRB given by the FDRA. 
For configuration #2, the start-RB (is determined as 

Proposal 11: When DMRS bundling is enabled, the phase coherency is not maintained across SBFD and non-SBFD symbols. The actual TDW is terminated at the boundary and new actual TDW is started.
Proposal 12: For PUSCH Type B repetition with inter-repetition frequency hopping in SBFD symbols, for an actual repetition within the n-th nominal repetition in SBFD symbols


For configuration #1, the start-RB (is given the RIV of the FDRA. 
For configuration #2, the start-RB (is determined as 

Proposal 13: For P/SP CSI reporting, UE shall derive the CSI metrics based on CSI-RS occasions no later than the CSI reference resource, where the CSI reference resource in time has to correspond to a valid DL slot. 
A valid DL slot may or may not contain SBFD symbols.
For deriving SBFD CSI metrics, the UE shall assume that the CSI reference resource contains only the usable DL PRBs in the CSI report bandwidth.     

Proposal 14: For a CSI report associated P/SP CSI-RS and valid symbol is to SBFD symbols only, UE doesn’t expect to be configured for CSI reporting subband(s) that is completely outside the DL usable PRBs 

Proposal 15: Support separate default power control parameters for SBFD and non-SBFD symbols configured per UL-BWP when the unified TCI state is not associated with power control parameters. 

Proposal 16: Support two PHRs reporting associated with uplink transmission in SBFD and non-SBFD symbols.

3GPP TSG RAN WG1 #121			R1-2504478
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Sharp
Title:	SBFD Tx/Rx/measurement aspects
Agenda Item:	9.3.1
Document for:	Discussion and Decision
Resource mapping and rate matching
PDSCH
The draft CR for TS38.214 was endorsed in R1-2503480 [1]. Below is the relevant part related to PDSCH resource mapping and rate matching, available in the latest update at [Post-120bis-Rel19-38.214-NR_duplex_evo].

The above shows that in both RA types, only the assigned PRBs that fall within both the active DL BWP and the DL sub-band(s) are used for PDSCH reception in SBFD symbol(s). However, it remains unclear how the assigned PRBs outside the DL sub-band(s) which are not used for PDSCH reception should be handled in SBFD symbols. There are two possible interpretations.
(puncturing-based approach) the modulation symbols in the assigned PRBs outside of the DL sub-band(s) not used for PDSCH reception are punctured 
(rate-matching-based approach) the modulation symbols are mapped avoiding the assigned PRBs outside of the DL sub-band(s) not used for PDSCH reception
Our view is interpretation 2. Interpretation 1 will lead to degraded performance due to unexpected puncturing of systematic bits, e.g., for initial transmission with RV0. Therefore, we propose the following clarification.
Proposal 1: The modulation symbols are mapped avoiding (or rate-matched around) the assigned PRBs outside of the DL sub-band(s) not used for PDSCH reception in SBFD symbols.
To clarify the behaviour above, we need a change to the modulation symbol mapping procedure in TS38.211. Here is the suggested update on TS38.211.
Proposal 2: Adopt the following TP#1.

PUSCH
The draft CR for TS38.214 was endorsed in R1-2503480 [1]. Below is the relevant part related to PUSCH resource mapping and rate matching, available in the latest update at [Post-120bis-Rel19-38.214-NR_duplex_evo].

The above indicates that only the allocated PRBs that fall within both the active UL BWP and the UL sub-band are used for PUSCH transmission in SBFD symbol(s). A similar question arises for PUSCH as it does for PDSCH. Our understanding is that modulation symbols are mapped avoiding the allocated PRBs that fall outside the UL sub-band and are therefore not used for PUSCH transmission.
Proposal 3: The modulation symbols are mapped avoiding (or rate-matched around) the assigned PRBs outside of the UL sub-band not used for PUSCH transmission in SBFD symbols.
Corresponding TP is provided on the endorsed TS38.211 draft CR [2].
Proposal 4: Adopt the following TP#2.

PT-RS
With the current specification, if PT-RS mapping does not change, the mapping of PT-RS may be outside of the DL/UL subband(s). An example for the case of PT-RS mapping when transform precoding is enabled is shown in Figure 1. In Figure 1, the number of PT-RS groups , and the number of samples per PT-RS group . In this case, PT-RS mapping occurs at both edges of the scheduled bandwidth, as shown in blue. However, the edge RBs are highly likely outside of the UL subband, causing the PT-RS samples in these RBs to be lost.
To address this issue, assigned PRBs outside of the UL sub-band should be excluded from the scheduled bandwidth before PT-RS mapping determination. This ensures that PT-RS mapping remains within the UL sub-band.
Proposal 5: At least when transform precoding is enabled, the assigned PRBs outside of the UL sub-band should be excluded from the scheduled bandwidth before PT-RS mapping determination.

Figure 1: PT-RS mapping when transform precoding is enabled, the number of PT-RS groups , and the number of samples per PT-RS group 
Collision handling order
In the feature lead summary developed in RAN1#120 [3], the following proposal was captured and discussed.

Option 1 has a critical issue when the PUCCH resource changes after collision handling (i.e., UCI multiplexing). If the PUCCH resource after change is mapped beyond the UL subband, SBFD specific collision resolution need to be done again.
Figure 2 shows an example of PUCCH resource change during UCI multiplexing procedure. If PUCCH#0 for HARQ-ACK overlaps with PUCCH#1 for CSI, in the UCI multiplexing procedure, the final PUCCH resource may change by PUCCH resource set selection. For example, if PUCCH#0 is a PUCCH resource in PUCCH resource set#0 which gives resource for up to 2 UCI bits, during the UCI multiplexing procedure, a new PUCCH resource (i.e., PUCCH#2 in Figure 2) would be identified from a PUCCH resource set other than the PUCCH resource set#0. It is possible that the new PUCCH resource is mapped beyond the UL subband. Therefore, Option 1 does not work.

Figure 2: PUCCH resource change during UCI multiplexing procedure
Difference in Option 2 and 3 lies in the collision handling order. For example, in an example shown in Figure 3a, Option 2 will provide benefit over Option 3 since in Option 2, SPS PDSCH reception is available while in Option 3, the SPS PDSCH reception is dropped. However, in Figure 3b, in Option 2, PUCCH#0 for CSI is dropped while in Option 3, CSI and HARQ-ACK can be multiplexed in PUCCH#2 during the UCI multiplexing procedure. Therefore, Option 2 and 3 have pros and cons. 
From the legacy specification perspective, the situation in Figure 3b has not been solved in any Releases of 5G NR. Thus, we think it is an error case. The situation in Figure 3b is possible and in the legacy specification, it follows the order in Option 3.

Figure 3: Example collision handling order
Our view is closest to Option 3. However, strictly speaking, our understanding of how the current specification works is different, which is as follows:
Step 1: Perform UCI multiplexing
Step 2: Resolve collision handling specified in Section 11.1 of TS38.213 as well as SBFD specific collision handling

With that, we believe no specification change or work is required to resolve collisions.
Proposal 6: Clarify the collision handling order as follows:
Step 1: Perform UCI multiplexing
Step 2: Resolve collision handling specified in Section 11.1 of TS38.213 as well as SBFD specific collision handling
Observation 1: No specification change is necessary in the order of collision resolution specified in Section 11.1 of TS38.213 and SBFD specific collision resolution.
PUCCH repetition available slot counting
The following agreement has been made at RAN1#120bis meeting [4].

However, the above agreement for PUCCH available slot counting was not captured in the TS38.213 draft CR [5]. Therefore, we propose the following text proposals to capture the PUCCH available slot counting for Configuration 1.
Proposal 7: Adopt the following TP#3.

The following agreement has been made at RAN1#120bis meeting [4].

However, the above agreement for PUCCH available slot counting was not captured in the TS38.213 draft CR [5]. Therefore, we propose the following text proposals to capture the PUCCH available slot counting for Configuration 2.
Proposal 8: Adopt the following TP#4.

Remaining issues on PUSCH repetition type B
The following agreement has been made at RAN1#120bis meeting [4].

A remaining issue is how to handle power control when nominal repetition is segmented around boundary of SBFD symbols. According to TS38.213, PUSCH power control is per nominal repetition. However, when PUSCH repetition type B was applied with Configuration 2, two actual repetitions in SBFD symbols and non-SBFD symbols originating from the single nominal repetition must use the same power control, which is not aligned with the previous agreement. In SBFD, power control should be separately performed in SBFD and non-SBFD symbols. Therefore, we propose to further study how to handle the case of PUSCH repetition B with Configuration 2.
Proposal 9: Further study whether and how to handle PUSCH power control for two actual repetitions in SBFD symbols and non-SBFD symbols originating from the single nominal repetition in Configuration 2.
Dual connectivity
RAN1 has received a LS from RAN2 on simultaneous configuration of SBFD and DC [6]. The question is copied below.

From RAN1 perspective, there is no issues on the simultaneous configuration of SBFD and DC. Most of the DC procedures are transparent to the RAN1 specifications. Power control is an exception where some power sharing mechanisms are supported for DC, in which UE Tx power is shared among two cell groups when the UL/flexible symbols of the two cell groups overlap in time. For determination of symbol overlap, the UE refers to semi-static TDD UL/DL configuration. On the other hand, in Rel-19 SBFD, if simultaneous configuration of SBFD and DC is provided, symbols with UL sub-band on semi-static DL symbols should be treated like flexible symbols since uplink transmissions may happen in the UL sub-band. However, we don’t think this minor change would prevent us from supporting simultaneous configuration of SBFD and DC.
On the other hand, in RAN1#120 meeting, RAN1 agreed support for simultaneous configuration of SBFD and CA [7].

As in the agreement, RAN1 agreed to limit the number of SBFD carriers to one in multi-carrier scenario. Therefore, it is suggested to apply the same limitation for DC, i.e., support SBFD operation on one carrier in DC scenario.
In our view, SBFD can support all the DC options (i.e., EN-DC, NE-DC, and NR-DC) since there is no reasons to restrict the options from RAN1 perspective.
Proposal 10: Support SBFD operation on one carrier in EN-DC, NE-DC, and NR-DC.
As discussed above, to support simultaneous configuration of SBFD and DC, UE Tx power sharing mechanism should be modified to make sure power sharing applies to UL sub-bands. That is, the UE should share the Tx power among two cell groups when a SBFD symbol of one cell group overlaps in time with another UL/flexible/SBFD symbol of the other cell group.
On the other hand, the changes are only for NE-DC and NR-DC since in EN-DC, LTE PCG is prioritized irrespective of NR SCG TDD pattern. Therefore, we have the following proposals with TP.
Proposal 11: For NE-DC and NR-DC, the UE should share the Tx power among two cell groups when a SBFD symbol of one cell group overlaps in time with another UL/flexible/SBFD symbol of the other cell group.
Proposal 12: Adopt the following TP#5.
 

Conclusion
In this contribution, we have the following observations:
Observation 1: No specification change is necessary in the order of collision resolution specified in Section 11.1 of TS38.213 and SBFD specific collision resolution.
In this contribution, we have the following proposals:
Proposal 1: The modulation symbols are mapped avoiding (or rate-matched around) the assigned PRBs outside of the DL sub-band(s) not used for PDSCH reception in SBFD symbols.
Proposal 2: Adopt the following TP#1.
Proposal 3: The modulation symbols are mapped avoiding (or rate-matched around) the assigned PRBs outside of the UL sub-band not used for PUSCH transmission in SBFD symbols.
Proposal 4: Adopt the following TP#2.
Proposal 5: At least when transform precoding is enabled, the assigned PRBs outside of the UL sub-band should be excluded from the scheduled bandwidth before PT-RS mapping determination.
Proposal 6: Clarify the collision handling order as follows:
Step 1: Perform UCI multiplexing
Step 2: Resolve collision handling specified in Section 11.1 of TS38.213 as well as SBFD specific collision handling
Proposal 7: Adopt the following TP#3.
Proposal 8: Adopt the following TP#4.
Proposal 9: Further study whether and how to handle PUSCH power control for two actual repetitions in SBFD symbols and non-SBFD symbols originating from the single nominal repetition in Configuration 2.
Proposal 10: Support SBFD operation on one carrier in EN-DC, NE-DC, and NR-DC.
Proposal 11: For NE-DC and NR-DC, the UE should share the Tx power among two cell groups when a SBFD symbol of one cell group overlaps in time with another UL/flexible/SBFD symbol of the other cell group.
Proposal 12: Adopt the following TP#5.
References
R1-2503480, Introduction of evolution of NR duplex operation: Sub-band full duplex (SBFD), Nokia, May 2025
R1-2503455, Introduction of sub-band full duplex (SBFD), Ericsson, May 2025
R1-2501340, Summary #3 of SBFD TX/RX/measurement procedures	Moderator (Xiaomi), February 2025
RAM1 chairman’s note at RAN1#120bis meeting, April 2025
R1-2503169, Introduction of evolution of NR duplex operation: Sub-band full duplex (SBFD), Samsung, May 2025
R1-2503615, LS on simultaneous configuration of SBFD and DC, RAN2, May 2025
RAM1 chairman’s note at RAN1#120 meeting, February 2025

TDoc file conclusion not found

3GPP TSG RAN WG1 #121			R1-2504498
St Julian’s, Malta, May 19th – 23th, 2025

Source:	NTT DOCOMO, INC.
Title:	Discussion on SBFD TX/RX/measurement procedures
Agenda Item:	9.3.1
Document for: 	Discussion and Decision

Conclusion
In this contribution, we discussed enhancements for SBFD TX/RX/measurement procedures. We have the following observations and proposals:
Proposal 1: UE doesn’t expect any non-SBFD DL symbol between SBFD symbols and UL symbols within a TDD pattern period.
Proposal 2: For cell-specific configuration of SBFD subband locations for SCSs in SpecificCarrierList, following restrictions are considered:
UE doesn’t expect UL subband configured for any SCS to overlap with DL subband configured for any SCS.
UL subbands configured for SCSs should be contiguous from carrier bandwidth perspective.
Whether/how to allow unaligned DL subband boundary among SCSs and whether/how to allow unaligned UL subband boundary among SCSs should also be discussed.

Proposal 3: For CSI report based on CSI-RS on SBFD symbols: 
CSI reporting subband interpretation is based on DL BWP size.
A CSI reporting subband fully overlapping with PRB outside DL usable PRBs is not expected. 

Proposal 4: For configuration 1, for valid symbol type determination for semi-statically configured transmissions/receptions without activation DCI, 
if the valid symbol type configuration is not provided, default valid symbol type is determined as “non-SBFD”.

Proposal 5: For configuration 1:
For multi-PDSCH scheduled by single DCI:
The indicated HP ID is applied to the first PDSCH not overlapping with UL symbol.
HP ID is incremented by 1 for each subsequent PDSCH in valid symbol type and not overlapping with UL symbol.
For multi-PUSCH scheduled by single DCI:
The indicated HP ID is applied to the first PUSCH not overlapping with non-SBFD DL symbol or SSB symbol
HP ID is incremented by 1 for each subsequent PUSCH in valid symbol type and not overlapping with non-SBFD DL symbol or SSB symbol.
For multi-PUSCH CG:
HP ID is incremented by 1 for each subsequent configured grant PUSCH in valid symbol type and not overlapping with non-SBFD DL symbol or SSB symbol.

Proposal 6: For configuration 1, for type 1 HARQ-ACK feedback for multi-PDSCH scheduled by single DCI, if timeDomainHARQ-BundlingType1 is provided, HARQ-ACK for the multiple PDSCHs scheduled by single DCI is determined by binary AND operation of the HARQ-ACK information bits of PDSCH receptions that do not overlap with UL symbols, and not in (or overlap with) invalid symbol type.

Proposal 7: For configuration 1, for type 2 HARQ-ACK feedback for multi-PDSCH scheduled by single DCI, if nrofHARQ-BundlingGroups is provided, 
For a TBG including at least one PDSCH not overlapping with UL symbol and not overlapping with invalid symbol type, UE assumes a PDSCH overlapping with UL symbol or overlapping with invalid symbol type is correctly received.
For a TBG including only PDSCHs overlapping with UL symbol or overlapping with invalid symbol type, UE generates NACK value for the TBG.
The number of TBGs including at least one PDSCH not overlapping with UL symbol and not overlapping with invalid symbol type is used to determine PUCCH transmission power.

Proposal 8: For configuration 1, the SPS PDSCH collision handling procedure is applied after excluding SPS PDSCH in the invalid symbol type.

Proposal 9: For configuration 1, for SPS HARQ-ACK codebook construction, SPS PDSCHs not received due to overlapping with invalid symbol type are not included.

Proposal 10: 
For configuration 2 and frequency resource allocation Type 0, if PDSCH occasions of SPS PDSCH, PDSCH repetitions, multi-PDSCH scheduled by a single DCI, are in SBFD symbols only,
When an assigned RBG overlaps with the subband boundary, only the PRBs within DL usable PRBs are considered to be valid for PDSCH reception.
The number of PRBs for TBS determination is based on the assigned PRBs within DL usable PRBs only.
SBFD aware UE does not expect to be assigned with a RBG for PDSCH which is fully outside DL usable PRBs.
For configuration 2 and frequency resource allocation Type 1, if PDSCH occasions of SPS PDSCH, PDSCH repetitions, multi-PDSCH scheduled by a single DCI, are in SBFD symbols only,
Only the assigned PRBs within DL usable PRBs are considered to be valid for PDSCH.
Assigned PRBs that fall outside DL usable PRBs are considered to be invalid and should not be used for PDSCH resource mapping.
Existing RB indexing and VRB-to-PRB mapping are reused.
The number of PRBs for TBS determination is based on the assigned PRBs within DL usable PRBs only.

Proposal 11: When configuration 2 is provided, for PUCCH occasions (e.g. P/SP PUCCH, PUCCH repetitions) across SBFD symbols and non-SBFD symbols:
If separate frequency configurations for SBFD and non-SBFD are provided, corresponding parameter configurations are applied for PUCCH or PUCCH repetitions in SBFD symbols and non-SBFD symbols respectively.
If separate frequency configuration for SBFD is not provided, the frequency configuration for non-SBFD symbols is applied for PUCCH occasion in SBFD symbols.
For P/SP PUCCH (e.g. SR PUCCH, P/SP CSI PUCCH), if a PUCCH in SBFD symbols overlap with RB outside UL usable PRBs, the PUCCH is dropped.
For PUCCH repetitions, if a PUCCH repetition in SBFD symbols overlaps with RB outside UL usable PRBs, the PUCCH repetition is postponed.

Proposal 12: For half duplex CA directional collision handling with one SBFD cell, the legacy rule is reused with considering SBFD symbol as flexible symbol.

Proposal 13: For PUSCH repetition type B:
A non-SBFD symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is considered as an invalid symbol.
A SBFD symbol that is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is considered as a valid symbol.
Only actual repetitions in the valid symbol type with more than 1 symbol are transmitted.
If configuration 2 is provided, actual repetitions with more than 1 symbol are transmitted.

Proposal 14: If SPS HARQ-ACK deferring is enabled,
SPS HARQ-ACK is deterred if the determined SPS HARQ-ACK PUCCH resource overlaps with non-SBFD DL symbol or SSB symbol, or if it overlaps with RB outside UL usable PRBs in SBFD symbols.  
The target slot for deferring is the first slot in which the determined PUCCH resource is not overlapping with non-SBFD DL symbol or SSB symbol and not overlapping with RB outside UL usable PRBs in SBFD symbols.

Proposal 15: For UL cancellation DCI format 2_4, the  symbols are determined excluding non-SBFD DL symbols and SSB symbols.

TDoc file reading error

TDoc file reading error

3GPP TSG RAN WG1 #121                                                                  R1-2504582
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item:		9.3.1
Source: 		Google
Title:			Discussion on SBFD TX/RX/measurement procedures
Document for: 	Discussion and Decision

Conclusion
Observation 1: With no agreement on the order between UCI multiplexing procedures and collision handling rules, SBFD specific collision handling will be applied after UE resolving PUCCH/PUSCH overlapping transmissions according to the existing specifications.
Observation 2: If a UE already has sufficient UL resources from TDD CA, there is no need to configure SBFD to the UE.

3GPP TSG RAN WG1 #121		                                              R1-2504593
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Moderator (Xiaomi)
Title:	Summary #1 of 	SBFD TX/RX/measurement procedures
Agenda Item:	9.3.1
Document for:	Discussion and Decision

Conclusion
For SPS HARQ-ACK transmission when Configuration 1 is configured for the UL BWP, the symbol type can be different for different PUCCH transmission occasions.

Agreement
For PUCCH repetition, PUSCH repetition with available counting and TBoMS with Configuration 1,
In case the valid symbol type is SBFD symbol, a slot is determined as available if the symbols allocated for PUCCH/PUSCH in the slot are all SBFD symbols and not include a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.
In case the valid symbol type is non-SBFD symbol, a slot is determined as available if the symbols allocated for PUCCH/PUSCH in the slot are all non-SBFD symbols and not include a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated if provided or a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.

Agreement
For PUCCH repetition, PUSCH repetition with available counting and TBoMS with Configuration 2, a slot is determined as available if 
the symbols allocated for PUCCH/PUSCH in the slot are all SBFD symbols and not include a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst, or
the symbols allocated for PUCCH/PUSCH in the slot are all non-SBFD symbols and not include a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated if provided or a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.

R1-2502799	Summary #2 of SBFD TX/RX/measurement procedures	Moderator (Xiaomi)

Agreement
For PUSCH repetition type B, adopt Option 1.
Option 1: A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols. 

Agreement
For PUSCH repetition Type B with Configuration 1:
Alt 2:
For type 2 CG PUSCH, the valid symbol type for type 2 CG PUSCH is determined based on the symbol type of the first actual repetition associated with activation DCI.
For dynamically scheduled PUSCH, the valid symbol type is determined based on the symbol type of the first actual repetition occasion indicated by scheduling DCI.
FFS: UE drops an actual repetition if the actual repetition is in the invalid symbol type.

3GPP TSG RAN WG1 #121		                                              R1-2504594
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	Moderator (Xiaomi)
Title:	Summary #2 of 	SBFD TX/RX/measurement procedures
Agenda Item:	9.3.1
Document for:	Discussion and Decision

Conclusion
For SPS HARQ-ACK transmission when Configuration 1 is configured for the UL BWP, the symbol type can be different for different PUCCH transmission occasions.

Agreement
For PUCCH repetition, PUSCH repetition with available counting and TBoMS with Configuration 1,
In case the valid symbol type is SBFD symbol, a slot is determined as available if the symbols allocated for PUCCH/PUSCH in the slot are all SBFD symbols and not include a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.
In case the valid symbol type is non-SBFD symbol, a slot is determined as available if the symbols allocated for PUCCH/PUSCH in the slot are all non-SBFD symbols and not include a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated if provided or a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.

Agreement
For PUCCH repetition, PUSCH repetition with available counting and TBoMS with Configuration 2, a slot is determined as available if 
the symbols allocated for PUCCH/PUSCH in the slot are all SBFD symbols and not include a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst, or
the symbols allocated for PUCCH/PUSCH in the slot are all non-SBFD symbols and not include a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated if provided or a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.

R1-2502799	Summary #2 of SBFD TX/RX/measurement procedures	Moderator (Xiaomi)

Agreement
For PUSCH repetition type B, adopt Option 1.
Option 1: A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols. 

Agreement
For PUSCH repetition Type B with Configuration 1:
Alt 2:
For type 2 CG PUSCH, the valid symbol type for type 2 CG PUSCH is determined based on the symbol type of the first actual repetition associated with activation DCI.
For dynamically scheduled PUSCH, the valid symbol type is determined based on the symbol type of the first actual repetition occasion indicated by scheduling DCI.
FFS: UE drops an actual repetition if the actual repetition is in the invalid symbol type.

3GPP TSG RAN WG1 #121                                           	    R1-2504598
Malta, MT, 19th –23rd, May, 2025

Source: 	CEWiT
Title:	Discussion on SBFD TX/RX/measurement procedures
Agenda Item:	9.3.1
Document for:	Discussion and Decision



1.

Conclusion
The following observations and proposals are made in the contribution:
Observation 1: For SBFD scenario, keeping the legacy definition of valid DL slot can result in non-availability of valid downlink slot for the CSI reference resource and unnecessary dropping of the CSI report.
Proposal 1: If the valid symbol type for CSI derivation for periodic/semi-persistent CSI-RS resources for the CSI report is configured, the CSI reference resource for the CSI report is defined as follows:

A slot comprises at least one higher layer configured downlink or flexible symbol
A slot comprises at least one symbol with the same symbol type as the configured valid symbol type for CSI derivation; and
The slot does not fall within a configured measurement gap for that UE.

Observation 2: In case of configuring separate CSI-ReportConfig for SBFD and non-SBFD scenario, the CSI reporting criteria are associated with the valid symbol type for CSI derivation.

Proposal 2: In case of configuring valid symbol type for CSI derivation, UE reporting CSI only if it receives at least one CSI-RS resource, in valid symbol type for CSI derivation, before the CSI Reference resource is supported.

Proposal 3: In case of configuring valid symbol type for CSI derivation and timeRestrictionForChannelMeasurements or timeRestrictionForInterferenceMeasurements, UE deriving the CSI parameter based on the most recent CSI-RS occasion, in valid symbol type and no later than the CSI reference resource, is supported.

Proposal 4: Defining priority rule for CSI report comprising CSI parameters associated with SBFD and non-SBFD scenario is supported.

Observation 3: CSI reports comprising CSI parameters for SBFD scenario should be prioritized over non-SBFD scenario because 
SBFD operation is more sensitive to interference and requires precise CSI for effective link adaptation and interference management. 
Ensures simultaneous UL and DL transmission/reception under limited UL resources.
CSI measurement is the only option to get channel state information corresponding to SBFD scenario, as the SBFD scenario is not applicable for SSB symbols.
Proposal 5: Prioritizing CSI parameters for SBFD scenarios over non-SBFD scenario for Part 1 CSI Report and for each category in part 2 CSI Report is supported.

4. 

3GPP TSG RAN WG1 Meeting #121	R1-2504609
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.3.1
Source:	Ericsson
Title:	SBFD Tx/Rx/measurement procedures
Document for:	Discussion, Decision

Conclusion
In the previous sections we made the following observations: 
Observation 1	The SBFD frequency configuration needs to be area-specific for interference reasons.
Observation 2	Because the WID does not include new UE RF requirements for SBFD-aware UEs, they cannot be expected to have improved spectral filtering capabilities and thus there is no benefit with UE-specific guard bands.
Observation 3	Since random access in RRC_IDLE is supported, a UE performing subband filtering needs to support the cell-specific guard band configuration.
Observation 4	Limitations in SSB placement and associated CORESET 0 placement cause any further narrowing of a DL subband to be infeasible.
Observation 5	UE-to-UE CLI can mostly be avoided by scheduling.
Observation 6	For interference reasons, it would be beneficial to separate DL and UL spectrum in the intersection between DL and SBFD symbols, i.e., to introduce a guard band in the first symbol(s) of the UL subband.
Observation 7	Configuring SSB slots as DL would result in severe intercell interference in resources in networks without collocated SSBs.
Observation 8	A possible support for link direction does not change the prioritization for Case 6.
Observation 9	Following the collision formulations of the current spec, there is no need for a collisions resolution order between collision Case 5 and other collisions cases.
Observation 10	For collision Case 6, there is no ambiguity in the collision management to be resolved by specifying a collision resolution order.
Observation 11	The spec [TS 38.213, §9.2.2] already covers the case where HARQ-ACK is transmitted either in PUSCH or in PUCCH for the case where the PUSCH is down-prioritized with respect to a DL transmission.
Observation 12	For closed-loop power control, the gNB can decide to use identical or distinct closed-loop processes for SBFD and non-SBFD symbols by providing the same or different closed-loop indexes for the corresponding pair of p0AlphaSet values, as long as the total number of power control loops does not exceed two in any application scenario, whether in a single TRP or multi-TRP context.
Observation 13	When unified TCI state is not configured to the UE, it is not necessary to introduce any enhancements for power control in SRS transmission, since the current specification already allows specific configuration of power control parameters for each SRS resource set.
Observation 14	The existing specifications for CORESET and search space configuration are sufficiently flexible to support SBFD operation.
Observation 15	If SBFD is supported in combination with intraband CA or interband CA for UEs not supporting SimultaneousRxTxInterBandCA  then RAN1 needs to specify prioritization rules between DL and UL operation among different carriers.
Observation 16	The only beneficial and technically feasible combination of SBFD and CA would be interband CA in combination with UEs capable of SimultaneousRxTxInterBandCA for that band combination.
Observation 17	The benefit of supporting SBFD in a CA scenario is significantly limited.
Observation 18	CA has RAN2 and RAN4 specification impact, e.g., signaling and activation requirements, that will be difficult to finalize in Rel-19.

Based on the discussion in the previous sections we propose the following:
Proposal 1	No UE-specific frequency configuration of SBFD symbols is supported.
Proposal 2	Introduce a guard subband in the first symbol(s) of the UL subband. FFS: guard subband duration.
Proposal 3	RAN1 will not introduce specific functionality for enabling non-SBFD DL symbols inbetween SBFD and UL symbols.
Proposal 4	For collision Case 3 (with semi-statically configured DL Rx vs. semi-statically configured UL Tx with repetitions), the same collision handling rules and timeline for DL receptions and UL transmissions without repetitions are applied for each repetition.
Proposal 5	Confirm WA on SSB symbols configured with SBFD subbands are SBFD.
Proposal 6	To resolve any ambiguity while determining invalid symbol(s) after segmenting a nominal repetition into into actual repetitions around boundary of SBFD symbols and non-SBFD symbols for PUSCH repetition type B, higher layer parameters are to be introduced to indicate to the UE the number of invalid symbols resulting from transitions from DL to SBFD symbols and from SBFD to UL symbols.
Proposal 7	Introduce a second set of p0AlphaSet values to Uplink-PowerControl associated with a Joint or UL TCI state to allow separate UL power control parameters for transmission in SBFD and non-SBFD symbols associated with the TCI state.
Proposal 8	The second set of p0AlphaSet values in the Uplink-PowerControl IE is optional. If the second set of p0AlphaSet values are not provided, uplink power control should be performed according to the parameters specified in the first (legacy) set of p0AlphaSet values in both SBFD and non-SBFD symbols.
Proposal 9	For a single TRP scenario, when unified TCI state is not configured to the UE, for separate UL power control for PUSCH/PUCCH/SRS transmissions in SBFD symbols and non-SBFD symbols, support same spatial relation info associated with separate UL power control parameters for SBFD symbols and non-SBFD symbols.
Proposal 10	When the UE is not configured with unified TCI state, for PUSCH transmission across SBFD and non-SBFD symbols in multiple slots, a second sri-P0-PUSCH-AlphaSetId and a second sri-PUSCH-ClosedLoopIndex are introduced in SRI-PUSCH-PowerControl. The first set of the parameters is used for PUSCH transmission in non-SBFD symbols and the second for PUSCH transmission in SBFD symbols. If the second set of the parameters are absent, uplink power control should be performed according to the first (legacy) set of the parameters in both SBFD and non-SBFD symbols.
Proposal 11	When unified TCI state is not configured to the UE, for PUCCH transmission across SBFD and non-SBFD symbols in multiple slots, a second set of power control parameters are introduced in PUCCH-SpatialRelationInfo. The first set of the parameters is used for PUSCH transmission in non-SBFD symbols and the second for PUSCH transmission in SBFD symbols. If the second set of the parameters are absent, uplink power control should be performed according to the first (legacy) set of the parameters in both SBFD and non-SBFD symbols.
Proposal 12	RAN1 shall not pursue further PDCCH enhancements other than facilitating SBFD-aware UEs to skip evaluating PDCCH candidates mapped to one or more REs that overlap with REs outside DL subband(s).
Proposal 13	For a SBFD-aware UE, RAN1 to conclude that Configuration 2 reception, i.e., reception in both symbols types for CSI-RS is default capability.
Proposal 14	For CSI report associated with aperiodic CSI-RS, valid symbol type for CSI derivation is determined based on symbol type of the CSI-RS reception, indicated in DCI via CSI-RS slot offset.
Proposal 15	If the resources indicated for use for PUCCH in an SBFD symbol are not entirely within the UL subband, the transmission is dropped.
Proposal 16	Two slot repetition counters, one for SBFD slots and one for non-SBFD slots, should be used for PUCCH inter-slot frequency hopping to ensure optimal frequency resource allocation across the slots.
Proposal 17	Starting PRB of first hop for PUSCH repetitions/transmissions with frequency hopping RB_start^SBFD is determined based on same formula as agreed for starting PRB of PUSCH repetitions/transmissions without frequency hopping, i.e., Equation 1-C2: RB_start^SBFD = RB_start^ULSB + mod(RB_start^non-SBFD + RB_offset^SBFD, N_ULSB^size), where if RB_offset^SBFD is not configured, it is zero.
Proposal 18	SBFD is not supported in a multi-carrier scenario from a UE perspective.
Proposal 19	Clarify the RAN1 agreement on SBFD operation in a multi-carrier scenario:
Support gNB SBFD operation on one TDD carrier in multi-carrier scenario.

3GPP TSG RAN WG1 #121			R1-2504615
St. Julians, Malta, May 19th – 23rd, 2025

Source:	WILUS Inc.
Title:	Discussion on SBFD TX/RX/measurement procedures
Agenda item:	9.3.1
Document for:	Discussion

Conclusion
In this contribution, we discussed issues such as semi-static configuration of SBFD subbands, UE transmission/reception/measurement behavior and procedures in SBFD symbols and/or non-SBFD symbols for SBFD aware UE for SBFD operation and summarize our views as the followings:
Proposal 1: We propose to confirm the working assumption that cell-specific configuration on frequency location of SBFD subbands is supported within a TDD carrier.
UE-specific configuration on frequency locations of SBFD subbands is not supported.
Proposal 2: PUSCH transmissions of PUSCH repetition or TB processing over multiple slots, or PUCCH transmissions of PUCCH repetition within UL subband across SBFD slots or symbols configured as DL by tdd-UL-DL-ConfigCommon should not be an event which causes power consistency and phase continuity not to be maintained for actual TDW determination for a SBFD-aware UE.
Proposal 3: If separate UL power control parameters are applied across SBFD and non-SBFD symbols for Configuration 2, it should be considered as an event which causes power consistency and phase continuity not to be maintained and different actual TDWs for different symbol types should be determined for PUSCH transmissions of PUSCH repetition or PUCCH transmissions of PUCCH repetition.
Proposal 4: In addition to availability in time domain, availability in frequency domain should be further considered when determining the HPN for multi-slot PUSCHs scheduled by a single DCI for an SBFD-aware UE with Configuration 2.
The HPN of allocated PUSCH should be incremented if its allocated frequency resources are within the UL usable PRBs on SBFD symbols regardless of the symbol type of the allocated PUSCH is configured as DL or Flexible symbols, as indicated by tdd-UL-DL-ConfigCommon or tdd-UL-DL-ConfigDedicated.
The HPN of allocated PUSCH should not be incremented for a PUSCH that is not transmitted due to a collision between SSB symbols indexed by ssb-PositionsInBurst and one of multiple PUSCHs on SBFD symbols in the time domain.
Proposal 5: For each scheduling case of multi-slot PUSCHs by a single DCI and multi-slot PDSCHs by a single DCI with Configuration 1, the rule for HARQ process ID allocation should be revised for a SBFD-aware UE differently to the current specification.
When the first reception occasion indicated by the DCI is on SBFD symbols,
In case of multi-slot PDSCHs scheduling, the UE should not increment the HPN for any PDSCH(s) that is not received on non-SBFD DL symbols (i.e. legacy DL symbols).
In case of multi-slot PUSCHs scheduling, the UE should not increment the HPN for any PUSCH(s) that is not transmitted on non-SBFD UL symbols (i.e. legacy UL symbols) or on any symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.
When the first reception occasion indicated by the DCI is on non-SBFD symbols,
In case of multi-slot PDSCHs scheduling, the UE should not increment the HPN for any PDSCH(s) that is not received if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with an SBFD symbol.
In case of multi-slot PUSCHs scheduling, the UE should not increment the HPN for any PUSCH(s) that is not transmitted if at least one of the symbols indicated by the indexed row of the used resource allocation table in the slot overlaps with an SBFD symbol or a symbol of an SS/PBCH block with index provided by ssb-PositionsInBurst.
Proposal 6: For a SBFD-aware UE, RE-level PUSCH scheduled within UL subband in a symbol configured as DL via TDD-UL-DL-ConfigCommon 
can be rate-matched around REs of LTE CRS configured for LTE UE in case of spectrum sharing between SBFD-aware UE and LTE UE.
can be rate-matched around REs of ZP CSI-RS configured for other NR UE.
Proposal 7: For a SBFD-aware UE, we propose that 
Both non-SBFD symbols configured as DL by TDD-UL-DL-ConfigCommon and symbols configured for SSB reception are excluded as reference time-frequency resource region for UL CI,  
And an UL subband in both symbols configured as DL by TDD-UL-DL-ConfigCommon and symbols (i.e., DL or Flexible symbols) not configured for SSB reception should be included as reference time-frequency resource region for UL CI in addition to UL symbols and flexible symbols not configured for SSB reception.
Proposal 8 : RAN1 should further discuss how to indicate cancellation of uplink signals/channels scheduled in the UL subband to SBFD-aware UEs using DCI format 2_4 as group common signalling without impacting the existing operation of legacy UEs.

3GPP TSG RAN WG1 #121	        		R1-2504626
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item: 	9.3.1
Source: 	Sony 
Title: 	SBFD procedures
Document for: 	Discussion / decision

Conclusion
In this contribution, we discuss some operations issues on SBFD, and we observe the following:
Observation1: The gNB should be able to configure one or two CSI-ReportConfig with separate CSI measurements, where one CSI measurement is derived from CSI-RS in SBFD symbols and another CSI measurement is derived from CSI-RS in non-SBFD symbols.
Observation 2: For repetitive and periodic transmissions/receptions across SBFD and non-SBFD OFDM symbols, the QCL assumption may be different for SBFD OFDM symbols and non-SBFD OFDM symbols.


We therefore propose the following:
Proposal 1: The transient period between SBFD and non-SBFD OFDM symbols is implicitly indicated via gNB scheduling.

Proposal 2: The gNB can configure the following CSI report for SBFD UE:
Configuration A: For separate CSI reports on SBFD and non-SBFD, one CSI-ReportConfig is associated with CSI-RS(s) restricted to SBFD symbols only and the second CSI-ReportConfig is associated with CSI-RS(s) restricted to non-SBFD symbols only.
Configuration B: Enhance Rel-18 NES CSI reporting framework to support one CSI-ReportConfig with one sub-configuration associated with SBFD symbols and the other sub-configuration associated with non-SBFD symbols

Proposal 3: Support different TCI state indications for transmissions in SBFD and non-SBFD OFDM symbols.

3GPP TSG-RAN WG1 Meeting #121	R1-2504857
St Julian's, Malta, 19 - 23 May, 2025

Title:	Draft reply LS on simultaneous configuration of SBFD and DC
Response to:	R2-2503191
Release:	Rel-19
Work Item:	NR_duplex_evo-Core

Source:	Xiaomi
To:	RAN2
Cc:	RAN3, RAN4

Contact person:			Yanping Xing
			xingyanping@xiaomi.com
	
Send any reply LS to:	3GPP Liaisons Coordinator, mailto:3GPPLiaison@etsi.org

Attachments:	-

1	Overall description
RAN1 would like to thank RAN2 for the LS on simultaneous configuration of SBFD and DC in R2-2503191. 
For the question on whether SBFD and DC can be configured simultaneously, and whether there is any issue with such configuration for an SBFD-aware UE, RAN1 made the following conclusion.
Conclusion: 
From RAN1 perspective, considering the specification impact, SBFD and NR-DC can be configured simultaneously only for inter-band NR-DC if a UE is capable of simultaneous transmission and reception indicated by UE capability simultaneousRxTxInterBandCA, where SBFD operation is applicable on only one NR TDD carrier.
Inform RAN2 that specification impact to support this feature is not restricted to RAN1 but will result in specification impact on RAN4 as well. If supported, at least the following specification change to TS 38.213 should be adopted and the RAN4 specification for the configured transmitted power level for NR-DC in TS38.101-1 Clause 6.2B.4.1 may also need to be updated accordingly.
It is up to RAN2 to decide whether or not to support simultaneous configuration of SBFD and DC. 
CC: RAN3 and RAN4.

2	Actions
To RAN2:
ACTION: 	RAN1 respectfully asks RAN2 to take the above conclusion into account.
3	Dates of next TSG RAN WG1 meetings
TSG RAN1 Meeting #122			25 - 29 Aug 2025					Bangalore, India
TSG RAN1 Meeting #122bis		13 - 17 Oct 2025					Prague, CZ

TDoc file conclusion not found