Content for  TS 38.331  Word version:  17.3.0

This ID is used in the DCI Format 2_5 payload to dynamically select this AvailabilityCombination, see TS 38.213, clause 14.

Indicates the resource availability of soft symbols for a set of consecutive slots in the time domain. The meaning of this field is described in TS 38.213, Table 14.3. If included in RB-SetGroup within AvailabilityCombinationRB-Groups-r17, it indicates the availability of soft resources for an RB set group. If included in AvailabilityCombinationRB-Groups-r17 when the rb-SetGroups is not configured, it indicates the availability of soft resources in one or multiple slots for all RB sets of a DU cell.

The ID of the IAB-DU cell for which the availabilityCombinations are applicable.

The (starting) position (bit) of the availabilityCombinationId for the indicated IAB-DU cell (iab-DU-CellIdentity) within the DCI payload. If positionInDCI-AI-RBGroups is not configured, it applies to the availabilityCombinationId included in availabilityCombinations and in availabilityCombinationsRBGroups. If positionInDCI-AI-RBGroups is configured, it applies to the availabilityCombinationId included in availabilityCombinations.

The (starting) position (bit) of the availabilityCombinationId associated to the availabilityCombinationsRBGroups for the indicated IAB-DU cell (iab-DU-CellIdentity) within the DCI payload.

Indicates the RB set groups configured for the availability combination. Each group includes consecutive RB sets.

Indicates the one or more RB set indexes associated to one or more RB sets configured for one RB set group.

Used by an IAB-MT for detection of DCI format 2_5 indicating AvailabilityCombinationId for an IAB-DU's cells.

A list of availabilityCombinations to add for the IAB-DU's cells. (see TS 38.213, clause 14).

A list of availabilityCombinations to release for the IAB-DU's cells. (see TS 38.213, clause 14).

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

The ID of a destination IAB-node or IAB-donor-DU used in the BAP header.

The ID of a path used in the BAP header.

Timer for beam failure recovery timer. Upon expiration of the timer the UE does not use CFRA for BFR. Value in ms. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on.

Set of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated RA parameters. This set includes all elements of candidateBeamRSList (without suffix) and all elements of candidateBeamRSListExt-v1610. The UE maintains candidateBeamRSList and candidateBeamRSListExt-v1610 separately: Receiving candidateBeamRSListExt-v1610 set to release releases only the entries that were configured by candidateBeamRSListExt-v1610, and receiving candidateBeamRSListExt-v1610 set to setup replaces only the entries that were configured by candidateBeamRSListExt-v1610 with the newly signalled entries. The network configures these reference signals to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided.

Subcarrier spacing for contention free beam failure recovery (see TS 38.211, clause 5.3.2). Only the following values are applicable depending on the used frequency:

L1-RSRP threshold used for determining whether a candidate beam may be used by the UE to attempt contention free random access to recover from beam failure (see TS 38.213, clause 6).

Parameters which apply for prioritized random access procedure for BFR (see TS 38.321, clause 5.1.1).

Parameters which apply for prioritized 2-step random access procedure for BFR (see TS 38.321, clause 5.1.1).

Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321. The mask is valid for all SSB resources.

Configuration of random access parameters for BFR.

Search space to use for BFR RAR. The network configures this search space to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided. The CORESET associated with the recovery search space cannot be associated with another search space. Network always configures the UE with a value for this field when contention free random access resources for BFR are configured.

PRACH root sequence index (see TS 38.211, clause 6.3.3.1) for beam failure recovery.

Indicates that UE is configured to send BFR MAC CE for SpCell BFR as specified in TS 38.321.

Number of SSBs per RACH occasion for CF-BFR, see TS 38.213, clause 8.1.

The ID of a NZP-CSI-RS-Resource configured in the CSI-MeasConfig of this serving cell. This reference signal determines a candidate beam for beam failure recovery (BFR).

RA occasions that the UE shall use when performing BFR upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots. If the field is absent the UE uses the RA occasion associated with the SSB that is QCLed with this CSI-RS.

The RA preamble index to use in the RA occasions associated with this CSI-RS. If the field is absent, the UE uses the preamble index associated with the SSB that is QCLed with this CSI-RS.

