Content for  TS 38.331  Word version:  18.0.0

This field provides barometric pressure measurements as Sensor-MeasurementInformation defined in TS 37.355. The first/leftmost bit of the first octet contains the most significant bit.

This field provides motion sensor measurements as Sensor-MotionInformation defined in TS 37.355. The first/leftmost bit of the first octet contains the most significant bit.

Presence of this field indicates absence on a long term basis (e.g. by level of regulation) of any other technology sharing the carrier; absence of this field indicates the potential presence of any other technology sharing the carrier, as specified in clauses 4.2.1 and 4.2.3 of TS 37.213.

Indicates whether to use the maxEnergyDetectionThreshold or the energyDetectionThresholdOffset (see clause 4.2.3 of TS 37.213).

Indicates the offset to the default maximum energy detection threshold value. Unit in dB. Value -13 corresponds to -13dB, value -12 corresponds to -12dB, and so on (i.e. in steps of 1dB) as specified in clause 4.2.3 of TS 37.213.

Indicates the absolute maximum energy detection threshold value. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm) as specified in clause 4.2.3 of TS 37.213.

The N_TA-Offset2 to be applied for all uplink transmissions on this serving cell associated to tag2. If absent, n-TimingAdvanceOffset is applied for all uplink transmissions on this serving cell associated to tag2.

Maximum energy detection threshold that the UE should use to share channel occupancy with gNB for DL transmission as specified in clause 4.1.3 of TS 37.213 for downlink channel access and clause 4.2.3 for uplink channel access. This field is not applicable in semi-static channel access mode.

List of information for the additional SSB with different PCI than the serving cell PCI. The additional SSBs with different PCIs are not used for serving cell quality derivation.

The duration in ms after which the UE falls back to the default Bandwidth Part (see clause 5.15 of TS 38.321). When the network releases the timer configuration, the UE stops the timer without switching to the default BWP.

