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

Agenda Item:	9.3.3
Source:	Huawei, HiSilicon
Title:	On cross-link interference handling for subband full duplex
Document for:	Discussion and Decision

Conclusions
In this contribution, the following are proposed for gNB-to-gNB CLI handling and UE-to-UE CLI handling:
Observation 1: If an UL resource muting symbol overlaps with a symbol containing PT-RS for a PUSCH and when transform precoding is enabled for the PUSCH, there is no collision between PT-RS and UL muting resources since PT-RS is inserted prior to DFT, and the output of DFT is mapped only to unmuted subcarriers.
Proposal 1: An indicator is provided to disable UL resource muting in non-SBFD symbols for SBFD-aware UEs
If this indicator is provided, UL resource muting cannot be applied in non-SBFD symbols 
Otherwise, UL resource muting is applied in both SBFD symbols and non-SBFD symbols
Proposal 2: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, support Alt-3.
Alt-3
For PT-RS insertion in a block of  samples prior to transform precoding
 and  are determined as legacy from 38.214 Table 6.2.3.2-1
PT-RS sample positions are determined as legacy, but only for the first  groups
Note: After PT-RS insertion, all of the mathematically equivalent DFT Options 1, 2A, and 2B from the RAN1#120 agreement are applicable, where the choice is up to UE implementation
Proposal 3: For each CSI Reporting Setting, UE can be configured with up to 32 SRS-RSRP resources and 64 CLI-RSSI resources regardless of measurement resource type for L1 based CLI measurement depending on UE capability.
Proposal 4: The symbol type configuration does not apply for SRS-RSRP/CLI-RSSI measurement resources, i.e., L1 UE-to-UE CLI measurement are restricted in SBFD symbols for SBFD-aware UEs.
Proposal 5: A UE does not expect to be configured with a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for AP CLI and the first symbol of the aperiodic CLI SRS-RSRP or CLI-RSSI resources is smaller than the UE reported threshold beamSwitchTiming.
Proposal 6: A UE can be configured with L1 and L3 UE-to-UE CLI measurement resources. It is up to UE implementation whether to prioritize L1 or L3 UE-to-UE CLI measurement when two measurement resources overlap in time.
Proposal 7: The number of CPUs in a component carrier and across all component carriers are not increased for L1 CLI measurement and reporting.
Proposal 8: For aperiodic CLI measurement and reporting, the slot offset between the slot containing the DCI that triggers a set of aperiodic SRS-RSRP resources and the slot in which the SRS-RSRP resource set is measured can be smaller than 1.

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

Source:	ZTE Corporation, Sanechips
Title:	Discussion on CLI handling for Rel-19 duplex operation
Agenda item:	9.3.3
Document for:	Discussion and Decision

Conclusion
According to the discussion above, we have the following observation and proposals.
UL resource muting
Proposal 1: For the PTRS on the OFDM symbols with UL muting resource when the transform precoding is enabled
 and  are determined as legacy from 38.214 Table 6.2.3.2-1
PT-RS sample positions are determined as legacy, but only for the first  groups
Note: After PT-RS insertion, all of the mathematically equivalent DFT Options 1, 2A, and 2B from the RAN1#120 agreement are applicable, where the choice is up to UE implementation
Proposal 2: Whether UL resource muting can be applied to non-SBFD symbols should be configured by the gNB.
L1 based UE-to-UE CLI measurement and reporting
Observation 1: L1-based CLI measurement is still needed in the non-SBFD symbols since the interference from the aggressor UE still exists as long as the aggressor UE transmits UL signal.
Proposal 3: The valid symbol type for CSI derivation configured in CSI-ReportConfig should be applicable for L1 UE-to-UE CLI measurement and reporting.
Proposal 4: More than one CLI-RSSI measurement resource should be supported.
Proposal 5: The maximum number of the CLI-RSSI resource within one CSI-ResourceConfig should be 64.
Proposal 6: Regarding the UE behaviour for CLI-RSSI measurement, there should be no specification impact.
Proposal 7: There should be no need to configure the reference serving cell for the CLI-RSSI measurement resource.
Proposal 8: The available slot offset should not be supported for aperiodic SRS for CLI measurement.
Proposal 9: For the configuration of the SRS resource, the DL BWP ID, and the physical cell ID of the aggressor UE should be needed and the reference serving cell should not be needed.
Proposal 10: For measurement timing, the Rel-16 method should be adopted as the baseline and further discuss whether the enhancements are needed.
Proposal 11: The issue that the time offset between the DCI and the aperiodic measurement resource is smaller than the UE reported threshold beamSwitchTiming should be handled by gNB implementation.
RRC signalling
Proposal 12: The number of the CLI measurement resource sets, including CLI-RSSI resource sets or SRS-RSRP resource sets in the CSI-ResourceConfig should be 16 and the number of SRS resources in the set should be 32.

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

Source:	vivo
Title:	Remaining issues on CLI handling for Rel-19 NR duplex
Agenda Item:	9.3.3
Document for:	Discussion and Decision

Conclusion
In this contribution, CLI handling for Rel-19 NR duplex including gNB-to-gNB co-channel and UE-to-UE co-channel CLI handling are discussed, with the following proposals:
Proposal 1: If an UL resource muting symbol overlaps with a symbol containing PTRS for a PUSCH and transform precoding is enabled for the PUSCH, UL resource muting is not applied in the PUSCH symbol containing PT-RS
Proposal 2: For L1 CLI measurement and reporting, 4-bit is reported for each differential value in case the largest measurement is out of range and the reported 4bits may be meaningless.
Proposal 3: For the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for aperiodic CLI reporting and the first symbol of the aperiodic SRS-RSRP measurement resource or CLI-RSSI measurement resources, Alt 1 is supported
Alt 1: UE does not expect to be configured with a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for AP CLI and the first symbol of the aperiodic CLI SRS-RSRP or CLI-RSSI resources is smaller than the UE reported threshold beamSwitchTiming.

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

Agenda Item:	9.3.3
Source: 	LG Electronics
Title: 	Discussion on CLI handling
Document for:	Discussion and decision

Summary
In this contribution, we have discussed on potential enhancements on CLI handling. From the discussion, we obtained following proposals and observations;

