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

Agenda Item:	9.10.1
Source:	Huawei, HiSilicon
Title:	Discussions on scheduling enhancements considering RRM measurements for XR
Document for:	Discussion and Decision 

Conclusions
In this contribution, we analyze the remaining issue of the higher layer parameters and the valid downlink slot. The following proposals are given:
Proposal 1: RAN1 does not need to discuss Column E (RAN2 Parent IE) of mg-CancellationDCI-1-3 and mg-CancellationDCI-0-3. This Column should be left empty for all parameters.
Proposal 2: The definition of valid downlink slot remains unchanged in TS 38.214. TS 38.214 does not need to be updated for Rel-19 XR.

3GPP TSG RAN WG1 meeting #121		                                   R1-2503321
St Julian's, Malta, May 19th – May 23rd, 2025
Title: 	Discussion on measurement gap for XR
Source: 	ZTE Corporation, Sanechips
Agenda item:	9.10.1
Document for:	Discussion and decision

Conclusion
In this contribution, we have the following observations/proposals:
Observation 1:	In the scenario of multiple overlapped gaps/restrictions configured and activated for one UE, single bit indication may cause ambiguities on UE behaviors.

Proposal 1:	Consider TP#1 for measurement gap cancellation in TS38.213.
Proposal 2:	Consider TP#2 for measurement gap cancellation in TS38.214.
Proposal 3:	In the scenario of multiple overlapped gaps/restrictions configured and activated for one UE, the 1-bit field in DCI signaling for the measurement gap can be down-selected in one of the following two ways:
•	Option 1: The 1-bit field in DCI indicates to skip two conflicting measurement gap occasions simultaneously.
•	Option 2: The 1-bit field in DCI indicates to skip the measurement gap occasion with high priority.

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

Source:	vivo
Title:	Remaining issues on enabling data transmissions for XR during RRM measurements
Agenda Item:	9.10.1
Document for:	Discussion and Decision

Conclusion
In this contribution, some remaining issues about enhancements to enable transmissions/receptions in gaps/restrictions are discussed, with the following proposals:
Proposal 1: For Option 2, if there are multiple DCI formats corresponding to the same gap/restriction occasion, a UE follows the indication in a last DCI format, where the last DCI format is determined in a similar way as that of determining a last DCI format for HARQ-ACK PUCCH resource determination. Specifically, among the detected DCI formats that have a value of gap skipping indicator field indicating a same gap/restriction occasion, to determine a last DCI format for determining skipping status for the gap/restriction occasion,
The detected DCI formats are first indexed in ascending order across indexes of respective scheduled cells for a same PDCCH monitoring occasion, and are then indexed in ascending order across indexes of PDCCH monitoring occasions.
For indexing a detected DCI format associated with two or more scheduled cells, a respective scheduled cell is the one with the smallest index among the two or more scheduled cells.
If a UE is not provided coresetPoolIndex or is provided coresetPoolIndex with value 0 for one or more first CORESETs and is provided coresetPoolIndex with value 1 for one or more second CORESETs on an active DL BWP of a serving cell, detected DCI formats from PDCCH receptions in the first CORESETs are indexed prior to detected DCI formats from PDCCH receptions in the second CORESETs.

3GPP TSG RAN WG1 #121	        		               R1-2503581
St Julian's, Malta, May 19th – 23rd, 2025
Agenda item:		9.10.1
Source:			Samsung
Title:			Remaining topics on enabling TX/RX during RRM measurements for XR
Document for:		Discussion and decision

Conclusions
This contribution considered an outstanding discussion point on enabling Tx/Rx during RRM measurements for XR and proposes the following.

Proposal: The procedures defined in TS 38.133 of resolving MG overlapping remain applicable before determining the MG occasions for the applicability of the “Measurement Gap Cancellation” field in the DCI format.

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

Source: 	CMCC
Title:	Discussion on enabling TX/RX for XR during RRM measurements
Agenda item:	9.10.1
Document for:	Discussion & Decision

Conclusions
In this contribution, we discuss the draft CR for the dynamic indication based solution to enable Tx/Rx in gaps/restrictions that are caused by RRM measurements. The following text proposal is made.
Text Proposal 1: Endorse the following text proposal for the agreed draft CR of TS 38.213:

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