Slot offset between the primary cell (PCell/PSCell) and the SCell in unaligned frame boundary with slot alignment and partial SFN alignment inter-band CA. Based on this field, the UE determines the time offset of the SCell as specified in clause 4.5 of TS 38.211. The granularity of this field is determined by the reference SCS for the slot offset (i.e. the maximum of PCell/PSCell lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB and this serving cell's lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB). The Network configures at most single non-zero offset duration in ms (independent on SCS) among CCs in the unaligned CA configuration. If the field is absent, the UE applies the value of 0. The slot offset value can only be changed with SCell release and add.

Indicates whether processing types 1 and 2 based CBG based operation is enabled according to Rel-16 UE capabilities.

Used to configure cell DTX/DRX for the serving cell, as specified in TS 38.321. A maximum of two cell DTX/DRX patterns can be configured per MAC entity for different serving cells. The two configured patterns are aligned, that the start and slot offset are common and the periodicity of one pattern is an integer multiple of the other.

This field is used to configure CJT Tx scheme cjtSchemeA or cjtSchemeB for PDSCH reception, see Reference XXX.

List of parameters used for access procedures of operation with shared spectrum channel access (see TS 37.213.

If present, this field indicates that the UE shall apply channel access procedures for operation with shared spectrum channel access in accordance with clause 4.4 of TS 37.213 for FR2-2. If absent, the UE does not apply these channel access procedures. The network always configures this field if channel access procedures are required for the serving cell within this region by regulations. Overwrites the corresponding field in ServingCellConfigCommon or ServingCellConfigCommonSIB for this serving cell.

Indicates whether this serving cell is cross-carrier scheduled by another serving cell or whether it cross-carrier schedules another serving cell. If the field other is configured for an SpCell (i.e., the SpCell is cross-carrier scheduled by another serving cell), the SpCell can be additionally scheduled by the PDCCH on the SpCell.

If this field is included, the UE shall release the cross carrier scheduling configuration configured by crossCarrierSchedulingConfig. The network may only include either crossCarrierSchedulingConfigRelease or crossCarrierSchedulingConfig at a time.

Indicates how UE performs rate matching when both lte-CRS-PatternList1-r16 and lte-CRS-PatternList2-r16 are configured or when both lte-CRS-PatternList3-r18 and lte-CRS-PatternList4-r18 are configured as specified in clause 5.1.4.2 of TS 38.214.

Indicates how the UE performs periodic and semi-persistent CSI-RS reception in a slot. The presence of this field indicates that the UE uses DCI detection to validate whether to receive CSI-RS (see clause 11.1 of TS 38.213).

The initial bandwidth part is referred to by BWP-Id = 0. ID of the downlink bandwidth part to be used upon expiry of the BWP inactivity timer. This field is UE specific. When the field is absent the UE uses the initial BWP as default BWP. (see clause 12 of TS 38.213, and clause 5.15 of TS 38.321).

Indicates that this serving cell is using directional collision handling between a reference and other cell(s) for half-duplex operation in TDD CA with same SCS as specified in clause 11.1 of TS 38.213. The half-duplex operation only applies within the same frequency range and cell group. The network only configures this field for TDD serving cells that are using the same SCS.

For the IAB-MT, it indicates that this serving cell is using directional collision handling between a reference and other cell(s) for half-duplex operation in TDD NR-DC with same SCS within same cell group or cross different cell groups.

The dormant BWP configuration for an SCell. This field can be configured only for a (non-PUCCH) SCell.

List of additional downlink bandwidth parts to be added or modified. (see clause 12 of TS 38.213).

List of additional downlink bandwidth parts to be released. (see clause 12 of TS 38.213).

A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in DownlinkConfigCommon / DownlinkConfigCommonSIB. Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1, TS 38.101-2, and TS 38.101-5. If the UE is a RedCap UE and needs to autonomously switch to its initial downlink bandwidth part to perform a random access procedure but its current UE specific channel bandwidth does not cover the initial downlink bandwidth part, the UE autonomously changes its UE specific channel bandwidth to cover the initial downlink bandwidth part. In that case, after completion of the random access procedure, the network ensures that the UE specific channel bandwidth fully covers the UE's active downlink bandwidth part in subsequent bandwidth part switch operations.

This field is not used in the specification. If received it shall be ignored by the UE.

Indicates the aperiodic CSI-RS triggering with beam switching triggering behaviour as defined in clause 5.2.1.5.1 of TS 38.214.

Presence of this field indicates the UE shall follow the release 16 behavior of default TCI state per CORESETPoolindex when the UE is configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in ControlResourceSet is enabled.

Presence of this field indicates the UE shall follow the release 16 behavior of two default TCI states for PDSCH when at least one TCI codepoint is mapped to two TCI states is enabled

Indicates the Type-1 HARQ codebook generation as specified in clause 9.1.2.1 of TS 38.213.

If configured for an SpCell, this field contains the ID of the DL BWP to be activated or to be used for RLM, BFD and measurements if included in an RRCReconfiguration message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated, upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If the field is absent for the PSCell at SCG deactivation, the UE considers the previously activated DL BWP as the BWP to be used for RLM, BFD and measurements. If the field is absent for the PSCell at SCG activation, the DL BWP to be activated is the DL BWP previously to be used for RLM, BFD and measurements. If configured for an SCell, this field contains the ID of the downlink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BWP-Id = 0. Upon reconfiguration with reconfigurationWithSync, the network sets the firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id to the same value.

The dedicated (UE-specific) configuration for the initial downlink bandwidth-part (i.e., DL BWP#0). If any of the optional IEs are configured within this IE, the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1

List of intra-cell guard bands in a serving cell for operation with shared spectrum channel access in FR1. If not configured, the guard bands are defined according to 38.101-1 [15], see clause 7 of TS 38.214. For operation in licensed spectrum, this field is absent, and no UE action is required.

A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The network does not configure this field and lte-CRS-ToMatchAround simultaneously.

A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH scheduled with a DCI detected on a CORESET with CORESETPoolIndex configured with 1. This list is configured only if CORESETPoolIndex configured with 1. The first LTE CRS pattern in this list shall be fully overlapping in frequency with the first LTE CRS pattern in lte-CRS-PatternList1, The second LTE CRS pattern in this list shall be fully overlapping in frequency with the second LTE CRS pattern in lte-CRS-PatternList1, and so on. Network configures this field only if the field lte-CRS-ToMatchAround is not configured and there is at least one ControlResourceSet in one DL BWP of this serving cell with coresetPoolIndex set to 1.

A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The network does not configure this field and lte-CRS-ToMatchAround, or this field and lte-CRS-PatternList1, or this field and lte-CRS-PatternList2 simultaneously.

A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The first LTE CRS pattern in this list shall be fully overlapping in frequency with the first LTE CRS pattern in lte-CRS-PatternList3. The second LTE CRS pattern in this list shall be fully overlapping in frequency with the second LTE CRS pattern in lte-CRS-PatternList3, and so on. Network configures this field only if the field lte-CRS-ToMatchAround is not configured and the field lte-CRS-PatternList3 is configured.

Parameters to determine an LTE CRS pattern that the UE shall rate match around.

If the field is not configured, the following default network configuration assumptions are valid for all LTE neighbour cells for the purpose of CRS interference mitigation (CRS-IM) in scenarios with overlapping spectrum for LTE and NR (see TS 38.101-4).

• The CRS port number is the same as the one indicated in RateMatchPatternLTE-CRS if configured for the serving cell.
• The CRS port number is 4 if RateMatchPatternLTE-CRS is not configured for the serving cell.
• The channel bandwidth and centre frequency are the same as the ones indicated in RateMatchPatternLTE-CRS if configured for the serving cell.
• The MBSFN configuration is the same as the one indicated in RateMatchPatternLTE-CRS if configured for the serving cell. If RateMatchPatternLTE-CRS is not configured for the serving cell, MBSFN subframe is not configured.
• Network-based CRS interference mitigation (i.e., CRS muting), as in crs-IntfMitigConfig specified in TS 36.331, is not enabled.

If the field is configured (i.e. false) and LTE-NeighCellsCRS-AssistInfoList is configured, the configuration provided in LTE-NeighCellsCRS-AssistInfoList overrides the default network configuration assumptions. If the field is configured (i.e. false) and LTE-NeighCellsCRS-AssistInfoList is not configured, it is up to the UE implementation whether to apply CRS-IM operation.

List of up to N (N≤4) configurations of set(s) of cells for multi-cell PDSCH/PUSCH scheduling from the serving cell, where N is reported as UE capability and up to 4 sets of cells can be configured per PUCCH group. When this field is configured to a SCell, PCell cannot be included in either ScheduledCellListDCI-1-3 or ScheduledCellListDCI-0-3.

Configures the UE behaviour for Type1 codebook HARQ ACK generation regarding the number of PDSCHs per slot on a serving cell as specified in clause 9.1.2.1 of TS 38.213. When this parameter is configured and set to disabled for a serving cell, the network does not schedule UE with more than one PDSCH in a slot on the serving cell if HARQ-ACKs of any two PDSCHs in the slot on the serving cell are supposed to be reported on one PUCCH resource in the same PUCCH slot. If two coresetPoolIndex values are configured, the number of received PDSCHs is per coresetPoolIndex value per slot for a serving cell. If the UE generates two HARQ-ACK codebooks for two priorities, the number of received PDSCHs is per priority per slot for a serving cell. If fdmed-ReceptionMulticast is configured, the number of received PDSCHs is per traffic type (unicast / multicast) per slot for a serving cell.

Configures the DL PRS for propagation delay compensation. When configured, the UE measures the UE Rx-Tx time difference based on the reference signals configured in this field.

Indicates the number of HARQ bundling groups for type2 HARQ-ACK codebook.

Indicates whether UE shall apply as pathloss reference either the downlink of SpCell (PCell for MCG or PSCell for SCG) or of SCell that corresponds with this uplink (see clause 7 of TS 38.213).

Presence of this field indicates the UE shall monitor PDCCH candidates that overlap with LTE CRS RE(s).

PDSCH related parameters that are not BWP-specific.

The starting bit position of an information block of DCI format 2_9 for this serving cell (see clause 7.3.1.3.10 of TS 38.212).

Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology. See clause 5.1.4.1 of TS 38.214. If a RateMatchPattern with the same RateMatchPatternId is configured in both ServingCellConfig/ServingCellConfigCommon and in SIB20/MCCH, the entire RateMatchPattern configuration shall be the same, including the set of RBs/REs indicated by the patterns for the rate matching around, and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214.

SCell deactivation timer in TS 38.321. If the field is absent, the UE applies the value infinity.

This parameter is used to configure single frequency network scheme for PDCCH: sfnSchemeA or sfnSchemeB as specified (see clause 5.1 of TS 38.214). If network includes both sfnSchemePDCCH and sfnSchemePDSCH, same value shall be configured.

This parameter is used to configure single frequency network scheme for PDSCH: sfnSchemeA or sfnSchemeB as specified (see clause 5.1 of TS 38.214). If network includes both sfnSchemePDCCH and sfnSchemePDSCH, same value shall be configured. The network does not configure this parameter and repetitionSchemeConfig in PDSCH-Config simultaneously in the same serving cell.

When this field is configured and when channelAccessMode-r16 (see IE ServingCellConfigCommon and IE ServingCellConfigCommonSIB) is configured to semiStatic, the UE operates in semi-static channel access mode and can initiate a channel occupancy periodically (see clause 4.3 of TS 37.213). The period can be configured independently from period configured in SemiStaticChannelAccessConfig-r16 if the UE indicates the corresponding capability. Otherwise, the periodicity configured by periodUE-r17 is an integer multiple of or an integer factor of the periodicity indicated by period in SemiStaticChannelAccessConfig-r16.

measObjectId of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and frequencyInfoDL in ServingCellConfigCommon/ ServingCellConfigCommonSIB of the serving cell: if ssbFrequency is configured, its value is the same as the absoluteFrequencySSB and if csi-rs-ResourceConfigMobility is configured, the value of its subcarrierSpacing is present in one entry of the scs-SpecificCarrierList, csi-RS-CellListMobility includes an entry corresponding to the serving cell (with cellId equal to physCellId in ServingCellConfigCommon) and the frequency range indicated by the csi-rs-MeasurementBW of the entry in csi-RS-CellListMobility is included in the frequency range indicated by in the entry of the scs-SpecificCarrierList.

Network may configure this field only when supplementaryUplinkConfig is configured in ServingCellConfigCommon or supplementaryUplink is configured in ServingCellConfigCommonSIB.

If this field is included, the UE shall release the uplink configuration configured by supplementaryUplink. The network only includes either supplementaryUplinkRelease or supplementaryUplink at a time.

Timing Advance Group ID, as specified in TS 38.321, which this cell or set of TCI-States of this cell belongs to. The tag2-Id is optionally configured in a serving cell if and only if the serving cell is configured with more than one value for the coresetPoolIndex

If this field is set to true, the tag2-Id is associated to value 0 and tag-Id is associated to value 1 of field TI bit in RAR , fallbackRAR and in the absolute TAC MAC CE, see TS 38.321. Otherwise, the tag2-Id is associated to value 1 and tag-Id is associated to value 0 of field R bit in RAR, fallbackRAR and in the absolute TAC MAC CE, see TS 38.321.

If configured for an SCell, or if configured for the PSCell when the SCG is being activated upon the reception of the containing message, the UE shall consider the TCI states provided in this field as the activated TCI states for PDCCH/PDSCH reception on this serving cell. If configured for the PSCell when the SCG is indicated as deactivated in the containing message:

• the UE shall consider the TCI states provided in this field as the TCI states to be activated for PDCCH/PDSCH reception upon a later SCG activation in which tci-ActivatedConfig is absent
• if bfd-and-RLM is configured and no RS is configured in RadioLinkMonitoringConfig for RLM, respectively for BFD, the UE shall use the TCI states provided in this field for PDCCH as RS for RLM, respectively for BFD.

When this field is absent for the PSCell and the SCG is being deactivated:

• the UE shall consider the previously activated TCI states as the TCI states to be activated for PDCCH/PDSCH reception upon a later SCG activation in which tci-ActivatedConfig is absent
• if bfd-and-RLM is configured and no RS is configured in RadioLinkMonitoringConfig for RLM, respectively for BFD, the UE shall use the previously activated TCI states for PDCCH as RS for RLM, respectively for BFD.

Resource configuration per IAB-MT D/U/F overrides all symbols (with a limitation that effectively only flexible symbols can be overwritten in Rel-16) per slot over the number of slots as provided by TDD-UL-DL ConfigurationCommon.

Indicates the unified TCI state type the UE is configured for this serving cell. The value separate means this serving cell is configured with dl-OrJointTCI-StateList for DL TCI state and ul-TCI-ToAddModList for UL TCI state. The value joint means this serving cell is configured with dl-OrJointTCI-StateList for joint TCI state for UL and DL operation.

Network may configure this field only when uplinkConfigCommon is configured in ServingCellConfigCommon or ServingCellConfigCommonSIB. Addition or release of this field can only be done upon SCell addition or release (respectively).

Configures UL power control parameters for PUSCH, PUCCH and SRS when field unifiedTCI-StateType is configured for this serving cell.

Includes parameters for configuration of carrier based SRS switching (see clause 6.2.1.3 of TS 38.214).

When the parameter is present, UE derives the spatial relation and the corresponding pathloss reference Rs as specified in clauses 7.1.1, 7.2.1, 7.3.1 and 9.2.2 of TS 38.213. The network only configures these parameters for FR2.

When this parameter is present, the Rel-16 feature of MAC CE based pathloss RS updates for PUSCH/SRS is enabled. Network only configures this parameter when the UE is configured with sri-PUSCH-PowerControl. If this field is not configured, network configures at most 4 pathloss RS resources for PUSCH/PUCCH/SRS transmissions per BWP, not including pathloss RS resources for SRS transmissions for positioning. (See clause 7 of TS 38.213).

If configured for an SpCell, this field contains the ID of the UL BWP to be activated upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If configured for an SCell, this field contains the ID of the uplink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BandiwdthPartId = 0.

The dedicated (UE-specific) configuration for the initial uplink bandwidth-part (i.e. UL BWP#0). If any of the optional IEs are configured within this IE as part of the IE uplinkConfig, the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1

Indicates the mode of NACK-only feedback in the PUCCH transmission, as specified in clause 18 of TS 38.213. If multicast CFR is not configured, this field is not included. Otherwise, if the field is absent, UE uses mode 1 for multicast CFR.

Indicates whether UE is allowed to boost uplink transmission power by suspending in-band emission (IBE) requirements as specified in TS 38.101-2. Network only configures this field for FR2 serving cells.

If this field is set to true, the UE determines the maximum output power for PUCCH/PUSCH transmissions that use pi/2 BPSK modulation according to clause 6.2.4 of TS 38.101-1.

PUSCH related parameters that are not BWP-specific.

Contains configuration related to the SRS for Positioning hopping outside the active BWP of the UE.

The additional bandwidth parts for uplink to be added or modified. In case of TDD uplink- and downlink BWP with the same bandwidthPartId are considered as a BWP pair and must have the same center frequency.

The additional bandwidth parts for uplink to be released.

A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in UplinkConfigCommon / UplinkConfigCommonSIB. Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1, TS 38.101-2, and TS 38.101-5. If the UE is a RedCap UE and needs to autonomously switch to its initial uplink bandwidth part to perform a random access procedure but its current UE specific channel bandwidth does not cover the initial uplink bandwidth part, the UE autonomously changes its UE specific channel bandwidth to cover the initial uplink bandwidth part. In that case, after completion of the random access procedure, the network ensures that the UE specific channel bandwidth fully covers the UE's active uplink bandwidth part in subsequent bandwidth part switch operations.

Indicates whether the location of UL Tx switching period is configured in this uplink carrier in case of inter-band UL CA, SUL, or (NG)EN-DC, as specified in TS 38.101-1 and TS 38.101-3. In case of (NG)EN-DC, network always configures this field to TRUE for NR carrier (i.e. with (NG)EN-DC, the UL switching period always occurs on the NR carrier). In case of inter-band UL CA or SUL, for dynamic uplink Tx switching between 2 bands with 2 uplink carriers or 3 uplink carriers as defined in TS 38.101-1, network configures this field to TRUE for the uplink carrier(s) on one band and configures this field to FALSE for the uplink carrier(s) on the other band. This field is set to the same value for the carriers on the same band.

Indicates that the configured carrier is carrier1 or carrier2 for dynamic uplink Tx switching, as defined in TS 38.101-1 and TS 38.101-3. In case of (NG)EN-DC, network always configures the NR carrier as carrier 2. In case of inter-band UL CA or SUL, for dynamic uplink Tx switching between 2 bands with 2 uplink carriers or 3 uplink carriers as defined in TS 38.101-1, network configures the uplink carrier(s) on one band as carrier1 and the uplink carrier(s) on the other band as carrier2. This field is set to the same value for the carriers on the same band.

This field contains the ID of an SCell group for Dormancy within active time, to which this SCell belongs. The use of the Dormancy within active time for SCell groups is specified in TS 38.213.

This field contains the ID of an SCell group for Dormancy outside active time, to which this SCell belongs. The use of the Dormancy outside active time for SCell groups is specified in TS 38.213.

This field contains the ID of the downlink bandwidth part to be used as dormant BWP. If this field is configured, its value is different from defaultDownlinkBWP-Id, and at least one of the withinActiveTimeConfig and outsideActiveTimeConfig should be configured.

This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy outside active time.

This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy within active time.

This field contains the configuration to be used for SCell dormancy outside active time, as specified in TS 38.213. The field can only be configured when the cell group the SCell belongs to is configured with dcp-Config.

This field contains the configuration to be used for SCell dormancy within active time, as specified in TS 38.213.

Indicates the starting RB of the guard band.

Indicates the length of the guard band in RBs. When set to 0, zero-size guard band is used.

Configure the indication type for antenna port(s) field in DCI format 1_3 and DCI format 0_3, respectively (See clause 7.3.1.2.4 of TS 38.212).

Configure the presence of Scell dormancy indication field in DCI format 1_3 and DCI format 0_3, respectively.

Configure the presence of minimum applicable scheduling offset indicator field in DCI format 1_3 and DCI format 0_3, respectively.

Configure n_CI value used for the set of cells, where unique n_CI value is configured for each set of cells.

Configure the presence of PDCCH monitoring adaptation indication field in DCI format 1_3 and DCI format 0_3, respectively.

Enable the enhanced Type 3 HARQ-ACK codebook triggering using DCI format 1_3.

Enables the enhanced Type 3 CB through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in DCI format 1_3 if the more than one enhanced Type HARQ-ACK codebook is configured for the primary PUCCH cell group.

When configured, the DCI_format 1_3 can request the UE to report A/N for all HARQ processes and all CCs configured in the PUCCH group.

When configured, the DCI format 1_3 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource.

Configure the presence of priority indicator field in DCI format 1_3 and DCI format 0_3, respectively.

Configure the UE with PUCCH cell switching based on dynamic indication in DCI format 1_3.

Configure each row of the joint rate matching indication table for DL scheduling via DCI format 1_3, where bitmap for a cell points to a corresponding rate matching indication applicable for DCI format 1-1 (i.e., MSB and LSB of bitmap refer rateMatchPatternGroup1 and rateMatchPatternGroup2 for a cell, respectively), the order of rate matching indication bitmap in each row refers the order of cells in ScheduledCell-ListDCI-1-3, that are configured with rateMatchPatternGroup1 or rateMatchPatternGroup2 on at least one DL BWP (i.e., first bitmap is for the first cell in ScheduledCell-ListDCI-1-X, that are configured with rateMatchPatternGroup1 or rateMatchPatternGroup2 on at least one DL BWP and so on), the number of entries in a row of rateMatchDCI-1-3 should be the same as the number of cells, that are configured with rateMatchPatternGroup1 or rateMatchPatternGroup2 on at least one DL BWP, included in ScheduledCell-ListDCI-1-3, and entries for co-scheduled cells in a row of rateMatchDCI-1-3 are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3.

Configure joint rate matching indication table for DL scheduling via DCI format 1_3.

Configure each row of the table for combinations of co-scheduled cells for DL scheduling via DCI format 1_3 and for UL scheduling via DCI format 0_3, where index with value INTEGER (0...3) of co-scheduled cell refers to ScheduledCell-ListDCI-1-3 for DL and ScheduledCell-ListDCI-0-3 for UL.

Configure the table for combinations of co-scheduled cells for DL scheduling via DCI format 1_3 and DCI format 0_3, respectively.

Configure the list of possible co-scheduled cells in the set for DL scheduling via DCI format 1_3 and DCI format 0_3 respectively, where the serving cells in the list are in ascending order of serving cell indices and are mapped to index {0, 1, 2, 3} in the set. Total number of cells within the same set of cells i.e., in ScheduledCell-ListDCI-1-3 and ScheduledCell-ListDCI-0-3, is up to 4. When a cell is included in either or both of ScheduledCell-ListDCI-1-3 or ScheduledCell-ListDCI-0-3 for one set of cells MC-DCI-SetofCells, the cell cannot be included in any of ScheduledCell-ListDCI-1-3 or ScheduledCell-ListDCI-0-3 for any other set of cells.

Configure index of the set of cells to be indicated in DCI format 0_3/1_3.

Configure the indication type for SRS resource indicator field in DCI format 0_3 (See clause 7.3.1.1.4 of TS 38.212).

Configure each row of the joint SRS offset indicator table for DL scheduling via DCI format 1_3 and for UL scheduling via DCI format 0_3, where index for a cell points to a corresponding SRS offset indicator applicable for DCI format 1-1 and 0-1, and the order of SRS offset indicator index in each row refers the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first index is for the first cell in ScheduledCell-ListDCI-1-3, that are configured with more than one entry in availableSlotOffsetList for at least one aperiodic SRS resource set on at least one UL BWP and so on) for DL and ScheduledCell-ListDCI-0-3 for UL, included in ScheduledCell-ListDCI-1-3 for srs-OffsetListDCI-1-3 and ScheduledCell-ListDCI-0-3 for srs-OffsetListDCI-0-3, and entries for co-scheduled cells in a row of SRS-OffsetCombo are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3/0_3.

Configure joint SRS offset indicator table for DL scheduling via DCI format 1_3 and DCI format 0_3, respectively.

Configure each row of the joint SRS request table for DL scheduling via DCI format 1_3 and for UL scheduling via DCI format 0_3, where index for a cell points to a corresponding SRS request applicable for DCI format 1-1 and 0-1, and the order of SRS request index in each row refers the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first index is for the first cell in ScheduledCell-ListDCI-1-3 and so on) for DL and ScheduledCell-ListDCI-0-3 for UL. The number of entries in a row of SRS-RequestCombo should be the same as the number of cells included in ScheduledCell-ListDCI-1-3 for srs-RequestListDCI-1-3 and ScheduledCell-ListDCI-0-3 for srs-RequestListDCI-0-3, and entries for co-scheduled cells in a row of SRS-RequestCombo are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3/0_3.

Configure joint SRS request table for DL scheduling via DCI format 1_3 and DCI format 0_3, respectively.

Configure each row of the joint TCI table for DL scheduling via DCI format 1_3, where index for a cell points to a corresponding TCI applicable for DCI format 1-1, and the order of TCI index in each row refers the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first index is for the first cell in ScheduledCell-ListDCI-1-3 that configured with tci-StatesToAddModList and so on), the number of entries in a row of TCI-DCI-1-3 should be the same as the number of cells that configured with tci-StatesToAddModList on at least one DL BWP, included in ScheduledCell-ListDCI-1-3, and entries for co-scheduled cells in a row of TCI-DCI-1-3 are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3.

Configure joint TCI table for DL scheduling via DCI format 1_3

Configure each row of the joint TDRA field table for UL scheduling via DCI format 0_3 containing the applicable TDRA field indexes for multiple BWPs/cells, where the TDRA index for a BWP of a cell points to a corresponding TDRA in the TDRA table applicable for DCI format 0-1, the order of TDRA index in each row refers the BWP-Id for a cell and the order of cells in ScheduledCell-ListDCI-0-3 (i.e., first TDRA index in a row is for the smallest BWP-Id that can be scheduled by the DCI format 0-3, as specified in 38.212, of the first cell in ScheduledCell-ListDCI-0-3, second TDRA index in a row is for the second smallest BWP-Id 1 that can be scheduled by the DCI format 0-3, as specified in 38.212, of the first cell and so on), and the number of TDRA indices in a row of TDRA-FieldIndexDCI-0-3 should be the same as the total number of BWPs that can be scheduled by the DCI format 0-3, as specified in 38.212, across cells included in ScheduledCell-ListDCI-0-3.

Configure each row of the joint TDRA field table for DL scheduling via DCI format 1_3 containing the applicable TDRA field indexes for multiple BWPs/cells, where the TDRA index for a BWP of a cell points to a corresponding TDRA in the TDRA table applicable for DCI format 1-1, the order of TDRA index in each row refers the BWP-Id for a cell and the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first TDRA index in a row is for the smallest BWP-Id that can be scheduled by the DCI format 1-3, as specified in 38.212, of the first cell in ScheduledCell-ListDCI-1-3, second TDRA index in a row is for the second smallest BWP-Id that can be scheduled by the DCI format 1-3, as specified in 38.212, of the first cell and so on ), and the number of TDRA indices in a row of TDRA-FieldIndexDCI-1-3 should be the same as the total number of BWPs that can be scheduled by the DCI format 1-3, as specified in 38.212, across cells included in ScheduledCell-ListDCI-1-3.

