TDoc file unavailable

3GPP TSG RAN WG1 #120bis			R1-2501752
Wuhan, China, April 7th – 11th, 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: Determine the configuration method of SBFD symbol location in a way that prevents UL symbols configured by TDD-UL-DL-ConfigCommon from being designated as SBFD symbols.
Proposal 2: For the starting slot/symbol and/or the ending slot/symbol of SBFD symbols within TDD-UL-DL pattern period,
The reference position for indicating the starting slot of the SBFD symbols is the starting slot of the TDD-UL-DL pattern period. If 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.
The reference position for indicating the ending slot of the SBFD symbols is the slot where the last symbol among the DL or Flexible symbols configured by TDD-UL-DL-ConfigCommon is contained. If 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 3: Explicitly configure a guard period for the transition from non-SBFD to SBFD symbol and the related behavior of an SBFD-aware UE.

1.2) Semi-static indication of frequency location of SBFD subbands
Proposal 4:  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 5: 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 6: For PUSCH repetition type B, if a particular nominal repetition contains SBFD and non-SBFD symbols, divide the actual repetition based on the boundary between SBFD symbol and non-SBFD symbol.
In case Configuration 1, OFDM symbols in SBFD symbols only or OFDM symbols in non-SBFD symbols can be determined as valid for actual repetition. Support option 2 (i.e., A nominal repetition is segmented into actual repetitions as in legacy operation. An actual repetition mapped to both SBFD and non-SBFD symbols is dropped.)
In case Configuration 2, both OFDM symbols in SBFD symbols only or OFDM symbols in non-SBFD symbols can be determined as valid for actual repetition. Support option 1 (i.e., A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols.)

2.2) Resource allocation in frequency domain in SBFD symbols
Proposal 7: For frequency resource allocation Type 1 for PUSCH in a single slot by DCI based scheduling (without repetition or TBoMS), when an assigned RBG overlaps with the subband boundary,
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 a RBG for PUSCH which is fully outside UL usable PRBs.
The number of PRBs for TBS determination is based on the assigned PRBs within UL usable PRBs only for PDSCH and PUSCH respectively.

2.3) Physical channels/signals and procedure across SBFD and non-SBFD symbols
Proposal 8: 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 9: A single PRI in DCI can be used to indicate PRI for SBFD symbol and non-SBFD symbol. The starting PRB and second hop PRB for the PRI indicated by DCI can then be applied with values corresponding to the symbol type, i.e., non-SBFD symbols and SBFD symbols, respectively.
Proposal 10: When no separate configuration of starting PRB and second hop PRB for SBFD symbol is provided, PUCCH transmissions for this pucch-ResourceId is not expected in SBFD symbols.

Proposal 11: 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 12: 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 

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

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

Conclusion
There is no RAN1 consensus to support semi-static link direction indication for SBFD aware UEs.
For a serving cell configured with SBFD subband time and frequency location, for an SBFD aware UE, TDD-UL-DL-ConfigDedicated is only applicable to non-SBFD symbols but not applicable to SBFD symbols

Resource allocation in frequency domain

UL transmissions and DL receptions across SBFD symbols and non-SBFD symbols
Provision of configurations
Applicable range
Agreement
The configuration of Configuration 1 or 2 for DL BWP only applies to PDSCH receptions within the DL BWP.

Details for Configuration 1
Determination of valid symbol type
Agreement
For a CSI report associated with periodic/semi-persistent CSI-RS, the valid symbol type for CSI derivation is configured in CSI-ReportConfig.

Agreement
For Configuration 1: The transmissions/receptions are restricted to SBFD symbols only or non-SBFD symbols only,
The valid symbol type for PUSCH carrying SP-CSI is determined based on the symbol type of the first PUSCH occasion associated with activation DCI.
For SP-CSI on PUCCH:
Option 2: the valid symbol type for PUCCH carrying SP-CSI is configured in semiPersistentOnPUCCH in CSI-ReportConfig.

Agreement
For Configuration 1: The transmissions/receptions are restricted to SBFD symbols only or non-SBFD symbols only,
The valid symbol type for Type 1 CG PUSCH is configured in rrc-ConfiguredUplinkGrant in ConfiguredGrantConfig.
The valid symbol type for PUCCH configured for SR is configured in SchedulingRequestResourceConfig.
The valid symbol type for PUCCH carrying P-CSI is configured in periodic in CSI-ReportConfig.

Details for Configuration 2
Configuration of RB offset for PUSCH
Agreement
For determining starting PRB for PUSCH transmissions in SBFD symbols for Configuration 2, 
For type 1 CG PUSCH, a  is configured in rrc-ConfiguredUplinkGrant in ConfiguredGrantConfig.
For type 2 CG PUSCH and DG PUSCH, a  is configured per UL BWP in PUSCH-Config.
The is commonly applicable to all DCI formats which schedule PUSCH
Ifis not configured, it is assumed to be zero

TB size determination for PDSCH
Agreement
For SPS PDSCH with Configuration 2, for TBS determination, 
For SPS PDSCH without repetition, 
The number of PRBs for TBS determination for an SPS PDSCH in SBFD symbols is based on assigned PRBs within DL usable PRBs only. 
The number of PRBs for TBS determination for an SPS PDSCH in non-SBFD symbols is based on assigned PRBs.
For SPS PDSCH with repetition, TBS is determined based on the first repetition occasion.
If the first repetition occasion of a SPS PDSCH is in SBFD symbols, the number of PRBs for TBS determination for the SPS PDSCH is based on assigned PRBs within DL usable PRBs only.
If the first repetition occasion of a SPS PDSCH is in non-SBFD symbols, the number of PRBs for TBS determination for the SPS PDSCH is based on assigned PRBs.

Separate configurations
Frequency hopping for PUSCH
Agreement
For a type 1 CG PUSCH with Configuration 2, if FH offset for SBFD symbols is not configured for the type 1 CG PUSCH, frequency hopping is disabled for the type 1 CG PUSCH transmissions in SBFD symbols.
For a type 2 CG PUSCH/PUSCH scheduled by DCI, if FH offset lists for SBFD symbols are not configured for the type 2 CG PUSCH/PUSCH scheduled by DCI, frequency hopping is disabled for the transmission of the type 2 CG PUSCH/PUSCH scheduled by DCI in SBFD symbols.

PUCCH
Agreement
If starting PRB is not configured for SBFD symbols for a PUCCH-Resource, starting PRB configured for non-SBFD symbols for the PUCCH-Resource is used for PUCCH transmissions in SBFD symbols associated with this pucch-ResourceId.

Agreement
The one configuration of intraSlotFrequencyHopping for a PUCCH-Resource is applied to both PUCCH transmissions in SBFD symbols and in non-SBFD symbols associated with this pucch-ResourceId.

SRS
Agreement
For aperiodic SRS with available slot counting, 
For SRS-ResourceSet configured for SBFD symbol, an available slot is a slot satisfying there are SBFD symbol(s) for the time-domain location(s) for all the SRS resources in the resource set and it satisfies UE capability on the minimum timing requirement between triggering PDCCH and all the SRS resources in the resource set.
For SRS-ResourceSet configured for non-SBFD symbol, an available slot is a slot satisfying there are UL or flexible symbol(s) not configured as SBFD symbols for the time-domain location(s) for all the SRS resources in the resource set and it satisfies UE capability on the minimum timing requirement between triggering PDCCH and all the SRS resources in the resource set.

Agreement
When higher layer parameter ul-FullPowerTransmission is set to 'fullpowerMode2', the numbers of SRS ports should be the same for SRS resources with the same corresponding SRI values in the two SRS resource sets associated with SBFD and non-SBFD symbols.

Collision handling

3GPP TSG RAN WG1 Meeting #120bis	                                                                      R1-2501843
Wuhan, China, April 7th –April 11th 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, FH and UL power control parameters for SRS, PUCCH, and PUSCH in SBFD and non-SBFD symbols, and physical channel mapping to SBFD and non-SBFD symbols within a slot or in different slots. 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.
Observation 3: Determining the link direction of SBFD-aware UE transmission/reception in SBFD symbols may introduce unnecessary signaling for link direction which can be achieved without signaling.
Observation 4: If DL receptions are allowed within DL usable PRBs in the SSB symbols, it will degrade the SSB detection and create new cases of collision between SSB and other DL channels/signals.
Observation 5: If an SBFD aware UE is configured with FH offset list for PUSCH for non-SBFD symbols but not configured with FH offset list for PUSCH for SBFD symbols, FH is disabled for PUSCH transmissions in SBFD symbols.
Observation 6: Option 2 is straightforward, as it uses a unified TCI state to enable separate UL power control for SBFD and non-SBFD symbols without requiring entirely separate TCI states.
Observation 7: The legacy mechanism of the unified TCI framework may not be able to indicate the association between the TCI states and the DL/UL transmission in SBFD and non-SBFD symbols.