Agenda Item:	9.10.1
Source:	InterDigital, Inc.
Title:	Discussion on enabling TX/RX for XR during RRM measurements
Document for:	Discussion

Conclusion
In this contribution, the following observations are made:
Observation 1: In legacy, collsion between gap occasions can apply to both Type-1 and Type-2 gaps (i.e. gaps without assigned priority) and R18 concurrent gaps (i.e. gaps with assigned priority).
Observation 2: Given the relatively long time offset (i.e. X = 5ms) between the DCI-based skiping indication and the gap occasion to be skipped, the possibility of colliding increases with an ambiguity on whether the skipping applies to the first, second or both gap occasions when the UE is configured with multiple MG configurations
The following proposals are made:
Proposal 1: For colliding gaps with assigned priority (e.g. R18 concurrent gaps), support UE applying the DCI-based skipping indication to the remaining gap occasion(s) after resolving the collision between the gap occasions
Proposal 2: For colliding gaps without assigned priority (e.g. Type-1 and Type-2 gaps), support UE applying the DCI-based skipping indication to the first gap occasion
Appendix: Agreements on enabling Tx/Rx during RRM measurements
RAN#120 Agreements

RAN#119 Agreements
RAN#118bis Agreements

RAN#118 Agreements

RAN#117 Agreements

RAN#116bis Agreements

RAN#116 Agreements

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


Agenda Item: 	9.10.1
Source: 	Sony 
Title: 	Remaining Issues on Enabling TX/RX during RRM measurements 
Document for: 	Discussion & Decision

Conclusion
In this contribution, we provide our views on enabling transmission/reception during measurement gap. The observations and proposals are listed below. 
Observation 1: UE has better knowledge, particularly for the UL traffic. Hence, UE assistance information (UAI) could be beneficial in assisting gNB to allow XR traffic when there is a collision between XR traffic and RRM measurement.
Observation 2: UE assistance information indicating the number of gap(s) / restriction(s) that can be skipped during a configured RRM measurement is beneficial in the operation of XR transmission during RRM measurement.

Proposal 1: Support UE Assistance Information (UAI) indicating the gNB on the MG occasions(s) to be cancelled/skipped by the UE.
Proposal 2: The detailed implementation of UAI to assist the gNB in cancelling/skipping the MG occasion(s) by the UE is defined by WG RAN2.

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

Agenda item:		9.10.1
Source:	Nokia
Title:	Enabling TX/RX for XR during RRM measurements
Document for:		Discussion and Decision

Conclusion
In this contribution we have discussed remaining open items in RAN1 related to the Rel-19 XR work.
In section 2 we discuss some remining aspects related to the dynamic indication with following observations and proposals:-
Observation 1: For determination of Option 2 behaviour two alternative approaches to define UE expectancy of consistent information: 
Alt 1: UE’s do not expect non-consistent indication in the DCI skipping field carried by PDCCHs that end in at the same symbol, or
Alt 2: UE’s do not expect non-consistent indication in the DCI skipping field carried by PDCCHs that are received in same PDCCH monitoring occasion and targeting the same measurement gap

Proposal 1: For determination of UE expectancy of consistent information for Option 2 down select among following two alternatives:
Alt 1: UE’s do not expect non-consistent indication in the DCI skipping field on PDCCHs that end in at the same symbol, or
Alt 2: UE’s do not expect non-consistent indication in the DCI skipping field on PDCCHs that are received in same PDCCH monitoring occasion and targeting the same measurement gap.

Proposal 2: For determination of valid downlink slot for CSI reporting down select among following two alternatives:
Opt.1 Definition of valid downlink slot definition is only determined by the configured measurement gap pattern and not affected by dynamic Measurement gap cancellation field in DCI. 
Opt.2 A slot that is overlapped with a cancelled measurement gap occasion is considered as a valid downlink slot for CSI resources