Configure joint TDRA table for UL scheduling via DCI format 1_3 and DCI format 0_3, respectively.

Configure the indication type for precoding information and number of layers field in DCI format 0_3 (See clause 7.3.1.1.4 of TS 38.212).

Configure each row of the joint ZP-CSI-RS trigger table for DL scheduling via DCI format 1_3, where index for a cell points to a corresponding ZP-CSI-RS trigger applicable for DCI format 1-1, and the order of ZP-CSI-RS trigger index in each row refers the order of cells in ScheduledCell-ListDCI-1-3 (i.e., first index is for the first cell in ScheduledCell-ListDCI-1-3, that are configured with aperiodic-ZP-CSI-RS-ResourceSetsToAddModList on at least one DL BWP and so on), the number of entries in a row of ZP-CSI-DCI-1-3 should be the same as the number of cells, that are configured with aperiodic-ZP-CSI-RS-ResourceSetsToAddModList on at least one DL BWP, included in ScheduledCell-ListDCI-1-3, and entries for co-scheduled cells in a row of ZP-CSI-DCI-1-3 are interpreted based on the BWPs of co-scheduled cells that is determined by the BWP indicator field of DCI format 1_3.

Configure joint ZP-CSI-RS trigger table for DL scheduling via DCI format 1_3.