Uplink resource muting for PUSCH
Proposal 1. PUSCH-MutingResources can be configured across SBFD/non-SBFD symbol and only within SBFD symbol are valid.
Proposal 2. For the following conditions, RRC configured UL resource muting is invalid.
For PUSCH repetition type B, number of symbols for actual repetition is less than X.
Proposal 3. Support Alt-4 (i.e., When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, UL resource muting is not applied in the PUSCH symbol containing PT-RS.)
Proposal 4. If the BW of PUSCH-MutingResources includes PUSCH but entire indicated symbols does not include that of the PUSCH, UL resource muting is applied.
Proposal 5. When the BW of the PUSCH is not fully indicated by PUSCH-MutingResources, UL resource muting is not applied to the PUSCH.
Proposal 6. UL resource muted PUSCH is considered as a semi-static event when it is configured with DMRS bundling.

L1 based UE-to-UE CLI measurement and reporting
Proposal 7. The CSI reference resource for CLI reporting is determined by NZP CSI-RS resources configured within the triggered report configuration. 
The existing CSI reference resource definition in section 5.2.2.5 of TS 38.214 is reused.
Proposal 8. The resources configured for the L1 based CLI measurement and report are counted for the active number of CSI-RS resources.

TDoc file unavailable

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

Agenda Item:	9.3.3
Source:	Spreadtrum, UNISOC
Title:	Discussion on CLI handling
Document for:	Discussion and decision

Conclusion
In this contribution, we discussed the potential normative work for CLI handling. The conclusion and proposals are given below:
Proposal 1: UL resource muting cannot be applied in non-SBFD symbols.
Proposal 2: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, UL resource muting is not applied in the PUSCH symbol containing PT-RS.
Proposal 3: Support Alt.2: Same default beam rules as AP CSI-RS resource defined in 38.214 can be applied to AP CLI SRS-RSRP or CLI-RSSI resource.
Proposal 4: The valid symbol type for CSI derivation configured in CSI-ReportConfig is not applicable for L1 UE-to-UE CLI measurement and reporting.
UE shall perform L1 UE-to-UE CLI measurement only in SBFD symbols 
Proposal 5: No special handling is needed when the largest measurement is out of range.

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

Agenda Item:	9.3.3
Source:	Samsung
Title:	Cross-link interference handling for SBFD
Document for:	Discussion

Conclusion
In this contribution, we made the following observations and proposals for UL resource muting for PUSCH:
Proposal 1: UL resource muting can be applied in non-SBFD symbols.
Observation 1: Alt-3 can result in new/additional non-legacy PT-RS patterns due to puncturing half of the PT-RS samples. This is out-of-scope as by approved Rel-19 WID objectives.
Proposal 2: Do not introduce any new/additional PT-RS patterns in Rel-19.
Proposal 3: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, support:
Alt-4: UL resource muting is not applied in the PUSCH symbol containing PT-RS.
Proposal 4: UL resource muting is not applied to PUSCH allocations <7 symbols.
Proposal 5: Support of UL muting on PUSCH symbols that can carry UCI is an optional UE capability in Rel-19 SBFD.
Proposal 6: When the UE does not indicate support for UL muting on PUSCH symbols that can carry UCI, and the UE determines presence of UCI on a configured/indicated UL muting symbol, the UE does not apply the UL resource muting in the symbol.
Proposal 7: UL resource muting is not applied to PUSCH carrying UCI-only payload.

In this contribution, we made the following proposals for L1 based UE CLI measurement/reporting:
Proposal 8: The CLI-RSSI measurement resource type#2 is counted as two L1 CLI-RSSI measurement resource type#1.
Proposal 9: The maximum configurable number of L1 CLI-RSSI measurement resources in CLI-RSSI-MeasurementResourceSet is same as maxNrofCLI-RSSI-Resources-r16.
Proposal 10: The supported number of CLI-RSSI measurement resources is subject to UE capability.
Proposal 11: The maximum configurable number of L1 SRS-RSRP measurement resources in SRS-RSRP-MeasurementResourceSet is same as value of maxNrofSRS-RSRP-Resources-r16.
Proposal 12: The supported number of SRS-RSRP measurement resources is subject to UE capability.
Proposal 13: Down-select from the following 2 options
Option 1: the UE doesn’t expect to be configured for Rel-16 L3 CLI reporting and Rel-19 L1 reporting.
Option 2: when the UE is configured for both Rel-16 L3 CLI reporting and Rel-19 L1 reporting, the UE expects to be configured with a maximum number of CLI-RSSI or SRS-RSRP measurement resources according to the reported Rel-19 UE capability.
Proposal 14: If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for aperiodic CLI reporting and the first symbol of the aperiodic SRS-RSRP measurement resource or CLI-RSSI measurement resources is smaller than the UE reported threshold beamSwitchTiming, support Alt.2.
Proposal 15: The slot offset between the slot containing the DCI that triggers a set of aperiodic SRS-RSRP resources and the slot in which the SRS-RSRP resource set is measured shall not be smaller than 1.

3GPP TSG RAN WG1 #121			R1-2503625
St Julian's, Malta, May 19th – 23rd, 2025
                                   
Agenda Item:	9.3.3
Source:	InterDigital, Inc.
Title:	Discussion on CLI handling for SBFD operation
Document for:	Discussion and Decision

