DMRS-BundlingPUCCH-Config field descriptions |
---|
pucch-DMRS-Bundling
Indicates whether DMRS bundling and time domain window for PUCCH are jointly enabled.
|
pucch-FrequencyHoppingInterval
Configures the number of consecutive slots for the UE to perform inter-slot frequency hopping with inter-slot bundling for PUCCH. When both inter-frequency hopping and DMRS bundling are enabled for PUCCH repetitions, the UE is expected to be configured with at least one pucch-FrequencyHoppingInterval-r17 and pucch-TimeDomainWindowLength-r17. When DMRS bundling for PUCCH is enabled by pucch-DMRS-Bundling-r17, PUCCH frequency hopping interval is only determined by the configuration of PUCCH hopping interval if PUCCH hopping interval is configured. If the field is absent, the number of consecutive slots for the UE to perform inter-slot PUCCH frequency hopping is indicated by pucch-TimeDomainWindowLength-r17.
|
pucch-TimeDomainWindowLength
Configures the length of a nominal time domain window in slots for DMRS bundling for PUCCH. The value shall not exceed the maximum duration for DMRS bundling for PUCCH as specified in TS 38.306. If this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the time duration for the transmission of all PUCCH repetitions and the maximum duration for DMRS bundling for PUCCH as specified in TS 38.306.
|
pucch-WindowRestart
Indicates whether UE bundles PUCCH DMRS remaining in a nominal time domain window after event(s) triggered by DCI or MAC CE that violate power consistency and phase continuity requirements is enabled (see clause 6.1.7 of TS 38.214).
|
DMRS-BundlingPUSCH-Config field descriptions |
---|
pusch-DMRS-Bundling
Indicates whether DMRS bundling and time domain window for PUSCH are jointly enabled.
|
pusch-FrequencyHoppingInterval
Configures the number of consecutive slots for the UE to perform inter-slot frequency hopping with inter-slot bundling for PUSCH. When both inter-frequency hopping and DMRS bundling are enabled for PUSCH repetitions, the UE is expected to be configured with at least one pusch-FrequencyHoppingInterval-r17 and pusch-TimeDomainWindowLength-r17. This parameter is shared for both DG-PUSCH and CG-PUSCH. When DMRS bundling for PUSCH is enabled by pusch-DMRS-Bundling-r17, PUSCH frequency hopping interval is only determined by the configuration of PUSCH hopping interval if PUSCH hopping interval is configured. If the field is absent, the number of consecutive slots for the UE to perform inter-slot PUSCH frequency hopping is indicated by pusch-TimeDomainWindowLength-r17.
|
pusch-TimeDomainWindowLength
Configures the length of a nominal time domain window in number of consecutive slots for DMRS bundling for PUSCH. The value shall not exceed the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306. For PUSCH repetition type A/B, if this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the time duration for the transmission of all PUSCH repetitions and the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306. For TBoMS, if this field is absent, the UE shall apply the default value that is the minimum value in the unit of consecutive slots of the duration of TBoMS transmission (including repetition of TBoMS) and the maximum duration for DMRS bundling for PUSCH as specified in TS 38.306.
|
pusch-WindowRestart
Indicates whether UE bundles PUSCH DMRS remaining in a nominal time domain window after event(s) triggered by DCI or MAC CE that violate power consistency and phase continuity requirements is enabled (see clause 6.1.7 of TS 38.214).
|
DMRS-DownlinkConfig field descriptions |
---|
dmrs-AdditionalPosition
Position for additional DM-RS in DL, see Tables 7.4.1.1.2-3 and 7.4.1.1.2-4 in TS 38.211. If the field is absent, the UE applies the value pos2. See also clause 7.4.1.1.2 of TS 38.211 for additional constraints on how the network may set this field depending on the setting of other fields.
|
dmrs-Downlink
This field indicates whether low PAPR DMRS is used, as specified in clause 7.4.1.1.1 of TS 38.211.
|
dmrs-Type
Selection of the DMRS type to be used for DL (see clause 7.4.1.1.1 of TS 38.211). If the field is absent, the UE uses DMRS type 1.
|
maxLength
The maximum number of OFDM symbols for DL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1. If set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI. (see clause 7.4.1.1.2 of TS 38.211).
|
phaseTrackingRS
Configures downlink PTRS. If the field is not configured, the UE assumes that downlink PTRS are absent. See clause 5.1.6.3 of TS 38.214.
|
scramblingID0
DL DMRS scrambling initialization (see clause 7.4.1.1.1 of TS 38.211). When the field is absent the UE applies the value physCellId configured for this serving cell.
|
scramblingID1
DL DMRS scrambling initialization (see clause 7.4.1.1.1 of TS 38.211). When the field is absent the UE applies the value physCellId configured for this serving cell.
|
DMRS-UplinkConfig field descriptions |
---|
dmrs-AdditionalPosition
Position for additional DM-RS in UL (see clause 6.4.1.1.3 of TS 38.211). If the field is absent, the UE applies the value pos2. See also clause 6.4.1.1.3 of TS 38.211 for additional constraints on how the network may set this field depending on the setting of other fields.
|
dmrs-Type
Selection of the DMRS type to be used for UL (see clause 6.4.1.1.3 of TS 38.211) If the field is absent, the UE uses DMRS type 1.
|
dmrs-Uplink
This field indicates whether low PAPR DMRS is used, as specified in TS 38.211, clause 6.4.1.1.1.1.
|
dmrs-UplinkTransformPrecoding
This field indicates whether low PAPR DMRS is used for PUSCH with pi/2 BPSK modulation, as specified in TS 38.211, clause 6.4.1.1.1.2. The network configures this field only if tp-pi2BPSK is configured in PUSCH-Config.
|
maxLength
The maximum number of OFDM symbols for UL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1. If set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI. (see clause 6.4.1.1.3 of TS 38.211).
|
nPUSCH-Identity
Parameter: N_ID^(PUSCH) for DFT-s-OFDM DMRS. If the value is absent or released, the UE uses the value Physical cell ID (physCellId). See TS 38.211.
|
phaseTrackingRS
Configures uplink PTRS (see TS 38.211).
|
pi2BPSK-ScramblingID0, pi2BPSK-ScramblingID1
UL DMRS scrambling initialization for pi/2 BPSK DMRS for PUSCH (see clause 6.4.1.1.2 of TS 38.211). When the field is absent the UE applies the value Physical cell ID (physCellId) of the serving cell.
|
scramblingID0
UL DMRS scrambling initialization for CP-OFDM (see TS 38.211, clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID (physCellId).
|
scramblingID1
UL DMRS scrambling initialization for CP-OFDM. (see TS 38.211, clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID (physCellId).
|
sequenceGroupHopping
For DMRS transmission with transform precoder the NW may configure group hopping by the cell-specific parameter groupHoppingEnabledTransformPrecoding in PUSCH-ConfigCommon. In this case, the NW may include this UE specific field to disable group hopping for PUSCH transmission except for Msg3, i.e., to override the configuration in PUSCH-ConfigCommon (see TS 38.211). If the field is absent, the UE uses the same hopping mode as for Msg3.
|
sequenceHopping
Determines if sequence hopping is enabled for DMRS transmission with transform precoder for PUSCH transmission other than Msg3 (sequence hopping is always disabled for Msg3). If the field is absent, the UE uses the same hopping mode as for msg3. The network does not configure simultaneous group hopping and sequence hopping. See TS 38.211, clause 6.4.1.1.1.2.
|
transformPrecodingDisabled
DMRS related parameters for Cyclic Prefix OFDM.
|
transformPrecodingEnabled
DMRS related parameters for DFT-s-OFDM (Transform Precoding).
|
DownlinkConfigCommon field descriptions |
---|
frequencyInfoDL
Basic parameters of a downlink carrier and transmission thereon.
|
initialDownlinkBWP
The initial downlink BWP configuration for a serving cell. The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain.
|
initialDownlinkBWP-RedCap
If present, RedCap UEs use this DL BWP instead of initialDownlinkBWP.
If absent, RedCap UEs use initialDownlinkBWP provided that it does not exceed the RedCap UE maximum bandwidth (see also clause 5.2.2.4.2).
|
Conditional Presence | Explanation |
---|---|
InterFreqHOAndServCellAdd | This field is mandatory present for inter-frequency handover, and upon serving cell (PSCell/SCell) addition. Otherwise, the field is optionally present, Need M. |
ServCellAdd | This field is mandatory present upon serving cell addition (for PSCell and SCell) and upon handover from E-UTRA to NR. It is optionally present, Need M otherwise. |
DownlinkConfigCommonSIB field descriptions |
---|
bcch-Config
The modification period related configuration.
|
frequencyInfoDL-SIB
Basic parameters of a downlink carrier and transmission thereon.
|
initialDownlinkBWP
The initial downlink BWP configuration for a PCell. The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain. The UE applies the locationAndBandwidth upon reception of this field (e.g. to determine the frequency position of signals described in relation to this locationAndBandwidth) but it keeps CORESET#0 until after reception of RRCSetup/RRCResume/RRCReestablishment.
|
initialDownlinkBWP-RedCap
If present, RedCap UEs use this DL BWP instead of initialDownlinkBWP. If the locationAndBandwidth of this BWP contains the entire CORESET#0, the UE applies the locationAndBandwidth upon reception of this field (e.g. to determine the frequency position of signals described in relation to this locationAndBandwidth) but it keeps CORESET#0 until after reception of RRCSetup/RRCResume/RRCReestablishment. Otherwise, i.e., if the locationAndBandwidth of this BWP does not contain the entire CORESET#0, the UE uses this BWP for receiving DL messages during initial access (Msg2, MsgB, Msg4) and after initial access.
If absent, RedCap UEs use initialDownlinkBWP provided that it does not exceed the RedCap UE maximum bandwidth (see also clause 5.2.2.4.2).
|
lastUsedCellOnly
When present, the field indicates that the UE monitors PEI only if the latest received RRCRelease without noLastCellUpdate is from this cell. A PEI-capable UE stores its last used cell information.
|
nrofPDCCH-MonitoringOccasionPerSSB-InPO
The number of PDCCH monitoring occasions corresponding to an SSB within a Paging Occasion, see clause 7.1 of TS 38.304.
|
pcch-Config
The paging related configuration.
|
pei-Config
The PEI related configuration.
|
subgroupConfig
The paging subgroup related configuration.
|
BCCH-Config field descriptions |
---|
modificationPeriodCoeff
Actual modification period, expressed in number of radio frames m = modificationPeriodCoeff * defaultPagingCycle, see clause 5.2.2.2.2. n2 corresponds to value 2, n4 corresponds to value 4, and so on.
|
PCCH-Config field descriptions |
---|
defaultPagingCycle
Default paging cycle, used to derive 'T' in TS 38.304. Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on.
|
firstPDCCH-MonitoringOccasionOfPO
Points out the first PDCCH monitoring occasion for paging of each PO of the PF, see TS 38.304.
|
nAndPagingFrameOffset
Used to derive the number of total paging frames in T (corresponding to parameter N in TS 38.304) and paging frame offset (corresponding to parameter PF_offset in TS 38.304). A value of oneSixteenthT corresponds to T / 16, a value of oneEighthT corresponds to T / 8, and so on.
If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 2 or 3 (as specified in TS 38.213):
|
ns
Number of paging occasions per paging frame.
|
ranPagingInIdlePO
Indicates that the network supports to send RAN paging in PO that corresponds to the i_s as determined by UE in RRC_IDLE state, see TS38.304 [20].
|
PEI-Config field descriptions |
---|
payloadSizeDCI-2-7
Payload size of PEI DCI, i.e., DCI format 2_7. The size is no larger than the payload size of paging DCI which has maximum of 41 bits and 43 bits for licensed and unlicensed spectrums, respectively.
|
pei-FrameOffset
Offset, in number of frames from the start of a reference frame for PEI-O to the start of a first paging frame of the paging frames associated with the PEI-O, see clause 10.4A of TS 38.213.
|
po-NumPerPEI
The number of PO(s) associated with one PEI monitoring occasion. It is a factor of the total PO number in a paging cycle, i.e N x Ns, as specified in TS 38.304. The maximum number of PF associated with one PEI monitoring occasion is 2. The number of PO mapping to one PEI should be multiple of Ns when po-NumPerPEI is larger than Ns.
|
SubgroupConfig field descriptions |
---|
subgroupsNumPerPO
Total number of subgroups per Paging Occasion (PO) for UE to read subgroups indication from physical-layer signaling. The field represents the sum of CN-assigned and UEID-based subgroups supported by the network. When PEI-Config is configured, there is always at least one subgroup (UEID-based subgroup or CN-assigned subgroup) configured.
|
subgroupsNumForUEID
Number of subgroups per Paging Occasion (PO) for UE to read subgroups indication from physical-layer signaling, for UEID-based subgrouping method. When present, the field is set to an integer smaller than or equal to subgroupsNumPerPO. subgroupsNumPerPO equals to subgroupsNumForUEID when the network does not support CN-assigned subgrouping. The field is absent when the network only supports CN-assigned subgrouping. Both this field and subgroupsNumPerPO are equal to 1 when the network does not support subgrouping.
|
Conditional Presence | Explanation |
---|---|
SharedSpectrum2 | The field is optional present, Need R, if this cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
DownlinkPreemption field descriptions |
---|
dci-PayloadSize
Total length of the DCI payload scrambled with INT-RNTI (see clause 11.2 of TS 38.213).
|
int-ConfigurationPerServingCell
Indicates (per serving cell) the position of the 14 bit INT values inside the DCI payload (see clause 11.2 of TS 38.213).
|
int-RNTI
RNTI used for indication pre-emption in DL (see clause 10 of TS 38.213).
|
timeFrequencySet
Set selection for DL-preemption indication (see clause 11.2 of TS 38.213) The set determines how the UE interprets the DL preemption DCI payload.
|
INT-ConfigurationPerServingCell field descriptions |
---|
positionInDCI
Starting position (in number of bit) of the 14 bit INT value applicable for this serving cell (servingCellId) within the DCI payload (see clause 11.2 of TS 38.213). Must be multiples of 14 (bit).
|
DRX-Config field descriptions |
---|
drx-HARQ-RTT-TimerDL
Value in number of symbols of the BWP where the transport block was received. drx-HARQ-RTT-TimerDL-r17 is only applicable for SCS 480 kHz and 960 kHz. If configured, the UE shall ignore drx-HARQ-RTT-TimerDL (without suffix) for SCS 480 kHz and 960 kHz.
|
drx-HARQ-RTT-TimerUL
Value in number of symbols of the BWP where the transport block was transmitted. drx-HARQ-RTT-TimerUL-r17 is only applicable for SCS 480 kHz and 960 kHz. If configured, the UE shall ignore drx-HARQ-RTT-TimerUL (without suffix) for SCS 480 kHz and 960 kHz.
|
drx-InactivityTimer
Value in multiple integers of 1 ms. ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on.
|
drx-LongCycleStartOffset
drx-LongCycle in ms and drx-StartOffset in multiples of 1 ms. If drx-ShortCycle is configured, the value of drx-LongCycle shall be a multiple of the drx-ShortCycle value.
|
drx-onDurationTimer
Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on.
|
drx-RetransmissionTimerDL
Value in number of slot lengths of the BWP where the transport block was received. value sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on.
|
drx-RetransmissionTimerUL
Value in number of slot lengths of the BWP where the transport block was transmitted. sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on.
|
drx-ShortCycleTimer
Value in multiples of drx-ShortCycle. A value of 1 corresponds to drx-ShortCycle, a value of 2 corresponds to 2 * drx-ShortCycle and so on.
|
drx-ShortCycle
Value in ms. ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on.
|
drx-SlotOffset
Value in 1/32 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 1/32 ms, value 2 corresponds to 2/32 ms, and so on.
|
DRX-ConfigSecondaryGroup field descriptions |
---|
drx-InactivityTimer
Value in multiple integers of 1 ms. ms0 corresponds to 0 ms, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on, as specified in TS 38.321. The network configures a drx-InactivityTimer value for the second DRX group that is smaller than the drx-InactivityTimer configured for the default DRX group in IE DRX-Config.
|
drx-onDurationTimer
Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSeconds). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on, as specified in TS 38.321. The network configures a drx-onDurationTimer value for the second DRX group that is smaller than the drx-onDurationTimer configured for the default DRX group in IE DRX-Config.
|
DRX-ConfigSL field descriptions |
---|
drx-HARQ-RTT-TimerSL
Value in number of symbols of the BWP where the PDCCH was transmitted. Value 0 is used in case sl-PUCCH-Config is not configured and the corresponding resource pool is not configured with PSFCH.
|
drx-RetransmissionTimerSL
Value in number of slot lengths of the BWP where the PDCCH was transmitted. sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on.
|
EphemerisInfo field descriptions |
---|
eccentricity
Satellite orbital parameter: eccentricity e, see NIMA TR 8350.2 [71]. Unit is radian.
Step of 1.431 * 10-8. Actual value = field value * (1.431 * 10-8).
|
inclination
Satellite orbital parameter: inclination i, see NIMA TR 8350.2 [71]. Unit is radian.
Step of 2.341* 10-8 rad. Actual value = field value * (2.341* 10-8).
|
longitude
Satellite orbital parameter: longitude of ascending node Ω, see NIMA TR 8350.2 [71]. Unit is radian.
Step of 2.341* 10-8 rad. Actual value = field value * (2.341* 10-8).
|
meanAnomaly
Satellite orbital parameter: Mean anomaly M at epoch time, see NIMA TR 8350.2 [71]. Unit is radian.
Step of 2.341* 10-8 rad. Actual value = field value * (2.341* 10-8).
|
periapsis
Satellite orbital parameter: argument of periapsis ω, see NIMA TR 8350.2 [71]. Unit is radian.
Step of 2.341* 10-8 rad. Actual value = field value * (2.341* 10-8).
|
positionX, positionY, positionZ
X, Y, Z coordinate of satellite position state vector in ECEF. Unit is meter.
Step of 1.3 m. Actual value = field value * 1.3.
|
semiMajorAxis
Satellite orbital parameter: semi major axis α, see NIMA TR 8350.2 [71]. Unit is meter.
Step of 4.249 * 10-3 m. Actual value = 6500000 + field value * (4.249 * 10-3).
|
velocityVX, velocityVY, velocityVZ
X, Y, Z coordinate of satellite velocity state vector in ECEF. Unit is meter/second.
Step of 0.06 m/s. Actual value = field value * 0.06.
|
FeatureCombination field descriptions |
---|
redCap
If present, this field indicates that RedCap is part of this feature combination.
|
smallData
If present, this field indicates that Small Data is part of this feature combination.
|
nsag
If present, this field indicates NSAG(s) that are part of this feature combination.
|
msg3-Repetitions
If present, this field indicates that signalling of msg3 repetition is part of this feature combination. This field is not configured in a set of preambles that is configured with 2-step random-access type.
|
FeatureCombinationPreambles field descriptions |
---|
deltaPreamble
Power offset between msg3 or msgA-PUSCH and RACH preamble transmission. If configured, this parameter overrides msg3-DeltaPreamble or msgA-DeltaPreamble, Actual value = field value * 2 [dB] (see clause 7.1 of TS 38.213). If msgA-DeltaPreamble is configured in separateMsgA-PUSCH-Config-r17, this field is absent.
|
featureCombination
Indicates which combination of features that the preambles indicated by this IE are associated with. The UE ignores a RACH resource defined by this FeatureCombinationPreambles if any feature within the featureCombination is not supported by the UE or if any of the spare fields within the featureCombination is set to true.
|
messagePowerOffsetGroupB
Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to -infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on (see clause 5.1.2 of TS 38.321).
|
msgA-RSRP-Threshold
The UE selects 2-step random access type to perform random access based on this threshold (see clause 5.1.1 of TS 38.321). This field is only present if both 2-step and 4-step RA type are configured for the concerned feature combination in the BWP. If configured, this parameter overrides msgA-RSRP-Threshold-r16. If absent, the UE applies msgA-RSRP-Threshold-r16, if configured
|
numberOfPreamblesPerSSB-ForThisPartition
It determines how many consecutive preambles are associated to the Feature Combination starting from the starting preamble(s) per SSB.
|
numberOfRA-PreamblesGroupA
It determines how many consecutive preambles per SSB are associated to Group A starting from the starting preamble(s). The remaining preambles associated to the Feature Combination are associated to Group B
|
ra-SizeGroupA
Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see clause 5.1.2 of TS 38.321). If this feature combination preambles are associated to a RACH-ConfigCommon-twostepRA, this field correspond to ra-MsgA-SizeGroupA, otherwise it corresponds to ra-Msg3SizeGroupA.
|
rsrp-ThresholdSSB
L1-RSRP threshold used for determining whether a candidate beam may be used by the UE. If this parameter is included in FeatureCombinationPreambles which is included in RACH-ConfigCommonTwoStepRA, it corresponds to msgA-RSRP-ThresholdSSB, as defined in TS 38.321. If this parameter is included in FeatureCombinationPreambles which is included in RACH-ConfigCommon, it it corresponds to rsrp-ThresholdSSB, as defined in TS 38.321.
|
separateMsgA-PUSCH-Config
If present it specifies how the 2-step RACH preambles identified by this FeatureCombinationPreambles are mapped to a PUSCH slot separate from the one defined in MsgA-ConfigCommon-r16. If the field is absent, the UE should apply the corresponding parameter in the RACH-ConfigCommonTwoStepRA of the BWP which includes the FeatureCombinationPreambles IE.
|
ssb-SharedRO-MaskIndex
Mask index (see TS 38.321).
Indicates a subset of ROs where preambles are allocated for this feature combination.
If this field is configured within FeatureCombinationPreambles which is included in RACH-ConfigCommonTwoStepRA:
|
startPreambleForThisPartition
It defines the first preamble associated with the Feature Combination. If the UE is provided with a number N of SSB block indexes associated with one PRACH occasion, and N<1, the first preamble in each PRACH occasion is the one having the same index as indicated by this field. If N≥1, N blocks of preambles associated with the Feature Combination are defined, each having start index + startPreambleForThisPartition, where n refers to SSB block index (see clause 8.1 of TS 38.213).
|
Conditional Presence | Explanation |
---|---|
MsgAConfigCommon | The field is optionally present, Need S, if FeatureCombinationPreambles is included in RACH-ConfigCommonTwoStepRA. Otherwise, it is absent. If the field is absent in FeatureCombinationPreambles included in RACH-ConfigCommonTwoStepRA, the UE applies MsgA-PUSCH-Config included in the corresponding MsgA-ConfigCommon. |
FreqPriorityDedicatedSlicing field descriptions |
---|
dl-ExplicitCarrierFreq
Indicates the downlink carrier frequency to which SliceInfoListDedicated is associated.
|
Conditional Presence | Explanation |
---|---|
Mandatory | The field is mandatory present. |
FreqPriorityListSlicing field descriptions |
---|
dl-ImplicitCarrierFreq
Indicates the downlink carrier frequency to which sliceInfoList is associated with. The frequency is signalled implicitly, value 0 corresponds to the serving frequency, value 1 corresponds to the first frequency indicated by the InterFreqCarrierFreqList in SIB4, and value 2 corresponds to the second frequency indicated by the InterFreqCarrierFreqList in SIB4, and so on.
|
SliceInfo field descriptions |
---|
sliceAllowedCellListNR
List of allow-listed cells for slicing. If present, the cells listed in this list support the corresponding nsag-frequency pair, and the cells not listed in this list do not support the corresponding nsag-frequency pair, according to clause 5.2.4.11 of TS 38.304.
|
sliceCellListNR
Contains either the list of allow-listed or exclude-listed cells for slicing. If absent, it implies all the cells support the corresponding nsag-frequency pair, according to clause 5.2.4.11 of TS 38.304.
|
sliceExcludedCellListNR
List of exclude-listed cells for slicing. If present, the cells listed in this list do not support the corresponding nsag-frequency pair, and the cells not listed in this list support the corresponding nsag-frequency pair, according to clause 5.2.4.11 of TS 38.304.
|
Conditional Presence | Explanation |
---|---|
Mandatory | The field is mandatory present. |
FrequencyInfoDL field descriptions |
---|
absoluteFrequencyPointA
Absolute frequency position of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A (see clause 4.4.4.2 of TS 38.211). Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList.
|
absoluteFrequencySSB
Frequency of the SSB to be used for this serving cell. SSB related parameters (e.g. SSB index) provided for a serving cell refer to this SSB frequency unless mentioned otherwise. The CD-SSB of the PCell is always on the sync raster. Frequencies are considered to be on the sync raster if they are also identifiable with a GSCN value (see TS 38.101-1). If the field is absent, the SSB related parameters should be absent, e.g. ssb-PositionsInBurst, ssb-periodicityServingCell and subcarrierSpacing in ServingCellConfigCommon IE. If the field is absent, the UE obtains timing reference from the SpCell or an SCell if applicable as described in clause 4.1 of TS 38.213. This is only supported in case the SCell for which the UE obtains the timing reference is in the same frequency band as the cell (i.e. the SpCell or the SCell, respectively) from which the UE obtains the timing reference.
For cells supporting RedCap, this field corresponds to the CD-SSB.
|
frequencyBandList
List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported.
|
scs-SpecificCarrierList
A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see clause 5.3 of TS 38.211).
|
Conditional Presence | Explanation |
---|---|
SpCellAdd | The field is mandatory present if this FrequencyInfoDL is for SpCell. Otherwise the field is optionally present, Need S. |
FrequencyInfoDL-SIB field descriptions |
---|
offsetToPointA
Represents the offset to Point A as defined in clause 4.4.4.2 of TS 38.211.
|
frequencyBandList
List of one or multiple frequency bands to which this carrier(s) belongs.
|
scs-SpecificCarrierList
A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see clause 5.3 of TS 38.211). The network configures this for all SCSs that are used in DL BWPs in this serving cell.
|
FrequencyInfoUL field descriptions |
---|
absoluteFrequencyPointA
Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see clause 4.4.4.2 of TS 38.211).
|
additionalSpectrumEmission
The additional spectrum emission requirements to be applied by the UE on this uplink. If the field is absent, the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1, tables 6.2.3.1-1A, 6.2A.3.1.1-2 and 6.2A.3.1.2-2, and TS 38.101-2, tables 6.2.3.1-2 and 6.2A.3.1-2). Network configures the same value in additionalSpectrumEmission for all uplink carrier(s) of the same band with UL configured, except for additionalSpectrumEmission value corresponding to NS_55/NS_57. If NS_55/NS_57 (see TS 38.101-1, table 6.2.3.1-1) is applicable for at least one uplink carrier, the network may configure either NS_55/NS_57 or NS_01 for these uplink carriers, and NS_01 for the remaining uplink carrier(s) of band n77. The additionalSpectrumEmission is applicable for all uplink carriers of the same band with UL configured.
|
frequencyBandList
List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported.
|
frequencyShift7p5khz
Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.
|
p-Max
Maximum transmit power allowed in this serving cell. The maximum transmit power that the UE may use on this serving cell may be additionally limited by p-NR-FR1 (configured for the cell group) and by p-UE-FR1 (configured total for all serving cells operating on FR1). If absent, the UE applies the maximum power according to TS 38.101-1 in case of an FR1 cell or TS 38.101-2 in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2. Value in dBm. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174.
|
scs-SpecificCarrierList
A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see clause 5.3 of TS 38.211).
|
Conditional Presence | Explanation |
---|---|
FDD-OrSUL | The field is mandatory present if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL) or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise (if this FrequencyInfoUL is for an unpaired UL (TDD). |
FDD-TDD-OrSUL-Optional | The field is optionally present, Need R, if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL), or if this FrequencyInfoUL is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in clause 5.4.2.1 of TS 38.104), or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise. |
FrequencyInfoUL-SIB field descriptions |
---|
absoluteFrequencyPointA
Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see clause 4.4.4.2 of TS 38.211).
|
frequencyBandList
Provides the frequency band indicator and a list of additionalPmax and additionalSpectrumEmission values as defined in TS 38.101-1, table 6.2.3.1-1, and TS 38.101-2, table 6.2.3.1-2. The UE shall apply the first listed band which it supports in the frequencyBandList field.
|
frequencyShift7p5khz
Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.
|
p-Max
Value in dBm applicable for the cell. If absent the UE applies the maximum power according to TS 38.101-1 in case of an FR1 cell or TS 38.101-2 in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174.
|
scs-SpecificCarrierList
A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see clause 5.3 of TS 38.211). The network configures this for all SCSs that are used in UL BWPs configured in this serving cell.
|
Conditional Presence | Explanation |
---|---|
FDD-OrSUL | The field is mandatory present if this FrequencyInfoUL-SIB is for the paired UL for a DL (defined in a FrequencyInfoDL-SIB) or if this FrequencyInfoUL-SIB is for a supplementary uplink (SUL). It is absent otherwise (if this FrequencyInfoUL-SIB is for an unpaired UL (TDD). |
FDD-TDD-OrSUL-Optional | The field is optionally present, Need R, if this FrequencyInfoUL-SIB is for the paired UL for a DL (defined in a FrequencyInfoDL-SIB), or if this FrequencyInfoUL-SIB is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in clause 5.4.2.1 of TS 38.104), or if this FrequencyInfoUL-SIB is for a supplementary uplink (SUL). It is absent otherwise. |