Content for  TS 38.331  Word version:  18.0.0

If absent, UE assumes the trackingAreaCode of the serving cell.

This field provides satellite ephemeris either in format of position and velocity state vector or in format of orbital parameters. This field is excluded when determining changes in system information, i.e. changes to ephemerisInfo should neither result in system information change notifications nor in a modification of valueTag in SIB1.

Indicate the epoch time for the NTN assistance information. When explicitly provided through SIB, or through dedicated signaling, the EpochTime is the starting time of a DL sub-frame, indicated by a SFN and a sub-frame number signaled together with the assistance information. For serving cell, the field sfn indicates the current SFN or the next upcoming SFN after the frame where the message indicating the epochTime is received. For neighbour cell, the sfn indicates the SFN nearest to the frame where the message indicating the epochTime is received. The reference point for epoch time of the serving or neighbour NTN payload ephemeris and Common TA parameters is the uplink time synchronization reference point when this field is provided in an NTN cell and the gNB when this field is provided in a TN cell. If this field is absent for the serving cell, the epoch time is the end of SI window where this SIB19 is scheduled. This field is mandatory present when ntn-Config is provided in dedicated configuration. If this field is absent in ntn-Config provided via NTN-NeighCellConfig the UE uses epoch time of the serving cell, otherwise the field is based on the timing of the serving cell, i.e. the SFN and sub-frame number indicated in this field refers to the SFN and sub-frame of the serving cell. In case of handover or conditional handover, this field is based on the timing of the target cell, i.e. the SFN and sub-frame number indicated in this field refers to the SFN and sub-frame of the target cell. For the target cell the UE considers epoch time, indicated by the SFN and sub-frame number in this field, to be the frame nearest to the frame in which the message indicating the epoch time is received. This field is excluded when determining changes in system information, i.e. changes to epochTime should neither result in system information change notifications nor in a modification of valueTag in SIB1.

Scheduling offset used for the timing relationships that are modified for NTN (see TS 38.213). The unit of the field K_offset is number of slots for a given subcarrier spacing of 15 kHz. If the field is absent UE assumes value 0.

Scheduling offset provided by network if downlink and uplink frame timing are not aligned at gNB. If the field is absent UE assumes value 0. In FR1, the unit of kmac is number of slots for a given subcarrier spacing of 15 kHz.

If present, this parameter indicates polarization information for downlink transmission on service link: including Right hand, Left hand circular polarizations (RHCP, LHCP) and Linear polarization.

If present, this parameter indicates Polarization information for uplink service link. If not present and ntn-PolarizationDL is present, UE assumes the same polarization for UL and DL.

A validity duration configured by the network for assistance information (i.e. Serving and/or neighbour satellite ephemeris and Common TA parameters) which indicates the maximum time duration (from epochTime) during which the UE can apply assistance information without having acquired new assistance information. The unit of ntn-UlSyncValidityDuration is second. Value s5 corresponds to 5 s, value s10 indicate 10 s and so on. This parameter applies to both connected and idle mode UEs. If this field is absent in ntn-Config provided via NTN-NeighCellConfig, the UE uses validity duration from the serving cell assistance information. This field is excluded when determining changes in system information, i.e. changes of ntn-UlSyncValidityDuration should neither result in system information change notifications nor in a modification of valueTag in SIB1. ntn-UlSyncValidityDuration is only updated when at least one of epochTime, ta-Info, ephemerisInfo is updated.

Network-controlled common timing advanced value and it may include any timing offset considered necessary by the network. ta-Common with value of 0 is supported. The granularity of ta-Common is 4.072 × 10^(-3) μs. Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-Common should neither result in system information change notifications nor in a modification of valueTag in SIB1.

Indicate drift rate of the common TA. The granularity of ta-CommonDrift is 0.2 × 10^(-3) μs/s. Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-CommonDrift should neither result in system information change notifications nor in a modification of valueTag in SIB1.

Indicate drift rate variation of the common TA. The granularity of ta-CommonDriftVariant is 0.2×10^(-4) μs/s^2. Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-CommonDriftVariant should neither result in system information change notifications nor in a modification of valueTag in SIB1.

When this field is included in SIB19, it indicates reporting of timing advanced is enabled during Random Access due to RRC connection establishment or RRC connection resume, and during RRC connection reestablishment. When this field is included in ServingCellConfigCommon within dedicated signalling, it indicates TA reporting is enabled during Random Access due to reconfiguration with sync (see clause 5.4.8 of TS 38.321).

Periodicity and slot offset sl1 corresponds to a periodicity of 1 slot, sl2 to a periodicity of two slots, and so on. The corresponding offset is also given in number of slots (see clause 5.2.2.3.1 of TS 38.214). Network always configures the UE with a value for this field for periodic and semi-persistent NZP-CSI-RS-Resource (as indicated in CSI-ResourceConfig).

Power offset of PDSCH RE to NZP CSI-RS RE. Value in dB (see clauses 5.2.2.3.1 and 4.1 of TS 38.214). The UE shall ignore this field in case NZP-CSI-RS-Resources is received as part of an LTM-Candidate IE.

Power offset of NZP CSI-RS RE to SSS RE. Value in dB (see clause 5.2.2.3.1 of TS 38.214).

For a target periodic CSI-RS, contains a reference to one TCI-State in TCI-States for providing the QCL source and QCL type. For periodic CSI-RS, the source can be SSB or another periodic-CSI-RS. Refers to the TCI-State or dl-OrJoint-TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList or in dl-OrJointTCI-StateList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resource belongs to (see clause 5.2.2.3.1 of TS 38.214). In case NZP-CSI-RS-Resources is received as part of an LTM-Candidate IE, it refers to the TCI state identifier in CandidateTCI-State and is defined in ltm-DL-OrJointTCI-StateToAddModList within the LTM-Candidate IE.

