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

Source:	ZTE Corporation, Sanechips 
Title:	On Rel-19 TEI proposals 
Agenda Item:	9.14
Document for:  	Discussion/Decision

Conclusion
In this contribution, we summarize the observation(s) and proposal(s) for Rel-19 TEI on SR occasion switching upon TCI update, and the Recommended RRC parameter list and TP for approved Rel-19 TEIs.
Rel-19 TEI on SR occasion switching upon TCI update
Observation 1: On analog/hybrid beam-forming architecture, for the same set of OFDM symbols, there are numerous SR transmission occasions from different UEs that being aligned with the same gNB Rx beam.
The above can be observed for the realistic NW implementation in both FR1 (U6GHz) and FR2.
Observation 2: On an SR transmission comprising a list of UEs, once that the beam direction (i.e., NW UL Rx beam) of one SR resource is changed, the NW UL RX beam applied to the UE are not aligned anymore, while considering, as in legacy, the transmission occasion for the SR can NOT be updated simultaneously.
Proposal 1: On unified TCI framework, support that one joint/UL TCI state can be associated with a time-domain offset (in slot level)
If a joint/UL TCI state is indicated or provided to a PUCCH resource used for an SR transmission, then the associated time-domain offset is applied for deriving the corresponding SR transmission occasion.
Introduce a new RRC parameter of the time-domain offset (in slot level) in a joint/UL TCI state and corresponding UE capability signaling.
Recommended RRC parameter list and TP for approved Rel-19 TEIs
Recommended RRC parameter list for ‘TN32HARQ’ and ‘Pos_SRSHop’ is in the attachment - Rel-19 - RRC_TN32HARQ_and_Pos_SRSHop.xls.
Proposal 2: Support TP#1 on TS 38.212 for support of 32 HARQ process numbers for TN in FR1 and FR2-1. 
Proposal 3: There is no need to introduce new parameters to support positioning SRS FH feature for non-RedCap UE. 
Value range of C_SRS is reused to indicate the bandwidth per hop, wherein the maximum bandwidth per hop for non-RedCap UE can be up to 100MHz for FR1 and 400MHz for FR2. Update the field description of “freqHopping” shown in attachment Rel-19 - RRC_TN32HARQ_and_Pos_SRSHop.xls
The maximum bandwidth across all hops is at most 100MHz for FR1 and 400MHz for FR2.
Details in the attachment - Rel-19 - RRC_TN32HARQ_and_Pos_SRSHop.xls.
Proposal 4: Support TP#2 on TS 38.214 for non-RedCap UE SRS frequency hopping for positioning 

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

Agenda item:	9.14 
Source: 	EBU
Title: 	Muting of always-on signals for 5G Broadcast
Document for:	Discussion and Decision
Motivation
Existing broadcast technologies such as DVB-T2 [1] presume the usage of dedicated receivers to display TV programmes. Almost all DVB-T deployments are based on stationary reception even though the standard allows for serving devices under mobile receiving conditions. However, existing broadcast transmissions cannot be received on 3GPP devices such as smartphones and tablets. 5G Broadcast has been specified in 3GPP starting with Release 14 and following in order to reach mobile users with attractive linear broadcast content. To this end, existing broadcast transmitter networks can be utilized using broadcast spectrum in the band 470 – 694/698 MHz. However, in most countries this spectrum is heavily used by existing DVB-T2 deployments. In order to facilitate the deployment of 5G Broadcast services Time-Division-Multiplexing (TDM) of a given UHF channel would provide a means to pave the way for a low-barrier market introduction of 5G Broadcast. This would meet the needs of broadcasters for future technology migration paths. DVB-T2 already has in-built provisions for TDM with other technologies via the concept of Future Extension Frames (FEF). As of now, sharing of a UHF channel between DVB-T2 and 5G Broadcast is not feasible as the latter technology does not foresee corresponding mechanisms. However, it appears to be rather simple and straightforward to do so by muting parts of the 5G Broadcast signal. This only calls for a simple signalling addition to the 5G Broadcast configuration by defining the corresponding parameters needed for periodic muting of CAS, MCCH and MSI. This document provides a detailed description how to implement such a feature.  
Muting always-on signals in 5G Broadcast
The “always on signals” in an MBMS-dedicated cell are:
the Cell Acquisition Subframe (CAS), which is a non-MBSFN subframe of 1 ms duration, occurring once every 40 ms. The CAS includes the synchronization signals—PSS/SSS/PBCH (containing MIB-MBMS for MBMS-dedicated cells), as well as the SIBs, including SIB1-MBMS for MBMS-dedicated cells;
the MCCH, which conveys common control information for all the PMCHs in an MBSFN Area. The MCCH has a preconfigured periodicity from within a set of once every {1,2,4,8,16,32,64,128,256} radio frames (rfs);
the MCH scheduling information (MSI) MAC-CE, which is associated with each PMCH in a list of PMCHs in a MBSFN Area. The MSI has a preconfigured periodicity from within a set of once every {1,2,4,8,16,32,64,128,256,512,1024} radio frames (rfs).
Observation 1: The signals that need to be muted, to create blanks in 5G Broadcast transmissions in an MBMS-dedicated cell (which may be used to time-division multiplex other broadcast technologies with 5G Broadcast) are:
The Cell Acquisition Subframe (CAS)
The MCCH
The MSI
The signals transmitted in the CAS may be combined (e.g., to increase the received SNR) over up to 4 consecutive CAS transmissions—i.e., over a time duration of —during which the contents of the CAS (e.g., the MIB-MBMS and SIB1-MBMS) do not change. Each such 160 ms duration described above starts in a radio frame with system frame number (SFN) given by . 
The structure of the CAS described above dictates that a repeating period, comprising a CAS ON duration followed by a CAS muted duration, must be a multiple of 160 ms, so that (at least the first set of) successive CASs within that period can be combined, and that every period begins with combinable CASs, starting at radio frames satisfying .
Observation 2: A repeating period, comprising a CAS ON duration followed by a CAS muted duration, must be a multiple of 160 ms in duration
This facilitates combining across (at least the first) four consecutive CASs, spaced 40 ms apart, within each such period, as supported in the current specifications.
A valid CAS ON/OFF pattern within each such repeating period would have the first few CASs ON (i.e., non-muted CAS) within the . Since each set of  () units will comprise four consecutive CASs that can be combined, we can use this as a starting point for the CAS ON duration, for different values of . However, additional CASs may also be needed, e.g., to facilitate efficient alignment with the coexistence parameters provided by other broadcast standards. This can be achieved by adding a further  (i.e.,  additional CASs), on top of the baseline , to the CAS ON duration.
An example where this is relevant is co-existence with DVB-T2, which provides Future Extension Frames (FEFs) of duration up to 250 ms, within which 5G Broadcast can be TDM-ed. Configuring  ensures a CAS ON duration of 240 ms, which is closely aligned (minimizing resource wastage) with the DVB-T2 FEFs.
The values of values of  will, in general, be configured from a set of candidate values. This results in a “duty cycle” of for 5G Broadcast, a fraction  for time-division multiplexing with other broadcasting technologies, such as DVB-T2. This is illustrated in Fig. 1 below. 

