3GPP TSG RAN WG1 #120bis	R1-2501715
Wuhan, China, April 7th  – 11th, 2025
Agenda Item:	9.5.3
Source:	Futurewei
Title:	Discussion of the adaptation of common signal/channel transmissions
Document for:	Discussion and decision 

Conclusions

Proposal 1: UE is configured with one additional burst periodicity for SCell.

Proposal 2: Support in DCI format 2_9 a new field that indicates periodicity index for SSB time adaptation. 

Proposal 3:  The configuration of the additional PRACH resources is available or not only after DCI 1_0 with C-RNTI indication. 

Proposal 4: For DCI-based adaptation for additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information for additional PRACH resource for a validity time duration with slot granularity, including a possible validity time duration of zero.

Proposal 5: DCI format 1_0 with P-RNTI uses the short message indicator value 00 to indicate PRACH time adaptation.

Proposal 6: A UE does not expect to receive a DCI format 1_0 signaling PRACH adaptation in the same PO with a legacy DCI format 1_0 scrambled with P-RNTI.

Proposal 7: Support Alt 1: the PRACH mask to identify the subset of the additional PRACH resources is applicable at the unit of PRACH association period.

Proposal 8: Do not use a mask to identify the subset of the additional PRACH resources for UE in connected mode.

Proposal 9: Support Option 5: From the first frame of the next SI modification period.

Proposal 10: R19 NES UEs must access with higher probability the additional PRACH time adapting resources to reduce the collisions on the legacy PRACH resources access. 

Proposal 11: Time adaptation of paging is left for RAN2 discussions.

3GPP TSG RAN WG1 meeting #120bis		                                   R1-2501766
Wuhan, China, Apr. 7th – Apr. 11th, 2025
Title: 	Discussion on common signal/channel for NES 
Source: 	ZTE Corporation, Sanechips
Agenda item:	9.5.3
Document for:	Discussion and decision

Conclusion
In this contribution, we have the following observations/proposals:
Observation 1:	Whether or not to consider SSB adaptation along with on-demand SSB depends on the support of on-demand SSB in scenario#3B.
Observation 2:	The total number of FDM-ed valid ROs (legacy ROs + additional ROs) would be larger than 8, when there is no configuration of Msg1-FDM for additional PRACH resources.
Observation 3:	Using one bit to indicate/deactivate the whole additional PRACH resources/PRACH mask pattern is sufficient.

Proposal 1:	Support there are up to 6 candidate values for additional SSB burst periodicity for the SCell configured in RRC signaling, and DCI signaling selects one of them for adapting SSB burst periodicity.
Proposal 2:	It is not necessary to introduce other parameters to restrict SSB after and SSB before adaptation.
Proposal 3:	Discuss the application delay of DCI signaling for SSB adaptation and the time instance for UE assuming adapted SSB transmission.
Proposal 4:	Support DCI format 2_9 with new RNTI for SSB burst periodicity adaptation.
Proposal 5:	Support DCI-based SSB burst periodicity adaptation in Scenario#3B.
Proposal 6:	Support Option 2: The PRACH mask is based on configuration parameters e.g., bitmap at SFN level, periodic time domain window.
Proposal 7:	When there is no configuration of Msg1-FDM for additional PRACH resources, support to define the default value for the number of FDM-ed additional PRACH resources, e.g., the default value is 1.
Proposal 8:	Clarify the two aspects for C-RNTI DCI based additional PRACH resources adaptation:
•	Which types of additional PRACH resources the C-RNTI DCI can adapt (e.g., CBRA-based PRACH resources or CFRA-based PRACH resources)
•	Which semi-static signaling for configured additional PRACH resources the C-RNTI DCI can adapt. (e.g., additional PRACH resources in SIB1 or additional PRACH resources in RRC signaling).
Proposal 9:	Support reusing the existing bit fields for adaptation of PRACH in time domain in C-RNTI DCI.
Proposal 10:	Support a new bit field for adaptation of PRACH in time domain in C-RNTI DCI.
Proposal 11:	Consider the legacy application delay of C-RNTI DCI as a starting point for the reference time point of the validity time duration
Proposal 12:	Support Option 2, i.e., Use one or more bits in ranging from bits#5 to bits#8 in the Short Message in paging DCI to carry the adaptation indication if the payload size of adaptation indication is smaller than or equal to 4.
Proposal 13:	Support ‘DCI payload size’ is one bit in P-RNTI for the adaptation of additional PRACH resources.
Proposal 14:	Support Option 2 or Option 4 (i.e., SFN of the first PF from the current I-DRX cycle or the first frame of the current SI modification period) for the reference point for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF.
Proposal 15:	Support Option 3: PEI bits for legacy POs and additional Rel-19 POs are always or not multiplexed in the same DCI 2_7 are supported via gNB configuration.

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

Agenda item:		9.5.3
Source:	Nokia, Nokia Shanghai Bell
Title:		Adaptation of Common Signal Channel Transmissions
Document for:		Discussion and Decision

Conclusions
In this contribution, we have the following observations and proposals:
Proposal-1: RAN1 considers the scenarios for SSB burst periodicity adaptation at least with Scenarios #2, #2A and #3B in AI 9.5.1. 
Proposal-2: The number of bits required for indicating the adapted SSB periodicity in DCI format 2_9 depends on the number of configured candidate SSB burst periodicity values in RRC. 
Proposal-3: Support indication of SSB adaptation jointly or independently from Cell DTX/DRX operation.
Proposal-4: Support that UE is configured to monitor DCI 2_9 with cellDTRX-RNTI for SSB adaptation.
Proposal-5: Discuss the processing time of DCI 2_9 when it indicates only SSB adaptation and when it indicates both Cell DTX/DRX and SSB adaptation.
Proposal-6: New methods to handle missed DCI is not introduced in R19.
Proposal-7: DCI or MAC-CE signalling can be considered for indicating SSB adaptation in time domain after completion of the SCell activation.
Proposal-8: Signaling of SSB adaptation in time domain for SCell should be considered jointly with the MAC-CE specified for OD-SSB at least for SCell activation. Design details, including any differentiation aspects from the OD-SSB design, can be further considered in RAN2.
Proposal-9: Support direct SCell activation with SSB adaptation in time domain based on RRC signalling. 
Proposal-10: RAN1 to discuss and decide how adaptation of SSB periodicity affects rate matching operation and CSI measurements and reporting. 
Proposal-11: RAN1 to clarify whether Rel-19 additional ROs could be used for 2-step PRACH procedure and, if yes, how. 
Proposal-12: PRACH adaptation applied to CFRA should also be investigated, if time allows, however no CFRA-specific PRACH adaptation solutions should be considered.
Proposal-13: The Rel-19 PRACH mask for NES is from a PRACH mask table. 
Proposal-14: The Rel-19 PRACH mask should apply the unit of association periods. 
Proposal-15: The PRACH mask operates over association periods, and is reset every N association periods, or every association pattern periods. Details about N, if applicable, are FFS. 
Proposal-16: If the semi-static configuration of a 4-bit mask is supported, the following Rel-19 NES PRACH mask is supported:

Proposal-17: If the semi-static configuration of a 3-bit mask is supported, the following Rel-19 NES PRACH mask is supported:

Proposal-18: If the semi-static configuration of a 2-bit mask is supported, the following Rel-19 NES PRACH mask is supported:

Observation-1: Dynamic adaptation of PRACH resources may be eventually agreed to be subject to UE capability reporting. A semi-static indication of the mask selection could then serve as baseline supported by all UEs, with processing of dynamic indication supported only by UEs who reported the corresponding capability, if any. 
Proposal-19: RAN1 to also consider higher-layer signalling based on SI, e.g. SIB1, for PRACH adaptation, in addition to the DCI-based adaptation, especially if a UE capability related to the DCI-based adaptation is introduced.
Proposal-20: RAN1 to confirm the size of the PRACH adaptation indication in the DCI, i.e., 1 bit, and to select option 2: where one of the reserved bits 5-8 within the Short Message indication is used. 
Proposal-21: The validity time duration of additional PRACH resources shall be expressed in association (pattern) period and provided to the UE via semi-static signalling, e.g. SIB1.
Proposal-22: RAN1 does not support DCI-based deactivation of additional PRACH resources.
Proposal-23: RAN1 to support Option 4 (From the first frame of the current SI modification period) or Option 5 (From the first frame of the next SI modification period) for determining the reference point for the application of the PRACH adaptation indication provided in DCI 1_0 with P-RNTI.
Proposal-24: RAN1 to discuss whether additional and legacy ROs are considered jointly (or separately) for the application of the PRACH mask index indicated in DCI 1_0 with C-RNTI, when applicable. Details of possible additional indications or PRACH mask indication application are FFS.
Observation-2: The network energy saving potential is maximized if the network can address both legacy POs and additional release 19 POs using a single PEI with DCI format 2_7.
Observation-3: A subset of the additional release 19 POs can be multiplexed with the legacy POs in a DCI format 2_7, while the remaining release 19 POs can be addressed by spare bits in the same DCI format 2_7.  
Observation-4: There may be more than 20 spare bits in the PEI DCI format 2_7, when the number of legacy POs per PEI is 4.
Observation-5: Multiplexing legacy POs and additional release 19 POs is not problematic for the false alarm rate since the paging load is low.
Proposal-25: A single PEI with DCI format 2_7 can address both legacy POs and additional release 19 POs using a mixture of multiplexing and separate signalling. 
Proposal-26: If RAN1 decides to use two PEIs, a second PEI for additional release 19 POs shall only be transmitted when needed. 
Proposal-27: RAN1 to consider PRACH adaptation in time domain to spread PRACH load when paging occasion adaptation is used.

3GPP TSG RAN WG1 #120bis                        		     R1-2501812
Wuhan, China, April 7th – 11th, 2025
Source: 	vivo
Title:	Adaptation of common signal/channel transmissions
Agenda Item:	9.5.3
Document for:	Discussion and Decision

Conclusion
In this contribution, the following proposals are summarized as follows: 
Proposal 1: Support group common DCI signalling for switching the SSB burst periodicity using DCI format 2_9 with cellDTRX-RNTI. In each block, ssb_periodicity indication is used to indicate the ssb periodicity adaptation if the higher layer parameter ssb_periodicity_adaptation is configured.
3 bit is used to indicate the ssb periodicity. 
Proposal 2: For adaptation of SSB in time-domain, SSB burst periodicity adaptation on an SCell  is applicable to Scenario 2, Scenario 2A, Scenario 3A, Scenario 3B defined in AI 9.5.1.
Proposal 3: The SSB adaptation starts from the first candidate SSB burst corresponding to the indicated periodicity by a DCI 2_9 that is X slots (DCI processing time) after the DCI format 2-9.
Proposal 4: The additional RO is invalid by a legacy RO in which the additional RO is within the same configuration of the legacy RO.
When UE is not provided with featurecombination for RA partitioning, validation for the additional ROs is based on the ROs in legacy RACH-configCommon.
When UE is provided with featurecombination for RA partitioning, validation for the additional ROs for a certain featurecombination is based on the ROs in AdditionalRACH-Config with the same featurecombiantion.
Proposal 5: For additional RO configured in RACH-ConfigCommon, the total number for CBRA and CFRA is 64.
Proposal 6: When the additional RO configured in RACH-ConfigCommon is shared by CFRA, the preambles for CBRA and CFRA per SSB per RO is determined by and ssb-perRACH-OccasionAndCB-PreamblesPerSSB for additional RO and the total number of preamble 64 in as the legacy rule.
Proposal 7: For DCI-based adaptation for additional PRACH resources, Paging DCI contains activation information for additional PRACH resource, and the length of validity time duration for availability is configured by higher layer signaling.
The reserved codepoint of Short Message indicator in the DCI format can be used for adaptation indication. 
Proposal 8: When a UE receives an activation signaling, the UE assumes the additional PRACH resources are available for N unit times starting from a reference point from the first frame of the first PRACH association period after UE receives the DCI, where N is configured by higher layer signaling.
Proposal 9: A unit time of the validity time duration is a PRACH association period.
Proposal 10: The starting time (reference point) of the validity time of additional PRACH resources is the first unit time (a PRACH association period) after UE receives and processes the activation DCI, where the DCI processing time can be defined similarly as that of the SPS release indication.
Proposal 11: When the additional RO is activated by paging DCI, UE performs RACH procedure with legacy RO or additional RO according the indication in DCI format 1_0 with C-RNTI used to trigger PRACH. However, when the additional RO is in deactivated state, UE should ignore the indication for whether the additional PRACH resource(s) is available for the triggered PRACH.
Proposal 12: For a single PRACH mask, the mask is applicable at unit of PRACH association period, and is based on bitmap at unit of PRACH association period.
Proposal 13: When a PRACH mask is configured, the reference point is from the first frame with valid RO configured by the PRACH mask within the first PRACH association period after receiving DCI. The validity time counting does not consider the PRACH mask configuration.
Proposal 14: Study PRACH resource congestion issue caused by paging concentration.
Proposal 15: PEI bits for legacy POs and additional Rel-19 POs are not multiplexed in the same DCI 2_7.
Proposal 16: For PRACH adaptation, the RRC parameters are listed in Table 1.

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

Agenda Item:	9.5.3
Source:	Spreadtrum, UNISOC
Title: 	Discussion on adaptation of common signal/channel transmission
Document for:	Discussion and decision