OFDM symbol location(s) in a slot and subcarrier occupancy in a PRB of the CSI-RS resource.

Scrambling ID (see clause 5.2.2.3.1 of TS 38.214).

Offset X between the slot containing the DCI that triggers a set of aperiodic NZP CSI-RS resources and the slot in which the CSI-RS resource set is transmitted. For aperiodicTriggeringOffset, the value 0 corresponds to 0 slots, value 1 corresponds to 1 slot, value 2 corresponds to 2 slots, value 3 corresponds to 3 slots, value 4 corresponds to 4 slots, value 5 corresponds to 16 slots, value 6 corresponds to 24 slots. For aperiodicTriggeringOffset-r16 and aperiodicTriggeringOffset-r17, the value indicates the number of slots. aperiodicTriggeringOffset-r17 is applicable to SCS 480 kHz and 960 kHz, and only the values of integer multiples of 4 are valid, i.e. 0, 4, 8, and so on. The network configures only one of the fields. When neither field is included, the UE applies the value 0. This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE.

Indicates triggering offset of aperiodic NZP CSI-RS resources used for fast activation of the SCell (see clause 5.2.1.5.3 of TS 38.214), when the NZP CSI-RS resources are activated by the MAC CE (see clause 5.9 of TS 38.321). The value indicates the number of slots. This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE.

Configures CMR groups and pairs. The first nrofResourcesGroup1 resources in the NZP-CSI-RS resource set belong to Group 1 and the remaining resources in the NZP-CSI-RS resource set belong to Group 2. nrofResourcesGroup1 is K_1 and the number of remaining resources in the NZP-CSI-RS resource set belonging to Group 2 is K_2 as specified in clause 5.2.1.4.1 of TS 38.214. Maximum total number in Group 1 and Group 2 is 8 (see clauses 5.2.1.4.1 and 5.2.1.4.2 of TS 38.214). This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE.

A pair of NZP CSI-RS resources. In one pair, one resource shall belong to group 1 and the other resource shall belong to group 2 (see clause 5.2.1.4.1 of TS 38.214).

NZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set (see clause 5.2 of TS 38.214). For CSI, there are at most 8 NZP CSI RS resources per resource set. For Doppler or Doppler-PS codebook operation there are at most 1 P/SP NZP CSI-RS resource and 4, 8 or 12 AP NZP CSI-RS resources and for CJT or CJT-PS, there are 1, 2, 3, or 4 AP/P/SP NZP-CSI-RS resources, see clause 5.2.1.4 of TS 38.214.

The nzp-CSI-RS-ResourceId1-r17 represents the index of the NZP CSI-RS resource in Resource Group 1, and nzp-CSI-RS-ResourceId2-r17 represents the index of the NZP CSI-RS resource in Resource Group 2.

Indicates that this NZP-CSI-RS-ResourceSet, if configured also with trs-Info, is used for propagation delay compensation. The field can be present only if trs-info is present. The field can be present in only one NZP-CSI-RS-ResourceSet. If network configures this field for an NZP-CSI-RS-ResourceSet, the UE measures the UE Rx-Tx time difference based on resources configured in this resource set. This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE.

Indicates whether repetition is on/off. If the field is set to off or if the field is absent, the UE may not assume that the NZP-CSI-RS resources within the resource set are transmitted with the same downlink spatial domain transmission filter (see clauses 5.2.2.3.1 and 5.1.6.1.2 of TS 38.214). It can only be configured for CSI-RS resource sets which are associated with CSI-ReportConfig with report of L1 RSRP, L1 SINR or "no report". This field is not present in case NZP-CSI-RS-ResourcesSet is received as part of an LTM-Candidate IE.

Indicates that the antenna port for all NZP-CSI-RS resources in the CSI-RS resource set is same. If the field is absent or released the UE applies the value false (see clause 5.2.2.3.1 of TS 38.214).

Time domain behavior of resource configuration (see clause 5.2.1.2 of TS 38.214).

Indicates the physical cell ID (PCI) of the SSB for the referenceSignal.

Indicates the number of physical cell identities in the range (including start). Value n4 corresponds with 4, value n8 corresponds with 8 and so on. The UE shall apply value 1 in case the field is absent, in which case only the physical cell identity value indicated by start applies.

Indicates the lowest physical cell identity in the range.

Physical cell identity or a range of physical cell identities.

List of UE specifically configured Control Resource Sets (CORESETs) to be used by the UE. The network restrictions on configuration of CORESETs per DL BWP are specified in clause 10.1 of TS 38.213, and TS 38.306. The UE shall consider entries in controlResourceSetToAddModList and in controlResourceSetToAddModListSizeExt as a single list, i.e. an entry created using controlResourceSetToAddModList can be modified using controlResourceSetToAddModListSizeExt (or deleted using controlResourceSetToReleaseListSizeExt) and vice-versa. In case network reconfigures control resource set with the same ControlResourceSetId as used for commonControlResourceSet or commonControlResourceSetExt configured via PDCCH-ConfigCommon or via SIB20, the configuration from PDCCH-Config always takes precedence and should not be updated by the UE based on servingCellConfigCommon or based on SIB20.

List of UE specifically configured Control Resource Sets (CORESETs) to be released by the UE. This field only applies to CORESETs configured by controlResourceSetToAddModList or controlResourceSetToAddModListSizeExt and does not release the field commonControlResourceSet configured by PDCCH-ConfigCommon and commonControlResourceSetExt configured by SIB20.

Configuration of downlink preemption indications to be monitored in this cell (see clause 11.2 of TS 38.213).