Figure : Illustration of CAS muting in 5G Broadcast, and potential coexistence with DVB-T2.

Observation 3: A CAS “ON duration” comprising the first  out of every ( facilitates a 5G Broadcast duty cycle of  and allows for TDM-ing with other broadcasting technologies with a duty cycle of . 
Observation 4: Setting  results in a CAS ON duration of 240 ms, which minimizes resource wastage when 5G Broadcast is TDM-ed within the Future Extension Frames (FEFs) of DVB-T2, which are up to 250 ms duration each.
We further observe that, for the other “always on” signals in 5G broadcast—the MCCH and the MSI—described above, there are several candidate values of “” such that a periodicity of  (i.e.,  rfs) aligns with an existing periodicity of the MCCH and/or the MSI.
Specifically, the values of  in the set {2,4,8,16} can be supported with compatible MCCH and MSI periodicities that are specified up to Release 16, such that the MCCHs and MSIs are not transmitted in the CAS-muted regions. We also note that, there are currently 7 spare values in the configuration for MCCH periodicity, which can be utilized to further augment the values of  that may be supportable.
Observation 5: For a periodicity of , defining the periodic CAS muting pattern, values of  in the set {2,4,8,16} are compatible with existing MCCH and MSI periodicities (up to Release 16), such that the MCCHs and MSIs are only transmitted in the CAS “ON durations”.
Larger values of  can be supported by defining larger MCCH periodicities; there are currently seven spare values to achieve this.
With the above analysis, we have established that to support muting of the always-on signals for 5G Broadcast (to facilitate flexible TDM-ing with other broadcasting technologies such as DVB-T2), at the higher layers, we only need to define a semi-static muting configuration in SIB1-MBMS, where the configuration will state when the CAS is on, and when it is off. This is the only signalling update needed in TS 36.331.
With this in mind, we make the following proposal.
Proposal 1: The non-MBSFN subframes containing the cell acquisition signals (PSS/SSS/PBCH/SIB1) in an MBMS-dedicated cell shall only be transmitted within the first  out of every .
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {2,4,8,16}.
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {1,2,3, … ,15}.
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {0,1,2,3}
In the absence of the above parameters , all non-MBSFN subframes containing cell acquisition signals in an MBMS-dedicated cell shall be transmitted
Conclusion
In this contribution we presented our views on muting the always on signals for 5G Broadcast, to facilitate TDM-ing with other broadcasting technologies, such as DVB-T2. Our observations and proposal are summarized below.
Observation 1: The signals that need to be muted, to create blanks in 5G Broadcast transmissions in an MBMS-dedicated cell (which may be used to time-division multiplex other broadcast technologies with 5G Broadcast) are:
The Cell Acquisition Subframe (CAS)
The MCCH
The MSI
Observation 2: A repeating period, comprising a CAS ON duration followed by a CAS muted duration, must be a multiple of 160 ms in duration
This facilitates combining across (at least the first) four consecutive CASs, spaced 40 ms apart, within each such period, as supported in the current specifications.
Observation 3: A CAS “ON duration” comprising the first  out of every ( facilitates a 5G Broadcast duty cycle of  and allows for TDM-ing with other broadcasting technologies with a duty cycle of . 
Observation 4: Setting  results in a CAS ON duration of 240 ms, which minimizes resource wastage when 5G Broadcast is TDM-ed within the Future Extension Frames (FEFs) of DVB-T2, which are up to 250 ms duration each.
Observation 5: For a periodicity of , defining the periodic CAS muting pattern, values of  in the set {2,4,8,16} are compatible with existing MCCH and MSI periodicities (up to Release 16), such that the MCCHs and MSIs are only transmitted in the CAS “ON durations”.
Larger values of  can be supported by defining larger MCCH periodicities; there are currently seven spare values to achieve this.
Proposal 1: The non-MBSFN subframes containing the cell acquisition signals (PSS/SSS/PBCH/SIB1) in an MBMS-dedicated cell shall only be transmitted within the first  out of every .
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {2,4,8,16}.
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {1,2,3, … ,15}.
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {0,1,2,3}
In the absence of the above parameters , all non-MBSFN subframes containing cell acquisition signals in an MBMS-dedicated cell shall be transmitted

4. References
[1] ETSI TS 102 755, V1.1.1 Digital Video Broadcasting (DVB); Frame structure channel coding and modulation for a second generation digital terrestrial television broadcasting system (DVB-T2), 2023.

TDoc file conclusion not found

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

Agenda Item:	9.14
Source:	Apple Inc.
Title:	Higher layer parameters for Rel-19 TEI SRSCS_ULTxSwitch
Document for:	Discussion/Decision

TDoc file conclusion not found

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

Agenda item:		9.14
Source:	MediaTek Inc., Nokia, Apple, Ericsson, Orange, NTT DOCOMO
Title:	Proposal for TEI19
Document for:		Discussion and Decision

Conclusion
The following proposals are made:
Proposal 1: For simultaneous CSI-RS reception in UE features 2-33, 2-36, 2-40, 2-41 and 2-43, define 2 new UE capabilities:
UE capability 1: To allow the UE to indicate that CSI-RS ports within one CSI-RS resource, as well as the CSI-RS resource, are counted as one resource, even if the CSI-RS resource is referred by N Report Settings.
UE capability 2: To allow the UE to indicate that CSI-RS ports within one CSI-RS resource, as well as the CSI-RS resource, are counted as one resource even if the CSI-RS resource is referred by N Report Settings, but ONLY if all of the reporting configuration parameters (except for reportConfigId and reportConfigType) within CSI-ReportConfig are set to the same value for each of the N reports.

Proposal 2: For simultaneous CSI-RS reception in Network Energy saving UE features 42-1/1a/1b/1c, and 42-2/2a/2b/2c, define the following new UE capability:
UE capability 3: To allow the UE to indicate that CSI-RS ports within one CSI-RS resource, as well as the CSI-RS resource, are counted as one resource even if the CSI-RS resource is referred multiple times.

Proposal 3: Consider the draft Text Proposal and UE Feature descriptions in this document for the specification update.
4	

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

Source:	CATT
Title:	Enhancement of SRS antenna switching pattern reporting
Agenda Item:	9.14
Document for:	Discussion and Decision

Conclusion
In this contribution, we have discussed the motivation and the spec impacts of SRS antenna switching pattern reporting. We summarize the observation and proposals for enhancement of SRS antenna switching pattern reporting as follows:
Observation 1: Allowing UE reports preferred SRS antenna switching pattern is beneficial for UE to turn off some antennas due to overheating or power saving, and is also beneficial to save SRS resources and improve UL transmission efficiency.
Proposal 1: Support UE reports its preferred SRS antenna switching pattern to NW via UAI.
Optionally, the duration/periodicity of the preferred pattern is also reported.
Proposal 2: Send an LS to RAN2 for introducing the SRS antenna switching pattern reporting in UAI.

3GPP TSG RAN WG1 #120bis		     	 R1-2502862
Wuhan, China, April 7th – 11th, 2025
Agenda item:	9.14
Source: 	Qualcomm Incorporated
Title: 	Proposal for Rel-19 RAN1 TEI
Document for:	Discussion/Decision

Conclusions
The following proposal is proposed to address the issue of no gap between back-to-back PUCCH/PUSCH and SRS transmissions. 
Proposal 1: At least Y symbol gap is expected between PUCCH/PUSCH and xTyR (where x

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

Agenda item:	9.14 
Source: 	EBU, SWR, ORS, BNE, Rohde & Schwarz, Qualcomm Incorporated
Title: 	Muting of always-on signals for 5G Broadcast
Document for:	Discussion and Decision
Motivation
Existing broadcast technologies such as DVB-T2 [1] presume the usage of dedicated receivers to display TV programmes. Almost all DVB-T deployments are based on stationary reception even though the standard allows for serving devices under mobile receiving conditions. However, existing broadcast transmissions cannot be received on 3GPP devices such as smartphones and tablets. 5G Broadcast has been specified in 3GPP starting with Release 14 and following in order to reach mobile users with attractive linear broadcast content. To this end, existing broadcast transmitter networks can be utilized using broadcast spectrum in the band 470 – 694/698 MHz. However, in most countries this spectrum is heavily used by existing DVB-T2 deployments. In order to facilitate the deployment of 5G Broadcast services Time-Division-Multiplexing (TDM) of a given UHF channel would provide a means to pave the way for a low-barrier market introduction of 5G Broadcast. This would meet the needs of broadcasters for future technology migration paths. DVB-T2 already has in-built provisions for TDM with other technologies via the concept of Future Extension Frames (FEF). As of now, sharing of a UHF channel between DVB-T2 and 5G Broadcast is not feasible as the latter technology does not foresee corresponding mechanisms. However, it appears to be rather simple and straightforward to do so by muting parts of the 5G Broadcast signal. This only calls for a simple signalling addition to the 5G Broadcast configuration by defining the corresponding parameters needed for periodic muting of CAS, MCCH and MSI. This document provides a detailed description how to implement such a feature.  
Muting always-on signals in 5G Broadcast
The “always on signals” in an MBMS-dedicated cell are:
the Cell Acquisition Subframe (CAS), which is a non-MBSFN subframe of 1 ms duration, occurring once every 40 ms. The CAS includes the synchronization signals—PSS/SSS/PBCH (containing MIB-MBMS for MBMS-dedicated cells), as well as the SIBs, including SIB1-MBMS for MBMS-dedicated cells;
the MCCH, which conveys common control information for all the PMCHs in an MBSFN Area. The MCCH has a preconfigured periodicity from within a set of once every {1,2,4,8,16,32,64,128,256} radio frames (rfs);
the MCH scheduling information (MSI) MAC-CE, which is associated with each PMCH in a list of PMCHs in a MBSFN Area. The MSI has a preconfigured periodicity from within a set of once every {1,2,4,8,16,32,64,128,256,512,1024} radio frames (rfs).
Observation 1: The signals that need to be muted, to create blanks in 5G Broadcast transmissions in an MBMS-dedicated cell (which may be used to time-division multiplex other broadcast technologies with 5G Broadcast) are:
The Cell Acquisition Subframe (CAS)
The MCCH
The MSI
The signals transmitted in the CAS may be combined (e.g., to increase the received SNR) over up to 4 consecutive CAS transmissions—i.e., over a time duration of —during which the contents of the CAS (e.g., the MIB-MBMS and SIB1-MBMS) do not change. Each such 160 ms duration described above starts in a radio frame with system frame number (SFN) given by . 
The structure of the CAS described above dictates that a repeating period, comprising a CAS ON duration followed by a CAS muted duration, must be a multiple of 160 ms, so that (at least the first set of) successive CASs within that period can be combined, and that every period begins with combinable CASs, starting at radio frames satisfying .
Observation 2: A repeating period, comprising a CAS ON duration followed by a CAS muted duration, must be a multiple of 160 ms in duration
This facilitates combining across (at least the first) four consecutive CASs, spaced 40 ms apart, within each such period, as supported in the current specifications.
A valid CAS ON/OFF pattern within each such repeating period would have the first few CASs ON (i.e., non-muted CAS) within the . Since each set of  () units will comprise four consecutive CASs that can be combined, we can use this as a starting point for the CAS ON duration, for different values of . However, additional CASs may also be needed, e.g., to facilitate efficient alignment with the coexistence parameters provided by other broadcast standards. This can be achieved by adding a further  (i.e.,  additional CASs), on top of the baseline , to the CAS ON duration.
An example where this is relevant is co-existence with DVB-T2, which provides Future Extension Frames (FEFs) of duration up to 250 ms, within which 5G Broadcast can be TDM-ed. Configuring  ensures a CAS ON duration of 240 ms, which is closely aligned (minimizing resource wastage) with the DVB-T2 FEFs.
The values of values of  will, in general, be configured from a set of candidate values. This results in a “duty cycle” of for 5G Broadcast, a fraction  for time-division multiplexing with other broadcasting technologies, such as DVB-T2. This is illustrated in Fig. 1 below. 

Figure 1: Illustration of CAS muting in 5G Broadcast, and potential coexistence with DVB-T2.

Observation 3: A CAS “ON duration” comprising the first  out of every ( facilitates a 5G Broadcast duty cycle of  and allows for TDM-ing with other broadcasting technologies with a duty cycle of . 
Observation 4: Setting  results in a CAS ON duration of 240 ms, which minimizes resource wastage when 5G Broadcast is TDM-ed within the Future Extension Frames (FEFs) of DVB-T2, which are up to 250 ms duration each.
We further observe that, for the other “always on” signals in 5G broadcast—the MCCH and the MSI—described above, there are several candidate values of “” such that a periodicity of  (i.e.,  rfs) aligns with an existing periodicity of the MCCH and/or the MSI.
Specifically, the values of  in the set {2,4,8,16} can be supported with compatible MCCH and MSI periodicities that are specified up to Release 16, such that the MCCHs and MSIs are not transmitted in the CAS-muted regions. We also note that, there are currently 7 spare values in the configuration for MCCH periodicity, which can be utilized to further augment the values of  that may be supportable.
Observation 5: For a periodicity of , defining the periodic CAS muting pattern, values of  in the set {2,4,8,16} are compatible with existing MCCH and MSI periodicities (up to Release 16), such that the MCCHs and MSIs are only transmitted in the CAS “ON durations”.
Larger values of  can be supported by defining larger MCCH periodicities; there are currently seven spare values to achieve this.
With the above analysis, we have established that to support muting of the always-on signals for 5G Broadcast (to facilitate flexible TDM-ing with other broadcasting technologies such as DVB-T2), at the higher layers, we only need to define a semi-static muting configuration in SIB1-MBMS, where the configuration will state when the CAS is on, and when it is off. This is the only signalling update needed in TS 36.331.
With this in mind, we make the following proposal.
Proposal 1: The non-MBSFN subframes containing the cell acquisition signals (PSS/SSS/PBCH/SIB1) in an MBMS-dedicated cell shall only be transmitted within the first  out of every .
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {2,4,8,16}.
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {1,2,3, … ,15}.
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {0,1,2,3}
In the absence of the above parameters , all non-MBSFN subframes containing cell acquisition signals in an MBMS-dedicated cell shall be transmitted
Conclusion
In this contribution we presented our views on muting the always on signals for 5G Broadcast, to facilitate TDM-ing with other broadcasting technologies, such as DVB-T2. Our observations and proposal are summarized below.
Observation 1: The signals that need to be muted, to create blanks in 5G Broadcast transmissions in an MBMS-dedicated cell (which may be used to time-division multiplex other broadcast technologies with 5G Broadcast) are:
The Cell Acquisition Subframe (CAS)
The MCCH
The MSI
Observation 2: A repeating period, comprising a CAS ON duration followed by a CAS muted duration, must be a multiple of 160 ms in duration
This facilitates combining across (at least the first) four consecutive CASs, spaced 40 ms apart, within each such period, as supported in the current specifications.
Observation 3: A CAS “ON duration” comprising the first  out of every ( facilitates a 5G Broadcast duty cycle of  and allows for TDM-ing with other broadcasting technologies with a duty cycle of . 
Observation 4: Setting  results in a CAS ON duration of 240 ms, which minimizes resource wastage when 5G Broadcast is TDM-ed within the Future Extension Frames (FEFs) of DVB-T2, which are up to 250 ms duration each.
Observation 5: For a periodicity of , defining the periodic CAS muting pattern, values of  in the set {2,4,8,16} are compatible with existing MCCH and MSI periodicities (up to Release 16), such that the MCCHs and MSIs are only transmitted in the CAS “ON durations”.
Larger values of  can be supported by defining larger MCCH periodicities; there are currently seven spare values to achieve this.
Proposal 1: The non-MBSFN subframes containing the cell acquisition signals (PSS/SSS/PBCH/SIB1) in an MBMS-dedicated cell shall only be transmitted within the first  out of every .
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {2,4,8,16}.
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {1,2,3, … ,15}.
Introduce a new parameter , to be configured in SIB1-MBMS, from the set {0,1,2,3}
In the absence of the above parameters , all non-MBSFN subframes containing cell acquisition signals in an MBMS-dedicated cell shall be transmitted

4. References
[1] ETSI TS 102 755, V1.1.1 Digital Video Broadcasting (DVB); Frame structure channel coding and modulation for a second generation digital terrestrial television broadcasting system (DVB-T2), 2023.

TDoc file conclusion not found

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

Agenda item:	9.14
Source: 	Moderator (NTT DOCOMO, INC.)
Title: 	FL Summary #1 on Rel-19 TEIs
Document for:	Discussion and Decision

Conclusion
To be updated


Agreements in Rel-19 TEI
RAN1#120
Agreement
Extend Rel-18’s UL frequency hopping UL SRS for positioning transmission to non-RedCap UEs in a single carrier
UE capability for non-RedCap UEs for UL SRS frequency hopping for positioning transmission
Send LS to RAN2 to inform this agreement, whether new parameter is needed is up to RAN2 discussion.


Agreement
Send LS R1-2501573 to RAN2 with following information:
In RAN1#120 meeting TEI agenda, RAN1 has made the following agreement for enabling non-RedCap UE performing UL SRS frequency hopping for positioning:
As this agreement may relate to RAN2 specification, this liaison informs RAN2 about this agreement and whether new parameter for non-RedCap UE UL frequency hopping is needed is up to RAN2 discussion.
To RAN2
ACTION: RAN1 respectfully asks RAN2 to take the agreement into account in their Rel-19 specification, and feedback if there is any spec impact.


Agreement
If a UE is instructed to monitor PDCCH according to search space sets with a group index other than a designated index, the UE stops PDCCH monitoring according to search space sets with the group index and start PDCCH monitoring according to search space sets with the designated group index from the first slot that is at least P_switch symbols after the last symbol of a PUCCH carrying an SR.
Introduce corresponding UE capability and RRC parameters to enable/disable the above feature and indicate the designated SSSG index.
Send LS to RAN2 to inform above agreement and ask for the support of the UE capability and the corresponding RRC parameters.


Agreement
To resolve ambiguities with concurrent configuration of SRS-CS and ulTxswitch in a case where a UE configured with SRS CS on target CC and its “switch-from” CC on CC2 and configured with UL Tx switching operation for UL CC2 and at least one UL CC1 
Confirm that the prioritization rules in 38.214 Sec. 6.2.1.3 are applied between target and CC1, regardless of SRS-AS antenna port configuration on target CC, if UE indicates based on srs-SwitchingAffectedBandsListNR-r17 that SRS-CS on target impacts CC1, where CC1 is one of the CC(s) which may share Tx chains with source CC. No spec change is needed.
Note: if UE does not indicate srs-SwitchingAffectedBandsListNR-r17, UE can only perform simultaneous transmission when the total number of involved Tx chains for simultaneous transmission on all the bands/carriers is not greater than number of Tx chains supported by the UE for simultaneous UL transmission. No spec change is needed. 
If the UE is under the operation state in which all Tx chains are available at the source CC, the required switching time before the beginning of SRS-CS transmission on target CC is SRS-SwitchingTimeNR. Otherwise, the required switching time before the beginning of SRS-CS transmission on target CC is indicated by a UE capability. Details about UE capability will be discussed in UE feature session.
The existing scheduling restriction of maximum one switching per reference slot for UL Tx switching is also taking into account the triggered SRS CS
After SRS transmissions within an SRS resource set is done, if UE is indicated to transmit on CC1, the required switching time between the end of SRS-CS transmission on target CC and start of UL transmission on CC1 is indicated by the UE capability defined above. Otherwise, it is assumed for the determination of any future switching time that all Tx chains are returned to the source CC, and the RF tuning time to switch from target to source will be SRS-SwitchingTimeN

RAN1#119
Agreement
For up to 32 HARQ process numbers for TN in FR1 and FR2-1,
The value ranges of the new RRC parameters are defined as follows
harq-ProcessNumberSizeDCI-0-1-Ext-r19 with value range of ‘INTEGER (5)’, 
harq-ProcessNumberSizeDCI-1-1-Ext-r19 with value range of ‘INTEGER (5)’,
harq-ProcessNumberSizeDCI-0-2-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-1-2-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-0-3-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-1-3-Ext-r19 with value range of ‘INTEGER (0..5)’.


RAN1#118bis
Agreement
For the indication of whether a UE can simultaneously perform SRS carrier switches 
srs-SwitchingAffectedBandsListNR-r17 is the baseline for indication.
Details about UE capability will be discussed in UE feature session.
The structure of UE capability signalling is reused
Two SRS carrier switches are considered to be simultaneous if the SRS transmission (including RF retuning time) in both CCs overlap in time.
A UE that indicates it is not capable of simultaneous SRS carrier switching among a set of switching pairs is not expected to be configured / scheduled with simultaneous SRS carrier switching in the set of switching pairs.
Note: except for UE capability, the spec impact is only 38.214


Agreement
Support a maximum of 32 HARQ process numbers for TN in FR1 and FR2-1 in Rel-19.
Introduce new UE capabilities, by duplicating the Rel-17 UE FGs 24-8/24-9 defined for FR2-2 to FR1 and FR2-1.
The reporting granularity of the UE capabilities is changed to ‘per FSPC’. 
Introduce new RRC parameters, harq-ProcessNumberSizeDCI-0-1-Ext-r19, harq-ProcessNumberSizeDCI-1-1-Ext-r19, harq-ProcessNumberSizeDCI-0-2-Ext-r19, harq-ProcessNumberSizeDCI-1-2-Ext-r19, harq-ProcessNumberSizeDCI-0-3-Ext-r19, harq-ProcessNumberSizeDCI-1-3-Ext-r19.
For FR1, the above downlink related parameters can only be configured when the maximum number of layers configured for PDSCH is up to 4.
For FR1, the above uplink related parameters can only be configured when the maximum number of layers configured for PUSCH is up to 4.


Agreement
For the indication of whether a UE can simultaneously perform SRS carrier switches 
srs-SwitchingAffectedBandsListNR-r17 is the baseline for indication.
Details about UE capability will be discussed in UE feature session.
The structure of UE capability signalling is reused
Two SRS carrier switches are considered to be simultaneous if the SRS transmission (including RF retuning time) in both CCs overlap in time.
A UE that indicates it is not capable of simultaneous SRS carrier switching among a set of switching pairs is not expected to be configured / scheduled with simultaneous SRS carrier switching in the set of switching pairs.
Note: except for UE capability, the spec impact is only 38.214


Agreement
Support a maximum of 32 HARQ process numbers for TN in FR1 and FR2-1 in Rel-19.
Introduce new UE capabilities, by duplicating the Rel-17 UE FGs 24-8/24-9 defined for FR2-2 to FR1 and FR2-1.
The reporting granularity of the UE capabilities is changed to ‘per FSPC’. 
Introduce new RRC parameters, harq-ProcessNumberSizeDCI-0-1-Ext-r19, harq-ProcessNumberSizeDCI-1-1-Ext-r19, harq-ProcessNumberSizeDCI-0-2-Ext-r19, harq-ProcessNumberSizeDCI-1-2-Ext-r19, harq-ProcessNumberSizeDCI-0-3-Ext-r19, harq-ProcessNumberSizeDCI-1-3-Ext-r19.
For FR1, the above downlink related parameters can only be configured when the maximum number of layers configured for PDSCH is up to 4.
For FR1, the above uplink related parameters can only be configured when the maximum number of layers configured for PUSCH is up to 4.

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

Agenda item:	9.14
Source: 	Moderator (NTT DOCOMO, INC.)
Title: 	FL Summary #2 on Rel-19 TEIs
Document for:	Discussion and Decision

Conclusion
To be updated


Agreements in Rel-19 TEI
RAN1#120
Agreement
Extend Rel-18’s UL frequency hopping UL SRS for positioning transmission to non-RedCap UEs in a single carrier
UE capability for non-RedCap UEs for UL SRS frequency hopping for positioning transmission
Send LS to RAN2 to inform this agreement, whether new parameter is needed is up to RAN2 discussion.


Agreement
Send LS R1-2501573 to RAN2 with following information:
In RAN1#120 meeting TEI agenda, RAN1 has made the following agreement for enabling non-RedCap UE performing UL SRS frequency hopping for positioning:
As this agreement may relate to RAN2 specification, this liaison informs RAN2 about this agreement and whether new parameter for non-RedCap UE UL frequency hopping is needed is up to RAN2 discussion.
To RAN2
ACTION: RAN1 respectfully asks RAN2 to take the agreement into account in their Rel-19 specification, and feedback if there is any spec impact.


Agreement
If a UE is instructed to monitor PDCCH according to search space sets with a group index other than a designated index, the UE stops PDCCH monitoring according to search space sets with the group index and start PDCCH monitoring according to search space sets with the designated group index from the first slot that is at least P_switch symbols after the last symbol of a PUCCH carrying an SR.
Introduce corresponding UE capability and RRC parameters to enable/disable the above feature and indicate the designated SSSG index.
Send LS to RAN2 to inform above agreement and ask for the support of the UE capability and the corresponding RRC parameters.


Agreement
To resolve ambiguities with concurrent configuration of SRS-CS and ulTxswitch in a case where a UE configured with SRS CS on target CC and its “switch-from” CC on CC2 and configured with UL Tx switching operation for UL CC2 and at least one UL CC1 
Confirm that the prioritization rules in 38.214 Sec. 6.2.1.3 are applied between target and CC1, regardless of SRS-AS antenna port configuration on target CC, if UE indicates based on srs-SwitchingAffectedBandsListNR-r17 that SRS-CS on target impacts CC1, where CC1 is one of the CC(s) which may share Tx chains with source CC. No spec change is needed.
Note: if UE does not indicate srs-SwitchingAffectedBandsListNR-r17, UE can only perform simultaneous transmission when the total number of involved Tx chains for simultaneous transmission on all the bands/carriers is not greater than number of Tx chains supported by the UE for simultaneous UL transmission. No spec change is needed. 
If the UE is under the operation state in which all Tx chains are available at the source CC, the required switching time before the beginning of SRS-CS transmission on target CC is SRS-SwitchingTimeNR. Otherwise, the required switching time before the beginning of SRS-CS transmission on target CC is indicated by a UE capability. Details about UE capability will be discussed in UE feature session.
The existing scheduling restriction of maximum one switching per reference slot for UL Tx switching is also taking into account the triggered SRS CS
After SRS transmissions within an SRS resource set is done, if UE is indicated to transmit on CC1, the required switching time between the end of SRS-CS transmission on target CC and start of UL transmission on CC1 is indicated by the UE capability defined above. Otherwise, it is assumed for the determination of any future switching time that all Tx chains are returned to the source CC, and the RF tuning time to switch from target to source will be SRS-SwitchingTimeN

RAN1#119
Agreement
For up to 32 HARQ process numbers for TN in FR1 and FR2-1,
The value ranges of the new RRC parameters are defined as follows
harq-ProcessNumberSizeDCI-0-1-Ext-r19 with value range of ‘INTEGER (5)’, 
harq-ProcessNumberSizeDCI-1-1-Ext-r19 with value range of ‘INTEGER (5)’,
harq-ProcessNumberSizeDCI-0-2-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-1-2-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-0-3-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-1-3-Ext-r19 with value range of ‘INTEGER (0..5)’.


RAN1#118bis
Agreement
For the indication of whether a UE can simultaneously perform SRS carrier switches 
srs-SwitchingAffectedBandsListNR-r17 is the baseline for indication.
Details about UE capability will be discussed in UE feature session.
The structure of UE capability signalling is reused
Two SRS carrier switches are considered to be simultaneous if the SRS transmission (including RF retuning time) in both CCs overlap in time.
A UE that indicates it is not capable of simultaneous SRS carrier switching among a set of switching pairs is not expected to be configured / scheduled with simultaneous SRS carrier switching in the set of switching pairs.
Note: except for UE capability, the spec impact is only 38.214


Agreement
Support a maximum of 32 HARQ process numbers for TN in FR1 and FR2-1 in Rel-19.
Introduce new UE capabilities, by duplicating the Rel-17 UE FGs 24-8/24-9 defined for FR2-2 to FR1 and FR2-1.
The reporting granularity of the UE capabilities is changed to ‘per FSPC’. 
Introduce new RRC parameters, harq-ProcessNumberSizeDCI-0-1-Ext-r19, harq-ProcessNumberSizeDCI-1-1-Ext-r19, harq-ProcessNumberSizeDCI-0-2-Ext-r19, harq-ProcessNumberSizeDCI-1-2-Ext-r19, harq-ProcessNumberSizeDCI-0-3-Ext-r19, harq-ProcessNumberSizeDCI-1-3-Ext-r19.
For FR1, the above downlink related parameters can only be configured when the maximum number of layers configured for PDSCH is up to 4.
For FR1, the above uplink related parameters can only be configured when the maximum number of layers configured for PUSCH is up to 4.


Agreement
For the indication of whether a UE can simultaneously perform SRS carrier switches 
srs-SwitchingAffectedBandsListNR-r17 is the baseline for indication.
Details about UE capability will be discussed in UE feature session.
The structure of UE capability signalling is reused
Two SRS carrier switches are considered to be simultaneous if the SRS transmission (including RF retuning time) in both CCs overlap in time.
A UE that indicates it is not capable of simultaneous SRS carrier switching among a set of switching pairs is not expected to be configured / scheduled with simultaneous SRS carrier switching in the set of switching pairs.
Note: except for UE capability, the spec impact is only 38.214


Agreement
Support a maximum of 32 HARQ process numbers for TN in FR1 and FR2-1 in Rel-19.
Introduce new UE capabilities, by duplicating the Rel-17 UE FGs 24-8/24-9 defined for FR2-2 to FR1 and FR2-1.
The reporting granularity of the UE capabilities is changed to ‘per FSPC’. 
Introduce new RRC parameters, harq-ProcessNumberSizeDCI-0-1-Ext-r19, harq-ProcessNumberSizeDCI-1-1-Ext-r19, harq-ProcessNumberSizeDCI-0-2-Ext-r19, harq-ProcessNumberSizeDCI-1-2-Ext-r19, harq-ProcessNumberSizeDCI-0-3-Ext-r19, harq-ProcessNumberSizeDCI-1-3-Ext-r19.
For FR1, the above downlink related parameters can only be configured when the maximum number of layers configured for PDSCH is up to 4.
For FR1, the above uplink related parameters can only be configured when the maximum number of layers configured for PUSCH is up to 4.

3GPP TSG RAN WG1 #118bis		     	 R1-2503073
Wuhan, China, April 7th – 11th, 2025
Agenda item:	9.14
Source: 	Qualcomm Incorporated, Apple Inc, ZTE Corporation, Verizon
Title: 	Proposal for Rel-19 RAN1 TEI
Document for:	Discussion/Decision

Conclusions
The following proposal is proposed to address the issue of no gap between back-to-back PUCCH/PUSCH and SRS transmissions. 
Proposal 1: Except for the following special case, at least Y symbol gap is expected between a PUCCH/PUSCH transmission resource and a xTyR (where x

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

Agenda item:	9.14
Source: 	Moderator (NTT DOCOMO, INC.)
Title: 	FL Summary #3 on Rel-19 TEIs
Document for:	Discussion and Decision

Conclusion
Agreement
For simultaneous CSI-RS reception in UE features 2-33, 2-36, 2-40, 2-41, 2-43, 16-3a and 16-3b, define 1 new UE capability:
UE capability 1: To allow the UE to indicate that CSI-RS ports within one periodic/semi-persistent CSI-RS resource, as well as the periodic/semi-persistent CSI-RS resource, are counted as one resource, even if the periodic/semi-persistent CSI-RS resource is referred by N Report Settings.


Agreement
The non-MBSFN subframes containing the cell acquisition signals (PSS/SSS/PBCH/SIB1) in an MBMS-dedicated cell shall only be transmitted within the first (k×40) ms out of every (n×160) ms.
Introduce a new parameter n, to be configured for support MBMS, from the set {2,4,8,16}.
Introduce a new parameter k, to be configured for support MBMS, from the set {4,5,6,7,…,63}
In the absence of the above parameters {n,k}, all non-MBSFN subframes containing cell acquisition signals in an MBMS-dedicated cell shall be transmitted
NOTE: For a MBMS-dedicated cell, there is no RAN4 impact from the above TEI proposal.


Agreement 
Adopt the following TP to Section 6.2.1.4.1, TS 38.214.


Agreement
Adopt the following TPs to TS 38.212.


Agreements in Rel-19 TEI
RAN1#120bis
Agreement
For simultaneous CSI-RS reception in UE features 2-33, 2-36, 2-40, 2-41, 2-43, 16-3a and 16-3b, define 1 new UE capability:
UE capability 1: To allow the UE to indicate that CSI-RS ports within one periodic/semi-persistent CSI-RS resource, as well as the periodic/semi-persistent CSI-RS resource, are counted as one resource, even if the periodic/semi-persistent CSI-RS resource is referred by N Report Settings.


Agreement
The non-MBSFN subframes containing the cell acquisition signals (PSS/SSS/PBCH/SIB1) in an MBMS-dedicated cell shall only be transmitted within the first (k×40) ms out of every (n×160) ms.
Introduce a new parameter n, to be configured for support MBMS, from the set {2,4,8,16}.
Introduce a new parameter k, to be configured for support MBMS, from the set {4,5,6,7,…,63}
In the absence of the above parameters {n,k}, all non-MBSFN subframes containing cell acquisition signals in an MBMS-dedicated cell shall be transmitted
NOTE: For a MBMS-dedicated cell, there is no RAN4 impact from the above TEI proposal.


Agreement 
Adopt the following TP to Section 6.2.1.4.1, TS 38.214.


Agreement
Adopt the following TPs to TS 38.212.

RAN1#120
Agreement
Extend Rel-18’s UL frequency hopping UL SRS for positioning transmission to non-RedCap UEs in a single carrier
UE capability for non-RedCap UEs for UL SRS frequency hopping for positioning transmission
Send LS to RAN2 to inform this agreement, whether new parameter is needed is up to RAN2 discussion.

Agreement
Send LS R1-2501573 to RAN2 with following information:
In RAN1#120 meeting TEI agenda, RAN1 has made the following agreement for enabling non-RedCap UE performing UL SRS frequency hopping for positioning:
As this agreement may relate to RAN2 specification, this liaison informs RAN2 about this agreement and whether new parameter for non-RedCap UE UL frequency hopping is needed is up to RAN2 discussion.
To RAN2
ACTION: RAN1 respectfully asks RAN2 to take the agreement into account in their Rel-19 specification, and feedback if there is any spec impact.

Agreement
If a UE is instructed to monitor PDCCH according to search space sets with a group index other than a designated index, the UE stops PDCCH monitoring according to search space sets with the group index and start PDCCH monitoring according to search space sets with the designated group index from the first slot that is at least P_switch symbols after the last symbol of a PUCCH carrying an SR.
Introduce corresponding UE capability and RRC parameters to enable/disable the above feature and indicate the designated SSSG index.
Send LS to RAN2 to inform above agreement and ask for the support of the UE capability and the corresponding RRC parameters.

Agreement
To resolve ambiguities with concurrent configuration of SRS-CS and ulTxswitch in a case where a UE configured with SRS CS on target CC and its “switch-from” CC on CC2 and configured with UL Tx switching operation for UL CC2 and at least one UL CC1 
Confirm that the prioritization rules in 38.214 Sec. 6.2.1.3 are applied between target and CC1, regardless of SRS-AS antenna port configuration on target CC, if UE indicates based on srs-SwitchingAffectedBandsListNR-r17 that SRS-CS on target impacts CC1, where CC1 is one of the CC(s) which may share Tx chains with source CC. No spec change is needed.
Note: if UE does not indicate srs-SwitchingAffectedBandsListNR-r17, UE can only perform simultaneous transmission when the total number of involved Tx chains for simultaneous transmission on all the bands/carriers is not greater than number of Tx chains supported by the UE for simultaneous UL transmission. No spec change is needed. 
If the UE is under the operation state in which all Tx chains are available at the source CC, the required switching time before the beginning of SRS-CS transmission on target CC is SRS-SwitchingTimeNR. Otherwise, the required switching time before the beginning of SRS-CS transmission on target CC is indicated by a UE capability. Details about UE capability will be discussed in UE feature session.
The existing scheduling restriction of maximum one switching per reference slot for UL Tx switching is also taking into account the triggered SRS CS
After SRS transmissions within an SRS resource set is done, if UE is indicated to transmit on CC1, the required switching time between the end of SRS-CS transmission on target CC and start of UL transmission on CC1 is indicated by the UE capability defined above. Otherwise, it is assumed for the determination of any future switching time that all Tx chains are returned to the source CC, and the RF tuning time to switch from target to source will be SRS-SwitchingTimeN

RAN1#119
Agreement
For up to 32 HARQ process numbers for TN in FR1 and FR2-1,
The value ranges of the new RRC parameters are defined as follows
harq-ProcessNumberSizeDCI-0-1-Ext-r19 with value range of ‘INTEGER (5)’, 
harq-ProcessNumberSizeDCI-1-1-Ext-r19 with value range of ‘INTEGER (5)’,
harq-ProcessNumberSizeDCI-0-2-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-1-2-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-0-3-Ext-r19 with value range of ‘INTEGER (0..5)’, 
harq-ProcessNumberSizeDCI-1-3-Ext-r19 with value range of ‘INTEGER (0..5)’.


RAN1#118bis
Agreement
For the indication of whether a UE can simultaneously perform SRS carrier switches 
srs-SwitchingAffectedBandsListNR-r17 is the baseline for indication.
Details about UE capability will be discussed in UE feature session.
The structure of UE capability signalling is reused
Two SRS carrier switches are considered to be simultaneous if the SRS transmission (including RF retuning time) in both CCs overlap in time.
A UE that indicates it is not capable of simultaneous SRS carrier switching among a set of switching pairs is not expected to be configured / scheduled with simultaneous SRS carrier switching in the set of switching pairs.
Note: except for UE capability, the spec impact is only 38.214

Agreement
Support a maximum of 32 HARQ process numbers for TN in FR1 and FR2-1 in Rel-19.
Introduce new UE capabilities, by duplicating the Rel-17 UE FGs 24-8/24-9 defined for FR2-2 to FR1 and FR2-1.
The reporting granularity of the UE capabilities is changed to ‘per FSPC’. 
Introduce new RRC parameters, harq-ProcessNumberSizeDCI-0-1-Ext-r19, harq-ProcessNumberSizeDCI-1-1-Ext-r19, harq-ProcessNumberSizeDCI-0-2-Ext-r19, harq-ProcessNumberSizeDCI-1-2-Ext-r19, harq-ProcessNumberSizeDCI-0-3-Ext-r19, harq-ProcessNumberSizeDCI-1-3-Ext-r19.
For FR1, the above downlink related parameters can only be configured when the maximum number of layers configured for PDSCH is up to 4.
For FR1, the above uplink related parameters can only be configured when the maximum number of layers configured for PUSCH is up to 4.

Agreement
For the indication of whether a UE can simultaneously perform SRS carrier switches 
srs-SwitchingAffectedBandsListNR-r17 is the baseline for indication.
Details about UE capability will be discussed in UE feature session.
The structure of UE capability signalling is reused
Two SRS carrier switches are considered to be simultaneous if the SRS transmission (including RF retuning time) in both CCs overlap in time.
A UE that indicates it is not capable of simultaneous SRS carrier switching among a set of switching pairs is not expected to be configured / scheduled with simultaneous SRS carrier switching in the set of switching pairs.
Note: except for UE capability, the spec impact is only 38.214

Agreement
Support a maximum of 32 HARQ process numbers for TN in FR1 and FR2-1 in Rel-19.
Introduce new UE capabilities, by duplicating the Rel-17 UE FGs 24-8/24-9 defined for FR2-2 to FR1 and FR2-1.
The reporting granularity of the UE capabilities is changed to ‘per FSPC’. 
Introduce new RRC parameters, harq-ProcessNumberSizeDCI-0-1-Ext-r19, harq-ProcessNumberSizeDCI-1-1-Ext-r19, harq-ProcessNumberSizeDCI-0-2-Ext-r19, harq-ProcessNumberSizeDCI-1-2-Ext-r19, harq-ProcessNumberSizeDCI-0-3-Ext-r19, harq-ProcessNumberSizeDCI-1-3-Ext-r19.
For FR1, the above downlink related parameters can only be configured when the maximum number of layers configured for PDSCH is up to 4.
For FR1, the above uplink related parameters can only be configured when the maximum number of layers configured for PUSCH is up to 4.

TDoc file reading error