In Section 3 we consider the possible handling of colliding measurements gaps, for the case that RAN4 agrees to support them:-
Proposal 3: RAN1 concludes that if concurrent measurement gaps supported for measurement gap occasion cancellation and are configured, the DCI-based measurement gap occasion cancellation is applied after RAN4 defined UE behaviour for the measurement gap dropping is applied to the remaining measurement gap occasion.
Finally in section 4 the open item in agreed higher layer parameters is discussed:-
Proposal 4: The parent IE for the configuration of skipping indication for DCI format 0_3 and 1_3, is PUSCH-ConfigDCI-1-3 in PUSCH-config or PDSCH-ConfigDCI-1-3 in PDSCH-config, respectively

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

Agenda item:		9.10.1
Source:	Moderator (Nokia)
Title:	Moderator summary #1 - Enabling TX/RX for XR during RRM measurements
Document for:		Discussion and Decision

Conclusion
It is RAN1 understanding that if measurement gap/restriction is indicated to be skipped by explicit indication by DCI, the TX/RX is enabled on all the serving cells in the applicable range of the skipped measurement gap/restriction.
Note: Applicable range of measurement gap/restriction is based on RAN4 specifications

Agreement
Agreement from RAN1#119 is updated (red part)
For explicit indication by DCI to skip a particular gap/restriction, in addition to DCI formats 0_1/1_1 and 0_2/1_2, one bit indication can be included as a part of DCI formats 0_3/1_3.
Explicit indication can be configured for each DCI format individually by higher layer.
The skipping indication corresponds to the first gap/restriction occasion among co-scheduled cells by the DCI (Type-1C field)
Above applies only for intra-band CA cases (same SCS for cells in the set of co-scheduled cells).
Alt1: If skipping field is configured to DCI format 0_3/1_3, only cells that are intra-band (and have same SCS) can be co-scheduled. In other words, if co-scheduled cells could be inter-band, skipping indication field cannot be configured.


Agreement
When measurement gap/restriction is indicated to be skipped by explicit indication by DCI format 1_1/1_2 that does not schedule PDSCH and 
if CIF field is present, the scheduled cell for the skipping indication is determined by CIF field.
if CIF field is not present, the scheduled cell for the skipping indication is the scheduling cell.

Company proposals:
Company proposals to RAN1#121 are captured below. Please note that some formatting has been changed, thus please refer to original document for exact observation/proposal.

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

Source:	OPPO
Title:	Enhancements to enable Tx/Rx for XR during RRM measurements
Agenda Item:	9.10.1
Document for:	Discussion and Decision

Conclusions
In this contribution, we discuss the enhancements to enable transmission/reception for XR during RRM measurements with following observations and proposals:
Observation 1: The terminology of “last DCI” for a particular gap/restriction occasion needs be clearly defined to support option 2 for the interpretation of bit value equal to 0.
Proposal 1:  One of the following options can be considered to determine the last DCI for a particular gap/restriction occasion:
Option 1: A last DCI format is from a set of detected DCI formats corresponding to a same gap/restriction occasion. Detected DCI formats in the set are firstly indexed in the order of DL grant followed by UL grant for a same respective scheduled cell in in a same PDCCH monitoring occasion, and secondly indexed in ascending order across indexes of respective scheduled cells for a same PDCCH monitoring occasion, and lastly indexed in ascending order across indexes of PDCCH monitoring occasions. 
UE does not expect to receive more than one DL grant or more than one UL grant for a same respective scheduled cell in a same PDCCH monitoring occasion with different bit values to indicate whether to skip the gap/restriction occasion.
Option 2: A last DCI format is from a set of detected DCI formats corresponding to a same gap/restriction occasion. Detected DCI formats in the set are firstly indexed in ascending order across indexes of respective scheduled cells for a same PDCCH monitoring occasion, and then indexed in ascending order across indexes of PDCCH monitoring occasions. 
UE does not expect to receive more than one DCIs for a same respective scheduled cell in a same PDCCH monitoring occasion with different bit values to indicate whether to skip the gap/restriction occasion.
Option 3: A last DCI format is from a set of detected DCI formats corresponding to a same gap/restriction occasion. Detected DCI formats in the set are indexed in ascending order across indexes of PDCCH monitoring occasions. 
UE does not expect to receive more than one DCIs in a same PDCCH monitoring occasion with different bit values to indicate whether to skip the gap/restriction occasion.
Proposal 2: If R17/18 concurrent gap is applicable for enabling Tx/Rx in gaps/restrictions, the execution order between R17/18 collision handling for gaps/restrictions caused by RRM measurements and R19 enabling Tx/Rx in gaps/restrictions should be further studied.

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