Conclusion
We have the following proposals.
Proposal 1: The following Working Assumption can be confirmed.
Proposal 2: Support 2 bits in DCI 1_0 with P-RNTI to indicate available PRACH resources, one is applicable for initial BWP and another is applicable for RedCap specific initial BWP.
Proposal 3: Both bits 5-8 within the Short Message (from upper layers) and reserved bits in the DCI format 1_0 with P-RNTI should be used to DCI-based adaptation for additional PRACH resources.
Proposal 4: Validity time duration for availability is configured by higher layer signaling.
Proposal 5: DCI cannot be used to explicitly deactivate the additional PRACH resources.
Proposal 6: Regarding the granularity of the validity time duration of the availability information for additional PRACH resource, paging cycle can be used.
Proposal 7: The reference point for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF for RRC idle/inactive mode UE and RRC connected mode UE can be determined by Option 1.
Option 1: SFN of the first PF from the next DRX cycle

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

Agenda Item:	9.5.3
Source:	Google
Title:	Adaptation of Common Signals
Document for:	Discussion/Decision

Conclusion
In this contribution, we provided discussion on adaptation of common signals. Based on the discussion, the following proposals are provided.
SSB time-domain adaptation
Proposal 1: Support a new RNTI (e.g., SSB-RNTI) for the group-common DCI for SSB burst periodicity update.
Proposal 2: Support MAC CE based RLM/BFD RS configuration with regard to dynamic periodicity update of SSB.
Proposal 3: For UE-dedicated signal, the rate matching pattern should be based on the updated periodicity for the SSB.
Proposal 4: For UE-dedicated signal, the rate matching pattern should be based on the initial periodicity for the SSB configured by RRC.
Proposal 5: With regard to SSB time-domain adaptation, a valid RO that overlaps with SSB should be considered as an unavailable RO
UE transmits the PRACH on the available valid RO

PRACH time-domain adaptation
Proposal 6: For PDCCH-ordered PRACH, when the additional PRACH resource is available, the applicable resources are based on the additional PRACH resource 
Proposal 7: For CFRA, support the NW to configure whether the UE should select the RO from additional PRACH resources for NES or legacy PRACH resources.
Proposal 8: For initial transmission of CBRA, support the UE to select the PRACH resource set based on the measured RSRP
If the measured RSRP is above a threshold, UE selects the RO from the additional PRACH resources for NES; otherwise, UE selects the RO from legacy PRACH resources
Proposal 9: For retransmission of CBRA, support the UE to select the RO either from the additional PRACH resources for NES or legacy PRACH resources
FFS: how to perform the power ramping for the retransmission of PRACH
Proposal 10: With regard to UEs that support NES only and UEs that support both SBFD and NES, support to configure two additional PRACH resource sets for NES
The first set is not applicable to the SBFD symbols/slots and the second set is applicable to the SBFD symbols/slots
Proposal 11: Regarding the action delay for the PRACH adaptation, support option 3 below:
Option 3: From the first frame of the first PRACH association period after UE receives the DCI

PO/PEI-O adaptation
Proposal 12: Support SSB-group-specific PO/PEI-O configuration
One PO/PEI-O may include the MOs associated one group of SSBs
Proposal 13: Support dynamic update of PO/PEI-O configuration, including
Activation/deactivation of PO/PEI-O
Activation/deactivation of MOs of a PO/PEI-O

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

Source: 	CATT
Title:	Discussion on adaptation of common signal/channel transmissions
Agenda Item:	9.5.3
Document for:	Discussion and Decision

Conclusion
In this contribution, the potential spec impacts for adaptation of common signal/channel transmission are discussed. The observations and proposals are summarized as follows:
Proposal 1: The UE is configured with one additional SSB burst periodicity for the SCell.
1 bit indication is used to activate/deactivate the additional SSB burst periodicity for a SCell.
Proposal 2: The offset between the latest SSB occasion before the switch and the first SSB occasion after the switch should follow the shorter SSB burst periodicity both before and after the switching.
No need to introduce a new RRC signaling. 
Proposal 3：For the DCI content of DCI format 2_9 with [cell DTRX-RNTI], the SSB burst periodicity indication is transmitted in the each of existing block
Proposal 4：The adaptation of SSB burst periodicity should be applicable to all scenarios in AI 9.5.1. 
Proposal 5: The SSB adaptation status can be indicated to the UE by RRC signaling.
Proposal 6: For clarification on configuration of legacy ROs, support as following：
Define the PRACH resources configured in Rel-15 RACH-ConfigCommon as ‘legacy RO’.
Proposal 7:  The parameter Msg1-FDM for the additional PRACH resources should be always configured. 
Proposal 8: When the UE receives a PDCCH order indicating the additional PRACH resource(s) available, the UE can only use additional PRACH resource to initiate RACH.
Proposal 9: One of the reserved bits in DCI 1_0 scrambled by C-RNTI can be used for PRACH adaptation indication.
Proposal 10: For the identification of the subset of the additional PRACH resource, the mask is applicable at unit of PRACH association period. 
Proposal 11: The PRACH mask for Rel-19 additional RACH resource is from a predefined PRACH mask table, and the UE can be configured with a PRACH mask from the table via semi-static signaling. 
Proposal 12: For the DCI 1_0 with P-RNTI for additional PRACH resource, the validity time duration for availability is configured by higher layer signaling, and the granularity can be one default paging cycle.
Proposal 13：For the DCI 1_0 with P-RNTI for additional PRACH resource, the location of reference point can be SFN of the first PF from next I-DRX.
Proposal 14: The DCI format 1_0 with P-RNTI can be used to carry the adaptation indication as follows:
Use one reserved bit (e.g. bits 5-8) in short message field of paging DCI to indicate available of the additional PRACH resources.
Proposal 15: The initial status for the additional PRACH resource can be indicated to UE by SIB1 or RRC signaling. 
Proposal 16：For the DCI-based adaptation indication, the payload size can be 1 bit.

3GPP TSG RAN WG1 #120bis		                         R1-2502028
Wuhan, China, April 7th – 11st, 2025
Agenda Item:	9.5.3
Source:	China Telecom
Title:	Discussion on common channel signal adaptation 
Document for:	Discussion and Decision

Conclusions
In this contribution, we discuss NES and have following observations and proposals:
Observation 1: The PRACH mask and PRACH level adaptation shouldn’t be triggered at the same time, the same 1 bit indication should be used to activate the utilization of PRACH mask. 
Observation 2: Whether the PRACH mask is available should be indicated explicitly when the additional PRACH and PRACH mask are configured at the same time. 
Proposal 1: SSB adaptation can be adopted in Scenario #3A/#3B. 
Proposal 2: Support UE to be configured with 3 additional SSB burst periodicities. 
Proposal 3: Support to predefine the PRACH mask in a mask table and configure corresponding index in RRC parameters.  
Proposal 4: Support to configure the value/granularity of validity time duration in RRC configuration. 
Proposal 5: Value 0 of the 1-bit indication in DCI 1_0 with P-RNTI should be used to deactivate the PRACH adaptation, including additional PRACH resources and PRACH mask.
Proposal 6: Support Option 3, i.e., from the first frame of the first PRACH association period after UE receives the DCI, as the reference point of PRACH adaptation. 
Proposal 7: Not support partial muting of PRACHs in a PRACH association period or PRACH pattern association period in the corresponding level PRACH mask mechanism. 
Proposal 8: For determining the additional PRACH resources for the adaptation of PRACH in time-domain, for Alt1 (same PRACH configuration index), Opt 1-2a should be prioritized with N1=1.
Proposal 9: Support Opt 1-5, i.e., no additional mechanism adapted, for determining the additional PRACH resources for the adaptation of PRACH in time-domain, for Alt2 (different PRACH configuration index).
Proposal 10: Not support to adopting the PRACH adaptation in time-domain with both same and different configuration index at the same time.   

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

Agenda item:	9.5.3
Source:	KT Corp.
Title:	Discussion on adaptation of common signal/channel transmissions
Document for:	Discussion and decision


1. 

Conclusion
We give our proposals in this contribution as follows:

Proposal 1: For the adaptation of CD-SSB on sync raster (B1), if it is supported, the maximum period is limited to 20ms.

Proposal 2: The changed period is initially applied between the first SSB burst and the second SSB burst after the indication.

Proposal 3: UE can be configured with multiple SSBs with adaptive periodicity, as well as multiple additional SSB burst periodicities for the SCell.

Proposal 4: Indication signal contains target SSB and target periodicity, if it is needed.

Proposal 5: Both MAC-CE and DCI can be used to indicae aperiod switch.

Proposal 6:  For a cell supporting SSB adaptation operation, support at least Option 2 and further study whether to additionally support Option 1.
Option 1: A CSI report configuration is associated with both of SSB after and before adaptation 
Option 2: A CSI report configuration is associated with one of SSB after and before adaptation 

Proposal 7: For a cell supporting SSB adaptation operation and for L1 measurement based on adaptive SSB, further study whtheer periodic, semi-persistent, or aperiodic CSI report can be supported.
If MAC-CE based trigerring is supported, semi-persistent, or aperiodic CSI report is supported and periodic CSI report is not supported.

Proposal 8: Collision handling with another signal and channel is further studied at least for the region of SSB transmission that is not transmitted after adaptation, including collision with CSI-RS and PDSCH.

Proposal 9: For the additional PRACH resources by adaptation, only CBRA is supported.


5. 

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

Agenda Item:	9.5.3
Source: 	Fujitsu
Title:	Discussion on adaptation of common signal / channel transmissions
Document for:	Discussion/Decision

Conclusions
In this contribution, we discussed common signal/channel adaptation to achieve power saving for network. The following observations and proposals are provided.
Observation 1. The group common DCI for switching SSB burst periodicity can be applied in all the scenarios identified in 9.5.1.
Proposal 1. Regarding the group common DCI for switching SSB burst periodicity using DCI format 2_9, support the following:
reuse the cellDTRX-RNTI
same search space configuration 
Proposal 2. To indicating SSB periodicity switching by DCI format 2_9 with CellDTRX-RNTI, the following two options can be considered.
Option 1. The information block for Rel.19 SSB periodicity switching indication is always separate from the information block for Rel.18 Cell DTX/DRX indication and Rel.18 NES mode indication  
Option 2. The Rel.19 SSB periodicity switching indication can be placed in the same the information block as Rel.18 Cell DTX/DRX indication and Rel.18 NES mode indication if the UE supports both Rel.18 NES feature and Rel.19 SSB adaptation
Proposal 3. PRACH adaptation for 2-step RACH is deprioritized. 
Proposal 4. Support using PRACH association pattern period as the unit for the semi-static configured PRACH mask.
Proposal 5. The PRACH mask is identified based on configuration parameters, e.g. bitmap at PRACH association pattern level.
Proposal 6. For the DCI-based adaptation to indicate whether the additional PRACH resources are available or not, confirm that DCI payload size = 1 bit.
Proposal 7. To carry the adaptation indication in DCI format 1_0 with P-RNTI, Option 2 (i.e., Use one of Bits 5-8 within the Short Message) is supported. 
Proposal 8. Regarding the reference point for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI, 
If RRC_CONNECTED mode UEs monitor DCI format 1_0 with P-RNTI in every paging cycle, same as the legacy ETWS or CMAS capable RRC_CONNECTED UEs, Support option 1 (i.e., SFN of the first PF from the next I-DRX cycle)
Otherwise, support option 5 (i.e., From the first frame of the next SI modification period)
Proposal 9. The validity time duration for availability indication is defined as an integer multiple of a certain unit. 
If a RRC parameter, e.g., PRACH_validityDuration, is configured, the configured value is used.
If the parameter is absent, a default/pre-defined value is used.
Proposal 10. The unit of the validity time duration is aligned with the reference point. Select one of the following options based on the discussion outcome of reference point.
I-DRX cycle
SI modification period
PRACH association period
Observation 2. Using DCI to deactivate the additional PRACH resources in the middle of the validity time duration is beneficial for network energy saving. However, it may cause RACH failure if a UE misses the deactivation DCI and continues to transmit on the additional PRACH resources.
Proposal 11. The UE assumes that the availability indication of additional PRACH resources indicated by the PDCCH order is applied immediately and that the additional PRACH resources remains available until the triggered RACH procedure is completed.
Proposal 12. At least when the value of “random access preamble index” field is not all zeros, the SSB index and PRACH mask index indicated by the PDCCH order apply to both legacy PRACH resources and additional PRACH resources.
If the PRACH mask index indicates a PRACH occasion that exists solely for additional PRACH resources or legacy PRACH resources, then it can only be applied to those specific resources. 
Observation 3. At least 4 bits are reserved in PDCCH order.
Proposal 13. The 1-bit indication of PRACH adaptation is carried by one of the reserved bits.
Observation 4. When the additional PRACH resources are configured to be FDMed with the legacy PRACH resources, the RA-RNTI issue occurs even if the UEs select different ROs, making the UEs unable to distinguish the RAR intended for them. 
Proposal 14. Whether/how to address the RA-RNTI issue is left to RAN2.
Send a LS to RAN2 regarding the RA-RNTI issue.
Proposal 15. How to select PRACH resources is left to RAN2.

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

Source: 	CMCC
Title:	Discussion on adaptation of common signal/channel transmissions
Agenda item:	9.5.3
Document for:	Discussion/Decision

Conclusion 
In this contribution, we discussed the adaption of common signal/channels, include SSB adaptation in time domain, PRACH adaptation in time domain and Paging adaptation, and the following proposals are made:
Proposal 1: For SSB adaptation, support Scenario #3B (When SCell activation is completed and SCell is activated or after SCell activation is completed and SCell is activated) under AI 9.5.1 as the applicable scenario.

