R2-2503374 - Summary of [POST129b][122][NES] (OPPO)_V20_Rapp_Clean.docx
3GPP TSG-RAN2 Meeting#130 R2-2503374 Malta, Malta, May 19th - May 23rd, 2025 Agenda Item: 8.5.4 Source: OPPO Title: Summary of [122] Document for: Discussion, Decision
Conclusion Based on the offline, we reached the following WF Proposal 1 R2 not pursue spec impact specifically for the usage of R19 additional RACH resources for CFRA initiated by PDCCH order for additional RACH; L3 HO command. LTM CSC MAC-CE; PDCCH order for LTM early UL sync; Proposal 2 R2 not pursue spec impact specifically for the usage for R19 additional RACH resources for CFRA initiated by BFR. And taking that as a premise, R2 discuss whether UE does not base on DCI 1_0 of P-RNTI to know the availability of RACH resource indicated in rach-configGeneric for BFR. Proposal 3 R2 confirms the newly introduced 1-bit indication in DCI 1_0 for C-RNTI, i.e., PDCCH order, applies to both CBRA and CFRA.
R2-2503393_Adaptation of common signal channel transmissions.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503393 St.Julians, Malta, May 19th – 23rd , 2025 Agenda item: 8.5.4 Source: Samsung Title: Adaptation of common signal transmissions Document for: Discussion and Decision
Conclusion Proposal 1: If cell supports paging adaptation, Starting PDCCH monitoring occasion number (firstPDCCH-MonitoringOccasionOfPO’) of PO is configured separately for paging adaptation. firstPDCCH-MonitoringOccasionOfPO’ for paging adaptation is optional. if firstPDCCH-MonitoringOccasionOfPO’ for paging adaptation is configured, PO for paging adaptation is determined based on starting PDCCH monitoring occasion number, otherwise not. Proposal 2: Introduce prach-ConfigurationIndex, msg1-FrequencyStart, mask index and a value of K (number of association pattern periods) for additional rach resources in RACH-ConfigGeneric IE. Proposal 3: PRACH adpatation in time domain is supported for both NUL and SUL. Proposal 4: RAN2 to discuss and agree one of the following for RRC_CONNECTED Option 1: if adaptation for additional PRACH resources is supported in active UL BWP, network ensures that paging search space is configured in active DL BWP. Option 2: Introduce other mechanism (such RRC Reconfiguration message or MAC CE or group DCI) for adaptation for additional PRACH resources in RRC_CONNECTED. Proposal 5: RAN2 to discuss and agree one of the following for RRC_CONNECTED Option 1: For DCI-based adaptation indication for additional PRACH resources in RRC_CONNECTED, UE monitors the indication in any paging occasion at least once every defaultPagingCycle Option 2: For DCI-based adaptation for additional PRACH resources in RRC_CONNECTED, UE monitors the indication in any paging occasion at least once every modification period Proposal 6: the f_id in the RA-RNTI calculation for additional RO is starting from legacy FDMed RO to additionally FDMed RO, i.e., f_id for additional NES PRACH is From 0 to msg1_FDMed_additional if there is no FDMed legacy RO From msg1_FDMed_legacy to msg1_FDMed_legacy + msg1_FDMed_additional if there is FDMed legacy RO. References
R2-2503416 Adaptation of Common signal channel transmissions.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503416 St Julian, Malta, 19th – 23rd May, 2025 Source: CATT Title: Adaptation of common signal channel transmissions Agenda Item: 8.5.4 Document for: Discussion and Decision
Conclusion According to the analysis in section 2, we have the following observations and proposals: Paging Adaptation Proposal 1: A separate firstPDCCH-MonitoringOccasionOfPO for R19 paging adaptation is introduced: The maximum PO per PF is extended to 8; The maximum offset value is extended to 32 radio frames at symbol level. Proposal 2: If paging adaptation is enabled (i.e., pagingAdaptation-NS and pagingAdaptationNAndPagingFrameOffset are signaled in system information) in the cell, but the firstPDCCH-MonitoringOccasionOfPO for R19 paging adaptation is absent, UE supporting paging adaption uses legacy firstPDCCH-MonitoringOccasionOfPO if configured. Proposal 3a: A separate pei-ConfigBWP for paging adaptation is not needed, but firstPDCCH-MonitoringOccasionOfPEI-O in the legacy pei-ConfigBWP-r17 is needed to be introduced separately for paging adaptation, i.e., a separate firstPDCCH-MonitoringOccasionOfPEI-O for R19 paging adaptation is introduced. Proposal 3b: For the separate firstPDCCH-MonitoringOccasionOfPEI-O for R19 paging adaptation: The maximum number of PEI occasion per paging frame is extended to 8; The maximum offset value is extended to 32 radio frames at symbol level. Proposal 4: If pagingAdaptationPEI-Config is signaled in system information but the separate firstPDCCH-MonitoringOccasionOfPEI-O for R19 paging adaptation is absent, R19 UE supporting paging adaption uses legacy firstPDCCH-MonitoringOccasionOfPEI-O if configured. Proposal 5: Add a restriction in the field description of pagingAdaptationNAndPagingFrameOffset, i.e., the number of total paging frames in T with should be less than that with nAndPagingFrameOffset. Proposal 6: Remove “oneT” from pagingAdaptationNAndPagingFrameOffset. RACH Adaptation Proposal 7: Use the 5th bit within the Short Message field for RACH adaptation indication in DCI format 1_0 with P-RNTI. Proposal 8: NW ensures that paging search space is configured in active DL BWP if RACH adaptation indication via DCI format 1_0 with P-RNTI is applied to a connected UE. Proposal 9: For IDLE/INACTIVE mode UEs and CONNECTED UEs to monitor RACH adaptation indication via DCI format 1_0 with P-RNTI, UE follows legacy procedure of monitoring SI change indication.
R2-2503454 - NES O3 - final.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503454 St.Julians, Malta, 19th – 23rd May, 2025 Agenda Item: 8.5.4 Source: OPPO Title: Discussion on adaptation of common signal/channel transmission Document for: Discussion and Decision
Conclusion Based on the discussion above, we made the following observations and proposals: Applicable RA types for RACH adaptation R2 confirms not applying RACH adaptation to RACH resources for OD-SIB1 introduced in Rel-19 NES. R2 has not started to discuss on the support of 2-step RA type, with and without feature (combination)-based RACH resource partitioning, considering the late stage of this release. R2 does not consider RACH adaptation for 2-step RA type. R2 does not pursue spec impact to enable RACH adaptation for CFRA for C-HO/C-LTM. For CFRA towards neighbouring cell (during HO or LTM), if rach-configGeneric is not present in rach-ConfigDedicated, R2 does not consider RACH adaptation, i.e., legacy RACH resources are used in this case. For CBRA towards neighboring cell (during HO or LTM), R2 does not consider RACH adaptation, i.e., legacy RACH resources are used in this case. RRC remaining issues for RACH adaptation For the configuration of additional RACH resources, R2 discusses the following options: Option-1: add the parameters for additional RACH resources within the same RACH-ConfigGeneric used for legacy RACH resource; Option-2: add another RACH-ConfigGeneric for additional RACH resources within the same RACH-ConfigCommon for legacy RACH resources; Option-3: add another RACH-ConfigCommon for additional RACH resources. CE and its related feature combinations are not supported for additional RACH resources introduced by RACH adaptation. R2 discusses the approaches to enable feature(-combination)-based RACH resource partitioning for the legacy RACH resources and the new additional RACH resources, including 1) two different feature(-combination)-based RACH partitioning schemes, 2) a same feature(-combination)-based RACH partitioning scheme. MAC remaining issues for RACH adaptation R2 de-prioritizes the discussion of NES and SBFD co-existence, and leave the related issue, if any (e.g., RA-RNTI design for additional RACH), to maintenance phase. R2 discusses whether to leave the RAR differentiation issue caused by the additional RACH resources to R1 or network implementation. If No for P7, R2 further discusses the two solutions below: Solution-1: introduce new value range different from ones for RA-RNTI and MSGB-RNTI using a fixed offset on the legacy RA-RNTI formula, i.e., new 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 80 x 8 x 4; Solution-2: within the value range of RA-RNTI, legacy RACH resources use f_id values from 0 to N-1 as in legacy, while RA-RNTI for additional RACH resources (excluding the invalidated ROs due to overlapping with legacy RACH resources) adopt f_id values from N. Remaining issues in LS (R2-2503312) for RACH adaptation R2 confirms that the usage of one bit from the Bits 5-8 within the Short Message field for adaptation indication in DCI format 1_0 with P-RNTI is feasible. R2 discusses the options to handle the UE who camps on the cell after the first modification period where the additional RACH resources are being activated (i.e., camp at MP#1 or MP#2 in the figure): Option-1: Not handle this issue; Option-2: Handle this issue, e.g., reuse the new validity duration parameter to indicate the remaining validity duration of the additional RACH resources. R2 discusses whether UE is required to read SIB1 to acquire additional RACH resource configuration upon reception of the activation indication via DCI 1_0 with P-RNTI or not. If Yes for P10, the update of the additional RACH configuration does not result in system information change notifications in Short Message. Otherwise, it does. SSB adaptation For SSB adaptation, R2 concludes the support of L3 measurement configuration based on a single MO. For SSB adaptation, R2 further discusses whether to support it for NCD-SSB configured in BWP-DownlinkDedicated as well. Paging adaptation No motivation to introduce separate pei-SearchSpace from R2 perspective. R2 clarifies that a separate PEI-O location for Rel-19 NES UEs is sufficient, and no need to introduce a separate PEI search space. 4.
R2-2503468.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503468 St Julian’s, Malta, May 19-23, 2025 Agenda item: 8.5.4 Discussion on Adaptation of common signal channel transmissions Source: NEC Title: PRACH, paging adaptation for NES Document for: Discussion, Decision
Conclusion and Proposal We have the following proposal: Proposal 1: Rel-19 NES-capable UEs should be configured to prioritize NES-specific PRACH resources, while maintaining its capability to access legacy PRACH resources by network configuration, to avoid less impact on legacy UE operations.
R2-2503553 Adaptation of common signal or channel.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503553 St. Julians, Malta, May 19th – 23rd, 2025 Agenda item: 8.5.4 Source: Fujitsu Title: Adaptation of common signal or channel Document for: Discussion and decision
Conclusion In this contribution, we have some discussions about the adaptation of common signals or channels, and the following proposals are made: Proposal 1: RAN2 to confirm that SSB adaptation has no impact on RLM and BFD/BFR. Proposal 2: Regarding RA type for PRACH adaptation, support only 4-step RA in Rel-19. Proposal 3: RAN2 to confirm that additional PRACH resources, if configured and activated, should be in the same RA resource set with legacy PRACH resources. Observation 1. With separate configuration of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, it is possible that for the same selected SSB, the preambles assigned by additional PRACH resource configuration differ from those assigned by legacy PRACH resource configuration. Proposal 4: RAN2 to discuss how to handle the RA resource selection when there are different preamble assignments for additional PRACH resource configuration and legacy PRACH resource configuration. Proposal 5: In the RA procedure, the UE should verify the availability of the additional PRACH resources at the beginning of RA resource selection.
R2-2503574 Discussion on PRACH adaptation.doc
TDoc file reading error

R2-2503712 - Remaining issues on common signal transmission adaptation.docx
3GPP TSG RAN WG2 Meeting #130 R2-2503712 St Julian’s, Malta, May 19th – 23rd, 2025 Agenda item: 8.5.4 Source: Apple Title: Remaining issues on common signal transmission adaptation WID/SID: Netw_Energy_NR_enh-Core– Release 19 Document for: Discussion and Decision 1
Conclusion In this contribution, we further discuss remaining issues on common signal transmission adaptation. Our observations are: Observation 1: There are two gaps to use legacy firstPDCCH-MonitoringOccasionOfPO to support Rel-19 PO: Need to extend maxPO-perPF-r19 to 8. Need to introduce new IE with extended range to cover the case of 32 frames (for N=1/32 case). Observation 2: As it was agreed to only extend N to 32 which is just double from legacy, the RRC overhead is not an issue anymore. Thus, no need to introduce slot level offset in firstPDCCH-MonitoringOccasionOfPO. Observation 3: Similar to PMO offset, there are two gaps to use legacy firstPDCCH-MonitoringOccasionOfPEI-O to support Rel-19 PEI: Need to extend maxPEI-perPF-r19 to 8. Need to introduce new IE with extended range to cover the case of 32 frames (for N=1/32 case). Observation 4: Only allowing DCI triggered RACH adaptation will lead to extra paging message. Furthermore, for UEs that have just accessed the network, they may not receive the Paging DCI yet in the current SI modification period. This results in that these UEs will not be able to utilize the additional PRACH resources. Observation 5: Different from DCI triggered RACH adaptation, validate duration is not needed for SIB1 triggered RACH adaptation because BCCH modification period essentially indicates its validity duration. Observation 6: As DCI with P-RNTI is cell common signaling, it is possible that the UE has on-going RACH procedure upon reception of DCI with RACH adaptation indication. Observation 7: As legacy ROs and additional ROs could be overlapping in time domain, for the ROs which are FDMed with the same f_id, their RA-RNTI are the same, which may lead to increasing RAR collision probability and UE power consumption for detecting RAR not intended for itself. Observation 8: RAN1#120 has agreed to use DCI 1-0 with C-RNTI to trigger adaptation PDCCH order RACH. However, it is not clear whether “PDCCH order” in the agreement means PDCCH order RACH in serving cell (e.g., for time alignment) or PDCCH order RACH in candidate cell (i.e. PDCCH order for early sync in LTM). Observation 9: If supporting PDCCH order RACH adaptation for early sync in LTM, it requires candidate cell to reserve two PRACH resource sets and timely coordination between source cell and target cell. Furthermore, it requires RRC specification change to add additional RACH resource configuration in IE LTM-Candidate. Based on observations, our proposals are: Paging adaptation Proposal 1: No need to have any configuration restriction on Rel-19 paging configuration (i.e. pagingAdaptationNAndPagingFrameOffset, pagingAdaptation-NS). Proposal 2: The UE derives Rel-19 paging cycle as legacy, i.e. min(default paging cycle, UE specific DRX cycle). Proposal 3: Introduce a new optional IE firstPDCCH-MonitoringOccasionOfPO-r19 to support Rel-19 PO: Extend maxPO-perPF-r19 to 8. Redesign symbol level offset IEs to cover the case of N=1/32. Example of ASN.1 change: firstPDCCH-MonitoringOccasionOfPO-r19 CHOICE { sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF-r19)) OF INTEGER (0..139), sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1.. maxPO-perPF-r19)) OF INTEGER (0..279), sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1.. maxPO-perPF-r19)) OF INTEGER (0..559), sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1.. maxPO-perPF-r19)) OF INTEGER (0..1119), sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF-r19)) OF INTEGER (0..2239), sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT-SCS15KHZone32T SEQUENCE (SIZE (1..maxPO-perPF-r19)) OF INTEGER (0..4479), sCS120KHZoneEighthT-SCS60KHZoneSixteenthT-SCS30KHZone32T SEQUENCE (SIZE (1..maxPO-perPF-r19)) OF INTEGER (0..8959), sCS120KHZoneSixteenthT-SCS60KHZone32T SEQUENCE (SIZE (1..maxPO-perPF-r19)) OF INTEGER (0..17919), sCS480KHZoneEighthT-sCS120KHZone32T SEQUENCE (SIZE (1..maxPO-perPF-r19)) OF INTEGER (0..35839), sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF-r19)) OF INTEGER (0..71679), sCS480KHZone32T SEQUENCE (SIZE (1..maxPO-perPF-r19)) OF INTEGER (0..143359) } maxPO-perPF-r19 INTEGER ::= 8 -- Maximum number of paging occasion per paging frame Proposal 4: No need to introduce a separate PEI SearchSpace for Rel-19 PEI. Proposal 5: Introduce a new IE firstPDCCH-MonitoringOccasionOfPEI-O-r19 to support Rel-19 PEI: Extend maxPEI-perPF-r19 to 8. Redesign symbol level offset IEs to cover the case of N=1/32. Example of ASN.1 change: firstPDCCH-MonitoringOccasionOfPEI-O-r19 CHOICE { sCS15KHZoneT SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..139), sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..279), sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1.. maxPO-perPF-r19)) OF INTEGER (0..559), sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..1119), sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..2239), sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT-SCS15KHZone32T SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..4479), sCS120KHZoneEighthT-SCS60KHZoneSixteenthT-SCS30KHZone32T SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..8959), sCS120KHZoneSixteenthT-SCS60KHZone32T SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..17919), sCS480KHZoneEighthT-sCS120KHZone32T SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..35839), sCS480KHZoneSixteenthT SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..71679), sCS480KHZone32T SEQUENCE (SIZE (1.. maxPEI-perPF-r19)) OF INTEGER (0..143359) } maxPEI-perPF-r19 INTEGER ::= 8 -- Maximum number of PEI occasion per paging frame RACH adaptation Proposal 6: Introduce addl-RACH-Config-Adaptation under BWP-UplinkCommon RACH-ConfigCommon in SIB1. Proposal 7: addl-RACH-Config-Adaptation can also be configured under BWP-UplinkCommon AdditionalRACHConfig RACH-ConfigCommon in SIB1. Proposal 8: Besides DCI triggered RACH adaptation, also support RACH adaptation indicated by SIB1, i.e. introduce a new indication in SIB1 to activate / deactivate RACH adaptation. Proposal 9: If UE has on-going RACH procedure upon reception of DCI with RACH adaptation indication, the UE stops the on-going RACH procedure, and re-initiates the RACH procedure with updated RACH resources. Proposal 10: RAN2 discuss RA-RNTI ambiguity issue, and consider the following alternatives: Alt 1: Introduce a fixed k_offset for the additional PRACH resources like 2-step RACH, 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 (k_offset>1). Alt 2: f_id for the additional PRACH resources is reinterpreted as the index of the PRACH occasion in the frequency domain plus the number of FDMed legacy ROs. Proposal 11: To ensure efficient discussion, proponents of CFRA adaptation is suggested to clarify their understanding on below aspects: Which additional RACH resource is applied in CFRA adaptation (e.g. whether RACH resource configured via RACH-ConfigCommon in SIB1 or dedicated CFRA resource). Whether need to introduce dedicated SSB-to-RO mapping config for additional CFRA resource. Which Mask is applied in CFRA adaptation (e.g. whether new Mask configured in SIB1 or legacy Mask configured in RRC). 4
R2-2503757_Remaining issues of common signal or channel transmissions.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503757 St Julian, Malta, 19th– 23rd May 2025 Agenda item: 8.5.4 Title: Remaining issues of common signal/channel adaption Source: ZTE Corporation, Sanechips Document for: Discussion and Decision
Conclusion and proposals Based on the analysis in previous sections, the following proposals are given: Proposal 1: The following new values for firstPDCCH-MonitoringOccasionOfPO should be introduced in 38.331. sCS15KHZoneThirtysecondT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479), sCS30KHZoneThirtysecondT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959), sCS60KHZoneThirtysecondT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17920), sCS120KHZoneThirtysecondT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839), sCS480KHZoneThirtysecondT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..143359) Proposal 2: RAN2 confirm that it is feasible to use 1 bit from the 5-8 within the Short Message field to indicate PRACH adaption. Proposal 3: The additional PRACH resources should be cell specific and broadcast via system information, e.g. SIB1. Proposal 4: Based on the latest input from RAN1, the following parameters should be included in system information for PRACH adaption: PRACH-Config Index msg1-FrequencyStart addl-ssb-Periodicity prach-SubsetMask-Index-Adaptation msg1-FDM ssb-perRACH-OccasionAndCB-PreamblesPerSSB
R2-2503828 Discussion on PRACH adaptation_cl.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503828 St. Julians, Malta, May 19th – 23rd, 2025 Agenda item: 8.5.4 Source: Sharp Title: Discussion on PRACH adaptation Document for: Discussion and Decision
Conclusions Based on the discussion above, we have the following proposals: Proposal 1: When additional RA resources are configured, the UE treats the legacy and additional RA resources as belonging to the same set of RA resources without applying prioritization. Proposal 2: For the initial Msg1 transmission, if the selected set of RA resources includes additional RA resources, the MAC shall determine their availability based on an indication from the lower layer. Proposal 3: Upon Msg1 retransmission, if the selected set of RA resources includes additional RA resources, the MAC shall determine their availability based on an indication from the lower layer. Proposal 4: PRACH adaptation is supported for 4-step RA that is switched from 2-step RA.
R2-2503895 Adaptation of Common Signal Channel Transmissions.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503895 Saint Julian’s, Malta, 19 – 23 May 2025 Agenda item: 8.5.4 Source: Nokia, Nokia Shanghai Bell Title: On Adaptation of common signal/channel transmissions for NES WID/SID: Netw_Energy_NR_enh Document for: Discussion and Decision 1
Conclusion Proposal 1: Consider SSB burst periodicity adaptation at least for Scenario #3B of Objective 1. Observation 1: One needs to be able to configure one or two additional periodicities for SSB Proposal 2: Allow configuring 1 or 2 periodicities for adapted SSB – Value range should be same as for legacy SSB configurations. Observation 2: The same structure of Rel-18 DCI 2_9 can be reused for SSB adaptation- Before agreeing final parameters we can wait for RAN1 indication of required parameters. Proposal 3: Allow direct SSB adaptation activation with RRC configuration. Proposal-4: Same number of SMTCs periodicities should be mapped to the additional periodicities, i.e., Xmax=2. Observation 3: Adapted SSB periodicity in SCell is not larger than the legacy SMTC periodicity. No impact to specification as such seen from this. Proposal 5: RAN2 to confirm that the existing servingCellMO can be used to derive the serving cell measurement in case the frequency of SSB configuration is same as for always on SSB (always the case with SSB adaptation in time domain). Proposal 6: When OD-SSB signaling is derived see whether it makes sense to use same IE with some optional fields to allow additional parameters for OD-SSB (e.g. frequency, nrOfBurst etc…) Proposal 7: add all the parameters for additional PRACH configuration in RACH-ConfigGeneric including ssb-perRACH-OccasionAndCB-PreamblesPerSSB and the new IE prach-SubsetMask-Index-Adaptation in addition to the other IEs already in RACH-ConfigGeneric level, i.e. no need to extend RACH-ConfigCommon to add the parameters or RACH-ConfigGeneric-19. Proposal 8: it is up to RAN1 to decide whether PRACH adaptation is supported for the 2-step as well. Proposal 9: Additional PRACH resources can be configured for beam failure recovery procedure and the UE considers the additional resources as available if it has been activated when BFR is triggered. Proposal 10: Higher-layer signalling based on SI, e.g. SIB1, for PRACH adaptation could be considered, in addition to the DCI-based adaptation. Proposal 11: No need to extend the RA-RNTI space for additional PRACH occasions, i.e. no RAN2 impact for RA-RNTI calculation. Proposal 12: PRACH adaptation in time domain is supported to temporarily increase the PRACH capacity to be aligned with clustered paging and spread the PRACH load when paging occasion adaptation is used. Observation 4: The use of Ns=8 and N=T/32 will result in more than double number of bits required for firstPDCCH-MonitoringOccasionOfPO as compared to the legacy signaling. Proposal 13: Add missing configuration for firstPDCCH-MonitoringOccasionOfPO to the ASN.1 (see annex for details) Proposal 14: RAN2 to discuss how to efficiently transmit firstPDCCH-MonitoringOccasionOfPO for the 4 additional POs of a PF e.g. by reducing granularity or delta to previous PO signaling. Annex A: SSB adaptation in time domain SSB ASN.1 – ServingCellConfig The IE ServingCellConfig is used to configure (add or modify) the UE with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. The parameters herein are mostly UE specific but partly also cell specific (e.g. in additionally configured bandwidth parts). Reconfiguration between a PUCCH and PUCCHless SCell is only supported using an SCell release and add. ServingCellConfig information element -- ASN1START -- TAG-SERVINGCELLCONFIG-START ServingCellConfig ::= SEQUENCE { tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, -- Cond TDD initialDownlinkBWP BWP-DownlinkDedicated OPTIONAL, -- Need M downlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need N downlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink OPTIONAL, -- Need N firstActiveDownlinkBWP-Id BWP-Id OPTIONAL, -- Cond SyncAndCellAdd bwp-InactivityTimer ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40,ms50, ms60, ms80,ms100, ms200,ms300, ms500, ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, --Need R defaultDownlinkBWP-Id BWP-Id OPTIONAL, -- Need S uplinkConfig UplinkConfig OPTIONAL, -- Need M supplementaryUplink UplinkConfig OPTIONAL, -- Need M pdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig } OPTIONAL, -- Need M pdsch-ServingCellConfig SetupRelease { PDSCH-ServingCellConfig } OPTIONAL, -- Need M csi-MeasConfig SetupRelease { CSI-MeasConfig } OPTIONAL, -- Need M sCellDeactivationTimer ENUMERATED {ms20, ms40, ms80, ms160, ms200, ms240, ms320, ms400, ms480, ms520, ms640, ms720, ms840, ms1280, spare2,spare1} OPTIONAL, -- Cond ServingCellWithoutPUCCH crossCarrierSchedulingConfig CrossCarrierSchedulingConfig OPTIONAL, -- Need M tag-Id TAG-Id, dummy1 ENUMERATED {enabled} OPTIONAL, -- Need R pathlossReferenceLinking ENUMERATED {spCell, sCell} OPTIONAL, -- Cond SCellOnly servingCellMO MeasObjectId OPTIONAL, -- Cond MeasObject ..., [[ lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, -- Need M rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N downlinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S ]], [[ supplementaryUplinkRelease-r16 ENUMERATED {true} OPTIONAL, -- Need N tdd-UL-DL-ConfigurationDedicated-IAB-MT-r16 TDD-UL-DL-ConfigDedicated-IAB-MT-r16 OPTIONAL, -- Cond TDD_IAB dormantBWP-Config-r16 SetupRelease { DormantBWP-Config-r16 } OPTIONAL, -- Need M ca-SlotOffset-r16 CHOICE { refSCS15kHz INTEGER (-2..2), refSCS30KHz INTEGER (-5..5), refSCS60KHz INTEGER (-10..10), refSCS120KHz INTEGER (-20..20) } OPTIONAL, -- Cond AsyncCA dummy2 SetupRelease { DummyJ } OPTIONAL, -- Need M intraCellGuardBandsDL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need S intraCellGuardBandsUL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need S csi-RS-ValidationWithDCI-r16 ENUMERATED {enabled} OPTIONAL, -- Need R lte-CRS-PatternList1-r16 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M lte-CRS-PatternList2-r16 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M crs-RateMatch-PerCORESETPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableTwoDefaultTCI-States-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultTCI-StatePerCoresetPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableBeamSwitchTiming-r16 ENUMERATED {true} OPTIONAL, -- Need R cbg-TxDiffTBsProcessingType1-r16 ENUMERATED {enabled} OPTIONAL, -- Need R cbg-TxDiffTBsProcessingType2-r16 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ directionalCollisionHandling-r16 ENUMERATED {enabled} OPTIONAL, -- Need R channelAccessConfig-r16 SetupRelease { ChannelAccessConfig-r16 } OPTIONAL -- Need M ]], [[ nr-dl-PRS-PDC-Info-r17 SetupRelease {NR-DL-PRS-PDC-Info-r17} OPTIONAL, -- Need M semiStaticChannelAccessConfigUE-r17 SetupRelease {SemiStaticChannelAccessConfigUE-r17} OPTIONAL, -- Need M mimoParam-r17 SetupRelease {MIMOParam-r17} OPTIONAL, -- Need M channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R timeDomainHARQ-BundlingType1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R nrofHARQ-BundlingGroups-r17 ENUMERATED {n1, n2, n4} OPTIONAL, -- Need R fdmed-ReceptionMulticast-r17 ENUMERATED {true} OPTIONAL, -- Need R moreThanOneNackOnlyMode-r17 ENUMERATED {mode2} OPTIONAL, -- Need S tci-ActivatedConfig-r17 TCI-ActivatedConfig-r17 OPTIONAL, -- Cond TCI_ActivatedConfig directionalCollisionHandling-DC-r17 ENUMERATED {enabled} OPTIONAL, -- Need R lte-NeighCellsCRS-AssistInfoList-r17 SetupRelease { LTE-NeighCellsCRS-AssistInfoList-r17 } OPTIONAL -- Need M ]], [[ lte-NeighCellsCRS-Assumptions-r17 ENUMERATED {false} OPTIONAL -- Need R ]], [[ crossCarrierSchedulingConfigRelease-r17 ENUMERATED {true} OPTIONAL -- Need N ]], [[ multiPDSCH-PerSlotType1-CB-r17 ENUMERATED {enabled, disabled} OPTIONAL -- Need R ]], [[ lte-CRS-PatternList3-r18 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M lte-CRS-PatternList4-r18 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M pdcch-CandidateReceptionWithCRS-Overlap-r18 ENUMERATED {enabled} OPTIONAL, -- Need R cjt-Scheme-PDSCH-r18 ENUMERATED {cjtSchemeA, cjtSchemeB} OPTIONAL, -- Need R tag2-r18 Tag2-r18 OPTIONAL, -- Need R cellDTX-DRX-Config-r18 SetupRelease { CellDTX-DRX-Config-r18 } OPTIONAL, -- Need M positionInDCI-cellDTRX-r18 INTEGER (0..maxDCI-2-9-Size-1-r18) OPTIONAL, -- Need R cellDTX-DRX-L1activation-r18 ENUMERATED {enabled} OPTIONAL, -- Need R mc-DCI-SetOfCellsToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSetsOfCells-r18)) OF MC-DCI-SetOfCells-r18 OPTIONAL, -- Need N mc-DCI-SetOfCellsToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSetsOfCells-r18)) OF SetOfCellsId-r18 OPTIONAL -- Need N ]], [[ mimoParam-v1850 SetupRelease {MIMOParam-v1850} OPTIONAL -- Need M ]] } Tag2-r18 ::= SEQUENCE { tag2-Id-r18 TAG-Id, tag2-flag-r18 BOOLEAN, n-TimingAdvanceOffset2-r18 ENUMERATED { n0, n25600, n39936, spare1 } OPTIONAL -- Need S } UplinkConfig ::= SEQUENCE { initialUplinkBWP BWP-UplinkDedicated OPTIONAL, -- Need M uplinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need N uplinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Uplink OPTIONAL, -- Need N firstActiveUplinkBWP-Id BWP-Id OPTIONAL, -- Cond SyncAndCellAdd pusch-ServingCellConfig SetupRelease { PUSCH-ServingCellConfig } OPTIONAL, -- Need M carrierSwitching SetupRelease { SRS-CarrierSwitching } OPTIONAL, -- Need M ..., [[ powerBoostPi2BPSK BOOLEAN OPTIONAL, -- Need M uplinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S ]], [[ enablePL-RS-UpdateForPUSCH-SRS-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForPUSCH0-0-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForSRS-r16 ENUMERATED {enabled} OPTIONAL, -- Need R uplinkTxSwitching-r16 SetupRelease { UplinkTxSwitching-r16 } OPTIONAL, -- Need M mpr-PowerBoost-FR2-r16 ENUMERATED {true} OPTIONAL -- Need R ]], [[ srs-PosTx-Hopping-r18 SetupRelease { SRS-PosTx-Hopping-r18 } OPTIONAL, -- Need M enablePL-RS-UpdateForType1CG-PUSCH-r18 ENUMERATED {enabled} OPTIONAL, -- Need R powerBoostPi2BPSK-r18 BOOLEAN OPTIONAL, -- Need R powerBoostQPSK-r18 BOOLEAN OPTIONAL -- Need R ]] } DummyJ ::= SEQUENCE { maxEnergyDetectionThreshold-r16 INTEGER(-85..-52), energyDetectionThresholdOffset-r16 INTEGER (-20..-13), ul-toDL-COT-SharingED-Threshold-r16 INTEGER (-85..-52) OPTIONAL, -- Need R absenceOfAnyOtherTechnology-r16 ENUMERATED {true} OPTIONAL -- Need R } ChannelAccessConfig-r16 ::= SEQUENCE { energyDetectionConfig-r16 CHOICE { maxEnergyDetectionThreshold-r16 INTEGER (-85..-52), energyDetectionThresholdOffset-r16 INTEGER (-13..20) } OPTIONAL, -- Need R ul-toDL-COT-SharingED-Threshold-r16 INTEGER (-85..-52) OPTIONAL, -- Need R absenceOfAnyOtherTechnology-r16 ENUMERATED {true} OPTIONAL -- Need R } IntraCellGuardBandsPerSCS-r16 ::= SEQUENCE { guardBandSCS-r16 SubcarrierSpacing, intraCellGuardBands-r16 SEQUENCE (SIZE (1..4)) OF GuardBand-r16 } GuardBand-r16 ::= SEQUENCE { startCRB-r16 INTEGER (0..274), nrofCRBs-r16 INTEGER (0..15) } DormancyGroupID-r16 ::= INTEGER (0..4) DormantBWP-Config-r16::= SEQUENCE { dormantBWP-Id-r16 BWP-Id OPTIONAL, -- Need M withinActiveTimeConfig-r16 SetupRelease { WithinActiveTimeConfig-r16 } OPTIONAL, -- Need M outsideActiveTimeConfig-r16 SetupRelease { OutsideActiveTimeConfig-r16 } OPTIONAL -- Need M } WithinActiveTimeConfig-r16 ::= SEQUENCE { firstWithinActiveTimeBWP-Id-r16 BWP-Id OPTIONAL, -- Need M dormancyGroupWithinActiveTime-r16 DormancyGroupID-r16 OPTIONAL -- Need R } OutsideActiveTimeConfig-r16 ::= SEQUENCE { firstOutsideActiveTimeBWP-Id-r16 BWP-Id OPTIONAL, -- Need M dormancyGroupOutsideActiveTime-r16 DormancyGroupID-r16 OPTIONAL -- Need R } UplinkTxSwitching-r16 ::= SEQUENCE { uplinkTxSwitchingPeriodLocation-r16 BOOLEAN, uplinkTxSwitchingCarrier-r16 ENUMERATED {carrier1, carrier2} } MIMOParam-r17 ::= SEQUENCE { additionalPCI-ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17 OPTIONAL, -- Need N additionalPCI-ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17 OPTIONAL, -- Need N unifiedTCI-StateType-r17 ENUMERATED {separate, joint} OPTIONAL, -- Need R uplink-PowerControlToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF Uplink-powerControl-r17 OPTIONAL, -- Need N uplink-PowerControlToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF Uplink-powerControlId-r17 OPTIONAL, -- Need N sfnSchemePDCCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL, -- Need R sfnSchemePDSCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL -- Need R } MIMOParam-v1850 ::= SEQUENCE { additionalTDDConfig-perPCI-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofAdditionalPCI-r17)) OF AdditionalTDDConfig-perPCI-ToAddMod-r18 OPTIONAL, -- Cond 2TA-TDD-Only additionalTDDConfig-perPCI-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17 OPTIONAL -- Need N } AdditionalTDDConfig-perPCI-ToAddMod-r18 ::= SEQUENCE { additionalTDDConfig-Index-r18 AdditionalPCIIndex-r17, tdd-UL-DL-ConfigurationCommon-r18 TDD-UL-DL-ConfigCommon } MC-DCI-SetOfCells-r18 ::= SEQUENCE { setOfCellsId-r18 SetOfCellsId-r18, nCI-Value-r18 INTEGER (0..7), scheduledCellListDCI-1-3-r18 SEQUENCE (SIZE (2..maxNrofCellsInSet-r18)) OF ServCellIndex OPTIONAL, -- Need R scheduledCellListDCI-0-3-r18 SEQUENCE (SIZE (2..maxNrofCellsInSet-r18)) OF ServCellIndex OPTIONAL, -- Need R scheduledCellComboListDCI-1-3-r18 SEQUENCE (SIZE (1..maxNrofCellCombos-r18)) OF ScheduledCellCombo-r18 OPTIONAL, -- Need R scheduledCellComboListDCI-0-3-r18 SEQUENCE (SIZE (1..maxNrofCellCombos-r18)) OF ScheduledCellCombo-r18 OPTIONAL, -- Need R antennaPortsDCI1-3-r18 ENUMERATED {type1a, type2} OPTIONAL, -- Cond TypeDCI1-3 antennaPortsDCI0-3-r18 ENUMERATED {type1a, type2} OPTIONAL, -- Cond TypeDCI0-3 tpmi-DCI0-3-r18 ENUMERATED {type1a, type2} OPTIONAL, -- Cond TypeDCI0-3 sri-DCI0-3-r18 ENUMERATED {type1a, type2} OPTIONAL, -- Cond TypeDCI0-3 priorityIndicatorDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R priorityIndicatorDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R dormancyDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R dormancyDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdcchMonAdaptDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdcchMonAdaptDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R minimumSchedulingOffsetK0DCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R minimumSchedulingOffsetK0DCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-OneShotFeedbackDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-enhType3DCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-enhType3DCIfieldDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-retxDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pucch-sSCellDynDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R tdra-FieldIndexListDCI-1-3-r18 SEQUENCE (SIZE (1..32)) OF TDRA-FieldIndexDCI-1-3-r18 OPTIONAL, -- Need R tdra-FieldIndexListDCI-0-3-r18 SEQUENCE (SIZE (1..64)) OF TDRA-FieldIndexDCI-0-3-r18 OPTIONAL, -- Need R rateMatchListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF RateMatchDCI-1-3-r18 OPTIONAL, -- Need R zp-CSI-RSListDCI-1-3-r18 SEQUENCE (SIZE (1..8)) OF ZP-CSI-DCI-1-3-r18 OPTIONAL, -- Need R tci-ListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF TCI-DCI-1-3-r18 OPTIONAL, -- Need R srs-RequestListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF SRS-RequestCombo-r18 OPTIONAL, -- Need R srs-OffsetListDCI-1-3-r18 SEQUENCE (SIZE (1..8)) OF SRS-OffsetCombo-r18 OPTIONAL, -- Need R srs-RequestListDCI-0-3-r18 SEQUENCE (SIZE (1..16)) OF SRS-RequestCombo-r18 OPTIONAL, -- Need R srs-OffsetListDCI-0-3-r18 SEQUENCE (SIZE (1..8)) OF SRS-OffsetCombo-r18 OPTIONAL -- Need R } SetOfCellsId-r18 ::= INTEGER (0..maxNrofSetsOfCells-1-r18) ScheduledCellCombo-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsInSet-r18)) OF INTEGER (0..maxNrofCellsInSet-1-r18) RateMatchDCI-1-3-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (1..2)) ZP-CSI-DCI-1-3-r18 ::= SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (1..2)) TCI-DCI-1-3-r18 ::= SEQUENCE (SIZE (2.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (3)) SRS-RequestCombo-r18 ::= SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (2..3)) SRS-OffsetCombo-r18 ::= SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF INTEGER (0..3) TDRA-FieldIndexDCI-1-3-r18 ::= SEQUENCE (SIZE (2.. maxNrofBWPsInSetOfCells-r18)) OF INTEGER (0..maxNrofDL-Allocations-1-r18) TDRA-FieldIndexDCI-0-3-r18 ::= SEQUENCE (SIZE (2.. maxNrofBWPsInSetOfCells-r18)) OF INTEGER (0..maxNrofUL-Allocations-1-r18) -- TAG-SERVINGCELLCONFIG-STOP -- ASN1STOP NOTE 1: If the dedicated part of initial UL/DL BWP configuration is absent, the initial BWP can be used but with some limitations. For example, changing to another BWP requires RRCReconfiguration since DCI format 1_0 doesn't support DCI-based switching. Annex B – PDCCH monitoring signaling – DownlinkConfigCommonSIB The IE DownlinkConfigCommonSIB provides common downlink parameters of a cell. DownlinkConfigCommonSIB information element -- ASN1START -- TAG-DOWNLINKCONFIGCOMMONSIB-START DownlinkConfigCommonSIB ::= SEQUENCE { frequencyInfoDL FrequencyInfoDL-SIB, initialDownlinkBWP BWP-DownlinkCommon, bcch-Config BCCH-Config, pcch-Config PCCH-Config, ..., [[ pei-Config-r17 PEI-Config-r17 OPTIONAL, -- Need R initialDownlinkBWP-RedCap-r17 BWP-DownlinkCommon OPTIONAL -- Need R ]], [[ frequencyInfoDL-v1800 FrequencyInfoDL-SIB-v1800 OPTIONAL -- Need R ]] , [[ pagingAdaptationPEI-Config-r19 PEI-Config-r17 OPTIONAL -- Need R ]] } DownlinkConfigCommonSIB-v1760 ::= SEQUENCE { frequencyInfoDL-v1760 FrequencyInfoDL-SIB-v1760 } BCCH-Config ::= SEQUENCE { modificationPeriodCoeff ENUMERATED {n2, n4, n8, n16}, ... } PCCH-Config ::= SEQUENCE { defaultPagingCycle PagingCycle, nAndPagingFrameOffset CHOICE { oneT NULL, halfT INTEGER (0..1), quarterT INTEGER (0..3), oneEighthT INTEGER (0..7), oneSixteenthT INTEGER (0..15) }, ns ENUMERATED {four, two, one}, firstPDCCH-MonitoringOccasionOfPO CHOICE { sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139), sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279), sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559), sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119), sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239), sCS480KHZoneT-SCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479), sCS480KHZhalfT-SCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959), sCS480KHZquarterT-SCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919) } OPTIONAL, -- Need R ..., [[ nrofPDCCH-MonitoringOccasionPerSSB-InPO-r16 INTEGER (2..4) OPTIONAL -- Cond SharedSpectrum2 ]], [[ ranPagingInIdlePO-r17 ENUMERATED {true} OPTIONAL, -- Need R firstPDCCH-MonitoringOccasionOfPO-v1710 CHOICE { sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839), sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679) } OPTIONAL -- Need R ]] , [[ pagingAdaptation-r19 ENUMERATED {eight,four, two, one} OPTIONAL, -- Need R pagingAdaptationNAndPagingFrameOffset CHOICE { oneT NULL, halfT INTEGER (0..1), quarterT INTEGER (0..3), oneEighthT INTEGER (0..7), oneSixteenthT INTEGER (0..15), oneThirtySecondT INTEGER (0..31) } ]] } PEI-Config-r17 ::= SEQUENCE { po-NumPerPEI-r17 ENUMERATED {po1, po2, po4, po8}, payloadSizeDCI-2-7-r17 INTEGER (1..maxDCI-2-7-Size-r17), pei-FrameOffset-r17 INTEGER (0..16), subgroupConfig-r17 SubgroupConfig-r17, lastUsedCellOnly-r17 ENUMERATED {true} OPTIONAL, -- Need R ... } SubgroupConfig-r17 ::= SEQUENCE { subgroupsNumPerPO-r17 INTEGER (1.. maxNrofPagingSubgroups-r17), subgroupsNumForUEID-r17 INTEGER (1.. maxNrofPagingSubgroups-r17) OPTIONAL, -- Need S ... } -- TAG-DOWNLINKCONFIGCOMMONSIB-STOP -- ASN1STOP Editor’s note: FFS field description for pagingAdaptationNAndPagingFrameOffset with respect to possible configuration restrictions. FFS: firstPDCCH-MonitoringOccasionOfPO for paging adaptations. FFS: Do we need to introduce a separate pei-ConfigBWP for paging adaptation? ----------------------------OMITTED SOME PARTS------------------------------------------- 6.4 RRC multiplicity and type constraint values – Multiplicity and type constraint definitions -- ASN1START -- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-START maxAdditionalRACH-r17 INTEGER ::= 256 -- Maximum number of additional RACH configurations. maxAI-DCI-PayloadSize-r16 INTEGER ::= 128 --Maximum size of the DCI payload scrambled with ai-RNTI maxAI-DCI-PayloadSize-1-r16 INTEGER ::= 127 --Maximum size of the DCI payload scrambled with ai-RNTI minus 1 maxBandComb INTEGER ::= 65536 -- Maximum number of DL band combinations maxBandComb-MUSIM-r18 INTEGER ::= 64 -- Maximum number of MUSIM bands and/or band combinations maxBandsUTRA-FDD-r16 INTEGER ::= 64 -- Maximum number of bands listed in UTRA-FDD UE caps maxCandidateBandIndex-r18 INTEGER ::= 8 -- Maximum number of band entry index for MUSIM capability maxBH-RLC-ChannelID-r16 INTEGER ::= 65536 -- Maximum value of BH RLC Channel ID maxBT-IdReport-r16 INTEGER ::= 32 -- Maximum number of Bluetooth IDs to report maxBT-Name-r16 INTEGER ::= 4 -- Maximum number of Bluetooth name maxCAG-Cell-r16 INTEGER ::= 16 -- Maximum number of NR CAG cell ranges in SIB3, SIB4 maxTwoPUCCH-Grp-ConfigList-r16 INTEGER ::= 32 -- Maximum number of supported configuration(s) of {primary PUCCH group -- config, secondary PUCCH group config} maxTwoPUCCH-Grp-ConfigList-r17 INTEGER ::= 16 -- Maximum number of supported configuration(s) of {primary PUCCH group -- config, secondary PUCCH group config} for PUCCH cell switching maxCBR-Config-r16 INTEGER ::= 8 -- Maximum number of CBR range configurations for sidelink communication -- congestion control maxCBR-Config-1-r16 INTEGER ::= 7 -- Maximum number of CBR range configurations for sidelink communication -- congestion control minus 1 maxCBR-Level-r16 INTEGER ::= 16 -- Maximum number of CBR levels maxCBR-Level-1-r16 INTEGER ::= 15 -- Maximum number of CBR levels minus 1 maxCellATG-r18 INTEGER ::= 8 -- Maximum number of ATG neighbour cells for which assistance information is -- provided maxCellExcluded INTEGER ::= 16 -- Maximum number of NR exclude-listed cell ranges in SIB3, SIB4 maxCellGroupings-r16 INTEGER ::= 32 -- Maximum number of cell groupings for NR-DC maxCellHistory-r16 INTEGER ::= 16 -- Maximum number of visited PCells reported maxPSCellHistory-r17 INTEGER ::= 16 -- Maximum number of visited PSCells across all reported PCells maxCellInter INTEGER ::= 16 -- Maximum number of inter-Freq cells listed in SIB4 maxCellIntra INTEGER ::= 16 -- Maximum number of intra-Freq cells listed in SIB3 maxCellMeasEUTRA INTEGER ::= 32 -- Maximum number of cells in E-UTRAN maxCellMeasIdle-r16 INTEGER ::= 8 -- Maximum number of cells per carrier for idle/inactive measurements maxCellMeasUTRA-FDD-r16 INTEGER ::= 32 -- Maximum number of cells in FDD UTRAN maxCellNTN-r17 INTEGER ::= 4 -- Maximum number of NTN neighbour cells for which assistance information is -- provided maxCarrierTypePairList-r16 INTEGER ::= 16 -- Maximum number of supported carrier type pair of (carrier type on which -- CSI measurement is performed, carrier type on which CSI reporting is -- performed) for CSI reporting cross PUCCH group maxCellAllowed INTEGER ::= 16 -- Maximum number of NR allow-listed cell ranges in SIB3, SIB4 maxEARFCN INTEGER ::= 262143 -- Maximum value of E-UTRA carrier frequency maxEUTRA-CellExcluded INTEGER ::= 16 -- Maximum number of E-UTRA exclude-listed physical cell identity ranges -- in SIB5 maxEUTRA-NS-Pmax INTEGER ::= 8 -- Maximum number of NS and P-Max values per band maxFeatureCombPreamblesPerRACHResource-r17 INTEGER ::= 256 -- Maximum number of feature combination preambles. maxLogMeasReport-r16 INTEGER ::= 520 -- Maximum number of entries for logged measurements maxMultiBands INTEGER ::= 8 -- Maximum number of additional frequency bands that a cell belongs to maxNARFCN INTEGER ::= 3279165 -- Maximum value of NR carrier frequency maxNR-NS-Pmax INTEGER ::= 8 -- Maximum number of NS and P-Max values per band maxFreqIdle-r16 INTEGER ::= 8 -- Maximum number of carrier frequencies for idle/inactive measurements maxNrofServingCells INTEGER ::= 32 -- Max number of serving cells (SpCells + SCells) maxNrofServingCells-1 INTEGER ::= 31 -- Max number of serving cells (SpCells + SCells) minus 1 maxNrofAggregatedCellsPerCellGroup INTEGER ::= 16 maxNrofAggregatedCellsPerCellGroupMinus4-r16 INTEGER ::= 12 maxNrofAperiodicFwdTimeResource-r18 INTEGER ::= 112 -- Max number of aperiodic fowarding time resources for NCR maxNrofAperiodicFwdTimeResource-1-r18 INTEGER ::= 111 -- Max number of aperiodic fowarding time resources for NCR minus 1 maxNrofDUCells-r16 INTEGER ::= 512 -- Max number of cells configured on the collocated IAB-DU maxNrofAppLayerMeas-r17 INTEGER ::= 16 -- Max number of simultaneous application layer measurements maxNrofAppLayerMeas-1-r17 INTEGER ::= 15 -- Max number of simultaneous application layer measurements minus 1 maxNrofAppLayerReports-r18 INTEGER ::= 16 -- Max number of application layer measurement reports with the same -- measConfigAppLayerId included in the same -- MeasurementReportAppLayerMessage maxNrofAvailabilityCombinationsPerSet-r16 INTEGER ::= 512 -- Max number of AvailabilityCombinationId used in the DCI format 2_5 maxNrofAvailabilityCombinationsPerSet-1-r16 INTEGER ::= 511 -- Max number of AvailabilityCombinationId used in the DCI format 2_5 minus 1 maxNrofIABResourceConfig-r17 INTEGER ::= 65536 -- Max number of IAB-ResourceConfigID used in MAC CE maxNrofIABResourceConfig-1-r17 INTEGER ::= 65535 -- Max number of IAB-ResourceConfigID used in MAC CE minus 1 maxNrofPeriodicFwdResourceSet-r18 INTEGER ::= 32 -- Max number of periodic fowarding resource sets for NCR maxNrofPeriodicFwdResourceSet-1-r18 INTEGER ::= 31 -- Max number of periodic fowarding resource sets for NCR minus 1 maxNrofPeriodicFwdResource-r18 INTEGER ::= 1024 -- Max number of periodic fowarding resources for NCR maxNrofPeriodicFwdResource-1-r18 INTEGER ::= 1023 -- Max number of periodic fowarding resources for NCR minus 1 maxNrofSemiPersistentFwdResourceSet-r18 INTEGER ::= 32 -- Max number of semi-persistent fowarding resource sets for NCR maxNrofSemiPersistentFwdResourceSet-1-r18 INTEGER ::= 31 -- Max number of semi-persistent fowarding resource sets for NCR minus 1 maxNrofSemiPersistentFwdResource-r18 INTEGER ::= 128 -- Max number of semi-persistent fowarding resources for NCR maxNrofSemiPersistentFwdResource-1-r18 INTEGER ::= 127 -- Max number of semi-persistent fowarding resources for NCR minus 1 maxNrofSCellActRS-r17 INTEGER ::= 255 -- Max number of RS configurations per SCell for SCell activation maxNrofSCells INTEGER ::= 31 -- Max number of secondary serving cells per cell group maxNrofCellMeas INTEGER ::= 32 -- Maximum number of entries in each of the cell lists in a measurement object maxNrofCRS-IM-InterfCell-r17 INTEGER ::= 8 -- Maximum number of LTE interference cells for CRS-IM per UE maxNrofRelayMeas-r17 INTEGER ::= 32 -- Maximum number of L2 U2N Relay UEs to measure for each measurement object -- on sidelink frequency maxNrofCG-SL-r16 INTEGER ::= 8 -- Max number of sidelink configured grant maxNrofCG-SL-1-r16 INTEGER ::= 7 -- Max number of sidelink configured grant minus 1 maxSL-GC-BC-DRX-QoS-r17 INTEGER ::= 16 -- Max number of sidelink DRX configurations for NR -- sidelink groupcast/broadcast communication maxNrofSL-RxInfoSet-r17 INTEGER ::= 4 -- Max number of sidelink DRX configuration sets in sidelink DRX assistant -- information maxNrofSS-BlocksToAverage INTEGER ::= 16 -- Max number for the (max) number of SS blocks to average to determine cell measurement maxNrofCondCells-r16 INTEGER ::= 8 -- Max number of conditional candidate SpCells maxNrofCondCells-1-r17 INTEGER ::= 7 -- Max number of conditional candidate SpCells minus 1 maxNrofCSI-RS-ResourcesToAverage INTEGER ::= 16 -- Max number for the (max) number of CSI-RS to average to determine cell measurement maxNrofDL-Allocations INTEGER ::= 16 -- Maximum number of PDSCH time domain resource allocations maxNrofDL-AllocationsExt-r17 INTEGER ::= 64 -- Maximum number of PDSCH time domain resource allocations for multi-PDSCH -- scheduling maxNrofDL-Allocations-1-r18 INTEGER ::= 15 -- Maximum number of PDSCH time domain resource allocations minus 1 maxNrofPDU-Sessions-r17 INTEGER ::= 256 -- Maximum number of PDU Sessions maxNrofSR-ConfigPerCellGroup INTEGER ::= 8 -- Maximum number of SR configurations per cell group maxNrofLCGs-r18 INTEGER ::= 8 -- Maximum number of LCGs maxLCG-ID INTEGER ::= 7 -- Maximum value of LCG ID maxLCG-ID-IAB-r17 INTEGER ::= 255 -- Maximum value of LCG ID for IAB-MT maxLC-ID INTEGER ::= 32 -- Maximum value of Logical Channel ID maxLC-ID-Iab-r16 INTEGER ::= 65855 -- Maximum value of BH Logical Channel ID extension maxLTE-CRS-Patterns-r16 INTEGER ::= 3 -- Maximum number of additional LTE CRS rate matching patterns maxNrOfLinkedSRS-CarriersInactive-1-r18 INTEGER ::= 2 -- Maximum number of carriers for positioning SRS CA in RRC_INACTIVE minus 1 maxNrofTAGs INTEGER ::= 4 -- Maximum number of Timing Advance Groups maxNrofTAGs-1 INTEGER ::= 3 -- Maximum number of Timing Advance Groups minus 1 maxNrofBWPs INTEGER ::= 4 -- Maximum number of BWPs per serving cell maxNrofCombIDC INTEGER ::= 128 -- Maximum number of reported MR-DC combinations for IDC maxNrofSymbols-1 INTEGER ::= 13 -- Maximum index identifying a symbol within a slot (14 symbols, indexed from 0..13) maxNrofSlots INTEGER ::= 320 -- Maximum number of slots in a 10 ms period maxNrofSlots-1 INTEGER ::= 319 -- Maximum number of slots in a 10 ms period minus 1 maxNrofPhysicalResourceBlocks INTEGER ::= 275 -- Maximum number of PRBs maxNrofPhysicalResourceBlocks-1 INTEGER ::= 274 -- Maximum number of PRBs minus 1 maxNrofPhysicalResourceBlocksPlus1 INTEGER ::= 276 -- Maximum number of PRBs plus 1 maxNrofControlResourceSets INTEGER ::= 12 -- Max number of CoReSets configurable on a serving cell maxNrofControlResourceSets-1 INTEGER ::= 11 -- Max number of CoReSets configurable on a serving cell minus 1 maxNrofControlResourceSets-1-r16 INTEGER ::= 15 -- Max number of CoReSets configurable on a serving cell extended in minus 1 maxNrofCoresetPools-r16 INTEGER ::= 2 -- Maximum number of CORESET pools maxCoReSetDuration INTEGER ::= 3 -- Max number of OFDM symbols in a control resource set maxNrofSearchSpaces-1 INTEGER ::= 39 -- Max number of Search Spaces minus 1 maxNrofSearchSpacesLinks-1-r17 INTEGER ::= 39 -- Max number of Search Space links minus 1 maxNrofBFDResourcePerSet-r17 INTEGER ::= 64 -- Max number of reference signal in one BFD set maxSFI-DCI-PayloadSize INTEGER ::= 128 -- Max number payload of a DCI scrambled with SFI-RNTI maxSFI-DCI-PayloadSize-1 INTEGER ::= 127 -- Max number payload of a DCI scrambled with SFI-RNTI minus 1 maxIAB-IP-Address-r16 INTEGER ::= 32 -- Max number of assigned IP addresses maxINT-DCI-PayloadSize INTEGER ::= 126 -- Max number payload of a DCI scrambled with INT-RNTI maxINT-DCI-PayloadSize-1 INTEGER ::= 125 -- Max number payload of a DCI scrambled with INT-RNTI minus 1 maxNrofRateMatchPatterns INTEGER ::= 4 -- Max number of rate matching patterns that may be configured maxNrofRateMatchPatterns-1 INTEGER ::= 3 -- Max number of rate matching patterns that may be configured minus 1 maxNrofRateMatchPatternsPerGroup INTEGER ::= 8 -- Max number of rate matching patterns that may be configured in one group maxNrofCSI-ReportConfigurations INTEGER ::= 48 -- Maximum number of report configurations maxNrofCSI-ReportConfigurations-1 INTEGER ::= 47 -- Maximum number of report configurations minus 1 maxNrofCSI-ResourceConfigurations INTEGER ::= 112 -- Maximum number of resource configurations maxNrofCSI-ResourceConfigurations-1 INTEGER ::= 111 -- Maximum number of resource configurations minus 1 maxNrofAP-CSI-RS-ResourcesPerSet INTEGER ::= 16 maxNrOfCSI-AperiodicTriggers INTEGER ::= 128 -- Maximum number of triggers for aperiodic CSI reporting maxNrofReportConfigPerAperiodicTrigger INTEGER ::= 16 -- Maximum number of report configurations per trigger state for aperiodic reporting maxNrofNZP-CSI-RS-Resources INTEGER ::= 192 -- Maximum number of Non-Zero-Power (NZP) CSI-RS resources maxNrofNZP-CSI-RS-Resources-1 INTEGER ::= 191 -- Maximum number of Non-Zero-Power (NZP) CSI-RS resources minus 1 maxNrofNZP-CSI-RS-ResourcesPerSet INTEGER ::= 64 -- Maximum number of NZP CSI-RS resources per resource set maxNrofNZP-CSI-RS-ResourcesPerSet-1-r18 INTEGER ::= 63 -- Maximum number of NZP CSI-RS resources per resource set minus 1 maxNrofNZP-CSI-RS-ResourceSets INTEGER ::= 64 -- Maximum number of NZP CSI-RS resource sets per cell maxNrofNZP-CSI-RS-ResourceSets-1 INTEGER ::= 63 -- Maximum number of NZP CSI-RS resource sets per cell minus 1 maxNrofNZP-CSI-RS-ResourceSetsPerConfig INTEGER ::= 16 -- Maximum number of resource sets per resource configuration maxNrofNZP-CSI-RS-ResourcesPerConfig INTEGER ::= 128 -- Maximum number of resources per resource configuration maxNrofZP-CSI-RS-Resources INTEGER ::= 32 -- Maximum number of Zero-Power (ZP) CSI-RS resources maxNrofZP-CSI-RS-Resources-1 INTEGER ::= 31 -- Maximum number of Zero-Power (ZP) CSI-RS resources minus 1 maxNrofZP-CSI-RS-ResourceSets-1 INTEGER ::= 15 maxNrofZP-CSI-RS-ResourcesPerSet INTEGER ::= 16 maxNrofZP-CSI-RS-ResourceSets INTEGER ::= 16 maxNrofCSI-IM-Resources INTEGER ::= 32 -- Maximum number of CSI-IM resources maxNrofCSI-IM-Resources-1 INTEGER ::= 31 -- Maximum number of CSI-IM resources minus 1 maxNrofCSI-IM-ResourcesPerSet INTEGER ::= 8 -- Maximum number of CSI-IM resources per set maxNrofCSI-IM-ResourceSets INTEGER ::= 64 -- Maximum number of NZP CSI-IM resource sets per cell maxNrofCSI-IM-ResourceSets-1 INTEGER ::= 63 -- Maximum number of NZP CSI-IM resource sets per cell minus 1 maxNrofCSI-IM-ResourceSetsPerConfig INTEGER ::= 16 -- Maximum number of CSI IM resource sets per resource configuration maxNrofCSI-SSB-ResourcePerSet INTEGER ::= 64 -- Maximum number of SSB resources in a resource set maxNrofCSI-SSB-ResourceSets INTEGER ::= 64 -- Maximum number of CSI SSB resource sets per cell maxNrofCSI-SSB-ResourceSets-1 INTEGER ::= 63 -- Maximum number of CSI SSB resource sets per cell minus 1 maxNrofCSI-SSB-ResourceSetsPerConfig INTEGER ::= 1 -- Maximum number of CSI SSB resource sets per resource configuration maxNrofCSI-SSB-ResourceSetsPerConfigExt INTEGER ::= 2 -- Maximum number of CSI SSB resource sets per resource configuration -- extended maxNrofFailureDetectionResources INTEGER ::= 10 -- Maximum number of failure detection resources maxNrofFailureDetectionResources-1 INTEGER ::= 9 -- Maximum number of failure detection resources minus 1 maxNrofFailureDetectionResources-1-r17 INTEGER ::= 63 -- Maximum number of the enhanced failure detection resources minus 1 maxNrofFreqSL-r16 INTEGER ::= 8 -- Maximum number of carrier frequency for NR sidelink communication maxNrofFreqSL-1-r18 INTEGER ::= 7 -- Maximum number of carrier frequency for NR sidelink communication minus 1 maxNrofSL-BWPs-r16 INTEGER ::= 4 -- Maximum number of BWP for NR sidelink communication maxNrofSL-CarrierSetConfig-r18 INTEGER ::= 96 -- Maximum number of SCCH carrier set configuration for NR sidelink -- communication maxFreqSL-EUTRA-r16 INTEGER ::= 8 -- Maximum number of EUTRA anchor carrier frequency for NR sidelink -- communication maxNrofSL-MeasId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement identity (RSRP) per destination maxNrofSL-ObjectId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement objects (RSRP) per destination maxNrofSL-ReportConfigId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement reporting configuration(RSRP) per destination maxNrofSL-PoolToMeasureNR-r16 INTEGER ::= 8 -- Maximum number of resource pool for NR sidelink measurement to measure -- for each measurement object (for CBR) maxNrofDedicatedSL-PRS-PoolToMeas-r18 INTEGER ::= 8 -- Maximum number of SL-PRS dedicated resource pool for positioning -- measurement to measure for each measurement object (for SL-PRS CBR) maxFreqSL-NR-r16 INTEGER ::= 8 -- Maximum number of NR anchor carrier frequency for NR sidelink communication maxNrofSL-QFIs-r16 INTEGER ::= 2048 -- Maximum number of QoS flow for NR sidelink communication per UE maxNrofSL-QFIsPerDest-r16 INTEGER ::= 64 -- Maximum number of QoS flow per destination for NR sidelink communication maxNrofObjectId INTEGER ::= 64 -- Maximum number of measurement objects maxNrofPageRec INTEGER ::= 32 -- Maximum number of page records maxNrofPCI-Ranges INTEGER ::= 8 -- Maximum number of PCI ranges maxPLMN INTEGER ::= 12 -- Maximum number of PLMNs broadcast and reported by UE at establishment maxTAC-r17 INTEGER ::= 12 -- Maximum number of Tracking Area Codes to which a cell belongs to maxNrofCSI-RS-ResourcesRRM INTEGER ::= 96 -- Maximum number of CSI-RS resources per cell for an RRM measurement object maxNrofCSI-RS-ResourcesRRM-1 INTEGER ::= 95 -- Maximum number of CSI-RS resources per cell for an RRM measurement object -- minus 1. maxNrofMeasId INTEGER ::= 64 -- Maximum number of configured measurements maxNrofQuantityConfig INTEGER ::= 2 -- Maximum number of quantity configurations maxNrofCSI-RS-CellsRRM INTEGER ::= 96 -- Maximum number of cells with CSI-RS resources for an RRM measurement object maxNrofSL-Dest-r16 INTEGER ::= 32 -- Maximum number of destination for NR sidelink communication and discovery maxNrofSL-Dest-1-r16 INTEGER ::= 31 -- Highest index of destination for NR sidelink communication and discovery maxNrofSL-PRS-PerDest-r18 INTEGER ::= 8 -- Max number of SL-PRS transmission supported per destination UE maxNrofSLRB-r16 INTEGER ::= 512 -- Maximum number of radio bearer for NR sidelink communication per UE without duplication maxSL-LCID-Plus1-r18 INTEGER ::= 513 -- Maximum number of RLC bearer for NR sidelink communication per UE without duplication plus 1 maxSL-LCID-r18 INTEGER ::= 1024 -- Maximum number of RLC bearer for NR sidelink communication per UE with duplication maxSL-NonAnchorRBsets INTEGER ::= 4 -- Maximum number of non-anchor RB sets maxSL-LCID-r16 INTEGER ::= 512 -- Maximum number of RLC bearer for NR sidelink communication per UE maxSL-SyncConfig-r16 INTEGER ::= 16 -- Maximum number of sidelink Sync configurations maxNrofRXPool-r16 INTEGER ::= 16 -- Maximum number of Rx resource pool for NR sidelink communication and -- discovery maxNrofTXPool-r16 INTEGER ::= 8 -- Maximum number of Tx resource pool for NR sidelink communication and -- discovery maxNrofPoolID-r16 INTEGER ::= 16 -- Maximum index of resource pool for NR sidelink communication and -- discovery maxNrofSRS-PathlossReferenceRS-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for SRS power control. maxNrofSRS-PathlossReferenceRS-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for SRS power control -- minus 1. maxNrofSRS-ResourceSets INTEGER ::= 16 -- Maximum number of SRS resource sets in a BWP. maxNrofSRS-ResourceSets-1 INTEGER ::= 15 -- Maximum number of SRS resource sets in a BWP minus 1. maxNrofSRS-PosResourceSets-r16 INTEGER ::= 16 -- Maximum number of SRS Positioning resource sets in a BWP. maxNrofSRS-PosResourceSets-1-r16 INTEGER ::= 15 -- Maximum number of SRS Positioning resource sets in a BWP minus 1. maxNrofSRS-Resources INTEGER ::= 64 -- Maximum number of SRS resources. maxNrofSRS-Resources-1 INTEGER ::= 63 -- Maximum number of SRS resources minus 1. maxNrofSRS-PosResources-r16 INTEGER ::= 64 -- Maximum number of SRS Positioning resources. maxNrofSRS-PosResources-1-r16 INTEGER ::= 63 -- Maximum number of SRS Positioning resources minus 1. maxNrofSRS-ResourcesPerSet INTEGER ::= 16 -- Maximum number of SRS resources in an SRS resource set maxNrofSRS-TriggerStates-1 INTEGER ::= 3 -- Maximum number of SRS trigger states minus 1, i.e., the largest code point. maxNrofSRS-TriggerStates-2 INTEGER ::= 2 -- Maximum number of SRS trigger states minus 2. maxRAT-CapabilityContainers INTEGER ::= 8 -- Maximum number of interworking RAT containers (incl NR and MRDC) maxSimultaneousBands INTEGER ::= 32 -- Maximum number of simultaneously aggregated bands maxSimultaneousBands-2-r18 INTEGER ::= 30 -- Maximum number of simultaneously aggregated bands minus 2. maxULTxSwitchingBandPairs INTEGER ::= 32 -- Maximum number of band pairs supporting dynamic UL Tx switching in a band -- combination. maxULTxSwitchingBetweenBandPairs-r18 INTEGER ::= 32 -- Maximum number of combinations of a band pair and another band pair/band -- between which dynamic UL Tx switching requires additional switching -- period. maxSchedulingBandCombination-r18 INTEGER ::= 32 -- Maximum number of combinations of scheduling cell and co-scheduled cells -- have same or different carrier type. maxNrofSlotFormatCombinationsPerSet INTEGER ::= 512 -- Maximum number of Slot Format Combinations in a SF-Set. maxNrofSlotFormatCombinationsPerSet-1 INTEGER ::= 511 -- Maximum number of Slot Format Combinations in a SF-Set minus 1. maxNrofTrafficPattern-r16 INTEGER ::= 8 -- Maximum number of Traffic Pattern for NR sidelink communication. maxNrofPUCCH-Resources INTEGER ::= 128 maxNrofPUCCH-Resources-1 INTEGER ::= 127 maxNrofPUCCH-ResourceSets INTEGER ::= 4 -- Maximum number of PUCCH Resource Sets maxNrofPUCCH-ResourceSets-1 INTEGER ::= 3 -- Maximum number of PUCCH Resource Sets minus 1. maxNrofPUCCH-ResourcesPerSet INTEGER ::= 32 -- Maximum number of PUCCH Resources per PUCCH-ResourceSet maxNrofPUCCH-P0-PerSet INTEGER ::= 8 -- Maximum number of P0-pucch present in a p0-pucch set maxNrofPUCCH-PathlossReferenceRSs INTEGER ::= 4 -- Maximum number of RSs used as pathloss reference for PUCCH power control. maxNrofPUCCH-PathlossReferenceRSs-1 INTEGER ::= 3 -- Maximum number of RSs used as pathloss reference for PUCCH power control -- minus 1. maxNrofPUCCH-PathlossReferenceRSs-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUCCH power control -- extended. maxNrofPUCCH-PathlossReferenceRSs-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUCCH power control -- minus 1 extended. maxNrofPUCCH-PathlossReferenceRSs-1-r17 INTEGER ::= 7 -- Maximum number of RSs used as pathloss reference for PUCCH power control -- minus 1. maxNrofPUCCH-PathlossReferenceRSsDiff-r16 INTEGER ::= 60 -- Difference between the extended maximum and the non-extended maximum maxNrofPUCCH-ResourceGroups-r16 INTEGER ::= 4 -- Maximum number of PUCCH resources groups. maxNrofPUCCH-ResourcesPerGroup-r16 INTEGER ::= 128 -- Maximum number of PUCCH resources in a PUCCH group. maxNrofPowerControlSetInfos-r17 INTEGER ::= 8 -- Maximum number of PUCCH power control set infos maxNrofMultiplePUSCHs-r16 INTEGER ::= 8 -- Maximum number of multiple PUSCHs in PUSCH TDRA list maxNrofP0-PUSCH-AlphaSets INTEGER ::= 30 -- Maximum number of P0-pusch-alpha-sets (see TS 38.213 [13], clause 7.1) maxNrofP0-PUSCH-AlphaSets-1 INTEGER ::= 29 -- Maximum number of P0-pusch-alpha-sets minus 1 (see TS 38.213 [13], clause 7.1) maxNrofPUSCH-PathlossReferenceRSs INTEGER ::= 4 -- Maximum number of RSs used as pathloss reference for PUSCH power control. maxNrofPUSCH-PathlossReferenceRSs-1 INTEGER ::= 3 -- Maximum number of RSs used as pathloss reference for PUSCH power control -- minus 1. maxNrofPUSCH-PathlossReferenceRSs-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUSCH power control -- extended maxNrofPUSCH-PathlossReferenceRSs-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUSCH power control -- extended minus 1 maxNrofPUSCH-PathlossReferenceRSsDiff-r16 INTEGER ::= 60 -- Difference between maxNrofPUSCH-PathlossReferenceRSs-r16 and -- maxNrofPUSCH-PathlossReferenceRSs maxNrofPathlossReferenceRSs-r17 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUSCH, PUCCH, SRS -- power control for unified TCI state operation maxNrofPathlossReferenceRSs-1-r17 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUSCH, PUCCH, SRS -- power control for unified TCI state operation minus 1 maxNrofNAICS-Entries INTEGER ::= 8 -- Maximum number of supported NAICS capability set maxBands INTEGER ::= 1024 -- Maximum number of supported bands in UE capability. maxBandsMRDC INTEGER ::= 1280 maxBandsEUTRA INTEGER ::= 256 maxCellReport INTEGER ::= 8 maxDRB INTEGER ::= 29 -- Maximum number of DRBs (that can be added in DRB-ToAddModList). maxFreq INTEGER ::= 8 -- Max number of frequencies. maxFreqLayers INTEGER ::= 4 -- Max number of frequency layers. maxFreqPlus1 INTEGER ::= 9 -- Max number of frequencies for Slicing. maxFreqIDC-r16 INTEGER ::= 128 -- Max number of frequencies for IDC indication. maxCombIDC-r16 INTEGER ::= 128 -- Max number of reported UL CA for IDC indication. maxFreqIDC-MRDC INTEGER ::= 32 -- Maximum number of candidate NR frequencies for MR-DC IDC indication maxNrofCandidateBeams INTEGER ::= 16 -- Max number of PRACH-ResourceDedicatedBFR in BFR config. maxNrofCandidateBeams-r16 INTEGER ::= 64 -- Max number of candidate beam resources in BFR config. maxNrofCandidateBeamsExt-r16 INTEGER ::= 48 -- Max number of PRACH-ResourceDedicatedBFR in the CandidateBeamRSListExt maxNrofPCIsPerSMTC INTEGER ::= 64 -- Maximum number of PCIs per SMTC. maxNrofQFIs INTEGER ::= 64 maxNrofResourceAvailabilityPerCombination-r16 INTEGER ::= 256 maxNrOfSemiPersistentPUSCH-Triggers INTEGER ::= 64 -- Maximum number of triggers for semi persistent reporting on PUSCH maxNrofSR-Resources INTEGER ::= 8 -- Maximum number of SR resources per BWP in a cell. maxNrofSlotFormatsPerCombination INTEGER ::= 256 maxNrofSpatialRelationInfos INTEGER ::= 8 maxNrofSpatialRelationInfos-plus-1 INTEGER ::= 9 maxNrofSpatialRelationInfos-r16 INTEGER ::= 64 maxNrofSpatialRelationInfosDiff-r16 INTEGER ::= 56 -- Difference between maxNrofSpatialRelationInfos-r16 and maxNrofSpatialRelationInfos maxNrofIndexesToReport INTEGER ::= 32 maxNrofIndexesToReport2 INTEGER ::= 64 maxNrofSSBs-r16 INTEGER ::= 64 -- Maximum number of SSB resources in a resource set. maxNrofSSBs-1 INTEGER ::= 63 -- Maximum number of SSB resources in a resource set minus 1. maxNrofS-NSSAI INTEGER ::= 8 -- Maximum number of S-NSSAI. maxNrofTCI-StatesPDCCH INTEGER ::= 64 maxNrofTCI-States INTEGER ::= 128 -- Maximum number of TCI states. maxNrofTCI-States-1 INTEGER ::= 127 -- Maximum number of TCI states minus 1. maxUL-TCI-r17 INTEGER ::= 64 -- Maximum number of TCI states. maxUL-TCI-1-r17 INTEGER ::= 63 -- Maximum number of TCI states minus 1. maxNrofAdditionalPCI-r17 INTEGER ::= 7 -- Maximum number of additional PCI maxNrofAdditionalPRACHConfigs-r18 INTEGER ::= 7 -- Maximum number of additional PRACH configurations for 2TA maxNrofdelayD-r18 INTEGER ::= 4 -- Maximum number of delayD values. maxMPE-Resources-r17 INTEGER ::= 64 -- Maximum number of pooled MPE resources maxNrofUL-Allocations INTEGER ::= 16 -- Maximum number of PUSCH time domain resource allocations. maxQFI INTEGER ::= 63 maxRA-CSIRS-Resources INTEGER ::= 96 maxRA-OccasionsPerCSIRS INTEGER ::= 64 -- Maximum number of RA occasions for one CSI-RS maxRA-Occasions-1 INTEGER ::= 511 -- Maximum number of RA occasions in the system maxRA-SSB-Resources INTEGER ::= 64 maxSCSs INTEGER ::= 5 maxSecondaryCellGroups INTEGER ::= 3 maxNrofServingCellsEUTRA INTEGER ::= 32 maxMBSFN-Allocations INTEGER ::= 8 maxNrofMultiBands INTEGER ::= 8 maxCellSFTD INTEGER ::= 3 -- Maximum number of cells for SFTD reporting maxReportConfigId INTEGER ::= 64 maxNrofCodebooks INTEGER ::= 16 -- Maximum number of codebooks supported by the UE maxNrofCSI-RS-ResourcesExt-r16 INTEGER ::= 16 -- Maximum number of codebook resources supported by the UE for eType2/Codebook combo maxNrofCSI-RS-ResourcesExt-r17 INTEGER ::= 8 -- Maximum number of codebook resources for fetype2R1 and fetype2R2 maxNrofCSI-RS-Resources INTEGER ::= 7 -- Maximum number of codebook resources supported by the UE maxNrofCSI-RS-ResourcesAlt-r16 INTEGER ::= 512 -- Maximum number of alternative codebook resources supported by the UE maxNrofCSI-RS-ResourcesAlt-1-r16 INTEGER ::= 511 -- Maximum number of alternative codebook resources supported by the UE minus 1 maxNrofSRI-PUSCH-Mappings INTEGER ::= 16 maxNrofSRI-PUSCH-Mappings-1 INTEGER ::= 15 maxSIB INTEGER::= 32 -- Maximum number of SIBs maxSI-Message INTEGER::= 32 -- Maximum number of SI messages maxSIB-MessagePlus1-r17 INTEGER::= 33 -- Maximum number of SIB messages plus 1 maxPO-perPF INTEGER ::= 4 -- Maximum number of paging occasion per paging frame maxPEI-perPF-r17 INTEGER ::= 4 -- Maximum number of PEI occasion per paging frame maxAccessCat-1 INTEGER ::= 63 -- Maximum number of Access Categories minus 1 maxBarringInfoSet INTEGER ::= 8 -- Maximum number of access control parameter sets maxCellEUTRA INTEGER ::= 8 -- Maximum number of E-UTRA cells in SIB list maxEUTRA-Carrier INTEGER ::= 8 -- Maximum number of E-UTRA carriers in SIB list maxPLMNIdentities INTEGER ::= 8 -- Maximum number of PLMN identities in RAN area configurations maxDownlinkFeatureSets INTEGER ::= 1024 -- (for NR DL) Total number of FeatureSets (size of the pool) maxUplinkFeatureSets INTEGER ::= 1024 -- (for NR UL) Total number of FeatureSets (size of the pool) maxEUTRA-DL-FeatureSets INTEGER ::= 256 -- (for E-UTRA) Total number of FeatureSets (size of the pool) maxEUTRA-UL-FeatureSets INTEGER ::= 256 -- (for E-UTRA) Total number of FeatureSets (size of the pool) maxFeatureSetsPerBand INTEGER ::= 128 -- (for NR) The number of feature sets associated with one band. maxPerCC-FeatureSets INTEGER ::= 1024 -- (for NR) Total number of CC-specific FeatureSets (size of the pool) maxFeatureSetCombinations INTEGER ::= 1024 -- (for MR-DC/NR)Total number of Feature set combinations (size of the pool) maxInterRAT-RSTD-Freq INTEGER ::= 3 maxGIN-r17 INTEGER ::= 24 -- Maximum number of broadcast GINs maxHRNN-Len-r16 INTEGER ::= 48 -- Maximum length of HRNNs maxNPN-r16 INTEGER ::= 12 -- Maximum number of NPNs broadcast and reported by UE at establishment maxSNPN-ConfigCellId-r18 INTEGER ::= 32 -- Maximum number of Cell ID subject for SNPNS for MDT scope maxSNPN-ConfigID-r18 INTEGER ::= 16 -- Maximum number of SNPNs subject for MDT scope maxSNPN-ConfigTAI-r18 INTEGER ::= 8 -- Maximum number of TA subject for MDT scope maxNrOfMinSchedulingOffsetValues-r16 INTEGER ::= 2 -- Maximum number of min. scheduling offset (K0/K2) configurations maxK0-SchedulingOffset-r16 INTEGER ::= 16 -- Maximum number of slots configured as min. scheduling offset (K0) maxK2-SchedulingOffset-r16 INTEGER ::= 16 -- Maximum number of slots configured as min. scheduling offset (K2) maxK0-SchedulingOffset-r17 INTEGER ::= 64 -- Maximum number of slots configured as min. scheduling offset (K0) maxK2-SchedulingOffset-r17 INTEGER ::= 64 -- Maximum number of slots configured as min. scheduling offset (K2) maxDCI-2-6-Size-r16 INTEGER ::= 140 -- Maximum size of DCI format 2-6 maxDCI-2-7-Size-r17 INTEGER ::= 43 -- Maximum size of DCI format 2-7 maxDCI-2-6-Size-1-r16 INTEGER ::= 139 -- Maximum DCI format 2-6 size minus 1 maxDCI-2-9-Size-r18 INTEGER ::= 140 -- Maximum DCI format 2-9 size maxDCI-2-9-Size-1-r18 INTEGER ::= 139 -- Maximum DCI format 2-9 size minus 1 maxNrofUL-Allocations-r16 INTEGER ::= 64 -- Maximum number of PUSCH time domain resource allocations maxNrofUL-Allocations-1-r18 INTEGER ::= 63 -- Maximum number of PUSCH time domain resource allocations minus 1 maxNrofP0-PUSCH-Set-r16 INTEGER ::= 2 -- Maximum number of P0 PUSCH set(s) maxOnDemandSIB-r16 INTEGER ::= 8 -- Maximum number of SIB(s) that can be requested on-demand maxOnDemandPosSIB-r16 INTEGER ::= 32 -- Maximum number of posSIB(s) that can be requested on-demand maxCI-DCI-PayloadSize-r16 INTEGER ::= 126 -- Maximum number of the DCI size for CI maxCI-DCI-PayloadSize-1-r16 INTEGER ::= 125 -- Maximum number of the DCI size for CI minus 1 maxUu-RelayRLC-ChannelID-r17 INTEGER ::= 32 -- Maximum value of Uu Relay RLC channel ID maxWLAN-Id-Report-r16 INTEGER ::= 32 -- Maximum number of WLAN IDs to report maxWLAN-Name-r16 INTEGER ::= 4 -- Maximum number of WLAN name maxRAReport-r16 INTEGER ::= 8 -- Maximum number of RA procedures information to be included in the RA report maxTxConfig-r16 INTEGER ::= 64 -- Maximum number of sidelink transmission parameters configurations maxTxConfig-1-r16 INTEGER ::= 63 -- Maximum number of sidelink transmission parameters configurations minus 1 maxPSSCH-TxConfig-r16 INTEGER ::= 16 -- Maximum number of PSSCH TX configurations maxNrofCLI-RSSI-Resources-r16 INTEGER ::= 64 -- Maximum number of CLI-RSSI resources for UE maxNrofCLI-RSSI-Resources-1-r16 INTEGER ::= 63 -- Maximum number of CLI-RSSI resources for UE minus 1 maxNrofCLI-SRS-Resources-r16 INTEGER ::= 32 -- Maximum number of SRS resources for CLI measurement for UE maxCLI-Report-r16 INTEGER ::= 8 maxNrofCC-Group-r17 INTEGER ::= 16 -- Maximum number of CC groups for DC location report maxNrofConfiguredGrantConfig-r16 INTEGER ::= 12 -- Maximum number of configured grant configurations per BWP maxNrofConfiguredGrantConfig-1-r16 INTEGER ::= 11 -- Maximum number of configured grant configurations per BWP minus 1 maxNrofCG-Type2DeactivationState INTEGER ::= 16 -- Maximum number of deactivation state for type 2 configured grants per BWP maxNrofConfiguredGrantConfigMAC-1-r16 INTEGER ::= 31 -- Maximum number of configured grant configurations per MAC entity minus 1 maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18 INTEGER ::= 8 -- Maximum number of CSI report subconfigurations per CSI report -- configuration maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-1-r18 INTEGER ::= 7 -- Maximum number of CSI report subconfigurations per CSI report -- configuration minus 1 maxNrofSPS-Config-r16 INTEGER ::= 8 -- Maximum number of SPS configurations per BWP maxNrofSPS-Config-1-r16 INTEGER ::= 7 -- Maximum number of SPS configurations per BWP minus 1 maxNrofSPS-DeactivationState INTEGER ::= 16 -- Maximum number of deactivation state for SPS per BWP maxNrofPPW-Config-r17 INTEGER ::= 4 -- Maximum number of Preconfigured PRS processing windows per DL BWP maxNrofPPW-ID-1-r17 INTEGER ::= 15 -- Maximum number of Preconfigured PRS processing windows minus 1 maxNrOfTxTEGReport-r17 INTEGER ::= 256 -- Maximum number of UE Tx Timing Error Group Report maxNrOfTxTEG-ID-1-r17 INTEGER ::= 7 -- Maximum number of UE Tx Timing Error Group ID minus 1 maxNrofPagingSubgroups-r17 INTEGER ::= 8 -- Maximum number of paging subgroups per paging occasion maxNrofPUCCH-ResourceGroups-1-r16 INTEGER ::= 3 maxNrofReqComDC-Location-r17 INTEGER ::= 128 -- Maximum number of requested carriers/BWPs combinations for DC location -- report maxNrofServingCellsTCI-r16 INTEGER ::= 32 -- Maximum number of serving cells in simultaneousTCI-UpdateList maxNrofTxDC-TwoCarrier-r16 INTEGER ::= 64 -- Maximum number of UL Tx DC locations reported by the UE for 2CC uplink CA maxNrofRB-SetGroups-r17 INTEGER ::= 8 -- Maximum number of RB set groups maxNrofRB-Sets-r17 INTEGER ::= 8 -- Maximum number of RB sets maxNrofEnhType3HARQ-ACK-r17 INTEGER ::= 8 -- Maximum number of enhanced type 3 HARQ-ACK codebook maxNrofEnhType3HARQ-ACK-1-r17 INTEGER ::= 7 -- Maximum number of enhanced type 3 HARQ-ACK codebook minus 1 maxNrofPRS-ResourcesPerSet-r17 INTEGER ::= 64 -- Maximum number of PRS resources for one set maxNrofPRS-ResourcesPerSet-1-r17 INTEGER ::= 63 -- Maximum number of PRS resources for one set minus 1 maxNrofPRS-ResourceOffsetValue-1-r17 INTEGER ::= 511 maxNrofGapId-r17 INTEGER ::= 8 -- Maximum number of measurement gap ID maxNrofPreConfigPosGapId-r17 INTEGER ::= 16 -- Maximum number of preconfigured positioning measurement gap maxNrOfGapPri-r17 INTEGER ::= 16 -- Maximum number of gap priority level maxCEFReport-r17 INTEGER ::= 4 -- Maximum number of CEF reports by the UE maxNrofMultiplePDSCHs-r17 INTEGER ::= 8 -- Maximum number of PDSCHs in PDSCH TDRA list maxSliceInfo-r17 INTEGER ::= 8 -- Maximum number of NSAGs maxCellSlice-r17 INTEGER ::= 16 -- Maximum number of cells supporting the NSAG maxNrofTRS-ResourceSets-r17 INTEGER ::= 64 -- Maximum number of TRS resource sets maxNrofSearchSpaceGroups-1-r17 INTEGER ::= 2 -- Maximum number of search space groups minus 1 maxNrofRemoteUE-r17 INTEGER ::= 32 -- Maximum number of connected L2 U2N Remote UEs maxDCI-4-2-Size-r17 INTEGER ::= 140 -- Maximum size of DCI format 4-2 maxFreqMBS-r17 INTEGER ::= 16 -- Maximum number of MBS frequencies reported in MBSInterestIndication maxNrofDRX-ConfigPTM-r17 INTEGER ::= 64 -- Max number of DRX configuration for PTM provided in MBS broadcast in a -- cell maxNrofDRX-ConfigPTM-1-r17 INTEGER ::= 63 -- Max number of DRX configuration for PTM provided in MBS broadcast in a -- cell minus 1 maxNrofMBS-ServiceListPerUE-r17 INTEGER ::= 16 -- Maximum number of services which the UE can include in the MBS interest -- indication maxNrofMBS-Session-r17 INTEGER ::= 1024 -- Maximum number of MBS sessions provided in MBS broadcast or multicast in -- a cell maxNrofMTCH-SSB-MappingWindow-r17 INTEGER ::= 16 -- Maximum number of MTCH to SSB beam mapping pattern maxNrofMTCH-SSB-MappingWindow-1-r17 INTEGER ::= 15 -- Maximum number of MTCH to SSB beam mapping pattern minus 1 maxNrofMRB-Broadcast-r17 INTEGER ::= 4 -- Maximum number of broadcast MRBs configured for one MBS broadcast service maxNrofPageGroup-r17 INTEGER ::= 32 -- Maximum number of paging groups in a paging message maxNrofPDSCH-ConfigPTM-r17 INTEGER ::= 16 -- Maximum number of PDSCH configuration groups for PTM maxNrofPDSCH-ConfigPTM-1-r17 INTEGER ::= 15 -- Maximum number of PDSCH configuration groups for PTM minus 1 maxG-RNTI-r17 INTEGER ::= 16 -- Maximum number of G-RNTI that can be configured for a UE. maxG-RNTI-1-r17 INTEGER ::= 15 -- Maximum number of G-RNTI that can be configured for a UE minus 1. maxG-CS-RNTI-r17 INTEGER ::= 8 -- Maximum number of G-CS-RNTI that can be configured for a UE. maxG-CS-RNTI-1-r17 INTEGER ::= 7 -- Maximum number of G-CS-RNTI that can be configured for a UE minus 1. maxMRB-r17 INTEGER ::= 32 -- Maximum number of multicast MRBs (that can be added in MRB-ToAddModLIst) maxFSAI-MBS-r17 INTEGER ::= 64 -- Maximum number of MBS frequency selection area identities maxNeighCellMBS-r17 INTEGER ::= 8 -- Maximum number of MBS broadcast neighbour cells maxNrofPdcch-BlindDetectionMixed-1-r16 INTEGER ::= 7 -- Maximum number of combinations of mixed Rel-16 and Rel-15 PDCCH -- monitoring capabilities minus 1 maxNrofPdcch-BlindDetection-r17 INTEGER ::= 16 -- Maximum number of combinations of PDCCH blind detection monitoring -- capabilities maxNrofAltitudeRanges-r18 INTEGER ::= 8 -- Maximum number of altitude ranges for altitude-based measurement configurations maxWayPoint-r18 INTEGER ::= 20 -- Maximum number of flight path information waypoints maxAltitude-r18 INTEGER ::= 10000 -- Maximum altitude in meters minAltitude-r18 INTEGER ::= -420 -- Minimum altitude in meters maxMeasSequence-r18 INTEGER ::= 64 -- Maximum number of configured sequence for measurement maxNrofHops-1-r18 INTEGER ::= 5 -- Maximum number of Hops that can be configured for Positioning SRS Transmission maxNrOfCellsInVA-r18 INTEGER ::= 16 -- Maximum number of cells in validity area for Positioning SRS maxNrOfCellsInVA-Ext-r18 INTEGER ::= 16 -- Maximum number of additional cells in validity area for Positioning SRS maxNrOfLinkedSRS-PosResourceSet-r18 INTEGER ::= 3 -- Maximum number of linked SRSPosResourceSets that can be aggregated across -- CCs maxNrOfLinkedSRS-PosResSetComb-r18 INTEGER ::= 32 -- Maximum number of combinations of linked SRSPosResourceSets that can be -- aggregated in RRC_CONNECTED state maxNrOfLinkedSRS-PosResSetCombInactive-r18 INTEGER ::= 16 -- Maximum number of combinations of linked SRSPosResourceSets that can be -- aggregated in RRC_INACTIVE state maxCBR-ConfigDedSL-PRS-1-r18 INTEGER ::= 7 -- Maximum number of CBR ranges for dedicated SL PRS resource pool maxCBR-LevelDedSL-PRS-1-r18 INTEGER ::= 15 -- Maximum number of CBR levels for dedicated SL PRS resource pool maxNrofSL-PRS-TxPool-r18 INTEGER ::= 8 -- Maximum number of Tx dedicated SL-PRS resource pool for NR sidelink positioning maxNrofSL-PRS-TxConfig-r18 INTEGER ::= 64 -- Maximum number of SL PRS transmission parameter configurations maxNrOfVA-r18 INTEGER ::= 16 -- Maximum number of validity area maxNrofLTM-Configs-r18 INTEGER ::= 8 -- Maximum number of LTM candidate cells maxNrofLTM-Configs-plus1-r18 INTEGER ::= 9 -- Maximum number of LTM candidate cells plus 1 maxNrofLTM-CSI-ReportConfigurations-r18 INTEGER ::= 48 -- Maximum number of LTM CSI reporting configurations maxNrofLTM-CSI-ReportConfigurations-1-r18 INTEGER ::= 47 -- Maximum number of LTM CSI reporting configurations minus 1 maxNrofLTM-CSI-SSB-ResourcesPerSet-r18 INTEGER ::= 512 -- Maximum number of LTM CSI SSB resource per set maxNrofLTM-CSI-ResourceConfigurations-r18 INTEGER ::= 112 -- Maximum number of LTM CSI resource configurations maxNrofLTM-CSI-ResourceConfigurations-1-r18 INTEGER ::= 111 -- Maximum number of LTM CSI resource configurations minus 1 maxNrofCandidateTCI-State-r18 INTEGER ::= 128 -- Maximum number of LTM TCI states maxNrofCandidateUL-TCI-r18 INTEGER ::= 64 -- Maximum number of LTM UL TCI states maxSecurityCellSet-r18 INTEGER ::= 9 -- Maximum number of cell sets for subsequent CPAC. maxSK-Counter-r18 INTEGER ::= 8 -- Maximum number of SK-counters configured for a cell set for subsequent CPAC. maxNrofThresholdMBS-r18 INTEGER ::= 8 -- Max number of thresholds of MBS sessions for RRC connection resume for a -- UE receiving multicast in RRC_INACTIVE maxNrofThresholdMBS-1-r18 INTEGER ::= 7 -- Max number of thresholds of MBS sessions for RRC connection resume for a -- UE receiving multicast in RRC_INACTIVE minus 1 maxTN-AreaInfo-r18 INTEGER ::= 32 -- Maximum number of TN coverage areas for which assistance info is -- provided in an NTN cell maxNrofSetsOfCells-r18 INTEGER ::= 4 -- Maximum number of sets of cells for multi-cell PDSCH/PUSCH scheduling maxNrofSetsOfCells-1-r18 INTEGER ::= 3 -- Maximum number of sets of cells for multi-cell PDSCH/PUSCH scheduling -- minus 1 maxNrofCellsInSet-r18 INTEGER ::= 4 -- Maximum number of cells configured in a set of cells for multi-cell -- PDSCH/PUSCH scheduling maxNrofCellsInSet-1-r18 INTEGER ::= 3 -- Maximum number of cells configured in a set of cells for multi-cell -- PDSCH/PUSCH scheduling minus 1 maxNrofCellCombos-r18 INTEGER ::= 16 -- Maximum number of combinations of co-scheduled cells for multi-cell -- PDSCH/PUSCH scheduling maxNrofBWPsInSetOfCells-r18 INTEGER ::= 16 -- Maximum number of BWPs configured in a set of cells for multi-cell -- PDSCH/PUSCH scheduling maxLowerMSD-r18 INTEGER ::= 256 -- Maximum number of lower MSD capability sets for a victim band maxLowerMSDInfo-r18 INTEGER ::= 64 -- Maximum number of lower MSD capability sets for a band combination maxNrofIntraEndc-Components-r17 INTEGER ::= 4 -- Maximum number of intra-band (NG)EN-DC band components in an inter-band -- (NG)EN-DC band combination -- TAG-MULTIPLICITY-AND-TYPE-CONSTRAINT-DEFINITIONS-STOP -- ASN1STOP – End of NR-RRC-Definitions -- ASN1START END -- ASN1STOP
R2-2503945 Discussion on adaptation of common signalsú»channels transmissions.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2503945 St. Julian’s, Malta, 19 - 23 May, 2025 Source: Huawei, HiSilicon Title: Discussion on adaptation of common signal/channel transmissions Agenda Item: 8.5.4 Document for: Discussion and decision
Conclusion In this contribution, we discussed the adaptation of common signal/channel transmissions, and made the following proposals: Proposal 1: Add the clarification “The UE supporting paging adaptation ignores this field in RRC_CONNECTED” into the field descriptions of pagingAdaptation-NS and pagingAdaptationNAndPagingFrameOffset. Proposal 2: RAN2 to discuss whether RRC_CONNECTED UE ignores the R19 PEI configuration. Proposal 3: A new firstPDCCH-MonitoringOccasionOfPO-r19 is added, value range is extended to “(0..143359)” to accommodate SCS=480kHz and N=T/32. Proposal 4: A separate pei-ConfigBWP is introduced, which contains pei-SearchSpace and firstPDCCH-MonitoringOccasionOfPEI-O-r19. The value range of firstPDCCH-MonitoringOccasionOfPEI-O-r19 is extended to “(0..143359)” to accommodate SCS=480kHz and N=T/32. Observation 1: In the existing spec, PEI is associated to at most 2 PFs, at most 8 POs, based on the assumption that each PF has at most 4 POs. The restriction is a trade-off between PEI overhead and paging latency. Proposal 5: Extend POnumPerPEI to 16 to maintain the same principle as R17 that PEI can be associated with 2 PFs. Proposal 6: New RACH-ConfigCommon is added in BWP-ConfigCommon for R19 NES UEs. Proposal 7: RAN2 to down-select from the following for (e)Redcap UEs: Option 1: A Redcap-specific R19 RACH-ConfigCommon is added to BWP-UplinkCommon; Option 2: An NES-specific RACH-ConfigCommon is added to AdditionalRACH-Config-r17; Option 3: RACH adaptation is not supported for (e)Redcap UEs. The similar approach applies to other RA features (e.g. SDT, Slicing). Proposal 8: RAN2 to discuss whether the RA procedure can be terminated earlier if the selected RA resource is deactivated. Proposal 9: Reply to RAN1 that it is feasible to use one of the spare bits in short message to indicate the availability of additional RO. Proposal 10: The additional SMTC configured on SSB for SSB adaptation is used for serving cell and intra-frequency neighbour cell measurements upon receiving DCI 2_9. Proposal 11: RAN2 does not aim at a unified L3 RRM measurement design for both OD-SSB and SSB adaptation.
R2-2503968 Issue for additional PRACH resources with multiple initial BWPs.doc
TDoc file reading error