If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 of TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures as defined in clause 4.1 and 4.2 of TS 37.213.

If present, the UE shall apply channel access procedures for operation with shared spectrum channel access in accordance with clause 4.4 of TS 37.213 for FR2-2. If absent, the UE shall not apply any channel access procedure. The network always configures this field if channel access procedures are required for the serving cell within this region by regulations.

Position of (first) DM-RS for downlink (see clause 7.4.1.1.1 of TS 38.211) and uplink (clause 6.4.1.1.3 of TS 38.211).

The common downlink configuration of the serving cell, including the frequency information configuration and the initial downlink BWP common configuration. The parameters provided herein should match the parameters configured by MIB and SIB1 (if provided) of the serving cell, with the exception of controlResourceSetZero and searchSpaceZero which can be configured in ServingCellConfigCommon even if MIB indicates that they are absent.

Indicates the window length of the discovery burst in ms (see TS 37.213). The field discoveryBurstWindowLength-r17 is applicable to SCS 480 kHz and SCS 960 kHz.

Indicates priorities for features, such as (e)RedCap, Slicing, SDT, MSG1-Repetitions, and MSG3-Repetitions for Coverage Enhancements. These priorities are used to determine which FeatureCombinationPreambles the UE shall use when a feature maps to more than one FeatureCombinationPreambles, as specified in TS 38.321. A lower value means a higher priority. The network does not signal the same priority for more than one feature. The network signals a priority for all feature that map to at least one FeatureCombinationPreambles.

Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in clause 4.1 of TS 38.213.

Parameters to determine an LTE CRS pattern that the UE shall rate match around.

Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in clause 4.1 of TS 38.213.

The N_TA-Offset to be applied for all uplink transmissions on this serving cell if n-TimingAdvanceOffset is not configured. If tag2 is configured for this serving cell, this field is to be applied to all uplink transmissions associated to tag-id configured for this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133, table 7.1.2-2.

If present, this field indicates that the UE shall apply channel access procedures before msg1/msgA transmission for operation with shared spectrum channel access in accordance with clause 4.4.5 of TS 37.213 for FR2-2.

Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology (see clause 5.1.4.1 of TS 38.214). If a RateMatchPattern with the same RateMatchPatternId is configured in both ServingCellConfig/ServingCellConfigCommon and in SIB20/MCCH, the entire RateMatchPattern configuration, including the set of RBs/REs indicated by the patterns for the rate matching around, shall be the same and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214.

Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in clause 4.1 of TS 38.213.

Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see clause 7 of TS 38.213.

The SSB periodicity in ms for the rate matching purpose. If the field is absent, the UE applies the value ms5. (see clause 4.1 of TS 38.213)

Indicates the QCL relation between SSB positions for this serving cell as specified in clause 4.1 of TS 38.213.

For operation in licensed spectrum, indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in clause 4.1 of TS 38.213. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. For operation with shared spectrum channel access, the UE assumes that one or more SS/PBCH blocks indicated by ssb-PositionsInBurst may be transmitted within the discovery burst transmission window and have candidate SS/PBCH blocks indexes corresponding to SS/PBCH block indexes provided by ssb-PositionsInBurst (see clause 4.1 of TS 38.213). If the k-th bit of ssb-PositionsInBurst is set to 1, the UE assumes that one or more SS/PBCH blocks within the discovery burst transmission window with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k - 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1's in the bitmap. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. For operation with shared spectrum channel access in FR1, only mediumBitmap is used, and for FR2-2, longBitmap is used.

Subcarrier spacing of SSB. Only the following values are applicable depending on the used frequency: FR1: 15 or 30 kHz FR2-1: 120 or 240 kHz FR2-2: 120, 480, or 960 kHz

The network configures this field only if uplinkConfigCommon is configured. If this field is absent, the UE shall release the supplementaryUplinkConfig and the supplementaryUplink configured in ServingCellConfig of this serving cell, if configured.

A cell-specific TDD UL/DL configuration, see clause 11.1 of TS 38.213.

If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 of TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures as defined in clause 4.1 and 4.2 of TS 37.213.

If present, this field indicates that the UE shall apply channel access procedures for operation with shared spectrum channel access in accordance with clause 4.4 of TS 37.213 for FR2-2. If absent, the UE shall not apply any channel access procedure. The network always configures this field if channel access procedures are required for the serving cell within this region by regulations.

Indicates the window length of the discovery burst in ms (see TS 37.213). The field discoveryBurstWindowLength-v1700 is applicable to SCS 480 kHz and SCS 960 kHz.

If the field is present and UE supports the enhanced cell reselection requirements for NTN LEO in RRC_IDLE/RRC_INACTIVE, the UE shall apply the enhanced cell reselection requirements for NTN LEO as specified in TS 38.133, clauses 4.2C.2.3 and 4.2C.2.4.

This field is present when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in clause 4.1 of TS 38.213. The first/leftmost bit corresponds to the SS/PBCH index 0-7, the second bit corresponds to SS/PBCH block 8-15, and so on. Value 0 in the bitmap indicates that the SSBs according to inOneGroup are absent. Value 1 indicates that the SS/PBCH blocks are transmitted in accordance with inOneGroup.

When maximum number of SS/PBCH blocks per half frame equals to 4 as defined in clause 4.1 of TS 38.213, only the 4 leftmost bits are valid; the UE ignores the 4 rightmost bits. When maximum number of SS/PBCH blocks per half frame equals to 8 as defined in clause 4.1 of TS 38.213, all 8 bits are valid. The first/ leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. When maximum number of SS/PBCH blocks per half frame equals to 64 as defined in clause 4.1 of TS 38.213, all 8 bit are valid; The first/ leftmost bit corresponds to the first SS/PBCH block index in the group (i.e., to SSB index 0, 8, and so on); the second bit corresponds to the second SS/PBCH block index in the group (i.e., to SSB index 1, 9, and so on), and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted.

The N_TA-Offset to be applied for random access on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133, table 7.1.2-2.

If present, this field indicates that the UE shall apply channel access procedures before msg1/msgA transmission for operation with shared spectrum channel access in accordance with clause 4.4.5 of TS 37.213 for FR2-2.

Time domain positions of the transmitted SS-blocks in an SS-burst as defined in clause 4.1 of TS 38.213. For operation with shared spectrum channel access in FR1, only inOneGroup is used and the UE interprets this field same as mediumBitmap in ServingCellConfigCommon. The UE assumes that a bit in inOneGroup at position k > N_SSB^QCL is 0, where N_SSB^QCL is obtained from MIB as specified in clause 4.1 of TS 38.213. For operation with shared spectrum channel access in FR2-2, the m-th bit in groupPresence is set to 0 for m > N_SSB^QCL/8, where N_SSB^QCL is obtained from MIB as specified in clause 4.1 of TS 38.213.

Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see clause 7 of TS 38.213.

Configuration of dedicated RACH Occasions for SI. If the field is absent, the UE uses the corresponding parameters configured in rach-ConfigCommon of the initial uplink BWP.

Periodicity of the SI-Request configuration in number of association periods.

If there is only one entry in the list, the configuration is used for all SI messages for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting. Otherwise:

• If si-SchedulingInfo-v1700 is not present and the SI-RequestConfig is used for on-demand SI request in SI-SchedulingInfo or PosSI-SchedulingInfo, the 1st entry in the list corresponds to the first SI message in schedulingInfoList or posSchedulingInfoList for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message in schedulingInfoList or posSchedulingInfoList for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting and so on.
• If si-SchedulingInfo-v1700 is present and SI-RequestConfig is configured in SI-SchedulingInfo for on-demand SI request, the UE generates a list of concatenated SI messages by appending the SI messages containing type1 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 to the SI messages configured by schedulingInfoList in si-SchedulingInfo. The 1st entry in the list corresponds to the first SI message for which si-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message for which si-BroadcastStatus is set to notBroadcasting and so on.
• If si-SchedulingInfo-v1700 is present and SI-RequestConfig is configured in PosSI-SchedulingInfo for on-demand SI request, the UE generates a list of concatenated SI messages by appending the SI messages containing type2 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 to the SI messages configured by posSchedulingInfoList in posSI-SchedulingInfo. The 1st entry in the list corresponds to the first SI message for which posSI-BroadcastStatus or si-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message for which posSI-BroadcastStatus or si-BroadcastStatus is set to notBroadcasting and so on.

Change of si-RequestResources should not result in system information change notification.

Index of the association period in the si-RequestPeriod in which the UE can send the SI request for SI message(s) corresponding to this SI-RequestResources, using the preambles indicated by ra-PreambleStartIndex and rach occasions indicated by ra-ssb-OccasionMaskIndex.

If N SSBs are associated with a RACH occasion, where N > = 1, for the i-th SSB (i=0, …, N-1) the preamble with preamble index = ra-PreambleStartIndex + i is used for SI request; For N <1, the preamble with preamble index = ra-PreambleStartIndex is used for SI request.

Indicates the configurations for Msg1-based SI request with Msg1 repetition for repetition number 2, 4 and 8, respectively. If there is only one entry in the list, the configuration is used for all SI messages for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting. Otherwise:

• If si-SchedulingInfo-v1700 is not present and the SI-RequestConfigRepetitionNum2/SI-RequestConfigRepetitionNum4/SI-RequestConfigRepetitionNum8 is used for on-demand SI request in SI-SchedulingInfo or PosSI-SchedulingInfo, the 1st entry in the list corresponds to the first SI message in schedulingInfoList or posSchedulingInfoList for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message in schedulingInfoList or posSchedulingInfoList for which si-BroadcastStatus or posSI-BroadcastStatus is set to notBroadcasting and so on.
• If si-SchedulingInfo-v1700 is present and SI-RequestConfigRepetitionNum2/SI-RequestConfigRepetitionNum4/SI-RequestConfigRepetitionNum8 is configured in SI-SchedulingInfo for on-demand SI request, the UE generates a list of concatenated SI messages by appending the SI messages containing type1 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 to the SI messages configured by schedulingInfoList in si-SchedulingInfo. The 1st entry in the list corresponds to the first SI message for which si-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message for which si-BroadcastStatus is set to notBroadcasting and so on.
• If si-SchedulingInfo-v1700 is present and SI-RequestConfigRepetitioNum2/SI-RequestConfigRepetitionNum4/SI-RequestConfigRepetitionNum8n is configured in PosSI-SchedulingInfo for on-demand SI request, the UE generates a list of concatenated SI messages by appending the SI messages containing type2 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 to the SI messages configured by posSchedulingInfoList in posSI-SchedulingInfo. The 1st entry in the list corresponds to the first SI message for which posSI-BroadcastStatus or si-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message for which posSI-BroadcastStatus or si-BroadcastStatus is set to notBroadcasting and so on.

Change of si-RequestResourcesRepetitionNum2/SI-RequestConfigRepetitionNum4/SI-RequestConfigRepetitionNum8 should not result in system information change notification.

Indicates that a SIB is area specific. If the field is absent, the SIB is cell specific.

Indicates if the SI message is being broadcasted or not. Change of si-BroadcastStatus should not result in system information change notifications in Short Message transmitted with P-RNTI over DCI (see clause 6.5). The value of the indication is valid until the end of the BCCH modification period when set to broadcasting. When SIB19 is scheduled in an NTN cell, the si-BroadcastStatus for the mapped SIB19 is set to broadcasting. If si-SchedulingInfo-v1700 is present, the network ensures that the total number of SI messages with si-BroadcastStatus set to notBroadcasting in the list of concatenated SI messages configured by schedulingInfoList in si-SchedulingInfo and SI messages containing type1 SIB configured by schedulingInfoList2 in si-SchedulingInfo-v1700 does not exceed the limit of maxSI-Message when si-RequestConfig, si-RequestConfigRedCap or si-RequestConfigSUL is configured.

Periodicity of the SI-message in radio frames. Value rf8 corresponds to 8 radio frames, value rf16 corresponds to 16 radio frames, and so on.

This field is not used in this specification. If received, it is ignored by the UE.

Configuration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.

Configuration of Msg1 repetition resources on NUL that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting. This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages.

Configuration of Msg1 resources for initialUplinkBWP-RedCap that the (e)RedCap UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.

Configuration of Msg1 repetition resources for initialUplinkBWP-RedCap that the RedCap UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting. This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages.

Configuration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.

Configuration of Msg1 repetition resources on SUL that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting. This field is only applicable when Msg1 repetition resources can be used for requesting SI-messages.

The length of the SI scheduling window. Value s5 corresponds to 5 slots, value s10 corresponds to 10 slots and so on. The network always configures si-WindowLength to be shorter than or equal to the si-Periodicity. The values s2560-v1710 and s5120-v1710 are only applicable for SCS 480 kHz.

Indicates the system information area that the cell belongs to, if any. Any SIB with areaScope within the SI is considered to belong to this systemInformationAreaID. The systemInformationAreaID is unique within a PLMN/SNPN.

The presence of this field indicates that the pos-sib-type is encrypted as specified in TS 37.355.

The presence of this field indicates that the positioning SIB type is for a specific GNSS. Indicates a specific GNSS (see also TS 37.355)

The posSIBs as defined in TS 37.355 mapped to SI for scheduling using schedulingInfoList2.

The presence of this field indicates that the positioning SIB type is for a specific SBAS. Indicates a specific SBAS (see also TS 37.355).

This field indicates the SI window position of the associated SI-message. The network provides si-WindowPosition in an ascending order, i.e. si-WindowPosition in the subsequent entry in schedulingInfoList2 has always value higher than in the previous entry of schedulingInfoList2. The network configures this field in a way that ensures that SI messages scheduled by schedulingInfoList and/or posSchedulingInfoList do not overlap with SI messages scheduled by schedulingInfoList2.

Indicates which SIBs or posSIBs are contained in the SI message.

The type of SIB(s) mapped to SI for scheduling using schedulingInfoList2. Value type1 indicates SIBs and value type2 indicates posSIBs.

This ID is used in the DCI payload to dynamically select this SlotFormatCombination (see clause 11.1.1 of TS 38.213).

Slot formats that occur in consecutive slots in time domain order as listed here (see clause 11.1.1 of TS 38.213, and clause 14 of TS 38.213, for IAB-MT).

If configured, the UE is allowed to transmit uplink signals/channels (SRS, PUCCH, CG-PUSCH) in the set of symbols of the slot when the UE does not detect a DCI format 2_0 providing a slot format for the set of symbols (see TS 38.213, 11.1.1). This field is applicable only if cg-RetransmissionTimer-r16 is configured.

The (starting) position (bit) of the slotFormatCombinationId (SFI-Index) for this serving cell (servingCellId) within the DCI payload (see clause 11.1.1 of TS 38.213).

The ID of the serving cell for which the slotFormatCombinations are applicable.

A list with SlotFormatCombinations. Each SlotFormatCombination comprises of one or more SlotFormats (see clause 4.3.2 of TS 38.211). The total number of slotFormats in the slotFormatCombinations list does not exceed 512.

Reference subcarrier spacing for a Slot Format Combination on an FDD or SUL cell (see clause 11.1.1 of TS 38.213). For FDD, subcarrierSpacing (SFI-scs) is the reference SCS for DL BWP and subcarrierSpacing2 (SFI-scs2) is the reference SCS for UL BWP. For SUL, subcarrierSpacing (SFI-scs) is the reference SCS for non-SUL carrier and subcarrierSpacing2 (SFI-scs2) is the reference SCS for SUL carrier. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications.

Reference subcarrier spacing for this Slot Format Combination. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications (see clause 11.1.1 of TS 38.213).

A list of AvailableRB-SetsPerCell objects (see clause 11.1.1 of TS 38.213).

A list of CO-DurationsPerCell objects. If not configured, the UE uses the slot format indicator (SFI), if available, to determine the channel occupancy duration (see clause 11.1.1 of TS 38.213).

A list of CO-DurationsPerCell objects to be released. An entry created using co-DurationsPerCellToAddModList-r16 or co-DurationsPerCellToAddModList-r17 can be deleted using co-DurationsPerCellToReleaseList.

Total length of the DCI payload scrambled with SFI-RNTI (see clause 11.1.1 of TS 38.213).

RNTI used for SFI on the given cell (see clause 11.1.1 of TS 38.213).

A list of SlotFormatCombinations for the UE's serving cells (see clause 11.1.1 of TS 38.213).

A list of SearchSpaceSwitchTrigger objects. Each SearchSpaceSwitchTrigger object provides position in DCI of the bit field indicating search space switching flag for a serving cell or, if cellGroupsForSwitchList is configured, group of serving cells (see clause 10.4 of TS 38.213). If cellGroupsForSwitchList is configured, only one of the cells belonging to the same cell group is added/modified, and the configuration applies to all cells belonging to the cellGroupsForSwitchList (see clause 10.4 of TS 38.213). The network configures more than 4 SearchSpaceSwitchTrigger objects only if cellGroupsForSwitchList is not configured. The UE shall consider entries in switchTriggerToAddModList and in switchTriggerToAddModListSizeExt as a single list, i.e. an entry created using switchTriggerToAddModList can be modifed using switchTriggerToAddModListSizeExt and vice-versa.

A list of SearchSpaceSwitchTriggers to be released. If cellGroupsForSwitchList is configured, the SearchSpaceSwitchTrigger is released for all serving cells belonging to the same CellGroupForSwitch. The UE shall consider entries in switchTriggerToReleaseList and in switchTriggerToReleaseListSizeExt as a single list, i.e. an entry created using switchTriggerToAddModList or switchTriggerToAddModListSizeExt can be deleted using switchTriggerToReleaseList or switchTriggerToReleaseListSizeExt.

The (starting) position of the bits within DCI payload indicating the availability of the RB sets of a serving cell (see clause 11.1.1 of TS 38.213).

The ID of the serving cell for which the configuration is applicable.

A list of Channel Occupancy duration in symbols. The maximum duration that can be configured for the following SCS:

• 15 kHz: 280.
• 30 kHz: 560.
• 60 kHz: 1120.
• 120 kHz: 560.
• 480 kHz: 2240.
• 960 kHz: 4480.

Position in DCI of the bit field indicating Channel Occupancy duration for UE's serving cells (see clause 11.1.1 of TS 38.213).

The ID of the serving cell for which the configuration is applicable.

Reference subcarrier spacing for the list of Channel Occupancy durations (see clause 11.1.1 of TS 38.213).

FR1: 15, 30, or 60 kHz FR2-2: 120, 480, or 960 kHz

The position of the bit within DCI payload containing a search space switching flag (see clause 11.1.1 of TS 38.213).

The ID of the serving cell for which the configuration is applicable or the group of serving cells as indicated by CellGroupsForSwitch-r16 containing this servingCellId.

Indicates the S-NSSAI consisting of Slice/Service Type, see TS 23.003.

Indicates the S-NSSAI consisting of Slice/Service Type and Slice Differentiator, see TS 23.003.

The concerned mobility control related parameter is multiplied with this factor if the UE is in High Mobility state as defined in TS 38.304. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, oDot75 corresponds to 0.75 and so on.

The concerned mobility control related parameter is multiplied with this factor if the UE is in Medium Mobility state as defined in TS 38.304. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, value oDot75 corresponds to 0.75, and so on.

Indicates the HARQ-ACK codebook index for the corresponding HARQ-ACK codebook for SPS PDSCH and ACK for SPS PDSCH release.

Indicates the offset used in deriving the HARQ process IDs, see clause 5.3.1 of TS 38.321.