Conclusion
In this contribution, we discussed issues on CLI mitigation aspects in SBFD systems. From the discussions, we made following observations and proposals:
2.1 L1-based UE-to-UE CLI measurement and reporting
2.1.1 Configuration of CLI measurement resources and reporting
Proposal 1. For frequency resource allocation of a CLI-RSSI, the UE reports a capability for the supported maximum number of resources for measurement resource type#1 and measurement resource type#2 separately. 
Proposal 2. For frequency resource allocation of a CLI-RSSI, the network configures measurement resources for each of the resource measurement types separately, up to the maximum number of supported resources reported by the UE. 
2.1.2 Subband and edge-specific measurement and reporting
Observation 1. Inter-subband UE-to-UE CLI measurement in SBFD DL subbands based on measuring over configured RB resources and averaging may result in down-estimation, as the subband-edge RBs experience higher CLI compared to RBs in the middle of the subband. 
Proposal 3. In UE-to-UE CLI-RSSI measurement techniques within active DL BWP, support measuring and reporting delta-CLI-RSSI based on differences in measured CLI-RSSI in subband-edge or guard-bands with measured CLI-RSSI in the middle of the DL subband. 
2.1.3	Beam aspects for CLI-based measurement and reporting
2.1.3.1	Triggers for CLI measurements and reporting
Observation 2. Since a general CSI/beam reporting in NR is not based on dynamic CLI-related information, a victim UE may unpredictably experience DL performance degradation if a UE-to-UE CLI occurs especially when an aggressor UE is served by a different serving gNB/TRP. 
Proposal 4. Support a conditional CLI handling behaviour based on monitoring the beams at the victim UE side, where the condition can at least include a case when the victim UE detects a PDSCH reception failure, which initiates a CLI measurement/reporting for a subband switching to avoid the CLI.
Observation 3. Transmitting and monitoring other UE’s SRS can help UE in the following aspects to be considered: 
Preventive aspects, that is determining the victim and aggressor UEs beam pairs to be avoided.
Beam pairing aspects, that is determining the gNB and victim UE beam pairs to be used based on directional CLI from the aggressor UEs. 
Proposal 5. Support UE configurations to enable CLI-based joint beam-sweeping, where the UE may determine and report the most favourable beam pairing(s) between the gNB and the victim UE in consideration of minimizing the measured CLI from the aggressor UEs.
2.1.3.2	Further enhancements for scheduling based on directional CLI reporting
Observation 4. Restricting one or more UL beam directions at the aggressor UE due to causing CLI on victim UEs, throughout all occasions of a configured UL transmission, could degrade the UL performance, as the aggressor UE may be restricted to transmit based on suboptimal UL beam directions.
Observation 5. Restricting one or more UL beam directions at the aggressor UE due to causing CLI on victim UEs, throughout all occasions of a configured UL transmission, could be unnecessary as the respective victim UEs may not be scheduled for DL reception in all corresponding configured UL occasions.
Proposal 6. Support methods to restrict UL beam directions for a configured UL transmission at an aggressive UE based on scheduled victim UEs, that is only for the occasions that a respective victim UE is scheduled for DL reception.
Observation 6. An aggressor UE can be configured with a first UL beam direction and a second candidate UL beam direction, where the first UL beam direction can be used in case no CLI is caused, and the second candidate UL beam direction can be used in case CLI is caused. 
Proposal 7. Support CLI mitigation techniques based on configuring a second candidate UL beam direction at the aggressor UE to be used in case the UL transmission based on the first UL beam direction could cause CLI to other UEs.
2.2 UL resource muting for PUSCH
Proposal 8. Do not support UL resource muting in non-SBFD symbols in NR Release-19.

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

Source:                Tejas Networks Ltd.
Title:                     Discussion on gNB-gNB CLI handling 
Agenda Item:       9.3.3
Document for:     Discussion and decision

Conclusion
In this contribution, we discuss about CLI handling with the following proposals and observations.

Proposal 1: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, we support Alt-3.
Alt-3
For PT-RS insertion in a block of  samples prior to transform precoding
 and  are determined as legacy from 38.214 Table 6.2.3.2-1
PT-RS sample positions are determined as legacy, but only for the first  groups
Note: After PT-RS insertion, all of the mathematically equivalent DFT Options 1, 2A, and 2B from the RAN1#120 agreement are applicable, where the choice is up to UE implementation.

Proposal 2: Support UL resource muting for the retransmission if UL resource muting is done for new data transmission for that PUSCH.
Proposal 3: Support PUSCH carrying certain UCI type with high priority, UL resource muting is not applied.

Proposal 4: Support the UL resource muting for each of the PUSCH transmission of multi-PUSCH scheduled by a single DCI can be turned ON/OFF using their TDRA field in DCI

Proposal 5: The UL resource muting can be turned ON/OFF dynamically using TDRA field in DCI. Hence no conditional check required for following conditions,   
Condition 1: When the number of PUSCH symbols is less than threshold, UL resource muting is not applied
Condition 2: If the scheduled PUSCH uses a MCS lower than certain reference MCS index, UL resource muting is not applied
Condition 3: When the number of scheduled RBs is less than threshold, UL resource muting is not applied
Condition 4: When the number of DMRS symbols is larger than threshold, UL resource muting is not applied

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

Agenda item:		9.3.3
Source:		Ofinno
Title:			Discussion on CLI handling
Document for:	Discussion and Decision

Conclusion
This contribution has discussed the remaining issues related to the physical layer aspects of CLI handling. The following are our proposals: 
Proposal 1. For an aperiodic CLI report based on aperiodic CLI measurement resources, a UE does not expect to be configured with a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for AP CLI and the first symbol of the aperiodic CLI resources is smaller than the UE reported threshold beamSwitchTiming.
Proposal 2. L1 UE-to-UE CLI measurement is configured within SBFD symbols. 
Proposal 3. For the newly introduced UE feature “FDMed reception of DL signals/channels and L1 SRS-RSRP measurement resource”, clarify that PRS is included for the “DL signals/channels”.

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

Source:	CATT
Title:	Discussion on CLI handling for NR duplex evolution
Agenda Item:	9.3.3
Document for:	Discussion and Decision

Conclusions 
In this contribution, we provide our views on CLI handling schemes with the following proposals.
Proposal 1： Support to apply UL muting on non-SBFD symbol based on gNB’s per cell indication.
Proposal 2: If an UL muting symbol overlaps with a symbol containing PT-RS for a PUSCH and when transform precoding is enabled for the PUSCH, PT-RS is prioritized, i.e., UE does not apply UL resource muting in the symbol.
Proposal 3：For UL muting applied for UL TBoMS, no additional specification impact is needed for the index of the starting coded bit in a slot, except the first slot.
Proposal 4: Support multiple measurement resources configured for one L1-CLI report.Maximum number of CLI-RSSI measurement resources and CLI-SRS measurement resources are 64 and 32 respectively per report.
Proposal 5: Support to configure L3 and L1 UE-to-UE CLI measurement resources in the same slot.
Proposal 6: The slot offset between the slot containing the DCI that triggers a set of aperiodic SRS-RSRP resources and the slot in which the SRS-RSRP resource set is measured shall not be smaller than 1.
Proposal 7: UE does not expect to be configured with a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for AP CLI and the first symbol of the aperiodic CLI SRS-RSRP or CLI-RSSI resources is smaller than the UE reported threshold beamSwitchTiming.
Proposal 8: For L1-CLI differential measurement report, if the number of reported L1-SRS-RSRP measurement resources is M and the number of L1-SRS-RSRP measurements which are out of range is X (X<=M)
An “out of range” indicator corresponding to a codepoint mapping to “infinity”  is reported for one of the X L1-SRS-RSRP measurement : 7 bits 
A list of indications are reported for each of the X-1 L1-SRS-RSRP measurement: (X-1)*4bits
DIFFRSRP_0 is used to indicate each of the X-1 L1-SRS-RSRP measurement result(s) which is out of range.
Proposal 9: For collision between L1-CLI measurement and DL reception, consider the handling scheme used for L3 CLI measurement as starting point.
Proposal 10: Keep the existing number (i.e., 64) of CLI-RSSI measurement resources.

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

