Content for  TS 38.331  Word version:  18.0.0

If configured, indicates that the RLC entity is used for PTM reception. When the field is absent the RLC entity is used for PTP transmission/reception.

ID used commonly for the MAC logical channel and for the RLC bearer. Value 4 is not configured for DRBs if SRB4 is configured.

Extended logical channel ID used commonly for the MAC logical channel and for the RLC bearer for PTM reception. If this field is configured, the UE shall ignore logicalChannelIdentity.

Indicates that RLC should be re-established. Network sets this to true at least whenever the security key used for the radio bearer associated with this RLC entity changes. For SRB2, multicast MRBs and DRBs, unless full configuration is used, it is also set to true during the resumption of the RRC connection or the first reconfiguration after reestablishment. For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment, the network does not set this field to true. The network does not include this field if the RLC-BearerConfig IE is part of an RRCReconfiguration message within the LTM-Config IE.

Determines the RLC mode (UM, AM) and provides corresponding parameters. RLC mode reconfiguration can only be performed by DRB/multicast MRB release/addition or full configuration. The network may configure rlc-Config-v1610 only when rlc-Config (without suffix) is set to am.

Associates the RLC Bearer with a multicast MRB. The UE shall deliver DL RLC SDUs received via the RLC entity of this RLC bearer to the PDCP entity of the servedMBS-RadioBearer.

Associates the RLC Bearer with an SRB or a DRB. The UE shall deliver DL RLC SDUs received via the RLC entity of this RLC bearer to the PDCP entity of the servedRadioBearer. Furthermore, the UE shall advertise and deliver uplink PDCP PDUs of the uplink PDCP entity of the servedRadioBearer to the uplink RLC entity of this RLC bearer unless the uplink scheduling restrictions (moreThanOneRLC in PDCP-Config and the restrictions in LogicalChannelConfig) forbid it to do so.

Parameter for RLC AM in TS 38.322. Value t1 corresponds to 1 retransmission, value t2 corresponds to 2 retransmissions and so on.

Parameter for RLC AM in TS 38.322. Value kB25 corresponds to 25 kBytes, value kB50 corresponds to 50 kBytes and so on. infinity corresponds to an infinite amount of kBytes.

Parameter for RLC AM in TS 38.322. Value p4 corresponds to 4 PDUs, value p8 corresponds to 8 PDUs and so on. infinity corresponds to an infinite number of PDUs.

Indicates the RLC SN field size, see TS 38.322, in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLength of an RLC entity for the DRB/multicast MRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB.

Timer for RLC AM in TS 38.322, in milliseconds. Value ms5 means 5 ms, value ms10 means 10 ms and so on.

Timer for reassembly in TS 38.322, in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-ReassemblyExt-r17 is configured, the UE shall ignore t-Reassembly (without suffix).

Timer for status reporting in TS 38.322, in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-StatusProhibit-v1610 is present, the UE shall ignore t-StatusProhibit (without suffix).

Constants are described in clause 7.3. Value n1 corresponds to 1, value n2 corresponds to 2 and so on.

Timers are described in clause 7.1. Value ms0 corresponds to 0 ms, value ms50 corresponds to 50 ms and so on.

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 or dl-OrJointTCI-StateList 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. UE indicates support of the following SR periodicities in additionalSR-Periodicities (see clause 4.2.6 of TS 38.306): SCS = 30 kHz: 5sl SCS = 120 kHz: 5sl, 10sl

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, UE monitors the DCI format 2_9 according to clause 10.1, 11.5 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.

Indicate whether the UE monitors in this USS for DCI format 0_3 or for format 1_3 or for formats 0_3 and 1_3. Separate search space sets for DCI format 0_3/1_3 and legacy DCI formats are independently configured. If this field is present, the field dci-Formats is ignored.

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

Indicates whether the NCR-MT monitors the DCI formats 2-8 according to clause 20 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.