Configures either Rel-15 PDCCH monitoring capability, Rel-16 PDCCH monitoring capability or Rel-17 PDCCH monitoring capability for PDCCH monitoring on a serving cell (see clause 10.1 of TS 38.213). Value r15monitoringcapability enables the Rel-15 monitoring capability, and value r16monitoringcapability enables the Rel-16 PDCCH monitoring capability. r17monitoringcapability enables the Rel-17 PDCCH multi-slot monitoring capability. For 480 and 960 kHz SCS, only value r17monitoringcapability is applicable.

This field is used to enable UE PDCCH monitoring resumption after PDCCH skipping has started, if the UE transmits a NACK due to incorrectly decoding a PDSCH scheduled by a DCI format received from the serving cell (see clause 10.4 of TS 38.213).

Provides one or more values to derive the skipping duration in unit of slots, as specified in clause 10.4 of TS 38.213. The DCI which schedules data indicates which of the values is to be applied (see clause 10.4 of TS 38.213). For the 15kHz SCS, for each entry, only the first 26 values are valid and correspond to {1, 2, 3, …, 20, 30, 40, 50, 60, 80, 100}. For the 30kHz SCS, for each entry, only the first 46 values are valid and correspond to {1, 2, 3, …, 40, 60, 80, 100, 120, 160, 200}. For the 60kHz SCS, for each entry, only the first 86 values are valid and correspond to {1, 2, 3, …, 80, 120, 160, 200, 240, 320, 400}. For the 120kHz SCS, for each entry, the 166 values correspond to {1, 2, 3, …, 160, 240, 320, 400, 480, 640, 800}. For the 480kHz SCS, for each entry, the 166 values correspond to {4, 8, 12, …, 640, 960, 1280, 1600, 1920, 2560, 3200}. For the 960kHz SCS, for each entry, the 166 values correspond to {8, 16, 24, …, 1280, 1920, 2560, 3200, 3840, 5120, 6400}.

List of UE specifically configured Search Spaces or MBS multicast Search Spaces. The network configures at most 10 Search Spaces per BWP per cell (including UE-specific and common Search Spaces). If the network includes searchSpacesToAddModListExt, it includes the same number of entries, and listed in the same order, as in searchSpacesToAddModList in each of them.

Configuration to control the UE behavior to switch from search space group X back to search space group 0, as specified in clause 10 of TS 38.213. The network only configures either searchSpaceSwitchConfig-r16 or searchSpaceSwitchConfig-r17 for a UE.

Enable and configure reception of group TPC commands for PUCCH.

Enable and configure reception of group TPC commands for PUSCH.

Enable and configure reception of group TPC commands for SRS.

Configuration of uplink cancellation indications to be monitored in this cell (see clause 11.2A of TS 38.213).

The list of serving cells which are bundled for the search space group switching purpose (see clause 10.4 of TS 38.213). A serving cell can belong to only one CellGroupForSwitch. The network configures the same list for all BWPs of serving cells in the same CellGroupForSwitch.

Indicates the value to be applied by a UE for Search Space Set Group switching; corresponds to the P value in clause 10.4 of TS 38.213. The network configures the same value for all BWPs of serving cells in the same CellGroupForSwitch. For 120/480/960 kHz SCS, only values 40,41, ... 52 are valid and the actual value = field value * SCS/120 kHz i.e. field value 40 corresponds to 40 with 120 kHz SCS, 160 with 480 kHz SCS and 320 with 960 kHz SCS, and so on.

Timer (in unit of slots) to control the UE behavior to switch from search space group X back to search space group 0, as specified in clause 10 of TS 38.213. For the 15kHz SCS, only the first 26 values are valid and correspond to {1, 2, 3, …, 20, 30, 40, 50, 60, 80, 100}. For the 30kHz SCS, only the first 46 values are valid and correspond to {1, 2, 3, …, 40, 60, 80, 100, 120, 160, 200}. For the 60kHz SCS, only the first 86 values are valid and correspond to {1, 2, 3, …, 80, 120, 160, 200, 240, 320, 400}. For the 120kHz SCS, the 166 values correspond to {1, 2, 3, …, 160, 240, 320, 400, 480, 640, 800}. For the 480kHz SCS, the 166 values correspond to {4, 8, 12, …, 640, 960, 1280, 1600, 1920, 2560, 3200}. For the 960kHz SCS, the 166 values correspond to {8, 16, 24, …, 1280, 1920, 2560, 3200, 3840, 5120, 6400}.

This field indicates, for PDCCH reception in CORESET #0, if UE applies the first, the second, both or none of the "indicated" DL only TCI or joint TCI as specified in clause 10.1 of TS 38.213.

An additional common control resource set which may be configured and used for any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetId other than 0 for this ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is contained in the bandwidth of CORESET#0. If the (e)RedCap-specific initial downlink BWP does not contain the entire CORESET#0, the network configures the commonControlResourceSet in the (e)RedCap-specific initial downlink BWP in SIB1 for (e)RedCap such that it does not have to be contained in the bandwidth of CORESET#0.

A list of additional common search spaces. If the network configures this field, it uses the SearchSpaceIds other than 0. If the field is included, it replaces any previous list, i.e. all the entries of the list are replaced and each of the SearchSpace entries is considered to be newly created and the conditions and Need codes for setup of the entry apply. If the network includes commonSearchSpaceListExt/commonSearchSpaceListExt2, it includes the same number of entries, and listed in the same order, as in commonSearchSpaceList.

Parameters of the common CORESET#0 which can be used in any common or UE-specific search spaces. The values are interpreted like the corresponding bits in MIB pdcch-ConfigSIB1. Even though this field is only configured in the initial BWP (BWP#0) controlResourceSetZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions defined in clause 10 of TS 38.213 are satisfied.