Proposal 2: Support to reuse the legacy RNTI, i.e. cellDTRX-RNTI, for DCI indication on SSB adaptation.

Proposal 3: For DCI format 2_9, support to introduce the following indications in each information block:
A common indication to indicate the periodicity of SSB transmission.
An extra indication to indicate the SSB periodicity for measurement.

Proposal 4: For the overlapping issue on PRACH adaptation in time domain, support one of the followings:
Clarify that it can up to gNB implementation to avoid the PRACH configuration that different UE have different understanding on the valid/invalid RO resource for Rel-19 additional PRACH resource.
Clarify that the legacy RO for valid RO determination on Rel-19 additional PRACH resource is all PRACH resources in SIB1/RRC configuration, regardless of whether a UE support the corresponding feature.

Proposal 5: For the DCI indication for PRACH adaptation, support:
Option 5 (From the first frame of the next SI modification period) for the reference point.
The validity time duration is a predefined value, e.g., one SI modification period.

Proposal 6: For Paging adaptation, support RAN1 to further discuss:
Whether the existing procedure (e.g., SI update and RRC re-configuration) on indication method is enough or enhancement is needed.
Whether a unified design is needed for indication on common signal adaptation.

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

Agenda Item:	9.5.3
Source:	Panasonic
Title:	Discussion on adaptation of common signal/channel transmission
Document for:	Discussion/Decision

Conclusion
There is no RAN1 consensus to support time domain adaptation for CD-SSB in Rel-19 for SCell

Agreement
For adaptation of SSB in time-domain, support the following to adapt SSB burst periodicity for an SCell
UE is configured with SSB burst periodicity using legacy signalling for the SCell 
UE is configured with X additional SSB burst periodicity for the SCell
FFS: Value of X
SSB occasions with larger periodicity are subset of the SSB occasions with shorter periodicity
FFS: Whether there is specification impact
Note: This does not impact the discussion on OD-SSB
For switching the periodicity, down-select between 
(MAC-CE) 
MAC-CE details for SSB burst periodicity adaptation is up to RAN2.
(DCI)
Alt 1-3: DCI based signalling is used

Agreement
For adaption of PRACH in time-domain, for a connected mode UE, support a 1-bit field in DCI 1_0 with C-RNTI used to trigger PRACH (i.e. PDCCH order) to indicate whether the additional PRACH resource(s) is available for the triggered PRACH. 
FFS: UE behaviour (e.g. applicable resources for PRACH mask index) when it is indicated of additional PRACH resource(s)
FFS: Details on how to reuse existing bit for the 1-bit indication

Agreement
For DCI-based adaptation for additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information for additional PRACH resource from a reference point and for a validity time duration
FFS: Validity time duration for availability is configured by higher layer signaling or predefined
FFS: Location of the reference point defined in the specification
FFS: Value/granularity of the validity time duration.
FFS: Whether DCI can be used to explicitly deactivate the additional PRACH resources

Agreement
For DCI-based adaptation for additional PRACH resources, support optional semi-static signalling of a single PRACH mask to identify the subset of the additional PRACH resources 
The mask is applicable at unit of 
Alt 1: PRACH association period 
Alt 2: PRACH association pattern period
Alt 3: SFN level
The PRACH association period is determined based on valid additional ROs only.
The mask is applied after valid RO determination and SSB-RO mapping.
Note: The existing behaviour in TS 38.213 "An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec." is not impacted due to application of the mask.
This is applicable at least for adaptation for DCI 1_0 with P-RNTI 
The DCI does not indicate PRACH mask selection
FFS: how the mask is identified 
Option 1: The PRACH mask is from a PRACH mask table
Pre-defined table with N=[4 or 8 or 16] rows
The semi-static signalling indicates a PRACH mask index 
Option 2: The PRACH mask is based on configuration parameters e.g. bitmap at SFN-level, periodic time domain window, …

Agreement
Separate configuration of Msg1-FDM for the additional PRACH resources at least for 4-step RACH is supported
UE is not expected to be configured such that there are more than 8 FDM-ed valid ROs (legacy + additional ROs)
FFS: When there is no configuration of Msg1-FDM
Separate configuration of number of SSB per RO is supported

Agreement
Study the following options for the reference point (for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF) for RRC idle/inactive mode UE and RRC connected mode UE, 
Option 1: SFN of the first PF from the next I-DRX cycle 
Option 2: SFN of the first PF from the current I-DRX cycle 
Option 3: From the first frame of the first PRACH association period after UE receives the DCI
Option 4: From the first frame of the current SI modification period 
Option 5: From the first frame of the next SI modification period

Agreement
For adaptation of SSB in time-domain, for adapting SSB burst periodicity for an SCell
Support group common DCI signalling for switching the SSB burst periodicity using DCI format 2_9 with [cellDTRX-RNTI]
FFS: which scenario(s) is this applicable for (e.g. as defined in 9.5.1)
Note: Above does not prevent RAN2 from designing a MAC CE based on OD-SSB feature and also used for SSB burst adaptation

3GPP TSG RAN WG1 #120bis Meeting		             		R1-2502200
Wuhan, China, April 7th – 11th, 2025	
Agenda item:	9.5.3
Source:	NEC
Title:	Discussion on adaptation of common signal/channel transmissions 
Document for:	Discussion 

Conclusion
From the discussion, we have the following proposals:
Proposal 1: Support up to two additional SSB burst periodicity configurations for the SCell for SSB adaptation.
Proposal 2: Support multiplexing of SSB adaptation indication and Rel-18 cell DTX/DRX indication within the DCI message scrambled with cellDTRX-RNTI.
Proposal 3: Following information is indicated to the UE using DCI format 2_9 for SSB adaptation,
Identity of the serving cell where SSB adaptation is being performed
Periodicity of the SSB bursts to be used for SSB transmission
Proposal 4: Support CSI report configuration associated with both of CD-SSB and NCD-SSB or one of CD-SSB and NCD-SSB based on configuration.
Observation 1: Availability of reserved bits within the DCI format 1_0 scrambled with P-RNTI ranges from 0 to 6 bits and depends on whether TRS availability indication is present within the DCI and the size of the TRS availability indication.
Proposal 5: RAN1 to discuss whether reserved bits of DCI 1_0 with P-RNTI can carry PRACH adaptation indication for all cases or another field of the DCI format should be used to carry the indication.
Proposal 6: Validity duration for availability of additional PRACH resources can be configured within the additional PRACH configuration.
Observation 2: High network energy savings can be achieved if DCI-based adaptation can control the activated PRACH resources depending on the cell load.
Proposal 7: Support gNB to configure one or more values of PRACH validity duration for additional PRACH resources. One of the PRACH validity duration is indicated by the DCI indication for PRACH adaptation which should be used by UE to determine the available PRACH resources.
Observation 3: Option-1 and Option-2 result in different reference points for different UEs for PRACH adaptation, while the network is expected to initiate PRACH adaptation for multiple UEs in the cell which may require a common reference point for different UEs. 
Proposal 8: For the reference point (for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF) for RRC idle/inactive mode UE and RRC connected mode UE, down select between the following options:
Option 3: From the first frame of the first PRACH association period after UE receives the DCI
Option 4: From the first frame of the current SI modification period 
Proposal 9: The granularity of the validity time duration is association period of the additional PRACH resources. 
Proposal 10: If UE receives a PDCCH order and the PDCCH order can indicate availability of additional PRACH resources, the UE selects the PRACH resources for PRACH transmission according to
If additional PRACH resources are not indicated as available, then UE selects the legacy PRACH resources for PRACH transmission
If additional PRACH resources are indicated as available, then UE selects the additional PRACH resources for PRACH transmission
Proposal 11: UE applies the values of Random Access Preamble index and PRACH Mask index to the PRACH resource type (additional vs legacy) selected by UE for PRACH transmission.
Proposal 12: One of the reserved bits of PDCCH order is used to indicate the availability of additional PRACH resources.

3GPP TSG-RAN WG1 Meeting #120bis	R1-2502231 
Wuhan, China, April 7 – 11, 2025
 
Agenda item:	9.5.3
Source:	Huawei, HiSilicon
Title:	On common channel/signal adaptation for eNES
Document for:	Discussion and Decision

Conclusions
The following observations and proposals are provided.
In TDD system, a valid PRACH Occasion for Type-1 RA needs to start at least a given number of symbols after a last SSB symbol on the PRACH slot, where the SSB position in time is given by SIB1 or RRCReconfiguration.
For Rel-19 UEs who only supports PRACH adaptation, if the additional RO is deactivated, the UE can only use RO configured by R15 prach-ConfigurationIndex.
For UEs who supports PRACH adaptation and another legacy feature e.g. RedCap etc., if the additional RO is deactivated,
if R17 prach-ConfigurationIndex for RedCap is not configured, the UE would only be able to use RO configured by R15 prach-ConfigurationIndex.
if R17 prach-ConfigurationIndex for RedCap is configured, the UE would be able to use RO configured by R17 prach-ConfigurationIndex for RedCap.
In legacy PRACH configuration, CB-PreamblesPerSSB is dependent on ssb-perRACH-Occasion, that is
For ssb-perRACH-Occasion <=1, the value range of CB-PreamblesPerSSB is 4 ~ 64
For ssb-perRACH-Occasion >1, the value range of CB-PreamblesPerSSB is 1 ~ or 4 ~ .
In legacy PRACH configuration, totalNumberOfRA-Preambles should be a multiple of the number of SSBs per RACH occasion. And numberOfRA-PreamblesGroupA should be consistent with ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

Support DCI format 2_9 with a new RNTI to indicate the SSB adaptation.
Each block in DCI format 2_9 contains bits corresponding to the index of the newly indicated SSB periodicity from the configured candidate SSB periodicities for one serving cell.
RAN1 takes Table 11.5-1 in TS 38.213 as the timeline for applying the SSB periodicity switching received in the DCI 2_9.
This group-common DCI signalling can be applied to all of the scenarios (defined in AI 9.5.1).
The PRACH occasion validation rules should be re-evaluated if SSB adaptation took place.
RAN1 to introduce indication on whether (periodic) CSI-RS resource is valid or not when it is overlapped with the adapted SSB in time domain.
One reserved bit in short message field is used for PRACH adaptation indication.
For PRACH adaptation indication, additionally support the use of DCI 2_7 for idle/inactive UEs by configuring a 1-bit field indication. 
For overlapping between additional RO and legacy valid RO, the legacy RO is the RO configured by a legacy prach-ConfigurationIndex where this legacy prach-ConfigurationIndex and R19 additional prach-ConfigurationIndex are associated with the same feature combination.
CB-PreamblesPerSSB, totalNumberOfRA-Preambles and numberOfRA-PreamblesGroupA can be configured separately for the additional PRACH resources to guarantee consistent setting as in legacy.
Validity time duration for availability is configured by higher layer signalling
For the reference point of the validity time duration, support option 4.
The mask is applicable at a unit of PRACH association period. 


References

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


Agenda item:	9.5.3
Source: 	Lenovo
Title: 	Adaptation of common signals and channels
Document for:	Discussion and decision

Conclusion
In summary, we have following observations and proposals:
Proposal 1: Consider multiple SSB transmissions (with different index) within the same slot of a half-frame to limit the time the gNB needs to transmit signals for enhanced energy saving.
Observation 1: Even though there is a mismatch between an actual SSB transmission periodicity and legacy UE’s assumption, legacy UEs would not select a SSB not being transmitted based on measurement. 
Proposal 2: Support SSB transmission with multiple SSB periodicities for multiple SSB subsets, each SSB periodicity applicable to each SSB subset. 
Proposal 3: Support one additional SSB burst periodicity configuration for an SCell, i.e. X=1. 
Proposal 4: New PRACH periodicities should be limited to {20 ms, 40 ms}.
Proposal 5: Use one of the currently “Reserved bits” in a PDCCH order DCI to carry the PRACH additional resource availability indication. Further discussion about application of the PRACH mask index for the additional resource can be left to RAN2.
Proposal 6: Support option 2, i.e., SFN of the first PF from the current I-DRX cycle, as the reference point for the availability information of additional PRACH resources indicated by paging DCI. 
Proposal 7: The additional PRACH resources triggered by paging DCI are valid in a time window. 
Proposal 8: For the case that legacy UEs and Rel-19 UEs co-ex in a same PO, RAN1 to decide whether legacy UEs and Rel-19 UEs follow the same (legacy) paging DCI, or separate DCIs are used for scheduling paging for legacy UEs and for Rel-19 UEs. 

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

Source:	OPPO
Title:	Discussion on adaptation of common signal/channel transmission
Agenda Item:	9.5.3
Document for:	Discussion and Decision

Conclusion
In this contribution, we provide our views on adaptation of common signal/channel transmission for Rel-19 NES. The following proposals are provided.
Observation 1: Different UE types monitors the paging DCI at different time locations. If the validity duration starts from the current I-DRX or current SI modification period, some UE may always benefit the additional PRACH occasions earlier than the others. This is not a fair solution. 
Observation 2: the PRACH adaptation should not be too dynamic and should at least be a duration of SI modification period. Otherwise, there may be a risk that the connected UE may miss this, and therefore, cannot benefit from the PRACH adaptation. 
Observation 3: when network has triggered PRACH adaptation via DCI, the network normally does not signal the paging DCI again to trigger another PRACH adaptation during the validity time duration.Otherwise, it would result in an endless adaptation. If the UE camps during the validity time duration, the UE is not able to know the additional PRACH occasions are made available. 
Observation 4: PRACH mask at SFN level will result in non-uniform beam distribution, which was not acceptable in Rel-19. PRACH mask at PRACH association period level seems feasible and straightforward. PRACH mask at the PRACH association pattern period level may need to introduce new dimension for the range in which the PRACH association pattern period(s) are masked.

