TDoc file unavailable

3GPP TSG RAN WG1 #120bis			R1-2501754
Wuhan, China, April 7th – 11th, 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 UL muting applied to UL TBoMS, Option 2 (i.e., 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and considering the muted REs) is supported for determining the index of the starting coded bit in a slot, as it aligns with the original principle used to determine the starting bit within the TBoMS and introduces no specification impact.

Proposal 3. 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.
Any of DMRS/PTRS collides with resource indicated by UL resource muting

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. For dynamic ON/OFF indication of UL resource muting, single bit of TDRA with fixed location in DCI is used.

Observation 1. UE cannot maintain power consistency during entire PUSCH repetition when any of PUSCH is muted.
Proposal 7. 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
Observation 2. The L1 based CLI measurement and reporting is based on the short-term measurement of CLI and report it in timely manner.

Proposal 8. Reuse aperiodicTriggeringOffset for both of SRS-RSRP and CLI-RSSI.

Observation 3. In order to satisfy the intention for which L1 based CLI measurement and report was introduced, UE always measures the latest resource to derive a report.

Proposal 9. 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 10. The resources configured for the L1 based CLI measurement and report are counted for the active number of CSI-RS resources.

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

Source:	vivo
Title:	Discussion 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, PTRS is prioritized, i.e., the UE does not apply UL resource muting in the symbol.
Proposal 2: For UL muting applied for UL TBoMS, the index of the starting coded bit in a slot, except the first slot, within the 𝑁𝑠 slots allocated for the transmission of TB processing over multiple slots is determined according to Section 6.2.5, TS38.212 as follows
and H is determined based on option 2
Option 2: 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and considering the muted REs
Note: No specification impact for option 2.
Proposal 3: 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 4: 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, 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 #120bis                           R1-2501867
Wuhan, China, April 7th – 11th, 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:
Observation 1: PTRS pattern in UL resource muting symbol is different from that in symbols without UL resource muting when transform precoding is enabled. 
Proposal 1: For UCI rate matching, to determine the number of coded modulation symbols per layer for UCI transmission on PUSCH repetition type B, the number of coded modulation symbols per layer for UCI on PUSCH is calculated based on  and after excluding the UL muting resource.
Proposal 2: For data and control multiplexing, to determine the available number of resource elements for data/UCI transmission in an OFDM symbol, 
 in section 6.2.7, TS 38.212 is the set of resource elements after excluding the UL muting resource. 
 in section 6.2.7, TS 38.212 is the set of resource elements after excluding the UL muting resource. 
Proposal 3: Support Option 2: 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and considering the muted REs.
Proposal 4: 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 5: Maximum number of CLI resource set per configuration should be defined in CSI-ResourceConfig.
Proposal 6: Maximum number of CLI resource per resource set in Rel-16 can be reused in new CLI resource set. 
Proposal 7: The available slot offset configured in legacy SRS-ResourceSet is not reused for SRS-RSRP measurement.
Proposal 8: 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 9: Confirm the following working assumption
Working assumption
For L1 based CLI measurement and reporting, the following is adopted
For L1 SRS-RSRP, a 7-bit value in the quantization range [-140, -44] dBm with 1dB step size, and the differential L1 SRS-RSRP is quantized to a 4-bit value. The differential L1 SRS-RSRP value is computed with 2 dB step size with a reference to the largest measured L1 SRS-RSRP value.
For L1 CLI-RSSI, a 7-bit value in the quantization range [-100, -25] dBm with 1dB step size, and the differential L1 CLI RSSI is quantized to a 4-bit value. The differential L1 CLI-RSSI value is computed with 2 dB step size with a reference to the largest measured L1 CLI-RSSI value.
Proposal 10: No special handling is needed when the largest measurement is out of range.
Proposal 11: The valid CLI reference resource slot should comprises at least one higher layer configured SBFD or flexible symbol and not fall within a configured measurement gap.

3GPP TSG RAN WG1 #120bis			R1-2501909
Wuhan, China, 07th - 11th April 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 determined as legacy, but with  replaced by   in 38.211 Table 6.4.1.2.2.2-1
Proposal 2: When UL resource muting is applied to the TBoMS transmission, the muted RE should be considered for the bit selection in rate matching. 
Proposal 3: 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
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: A new MAC CE should be introduced for activating or deactivating the semi-persistent CLI-RSSI measurement resource.
Proposal 8: There should be no need to configure the reference serving cell for the CLI-RSSI measurement resource.
Proposal 9: The available slot offset should not be supported for aperiodic SRS for CLI measurement.
Proposal 10: 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 11: For measurement timing, the Rel-16 method should be adopted as the baseline and further discuss whether the enhancements are needed.
Proposal 12: 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 13: The parameters of CLI measurement resources should be included in CSI-ResourceConfig and an example is shown below.