Proposal 1: UE-specific configurations for the time and frequency locations of SBFD subbands is not supported.
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: For PUSCH repetition type B across SBFD and non-SBFD symbols within a slot, support option 1: A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols.
Proposal 4: Consider separate startingPRB and secondHopPRB within a PUCCH-resoruceId for PUCCH FH in SBFD and non-SBFD symbols.  
Proposal 5: RAN1 to Consider beam indication in unified TCI state framework.
Proposal 6: For the association between TCI states and DL/UL transmission in SBFD and non-SBFD symbols, consider the following alternatives: 
Alt1: RRC message indicates the association.
Alt 2: MAC CE indicates the association.
Alt 3: A field in DCI indicates the association.
Alt 4: Pre-define a rule about the association.

3GPP TSG RAN WG1 #120bis			R1-2501865
Wuhan, China, April 7th – 11th, 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.
For transient period in SBFD operation, it does not need to explicitly configure transient period.
The transient period should be discussed separately. 
The Option 1 is supported regardless of transient period between UL symbols and SBFD symbols is located within the SBFD slot/symbol or not.
For PUSCH repetition type B, segmentation around boundary of SBFD symbols and non-SBFD symbols is supported with either Configuration 1/2.
For Configuration 1, actual repetitions in the invalid symbol type are dropped.
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. 
Confirm the following WA without the last sub-bullet which has been solved:
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)
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 persistent SRS, periodic SRS and aperiodic SRS, the valid symbol type is explicitly configured.
Confirm the following working assumption:
For an SPS PDSCH configuration without repetitions, if the reception occasions are across SBFD symbols and non-SBFD symbols where each reception occasion has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), PDSCH repetitions 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-PDSCH scheduled by a single DCI across SBFD symbols and non-SBFD symbols, where each PDSCH within a slot has either all SBFD or all non-SBFD symbols (i.e. Configuration 2), 
Option 5: Only the assigned PRBs within DL usable PRBs in SBFD symbols are considered to be valid.
The condition to disable whether to apply 〖RB〗_SBFD^offset in SBFD symbols is PUSCH frequency resources in non-SBFD symbols is within the UL usable PRBs.
The Equation 1-C2 can be applied to RA type 1 and RA type 0.
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
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.
The red part related TPMI can be confirmed.
If separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols not applicable to usage set to ' beamManagement,  it should be clarified that whether SRS resources in SRS resources set for beam management is transmitted only in one type of symbols or not.
Separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols not applicable to usage set to ' beamManagement’.
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.
In case of SBFD operation is configured on one TDD carrier in multi-carrier scenario, directional collision handling for half-duplex TDD CA is reused.
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
Option 1 is supported:
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. 

3GPP TSG RAN WG1 #120bis	R1-2501907
Wuhan, China, April 7th – 11st, 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 within a slot, Option 1 is supported. 
Option 1: A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols. 
The transmission mechanism of PUSCH repetition type A with Configuration 2 on different symbol types across different slots is applied to each actual repetition of PUSCH repetition type B on different symbol types within a slot. 
Configuration 1 and Configuration 2 is not applicable to PUSCH repetition type B. 
Proposal 3: 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 4: 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 5: 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 6: 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 7: Confirm the following WA. 

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 Configuration 1, further clarify whether/how to determine the valid symbol type of each PUCCH occasion carrying HARQ-ACK corresponding to SPS PDSCHs. 
Proposal 10: Confirm the above working assumption for separate SRS configurations for SBFD and non-SBFD symbols.
Proposal 11: The applicable usages of separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols include 'beammanagement'.
Proposal 12: For PUSCH repetitions/TBoMS/CG PUSCH configuration in Configuration 2, select one or multiple the following options for determination of frequency resource in SBFD symbols when RA type 0 is used. 
Option 1:  Equation 1-C2 is reused to determine the minimum PRB index allocated in SBFD symbols based on the minimum PRB index among the non-contiguous PRBs allocated in non-SBFD symbols. The PUSCH occupies a number of contiguous PRBs starting from the minimum PRB index and the number of PRBs of the PUSCH does not change. 
Option 2:  If the bandwidth of UL usable PRBs is the same as the bandwidth of UL BWP, RA type 0 can be used and PRBs allocated based on FDRA are applicable to both SBFD symbols and non-SBFD symbols. Otherwise, RA type 0 is prohibited.
Proposal 13: For PDSCH with repetition or SPS PDSCH, the invalid PDSCH should not be considered in in PDSCH candidates for determination of Type 1 HARQ-ACK codebook. 
The invalid PDSCH includes at least PDSCH scheduled on invalid symbol type for Configuration 1. 
Proposal 14: The parameter maxCodeRate in PUCCH-FormatConfig should be configured separately for SBFD symbols and non-SBFD symbols.
Proposal 15: RAN1 clarifies that the SSB refers to the actual SSB transmission configured by RRC signaling “ssb-PositionsInBurst” in SIB1 in the following WA.
Proposal 16: 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 17: RAN1 needs to further discuss whether any optimization is needed for each of the Rel-16~Rel-19 features. 
RRC parameters
Proposal 18: Introduce and modify the following RRC parameters. 
 

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

Agenda Item:	9.3.1
Source:	InterDigital, Inc.
Title:	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.

3GPP TSG RAN WG1 #120bis 		R1-2501989
Wuhan, China, April 7th – 11th, 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 observations 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: For PUSCH repetition type B, if a nominal repetition is mapped to SBFD and non-SBFD symbols within a slot, the nominal repetition is segmented into actual repetitions as in legacy operation and an actual repetition mapped to both SBFD and non-SBFD symbols is dropped.
Proposal 3: For PUSCH with configuration 2, both of the following options can be considered to determine the starting PRB for PUSCH transmissions in SBFD symbols for PUSCH with RA type 0. 
Option 1: The equation to determine the starting PRB for PUSCH transmissions in SBFD symbols cannot be applied to RA type 0. gNB ensure that the allocated RBGs are inside UL usable PRBs or only the assigned PRBs within UL usable PRBs in SBFD symbols are considered to be valid.
Option 2: The equation to determine the starting PRB for PUSCH transmissions in SBFD symbols can be applied to RA type 0 without enhancements. gNB should ensure the determined  in SBFD symbols is aligned with RBG boundary.
Proposal 4: 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 5: 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 A, the valid symbol type for CSI derivation can be configured in NZP-CSI-RS-ResourceSet/NZP-CSI-RS-Resource;
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 6: For a single TRP scenario, support separate UL power control based on unified TCI state framework.
Proposal 7: 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 8: The number of values configured in availableSlotOffsetList for SBFD symbols is same as the number of values configured in availableSlotOffsetList for non-SBFD symbols.
Proposal 9: Do not introduce enhancements for SRS frequency hopping counter.
Proposal 10: Separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols does not apply for SRS resource sets with usage set to 'beamManagement'.
Proposal 11: 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 12: 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 13: For SBFD aware UEs, collision between transmissions/receptions and unusable resources is handled before intra-UE multiplexing/prioritization.
Proposal 14: For SBFD operation on one TDD carrier in multi-carrier scenario, half-duplex CA should be supported.
Proposal 15: 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.
Proposal 16: The frequency location of DL/UL subbands are configured under SCS-SpecificCarrier IE.
Proposal 17: It is up to RAN2 to decide whether to introduce a new RRC parameter to configure the valid symbol type for SRS-ResourceSet within it, or introduce a new list of SRS resource sets for SBFD.

3GPP TSG RAN WG1 #120-bis							R1-2502013
Wuhan, China, April 7th – 11th, 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 needed for the transition from non-SBFD symbols to SBFD symbols must be placed exclusively in the SBFD slots.
Proposal 2: UE specific guard band is not required in SBFD operation.
Proposal 3:  Option 1 is preferred over Option 2 as Option 1 enables optimal resource usage. 
Proposal 4: Consider switching period (SBFD to non SBFD symbols) as invalid 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.

Proposal 12: 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: Cancel the first uplink subband symbol, either by SBFD frame structure configuration, RRC configuration or by sending DCI
   Option 3: Shortening the first uplink symbol by mapping alternate subcarriers.  
 