Source: 	CMCC
Title:	Discussion on CLI handling
Agenda item:	9.3.3
Document for:	Discussion & Decision

Conclusions
In this contribution, we discuss the UL resource muting for PUSCH and L1 based UE-to-UE CLI measurement and reporting, and we have the following observations and proposals.
UL resource muting for PUSCH
Observation 1: For SBFD Deployment Case 3, gNB-gNB intra-subband CLI dominates the interferences. The interference covariance matrix experienced by the victim gNB is impacted by the Tx beamforming of aggressor gNB in the same REs of PUSCH.
Observation 2: For SBFD Deployment Case 1, gNB-gNB inter-subband CLI dominates the interferences. The gNB-gNB inter-subband CLI is independent of Tx beamforming for individual UE when there are multiple UEs in the DL subband(s) of aggressor gNBs with different Tx beamforming. Instead, the gNB-gNB inter-subband CLI characteristics experienced by the victim gNB are mainly impacted by the number of allocated DL RBs in DL subband(s) of aggressor gNBs.
Proposal 1: For UL transmissions across different slots with Configuration 2, UL resource muting only apply to SBFD symbol(s).
Proposal 2: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, support Alt-3.
Alt-3
For PT-RS insertion in a block of  samples prior to transform precoding
 and  are determined as legacy from 38.214 Table 6.2.3.2-1
PT-RS sample positions are determined as legacy, but only for the first  groups
Note: After PT-RS insertion, all of the mathematically equivalent DFT Options 1, 2A, and 2B from the RAN1#120 agreement are applicable, where the choice is up to UE implementation
L1 based UE-to-UE CLI measurement and reporting
Proposal 3: A UE does not expect to be configured with a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for AP CLI and the first symbol of the aperiodic CLI SRS-RSRP or CLI-RSSI resources is smaller than the UE reported threshold beamSwitchTiming.
Proposal 4: For a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to ‘cli-SRS-RSRP’, if the number of reported L1-SRS-RSRP measurement resources is M, and the number of L1-SRS-RSRP measurements which are either >=-44dBm or infinity (infinity means UE cannot detect SRS due to too strong signal to measure) is X (X<=M), support the following Alt. 1:
Alt.1: The following are reported within one report
An indicator corresponding to a codepoint mapping to out-of-range (L1-SRS-RSRP >= -44 dBm) or infinity: 7 bits 
A list of “out-of-range” indications based on differential measurement reporting table are reported for each of the X-1 L1-SRS-RSRP measurement: (X-1)*4bits
A codepoint defined as ‘out-of-range’ is introduced in the differential measurement reporting table
For the M-X L1-SRS-RSRP measurements which are within the reporting range (L1-SRS-RSRP <-44Bm), a differential reporting method is adopted using -44dbm as the reference: (M-X)*4bits

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

Agenda item:	9.3.3
Source:	Xiaomi
Title:	Discussion on CLI handling for SBFD operation
Document for:	Decision

Conclusions
In this contribution, we provide our views on UE-to-UE CLI handling and UL resource muting for PUSCH. The following proposals are made based on our analysis:
Proposal 1: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, adopt Alt-4.
-	Alt-4
o	UL resource muting is not applied in the PUSCH symbol containing PT-RS
Proposal 2: UL resource muting should not be applied in non-SBFD symbols.
Proposal 3: The valid symbol type for CSI derivation configured in CSI-ReportConfig is applicable for L1 UE-to-UE CLI measurement and reporting. 
UE shall perform L1 UE-to-UE CLI measurement based on the valid symbol type configured in CSI-ReportConfig
Note: The valid symbol type configured in CSI-ReportConfig for L1 UE-to-UE CLI measurement and reporting is expected to be SBFD symbols
Proposal 4: If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for aperiodic CLI reporting and the first symbol of the aperiodic SRS-RSRP measurement resource or CLI-RSSI measurement resources is smaller than the UE reported threshold beamSwitchTiming, adopt Alt.1:
Alt.1: UE does not expect to be configured with a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for AP CLI and the first symbol of the aperiodic CLI SRS-RSRP or CLI-RSSI resources is smaller than the UE reported threshold beamSwitchTiming.
Proposal 5: No enhancement is needed to handle the case when largest CLI measurement is out of range.
Proposal 6: UE does not expect SRS-RSRP resource to be measured starts earlier than the triggering DCI.

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

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

Conclusion 
In this contribution, we discussed SBFD for NR duplex operation. Observations and Proposals are summarized as follows: 
Proposal 1:
For RACH configuration Option 2, support separate PREAMBLE_POWER_RAMPING_STEP
Proposal 2: 
For RACH configuration Option 2, if separate PREAMBLE_POWER_RAMPING_STEP values are configured for legacy-ROs and additional-ROs, the value ΔPrampup_requested,b,f,c​ used for Msg3 PUSCH power control is calculated based on the PREAMBLE_POWER_RAMPING_STEP corresponding to the RO type (legacy or additional) of the most recent PRACH transmission attempt.
Proposal 3:
Support separate msg3-DeltaPreamble for non-SBFD symbols and SBFD-symbols
Proposal 4: 
For SBFD-aware UEs and CFRA triggered by BFR or SI request, support one of the following for UE to determine the RO resource
New table can be defined for SBFD aware UE to determine the RO resource of SSB for PRACH transmission on SBFD symbols 
New column is added in PRACH Mask Index/msgA-SSB-SharedRO-MaskIndex/ssb-SharedRO-MaskIndex values table for SBFD aware UE to determine the RO resource of SSB for PRACH transmission on SBFD symbols 
gNB configure the applied symbol type (SBFD symbol or non-SBFD symbol or both) or RO Type for CFRA
Proposal 5:
The aspects below should be considered for SDT enhancements on SBFD symbols:
PUSCH allocation/configuration in the UL subband of SBFD symbols
Valid PO determination on SBFD symbols
The PO mapping relationship with SSB for PO in SBFD symbols 
Proposal 6:
 For failed PRACH attempts in SBFD slots, the UE will wait for dedicated UL slots to re-attempt PRACH. 

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