Proposal 1: When a UE receives DCI indicating additional PRACH occasions are available, the additional PRACH occasions are available from the next SI modification period. 
Proposal 2: The validity time duration for DCI-based PRACH adaptation is at least SI modification period. 
Proposal 3: For the configured additional PRACH, the system information should also configure a default status and a default applicable validity time duration. 
Proposal 4:PRACH mask is at PRACH association period level. The mask includes all association periods, even indexed association periods, and odd indexed association periods
Proposal 5: Reuse the DCI Format 2_9 with cellDTRX-RNTI for DCI-based SSB adaptation for SCell.
Proposal 6: The bit location for SSB adaptation indication in DCI format 2_0 is 1-bit per cell and it is placed after DTX/DRX indication and CHO indication. The value ‘1’ indicates an configured SSB burst periodicity and the value ‘0’ indicates another configured SSB burst periodicity.
Proposal 7: The network should set a default periodicity for the SCell at the moment of SCell configuration to avoid mis-match of SSB burst periodicity determination by the UE.  

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

Agenda Item:	9.3.1.5
Source:	InterDigital Inc.
Title:	Discussion on adaptation of common signal/channel transmissions
Document for:	Discussion 

Conclusion
In this contribution, the following proposals are made:
Proposal 1: Support DCI format 2_9 for adapting the SSB burst periodicity in Scenario 2 and Scenario 3B  
Proposal 2: Support DCI format 2_9 with CRC scrambled by cellDTRX-RNTI for adapting the SSB burst periodicity
Proposal 3: Support configuring the UE with one additional value (X=1) to adapt the SSB burst periodicity for an SCell 
Proposal 4: Support one bit per information block (per SCell) in DCI format 2_9 for adapting the SSB burst periodicity
Proposal 5: Support configuring the same search space for DCI format 2_9 for adapting the SSB burst periodicity and cell DTX/DRX operation
Proposal 6: Support the first frame of the first PRACH association period after UE receives the DCI (Option 3) as the reference point for the availability of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF  
Proposal 7: Support configuring the UE with a PRACH mask index from the predefined legacy PRACH mask table (Option 1) for identifying a subset of additional PRACH resources 
Proposal 8: Support the PRACH association period (Alt 1) as the applicable unit of PRACH mask for indicating a subset of the additional PRACH resources 
Proposal 9: Support using the reserved bits within the Short Message (bits 5-8) of DCI format 1_0 with P-RNTI for indicating the availability of additional PRACH resources (Option 2)  
Appendix: Agreements on Adaptation of common signal/channel transmissions
RAN1#120 Agreements

RAN1#119 Agreements

RAN1#118bis Agreeements

RAN1#118 Agreeements

RAN1#117 Agreeements

RAN1#116bis Agreeements

RAN1#116 Agreeements

3GPP TSG RAN WG1 #120bis		R1-2502374
Wuhan, Hubei, China, April 7th – 11th, 2025
Agenda item:	9.5.3
Source:	Samsung
Title:	Adaptation of common signal/channel transmissions
Document for:	Discussion and decision

Conclusion
There is no RAN1 consensus to support time domain adaptation for CD-SSB in Rel-19 for SCell

Agreement
For adaptation of SSB in time-domain, support the following to adapt SSB burst periodicity for an SCell
UE is configured with SSB burst periodicity using legacy signalling for the SCell 
UE is configured with X additional SSB burst periodicity for the SCell
FFS: Value of X
SSB occasions with larger periodicity are subset of the SSB occasions with shorter periodicity
FFS: Whether there is specification impact
Note: This does not impact the discussion on OD-SSB
For switching the periodicity, down-select between 
(MAC-CE) 
MAC-CE details for SSB burst periodicity adaptation is up to RAN2.
(DCI)
Alt 1-3: DCI based signalling is used

Agreement
For adaption of PRACH in time-domain, for a connected mode UE, support a 1-bit field in DCI 1_0 with C-RNTI used to trigger PRACH (i.e. PDCCH order) to indicate whether the additional PRACH resource(s) is available for the triggered PRACH. 
FFS: UE behaviour (e.g. applicable resources for PRACH mask index) when it is indicated of additional PRACH resource(s)
FFS: Details on how to reuse existing bit for the 1-bit indication

Agreement
For DCI-based adaptation for additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information for additional PRACH resource from a reference point and for a validity time duration
FFS: Validity time duration for availability is configured by higher layer signaling or predefined
FFS: Location of the reference point defined in the specification
FFS: Value/granularity of the validity time duration.
FFS: Whether DCI can be used to explicitly deactivate the additional PRACH resources

Agreement
For DCI-based adaptation for additional PRACH resources, support optional semi-static signalling of a single PRACH mask to identify the subset of the additional PRACH resources 
The mask is applicable at unit of 
Alt 1: PRACH association period 
Alt 2: PRACH association pattern period
Alt 3: SFN level
The PRACH association period is determined based on valid additional ROs only.
The mask is applied after valid RO determination and SSB-RO mapping.
Note: The existing behaviour in TS 38.213 "An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec." is not impacted due to application of the mask.
This is applicable at least for adaptation for DCI 1_0 with P-RNTI 
The DCI does not indicate PRACH mask selection
FFS: how the mask is identified 
Option 1: The PRACH mask is from a PRACH mask table
Pre-defined table with N=[4 or 8 or 16] rows
The semi-static signalling indicates a PRACH mask index 
Option 2: The PRACH mask is based on configuration parameters e.g. bitmap at SFN-level, periodic time domain window, …

Agreement
Separate configuration of Msg1-FDM for the additional PRACH resources at least for 4-step RACH is supported
UE is not expected to be configured such that there are more than 8 FDM-ed valid ROs (legacy + additional ROs)
FFS: When there is no configuration of Msg1-FDM
Separate configuration of number of SSB per RO is supported

Agreement
Study the following options for the reference point (for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF) for RRC idle/inactive mode UE and RRC connected mode UE, 
Option 1: SFN of the first PF from the next I-DRX cycle 
Option 2: SFN of the first PF from the current I-DRX cycle 
Option 3: From the first frame of the first PRACH association period after UE receives the DCI
Option 4: From the first frame of the current SI modification period 
Option 5: From the first frame of the next SI modification period

Agreement
For adaptation of SSB in time-domain, for adapting SSB burst periodicity for an SCell
Support group common DCI signalling for switching the SSB burst periodicity using DCI format 2_9 with [cellDTRX-RNTI]
FFS: which scenario(s) is this applicable for (e.g. as defined in 9.5.1)
Note: Above does not prevent RAN2 from designing a MAC CE based on OD-SSB feature and also used for SSB burst adaptation

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

Agenda item: 	9.5.3
Source: 	Xiaomi
Title:	Discussion on adaptation of common signal and channel transmissions
Document for:	Decision

1 

Conclusion
Based on the discussion and analyses in section 2, we have the following observations and proposals:

Observations:
Observation 1: Adaptation of PRACH may bring significant influence on UE behavior associated with RACH procedure.
Observation 2: The impacts on legacy UE due to adaptation of common signal and channel transmissions depend on mechanism of realizing those adaptation.

Proposals:
Proposal 1: For adaptation of SSB in time domain, the mechanisms captured in current specification are applied to the following aspects:
The impact on DL RE mapping
The impact on UL transmission
The impact on initial access
UE’s assumption on SSB pattern
Proposal 2: For DCI format 2_9 used to indicate SSB burst periodicity adaptation, a new RNTI value other than cellDTRX-RNTI is applied.
Proposal 3: For adaptation of SSB in time-domain, it is applicable to an activated SCell.
Proposal 4: The adaptation of PRACH can be applied to CBRA and CFRA, including 4-step RACH and 2-step RACH.
Proposal 5: For the case same PRACH configuration index for additional and legacy PRACH resources, the following option 1-2a and option 1-4 can be further considered:
Opt 1-2a: up to N1 additional value(s) of (x, y) 
FFS: value of N1(>=1)
Opt 1-4: 
up to N4_1 additional timing offset(s) at frame-level
up to N4_2 additional timing offset(s) at slot-level
FFS: values of N4_1(>=1) and N4_2(>=1)
Proposal 6: For the case different PRACH configuration index for additional and legacy PRACH resources, the following option 1-5 is adopted:
Opt 1-5: No additional mechanism is selected.
Proposal 7: Only DCI format 1_0 with CRC scrambled by P-RNTI is used to carry PRACH adaptation indication.
Proposal 8: For DCI-based adaptation to indicate whether the additional PRACH resources provided by semi-static signalling are available or not, 1 bit in DCI format 1_0 with CRC scrambled by P-RNTI.
‘0’ indicates default PRACH resources are available
‘1’ indicates additional PRACH resources are available
Proposal 9: For DCI-based adaptation for additional PRACH resources, use reserved bits in the DCI format 1_0 with CRC scrambled by P-RNTI.
Proposal 10: If the availability information for additional PRACH resource is introduced, the following should be adopted:
Validity time duration for availability is predefined.
The reference time point is the first frame of the first PRACH association period after UE receives the DCI.
Proposal 11: The impacts on legacy UE due to adaptation of common signal and channel transmissions can be further studied after RAN1 achieves big picture on NES technique.
Proposal 12: Further study the inter-action among different NES technologies.

4 

3GPP TSG RAN WG1 #120-bis			R1-2502470
Wuhan, China, April 17th – 21, 2025
Source:           Tejas Networks Ltd
Title:                    Adaptation of common signal/channel transmissions for network energy
                         saving
Agenda item:	 9.5.3	
Document for: Discussion and Decision

Conclusions

Value of X depend on the legacy SSB burst periodicity.

If legacy SSB burst periodicity is 160 msec, then X is 5, if legacy SSB burst periodicity is 80 msec then value of X is 4, if legacy SSB burst periodicity is 40 msec then value of X is 3, and so on. 
FFS: Indication of additional SSB burst periodicity value to UE among the configured additional SSB periodicity values.

Support DCI based adaptation of SSB’s for scenario #3A and scenario #3B defined in agenda item 9.5.1.

Adaptation based on skipping/transmitting some SSB bursts non-uniformly with a single SSB configuration should be prioritized, as few SSBs (Synchronization Signal Block) (Synchronization Signal Block) are required for UE synchronization before decoding paging information.  

Transmit non-uniform SSB burst across time, before paging occasion, to assist idle/inactive UE’s for obtaining synchronization with the base station and to decode paging information.

For UEs in idle/ inactive mode, If the SSB burst periodicity value is changing from a low value ( ) to high value () then, SSBs are transmitted with a varying SSB burst periodicity pattern (Geometric progression sum pattern) during the SSB adaptation time. After completion of SSB adaptation time, the base station will transmit SSB with a new SSB burst periodicity  uniformly. 

Support explicit indication for deactivation of additional PRACH resources.

The reference point for the UE to start using the additional PRACH resources can be the last symbol of the PDCCH.
The time gap between reference point and point where UE will start using the additional PRACH resources can be predefined in the standard considering the UE processing time for decoding PDCCH and UE processing time for preparing PRACH.

Support indication of the PRACH mask based on configuration. 

A default value (considering that maximum number of FDM RACH resources not exceeding 8) can be considered when Msg1-FDM is not configured.

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

Agenda Item:	9.5.3
Source: 	LG Electronics
Title: 	Adaptation of common signal/channel transmissions
Document for:	Discussion and decision