3GPP TSG RAN WG1 #120bis			R1-2502020
Wuhan, China, April 7th – 11th, 2025
Agenda item:			9.3.1
Source:	China Telecom
Title:	Discussion 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 behavior of the case when the scheduled PUSCH for SBFD-aware UEs overlaps with the resource not available for PDSCH resource mapping is further studied by RAN1, 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: For a physical channel/signal occasion mapped to SBFD and non-SBFD symbols within a slot, if an SBFD aware UE does not transmit or receive the physical channel/signal,
For PUSCH repetition type A with available slot counting, A-SRS with available slot counting, TBoMS and PUCCH repetitions, UE postpones transmissions in the 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, transmissions/receptions in the slot are dropped.

Proposal 5: For PUSCH repetition type B, a nominal repetition mapped to SBFD and non-SBFD symbols within a slot is segmented into multiple actual repetitions around boundary of SBFD symbols and non-SBFD symbols. An actual repetition is dropped when it is of invalid symbol type for configuration 1.
Proposal 6: Further 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 and the corresponding behaviour.
Proposal 7: For PUSCH FH using configured FH interval, consider at least the support of configuring separate FH intervals for each TDD-UL-DL pattern when two TDD-UL-DL patterns are configured to reduce the kinds of the number of consecutive slots with the same PUSCH frequency location, other specification impact is FFS. 
Proposal 8: For PUCCH FH using configured FH interval, consider the FH interval counting only the UL usable slots to reduce the kinds of the number of consecutive slots 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 #120bis	R1- 2502040
Wuhan, China, April 7th – 11th, 2025

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

Conclusion
This contribution has discussed the remaining issues related to the SBFD frequency location indication, transmission, reception, and measurement behaviors. The following are our proposals: 
Proposal 1: RAN1 to conclude that there is no UE-specific indication of SBFD subband frequency location.
Proposal 2: A basic capability of a SBFD includes single DL subband and UL subband, with optional FG on two DL subbands support. 
Proposal 3: RAN1 to further consider how to support a SBFD-aware UE supporting only one downlink when a cell has D-U-D partition. 
Proposal 4: The initial BWP is configured such that it overlaps with only one downlink subband regardless of a partition type of a cell (D-U, U-D or D-U-D). 
Proposal 5: When the UE only supports U-D or D-U partitions, the UE does not expect to be configured with a dedicated BWP overlapping with more than one downlink subbands.
Proposal 6: NRB for determining PTRS frequency density and locations () is computed based on a bandwidth/number of actually transmitted PRBs that are within the usable DL PRBs and the scheduled PRBs.
Proposal 7: For Configuration 1, if a symbol type is not explicitly configured for Type 1 CG PUSCH, SR, periodic CSI PUCCH, SP-CSI PUCCH, a non-SBFD symbol type is assumed for the (semi-)periodic resource. 
Proposal 8: For Configuration 1, the UE should not expect that a valid symbol type of a resource (e.g., Type 1 CG PUSCH, SR, periodic CSI PUCCH, SP-CSI PUCCH) be configured as SBFD and all occasions for the resource locate in non-SBFD symbols. Likewise, the UE should not expect that a valid symbol type of a resource (e.g., Type 1 CG PUSCH, SR, periodic CSI PUCCH, SP-CSI PUCCH) be configured as non-SBFD and all occasions for the resource locate in the SBFD symbols. 
Proposal 9: Add a note in the 38.331 indicating that under Configuration 1, the UE expects that all resources indicated by the multi-CSI-PUCCH-ResourceList to have the same valid symbol type in a slot overlapping with one or more P/SP CSI reports. 
Proposal 10: Under Configuration 1, when PUCCH resources for 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 11: Introduce new capabilities indicating the UE has the capability to rate match SPS PDSCH repetitions around REs/PRBs determined according to SBFD time-frequency locations and the assigned PRBs. 
If the UE does not indicate the new capabilites, the NW should not configure SPS PDSCH repeitions for Configuraion 2 such that the repetitions be across SBFD and non-SBFD symbols while the assigned PRBs overlap with UL usable PRBs and/or Guardband(s) if configured.
Proposal 12: For PUSCH repetition Type B a nominal repetition includes both SBFD symbols and non-SBFD symbols, a nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols. 
Define new UE behavior to segment a nominal repetition mapped to SBFD and non-SBFD symbols within a slot into multiple actual repetitions around boundary of SBFD symbols and non-SBFD symbols by considering any additional invalid symbols determined based on symbols of transition period, if configured:
for SBFD-to-UL switching
for DL-to-SBFD switching if the switching is located in the SBFD
Proposal 13: Support separate beam/TCI states for SBFD and non-SBFD symbols for single-TRP scenario for both UL and DL.
Proposal 14: When gNB supports separate TCI states for SBFD and non-SBFD symbols, down-select from the following options for the UE to determine which TCI state is for SBFD symbols and which TCI state is for 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 bitfield 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 15: If separate UL power control for SBFD is not associated within unified TCI state, separate UL power control parameters for SBFD configured in BWP-UplinkDedicated are applied.
Extend the UL power control configuration within unified TCI states to BWP-UplinkDedicated. 
Proposal 16: Support explicit indication of enabling/disabling a SBFD operation on a cell. Consider mechanisms to switch a cell of a SBFD operation (e.g., for deactivated cell with SBFD operation, for flexibility, etc). 
Proposal 17: In handling a half-duplex CA with a SBFD operation, consider candidate options: a) Similar to SFI handling, this case is left to network scheduling i.e., UE does not perform reference cell determination if a cell is enabled with a SBFD operation; b) For a symbol overlapping with a SBFD symbol of a cell, UE determines a reference cell from cell(s) with downlink symbol or uplink symbol by RRC signalling (e.g., CSI-RS, PDCCH, PDSCH, SRS, PUCCH, PUSCH, PRACH). 
Proposal 18: To allow intra-band CA with a SBFD operation, relax TDD configuration and dynamic UL collision. A symbol indicated as downlink by TDD configuration on a reference cell, if the symbol is not a SBFD symbol of another cell in a same frequency band to the reference cell, UE does not expect to detect a DCI format scheduling a transmission on the another cell. Otherwise, UE may expect to detect a DCI format scheduling a transmission on the other cell on the symbol. 