Offset, in number of symbols, from the start of the reference frame for PEI-O to the start of the first PDCCH monitoring occasion of PEI-O on this BWP, see clause 10.4A of TS 38.213. For the case po-NumPerPEI is smaller than Ns, UE applies the (floor(i_s/po-NumPerPEI)+1)-th value out of (N_s/po-NumPerPEI) configured values in firstPDCCH-MonitoringOccasionOfPEI-O for the symbol-level offset. When po-NumPerPEI is one or multiple of Ns, UE applies the first configured value in firstPDCCH-MonitoringOccasionOfPEI-O for the symbol-level offset.

Indicates the first PDCCH monitoring occasion of each PO of the PF on this BWP, see TS 38.304. The field sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT, sCS120KHZoneEighthT-SCS60KHZoneSixteenthT and sCS120KHZoneSixteenthT can be applied for SCS 480kHz, corresponding to sCS480KHZoneT-SCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT, sCS480KHZhalfT-SCS120KHZoneEighthT-SCS60KHZoneSixteenthT and sCS480KHZquarterT-SCS120KHZoneSixteenthT in IE DownlinkConfigCommonSIB respectively.

When set to enabled, for PDCCH reception in CORESET #0, the UE applies the "indicated" DL only TCI or joint TCI as specified in clause 5.1.5 of TS 38.214.

ID of the search space for paging (see clause 10.1 of TS 38.213). If the field is absent, the UE does not receive paging in this BWP (see clause 10 of TS 38.213). This field is absent for the (e)RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0. In that case, an (e)RedCap UE in RRC_IDLE or RRC_INACTIVE while SDT procedure is not ongoing, shall monitor paging in the initial DL BWP that includes CORESET#0.

Provides the configuration for PEI reception in this BWP. If the field is absent, the UE does not receive PEI in this BWP. For the initialDownlinkBWP-RedCap not including CD-SSB and the entire CORESET#0, a RedCap UE in RRC_IDLE or RRC_INACTIVE while SDT procedure is not ongoing monitors PEI in the initialDownlinkBWP that includes CORESET#0, if the initialDownlinkBWP is configured with pei-ConfigBWP.

ID of dedicated search space for PEI. It can be configured to one of up to 4 common SS sets configured by commonSearchSpaceList with SearchSpaceId > 0. The CCE aggregation levels and maximum number of PDCCH candidates per CCE aggregation level follows Table 10.1-1 of TS38.213 [13]. SearchSpaceId = 0 can be configured for the case of SS/PBCH block and CORESET multiplexing pattern 2 or 3.

ID of the Search space for random access procedure (see clause 10.1 of TS 38.213). If the field is absent, the UE does not receive RAR in this BWP. This field is mandatory present in the DL BWP(s) if the conditions described in clause 5.15 of TS 38.321 are met.

Common search space for CG-SDT and RA-SDT (see TS 38.213). If an existingSearchSpace is used, the network only signals the search space ID of the ra-SearchSpace.

ID of the search space for MCCH. If the field is absent, the UE does not receive MCCH in this BWP (see clause 10 of TS 38.213). This field is absent for the (e)RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0.

ID of the search space for MTCH of MBS broadcast. If the field is absent, the UE applies searchSpaceMCCH also for MTCH, (see clause 10 of TS 38.213). This field is absent for the (e)RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0.

ID of the search space for multicast MCCH. If the field is absent, the UE does not receive multicast MCCH in this BWP (see clause 10 of TS 38.213). This field is absent for the RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0.

ID of the search space for multicast MTCH. If the field is absent, the UE applies searchSpaceMulticastMCCH also for multicast MTCH, (see clause 10 of TS 38.213). This field is absent for the RedCap-specific initial downlink BWP, if it does not include CD-SSB and the entire CORESET#0.

ID of the Search space for other system information, i.e., SIB2 and beyond (see clause 10.1 of TS 38.213). If the field is absent, the UE does not receive other system information in this BWP. This field is absent for the (e)RedCap-specific initial DL BWP, if it does not include CD-SSB and the entire CORESET#0. In that case, an (e)RedCap UE in RRC_IDLE or RRC_INACTIVE shall monitor PDCCH to receive other system information using searchSpaceOtherSystemInformation in the initial DL BWP that includes CD-SSB and the entire CORESET#0.

ID of the search space for SIB1 message. In the initial DL BWP of the UE's PCell, the network sets this field to 0. If the field is absent, the UE does not receive SIB1 in this BWP. (see clause 10 of TS 38.213). This field is absent for the (e)RedCap-specific initial DL BWP, if it does not include CD-SSB and the entire CORESET#0. In that case, an (e)RedCap UE in RRC_IDLE or RRC_INACTIVE shall monitor PDCCH to receive SIB1 using searchSpaceSIB1 in the initial DL BWP that includes CD-SSB and the entire CORESET#0.

Parameters of the common SearchSpace#0. The values are interpreted like the corresponding bits in MIB pdcch-ConfigSIB1. Even though this field is only configured in the initial BWP (BWP#0), searchSpaceZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions described in clause 10 of TS 38.213 are satisfied.

Determines a common ControlResourceSet (CORESET) with ID #0, see clause 13 of TS 38.213.

Determines a common search space with ID #0, see clause 13 of TS 38.213.

Use to configure monitoring a PDCCH for Availability Indicators (AI).

The value of the timer in slots for monitoring PDCCH in the active DL BWP of the serving cell before moving to the default search space group (see clause 10.4 of TS 38.213). The network configures the same value for all serving cells in the same CellGroupForSwitch.

Configuration of Slot-Format-Indicators to be monitored in the correspondingly configured PDCCHs of this serving cell.

If included, ciphering is disabled for this DRB regardless of which ciphering algorithm is configured for the SRB/DRBs. The field may only be included if the UE is connected to 5GC. Otherwise the field is absent. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up.

Value in ms of discardTimer specified in TS 38.323. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms and so on. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.