The preamble index that the UE shall use when performing BFR upon selecting the candidate beams identified by this SSB.

The ID of an SSB transmitted by this serving cell. It determines a candidate beam for beam failure recovery (BFR).

A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery. The network always configures this parameter in every instance of this IE.

A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery.

L1-RSRP threshold used for determining whether a candidate beam may be included by the UE in BFR MAC CE (see TS 38.213, clause 6). The network always configures this parameter in every instance of this IE.

Up to 2 bits HARQ-ACK (see TS 38.213, clause 9.3). When the field is absent the UE applies the value 11.

Up to 11 bits HARQ-ACK (see TS 38.213, clause 9.3). When the field is absent the UE applies the value 11.

Above 11 bits HARQ-ACK (see TS 38.213, clause 9.3). When the field is absent the UE applies the value 11.

Up to 11 bits of CSI part 1 bits (see TS 38.213, clause 9.3). When the field is absent the UE applies the value 13.

Above 11 bits of CSI part 1 bits (see TS 38.213, clause 9.3). When the field is absent the UE applies the value 13.

Up to 11 bits of CSI part 2 bits (see TS 38.213, clause 9.3). When the field is absent the UE applies the value 13.

Above 11 bits of CSI part 2 bits (see TS 38.213, clause 9.3). When the field is absent the UE applies the value 13.

ID used for the MAC logical channel.

ID used for the MAC logical channel.

Indicates the logical channel id for BH RLC channel of the IAB-node.

Indicates the BH RLC channel in the link between IAB-MT of the IAB-node and IAB-DU of the parent IAB-node or IAB-donor-DU.

Indicates that RLC should be re-established.

Determines the RLC mode (UM, AM) and provides corresponding parameters.

Value in number of subframes. Value sf20 corresponds to 20 subframes, sf40 corresponds to 40 subframes, and so on.

Value in number of subframes. Value sf1 corresponds to 1 subframe, value sf5 corresponds to 5 subframes and so on.

Value in number of subframes. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes and so on.

Indicates whether to use the extended cyclic prefix for this bandwidth part. If not set, the UE uses the normal cyclic prefix. Normal CP is supported for all subcarrier spacings and slot formats. Extended CP is supported only for 60 kHz subcarrier spacing. (see TS 38.211, clause 4.2). Except for SUL, the network ensures the same cyclic prefix length is used in active DL BWP and active UL BWP within a serving cell.

Frequency domain location and bandwidth of this bandwidth part. The value of the field shall be interpreted as resource indicator value (RIV) as defined TS 38.214 with assumptions as described in TS 38.213, clause 12)TS 38.213, clause 12)

Subcarrier spacing to be used in this BWP for all channels and reference signals unless explicitly configured elsewhere. Corresponds to subcarrier spacing according to TS 38.211, table 4.2-1. The value kHz15 corresponds to μ=0, value kHz30 corresponds to μ=1, and so on. Only the following values are applicable depending on the used frequency: For the initial DL BWP and operation in licensed spectrum this field has the same value as the field subCarrierSpacingCommon in MIB of the same serving cell. Except for SUL, the network ensures the same subcarrier spacing is used in active DL BWP and active UL BWP within a serving cell. For the initial DL BWP and operation with shared spectrum channel access, the value of this field corresponds to the subcarrier spacing of the SSB associated to the initial DL BWP.

An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP.

Cell specific parameters for the PDCCH of this BWP. This field is absent for a dormant BWP.

Cell specific parameters for the PDSCH of this BWP.

Configuration of candidate RS for beam failure recovery on SCells.

Configuration of candidate RS for beam failure recovery on the SpCell. This field can only be configured when beamfailure is configured in RadioLinkMonitoringConfig.

UE specific common frequency resource configuration for MBS multicast for one dedicated BWP. This field can be configured within at most one serving cell.

Indicates a list of DL-PRS processing window configurations to be added or modified for the dedicated DL BWP.

Indicates a list of DL-PRS processing window configurations to be released for the dedicated DL BWP.