3GPP TSG RAN WG1 #120bis	R1-2502121
Wuhan, China, April 7th – 11th, 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. 
Configuration of SBFD subbands
Proposal 1: Do not support UE-specific configuration of SBFD subbands.
Proposal 2: Extend SCS-SpecificCarrier IE to configure the corresponding DL/UL subbands for the SCS configuration inside.
Proposal 3: 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.
Collision handling
Proposal 4: Confirm the following Working Assumption.
Separate power control
Proposal 5: 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 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
(HARQ process ID allocation)
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.
(Multiple SPS PDSCHs in a slot)
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.
(PUSCH repetition type A with available slot counting or TBoMS)
Proposal 10: For PUSCH repetition type A with available slot counting or TBoMS, enhance the rules for available slot counting to resolve the collision with the invalid symbol type and to allow PUSCH transmissions overlapping with symbols indicated DL by tdd-UL-DL-ConfigurationCommon.
Proposal 11: For PUSCH repetition type A with available slot counting or TBoMS scheduled by DCI, clarify whether the first transmission/reception occasion indicated by the DCI refers to the symbol allocation in the slot determined based on slot offset K2 in the TDRA row indicated by the DCI or the symbol allocation in the first available slot.
If the first transmission/reception occasion indicated by the DCI refers to the symbol allocation in the first available slot, the first available slot is determined before determining the invalid symbol type.
(PUSCH repetition type B)
Proposal 12: To determine the invalid symbols for PUSCH repetition Type B transmission, support the following enhancement for SBFD operation.
In Configuration 1,
If the valid symbol type is SBFD symbols, a non-SBFD symbol is considered as an invalid symbol.
If the valid symbol type is non-SBFD symbols, an SBFD symbol is considered as an invalid symbol, and 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.
In Configuration 2,
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.
Proposal 13: For PUSCH repetition type B with Configuration 2, support Option 2.
Option 2: A nominal repetition is segmented into actual repetitions as in legacy operation. An actual repetition mapped to both SBFD and non-SBFD symbols is dropped.
(UCI multiplexing)
Proposal 14: 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.
CSI report
Proposal 15: For CSI report associated with periodic/semi-persistent CSI-RS, support Option B with similar restrictions as Option A.
Option 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.
gNB configuration may not ensure that the CSI-RS associated with each sub-configuration is confined to either SBFD symbols or non-SBFD symbols only.
For the sub-configuration associated with CSI-RS(s) restricted to SBFD symbols only, only CSI-RS transmission occasions within SBFD symbols are used for CSI derivation. For the sub-configuration associated with CSI-RS(s) restricted to non-SBFD symbols only, only CSI-RS transmission occasions within non-SBFD symbols are used for CSI derivation.
SRS
Proposal 16: Introduce a new separate RRC parameter to configure SRS resource set(s) for SBFD symbols.
Proposal 17: For SRS resource set with usage set to 'nonCodebook', regarding symbol type of the associated CSI-RS, discuss which case(s) below are supported :
Case 1: For SRS resource set for SBFD symbols, the associated CSI-RS is in SBFD symbols.
Case 2: For SRS resource set for SBFD symbols, the associated CSI-RS is in non-SBFD symbols.
Case 3: For SRS resource set for non-SBFD symbols, the associated CSI-RS is in SBFD symbols.
Case 4: For SRS resource set for non-SBFD symbols, the associated CSI-RS is in non-SBFD symbols.
Proposal 18: Do not support separate SRS resource sets for SBFD symbols and non-SBFD symbols for usage set to ‘beamManagement’.
Carrier aggregation
Proposal 19: For the CA scenario aggregating SBFD and non-SBFD carriers, it should be specified whether an SBFD carrier can be configured by unifiedTCI-StateRef to use the TCI state pool of a non-SBFD carrier, and vice versa. 
If yes, it should be specified how to determine the power control parameters when the SBFD carrier uses the TCI state of the non-SBFD carrier, and vice versa.
Proposal 20: 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 #120bis	               	           R1-2502157 
Wuhan, China, April 7th – 11th, 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: For the time location indication of SBFD subbands, guard periods can be explicitly configured outside the SBFD subband time location to avoid mapping resources on them.
Proposal 2: For a physical channel/signal occasion mapped to SBFD and non-SBFD symbols within a slot, for PUSCH repetition type B, support the following option:
Option 1: A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols. 
Proposal 3: For PUSCH repetition type B whose actual repetitions across SBFD symbols and non-SBFD symbols in the same slot or different slots where each transmission occasion has either all SBFD or all non-SBFD symbols,
The number of PRBs for actual repetitions in SBFD and non-SBFD symbols are determined as legacy.
The PRBs for actual repetitions in non-SBFD symbols are determined as legacy. 
The starting PRB for actual repetitions in SBFD symbols is determined according to the following equation:
Equation 1-C2: 
If  is not configured, it is zero
Proposal 4: 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 5: 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 6: 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.
The frequency hopping counter  can be calculated as legacy.
Proposal 7: Support separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols for the usage ‘beamManagement’.
Proposal 8: 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 9: 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 10: 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 11: 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 12: 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 13: 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 14: 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 15: 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 #120bis		 	R1-2502197
Wuhan, China, April 7 – 11, 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 PUSCH repetition type B, a nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols.
FFS: Discuss further whether transmission gap needs to be introduced between two actual repetitions which occur boundary of SBFD and non-SBFD symbols
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:
Specify DMRS bundling enhancement when the TDW overlaps with SBFD symbols.
Proposal 12: 
Separate SSBs for SBFD devices are required to allow for sufficient flexibility in SBFD slots. 
Proposal 13: 
When determining the size of DL usable PRBs, considerations need to be made to ensure the SSB is able to fit within the subbands.
Proposal 14: 
Additional PDCCH monitoring occasions to send DCI for paging on SBFD symbols can be considered.
Proposal 15: 
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 16: 
Set the maximum number of switching times from uplink-downlink or downlink-uplink to 2 times per SBFD slot.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502241
Wuhan, China, April 7 – 11, 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: For a physical channel/signal occasion mapped to SBFD and non-SBFD symbols within a slot, for PUSCH repetition type B, support Option 1.
Option 1: A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols.
Proposal 4: When the number of partial PRGs for a PDSCH exceeds the maximum number of supported partial PRGs in SBFD symbols, down-select one from the following options
Option 1: UE does not expect the number of partial PRGs in SBFD symbols will exceed UE capability 
Option 2: Introduce predefined rules to determine which PRGs are valid or used
Proposal 5: 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 6: 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 7: 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 8: For PUSCH transmissions/repetition across SBFD symbols and non-SBFD in different slots where each transmission occasion/repetition has either all SBFD or all non-SBFD symbols (i.e., Configuration 2), for RA type 0, reuse the method for RA type1 with the following modification
The RBG containing the starting PRB for PUSCH in SBFD symbol  is taken as the first allocated RBG in SBFD symbols and the other allocated RBGs in SBFD symbols are determined based on the relative positions of RBGs in non-SBFD symbols
is changed to the number of PRBs from the starting PRB of the first allocated RBG to the end PRB of the last allocated RBG in non-SBFD symbols
Proposal 9: Support separate SRS resource set configurations in SBFD and non-SBFD symbols for usage set to 'beamManagement'.
Proposal 10: Support separate PCMAX,c configurations for SBFD symbols and non-SBFD symbols.
Proposal 11: Support separate PHR reporting for SBFD symbols and non-SBFD symbols.
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.

3GPP TSG RAN WG1 #120bis                                                                                         R1-2502277
Wuhan, China, April 7th – 11th, 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: For a physical channel/signal occasion mapped to SBFD and non-SBFD symbols within a slot, support option 2 for PUSCH repetition type B, i.e., a nominal repetition is segmented into actual repetitions as in legacy operation and an actual repetition mapped to both SBFD and non-SBFD symbols is dropped.
Proposal 4: For SPS HARQ-ACK transmission for Configuration 1, the valid symbol type for SPS HARQ-ACK is determined based on the symbol type of the first SPS HARQ-ACK occasion after the activation DCI.
Proposal 5: For PUSCH across SBFD symbols and non-SBFD symbols for configuration 2 and RA type 0, for determining the PRB for PUSCH transmissions in SBFD symbols, only the assigned PRBs within UL usable PRBs in SBFD symbols are considered to be valid.
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.
Observation 1:  is the UE configured maximum output power which is set by UE itself, instead of configured by network.
Observation 2: UE is allowed to set its configured maximum output power  in each slot by the current TS 38.101, which means UE can set its configured maximum output power  to be different for SBFD slot and non-SBFD slot by its implementation.
Proposal 7: 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.
Proposal 8:  It is captured in 38.211 or 38.213 or RRC recommendation to 38.331 that a UE does not expect the downlink subband(s) and uplink subband in a carrier are allocated in such a way that a downlink subband is in frequency domain between another downlink subband and a uplink subband.

3GPP TSG RAN WG1 #120bis		R1-2502315
Wuhan, China, April 7th – 11th, 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:
Observation 1: If the gNB schedules a PUSCH to be within the UL subband, the PUSCH occasion in SBFD OFDM symbols may be frequency shifted resulting in misalignment in frequency location between PUSCH occasions in SBFD and non-SBFD OFDM symbols.
Observation 2: PUSCH repetition Type B was introduced for URLLC, where the objective was to rapidly transmits as many PUSCH repetitions as possible to meet the low latency and high reliability requirement.  This objective is met in SBFD if the nominal repetition is segmented at SBFD and non-SBFD boundaries in addition to the legacy segmentation conditions.
Observation 3: 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 4: 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 by the via gNB scheduling.

Proposal 2: For Configuration 2, the starting PRB of PUSCH without frequency hopping in SBFD symbols for CG-PUSCH without repetitions, PUSCH repetition Type-A, multi-PUSCH scheduled by a single DCI and TBoMS, is determined using the following equation (i.e. modified Equation 1-C):
if  is outside of UL useable PRB
, 
Otherwise,


Proposal 3: For Configuration 2, PUSCH that is scheduled with FDRA Type 0 and without frequency hopping in SBFD symbols, for CG-PUSCH without repetitions, PUSCH repetition Type-A, multi-PUSCH scheduled by a single DCI and TBoMS:
The PUSCH is transmitted if the PUSCH can be fully contained within the UL useable PRB after it has been frequency shifted to , 
otherwise, it is dropped.

Proposal 4: For the transmission of PUSCH repetition Type B that crosses SBFD and non-SBFD OFDM symbols within a slot, the nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols in addition to the legacy segmentation conditions (i.e. Option 1).
Proposal 5: 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 6: Support different TCI state indications for transmissions in SBFD and non-SBFD OFDM symbols.

3GPP TSG RAN WG1 #120bis	R1-2502365
Wuhan, China, April 7th – 11th, 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. No need to define the explicit guard symbols for Case-A, Case-B, Case-D.
Observation 2. 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 3. 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
Observation 4. Current SRS counter works well with proper gNB’s configuration and tiggering