Value in ms of discardTimer specified in TS 38.323. Value ms0dot5 corresponds to 0.5 ms, value ms1 corresponds to 1ms and so on. If this field is present, the field discardTimer is ignored and discardTimerExt is used instead.

Value in ms of discardTimerExt specified in TS 38.323. Value ms2000 corresponds to 2000 ms. If this field is present, the field discardTimer and discardTimerExt are ignored and discardTimerExt2 is used instead.

Value in ms of discardTimerForLowImportance specified in TS 38.323. Value ms0 corresponds to 0 ms, value ms2 corresponds to 2 ms and so on. The value of this timer for a PDCP entity is always configured shorter than discardTimer, discardTimerExt or discardTimerExt2, whichever is used for the PDCP entity.

Indicates whether the PDCP entity continues or resets the ROHC header compression protocol during PDCP re-establishment, as specified in TS 38.323. This field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. The network does not include the field if the bearer is configured as DAPS bearer. This field can be configured for both DRB and multicast MRB.

This field indicates the uplink PDCP duplication state for the associated RLC entities at the time of receiving this IE. If set to true, the PDCP duplication state is activated for the associated RLC entity. The index for the indication is determined by ascending order of logical channel ID of all RLC entities other than the primary RLC entity indicated by primaryPath in the order of MCG and SCG, as in clause 6.1.3.32 of TS 38.321. If the number of associated RLC entities other than the primary RLC entity is two, UE ignores the value in the largest index of this field. If the field is absent, the PDCP duplication states are deactivated for all associated RLC entities.

This fields configures Ethernet Header Compression. This field can only be configured for a bi-directional DRB or a bi-directional multicast MRB. The network reconfigures ethernetHeaderCompression only upon reconfiguration involving PDCP re-establishment and with neither drb-ContinueEHC-DL nor drb-ContinueEHC-UL configured. Network only configures this field when uplinkDataCompression is not configured.

If rohc is configured, the UE shall apply the configured ROHC profile(s) in both uplink and downlink. If uplinkOnlyROHC is configured, the UE shall apply the configured ROHC profile(s) in uplink (there is no header compression in downlink). ROHC can be configured for any bearer type. ROHC and EHC can be both configured simultaneously for a DRB or a multicast MRB. The network reconfigures headerCompression only upon reconfiguration involving PDCP re-establishment or involving PDCP entity reconfiguration to configure DAPS bearer(s), and without any drb-ContinueROHC. Network configures headerCompression to notUsed when outOfOrderDelivery is configured. Network only configures this field when uplinkDataCompression is not configured.

Indicates the initial value of RX_DELIV during PDCP window initialization for multicast MRB as specified in TS 38.323.

Indicates whether or not integrity protection is configured for this radio bearer. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up.

Indicates the value of the MAX_CID parameter as specified in TS 38.323. The total value of MAX_CIDs across all bearers for the UE should be less than or equal to the value of maxNumberROHC-ContextSessions parameter as indicated by the UE.

This field configures UL data transmission when more than one RLC entity is associated with the PDCP entity. This field is not present if the bearer is configured as DAPS bearer.

This field configures UL data transmission when more than two RLC entities are associated with the PDCP entity for DRBs.

Indicates whether or not outOfOrderDelivery specified in TS 38.323 is configured. This field should be either always present or always absent, after the radio bearer is established.

Indicates whether or not uplink duplication status at the time of receiving this IE is configured and activated as specified in TS 38.323. The presence of this field indicates that duplication is configured. PDCP duplication is not configured for CA packet duplication of LTE RLC bearer. The value of this field, when the field is present, indicates the state of the duplication at the time of receiving this IE. If set to true, duplication is activated. The value of this field is always true, when configured for a SRB. For PDCP entity with more than two associated RLC entities for UL transmission, this field is always present. If the field moreThanTwoRLC-DRB is present, the value of this field is ignored and the state of the duplication is indicated by duplicationState. For PDCP entity with more than two associated RLC entities, only NR RLC bearer is supported.

PDCP sequence number size for downlink, 12 or 18 bits, as specified in TS 38.323. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.

PDCP sequence number size for uplink, 12 or 18 bits, as specified in TS 38.323. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.

If set to true, the UE shall perform PDU set based discarding for this PDCP entity, as specified in TS 38.323.

Indicates the cell group ID and LCID of the primary RLC entity as specified in clause 5.2.1 of TS 38.323 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs, except for the split SRB2 of the IAB-MT, and except when the UE is required to set the primaryPath to refer to the SCG as specified in clause 5.7.3b.4. In this last case, if the network sends an RRCReconfiguration message (in NR-DC) or an EUTRA RRCConnectionReconfiguration message (in (NG)EN-DC) keeping SRB1 as split SRB, the network explicitly configures the primaryPath for the PDCP entity of SRB1 to refer to the MCG. In this version of the specification, only cell group ID corresponding to MCG is supported for DRBs when the SCG is deactivated. In MR-DC, the NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW always indicates logicalChannel if CA based PDCP duplication is configured in the cell group indicated by cellGroup of this field. In MP, when the primay path is set to indirect path, the field cellGroup and logicalChannel are absent, and the field primaryPathOnIndirectPath is set to true.

Indicates that the primary RLC entity is on indirect path for DRB when MP is configured.

Indicates the LCID of the split secondary RLC entity as specified in TS 38.323 for fallback to split bearer operation when UL data transmission with more than two RLC entities is associated with the PDCP entity. This RLC entity belongs to a cell group that is different from the cell group indicated by cellGroup in the field primaryPath.

For AM DRBs, AM MRBs and DAPS UM DRBs, indicates whether the DRB or the multicast MRB is configured to send a PDCP status report in the uplink, as specified in TS 38.323. For DAPS AM DRBs, it also indicates whether the DRB is configured to send a second PDCP status report in the uplink, as specified in TS 38.323.