Proposal 14: The parameters of the measurement resources for aperiodic reporting should be included in CSI-AssociatedReportConfigInfo and an example is shown below.

Proposal 15: The following parameters should be introduced for CLI.

3GPP TSG RAN WG1 #120bis			R1-2501930
Wuhan, China, April 7th – 11th, 2025
                                   
Agenda Item:	9.3.3
Source:	InterDigital, Inc.
Title:	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. 
Proposal 3. For clarification of the CLI-RSSI measurement and reporting configuration, add an indication of which Method (Method#1 vs Method#3) and/or Resource Types in the CLI-RSSI-MeasurementResourceSet or CSI-ReportConfig, and clarify the configuration that should be considered as error case, if any.
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 4. 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 5. 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 6. Support UE configuration where the UE is indicated one or more RX beam(s) for CLI resources (e.g., L1-SRS-RSRP), e.g., by indication of a CSI resource indicator (CRI) from the network for semi-persistent and periodic reporting. 
Proposal 7. Support UE configurations to enable CLI-based beam-sweeping, where the UE may determine and report the most and least favourable beam(s) or beam pairing(s) between the victim and aggressor UEs.
Proposal 8. Support the UE determination of beam pairing between (victim) UE and gNB based on directional CLI measurements and reports.
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 9. 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 10. 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 11. Do not support UL resource muting in non-SBFD symbols in NR Release-19.

3GPP TSG RAN WG1 #120bis		R1-2501991
Wuhan, China, April 7th – 11th, 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 observation and proposals.
Observation 1: L1-CLI computation delay requirement depends on whether to support configuration of ‘typeD’ QCL assumption for measurement resource.
Proposal 1: 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 2: For UL muting applied for UL TBoMS, the H used for determining the index of the starting coded bit in a slot, except the first slot, is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and considering the muted REs.
Proposal 3: 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 4: 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: 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 6: For collision between L1-CLI measurement and DL reception, consider the handling scheme used for L3 CLI measurement as starting point.
Proposal 7: Keep the existing number (i.e., 64) of CLI-RSSI measurement resources.

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

Source:                Tejas Networks Pvt. 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.
Observation 1:  In case of alternative-1 the PT-RS density will increase for the symbol containing PT-RS with UL resource muting as compared to the symbol containing PT-RS without UL resource muting when transform precoding is enabled.

Observation 2: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, if we replace  with  in Table 6.2.3.2-1 of 38.214, the PTRS density does not remain consistent with respect to the symbol containing PTRS without UL resource muting.

Proposal 1: When transform precoding is enabled and an UL muting symbol overlaps a symbol containing PT-RS, we support the PT-RS sample positions are determined as legacy, but only the first  groups are used for PT-RS transmission.

Proposal 2:  For UL muting applied for UL TBoMS, the index of the starting coded bit in a slot, except the first slot, within the 𝑁𝑠 slots allocated for the transmission of TB processing over multiple slots is determined according to Section 6.2.5, TS38.212 as follows

and H is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and assuming no muted REs.

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

Proposal 5: 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 6: 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 #120bis										   		R1-2502086
Wuhan, China, April 7th – 11th, 2025
Source:	NEC
Title:	CLI Handling for NR duplex operation
Agenda item:	9.3.3
Document for:   Discussion and decision
1 

Conclusion
Based on the discussion in the previous sections, this contribution is concluded with the following proposals:
Proposal 1: The configuration information for UE-to-UE L1 CLI measurement should include a list of TCI states for beam-based CLI measurements.
Proposal 2: 
A unified design for CLI RS for gNB-to-gNB and UE-to-UE measurement should be considered to reduce the RS overhead. The RS for UE-UE and gNB-gNB interference measurement can be orthogonal in order to achieve this goal.
Proposal 3: 
For L1 based SRS-RSRP reporting, the following options are considered
•	Option 3: UE is configured to report the X most interfering or Y least interfering SRS-RSRP measurement resources in one report.
•	Option 4: UE is configured to report the X most interfering and Y least interfering SRS-RSRP measurement resources in one report.

For L1 based CLI-RSSI reporting, the following options are considered
•	Option 3: UE is configured to report the X most interfering or Y least interfering CLI-RSSI measurement resources in one report.
•	Option 4: UE is configured to report the X most interfering and Y least interfering CLI-RSSI measurement resources in one report.
Proposal 4: 
For L1 UE-to-UE CLI measurement and reporting, support the following new report quantity: 
-	A bitmap corresponding to a list of SRS-RSRP measurement resource indices with L1-SRS-RSRP above a given threshold (Th1), and/or a bitmap corresponding to a list of SRS-RSRP measurement resource indices with L1-SRS-RSRP below a given threshold (Th2)
o	The measurement resource index lists may be reported via separate bitmap or via joint coding.
o	The two thresholds (Th1 and Th2) can be configured via higher-layer parameters.
Proposal 5: 
For L1 SRS-RSRP measurement, 
•	Alt 1: Reuse the timing for Rel-16 L3 based SRS-RSRP measurement, i.e., a constant offset relative to the downlink reference timing in the serving cell shall be applied. The constant offset value is derived by UE implementation and shall be at least Tc*NTA_offset.
Proposal 6:
Consider the CSI report size enhancement for SBFD operation and different types of CLI interference.
Consider the non-uniform CLI bandwidth in inter-subband CLI measurement/report. 
Proposal 7:
Differentiation of the BFR caused by CLI with the beam blockage is needed. 
BFI triggered CLI measurement and report can be defined.  
Dedicated PRACH/SR resources can be configured to UE to report the BF caused by CLI.

4 

3GPP TSG RAN WG1 #120bis			R1-2502159
Wuhan, China, April 7th – 11th, 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: If an UL muting symbol overlaps with a symbol containing PT-RS for a PUSCH and when transform precoding is enabled for the PUSCH, for PT-RS insertion prior to transform precoding, support Option 2.
Option 2: The PT-RS sample positions are determined using  in table 6.4.1.2.2.2-1 of TS38.211 and the PT-RS sample positions larger than  are dropped
Proposal 3: For UL muting applied for UL TBoMS, support Option 2 to determine H 
Option 2: 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and considering the muted REs
L1 based UE-to-UE CLI measurement and reporting
Observation 3: Reporting only a subset of measured RSRP/RSSI values, such as only the  of the M most interfering CLI out of all N RS for measurement (where M is much less than N), is inadequate, as it may omit many critical details, e.g., some strong enough CLIs.
Proposal 4: For a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to ‘cli-RSSI’ or ‘cli-SRS-RSRP’, the following are supported,
When the number of reported CLI measurement resources is larger than one, in case the largest measurement value(s) is(are) out of range, upper bound of the value range of L1 CLI-RSSI or CLI-SRS-RSRP is reported instead of the actual largest measurement value(s), and a differential reporting method is used taking the upper bound of the value range of L1 CLI-RSSI or CLI-SRS-RSRP as the reference.
Proposal 5: Support two additional report quantities {‘cli-RSSI-measurement-resource-bitmap’, ‘cli-SRS-RSRP-measurement-resource-bitmap’} to reportQuantity 
If reportQuantity is set to ‘cli-RSSI-measurement-resource-bitmap’, a bitmap corresponding to a set of CLI-RSSI measurement resource indices indicating whether L1-CLI-RSSI is above a given threshold
The length of the bitmap is same as the number of CLI-RSSI measurement resources within the CLI-RSSI measurement resource set
The threshold is configured by the gNB
The supported number of CLI-RSSI measurement resources within [X] slots is up to UE capability
If reportQuantity is set to ‘cli-SRS-RSRP-measurement-resource-bitmap’, a bitmap corresponding to a set of SRS-RSRP measurement resource indices indicating whether L1-SRS-RSRP is above a given threshold 
The length of the bitmap is same as the number of SRS-RSRP measurement resources within the SRS-RSRP measurement resource set
The threshold is configured by the gNB
The supported number of SRS-RSRP measurement resources within [X] slots is up to UE capability

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502243
Wuhan, China, April 7 – 11, 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: UL resource muting can be applied in non-SBFD symbols. 
Proposal 2: If an UL muting symbol overlaps with a symbol containing PT-RS for a PUSCH and transform precoding is enabled for the PUSCH, the PT-RS samples prior to transform precoding in OFDM symbol l is determined as follows
 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
Proposal 3: For UL muting applied for UL TBoMS, the index of the starting coded bit in a slot, except the first slot, within the 𝑁𝑠 slots allocated for the transmission of TB processing over multiple slots is determined according to Section 6.2.5, TS38.212 as follows

where 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and considering the muted REs.
Proposal 4: 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 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: The number of CPUs in a component carrier and across all component carriers are not increased for L1 CLI measurement and reporting.
Proposal 7: For aperiodic CLI report, reuse the existing CSI computation delay requirement for beam-reporting class (Z3).

3GPP TSG RAN WG1 #120bis                                                                                              R1-2502279
Wuhan, China, April 7th – 11st, 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: RAN1 discusses how to handle the potential measurement inaccuracy caused by another UE’s PDSCH overlapping on the L1 CLI-RSSI resources. 
Proposal 3: The bitmap report with bit value subject to a given CLI threshold is supported for at least L1-CLI-RSSI report.
Observation 1: There can be two interpretations for “out of range” that is applicable to the reference value used in differential reporting, where Interpretation #2 can lead to large quantization error propagation across all reported values in the differential reporting.
Interpretation #1: “The largest measurement (used for reference) being out of range” means the largest measurement is larger than -44dBm for L1 SRS-RSRP and -25dBm for L1 CLI-RSSI. 
Interpretation #2: “The largest measurement (used for reference) being out of range” specifically means the largest measurement of L1 SRS-RSRP is infinity (actually is too large to be measured) per RAN4 definition. There is no such “out of range” value for L1 CLI-RSSI.  
Proposal 4:  RAN1 further discusses how to determine the reference value to be used in differential quantization in case the largest measurement value is “out of range” (based on Interpretation #1 above).
Option 1:  Use the largest measurement value (other than the infinite one per RAN4 spec) as the reference value, respectively in L1 SRS-RSRP reporting and L1 CLI-RSSI reporting, with additional step to make the largest value not being “out of range” in the 7-bit quantization mapping, or the differential mapping table is modified to have one code-points specifically refers to the case where the corresponding measured value is larger than a given threshold, if the largest measurement value as the reference value is “out of range”.
The differential quantization table is basically one-directional (e,g., negative quantization input only). 
Option 2:  Use the largest SRS-RSRP measurement value but no larger than -44dBm as the reference value in L1 SRS-RSRP reporting, and the largest CLI-RSSI measurement value but no larger than -25dBm as the reference value in L1 CLI-RSSI reporting. 
The differential quantization table is two-directional (i.e., the differential value can be either positive or negative).
Option 3: Use -44dBm as the reference value in L1 SRS-RSRP reporting, and -25dBm as the reference value in L1 CLI-RSSI reporting
The differential quantization table is two-directional (i.e., the differential value can be either positive or negative).

For gNB-to-gNB co-channel CLI handling: 
Proposal 5: Per UE semi-static UL resource muting pattern configuration should be supported.
Observation 2: Disable UL resource muting in the symbols containing PTRS for DFT-s-OFDM is a simple way to avoid inaccurate phase tracking and compensation.
Proposal 6: The muted REs are counted in calculating H (the total number of coded bits available for transmission of the transport block in the previous slot), i.e., support Option 2 provided in RAN1 #120 discussion.
Note: Option-2 may have no additional RAN1 spec impact on top of existing Rel-19 agreements on SBFD.  

3GPP TSG RAN WG1 #120bis		R1-2502317
Wuhan, China, April 7th – 11th, 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.  
Observation 2: The gNB gets the actual RSRP for each measurement resource ID and hence a bitmap indicating which measurement resource ID has RSRP above a threshold does not offer any more benefit but consumes more reporting resources.


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.
Proposal 2: In determining the index , of the starting coded bit in a slot for UL TBoMS, the definition of  is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and assuming no muted REs (Option 1).
Proposal 3: Measurement resource indices is not reported in CLI measurement report.

3GPP TSG RAN WG1 Meeting #120bis	R1-2502367
Wuhan, China, April 7th – 11th, 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 proposals for UL resource muting for PUSCH:
Proposal 1: UL resource muting can be applied in non-SBFD symbols.
Proposal 2: When determining “the total number of coded bits available for transmission of the transport block” used in TS38.212, the muted REs are not considered.
Note: No specification impacts are expected.
Proposal 3: If an UL resource muting symbol overlaps with a symbol containing PTRS for a PUSCH and when transform precoding is enabled for PUSCH, PTRS is prioritized, i.e., UE does not apply UL resource muting in the symbol.
Proposal 4: Do not introduce any new PT-RS patterns in Rel-19.
Proposal 5: UL resource muting is not applied to PUSCH allocations <7 symbols.
Proposal 6: Support of UL muting on PUSCH symbols that can carry UCI is an optional UE capability in Rel-19 SBFD.
Proposal 7: 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 8: 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 9: The CLI-RSSI measurement resource type#2 is counted as two L1 CLI-RSSI measurement resource type#1.
Proposal 10: The maximum configurable number of L1 CLI-RSSI measurement resources in CLI-RSSI-MeasurementResourceSet is same as maxNrofCLI-RSSI-Resources-r16.
Proposal 11: The supported number of CLI-RSSI measurement resources is subject to UE capability.
Proposal 12: The maximum configurable number of L1 SRS-RSRP measurement resources in SRS-RSRP-MeasurementResourceSet is same as value of maxNrofSRS-RSRP-Resources-r16.
Proposal 13: The supported number of SRS-RSRP measurement resources is subject to UE capability.
Proposal 14: 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 15: 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 16: The existing CSI timeline for L1 beam reporting is reused for the aperiodic CLI measurement and reporting in Rel-19 SBFD.

3GPP TSG RAN WG1 #120-bis	R1- 2502407
Wuhan, China, April 7th – 11st, 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, UE doesn’t not apply UL resource muting in the symbols including PTRS.
Proposal 2:	Support conditional UL muting to reduce the number of entries in the TDRA table, while allowing certain flexibility in the applicability of the UL resource muting.
Proposal 3:	Support Condition 2 (MCS index), Condition 3 (number of PRBs) of the list of conditions captured in the Proposal 1-7.
Proposal 4:	For UL resource muting applied to UL TBoMS, H is calculated as the total number of coded bits available for transmission of the transport block in the previous slot within the Ns slots assuming no UCI multiplexing and assuming no muted REs (Option 1).
Observation 1:	The use-case of UL resource muting to non-SBFD symbols needs to be clarified.
Proposal 5:	Allow the UL resource muting in non-SBFD symbols without any separate UE capability
Proposal 6:	For L1 CLI measurement resource configuration, perform a down-selection from Rel-16 parameters by:
-	Removing srs-SCS-r16/rssi-SCS-r16
-	Removing refBWP-r16
-	Removing refServCellIndex-r16
-	Updating startPRB-r16 range INTEGER(0..2169) to INTEGER(0..maxNrofPhysicalResourceBlocks)
Proposal 7:	Support new MAC-CE for semi-persistent L1-CLI-RSSI measurement resource activation/deactivation.
Proposal 8:	A UE can be configured with up to 64 L1-CLI-RSSI measurement resources within a CLI-RSSI-MeasurementResourceSet.
Proposal 9:	A UE can be configured with up to 32 L1-SRS-RSRP measurement resources within a SRS-RSRP-MeasurementResourceSet.
Proposal 10:	A L1-CLI-RSSI measurement resource type#2 is considered as a single measurement resource for the determination of the number of configured measurement resources.
Proposal 11:	RAN1 to clarify whether a UE shall always assume Method#1 for a L1-CLI-RSSI measurement resource configured as measurement resource type#2.
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 subbands.
Proposal 13:	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 2:	The codepoint associated to “infinity” for SRS-RSRP measurement is related “UE operational state” rather than measurement. Also, this cannot be considered as the SRS-resource power is such high value.
Proposal 14:	For L1-SRS-RSRP measurement, any measurement set to “infinity” is precluded from the reporting.
Proposal 15:	Support two new report quantities {‘cli-RSSI-measurement-resource-bitmap’, ‘cli-SRS-RSRP-measurement-resource-bitmap’} to reportQuantity
Observation 3:	For Rel-19 SBFD operation, the L1 UE-to-UE CLI measurements are only applicable to SBFD symbols.
Observation 4:	For dynamic TDD, the L1 UE-to-UE CLI measurement shall be performed on the non-SBFD symbols.
Proposal 16:	RAN1 to decide whether L1 UE-to-UE CLI measurements can be supported for dynamic TDD operation, i.e., measurement resources are configured in non-SBFD symbols.
Proposal 17:	RAN1 to discuss whether the symbolType parameter is also applicable for L1-SRS-RSRP and L1-CLI-RSSI measurements.

3GPP TSG RAN WG1 #120		    R1-2502410
Wuhan, China, April 7th – 11th, 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: For L1-based SRS-RSRP considering out-of-range issue, UE needs to report the information that UE cannot detect SRS using absolute value and differential value.
Proposal 5: For L1-based SRS-RSRP reporting considering out-of-range issue, ‘Invalid’ should be defined in the mapping of measured quantity for differential value.
Proposal 6: If absolute value is reported as "Infinity", a differential reporting method should be adopted using -44 dBm as the reference. 

3GPP TSG RAN WG1 #120bis			R1-2502422
Wuhan, China, April 7th – 11th, 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	Support RE muting with a symbol containing PT-RS for a PUSCH with transform precoding enabled.
Proposal 2	For a DFT-s-OFDM symbol with muting + PTRS, RAN1 to down-select to one alternative for PTRS insertion amongst Alt-1, 2, and 3 from Proposal 1-11 from RAN1#120.
Proposal 3	For UL resource muting applied for UL TBoMS, for determination of the index of the starting coded bits in a slot, except for the first slot, within the Ns slots allocated for the transmission of TBoMS, Option 1 should be adopted. I.e., H is the total number of coded bits available for transmission of the transport block in the previous slot within the Ns slots assuming no UCI multiplexing and assuming no muted REs.
Proposal 4	Update the RAN1#120 agreement as follows:
Agreement
For PUSCH repetition Type A in SBFD symbols with Configuration 2, the same time location of none, one or two UL muting symbol(s) is applied for all PUSCH repetitions in SBFD symbols. No muting is applied for PUSCH repetitions in non-SBFD symbols.
For PUSCH repetition Type B in SBFD symbols with Configuration 2, the same time location of none, one or two UL muting symbol(s) per slot is applied for all the actual PUSCH repetitions in SBFD symbols. No muting is applied for actual repetitions in non-SBFD symbols.
Note: whether UL resource muting is also applied in non-SBFD symbols is discussed separately

Proposal 5	For multi-PUSCH scheduling with single DCI, the same time location of none, one or two UL muting symbol(s) is applied for all PUSCH(s) in SBFD symbols. No muting is applied for PUSCH(s) in non-SBFD symbols.
Proposal 6	Send a follow-up LS to RAN4 with the following RAN1 agreement from RAN#120 on power boosting in symbols containing PTRS.
Agreement
For the PUSCH symbol containing PT-RS with UL resource muting when transform precoding is not enabled, 3 dB power boosting for both PUSCH and PTRS REs if present, regardless of the PTRS density K and number of PUSCH layers L.

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 #120bis			      R1-2502440
Wuhan, China, April 7th – 11th, 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: If an UL muting symbol overlaps with a symbol containing PT-RS for a PUSCH when transform precoding is enabled, UE does not apply UL resource muting in the symbol.
Proposal 2: For UL muting applied for UL TBoMS, the index of the starting coded bit in a slot, except the first slot, within the 𝑁𝑠 slots allocated for the transmission of TB processing over multiple slots is determined according to Section 6.2.5, TS38.212 as follows

Option 1: 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and assuming no muted REs.
Note: No impact on TBS determination.
Proposal 3: Restrictions to time domain configuration parameters such as Starting symbol and Number of symbols configured in CLI-RSSI-MeasurementResource should be considered.
CLI-RSSI resource should be within slot boundary of reference SCS and SCS of configured DL BWP
Starting symbol and Number of symbols are integer multiple of reference SCS divided by configured BWP SCS
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, down-select from the following alternatives:
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: Update the agreement in RAN1#120 as follows:
For discussion purpose, SRS-RSRP measurement resource index is referred to as SRS-RSRP-MRI and CLI-RSSI measurement resource index is referred to as SRS-RSRP-MRICLI-RSSI-MRI.
The mapping order of CSI fields of one report for SRS-RSRP-MRI/SRS-RSRP or CLI-RSSI-MRI/CLI-RSSI reporting is provided in Table 1 with following modifications based on Table 6.3.1.1.2-8 defined in TS38.212 
CRI and SSBRI is replaced with SRS-RSRP-MRI or CLI-RSSI-MRI.
Capability index is crossed out in the table.
RSRP is replaced with L1-SRS-RSRP 
L1-CLI-RSSI is added in the table if the CSI report is associated with CLI-RSSI measurement resource.
Table 1: Mapping order of CSI fields of one report for SRS-RSRP-MRI/SRS-RSRP or CLI-RSSI-MRI/CLI-RSSI

Table 2. Bitwidth for SRS-RSRP-MRI, SRS-RSRP, CLI-RSSI-MRI and CLI-RSSI
: Number of SRS-RSRP measurement resources in the corresponding resource set
: Number of CLI-RSSI measurement resources in the corresponding resource set
Proposal 6: If CLI-RSSI measurement resource is configured across two DL subbands, the frequency resources of CLI-RSSI measurement resource are derived by excluding the frequency resources outside DL usable PRBs.

3GPP TSG RAN WG1 Meeting #120-bis			    			             R1-2502510
Wuhan, China, April 07th – 11th, 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: Frequent changes in the number of muted symbols result in variations in the available REs, causing the TBS calculations to differ with each slot. This leads to increased complexity in both UE and base station implementations.
Observation 2: 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 3: 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: To address the challenges arising from frequently changing muting symbols, it is proposed to fix or semi-statically configure the number of muting symbols for TBS calculation.
Proposal 2: UL resource muting within non-SBFD symbols is not supported in Rel-19 SBFD.
Proposal 3: 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 4: If transform precoding is enabled, we do not support assigning a PT-RS symbol and a UL muting symbol to the same symbol. Symbol-level collision avoidance between RE muting and PT-RS should be ensured.
Proposal 5: 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 6: We propose discussing how/whether to address timing misalignment between CLI-RS and UL signals received by a gNB.
Proposal 7: We propose supporting Alt.2 for the case where 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.
Proposal 8: 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 #120bis                                                  R1-2502558
Wuhan, China, April 7th – 11th, 2025


Source: Google
Title:	On the gNB-to-gNB CLI and the UE-to-UE CLI handling
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 Option 1 for the calculation of the index of the starting coded bit in a slot when UL muting applied for UL TBoMS to eliminate the need for the UE to employ two distinct calculation methods based on the presence or absence of muted REs:
Option 1: 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and assuming no muted REs.

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.


Support Periodic reporting and semi-persistent CLI reporting using a configured threshold and a bitmap.

Support two new report quantities {‘cli-RSSI-measurement-resource-bitmap’, ‘cli-SRS-RSRP-measurement-resource-bitmap’} to reportQuantity 
If reportQuantity is set to ‘cli-RSSI-measurement-resource-bitmap’, a bitmap corresponding to a set of CLI-RSSI measurement resource indices indicating whether L1-CLI-RSSI is above a given threshold
The length of the bitmap is same as the number of CLI-RSSI measurement resources within the CLI-RSSI measurement resource set
The threshold is configured by higher-layer parameters
If reportQuantity is set to ‘cli-SRS-RSRP-measurement-resource-bitmap’, a bitmap corresponding to a set of SRS-RSRP measurement resource indices indicating whether L1-SRS-RSRP is above a given threshold 
The length of the bitmap is same as the number of SRS-RSRP measurement resources within the SRS-RSRP measurement resource set
The threshold is configured by higher-layer parameters

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.

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

For UL resource muting for PUSCH repetition with Configuration 2, muting is applied to SBFD symbols only.

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

Agenda Item:	9.3.3
Source:	Apple Inc.
Title:	Discussion 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: If the scheduling offset between end of DCI triggering APL-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, 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 2: For UL muting applied for UL TBoMS, the index of the starting coded bit in a slot, except the first slot, within the 𝑁𝑠 slots allocated for the transmission of TB processing over multiple slots is determined according to Section 6.2.5, TS38.212 as follows

and H is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and assuming no muted REs.

3GPP TSG RAN WG1 #120bis			R1-2502650
Wuhan, China, April 7th – 11th, 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 #120bis			R1-2502765
Wuhan, China, April 7th – 11th, 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 observation and proposals.
Proposal 1: If an UL resource muting symbol overlaps with a symbol containing PTRS for a PUSCH and transform precoding is enabled, UL muting is applied on REs not containing PTRS RE.
Proposal 2: For UL muting applied for UL TBoMS, to determine the index of the starting coded bit in a slot, except the first slot, within the 𝑁𝑠 slots allocated for the transmission of TB processing over multiple slots, support option 1. 
Option 1: 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and assuming no muted REs.

Proposal 3: 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 beamSwitchTimingss, i.e. Alt 1 is supported.

3GPP TSG RAN WG1 #120bis			    R1-2502838
Wuhan, China, April 7th – 11th, 2025
Agenda item:	9.3.3
Source: 	Qualcomm Incorporated
Title: 	Enhancements for CLI handling
Document for:	Discussion/Decision

Conclusion
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: For periodic L1 CLI-RSSI reporting on PUCCH based on a set of periodic CLI measurement resources, the TCI state(s) with QCL typeD for the CLI measurement resources in the periodic CLI measurement resource set are configured per CLI measurement resource (either for all resources in the set or none) by higher-layer parameter
For each periodic CLI measurement resource, this higher-layer parameter provides a reference to one TCI-State in TCI-States for providing the QCL source and QCL typeD.
If the TCI state is not configured, the UE QCL assumptions are the default rules agreed in RAN1#118bis
Proposal 4: 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 5: For L1 based UE-to-UE CLI measurement and reporting based on existing CSI framework, RAN1 to discuss the AP CLI timeline with reusing beam reporting class as a baseline and the gap time between triggering DCI and the AP CLI measurement resource.
Proposal 6: 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: Support 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 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 7: 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 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 UL muting can apply to SBFD symbols and non-SBFD symbols as a conclusion.
Proposal 10: Support Option 2 to determine the index of the of starting coded bit in a slot, except the first slot, within the 𝑁𝑠 slots allocated for the transmission of TB processing over multiple slots of UL TBoMS:
Option 2 (Motivation: more accurate and less gap)  𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and considering the muted REs
Proposal 11: 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.

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

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

 
1. 

Conclusion
The following observations and proposals are made in the contribution
Observation 1:  For the CLI measurement resources:
SRS-RSRP-MeasurementResourceSetId and SRS-RSRP-MeasurementResourceId allows a single SRS-RSRP Resource Set ID to represent a set of SRS-RSRP resources with distinct resource IDs, simplifying configuration and measurement.
CLI-RSSI-MeasurementResourceSetId and CLI-RSSI-MeasurementResourceId allows a single CLI-RSSI Resource Set ID to represent a set of CLI-RSSI resources with distinct resource IDs, simplifying configuration and measurement.

Proposal 1: For definition of CLI measurement resources following configuration is needed:
 SRS-RSRP-MeasurementResourceSetId - unique identifier for the resource set.
SRS-RSRP-MeasurementResourceId - unique identifier for individual SRS-RSRP measurement resources within the resource set.
CLI-RSSI-MeasurementResourceSetId - unique identifier for the resource set.
CLI-RSSI-MeasurementResourceId - unique identifier for individual CLI-RSSI measurement resources within the resource set.

Observation 2: CLI measurement resources set to be periodic, semi-persistent, or aperiodic, but no mechanism exists to activate/deactivate these semi-persistent resources in current specification. To enable their activation and deactivation, a new MAC-CE should be introduced.
Proposal 2: Introduce a new MAC-CE to enable the activation and deactivation of semi-persistent CLI measurement resources.
Proposal 3: Support threshold-based reporting for L1 based UE-to-UE CLI measurement and reporting.
Proposal 4: Support reporting a bitmap corresponding to a set of SRS-RSRP or CLI-RSSI measurement resource indices.
Proposal 5: In cases where the largest CLI measurement is out of range, following alternatives can be considered for reporting:
Alt 1: Reporting maximum representable level along with out-of-range flag.
Alt 2: Reporting Differential value with respect to maximum representable level along with out-of-range flag.
Observation 3: The following options can be considered for indicating the subband for RSSI measurement:
Alt 1: Based on the resources within the CLI-RSSI measurement resource set (i.e., the resources within the CLI-RSSI measurement resource set are confined to either DL subband or UL subband)
Alt 2: Explicit indicating the subband for ‘cli-RSSI’ measurement in CSI-ReportConfig
Observation 4: Regarding Alt 1 for indicating subband for RSSI measurement
Complicates the scheduling of CLI-RSSI resources 
One CSI-ResourceConfig can be used for configuring either RSSI measurement in DL subband or UL subband, as the number of periodic/semi-persistent CLI measurement resource sets is restricted to 1 in a CSI-ResourceConfig
Creates ambiguity in case of Measurement resource type#2
Deviates from the common framework followed in SBFD design and not reusing the SBFD configuration shared with the UEs
Proposal 6: The CSI-ReportConfig, with the higher-layer parameter reportQuantity is set to ‘cli-RSSI’, explicitly indicating the type of subband (i.e., UL subband and/or DL subband) for RSSI measurement (Alt 2) is supported.
Observation 5: There are two types of CLI-RSSI measurement resources: Type 1, confined to either DL or UL subband, and Type 2, spanning across DL subbands. To avoid ambiguity in measurement and reporting, CSI-ReportConfig with the higher-layer parameter reportQuantity is set to ‘cli-RSSI’ should explicitly indicate whether the UE should measure RSSI using Type 1 or Type 2 resources. If the measurement resource type is not indicated, the UE may measure in both measurement resources, leading to variations in accuracy.
Proposal 7: The CSI-ReportConfig, with the higher-layer parameter reportQuantity is set to ‘cli-RSSI’, explicitly indicating the type of measurement resource type (i.e., Type 1 or Type 2) for CLI-RSSI measurement.
4. 

3GPP TSG RAN WG1 #120bis			R1-2502958
Wuhan, China, April 7th – 11th, 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 observation and proposals.
Proposal 1: If an UL resource muting symbol overlaps with a symbol containing PTRS for a PUSCH and transform precoding is enabled, UL muting is applied on REs not containing PTRS RE.
Proposal 2: For UL muting applied for UL TBoMS, to determine the index of the starting coded bit in a slot, except the first slot, within the 𝑁𝑠 slots allocated for the transmission of TB processing over multiple slots, support option 1. 
Option 1: 𝐻 is the total number of coded bits available for transmission of the transport block in the previous slot within the 𝑁𝑠 slots assuming no UCI multiplexing and assuming no muted REs.
Proposal 3: Whether configured UL muting applied to PUSCH in non-SBFD symbols can be configured by RRC.
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 4: 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 beamSwitchTimingss, i.e. Alt 1 is supported.

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

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

Conclusion
For a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to ‘cli-RSSI’ or ‘cli-SRS-RSRP’, new reporting criteria considering the least interfered measured L1-CLI-RSSI or L1-SRS-RSRP are not supported.

Agreement
For L1 CLI measurement and reporting, the number of occupied CPU(s) is determined as follows
 for a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to ‘cli-RSSI’, ‘cli-SRS-RSRP’.

Agreement
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, down-select from the following alternatives:
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.
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.
FFS: whether Alt.1 or Alt.2 has any specification impact.

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

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

Conclusion
For a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to ‘cli-RSSI’ or ‘cli-SRS-RSRP’, new reporting criteria considering the least interfered measured L1-CLI-RSSI or L1-SRS-RSRP are not supported.

Agreement
For L1 CLI measurement and reporting, the number of occupied CPU(s) is determined as follows
 for a CSI report with CSI-ReportConfig with higher layer parameter reportQuantity set to ‘cli-RSSI’, ‘cli-SRS-RSRP’.

Agreement
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, down-select from the following alternatives:
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.
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.
FFS: whether Alt.1 or Alt.2 has any specification impact.