Proposal 1. Confirm the cell-specific configuration on frequency location of SBFD subbands. 
Proposal 2. RAN1 to discuss the necessity of explicit guard symbols for Case-C. If the necessity is justified, RAN1 to define a signalling to configure the number of explicit guard symbols and locations
Proposal 3. 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 4. 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 5. When SPS PDSCHs, PDSCH repetitions and multi-PDSCHs across non-SBFD symbols and SBFD symbols (Configuration 2), RAN1 further discusses how to apply wideband PRG size when the scheduled PRBs in a repetition/SPS PDSCH are contiguous in non-SBFD symbols, but the valid PRBs in a repetition/SPS PDSCH are non-contiguous in SBFD symbols.
Proposal 6. 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 7. The frequency shift is applicable to FDRA type-0 without any optimization.
Proposal 8. If both frequency shift and frequency hopping are applied, the frequency shift is firstly applied and then frequency hopping is applied. In other words, the starting PRB of the first hop of PUSCH in SBFD symbols is determined by the frequency shift.
Proposal 9. 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 10. 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. 
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 11. For CSI report associated with periodic/semi-persistent CSI-RS, support option B.
For option B, further study how to identify a sub-configuration is for SBFD symbols or for non-SBFD symbols
Proposal 12. 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 13. 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 14. 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 15. 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
Proposal 16. 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 17. 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 18. UE expects the same number of available slot offset values under two separate SRS resource set configuration.
Proposal 19. 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 20. 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 21. 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 22. For half-duplex CA case, SBFD symbol is considered as flexible symbol. 
Proposal 23. 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.

3GPP TSG RAN WG1 #120bis		  R1-2502402
Wuhan, China, April 7th – 11th, 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 CSI report associated with periodic/semi-persistent CSI-RS, support Option A.
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 maximum output power  for a slot containing SBFD symbol.
Proposal 6: Support the following collision handling in SBFD symbol.
Step 1: Resolving SBFD specific collision between transmissions/receptions and unusable resources, if any.
Step 2: Resolving the collision as in legacy, if any.
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 #120-bis	R1-2502405  
Wuhan, China, April 07 – April 11, 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:	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 5:	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 2:	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 3:	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 6:	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 7:	RAN1 can also discuss some compromise solution, e.g. on which case Option 1 is selected and on which case Option 2 is selected.
Observation 4:	On collision handling order, the moderator’s example in R1-2501340 for Case 1, Option 1 is not correct: step 1 does not result in cancelling the PUCCH since the PUCCH is in the UL usable RBs. Instead, all the collision handling would take place in Step 2, where UCI is multiplexed in DG PUSCH and transmitted according to legacy.
Proposal 8:	Transmission/receptions on unusable resources, e.g. when using configuration 1, should be excluded before handling collisions between channels and signals. Remaining handling of the collision between two or more DL/UL channels or signals follows existing/legacy procedure without specification impact.
Observation 5:	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 6:	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 9:	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 10:	For PUSCH repetition type B, support Option 1, i.e., a nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols.
Proposal 11:	For SBFD operation in half-duplex CA scenario, collision handling rules as agreed for the transmission/reception across UL and DL sub-bands can be reused.
Proposal 12:	RAN1 to discuss potential issue with UL Tx switching and unaligned TDD pattern when there is at least one CC is configured with SBFD.
Proposal 13:	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 7:	Some PDCCH candidates, e.g. with aggregation level 4/8/16, may be disrupted as they overlap with UL subband/guard band.
Observation 8:	Different number of PDCCH candidates are available in SBFD and non-SBFD slots.
Proposal 14:	Only the available/non-disrupted PDCCH candidates can be considered in PDCCH detection, in both SBFD and non-SBFD slots.
Observation 9:	RAN1 has agreed that the configuration of a valid symbol type is not applicable to CSI-RS configured for RLM/BFD.
Observation 10:	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 15:	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.
Proposal 16:	If no separate configuration is provided for SBFD symbols, PUCCH transmissions in SBFD symbols for the pucch-ResourceId is not expected.
Proposal 17:	RAN1 should avoid micro-optimization on frequency hopping counter if there is no clear benefit.
Proposal 18:	RAN1 should avoid any further enhancement for the ‘beamManagement’ usage.

3GPP TSG RAN WG1 Meeting #120-bis	R1-2502420
Wuhan, P. R. China, April 7th – 11th 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	The transmitter transient period, agreed by RAN4, will affect both legacy and SBFD-aware UEs and for that reason cannot be configured by signaling. Instead, a guard symbol can be implemented by the gNB in the DL symbol preceding the SBFD subband without specification impact.
Observation 7	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 8	Configuring SSB slots as DL would result in severe inter-cell interference in resources in networks without collocated SSBs.
Observation 9	A possible support for link direction does not change the prioritization for Case 6.
Observation 10	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 11	For collision Case 6, there is no ambiguity in the collision management to be resolved by specifying a collision resolution order.
Observation 12	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 13	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 14	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 15	The existing specifications for CORESET and search space configuration are sufficiently flexible to support SBFD operation.
Observation 16	Frequency hopping counter for an SRS resource is determined based on the SRS resource configuration and the timing of the transmission occasion. Restricting an SRS resource for transmission in SBFD or non-SBFD symbol will not have impact on the corresponding frequency hopping counter.
Observation 17	If SBFD is supported in combination with intra-band CA or inter-band CA for UEs not supporting Simultaneous TxRx then RAN1 needs to specify prioritization rules between DL and UL operation among different carreirs.
Observation 18	The only beneficial and technically feasible combination of SBFD and CA would be inter-band CA in combination with UEs capable of Simultaneous TxRx for that band combination.
Observation 19	The benefit of supporting SBFD in a CA scenario is significantly limited.
Observation 20	CA has RAN2 and RAN4 specification impact, e.g., signaling and activation requirements, that will be difficult to finalize in Rel-19.
Observation 21	The RAN1 agreement states that symbolType is introduced in rrc-ConfiguredUplinkGrant in ConfiguredGrantConfig to indicate valid symbol type for Type 1 CG PUSCH.
Observation 22	The RAN1 agreement states that symbolType is introduced in SchedulingRequestResourceConfig to indicate valid symbol type for PUCCH for SR.
Observation 23	The RAN1 agreement states that symbolType is introduced in periodic in CSI-ReportConfig to indicate valid symbol type for PUCCH carrying P-CSI.
Observation 24	The RAN1 agreement states that symbolType is introduced in semiPersistentOnPUCCH in CSI-ReportConfig to indicate valid symbol type for PUCCH carrying SP-CSI.

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	For PUSCH repetition type B, if Option 1 is adopted (i.e., a nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols), higher layer parameters could 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	Clarify the RAN1 agreement on SBFD operation in a multi-carrier scenario:
Support gNB SBFD operation on one TDD carrier in multi-carrier scenario.
Proposal 19	SBFD is only supported in non-CA multi-carrier scenarios from a UE perspective.

3GPP TSG RAN WG1 #120bis			R1-2502438
Wuhan, China, April 7th – 11th, 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: For PUSCH repetition type B, adopt Option 2.
Option 2: A nominal repetition is segmented into actual repetitions as in legacy operation. An actual repetition mapped to both SBFD and non-SBFD symbols is dropped. 
Proposal 2: Symbols indicated as downlink by tdd-UL-DL-ConfigurationCommon and configured as SBFD symbols are not invalid symbols for PUSCH repetition Type B transmission.
Proposal 3: Confirm the working assumption in red in the agreement made in RAN1#119 for separate SRS configurations for SBFD and non-SBFD symbols.
Proposal 4: For separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols, there is no impact on frequency hopping counter.
Proposal 5: Separate SRS-ResourceSets configurations for SBFD and non-SBFD symbols for a given usage is applicable to SRS-ResourceSets with usage set to ‘beamManagement’.
Proposal 6: 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 7: For collision handling in SBFD symbols for SBFD aware UEs,
Step 1: Resolving the collision as in legacy, if any. 
Step 2: Resolving SBFD specific collision between transmissions/receptions and unusable resources, if any.
Proposal 8: Introduce the following RRC parameters.

3GPP TSG RAN WG1 Meeting #120bis															R1-2502497 Wuhan, China, April 7th – 11th, 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, the frequency hopping counter remains the same as legacy.
Proposal 3: For SRS, FFS the impact on parameters like associated CSI-RS and spatial relation info.

Proposal 4: For SRS usage set to “beamManagement”, downselect from the 2 options:
For usage set “beamManagement”, support separate SRS resource sets for SBFD symbols and for non-SBFD symbols or
For usage set “beamManagement”, an SRS resource set is not explicitly associated with either SBFD or non-SBFD symbols.
FFS: How valid symbol type for each SRS resource is determined by the UE.
Proposal 5: For SRS usage set to “antennaSwitching”, an SRS resource set is not explicitly associated with either SBFD or non-SBFD symbols.
FFS: How valid symbol type for each SRS resource is determined by the UE.
Proposal 6: For SPS and CG, indication or determination of different MCS values are supported for SBFD and non-SBFD symbols in different slots.
Proposal 7: 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 8: For PUSCH DMRS bundling, DMRS bundling across both SBFD and non-SBFD symbols is avoided.
Proposal 9: When SBFD operation on one TDD carrier in multi-carrier scenario is supported, enhancements are required to handle the half-duplex CA case.