Indicates whether the DRB associated with this PDCP entity has survival time state support. If this field is configured to be true, all associated RLC entities are activated for PDCP duplication upon reception of a retransmission grant addressed to CS-RNTI, as specified in TS 38.321.

Value in ms of t-Reordering specified in TS 38.323. Value ms0 corresponds to 0 ms, value ms20 corresponds to 20 ms, value ms40 corresponds to 40 ms, and so on. When the field is absent the UE applies the value infinity. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.

Parameter specified in TS 38.323. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting splitDRB-withUL-Both-MCG-SCG and when the SCG is deactivated. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied.

Indicates the UDC configuration that the UE shall apply. Network does not configure uplinkDataCompression for a DRB, if headerCompression or ethernetHeaderCompression is already configured or outOfOrderDelivery or DAPS is configured for the DRB. The maximum number of DRBs where uplinkDataCompression can be applied is two. The network reconfigures uplinkDataCompression only upon reconfiguration involving PDCP re-establishment. If the field is set to drb-ContinueUDC, the PDCP entity continues the uplink data compression protocol during PDCP re-establishment, as specified in TS 38.323. The field is set to drb-ContinueUDC only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated.

Indicates whether the PDCP entity continues or resets the downlink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated.

Indicates whether the PDCP entity continues or resets the uplink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated.

Indicates the length of the CID field for EHC packet. The value bits7 indicates the length is 7 bits, and the value bits15 indicates the length is 15 bits. Once the field ethernetHeaderCompression-r16 is configured for a DRB or a multicast MRB, the value of the field ehc-CID-Length for this DRB or multicast MRB is not reconfigured to a different value.

Indicates the configurations that apply for both downlink and uplink.

Indicates the configurations that apply for only downlink. If the field is configured, then Ethernet header compression is configured for downlink. Otherwise, it is not configured for downlink.

Indicates the configurations that apply for only uplink. If the field is configured, then Ethernet header compression is configured for uplnik. Otherwise, it is not configured for uplink.

Indicates the value of the MAX_CID_EHC_UL parameter as specified in TS 38.323. The total value of MAX_CID_EHC_UL across all bearers for the UE should be less than or equal to the value of maxNumberEHC-Contexts parameter as indicated by the UE.

This field indicates the buffer size applied for UDC as specified in TS 38.323. Value kbyte2 means 2048 bytes, kbyte4 means 4096 bytes and so on.

This field indicates which pre-defined dictionary is used for UDC as specified in TS 38.323. The value sip-SDP means that UE shall prefill the buffer with standard dictionary for SIP and SDP defined in TS 38.323, and the value operator means that UE shall prefill the buffer with operator-defined dictionary.

A set of assistance information for R-ML (reduced complexity ML) receivers with enhanced inter-user interference suppression for MU-MIMO transmissions.

Configure the presence of "Antenna ports" field in DCI format 1_2. When the field is configured, then the "Antenna ports" field is present in DCI format 1_2. Otherwise, the field size is set to 0 for DCI format 1_2 (See clause 7.3.1.1.3 of TS 38.212). If neither dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 nor dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 is configured, this field is absent.

AddMod/Release lists for configuring aperiodically triggered zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList). The network configures the UE with at most 3 aperiodic ZP-CSI-RS-ResourceSets and it uses only the ZP-CSI-RS-ResourceSetId 1 to 3. The network triggers a set by indicating its ZP-CSI-RS-ResourceSetId in the DCI payload. The DCI codepoint '01' triggers the resource set with ZP-CSI-RS-ResourceSetId 1, the DCI codepoint '10' triggers the resource set with ZP-CSI-RS-ResourceSetId 2, and the DCI codepoint '11' triggers the resource set with ZP-CSI-RS-ResourceSetId 3 (see clause 5.1.4.2 of TS 38.214). The field aperiodic-ZP-CSI-RS-ResourceSetsToAddModList applies to DCI format 1_1 and the field aperiodic-ZP-CSI-RS-ResourceSetsToAddModListDCI-1-2 applies to DCI format 1_2 (see clause 5.1.4.2 of TS 38.214 and clause 7.3.1 of TS 38.212).

Indicates the first slot to apply the unified TCI indicated by DCI as specified in clause 5.1.5 of TS 38.214. The value n1 means 1 symbol, n2 two symbols and so on. The first slot is at least Y symbols indicated by beamAppTime parameter after the last symbol of the acknowledgment of the joint or separate DL/UL beam indication. The same value shall be configured for all serving cells in any one of the simultaneousU-TCI-UpdateListN configured in IE CellGroupConfig based on the smallest SCS of the active BWP.

Identifier(s) used to initialize data scrambling (c_init) for PDSCH as specified in clause 7.3.1.1 of TS 38.211. The dataScramblingIdentityPDSCH2 is configured if coresetPoolIndex is configured with 1 for at least one CORESET in the same BWP.

A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports, PDCCH DMRS ports, and CSI-RS, and in case of join mode, also the PUSCH, PUCCH and SRS (see clause 5.1.5 of TS 38.214).