Agenda Item:	9.10.1
Source: 	LG Electronics
Title: 	Discussion on XR during RRM measurements
Document for:	Discussion and decision

Conclusion
In this contribution, we discussed and provided our views on the potential capacity enhancement techniques for Rel-19 XR, and the followings are proposed:
Proposal 1: In case of cross carrier scheduling, consider the following Options for configuring gap skip/cancel indication in a DCI format. The one-bit indication is included by the configuration for the DCI format of the scheduling cell. 
Proposal 2: 7: For DCI formats 0_3/1_3, to determine the RRC configuration for the inclusion of the 1-bit gap/restriction skipping indication, consider the following options:
Option 1: A RRC parameter configured on the scheduling cell determines the inclusion of the 1-bit indication
Option 2 A RRC parameter configured for a 'set' of co-scheduled cells determines the inclusion of the 1-bit indication.
Option 3: The 1-bit indication is included in the DCI if 'at least one' or ‘all’ of the co-scheduled cells has a RRC parameter configured.
Proposal 3: Introduce RRC parameter to set minimum time offset(s) X, which indicates the time from the end of the last symbol of the PDCCH carrying the DCI to the start of the corresponding measurement gap to be skipped. 
Proposal 4: For the minimum time offset(s) X, down-select from the following options for both multi-carrier and cross-carrier scheduling scenarios:
Option 1: Apply the X value of the scheduling cell.
Option 2-1: Apply the largest X value among scheduled cells.
Option 2-2: Apply individual X values for each scheduled cell.

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

Agenda Item:	9.10.1
Source:	Apple Inc.
Title:	Discussion on RRM measurement adaptation for XR
Document for:	Discussion/Decision
1. 

Conclusion
Proposal 1: To facilitate adaptation of legacy MGs, Network Controlled Small Gaps, pre-configured MG, MGs for multi-SIM, MGs for positioning with a unified signaling design, MGs can be indexed. A MG index set consists of one or more MG index, MGs referred by a MG index set can be skipped through a single NW indication.  

Proposal 2: when MGs are eligible for adaptation but L1-scheduling restriction are not eligible for adaptation, consider the following
·       Alt. 1: among MG occasions start at the same time, the MG occasion with the shortest duration is referred by the dynamic signaling (e.g., MG-2)
·       Alt. 2: among MG occasions start at the same time, the MG occasion with the longest duration is referred by the dynamic signaling (e.g., MG-1)
·       Alt. 3: among MG occasions overlapping one another, the MG occasion with the shortest duration is referred by the dynamic signaling;
·       Alt. 4: among MG occasions overlapping one another, the MG occasion with the longest duration is referred by the dynamic signaling;
·       Alt. 5: among MG occasions overlapping one another, the MG occasion which finishes earliest is referred by the dynamic signaling;
·       Alt. 6: among MG occasions overlapping one another, the MG occasion which finishes last is referred by the dynamic signaling;
·       Alt. 7: among MG occasions overlapping one another, the MG occasion which starts earliest is referred by the dynamic signaling;
·       Alt. 8: among MG occasions overlapping one another, the MG occasion which starts last is referred by the dynamic signaling

Proposal 3: to handle potential partial skipping situations, consider 
Alt. 1:
 UE does not expect to receive signaling from NW which would lead to partial skipping of MG/scheduling restriction.