3GPP TSG RAN WG1 #120bis	R1-2502508
Wuhan, China, April 7th – 11th, 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. According to the network implementation, a UE may maintain power coherence across SBFD/non-SBFD symbol boundary for uplink transmissions.

Proposal 1. For PUSCH repetition type B, a nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols (option 1).
Proposal 2. RAN1 to clarify that a single power control can be used for both SBFD and non-SBFD symbols (i.e., separate power control for SBFD and non-SBFD symbols is not a mandatory feature).
If RAN1 agrees to go with the other alternative (i.e., in case that separate power control for SBFD and non-SBFD symbols is a basic feature for SBFD), we think this aspect should be clearly captured in the specifications.
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 all CMRs, IMRs, and 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
CSI reference resource for a CSI report with valid symbol type configured as SBFD symbol should include one or more SBFD symbols and one or more DL usable PRBs. 
If the valid symbol type configured by the CSI report is non-SBFD symbols, only the REs on non-SBFD symbols 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
CSI reference resource for a CSI report with aperiodic CSI-RS measured in SBFD symbol should include one or more SBFD symbols and one or more DL usable PRBs. 
if the valid symbol type is non-SBFD symbols, only the REs on non-SBFD symbols 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#120bis                           R1- 2502540
Wuhan, China, April 7th – 11th, 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: Confirm the working assumption
Agreement
For RRC connected mode UEs, at least cell-specific configuration on time and frequency(working assumption) location of SBFD subbands is supported within a TDD carrier.
FFS: Additional support of UE-specific configuration on time and/or frequency locations of SBFD subbands 
Proposal 2: UE-specific configuration on frequency locations of SBFD subbands should not be supported.
Proposal 3: Guard period between the last non-SBFD DL symbol and the first symbol of UL subband is needed.
Proposal 4: 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 5: 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 6: The issue of the RBs within UL subband cannot be indicated by fallback DCI should be studied.
Proposal 7: An offset that is applied to the start of the RB allocation indicated by the fallback DCI should be introduced.
Proposal 8: 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 9: For PUSCH repetition type B, if a particular nominal repetition includes both SBFD and non-SBFD symbols, several methods can be considered:
Divide the actual repetition based on the boundary between SBFD symbol and non-SBFD symbol.
One of these types of symbols is considered invalid.
Proposal 10: For configuration 1, the exclusion of SPS PDSCH transmission in the invalid symbol type should be applied before SPS PDSCH transmission collision handling.
Proposal 11: 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 12: For CSI report associated with periodic/semi-persistent CSI-RS, support Option A.
Proposal 13: For periodic and semi-persistent CSI-RS, the CSI-RS transmissions in invalid symbol types should be dropped.

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

Agenda Item:	9.3.1
Source:	Apple Inc.
Title:	Discussion 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: Regarding partial RBG, it is concluded that partial RBGs is already supported where nominal RBG size is based on active BWP size, not based on sub-band size.

Proposal 2: 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 3: 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 4: 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 5: 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 Meeting #120-bis                                                 	   R1-2502652
Wuhan, China, April 7th – 11th, 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: Limit the maximum UE transmit power in the SBFD symbols/slots to limit UE-to-UE CLI in the adjacent legacy TDD networks.  gNB will convey either the maximum SBFD UE transmit power to UE 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: To limit the UE-to-UE CLI in the network, write an LS to RAN4 to specify the maximum UE transmit power for UL transmissions in the SBFD symbols/slots in 38.101-1, 38.101-2 and 38.101-3.

Observation 1: If it should become possible for SRS configurations to be exchanged between gNBs then victim UEs served by some gNB can identify any aggressor UE(s) served by some neighboring gNB and the latter can limit the maximum transmit power of such identified aggressor 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.

Proposal 5: High power SBFD aware UEs are not scheduled in the SBFD symbols/slots and gNB can use different mechanism of estimated transmit power level per UE or reported PHR per UE  

Proposal 6:  Thresholds for managing SBFD UL resources for the served UEs can be found based on historical measurements/reports fed back by the served UEs and used to schedule UL resources in SBFD symbols/slots to different groups of UEs.

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

Source:	Sharp
Title:	SBFD Tx/Rx/measurement aspects
Agenda Item:	9.3.1
Document for:	Discussion and Decision
TX/RX/measurement procedures
Tx/Rx occasion mapped to SBFD and non-SBFD symbols within a slot
For Tx/Rx within a slot, repetition type B was marked as FFS, as per the following agreement reached at the RAN1#119 meeting [1].

Compared to Option 2, Option 1 conserves some resources in a nominal repetition within a slot that includes both SBFD and non-SBFD symbols. Furthermore, the specification impact is not significant. Option 1 can be implemented by defining a new "invalid symbol" type for actual repetition determination. Therefore, we support Option 1.
Proposal 1: Support Option 1 for PUSCH repetition type B (i.e., A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols).
FDRA RA type 1
In [2], the following is captured for RA type 1 on PDSCH.

In DCI format 1_0 monitored in CSS, the maximum bandwidth allocation is constrained by the bandwidth of CORESET0. In FR1, the maximum CORESET0 bandwidth does not exceed 20 MHz, which is smaller than the 40 MHz DL subband. In FR2-1, the maximum CORESET0 bandwidth is 70 MHz, which is smaller than the 75 MHz DL subband. In [3], an alternative option for a DL subband of approximately 40 MHz is proposed. However, most companies evaluated 75 MHz. Therefore, we consider this a micro-optimization.
Proposal 2: Enhancement of RA type 1 for DCI format 1_0 monitored in CSS is not pursued for Rel-19.
PTRS
When transform precoding is enabled, PT-RS mapping appears on the edge RBs. If these edge RBs are invalidated, the corresponding PT-RS samples will be lost, leading to performance degradation.
Figure 1 illustrates an example of PT-RS mapping when transform precoding is enabled, with 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, invalidated RBs should be excluded from the scheduled bandwidth before PT-RS mapping determination. This ensures that PT-RS mapping remains within the UL subband.
Proposal 3: When transform precoding is enabled, invalidated RBs 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
In the feature lead summary developed in RAN1#120 [4], 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 4: 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.
Miscellaneous issues
Frequency domain resource allocation Type 1 for PUSCH in a single slot
In [2], following agreement has been made for PDSCH.

However, for PUSCH, agreement has not been made yet. Therefore, we propose the corresponding agreement for PUSCH.
Proposal 5: For frequency domain resource allocation Type 1 for PUSCH in a single slot:
Only the assigned PRBs within UL usable PRBs are considered valid for PUSCH.
Assigned PRBs that fall outside UL usable PRBs are considered invalid and should not be used for PUSCH resource mapping.
Existing RB indexing and VRB-to-PRB mapping are reused.
The number of PRBs for TBS determination is based solely on the assigned PRBs within UL usable PRBs.
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: Support Option 1 for PUSCH repetition type B (i.e., A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols).
Proposal 2: Enhancement of RA type 1 for DCI format 1_0 monitored in CSS is not pursued for Rel-19.
Proposal 3: When transform precoding is enabled, invalidated RBs should be excluded from the scheduled bandwidth before PT-RS mapping determination.
Proposal 4: 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 5: For frequency domain resource allocation Type 1 for PUSCH in a single slot:
Only the assigned PRBs within UL usable PRBs are considered valid for PUSCH.
Assigned PRBs that fall outside UL usable PRBs are considered invalid and should not be used for PUSCH resource mapping.
Existing RB indexing and VRB-to-PRB mapping are reused.
The number of PRBs for TBS determination is based solely on the assigned PRBs within UL usable PRBs.
References
RAN1 chairman’s note RAN1#119, November 2024
RAN1 chairman’s note RAN1#117, May 2024
RP-232763, 3GPP TR 38.858 V2.0.0, Study on Evolution of NR Duplex Operation
R1-2501340, Summary #3 of SBFD TX/RX/measurement procedures	Moderator (Xiaomi), February 2025

TDoc file conclusion not found

3GPP TSG RAN WG1 #120bis			                 R1-2502668
Wuhan, China, April 7th – 11th, 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 PUSCH repetition type B with configuration 1, support the following option: 
Option 2: A nominal repetition is segmented into actual repetitions as in legacy operation. An actual repetition mapped to both SBFD and non-SBFD symbols is dropped.

