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

Agenda Item:	9.11.1
Source:	Huawei, HiSilicon
Title:	Discussion on downlink coverage enhancements for NR NTN
Document for:	Discussion and Decision 

Conclusions
In this contribution, downlink coverage enhancements are discussed based on the link level and system level evaluations according to the agreed methodology in RAN1#116. The following observations and proposals are proposed:
Observation 1: Managing thousands or hundreds of timing configurations simultaneously would significantly increase the gNB complexity.
Observation 2: Transmitting Type0-PDCCH and SIB1 PDSCH associated with different SSB beam in different SSB periods causes larger access delay and longer dwell time, which is contradictory with the benefit of configuring M=1 and M=1/2 to determine a shorter duration of Type0-CSS monitoring. 
Observation 3: For M=1 or M=1/2, transmitting Type0-PDCCH and SIB1 PDSCH associated with different SSB beams in the same SSB period should be supported. 
Observation 4: SIB1 has smaller coverage gap than common PDCCH, it is reasonable to consider the scenario when Type0 PDCCH repetition is not required while the PDSCH-SIB1 repetition is required. 


Proposal 1: Send LS to RAN4 to inform that from RAN1 perspective option 1 and option 2 are suggested to be further down-selected by RAN4.
Proposal 2: A validity window is introduced to indicate a subset of RACH occasions, where only the RACH occasions within the window are considered to be valid for PRACH transmission:
The length and an offset to configure the window location are introduced.
Proposal 3: Support cross-SSB-beam repetition for Type0 PDCCH repetition to enable intra-SSB-beam repetition in consecutive slot n0 and n0+1 at least for the case when M=1 and M=1/2.
Proposal 4: Using reserved bits ,  in PBCH payload to indicate the following combinations of PDCCH repetition solutions:
Both intra-SSB-beam repetition and cross-SSB-beam repetition are enabled;
Only intra-SSB-beam repetition is enabled;
Only cross-SSB beam repetition is enabled;
No PDCCH repetition for Type0-CSS;
Proposal 5: Confirm the working assumption:
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported. 
Proposal 6: Similar as Type0-CSS, support cross-SSB-beam repetition for type0A-CSS PDCCH.
Proposal 7: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS and the PDCCH CSS is configured by SearchSpaceZero, support inter-slot repetition which is the same as PDCCH repetition for Type0-CSS. 
Proposal 8: Support option 3 for enabling/disabling SIB1 PDSCH repetition. 
Proposal 9: Cross-SSB-beam repetition is also supported for SIB1 PDSCH repetition when cross-SSB-beam repetition is enabled for type0-CSS PDCCH.
Proposal 10: Option 3 is preferred, i.e. Msg4 repetition is configured by SIB1 for Msg4 repetition. 
Proposal 11: Support UE request for Msg4 PDSCH repetition transmission, i.e., through Msg3 PUSCH.
Proposal 12: Support the applicability of Msg4 PDSCH repetition solution to the PDSCHs after Msg4 but before the RRC connection set-up is completed. 

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

 
Agenda Item:	9.11.1
Source:	Ericsson
Title:	On NR-NTN downlink coverage enhancement
Document for:	Discussion

Conclusion
In the previous sections we made the following observations: 
Observation 1	By assuming a 5 MHz CBW, 15 kHz SCS, 4SSB indices, 24-PRB CORESET#0 with 2-OFDM symbols, and upon inspecting different combinations of  and  in Table 13-11 of TS 38.213, two SSB indices per NTN cell are usable without any overlapping of consecutive slots for indices: 0, 2, 4, 6, 10, 11, 12, 13, 14, 15 while there exist either partial or full overlapping of consecutive slots for indices 1, 3, 5, 7.

Based on the discussion in the previous sections we propose the following:
Proposal 1	For a single SSB beam per NTN-cell and SSB and CORESET multiplexing pattern 1, the scheme considered for repetition of Type0 PDCCH CSS for M = 2 is also applicable to M = 1 and M = ½ without any overlapping of consecutive slots.
Proposal 2	For multiple SSB beams per NTN-cell with SSB and CORESET multiplexing pattern 1,  the scheme considered for repetition of Type0 PDCCH CSS for M = 2 is also applicable to M = 1 (i.e., indices 0, 2, 4, 6, 10-15 in Table 13-11 in TS 38.213) without any overlapping of consecutive slots associated with two SSB indices, i.e., either SSB indices = 0 and 2 or SSB indices 1 and 3.
Proposal 3	For multiple SSB beams per NTN-cell SSB and CORESET multiplexing pattern 1, the scheme considered for repetition of Type0 PDCCH CSS for M = 2 is applicable to M = 1/2 (i.e., indices 1, 3, 5, 7 in Table 13-11 in TS 38.213) with either partial or full overlapping of consecutive slots associated with two SSB indices.
Proposal 4	RAN1 to not consider the scheme of repeating PDCCH candidates in the two slots  and  [or  and  ] associated with the same SSB index (  as defined in section 13 of TS 38.213) where  for  and  for  due to its limitations such as increased specification impact and increased buffer and delay requirements for PDCCH decoding as well as the issue of backward compatibility for the legacy UEs that are not able to monitor slot  or .
Proposal 5	The scheme of repeating PDCCH candidates in two consecutive slots associated with different SSB indexes for  and  can only work in best-effort manner across different UE locations within the cell and hence may not be an attractive solution with respect to coverage enhancement.
Proposal 6	For the support of repetitions for Type0-PDCCH, RAN1 to adopt a unified solution for different cases of M, i.e., solution agreed for M = 2 is applied to M = 1 and M = ½ based on the network implementation.
Proposal 7	RAN1 to consider intra-slot repetition based on Option 1: Use same CORESET and two different SS (SS Set1 and SS Set2) for repetition of PDCCH CSS other than Type-0 CSS and other than Type-3 CSS.
Proposal 8	Blind decoding limit definition in the context of repetitions of PDCCH CSS for NTN operation shall ensure at least the combining of soft-bits to maximize the coverage benefits.
Proposal 9	RAN1 to not pursue the case where type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed.
Proposal 10	RAN1 to consider Option 3, i.e., the enabling/disabling of SIB1 PDSCH repetition is implicitly indicating by the enabling/disabling of Type-0 CSS PDCCH repetition.
Proposal 11	RAN1 to further discuss whether link-level enhancements for PDSCH with SIB1 may be applicable to other SIBs, e.g., SIB19.
Proposal 12	RAN1 to prioritize Option 2 to indicate the enabling of repetitions for PDSCH with MSG4 that is to determine implicitly based on the SIB1 PDSCH repetition as it allows to reduce the signaling overhead and the specification impact.
Proposal 13	RAN1 to support configuring MSG4 aggregation factor (i.e., number of repetitions) in SIB1.
Proposal 14	RAN1 to exclude UE capability reports for MSG4 PDSCH repetitions to minimize specification impact and signaling overhead, while ensuring backward compatibility with legacy UEs.

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

Source:	vivo
Title:	Discussions on NR-NTN downlink coverage enhancement
Agenda Item:	9.11.1
Document for:	Discussion and Decision

Conclusion
In this contribution, we provide our views on downlink coverage enhancement for NR-NTN. According to the discussions, we have following observations and proposals: 
Observation 1: The mTRP PDCCH repetition scheme only supports intra-slot repetition, while only inter-slot repetition should be supported for Type-0 CSS PDCCH. Therefore, the mTRP PDCCH repetition scheme should not be extended to the Type-0 CSS PDCCH configured by searchSpaceSIB1.
Observation 2: There are several methods to indicate the configuration of Msg4 PDSCH repetition, including
Option 1: Indicated by DCI scheduling Msg4 PDSCH
Option 2: Configured by SIB1
Option 3: Configured by SIB1, and indicated by DCI
For the above options, Option 1 and Option 3 raise compatibility issues, while Option 2 can provide sufficient scheduling flexibility, especially in NTN case. Moreover, Option 1 and Option 3 have larger spec changes than Option 2 does. Thus, Option 1 and Option 3 should also be deprioritized.