DMRS configuration for PDSCH transmissions using PDSCH mapping type A (chosen dynamically via PDSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeA applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 applies to DCI format 1_2 (see clause 7.3.1 of TS 38.212).

DMRS configuration for PDSCH transmissions using PDSCH mapping type B (chosen dynamically via PDSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeB applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 applies to DCI format 1_2 (see clause 7.3.1 of TS 38.212).

If configured, the UE may assume that the set of remaining orthogonal antenna ports, which are within the same code division multiplexing (CDM) group and have different frequency domain orthogonal cover codes (FD-OCC), are not associated with the PDSCH of another UE (see clause 5.1.6.2 of TS 38.214). It is applicable for PDSCH SCS of 480 and 960 kHz when rank 1 PDSCH with type-1 or type-2 DMRS is scheduled. If dmrs-TypeEnh-r18 is configured, this field is not configured.

Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 1_2 If the field is absent, then the UE applies the value of 0 bit for the field "DMRS Sequence Initialization" in DCI format 1_2. If the field is present, then the UE applies the value of 1 bit as in DCI format 1_2 (see clause 7.3.1 of TS 38.212).

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

Configure the number of bits for the field "HARQ process number" in DCI format 1_2 (see clause 7.3.1 of TS 38.212).

Indicates the maximum number of MIMO layers to be used for PDSCH in this DL BWP. If not configured, the UE uses the maxMIMO-Layers configuration in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs, when the UE operates in this BWP. The value of maxMIMO-Layers for a DL BWP shall be smaller than or equal to the value of maxMIMO-Layers configured in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs. For MBS multicast, indicates the maximum number of MIMO layers to be used for group-common PDSCH of MBS multicast in this CFR. If not configured for CFR, the UE applies value 1. The value of maxMIMO-Layers for a CFR shall be smaller than or equal to the value of maxMIMO-Layers configured in PDSCH-ServingCellConfig IE of the serving cell to which this CFR belongs.

Maximum number of code words that a single DCI may schedule. This changes the number of MCS/RV/NDI bits in the DCI message from 1 to 2.

Indicates which MCS table the UE shall use for PDSCH for DCI formats 1_0 and 1_1 (see clause 5.1.3.1 of TS 38.214). If all fields are absent the UE applies the value 64QAM. If the field mcs-Table-r17 is present for DCI format 1_1, the network does not configure the field mcs-Table (without suffix). For an (e)RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH.

Indicates which MCS table the UE shall use for PDSCH for DCI format 1_2 (see clause 5.1.3.1 of TS 38.214). If all fields are absent the UE applies the value 64QAM. If the field mcs-TableDCI-1-2-r17 is present, the network does not configure the field mcs-TableDCI-1-2-r16. For an (e)RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH.

List of minimum K0 values. Minimum K0 parameter denotes minimum applicable value(s) for the TDRA table for PDSCH and for A-CSI RS triggering Offset(s) (see clause 5.3.1 of TS 38.214).

Configures the number of bits for "Redundancy version" in the DCI format 1_2 (see clause 7.3.1 of TS 38.212 and clause 5.1.2.1 of TS 38.214).

Number of repetitions for data (see clause 5.1.2.1 of TS 38.214). When the field is absent in PDSCH-Config which is not used for MBS CFR, the UE applies the value 1.

When configured, enhanced Type 3 HARQ-ACK codebook triggering by DCI format 1_2 is enabled.

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

When configured, DCI format 1_2 can request the UE to report A/N for all HARQ processes and all component carriers configured in the PUCCH group (see clause 7.3.1 of TS 38.212).

When configured, DCI format 1_2 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource (see clause 9.1.5 of TS 38.213).

List of time-domain configurations for timing of DL assignment to DL data. The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0 and DCI format 1_1 (see table 5.1.2.1.1-1 in TS 38.214), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214). The field pdsch-TimeDomainAllocationListForMultiPDSCH applies to DCI format 1_1. The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config.

Indicates the PRB bundle type and bundle size(s) (see clause 5.1.2.3 of TS 38.214). If dynamic is chosen, the actual bundleSizeSet1 or bundleSizeSet2 to use is indicated via DCI. Constraints on bundleSize(Set) setting depending on vrb-ToPRB-Interleaver and rbg-Size settings are described in clause 5.1.2.3 of TS 38.214. If a bundleSize(Set) value is absent, the UE applies the value n2. The field prb-BundlingType applies to DCI format 1_1, and the field prb-BundlingTypeDCI-1-2 applies to DCI format 1_2 (see clause 7.3.1 of TS 38.212 and clause 5.1.2.3 of TS 38.214).

Configure the presence of "priority indicator" in DCI format 1_1/1_2/4_2. When the field is absent in the IE, then 0 bit for "priority indicator" in DCI format 1_1/1_2/4_2. The field priorityIndicatorDCI-1-1 applies to DCI format 1_1, the field priorityIndicatorDCI-1-2 applies to DCI format 1_2 and the field priorityIndicatorDCI-4-2 applies to DCI format 4_2, respectively (see clause 7.3.1 of TS 38.212 and clause 9 of TS 38.213).

When configured, PUCCH cell switching based on dynamic indication in DCI format 1_2 is enabled (see clause 9.A of TS 38.213).

A set of periodically occurring ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList). The network uses the ZP-CSI-RS-ResourceSetId=0 for this set. If p-ZP-CSI-RS-ResourceSet is configured in both PDSCH-Config for MBS CFR and PDSCH-Config for the associated BWP, it is subject to UE capability whether the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config for MBS CFR can be different from the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config for the assoicated BWP.

The IDs of a first group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig ->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI (see clause 5.1.4.1 of TS 38.214). The field rateMatchPatternGroup1 applies to DCI format 1_1, and the field rateMatchPatternGroup1DCI-1-2 applies to DCI format 1_2 (see clause 5.1.4.1 of TS 38.214).

The IDs of a second group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig ->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI (see clause 5.1.4.1 of TS 38.214). The field rateMatchPatternGroup2 applies to DCI format 1_1, and the field rateMatchPatternGroup2DCI-1-2 applies to DCI format 1_2 (see clause 5.1.4.1 of TS 38.214).

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 (see clause 5.1.4.1 of TS 38.214). If a RateMatchPattern with the same RateMatchPatternId is configured in both MBS CFR and its associated BWP, 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.