Proposal 2: 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 3: Support separate beam/spatial relation configuration for SBFD and non-SBFD symbols.

Proposal 4: 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 5: 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 6. For CSI derivation corresponding to a CSI-RS in SBFD symbols, TBS is determined based on the REs on SBFD symbols and DL usable PRBs in the SBFD symbols.

Proposal 7. For collision handling in SBFD symbols for SBFD aware UEs, the following option 2 is supported:
Option 2 
Step 1: Resolving SBFD specific collision between PUCCH with repetitions/PUSCH 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.
Step 2: Resolving SBFD specific collision between transmissions/receptions and unusable resources, if any.

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

TDoc file reading error

3GPP TSG RAN WG1 #120bis		R1-2502689
Wuhan, China, April 7th – 11th, 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: For PUSCH repetition type B, support Option 1.
Option 1: A nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols.
Proposal 3: Limit the number of Tx/Rx transitions the UE can perform within a time period.
Proposal 4: For SBFD operation on one TDD carrier in multi-carrier scenario, no enhancement is needed to handle half-duplex CA case.
Proposal 5: For collision handling in SBFD symbols for SBFD-aware UEs, SBFD-specific collision between transmissions/receptions and unusable resources is handled first followed by existing collision handling.
Proposal 6: 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 7: 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 8: 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 #120bis			R1-2502763
Wuhan, China, April 7th – 11th, 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: Confirm the working assumption to support cell-specific configuration on SBFD subband frequency location indication.
UE specific signaling via RRC is supported in addition to cell specific signaling via SIB.

Proposal 2: UE doesn’t expect any non-SBFD DL symbol between SBFD symbols and UL symbols within a TDD pattern period.
Proposal 3: For cell-specific configuration of SBFD subband locations for SCSs in SpecificCarrierList, at least 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.
FFS whether/how to allow unaligned DL subband boundary among SCSs, and whether/how to allow unaligned UL subband boundary among SCSs.

Proposal 4: 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 5: 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 6: 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 7: 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 8: 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 9: For configuration 1, the SPS PDSCH collision handling procedure is applied after excluding SPS PDSCH in the invalid symbol type.

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

Proposal 11: 
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 12: 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 13: For reference cell determination, the legacy rule is reused with considering SBFD symbol as flexible symbol.

Proposal 14: For PUSCH repetition type B, support Option 1, i.e. a nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols. 
An actual repetition includes SBFD symbols only or non-SBFD symbols only.
If configuration 1 is provided, the valid symbol type is determined based on the symbol type of the first actual repetition. Only actual repetitions in the valid symbol type with more than 1 symbol can be transmitted.
If configuration 2 is provided, actual repetitions with more than 1 symbol can be transmitted.

Proposal 15: 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 overlaps with RB outside UL usable PRBs in SBFD symbols.  
The target slot for deferring is the first slot in which determined PUCCH resource not overlapping with non-SBFD DL symbol or SSB symbol and not overlapping with RB outside UL usable PRBs in SBFD symbols.

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

TDoc file reading error

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

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

Conclusion
There is no RAN1 consensus to support semi-static link direction indication for SBFD aware UEs.
For a serving cell configured with SBFD subband time and frequency location, for an SBFD aware UE, TDD-UL-DL-ConfigDedicated is only applicable to non-SBFD symbols but not applicable to SBFD symbols

Agreement
For determining starting PRB for PUSCH transmissions in SBFD symbols for Configuration 2, 
For type 1 CG PUSCH, a  is configured in rrc-ConfiguredUplinkGrant in ConfiguredGrantConfig.
For type 2 CG PUSCH and DG PUSCH, a  is configured per UL BWP in PUSCH-Config.
The is commonly applicable to all DCI formats which schedule PUSCH
Ifis not configured, it is assumed to be zero

Agreement
When higher layer parameter ul-FullPowerTransmission is set to 'fullpowerMode2', the numbers of SRS ports should be the same for SRS resources with the same corresponding SRI values in the two SRS resource sets associated with SBFD and non-SBFD symbols.

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

Agreement
For Configuration 1: The transmissions/receptions are restricted to SBFD symbols only or non-SBFD symbols only,
The valid symbol type for Type 1 CG PUSCH is configured in rrc-ConfiguredUplinkGrant in ConfiguredGrantConfig.
The valid symbol type for PUCCH configured for SR is configured in SchedulingRequestResourceConfig.
The valid symbol type for PUCCH carrying P-CSI is configured in periodic in CSI-ReportConfig.

Agreement
For a type 1 CG PUSCH with Configuration 2, if FH offset for SBFD symbols is not configured for the type 1 CG PUSCH, frequency hopping is disabled for the type 1 CG PUSCH transmissions in SBFD symbols.
For a type 2 CG PUSCH/PUSCH scheduled by DCI, if FH offset lists for SBFD symbols are not configured for the type 2 CG PUSCH/PUSCH scheduled by DCI, frequency hopping is disabled for the transmission of the type 2 CG PUSCH/PUSCH scheduled by DCI in SBFD symbols.

Agreement
For SPS PDSCH with Configuration 2, for TBS determination, 
For SPS PDSCH without repetition, 
The number of PRBs for TBS determination for an SPS PDSCH in SBFD symbols is based on assigned PRBs within DL usable PRBs only. 
The number of PRBs for TBS determination for an SPS PDSCH in non-SBFD symbols is based on assigned PRBs.
For SPS PDSCH with repetition, TBS is determined based on the first repetition occasion.
If the first repetition occasion of a SPS PDSCH is in SBFD symbols, the number of PRBs for TBS determination for the SPS PDSCH is based on assigned PRBs within DL usable PRBs only.
If the first repetition occasion of a SPS PDSCH is in non-SBFD symbols, the number of PRBs for TBS determination for the SPS PDSCH is based on assigned PRBs.

R1-2501340	Summary #3 of SBFD TX/RX/measurement procedures	Moderator (Xiaomi)

Agreement
If starting PRB is not configured for SBFD symbols for a PUCCH-Resource, starting PRB configured for non-SBFD symbols for the PUCCH-Resource is used for PUCCH transmissions in SBFD symbols associated with this pucch-ResourceId.

Agreement
The one configuration of intraSlotFrequencyHopping for a PUCCH-Resource is applied to both PUCCH transmissions in SBFD symbols and in non-SBFD symbols associated with this pucch-ResourceId.

Agreement
Support SBFD operation on one TDD carrier in multi-carrier scenario. 
Note: If the TDD carrier for SBFD operation is an Scell, support UE dedicated signaling for cell-specific configuration of time and frequency location of SBFD subbands for the Scell.  
FFS whether/how to handle half-duplex CA case

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

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

Conclusion
There is no RAN1 consensus to support semi-static link direction indication for SBFD aware UEs.
For a serving cell configured with SBFD subband time and frequency location, for an SBFD aware UE, TDD-UL-DL-ConfigDedicated is only applicable to non-SBFD symbols but not applicable to SBFD symbols

Agreement
For determining starting PRB for PUSCH transmissions in SBFD symbols for Configuration 2, 
For type 1 CG PUSCH, a  is configured in rrc-ConfiguredUplinkGrant in ConfiguredGrantConfig.
For type 2 CG PUSCH and DG PUSCH, a  is configured per UL BWP in PUSCH-Config.
The is commonly applicable to all DCI formats which schedule PUSCH
Ifis not configured, it is assumed to be zero

Agreement
When higher layer parameter ul-FullPowerTransmission is set to 'fullpowerMode2', the numbers of SRS ports should be the same for SRS resources with the same corresponding SRI values in the two SRS resource sets associated with SBFD and non-SBFD symbols.

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

Agreement
For Configuration 1: The transmissions/receptions are restricted to SBFD symbols only or non-SBFD symbols only,
The valid symbol type for Type 1 CG PUSCH is configured in rrc-ConfiguredUplinkGrant in ConfiguredGrantConfig.
The valid symbol type for PUCCH configured for SR is configured in SchedulingRequestResourceConfig.
The valid symbol type for PUCCH carrying P-CSI is configured in periodic in CSI-ReportConfig.

Agreement
For a type 1 CG PUSCH with Configuration 2, if FH offset for SBFD symbols is not configured for the type 1 CG PUSCH, frequency hopping is disabled for the type 1 CG PUSCH transmissions in SBFD symbols.
For a type 2 CG PUSCH/PUSCH scheduled by DCI, if FH offset lists for SBFD symbols are not configured for the type 2 CG PUSCH/PUSCH scheduled by DCI, frequency hopping is disabled for the transmission of the type 2 CG PUSCH/PUSCH scheduled by DCI in SBFD symbols.