Indicates the MCS table the UE shall use for DL SPS (see clause 5.1.3.1 of TS 38.214. If present, the UE shall use the MCS table of low-SE 64QAM table indicated in Table 5.1.3.1-3 of TS 38.214. If this field is absent and field mcs-table in PDSCH-Config is set to 'qam256' and the activating DCI is of format 1_1, the UE applies the 256QAM table indicated in Table 5.1.3.1-2 of TS 38.214. If this field is absent and the field mcs-Table-r17 in PDSCH-Config is set to 'qam1024' and the activating DCI is format 1_1, the UE applies the 1024QAM table indicated in Table 5.1.3.1-4 of TS 38.214. Otherwise, the UE applies the non-low-SE 64QAM table indicated in Table 5.1.3.1-1 of TS 38.214.

HARQ resource for PUCCH for DL SPS. The network configures the resource either as format0 or format1. The actual PUCCH-Resource is configured in PUCCH-Config and referred to by its ID. See clause 9.2.3 of TS 38.213.

HARQ resource for PUCCH on PUCCH switching SCell (sSCell) for DL SPS. The network configures the resource either as format 0 or format 1. The actual PUCCH-Resource is configured in PUCCH-Config of the PUCCH sSCell and referred to by its ID. See clause 9.2.3 of TS 38.213.

Number of configured HARQ processes for SPS DL (see clause 5.8.1 of TS 38.321). If UE is configured with nrofHARQ-Processes-v1710 UE shall ignore nrofHARQ-Processes (without suffix).

Number of repetitions for SPS PDSCH (see clause 5.1.2.1 of TS 38.214). When the field is absent, the UE applies the value 1 for MBS multicast data and the pdsch-AggregationFactor in pdsch-Config for other data.

Periodicity for DL SPS (see TS 38.214, and clause 5.8.1 of TS 38.321).

This field is used to calculate the periodicity for DL SPS (see TS 38.214 and see clause 5.8.1 of TS 38.321). If this field is present, the field periodicity is ignored. The following periodicities are supported depending on the configured subcarrier spacing [ms]: periodicityExt-r17 is only applicable for SCS 480 kHz and 960 kHz.

Indicates the index of one of multiple SPS configurations.

Indicates the maximum number of slots or subslots the transmission of DL SPS HARQ-ACK in a slot or subslot can be deferred (see clause 9.2.5.4 of TS 38.213).

Indicates the maximum payload size for the corresponding PUCCH resource ID.

Indicates the PUCCH resource ID

Indicates the CC index in one CC set for Type A (see TS 38.212, clause 7.3.1, 11.4 of TS 38.213). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA.

Indicates the CC set index for Type A associated (see TS 38.212, clause 7.3.1, 11.4 of TS 38.213). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA. The network does not configure this field to 3 in this release of specification.

A set of serving cells for monitoring PDCCH conveying SRS DCI format with CRC scrambled by TPC-SRS-RNTI (see TS 38.212, clause 7.3.1, 11.3 of TS 38.213).

Indicates the serving cell whose UL transmission may be interrupted during SRS transmission on a PUSCH-less SCell. During SRS transmission on a PUSCH-less SCell, the UE may temporarily suspend the UL transmission on a serving cell with PUSCH in the same CG to allow the PUSCH-less SCell to transmit SRS. (see clause 6.2.1.3 of TS 38.214).

Network configures the UE with either typeA-SRS-TPC-PDCCH-Group or typeB-SRS-TPC-PDCCH-Group, if any.

Type A trigger configuration for SRS transmission on a PUSCH-less SCell (see clause 11.4 of TS 38.213). In this release, the network configures at most one entry (the first entry) of typeA, and the first entry corresponds to the serving cell in which the SRS-CarrierSwitching field is configured. SRS carrier switching to SUL carrier is not supported in this version of the specification.

Type B trigger configuration for SRS transmission on a PUSCH-less SCell (see clause 11.4 of TS 38.213).

A list of pairs of [cc-SetIndex; cc-IndexInOneCC-Set] (see TS 38.212, clause 7.3.1, 11.4 of TS 38.213). The network does not configure this field for typeB.

Indicates whether the single DCI-triggering SRS positioning resource sets across the linked carriers is enabled or not for bandwidth aggregation.

If the field is absent, UE applies TPC commands via accumulation. If disabled, UE applies the TPC command without accumulation (this applies to SRS when a separate closed loop is configured for SRS) (see clause 7.3 of TS 38.213).

Cyclic shift configuration (see clause 6.2.1 of TS 38.214).

Cyclic shift configuration (see clause 6.2.1 of TS 38.214).

Cyclic shift configuration (see clause 6.2.1 of TS 38.214).

Configures UE with comb offset hopping. The hoppingId is used to initialize pseudo random comb offset hopping. If UE is configured with both comb offset and cyclic shift hopping, only one hoppingId is configured. The hoppingWithRepetition configures time-domain hopping behavior for repetition factor R > 1.

Configures UE with cyclic shift hopping. The hoppingId is used to initialize pseudo random cyclic shift hopping. If UE is configured with both comb offset and cyclic shift hopping, only one hoppingId is configured. The hoppingFinerGranularity enables finer granular hopping, see TSxxxxx. If hoppingSubset is configured, hoppingFinerGranularity is not configured.

When this RRC parameter is configured, start RB location hopping is enabled for partial frequency sounding in different SRS frequency hopping periods for periodic/semi-persistent/aperiodic SRS as described in clause 6.4.1.4 of TS 38.211.

Includes parameters capturing SRS frequency hopping (see clause 6.2.1 of TS 38.214). For CLI SRS-RSRP measurement, the network always configures this field such that b-hop > b-SRS. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area. c-SRS Indicates the maximum bandwidth. When TxHoppingConfig is configured the valid values for c-SRS are such that the maximum bandwidth is: 104 PRBs, 48 PRBs, 132 PRBs, 64 PRBs, for 15,30,60,120 KHz respectively. The same value for c-SRS is configured for all the hops when TxHoppingConfig is configured.

Parameter(s) for configuring group or sequence hopping (see clause 6.4.1.4.2 of TS 38.211). For CLI SRS-RSRP measurement, the network always configures this parameter to 'neither'. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

Number of ports. For CLI SRS-RSRP measurement, the network always configures this parameter to 'port1'.

Number of ports if the number of antenna ports is 8. The value 'ports8' configures UE with 8 antenna ports and the value 'ports8tdm' configures the UE with 8 antenna ports which are partitioned into 2 subsets with each subset having 4 different ports, and the subsets are mapped to different OFDM symbols, see Reference XXX. If combOffsetHopping-r18 or cyclicShiftHopping-r18 is configured, this field is not set to ports8tdm. If this field is present UE ignores the field nrofSRS-Ports.

Periodicity and slot offset for this SRS resource. All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity sl1 the offset is 0 slots (see clause 6.2.1 of TS 38.214). For CLI SRS-RSRP measurement, sl1280 and sl2560 cannot be configured. For SRS-PosResource, values sl20480, sl40960 and sl81920 cannot be configured for SCS=15kHz, values sl40960 and sl81920 cannot be configured for SCS=30kHz, and value sl81920 cannot be configured for SCS=60kHz. When periodicityAndOffset-p-Ext is present, periodicityAndOffset-p shall be ignored by the UE.

Periodicity and slot offset for this SRS resource. All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity sl1 the offset is 0 slots (see clause 6.2.1 of TS 38.214). For SRS-PosResource, values sl20480, sl40960 and sl81920 cannot be configured for SCS=15kHz, values sl40960 and sl81920 cannot be configured for SCS=30kHz, and value sl81920 cannot be configured for SCS=60kHz. When periodicityAndOffset-sp-Ext is present, periodicityAndOffset-sp shall be ignored by the UE.

The PTRS port index for this SRS resource for non-codebook based UL MIMO. This is only applicable when the corresponding PTRS-UplinkConfig is set to CP-OFDM. The ptrs-PortIndex configured here must be smaller than the maxNrofPorts configured in the PTRS-UplinkConfig (see clause 6.2.3.1 of TS 38.214). This parameter is not applicable to CLI SRS-RSRP measurement.

OFDM symbol location of the SRS resource within a slot including nrofSymbols (number of OFDM symbols), startPosition (value 0 refers to the last symbol, value 1 refers to the second last symbol, and so on) and repetitionFactor (see clause 6.2.1 of TS 38.214, and clause 6.4.1.4 of TS 38.211). The configured SRS resource does not exceed the slot boundary. If resourceMapping-r16 is signalled, UE shall ignore the resourceMapping (without suffix). If resourceMapping-r17 is signalled, resourceMapping-r16 is not signalled and the UE shall ignore the resourceMapping (without suffix) and only the values of nrofSymbols which are integer multiples of the configured repetitionFactor can be configured. The network can only signal repetitionFactor-v1730 if resourceMapping-r17 is signalled. When repetitionFactor-v1730 is signalled, the UE shall ignore repetitionFactor-r17. For CLI SRS-RSRP measurement, the network always configures nrofSymbols and repetitionFactor to 'n1'. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

Periodicity and offset for semi-persistent and periodic SRS resource, or slot offset for aperiodic SRS resource for positioning (see clause 6.2.1 of TS 38.214). For CLI SRS-RSRP measurement, only 'periodic' is applicable for resourceType. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

Sequence ID used to initialize pseudo random group and sequence hopping (see clause 6.2.1 of TS 38.214). For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS (see clause 6.2.1 of TS 38.214). This parameter is not applicable to CLI SRS-RSRP measurement. This field is not configured if unifiedTCI-StateType is configured for the serving cell.

Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS-PDC (see clause 6.2.1 of TS 38.214). The field is present in case of resourceType=periodic and usagePDC-r17=true in the SRS-ResourceSet, otherwise the field is absent.

Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS (see clause 6.2.1 of TS 38.214). If the IE srs-ResourceId-Ext is present, the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 63. Otherwise the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 31.

Indicates whether the current SFN is even or odd SFN for SRS for Positioning transmission. If this filed is not configured, the UE assumes that SRS for positioning periodictity longer than one SFN is not configured.

Indicate the number of bits for "SRS request"in DCI format 0_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 0_2 is applied. If the parameter srs-RequestDCI-0-2 is configured to value 1, 1 bit is used to indicate one of the first two rows of Table 7.3.1.1.2-24 in TS 38.212 for triggered aperiodic SRS resource set. If the value 2 is configured, 2 bits are used to indicate one of the rows of Table 7.3.1.1.2-24 in TS 38.212. When UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication.

Indicate the number of bits for "SRS request" in DCI format 1_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 1_2 is applied. When the UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication (see clause 6.1.1.2 of TS 38.214).

List of SRS resource set to be added or modified for DCI format 0_2 (see clause 7.3.1 of TS 38.212).

List of SRS resource set to be released for DCI format 0_2 (see clause 7.3.1 of TS 38.212).

Configuration of either a UL TCI state or a joint TCI state for the SRS resource. In case of UL TCI-State, refers to the TCI state defined in ul-TCI-StateList in the BWP-UplinkDedicated where the SRS-Config is configured. In case of joint TCI state, refers to a TCI state defined in dl-OrJointTCI-StateList in pdsch-Config of the BWP-DownlinkDedicated and serving cell indicated by cellAndBWP. This field is absent when the SRS resource is in an SRS-ResourceSet configured with followUnifiedTCI-StateSRS-r17 or applyIndicatedTCI-State, or when the field unifiedTCI-StateType is not configured to the serving cell which the SRS resource is located in.

Configures the UE with the startRBIndex and freqScalingFactor for partial frequency sounding as described in clause 6.4.1.4 in TS 38.211. The startRBIndexForFScaling2 gives the startRBIndex when freqScalingFactor is 2 and the startRBIndexForFScaling4 gives the startRBIndex when FreqScalingFactor is 4

Comb value (2 or 4 or 8) and comb offset (0..combValue-1) (see clause 6.2.1 of TS 38.214). If network configures field transmissionComb-n8, the UE ignores transmissionComb. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

alpha value for SRS power control (see clause 7.3 of TS 38.213). When the field is absent the UE applies the value 1. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

An additional list of DCI "code points" upon which the UE shall transmit SRS according to this SRS resource set configuration (see clause 6 of TS 38.214). When the field is not included during a reconfiguration of SRS-ResourceSet of resourceType set to aperiodic, UE maintains this value based on the Need M; that is, this list is not considered as an extension of aperiodicSRS-ResourceTrigger for purpose of applying the general rule for extended list in clause 6.1.3.

The DCI "code point" upon which the UE shall transmit SRS according to this SRS resource set configuration (see clause 6 of TS 38.214).

This field indicates, for an SRS-ResourceSet, if UE applies the first or the second "indicated" UL only TCI or joint TCI as specified in clause 6.2.1 of TS 38.214. If more than one value for the field coresetPoolIndex is configured in IE controlResourceSet for the BWP, the value 'first' corresponds to the "indicated" joint/UL TCI states specific to coresetPoolIndex value 0 and the value 'second' correspond to the value 1, respectively. When UE is configured with two SRS resource sets with usage set to Codebook or nonCodebook, network does not configure the first set with value 'second' or second set with value 'first'.

ID of CSI-RS resource associated with this SRS resource set in non-codebook based operation (see clause 6.1.1.2 of TS 38.214).

Indicates a list of up to four different available slot offset values from slot n+k to the slot where the aperiodic SRS resource set is transmitted, where slot n is the slot with the triggering DCI, and k is the slotOffset (without suffix) as described in clause 6.2.1 of TS 38.214.

ID of CSI-RS resource associated with this SRS resource set (see clause 6.1.1.2 of TS 38.214).

This field indicates a PRS configuration.

When set to enabled, for SRS resource Set, the UE applies the "indicated" UL only TCI or joint TCI as specified in clause 5.1.5 of TS 38.214. This parameter may be configured for aperiodic SRS for BM or SRS of any time-domain behavior for codebook, non-codebook, and antenna switching.

P0 value for SRS power control. The value is in dBm. Only even values (step size 2) are allowed (see clause 7.3 of TS 38.213). For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

A reference signal (e.g. a CSI-RS config or a SS block) to be used for SRS path loss estimation (see clause 7.3 of TS 38.213).

A reference signal (e.g. a SS block or a DL-PRS config) to be used for SRS path loss estimation (see clause 7.3 of TS 38.213).

Multiple candidate pathloss reference RS(s) for SRS power control, where one candidate RS can be mapped to SRS Resource Set via MAC CE (clause 6.1.3.27 in TS 38.321). The network can only configure this field if pathlossReferenceRS is not configured in the same SRS-ResourceSet.

Time domain behavior of SRS resource configuration, see clause 6.2.1 of TS 38.214. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS. The aperiodic SRS is not applicable for the UE in RRC_INACTIVE. For SRS for positioning configuration in multiple cells this field is commonly configured across cells within the validity area.

An offset in number of slots between the triggering DCI and the actual transmission of this SRS-ResourceSet. If the field is absent the UE applies no offset (value 0).

Indicates whether the current SFN is even or odd SFN for SRS for Positioning transmission. If this filed is not configured, the UE assumes that SRS for positioning periodictity longer than one SFN is not configured.

Indicates whether hsrs,c(i) = fc(i,1) or hsrs,c(i) = fc(i,2) (if twoPUSCH-PC-AdjustmentStates are configured) or separate close loop is configured for SRS. This parameter is applicable only for Uls on which UE also transmits PUSCH. If absent or release, the UE applies the value sameAs-Fci1 (see clause 7.3 of TS 38.213).

The IDs of the SRS-Resources/SRS-PosResource used in this SRS-ResourceSet/SRS-PosResourceSet. If this SRS-ResourceSet is configured with usage set to codebook, the srs-ResourceIdList contains at most 2 entries. If this SRS-ResourceSet is configured with usage set to nonCodebook, the srs-ResourceIdList contains at most 4 entries. For SRS for positioning configuration in multiple cells srs-PosResourceIdList is commonly configured across cells within the validity area.

The ID of this resource set. It is unique in the context of the BWP in which the parent SRS-Config is defined. For SRS for positioning configuration in multiple cells srs-PosResourceSetId is commonly configured across cells within the validity area.

Indicates SSB index belonging to a serving cell where the SRS is configured.

This field indicates a SSB configuration from neighboring cell.

Indicates if the SRS resource set is used for beam management, codebook based or non-codebook based transmission or antenna switching. See clause 6.2.1 of TS 38.214. Reconfiguration between codebook based and non-codebook based transmission is not supported.

If configured, it indicates that this SRS resource set is used for propagation delay compensation. The field can be present in only one SRS-ResourceSet.

Indicates CSI-RS index belonging to a serving cell.

This field indicates a PRS configuration.

Indicates whether the configured SRS spatial relation resource is a SRS-Resource or SRS-PosResource.

The serving Cell ID of the source SSB, CSI-RS, or SRS for the spatial relation of the target SRS resource. If this field is absent the SSB, the CSI-RS, or the SRS is from the same serving cell where the SRS is configured.

Indicates SSB index belonging to a serving cell.

This field indicates a SSB configuration from neighboring cell.

This field specifies the physical cell ID of the neighbour cell or NCD-SSB of the serving cell for which SSB configuration is provided.

This field specifies the index of the SSB for a neighbour cell or NCD-SSB of the serving cell. See TS 38.213. If this field is absent, the UE determines the ssb-IndexNcell of the physicalCellId based on its SSB measurement from the cell.

This field specifies the full configuration of the SSB. If this field is absent, the UE obtains the configuration for the SSB from nr-SSB-Config received as part of DL-PRS assistance data in LPP, see TS 37.355, by looking up the corresponding SSB configuration using the field physicalCellId.

This field specifies the UE specific TRP ID (see TS 37.355) for which PRS configuration is provided.

This field specifies the PRS-ResourceSet ID of a PRS resourceSet.

This field specifies the PRS-Resource ID of a PRS resource. If this field is absent, the UE determines the dl-PRS-ResourceID based on its PRS measurement from the TRP (see TS 37.355) and DL-PRS Resource Set.

Indicates whether SSB is in the first half or the second half of the frame. Value zero indicates the first half and value 1 indicates the second half.

Indicates the subframe boundary offset of the cell in which SSB is transmited.

Indiactes the time offset of the SFN0 slot 0 for the cell with respect to SFN0 slot 0 of serving cell.

Specifies the SFN offset between the cell in which SSB is transmited and serving cell. The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of serving cell to the beginning of the closest subsequent radio frame #0 of the cell in which SSB is transmitted.

Indicates the SFN offset of the transmitted SSB relative to the start of the SSB period. Value 0 indicates that the SSB is transmitted in the first system frame, value 1 indicates that SSB is transmitted in the second system frame and so on. The network configures this field according to the field ssb-Periodicity such that the indicated system frame does not exceed the configured SSB periodicity.

Indicates the frequency of the SSB.

Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see clause 7 of TS 38.213.

Indicates the periodicity of the SSB. If the field is absent, the UE applies the value ms5. (see clause 4.1 of TS 38.213).

Subcarrier spacing of SSB. Only the following values are applicable depending on the used frequency:

This field specifies the number of hops. The configured values are 2,3,4,5,6.

This field specifies the overlap during SRS transmission in terms of number of resource blocks. Value zeroRB implies 0 PRB, value oneRB corresponds to 1 PRB, value twoRB corresponds to 2 PRBs and so on. The same value for the overlapValue is configured to all the hops.

This field specifies the starting slot offset and starting symbol for the SRS resource with tx hopping for different resource types (aperiodic, semi-persistent or periodic SRS transmission). Each hop is configured with the same periodcity.

Indicates the duration of the uplink transmission window. Value s1 indicates 1 slot, s2 indicates 2 slot and so on.

Indicates the Periodicity and slot offset for uplink transmission window occurrence.

Indicates the SRS Positioning Resource set carrier frequency that is linked for bandwidth aggregation.

Indicates the SRS Positioning Resource set that is linked for bandwidth aggregation.

Indicates the SRS Positioning Resource set uplink bandwidth ID that is linked for bandwidth aggregation.

The type of a field within the group DCI with SRS request fields (optional), which indicates how many bits in the field are for SRS request (0 or 2). Note that for Type A, there is a common SRS request field for all SCells in the set, but each SCell has its own TPC command bits. See clause 7.3.1 of TS 38.212 and clause 11.3 of TS 38.213.

The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands. The value 1 of the field corresponds to the first/left most bit of format2-3. The value 2 of the field corresponds to the second bit format2-3, and so on (see clause 7.3.1 of TS 38.212 and clause 11.3 of TS 38.213).

The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands for SUL carrier (see clause 7.3.1 of TS 38.212 and clause 11.3 of TS 38.213).

Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see clause 4.1 of TS 38.213).

Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see clause 5.5.2.10. Periodicity and offset are given in number of subframes.

