Content for  TS 38.331  Word version:  17.5.0

This field indicates the Rx-Tx time difference measurement, see TS 38.215, clause 10.1.25.3.1 of TS 38.133 for UE Rx-Tx time difference and clause 13.2.1 of TS 38.133 for gNB Rx-Tx time difference.

When this field is present, there are two bursts and it indicates the gap between the two bursts in number of slots. When this field is absent, there is a single burst.

Reference to TCI-State for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by resourceSet (see clause 5.1.6.1.1.1 of TS 38.214). TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink of this serving cell indicated by firstActiveDownlinkBWP-Id in the ServingCellConfig in which this IE is included.

nzp-CSI-ResourceSetId of the NZP-CSI-RS-ResourceSet of this serving cell used as resource configuration for one or two bursts for SCell activation. This NZP-CSI-RS-ResourceSet consists of four NZP CSI-RS resources in two consecutive slots with two NZP CSI-RS resources in each slot (see clause 5.1.6.1.1.1 of TS 38.214). The CSI-RS associated with this NZP-CSI-RS-ResourceSet are located in the BWP addressed by firstActiveDownlinkBWP-Id.

List of Scheduling Request configurations to add or modify. If schedulingRequestToAddModListExt is configured, it contains the same number of entries, and in the same order, as schedulingRequestToAddModList.

Used to modify a SR configuration and to indicate, in LogicalChannelConfig, the SR configuration to which a logical channel is mapped and to indicate, in SchedulingRequestresourceConfig, the SR configuration for which a scheduling request resource is used.

Timer for SR transmission on PUCCH in TS 38.321. Value is in ms. Value ms1 corresponds to 1ms, value ms2 corresponds to 2ms, and so on. If sr-ProhibitTimer-v1700 is configured, UE shall ignore sr-ProhibitTimer (without suffix). If both sr-ProhibitTimer (without suffix) and sr-ProhibitTimer-v1700 are absent, the UE applies the value 0.

Maximum number of SR transmissions as described in TS 38.321. Value n4 corresponds to 4, value n8 corresponds to 8, and so on.

SR periodicity and offset in number of symbols or slots (see clause 9.2.4 of TS 38.213) The following periodicities may be configured depending on the chosen subcarrier spacing: sym6or7 corresponds to 6 symbols if extended cyclic prefix and a SCS of 60 kHz are configured, otherwise it corresponds to 7 symbols. For periodicities 2sym, 7sym and sl1 the UE assumes an offset of 0 slots. If periodicityAndOffset-r17 is present, any previously configured periodicityAndOffset (without suffix) is released, and vice versa.

Indicates whether this scheduling request resource is high or low priority in PHY prioritization/multiplexing handling (see clause 9.2.4 of TS 38.213). Value p0 indicates low priority and value p1 indicates high priority.

ID of the PUCCH resource in which the UE shall send the scheduling request. The actual PUCCH-Resource is configured in PUCCH-Config of the same UL BWP and serving cell as this SchedulingRequestResourceConfig. The network configures a PUCCH-Resource of PUCCH-format0 or PUCCH-format1 (other formats not supported) (see clause 9.2.4 of TS 38.213)

The ID of the SchedulingRequestConfig that uses this scheduling request resource.

Width of this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier) (see clause 4.4.2 of TS 38.211).

Offset in frequency domain between Point A (lowest subcarrier of common RB 0) and the lowest usable subcarrier on this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier). The maximum value corresponds to 275*8-1. See clause 4.4.2 of TS 38.211.

Indicates the downlink Tx Direct Current location for the carrier. A value in the range 0..3299 indicates the subcarrier index within the carrier. The values in the value range 3301..4095 are reserved and ignored by the UE. If this field is absent for downlink within ServingCellConfigCommon and ServingCellConfigCommonSIB, the UE assumes the default value of 3300 (i.e. "Outside the carrier"). (see clause 4.4.2 of TS 38.211). Network does not configure this field via ServingCellConfig or for uplink carriers.

Subcarrier spacing of this carrier. It is used to convert the offsetToCarrier into an actual frequency. Only the following values are applicable depending on the used frequency:

Indicates whether or not this is the default DRB for this PDU session. Among all configured instances of SDAP-Config with the same value of pdu-Session, this field shall be set to true in at most one instance of SDAP-Config and to false in all other instances.

Indicates the list of QFIs of UL QoS flows of the PDU session to be additionally mapped to this DRB. A QFI value can be included at most once in all configured instances of SDAP-Config with the same value of pdu-Session. For QoS flow remapping, the QFI value of the remapped QoS flow is only included in mappedQoS-FlowsToAdd in sdap-Config corresponding to the new DRB and not included in mappedQoS-FlowsToRelease in sdap-Config corresponding to the old DRB.