Source:	Panasonic
Title: 	Discussion on CLI handling
Agenda Item:		9.3.3
Document for:	Discussion

Conclusion
In this contribution, we made the following proposals. 
Proposal 1: To discuss whether UCI resource, UL muting resource and data can be multiplexed in one OFDM symbol.
Proposal 2: If UL resource muting is allowed in a symbol with UCI, to discuss whether the number of REs for UCI is based on the gain of the EPRE boosting.
Proposal 3: UL resource muting can be applied in non-SBFD symbols.
Proposal 4: UE should not expect to be simultaneously configured with L3 and L1 UE-to-UE CLI measurement resource.
Observation 1: In RAN4, “Infinity” for L3-based SRS-RSRP is reused for L1-based SRS-RSRP in absolute value.
Proposal 5: Whether to define a list of "out-of-range" indications based on the differential measurement reporting table is up to RAN4.
Observation 2: In RAN1, if the absolute value is infinity or out-of-range, it is necessary to discuss how the differential value is calculated.
Proposal 6: If absolute value is reported as Infinity or out-of-range (L1-SRS-RSRP >= -44 dBm), a differential reporting method should be adopted using -44 dBm as the reference. 

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

Agenda item:		9.3.3
Source:	Nokia, Nokia Shanghai Bell
Title:	Cross-link interference handling for duplex evolution
Document for:		Discussion and Decision

Conclusions
This document discusses the CLI handling in SBFD for both gNB-to-gNB and UE-to-UE. The following includes the list of observations and proposals made throughout the text.

Observations and proposals: 
Proposal 1:	If transform precoding is used, support Alt 4, UL resource muting is not applied in the PUSCH symbol containing PT-RS.
Proposal 2:	Allow the UL resource muting in non-SBFD symbols without any separate UE capability. No additional restriction for applying UL resource muting to only SBFD symbol is required.
Proposal 3:	Support the configuration of multi-port SRS-RSRP measurements for L1 UE-to-UE CLI.
Proposal 4:	Do not support for any limitation for slot offset for AP L1-SRS-RSRP measurement and reporting.
Proposal 5:	In case, the scheduling offset between the PDCCH triggering an aperiodic L1 CLI measurement and the aperiodic measurement resources is smaller than beamSwitchTiming, the same default beam rules as AP CSI-RS resource defined in 38.214 can be applied to AP CLI SRS-RSRP or CLI-RSSI resource (Alt.2).
Observation 1:	The SRS-RSRP_98 codepoint of Table 10.1.22.1.-1 is also re-used for L1 SRS-RSRP measurements.
Observation 2:	Reporting SRS-RSRP_98 (infinity) should be reserved for cases where the UE RF front-end is blocked, while reporting SRS-RSRP_97 should be used in case the UE measures an SRS-RSRP higher than 44 dBm.
Proposal 6:	gNB should not rely on the reported measurements if one of the L1-SRS-RSRP measurement resources is reported as “infinity”.
Proposal 7:	If optimizations for differential reporting with one or more measurement resources reported as infinity are needed, support Alt.2.
Proposal 8:	Support the valid symbol type for CSI derivation configured in CSI-ReportConfig is applicable for L1 UE-to-UE CLI measurement and reporting (Alt.2).
Proposal 9:	Support the configuration of L1 UE-to-UE CLI measurements and reporting for dynamic TDD operation. This is applicable to legacy and SBFD-aware UEs.
Proposal 10:	The CSI reference resource for L1 UE-to-UE CLI measurements resources (L1-SRS-RSRP and L1-CLI-RSSI) follows same principle as for CSI-RS and CSI-IM.
Proposal 11:	Extend the definition of valid downlink slot for CSI reference resource determination to also considers slots with SBFD symbols.
Proposal 12:	Update the current CLI-RSSI measurement definition in TS 38.215 to capture the L1-CLI-RSSI measurements that span across 2 DL sub-bands.
Observation 3:	CLI handing by limiting UE transmit power can be supported by network scheduling only when it is necessary instead of configuring separate p-Max values for SBFD and non-SBFD with semi-static offset.
Proposal 13:	Support the second PHR reporting for CLI handling in SBFD symbol.
Proposal 14:	Support additional ACLR reporting for CLI handling

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

Source:	ETRI
Title:		Discussion on CLI handling for SBFD operation
Agenda item:	9.3.3
Document for:	Discussion

Summary
In this contribution, the following observations and proposals were made for CLI handling for SBFD operation.
Observation 1: Whether to agree on the applicability of muting within non-SBFD symbols (i.e., UL symbols) should depend on whether gNB-to-gNB CLI actually occurs in those symbols.
Observation 2: To ensure accurate RSRP and channel measurement using CLI-RS, it is necessary to consider adjusting the aggressor UE’s transmission timing of CLI-RS and/or victim UE’s reception timing of CLI-RS.

Proposal 1: UL resource muting within non-SBFD symbols is not supported in Rel-19 SBFD.
Proposal 2: With dynamic ON/OFF control using the TDRA field in DCI, we believe there is no need to support Condition 1 (small number of symbols), Condition 2 (low MCS), and Condition 3 (small number of RBs).
Proposal 3: If transform precoding is enabled, we support Alt-4 that proposes not to apply UL resource muting in PUSCH symbols containing PT-RS.
Proposal 4: In case of a collision between PT-RS and a UL muting symbol, we propose considering either omitting one of them or shifting one of them to a different symbol.
Proposal 5: We propose discussing how/whether to address timing misalignment between CLI-RS and UL signals received by a gNB.
Proposal 6: It is necessary to investigate specification impacts for timing alignment issues for UE-to-UE CLI measurement and reporting (e.g., timing synchronization between victim UE and aggressor UE for CLI-RSRP measurement, victim UE’s two different reception timings for CLI-RS and DL).

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