If enabled, UE reports ACK/NACK for the first SPS PDSCH after activation, regardless of if HARQ feedback is enabled or disabled corresponding to the first SPS PDSCH after activation. Otherwise, UE follows configuration of HARQ feedback enabled/disabled corresponding to the first SPS PDSCH after activation.

If configured, the RedCap UE operating in this BWP uses this SSB for the purposes for which it would otherwise have used the CD-SSB of the serving cell (e.g. obtaining sync, measurements, RLM). Furthermore, other parts of the BWP configuration that refer to an SSB (e.g. the "SSB" configured in the QCL-Info IE; the "ssb-Index" configured in the RadioLinkMonitoringRS; CFRA-SSB-Resource; PRACH-ResourceDedicatedBFR) refer implicitily to this NCD-SSB. The NCD-SSB has the same values for the properties (e.g., ssb-PositionsInBurst, PCI, ssb-periodicity, ssb-PBCH-BlockPower) of the corresponding CD-SSB apart from the values of the properties configured in the NonCellDefiningSSB-r17 IE.

UE specific PDCCH configuration for one BWP.

UE specific PDSCH configuration for one BWP.

Indicates whether the pre-configured measurement gaps (i.e. the gaps configured with preConfigInd) are activated or deactivated upon the switch to this BWP. If this field is configured, the UE shall apply network-controlled mechanism for activation and deactivation of the pre-configured measurement gaps, otherwise the UE shall apply the autonomous activation/deactivation mechanism, as specified in TS 38.133. The first/leftmost bit corresponds to the measurement gap with gap ID 1, the second bit corresponds to measurement gap with gap ID 2, and so on. Value 0 indicates that the corresponding pre-configured measurement gap is deactivated while value 1 indicates that the corresponding pre-configured measurement gap is activated. The UE shall ignore the bit if the corresponding measurement gap is not a pre-configured measurement gap.

measObjectId of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and nonCellDefiningSSB in BWP-DownlinkDedicated of the associated downlink BWP: if ssbFrequency is configured, its value is the same as the absoluteFrequencySSB in the nonCellDefiningSSB. If the field is present in a downlink BWP and the BWP is activated, the RedCap UE uses this measurement object for serving cell measurements, otherwise, the RedCap UE uses the servingCellMO in ServingCellConfig IE.

UE specific SPS (Semi-Persistent Scheduling) configuration for one BWP. Except for reconfiguration with sync, the NW does not reconfigure sps-Config when there is an active configured downlink assignment (see TS 38.321). However, the NW may release the sps-Config at any time. Network can only configure SPS in one BWP using either this field or sps-ConfigToAddModList.

Indicates a list of the deactivation states in which each state can be mapped to a single or multiple SPS configurations to be deactivated, see clause 10.2 of TS 38.213. If a state is mapped to multiple SPS configurations, each of these SPS configurations is configured with the same harq-CodebookID.

Indicates a list of one or more DL SPS configurations to be added or modified in one BWP. Except for reconfiguration with sync, the NW does not reconfigure a SPS configuration when it is active (see TS 38.321).

Indicates a list of one or more DL SPS configurations to be released. The NW may release a SPS configuration at any time.

UE specific configuration of radio link monitoring for detecting cell- and beam radio link failure occasions. The maximum number of failure detection resources should be limited up to 8 for both cell and beam radio link failure detection. For SCells, only periodic 1-port CSI-RS can be configured in IE RadioLinkMonitoringConfig.

Indicates the UE specific PDCCH configurations for receiving the SL grants (via SL-RNTI or SL-CS-RNTI) for NR sidelink communication/discovery.

Indicates the UE specific PDCCH configurations for receiving SL grants (i.e. sidelink SPS) for V2X sidelink communication.

An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP.

List of feature or feature combination-specific RACH configurations, i.e. the RACH configurations configured in addition to the one configured by rach-ConfigCommon and by msgA-ConfigCommon. The network associates all possible preambles of an additional RACH configuration to one or more feature(s) or feature combination(s). The network does not configure this list to have more than 16 entries. If both rach-ConfigCommon and msgA-ConfigCommon are configured for a specific FeatureCombination, the network always provides them in the same additionalRACH-Config.