PCIs that follow this SMTC.

Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see clause 4.1 of TS 38.213).

PCIs that follow this SMTC, used for IAB-node discovery.

Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes.

The set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS block index 0, the second bit corresponds to SS block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS block is not to be measured while value 1 indicates that the corresponding SS block is to be measured (see TS 38.215). When the field is not configured the IAB-MT measures on all SS blocks. Regardless of the value of this field, SS blocks outside of the applicable smtc are not to be measured. See clause 5.1.1 of TS 38.215.

PCIs that follow this SMTC.

Offset of the measurement window in which to receive SS/PBCH blocks, see clause 5.5.2.10. Offset is given in number of subframes.

PCI of the additional SSB different from serving cell PCI.

Periodicity of the SS/PBCH blocks, see clause 5.5.2.10. Periodicity is given in number of subframes.

Indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in clause 4.1 of TS 38.213. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted.

Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see clause 7 of TS 38.213.

Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in clause 4.1 of TS 38.213. For operation with shared spectrum channel access in FR2-2, if the k-th bit is set to 1, the UE assumes that one or more SS/PBCH blocks within the SMTC measurement duration with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to (k- 1) may be transmitted; if the k-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted.

Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in clause 4.1 of TS 38.213. For operation with shared spectrum channel access, if the k-th bit is set to 1, the UE assumes that one or more SS/PBCH blocks within the SMTC measurement duration with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k - 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL-Common and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1's in the bitmap. If ssb-PositionQCL is configured with a value smaller than ssb-PositionQCL-Common, only the leftmost K bits (K = ssb-PositionQCL) are applicable for the corresponding cell.

Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in clause 4.1 of TS 38.213.