Source:	OPPO
Title:	CLI handling in NR duplex operation
Agenda Item:	9.3.3
Document for:	Discussion and Decision

Conclusions 
In this contribution, we discuss the enhancements for CLI handling with following proposals and observations:
For UE-to-UE co-channel CLI handling: 
Proposal 1:  DL timing can be used for timing of CLI-RSSI measurement in UL subband.
Proposal 2: Support Alt-1 from RAN1 #120bis proposal for differential reporting of L1-SRS-RSRP, with the following modification. 
An indicator corresponding to a codepoint mapping to out-of-range (L1-SRS-RSRP >= -44 dBm) or infinity: 7 bits 
A list of “out-of-range” indications based on differential measurement reporting table are reported for each of the X-1 L1-SRS-RSRP measurement: (X-1)*4bits
A codepoint defined as ‘out-of-range’ is introduced in the differential measurement reporting table
One codepoint mapping to (L1-SRS-RSRP >= -44 dBm) but not infinity is introduced in the differential measurement reporting table. 
Another codepoint mapping to infinity (with the same RAN4 definition of “infinity”) is introduced in the differential measurement reporting table.
For the M-X L1-SRS-RSRP measurements which are within the reporting range (L1-SRS-RSRP <-44Bm), a differential reporting method is adopted using -44dbm as the reference: (M-X)*4bits

For gNB-to-gNB co-channel CLI handling: 
Proposal 3: The semi-static configuration of UL resource muting pattern is per UE, not per cell.
Proposal 4: When transform precoding is enabled, UL resource muting is not applied in the PUSCH symbol containing PT-RS.

Observation 1: For UL muting applied for UL TBoMS, the RAN1 #120bis agreement on the index of starting coded bit in a slot imposes no additional specification impact.  

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

Agenda Item:	9.3.3
Source:	Apple Inc.
Title:	Remaining issues on CLI handling
Document for:	Discussion/Decision

Conclusion
In this contribution, we shared our views on remaining issues about CLI handling. Based on what we discussed, the following proposals are made:
Proposal 1: The slot offset between a slot in which DCI triggering AP-CLI reporting ends and the slot in which SRS-RSRP measurement starts, including the effect of timing advance, shall not be smaller than 1 slot, in the smallest SCS between PDCCH carrying DCI and SRS-RSRP measurement resource.

Proposal 2: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, UL resource muting is not applied in the PUSCH symbol containing PT-RS.

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

Source:	Sharp
Title:	Cross-link interference (CLI) handling
Agenda Item:	9.3.3
Document for:	Discussion and Decision

Conclusion
In this paper, we discussed cross-link interference (CLI) management and proposed the following:
Proposal 1: Support including the TDRA field for turning the UL muting ON/OFF in the DCI format 0_x message that provides CG PUSCH Type 2 grant or schedules DG PUSCH.
Proposal 2: Support RRC indicating to the UE whether to expect the TDRA field for turning the UL muting ON/OFF.
Proposal 3: Consider dedicating a DCI message for the case of CG PUSCH Type 1 to communicate the TDRA field for turning the UL resource muting ON/OFF.
Proposal 4: Revoke the following agreement and replace it with a simple version that specifies to zero the  even or odd subcarriers on the symbol based on the indicated comb offset:

3GPP TSG RAN WG1 #121			    R1-2504393
St Julians, Malta, May 19th – 23rd, 2025
Agenda item:	9.3.3
Source: 	Qualcomm Incorporated
Title: 	Enhancements for CLI handling
Document for:	Discussion/Decision