Conclusions
Proposal #1: When DCI indicates SSB adaptation from periodicity #1 to periodicity #2, consider the following options for determining the SSB time domain location for SSB with periodicity #2.
Option 1: UE expects that SSB with periodicity #2 is transmitted at the earliest of the candidate occasions for SSB with periodicity #1 after the processing time for DCI.
Option 2: UE expects that SSB with periodicity #2 is transmitted from time instance A. Time instance A is the first “possible” SSB occasion with periodicity #2 which is at least after the processing time of DCI. The time domain location such as SFN offset and half frame index of “possible” SSB with periodicity #2 should be known to UE before the UE receives DCI.
Proposal #2: The DCI contents for adaptation of SSB in time-domain can be configured that the information block for switching SSB periodicity indication is configured for each cell and the starting position for monitoring the associated information blocks can be configured by the RRC.
Proposal #3: Discuss how UE performs RACH occasion validation, PDCCH monitoring, and DL/UL signals/channels reception/transmission, if the SSB periodicity can be adapted.
Proposal #4: Support Alt 1 (PRACH association period) or Alt 2 (PRACH association pattern period) to identify the subset of the additional PRACH resources.
Proposal #5: Regarding how the mask is identified,
If option 1 is adopted, the PRACH mask index can be indicated to identify the subset of the additional PRACH resources from a predefined table with N rows where each row in the table can be configured in PRACH association period or PRACH association pattern period units. 
If Option 2 is adopted, a bitmap can be configured to the UE where each bit of the bitmap can correspond to PRACH association period or PRACH association pattern period. One or multiple PRACH association period(s) or PRACH association pattern period(s) is indicated to identify the subset of the additional PRACH resources by the bitmap.
Proposal #6: For additional PRACH resources adaptation indication, Option 1 using reserved bits of DCI format 1_0 scrambled with P-RNTI is supported, and the following two alternatives can be considered:
Alt 1: Use the reserved bits with consideration of TRS availability indication bit(s).
Alt 2: Use the short message 8 bits by setting the short message indicator to ‘01’, or one or more of FDRA/TDRA/VRB-to-PRB mapping/MCS/TB scaling field(s) by setting the short message indicator to ‘10’.
Proposal #7: For multi-cell scenario (e.g., CA/DC), the following options can be considered to indicate additional PRACH resource adaptation in connected mode UEs:
Option 1: A DCI format 1_0 scrambled by P-RNTI of PCell can be used to additional PRACH resource adaptation for other cells (e.g., PScell/Scell). In this case, more than 1 bit payload can be required for the DCI.
Option 2: If the additional PRACH resource adaptation is indicated by DCI format 1_0 scrambled by P-RNTI in the PCell, UE can be interpret that the adaptation is also applied for PSCell/Scell.
Proposal #8: Support Option 3 (From the first frame of the first PRACH association period after UE receives the DCI) for the reference point for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF for RRC idle/inactive mode UE and RRC connected mode UE.
Proposal #9: Consider extending the ending point of validity time duration to be aligned for all UEs (idle/inactive and connected mode UEs).
Proposal #10: When PRACH is triggered with DCI format 1_0 with C-RNTI and additional PRACH resource(s) are indicated to be available, the following options can be considered to select RO
Option 1: The UE select the closest RO (legacy RO or additional RO) after applying PRACH mask index to transmit PRACH after receiving the DCI.
Option 2: If PRACH configuration index for the additional PRACH resources is same as the legacy PRACH resources, the UE select the closest RO (legacy RO or additional RO) after applying PRACH mask index to transmit PRACH after receiving the DCI. Otherwise (i.e., different PRACH configuration index) the UE will prioritize select the additional RO.
Proposal #11: To address the issue that PEI-enabled NES UEs require to monitor both PEI and PO to check whether additional ROs are activated or not, consider the following options:
Option 1: Support indicating the additional PRACH resource adaptation using the DCI format scrambled by PEI-RNTI
Option 2: Introduce 1-bit flag in DCI format scrambled with PEI-RNTI to indicate PO monitoring for the additional PRACH resource adaptation
Proposal#12: When additional PRACH resources (i.e., NES ROs) are configured for the NES-capable UE,
Consider the following options for initial PRACH transmission attempt in one random access procedure:
Option 1: Always select NES ROs as a high priority
Option 2: Select ROs based on the per-configured priority between default ROs and NES ROs 
Consider the following alternatives for PRACH transmission re-attempt in one random access procedure
Alt 1: Always use ROs of the same type (i.e., default RO or NES RO) as the earlier PRACH transmission for the rest of the random access procedure
Alt 2: First use ROs of the same type as the earlier PRACH transmission for a certain number of times, and if certain conditions are met, then use ROs of the other type for the rest of the random access procedure
FFS: how to handle the case when first used RO is no longer available at the time the UE attempts to retransmit PRACH
Proposal #13: PEI bits for legacy POs and PEI bits for additional Rel-19 POs are not multiplexed in the legacy PEI DCI (i.e., DCI format 2_7).
Proposal #14: For NES PEI DCI, introduce a new RNTI value for NES PEI DCI (e.g., NES-PEI-RNTI = FFFA(16)).
Existing DCI format 2_7 can be reused.
Proposal #15: If a PO configured for NES UEs is overlapped with that configured for legacy UEs, the UE-IDs to be assigned to the PO should be kept the same regardless of legacy UEs and NES UEs.
Proposal #16: Discuss whether/how to handle RACH congestion among NES UEs when it occurs due to consecutive POs.

3GPP TSG RAN WG1 #120bis                                       R1-2502515
Wuhan, China, April 7th – 11th, 2025
Source: 	ETRI
Title:	Adaptation of common signal/channel transmissions
Agenda Item:	9.5.3   Adaptation of common signal/channel transmissions
Document for:	Discussion/Decision

Conclusion
In this contribution, we discuss our view on potential enhancements for time domain adaptation of SSB, PRACH, and paging. The following proposals are noted.
Proposal 1: For further progress and drafting the Rel-19 specification, clarify the meaning of CD-SSB and NCD-SSB on SCell.
Proposal 2: For SSB adaptation on SCell, for each SSB, UE can be configured with up to one additional SSB burst periodicity value.
Proposal 3: For SSB adaptation via DCI format 2_9, introducing a new RNTI is slightly preferred.
Proposal 4: DCI format 2_9 can indicate periodicities of multiple SSBs for each serving cell.
Proposal 5: SSB adaptation for SCell via DCI format 2_9 applies for both
SSB associated with the current active DL BWP, and
SSB(s) not associated with DL BWP(s) other than the current active DL BWP.
Proposal 6: Extend the RAN1#117 and #118 agreements on the SSB-RO mapping rules in the same manner to cover the case where additional PRACH resources and legacy PRACH resources overlap in both time and frequency.
Proposal 7: Allow UE to switch PRACH resources between legacy PRACH resources and additional PRACH resources across the initial PRACH transmission and its retransmission.
Proposal 8: The validity time duration spans one or multiple PRACH association periods, with a granularity of a PRACH association period.
Proposal 9: The validity time duration as the number of PRACH association periods is configured by gNB.
Proposal 10: The validity time duration starts at the first PRACH association period after UE receives the DCI possibly with some time gap for processing (Option 3).
Proposal 11: Explicit deactivation indication for additional PRACH resources by DCI 1_0 with P-RNTI is not supported.
Proposal 12: The size of the DCI field for availability indication of additional PRACH resources is 1 bit.
Proposal 13: If the PRACH adaptation is supported together with the TRS availability indication, bits 5-8 within the Short Message field is used for the availability indication of additional PRACH resources.
Proposal 14: Revise the previous agreement regarding the PRACH adaptation based on PDCCH order as follows (unless the meaning of the previous wording is clarified):
Agreement
For adaption of PRACH in time-domain, for a connected mode UE, support a 1-bit field in DCI 1_0 with C-RNTI used to trigger PRACH (i.e. PDCCH order) to indicate to use the legacy PRACH resources or the additional PRACH resources whether the additional PRACH resource(s) is available for the triggered PRACH.
Proposal 15: For a case where legacy ROs and additional ROs are FDM-ed while occupying the same set of symbols, modify the RA-RNTI equation based on one of the following options:
Option 1: Reinterpret f_id such that it is mapped over legacy ROs first, followed by additional ROs.
Option 2: Include the PRACH configuration ID in the RA-RNTI equation.

3GPP TSG RAN WG1 #120bis		                        R1-2502544
Wuhan, China, April 7th-11th, 2025
Source: 	Transsion Holdings
Title:	Discussion on adaptive transmission of common signal or common channel
Agenda item:	9.5.3
Document for:	Discussion & Decision

Conclusions
In this contribution, some considerations on adaptation of common signal/channel are discussed, and the following proposals are made.
Proposal 1  Switching the SSB burst periodicity using DCI format 2_9 can be applied to all scenarios of AI 9.5.1.
Proposal 2 The payload size of DCI format 1_0 with CRC scrambled by P-RNTI depends on the number of adaptive PRACH resources. 
Proposal 3 Use Bits 5-8 within the Short Message of DCI format 1_0 with CRC scrambled by P-RNTI to carry the adaptation indication. 
Proposal 4 DCI 1_0 with P-RNTI can be used to explicitly deactivate the additional PRACH resources. 
Proposal 5 Using the slot of the first valid physical random access channel occasion in the first PRACH associated period after the UE receives the DCI as the reference point as the reference point. 
Proposal 6  The mask is applicable at unit of PRACH association period. 

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

Agenda item: 	9.5.3
Source: 	Apple
Title:	On adaptation of common signal/channel for NES enhancements
Document for:	Discussion/Decision
 

Conclusion
In this contribution, we discussed on the signaling and adaptation mechanisms for common SSB, PRACH and Paging for Rel-19 NES enhancements, the following proposal are made: 
SSB adaptation scenario
Proposal 1: SSB adaptation can be applied to NCD-SSBs on SCell without OD-SSB feature, i.e. applied to SCell without OD-SSB configuration. 
Proposal 2: SSB adaptation can be applied to AO-SSB for SCell with OD-SSB configuration but OD-SSB is not activated/transmitted. 

SSB adaptation signaling
Proposal 3: A new RNTI is introduced for scrambling DCI format 2_9. 
Proposal 4: Offset of SSB within the periodicity should be also configured with the adapted SSB periodicity.
Proposal 5: UE assumes SSB is transmitted with the adapted periodicity and offset after a sufficient time gap after the indication signaling. 
Proposal 6: The time gap between UE receiving the indication of SSB adaptation and UE assuming the SSB periodicity change shall be above certain value to give UE sufficient preparation time to implement new RRM behavior on new SSB periodicity.

PRACH adaptation
Legacy RO
Proposal 7: Legacy PRACH resource is the one that is configured in the same RACH-ConfigCommon as the additional PRACH resources. 
Proposal 8: In case of shared RO used for 4-step and 2-step RACH, 2-step RACH can also be performed on the additional PRACH resource if configured and indicated as available. 
Proposal 9: At least for the feature combinations configured by featureCombinationPreambleList-r17, the additional PRACH resources configured in the same RACH-ConfigCommon can be also used for those feature combinations.

Single PRACH mask
Proposal 10: A single PRACH mask in PRACH association period level can be configured in SIB1.
Proposal 11: Consider using Table 3 to configure the PRACH mask in SIB1, where the single PRACH mask can be indicated from the chosen table, and value M can be the number of association periods within a pattern period, or can be explicitly signaled by the NW.  
Table3 PRACH association period mask Example 3 with 3bits Mask index

Validity duration and reference point 
Proposal 12: UE assumes the additional PRACH resources are available from the first PRACH association period after UE receives the DCI. 
Proposal 13: Support Option 1 or Option 2 as the reference point for the validity duration and the validity duration is in units of paging cycles. 

PRACH adaptation signaling 
Proposal 14: For DCI-based adaptation for additional PRACH resources, support option 2: Use Bits 5-8 within the Short Message (from upper layers)
Proposal 15: For DCI payload size, select from the following options: 
Option 1: when the PRACH mask is configured in SIB1/RRC, one bit is used to indicated whether the mask configured in the higher layer signaling is activated or not. 
Option 2: 2bits to indicate whether the whole additional RPACH resource or the configured mask is activated or not. 
Proposal 16: Regarding how UE selects between the additional and legacy PRACH resources for transmission, consider the following options: 
Option 1: UE always selects the additional PRACH resources for transmission
Option 2: Up to UE implementation, to select between legacy or additional PRACH resources whichever comes first 
Option 3: 1 bit indication is introduced to indicate between Option 1 and Option 2. 

RA-RNTI calculation
Proposal 17: For RA-RNTI ambiguity issue, consider the following alternatives: 
Alt 1: Introduce a k_offset for the additional PRACH resources, i.e. RA-RNTI = 1 + s_id + 14 x t_id + 14 x 80 x f_id + 14 x 80 x8 x ul_carrier_id + 14 x 80x 8 x 2 x k_offset 
Alt 2: f_id for the additional PRACH resources is the index of the PRACH occasion in the frequency domain plus the number of FDMed legacy ROs.
FFS whether this applies only to the additional PRACH resources overlapped in time domain with legacy PRACH resources or applied to all additional PRACH resources. 

 

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

Agenda item:		9.5.3
Title:						Adaptation of Common Signals and Channels for NES
Source:				Fraunhofer IIS, Fraunhofer HHI
Document for:		Discussion

Conclusions
In this contribution, we discussed some aspects of Common signals adaptation for NES. The following observations and proposals have been made:

Proposal 1: RAN1 to specify the group common signaling for switching SSB periodicity with minimal changes to the DCI format 2_9, e.g. adding one bit per information block for a SCell.
Proposal 2: The group common signaling using DCI format 2_9 indicates the effective switching of the SSB periodicity to Rel-19 UEs, i.e. enabling or disabling the of complementary SSBs.

3GPP TSG RAN WG1 #120bis	R1-2502682
Wuhan, China, April 7th – 11st, 2025
Source:	Sharp
Title:	Discussion on adaptation of common signal/channel transmissions
Agenda Item:	9.5.3
Document for:	Discussion and Decision

Conclusion
In this contribution, we have the following observations and proposals:
Observation 1: For unit of the mask identifies the subset of the additional PRACH resources, there is no benefit to have narrower unit of the mask than association period (i.e. SFN level) since masking within an association period breaks fairness of the number of ROs between transmitted SSBs.
Proposal 1: For unit of the mask identifies the subset of the additional PRACH resources, support Alt 1 (PRACH association period).
Proposal 2: Regarding how the mask is identified, support Option 2. Specifically support utilizing a pre-defined table, configurable X for the number of association periods, and mask index.
Proposal 3: We propose following for 1 bit-indication on the CFRA by PDCCH order:
When NW indicates to the UE to use additional ROs, it sets the 1-bit indication to 1, and the UE determines the applicable ROs for sending PRACH by applying the mask index only to the additional ROs.
When NW indicates to the UE to use legacy ROs, it sets the 1-bit indication to 0, and the UE determines the applicable ROs for sending PRACH by applying the mask index only to the legacy ROs. 

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

Agenda Item:	9.5.3
Source:	HONOR
Title:	Discussion on adaptation of common signal/channel transmission
Document for:	Discussion and Decision

Conclusions
In this contribution, we discuss on adaptation of common signal/channel transmission with the following observations and proposals.
Observation 1: Regarding the adaptation of SSB in the time-domain, it can be applied to at least the following two scenarios: one is to dynamically adjust the SSB periodicity of SCell; the other is to dynamically adjust the periodicity of always-on SSB in conjunction with OD-SSB.