Agreement
For SPS PDSCH with Configuration 2, for TBS determination, 
For SPS PDSCH without repetition, 
The number of PRBs for TBS determination for an SPS PDSCH in SBFD symbols is based on assigned PRBs within DL usable PRBs only. 
The number of PRBs for TBS determination for an SPS PDSCH in non-SBFD symbols is based on assigned PRBs.
For SPS PDSCH with repetition, TBS is determined based on the first repetition occasion.
If the first repetition occasion of a SPS PDSCH is in SBFD symbols, the number of PRBs for TBS determination for the SPS PDSCH is based on assigned PRBs within DL usable PRBs only.
If the first repetition occasion of a SPS PDSCH is in non-SBFD symbols, the number of PRBs for TBS determination for the SPS PDSCH is based on assigned PRBs.

R1-2501340	Summary #3 of SBFD TX/RX/measurement procedures	Moderator (Xiaomi)

Agreement
If starting PRB is not configured for SBFD symbols for a PUCCH-Resource, starting PRB configured for non-SBFD symbols for the PUCCH-Resource is used for PUCCH transmissions in SBFD symbols associated with this pucch-ResourceId.

Agreement
The one configuration of intraSlotFrequencyHopping for a PUCCH-Resource is applied to both PUCCH transmissions in SBFD symbols and in non-SBFD symbols associated with this pucch-ResourceId.

Agreement
Support SBFD operation on one TDD carrier in multi-carrier scenario. 
Note: If the TDD carrier for SBFD operation is an Scell, support UE dedicated signaling for cell-specific configuration of time and frequency location of SBFD subbands for the Scell.  
FFS whether/how to handle half-duplex CA case

3GPP TSG RAN WG1 #120bis			   R1-2502836
Wuhan, China, April 7th – 11th, 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 the definition of partial RBG(s) for Type 0 PDSCH/PUSCH resource allocation for the RBG(s) that partially overlaps with the DL/UL usable PRBs for TBS size determination.

Proposal 5: For PDSCH resource allocation type 1 in SBFD symbols, support the following:
The definition of partial Resource block bundle when VRB-PRB interleaving is enabled.
The definition of partial RBG(s) for DCI format 1_2 when VRB-PRB interleaving is disabled.

Proposal 6: 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 7: UE doesn’t expect to be dynamically scheduled with a physical channel/signal in a slot that is mapped to both SBFD and non-SBFD symbols.  
UE drops or discard physical channel transmission or reception configured by higher layer that is mapped to SBFD and non-SBFD symbols in a slot. 
For PUCCH repetition or PUSCH repetition with available slot counting, the slot is not counted if the time resources of transmission occasion maps to both SBFD and non-SBFD symbols. 

Proposal 8: For PUSCH repetition type B, support option 1 where a nominal repetition is segmented into actual repetitions around boundary of SBFD symbols and non-SBFD symbols. 
The configuration of Configuration 1 or 2 for UL BWP is applicable to PUSCH repetition Type B.

Proposal 9: For PUCCH repetition, PUSCH repetition with available counting and TBoMS and UE is provided configuration 1 for UL transmission: 
When the valid symbol type is determined as SBFD, a slot is counted when
all symbols are SBFD symbols and frequency resources are within the uplink subband of SBFD symbols, and are not overlapping in time domain with SSB symbols
When the valid symbol is determined as non-SBFD, a slot is counted when
all symbols are non-SBFD symbols as UL symbols and/or FL symbols not overlapping in time domain with SSB symbols

Proposal 10: For PUSCH repetition Type B, when UE is provided with configuration #1:
The valid symbol type for Type 1 CG PUSCH is configured in rrc-ConfiguredUplinkGrant
The valid symbol type for Type 2 CG PUSCH (or DG-PUSCH) is determined based on the symbol type of the first nominal repetition associated with activation (or scheduling) DCI. 
Invalid SBFD/non-SBFD symbol(s) are considered invalid for PUSCH repetition type B.

Proposal 11: The semi-static configuration of Configuration 1 or 2 for UL BWP is applicable to PUCCH deferral of SPS-PDSCH. 
The valid symbol of the PUCCH resource is determined based on the first PUCCH transmission occasion associated with the activation DCI for the SPS-PDSCH.
The PUCCH deferral procedure shall consider invalid symbol type of configuration #1

Proposal 12: 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 13: 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 14: No support of other conditions to enable/disable to apply  in SBFD symbols. 
Proposal 15: The agreement of RB-offset determination for PUSCH transmission across SBFD and non-SBFD symbols should be extended to include PUSCH repetition type B and multiple CG-PUSCH occasions within a CG-period
Proposal 16: For PUCCH repetition, PUSCH repetition with available counting and TBoMS and UE is provided configuration 2 for UL transmission across SBFD and non-SBFD symbols, a slot is counted when
all symbols are SBFD symbols and frequency resources are within the uplink subband of SBFD symbols, and are not overlapping in time domain with SSB symbols, or 
all symbols are non-SBFD symbols as UL symbols and/or FL symbols not overlapping in time domain with SSB symbols.

Proposal 17: 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 18: 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 19: 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 20: 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 21: 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 22: 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 23: Support two PHRs reporting associated with uplink transmission in SBFD and non-SBFD symbols respectively.

3GPP TSG RAN WG1 #120b                                                         R1-2502901
Wuhan, China, April 7th – 11th, 2025
Agenda Item:		9.3.1
Source: 		Google
Title:			Discussion on SBFD TX/RX/measurement procedures
Document for: 	Discussion and Decision

Conclusion 1: UE performs SBFD specific collision handling and physical channel validation first, then applies legacy collision handling rules, if any. UE determines the UCI multiplexing resources after the physical channel validation.

3GPP TSG RAN WG1 #120-bis                                            	    R1-2502913
Wuhan, China, 7th – 11th, April, 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
Proposal 1: For configuring valid symbol type for CSI derivation in CSI-ReportConfig for SBFD and non-SBFD scenario, following options can be considered:
Alt 1: Introduce new field CSI-ReportConfig-Type for SBFD and non-SBFD scenario
Alt 2: Define format indicator for CSI report quantity impacted by SBFD scenario (E.g., CQIformatIndicator=SBFD)

Observation 1: In case of configuring separate CSI-ReportConfig for SBFD and non-SBFD scenario, the CSI reference resource and 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 2: 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 #120bis			R1-2502925
Wuhan, China, April 7th – 11th, 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: 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: In addition to availability in time domain, availability in frequency domain should be further considered to determine available slot of PUCCH repetition, PUSCH repetition with available slot counting and TBoMS for a SBFD-aware UE.
Proposal 3: To determine available slot for PUCCH repetition, PUSCH repetition with available slot counting and TBoMS for an SBFD-aware UE, 
When SBFD-Configuration2-Transmission is not enabled (i.e., Configuration 1) and the valid symbol type is determined as SBFD symbols, a slot is determined as available slot if all of the following conditions are met:
1) the slot consists of all SBFD symbols, 2) the allocated frequency resources are within the UL usable PRBs (i.e., UL subband) of the slot, and 3) the allocated frequency resources of the slot do not overlap with SSB symbols in the time domain.
When SBFD-Configuration2-Transmission is not enabled (i.e., Configuration 1) and the valid symbol type is determined as non-SBFD symbols, a slot is determined as available slot if both of the following conditions are met:
1) the slot consists of all non-SBFD symbols (i.e., UL and/or Flexible symbols) and 2) the allocated frequency resource of the slot do not overlap with SSB symbols in the time domain.
When SBFD-Configuration2-Transmission is enabled (i.e., Configuration 2), a slot is determined as available slot
if all of the following conditions are met: 1) the slot consists of all SBFD symbols, 2) the allocated frequency resources are within the UL usable PRBs (i.e., UL subband) of the slot, and 3) the allocated frequency resources of the slot do not overlapped with SSB symbols in the time domain. 
Or if both of the following conditions are met: 1) the slot consists of all non-SBFD symbols (i.e., UL and/or Flexible symbols) and 2) the allocated frequency resources of the slot do not overlap with SSB symbols in time domain.
Proposal 4: RBs within UL subband in symbols configured as downlink by TDD-UL-DL-ConfigCommon should not be an event of actual TDW determination for a SBFD-aware UE.
Proposal 5: For PUSCH transmissions or PUCCH transmissions across SBFD symbols and non-SBFD symbols in different slots, we propose to investigate how to maintain power consistency if DMRS bundling is configured as enabled for a SBFD-aware UE with Configuration 2.
Proposal 6: 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 7: 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 8: 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 9: For a SBFD-aware UE, an UL subband in symbols configured as DL by TDD-UL-DL-ConfigCommon and symbols 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.