Proposal 1: The condition (i.e., subject to UE capability) of supporting the SSB periodicity of 160ms during initial cell selection should be captured in the draft CR of TS 38.213.
Proposal 2: A unified and single solution is a must to support the PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, and it should be able to support all choices of M. Support to repeat PDCCH candidates in the two slots  and  [or  and  ] associated with the same SSB index .
Proposal 3: If searchSpaceSIB1 is configured to be zero (i.e., search space #0), the Type-0 CSS PDCCH repetition follows the configuration of Type-0 CSS PDCCH configured by searchSpaceZero. Otherwise, i.e., searchSpaceSIB1 is configured to search space other than search space zero (i.e., in a BWP not overlapping with initial BWP), the Type-0 CSS PDCCH repetition is disabled.
Proposal 4: For the CSS other than Type-0 CSS, e.g., Type-0A/1/1A/2/2A, if searchSpaceZero is not used for these CSSes, e.g., by configuring a new search spaces via the SIB, the R17 mTRP PDCCH repetition scheme is reused, i.e., applying a same CORESET with two linked different SS (SS Set1 and SS Set2).
Proposal 5: For the CSS other than Type-0 CSS, searchspace zero should not be used if Type-0 PDCCH repetition is enabled.
Proposal 6: When Type-0 CSS PDCCH repetition is enabled in SS#0, the repetition is not applied to fallback DCI (e.g., DCI with CRC scrambled by C-RNTI).
Proposal 7: RAN1 to clarify whether the UE should still monitor the USS fallback PDCCH candidates (e.g., DCI 1_0 with CRC scrambled by C-RNTI) in the SS#0 when Type-0 CSS PDCCH repetition is enabled.
Proposal 8: If UE is enabled with Type-0 CSS PDCCH repetition, UE should consider the BD to be counted as 1 in the early slot, and to be counted as 1 or 2 in the later slot, depending on the UE behavior to monitor the USS fallback PDCCH candidates when Type-0 CSS PDCCH repetition is enabled in SS#0 and the repetition is not applied to fallback DCI. Specifically, in the later slot,
Option A: UE performs two BDs, one for the combined PDCCH candidate for SI-RNTI and the other for PDCCH candidate for the UE-specific RNTI
Option B: UE performs only one BD for the combined PDCCH candidate for SI-RNTI 
Proposal 9: Support Option 3 to enable/disable SIB1 PDSCH repetition, i.e., the enabling/disabling of SIB1 PDSCH repetition follows that of Type-0 CSS PDCCH repetition.
Proposal 10: It is desirable to indicate the configuration of Msg4 PDSCH repetition by SIB1, including enabling/disabling Msg4 PDSCH repetition, and repetition number.
Proposal 11: It is desirable to indicate the UE capability of Msg4 PDSCH repetition by higher layer signalings in MsgA PUSCH or Msg3 PUSCH, e.g., LCID.
Proposal 12: At least the higher-layer parameters for defining the Msg4 PDSCH repetition number and a larger common searchspace list should be considered for downlink coverage enhancements for NR NTN.

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

Agenda Item:	9.11.1
Source:	Spreadtrum, UNISOC
Title:	Discussion on NR-NTN downlink coverage enhancement 
Document for:	Discussion and decision

Conclusion
In this contribution, we provided views on Redcap positioning. In summary, we have following observations and proposals:
Proposal 1: The reserved 1 bit of in PBCH payload can be used for enabling PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero, which aligns with the draft CR.
Proposal 2: Repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index (  as defined in section 13 of TS 38.213) for all M values should be supported.
Proposal 3: For number of BDs corresponding to two PDCCH candidates that are linked for PDCCH repetition of Type0-PDCCH CSS, 2 or 3 BDs for the two PDCCH candidates are supported.
When 3 BDs are counted for two linked candidates, the third BD is counted in the later slot PDCCH repetition.
Proposal 4: If searchSpaceSIB1 is set to a search space other than zero, meaning it does not overlap with the initial bandwidth part (BWP), the Type-0 CSS PDCCH repetition is disabled.
Proposal 5: The following working assumption can be confirmed

Proposal 6: Search space linkage based PDCCH repetition in R17 can be reused for PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero (i.e., Option 1)
Proposal 7: For number of BDs corresponding to two PDCCH candidates that are linked for PDCCH repetition of Type0A/1/2-PDCCH CSS, 2 or 3 BDs for the two PDCCH candidates are supported.
When 3 BDs are counted for two linked candidates, the third BD is counted in the later span for inter-span PDCCH repetition, which is same as Rel-17.
Proposal 8: For PDSCH with Msg4 Link level enhancement, the Msg4 PDSCH repetition can be indicated by DCI scheduling Msg4, Option 1.
Proposal 9: For UE capability of support PDSCH repetition, UE can report its request/capability of Msg4 PDSCH repetition via MAC-CE in Msg3 PUSCH.
Proposal 10: The case of type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed should not be supported.
Proposal 11: The enabling/disabling of SIB1 PDSCH repetition is implicitly indicating by the enabling/disabling of Type-0 CSS PDCCH repetition (i.e., Option 3).

3GPP TSG RAN WG1 #121    		                           R1-2503582
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:		9.11.1
Source:			Samsung
Title:			Discussion on downlink coverage enhancement for NR-NTN
Document for:		Discussion and decision

Conclusion
This contribution discusses remaining issues for downlink coverage enhancements. Followings are proposals in this contribution. 
Proposal 1: Support option 1 to enable intra-slot PDCCH repetition for PDCCH CSS other than Type-0 CSS and other than Type-3 CSS

Proposal 2: Not support that type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed

Proposal 3: Support the unified solution regardless of M values. If there is no consensus, M=2 is only supported in Rel-19

Proposal 4: Support to update the agreement as follows

Proposal 5: Support options 1 and 3 for Msg4 PDSCH repetition with the followings
Enabling PDSCH repetition using TDRA table or other DCI field
Msg3 PUSCH is used for UE capability reporting

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

Source:	ZTE Corporation, Sanechips
Title:	Discussion on DL coverage enhancement for NR NTN
Agenda Item:	9.11.1
Document for:   Discussion

Conclusions 
In this contribution, the system level and link level analysis are provided with following observation and proposals.
Proposal 1: Different periodicity per SSB can supported with the consideration on uneven traffic load among different beams. 
Proposal 2: Multiple SSB periodicities and respective SSB index sets can be provided in SIB1 to guarantee measurement precision, power efficiency, and reporting reliability.
Proposal 3: An active time configuration for valid ROs can be used with the usage of beam hopping.
Observation 1: The performance of cross-SSB beam combination is variant for different UEs and beam footprints, which cannot mitigate the coverage gap for sure.
Observation 2: Compared with option 1, option 2 will cause additional buffer requirement and cannot accelerate beam sweeping with smaller M values.
Proposal 4: For PDCCH repetition for Type0 PDCCH CSS, repeated PDCCH candidates in the two consecutive slots   and  associated with the same SSB index for all M values is preferred.
Proposal 5: For PDCCH repetition for Type0 PDCCH CSS, the repeated PDCCH candidates in the two slots is counted as 1 PDCCH candidate in first slot.
Proposal 6: The solution for PDCCH repetition for Type0-PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 should also be applied for searchSpaceZero configured in PDCCH-ConfigCommon.
Proposal 7: The enabling/disabling for PDCCH repetition for Type0-PDCCH CSS of searchSpaceZero can be additionally configured in SIB1, where the interpretation of signalled values are same as the enabling/disabling indication in PBCH.
Proposal 8: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot repetition based on SS linking should be adopted to reuse existing specification.
Proposal 9: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for SearchSpaceZero, intra-slot repetition based on SS linking should also be supported to maintain the flexibility search space configuration.
Proposal 10: For SearchSpaceZero, if a PDCCH CSS other than SearchSpaceZero is configured with a pre-defined linking ID, this PDCCH CSS is considered to be linked with SearchSpaceZero.
Proposal 11: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS, the enabling for PDCCH repetition can be implicitly indicated by linking another SS to the PDCCH CSS.
Proposal 12: The enabling/disabling of SIB1 PDSCH repetition is implicitly indicating by the enabling/disabling of Type-0 CSS PDCCH repetition.
Proposal 13: For Msg4 PDSCH repetition, a single repetition factor between 2 and 4 can be configured in SIB1.
Observation 3: PDSCH with Msg4 has similar performance as PDSCH with SIB1. The repetition enabling can be bundled.
Proposal 14: The enabling/disabling of Msg4 PDSCH repetition is implicitly indicated by the enabling/disabling of SIB1 PDSCH repetition.
Observation 4: Msg4 PDSCH repetition should not depend on the capability of a single UE, since it is to be received by multiple UEs.
Proposal 15: For repetition of PDSCH with Msg4, UE capability report is not needed.

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

Agenda Item:	9.11.1	
Source:	Thales
Title:	NR NTN Downlink coverage enhancements
Document for:	Discussion and decision

Conclusion

In this contribution. we made the following observations and proposals:

Default value of SSB periodicity

Observation 1: According to the RAN1#120 agreement, the maximum default SSB periodicity, apart from the existing 20ms value, is 160ms. Therefore, cells supporting initial access could have SSB periods of 5, 10, 20, 40, 80, or 160ms.

Monitoring period of PDCCH in the Type0-PDCCH CSS 

Proposal 1
For NTN with extended SSB periodicity, type0-PDCCH CSS set periodicity is as defined in clause 13 of TS 38.213.

Impact on UE’s cell search complexity and delay

Proposal 2
RAN1 to check whether a modification could be done on the channel raster to reduce the overall cell search time. 

Type0-PDCCH link level enhancement

Observation 2: In existing specifications, in FR1 with SS/PBCH block and CORESET multiplexing pattern 1, there are 2 type-0 SS Set in consecutive slots and two candidates SIB1 transmission for each SSB index.  a UE monitors PDCCH in the Type0-PDCCH CSS set over these two slots. In fact, only 1 of the 2 candidates is expected to be used. That is, the gNB can select between the two candidates. However, the UE is supposed to monitor both SS Sets for SIB1 PDSCH resource allocation.

Observation 3: To bridge the gap for PDCCH, 2 dB coverage enhancement are needed, and thereby two repetitions would be enough.

Observation 4: For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, Option 1 can be adopted for M=1 and M=½ when digital beamforming is employed. This requires that at least two simultaneous beams be illuminated. If two beams cannot be illuminated simultaneously, then M=2 could be configured.

Proposal 3 
For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, support repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index (  as defined in section 13 of TS 38.213).
Repeated PDCCH candidates share the same aggregation level (AL), coded bits and same candidate index
Note: if the network repeats the Type 0 PDCCH across two consecutive slots, a legacy UE might decode the PDCCH and associated PDSCH in one slot and skip PDCCH monitoring in the other slot. 
Note: all the values of M could be supported by configuration/implementation.

Proposal 4
For inter-slot PDCCH CSS repetition, the following BD is assumed: In later slot, one BD (Decode of the second PDCCH or Decode of a soft-combined PDCCH).
It should be defined in the specs that the BD counted in the later slot is 1. By implementation, UE determines either single or soft-combined PDCCH candidate to be detected.

Proposal 5
If searchSpaceSIB1 is set to zero, corresponding to search space #0, the Type-0 CSS PDCCH repetition adheres to the configuration specified by searchSpaceZero configured within MIB pdcch-ConfigSIB1. Conversely, if searchSpaceSIB1 is set to a search space other than zero, meaning it does not overlap with the initial bandwidth part (BWP), the Type-0 CSS PDCCH repetition is disabled.

Other CSS type PDCCH link level enhancement 

Proposal 6
For PDCCH link level enhancements support intra-slot repetition for Type0A-PDCCH, Type1-PDCCH and Type2-PDCCH.

Proposal 7
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported using same CORESET and two different SS (SS Set1 and SS Set2)
Linking two PDCCH candidates:
support linking two SS sets by configuration in SIB1 and dedicated signaling:
When PDCCH repetition is monitored in two linked SS sets, the UE does not expect a third monitored SS set to be linked with any of the two linked SS sets.
The two linked SS sets have the same DCI formats to monitor
The two SS sets should have the same periodicity and offset and the same duration
For linking monitoring occasions across the two SS sets that exist in the same slot: 
The two SS sets have the same number of monitoring occasions within a slot and n-th monitoring occasion of one SS set is linked to n-th monitoring occasion of the other SS set.

FFS: Blind decoding limit

Proposal 8
The following SS sets can be linked to another SS set for PDCCH repetition: SS set 0 which is not configured within MIB pdcch-ConfigSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace and SS set configured by recoverySearchSpaceId.
The parameter SearchSpaceLinkingId should be updated accordingly.

Proposal 9
When two PDCCH candidates are linked for PDCCH repetition, RAN1 to discuss, how they should be counted toward the BD (/ CCE) limit.

Proposal 10
To prevent ambiguity at the UE, a reference PDCCH candidate is defined for various processes such as timing and PDSCH reception.

Proposal 11
For CSS other than Type-0 CSS and Type-3 CSS when it is configured with SearchSpaceZero:
Same technique as PDCCH repetition for Type0-CSS of searchSpaceZero provided by MIB is used.

SIB1 PDSCH link level enhancement 

Proposal 12
It is supported that type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed.

Proposal 13
SIB1 PDSCH repetition is indicated using reserved bits in PBCH payload   

Proposal 14
Support a new parameter, type0-pdcchCSSandSIB1repetition, encoded in 2 bits, to enable or disable type0-pdcchCSS and/or SIB1 PDSCH repetition either jointly or separately. This parameter is signalled using two reserved bits within the PBCH payload in FR1 NTN.

MSG4 PDSCH link level enhancement 

Proposal 15
Msg4 PDSCH repetition is triggered upon UE request via MGS3
Proposal 16
The Msg4 PDSCH repetition is activated using PDCCH- DCI Format 1_0
FFS: indication details.
 RP-243300	Revised WID: Non-Terrestrial Networks (NTN) for NR Phase 3 (Rev from RP-241789)
Lin Chen et al, The Next Generation of Beam Hopping SatelliteSystems: Dynamic Beam Illumination WithSelective Precoding, IEEE TRANSACTIONS ON WIRELESS COMMUNICATIONS, VOL. 22, NO. 4, APRIL 2023
3GPP TR 38.864, Study on network power savings for NR (Release 18), 2023-03
3GPP TS 38.300 V18.0.0 NR; NR and NG-RAN Overall Description; Stage 2, 2023-12
RWS-230048, Consideration on RAN1/2/3 led NTN topics for Release 19, Thales, Hughes, SES, Inmarsat, Ligado, Eutelsat, TTP, Lockheed, Novamint, Airbus, Lockheed Martin, ST Engineering, Sateliot, CeWIT, TNO, JSAT, Gatehouse, Omnispace, ESA, Intelsat, OneWeb, Fraunhofer IIS, Fraunhofer HHI, TNO, IRT Saint Exupery, Hispasat, Gilat, Terrestar, Magister solutions, OQ Technology, 3GPP TSG RAN TSG Rel-19 Workshop Meeting
R1-2208268_Summary #5 for 9.12.1 Coverage enhancement for NR NTN
3GPP TR 38.811 V15.2.0 Study on New Radio (NR) to support non-terrestrial networks (Release 15)
3GPP TR 38.821 Solutions for NR to support non-terrestrial networks (NTN) (Release 16)
3GPP TS 38.211 Physical channels and modulation (Release 17)
R1-2401845 FL Summary #3: NR-NTN downlink coverage enhancements, 2024-03
R1-2406439 Work plan for Rel-19 NR_NTN_Ph3, 2024-04
RAN1 Chair’s Notes, 3GPP TSG RAN WG1 #116, Athens, Greece, February 26th – March 1st, 2024
RAN1 Chair’s Notes, 3GPP TSG RAN WG1 #116-bis, Changsha, Hunan Province, China, April 15th – 19th, 2024
RAN1 Chair’s Notes, 3GPP TSG RAN WG1 #117, Fukuoka City, Fukuoka, Japan, May 20th – 24th, 2024
R1-2406777, MediaTek Inc, 3GPP TSG RAN WG1 #118, August, 2024
R1-2407049, Qualcomm Incorporated, 3GPP TSG RAN WG1 #118, August, 2024
RAN1 Chair’s Notes, 3GPP TSG RAN WG1 #118bis, Hefei, China, October 14th – 18th, 2024
RAN1 Chair’s Notes, 3GPP TSG RAN WG1 #120, Athens, Greece, February 17th – 21st, 2025
R1-2503702 RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis, May 2025

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

Agenda Item:	9.11.1
Source:	Moderator (Thales)
Title:	FL Summary #1: NR-NTN downlink coverage enhancements
Document for:	Discussion, Decision

Conclusion

TBC
List of companies’ proposals on NR-NTN downlink coverage enhancement

The compilation of companies' proposals and observations within the contributions under agenda item 9.11.1 could be found in R1-2504715.
RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis

The compilation of RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis could be found in R1-2503702.

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

Agenda Item:	9.11.1
Source:	Moderator (Thales)
Title:	FL Summary #2: NR-NTN downlink coverage enhancements
Document for:	Discussion, Decision

Conclusion 
There is no consensus in RAN1 to support PDCCH repetiton for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 for M=1/2 and M=1
A UE capable of PDCCH repetition for Type0 PDCCH CSS Of searchSpaceZero does not expect to be configured with other values of M than 2.


Proposal 4-3-1-v1
Revise the RAN1#120bis agreement as follows:
Agreement
For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1:
Enabling/disabling using a reserved bit(s) (i.e ) in PBCH payload
No UE behavior is defined for UE in connected mode specifically for the case where the network changes its signaling between enabling and disabling PDCCH repetition for Type0 PDCCH CSS.

Proposal 5-4-1
Msg4 PDSCH repetition technique is applied to PDSCH transmissions after Msg4 and before the completion of the RRC RRC reconfiguration. 

Proposal 1-3-1
The enabling and disabling of PDCCH repetition for Type0-PDCCH CSS of searchSpaceZero can also be configured in PDCCH-ConfigCommon in SIB1.
The setting of the PDCCH repetition provided by SIB1 is the same as the setting of the PDCCH repetition provided by PBCH.

Proposal 2-3-1-v1
For PDCCH repetition for CSS other than Type-0 CSS and other than Type-3 CSS when it is configured with searchSpaceZero, if PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 is enabled, one of the following options should be selected (by the end of current meeting):
Alt 1: For the CSS other than Type-0 CSS, searchspace zero should not be used
Alt 2: Support inter-slot repetition which is the same as PDCCH repetition for Type0-CSS
[FFS: whether/how to handle the k0 when if inter-slot repetition is used for type-0A/1/2]
Alt3: PDCCH repetition is not applied to the DCI format with CRC scrambled by a RNTI other than SI-RNTI 

Proposal 3-1-2
For Type-0 CSS PDCCH repetition, the following rule for BD counting is defined:
Early slot: BD counted as 1.
Later slot: BD counted as 1 or 2, depending on UE behavior:
Option A: 2 BDs for combined PDCCH candidate for SI-RNTI and PDCCH candidate for UE-specific RNTI.
Option B: 1 BD for combined PDCCH candidate for SI-RNTI only.
Proposal 3-1-1
For intra-slot PDCCH repetition of PDCCH CSS other than Type-0 CSS and other than Type-3 CSS, if searchSpaceZero is not used for these CSS, BD is doubled if UE indicates three-BDforSSsetLinking, otherwise is counted as one (i.e. adopt the same BD rule defined in Release 17 for mTRP).

Proposed working assumption
For NTN with extended SSB periodicity, a subset of RACH occasions can be configured to support valid ROs for PRACH transmission.
FFS: detailed configuration solution (to be determined at RAN1#121), [e.g. reusing a solution from Rel-19 NES or some other simple configuration.]


List of companies’ proposals on NR-NTN downlink coverage enhancement
The compilation of companies' proposals and observations within the contributions under agenda item 9.11.1 could be found in R1-2504715.
RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis
The compilation of RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis could be found in R1-2503702.

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

Agenda Item:	9.11.1
Source:	Moderator (Thales)
Title:	FL Summary #3: NR-NTN downlink coverage enhancements
Document for:	Discussion, Decision

Conclusion 
There is no consensus in RAN1 to support PDCCH repetiton for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 for M=1/2 and M=1
A UE capable of PDCCH repetition for Type0 PDCCH CSS Of searchSpaceZero does not expect to be configured with other values of M than 2.


Proposal 4-3-1-v1
Revise the RAN1#120bis agreement as follows:
Agreement
For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1:
Enabling/disabling using a reserved bit(s) (i.e ) in PBCH payload
No UE behavior is defined for UE in connected mode specifically for the case where the network changes its signaling between enabling and disabling PDCCH repetition for Type0 PDCCH CSS.

Proposal 5-4-1
Msg4 PDSCH repetition technique is applied to PDSCH transmissions after Msg4 and before the completion of the RRC RRC reconfiguration. 

Proposal 1-3-1
The enabling and disabling of PDCCH repetition for Type0-PDCCH CSS of searchSpaceZero can also be configured in PDCCH-ConfigCommon in SIB1.
The setting of the PDCCH repetition provided by SIB1 is the same as the setting of the PDCCH repetition provided by PBCH.

Proposal 2-3-1-v1
For PDCCH repetition for CSS other than Type-0 CSS and other than Type-3 CSS when it is configured with searchSpaceZero, if PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 is enabled, one of the following options should be selected (by the end of current meeting):
Alt 1: For the CSS other than Type-0 CSS, searchspace zero should not be used
Alt 2: Support inter-slot repetition which is the same as PDCCH repetition for Type0-CSS
[FFS: whether/how to handle the k0 when if inter-slot repetition is used for type-0A/1/2]
Alt3: PDCCH repetition is not applied to the DCI format with CRC scrambled by a RNTI other than SI-RNTI 

Proposal 3-1-2
For Type-0 CSS PDCCH repetition, the following rule for BD counting is defined:
Early slot: BD counted as 1.
Later slot: BD counted as 1 or 2, depending on UE behavior:
Option A: 2 BDs for combined PDCCH candidate for SI-RNTI and PDCCH candidate for UE-specific RNTI.
Option B: 1 BD for combined PDCCH candidate for SI-RNTI only.
Proposal 3-1-1
For intra-slot PDCCH repetition of PDCCH CSS other than Type-0 CSS and other than Type-3 CSS, if searchSpaceZero is not used for these CSS, BD is doubled if UE indicates three-BDforSSsetLinking, otherwise is counted as one (i.e. adopt the same BD rule defined in Release 17 for mTRP).

Proposed working assumption
For NTN with extended SSB periodicity, a subset of RACH occasions can be configured to support valid ROs for PRACH transmission.
FFS: detailed configuration solution (to be determined at RAN1#121), [e.g. reusing a solution from Rel-19 NES or some other simple configuration.]

Proposals for Thursday offline session

Proposal 2-1-1-v2
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support intra-slot repetition based on:
BD is counted as one or two, subject to UE capability
When BD is counted as one, i.e. UE assumes that single DCI content is mapped on two PDCCH candidates. 
Note: From RAN1 perspective UE is expected to deliver performance no worse than soft combining
PDCCH repetition is applicable to configured RNTI of the CSS.
Repeated PDCCH candidates have the same frequency resources within the same CORESET repeated in the slot, and share the same aggregation level (AL), coded bits and same candidate index.
Up to editor how to capture this in writing the relevant RAN1 specification.


Proposal 5-4-1-v2
If Msg4 PDSCH repetition discussed in R19 NR NTN coverage enhancement is supported for PDSCH transmission scheduled by DCI format 1_0  [in Type 1 CSS,] when dedicated PDSCH resource configuration is not provided:
·        The agreements for PDSCH with Msg4 are applied to any C-RNTI based PDSCH transmission based on PDSCH-ConfigCommon
·        The same repetition factor is applied for PDSCH with Msg4 and subsequent C-RNTI based PDSCH transmissions based on PDSCH-ConfigCommon
·        Note: It is not precluded for gNB to provide dedicated PDSCH config via Msg4 PDSCH.


Proposal 3-1-2
Working assumption
For inter-slot Type-0 CSS PDCCH repetition, the following rule for BD counting is defined:
1 BD in first slot.
In the second slot: 2 BD
PDCCH repetition is only applicable to the SI-RNTI.



Proposed working assumption
For NTN with extended SSB periodicity an offset is provided in SIB1 and the  in PRACH configuration table is updated to +offset
Offset is configured in range of {0, 2,4,6,8,10,12,14}, when x=16 
Offset is configured in range of {0, 2,4,6}, when x=8
Offset is configured in range of {0, 2}, when x=4

For other x values, offset is 0
Option 2
OFFSET and time window duration configured in SIB1
Offset value 20 40 60 80 100 120 140 ms
Duration value 10 20 ms
Time window periodicity is equal to SSB periodicity indicated in SIB1
UE can select the RO within the time window and UE only transmits PraCH in RO within the time window
Time window starting location start from SFN0+offset


Proposal 5-1-2
Adopt the following TP for the LS on Msg4 PDSCH repetition:



Companies are encouraged to share views on the above proposals:
Proposals for Friday online session

Proposal 2-1-1-v2
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support intra-slot repetition based on:
BD is counted as one or two, subject to UE capability
When BD is counted as one, i.e. UE assumes that single DCI content is mapped on two PDCCH candidates. 
Note: From RAN1 perspective UE is expected to deliver performance no worse than soft combining
PDCCH repetition is applicable to configured RNTI of the CSS.
Repeated PDCCH candidates have the same frequency resources within the same CORESET repeated in the slot, and share the same aggregation level (AL), coded bits and same candidate index.
Up to editor how to capture this in writing the relevant RAN1 specification.

Proposal 3-1-2
Working assumption
For inter-slot Type-0 CSS PDCCH repetition, the following rule for BD counting is defined:
1 BD in first slot.
In the second slot: 2 BD
PDCCH repetition is only applicable to the SI-RNTI.

Proposal 6-2-1a
For NTN with extended SSB periodicity an active time configuration for valid ROs is configured in SIB1 with an OFFSET, a time window duration and periodicity:
Offset value 20, 40, 60, 80, 100, 120, 140 ms
Time window duration value 10, 20 ms
Periodicity is equal to SSB periodicity indicated in SIB1
Time window starting location start from SFN0+offset.
UE can select the RO within the time window and it only transmits PRACH in RO within the time window.

Proposal 6-2-1b
For NTN with extended SSB periodicity an offset is provided in SIB1 and the  in PRACH configuration table is updated to +offset
Offset is configured in range of {0, 2,4,6,8,10,12,14}, when x=16 
Offset is configured in range of {0, 2,4,6}, when x=8
Offset is configured in range of {0, 2}, when x=4
For other x values, offset is 0

Proposal 5-4-1-v2
If Msg4 PDSCH repetition discussed in R19 NR NTN coverage enhancement is supported for PDSCH transmission scheduled by DCI format 1_0  [in Type 1 CSS,] when dedicated PDSCH resource configuration is not provided:
·        The agreements for PDSCH with Msg4 are applied to any C-RNTI based PDSCH transmission based on PDSCH-ConfigCommon
·        The same repetition factor is applied for PDSCH with Msg4 and subsequent C-RNTI based PDSCH transmissions based on PDSCH-ConfigCommon
·        Note: It is not precluded for gNB to provide dedicated PDSCH config via Msg4 PDSCH.

List of companies’ proposals on NR-NTN downlink coverage enhancement
The compilation of companies' proposals and observations within the contributions under agenda item 9.11.1 could be found in R1-2504715.
RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis
The compilation of RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis could be found in R1-2503702.

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

Agenda Item:	9.11.1
Source:	Moderator (Thales)
Title:	FL Summary #3: NR-NTN downlink coverage enhancements
Document for:	Discussion, Decision

Conclusion 
There is no consensus in RAN1 to support PDCCH repetiton for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 for M=1/2 and M=1
A UE capable of PDCCH repetition for Type0 PDCCH CSS Of searchSpaceZero does not expect to be configured with other values of M than 2.


Proposal 4-3-1-v1
Revise the RAN1#120bis agreement as follows:
Agreement
For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1:
Enabling/disabling using a reserved bit(s) (i.e ) in PBCH payload
No UE behavior is defined for UE in connected mode specifically for the case where the network changes its signaling between enabling and disabling PDCCH repetition for Type0 PDCCH CSS.

Proposal 5-4-1
Msg4 PDSCH repetition technique is applied to PDSCH transmissions after Msg4 and before the completion of the RRC RRC reconfiguration. 

Proposal 1-3-1
The enabling and disabling of PDCCH repetition for Type0-PDCCH CSS of searchSpaceZero can also be configured in PDCCH-ConfigCommon in SIB1.
The setting of the PDCCH repetition provided by SIB1 is the same as the setting of the PDCCH repetition provided by PBCH.

Proposal 2-3-1-v1
For PDCCH repetition for CSS other than Type-0 CSS and other than Type-3 CSS when it is configured with searchSpaceZero, if PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 is enabled, one of the following options should be selected (by the end of current meeting):
Alt 1: For the CSS other than Type-0 CSS, searchspace zero should not be used
Alt 2: Support inter-slot repetition which is the same as PDCCH repetition for Type0-CSS
[FFS: whether/how to handle the k0 when if inter-slot repetition is used for type-0A/1/2]
Alt3: PDCCH repetition is not applied to the DCI format with CRC scrambled by a RNTI other than SI-RNTI 

Proposal 3-1-2
For Type-0 CSS PDCCH repetition, the following rule for BD counting is defined:
Early slot: BD counted as 1.
Later slot: BD counted as 1 or 2, depending on UE behavior:
Option A: 2 BDs for combined PDCCH candidate for SI-RNTI and PDCCH candidate for UE-specific RNTI.
Option B: 1 BD for combined PDCCH candidate for SI-RNTI only.
Proposal 3-1-1
For intra-slot PDCCH repetition of PDCCH CSS other than Type-0 CSS and other than Type-3 CSS, if searchSpaceZero is not used for these CSS, BD is doubled if UE indicates three-BDforSSsetLinking, otherwise is counted as one (i.e. adopt the same BD rule defined in Release 17 for mTRP).

Proposed working assumption
For NTN with extended SSB periodicity, a subset of RACH occasions can be configured to support valid ROs for PRACH transmission.
FFS: detailed configuration solution (to be determined at RAN1#121), [e.g. reusing a solution from Rel-19 NES or some other simple configuration.]

Proposals for Thursday offline session

Proposal 2-1-1-v2
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support intra-slot repetition based on:
BD is counted as one or two, subject to UE capability
When BD is counted as one, i.e. UE assumes that single DCI content is mapped on two PDCCH candidates. 
Note: From RAN1 perspective UE is expected to deliver performance no worse than soft combining
PDCCH repetition is applicable to configured RNTI of the CSS.
Repeated PDCCH candidates have the same frequency resources within the same CORESET repeated in the slot, and share the same aggregation level (AL), coded bits and same candidate index.
Up to editor how to capture this in writing the relevant RAN1 specification.


Proposal 5-4-1-v2
If Msg4 PDSCH repetition discussed in R19 NR NTN coverage enhancement is supported for PDSCH transmission scheduled by DCI format 1_0  [in Type 1 CSS,] when dedicated PDSCH resource configuration is not provided:
·        The agreements for PDSCH with Msg4 are applied to any C-RNTI based PDSCH transmission based on PDSCH-ConfigCommon
·        The same repetition factor is applied for PDSCH with Msg4 and subsequent C-RNTI based PDSCH transmissions based on PDSCH-ConfigCommon
·        Note: It is not precluded for gNB to provide dedicated PDSCH config via Msg4 PDSCH.


Proposal 3-1-2
Working assumption
For inter-slot Type-0 CSS PDCCH repetition, the following rule for BD counting is defined:
1 BD in first slot.
In the second slot: 2 BD
PDCCH repetition is only applicable to the SI-RNTI.



Proposed working assumption
For NTN with extended SSB periodicity an offset is provided in SIB1 and the  in PRACH configuration table is updated to +offset
Offset is configured in range of {0, 2,4,6,8,10,12,14}, when x=16 
Offset is configured in range of {0, 2,4,6}, when x=8
Offset is configured in range of {0, 2}, when x=4

For other x values, offset is 0
Option 2
OFFSET and time window duration configured in SIB1
Offset value 20 40 60 80 100 120 140 ms
Duration value 10 20 ms
Time window periodicity is equal to SSB periodicity indicated in SIB1
UE can select the RO within the time window and UE only transmits PraCH in RO within the time window
Time window starting location start from SFN0+offset


Proposal 5-1-2
Adopt the following TP for the LS on Msg4 PDSCH repetition:



Companies are encouraged to share views on the above proposals:
Proposals for Friday online session

Proposal 2-1-1-v2a
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support intra-slot repetition based on:
BD is counted as one or two, subject to UE capability
When BD is counted as one, i.e. UE assumes that single DCI content is mapped on two PDCCH candidates. 
Note: From RAN1 perspective UE is expected to deliver performance no worse than soft combining
PDCCH repetition is applicable to configured RNTI of the CSS.
Repeated PDCCH candidates have the same frequency resources within the same CORESET repeated in the slot, and share the same aggregation level (AL), coded bits and same candidate index.
Up to editor how to capture this in writing the relevant RAN1 specification.

Proposal 2-1-1-v2b
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support intra-slot repetition based on:
The starting symbol of monitoring occasion of the second SS is located right after the ending symbol of monitoring occasion of the first SS.
No additional RRC config
BD is counted as one or two, subject to UE capability
When BD is counted as one, i.e. UE assumes that single DCI content is mapped on two PDCCH candidates. 
Note: From RAN1 perspective UE is expected to deliver performance no worse than soft combining


Proposal 3-1-2
Working assumption
For inter-slot Type-0 CSS PDCCH repetition, the following rule for BD counting is defined:
1 BD in first slot.
In the second slot: 2 BD
PDCCH repetition is only applicable to the SI-RNTI.

Proposal 6-2-1a
For NTN with extended SSB periodicity an active time configuration for valid ROs is configured in SIB1 with an OFFSET, a time window duration and periodicity:
Offset value 20, 40, 60, 80, 100, 120, 140 ms
Time window duration value 10, 20 ms
Periodicity is equal to SSB periodicity indicated in SIB1
Time window starting location start from SFN0+offset.
UE can select the RO within the time window and it only transmits PRACH in RO within the time window.

Proposal 6-2-1b
For NTN with extended SSB periodicity an offset is provided in SIB1 and the  in PRACH configuration table is updated to +offset
Offset is configured in range of {0, 2,4,6,8,10,12,14}, when x=16 
Offset is configured in range of {0, 2,4,6}, when x=8
Offset is configured in range of {0, 2}, when x=4
For other x values, offset is 0

Proposal 6-2-1bc
For NTN with extended SSB periodicity, a subset of RACH occasions can be configured to support valid ROs for PRACH transmission. 
One RRC parameter in SIB1 is used to indicate the valid subset, where this RRC parameter denotes one bit- mapping rule for each 160ms-duration based on PRACH configuration table with 8 bits. Each bit is corresponding to one 20ms window, where ‘0’ means the ROs within this window is not valid, and “1” means the ROs within this window is activated. 
（for example, [1 0 0 0 0 0 0 0] means the first 20ms window is activated）

Proposal 5-4-1-v2
If Msg4 PDSCH repetition discussed in R19 NR NTN coverage enhancement is supported for PDSCH transmission scheduled by DCI format 1_0  [in Type 1 CSS,] when dedicated PDSCH resource configuration is not provided:
·        The agreements for PDSCH with Msg4 are applied to any C-RNTI based PDSCH transmission based on PDSCH-ConfigCommon
·        The same repetition factor is applied for PDSCH with Msg4 and subsequent C-RNTI based PDSCH transmissions based on PDSCH-ConfigCommon
·        Note: It is not precluded for gNB to provide dedicated PDSCH config via Msg4 PDSCH.

List of companies’ proposals on NR-NTN downlink coverage enhancement
The compilation of companies' proposals and observations within the contributions under agenda item 9.11.1 could be found in R1-2504715.
RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis
The compilation of RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis could be found in R1-2503702.

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

Agenda Item:	9.11.1
Source:	CATT 
Title:	Discussion on downlink coverage enhancement for NR NTN
Document for:	Discussion and Decision

Conclusion
In this contribution we analyse the reference satellite configuration. The downlink enhancement requirements are analyzed from the link level and system level. We have the following proposals and observations:
For SSB extention enhancement:
Regarding the beam hopping with 160ms SSB periodicity, it should allow gNB implementation based on SFN timing alignment among multiple cells served by one active beam.
The time-segmented bitmap indication method for RO mapping can be supported to adapt to beam hopping mechanism while adhering to the original PRACH resource allocation method as much as possible and without disrupting the mapping rules between SSB and RO.

For beam hopping case, RO mapping should be TDM based per cell to allow one beam to serve more beam footprints if 160ms SSB periodicity is used.  
Based on current RO mapping rule in specification, RO colliding will be much worse when one active beam serves multiple cells and configure same SFN timing for all cells. 
Maintaining different SFN separately for different cells will lead to high complexity in resource scheduling and beam management, which cause beam hopping unrealizable.

For link level enhancement:
PDCCH repetition in Rel-19 can be applied in TN and NTN both from the specification perspective.  
The configuration of M=1/2 has a low priority for coverage enhancement requirement.
For scenarios where M=1, a predefined additional time domain offset X can be used to indicate the repetition.
Taking into account minimizing specification modifications, linking two different CSSs would be an easier solution for enhancement of other PDCCH CSS types except Type0 and Type3 other than SearchSpaceZero. 
The enabling/disabling of SIB1 PDSCH repetition should be binded to Type-0 CSS PDCCH (Option3) with the advantage of lower signaling overhead.
UE can report the Msg4 repetition capability via 1bit in Msg3.
Using 1 MSB in MCS field in DCI scheduling Msg4 to indicate enabling/disabling of UE specific Msg4 PDSCH is a prefer option which works similar to Msg3 enhancements.

For scenarios where M=1/2, time domain resources are extremely limited for two PDCCHs of the Coreset0 and one PDSCH carrying SIB1 in one slot.
Whether UE reports the enhanced capabilities of PDSCH with Msg4 should be confirmed first, which will affect the signaling to indicate the UE.

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


Agenda Item:	9.11.1	
Source:	InterDigital, Inc.
Title:	NR-NTN downlink coverage enhancement
Document for:	Discussion

Conclusions
In this contribution, the following observations are made:
Observation 1: NES Cell DTx and cell DRx mechanisms may provide a baseline for NTN scenarios to enable beam hopping among satellite beams. 
Observation 2: The configuration and signaling mechanisms for NES cell DTx/DRx are not applicable in NTN scenarios. 
Observation 3: A single DTx/DRx pattern may not be suitable for NTN due to wide coverage of satellite beams supporting UEs in different RRC states and with different activity levels. 
Observation 4: Msg4 PDSCH repetition tied to SIB1 repetitions may result in un-necessary Msg4 repetitions.

The observations and the discussion have led to the following proposals:
Proposal 1: Support NTN DTx/DRx mechanisms which determine the transmission/reception of common and UE specific channels/signals.
Proposal 2: Support common signaling for configuration/activation of NTN DTx/DRx mechanisms.
Proposal 3: Support network indication to connected mode UEs an additional active duration for DTx/DRx through the following mechanisms:
Simultaneous activation of multiple DTx/DRx patterns.
Additional active time for the active DTx/DRx pattern. 

Proposal 4: RAN1 investigates the impact of increased SSB periodicity on the following:
System information transmission/acquisition
Paging
Random access

Proposal 5: For PDCCH CSS other than Type-0 CSS and other than Type-3, support intra-slot PDCCH CSS repetitions using Option 1, i.e., use same CORESET and two different SS (SS Set1 and SS Set2).
Proposal 6: For Msg4 PDSCH repetition, support Option 1, i.e., UE specific PDSCH with Msg4 repetition activation indicated via PDCCH- DCI Format 1_0.

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

Source: 	CMCC
Title:	Discussion on NR-NTN DL coverage enhancement
Agenda item:	9.11.1
Document for:	Discussion & Decision

Conclusions
In this contribution, we share our views on DL coverage enhancement for both system-level study and link-level study in NTN scenarios. The observations and proposals are summarized as follows.
Observation 1: For LEO-600 Set1-1/1-2/1-3, longer revisit period can be considered to improve the coverage ratio.
Observation 2: Within the dwelling window, the SSB and necessary system information (e.g., SIB1, SIB19) can be broadcasted for the target beam footprints, which can be utilized by UEs to access to the satellite/gNB within the dwelling window. For the residual slots of the dwelling window, it can be used for the dynamic scheduling for the same beam footprints as SSB or other beam footprints.
Observation 3: To provide services to all UEs covered by the satellite footprint, TDM beam scheduling/beam hopping can be performed to illuminate different beam footprint for SSB and necessary system information (e.g., SIB1, SIB19) transmission. 
Observation 4: The time span of the dynamic scheduled dwelling window for a given beam footprint can be allocated based on UE distribution and traffic distribution. 
Observation 5: If SFN offset for different NTN cells can be supported, current PRACH configuration and mapping relationship between SSB and RO can be used to adapt to the extended SSB periodicity and beam hopping pattern.
Proposal 1: Considering the extended SSB periodicity of 160ms, the periodicity of Type0-PDCCH CSS monitoring and UE measurement needs to be extended correspondingly.
Proposal 2: Take the following TP for TS 38.213 section 13.
Reason for change: For NR NTN, extended SSB periodicity of 160ms is supported, and periodicity of Type0-PDCCH CSS should also be extended to 160ms in this case.
Summary of change: Add the clarification on extending the periodicity of Type0-PDCCH CSS in TS 38.213 section 13. 
Consequence if not approved: Extending the periodicity of Type0-PDCCH CSS related to SSB periodicity is not included in TS 38.213.
Proposal 3: Support the system level enhancements to improve the coverage ratio in NR-NTN phase 3, with the consideration of introducing the revisit periodicity and dwelling window for other channels/signals to adapt to SSB periodicity extension.
Proposal 4: Potential enhancements to associate valid ROs among the entire set of configured ROs with an SSB index corresponding to a beam footprint should be considered.
Proposal 5: To improve the association of valid ROs among the entire set of configured ROs with an SSB index corresponding to a beam footprint, the following enhancements can be considered:
Option 1 (Validity Window Based): A validity window associated with a specific SSB index is introduced. ROs configured within this validity window are deemed valid.
Option 2 (Mapping Function Based): A mapping function between the SFN of a specific SSB index and the configured RO index(es) is introduced. The calculated ROs are valid for the corresponding SSB index. 
Alternatively, a mapping bitmap can also be considered.
Proposal 6: For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, support repeated PDCCH candidates in the two slots  and , and the slot offset () between PDCCH monitoring window can be predefined separately for different M values.
For M=1/2,  for M=1,  for M=2, .
Proposal 7: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported by using the same CORESET associated with one SS which is repeated by introducing symbol domain offset.
The enabling/disabling of PDCCH repetition and symbol offset between repeated PDCCHs can be indicated via system information.
Proposal 8: It can be supported that type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed, and the repeated PDSCHs can be transmitted in two consecutive slots.
Proposal 9: Considering DL coverage enhancements for PDSCH carrying SIB1/SIB19 in NTN scenarios, enable/disable PDSCH repetition by 1 reserved bit in DCI format 1_0 with CRC scrambled by SI-RNTI.
Proposal 10: For PDSCH with Msg4 link-level enhancement, enabling/disabling Msg4 PDSCH repetition by DCI format 1_0 with CRC scrambled by TC-RNTI can be supported.
1 MSB of MCS field in the DCI format 1_0 can be re-interpreted to indicate PDSCH with Msg4 repetition activation.

3GPP TSG RAN WG1 #121			                                                         R1-2503861
St Julian’s, Malta, May 19th – 23rd, 2025
	
Agenda item:	9.11.1 - NR-NTN downlink coverage enhancement
Source: 	Fraunhofer IIS, Fraunhofer HHI
Title: 	Discussion on downlink coverage enhancement for NR NTN
Document for:	Discussion 

Conclusion

Observation 1: The allocation of paging occasions and paging frames should be consistent with the beam hopping pattern, as no paging occasions are expected when the beam is off.
Proposal 1: RAN1 to study the impact of beam hopping and SSB periodicity extension on paging procedure.
Proposal 2: RAN1 to study the impact of beam hopping and SSB periodicity extension on random access.
Observation 2: Common downlink control signaling such as SIB1/SIB19 and uplink control signaling such as PRACH could be used to implement beam-hopping without modifications on the current rel-18 cell DTX/DRX.
Proposal 3: Techniques other than cell DTX/DRX should be considered to implement beam hopping.
Observation 3: In case beam hopping is applied, the beam might not be available to keep the periodicity of CORSET0 and the corresponding SIB1 for FR1 and multiplexing pattern1, which is 20ms.

Proposal 4: RAN1 to extend the periodicity of CORSET0 used to schedule SIB1 and the periodicity of the corresponding SIB1 to at least 160ms for FR1 and multiplexing pattern 1 in case beam hopping is to be applied.

Proposal 5: For the repetition of type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, RAN1 to support repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index only for M = 2.

Proposal 6: RAN1 to consider using 1 bit in PBCH to jointly indicate the repetition of both type0 PDCCH and the associated SIB1 or 2 bits within PBCH to indicate the repetition of SIB1 and type0 PDCCH separately. 

Proposal 7: For indication of repetition factor of PDSCH msg4, RAN1 to consider option 1, where PDCCH DCI1_0 scrambled with TC-RNTI is used to indicate the repetition factor. FFS: whether there are available bits to indicate the repetition factor.

Proposal 8: RAN 1 to consider UE capability indication for reception of PDSCH msg4 with repetition via msg3 based on RSRP measurements on RAR. 

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

Source: 	Xiaomi
Title:	Discussion on NR-NTN downlink coverage enhancement
Agenda item: 	9.11.1
Document for:	Decision

Conclusions
In this contribution, we present views on NR-NTN DL coverage enhancement, we have the following observations and proposals:
Proposal 1: If RACH enhancement is pursued in Rel-19, the beam hopping pattern specific RO selection can be discussed and optimized.
Proposal 2: Enhancements on cell DRX/DTX can be considered to support beam hopping in NTN.
During its non-active period UE does not except to receive/transmit any signal from/to the corresponding cell within the corresponding footprint;
A group common DCI can be used to dynamically indicate the beam hopping pattern.
Proposal 3: For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, the AL levels for PDCCH should be larger than a fixed thershold.
Proposal 4: Confirm the working assumption as below with option 2 selected. For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported.
Use same CORESET and two different SS (SS Set1 and SS Set2), and the blind decoding limit is 1.
Proposal 5: For enabling PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, option 1 and option 2 with kssb is supported. It’s not precluded combining both options if the repetition number exceeds 4.	
Proposal 6: Support UE request and capability indication for msg 4 repetition in msg 3. An RSRP threshold can be configured to UE to trigger such request. 
Proposal 7: For enabling/disabling Msg4 PDSCH repetition, UE specific PDSCH with Msg4 repetition activation indicated via PDCCH- DCI Format 1_0 with the following candidate indication approach
 Dedicated RNTI
 Reinterpretation of existing fields such as MCS or TDRA field

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

Agenda Item:	9.11.1
Source:	NEC
Title:	NR-NTN downlink coverage enhancement
Document for:	Discussion 

Conclusion
From the discussion, we have the following proposal.

Proposal 1: Support using the scheduling PDCCH to enable/disable SIB1 PDSCH repetition (Option 2).
Proposal 2: Support using PDCCH DCI Format 1_0 to enable/disable Msg3 PDSCH repetition (Option 1).

 

3GPP TSG RAN WG1 Meeting #121	R1-2504001
St Julian’s, Malta, May 19th – 23rd, 2025
Source:	Fujitsu
Title:	Discussion on downlink coverage enhancements
Agenda Item:	9.11.1
Document for:	Discussion

Conclusion
In this contribution, we provided our views as below.
Observation 1: For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, the potential solution for the M=1 and M=1/2 cases other than cross-SSB beam and time-separated type-0 PDCCH repetition can be further discussed.

Observation 2: For SIB1 PDSCH repetition, whether the out-of-order processing for PDSCH can be implemented or may not need to be clarified.


Proposal 1: For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, the UE only decode combined PDCCH in the slot n0+1 and the number of BD to decode combined PDCCH is counted within the BD limits in the slot n0+1.

Proposal 2: For PDCCH repetition (except type-0 and type-3), confirm the working assumption.

Proposal 3: For Rel-19 PDCCH repetition (except type-0 and type-3), support Option 2 to configure non-overlapped repeated CORESET and to define BD behaviour towards BD limits.

Proposal 4: For SIB1 PDSCH repetition, the following case should be supported: type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed.

Proposal 5: For enabling/disabling SIB1 PDSCH repetition, Option 2 should be supported if repetition factor of 4 is needed for SIB1 PDSCH repetition. Otherwise, Option 1 should be supported to align with that for type-0 PDCCH repetition.

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

Agenda Item: 	9.11.1
Source: 	Baicells
Title:	Discussion on downlink coverage enhancement for NR NTN
Document for:	Discussion and Decision



1. 

Conclusions

Observation 1:  There are 2 reserved bits in the additional timing related PBCH payload when =4. One of the two bits can be used to indicate the PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero.

Proposal 1:  For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1，enabling/disabling using one of the two bits (, ) in the additional timing related PBCH payload.

Observation 2: When repeated PDCCHs and SIB1s are transmitted in two consecutive slots associated with the same SSB index, the value of M (which determines the interval between PDCCH monitoring occasions) has a direct impact on the number of simultaneously active beams required to maintain coverage over multiple SSB beam footprints. Specifically, reducing M from 2 to 1 or 1/2 increases the number of required active beams from 1 to 2 or even 4, respectively, leading to higher beam resource consumption and a significant reduction in coverage ratio.

Proposal 2:  To avoid excessive beam resource usage and maintain an acceptable coverage ratio in NTN scenarios, it is recommended to use M=2 as the default configuration for Type0-PDCCH common search space when repeated PDCCH and SIB1 transmissions are scheduled across two consecutive slots associated with the same SSB index. Smaller M values (e.g., M=1 and M=1/2) should be avoided unless absolutely necessary for meeting latency requirements, due to their negative impact on coverage performance.

Observation 3: For the corner case that type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed, it can be determined by the network implementation without spec impact.

Proposal 3:  Do not support the case that type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed.

Observation 4:  For enabling/disabling SIB1 PDSCH repetition,  Option 1 is same as Option 3, or it may require an extra reserved bit than Option 3; Option 2 may require require additional specification work related to DCI; Option 3 is most effective.

Proposal 4: For enabling/disabling SIB1 PDSCH repetition, support Option 3: The enabling/disabling of SIB1 PDSCH repetition is implicitly indicating by the enabling/disabling of Type-0 CSS PDCCH repetition.


Observation 5:  The repetition factor (2 or 4) must initially be configured via SIB1. Enabling or disabling the repetition can then be indicated either dynamically or semi-statically. The advantage of using DCI for indication is its dynamic capability. However, a disadvantage is that it introduces additional complexity in the DCI design. For semi-static indication, SIB1 configuration can be used.

Proposal 5: For Msg4 PDSCH repetition, the repetition factor (2 or 4) configuration in SIB1 can also be an enabling indication.



4. 

3GPP TSG RAN WG1 #121			                                     R1-2504103
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	9.11.1
Source:	HONOR
Title:	Discussion on NR-NTN downlink coverage enhancement
Document for:	Discussion and Decision

Conclusions
In this contribution, we provide our views on NR-NTN downlink coverage enhancements with the following observations and proposals.
Observation 1: PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero in the two consecutive slots for M=1 and M=1/2 can be supported by network implementation.
Proposal 1: Use the bit  in PBCH payload to enable/disable PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero.
Proposal 2: For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero, the additional standardization solution for M=1 and M=1/2 is not considered in R19.
Proposal 3: Confirm the working assumption of RAN1#120bis with revisions as follows:
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported. RAN1 will specify support for the updated option 2:
Updated option 2: Use same CORESET associated with one SS which is repeated by introducing symbol domain offset X 
The maximum number of blind decoding at a given time shouldn’t be increased compared to Rel-18.
The offset X for each CCS type is configured by PDCCH-ConfigCommon IE in SIB.
Proposal 4: RAN1 will specify support using scheduling PDCCH for enabling/disabling SIB1 PDSCH repetition.
Proposal 5: Support type-0 PDCCH repetition not performed while PDSCH-SIB1 repetition performed.
Proposal 6: When type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed, the offset from the slot occupied by the PDCCH scheduling SIB1 to the repetition of PDSCH with SIB1 is indicated by the reserved bits in the DCI format 1_0 with CRC scrambled by SI-RNTI. 
Proposal 7: Support option 3 that enabling/disabling Msg4 repetition is indicated by SIB1 configuration.
Proposal 8: Use Msg1 to send the request for Msg 4 PDSCH repetition by the UE.  
Proposal 9: The information of UE capability and request for DL coverage enhancement can be shared by different DL channels, i.e. CSS PDCCH, PDSCH with SIB and PDSCH with Msg4.

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

Source:	Panasonic
Title: 	NR-NTN Downlink Coverage Enhancement
Agenda Item:		9.11.1 
Document for:	Discussion and decision

Conclusion
We propose the following:

Proposal 1: Confirm the working assumption and support intra-slot repetition for PDCCH CSS other than Type-0 CSS and other than Type-3 CSS. Use same CORESET and two different SS (SS Set1 and SS Set2) and link the two PDCCH candidates, i.e., adopt the same mechanism for SS linking specified in Rel.17.

Proposal 2: No new solutions for M=1 and M=1/2 are introduced for PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 based on repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index ( as defined in section 13 of TS 38.213) 

Proposal 3: When PDCCH CSS type-0 repetition is performed, for SIB1 link level enhancement, support PDSCH repetition of SIB1 transmitted within the same slot as the type0-CSS PDCCH repetition.
UE supporting SIB1 PDSCH coverage enhancement assumes that the PDCCH and associated PDSCH to be repeated in both slots where the corresponding PDCCHs are transmitted.
Each PDSCH SIB1 repetition is within the same slot of each PDCCH candidate for scheduling DCI
The two associated PDSCHs have the same RV

Proposal 4: The enabling/disabling of SIB1 PDSCH repetition is implicitly indicated by the enabling/disabling of Type-0 CSS PDCCH repetition.

Proposal 5: For enabling/disabling Msg4 PDSCH repetition, UE specific PDSCH with Msg4 repetition activation is indicated via PDCCH-DCI Format 1_0
DCI indicates enabling/disabling of Msg4 PDSCH repetitions via DAI field
Configure enabling/disabling of Msg4 PDSCH repetitions together with the number of Msg4 PUCCH repetitions for each codepoint of DAI field.

Proposal 6: For NTN with extended SSB periodicity, Type-0 PDCCH CSS set periodicity is equal to the periodicity of SSB for CORESET multiplexing pattern 1.

Proposal 7: RAN1 adopts the existing PRACH framework as baseline, if needed as a working assumption
FFS: The need for modifying PRACH configuration for extended SSB periodicity

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

Agenda item:	9.11.1 
Source: 	ETRI
Title: 	Discussion on NR-NTN downlink coverage enhancement 
Document for:	Discussion/Decision

Conclusions
Observation 1: Implicitly indicating the enabling/disabling of Msg4 PDSCH repetition by the enabling/disabling of SIB1 PDSCH repetition can lead to unnecessary repetitions.
Observation 2: By reusing the signaling mechanism from Rel-18 NR NTN for PUCCH repetitions for Msg4 HARQ-ACK, both Option 1 and Option 3 for enabling/disabling Msg4 PDSCH repetition can be applied simultaneously without conflict.
Observation 3: Supporting PDSCH-SIB1 repetition when type-0 PDCCH repetition is not performed can avoid unnecessary repetition of type-0 PDCCH CSS, particularly when considering SIB1 with a payload size of 1280 bits.
Observation 4:  When PDSCH-SIB1 repetition without type-0 PDCCH repetition is not supported, the Option 1 and Option 3 become equivalent.
Proposal 1: RAN1 to support Option 1 and/or Option3 for enabling/disabling Msg4 PDSCH repetition.
Proposal 2: RAN1 to reuse the signaling mechanism from Rel-18 NR NTN for PUCCH repetitions for Msg4 HARQ-ACK to also support the signaling of Msg4 PDSCH repetition.
Proposal 3: RAN1 to use a field of PDCCH- DCI Format 1_0 to indicate the number of UE specific PDSCH with Msg4 repetition.
Proposal 4: RAN1 to consider the RSRP measuring and threshold-based reporting for UE request/capability reporting for Msg4 PDSCH repetition transmission.
Proposal 5: RAN1 to introduce new filed in SIB1 for RSRP threshold used to initiate Msg4 PDSCH repetition.
Proposal 6: RAN1 to consider UE request/capability report for Msg4 PDSCH repetition by embedding the indication in Msg3 such as using MAC CE.
Proposal 7: RAN1 to supporting PDSCH-SIB1 repetition without type-0 PDCCH repetition.
Proposal 8: RAN1 to use scheduling PDCCH for enabling/disabling SIB1 PDSCH repetition.
Proposal 9: RAN1 to use scheduling PDCCH for SIB1 PDSCH to support/handle PDSCH-SIB1 repetition without type-0 PDCCH repetition.
Proposal 10: RAN1 to consider implicit indicating of SIB1 PDSCH repetition by the enabling/disabling of Type-0 CSS PDCCH repetition only when PDSCH-SIB1 repetition without type-0 PDCCH repetition is not supported.
Proposal 11: RAN1 to support repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index.

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

Source:               TCL
Title:                    Discussion on NR-NTN Downlink Coverage Enhancement
Agenda item:      9.11.1
Document for:    Discussion and Decision

Conclusion
In this contribution, the following proposals have been made:
Proposal 1: When extended periodicity of SSB is assumed, the definition of “beam hopping” needs to be clarified, e.g., beam hopping can be applied to both DL and UL beam pairs, when a beam is activated, both DL and UL can be regarded as activated simultaneously. 
 Proposal 2: For the default SSB periodicity extension and beam hopping, a valid time window associated with the SSB for the PDCCH monitoring in the type0-PDCCH CSS can be defined.
Proposal 3: The impacts of “beam hopping” on the random access procedure need to be studied, particularly with respect to the RAR window and RA contention resolution time window. 
Proposal 4: For enabling Msg4 PDSCH repetition, the repetition number can be joint coding with TDRA. 
Proposal 5: The UE capability of Msg4 with repetition needs to be reported, and Msg3 PUSCH can be utilized to carry this information.
4. 

3GPP TSG RAN WG1 #121	R1-2504170
St Julian's, Malta, 19 - 23 May, 2025
Agenda item:	9.11.1
Source: 	CCU
Title: 	Discussion on downlink coverage enhancements for NR NTN
Document for:	Discussion
1 

Conclusion
Based on the discussion in the previous sections, the following proposals were made:
Observation 1: No reserved bits remain in DCI scheduling Msg4.
Proposal 1: Support transmit repetition indicator of PDSCH repetition for Msg4 via SIB1.
Proposal 2: Support UE to report its capability.
Proposal 3: Support using DCI scheduling SIB1 to enable/disable SIB1 PDSCH repetition.
Proposal 4: Support using DCI scheduling SIB1 to indicate the slot for the second SIB1 PDSCH repetition when the Type-0 CSS PDCCH repetition is not performed.
5 

3GPP TSG RAN WG1 #121	R1-2504179
Malta, MT, 19 - 23 May 2025

Agenda item:		9.11.1
Source:	Nokia, Nokia Shanghai Bell
Title:	Discussions on downlink coverage enhancements
WI code:	NR_NTN_Ph3
Release:	Rel-19
Document for:		Discussion and Decision

Conclusion
In this contribution we have presented our observations and proposals for the DL coverage enhancements. These are as follows:
Observation 1: Adjusting the SMTC window and measurement gaps in case of dynamically changing SSB periodicity will increase the signalling overhead. 
Observation 2: A UE typically needs to measure only a very limited number of cells and not all neighbors of the serving cell.
Observation 3: Providing area specific SMTC windows increases the overhead and UE power consumption due to the extra signaling.
Observation 4: For Option 1, and when  or , the repetitions in slots associated with different SSB indexes lead to an increase in interference and impact NW scheduling flexibility. 
Observation 5: In the framework of two linked SS sets, for MOs with the same index in a slot (from each SS set), UE monitors PDCCH candidates  with the same value (from each set, i.e., ). Furthermore, UE’s expectation is that both SS sets have the same periodicity, offset, duration, maximum number of PDCCH candidates per aggregation level, and a same number of non-overlapping PDCCH MOs within a slot.   
Observation 6: With Option 1 of the working assumption, the CORESET is repeated two times.   
Observation 7: Option 2 of the working assumption led to two repetitions of the CORESET in a slot. 
Observation 8: Both Option 1 and Option 2 of the working assumption will lead to the same control overhead.
Observation 9: The UE is not intended to decode a PDSCH scheduled with SI-RNTI when modulation order is greater than 2 (QPSK). Therefore, MCS bits can be exploited to carry signalling for enabling SIB PDSCH repetitions. However, backwards compatibility must be considered for such an approach.
Observation 10: There is some room for reserved bits to carry the signaling information for enabling SIB PDSCH repetitions, but the feasibility of such solutions may be challenging, given that UE does not know at this stage if the network supports the feature or not.
Observation 11: The first PDSCH in slot  can be determined based on legacy specification, and the time/frequency resource for repeated PDSCH is indicated by the Type0-PDCCH in slot . 

Proposal 1: RAN1 should further define the assumptions for the beam activity.
Proposal 2: RAN1 to clarify if there is a coupling between DL and UL beams.
Proposal 3: RAN1 should focus on defining signals and procedures that allows flexible use of the beams in the cell.
Proposal 4: RAN1 should ensure signaling to maximize UE power savings in the case of flexible use of the beams.
Proposal 5: RAN1 to study how a UE can do a scan for neighboring cells over a period with the purpose of limiting the measurements afterwards to the relevant cells.
Proposal 6: RAN1 to ask RAN2 to study the possibility of setting the SSB periodicity to a lower value during mobility events in case of Earth Fixed Cells.
Proposal 7: PDCCH repetitions for Type0 CSS is only supported for M=2.
Proposal 8: RAN1 to down-select Option 2, i.e., repetition of the same CORESET that is associated with one SS by introducing symbol domain offset X. 
Proposal 9: RAN1 to discuss determination of the symbol domain offset X in an implicit manner and autonomously by the UE.
Proposal 10: RAN1 to down-select Option 2 for enabling/disabling SIB PDSCH repetition, i.e., using scheduling DCI.
Proposal 11: RAN1 to consider introducing a new DCI format 1-0 with different RNTI to support SIB PDSCH repetitions and PDCCH coverage enhancement.
Proposal 12: UE determines an index of slot  for repeat PDSCH as following equation:

Where  is the maximum number of SSB indexes that is specified in clause 4.1 of TS 38.213,  is SSB index and  is Type0-PDCCH multiplex factor.
Proposal 13: RAN1 to down-select Option 1 for enabling/disabling of PDSCH Msg4 repetition, i.e., UE specific PDSCH with Msg4 repetition activation indicated via PDCCH- DCI Format 1_0. 
Proposal 14: RAN1 to discuss solutions for UE to report scheduling assistant information for assisting the gNB scheduling of Msg4 PDSCH repetition factor. 
FFS: Information that needs to be included in the assistant information
FFS: Means for signaling of assistant information such as MAC-CE sub-header of Msg3
Proposal 15: RAN1 to decide expanding the functionality of “PDSCH-to-HARQ_feedback timing indicator” field in DCI 1_0 with CRC bits scrambled by TC-RNTI, where additional information to be carried related to enabling/disabling of PDSCH for Msg4 with repetition and/or repetition factor.    
Proposal 16: RAN1 to further discuss the higher layer parameters to use for DL coverage enhancements for NR over NTN.

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

Source:	OPPO
Title:	Discussion on NR-NTN downlink coverage enhancement 
Agenda Item:	9.11.1
Document for:	Discussion and Decision

Conclusion
In this contribution, we provide our view and analysis on the system-level and link-level enhancements for downlink coverage in NTN scenario. The following observations and proposals are made:
Observation 1: To support Type0 PDCCH repetition, Option 1 only requires the R19 UE to monitor the repeated PDCCH candidates in the slots   and  associated with the same SSB index for DCI detection, and the backward compatibility can be well guaranteed.
Observation 2: Option 1 can be applicable for M=1 and M=1/2, and the potential collision issue can be solved by gNB implementation, e.g., 
gNB transmits the Type0 PDCCH in the overlapping slots associated with different SSB indices with simultaneously active beams;
gNB transmits the Type0 PDCCH repetition associated with different SSB indices in the different SSB periods;
The number of SSB beams per cell is not larger than 2.
Observation 3: Option 2 requires more resources than Option 1 to support Type0-PDCCH repetition, which is not applicable to the R19 NTN scenario with limited system-level resource.
Observation 4: With Option 2, the large time span between slot  and  will degrades the combining gain of PDCCH repetition due to phase discontinuity.
Observation 5: Option 3 requires the UE to measure and record the 1st and 2nd strongest SSB beam indices, which complicates the cell search procedure, and is not feasible in some cases, e.g., 
When M=1/2, the UE cannot monitor the repeated PDCCH candidates in slots  associates with SSB index 0 and SSB index 1;
When 1 SSB beam per cell is deployed, the UE cannot monitor the repeated PDCCH candidates in slots  associates with different SSB indices.
Observation 6: Type0-PDCCH repetition with soft combining may be infeasible when there are monitoring occasions for PDCCH candidates of other PDCCH CSS set exist between the repeated PDCCH candidates of Type0-PDCCH CSS set over slots  and .
Observation 7: Besides SSB periodicity extension, extending Type0-PDCCH monitoring periodicity of 20ms can further reduce the common channel overhead to improve the DL coverage ratio.
Observation 8: The inconsistent periodicity between SSB and Type0-PDCCH may degrade the Type0-PDCCH detection performance.
Observation 9: For LEO600 set1-2, only one SI window for SIBx is covered in the active time and other SIBs cannot be transmitted.

Proposal 1: For PDCCH repetition for Type0-PDCCH CSS with  and , RAN1 to down-select from the following options:
Opt 1: Support repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index (same as M=2).
Opt 2: PDCCH repetition is not supported.
Proposal 2: For Type0-PDCCH repetition, the UE counts the repeated PDCCH candidates as 2 PDCCH candidates towards the BD limits.
Proposal 3: Confirm the work assumption with the following update (in red):
Working assumption
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported. 

RAN1 to down select between option 1 and option 2:

Option 1: Use same CORESET and two different SS (SS Set1 and SS Set2)
Linking two PDCCH candidates (adopt the same mechanism for SS linking specified in Release 17)
FFS: Blind decoding limit

Option 2: Use same CORESET associated with one SS which is repeated by introducing symbol domain offset X 
FFS: Blind decoding limit
FFS: details configuration and signalling

Nokia expressed the concern on the above working assumption that this will take physical resources away from intra-slot scheduling for legacy PDSCH.

Note: inter-slot PDCCH repetition may not allow PDCCH reception with soft combining if the UE is required to monitor the third PDCCH candidate from other PDCCH search space set between the repeated PDCCH candidates.
Proposal 4: If Type0-PDCCH repetition is enabled in PBCH, RAN1 to discuss whether the monitoring occasions for other SS sets can be configured between the repeated PDCCH candidates of Type0-PDCCH CSS set over slots  and .
Proposal 5: For intra-slot PDCCH repetition, RAN1 to support Option 2 to save the search space sets configured for PDCCH CSS repetition, and the only specification impact is to introduce a symbol offset value in the search space configuration to determine the repeated CORESET.
Proposal 6: When Type0-PDCCH CSS repetition is enabled and the searchspaceID is configured with zero value for Type0/0A/2-PDCCH CSS set, the PDCCH repetition scheme for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 should be reused.
Proposal 7: RAN1 to focus on the case that SIB1 PDSCH repetition is performed in conjunction with Type0-PDCCH repetition in R19 NTN, and the enabling/disabling of SIB1 PDSCH repetition is implicitly indicated by the enabling/disabling of Type-0 CSS PDCCH repetition.
Proposal 8: For Msg4 PDSCH repetition, 
A RSRP threshold are configured via SIB
If the measured RSRP is less than the RSRP threshold, the UE capable of Msg4 PDSCH repetition transmits repetition request and receives Msg4 PDSCH repetition.
Otherwise, the UE receives single Msg4 PDSCH.
Proposal 9: Extending Type0-PDCCH monitoring periodicity should be considered in conjunction with SSB periodicity extension in R19 NR NTN.
Proposal 10: RAN1 considers to transmit multiple SI messages in the same SI window or to transmit different SI messages in different SI periodicities.
Proposal 11: Enhancements on cell DTX/DRX should be considered as the targeted system-level enhancements in R19 NR NTN.
Support a new cell DTX/DRX mechanism, during non-active periods of cell DTX/DRX, the UE does not expect to receive/transmit any signal/channel.
The cell DTX/DRX pattern supported in R19 NR NTN apply to UE in idle mode and connected mode.

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

Agenda Item:	9.11.1
Source:	MediaTek Inc.
Title:	NR-NTN downlink coverage enhancement
Document for:	Discussion and Decision 


1 

Conclusion
In this contribution, the following proposals were made as follows:

Inter-slot PDCCH repetition for Type0 PDCCH CSS:
Observation 1: For Option 2 with X=1, the case M=1 is equivalent to Option 1 with M=2. 

Observation 2: For Option 3, the coverage is reduced by a factor 2 as each beam will need to transmit 2 SSBs with different SSB index for M=1/2 and M=1.
  
Observation 3: For Option 4, the coverage is reduced by a factor 2 as there must be overlapping of 2 activated beams for the PDCCH repetitions for M=1/2 and M=1.

Observation 4: For Option 1, it is up to the network to configure M=1/2 or M=1.

Proposal 1: RAN1 does not pursue potential solution for M=1 and M=1/2 for PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1.

Intra-slot PDCCH repetition for Type3 PDCCH CSS:
Observation 5: PDCCH 1% BLER @ SNR = -6.3 dB  (gap = 1.7 dB with -8 dB target). PDCCH with 2 repetitions combined 1% BLER @ SNR = -8.9 dB (meet the -8 dB target)
Observation 6: Option 2 requires specification of value of X depending on the duration of the CORESET and repetitions of CORESET associated with one CSS.
Proposal 2: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported with Option 1.

SIB1 repetitions:
Proposal 3: RAN1 does not pursue Type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed.


Msg4 repetitions:
Proposal 4:  RAN1 to support the following options for enabling/disabling of Msg 4 PDSCH repetitions:
Option 2: Implicitly indicated by the enabling/disabling of SIB1 PDSCH repetition.
Option 3: Explicitly indicated by SIB1 configuration.

Proposal 5: For Msg4 repetition, the network configures a single value between 2 and 4 on SIB1.

Physical layer procedures for ON/OFF beams:
Observation 7: Whether a beam is wide or narrow to perform initial DL synchronization, SI acquisition, random access procedure and data transfer is transparent to the UE in existing specifications.
Observation 8: A UE can synchronize and perform random access on wide beam and be configured via RRC signalling to make measurement with NCD-SSB transmitted on narrow beams to re-direct UE to best narrow beam for data transfer with the existing specifications.
Proposal 6: Support enhancements for transmitting the DL common channels using a wider beam footprint and transmitting DL/UL dedicated channels (incl. PRACH) using a narrower beam footprint with the following options:
As determined by the UE based on its location and assisted information broadcast on SIB.
As configured via common signalling on SIB based on UE measurements on NCD-SSBs with SS/PBCH Block index linked to narrow beam configured on SIB. 

Discontinuous reception for paging:

Observation 9: A necessary condition for UE to wake up during On duration of paging DRX cycle starting at time that coincides with an extended SSB transmission to monitor PDCCH Type-0 CSS (SIB1) and PDCCH Type-2 CSS (Paging) is that the PagingCycle is a multiple of extended SSB periodicities. 
Proposal 7: If SSB is transmitted with extended SSB periodicity, the PagingCycle is a multiple of extended SSB periodicities. 

8 

3GPP TSG RAN WG1 #121			R1-2504342
St Julian’s, Malta, May 19th – 23th, 2025 
 
Agenda Item:	9.11.1
Source:	Apple
Title:	On NR-NTN Downlink Coverage Enhancement
Document for:	Discussion/Decision

Conclusion
In this contribution, we provided our views on the downlink coverage enhancements. Our observations and proposals are as follows:

Observation 1: For inter-slot type0-PDCCH CSS repetition, if PDCCH repetitions occur in consecutive slots  and  for M=1 or ½, then 
In one implementation where type0-PDCCH/SIB1 has the same periodicity as SSB, multiple simultaneous satellite beams are required for a cell which reduces the system level coverage and leads to cross SSB beam interference.
In one implementation where type0-PDCCH/SIB1 has a larger periodicity than SSB, latency of type0-PDCCH/SIB1 reception is increased. 
In one implementation where type0-PDCCH/SIB1 periodicity for a beam is fixed to be 40 ms, the time gap between type0-PDCCH/SIB1 and SSB could be more than 20 ms, degrading the PDCCH decoding performance. 

Proposal 1: For inter-slot type0-PDCCH CSS repetition, support repeated PDCCH candidates in two slots ( and ) associated with the same SSB index (Option 2) when M=1 or ½,
where , with  being the maximum number of SSB beams allowed for a frequency band.

Proposal 2: For inter-slot type0-PDCCH CSS repetition, a capable UE performs blind decoding at slot  in a legacy way and performs blind decoding at slot  (or ) based on the combined LLR obtained from slot  and slot  (or ).
RAN1 to decide on aggregation level restriction for type0-PDCCH repetition.

Proposal 3: For inter-slot type0-PDCCH CSS repetition, further check whether cross-SSB beam type0-PDCCH repetition can be used as a supplementary scheme to enhance the coverage of type0-PDCCH.

Proposal 4: For intra-slot PDCCH (other than type0 and type3) repetition on CSS other than search space zero, support search spacing linkage scheme (Option 1).
The number of blind decoding for each PDCCH candidate in two linked search spaces is {0,1} or {1, 1}. 

Proposal 5: For enabling/disabling PDSCH with Msg4 repetition, support UE specific PDSCH with Msg4 repetition activation indicated via DCI scheduling PDSCH with Msg4 (Option 1). 

Proposal 6: For PDSCH with Msg4 repetition, 
SIB1 configures an RSRP threshold.
UE reports its capability and request for PDSCH with Msg4 repetition (e.g., via Msg3 PUSCH), where the request is triggered when the measured RSRP is smaller than the configured RSRP threshold.

Proposal 7: For the indication of PDSCH with Msg4 repetition, down-select one of the following alternatives on PDSCH with Msg4 scheduling DCI indicating the activation of PDSCH with Msg4 repetitions. 
Alt 1: New RNTI (e.g., TC-RNTI +1 mod )
Alt 2: Enhanced TDRA table with each TDRA entry associated with a repetition number
Alt 3: Calculated TBS of Msg4 larger than a TBS threshold
Alt 4: Re-interpreted MSB of MCS field.

Proposal 8: For PDSCH with Msg4 repetition, the RV sequence of [0 2 3 1] is used for N=2, and the starting RV is indicated in DCI scheduling PDSCH with Msg4 repetition, where N is the configured number of repetitions.

Observation 2: At 10% BLER, the required SNR for PDSCH without repetition is -3.85 dB with 1 PRB, at 120/1024 coding rate and QPSK.

Proposal 9: Extend PDSCH repetition from PDSCH with Msg4 repetition until dedicated PDSCH configuration is available, where the number of PDSCH repetition is equal to the number of PDSCH with Msg4 repetition.

Proposal 10: RAN1 to support PDSCH with SIB1 repetition without type0-PDCCH CSS repetition.

Proposal 11: For PDSCH with SIB1 repetition occurs without type0-PDCCH CSS repetition, support 
PDSCH with SIB1 initial transmission is in the same slot as type0-PDCCH transmission.
PDSCH with SIB1 repetition is X slots after the PDSCH with SIB1 initial transmission, where  for ;  for .
RV cycling is applied for PDSCH with SIB1 repetition.

Proposal 12: For the indication of PDSCH with SIB1 repetition, use a reserved bit in scheduling DCI with CRC scrambled by SI-RNTI.

Proposal 13: For the default SSB periodicity extension and beam hopping, the radio frames for UE’s PDCCH monitoring in the type0-PDCCH CSS sets need to be modified, depending on the default SSB periodicity and the radio frames with SSB coverage. 

Proposal 14: If the uplink beam hopping is considered, the RACH occasion offset need to be modified, depending on the radio frame with SSB coverage. 

Proposal 15: For the default SSB periodicity extension and beam hopping, adjust the Msg2/Msg4/MsgB reception window such that they are within the duration with satellite beam coverage. 

Proposal 16: To avoid UE’s unnecessary downlink monitoring and uplink transmissions, the duration of downlink and uplink beam coverage for a beam footprint should be indicated by network. 

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

Agenda item:	9.11.1
Source: 	Qualcomm Incorporated
Title: 	Downlink coverage enhancement for NR NTN
Document for:	Discussion/Decision

Summary
In this contribution, we have proposed solutions for link level enhancements for PDCCH from CSS, SIB1 PDSCH and msg4 PDSCH. We have also proposed several mechanisms to better support extended SSB periodicities during initial access. Our proposals and observations are listed below: 
Observation: In FR1, SIB1 repetition within two-consecutive slots can be transmitted 4 times within a 160 ms period for all the SSBs. 
Proposal 1: For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, support repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index (  as defined in section 13 of TS 38.213).
Repeated PDCCH candidates share the same aggregation level (AL), coded bits and same candidate index
Note: if the network repeats the Type 0 PDCCH across two consecutive slots, a legacy UE might decode the PDCCH and associated PDSCH in one slot and skip PDCCH monitoring in the other slot. 


Proposal 2: For enabling/disabling SIB1 PDSCH repetition, support option 3: 
Option 3: The enabling/disabling of SIB1 PDSCH repetition is implicitly indicated by the enabling/disabling of Type-0 CSS PDCCH repetition.


Proposal 3. For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported. 
Use same CORESET associated with one SS which is repeated by introducing symbol domain offset X 
Existing BDlimits apply. 
The maximal number of PDCCH repetitions is 2.
X (>=the number of symbols of the associated CORSET) is in the unit of DL symbols.
Details of signaling are up to RAN2. 

Proposal 4: Support indication of Msg4 repetition number X (X=1, 2 or 4) in SIB1.
Up to two different values of X, x1 and x2, can be configured together with a SFN number, N:
x1 for Msg4 transmitted earlier than beginning of SFN N and x2 for Msg4 transmitted in SFN N or after.
If only one value of X is configured, the value applies for all the time.
Unless UE indication of capability/request of Msg4 repetition is supported, UE capable of reception of Msg4 with repetitions assumes the number of Msg4 repetitions as configured in SIB1.

Proposal 5: For Msg4 PDSCH repetition, consider the support of UE indication of capability/request in Msg3.
UE indicating the capability/request of Msg4 repetition assumes the number of Msg4 repetitions as given by SIB1.
Network may configure a RSRP threshold for Mag4 repetition. 
If the RSRP threshold is configured, UE with RSRP greater than the threshold and being capable of reception of Msg4 with repetitions indicates its request in Msg3. 
If the RSRP is not configured, UE capable of reception of Msg4 with repetitions indicates its capability in Msg3.


Proposal 6: For an NR NTN cell that supports SSB periodicity more than 20 ms for initial access, consider reducing the synchronization raster frequency points.


Proposal 7: For SSB periodicity greater than 20 ms, UE only monitors Type0-PDCCH within 40 ms of an SSB transmission. 


Proposal 8: The periodicity of SIB1 is 320 ms when SSB periodicity for initial access is more than 20 ms. 

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

Agenda item:	9.11.1
Source: 	China Telecom
Title:	Further Discussion on NR NTN downlink coverage enhancement
Document for:	Discussion

Conclusions
In this contribution, we discussed the NR NTN downlink coverage enhancement and the following proposals were made.
Proposal 1：NTN should support PDSCH-SIB1 repetition separated with Type0-PDCCH repetition.
Proposal 2: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support Option 1: Use same CORESET and two different SS (SS Set1 and SS Set2). The symbol duration between two SSs is determined by NW to ensure non-overlapping PDCCH repetitions.
Proposal 3: For SIB1 link-level enhancement, the repetition of the SIB1 PDSCH can be enabling/disabling by scheduling PDCCH.
Proposal 4: For Msg4 PDSCH enhancement, support option 1 to indicate the repetition factor.

3GPP TSG RAN WG1 #121		R1-2504459
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item:	9.11.1
Source:	Lenovo
Title:	Discussion on downlink coverage enhancement for NR NTN
Document for:	Discussion

Conclusion
In this contribution, we discussed the issues related to DL coverage enhancement for NR NTN, and our observations and proposals are as following:
Observation 1: Impact to cell identification, time/frequency synchronization due to larger default SSB periodicity can be alleviated by pre-configuration of SSB time resource and satellite ephemeris.
Observation 2: System information reception periodicity, system information modification period, paging monitoring periodicity, RACH occasion periodicity will also be impacted by the increased default SSB periodicity.
Observation 3: Wider beams for common channel signalling and narrow beams for dedicated channels may be used to provide full DL coverage in scenarios, where extended periodicity of 160ms cannot provide full coverage.
Observation 4: Association between a wide beam and several narrow beams may be exploited to have a low latency beam refinement procedure for the selection of best narrow spatial filter from the set of narrow beams within a wider beam.
Proposal 1: Support a time domain offset associated with a geographical area for PRACH time domain resource determination.
Proposal 2: For relationship among cell id, geographical area id, satellite beam, SSB, each satellite beam is associated with a geographical area id, multiple geographical area can be associated with a same cell id, and each satellite beam/geographical area can be associated with a single SSB time position/SSB index.
Proposal 3: SSB time domain position and SSB index should be configured to UE in a geographical area for geographical area identification.
Proposal 4: Support use of wider beam for common channel signalling and the use of narrow beams for UL/DL dedicated channels as an alternative to SSB periodicity extension.
Proposal 5: RAN1 to further study at least the following methods to select a narrow beam within a wider beam;
Repeated PRACH transmission over extended duration
Use of reference locations within the coverage of a wider beam
Association of a set of reference signals to narrow beams within the coverage of a wider beam
Proposal 6: Consider time resource division between wide beam and narrow beam.
Proposal 7: Geographical area identification for narrow beam can consider both wide beam index and narrow beam index.
Proposal 8: Consider beam index and power value indication for spatial/power domain beam adaptation in NR NTN.
Proposal 9: Consider satellite beam level DTX/DRX.
Proposal 10: RAN1 to define UE behaviors in off status of a satellite beam.
Proposal 11: Consider the impact of large propagation delay and dynamic DL Tx power change in addition to on-off pattern indication in R19 NR NTN.
Proposal 12: For PDCCH repetition configured by SIB1, support option 2 to introduce a symbol domain offset.
Proposal 13: For type 0 PDCCH repetition, the time domain offset of PDCCH repetitions depends on value M. When M is 1 or 1/2, the time domain offset can be larger than 1.
Proposal 14: For Msg1 PDSCH repetition, for the case of PDSCH repetition without PDCCH repetition, the repeated PDSCH should occupy a slot not occupied by PDCCH associated with other SSB index.
Proposal 15: Scheduling DCI is used for Msg4 PDSCH repetition factor indication.

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

Source:	Sharp
Title:	Discussion on NR NTN Downlink Enhancements
Agenda Item:	9.11.1
Document for:	Discussion and Decision
Type-0 PDCCH repetition and SIB1 PDSCH
The following agreements have been made for type-0 PDCCH repetition [1].

Furthermore, the following agreements have been made for type-0 PDCCH repetition [1].

In our understanding, the agreed UE behaviour is backward compatible. The legacy UEs can receive and decode PDCCH candidates in consecutive slots  and  as specified in the legacy specification. If the legacy UE successfully decoded a PDCCH addressed to SI-RNTI, the legacy UE will decode the SIB1 PDSCH scheduled by the PDCCH and pass the SIB1 to its higher layers.
Therefore, if the NTN cell is operated for UEs with and without Rel-19 DL enhancements, PDSCH repetition should be performed together with PDCCH repetition. With that, the UEs with Rel-19 DL enhancements can assume two PDSCHs scheduled by respective PDCCHs in slots  and  and the UEs without Rel-19 DL enhancements does not assume repetition and decode each slot respectively.
Observation 1: If the NTN cell is operated for UEs with and without Rel-19 DL enhancements, PDSCH repetition should be performed together with PDCCH repetition.
Therefore, the Rel-19 UE should not make any assumptions on whether PDCCH repetition is performed, regardless of the agreed indication on enabling PDCCH repetition, as above since the base station which does not support Rel-19 SIB1 PDCCH repetition will set the reserved bit in any value, purely depending on the vendors discretion. Some vendors may set the value of the reserved bit to ‘0’ and the others will set ‘1’. Therefore, the indication of enabling PDCCH repetition is not meaningful. Thus, the expected UE behaviour should be, if the reserved bit is set to the value which indicates no repetition, the UE does not need to assume the PDCCH repetition, and if the reserved bit is set to the value which indicates PDCCH repetition, the UE needs to assume the PDCCH repetition may or may not be performed.
In that sense, the number of blind decoding counted in the PDCCH dropping procedure, the UE should count the number of blind decoding one per slot when the reserved bit is set to the value which indicates no PDCCH repetition, and the UE should count the number of blind decoding one for slot  and two for slot  if the reserved bit is set to the value which indicates PDCCH repetition. 
Proposal 1: The UE should count the number of blind decoding one per slot when the reserved bit is set to the value which indicates no PDCCH repetition, and the UE should count the number of blind decoding one for slot  and two for slot  if the reserved bit is set to the value which indicates PDCCH repetition.
If an operator wants to serve a cell for UEs with Rel-19 DL enhancements only, the following two operations can additionally be considered:
PDCCH repetition is not enabled while PDSCH repetition is enabled
PDCCH repetition is enabled while PDSCH repetition is not enabled
As observed in RAN1#117 meeting [2], required SNR for SIB1 PDSCH differs in different TBS. Therefore, it is beneficial to support the case where PDCCH repetition is not enabled while PDSCH repetition is enabled, depending on SIB1 PDSCH reception. 
On the other hand, there is also a scenario where PDCCH repetition is enabled while PDSCH repetition is not enabled, considering that when SSB periodicity is 20 ms as legacy, SIB1 PDSCH repetition is natively supported within 160 ms SIB1 TTI.
Therefore, we support both scenarios above. On the other hand, some timeline restriction should be addressed. For example, when PDCCH repetition is not enabled while PDSCH repetition is enabled, the UE should not expect the PDCCH reception in slot  since it requires buffering both slots until blind decoding in slot  has been done. Likewise, when PDCCH repetition is enabled while PDSCH repetition is not enabled, the UE should not expect the PDSCH reception in slot  since it requires buffering both slots in case the UE fails to decode the PDCCH in slot  in one-shot. 
Therefore, we have proposals as follows:
Proposal 2: Support both of the following scenarios:
PDCCH repetition is not enabled while PDSCH repetition is enabled, and
PDCCH repetition is enabled while PDSCH repetition is not enabled.
Proposal 3: When PDCCH repetition is not enabled while PDSCH repetition is enabled, the UE should not expect the PDCCH reception in slot .
Proposal 4: When PDCCH repetition is enabled while PDSCH repetition is not enabled, the UE should not expect the PDSCH reception in slot .
To support the scenarios above, indication of enabling PDSCH repetition is necessary. Furthermore, unless explicit indication is not sent, the UE will need to perform blind detection of whether SIB1 PDSCH is repeated, which will complicate the UE implementation. Therefore, indication of enabling PDSCH repetition is necessary. Thus, our proposal is to indicate it in PDCCH payload.
Proposal 5: For enabling/disabling SIB1 PDSCH repetition, 1 bit in reserved bits of the PDCCH with DCI format scrambled by SI-RNTI is used.
Regarding other FFS regarding the cases with M=1 and 1/2, there is no issues to support it. PDCCH resource overlap can be avoided by gNB’s SSB allocation.
Proposal 6: Support PDCCH CSS type-0 repetition for any values of M.
Other CSSs
The following agreement has been made for repetition for other PDCCHs [1].

Option 2 cannot support FDM of the two PDCCH candidates while Option 1 can support. Therefore, we support Option 1. Blind decoding limit can be reused from what has been specified in Rel-17 MIMO.
Proposal 7: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support Option 1 (i.e., Use same CORESET and two different SS).
Msg4 PDSCH repetition
The following agreements have been made for Msg4 PDSCH repetition [1].

As discussed above, indication of type-0 CSS repetition is not perfect, considering the possibility of serving cells served by a base station which does not support Rel-19 enhancements. Therefore, Option 2 is not feasible. Considering that Msg4 PDSCH has already supported HARQ retransmissions, indication based on each DCI is preferred. Therefore, we propose the following:
Proposal 8: For Msg4 PDSCH repetition, support Option 1 (i.e., UE specific PDSCH with Msg4 repetition activation indicated via PDCCH- DCI Format 1_0).
Regarding the FFS point of how and whether network is informed by the UE that certain conditions are met to trigger Msg4 PDSCH repetition, we think the UE capability information is available once the msg3 is sent. Therefore, in Msg4, the network and the UE should have the same understanding on the Msg4 PDSCH repetition capability. 
Proposal 9: UE capability for Msg4 PDSCH repetition is defined.
Conclusion
In this contribution, we have the following observations:
Observation 1: If the NTN cell is operated for UEs with and without Rel-19 DL enhancements, PDSCH repetition should be performed together with PDCCH repetition.
In this contribution, we have the following proposals:
Proposal 1: The UE should count the number of blind decoding one per slot when the reserved bit is set to the value which indicates no PDCCH repetition, and the UE should count the number of blind decoding one for slot  and two for slot  if the reserved bit is set to the value which indicates PDCCH repetition.
Proposal 2: Support both of the following scenarios:
PDCCH repetition is not enabled while PDSCH repetition is enabled, and
PDCCH repetition is enabled while PDSCH repetition is not enabled.
Proposal 3: When PDCCH repetition is not enabled while PDSCH repetition is enabled, the UE should not expect the PDCCH reception in slot .
Proposal 4: When PDCCH repetition is enabled while PDSCH repetition is not enabled, the UE should not expect the PDSCH reception in slot .
Proposal 5: For enabling/disabling SIB1 PDSCH repetition, 1 bit in reserved bits of the PDCCH with DCI format scrambled by SI-RNTI is used.
Proposal 6: Support PDCCH CSS type-0 repetition for any values of M.
Proposal 7: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support Option 1 (i.e., Use same CORESET and two different SS).
Proposal 8: For Msg4 PDSCH repetition, support Option 1 (i.e., UE specific PDSCH with Msg4 repetition activation indicated via PDCCH- DCI Format 1_0).
Proposal 9: UE capability for Msg4 PDSCH repetition is defined.
References
RAN1 chairman’s note at RAN1#120bis meeting, April 2025
RAN1 chairman’s note at RAN1#117 meeting, May 2024 

TDoc file conclusion not found

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

Source:	NTT DOCOMO, INC.
Title:	Discussion on DL coverage enhancement for NR-NTN
Agenda Item:	9.11.1
Document for: 	Discussion and Decision

Conclusion
In this contribution, we discussed DL coverage enhancement for NR-NTN. Observations/Proposals are summarized as following: 
Observation 1:
For PDCCH repetition of CSS type 0, there is no motivation to prohibit NW implementation to use M = 1 and M = 1/2.
Proposal 1:
For PDCCH repetition of CSS type 0, the same solution as for M = 2 is applied to M = 1 and M = 1/2.
i.e., M = 1 and M = 1/2 can be used for repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index.
No additional spec impact is assumed to support M = 1 and M = 1/2.
Observation 2:
For PDCCH repetition of CSS type 0A/0B/1/1A/2/2A, there is no motivation to do BD for each repetition without soft-combining.
Proposal 2:
For PDCCH repetition of CSS type 0A/0B/1/1A/2/2A, with respect to CORESET/SS,
Support Option 1, i.e., 
Use same CORESET and two different SS (SS Set1 and SS Set2)
Linking two PDCCH candidates (adopt the same mechanism for SS linking specified in Release 17)
The configurations are included in SIB1
Proposal 3:
For PDCCH repetition of CSS type 0A/0B/1/1A/2/2A, with respect to blind decoding,
Support ‘1’ as required number of BDs for the two PDCCH candidates
Proposal 4:
For PDCCH repetition of CSS type 0A/0B/1/1A/2/2A, with respect to enabling/disabling,
Enabled if configurations of CORESET/SS are received in SIB1.
Observation 3:
R17 PDCCH repetition is assumed with the following two decoding behavior, which may not be reasonable in R19 NTN.
A: Two blind decoding (Decode of the first PDCCH + Decode of the second PDCCH)
B: Three blind decoding (Decode of the first PDCCH + Decode of the second PDCCH + Decode of a soft-combined PDCCH)
Proposal 5:
For repetitions of PDCCH CSS type 3 and USS,
Support ‘1’ as required number of BDs for the two PDCCH candidates.
Specify BD counting rule for this support of ‘1’, in TS 38.213.
Proposal 6:
For SIB1 PDSCH repetition,
With respect to SIB1 PDSCH rep without PDCCH rep of type 0 CSS
Support this case.
When SIB1 PDSCH repetition is performed, the PDSCH slots are slots  and .
With respect to enabling/disabling, support Option 2, i.e., using scheduling PDCCH.
1 bit of 15 reserved bits is used for the indication.
Proposal 7:
For Msg4 PDSCH repetition, with respect to RV cycling for N = 2,
Apply RV cycling with “n mod 4 = 0” and “n mod 4 = 1” in the table for N = 4
Proposal 8:
For Msg4 PDSCH repetition, with respect to enabling/disabling,
RAN1 to clarify Option 3 means:
Interpretation 1: the repetition is performed w/o dynamic indication, or
Interpretation 2: whether to apply the repetition may be indicated dynamically
Proposal 9:
For Msg4 PDSCH repetition, with respect to enabling/disabling and repetition factor determination,
A single value X from {2, 4} is configured for repetition factor, via SIB1.
If configured, dynamic indication of Msg4 PDSCH repetition is enabled; otherwise, repetition is disabled.
A single value from {1, X} is indicated for repetition factor, via the scheduling DCI.
1 bit of MCS field is used for the indication.
Proposal 10:
For Msg4 PDSCH repetition, with respect to UE request based on conditions,
Not support that NW is informed by the UE that certain conditions are met to trigger Msg4 PDSCH repetition.
Proposal 11:
For Msg4 PDSCH repetition, with respect to UE capability,
UE being capable of RX of Msg4 PDSCH repetitions reports its capability via Msg3 LCID codepoints.
Proposal 12:
Not support RO enhancements to adapt to the extended SSB periodicity of 160 ms.


Agreements
RAN1#116
Agreement
For DL coverage study, consider the following additional reference satellite parameters scenarios for LEO600km Set1 in FR1 (i.e., S-band), referred to as Set1-1 FR1, Set1-2 FR1 and Set1-3 FR1:




Note: RAN1 will aim to identify necessary enhancements for these scenarios in the study phase. At the end of the study phase, RAN1 will further discuss whether the potential enhancements will be specified within Rel-19 framework.

Agreement
For DL coverage study at system level, consider the following additional reference satellite payload parameters for LEO600km in FR2 (i.e., Ka-band):


Agreement
Adopt the following phased array antenna parameters for LEO 600km in FR1:

Agreement
RAN1 to consider the following performance metrics for DL Coverage enhancement evaluation at system level:
At least:
CDF of the received SINR
The dwell time and revisit time interval for each beam illumination across the coverage
Periodicity of common control channels (e.g. SSB, CORESET0/SIB1, SIB19) and corresponding coverage ratio

Other metrics may be reported such as
CDF of the cell throughput
CDF of user perceived throughput (UPT)
CDF of Latency
Ratio of mean served cell throughput and offered cell throughput, denoted by 𝜌 (refer to TR36.889)

For system level study based on analytical evaluation:
N1 beam footprints are in state “off”
These beam footprints are not served by any signal (no satellite service in this area)
N2 beam footprints are in state “common messages only”
These beam footprints do not have any active user traffic, and are served the necessary information for cell discovery and initial access.
Optionally, companies may consider user arrival (e.g. RACH access) in this type of cell, and should describe how this is taken into account in the analytical evaluation
N3 beam footprints are in state “active traffic” 
These beam footprints have X active (e.g. VoNR) users each.
These beam footprints are also served the necessary information for cell discovery and initial access
N1 + N2 + N3 = “Total number of beam footprints “ 
N1, N2, N3, X are to be reported by companies.
Resource utilization obtained under the assumptions above is to be reported by companies.
Other assumptions made in the evaluation are to be reported by companies, e.g. power sharing scheme, beam hopping scheme, etc.

Agreement
For NR NTN Rel-19 DL coverage evaluation, UE characteristics for handheld terminals in Table 6.1.1.1-3 in TR 38.821 can be reused, with the following:
-5.5 dBi antenna gain is assumed
at least 2Rx are considered at the UE
4Rx can be optionally considered and reported 
Note: Redcap device is not considered in the scope of DL coverage study

Agreement
The following traffic models are considered for system level evaluation of DL coverage:
FTP3: as in Table 6.1.1.1-7 of TR 38.821: 0.5MB as packet size, 200ms as mean inter-arrival time 
FTP3 IM: 0.1MB as packet size, 2s as mean inter-arrival time 
VoIP can be considered in the evaluation. 

It is up to company report which traffic model is used among the discussed traffic models in their evaluations.
Other models may be used as well, and parameter (e.g. packet size and arrival rate) adjustment can be optionally considered and reported.

Agreement
For NR NTN Rel-19 DL coverage evaluation, Beam layout defined in Table 6.1.1.1-4 in TR 38.821 can be reused.
Using other beam layouts is not precluded, and should be reported by companies

Agreement
For NR NTN Rel-19 DL coverage evaluation, a value of beam steering latency equal to 0 at least if phase array antenna is assumed.
Values different from 0 can be optionally reported

Agreement
DL coverage is evaluated at link level with the following considerations:
NGSO at LEO-600 operating in FR1 is considered in priority
Additional satellite payload parameters defined for system level evaluation are used
FFS: Antenna gain reduction due to steering loss can be considered 

Agreement
For the evaluation of NTN downlink coverage at link level, reuse the target data rate from Rel-18 NTN Coverage enhancements:
For VoIP: AMR 4.75 kbps (TBS of 184 bits without CRC in physical layer) with 20 ms data arriving interval 
For data rate service: both 3 kbps and 1Mbps can be considered
Companies can also use the data rates corresponding to the traffic types used for system level evaluations

Agreement
For link-level study, downlink coverage performance in NR NTN is evaluated according to the following steps.
Step 1: CNR is calculated as defined in 6.1.3.1 of TR 38.821
Step 2: Required SNR of target service is evaluated by LLS
Step 3: The CNR and the required SNR are compared

Agreement
For link-level study, for NR NTN DL coverage enhancement, the following channels/signals can be considered for evaluations:
PDSCH for VoIP
PDSCH for low data rate service
PDSCH Msg.2
PDSCH Msg.4
PDSCH carry SIB, e.g., SIB1, SIB 19
PDSCH for paging
PDCCH
Broadcast PDCCH (e.g. PDCCH of Msg.2, paging)
SSB
Note: RAN1 will aim to identify necessary link-level enhancements for these channels in the study phase. At the end of the study phase, RAN1 will further discuss whether the potential link-level enhancements will be specified within Rel-19 framework.

Agreement
For DL coverage performance evaluation, the following are assumed for all channels/signals
Channel model/Delay spread:
Channel model as in Table 6.1.2-4 of TR38.821, NTN-TDL-C (LOS)
Evaluation scenario:
Rural (LOS)
Channel estimation: Realistic estimation:
Companies are encouraged to report channel estimation method.
SCS:
15 kHz only
UE speed: 3 km/h
Frequency drift: TBD
Frequency offset: 0.1 ppm

Agreement
For link budget calculation, parameters in the following table are assumed:

RAN1#116bis
Agreement
For coverage evaluation of PDCCH in NR NTN, the following table is assumed:

Agreement
For coverage evaluation of PDSCH in NR NTN, the following table is assumed:

Agreement
Antenna gain reduction due to steering loss is not considered in the link level evaluation.
Note: This is aligned with the assumptions made in Rel-18 UL coverage enhancement

Observation
The CNRs for the satellite payload parameters Set 1-1, Set 1-2 and Set 1-3 are equal to -1.9 dB, -1.9 dB and -9.9 dB respectively.

Agreement
Confirm the Satellite phased-array antenna parameters for LEO 600km in FR1 defined in RAN1#116.
Al least the above model is considered for SLS to ease the alignment between evaluation results. The model below can be optionally considered:
Note 1: The maximum antenna gain is determined by considering an overall array efficiency [of 50%.] 

Agreement
For coverage evaluation of PDSCH in NR NTN, the following payload sizes for PDSCH are assumed:
Note: At least the above values are simulated and reported. Other values can be considered.
Note: the values above are not the TBS.

Agreement
For DL coverage study at system level, it is up to companies to report the following parameters for LEO600km Set1-1 FR2:

Agreement
For coverage performance evaluation of DL channels/signals before the SIB19 acquisition, the maximum Doppler frequency drift is assumed to be equal to 0.27 ppm/s based on TR 38.821.

RAN1#117
Observation
Based on LLS results on PDCCH coverage evaluation collected from different sources:
It is observed that the required SNR for PDCCH is in average equal to -6dB (17 sources)
With parameter LEO600km Set1-1 FR1 and 1-2 FR1: 
17 sources observed that there is no coverage gap with Set1-1/1-2 FR1.
The coverage margin is around 4 dB compared to CNR of -1.9 dB.
With parameter LEO600km Set1-3 FR1: 
15 sources observed that there is a PDCCH coverage gap of 3.9dB in average compared to CNR of -9.9 dB.
Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDCCH.

Observation
Based on LLS results on PDSCH Msg2 coverage evaluation collected from different sources:
It is observed that the required SNR for PDSCH carrying Msg2 is in average equal to – 10.9 dB (14 sources)
With parameter LEO600km Set1-1 FR1 and 1-2 FR1: 
14 sources observed that there is no coverage gap for PDSCH with Msg2: 
The coverage margin is around 9 dB compared to CNR of -1.9 dB  
With parameter LEO600km Set1-3 FR1: 
12 sources observed that there is no coverage gap for PDSCH with Msg2: 
The coverage margin is around 1 dB on average compared to CNR of -9.9 dB
Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH Msg2.

Observation
Based on LLS results on PDSCH Msg4 coverage evaluation collected from different sources:
It is observed that the required SNR for PDSCH carrying Msg4 is in average equal to – 5.2 dB (14 sources)
With parameter LEO600km Set1-1 FR1 and 1-2 FR1: 
14 sources observed that there is no coverage gap for PDSCH with Msg4: 
The coverage margin is around 3.3 dB on average compared to CNR of -1.9 dB
With parameter LEO600km Set1-3 FR1: 
11 sources observed that there is a coverage gap for PDSCH with Msg4: 
The coverage gap is around 4.7 dB on average compared to CNR of -9.9 dB
1 source observed that there is no coverage gap for PDSCH with Msg4 with a coverage margin of 0.3 dB compared to CNR of -9.9 dB
Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH Msg4.

Observation
Based on LLS results on PDSCH SIB1 coverage evaluation collected from different sources:
For PDSCH carrying SIB1 option 1 (with a payload size of 800bits) it is observed that the required SNR is in average equal to – 5.8 dB (14 sources)
For PDSCH carrying SIB1 option 2 (with a payload size of 1280bits) it is observed that the required SNR is in average equal to – 3.4 dB (12 sources)
With parameter LEO600km Set1-1 FR1 and 1-2FR1: 
14 sources observed that there is no coverage gap for PDSCH with SIB1 option 1: 
The coverage margin is around 3.9 dB on average compared to CNR of -1.9 dB
12 sources observed that there is no coverage gap for PDSCH with SIB1 option 2: 
The coverage margin is around 1.5 dB on average compared to CNR of -1.9 dB

With parameter LEO600km Set1-3 FR1: 
11 sources observed that there is a coverage gap for PDSCH with SIB1 option 1: 
The coverage gap is around 4.1 dB on average compared to CNR of -9.9 dB
1 source observed that there is no coverage gap for PDSCH with SIB1 option 1: 
The coverage margin is 3.4 dB compared to CNR of -9.9 dB
10 sources observed that there is a coverage gap for PDSCH with SIB1 option 2: 
The coverage gap is around 6.5 dB on average compared to CNR of -9.9 dB
Note: some results assumed SIB1 combination (where SIB1 is repeated within 160 ms) and some results assumed no SIB1 combination
Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH carrying SIB1.

Observation
Based on LLS results on PDSCH SIB19 coverage evaluation collected from different sources:
It is observed that the required SNR for PDSCH carrying SIB19 is in average equal to – 6.9 dB (14 sources)
With parameter LEO600km Set1-1 FR1 and 1-2 FR1: 
12 sources observed that there is no coverage gap for PDSCH with SIB19: 
The coverage margin is around 4.2 dB on average compared to CNR of -1.9 dB  
With parameter LEO600km Set1-3 FR1: 
10 sources observed that there is a coverage gap for PDSCH with SIB19: 
The coverage gap is around 3.5 dB on average compared to CNR of -9.9 dB
Note: all the results above assumed no SIB19 combination
Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH carrying SIB19.

Observation
Based on the results of DL coverage ratio evaluation at system level collected from 7 sources for all the three LEO600km satellite parameter sets where the beam footprint diameter is 50 km:
For Set 1-1/1-3, the coverage ratio can be improved from 10% to 100% if the SSB periodicity is increased from 20ms to 80ms and beam hopping is applied
For Set 1-2, the coverage ratio can be improved from 1.5% to 96.8% if the SSB periodicity is increased from 20ms to 320ms and beam hopping is applied.
Note: coverage ratio is N2+N3/ total beam footprints
Note: the baseline assumes no beam hopping. TDM between SIB1 and SIB19 is assumed in those results, following current specs.
Based on the results of DL coverage ratio evaluation at system level collected from 3 sources for a deployment scenario implementing wide beam footprint:
1 source reports that with a deployment of wide beam covering 4 narrow (of 50km size) beams, which means Set 1-2 FR1 with additional EIRP reduction of 6dB, using SSB periodicity of 80 ms can provide coverage ratio of 96.8%, and Set 1-1/1-3 FR1 with additional EIRP reduction of 6dB, SSB periodicity of 80 ms can provide coverage of 100%.
1 source observed that for Set 1-1, 1-2 and 1-3, the coverage ratio can be improved from 1.5% to 100% using the legacy default SSB periodicity of 20ms during initial access, by choosing a wide beam footprint with beam footprint sizes of 84 km and 56 km respectively. 
Note: the PDCCH and the PDSCH for SIB19 is assumed to be transmitted within 2 OFDM symbols and 5 MHz bandwidth. the PDSCH for SIB1 is assumed to be transmitted within 3 OFDM symbols and 5 MHz bandwidth. This assumes no SIB1 and SIB19 transmission in N2 beam footprints. This assumes non-aligned SFN timing across different beams.
1 source observed, for Set 1-1 with increased beam size, that the legacy SSB periodicity of 20ms during initial access is usable with NTN beam hopping, by choosing a deployment scenario implementing wide beam footprint with beam footprint sizes of 70.7 km and 86.6 km, leading to a total of 529 and 353 beam footprints within the satellite coverage area, respectively, and the coverage ratio is 80% and 90%, respectively, and a ratio of simultaneously active beam footprints to the total number of beam foot prints equal to 20% and 30%. 
Note: Beam footprint size is increased by increasing only the adjacent beam spacing without increasing the 3dB beamwidth.
Note: RAN1 will further investigate the impact of SSB periodicity extension
Note: Any needed clarification “SSB channel enhancement is not considered” in the WID is up to RAN plenary
Note: RAN1 will further investigate the impact of wider beam of SSB and/or other channels on performance (e.g. link budget, capacity...)

Observation
Based on LLS results on PDSCH for VoIP coverage evaluation collected from different sources:
It is observed that the required SNR for PDSCH for VoIP is in average equal to – 11 dB (11 sources)
With parameter LEO600km Set1-1 and 1-2 FR1: 
When PDSCH repetition is enabled, 11 sources observed that there is no coverage gap for VoIP: 
The coverage margin is around 9.1 dB on average, compared to CNR of -1.9 dB   
With parameter LEO600km Set1-3 FR1: 
When PDSCH repetition is enabled, 9 sources observed that there is no coverage gap for VoIP: 
The coverage margin is around 2.3 dB on average, compared to CNR of -9.9 dB
1 source observed that even with 8 PDSCH repetitions there is a coverage gap of 1.5 dB compared to CNR of -9.9 dB
Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH for VoIP.

Observation
Based on LLS results on PDSCH 3kbps coverage evaluation collected from different sources:
It is observed that the required SNR for PDSCH for low data rate is in average equal to – 11 dB (8 sources)
With parameter LEO600km Set1-1 FR1 and 1-2 FR1: 
When PDSCH repetition is enabled, 8 sources observed that there is no coverage gap for PDSCH with 3kbp: 
The coverage margin is around 9.1 dB on average, compared to CNR of -1.9 dB   
With parameter LEO600km Set1-3 FR1: 
When PDSCH repetition is enabled, 6 sources observed that there is no coverage gap for PDSCH with 3kbp: 
The coverage margin is around 1.6 dB on average, compared to CNR of -9.9 dB
Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH 3kbps.

Observation
Based on LLS results on PDSCH 1Mbps coverage evaluation collected from different sources:
It is observed that the required SNR for PDSCH with 1Mbps data rate is in average equal to – 4.1 dB (7 sources)
With parameter LEO600km Set1-1 FR1 and 1-2 FR1: 
7 sources observed that there is no coverage gap for PDSCH with 1Mbps: 
The coverage margin is around 2.2 dB on average, compared to CNR of -1.9 dB   
With parameter LEO600km Set1-3 FR1: 
5 sources observed that, there is a coverage gap for PDSCH with 1Mbps: 
The coverage gap is around 5.5 dB on average, compared to CNR of -9.9 dB
Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH 1Mbps.

RAN1#118
Observation
Based on the results of DL coverage evaluation at system level collected from different sources, it is observed that extending the default value of SSB periodicity (different from 20ms) in NTN with LEO600km satellite parameter sets where the beam footprint diameter is 50 km, is beneficial in terms of reduction of common control channel overhead, when targeting a full coverage of 1058 beam footprints: 
With Set 1-1 FR1 and Set 1-3 FR1, the common messages (SSB, SIB1) overhead is around 40% assuming 5 MHz BW when SSB/SIB1 periodicity of 20ms is in use, this overhead ratio could be reduced to less than 14% when 160ms SSB/SIB1 periodicity is used.
With Set 1-2 FR1, the common message (SSB, SIB1) overhead is greater than 100% assuming 5 MHz BW when SSB/SIB1 periodicity of 20ms is in use, this overhead could be reduced to around 25.8% when 640ms SSB/SIB1 periodicity is used.
Note: the overhead of SIB19 was included in some of the results
Note: an observation when SSB/SIB1 periodicity is 320 ms will be discussed and added to the observation

Agreement
As part of the NTN DL coverage enhancements at both system level and link level, RAN1 to consider:
Extending the periodicity of the half frames with SS/PBCH blocks assumed by UE during initial access. 
Default value[s] with extended periodicity assumed by NTN UE for initial access can be:
One [or more] values from the list {40ms, 80 ms, 160 ms, 320ms, 640ms} 
Potential enhancements for transmitting the DL common channels using a wider beam footprint, while DL/UL dedicated channels (incl. PRACH) may be transmitted using a narrower beam footprint
Link-level enhancements for the following channels:
PDCCH 
PDSCH with Msg 4 
PDSCH with SIB1/SIB19.
Note: link-level enhancements for PDSCH with SIB1/SIB19 may be applicable to other SIBs, without additional specification impact.
Note: the above does not imply that all the channels above will be enhanced, but all of them should be considered based on this agreement

RAN1#118bis
Agreement
For NR NTN, support extended periodicity of the half frames with SS/PBCH blocks assumed by UE during initial access. 
The maximum of the additional default value (apart from the existing 20ms value) is at least 160 ms.
FFS: whether 320ms can be supported as the maximum of the additional default value instead of or in addition to 160ms

Agreement
Support PDCCH CSS Link level enhancement in Rel-19 for all CSS types except type 3. 
The following techniques are for further study:
PDCCH repetition, including:
Option 1: Intra-slot PDCCH repetition
Option 2: Inter-slot PDCCH repetition
CORESET length (i.e. number of OFDM symbols) extension 
DCI format optimization (e.g. size reduction, etc)
Note: the same technique is intended to apply to all search space types targeted for link level enhancements
For the above techniques, at least the following aspects should be discussed for the relevant candidate techniques:
Configuration
Backward compatibility and UE behaviour of legacy UE
Linked Search Space
Blocking probability
DCI format size budget
Resource overhead
Impact on CORESET0
Focus on coverage enhancement for set 1-3 with a target CNR of -8 dB for NR NTN DL coverage enhancements at link level.
FFS: whether to apply the selected solution to PDCCH CSS type3 and PDCCH USS

Agreement
For PDSCH with Msg4 Link level enhancement:
Continue studying PDSCH repetition
Further discuss the specification impact for at least the following:
Procedure and signaling
Repetition factor
Focus on coverage enhancement for set 1-3 with a target CNR of -8 dB for NR NTN DL coverage enhancements at link level.

RAN1#119
Agreement
For PDSCH with Msg4 Link level enhancement:
Support PDSCH repetition
FFS: signalling design including number of repetitions
FFS: impact on UE capability
Note: the target coverage enhancement to bridge the gap with respect to single Msg4 transmission is 2.8 dB
Focus on coverage enhancement for set 1-3 with a target CNR of -8 dB for NR NTN DL coverage enhancements at link level.

Observation
Backward compatibility for legacy UEs (i.e. Rel-17 and Rel-18 UEs) assuming a default SSB periodicity of 20ms is not guaranteed when SS/PBCH blocks periodicity is larger than 20ms within the cell used for initial frequency scan.
Legacy UEs (i.e. Rel-17 and Rel-18 UEs) are not expected to be able to camp on a cell with SS/PBCH blocks periodicity larger than 160 ms.

Agreement
For link level enhancement of PDSCH with SIB1:
Support PDSCH repetitions within 20 ms duration
The number of repetitions is fixed to 2 repetitions 
Further discuss the specification impact for at least the following:
Procedure and signaling (enabling repetitions, associated time resource determination, etc.)
Note 1: without the above PDSCH repetitions, the coverage gap is 2.2 dB to 4.6 dB depending on SIB1 size.
Note 2: Focus on coverage enhancement for set 1-3 with a target CNR of -8 dB for NR NTN DL coverage enhancements at link level.
Note 3: the above is not related to multiple SIB1 transmissions across 20 ms periodicities of SSB, which may not be available when the SSB periodicity is 160 ms or larger (if supported) depending on the SSB and CORESET multiplexing pattern.

Agreement
For PDCCH CSS (except Type-3) link level enhancements, support only PDCCH repetition for NTN.
FFS: intra-slot and/or inter-slot

RAN1#120
Agreement
For NR NTN, support extended periodicity of the half frames with SS/PBCH blocks assumed by UE during initial access. 
The additional default value assumed by UE during initial access (apart from the existing 20ms value) is 160 ms.

Agreement
Support only inter-slot repetition for Type0 PDCCH CSS.

Agreement
For Msg4 PDSCH repetition support, RAN1 to consider:
Option 1: UE specific repetition indication via DCI
Option 2: Msg4 repetition is configured by SIB1
Option 3: Msg4 PDSCH repetition is implicitly determined by SIB1 PDSCH repetition 

Agreement
At least for enabling PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, RAN1 to consider the following options
Option 1: Using the spare 1 bit in MIB
Option 2: Using reserved bit(s) in PBCH payload
Option 3: Using codepoint(s) in PBCH payload
Option 4: UE blind decoding without signaling from the network during initial access

Agreement
For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, consider the following:
Option 1: Support repeated PDCCH candidates in the two consecutive slots   and  associated with the same SSB index (  as defined in section 13 of TS 38.213)
Repeated PDCCH candidates share the same aggregation level (AL), coded bits and same candidate index
FFS: Details including how the two PDCCH candidates are counted toward the BD limits
Note: with option 1, if the network repeats the Type 0 PDCCH across two consecutive slots, a legacy UE might decode the PDCCH and associated PDSCH in one slot and skip PDCCH monitoring in the other slot. 
FFS: whether/how option 1 can be applicable for M=1 and M= ½
Option 2: Support repeated PDCCH candidates in the two slots   and  [or  and  ] associated with the same SSB index (  as defined in section 13 of TS 38.213)
Value of X>1, predefined or configured
FFS: Value of X 
Repeated PDCCH candidates share the same aggregation level (AL), coded bits and same candidate index
FFS: Backward compatibility to legacy UE
Option 3: 
The PDCCH candidates in slots n0 associated respectively with different SSB indexes are repetitions of each other and share the same aggregation level, coded bits and same candidate index
For M=1/2 and M=1, the repeated PDCCH candidates in two consecutive slots associated with different SSB indexes;
For M=2, the PDCCH candidates in slots n0+1 associated respectively with different SSB indexes are repetitions of each other and share the same aggregation level, coded bits and same candidate index
Option 4: Option 2 with cross SSB beam repetition support
The PDCCH candidates in slots n0 associated respectively with different SSB indexes are repetitions of each other and share the same aggregation level, coded bits and same candidate index

Agreement
For SIB1 link level enhancement, RAN1 to consider the following options:
Option 1: PDSCH repetition of SIB1 is transmitted within the same slot as the type0-CSS PDCCH repetition.
UE supporting SIB1 PDSCH coverage enhancement assumes that the PDCCH and associated PDSCH to be repeated in both slots where the corresponding PDCCHs are transmitted.
Each PDSCH SIB1 repetition is within the same slot of each PDCCH candidate for scheduling DCI
The two associated PDSCHs have the same RV
Option 2: Option 1 and an additional PDSCH with SIB1 repetition can occur after the slot of type0-PDCCH CSS repetition.
FFS: How to schedule the SIB1 repetition
Option 3: The repetition of PDSCH with SIB1 is indicated by the scheduling PDCCH
PDSCH is repeated in two slots
Note: Backward compatibility should be maintained

RAN1#120bis
Agreement
When PDCCH CSS type-0 repetition is performed, for SIB1 link level enhancement, support PDSCH repetition of SIB1 transmitted within the same slot as the type0-CSS PDCCH repetition.
UE supporting SIB1 PDSCH coverage enhancement assumes that the PDCCH and associated PDSCH to be repeated in both slots where the corresponding PDCCHs are transmitted.
Each PDSCH SIB1 repetition is within the same slot of each PDCCH candidate for scheduling DCI
The two associated PDSCHs have the same RV
FFS: Whether it is supported that type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed, and if so whether/how to handle the slot determination.

Agreement
For enabling/disabling SIB1 PDSCH repetition, RAN1 to consider the following options:
Option 1: Using reserved bit(s) in PBCH payload.
Option 2: Using scheduling PDCCH.
Option 3: The enabling/disabling of SIB1 PDSCH repetition is implicitly indicating by the enabling/disabling of Type-0 CSS PDCCH repetition.

Agreement
For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1:
Enabling/disabling using reserved bit(s) in PBCH payload
No UE behavior is defined for UE in connected mode specifically for the case where the network changes its signaling between enabling and disabling PDCCH repetition for Type0 PDCCH CSS.

Agreement
For Msg4 PDSCH repetition scheme, the Msg4 PDSCH is repeated in N consecutive slots:
The same resource allocation is assumed for all repetitions
The supported repetition factors are: 2 and 4
The network configures a single value between 2 and 4 at a given time
The RV cycling is used for each repetition
If N=4:


Agreement
For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, support repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index (  as defined in section 13 of TS 38.213) at least for M=2.
Repeated PDCCH candidates share the same aggregation level (AL), coded bits and same candidate index
Note: if the network repeats the Type 0 PDCCH across two consecutive slots, a legacy UE might decode the PDCCH and associated PDSCH in one slot and skip PDCCH monitoring in the other slot. 
Note: further discuss the potential solution for M=1 and M=1/2.

Working assumption
For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, intra-slot PDCCH repetition is supported. 
RAN1 to down select between option 1 and option 2:
Option 1: Use same CORESET and two different SS (SS Set1 and SS Set2)
Linking two PDCCH candidates (adopt the same mechanism for SS linking specified in Release 17)
FFS: Blind decoding limit
Option 2: Use same CORESET associated with one SS which is repeated by introducing symbol domain offset X 
FFS: Blind decoding limit
FFS: details configuration and signalling
Nokia expressed the concern on the above working assumption that this will take physical resources away from intra-slot scheduling for legacy PDSCH.

Agreement
For enabling/disabling Msg4 PDSCH repetition, RAN1 to down-select among the following options:
Option 1: UE specific PDSCH with Msg4 repetition activation indicated via PDCCH- DCI Format 1_0
FFS: indication details.
FFS: whether/how network is informed by the UE that certain conditions are met to trigger Msg4 PDSCH repetition (e.g. RSRP detected at UE is less than x dB) 
Option 2: The enabling/disabling of Msg4 PDSCH repetition is implicitly indicated by the enabling/disabling of SIB1 PDSCH repetition.
Option 3: The enabling/disabling is indicated by SIB1 configuration
FFS: whether/how network is informed by the UE that certain conditions are met to trigger Msg4 PDSCH repetition (e.g. RSRP detected at UE is less than x dB)
FFS: Whether UE reports its capability

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

Agenda item:	9.11.1
Source: 	CSCN
Title:	Discussion on downlink coverage enhancement for NR-NTN
Document for:	Discussion & Decision

Conclusions
In this contribution, we provide some views on downlink coverage enhancement for NR NTN scenarios. The proposals are summarized as following.
Proposal 1: SSB index should be associated with the ground beam footprint to ensure consistent synchronization and simplify mobility management for UEs.
Proposal 2: RAN1 to consider the beam hopping pattern, including dwell time and revisit time, and the UL beam hopping pattern should be considered in conjunction with the DL beam hopping pattern.
Proposal 3: The imbalanced user distribution of different beam footprints and DL/UL inter-beam interference should be considered for the beam hopping pattern design.
Proposal 4: Sufficiently sparser synchronization grids could be employed to decrease the cell search complexity.
Proposal 5: The existing Type0-PDCCH CSS MO needs to be adjusted to adapt the extended SSB periodicity and beam hopping pattern, i.e., dwell time and revisit time.
Observation 1: If the validity window mechanism is adopted:
If the same window length is configured for all cells, the complexity of on-board processing can be reduced.
Only continuous ROs can be configured for one cell in one validity window, which highly restricts the flexibility of RO configuration and beam hopping.
Observation 2: If the bitmap indication mechanism is adopted:
This mechanism needs different bitmap indications for different cells, which brings some complexity to on-board processing.
The continuous or discontinuous ROs can be configured by bitmap indication mechanism with greater flexibility, and the signaling overhead is related to the segmentation granularity.
Proposal 6: One of the following mechanisms should be introduced to configure ROs for different cells within the coverage of the same active beam:
Option 1: A validity window configured by time offset and window length,
Option 2: Time-segmented bitmap indication.
Proposal 7: The existing PO needs to be adjusted to adapt the extended SSB periodicity and beam hopping pattern.
Proposal 8: If wide beams are used, minimizing the impact on specs should be carefully considered.
Proposal 9: Option 3 should be supported which implicitly links SIB1 PDSCH repetition indication to Type-0 CSS PDCCH repetition indication, without additional signaling overhead.

3GPP TSG RAN WG1 #121	 				                           R1- 2504561
St Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item:	9.11.1
Source: 	LG Electronics
Title: 	Discussion on NR-NTN downlink coverage enhancement
Document for:	Discussion and decision

Conclusions
In this contribution, we discussed DL coverage enhancement for NR NTN. Based on the above discussion, our observations and proposals are given as follows:
Observation 1: If Type0-CSS periodicity increases, the latency to monitor PDCCHs in Type0-CSS will be increased further since the UE knows the information for CORESET#0 and Type0-CSS after completing the DL synchronization and the PBCH decoding. 
Observation 2: Type0-CSS periodicity needs to be kept to 20msec considering the coexistence with the legacy UE, the support of various sizes of SIB1 in practice, and the scheduling flexibility including the fallback operation. 
Observation 3: RAN1 haven’t discuss the necessity of the limited active UL beam ratio or the details on the active UL beam period or patterns. Moreover, it is understood that the active UL beam issue is out of scope of the WI. 
Observation 4: PRACH resource management enhancement to mitigate the interference among different cells would be out of scope. Meanwhile, in the past, RAN1 did not reach the consensus on the dynamic switching between the wide beam and narrow beam by using PRACH resource since some companies think that the UL coverage enhancement is out of scope.
Observation 5: Considering the narrow bandwidth in FR1-NTN scenario, even without PDDCH repetition for SIB1 PDCCH, some configuration of Type0-CSS of searchSpaceZero would be already restricted in practice. 
Observation 6: PDCCH repetition in slot n_0 and slot n_0+1 can work even for M=1/2 and 1 when a single SSB index or two non-contiguous SSB index are used in a cell or a beam footprint. For the case when more than 2 SSB index are used and/or two contiguous SSB index are used in a cell or a beam footprint, collision between PDCCH repetition resources can be avoided by the network implementation. 
Observation 7: UE can expect to receive the DCI format 1_0 and 0_0 with CRC scrambled by C-RNTI even in Type0-CSS after the UE is provided C-RNTI. For the DCI format with CRC scrambled by C-RNTI does not need to apply the PDCCH repetition. 

Proposal 1: RAN1 does not pursue a specific enhancement for Type0-CSS periodicity with respect to the extended default SSB periodicity of 160msec. 
Proposal 2: RAN1 does not pursue a specific enhancement for PRACH resource management including additional validity check with respect to the extended default SSB periodicity of 160msec.
Proposal 3: For PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1, support repeated PDCCH candidates in the two consecutive slots  and  associated with the same SSB index (  as defined in section 13 of TS 38.213) for all the value of M.
Repeated PDCCH candidates share the same aggregation level (AL), coded bits and same candidate index.
UE assumes that a DCI format 1_0 with CRC scrambled by SI-RNTI is mapped on the repeated PDCCH candidates.
FFS: Whether the PDCCH repetition is applicable only for the case when System information indicator is set to 0 (SIB1)
UE assumes that a DCI format 1_0 or 0_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI is mapped on a single PDCCH candidate. 
Observation 8: Considering DL coverage enhancement, the PDCCH repetition does not need to be applied to all the PDCCH candidates especially their AL is small. 
Proposal 4: If PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 is enabled, 
For PDCCH candidate X, the UE performs blind decoding of a DCI format 1_0 with CRC scrambled by SI-RNTI on repeated PDCCH candidates. 
PDCCH candidate X is PDCCH candidate with the highest CCE index with AL of 8 and/or 16 
For other cases, UE performs blind decoding of a DCI format 1_0 and 0_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI on a PDCCH candidate. 
Proposal 5: For PDCCH repetition for CSS other than Type-0 CSS and other than Type-3 CSS when it is configured with searchSpaceZero, if PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1 is enabled, PDCCH repetition is not applied to the DCI format with CRC scrambled by a RNTI other than SI-RNTI.
For PDCCH candidate X, the UE performs blind decoding of a DCI format 1_0 with CRC scrambled by SI-RNTI on repeated PDCCH candidates. 
PDCCH candidate X is PDCCH candidate with the highest CCE index with AL of 8 and/or 16 
For other cases, UE performs blind decoding of a DCI format 1_0 and 0_0 with CRC scrambled by RNTIs other than SI-RNTI on a PDCCH candidate. 
Proposal 6: For PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, support 
Option 1: Use same CORESET and two different SS (SS Set1 and SS Set2)
Linking two PDCCH candidates (adopt the same mechanism for SS linking specified in Release 17)
Remove “Cond DedicatedOnly” for searchSpaceLiningId in IE SearchSpace.
The UE counts each PDCCH candidate for the one of the search space sets  and  that the UE monitors PDCCH in the later span, as two PDCCH candidates.
Proposal 7: For Type0-CSS other than searchSpaceZero, PDCCH repetition is not supported in Rel-19 NTN WI. 
Note: Even if searchSpaceLinkingId can be configured for other CSS, the UE will ignore the searchSpaceLinkingId for Type0-CSS. 
Proposal 8: Mechanism for PDSCH repetition of SIB1 is appliable to the PDSCH addressed to SI-RNTI when PDCCH CSS type-0 repetition is performed for the DCI format scheduling the PDSCH addressed to SI-RNTI.
Proposal 9: RAN1 does not pursue any specific enhancement to support the case where type-0 PDCCH repetition is not performed while the PDSCH-SIB1 repetition is performed.
Proposal 10: For Msg4 PDSCH enhancement in Rel-19 NR NTN, 
IE PDSCH-ConfigCommon is updated to include pdsch-AggregationFactor. 
If the UE is configured with pdsch-AggregationFactor in pdsch-ConfigCommon, when receiving PDSCH scheduled by DCI format 1_0 in PDCCH with CRC scrambled by TC-RNTI, the UE assumes that the PDSCH is repeated in the pdsch-AggregationFactor consecutive slots.

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

Agenda item:	9.11.1 (NR-NTN downlink coverage enhancement)
Source: 	NICT
Title: 	Discussion on DL coverage enhancements for NR-NTN
Document for:	Discussion and Decision

Conclusion
Observations
Observation 1:
With maximum SSB periodicity of 160ms, SSB cannot be delivered to more than half of the total beam footprints for the satellite parameter set 1-2 with reasonable control signal overhead. The beam footprints without SSB transmission also occur with the satellite parameter set 1-1 and 1-3 when legacy SSB periodicity is supported in part of the satellite coverage. It is undesirable situation if they are left as out of service area.
Observation 2:
Wide beam is one of the measures to eliminate out of service area of the satellite if issues on link budget and narrow beam resolution are addressed. The narrow beam resolution can be performed with minimum specification impact if narrow beam identification capability is assumed in the satellite receiver.

Proposals
Proposal 1:
RAN1 to design optional new signal transmission for the UE which can be transmitted in response to PSS (and SSS) detection for NTN without TN coverage to enable satellite stations to start transmiting SSB and SIBs with narrow beam that the new signal is detected. 

3GPP TSG RAN WG1 #121		 R1-2504583
St Julian’s, Malta, May 19th – 23th, 2025
Agenda Item:	9.11.1
Source:	Google
Title:	Discussion on Downlink Coverage Enhancement for NR NTN
Document for:	Discussion/Decision

Conclusion
Observation 1: Apply repetitions in occasions  and  leads to following consequence; UE needs to double the buffer size and buffering time, and base station needs to double the dwell time to the cell.
Observation 2: Cross beam repetitions can be implemented based on gNB configuration without specification impact.
Proposal 1: For M=1 and M=1/2, repetitions in occasions  and  are applied. 
Proposal 2: For enabling/disabling SIB1 PDSCH repetition, it is implicitly indicating by the enabling/disabling of Type-0 CSS PDCCH repetition (Option 3).
Proposal 3: For enabling/disabling Msg4 repetition, it is implicitly indicating by the enabling/disabling of Type-0 CSS PDCCH repetition (Option 2).

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

Agenda item:	9.11.1
Source: 	CEWiT
Title: 	Discussion on Downlink Coverage Enhancements for NR NTN
Document for:	Discussion and Decision
____________________________________________________________________

Conclusion
This contribution includes the specification impacts on link and system level enhancements. 

Proposal 1: At least two repetitions can be considered to reduce the coverage gap for PDCCH at least for CSS.

Proposal 2:  Each repetition of Type0-PDCCH can have maximum number of PDCCH candidates per slot as it is inter slot repetitions

Proposal 3:  Each repetition of PDCCH, other than Type0-PDCCH, can have maximum number of PDCCH candidates per slot based on inter/intra  slot repetitions. 

Proposal 4: PDSCH timing can be decided based on the latest PDCCH repetition if the repetition is enabled. 

Proposal 5: For PDCCH repetition, apart from Type0, the same CORESET can be used with different search spaces.

Proposal 6: The searchspacelinkingID can be used to link two search spaces for the PDCCH candidates which carry the same DCI information in the consecutive slots for PDCCH repetition other than Type0-PDCCH. 

Proposal  7: Enable PDCCH repetition dynamically based on link quality.

Proposal 8: Support Cell DRX/DTX to turn ON/OFF the beams as a system level enhancement to improve the DL coverage for Rel-19 NR NTN. Rel-18 NES DRX/DTX mechanism should be modified for NTN specific scenarios as follows.
DTX/DRX can be beam-specific rather than cell-specific
SSB transmission should not be affected
Dynamic DTX/DRX patterns can be supported for a single beam as the satellite moves

Rel-19 NES introduces on-demand SSB/SIB1. Similarly, the UE can request the activation of a specific beam when it has traffic to transmit, and UE is in a RRC connected mode.

Proposal 9: Support on-demand beam activation when the UE has traffic to transmit to improve the DL coverage for Rel-19 NR NTN.

Proposal 10: Study the signalling of beam-specific DTX/DRX configurations via DCI, either by introducing a new DCI or modifying the existing DCI format.

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

Agenda Item:	9.11.1
Source:	Moderator (Thales)
Title:	List of companies’ proposals on NR-NTN downlink coverage enhancement
Document for:	Discussion, Decision

TDoc file conclusion not found

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

Agenda Item:	9.11.1
Source:	Moderator (Thales)
Title:	FL Summary #5: NR-NTN downlink coverage enhancements
Document for:	Discussion, Decision

Conclusion
It can be discussed in UE feature session whether a dedicated PDSCH repetition capability (e.g. FG5-17a and FG16-2b-5) is a pre-requisite UE feature for Msg4 PDSCH repetition.


List of companies’ proposals on NR-NTN downlink coverage enhancement
The compilation of companies' proposals and observations within the contributions under agenda item 9.11.1 could be found in R1-2504715.
RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis
The compilation of RAN1 agreements for NR NTN Phase 3 up to RAN1#120-bis could be found in R1-2503702.