Conclusion
Observation 1: Simulation for FR1 Urban Macro scenario with R18 study item simulation assumption with 2 clusters per cell, the SRS-RSRP for UEs with distance less than 50 meters and among those UEs, we can see more than 40% of UEs with distance < 50 meters, measure SRS-RSRP larger than -44 dBm, which is out of range of the measurement table.
Proposal 1: UE does not expect to be simultaneously configured with both L3 and L1 UE-to-UE CLI measurement resources, if UE supports both features.
Proposal 2: If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for aperiodic CLI reporting and the first symbol of the aperiodic SRS-RSRP measurement resource or CLI-RSSI measurement resources is smaller than the UE reported threshold beamSwitchTiming, support Alt. 2.
Proposal 3: If the number of reported L1-SRS-RSRP measurement resources is M and the number of L1-SRS-RSRP measurements which are out of range is X (X<=M), the following are reported within one report
An “out of range” indicator corresponding to a codepoint mapping to out-of-range (>= -44) or infinity: 7 bits 
A list of out-of-range indications based on differential measurement reporting table are reported for each of the X-1 L1-SRS-RSRP measurement: (X-1)*4bits
For the M-X L1-SRS-RSRP measurements which are within the reporting range, a differential reporting method is adopted using -44dbm as the reference: (M-X)*4bits
If the number of reported L1-CLI-RSSI measurement resources is M and the number of L1- CLI-RSSI measurements which are out of range is X (X<=M), the following are reported within one report
An “out of range” indicator corresponding to a codepoint mapping to out-of-range (>= -25) or infinity: 7 bits 
A list of out-of-range indications based on differential measurement reporting table are reported for each of the X-1 L1- CLI-RSSI measurement: (X-1)*4bits
For the M-X L1- CLI-RSSI measurements which are within the reporting range, a differential reporting method is adopted using -25dbm as the reference: (M-X)*4bits.
Proposal 4: RAN1 shall discuss to the slot offset between the slot containing the DCI that triggers a set of aperiodic CLI SRS-RSRP resources and the slot in which the SRS-RSRP resource set is measured:
Alt 1: Confirm the FFS that the slot offset between the slot containing the DCI that triggers a set of aperiodic SRS-RSRP resources and the slot in which the SRS-RSRP resource set is measured shall be more than or equal to 1 or 2 slot to compensate for the timing switching. 
Alt 2: Support a new UE capability to report the minimum slot offset value and the value can be per frequency range.
Proposal 5: Support CLI SRS-RSRP or CLI-RSSI measurements on SBFD symbols or non-SBFD symbols. 
Reuse valid symbol type configured in CSI-ReportConfig 
UE will measure in SBFD or non-SBFD only based on the valid symbol type, and skip/drop CLI resources in non-SBFD or SBFD symbols.
If valid symbol type is absent, default valid symbol type is SBFD symbols.
Proposal 6: Support UE does not expect to be configured L1-CLI-RSSI measurements resources in DL subband(s) (Method#1) and L1-SRS-RSRP (Method#2) on the same symbol
Proposal 7: Support UE does not expect to be configured with L1-CLI-RSSI measurements resources in UL subband(s) (Method#3) and L1-SRS-RSRP (Method#2) on the same symbol. 
Proposal 8: Support UE does not expect to be scheduled/configured with DL data channel/RS and L1-CLI-RSSI measurements resources in DL subband(s) (Method#1 for leakage measurement) on the same symbol.Proposal 8: For UL resource muting for PUSCH, RAN1 to discuss implicit rule whether to apply UL resource muting pattern based on PUSCH time and frequency allocation.
Proposal 9: Support Alt 4 that if an UL resource muting symbol overlaps with a symbol containing PT-RS for a PUSCH and transform precoding is enabled for the PUSCH, PT-RS is prioritized, i.e., UE does not apply UL resource muting in the symbol.
Proposal 10: Support UL muting can apply to SBFD symbols and non-SBFD symbols. gNB indicates to UE whether to apply UL resource muting on non-SBFD symbols or not.
If this indication field is absent, UE applies UL resource muting on SBFD symbols if SBFD symbols are configured.
If this field indication is absent, UE applies UL muting to F/U symbols if SBFD symbols are not configured
Proposal 11: Support if [ul-MutingIndicator] is absent for a TDRA entry indicated for the PUSCH transmission, UL muting is used for the PUSCH transmission.

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

Source:	NTT DOCOMO, INC.
Title:	Discussion on CLI handling
Agenda Item:	9.3.3
Document for: 	Discussion and Decision

Conclusion
In this contribution, we discussed potential enhancements on CLI handling for SBFD. Based on the discussion we made the following proposals.
Proposal 1: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, support Alt-3.
For PT-RS insertion in a block of  samples prior to transform precoding
 and  are determined as legacy from 38.214 Table 6.2.3.2-1
PT-RS sample positions are determined as legacy, but only for the first  groups
Note: After PT-RS insertion, all of the mathematically equivalent DFT Options 1, 2A, and 2B from the RAN1#120 agreement are applicable, where the choice is up to UE implementation

Proposal 2: A UE can be configured to apply UL resource muting in non-SBFD symbols.
The configuration of enable/disable UL muting on non-SBFD symbols is applicable for all types of PUSCH transmissions, including single-PUSCH scheduled by DCI without repetition, PUSCH repetitions, multi-PUSCH scheduled by single DCI, CG PUSCH, and PUSCH TBoMS.

Proposal 3: The valid symbol type for CSI derivation configured in CSI-ReportConfig is applicable for L1 UE-to-UE CLI measurement and reporting.

Proposal 4: For out-of-range or infinity reporting for L1 SRS-RSRP reporting, Alt 1 is preferred.
If the number of reported L1-SRS-RSRP measurement resources is M, and the number of L1-SRS-RSRP measurements which are either >=-44dBm or infinity (infinity means UE cannot detect SRS due to too strong signal to measure) is X (X<=M),
An indicator corresponding to a codepoint mapping to out-of-range (L1-SRS-RSRP >= -44 dBm) or infinity: 7 bits 
A list of “out-of-range” indications based on differential measurement reporting table are reported for each of the X-1 L1-SRS-RSRP measurement: (X-1)*4bits
A codepoint defined as ‘out-of-range’ is introduced in the differential measurement reporting table
For the M-X L1-SRS-RSRP measurements which are within the reporting range (L1-SRS-RSRP <-44Bm), a differential reporting method is adopted using -44dbm as the reference: (M-X)*4bits

Proposal 5: UE does not expect to be configured with a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for AP CLI and the first symbol of the aperiodic CLI SRS-RSRP or CLI-RSSI resources is smaller than the UE reported threshold beamSwitchTiming, i.e. Alt 1 is supported.

Proposal 6: Number of antenna ports for L1 SRS-RSRP measurement resource can be 1 or larger than 1. 

Proposal 7: If UE is not capable of the capability of FDM-ed DL reception and L1 SRS-RSRP measurement, support collision handling between FDM-ed DL reception and L1 SRS-RSRP measurement similar to physical DL and UL channel collision. 
Case #1: AP L1 SRS-RSRP measurement resource vs. configured DL reception
prioritize AP L1 SRS-RSRP measurement 
Case #2: P/SP L1 SRS-RSRP measurement resource vs. dynamic DL reception
prioritize dynamic DL reception
Case #3: P/SP L1 SRS-RSRP measurement resource vs. configured DL reception
Not expect
Case #4: AP L1 SRS-RSRP measurement resource vs.  dynamic DL reception
Not expect

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


Source: Google
Title:	On CLI handling for SBFD operation
Document for: Discussion and Decision

Conclusion
In this contribution, we have presented several proposals to specify the support of the gNB-to-gNB CLI and the UE-to-UE CLI handling. We made the following proposals: 

Support Alt-2 for scenarios where the scheduling offset between the triggering PDCCH last symbol (for aperiodic CLI reporting) and the first symbol of aperiodic SRS-RSRP or CLI-RSSI measurement resources is less than the UE reported beamSwitchTiming threshold:
 Alt.2: Same default beam rules as AP CSI-RS resource defined in 38.214 can be applied to AP CLI SRS-RSRP or CLI-RSSI resource.

If a multiple ports SRS resource is configured for L1-SRS-RSRP measurement, the UE can measure/report the L1-SRS-RSRP for each SRS port or can be configured with the antenna port to measure.

Study the behaviour of the victim UE when the SRS transmission is dropped by the aggressor UE, e.g. due to collision with other UL signals.

If a vicitm UE is to receive a DL signal and is also expecting an SRS transmission from  agressor UE for UE-to-UE CLI measurements based on different QCL -TypeD, it cannot receive both the SRS and the DL signal simultaneously. Some solutions could be specified:
Dropping SRS
Dropping DL signal
Follow priority rules

If not discussed in RAN1, send LS to RAN4 to address the collision handling between L1 SRS-RSRP measurement or L1 CLI-RSSI and other UL transmission(s) or DL reception(s) and if any scheduling restrictions needed. 

To avoid impact on pi/2 BPSK modulation for PUSCH/PT-RS symbols with UL muting, the first  complex symbols are selected for the frequency mapping

Clarify whether PUSCH repetitions with OCC can overlap with UL muting symbols and if they need to have the same muting patterns. 

At least when when the ratio the muted REs in a PUSCH is large, the number of REs allocated for PUSCH within a PRB  in the TBS formula has to be adjusted to account for the muted REs.

For the case of initial transmission with no muted REs and the HARQ retransmission(s) with muted REs and vice versa (and also for PUSCH repetitions), the TBS determination can be based on the initial transmission.

PT-RS are not transmitted on symbols with DFT-s-OFDM when UL resource muting is applied on the OFDM symbol

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

Source: 	CEWiT
Title:	Discussion on CLI Handling
Agenda Item:	9.3.3
Document for:	Discussion and Decision



1. 

Conclusion
The following observation and proposals are made in the contribution:
Observation 1: Regarding applicability of valid symbol type for CSI derivation for CLI measurement
Alt 1 is restrictive and can be achieved usig Alt 2 
If BS configures the valid symbol type for measurement as SBFD whenever the report quantity is CLI-RSSI or CLI SRS-RSRP.
Alt 2 is more generic and flexible
Proposal 1: Alt 2 is supported
Valid symbol type for CSI derivation configured in CSI-ReportConfig is not applicable for L1 UE-to-UE CLI measurement and reporting.
Proposal 2: Time restriction for measurement is supported for L1 UE to UE CLI measurement and reporting by using timeRestrictionForInterferenceMeasurements.
Valid symbol type for CSI derivation configured in CSI-ReportConfig is not applicable for L1 UE-to-UE CLI measurement and reporting.
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: Alt. 2 is supported for reporting out of the range CLI measurements.
4. 

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

Agenda Item:	9.3.3
Source:	Ericsson
Title:	SBFD CLI Handling 
Document for:	Discussion, Decision
1	

Conclusion
Based on the discussion in the previous sections we propose the following:
Proposal 1	When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, RAN1 to support Alt-3 for PTRS insertion from the agreement in RAN1#120bis.
Proposal 2	UL resource muting in non-SBFD symbols can be up to gNB configuration for the PUSCH repetition case.
Proposal 3	Instead of Alt-1 and Alt-2 in the above, RAN1 should agree that UE measures CLI based on the configuration provided in CSI-ResourceConfig (indicated by CSI-ReportConfig). This means that there is no need to include a parameter indicating valid symbol type in CSI-ReportConfig which indicates resources for L1 CLI measurements.
Proposal 4	Support Proposal 2-6 from RAN1 #120bis: A UE does not expect to be configured with L3 and L1 UE-to-UE CLI measurement resources simultaneously in the same slot.
Proposal 5	Support Proposal 2-7 from RAN1 #120bis: For SRS-RSRP measurement resource configuration, the number of antenna ports is 1.
Proposal 6	If the number of reported L1-SRS-RSRP measurement resources is M, and the number of L1-SRS-RSRP measurements which are either >=-44dBm or infinity (infinity means UE cannot detect SRS due to too strong signal to measure) is X (X<=M),
	An indicator corresponding to a codepoint mapping to out-of-range (L1-SRS-RSRP >= -44) or infinity: 7 bits
	For the M-1 L1-SRS-RSRP measurement, a single codepoint is adopted from the differential reporting table for all the M-1 measurements which indicates to the gNB that all the differential reports are invalid. (M-1)*4bits.
Proposal 7	If the scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for aperiodic CLI reporting and the first symbol of the aperiodic SRS-RSRP measurement resource or CLI-RSSI measurement resources is smaller than the UE reported theshold beamSwitchTiming, down-select to Alt-1 from the RAN1#120 agreement:
Alt.1: UE does not expect to be configured with a scheduling offset between the last symbol of the PDCCH carrying the triggering DCI for AP CLI and the first symbol of the aperiodic CLI SRS-RSRP or CLI-RSSI resources is smaller than the UE reported threshold beamSwitchTiming.
 

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

Agenda Item: 	9.3.3
Source: 	Sony 
Title: 	SBFD CLI handling
Document for: 	Discussion / decision

Conclusion
In this contribution, we discuss some the CLI handling schemes for SBFD, and we observe the following:
Observation 1: Since CG-PUSCH Type 1 is not scheduled by DCI, UL muting pattern cannot be dynamically turned ON/OFF for CG-PUSCH Type 1.  


We therefore propose the following:
Proposal 1: UL muting is not applied for every CG-PUSCH occasion, if the percentage of UL muted REs relative to REs carrying PUSCH modulated symbols after REs carrying UCI bits are multiplexed, is larger than a threshold and the PUSCH has a high L1 priority.

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

Agenda Item:	9.3.3
Source:	Moderator (Huawei)
Title:	Summary #1 of CLI handling
Document for:	Discussion and Decision

Conclusion
There is no RAN1 consensus to support two new report quantities {‘cli-RSSI-measurement-resource-bitmap’, ‘cli-SRS-RSRP-measurement-resource-bitmap’} to reportQuantity 

Agreement
LS on impact on transmit signal quality/MPR requirement is agreed in R1-2503089.
Reply LS on L1 measurement is agreed in R1-2503090.

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

Agenda Item:	9.3.3
Source:	Moderator (Huawei)
Title:	Summary #2 of CLI handling
Document for:	Discussion and Decision

Conclusion
There is no RAN1 consensus to support two new report quantities {‘cli-RSSI-measurement-resource-bitmap’, ‘cli-SRS-RSRP-measurement-resource-bitmap’} to reportQuantity 

Agreement
LS on impact on transmit signal quality/MPR requirement is agreed in R1-2503089.
Reply LS on L1 measurement is agreed in R1-2503090.