Indicates the list of QFIs of QoS flows of the PDU session to be released from existing QoS flow to DRB mapping of this DRB.

Identity of the PDU session whose QoS flows are mapped to the DRB.

Indicates whether or not a SDAP header is present for UL data on this DRB. The field cannot be changed after a DRB is established. The network sets this field to present if the field defaultDRB is set to true.

Indicates whether or not a SDAP header is present for DL data on this DRB. The field cannot be changed after a DRB is established.

Configures this search space as common search space (CSS) and DCI formats to monitor.

The CORESET applicable for this SearchSpace. Value 0 identifies the common CORESET#0 configured in MIB and in ServingCellConfigCommon. Values 1..maxNrofControlResourceSets-1 identify CORESETs configured in System Information or by dedicated signalling. The CORESETs with non-zero controlResourceSetId are configured in the same BWP as this SearchSpace except commonControlResourceSetExt which is configured by SIB20. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix).

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

If configured, the UE monitors the DCI formats 0_0 and 1_0 according to clause 10.1 of TS 38.213.

If configured, UE monitors the DCI format 2_0 according to clause 10.1, 11.1.1 of TS 38.213.

If configured, UE monitors the DCI format 2_1 according to clause 10.1, 11.2 of TS 38.213.

If configured, UE monitors the DCI format 2_2 according to clause 10.1, 11.3 of TS 38.213.

If configured, UE monitors the DCI format 2_3 according to clause 10.1, 11.4 of TS 38.213.

If configured, UE monitors the DCI format 2_4 according to clause 11.2A of TS 38.213.

If configured, IAB-MT monitors the DCI format 2_5 according to clause 14 of TS 38.213.

If configured, UE monitors the DCI format 2_6 according to clause 10.1, 10.3 of TS 38.213. DCI format 2_6 can only be configured on the SpCell.

If configured, UE monitors the DCI format 2_7 according to clause 10.1, 10.4A of TS 38.213.

If configured, the UE monitors the DCI format 4_0 with CRC scrambled by MCCH-RNTI/G-RNTI according to clause 10.1 of TS 38.213.

If configured, the UE monitors the DCI format 4_1 and 4_2 with CRC scrambled by G-RNTI/G-CS-RNTI according to clause 11.1 of TS 38.213.

If configured, the UE monitors the DCI format 4_1 with CRC scrambled by G-RNTI/G-CS-RNTI according to clause 10.1 of TS 38.213.

If configured, the UE monitors the DCI format 4_2 with CRC scrambled by G-RNTI/G-CS-RNTI according to clause 10.1 of TS 38.213.

Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.

If this field is present, the field dci-Formats is ignored and dci-FormatsExt is used instead to indicate whether the UE monitors in this USS for DCI format 0_2 and 1_2 or formats 0_1 and 1_1 and 0_2 and 1_2 (see clause 7.3.1 of TS 38.212 and clause 10.1 of TS 38.213). This field is not configured for operation with shared spectrum channel access in this release.

Indicates whether the IAB-MT monitors the DCI formats 2-5 according to clause 14 of TS 38.213.

Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1 or for format 3-0 or for format 3-1 or for formats 3-0 and 3-1. If this field is present, the field dci-Formats is ignored and dci-FormatsSL is used.

Number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset. If the field is absent, the UE applies the value 1 slot, except for DCI format 2_0. The UE ignores this field for DCI format 2_0. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset). For SCS 480 kHz and SCS 960 kHz, duration-r17 is used, and the configured duration is restricted to be an integer multiple of L slots and smaller than periodicity, where L is the configured length of the bitmap monitoringSlotsWithinSlotGroup-r17. If duration-r17 is absent, the UE assumes the duration in slots is equal to L. The maximum valid duration is periodicity-L. For IAB-MT, duration indicates number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset. If the field is absent, the IAB-MT applies the value 1 slot, except for DCI format 2_0 and DCI format 2_5. The IAB-MT ignores this field for DCI format 2_0 and DCI format 2_5. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset).

Defines an association of the search space to multiple monitoring locations in the frequency domain and indicates whether the pattern configured in the associated CORESET is replicated to a specific RB set, see clause 10.1 of TS 38.213. Each bit in the bitmap corresponds to one RB set, and the leftmost (most significant) bit corresponds to RB set 0 in the BWP. A bit set to 1 indicates that a frequency domain resource allocation replicated from the pattern configured in the associated CORESET is mapped to the RB set.

Slots for PDCCH Monitoring configured as periodicity and offset. For SCS 15, 30, 60, and 120 kHz and if the UE is configured to monitor:

• DCI format 2_1, only the values 'sl1', 'sl2' or 'sl4' are applicable.
• DCI format 2_0, only the values 'sl1', 'sl2', 'sl4', 'sl5', 'sl8', 'sl10', 'sl16', and 'sl20' are applicable (see clause 10 of TS 38.213).
• DCI format 2_4, only the values 'sl1', 'sl2', 'sl4', 'sl5', 'sl8' and 'sl10' are applicable.

For SCS 480 kHz and if the UE is configured to monitor:

• DCI format 2_0, only the values 'sl8', 'sl16', 'sl32', 'sl40', 'sl64', 'sl80', 'sl128', and 'sl160' are applicable.
• DCI format 2_1, only the values 'sl8', 'sl16', and 'sl32' are applicable.
• DCI format 2_4, only the values 'sl4', 'sl8', 'sl16', 'sl20', 'sl32', 'sl40' are applicable.

For SCS 960 kHz and if the UE is configured to monitor:

• DCI format 2_0, only the values 'sl4', 'sl8', 'sl16', 'sl20', 'sl32', 'sl40', 'sl64', and 'sl80' are applicable.
• DCI format 2_1, only the values 'sl4', 'sl8', and 'sl16' are applicable.
• DCI format 2_4, only the values 'sl8', 'sl16', 'sl32', 'sl40', 'sl64', 'sl80' are applicable.

For SCS 480 kHz and SCS 960 kHz, and the configured periodicity and offset are restricted to be an integer multiple of L slots, where L is the configured length of the bitmap provided by monitoringSlotsWithinSlotGroup-r17, i.e. for a given periodicity, the offset has a range of {0, L, 2*L, …, L*FLOOR(1/L*(periodicity-1))}. For IAB-MT, If the IAB-MT is configured to monitor DCI format 2_1, only the values 'sl1', 'sl2' or 'sl4' are applicable. If the IAB-MT is configured to monitor DCI format 2_0 or DCI format 2_5, only the values 'sl1', 'sl2', 'sl4', 'sl5', 'sl8', 'sl10', 'sl16', and 'sl20' are applicable (see clause 10 of TS 38.213). If monitoringSlotPeriodicityAndOffset-v1710 is present, any previously configured monitoringSlotPeriodicityAndOffset is released, and if monitoringSlotPeriodicityAndOffset is present, any previously configured monitoringSlotPeriodicityAndOffset-v1710 is released.

Indicates which slot(s) within a slot group are configured for multi-slot PDCCH monitoring. The first (leftmost, most significant) bit represents the first slot in the slot group, the second bit represents the second slot in the slot group, and so on. A bit set to '1' indicates that the corresponding slot is configured for multi-slot PDCCH monitoring (see clause 10 of TS 38.213). The number of slots for multi-slot PDCCH monitoring is configured according to clause 10 in TS 38.213.

The first symbol(s) for PDCCH monitoring in the slots configured for (multi-slot) PDCCH monitoring (see monitoringSlotPeriodicityAndOffset and duration). The most significant (left) bit represents the first OFDM in a slot, and the second most significant (left) bit represents the second OFDM symbol in a slot and so on. The bit(s) set to one identify the first OFDM symbol(s) of the control resource set within a slot. If the cyclic prefix of the BWP is set to extended CP, the last two bits within the bit string shall be ignored by the UE or IAB-MT. For DCI format 2_0, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol. See clause 10 of TS 38.213. For IAB-MT: For DCI format 2_0 or DCI format 2_5, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol. See clause 10 of TS 38.213.

The number of PDCCH candidates specifically for format 2-4 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see clause 10.1 of TS 38.213).

The number of PDCCH candidates specifically for format 2-7 for the configured aggregation level.

The number of PDCCH candidates specifically for format 2-0 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see clause 11.1.1 of TS 38.213). For a search space configured with freqMonitorLocations-r16, only value 'n1' is valid.

Number of PDCCH candidates per aggregation level. The number of candidates and aggregation levels configured here applies to all formats unless a particular value is specified or a format-specific value is provided (see inside searchSpaceType). If configured in the SearchSpace of a cross carrier scheduled cell, this field determines the number of candidates and aggregation levels to be used on the linked scheduling cell (see clause 10 of TS 38.213).

List of search space group IDs which the search space is associated with. The network configures at most 2 search space groups per BWP where the group ID is either 0 or 1 if searchSpaceGroupIdList-r16 is included. The network configures at most 3 search space groups per BWP where the group ID is either 0, 1 or 2 if searchSpaceGroupIdList-r17 is included. And if searchSpaceGroupIdList-r17 is included, searchSpaceGroupIdList-r16 is ignored.