Within a slot that is configured for RSSI measurements (see measurementSlots) the UE measures the RSSI from symbol 0 to symbol endSymbol. This field identifies the entry in Table 5.1.3-1 in TS 38.215, which determines the actual end symbol.

Indicates the slots in which the UE can perform RSSI measurements. The length of the BIT STRING is equal to the number of slots in the configured SMTC window (determined by the duration and by the subcarrierSpacing). The first (left-most / most significant) bit in the bitmap corresponds to the first slot in the SMTC window, the second bit in the bitmap corresponds to the second slot in the SMTC window, and so on. The UE measures in slots for which the corresponding bit in the bitmap is set to 1. In case this field is configured for a SCell with ca-SlotOffset-r16, the bits in the bitmap corresponds to the slots that are fully contained in the SMTC window.

Indicates the TAG of the SpCell or an SCell, see TS 38.321. Uniquely identifies the TAG within the scope of a Cell Group (i.e. MCG or SCG).

The timeAlignmentTimer for TAG with ID tag-Id, as specified in TS 38.321.

Offset for TA reporting as specified in TS 38.321. Network only configures this parameter for MCG. For ATG, network only configures offsetThresholdTA-r18 in unit of symbols.

Used to configure whether a Timing Advance report may trigger a Scheduling Request as specified in TS 38.321.

Indicates the TCI state for PDCCH for each configured CORESET of the DL BWP to be activated at SCell activation, to be activated for the PSCell at SCG activation and/or to be used for BFD, RLM and measurements while the SCG is deactivated. The list includes exactly as many entries as CORESETs configured in this BWP, ordered by increasing values of ControlResourceSet-Id, i.e. the first entry indicates the TCI state for the configured CORESET with the lowest ControlResourceset-Id value, the second value indicates the TCI states for the configured CORESET with the second lowest ControlResourceset-Id value, and so on.

Indicates TCI states for PDSCH reception at SCell addition/activation or of the PSCell at SCG activation. This field indicates activated TCI state(s) for this BWP ordered by increasing values of TCI-StateId, i.e. the first bit indicates the activation state of the TCI state with the lowest TCI-StateId value, the second value indicates the activation status of the TCI state with the second lowest TCI-State-Id value, and so on. A bit set to 0 indicates that the corresponding TCI state is deactivated, a bit set to 1 indicates that the TCI state is activated.

The DL BWP which the RS is located in. If the field is absent, the RS is located in the DL BWP in which the TCI-State is applied by the UE.

The UE's serving cell in which the referenceSignal is configured. If the field is absent, the referenceSignal is configured in the serving cell in which the TCI-State is applied by the UE. The RS can be located on a serving cell other than the serving cell for which the TCI-State is applied by the UE only if the qcl-Type is configured as typeC or typeD. If the referenceSignal is set to csi-rs and unifiedTCI-StateType is configured, either both cell and bwp-Id are present or both cell and bwp-Id are absent. See clause 5.1.5 of TS 38.214.

Reference signal with which quasi-collocation information is provided as specified in clause 5.1.5 of TS 38.214.

QCL type as specified in clause 5.1.5 of TS 38.214.

Indicates the physical cell IDs (PCI) of the SSBs when referenceSignal is configured as SSB for both QCL-Type1 and QCL-Type2. In case the cell is present, the additionalPCI refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell indicated by the field cell. Otherwise, it refers to a PCI value configured in a list additionalPCI-ToAddModList configured in the serving cell where the TCI-State is applied by the UE. When this field is present the cell for qcl-Type1 and qcl-Type2 is configured with same value, if present.

The ID of the reference signal (e.g. a CSI-RS or an SS block) used for PUSCH, PUCCH and SRS path loss estimation. This field refers to an element in the list configured using pathlossReferenceRSToAddModList in the serving cell and UL BWP where the TCI State is applied by the UE.

QCL information for the TCI state as specified in clause 5.1.5 of TS 38.214.

It indicates the TAG that is associated with this TCI state, value n0 means the TCI state associate with the TAG indicated by tag-Id, value n1 means this TCI state associated with the TAG indicated by tag2-Id. The tag_id_ptr refers to the TAG of the serving cell where the TCI state is applied.

ID number of the TCI state.

Configures power control parameters for PUCCH, PUSCH and SRS for this TCI state. The field is present here only if ul-powerControl is not configured in any BWP-Uplink-Dedicated of this serving cell. This field refers to an element in the list configured using uplink-PowerControlToAddModList in the serving cell where the dl-OrJointTCI-StateToAddModList is configured.

Indicates the physical cell IDs (PCI) of the SSBs when referenceSignal is configured as SSB. In case the servingCellId is present, the additionalPCI refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell indicated by the field servingCellId. Otherwise, it refers to a PCI value configured in the list configured using additionalPCI-ToAddModList in the serving cell where the ul-TCI-StateList is applied by the UE.

The DL BWP which the CSI-RS is located in or UL BWP where the SRS is located in.

The UE's serving cell in which the referenceSignal is configured. If the field is absent, the referenceSignal is configured in the serving cell in which the TCI-UL-State is applied by the UE.

The ID of the reference Signal (e.g. a CSI-RS or a SS block) used for PUSCH, PUCCH and SRS path loss estimation. This field refers to an element in the list configured using pathlossReferenceRSToAddModList in the serving cell and UL BWP where the UL TCI State is applied by the UE.

It indicates the TAG that is associated with this TCI state, value n0 means the TCI state associate with the TAG indicated by tag-Id, value n1 means this TCI state associated with the TAG indicated by tag2-Id. The tag_id_ptr refers to the TAG of the serving cell where the TCI state is applied.

Configures power control parameters for PUCCH, PUSCH and SRS for this TCI state. The field is present here only if ul-powerControl is not configured in any BWP-Uplink-Dedicated of this serving cell. This field refers to an element in the list configured using uplink-PowerControlToAddModList in the serving cell where the ul-TCI-ToAddModList is configured.

Reference SCS used to determine the time domain boundaries in the UL-DL pattern which must be common across all subcarrier specific carriers, i.e., independent of the actual subcarrier spacing using for data transmission. Only the following values are applicable depending on the used frequency: The network configures a not larger than any SCS of configured BWPs for the serving cell. The network or SL-PreconfigGeneral configures a not larger than the SCS of (pre-)configured SL BWP.See clause 11.1 of TS 38.213.

Periodicity of the DL-UL pattern, see clause 11.1 of TS 38.213. If the dl-UL-TransmissionPeriodicity-v1530 is signalled, UE shall ignore the dl-UL-TransmissionPeriodicity (without suffix).

Number of consecutive full DL slots at the beginning of each DL-UL pattern, see clause 11.1 of TS 38.213. In this release, the maximum value for this field is 320.

Number of consecutive DL symbols in the beginning of the slot following the last full DL slot (as derived from nrofDownlinkSlots). The value 0 indicates that there is no partial-downlink slot. (see clause 11.1 of TS 38.213).

Number of consecutive full UL slots at the end of each DL-UL pattern, see clause 11.1 of TS 38.213. In this release, the maximum value for this field is 320.

Number of consecutive UL symbols in the end of the slot preceding the first full UL slot (as derived from nrofUplinkSlots). The value 0 indicates that there is no partial-uplink slot. (see clause 11.1 of TS 38.213).

The slotSpecificConfigurationToAddModList allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon, see clause 11.1 of TS 38.213.

The slotSpecificConfigurationToAddModList-IAB-MT allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon with a limitation that effectively only flexible symbols can be overwritten in Rel-16.

The slotSpecificConfigurationsToReleaseList-IAB-MT allows release of a set of slot configuration previously add with slotSpecificConfigurationToAddModList-IAB-MT.

Number of consecutive DL symbols in the beginning of the slot identified by slotIndex. If the field is absent the UE assumes that there are no leading DL symbols. (see clause 11.1 of TS 38.213).

Number of consecutive UL symbols in the end of the slot identified by slotIndex. If the field is absent the UE assumes that there are no trailing UL symbols. (see clause 11.1 of TS 38.213).

Identifies a slot within a slot configuration period given in tdd-UL-DL-configurationCommon, see clause 11.1 of TS 38.213.

The direction (downlink or uplink) for the symbols in this slot. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively.

The symbols-IAB-MT is used to configure an IAB-MT with the SlotConfig applicable for one serving cell. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively; value explicit-IAB-MT indicates explicitly how many symbols in the beginning and end of this slot are allocated to uplink and downlink, respectively.