Selection between config 1 and config 2 for RBG size for PDSCH. The UE ignores this field if resourceAllocation is set to resourceAllocationType1 (see clause 5.1.2.2.1 of TS 38.214).

Enable using the starting symbol of the PDCCH monitoring occasion in which the DL assignment is detected as the reference of the SLIV for DCI format 1_2. When the RRC parameter enables the utilization of the new reference, the new reference is applied for TDRA entries with K0=0. For other entries (if any) in the same TDRA table, the reference is slot boundary as in Rel-15. PDSCH mapping type A is not supported with the new reference. The new reference of SLIV is not configured for a serving cell configured to be scheduled by cross-carrier scheduling on a scheduling cell with different numerology (see clause 7.3.1 of TS 38.212 and clause 5.1.2.1 of TS 38.214).

Configure the UE with repetition schemes. The network does not configure repetitionSchemeConfig-r16 and repetitionSchemeConfig-v1630 simultaneously to setup in the same PDSCH-Config. The network does not configure this parameter and sfnSchemePDSCH in MIMOParam-r17 simultaneously in the same serving cell.

Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see clause 5.1.2.2 of TS 38.214). The field resourceAllocation applies to DCI format 1_1, and the field resourceAllocationDCI-1-2 applies to DCI format 1_2 (see clause 5.1.2.2 of TS 38.214).

Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_2. If this field is absent, the granularity is 1 PRB (see clause 5.1.2.2.2 of TS 38.214).

Indicates the size of DCI format 4-2 (see clause 10.1 of TS 38.213).

AddMod/Release lists for configuring semi-persistent zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList) (see clause 5.1.4.2 of TS 38.214).

A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports (see clause 5.1.5 of TS 38.214). If unifiedTCI-StateType is configured for the serving cell, no element in this list is configured.

Provides the serving cell and BWP where the configuration for dl-OrJointTCI-StateToAddModList-r17 are defined. When this field is present, dl-OrJointTCI-StateToAddModList and dl-OrJointTCI-StateToReleaseList are not present. The value of unifiedTCI-StateType of current serving cell is the same in the serving cell indicated by unifiedTCI-StateRef.

Interleaving unit configurable between 2 and 4 PRBs (see clause 7.3.1.6 of TS 38.211). When the field is absent, the UE performs non-interleaved VRB-to-PRB mapping.

Accounts for an overhead from CSI-RS, CORESET etc. If the field is absent, the UE applies value xOh0 (see TS 38.214).

A list of Zero-Power (ZP) CSI-RS resources used for PDSCH rate-matching. Each resource in this list may be referred to from only one type of resource set, i.e., aperiodic, semi-persistent or periodic (see TS 38.214).

Configure the number of bits for the field "HARQ process number" in DCI format 1_3 (see clause 7.3.1 of TS 38.212).

Configures the number of bits for "Redundancy version" in the DCI format 1_3 (see clause 7.3.1 of TS 38.212, and clause 5.1.2.1 of TS 38.214).

Selection among config 1, config 2 and config 3 for RBG size for PDSCH. The UE ignores this field if resurceAllocationDCI-1-3 is set to resourceAllocationType1. (see clause 5.1.2.2.1 of TS 38.214).

Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see clause 5.1.2.2 of TS 38.214).

Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_3. If this field is absent, the granularity is 1 PRB (see clause 5.1.2.2.2 of TS 38.214).

List of time-domain configurations for timing of DL assignment to DL data (see table 5.1.2.1.1-1 in TS 38.214).

Indicates whether CBGFI for CBG based (re)transmission in DL is enabled (true). (see clause 7.3.1.2.2 of TS 38.212).

Maximum number of code-block-groups (CBGs) per TB. In case of multiple CW, the maximum CBG is 4 (see clause 9.1.1 of TS 38.213).

Enables and configures code-block-group (CBG) based transmission (see clause 9.1.1 of TS 38.213). Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. The network does not configure this field if

• the SCS of at least one DL BWP configured in the cell is 480 or 960 kHz
• Type-1 HARQ-ACK codebook is configured and pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for this serving cell contains pdsch-AllocationList with multiple entries (multiple PDSCH)
• Type-2 HARQ-ACK codebook is configured and pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for any cell in the same PUCCH cell group associated with this serving cell contains pdsch-AllocationList with multiple entries (multiple PDSCH)

Used to disable the DL HARQ feedback, sent in the uplink, per HARQ process ID. The first/leftmost bit corresponds to HARQ process ID 0, the next bit to HARQ process ID 1 and so on. Bits corresponding to HARQ process IDs that are not configured shall be ignored. The bit(s) set to one identify HARQ processes with disabled DL HARQ feedback and the bit(s) set to zero identify HARQ processes with enabled DL HARQ feedback.

Indicates the maximum number of MIMO layers to be used for PDSCH in all BWPs of this serving cell. (see clause 5.4.2.1 of TS 38.212).

The number of HARQ processes to be used on the PDSCH of a serving cell. Value n2 corresponds to 2 HARQ processes, value n4 to 4 HARQ processes, and so on. If both nrofHARQ-ProcessesForPDSCH and nrofHARQ-ProcessesForPDSCH-v1700 are absent, the UE uses 8 HARQ processes (see clause 5.1 of TS 38.214).

A list of configurations for up to two simultaneously constructed HARQ-ACK codebooks (see clause 9.3 of TS 38.213).

Enables configuration of advanced processing time capability 2 for PDSCH (see clause 5.3 of TS 38.214).

The ID of the serving cell (of the same cell group) to use for PUCCH. If the field is absent, the UE sends the HARQ feedback on the PUCCH of the SpCell of this cell group, or on this serving cell if it is a PUCCH SCell.

Accounts for overhead from CSI-RS, CORESET, etc. If the field is absent, the UE applies value xOh0 (see clause 5.1.3.2 of TS 38.214).