Identity of the search space. SearchSpaceId = 0 identifies the searchSpaceZero configured via PBCH (MIB) or ServingCellConfigCommon and may hence not be used in the SearchSpace IE. The searchSpaceId is unique among the BWPs of a Serving Cell. In case of cross carrier scheduling, search spaces with the same searchSpaceId in scheduled cell and scheduling cell are linked to each other. The UE applies the search space for the scheduled cell only if the DL BWPs in which the linked search spaces are configured in scheduling cell and scheduled cell are both active. For an IAB-MT, the search space defines how/where to search for PDCCH candidates for an IAB-MT where each search space is associated with one ControlResearchSet and for a scheduled cell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent.

This parameter is used to link two search spaces of same type in the same BWP. If two search spaces have the same SearchSpaceLinkingId UE assumes these search spaces are linked to PDCCH repetition REF. When PDCCH repetition is monitored in two linked search space (SS) sets, the UE does not expect a third monitored SS set to be linked with any of the two linked SS sets. The two linked SS sets have the same SS set type (USS/CSS). The two linked SS sets have the same DCI formats to monitor. For intra-slot PDCCH repetition: The two SS sets should have the same periodicity and offset (monitoringSlotPeriodicityAndOffset), and the same duration. For linking monitoring occasions across the two SS sets that exist in the same slot: The two SS sets have the same number of monitoring occasions within a slot and n-th monitoring occasion of one SS set is linked to n-th monitoring occasion of the other SS set. The following SS sets cannot be linked with another SS set for PDCCH repetition: SS set 0, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, searchSpaceMCCH, searchSpaceMTCH, peiSearchSpace, and sdt-SearchSpace. SS set configured by recoverySearchSpaceId cannot be linked to another SS set for PDCCH repetition. When a scheduled serving cell is configured to be cross-carrier scheduled by a scheduling serving cell, two PDCCH candidates (with the same AL and candidate index associated with the scheduled serving cell) are linked only if the corresponding two SS sets in the scheduling serving cell are linked and two SS sets in the scheduled serving cell with the same SS set IDs are also linked. This parameter is not applicable to search space configured with dci-FormatsSL for monitoring format 3-0 or format 3-1 or for monitoring formats 3-0 and format 3-1.

Indicates whether this is a common search space (present) or a UE specific search space as well as DCI formats to monitor for.

Configures this search space as UE specific search space (USS). The UE monitors the DCI format with CRC scrambled by C-RNTI, CS-RNTI (if configured), and SP-CSI-RNTI (if configured)

Indicates the ciphering algorithm to be used for SRBs and DRBs, as specified in TS 33.501. The algorithms nea0-nea3 are identical to the LTE algorithms eea0-3. The algorithms configured for all bearers using master key shall be the same, and the algorithms configured for all bearers using secondary key, if any, shall be the same. If UE is connected to E-UTRA/EPC, this field indicates the ciphering algorithm to be used for RBs configured with NR PDCP, as specified in TS 33.501.

Indicates the integrity protection algorithm to be used for SRBs and DRBs, as specified in TS 33.501. The algorithms nia0-nia3 are identical to the E-UTRA algorithms eia0-3. The algorithms configured for all bearers using master key shall be the same and the algorithms configured for all bearers using secondary key, if any, shall be the same. The network does not configure nia0 except for unauthenticated emergency sessions for unauthenticated UEs in LSM (limited service mode). If UE is connected to E-UTRA/EPC, this field indicates the integrity protection algorithm to be used for SRBs configured with NR PDCP as specified in TS 33.501, and DRBs configured with integrity protection as specified in TS 33.401. The network does not configure nia0 for SRB3.

Indicates the periodicity of the semi-static channel access mode (see clause 4.3 of TS 37.213). Value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, value ms2dot5 corresponds to 2.5 ms, and so on.

Indicates the period of a channel occupancy that the UE can initiate as described in clause 4.3 of TS 37.213. Value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, value ms2dot5 corresponds to 2.5 ms, and so on.

Indicates the number of symbols from the beginning of the even indexed radio frame to the start of the first period within that radio frame that the UE can initiate a channel occupancy (see clause 4.3 of TS 37.213), based on the smallest SCS among the configured SCSs in the serving cell. The offset duration indicated by this field is less than the period duration indicated by periodUE. The maximum value is 139, 279 and 559 for 15, 30 and 60 kHz subcarrier spacing, respectively.

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.

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.

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 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.

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.

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.

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).

PDSCH related parameters that are not BWP-specific.

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 SFN 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 SFN 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.

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 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 belongs to.

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. The network does not configure the field in a serving cell that is configured with more than one value for the coresetPoolIndex.

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.

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.

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 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 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.

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 RedCap, Slicing, SDT 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 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 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, 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 resources for initialUplinkBWP-RedCap that the RedCap UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.

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

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.