Consider two cases:
A MG/scheduling restriction which is previously indicated as “skipped” cannot be “revived” by a later signaling
A MG/scheduling restriction which is not skipped cannot be skipped due to UE’s skipping of an overlapping MG/scheduling restriction.
Alt. 2:
If NW signaling would lead to partial skipping of MG/scheduling restriction, it is up to UE implementation to handle it.
Alt. 3:
Once a MG/scheduling restriction is indicated as skipping, it cannot be partially un-skipped by a later skipping signaling.
And a second MG/scheduling restriction which partially/fully overlaps with a first skipped MG/scheduling restriction is also skipped.
Alt. 4 (An algorithmic description for Alt. 3), an operational procedure to derive set S can be found below:
The UE starts with a skipped MG/scheduling restriction (instance-1), and a set S consisting of OFDM symbols/time duration of instance-1, If there is any skippable MG/scheduling restriction (designated as instance-2) which overlaps with S, then S <= Union of (S, instance-2), … until S cannot be expanded further. If TS 38.133 processing has not been conducted over S, then TS 38.133 processing is conducted on S. Then S is the time unit for the skipping signaling. Then UE does not expect to receive a signaling to indicate “not skipped” for any duration fully or partially covered by S.
Specifically for Option 2, NW signaling cannot revert a MG/scheduling skipping which is covered in a proper superset S. 
In the example below, SMTC-2 and MG-2 cannot be “revived” by a revert signaling. 
In an optimization, only MG/scheduling restriction at the beginning of a superset S can be “revived” by a revert signaling (e.g., MG-1 is at the beginning of the superset S, thus eligible for “being revived”).

Proposal 4: For the dynamic signaling for RRM measurement adaptation for XR, regarding the designation of “valid downlink slot”, consider
Alt. 1: when a slot is designated as not a “valid downlink slot” due to overlap with a configured measurement gap occasion, and that measurement gap occasion is skipped due to RRM measurement adaptation for XR, the slot is NOT converted into a “valid downlink slot”

Alt. 2: when a slot is designated as not a “valid downlink slot” due to overlap with a configured measurement gap occasion, and that measurement gap occasion is skipped due to RRM measurement adaptation for XR,   for the basic UE feature supporting RRM measurement adaptation, the slot is NOT converted into a “valid downlink slot” and the slot may be eligible to be designated as “valid downlink slot” subject to additional UE capability.  

3GPP TSG RAN WG1 #121			R1-2504409
St Julian’s, Malta, May 19th – 23th, 2025
	
Agenda item:	9.10.1
Source: 	Qualcomm Incorporated
Title: 	Enabling Tx/Rx for XR during RRM measurements
Document for:	Discussion and Decision

Conclusions
In this contribution, we have provided the following proposals:
Observation 1: For the definition of the minimum time offset for measurement gap skipping, end of the DCI carrying the indication is used. This implies the DCI that has the latest end among all DCIs matters for the measurement gap subject to skipping. 
Proposal 1: If multiple DCIs containing measurement gap skipping indication are received before the gap, the last DCI is determined by the end of the DCI.
Proposal 2: If two DCIs carrying the measurement gap skipping indication have the same end time, the same 1-bit value is expected in both DCIs.
Observation 2: For DCI format 1_1/1_2 and 0_1/0_2, if measurement gap skipping is configured for the PDSCH or PUSCH in a cell, the corresponding DL or UL scheduling DCI contains the 1-bit measurement gap skipping indication.
Proposal 3: For measurement gap skipping indication in DCI format 1_3/0_3, MC-DCI-SetOfCells is used as the RAN2 parent IE for the higher layer configuration.

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

Source:	NTT DOCOMO, INC.
Title:	Discussion on Enaling TX/RX for XR during RRM
Agenda Item:	9.10.1
Document for: 	Discussion and Decision

Conclusion
In this contribution, we discussed possible methods to enable transmission/reception in gaps/restrictions that are caused by RRM measurements. We have the following observations and proposals:

Proposal 1: When multiple DCI formats are corresponding to the same gap/restriction occasion, the multiple DCIs are ordered by PDCCH starting symbol firstly, and then by serving cell index.

Proposal 2: On update of “valid downlink slot” for CSI reference resource, following options can be considered: 
Option 1: the second condition is modified into: “it does not fall within a configured measurement gap if UE doesn’t support FG 64-1”. 
Option 2: the second condition is modified into: “it does not fall within a configured measurement gap if UE is not configured with Measurement gap cancellation field for any DCI format”.
Option 3: The second condition can be modified into: “it does not fall within a configured measurement gap if UE is not configured with RRC parameter to indicate CSI reference resource within a relaxed gap”.

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

Source: Google
Title:	On enabling Tx/Rx for XR during RRM measurements 
Document for: Discussion and Decision