R2-2504038_Discussion on adaptation of common signal transmissions.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2504038 St.Julian, Malta, May 19th – 23rd, 2025 Agenda Item: 8.5.4 Source: vivo Title: Discussion on adaptation of common signal transmissions Document for: Discussion and Decision
Conclusion Based on the discussion, we have the following proposals: Adaptation of paging occasions in the time domain Proposal 1: For signaling overhead optimization of Rel-19 firstPDCCH-MonitoringOccasionOfPO, RAN2 to discuss the following options: Option 1: restrict the maximum value range of Rel-19 firstPDCCH-MonitoringOccasionOfPO for different SCS corresponding to the Rel-19 nAndPagingFrameOffset (i.e. N); Option 2: support configuring evenly distributed POs, i.e., the first PO position among 8 POs and the interval between them. Proposal 2: Introduce a separate pei-ConfigBWP for paging adaptation. FFS whether to introduce a new maxPEI-perPF-r19. Proposal 3: If P1 is agreed, similar handling of Rel-19 firstPDCCH-MonitoringOccasionOfPO is also applied to Rel-19 firstPDCCH-MonitoringOccasionOfPEI-O-r17. Adaptation of RACH adaptation in the time domain Proposal 4：It is feasible to use one bit from the Bits 5-8 within the Short Message field for DCI-based adaptation for additional PRACH resources for RRC_IDLE/INACTIVE/CONNECTED UEs. Proposal 5：UEs in RRC_CONNECTED monitor for additional RACH resources availability indication in any paging occasion at least once per modification period if the UE is provided with common search space on the active BWP to monitor paging.
R2-2504055.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2504055 St.Julians, Malta, May 19th – 23rd, 2025 Agenda Item: 8.5.4 Source: Sony Title: RA-RNTI issue and RACH adaptations Document for: Discussion
Conclusion We propose RAN2 to discuss following proposals: Proposal 1: The additional PRACH resources for RACH adaptation should be included in a SIB. Proposal 2: To avoid RNTI collision/confusion, simply introduce a configurable offset for the symbol index (s_id) in the RNTI equation, and the offset is signalled in SIB1 as a part of additional PRACH resources for RACH adaptation for NES -capable UEs.
R2-2504244_Discussion_on_Adaptation_Common_Signal_Channel.docx
3GPP TSG RAN WG2 Meeting #130 R2-2504244 St. Julians, Malta, May 19th – 23rd, 2025 Agenda item: 8.5.4 Source: Qualcomm Incorporated Title: Discussion on Adaptation of Common Signal/Channel Transmissions WID/SID: Netw_Energy_NR_enh-Core – Release 19 Document for: Discussion
Conclusion In this contribution, we discussed PEI with paging adaptation in time and BFR using additional ROs with PRACH adaptation in time and concluded with the following observations and proposals. Adaptation of paging in time domain Proposal 1. A new PEI configuration supporting Release 19 paging adaptation contains at least the following parameters po-NumPerPEI-r19 firstPDCCH-MonitoringOccasionOfPEI-O-r19 Proposal 2. RAN2 introduces a new UE capability for Rel 19 PEI based on paging adaptation in time. Adaptation of PRACH in time domain Observation 1. For BFR, a UE needs to monitor DCI 1_0 with P-RNTI in order to use the additional ROs with PRACH adaptation in time. Observation 2. For BFR, a UE needs to receive PDCCH order to use the additional ROs with PRACH adaptation in time.
R2-2504279 (R19 NES WI AI 8.5.4 Time adaptation).docx
3GPP TSG-RAN WG2 Meeting #130 R2-2504279 Malta, May 19 – 23, 2025 Agenda Item: 8.5.4 Source: InterDigital Title: Time domain adaptation of common signalling and channels Document for: Discussion, Decision
Conclusion This contribution addresses time domain adaptation mechanisms for SSBs, PRACH, and paging in the time-domain, with focus on higher layer impacts and assumptions. The following proposals are provided: Proposal 1: RAN2 to consider provisioning additional PRACH resources, e.g. provided in R19 NES PRACH adaptation, to accommodate the increased number of PMOs/paging load within the PF. Observation 1: RAN1 agreed to support adaptation of PRACH in time-domain based on configuring additional PRACH resources for NES-capable UEs in addition to existing PRACH resources for legacy UEs. Those resources are activated by DCI addressed to the UE’s P-RNTI. Observation 2: Time-domain PRACH adaptation is applicable in RRC Idle, Inactive, and connected states. Proposal 2: From a MAC perspective, additional PRACH resources are considered available if a PDCCH activation indication is received by lower layers; otherwise not considered available.
R2-2504388 Discussion on Common signalling adaptation.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2504388 St.Julians, Malta, May 19th – 23rd , 2025 Agenda Item: 8.5.4 Source: CMCC Title: Discussion on Common signalling adaptation Document for: Discussion
Conclusions In this contribution, we analyse the paging adaptation related issues, and the following proposals and observation are made: Proposal 1: A separate pei-ConfigBWP is introduced for the separate PEI. Proposal 2: RAN2 should discuss whether the Rel-19 separate PEI is only configured when the new values for paging adaptation is configured by the network. Proposal 3: The following solutions can be discussed in RAN2 to solve the RA-RNTI collision issue caused by PRACH adaptation: Solution 1: It is up to network implementation to solve this.  Solution 2: A configurable offset of symbol index (s_id) or frequency index (f_id) can be introduced.  Solution 3: An additional offset can be introduced to the formula for computing RA-RNTI, such as: RA-RNTI= 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id + 14 × 80 × 8 × 4
R2-2504420.docx
3GPP TSG RAN WG2 #130 R2-2504420 St Julians, Malta, May 19th – 23rd, 2025 Source: NTT DOCOMO, INC. Title: Discussion on adaptation of common signal and channel Agenda Item: 8.5.4 Document for: Discussion and Decision
Conclusion In this contribution, we provided the following observations and proposals of adaptation of common signal and channel for network energy saving. Proposal 1: For PRACH adaptation mechanism, it is preferable not to support additional PRACH resources that are available via semi-static signaling (i.e., SIB1) only, i.e., support additional PRACH resources that are only available when DCI is indicated. Proposal 2: (RRC-RACH adaptation-1) Prefer to define new RRC parameters of additional PRACH that can be configured differently from the legacy ones only (e.g., PRACH config. index, msg1-FDM and msg1-frequencyStart) under the corresponding legacy IEs (e.g., RACH-ConfigGeneric) Proposal 3: (MAC-2) At least, the following aspects should be captured in MAC spec. for additional PRACH resources. MAC layer would apply new PRACH mask configured by RRC to additional PRACH resources MAC layer can use additional PRACH resources when lower layer indicates that they are available until indicated that they are unavailable.
R2-2504427 - Discussion on adaptation of common signal and channel transmissions.docx
3GPP TSG-RAN WG2 #130 R2-2504427 St. Julian’s, Malta, May 19th– 23rd, 2025 Agenda Item: 8.5.4 Source: Ericsson Title: Adaptation of common signal/channel transmissions for NES Document for: Discussion 1
Conclusion In this contribution we discuss the objective on the adaptation of common signal/channel transmissions. Based on the discussion in the previous sections we made the following observations: Observation 1 RAN2 requires further input from RAN1/RAN4 before finalizing the stage 3 aspects for this objective. Observation 2 Activation of additional PRACH occasions dynamically is supported for UEs in connected and idle/inactive modes. Observation 3 For UEs in idle/inactive mode, additional RA occasions can be activated at paging occasions via DCI 1_0 with P-RNTI as agreed in RAN1. Observation 4 It would be beneficial if gNB assigns a particular instance of the activated adaptive RA resources when paging a UE to balance the load. Observation 5 Option b) introduces significant signalling overhead (~46% larger message size than the respective legacy configuration with T = 128, N = T/16, Ns for legacy = 4, SCS = 15 kHz) even for the case where Ns for Rel-19 UEs is set to 8. Observation 6 The configuration of firstPDCCH-MonitoringOccasionOfPO parameter for Rel-19 UEs at slot level results in 4 octets (~31%) smaller message size than the configuration of firstPDCCH-MonitoringOccasionOfPO parameter for Rel-19 UEs at symbol level. Observation 7 According to the current specifications, max # of paging occasions per PF is four, max # of PFs associated with one PEI monitoring occasions is two, and if one PEI occasion is associated with POs of two PFs, the two PFs are consecutive PFs. Observation 8 Current specifications need to be updated in order to support co-existence of PEI and paging adaptations, i.e. Ns = 8. Observation 9 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. Based on the discussion in the previous section, we propose the following: Proposal 1 Group all newly introduced parameters for configuration of additional PRACH resources in the same IE, e.g., addl-RACH-Config-Adaptation. Proposal 2 Include addI-RACH-Config-Adaptation IE in the existing RACH-ConfigCommon IE. Proposal 3 For UEs in idle/inactive mode additional RA occasions can be activated at SIB1 transmission occasions. Proposal 4 An activated adaptive RA resource can be assigned to an adaptive paging frame/occasion. Proposal 5 If a UE is a public warning capable UE, it monitors the DCI-based adaptation indication at least once every defaultPagingCycle, otherwise at least once every SI modification period. Proposal 6 Use bit 5 within the Short Message field for indication in DCI format 1_0 with P-RNTI. Proposal 7 Adopt the TP below in the running 38.331 CR. Proposal 8 For Rel-19 NES UEs, firstPDCCH-MonitoringOccasionOfPO is configured at slot level. Proposal 9 For all possible values of ssb-periodicityServingCell in the field description of pagingAdaptationNAndPagingFrameOffset IE, the number of total paging frames in T (corresponding to parameter N in TS 38.304 [20]) can be set to oneThirtySecondT value. Proposal 10 For Rel-19 PEI, increase the maximum number of paging occasions per PF to 8. Proposal 11 To support separation of additional Rel-19 PEI transmission occasions from legacy ones, introduce pei-ConfigBWP-r19 for configuration of Rel-19 pei-SearchSpace and firstPDCCH-MonitoringOccasionOfPEI-O. Proposal 12 For Rel-19 PEI configuration, introduce the following parameters: -po-NumPerPEI-r19, -payloadSizeDCI-2-7-r19, -pei-FrameOffset-r19, -subgroupsNumPerPO-r19, -subgroupsNumForUEID-r19, -pei-SearchSpace-R19, -nrofCandidates-PEI-R19, -firstPDCCH-MonitoringOccasionOfPEI-O-R19 Proposal 13 For Rel-19 PEI configuration, use the same value ranges as for legacy PEI for the following parameters: -po-NumPerPEI-r19, -payloadSizeDCI-2-7-r19, -pei-FrameOffset-r19, -subgroupsNumPerPO-r19, -subgroupsNumForUEID-r19, -pei-SearchSpace-R19, -nrofCandidates-PEI-R19 Proposal 14 For Rel-19 NES UEs, firstPDCCH-MonitoringOccasionOfPEI-O is configured at slot level with the same value range as for legacy PEI.
R2-2504471 Discussion on adaptation of common signalchannel transmissions.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2504471 St.Julians, Malta, May 19th – 23rd, 2025 Agenda Item: 8.5.4 Source: HONOR Title: Discussion on adaptation of common signal/channel transmissions Document for: Discussion and decision 1.
Conclusions In this contribution, we made the following observations and proposals: Observations Observation 1: NW wakes up at each PEI-O between PFs to send PEIs, reducing the continuous sleep time that should have been extended due to the extended PF interval. Observation 2: When the collision on legacy resources is already unacceptable, if NES UE continues to access on legacy PRACH resources, it will lead to an access failure. Proposals Paging adaptation in time-domain Proposal 1: (38.331-DownlinkConfigCommonSIB-Issue3) Whether to introduce a separate pei-ConfigBWP including a separate pei-searchSpace is up to RAN1. Proposal 2: (38.331-DownlinkConfigCommonSIB-Issue3) PEI-O clustering/bundling of NES UEs can be considered. RACH adaptation in time-domain Proposal 3: (MAC-Issue2) If the additional PRACH resources is valid, NES UE can adjust the backoff time value received for legacy PRACH resources, e.g., by ignoring or reducing the value of backoff time. Proposal 4: (38.331-RACH adaptation-Issue1) Legacy Power-related parameters (i.e., preambleReceivedTargetPower and powerRampingStep) can be reused for NES UE. Proposal 5: (38.331-RACH adaptation-Issue1) The additional PRACH resources configuration should be in SIB1. Proposal 6: (MAC-Issue2) The validity indication should indicate the validity from the next starting reference point. Proposal 7: (MAC-Issue2) NW can indicate whether the NES UE can use the legacy PRACH resources when the additional PRACH resources is valid.
R2-2504494 Discussion on PRACH adaptation.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2504494 St. Julians, Malta, May. 19th – 23rd, 2025 Agenda Item: 8.5.4 Source: ASUSTeK Title: Discussion on PRACH adaptation Document for: Discussion and Decision
Conclusion Observation 1: RA-RNTI collision could occur when the additional RO and legacy RO are overlapped in time-domain. Proposal 1: Revise the RA-RNTI formula for RACH adaptation, e.g., introducing a new offset in RA-RNTI formula to separate the case that whether the selected RO is additional RO or legacy RO. Proposal 2: BI field corresponding to the additional RO should have a different value compared with BI field corresponding to the legacy RO.
R2-2504579 Remaining issues on common signal and channel transmissions adaptation.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2504579 St.Julians, Malta, 19th May – 23th May, 2025 Agenda Item: 8.5.4 (Netw_Energy_NR-enh-Core) Source: LG Electronics Inc. Title: Remaining issues on common signal and channel transmissions adaptation Document for: Discussion and Decision
Conclusion Regarding adaptation of paging occasions in the time domain Proposal 1 Introduce a separate pei-ConfigBWP for paging adaptation, including both pei-SearchSpace and firstPDCCH-MonitoringOccasionOfPEI-O. Proposal 2 Support association between Rel-19 paged UEs and PRACH resources to distribute RA attempts triggered by paging across multiple PRACH resources. Proposal 3 Configure firstPDCCH-MonitoringOccasionOfPO for paging adaptation in the same manner as in the legacy firstPDCCH-MonitoringOccasionOfPO. Regarding adaptation of PRACH in the time domain Proposal 4 Additional RACH resources are configured in RACH-ConfigCommon IE, and only essential parameters such as PRACH configuration index, msg1-FrequencyStart, msg1-FDM, number of SSB per RO, and CB-PreamblesPerSSB are considered in the configuration. Observation 1 RAN1 agreed that UE is not expected to be configured such that there are more than 8 FDM-ed valid ROs (legacy + additional ROs). The range of f_id (0 ≤ f_id < 8) is enough for indexing 8 FDM-ed valid ROs. Proposal 5 Use the existing equation for RA-RNTI computation below for the case that legacy ROs and additional ROs overlap in time domain: RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id Proposal 6 ROs are numbered from legacy ROs to additional ROs if legacy ROs and additional ROs overlap in time domain. i.e., the lower values of f_id are mapped to the legay ROs and the higher values of f_id are mapped to the additional ROs. 4.

09-May-2025 21:05:53

© 2025 Majid Ghanbarinejad. All rights reserved.