Indicates whether or not the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep should override the ra-PrioritizationForAccessIdentity. The field is applicable only when the UE is configured by upper layers with both NSAG and Access Identity 1 or 2. If value TRUE is configured, the UE should only apply the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep. If value FALSE is configured, the UE should only apply ra-PrioritizationForAccessIdentity. If the field is absent, whether to use ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep or ra-PrioritizationForAccessIdentity is up to UE implementation.

Configuration of eight candidate MCS indexes for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. Only the first 4 configured or default MCS indexes are used for PUSCH transmission scheduled by RAR UL grant. This field is only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon, the UE shall apply the values {0, 1, 2, 3, 4, 5, 6, 7} (see TS 38.214, clause 6.1.4).

Configuration of the cell specific PRACH and PUSCH resource parameters for transmission of MsgA in 2-step random access type procedure. The NW can configure msgA-ConfigCommon only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial BL BWP

The number of repetitions for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. This field is only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon, the UE shall apply the values {n1, n2, n3, n4} (see TS 38.214, clause 6.1.2.1).

Cell specific parameters for the PUCCH of this BWP.

Cell specific parameters for the PUSCH of this BWP.

Configuration of cell specific random access parameters which the UE uses for contention based and contention free random access as well as for contention based beam failure recovery in this BWP. The NW configures SSB-based RA (and hence RACH-ConfigCommon) only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial DL BWP or for RedCap UEs DL BWPs associated with nonCellDefiningSSB or the RedCap-specific initial downlink BWP. The network configures rach-ConfigCommon, whenever it configures contention free random access (for reconfiguration with sync or for beam failure recovery).

Configuration of cell specific random access parameters for the IAB-MT. The IAB specific IAB RACH configuration is used by IAB-MT, if configured.

Threshold used by the UE for determining whether to select resources indicating Msg3 repetition in this BWP, as specified in TS 38.321. The field is mandatory if both set(s) of Random Access resources with MSG3 repetition indication and set(s) of Random Access resources without MSG3 repetition indication are configured in the BWP. It is absent otherwise.

If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for cell-specific PUSCH, e.g., PUSCH scheduled by RAR UL grant (see TS 38.213, clause 8.3.2.2) and uses interlaced PUCCH Format 0 and 1 for cell-specific PUCCH (see TS 38.213 [13], clause 9.2.1).TS 38.214, clause 6.1.2.2TS 38.213, clause 9.2.1).

Configuration of beam failure recovery. If supplementaryUplink is present, the field is present only in one of the uplink carriers, either UL or SUL.

A Configured-Grant of type1 or type2. It may be configured for UL or SUL but in case of type1 not for both at a time. Except for reconfiguration with sync, the NW does not reconfigure configuredGrantConfig when there is an active configured uplink grant Type 2 (see TS 38.321). However, the NW may release the configuredGrantConfig at any time. Network can only configure configured grant in one BWP using either this field or configuredGrantConfigToAddModList.

Indicates a list of one or more configured grant configurations to be added or modified for one BWP. Except for reconfiguration with sync, the NW does not reconfigure a Type 2 configured grant configuration when it is active (see TS 38.321). The network configures multiple CG configurations for one BWP with either all configurations or no configuration configured with cg-RetransmissionTimer-r16.

Indicates a list of one or more UL Configured Grant configurations to be released. The NW may release a configured grant configuration at any time.

Indicates a list of the deactivation states in which each state can be mapped to a single or multiple Configured Grant type 2 configurations to be deactivated when the corresponding deactivation DCI is received, see clause 7.3.1 in TS 38.212 and clause 10.2 in TS 38.213.

Configures the cyclic prefix (CP) extension (see TS 38.211, clause 5.3.1). For 15 kHz SCS, {1..28} are valid for both cp-ExtensionC2 and cp-ExtensionC3. For 30 kHz SCS, {1..28} are valid for cp-ExtensionC2 and {2..28} are valid for cp-ExtensionC3. For 60 kHz SCS, {2..28} are valid for cp-ExtensionC2 and {3..28} are valid for cp-ExtensionC3.