Conclusion
In this contribution, we have presented several proposals to specify the support of skipping measurement gaps.
We made the following proposals: 


The UE doesn’t not expect inconsistent skipping indications in the same PDCCH or with multiple overlapping PDCCHs

  In addition to the per-DCI-format, support an RRC parameter within each measurement gap configuration (e.g., GapConfig) to enable/disable the applicability of DCI-based skipping for measurement occasions corresponding to that specific gap configuration.

If multiple measurement gaps are overlapping, the DCI-based measurement gap occasion cancellation is applied to the remaining measurement gap occasion after RAN4 defined UE behaviour for measurement gap dropping

33GPP TSG-RAN WG1 Meeting #121	R1-2504620
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	9.10.1
Source:	Ericsson
Title:	Enabling TX/RX for XR traffic during RRM measurement gaps
Document for:	Discussion, Decision
1	

Conclusion
It is RAN1 understanding that if measurement gap/restriction is indicated to be skipped by explicit indication by DCI, the TX/RX is enabled on all the serving cells in the applicable range of the skipped measurement gap/restriction.
Note: Applicable range of measurement gap/restriction is based on RAN4 specifications
Agreement
Agreement from RAN1#119 is updated (red part)
For explicit indication by DCI to skip a particular gap/restriction, in addition to DCI formats 0_1/1_1 and 0_2/1_2, one bit indication can be included as a part of DCI formats 0_3/1_3.
Explicit indication can be configured for each DCI format individually by higher layer.
The skipping indication corresponds to the first gap/restriction occasion among co-scheduled cells by the DCI (Type-1C field)
Above applies only for intra-band CA cases (same SCS for cells in the set of co-scheduled cells).
Alt1: If skipping field is configured to DCI format 0_3/1_3, only cells that are intra-band (and have same SCS) can be co-scheduled. In other words, if co-scheduled cells could be inter-band, skipping indication field cannot be configured.
Agreement
When measurement gap/restriction is indicated to be skipped by explicit indication by DCI format 1_1/1_2 that does not schedule PDSCH and 
if CIF field is present, the scheduled cell for the skipping indication is determined by CIF field.
if CIF field is not present, the scheduled cell for the skipping indication is the scheduling cell.

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

Agenda Item:	9.10.1
Source:	Apple Inc.
Title:	Discussion on RRM measurement adaptation for XR
Document for:	Discussion/Decision
1. 

Conclusion
Proposal 1: To facilitate adaptation of legacy MGs, Network Controlled Small Gaps, pre-configured MG, MGs for multi-SIM, MGs for positioning with a unified signaling design, MGs can be indexed. A MG index set consists of one or more MG index, MGs referred by a MG index set can be skipped through a single NW indication.  

Proposal 2: when MGs are eligible for adaptation but L1-scheduling restriction are not eligible for adaptation, consider the following
·       Alt. 1: among MG occasions start at the same time, the MG occasion with the shortest duration is referred by the dynamic signaling (e.g., MG-2)
·       Alt. 2: among MG occasions start at the same time, the MG occasion with the longest duration is referred by the dynamic signaling (e.g., MG-1)
·       Alt. 3: among MG occasions overlapping one another, the MG occasion with the shortest duration is referred by the dynamic signaling;
·       Alt. 4: among MG occasions overlapping one another, the MG occasion with the longest duration is referred by the dynamic signaling;
·       Alt. 5: among MG occasions overlapping one another, the MG occasion which finishes earliest is referred by the dynamic signaling;
·       Alt. 6: among MG occasions overlapping one another, the MG occasion which finishes last is referred by the dynamic signaling;
·       Alt. 7: among MG occasions overlapping one another, the MG occasion which starts earliest is referred by the dynamic signaling;
·       Alt. 8: among MG occasions overlapping one another, the MG occasion which starts last is referred by the dynamic signaling

Proposal 3: to handle potential partial skipping situations, consider 
Alt. 1:
 UE does not expect to receive signaling from NW which would lead to partial skipping of MG/scheduling restriction.