Proposal 1: UE is configured with 4 additional SSB burst periodicity for the SCell.
Proposal 2: The frame offset and the position of the first and second half-frames for large periodicity SSB occasions and small periodicity SSB occasions are the same.
Proposal 3: Support the validity time duration to be configured by the network side.
Proposal 4: Support option 3 for the reference point of additional PRACH resource availability.
Proposal 5: DCI indication for the deactivation of additional PRACH resources is not supported.
Proposal 6: Support option 1 for mask identification.
Proposal 7: Use reserved bits to indicate the availability of additional PRACH resources.

3GPP TSG RAN WG1 #120bis			           R1-250xxxx
Wuhan, CN, Apr 7th – Apr 11th, 2025
Agenda Item: 9.5.3
Source: MediaTek Inc.
Title: Adaptation of common signal/channel transmissions
Document for: Discussion and decision 

Conclusion
Observation 1: Most of the channels affected by cell DTX are related to data scheduling. It's unclear why the functions of SSB adaptation and cell DTX need to be combined.

Observation 2: If the DCI is scrambled by cellDTRX-RNTI, the network must transmit the information of cell DTRX and SSB adaptation simultaneously.

Proposal 1:  For SSB adaptation in the time domain, support a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType = common for DCI format with CRC scrambled by a new RNTI.

Proposal 2: The updated SSB periodicity should maintain the same SMTC offset as the legacy SSB configuration.
FFS: The length of application delay.

Figure 2. Maintain the same offset after updating the periodicity of SSB by DCI.

Proposal 3: a 3-bit indicator is used for updating the SSB period. This indicator allows for the selection of multiple predefined SSB periodicity options.
For example, an indicator value of ‘001’ could correspond to an update of the SSB period (ssb-periodicityServingCell) to a periodicity of 5ms (ms5).

Proposal 4: Introduce a RRC parameter SSBPeriodicityUpdating. If it is activated, the UE update the information of SSB periodicity after a configured application delay.

Observation 3: If additional RO and legacy RO follow the SSB mapping order simultaneously, there could be a conflict where different SSB indexes are mapped to the same RO as illustrated in Figure 3.


Figure 3. Additional RO and legacy RO follow the SSB mapping order simultaneously.


Proposal 5: Legacy and additional PRACH occasions should be mapped to SSB index independently as illustrated in Figure 4.


Figure 4. Additional RO and legacy RO are mapped to SSB index independently.

Proposal 6: Support Option1 to carry the updated information in paging DCI.
Option 1: Use reserved bits in the DCI format.

Proposal 7: Support a 1-bit indication to switch on/off the additional RO in paging DCI.

Observation 4: A PDCCH order triggers a RACH procedure initiated by the BS to re-sync with a specific UE.

Proposal 8: Using one reserved bit in PDCCH order to indicate to a connected mode UE the current status of the additional RO, while the status information should be aligned with the one indicated in the paging DCI. 


Observation 5: If Rel-19 idle and connected mode configurations differ, the network must follow the more frequent sleep time, reducing power savings and complicating RO availability maintenance.

Proposal 9: At least for contention-base RACH, maintain the RO status the same across all RRC states.

Observation 6: UEs in a cell may be configured with different periodicities of I-DRX cycle, making it difficult to maintain the availability of RO if either Option 1 or Option 2 is supported.

Observation 7: For Option 3 and Option 4, the information available before receiving the indication will be useless for the UE. Additionally, UEs will monitor PO at different times. To align the knowledge of all UEs in the same cell, the gNB must maintain the RO status until the next SI update time or RACH association period, as illustrated in Figure 5.



Figure 5. The reference point is set before the UE receives the RO adaptation signal.

Proposal 10: Support Option5 as the reference time for updating PRACH adaptation.
Option 5: From the first frame of the next SI modification period

Proposal 11: Support the validity duration of PRACH adaptation is configured by higher layer signaling, with the modification period as the unit.

Proposal 12: Support the additional RO is configured to be switched off by default.

Proposal 13: If the additional RO can be configured to default on or off, a 1-bit indication can be used to signal turning it off.

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

Source:	NTT DOCOMO, INC.
Title:	Discussion on adaptation of common signal/channel transmissions
Agenda Item:	9.5.3
Document for: 	Discussion and Decision

Conclusion
In this contribution, we provided the following observations and proposals of adaptation of common signal/channel transmissions for network energy saving.

Proposal 1:
For the adaptation of SSB burst periodicity in time-domain
Support one additional SSB burst periodicity is configured by RRC and availability is indicated through DCI.
No specification impact is expected by introducing the restriction with regard to the following statement.
“SSB occasions with larger periodicity are subset of the SSB occasions with shorter periodicity”
Proposal 2:
In terms of SSB adaptation using group-common DCI,
Support DCI format 2_9 with CRC scrambled by RRC-configurable new-RNTI
It can be possible that setting new-RNTI to be the same value as cellDTRX-RNTI does not increase the burden on the blind search for UEs. 
Proposal 3:
In terms of SSB adaptation using group-common DCI, 
We do not support on extending current specification to introduce new search space for different RNTI within the same DCI format. 
Proposal 4:
For the monitoring behavior of SSB adaptation indication, 
Support of UE monitoring the DCI only on active time when Cell-DTX and/or UE C-DRX is configured and activated (same behavior as to the case of cellDTRX-RNTI).
Proposal 5:
For the indication mechanism of SSB adaptation,
support 1 bit indication to indicate whether configured SSB adapted periodicity is applied or not.
Proposal 6:
For the handling overlapped resources between legacy and additional PRACH resources
We prefer to support to have a UE invalidate additional ROs overlapping with all the legacy ROs supported by the UE
We do not support on adapting PRACH resources except for common PRACH resources for 4-step RACH.
Proposal 7:
When there is no configuration of Msg1-FDM, UE expects that FDM value is 1. 
Proposal 8:
For DCI format 1_0 with CRC scrambled by C-RNTI
Support additional PRACH resource availability is indicated only for CBRA (ra-preambleindex = 0)
The mask [table/configuration] to apply for additional PRACH resources is the same as discussed for the case of P-RNTI and the mask is semi-statically configured.
Proposal 9:
For DCI format 1_0 with CRC scrambled by P-RNTI,
Use reserved bit of short message field to deliver PRACH adaptation
Proposal 10:
For the determination of reference point,
Support option 3 with some modification; from the first frame of the first PRACH association period after UE finishes decoding DCI upon reception of the DCI.
Not support providing additional offset.
For the determination of validity duration,
Support validity duration to be integer multiple of defaultpagingcycle
Proposal 11:
For the determination of the mask granularity, 
We support Alt. 2 (PRACH association pattern period level)
For the identification of the mask
Support option 2. 

3GPP TSG-RAN WG1 Meeting #120bis	 R1-2502797
Wuhan, China, April 7-11, 2025
Source:	KDDI Corporation
Title:	Discussion on common signal adaptation
Tdoc Type:	Discussion
Agenda Item:	9.5.3	
Document for:  Discussion 
Release:       Rel-19
1	

Conclusion
We make the following observations and proposals:
Proposal 1: up to 6 additional SSB burst periodicity for Scell can be configured to the UE.
Proposal 2:RAN1 to discuss dynamic adaptation of SSB index
Proposal 3: The legacy PRACH mask index can be applied to the additional PRACH resources.
Proposal 4: RAN1 to discuss to use either a dedicated random access preamble index, or a reserved bit to indicate the availability of the additional PRACH resources.
Proposal 5: Reference point application approach can be considered using the SI modification approach, new method is not needed unless there is significant specification impact.
Proposal 6: DCI-based PRACH adaptation deactivation is supported.
Proposal 7: UE rely on the msg1-FMD for legacy PRACH resource configuration when it is not configured for the additional PRACH resource.
Proposal 8: Reuse the legacy PRACH mask table for the additional PRACH resources.

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

Agenda Item:	9.5.3
Source:	Ericsson
Title:	Adaptation of common signal/channel transmissions for NES
Document for:	Discussion 

Conclusion
In previous sections, the following observations were made: 
Observation 1	Supporting additional RACH resources for 2-step RA requires provisioning of additional PUSCH resources associated with the additional RACH resources.
Observation 2	Separate configuration of additional RACH resources for on-demand OSI is not required.
Observation 3	For DCI-based adaptation indication via DCI 1_0 with P-RNTI, up to six reserved bits are available for repurposing for the indication (including potential sharing with TRS availability indication).
Observation 4	The reference point related to the SI modification period or DRX cycle may result in a large gap before activation, which offsets the benefits of dynamic adaptation.
Observation 5	Additional DCI based mechanism to explicitly deactivate PRACH resources is not needed, as a timer-based mechanism is already supported.
Observation 6	Providing the adaptation indication in DCI 1_0 with SI-RNTI and P-RNTI allows UE reselecting/camping on a cell to obtain the indication in a quicker fashion.
Observation 7	The RA-RNTI ambiguity issue occurs only for Case 2. There is no ambiguity for Case 1 and Case 3 (i.e. when additional and legacy RACH resources do not overlap in time).
Observation 8	RAN2 has already agreed that Paging adaptations are configured semi-statically and updated via system information update notification.
Observation 9	Based on the RAN2 agreement that the maximum Ns is 8, the legacy DCI 2_7 structure, which also supports Ns = 8, can be reused for Rel-19 PEI.
Observation 10	Rel-19 PEI independently addresses the additional Rel-19 POs, including those overlapping with legacy POs. Rel-19 UEs only need to decode the Rel-19 PEI, even when some Rel-19 POs overlap with legacy POs.
Observation 11	Separation of additional Rel-19 PEI transmission occasions from legacy ones can be achieved through different PEI-PO-Offset and/or pei-SearchSpace configurations, including firstPDCCH-MonitoringOccasionOfPEI-O.
Observation 12	Multiplexing legacy and Rel-19 PEIs conserves network energy by eliminating unnecessary transmissions. When feasible, legacy and Rel-19 PEI bits can be combined in the same DCI 2_7, without impacting legacy UEs.
Observation 13	Multiplexing legacy and Rel-19 PEIs through network implementation, without introducing additional parameters, requires CN subgrouping and the same po-NumPerPEI, which may limit flexibility.
Observation 14	By introducing one or two parameters, flexible multiplexing of legacy and Rel-19 PEIs can be achieved using the legacy DCI 2_7 reserved bits, without enforcing CN subgrouping or requiring the same po-NumPerPEI for legacy and/or Rel-19 UEs.

Based on the discussion in the previous sections we propose the following:
Proposal 1	For adaptation of SSB in time-domain, support up to X=3 (i.e. 1<=X<=3) additional SSB burst periodicities for an SCell.
Proposal 2	For adaptation of SSB in time-domain, support DCI format 2_9 with a new RNTI for switching the SSB burst periodicity
	The new RNTI is configured by higher layer signaling.
Proposal 3	For adaptation of SSB in time-domain, support up to 2-bits of an information block within DCI format 2_9 for indicating the applicable SSB burst periodicity for an SCell
	the starting position of the information block associated with the SCell is configured by higher layer signaling.
	the size of the information block associated with the SCell is given by ceil(log2(X+1)), where X <=3 is the number of additional SSB periodicities configured for the SCell.
Proposal 4	For adaptation of SSB in time-domain, following are explicitly configured by higher layer signaling for the DCI format 2_9 for switching the SSB burst periodicity of SCell(s).
	Search space
	DCI payload size
Proposal 5	For adaptation of SSB in time-domain, the DCI format 2_9 for switching the SSB burst periodicity of SCell(s) is carried only on the primary cell.
Proposal 6	For adaptation of SSB in time-domain, the existing Rel-18 DCI 2_9 time gap values and timeline are reused for applying the DCI 2_9 with new RNTI indicating SSB burst periodicity adaptation.
Proposal 7	For the additional PRACH resources determination, the RACH resources according to the following IEs are considered as legacy RO.
	rach-ConfigCommon
	msgA-ConfigCommon-r16
	additionalRACH-ConfigList-r17
Proposal 8	For the additional PRACH resources at least for 4-step RACH, separate configuration of CB preambles per SSB is also supported.
	Note: the number of SSB per RO and CB preambles per SSB can together be jointly indicated using legacy IE structure (ssb-perRACH-OccasionAndCB-PreamblesPerSSB) in addl-RACH-Config-Dyn.