Configures parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321.

A list of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for path loss estimation for PUSCH, PUCCH and SRS for unified TCI state operation. If unifiedTCI-StateType is not configured for the serving cell, no element in this list is configured.

PUCCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL, the network configures PUCCH only on the BWPs of one of the uplinks (normal UL or SUL). The network configures PUCCH-Config at least on non-initial BWP(s) for SpCell and PUCCH SCell. If supported by the UE, the network may configure at most one additional SCell of a cell group with PUCCH-Config (i.e. PUCCH SCell). If PUCCH cell switching is supported by the UE, the network may configure two TDD serving cells with PUCCH-Config within each PUCCH group. For supporting PUCCH cell switching in the PUCCH group with the SpCell, the TDD SpCell and one TDD SCell shall have PUCCH-Config on their normal UL. For supporting PUCCH cell switching in the PUCCH group with only SCells, two TDD SCells shall have PUCCH-Config on their normal UL. In (NG)EN-DC and NE-DC, the NW configures at most one serving cell per frequency range with PUCCH. In (NG)EN-DC and NE-DC, if two PUCCH groups are configured, the serving cells of the NR PUCCH group in FR2 use the same numerology. For NR-DC, the maximum number of PUCCH groups in each cell group is one, and only the same numerology is supported for the cell group with carriers only in FR2. The NW may configure PUCCH for a BWP when setting up the BWP. The network may also add/remove the pucch-Config in an RRCReconfiguration with reconfigurationWithSync (for SpCell or PUCCH SCell) or with SCell release and add (for PUCCH SCell) to move the PUCCH between the UL and SUL carrier of one serving cell. In other cases, only modifications of a previously configured pucch-Config are allowed. If one (S)UL BWP of a serving cell is configured with PUCCH, all other (S)UL BWPs must be configured with \break:10 PUCCH, too.

PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks (see TS 38.213, clause 9.1). Different PUCCH Resource IDs are configured in different PUCCH-Config within the pucch-ConfigurationList if configured.

PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks for MBS multicast (see TS 38.213, clause 9).

PUCCH configurations for two simultaneously constructed NACK-only feedback for MBS multicast (see TS 38.213, clause 9).

PUSCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL and if it has a PUSCH-Config for both UL and SUL, an UL/SUL indicator field in DCI indicates which of the two to use. See TS 38.212, clause 7.3.1.

PUCCH configuration for the HARQ-ACK codebook for MBS multicast when multicast feedback is not configured with a priority value (see TS 38.213, clause 9). If the field is not configured, pucch-Config applies.

PUCCH configuration for the NACK-only feedback for MBS multicast when multicast feedback is not configured with a priority value (see TS 38.213, clause 9). If the field is not configured, pucch-Config applies.

Indicates the UE specific PUCCH configurations used for the HARQ-ACK feedback reporting for NR sidelink communication.

Uplink sounding reference signal configuration.

Configures power control parameters for PUCCH, PUSCH and SRS when UE is configured with unifiedTCI-StateType for this serving cell. For each serving cell, ul-powerControl is either configured in all BWP-UplinkDedicated or it is not configured in any BWP-UplinkDedicated. When unifiedTCI-StateRef in the BWP-UplinkDedicated of a serving cell refers to another serving cell, ul-powerControl is either configured in all BWP-UplinkDedicated of these two serving cells or it is not configured in any BWP-UplinkDedicated of these two serving cells.

Indicates the applicable UL TCI states for PUCCH, PUSCH and SRS.

Indicates a list of UL TCI states.

Provides the serving cell and UL BWP where UL TCI states applicable to this UL BWP are defined.

If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for PUSCH (see TS 38.213, clause 8.3.2.2) and uses interlaced PUCCH Format 0, 1, 2, and 3 for PUCCH (see TS 38.213 [13], clause 9.2.1).TS 38.214, clause 6.1.2.2TS 38.213, clause 9.2.1).

Indicates the resource (i.e. SSB or CSI-RS) defining this beam resource.

If the field is absent, the RS belongs to the serving cell in which BeamFailureRecoveryRSConfig is configured.