Consider two cases:
A MG/scheduling restriction which is previously indicated as “skipped” cannot be “revived” by a later signaling
A MG/scheduling restriction which is not skipped cannot be skipped due to UE’s skipping of an overlapping MG/scheduling restriction.
Alt. 2:
If NW signaling would lead to partial skipping of MG/scheduling restriction, it is up to UE implementation to handle it.
Alt. 3:
Once a MG/scheduling restriction is indicated as skipping, it cannot be partially un-skipped by a later skipping signaling.
And a second MG/scheduling restriction which partially/fully overlaps with a first skipped MG/scheduling restriction is also skipped.
Alt. 4 (An algorithmic description for Alt. 3), an operational procedure to derive set S can be found below:
The UE starts with a skipped MG/scheduling restriction (instance-1), and a set S consisting of OFDM symbols/time duration of instance-1, If there is any skippable MG/scheduling restriction (designated as instance-2) which overlaps with S, then S <= Union of (S, instance-2), … until S cannot be expanded further. If TS 38.133 processing has not been conducted over S, then TS 38.133 processing is conducted on S. Then S is the time unit for the skipping signaling. Then UE does not expect to receive a signaling to indicate “not skipped” for any duration fully or partially covered by S.
Specifically for Option 2, NW signaling cannot revert a MG/scheduling skipping which is covered in a proper superset S. 
In the example below, SMTC-2 and MG-2 cannot be “revived” by a revert signaling. 
In an optimization, only MG/scheduling restriction at the beginning of a superset S can be “revived” by a revert signaling (e.g., MG-1 is at the beginning of the superset S, thus eligible for “being revived”).

Proposal 4: For the dynamic signaling for RRM measurement adaptation for XR, regarding the designation of “valid downlink slot”, consider
Alt. 1: when a slot is designated as not a “valid downlink slot” due to overlap with a configured measurement gap occasion, and that measurement gap occasion is skipped due to RRM measurement adaptation for XR, the slot is NOT converted into a “valid downlink slot”

Alt. 2: when a slot is designated as not a “valid downlink slot” due to overlap with a configured measurement gap occasion, and that measurement gap occasion is skipped due to RRM measurement adaptation for XR,   for the basic UE feature supporting RRM measurement adaptation, the slot is NOT converted into a “valid downlink slot” and the slot may be eligible to be designated as “valid downlink slot” subject to additional UE capability.  


Proposal 5: Introduce different FGs for dynamic signaling with DCI formats 0_1, 1_1, 0_2, 1_2, 0_3 and 1_3. Their Type is either “per band” or “per band combination”.

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

Agenda item:		9.10.1
Source:	Moderator (Nokia)
Title:	Moderator summary #2 - Enabling TX/RX for XR during RRM measurements
Document for:		Discussion and Decision

Conclusion
It is RAN1 understanding that if measurement gap/restriction is indicated to be skipped by explicit indication by DCI, the TX/RX is enabled on all the serving cells in the applicable range of the skipped measurement gap/restriction.
Note: Applicable range of measurement gap/restriction is based on RAN4 specifications

Agreement
Agreement from RAN1#119 is updated (red part)
For explicit indication by DCI to skip a particular gap/restriction, in addition to DCI formats 0_1/1_1 and 0_2/1_2, one bit indication can be included as a part of DCI formats 0_3/1_3.
Explicit indication can be configured for each DCI format individually by higher layer.
The skipping indication corresponds to the first gap/restriction occasion among co-scheduled cells by the DCI (Type-1C field)
Above applies only for intra-band CA cases (same SCS for cells in the set of co-scheduled cells).
Alt1: If skipping field is configured to DCI format 0_3/1_3, only cells that are intra-band (and have same SCS) can be co-scheduled. In other words, if co-scheduled cells could be inter-band, skipping indication field cannot be configured.


Agreement
When measurement gap/restriction is indicated to be skipped by explicit indication by DCI format 1_1/1_2 that does not schedule PDSCH and 
if CIF field is present, the scheduled cell for the skipping indication is determined by CIF field.
if CIF field is not present, the scheduled cell for the skipping indication is the scheduling cell.

Company proposals:
Company proposals to RAN1#121 are captured below. Please note that some formatting has been changed, thus please refer to original document for exact observation/proposal.