Proposal 9	For the additional PRACH resources, the framework of existing parameters (such as from rachConfig-Common and rachConfig-Generic) is reused when the corresponding parameter (e.g. msg1-FDM, etc) is not configured separately for the additional PRACH resources in addl-RACH-Config-Dyn.
Proposal 10	For adaption of PRACH in time-domain, the DCI field and location used for adaptation indication of additional PRACH resources in DCI 1_0 with P-RNTI is explicitly configured by higher layer signalling (i.e. based on Option 3 from RAN1#119 working assumption)
	Use reserved bits in the DCI format
	Note: the sum of the number of bits for this DCI field and the number for TRS bits (if configured) should not exceed 6.
	Use Bits 5-8 within the Short Message (from upper layers)
Proposal 11	For adaption of PRACH in time-domain, for the reference point for applying the availability indication in DCI 1_0 with P-RNTI, support Option 3, i.e. from the first frame of the first PRACH association period after UE receives the DCI.
Proposal 12	For adaption of PRACH in time-domain, the value of validity time duration for the availability indication in DCI 1_0 with P-RNTI is configured via higher layer signaling.
	Granularity of validity time duration is integer multiples of PRACH association period (e.g. (1,2,4,8, 16, 32, 64, 128, 256, 512, 768, 1024, 1536, 2048) x PRACH association period}.
Proposal 13	For the DCI-based adaptation for additional PRACH resources, also support DCI format 1_0 with CRC scrambled by SI-RNTI to carry the adaptation indication.
Proposal 14	For adaption of PRACH in time-domain, for PDCCH order (of connected mode UE),
	The new 1-bit field is used for triggering RACH based on additional RACH resources only when Random Access Preamble index" is all zeros
	The location of new 1-bit field to indicate whether the additional PRACH resource(s) is available for the triggered PRACH is explicitly configured by higher layer signaling.
Proposal 15	For the PRACH mask indicating subset of the additional RACH resources,
	The mask is applicable at unit of SFN level (Alt 3)
	Support a bitmap (of size [4 or 16] bits) applicable at SFN level to identify whether the additional RACH resources in corresponding SFN belong to the subset or not.
Proposal 16	Select one of the following alternatives for addressing RA-RNTI ambiguity issue:
	Alt a) modifying RA-RNTI equation
	Alt b) reindex the f_id for additional valid ROs by adding the value of msg1-FDM of legacy ROs when the additional valid ROs and legacy ROs overlap in time domain
	Alt c) no special handling (e.g. leave it up to implementation)
Proposal 17	For Rel-19 PEI configuration support of multiplexing of legacy and Rel-19 PEIs, ask RAN2 to additionally introduce the following optional parameters: - Starting bit position within DCI 2_7 for Rel-19 paging indication field [default 0] - Starting bit position within DCI 2_7 for TRS info
 
 

3GPP TSG RAN WG1 #120bis   		                                                                       R1-2502845 Wuhan, China, April 7th – 11th, 2025
Agenda item:	9.5.3
Source: 	Qualcomm Incorporated
Title: 	Adaptation of common channel transmissions
Document for:	Discussion/Decision

Conclusion
The contribution has discussed our views on adaptation of signal/channel transmissions. In particular, we make the following observations and proposals:
SSB adaptation in time domain
Observation 1: The current specifications mean that DCI adaptation of SSB periodicity is only limited to scenario 3B defined in agenda item 9.5.1. No specification change on application scenarios is necessary.
Observation 2: The same DCI 2_7 can carry early paging indication for both legacy and additional POs by concatenating a bitmap for the additional POs to the bitmap indicated for the legacy UE including early indication of legacy POs and any TRS availability indication. 

Proposal 1: Support configuration of one additional SSB burst periodicity for an Scell.
Proposal 2: Introduce a new RRC parameter [ssbPeriodicityAdaptation] to indicate whether information of SSB periodicity adaptation will be included in DCI2_9 for a serving cell or not while the position in DCI is determined by one of the following options:
Option 1: SSB adaptation indication is included at the end of the cell DTX/DRX indication block.
Option 2: Information block of SSB periodicity adaptation is separate from cell DTX/DRX indication block and is identified by a new parameter [positionInDCI-ssbAdapatation] provided by higher layers.

Proposal 2.1:  If Option 1 is adopted, RAN1 adopts the following update to TS 38.212.



Proposal 2.2:  If Option 2 is adopted, RAN1 adopts the following update to TS 38.212.


Proposal 3: Adopt the following update to Clause 11.5 of TS 38.213 for timeline of SSB burst periodicity adaptation using DCI 2_9.
If no consensus on a value of  is reached in RAN1, we suggest to send an LS to RAN4 on determining the value.

Proposal 4: For SSB burst periodicity adaptation by DCI 2_9, the UE is not expected to transmit PRACH in a valid PRACH occasion if the occasion precedes a SS/PBCH block in the PRACH slot and does not start at least  symbols after a last SS/PBCH block reception symbol where  is provided in Table 8.1-2 of TS 38.213 and the SS/PBCH block is the SS/PBCH block that is transmitted in response to SSB burst periodicity indication in DCI 2_9.

Proposal 5: Adopt the following update to Clause 10 of TS 38.213 for PDCCH monitoring.


Proposal 6: Adopt the following update to Clause 5.1.4 of TS 38.214 for PDSCH resource mapping.


PRACH adaptation in time domain
Proposal 7: PRACH adaptation is applied to common configuration defined by RACH-ConfigCommon associated with 4-step RACH and to the dedicated configuration defined by RACH-ConfigDedicated associated with a PDCCH order.
Further discuss whether one configuration of additional ROs is associated with one configuration of legacy ROs or one configuration of additional ROs can be associated with multiple configurations of legacy ROs.
Proposal 8: Discuss the use cases of RACH for which the additional PRACH resources can be applied and whether the adaptation indication indicates availability of additional ROs for all of them or a subset of them.
Proposal 9: The additional PRACH resources that overlap, even partially, in both time and frequency with the legacy ROs that are not mapped to SSBs are considered valid.
Proposal 10: Select one of the following options for semi-statically masking additional ROs:
Option 1: Define the following masking table in which the association period and association pattern period are defined based on additional ROs only. Furthermore, the masking is only applicable when the number of association periods per association pattern period is more than one.


Option 2: Define a periodic time domain window in which valid additional PRACH resources can be used for PRACH transmission.
Proposal 11: For adaptation indication using the paging DCI, use the reserved bits in the paging DCI (option 1).
Note: the total number of reserved bits would be split between TRS availability indication and PRACH adaptation indication if both features are supported.
Proposal 12: The reference point for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI is,
The SFN of the first PF from the next DRX cycle specified in Clause 7.1 in TS 38.304 for RRC idle/inactive UEs.
The SFN of the first PF from the next DRX cycle defined by defaultPagingCycle for RRC connected UEs.
Proposal 13: When using DCI1_0 with C-RNTI used to trigger PRACH to indicate the availability of additional PRACH resources, the availability indication is carried in the following fields based on whether the PDCCH order triggers CFRA or CBRA:
For CFRA: use reserved bits in the DCI.
For CBRA: reuse PRACH mask index field or SSB index field which are reserved under CBRA.
Proposal 14: Do not support indication of a separate PRACH mask index in DCI 1_0 triggering CFRA for the additional PRACH resources.
Proposal 15: The availability indication bit in the PDCCH order may indicate the availability of additional PRACH resources defined with respect to the common configuration if the UE is not configured with dedicated configuration or additional PRACH resources with respect to the dedicated configuration.
Proposal 16: In addition to paging DCI, consider supporting adaptation based on DCI format 2_7 for UE supporting PEI.
Proposal 17: Rel-19 UE should prioritize the transmission over the additional PRACH resources when they are indicated as available for transmission.
Proposal 18: Discuss Rel-19 UE PRACH power control when additional PRACH resources are available for transmission.
Proposal 19: To avoid RA-RNTI ambiguity when valid legacy and additional ROs overlap in time domain, consider one of the following options:
Option 1: Enhance RA-RNTI computation formula for the additional ROs.
Option 2: No change to RA-RNTI computation formula. Interpret the frequency domain index for ROs including both legacy ROs and additional ROs when they are overlapped in time.
Paging adaptation in time domain
Proposal 20: Adopt the following update to TS 38.212: 

3GPP TSG RAN WG1 Meeting #120-bis	  R1-2502919
Wuhan, China, Apri 7th – Apri 11th, 2025

Agenda Item:		9.5.3
Source:		CEWiT
Title:			Discussion on adaptation of common signal and channel transmissions.
Document for:		Discussion 

Conclusion
In this contribution, we discussed the techniques required for NES and the following proposals are made, 
Proposal 1: Time domain adaptation of the continuously transmitted number of SSBs within an SSB burst is supported.
Proposal 2: Indication of SSB adaptation in time using DCI format 2_9 can be supported through the following alternatives:
    Alternative 1: Use a DCI format 2_9 scrambled with a new RNTI dedicated to SSB adaptation.
    Alternative 2: Use additional blocks within the existing contents of DCI format 2_9 scrambled with cellDTRX-RNTI to indicate SSB adaptation.
Proposal 3: Support a PRACH mask based on configuration parameters, such as a bitmap at the SFN level or a periodic time-domain window, for DCI-based adaptation of additional PRACH resources. .

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

Agenda Item:	9.5.3
Source:	Moderator (Ericsson)
Title:	Summary#1 of AI 9.5.3 for R19 NES
Document for:	Discussion

Conclusion
There is no RAN1 consensus to support time domain adaptation for CD-SSB in Rel-19 for SCell

Agreement
For adaptation of SSB in time-domain, support the following to adapt SSB burst periodicity for an SCell
UE is configured with SSB burst periodicity using legacy signalling for the SCell 
UE is configured with X additional SSB burst periodicity for the SCell
FFS: Value of X
SSB occasions with larger periodicity are subset of the SSB occasions with shorter periodicity
FFS: Whether there is specification impact
Note: This does not impact the discussion on OD-SSB
For switching the periodicity, down-select between 
(MAC-CE) 
MAC-CE details for SSB burst periodicity adaptation is up to RAN2.
(DCI)
Alt 1-3: DCI based signalling is used

Agreement
For adaption of PRACH in time-domain, for a connected mode UE, support a 1-bit field in DCI 1_0 with C-RNTI used to trigger PRACH (i.e. PDCCH order) to indicate whether the additional PRACH resource(s) is available for the triggered PRACH. 
FFS: UE behaviour (e.g. applicable resources for PRACH mask index) when it is indicated of additional PRACH resource(s)
FFS: Details on how to reuse existing bit for the 1-bit indication

Agreement
For DCI-based adaptation for additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information for additional PRACH resource from a reference point and for a validity time duration
FFS: Validity time duration for availability is configured by higher layer signaling or predefined
FFS: Location of the reference point defined in the specification
FFS: Value/granularity of the validity time duration.
FFS: Whether DCI can be used to explicitly deactivate the additional PRACH resources

Agreement
For DCI-based adaptation for additional PRACH resources, support optional semi-static signalling of a single PRACH mask to identify the subset of the additional PRACH resources 
The mask is applicable at unit of 
Alt 1: PRACH association period 
Alt 2: PRACH association pattern period
Alt 3: SFN level
The PRACH association period is determined based on valid additional ROs only.
The mask is applied after valid RO determination and SSB-RO mapping.
Note: The existing behaviour in TS 38.213 "An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec." is not impacted due to application of the mask.
This is applicable at least for adaptation for DCI 1_0 with P-RNTI 
The DCI does not indicate PRACH mask selection
FFS: how the mask is identified 
Option 1: The PRACH mask is from a PRACH mask table
Pre-defined table with N=[4 or 8 or 16] rows
The semi-static signalling indicates a PRACH mask index 
Option 2: The PRACH mask is based on configuration parameters e.g. bitmap at SFN-level, periodic time domain window, …

Agreement
Separate configuration of Msg1-FDM for the additional PRACH resources at least for 4-step RACH is supported
UE is not expected to be configured such that there are more than 8 FDM-ed valid ROs (legacy + additional ROs)
FFS: When there is no configuration of Msg1-FDM
Separate configuration of number of SSB per RO is supported

Agreement
Study the following options for the reference point (for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF) for RRC idle/inactive mode UE and RRC connected mode UE, 
Option 1: SFN of the first PF from the next I-DRX cycle 
Option 2: SFN of the first PF from the current I-DRX cycle 
Option 3: From the first frame of the first PRACH association period after UE receives the DCI
Option 4: From the first frame of the current SI modification period 
Option 5: From the first frame of the next SI modification period

Agreement
For adaptation of SSB in time-domain, for adapting SSB burst periodicity for an SCell
Support group common DCI signalling for switching the SSB burst periodicity using DCI format 2_9 with [cellDTRX-RNTI]
FFS: which scenario(s) is this applicable for (e.g. as defined in 9.5.1)
Note: Above does not prevent RAN2 from designing a MAC CE based on OD-SSB feature and also used for SSB burst adaptation

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

Agenda Item:	9.5.3
Source:	Moderator (Ericsson)
Title:	Summary#2 of AI 9.5.3 for R19 NES
Document for:	Discussion

Conclusion
There is no RAN1 consensus to support time domain adaptation for CD-SSB in Rel-19 for SCell

Agreement
For adaptation of SSB in time-domain, support the following to adapt SSB burst periodicity for an SCell
UE is configured with SSB burst periodicity using legacy signalling for the SCell 
UE is configured with X additional SSB burst periodicity for the SCell
FFS: Value of X
SSB occasions with larger periodicity are subset of the SSB occasions with shorter periodicity
FFS: Whether there is specification impact
Note: This does not impact the discussion on OD-SSB
For switching the periodicity, down-select between 
(MAC-CE) 
MAC-CE details for SSB burst periodicity adaptation is up to RAN2.
(DCI)
Alt 1-3: DCI based signalling is used

Agreement
For adaption of PRACH in time-domain, for a connected mode UE, support a 1-bit field in DCI 1_0 with C-RNTI used to trigger PRACH (i.e. PDCCH order) to indicate whether the additional PRACH resource(s) is available for the triggered PRACH. 
FFS: UE behaviour (e.g. applicable resources for PRACH mask index) when it is indicated of additional PRACH resource(s)
FFS: Details on how to reuse existing bit for the 1-bit indication

Agreement
For DCI-based adaptation for additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information for additional PRACH resource from a reference point and for a validity time duration
FFS: Validity time duration for availability is configured by higher layer signaling or predefined
FFS: Location of the reference point defined in the specification
FFS: Value/granularity of the validity time duration.
FFS: Whether DCI can be used to explicitly deactivate the additional PRACH resources

Agreement
For DCI-based adaptation for additional PRACH resources, support optional semi-static signalling of a single PRACH mask to identify the subset of the additional PRACH resources 
The mask is applicable at unit of 
Alt 1: PRACH association period 
Alt 2: PRACH association pattern period
Alt 3: SFN level
The PRACH association period is determined based on valid additional ROs only.
The mask is applied after valid RO determination and SSB-RO mapping.
Note: The existing behaviour in TS 38.213 "An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec." is not impacted due to application of the mask.
This is applicable at least for adaptation for DCI 1_0 with P-RNTI 
The DCI does not indicate PRACH mask selection
FFS: how the mask is identified 
Option 1: The PRACH mask is from a PRACH mask table
Pre-defined table with N=[4 or 8 or 16] rows
The semi-static signalling indicates a PRACH mask index 
Option 2: The PRACH mask is based on configuration parameters e.g. bitmap at SFN-level, periodic time domain window, …

Agreement
Separate configuration of Msg1-FDM for the additional PRACH resources at least for 4-step RACH is supported
UE is not expected to be configured such that there are more than 8 FDM-ed valid ROs (legacy + additional ROs)
FFS: When there is no configuration of Msg1-FDM
Separate configuration of number of SSB per RO is supported

Agreement
Study the following options for the reference point (for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF) for RRC idle/inactive mode UE and RRC connected mode UE, 
Option 1: SFN of the first PF from the next I-DRX cycle 
Option 2: SFN of the first PF from the current I-DRX cycle 
Option 3: From the first frame of the first PRACH association period after UE receives the DCI
Option 4: From the first frame of the current SI modification period 
Option 5: From the first frame of the next SI modification period

Agreement
For adaptation of SSB in time-domain, for adapting SSB burst periodicity for an SCell
Support group common DCI signalling for switching the SSB burst periodicity using DCI format 2_9 with [cellDTRX-RNTI]
FFS: which scenario(s) is this applicable for (e.g. as defined in 9.5.1)
Note: Above does not prevent RAN2 from designing a MAC CE based on OD-SSB feature and also used for SSB burst adaptation

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

Agenda Item:	9.5.3
Source:	Moderator (Ericsson)
Title:	Summary#3 of AI 9.5.3 for R19 NES
Document for:	Discussion

Conclusion
There is no RAN1 consensus to support time domain adaptation for CD-SSB in Rel-19 for SCell

Agreement
For adaptation of SSB in time-domain, support the following to adapt SSB burst periodicity for an SCell
UE is configured with SSB burst periodicity using legacy signalling for the SCell 
UE is configured with X additional SSB burst periodicity for the SCell
FFS: Value of X
SSB occasions with larger periodicity are subset of the SSB occasions with shorter periodicity
FFS: Whether there is specification impact
Note: This does not impact the discussion on OD-SSB
For switching the periodicity, down-select between 
(MAC-CE) 
MAC-CE details for SSB burst periodicity adaptation is up to RAN2.
(DCI)
Alt 1-3: DCI based signalling is used

Agreement
For adaption of PRACH in time-domain, for a connected mode UE, support a 1-bit field in DCI 1_0 with C-RNTI used to trigger PRACH (i.e. PDCCH order) to indicate whether the additional PRACH resource(s) is available for the triggered PRACH. 
FFS: UE behaviour (e.g. applicable resources for PRACH mask index) when it is indicated of additional PRACH resource(s)
FFS: Details on how to reuse existing bit for the 1-bit indication

Agreement
For DCI-based adaptation for additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information for additional PRACH resource from a reference point and for a validity time duration
FFS: Validity time duration for availability is configured by higher layer signaling or predefined
FFS: Location of the reference point defined in the specification
FFS: Value/granularity of the validity time duration.
FFS: Whether DCI can be used to explicitly deactivate the additional PRACH resources

Agreement
For DCI-based adaptation for additional PRACH resources, support optional semi-static signalling of a single PRACH mask to identify the subset of the additional PRACH resources 
The mask is applicable at unit of 
Alt 1: PRACH association period 
Alt 2: PRACH association pattern period
Alt 3: SFN level
The PRACH association period is determined based on valid additional ROs only.
The mask is applied after valid RO determination and SSB-RO mapping.
Note: The existing behaviour in TS 38.213 "An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec." is not impacted due to application of the mask.
This is applicable at least for adaptation for DCI 1_0 with P-RNTI 
The DCI does not indicate PRACH mask selection
FFS: how the mask is identified 
Option 1: The PRACH mask is from a PRACH mask table
Pre-defined table with N=[4 or 8 or 16] rows
The semi-static signalling indicates a PRACH mask index 
Option 2: The PRACH mask is based on configuration parameters e.g. bitmap at SFN-level, periodic time domain window, …

Agreement
Separate configuration of Msg1-FDM for the additional PRACH resources at least for 4-step RACH is supported
UE is not expected to be configured such that there are more than 8 FDM-ed valid ROs (legacy + additional ROs)
FFS: When there is no configuration of Msg1-FDM
Separate configuration of number of SSB per RO is supported

Agreement
Study the following options for the reference point (for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF) for RRC idle/inactive mode UE and RRC connected mode UE, 
Option 1: SFN of the first PF from the next I-DRX cycle 
Option 2: SFN of the first PF from the current I-DRX cycle 
Option 3: From the first frame of the first PRACH association period after UE receives the DCI
Option 4: From the first frame of the current SI modification period 
Option 5: From the first frame of the next SI modification period

Agreement
For adaptation of SSB in time-domain, for adapting SSB burst periodicity for an SCell
Support group common DCI signalling for switching the SSB burst periodicity using DCI format 2_9 with [cellDTRX-RNTI]
FFS: which scenario(s) is this applicable for (e.g. as defined in 9.5.1)
Note: Above does not prevent RAN2 from designing a MAC CE based on OD-SSB feature and also used for SSB burst adaptation

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

Agenda Item:	9.5.3
Source:	Moderator (Ericsson)
Title:	Summary#4 of AI 9.5.3 for R19 NES
Document for:	Discussion

Conclusion
There is no RAN1 consensus to support time domain adaptation for CD-SSB in Rel-19 for SCell

Agreement
For adaptation of SSB in time-domain, support the following to adapt SSB burst periodicity for an SCell
UE is configured with SSB burst periodicity using legacy signalling for the SCell 
UE is configured with X additional SSB burst periodicity for the SCell
FFS: Value of X
SSB occasions with larger periodicity are subset of the SSB occasions with shorter periodicity
FFS: Whether there is specification impact
Note: This does not impact the discussion on OD-SSB
For switching the periodicity, down-select between 
(MAC-CE) 
MAC-CE details for SSB burst periodicity adaptation is up to RAN2.
(DCI)
Alt 1-3: DCI based signalling is used

Agreement
For adaption of PRACH in time-domain, for a connected mode UE, support a 1-bit field in DCI 1_0 with C-RNTI used to trigger PRACH (i.e. PDCCH order) to indicate whether the additional PRACH resource(s) is available for the triggered PRACH. 
FFS: UE behaviour (e.g. applicable resources for PRACH mask index) when it is indicated of additional PRACH resource(s)
FFS: Details on how to reuse existing bit for the 1-bit indication

Agreement
For DCI-based adaptation for additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information for additional PRACH resource from a reference point and for a validity time duration
FFS: Validity time duration for availability is configured by higher layer signaling or predefined
FFS: Location of the reference point defined in the specification
FFS: Value/granularity of the validity time duration.
FFS: Whether DCI can be used to explicitly deactivate the additional PRACH resources

Agreement
For DCI-based adaptation for additional PRACH resources, support optional semi-static signalling of a single PRACH mask to identify the subset of the additional PRACH resources 
The mask is applicable at unit of 
Alt 1: PRACH association period 
Alt 2: PRACH association pattern period
Alt 3: SFN level
The PRACH association period is determined based on valid additional ROs only.
The mask is applied after valid RO determination and SSB-RO mapping.
Note: The existing behaviour in TS 38.213 "An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec." is not impacted due to application of the mask.
This is applicable at least for adaptation for DCI 1_0 with P-RNTI 
The DCI does not indicate PRACH mask selection
FFS: how the mask is identified 
Option 1: The PRACH mask is from a PRACH mask table
Pre-defined table with N=[4 or 8 or 16] rows
The semi-static signalling indicates a PRACH mask index 
Option 2: The PRACH mask is based on configuration parameters e.g. bitmap at SFN-level, periodic time domain window, …

Agreement
Separate configuration of Msg1-FDM for the additional PRACH resources at least for 4-step RACH is supported
UE is not expected to be configured such that there are more than 8 FDM-ed valid ROs (legacy + additional ROs)
FFS: When there is no configuration of Msg1-FDM
Separate configuration of number of SSB per RO is supported

Agreement
Study the following options for the reference point (for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF) for RRC idle/inactive mode UE and RRC connected mode UE, 
Option 1: SFN of the first PF from the next I-DRX cycle 
Option 2: SFN of the first PF from the current I-DRX cycle 
Option 3: From the first frame of the first PRACH association period after UE receives the DCI
Option 4: From the first frame of the current SI modification period 
Option 5: From the first frame of the next SI modification period

Agreement
For adaptation of SSB in time-domain, for adapting SSB burst periodicity for an SCell
Support group common DCI signalling for switching the SSB burst periodicity using DCI format 2_9 with [cellDTRX-RNTI]
FFS: which scenario(s) is this applicable for (e.g. as defined in 9.5.1)
Note: Above does not prevent RAN2 from designing a MAC CE based on OD-SSB feature and also used for SSB burst adaptation

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

Agenda Item:	9.5.3
Source:	Moderator (Ericsson)
Title:	Final Summary of AI 9.5.3 for R19 NES
Document for:	Discussion

Conclusion
There is no RAN1 consensus to support time domain adaptation for CD-SSB in Rel-19 for SCell

Agreement
For adaptation of SSB in time-domain, support the following to adapt SSB burst periodicity for an SCell
UE is configured with SSB burst periodicity using legacy signalling for the SCell 
UE is configured with X additional SSB burst periodicity for the SCell
FFS: Value of X
SSB occasions with larger periodicity are subset of the SSB occasions with shorter periodicity
FFS: Whether there is specification impact
Note: This does not impact the discussion on OD-SSB
For switching the periodicity, down-select between 
(MAC-CE) 
MAC-CE details for SSB burst periodicity adaptation is up to RAN2.
(DCI)
Alt 1-3: DCI based signalling is used

Agreement
For adaption of PRACH in time-domain, for a connected mode UE, support a 1-bit field in DCI 1_0 with C-RNTI used to trigger PRACH (i.e. PDCCH order) to indicate whether the additional PRACH resource(s) is available for the triggered PRACH. 
FFS: UE behaviour (e.g. applicable resources for PRACH mask index) when it is indicated of additional PRACH resource(s)
FFS: Details on how to reuse existing bit for the 1-bit indication

Agreement
For DCI-based adaptation for additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information for additional PRACH resource from a reference point and for a validity time duration
FFS: Validity time duration for availability is configured by higher layer signaling or predefined
FFS: Location of the reference point defined in the specification
FFS: Value/granularity of the validity time duration.
FFS: Whether DCI can be used to explicitly deactivate the additional PRACH resources

Agreement
For DCI-based adaptation for additional PRACH resources, support optional semi-static signalling of a single PRACH mask to identify the subset of the additional PRACH resources 
The mask is applicable at unit of 
Alt 1: PRACH association period 
Alt 2: PRACH association pattern period
Alt 3: SFN level
The PRACH association period is determined based on valid additional ROs only.
The mask is applied after valid RO determination and SSB-RO mapping.
Note: The existing behaviour in TS 38.213 "An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS/PBCH block indexes repeats at most every 160 msec." is not impacted due to application of the mask.
This is applicable at least for adaptation for DCI 1_0 with P-RNTI 
The DCI does not indicate PRACH mask selection
FFS: how the mask is identified 
Option 1: The PRACH mask is from a PRACH mask table
Pre-defined table with N=[4 or 8 or 16] rows
The semi-static signalling indicates a PRACH mask index 
Option 2: The PRACH mask is based on configuration parameters e.g. bitmap at SFN-level, periodic time domain window, …

Agreement
Separate configuration of Msg1-FDM for the additional PRACH resources at least for 4-step RACH is supported
UE is not expected to be configured such that there are more than 8 FDM-ed valid ROs (legacy + additional ROs)
FFS: When there is no configuration of Msg1-FDM
Separate configuration of number of SSB per RO is supported

Agreement
Study the following options for the reference point (for the availability information of additional PRACH resources indicated by DCI 1_0 with P-RNTI in a PF) for RRC idle/inactive mode UE and RRC connected mode UE, 
Option 1: SFN of the first PF from the next I-DRX cycle 
Option 2: SFN of the first PF from the current I-DRX cycle 
Option 3: From the first frame of the first PRACH association period after UE receives the DCI
Option 4: From the first frame of the current SI modification period 
Option 5: From the first frame of the next SI modification period

Agreement
For adaptation of SSB in time-domain, for adapting SSB burst periodicity for an SCell
Support group common DCI signalling for switching the SSB burst periodicity using DCI format 2_9 with [cellDTRX-RNTI]
FFS: which scenario(s) is this applicable for (e.g. as defined in 9.5.1)
Note: Above does not prevent RAN2 from designing a MAC CE based on OD-SSB feature and also used for SSB burst adaptation