6.7.3 NB-IoT information elements

36.3313GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Protocol specificationRadio Resource Control (RRC)Release 15TS

6.7.3.1 NB-IoT System information blocks

SystemInformationBlockType2-NB

The IE SystemInformationBlockType2-NB contains radio resource configuration information that is common for all UEs.

NOTE: UE timers and constants related to functionality for which parameters are provided in another SIB are included in the corresponding SIB.

SystemInformationBlockType2-NB information element

— ASN1START

SystemInformationBlockType2-NB-r13 ::= SEQUENCE {

radioResourceConfigCommon-r13 RadioResourceConfigCommonSIB-NB-r13,

ue-TimersAndConstants-r13 UE-TimersAndConstants-NB-r13,

freqInfo-r13 SEQUENCE {

ul-CarrierFreq-r13 CarrierFreq-NB-r13 OPTIONAL, — Need OP

additionalSpectrumEmission-r13 AdditionalSpectrumEmission

},

timeAlignmentTimerCommon-r13 TimeAlignmentTimer,

multiBandInfoList-r13 SEQUENCE (SIZE (1..maxMultiBands)) OF AdditionalSpectrumEmission OPTIONAL, — Need OR

lateNonCriticalExtension OCTET STRING OPTIONAL,

…,

[[ cp-Reestablishment-r14 ENUMERATED {true} OPTIONAL — Need OP

]],

[[ servingCellMeasInfo-r14 ENUMERATED {true} OPTIONAL, — Need OR

cqi-Reporting-r14 ENUMERATED {true} OPTIONAL — Need OR

]],

[[ enhancedPHR-r15 ENUMERATED {true} OPTIONAL, — Need OR

freqInfo-v1530 SEQUENCE {

tdd-UL-DL-AlignmentOffset-r15 TDD-UL-DL-AlignmentOffset-NB-r15

} OPTIONAL, — Cond TDD

cp-EDT-r15 ENUMERATED {true} OPTIONAL, — Need OR

up-EDT-r15 ENUMERATED {true} OPTIONAL — Need OR

]]

}

— ASN1STOP

SystemInformationBlockType2-NB field descriptions

additionalSpectrumEmission

The UE requirements related to IE AdditionalSpectrumEmission are defined in TS 36.101 [42], clause 6.2.4F.

cp-EDT

For FDD: This field indicates whether the UE is allowed to initiate CP-EDT, see 5.3.3.1b.

cp-Reestablishment

This field indicates if the NB-IoT UE is allowed to trigger RRC connection re-establishment when AS security has not been activated.

cqi-Reporting

For FDD: This field indicates if downlink channel quality reporting in RRCConnectionReestablishmentRequest-NB, RRCConnectionRequest-NB and RRCConnectionResumeRequest-NB message is allowed.

enhancedPHR

For FDD: This field indicates if the NB-IoT UE is allowed to report enhanced PHR in MSG3 as specified in TS 36.321 [6].

multiBandInfoList

A list of additionalSpectrumEmission i.e. one for each additional frequency band included in multiBandInfoList in SystemInformationBlockType1-NB, listed in the same order.

servingCellMeasInfo

This field indicates if serving cell idle mode measurement reporting in RRCConnectionReestablishmentComplete-NB, RRCConnectionResumeComplete-NB and RRCConnectionSetupComplete-NB is allowed.

tdd-UL-DL-AlignmentOffset

Indicates the offset between the UL carrier frequency center with respect to DL carrier frequency center for the anchor carrier.

ul-CarrierFreq

For FDD: Uplink carrier frequency as defined in TS 36.101 [42], clause 5.7.3F. If operationModeInfo in the MIB-NB is set to standalone and the field is absent, the value of the carrier frequency is determined by the TX-RX frequency separation defined in TS 36.101 [42], table 5.7.4-1, and the value of the carrier frequency offset is 0. If operationModeInfo in the MIB-NB is not set to standalone, the field is mandatory present.

For TDD: This field is absent and the uplink carrier frequency is same as the downlink frequency.

up-EDT

For FDD: This field indicates whether the UE is allowed to initiate UP-EDT, see 5.3.3.1b.

Conditional presence

Explanation

TDD

The field is mandatory present for TDD; otherwise the field is not present and the UE shall delete any existing value for this field.

SystemInformationBlockType3-NB

The IE SystemInformationBlockType3-NB contains cell re-selection information common for intra-frequency, and inter-frequency cell re-selection as well as intra-frequency cell re-selection information other than neighbouring cell related.

SystemInformationBlockType3-NB information element

— ASN1START

SystemInformationBlockType3-NB-r13 ::= SEQUENCE {

cellReselectionInfoCommon-r13 SEQUENCE {

q-Hyst-r13 ENUMERATED {

dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10,

dB12, dB14, dB16, dB18, dB20, dB22, dB24

}

},

cellReselectionServingFreqInfo-r13 SEQUENCE {

s-NonIntraSearch-r13 ReselectionThreshold

},

intraFreqCellReselectionInfo-r13 SEQUENCE {

q-RxLevMin-r13 Q-RxLevMin,

q-QualMin-r13 Q-QualMin-r9 OPTIONAL, — Need OP

p-Max-r13 P-Max OPTIONAL, — Need OP

s-IntraSearchP-r13 ReselectionThreshold,

t-Reselection-r13 T-Reselection-NB-r13

},

freqBandInfo-r13 NS-PmaxList-NB-r13 OPTIONAL, — Need OR

multiBandInfoList-r13 SEQUENCE (SIZE (1..maxMultiBands)) OF

NS-PmaxList-NB-r13 OPTIONAL, — Need OR

lateNonCriticalExtension OCTET STRING OPTIONAL,

…,

[[ intraFreqCellReselectionInfo-v1350 IntraFreqCellReselectionInfo-NB-v1350 OPTIONAL — Cond Qrxlevmin

]],

[[ intraFreqCellReselectionInfo-v1360 IntraFreqCellReselectionInfo-NB-v1360 OPTIONAL — Need OR

]],

[[ intraFreqCellReselectionInfo-v1430 IntraFreqCellReselectionInfo-NB-v1430 OPTIONAL — Need OR

]],

[[ cellReselectionInfoCommon-v1450 CellReselectionInfoCommon-NB-v1450 OPTIONAL — Need OR

]],

[[ nsss-RRM-Config-r15 NSSS-RRM-Config-NB-r15 OPTIONAL, — Need OR

npbch-RRM-Config-r15 ENUMERATED {enabled} OPTIONAL — Need OR

]]

}

IntraFreqCellReselectionInfo-NB-v1350 ::= SEQUENCE {

delta-RxLevMin-v1350 INTEGER (-8..-1)

}

IntraFreqCellReselectionInfo-NB-v1360 ::= SEQUENCE {

s-IntraSearchP-v1360 ReselectionThreshold-NB-v1360

}

IntraFreqCellReselectionInfo-NB-v1430 ::= SEQUENCE {

powerClass14dBm-Offset-r14 ENUMERATED {dB-6, dB-3, dB3, dB6, dB9, dB12} OPTIONAL, — Need OP

ce-AuthorisationOffset-r14 ENUMERATED {dB5, dB10, dB15, dB20, dB25, dB30, dB35} OPTIONAL — Need OP

}

CellReselectionInfoCommon-NB-v1450 ::= SEQUENCE {

s-SearchDeltaP-r14 ENUMERATED {dB6, dB9, dB12, dB15}

}

— ASN1STOP

SystemInformationBlockType3-NB field descriptions

ce-AuthorisationOffset

Parameter "Qoffsetauthorization" in TS 36.304 [4]. Value in dB. Value dB5 corresponds to 5 dB, dB10 corresponds to 10 dB and so on.

If the field is absent, the UE applies the value of ce-authorisationOffset in SystemInformationBlockType1-NB.

multiBandInfoList

A list of additionalPmax and additionalSpectrumEmission values as defined in TS 36.101 [42], clause 6.2.4F, applicable for the intra-frequency neighbouring NB-IoT cells if the UE selects the frequency band from freqBandIndicator in SystemInformationBlockType1-NB.

npbch-RRM-Config

For FDD: Configuration for NPBCH-based RRM measurements. See TS 36.214 [24].

If enabled, NPBCH can be used in addition to NRS for RRM measurements for serving cell.

nsss-RRM-Config

For FDD: Configuration for NSSS-based RRM measurements for the serving cell.

powerClass14dBm-Offset

Parameter "Poffset" in TS 36.304 [4], only applicable for UE supporting powerClassNB-14dBm. Value in dB. Value dB-6 corresponds to -6 dB, dB-3 corresponds to -3 dB and so on. If the field is absent, the UE applies the (default) value of 0 dB for "Poffset" in TS 36.304 [4].

p-Max

Value applicable for the intra-frequency neighbouring E-UTRA cells. If absent the UE applies the maximum power according to the UE capability.

q-Hyst

Parameter Qhyst in TS 36.304 [4], Value in dB. Value dB1 corresponds to 1 dB, dB2 corresponds to 2 dB and so on.

q-QualMin

Parameter "Qqualmin" in TS 36.304 [4], applicable for intra-frequency neighbour cells. If the field is not present, the UE applies the (default) value of negative infinity for Qqualmin.

q-RxLevMin, delta-RxLevMin

Parameter "Qrxlevmin" in TS 36.304 [4], applicable for intra-frequency neighbour cells. If delta-RxLevMin is not included, actual value Qrxlevmin = q-RxLevMin * 2 [dBm]. If delta-RxLevMin is included, actual value Qrxlevmin = (q-RxLevMin + delta-RxLevMin) * 2 [dBm].

s-IntraSearchP

Parameter "SIntraSearchP" in TS 36.304 [4].

In case s-IntraSearchP-v1360 is included, the UE shall ignore s-IntraSearchP (i.e. without suffix).

s-NonIntraSearch

Parameter "SnonIntraSearchP" in TS 36.304 [4].

s-SearchDeltaP

Parameter "SSearchDeltaP" in TS 36.304 [4]. This parameter is only applicable for UEs supporting relaxed monitoring as specified in TS 36.306 [5]. Value dB6 corresponds to 6 dB, dB9 corresponds to 9 dB and so on.

t-Reselection

Parameter "TreselectionNB-IoT_Intra" in TS 36.304 [4].

Conditional presence

Explanation

Qrxlevmin

This field is optionally present, Need OR, if q-RxLevMin is set to the minimum value. Otherwise the field is not present.

SystemInformationBlockType4-NB

The IE SystemInformationBlockType4-NB contains neighbouring cell related information relevant only for intra-frequency cell re-selection. The IE includes cells with specific re-selection parameters.

SystemInformationBlockType4-NB information element

— ASN1START

SystemInformationBlockType4-NB-r13 ::= SEQUENCE {

intraFreqNeighCellList-r13 IntraFreqNeighCellList OPTIONAL, — Need OR

intraFreqBlackCellList-r13 IntraFreqBlackCellList OPTIONAL, — Need OR

lateNonCriticalExtension OCTET STRING OPTIONAL,

…,

[[ nsss-RRM-Config-r15 NSSS-RRM-Config-NB-r15 OPTIONAL, — Need OR

intraFreqNeighCellList-v1530 IntraFreqNeighCellList-NB-v1530 OPTIONAL — Need OR

]]

}

IntraFreqNeighCellList-NB-v1530 ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo-NB-v1530

IntraFreqNeighCellInfo-NB-v1530 ::= SEQUENCE {

nsss-RRM-Config-r15 NSSS-RRM-Config-NB-r15 OPTIONAL — Cond NSSS-RRM

}

— ASN1STOP

SystemInformationBlockType4-NB field descriptions

intraFreqBlackCellList

List of blacklisted intra-frequency neighbouring cells.

intraFreqNeighCellList

List of intra-frequency neighbouring cells with specific cell re-selection parameters.

nsss-RRM-Config

For FDD: Configuration for NSSS-based RRM measurements.

If intraFreqNeighCellList-NB-v1530 is present then for a cell which is included in intraFreqNeighCellList, the UE applies the nsss-RRM-Config configured in the corresponding entry of IntraFreqNeighCellList-NB-v1530. Otherwise, the UE applies the nsss-RRM-Config configured in SystemInformationBlockType4-NB-r13.

Conditional presence

Explanation

NSSS-RRM

This field is optionally present, Need OR, when nsss-RRM-Config is present in SystemInformationBlockType4-NB. Otherwise, the field is not present, and the UE shall delete any existing value for this field.

SystemInformationBlockType5-NB

The IE SystemInformationBlockType5-NB contains information relevant only for inter-frequency cell re-selection i.e. information about other NB-IoT frequencies and inter-frequency neighbouring cells relevant for cell re-selection. The IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters.

SystemInformationBlockType5-NB information element

— ASN1START

SystemInformationBlockType5-NB-r13 ::= SEQUENCE {

interFreqCarrierFreqList-r13 InterFreqCarrierFreqList-NB-r13,

t-Reselection-r13 T-Reselection-NB-r13,

lateNonCriticalExtension OCTET STRING OPTIONAL,

…,

[[ scptm-FreqOffset-r14 INTEGER (1..8) OPTIONAL — Need OP

]]

}

InterFreqCarrierFreqList-NB-r13 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-NB-r13

InterFreqCarrierFreqInfo-NB-r13 ::= SEQUENCE {

dl-CarrierFreq-r13 CarrierFreq-NB-r13,

q-RxLevMin-r13 Q-RxLevMin,

q-QualMin-r13 Q-QualMin-r9 OPTIONAL, — Need OP

p-Max-r13 P-Max OPTIONAL, — Need OP

q-OffsetFreq-r13 Q-OffsetRange DEFAULT dB0,

interFreqNeighCellList-r13 InterFreqNeighCellList-NB-r13 OPTIONAL, — Need OR

interFreqBlackCellList-r13 InterFreqBlackCellList-NB-r13 OPTIONAL, — Need OR

multiBandInfoList-r13 MultiBandInfoList-NB-r13 OPTIONAL, — Need OR

…,

[[ delta-RxLevMin-v1350 INTEGER (-8..-1) OPTIONAL — Cond Qrxlevmin

]],

[[ powerClass14dBm-Offset-r14 ENUMERATED {dB-6, dB-3, dB3, dB6, dB9, dB12}

OPTIONAL, — Need OP

ce-AuthorisationOffset-r14 ENUMERATED {dB5, dB10, dB15, dB20, dB25, dB30, dB35} OPTIONAL — Need OP

]],

[[ nsss-RRM-Config-r15 NSSS-RRM-Config-NB-r15 OPTIONAL, — Need OR

interFreqNeighCellList-v1530 InterFreqNeighCellList-NB-v1530 OPTIONAL — Need OR

]],

[[ dl-CarrierFreq-v1550 CarrierFreq-NB-v1550 OPTIONAL — Cond TDD

]]

}

InterFreqNeighCellList-NB-r13 ::= SEQUENCE (SIZE (1..maxCellInter)) OF PhysCellId

InterFreqNeighCellList-NB-v1530 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-NB-v1530

InterFreqNeighCellInfo-NB-v1530 ::= SEQUENCE {

nsss-RRM-Config-r15 NSSS-RRM-Config-NB-r15 OPTIONAL — Cond NSSS-RRM

}

InterFreqBlackCellList-NB-r13 ::= SEQUENCE (SIZE (1..maxCellBlack)) OF PhysCellId

— ASN1STOP

SystemInformationBlockType5-NB field descriptions

ce-AuthorisationOffset

Parameter "Qoffsetauthorization" in TS 36.304 [4]. Value in dB. Value dB5 corresponds to 5 dB, dB10 corresponds to 10 dB and so on. If the field is absent, the UE applies the value of ce-authorisationOffset in SystemInformationBlockType1-NB.

interFreqBlackCellList

List of blacklisted inter-frequency neighbouring cells.

interFreqCarrierFreqList

List of neighbouring inter-frequencies. E-UTRAN does not configure more than one entry for the same physical frequency regardless of the E-ARFCN used to indicate this.

interFreqNeighCellList

List of inter-frequency neighbouring cells. E-UTRAN may include interFreqNeighCellList when including InterFreqNeighCellList-NB-v1530 to provide cell specific NSSS-based measurement configuration. The UE that does not support NSSS-based RRM measurements shall ignore this field in this version of the specification.

multiBandInfoList

Indicates the list of frequency bands, with the associated additionalPmax and additionalSpectrumEmission values as defined in TS 36.101 [42], clause 6.2.4, in addition to the band represented by dl-CarrierFreq for which cell reselection parameters are common.

nsss-RRM-Config

For FDD: Configuration for NSSS-based RRM measurements.

If InterFreqNeighCellList-NB-v1530 is present then for a cell which is included in interFreqNeighCellList, the UE applies the nsss-RRM-Config configured in the corresponding entry of InterFreqNeighCellList-NB-v1530. Otherwise, the UE applies the nsss-RRM-Config configured in InterFreqCarrierFreqInfo.

p-Max

Value applicable for the neighbouring NB-IoT cells on this carrier frequency. If absent the UE applies the maximum power according to the UE capability.

powerClass14dBm-Offset

Parameter "Poffset" in TS 36.304 [4], only applicable for UE supporting powerClassNB-14dBm. Value in dB. Value dB-6 corresponds to -6 dB, dB-3 corresponds to -3 dB and so on. If the field is absent, the UE applies the (default) value of 0 dB for "Poffset" in TS 36.304 [4]

q-OffsetFreq

Parameter "Qoffsetfrequency" in TS 36.304 [4].

q-QualMin

Parameter "Qqualmin" in TS 36.304 [4]. If the field is not present, the UE applies the (default) value of negative infinity for Qqualmin.

q-RxlevMin, delta-RxLevMin

Parameter "QRxLevmin" in TS 36.304 [4]. If delta-RxLevMin is not included, actual value Qrxlevmin = q-RxLevMin * 2 [dBm]. If delta-RxLevMin is included, actual value Qrxlevmin = (q-RxLevMin + delta-RxLevMin) * 2 [dBm].

scptm-FreqOffset

Parameter QoffsetSCPTM in TS 36.304 [4]. Actual value QoffsetSCPTM = field value * 2 [dB].

If the field is absent, the UE uses infinite dBs for the SC-PTM frequency offset with cell ranking as specified in TS 36.304 [4].

t-Reselection

Parameter "TreselectionNB-IoT_Inter" in TS 36.304 [4].

Conditional presence

Explanation

NSSS-RRM

This field is optionally present, Need OR, when nsss-RRM-Config is present in InterFreqCarrierFreqInfo. Otherwise, the field is not present, and the UE shall delete any existing value for this field.

Qrxlevmin

This field is optionally present, Need OR, if q-RxLevMin is set to the minimum value. Otherwise the field is not present.

TDD

The field is optionally present, Need OR, in TDD. Otherwise, the field is not present.

SystemInformationBlockType14-NB

The IE SystemInformationBlockType14-NB contains the AB parameters.

SystemInformationBlockType14-NB information element

— ASN1START

SystemInformationBlockType14-NB-r13 ::= SEQUENCE {

ab-Param-r13 CHOICE {

ab-Common-r13 AB-Config-NB-r13,

ab-PerPLMN-List-r13 SEQUENCE (SIZE (1..maxPLMN-r11)) OF AB-ConfigPLMN-NB-r13

} OPTIONAL, — Need OR

lateNonCriticalExtension OCTET STRING OPTIONAL,

…,

[[ ab-PerNRSRP-r15 ENUMERATED {thresh1, thresh2} OPTIONAL — Need OR

]]

}

AB-ConfigPLMN-NB-r13 ::= SEQUENCE {

ab-Config-r13 AB-Config-NB-r13 OPTIONAL — Need OR

}

AB-Config-NB-r13 ::= SEQUENCE {

ab-Category-r13 ENUMERATED {a, b, c},

ab-BarringBitmap-r13 BIT STRING (SIZE(10)),

ab-BarringForExceptionData-r13 ENUMERATED {true} OPTIONAL, — Need OP

ab-BarringForSpecialAC-r13 BIT STRING (SIZE(5))

}

— ASN1STOP

SystemInformationBlockType14-NB field descriptions

ab-BarringBitmap

Access class barring for AC 0-9. The first/ leftmost bit is for AC 0, the second bit is for AC 1, and so on.

ab-BarringForExceptionData

Indicates whether ExceptionData is subject to access barring.

ab-BarringForSpecialAC

Access class barring for AC 11-15. The first/ leftmost bit is for AC 11, the second bit is for AC 12, and so on.

ab-Category

Indicates the category of UEs for which AB applies. Value a corresponds to all UEs, value b corresponds to the UEs that are neither in their HPLMN nor in a PLMN that is equivalent to it, and value c corresponds to the UEs that are neither in the PLMN listed as most preferred PLMN of the country where the UEs are roaming in the operator-defined PLMN selector list on the USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN, see TS 22.011 [10].

ab-Common

The AB parameters applicable for all PLMN(s).

ab-PerNRSRP

Access barring per NRSRP. Value thresh1 corresponds to the first entry configured in rsrp-ThresholdsPrachInfoList, value thresh2 corresponds to the second entry configured in rsrp-ThresholdsPrachInfoList.

ab-PerPLMN-List

The AB parameters per PLMN, listed in the same order as the PLMN(s) occur in plmn-IdentityList in SystemInformationBlockType1-NB.

SystemInformationBlockType15-NB

The IE SystemInformationBlockType15-NB contains the MBMS Service Area Identities (SAI) of the current and/ or neighbouring carrier frequencies.

SystemInformationBlockType15-NB information element

— ASN1START

SystemInformationBlockType15-NB-r14 ::= SEQUENCE {

mbms-SAI-IntraFreq-r14 MBMS-SAI-List-r11 OPTIONAL, — Need OR

mbms-SAI-InterFreqList-r14 MBMS-SAI-InterFreqList-NB-r14 OPTIONAL, — Need OR

lateNonCriticalExtension OCTET STRING OPTIONAL,

}

MBMS-SAI-InterFreqList-NB-r14 ::= SEQUENCE (SIZE (1..maxFreq)) OF MBMS-SAI-InterFreq-NB-r14

MBMS-SAI-InterFreq-NB-r14 ::= SEQUENCE {

dl-CarrierFreq-r14 CarrierFreq-NB-r13,

mbms-SAI-List-r14 MBMS-SAI-List-r11,

multiBandInfoList-r14 AdditionalBandInfoList-NB-r14 OPTIONAL — Need OR

}

— ASN1STOP

SystemInformationBlockType15-NB field descriptions

mbms-SAI-InterFreqList

Contains a list of neighboring frequencies including additional frequency bands, if any, that provide MBMS services and the corresponding MBMS SAIs.

mbms-SAI-IntraFreq

Contains the list of MBMS SAIs for the current frequency. A duplicate MBMS SAI indicates that this and all following SAIs are not offered by this cell but only by neighbour cells on the current frequency. For MBMS service continuity, the UE shall use all MBMS SAIs listed in mbms-SAI-IntraFreq to derive the MBMS frequencies of interest.

mbms-SAI-List

Contains a list of MBMS SAIs for a specific frequency.

multiBandInfoList

A list of additional frequency bands applicable for the cells participating in the SC-PTM transmission.

SystemInformationBlockType16-NB

The IE SystemInformationBlockType16-NB contains information related to GPS time and Coordinated Universal Time (UTC). The UE may use the parameters provided in this system information block to obtain the UTC, the GPS and the local time.

— ASN1START

SystemInformationBlockType16-NB-r13 ::= SystemInformationBlockType16-r11

— ASN1STOP

SystemInformationBlockType20-NB

For FDD, the IE SystemInformationBlockType20-NB contains the information required to acquire the control information associated with transmission of MBMS using SC-PTM.

SystemInformationBlockType20-NB information element

— ASN1START

SystemInformationBlockType20-NB-r14 ::= SEQUENCE {

npdcch-SC-MCCH-Config-r14 NPDCCH-SC-MCCH-Config-NB-r14,

sc-mcch-CarrierConfig-r14 CHOICE {

dl-CarrierConfig-r14 DL-CarrierConfigCommon-NB-r14,

dl-CarrierIndex-r14 INTEGER (0..maxNonAnchorCarriers-NB-r14)

},

sc-mcch-RepetitionPeriod-r14 ENUMERATED {rf32, rf128, rf512, rf1024,

rf2048, rf4096, rf8192, rf16384},

sc-mcch-Offset-r14 INTEGER (0..10),

sc-mcch-ModificationPeriod-r14 ENUMERATED { rf32, rf128, rf256, rf512, rf1024,

rf2048, rf4096, rf8192, rf16384, rf32768,

rf65536, rf131072, rf262144, rf524288,

rf1048576, spare1},

sc-mcch-SchedulingInfo-r14 SC-MCCH-SchedulingInfo-NB-r14 OPTIONAL, — Need OP

lateNonCriticalExtension OCTET STRING OPTIONAL,

}

NPDCCH-SC-MCCH-Config-NB-r14 ::= SEQUENCE {

npdcch-NumRepetitions-SC-MCCH-r14 ENUMERATED {r1, r2, r4, r8, r16,

r32, r64, r128, r256,

r512, r1024, r2048},

npdcch-StartSF-SC-MCCH-r14 ENUMERATED {v1dot5, v2, v4, v8,

v16, v32, v48, v64},

npdcch-Offset-SC-MCCH-r14 ENUMERATED {zero, oneEighth, oneQuarter,

threeEighth, oneHalf, fiveEighth,

threeQuarter, sevenEighth}

}

SC-MCCH-SchedulingInfo-NB-r14::= SEQUENCE {

onDurationTimerSCPTM-r14 ENUMERATED {

pp1, pp2, pp3, pp4,

pp8, pp16, pp32, spare},

drx-InactivityTimerSCPTM-r14 ENUMERATED {

pp0, pp1, pp2, pp3,

pp4, pp8, pp16, pp32},

schedulingPeriodStartOffsetSCPTM-r14 CHOICE {

sf10 INTEGER(0..9),

sf20 INTEGER(0..19),

sf32 INTEGER(0..31),

sf40 INTEGER(0..39),

sf64 INTEGER(0..63),

sf80 INTEGER(0..79),

sf128 INTEGER(0..127),

sf160 INTEGER(0..159),

sf256 INTEGER(0..255),

sf320 INTEGER(0..319),

sf512 INTEGER(0..511),

sf640 INTEGER(0..639),

sf1024 INTEGER(0..1023),

sf2048 INTEGER(0..2047),

sf4096 INTEGER(0..4095),

sf8192 INTEGER(0..8191)

},

}

— ASN1STOP

SystemInformationBlockType20-NB field descriptions

dl-CarrierConfig

Downlink carrier used for SC-MCCH. E-UTRAN cannot configure a downlink carrier operating in mixed operation mode.

dl-CarrierIndex

Index to a downlink carrier signalled in system information. Value ‘0’ corresponds to the anchor carrier, value ‘1’ corresponds to the first entry in dl-ConfigList in SystemInformationBlockType22-NB, value ‘2’ corresponds to the second entry in dl-ConfigList and so on.

drx-InactivityTimerSCPTM

Timer for SC-MCCH reception in TS 36.321 [6]. Value in number of NPDCCH periods. Value pp1 corresponds to 1 NPDCCH period, pp2 corresponds to 2 NPDCCH periods and so on.

npdcch-NumRepetitions-SC-MCCH

The maximum number of NPDCCH repetitions the UE needs to monitor for SC-MCCH multicast search space, see TS 36.213 [23].

npdcch-Offset-SC-MCCH

Fractional period offset of starting subframe for NPDCCH multicast search space for SC-MCCH, see TS 36.213 [23].

npdcch-StartSF-SC-MCCH

Starting subframes configuration of the NPDCCH multicast search space for SC-MCCH, see TS 36.213 [23].

onDurationTimerSCPTM

Timer for SC-MCCH reception in TS 36.321 [6]. Value in number of NPDCCH periods. Value pp1 corresponds to 1 NPDCCH period, pp2 corresponds to 2 NPDCCH periods and so on.

schedulingPeriodStartOffsetSCPTM

SCPTM-SchedulingCycle and SCPTM-SchedulingOffset in TS 36.321 [6]. The value of SCPTM-SchedulingCycle is in number of sub-frames. Value sf10 corresponds to 10 sub-frames, sf20 corresponds to 20 sub-frames and so on. The value of SCPTM-SchedulingOffset is in number of sub-frames.

sc-mcch-CarrierConfig

Downlink carrier that is used for SC-MCCH.

sc-mcch-ModificationPeriod

Defines periodically appearing boundaries, i.e. radio frames for which (H-SFN * 1024 +SFN) mod sc-mcch-ModificationPeriod = 0. The contents of different transmissions of SC-MCCH information can only be different if there is at least one such boundary in-between them. Value rf32 corresponds to 32 radio frames, value rf128 corresponds to 128 radio frames and so on.

sc-mcch-Offset

Indicates, together with the sc-mcch-RepetitionPeriod, the boundary of the repetition period: (H-SFN * 1024 +SFN) mod sc-mcch-RepetitionPeriod = sc-mcch-Offset.

sc-mcch-RepetitionPeriod

Defines the interval between transmissions of SC-MCCH information, in radio frames. Value rf32 corresponds to 32 radio frames, rf128 corresponds to 128 radio frames and so on.

sc-mcch-SchedulingInfo

DRX information for the SC-MCCH. If the field is absent, DRX is not used for SC-MCCH reception.

SystemInformationBlockType22-NB

The IE SystemInformationBlockType22-NB contains radio resource configuration for paging and random access procedure on non-anchor carriers.

SystemInformationBlockType22-NB information element

— ASN1START

SystemInformationBlockType22-NB-r14 ::= SEQUENCE {

dl-ConfigList-r14 DL-ConfigCommonList-NB-r14 OPTIONAL, — Need OR

ul-ConfigList-r14 UL-ConfigCommonList-NB-r14 OPTIONAL, — Need OR

pagingWeightAnchor-r14 PagingWeight-NB-r14 OPTIONAL, — Cond pcch-config

nprach-ProbabilityAnchorList-r14 NPRACH-ProbabilityAnchorList-NB-r14 OPTIONAL, — Cond nprach-config

lateNonCriticalExtension OCTET STRING OPTIONAL,

…,

[[ mixedOperationModeConfig-r15 SEQUENCE {

dl-ConfigListMixed-r15 DL-ConfigCommonList-NB-r14 OPTIONAL, — Cond dl-ConfigList

ul-ConfigListMixed-r15 UL-ConfigCommonList-NB-r14 OPTIONAL, — Cond ul-ConfigList

pagingDistribution-r15 ENUMERATED {true} OPTIONAL, — Need OR

nprach-Distribution-r15 ENUMERATED {true} OPTIONAL — Need OR

} OPTIONAL, — Need OR

ul-ConfigList-r15 UL-ConfigCommonListTDD-NB-r15 OPTIONAL — Cond TDD

]]

}

DL-ConfigCommonList-NB-r14 ::= SEQUENCE (SIZE (1..maxNonAnchorCarriers-NB-r14)) OF

DL-ConfigCommon-NB-r14

UL-ConfigCommonList-NB-r14 ::= SEQUENCE (SIZE (1..maxNonAnchorCarriers-NB-r14)) OF

UL-ConfigCommon-NB-r14

UL-ConfigCommonListTDD-NB-r15 ::= SEQUENCE (SIZE (1..maxNonAnchorCarriers-NB-r14)) OF

UL-ConfigCommonTDD-NB-r15

DL-ConfigCommon-NB-r14 ::= SEQUENCE {

dl-CarrierConfig-r14 DL-CarrierConfigCommon-NB-r14,

pcch-Config-r14 PCCH-Config-NB-r14 OPTIONAL, — Need OR

…,

[[ wus-Config-r15 WUS-ConfigPerCarrier-NB-r15 OPTIONAL — Cond WUS

]]

}

PCCH-Config-NB-r14 ::= SEQUENCE {

npdcch-NumRepetitionPaging-r14 ENUMERATED {

r1, r2, r4, r8, r16, r32, r64, r128,

r256, r512, r1024, r2048,

spare4, spare3, spare2, spare1} OPTIONAL, — Need OP

pagingWeight-r14 PagingWeight-NB-r14 DEFAULT w1,

}

PagingWeight-NB-r14 ::= ENUMERATED {w1, w2, w3, w4, w5, w6, w7, w8,

w9, w10, w11, w12, w13, w14, w15, w16}

UL-ConfigCommon-NB-r14 ::= SEQUENCE {

ul-CarrierFreq-r14 CarrierFreq-NB-r13,

nprach-ParametersList-r14 NPRACH-ParametersList-NB-r14 OPTIONAL, — Need OR

…,

[[ nprach-ParametersListEDT-r15 NPRACH-ParametersList-NB-r14 OPTIONAL — Cond EDT

]]

}

UL-ConfigCommonTDD-NB-r15 ::= SEQUENCE {

tdd-UL-DL-AlignmentOffset-r15 TDD-UL-DL-AlignmentOffset-NB-r15,

nprach-ParametersListTDD-r15 NPRACH-ParametersListTDD-NB-r15 OPTIONAL, — Need OR

}

NPRACH-ProbabilityAnchorList-NB-r14 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF

NPRACH-ProbabilityAnchor-NB-r14

NPRACH-ProbabilityAnchor-NB-r14 ::= SEQUENCE {

nprach-ProbabilityAnchor-r14 ENUMERATED {

zero, oneSixteenth, oneFifteenth, oneFourteenth,

oneThirteenth, oneTwelfth, oneEleventh, oneTenth,

oneNinth, oneEighth, oneSeventh, oneSixth,

oneFifth, oneFourth, oneThird, oneHalf}

OPTIONAL — Need OP

}

— ASN1STOP

SystemInformationBlockType22-NB field descriptions

dl-CarrierConfig

For FDD: Provides the configuration of the DL non-anchor carrier.

For TDD: Provides the configuration of the non-anchor carrier.

dl-ConfigList, dl-ConfigListMixed

For FDD: List of DL non-anchor carriers and associated configuration that can be used for paging and/or random access. E-UTRAN configures DL non-anchor carriers operating in mixed operation mode only in dl-ConfigListMixed and only a UE that supports mixed operation mode uses the carriers in dl-ConfigListMixed. A given carrier is either signalled in the dl-ConfigList or in dl-ConfigListMixed.

If dl-ConfigListMixed is present and at least one of the carriers in dl-ConfigListMixed is configured for paging:

– If pagingDistribution is present, the UE supporting mixed operation mode creates a combined list of DL carriers for paging by appending dl-ConfigListMixed to the dl-ConfigList while maintaining the order among dl-ConfigList and dl-ConfigListMixed; the total number of signalled DL non-anchor carriers cannot be more than maxNonAnchorCarriers-NB-r14.

– If pagingDistribution is absent, the UE supporting mixed operation mode uses the list of DL carriers for paging provided in dl-ConfigListMixed and considers pagingWeightAnchor being set to w0, i.e. the anchor carrier is not used.

Otherwise, the pagingDistribution field is not applicable and the UE shall ignore the value.

For TDD: List of non-anchor carriers and associated configuration that can be used for paging and/or random access.

mixedOperationModeConfig

For FDD: Provides the configuration of DL and UL non-anchor carriers that can be used for paging and random access by a UE that supports mixed operation mode.

For TDD: This parameter is absent.

npdcch-NumRepetitionPaging

Maximum number of repetitions for NPDCCH common search space (CSS) for paging, see TS 36.213 [23], clause 16.6.

If the field is absent, the value of npdcch-NumRepetitionPaging configured in SystemInformationBlockType2-NB in IE pcch-Config applies.

nprach-Distribution

Indicates which UL carriers a UE supporting mixed operation mode uses for random access as defined in description of ul-ConfigList, ul-ConfigListMixed.

nprach-ParametersList, nprach-ParametersList-EDT

Configure NPRACH parameters for each NPRACH resource on one non-anchor UL carrier. Up to three NPRACH resources can be configured on one non-anchor UL carrier. Each NPRACH resource is associated with a different number of NPRACH repetitions.

NPRACH resources in nprach-ParametersListEDT are used to initiate EDT. Each NPRACH resource is associated with a maximum TBS signalled in the corresponding entry of edt-TBS-InfoList in SystemInformationBlockType2-NB.

E-UTRAN includes the same number of entries, and listed in the same order, as in nprach-ParametersList in SystemInformationBlockType2-NB.

nprach-ParametersListTDD

For TDD: Configure NPRACH parameters for each NPRACH resource on one non-anchor UL carrier. Up to three NPRACH resources can be configured on one non-anchor UL carrier. Each NPRACH resource is associated with a different number of NPRACH repetitions.

E-UTRAN includes the same number of entries in nprach-ParametersListTDD, and listed in the same order, as in nprach-ParametersListTDD in SystemInformationBlockType2-NB..

nprach-ProbabilityAnchor

Configure the selection probability for the anchor carrier NPRACH resource, see TS 36.321 [6]. Value zero corresponds to a probability of 0, oneSixteenth corresponds to the probability of 1/16, oneFifteenth corresponds to the probability of 1/15, and so on.

If the field is absent, the selection probability of the anchor carrier NPRACH resource is 1.

All non-anchor carriers NPRACH resources have equal probability between them.

If there is no NPRACH resource defined on the anchor carrier for one repetition level in nprach-ParametersList-EDT, (respectively nprach-ParametersListFmt2, nprach-ParametersListFmt2-EDT), the UE shall use the value ‘zero’ and ignore the signalled value of nprach-ProbabilityAnchor for this repetition level for the NPRACH resources defined by nprach-ParametersList-EDT (respectively nprach-ParametersListFmt2, nprach-ParametersListFmt2-EDT).

nprach-ProbabilityAnchorList

Configures the selection probability for each NPRACH resource on the anchor carrier.

E-UTRAN includes the same number of entries, and listed in the same order, as in nprach-ParametersList in SystemInformationBlockType2-NB.

pagingDistribution

Indicates which DL carriers a UE supporting mixed operation mode monitors for paging as defined in description of dl-ConfigList, dl-ConfigListMixed.

pagingWeight

Weight of the non-anchor paging carrier for uneven paging load distribution across the carriers. Value w1 corresponds to a relative weight of 1, w2 corresponds to a relative weight of 2, and so on.

The paging load for a carrier ‘i’ is equal to w(i)/W where i is equal to 0 for the anchor carrier and equal to the index of the carrier in the dl-ConfigList / dl-ConfigListMixed for a non-anchor carrier, W is the sum of the weights of all paging carriers.

To avoid correlation between paging carrier and paging occasion, the weights should be assigned such that: nB * W <= 16384.

pagingWeightAnchor

Weight of the anchor carrier for uneven paging load distribution across the carriers. Value w1 corresponds to a relative weight of 1, w2 corresponds to a relative weight of 2, and so on.

If the field is absent, the (default) value of w0 is applied, i.e. the anchor carrier is not used for paging.

pcch-Config

Configure the PCCH parameters for the non-anchor DL carrier.

tdd-UL-DL-AlignmentOffset

Indicates the offset between the UL carrier frequency center with respect to DL carrier frequency center for the non-anchor carrier.

ul-CarrierFreq

For FDD: UL carrier frequency of the non-anchor carrier as defined in TS 36.101 [42], clause 5.7.3F.

For TDD: This field is absent and the uplink carrier frequency is same as the downlink frequency.

ul-ConfigList, ul-ConfigListMixed

For FDD: List of UL non-anchor carriers and associated configuration that can be used for random access. E-UTRAN configures UL non-anchor carriers operating in mixed operation mode only in ul-ConfigListMixed and only a UE that supports mixed operation mode uses the carriers in ul-ConfigListMixed. A given carrier is either signalled in the ul-ConfigList or in ul-ConfigListMixed.

If ul-ConfigListMixed is present and at least one of the carriers in ul-ConfigListMixed is configured for random access:

– If nprach-Distribution is present, the UE supporting mixed operation mode creates a combined list of UL carriers for random access by appending ul-ConfigListMixed to the ul-ConfigList while maintaining the order among both ul-ConfigList and ul-ConfigListMixed; the total number of signalled UL non-anchor carriers cannot be more than maxNonAnchorCarriers-NB-r14.

– If nprach-Distribution is absent, the UE supporting mixed operation mode uses the list of UL carriers for random access provided in ul-ConfigListMixed and considers nprach-ProbabiliyAnchor being set to zero for each NPRACH resource, i.e. the anchor carrier is not used for random access.

Otherwise, the nprach-Distribution field is not applicable and the UE shall ignore the value.

For TDD: E-UTRAN configures ul-ConfigList-r15 and includes the same number of entries as in dl-ConfigList. The UL carrier frequency of the non-anchor carrier is same as the DL carrier frequency.

wus-Config

For FDD: Carrier specific WUS Configuration.

Conditional presence

Explanation

dl-ConfigList

This field is optionally present, Need OR, if the field dl-ConfigList is present. Otherwise the field is not present.

EDT

The field is optionally present, Need OR, if edt-Parameters in SystemInformationBlockType2-NB is present; otherwise the field is not present and the UE shall delete any existing value for this field.

pcch-config

This field is optionally present, Need OP, if the field dl-ConfigList is present and at least one of the carriers in dl-ConfigList is configured for paging. Otherwise the field is not present and only the anchor carrier is used for paging.

nprach-config

This field is mandatory present, if the field ul-ConfigList is present and at least one of the carriers in ul-ConfigList is configured for random access. Otherwise the field is not present and only the anchor carrier is used for random access.

TDD

This field is optionally present, Need OR, for TDD. Otherwise the field is not present.

ul-ConfigList

This field is optionally present, Need OR, if the field ul-ConfigList is present. Otherwise the field is not present.

WUS

This field is mandatory present, if the field wus-Config is present in SystemInformationBlockType2-NB. Otherwise the field is not present, Need OR.

SystemInformationBlockType23-NB

For FDD, the IE SystemInformationBlockType23-NB contains radio resource configuration for NPRACH resources using preamble format 2 on non-anchor carriers.

SystemInformationBlockType23-NB information element

— ASN1START

SystemInformationBlockType23-NB-r15 ::= SEQUENCE {

ul-ConfigList-v1530 UL-ConfigCommonList-NB-v1530 OPTIONAL, — Need OR

ul-ConfigListMixed-v1530 UL-ConfigCommonList-NB-v1530 OPTIONAL, — Need OR

lateNonCriticalExtension OCTET STRING OPTIONAL,

}

UL-ConfigCommonList-NB-v1530 ::= SEQUENCE (SIZE (1..maxNonAnchorCarriers-NB-r14)) OF

UL-ConfigCommon-NB-v1530

UL-ConfigCommon-NB-v1530 ::= SEQUENCE {

nprach-ParametersListFmt2-r15 NPRACH-ParametersListFmt2-NB-r15 OPTIONAL, — Need OR

nprach-ParametersListFmt2EDT-r15 NPRACH-ParametersListFmt2-NB-r15 OPTIONAL, — Cond EDT

}

— ASN1STOP

SystemInformationBlockType23-NB field descriptions

nprach-ParametersListFmt2, nprach-ParametersListFmt2EDT

Configures NPRACH parameters for each NPRACH resource format 2 on one UL carrier. Up to three NPRACH resources can be configured on one carrier. Each NPRACH resource is associated with a different number of NPRACH repetitions.

E-UTRAN includes the same number of entries, and listed in the same order, as in nprach-ParametersList in SystemInformationBlockType2-NB.

The NPRACH resources in nprach-ParametersListFmt2EDT are used to initiate EDT. Each NPRACH resource is associated with a TBS signalled in the corresponding entry of edt-TBS-InfoList.

E-UTRAN configures the NPRACH resources format 2 so that they do not overlap in time domain with the NPRACH resources configured in nprach-ParametersList and nprach-ParametersListEDT on the same UL carrier.

If there is no NPRACH resource in nprach-ParametersListFmt2 (respectively nprach-ParametersListFmt2EDT) on any UL carrier, including the anchor carrier, for one NPRACH repetition level, the UE uses the NPRACH resources in nprach-ParametersList (respectively nprach-ParametersListEDT) for this NPRACH repetition level. Otherwise, the UE uses only NPRACH resources in nprach-ParametersListFmt2 (respectively nprach-ParametersListFmt2EDT).

If E-UTRAN configures NPRACH resources format 2 in one NPRACH repetition level, the E-UTRAN configures NPRACH resources format 2 in all NPRACH repetition levels upwards.

ul-ConfigList, ul-ConfigListMixed

ul-ConfigList (respectively ul-ConfigListMixed) is parallel to ul-ConfigList (respectively ul-ConfigListMixed) in SystemInformationBlockType22-NB.

E-UTRAN includes the same number of entries and in the same order in ul-ConfigList (respectively ul-ConfigListMixed) in SystemInformationBlockType23-NB as in ul-ConfigList (respectively ul-ConfigListMixed) in SystemInformationBlockType22-NB. The UE combines each entry in ul-ConfigList (respectively ul-ConfigListMixed) in SystemInformationBlockType23-NB with the corresponding entry in ul-ConfigList (respectively ul-ConfigListMixed) in SystemInformationBlockType22-NB.

Conditional presence

Explanation

EDT

The field is optionally present, Need OR, if edt-Parameters in SystemInformationBlockType2-NB is present; otherwise the field is not present and the UE shall delete any existing value for this field.

6.7.3.2 NB-IoT Radio resource control information elements

CarrierConfigDedicated-NB

The IE CarrierConfigDedicated-NB is used to specify a carrier in NB-IoT.

CarrierConfigDedicated-NB information elements

— ASN1START

CarrierConfigDedicated-NB-r13 ::= SEQUENCE {

dl-CarrierConfig-r13 DL-CarrierConfigDedicated-NB-r13,

ul-CarrierConfig-r13 UL-CarrierConfigDedicated-NB-r13

}

DL-CarrierConfigDedicated-NB-r13 ::= SEQUENCE {

dl-CarrierFreq-r13 CarrierFreq-NB-r13,

downlinkBitmapNonAnchor-r13 CHOICE {

useNoBitmap-r13 NULL,

useAnchorBitmap-r13 NULL,

explicitBitmapConfiguration-r13 DL-Bitmap-NB-r13,

spare NULL

} OPTIONAL, — Need ON

dl-GapNonAnchor-r13 CHOICE {

useNoGap-r13 NULL,

useAnchorGapConfig-r13 NULL,

explicitGapConfiguration-r13 DL-GapConfig-NB-r13,

spare NULL

} OPTIONAL, — Need ON

inbandCarrierInfo-r13 SEQUENCE {

samePCI-Indicator-r13 CHOICE {

samePCI-r13 SEQUENCE {

indexToMidPRB-r13 INTEGER (-55..54)

},

differentPCI-r13 SEQUENCE {

eutra-NumCRS-Ports-r13 ENUMERATED {same, four}

}

} OPTIONAL, — Cond anchor-guardband-or-standalone

eutraControlRegionSize-r13 ENUMERATED {n1, n2, n3}

} OPTIONAL, — Cond non-anchor-inband

…,

[[ nrs-PowerOffsetNonAnchor-v1330 ENUMERATED {dB-12, dB-10, dB-8, dB-6,

dB-4, dB-2, dB0, dB3}

OPTIONAL — Need ON

]],

[[ dl-GapNonAnchor-v1530 DL-GapConfig-NB-v1530 OPTIONAL — Cond TDD1

]],

[[ dl-CarrierFreq-v1550 CarrierFreq-NB-v1550 OPTIONAL — Cond TDD1

]]

}

UL-CarrierConfigDedicated-NB-r13 ::= SEQUENCE {

ul-CarrierFreq-r13 CarrierFreq-NB-r13 OPTIONAL, — Need OP

…,

[[ tdd-UL-DL-AlignmentOffset-r15 TDD-UL-DL-AlignmentOffset-NB-r15 OPTIONAL — Cond TDD

]]

}

— ASN1STOP

CarrierConfigDedicated-NB field descriptions

dl-CarrierConfig

Downlink carrier used for all unicast transmissions.

dl-CarrierFreq

DL carrier frequency. The downlink carrier is not in a E-UTRA PRB which contains E-UTRA PSS/SSS/PBCH.

dl-GapNonAnchor

Downlink transmission gap configuration for the anchor/ non-anchor carrier, see TS 36.211 [21], clause 10.2.3.4.

E-UTRAN may configure dl-GapNonAnchor-v1530 only if dl-GapNonAnchor-r13 is set to explicitGapConfiguration.

downlinkBitmapNonAnchor

For FDD: NB-IoT downlink subframe configuration for downlink transmission on the anchor/ non-anchor carrier. See TS 36.213 [23], clause 16.4.

For TDD: NB-IoT downlink, uplink and special subframes configuration for transmission on the anchor/ non-anchor carrier. See TS 36.213 [23], clause 16.4.

eutraControlRegionSize

Indicates the control region size of the E-UTRA cell for the in-band operation mode, see TS 36.213 [23]. Unit is in number of OFDM symbols. If operationModeInfo in MIB-NB is set to inband-SamePCI or inband-DifferentPCI, it should be set to the value broadcast in SIB1-NB.

eutra-NumCRS-Ports

Number of E-UTRA CRS antenna ports, either the same number of ports as NRS or 4 antenna ports. See TS 36.211 [21], TS 36.212 [22], and TS 36.213 [23].

inbandCarrierInfo

Provides the configuration of the anchor/ non-anchor inband carrier. If operationModeInfo is set to standalone in the MIB-NB, E-UTRAN only configures this field if the UE supports mixed operation mode.

indexToMidPRB

The PRB index is signaled by offset from the middle of the EUTRA system.

nrs-PowerOffsetNonAnchor

Provides the power offset of the downlink narrowband reference-signal EPRE of the anchor/ non-anchor carrier relative to the anchor carrier, unit in dB. Value dB-12 corresponds to -12 dB, dB-10 corresponds to -10 dB and so on. See TS 36.213 [23], clause16.2.2.

samePCI-Indicator

This parameter specifies whether the anchor/ non-anchor carrier reuses the same PCI as the EUTRA carrier.

ul-CarrierConfig

Uplink anchor/ non-anchor carrier used for all unicast transmissions.

ul-CarrierFreq

For FDD: UL carrier frequency as defined in TS 36.101 [42], clause 5.7.3F. If absent, the same TX-RX frequency separation and carrier frequency offset as for the anchor carrier applies.

For TDD: This field is absent and the uplink carrier frequency is equal to the downlink frequency.

Conditional presence

Explanation

non-anchor-inband

The field is mandatory present if the anchor/ non-anchor carrier is an inband carrier; otherwise it is not present.

anchor-guardband-or-standalone

The field is mandatory present if operationModeInfo is set to guardband or standalone in the MIB; otherwise it is not present.

TDD

The field is mandatory present for TDD; otherwise the field is not present and the UE shall delete any existing value for this field.

TDD1

The field is optionally present, Need OR, for TDD; otherwise the field is not present and the UE shall delete any existing value for this field.

CarrierFreq-NB

The IE CarrierFreq-NB is used to provide the NB-IoT carrier frequency, as defined in TS 36.101 [42].

CarrierFreq-NB information elements

— ASN1START

CarrierFreq-NB-r13 ::= SEQUENCE {

carrierFreq-r13 ARFCN-ValueEUTRA-r9,

carrierFreqOffset-r13 ENUMERATED {

v-10, v-9, v-8, v-7, v-6, v-5, v-4, v-3, v-2, v-1, v-0dot5,

v0, v1, v2, v3, v4, v5, v6, v7, v8, v9

} OPTIONAL — Need ON

}

CarrierFreq-NB-v1550 ::= SEQUENCE {

carrierFreqOffset-v1550 ENUMERATED {v-8dot5, v-4dot5, v3dot5, v7dot5}

}

— ASN1STOP

CarrierFreq-NB field descriptions

carrierFreq

Provides the ARFCN applicable for the NB-IoT carrier frequency as defined in TS 36.101 [42], Table 5.7.3-1.

carrierFreqOffset

Offset of the NB-IoT channel number to EARFCN as defined in TS 36.101 [42], clause 5.7.3F. Value v-10 means -10, v-9 means -9, and so on. E-UTRAN may configure the values v-8dot5, v-4dot5, v3dot5 and v7dot5 only for a carrier in a TDD band.

For TDD, the UE shall use the value signalled in carrierFreqOffset-v1550, if present, and ignore the value signaled in carrierFreqOffset-r13.

– ChannelRasterOffset-NB

The IE ChannelRasterOffset-NB is used to specify the NB-IoT offset from LTE channel raster. Unit in kHz in set { -7.5, -2.5, 2.5, 7.5} See TS 36.211[21] and TS 36.213 [23].

ChannelRasterOffset-NB information element

— ASN1START

ChannelRasterOffset-NB-r13 ::= ENUMERATED {khz-7dot5, khz-2dot5, khz2dot5, khz7dot5}

— ASN1STOP

DL-Bitmap-NB

The IE DL-Bitmap-NB is used to specify the set of NB-IoT downlink subframes for downlink transmission.

DL-Bitmap-NB information element

— ASN1START

DL-Bitmap-NB-r13 ::= CHOICE {

subframePattern10-r13 BIT STRING (SIZE (10)),

subframePattern40-r13 BIT STRING (SIZE (40))

}

— ASN1STOP

DL-Bitmap-NB field descriptions

subframePattern10, subframePattern40

For FDD: NB-IoT downlink subframe configuration over 10ms or 40ms for inband and 10ms for standalone/guardband.

For TDD: NB-IoT downlink, uplink and special subframes configuration over 10ms or 40ms for inband and 10ms for standalone/guardband.

The first/leftmost bit corresponds to the subframe #0 of the radio frame satisfying SFN mod x = 0, where x is the size of the bit string divided by 10. Value 0 in the bitmap indicates that the corresponding subframe is invalid for transmission. Value 1 in the bitmap indicates that the corresponding subframe is valid for transmission.

DL-CarrierConfigCommon-NB

The IE DL-CarrierConfigCommon-NB is used to specify the common configuration of a DL non-anchor carrier in NB-IoT.

DL-CarrierConfigCommon-NB information elements

— ASN1START

DL-CarrierConfigCommon-NB-r14 ::= SEQUENCE {

dl-CarrierFreq-r14 CarrierFreq-NB-r13,

downlinkBitmapNonAnchor-r14 CHOICE {

useNoBitmap-r14 NULL,

useAnchorBitmap-r14 NULL,

explicitBitmapConfiguration-r14 DL-Bitmap-NB-r13

},

dl-GapNonAnchor-r14 CHOICE {

useNoGap-r14 NULL,

useAnchorGapConfig-r14 NULL,

explicitGapConfiguration-r14 DL-GapConfig-NB-r13

},

inbandCarrierInfo-r14 SEQUENCE {

samePCI-Indicator-r14 CHOICE {

samePCI-r14 SEQUENCE {

indexToMidPRB-r14 INTEGER (-55..54)

},

differentPCI-r14 SEQUENCE {

eutra-NumCRS-Ports-r14 ENUMERATED {same, four}

}

} OPTIONAL, — Cond anchor-guardband-or-standalone

eutraControlRegionSize-r14 ENUMERATED {n1, n2, n3}

} OPTIONAL, — Cond non-anchor-inband

nrs-PowerOffsetNonAnchor-r14 ENUMERATED {dB-12, dB-10, dB-8, dB-6,

dB-4, dB-2, dB0, dB3} DEFAULT dB0,

…,

[[ dl-GapNonAnchor-v1530 DL-GapConfig-NB-v1530 OPTIONAL — Cond TDD

]],

[[ dl-CarrierFreq-v1550 CarrierFreq-NB-v1550 OPTIONAL — Cond TDD

]]

}

— ASN1STOP

DL-CarrierConfigCommon-NB field descriptions

dl-CarrierFreq

DL carrier frequency. The downlink carrier is not in a E-UTRA PRB which contains E-UTRA PSS/SSS/PBCH.

dl-GapNonAnchor

Downlink transmission gap configuration for the non-anchor carrier, see TS 36.211 [21], clause 10.2.3.4.

E-UTRAN may configure dl-GapNonAnchor-v1530 only if dl-GapNonAnchor-r14 is set to explicitGapConfiguration.

downlinkBitmapNonAnchor

For FDD: NB-IoT downlink subframe configuration for downlink transmission on the non-anchor carrier. See TS 36.213 [23], clause 16.4.

For TDD: NB-IoT downlink, uplink and special subframes configuration for transmission on the anchor/ non-anchor carrier. See TS 36.213 [23], clause 16.4.

eutraControlRegionSize

Indicates the control region size of the E-UTRA cell for the in-band operation mode, see TS 36.213 [23]. Unit is in number of OFDM symbols. If operationModeInfo in MIB-NB is set to inband-SamePCI or inband-DifferentPCI, it should be set to the value broadcast in SIB1-NB.

eutra-NumCRS-Ports

Number of E-UTRA CRS antenna ports, either the same number of ports as NRS or 4 antenna ports. See TS 36.211 [21], TS 36.212 [22], and TS 36.213 [23].

inbandCarrierInfo

Provides the configuration of a non-anchor inband carrier.

indexToMidPRB

The PRB index is signaled by offset from the middle of the EUTRA system.

nrs-PowerOffsetNonAnchor

Provides the downlink narrowband reference-signal EPRE offset of the non-anchor carrier relative to the downlink narrowband reference-signal EPRE of the anchor carrier, unit in dB. Value dB-12 corresponds to -12 dB, dB-10 corresponds to -10 dB and so on. See TS 36.213 [23], clause 16.2.2.

samePCI-Indicator

This parameter specifies whether the non-anchor carrier reuses the same PCI as the EUTRA carrier.

Conditional presence

Explanation

non-anchor-inband

The field is mandatory present if the non-anchor carrier is an inband carrier; otherwise it is not present.

anchor-guardband-or-standalone

The field is mandatory present, if operationModeInfo is set to guardband or standalone in the MIB; otherwise it is not present.

TDD

The field is optionally present, Need OR, for TDD; otherwise the field is not present and the UE shall delete any existing value for this field.

DL-GapConfig-NB

The IE DL-GapConfig-NB is used to specify the downlink gap configuration for NPDCCH and NPDSCH. Downlink gaps apply to all NPDCCH/NPDSCH transmissions except for BCCH.

DL-GapConfig-NB information element

— ASN1START

DL-GapConfig-NB-r13 ::= SEQUENCE {

dl-GapThreshold-r13 ENUMERATED {n32, n64, n128, n256},

dl-GapPeriodicity-r13 ENUMERATED {sf64, sf128, sf256, sf512},

dl-GapDurationCoeff-r13 ENUMERATED {oneEighth, oneFourth, threeEighth, oneHalf}

}

DL-GapConfig-NB-v1530 ::= SEQUENCE {

dl-GapPeriodicity-v1530 ENUMERATED {sf1024}

}

— ASN1STOP

DL-GapConfig-NB field descriptions

dl-GapDurationCoeff

Coefficient to calculate the gap duration of a DL transmission: dl-GapDurationCoeff * dl-GapPeriodicity, Duration in number of subframes. See TS 36.211 [21], clause 10.2.3.4.

dl-GapPeriodicity

Periodicity of a DL transmission gap in number of subframes. See TS 36.211 [21], clause 10.2.3.4.

Value sf64 corresponds to 64 subframes, value sf128 corresponds to 128 subframes, value sf256 corresponds to 256 subframes and so on. E-UTRAN may configure the value sf64 only in FDD mode and the value sf1024 only in TDD mode.

The UE shall use the value signalled in dl-GapPeriodicity-v1530, if present, and ignore the value signaled in dl-GapPeriodicity-r13.

dl-GapThreshold

Threshold on the maximum number of repetitions configured for NPDCCH before application of DL transmission gap configuration. See TS 36.211 [21], clause 10.2.3.4.

LogicalChannelConfig-NB

The IE LogicalChannelConfig-NB is used to configure the logical channel parameters.

LogicalChannelConfig-NB information element

— ASN1START

LogicalChannelConfig-NB-r13 ::= SEQUENCE {

priority-r13 INTEGER (1..16) OPTIONAL, — Cond UL

logicalChannelSR-Prohibit-r13 BOOLEAN OPTIONAL, — Need ON

}

— ASN1STOP

LogicalChannelConfig-NB field descriptions

logicalChannelSR-Prohibit

Value TRUE indicates that the logicalChannelSR-ProhibitTimer is enabled for the logical channel. If logicalChannelSR-Prohibit is configured (i.e. indicates value TRUE), E-UTRAN also configures logicalChannelSR-ProhibitTimer. See TS 36.321 [6].

priority

Logical channel priority in TS 36.321 [6]. Value is an integer.

Conditional presence

Explanation

UL

The field is mandatory present for UL logical channels; otherwise it is not present.

MAC-MainConfig-NB

The IE MAC-MainConfig-NB is used to specify the MAC main configuration for signalling and data radio bearers.

MAC-MainConfig-NB information element

— ASN1START

MAC-MainConfig-NB-r13 ::= SEQUENCE {

ul-SCH-Config-r13 SEQUENCE {

periodicBSR-Timer-r13 PeriodicBSR-Timer-NB-r13 OPTIONAL, — Need ON

retxBSR-Timer-r13 RetxBSR-Timer-NB-r13

} OPTIONAL, — Need ON

drx-Config-r13 DRX-Config-NB-r13 OPTIONAL, — Need ON

timeAlignmentTimerDedicated-r13 TimeAlignmentTimer,

logicalChannelSR-Config-r13 CHOICE {

release NULL,

setup SEQUENCE {

logicalChannelSR-ProhibitTimer-r13 ENUMERATED {

pp2, pp8, pp32, pp128, pp512,

pp1024, pp2048, spare}

}

} OPTIONAL, — Need ON

…,

[[ rai-Activation-r14 ENUMERATED {true} OPTIONAL, — Need OR

dataInactivityTimerConfig-r14 CHOICE {

release NULL,

setup SEQUENCE {

dataInactivityTimer-r14 DataInactivityTimer-r14

}

} OPTIONAL — Need ON

]],

[[ drx-Cycle-v1430 ENUMERATED {

sf1280, sf2560, sf5120, sf10240} OPTIONAL — Need ON

]],

[[ ra-CFRA-Config-r14 ENUMERATED {true} OPTIONAL — Need ON

]]

}

PeriodicBSR-Timer-NB-r13 ::= ENUMERATED {

pp2, pp4, pp8, pp16, pp64, pp128, infinity, spare}

RetxBSR-Timer-NB-r13 ::= ENUMERATED {

pp4, pp16, pp64, pp128, pp256, pp512, infinity, spare}

DRX-Config-NB-r13 ::= CHOICE {

release NULL,

setup SEQUENCE {

onDurationTimer-r13 ENUMERATED {

pp1, pp2, pp3, pp4, pp8, pp16, pp32, spare},

drx-InactivityTimer-r13 ENUMERATED {

pp0, pp1, pp2, pp3, pp4, pp8, pp16, pp32},

drx-RetransmissionTimer-r13 ENUMERATED {

pp0, pp1, pp2, pp4, pp6, pp8, pp16, pp24,

pp33, spare7, spare6, spare5,

spare4, spare3, spare2, spare1},

drx-Cycle-r13 ENUMERATED {

sf256, sf512, sf1024, sf1536, sf2048, sf3072,

sf4096, sf4608, sf6144, sf7680, sf8192, sf9216,

spare4, spare3, spare2, spare1},

drx-StartOffset-r13 INTEGER (0..255),

drx-ULRetransmissionTimer-r13 ENUMERATED {

pp0, pp1, pp2, pp4, pp6, pp8, pp16, pp24,

pp33, pp40, pp64, pp80, pp96,

pp112, pp128, pp160, pp320}

}

}

— ASN1STOP

MAC-MainConfigNB field descriptions

drx-Config

Used to configure DRX as specified in TS 36.321 [6].

drx-Cycle

longDRX-Cycle in TS 36.321 [6]. The value of longDRX-Cycle is in number of sub-frames. Value sf256 corresponds to 256 sub-frames, sf512 corresponds to 512 sub-frames and so on. In case drx-Cycle-v1430 is signalled, the UE shall ignore drx-Cycle-r13.

drx-StartOffset

drxStartOffset in TS 36.321 [6]. Value is in number of sub-frames by step of (drx-cycle / 256).

drx-InactivityTimer

Timer for DRX in TS 36.321 [6]. Value in number of PDCCH periods. Value pp0 corresponds to 0 PDCCH period and behaviour as specified in 7.3.2 applies, pp1 corresponds to 1 PDCCH period, pp2 corresponds to 2 PDCCH periods and so on.

drx-RetransmissionTimer

Timer for DRX in TS 36.321 [6]. Value in number of PDCCH periods. Value pp0 corresponds to 0 PDCCH period and behaviour as specified in 7.3.2 applies, pp1 corresponds to 1 PDCCH period, pp2 corresponds to 2 PDCCH periods and so on.

drx-ULRetransmissionTimer

Timer for DRX in TS 36.321 [6].

Value in number of PDCCH periods. Value pp0 corresponds to 0 PDCCH period and behaviour as specified in 7.3.2 applies, value pp1 corresponds to 1 PDCCH period, pp2 corresponds to 2 PDCCH periods and so on.

logicalChannelSR-ProhibitTimer

Timer used to delay the transmission of an SR. See TS 36.321 [6]. Value in number of PDCCH periods. Value pp2 corresponds to 2 PDCCH periods, pp8 corresponds to 8 PDCCH periods and so on.

periodicBSR-Timer

Timer for BSR reporting in TS 36.321 [6].

Value in number of PDCCH periods. Value pp2 corresponds to 2 PDCCH periods, pp4 corresponds to 4 PDCCH periods and so on.

ra-CFRA-Config

Activation of contention free random access (CFRA), see TS 36.321 [6].

rai-Activation

Activation of release assistance indication (RAI) in TS 36.321 [6].

retxBSR-Timer

Timer for BSR reporting in TS 36.321 [6]. Value in number of PDCCH periods. Value pp4 corresponds to 4 PDCCH periods, pp16 corresponds to 16 PDCCH periods and so on.

onDurationTimer

Timer for DRX in TS 36.321 [6]. Value in number of PDCCH periods. Value pp1 corresponds to 1 PDCCH period, pp2 corresponds to 2 PDCCH periods and so on.

timeAlignmentTimer

Indicates the value of the time alignment timer, see TS 36.321 [6].

NPDCCH-ConfigDedicated-NB

The IE NPDCCH-ConfigDedicated-NB specifies the subframes and resource blocks for NPDCCH monitoring.

NPDCCH-ConfigDedicated-NB information element

— ASN1START

NPDCCH-ConfigDedicated-NB-r13 ::= SEQUENCE {

npdcch-NumRepetitions-r13 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, r128,

r256, r512, r1024, r2048,

spare4, spare3, spare2, spare1},

npdcch-StartSF-USS-r13 ENUMERATED {v1dot5, v2, v4, v8, v16, v32, v48, v64},

npdcch-Offset-USS-r13 ENUMERATED {zero, oneEighth, oneFourth, threeEighth}

}

NPDCCH-ConfigDedicated-NB-v1530 ::= SEQUENCE {

npdcch-StartSF-USS-v1530 ENUMERATED {v96, v128}

}

— ASN1STOP

NPDCCH-ConfigDedicated-NB field descriptions

npdcch-NumRepetitions

Maximum number of repetitions for NPDCCH UE specific search space (USS), see TS 36.213 [23], clause 16.6. UE monitors one set of values (consisting of aggregation level, number of repetitions and number of blind decodes) according to the configured maximum number of repetitions.

npdcch-Offset-USS

Fractional period offset of starting subframe for NPDCCH UE specific search space (USS), see TS 36.213 [23], clause 16.6.

npdcch-StartSF-USS

Starting subframe configuration for an NPDCCH UE-specific search space, see TS 36.213 [23], clause 16.6. Value v1dot5 corresponds to 1.5, value 2 corresponds to 2 and so on. E-UTRAN may configure values v1dot5 and v2 only in FDD mode and values v96 and v128 only in TDD mode.

The UE shall use the value signalled in npdcch-StartSF-USS-v1530, if present, and ignore the value signalled in npdcch-StartSF-USS-r13.

NPDSCH-ConfigCommon-NB

The IE NPDSCH-ConfigCommon-NB is used to specify the common NPDSCH configuration.

NPDSCH-ConfigCommon-NB information element

— ASN1START

NPDSCH-ConfigCommon-NB-r13 ::= SEQUENCE {

nrs-Power-r13 INTEGER (-60..50)

}

— ASN1STOP

NPDSCH-ConfigCommon-NB field descriptions

nrs-Power

Provides the downlink narrowband reference-signal EPRE, see TS 36.213 [23], clause 16.2. The actual value in dBm.

NPRACH-ConfigSIB-NB

The IE NPRACH-ConfigSIB-NB is used to specify the NPRACH configuration for the anchor and non-anchor carriers.

NPRACH-ConfigSIB-NB information elements

— ASN1START

NPRACH-ConfigSIB-NB-r13 ::= SEQUENCE {

nprach-CP-Length-r13 ENUMERATED {us66dot7, us266dot7},

rsrp-ThresholdsPrachInfoList-r13 RSRP-ThresholdsNPRACH-InfoList-NB-r13 OPTIONAL, — Need OR

nprach-ParametersList-r13 NPRACH-ParametersList-NB-r13

}

NPRACH-ConfigSIB-NB-v1330 ::= SEQUENCE {

nprach-ParametersList-v1330 NPRACH-ParametersList-NB-v1330

}

NPRACH-ConfigSIB-NB-v1450 ::= SEQUENCE {

maxNumPreambleAttemptCE-r14 ENUMERATED {n3, n4, n5, n6, n7, n8, n10, spare1}

}

NPRACH-ConfigSIB-NB-v1530 ::= SEQUENCE {

tdd-Parameters-r15 SEQUENCE {

nprach-PreambleFormat-r15 ENUMERATED {

fmt0, fmt1, fmt2, fmt0-a, fmt1-a},

dummy ENUMERATED {

n1, n2, n4, n8, n16, n32, n64, n128,

n256, n512, n1024},

nprach-ParametersListTDD-r15 NPRACH-ParametersListTDD-NB-r15

} OPTIONAL, — Cond TDD

fmt2-Parameters-r15 SEQUENCE {

nprach-ParametersListFmt2-r15 NPRACH-ParametersListFmt2-NB-r15 OPTIONAL, — Need OR

nprach-ParametersListFmt2EDT-r15 NPRACH-ParametersListFmt2-NB-r15 OPTIONAL — Cond EDT2

} OPTIONAL, — Need OR

edt-Parameters-r15 SEQUENCE {

edt-SmallTBS-Subset-r15 ENUMERATED {true} OPTIONAL, — Need OR

edt-TBS-InfoList-r15 EDT-TBS-InfoList-NB-r15,

nprach-ParametersListEDT-r15 NPRACH-ParametersList-NB-r14 OPTIONAL — Need OR

} OPTIONAL — Cond EDT1

}

NPRACH-ConfigSIB-NB-v1550 ::= SEQUENCE {

tdd-Parameters-v1550 SEQUENCE {

nprach-ParametersListTDD-v1550 NPRACH-ParametersListTDD-NB-v1550

}

}

NPRACH-ParametersList-NB-r13 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF NPRACH-Parameters-NB-r13

NPRACH-ParametersList-NB-v1330 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF NPRACH-Parameters-NB-v1330

NPRACH-Parameters-NB-r13::= SEQUENCE {

nprach-Periodicity-r13 ENUMERATED {ms40, ms80, ms160, ms240,

ms320, ms640, ms1280, ms2560},

nprach-StartTime-r13 ENUMERATED {ms8, ms16, ms32, ms64,

ms128, ms256, ms512, ms1024},

nprach-SubcarrierOffset-r13 ENUMERATED {n0, n12, n24, n36, n2, n18, n34, spare1},

nprach-NumSubcarriers-r13 ENUMERATED {n12, n24, n36, n48},

nprach-SubcarrierMSG3-RangeStart-r13 ENUMERATED {zero, oneThird, twoThird, one},

maxNumPreambleAttemptCE-r13 ENUMERATED {n3, n4, n5, n6, n7, n8, n10, spare1},

numRepetitionsPerPreambleAttempt-r13 ENUMERATED {n1, n2, n4, n8, n16, n32, n64, n128},

npdcch-NumRepetitions-RA-r13 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, r128,

r256, r512, r1024, r2048,

spare4, spare3, spare2, spare1},

npdcch-StartSF-CSS-RA-r13 ENUMERATED {v1dot5, v2, v4, v8, v16, v32, v48, v64},

npdcch-Offset-RA-r13 ENUMERATED {zero, oneEighth, oneFourth, threeEighth}

}

NPRACH-Parameters-NB-v1330 ::= SEQUENCE {

nprach-NumCBRA-StartSubcarriers-r13 ENUMERATED {n8, n10, n11, n12, n20, n22, n23, n24,

n32, n34, n35, n36, n40, n44, n46, n48}

}

NPRACH-ParametersList-NB-r14 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF

NPRACH-Parameters-NB-r14

NPRACH-Parameters-NB-r14 ::= SEQUENCE {

nprach-Parameters-r14 SEQUENCE {

nprach-Periodicity-r14 ENUMERATED {ms40, ms80, ms160, ms240,

ms320, ms640, ms1280, ms2560}

OPTIONAL, — NEED OP

nprach-StartTime-r14 ENUMERATED {ms8, ms16, ms32, ms64,

ms128, ms256, ms512, ms1024}

OPTIONAL, — NEED OP

nprach-SubcarrierOffset-r14 ENUMERATED {n0, n12, n24, n36, n2, n18, n34, spare1}

OPTIONAL, — NEED OP

nprach-NumSubcarriers-r14 ENUMERATED {n12, n24, n36, n48}

OPTIONAL, — NEED OP

nprach-SubcarrierMSG3-RangeStart-r14 ENUMERATED {zero, oneThird, twoThird, one}

OPTIONAL, — NEED OP

npdcch-NumRepetitions-RA-r14 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, r128,

r256, r512, r1024, r2048,

spare4, spare3, spare2, spare1}

OPTIONAL, — NEED OP

npdcch-StartSF-CSS-RA-r14 ENUMERATED {v1dot5, v2, v4, v8, v16, v32, v48, v64}

OPTIONAL, — NEED OP

npdcch-Offset-RA-r14 ENUMERATED {zero, oneEighth, oneFourth, threeEighth}

OPTIONAL, — NEED OP

nprach-NumCBRA-StartSubcarriers-r14 ENUMERATED {n8, n10, n11, n12, n20, n22, n23, n24,

n32, n34, n35, n36, n40, n44, n46, n48}

OPTIONAL, — NEED OP

npdcch-CarrierIndex-r14 INTEGER (1..maxNonAnchorCarriers-NB-r14)

OPTIONAL, — Need OP

} OPTIONAL — Need OR

}

NPRACH-ParametersListTDD-NB-r15 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF

NPRACH-ParametersTDD-NB-r15

NPRACH-ParametersTDD-NB-r15 ::= SEQUENCE {

nprach-Parameters-r15 SEQUENCE {

nprach-Periodicity-r15 ENUMERATED {ms80, ms160, ms320, ms640,

ms1280, ms2560, ms5120, ms10240}

OPTIONAL, — NEED OP

nprach-StartTime-r15 ENUMERATED {ms10, ms20, ms40, ms80,

ms160, ms320, ms640, ms1280,

ms2560, ms5120, spare6, spare5,

spare4, spare3, spare2, spare1}

OPTIONAL, — NEED OP

nprach-SubcarrierOffset-r15 ENUMERATED {n0, n12, n24, n36, n2, n18, n34, spare1}

OPTIONAL, — NEED OP

nprach-NumSubcarriers-r15 ENUMERATED {n12, n24, n36, n48}

OPTIONAL, — NEED OP

nprach-SubcarrierMSG3-RangeStart-r15 ENUMERATED {zero, oneThird, twoThird, one}

OPTIONAL, — NEED OP

npdcch-NumRepetitions-RA-r15 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, r128,

r256, r512, r1024, r2048,

spare4, spare3, spare2, spare1}

OPTIONAL, — NEED OP

npdcch-StartSF-CSS-RA-r15 ENUMERATED {v4, v8, v16, v32, v48, v64, v96, v128}

OPTIONAL, — NEED OP

npdcch-Offset-RA-r15 ENUMERATED {zero, oneEighth, oneFourth, threeEighth}

OPTIONAL, — NEED OP

nprach-NumCBRA-StartSubcarriers-r15 ENUMERATED {n8, n10, n11, n12, n20, n22, n23, n24,

n32, n34, n35, n36, n40, n44, n46, n48}

OPTIONAL, — NEED OP

} OPTIONAL — Need OR

}

NPRACH-ParametersListTDD-NB-v1550 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF

NPRACH-ParametersTDD-NB-v1550

NPRACH-ParametersTDD-NB-v1550 ::= SEQUENCE {

maxNumPreambleAttemptCE-v1550 ENUMERATED {n3, n4, n5, n6, n7, n8, n10, spare1},

numRepetitionsPerPreambleAttempt-v1550 ENUMERATED {n1, n2, n4, n8, n16, n32, n64, n128,

n256, n512, n1024}

}

NPRACH-ParametersListFmt2-NB-r15 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF NPRACH-ParametersFmt2-NB-r15

NPRACH-ParametersFmt2-NB-r15 ::= SEQUENCE {

nprach-Parameters-r15 SEQUENCE {

nprach-Periodicity-r15 ENUMERATED {ms40, ms80, ms160, ms320,

ms640, ms1280, ms2560, ms5120}

OPTIONAL, — NEED OP

nprach-StartTime-r15 ENUMERATED {ms8, ms16, ms32, ms64,

ms128, ms256, ms512, ms1024}

OPTIONAL, — NEED OP

nprach-SubcarrierOffset-r15 ENUMERATED {n0, n36, n72, n108, n6, n54, n102, n42,

n78, n90, n12, n24, n48, n84, n60, n18}

OPTIONAL, — NEED OP

nprach-NumSubcarriers-r15 ENUMERATED {n36, n72, n108, n144}

OPTIONAL, — NEED OP

nprach-SubcarrierMSG3-RangeStart-r15 ENUMERATED {zero, oneThird, twoThird, one}

OPTIONAL, — NEED OP

npdcch-NumRepetitions-RA-r15 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, r128,

r256, r512, r1024, r2048,

spare4, spare3, spare2, spare1}

OPTIONAL, — NEED OP

npdcch-StartSF-CSS-RA-r15 ENUMERATED {v1dot5, v2, v4, v8, v16, v32, v48, v64}

OPTIONAL, — NEED OP

npdcch-Offset-RA-r15 ENUMERATED {zero, oneEighth, oneFourth, threeEighth}

OPTIONAL, — NEED OP

nprach-NumCBRA-StartSubcarriers-r15 ENUMERATED {

n24, n30, n33, n36, n60, n66, n69, n72,

n96, n102, n105, n108, n120, n132, n138, n144}

OPTIONAL, — NEED OP

npdcch-CarrierIndex-r15 INTEGER (1..maxNonAnchorCarriers-NB-r14)

OPTIONAL, — Need OP

} OPTIONAL — Need OR

}

RSRP-ThresholdsNPRACH-InfoList-NB-r13 ::= SEQUENCE (SIZE(1..2)) OF RSRP-Range

EDT-TBS-InfoList-NB-r15 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF EDT-TBS-NB-r15

EDT-TBS-NB-r15 ::= SEQUENCE {

edt-SmallTBS-Enabled-r15 BOOLEAN,

edt-TBS-r15 ENUMERATED {b328, b408, b504, b584, b680, b808, b936, b1000}

}

— ASN1STOP

NPRACH-ConfigSIB-NB field descriptions

dummy

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

edt-SmallTBS-Enabled

Value TRUE indicates UE performing EDT is allowed to select TBS smaller than edt-TBS for Msg3 according to the corresponding NPRACH resource, as specified in TS 36.213 [23].

edt-SmallTBS-Subset

Presence indicates only two of the TBS values can be used according to edt-TBS corresponding to the NPRACH resource, as specified in TS 36.213 [23]. When the field is not present, any of the TBS values according to edt-TBS corresponding to the NPRACH resource can be used. This field is applicable for a NPRACH resource only when edt-SmallTBS-Enabled is included for the corresponding NPRACH resource.

edt-TBS

Largest TBS for Msg3 for a NPRACH resource applicable to a UE performing EDT. Value in bits. Value b328 corresponds to 328 bits, value b408 corresponds to 408 bits and so on. See TS 36.213 [23].

maxNumPreambleAttemptCE

Maximum number of preamble transmission attempts per NPRACH resource. See TS 36.321 [6].

If the UE supports enhanced random access power control and maxNumPreambleAttemptCE-r14 is included, the UE shall use maxNumPreambleAttemptCE-r14 instead of maxNumPreambleAttemptCE-r13 for the first entry in nprach-ParametersList.

maxNumPreambleAttemptCE-r13 applies to FDD and maxNumPreambleAttemptCE-v1550 applies to TDD.

npdcch-CarrierIndex

For FDD: Index of the carrier in the list of DL non anchor carriers. The first entry in the list has index ‘1’, the second entry has index ‘2’ and so on.

If the UE supports mixed operation mode and dl-ConfigListMixed is present in systemInformationBlockType22-NB, the UE creates a combined list of DL carriers for random access by appending dl-ConfigListMixed to the dl-ConfigList while maintaining the order among both dl-ConfigList and dl-ConfigListMixed; only the first maxNonAnchorCarriers-NB-r14 DL non-anchor carriers in the concatenated list can be used for random access.

If the field is absent in the entry in nprach-ParametersListEDT in SystemInformationBlockType22-NB, the value of npdcch-CarrierIndex in the corresponding entry of nprach-ParametersList applies, if present. If the field is absent in an entry in nprach-ParametersListFmt2EDT in SystemInformationBlockType23-NB, the value of npdcch-CarrierIndex in the corresponding entry of nprach-ParametersListFmt2 applies, if present. Otherwise, the DL anchor carrier is used.

For TDD: This parameter is absent and the same carrier is used in uplink and downlink.

npdcch-NumRepetitions-RA

Maximum number of repetitions for NPDCCH common search space (CSS) for RAR, Msg3 retransmission and Msg4, see TS 36.213 [23], clause 16.6.

See NOTE.

npdcch-Offset-RA

Fractional period offset of starting subframe for NPDCCH common search space (CSS Type 2), see TS 36.213 [23], clause 16.6.

See NOTE.

npdcch-StartSF-CSS-RA

Starting subframe configuration for NPDCCH common search space (CSS), including RAR, Msg3 retransmission, and Msg4, see TS 36.213 [23], clause 16.6.

See NOTE.

nprach-CP-Length

Cyclic prefix length for NPRACH transmission (TCP), see TS 36.211 [21], clause 10.1.6. Value us66dot7 corresponds to 66.7 microseconds and value us266dot7 corresponds to 266.7 microseconds. If the UE uses a NPRACH resource for preamble format 2, the UE ignores the value signalled in nprach-CP-Length and considers the value to be 800 microseconds.

nprach-NumCBRA-StartSubcarriers

The number of start subcarriers from which a UE can randomly select a start subcarrier as specified in TS 36.321 [6].

If nprach-Config-v1330 is not included in SystemInformationBlockType2-NB, the UE sets the value of nprach-NumCBRA-StartSubcarriers-r13 to the value signalled by nprach-NumSubcarriers-r13 for the corresponding NPRACH resource.

The start subcarrier indices that the UE is allowed to randomly select from, are given by:

nprach-SubcarrierOffset + [0, nprach-NumCBRA-StartSubcarriers – 1].

See NOTE.

nprach-NumSubcarriers

Number of sub-carriers in a NPRACH resource, see TS 36.211 [21], clause 10.1.6. In number of subcarriers.

See NOTE.

nprach-ParametersList, nprach-ParametersListEDT

Configures NPRACH parameters for each NPRACH resource. Up to three PRACH resources can be configured in nprach-ParametersList in a cell. Each NPRACH resource is associated with a different number of NPRACH repetitions.

E-UTRAN includes the same number of entries, and listed in the same order for nprach-ParametersListEDT, as in nprach-ParametersList in SystemInformationBlockType2-NB.

The NPRACH resources in nprach-ParametersListEDT are used to initiate EDT. Each NPRACH resource is associated with a TBS signalled in the corresponding entry of edt-TBS-InfoList.

For TDD: The UE shall use nprach-ParametersListTDD and ignore nprach-ParametersList.

nprach-ParametersListTDD

For TDD: Configure NPRACH parameters for each NPRACH. Up to three NPRACH resources can be configured in a cell. Each NPRACH resource is associated with a different number of NPRACH repetitions.

nprach-ParametersListFmt2, nprach-ParametersListFmt2EDT

Configures NPRACH parameters for each NPRACH resource format 2. Up to three NPRACH resources can be configured on one carrier. Each NPRACH resource is associated with a different number of NPRACH repetitions.

E-UTRAN includes the same number of entries, and listed in the same order, as in nprach-ParametersList in SystemInformationBlockType2-NB.

The NPRACH resources in nprach-ParametersListFmt2EDT are used to initiate EDT. Each NPRACH resource is associated with a TBS signalled in the corresponding entry of edt-TBS-InfoList.

E-UTRAN configures the NPRACH resources format 2 so that they do not overlap in time domain with the NPRACH resources configured in nprach-ParametersList and nprach-ParametersListEDT.

If there is no NPRACH resource in nprach-ParametersListFmt2 (respectively nprach-ParametersListFmt2EDT) on any UL carrier for one NPRACH repetition level, the UE uses the NPRACH resources in nprach-ParametersList (respectively nprach-ParametersListEDT) for this NPRACH repetition level. Otherwise, the UE uses only NPRACH resources in nprach-ParametersListFmt2 (respectively nprach-ParametersListFmt2EDT).

nprach-Periodicity

Periodicity of a NPRACH resource, see TS 36.211 [21], clause10.1.6. Unit in millisecond.

See NOTE.

nprach-PreambleFormat

TDD: TDD preamble format, see TS 36.211 [21]. clause 10.1.6,

Value fmt0 corresponds to preamble format 0, value fmt1 corresponds to preamble format 1 and so on.

nprach-StartTime

Start time of the NPRACH resource in one period, see TS 36.211 [21], clause 10.1.6. Unit in millisecond.

See NOTE.

nprach-SubcarrierOffset

Frequency location of the NPRACH resource, see TS 36.211 [21], clause 10.1.6. In number of subcarriers, offset from sub-carrier 0.

See NOTE.

nprach-SubcarrierMSG3-RangeStart

Fraction for calculating the starting subcarrier index of the range reserved for indication of UE support for multi-tone Msg3 transmission, within the NPRACH resource, see TS 36.211 [21], clause 10.1.6. Multi-tone Msg3 transmission is not supported for {32, 64, 128} repetitions of NPRACH. For at least one of the NPRACH resources with the number of NPRACH repetitions other than {32, 64, 128}, the value of nprach-SubcarrierMSG3-RangeStart should not be 0.

If nprach-SubcarrierMSG3-RangeStart is equal to zero, no start subcarrier index for the single-tone Msg3 NPRACH is allocated and the start subcarrier indexes for the multi-tone Msg3 NPRACH partition are given by nprach-SubcarrierOffset + [0, nprach-NumCBRA-StartSubcarriers – 1].

If nprach-SubcarrierMSG3-RangeStart is equal to oneThird or twoThird, the start subcarrier indexes for the two partitions are given by:

nprach-SubcarrierOffset + [0, floor(nprach-NumCBRA-StartSubcarriers * nprach-SubcarrierMSG3-RangeStart) -1]

for the single-tone Msg3 NPRACH partition;

nprach-SubcarrierOffset + [floor(nprach-NumCBRA-StartSubcarriers * nprach-SubcarrierMSG3-RangeStart), nprach-NumCBRA-StartSubcarriers – 1]

for the multi-tone Msg3 NPRACH partition;

If nprach-SubcarrierMSG3-RangeStart is equal to one, the start subcarrier indexes for the single-tone Msg3 NPRACH are given by nprach-SubcarrierOffset + [0, nprach-NumCBRA-StartSubcarriers – 1] and no start subcarrier index for the multi-tone Msg3 NPRACH partition is allocated.

See NOTE.

numRepetitionsPerPreambleAttempt

Number of NPRACH repetitions per attempt for each NPRACH resource, See TS 36.211 [21], clause 10.1.6. numRepetitionsPerPreambleAttempt-r13 applies to FDD and numRepetitionsPerPreambleAttempt-v1550 applies to TDD.

rsrp-ThresholdsPrachInfoList

The criterion for UEs to select a NPRACH resource. Up to 2 RSRP threshold values can be signalled. The first element corresponds to RSRP threshold 1, the second element corresponds to RSRP threshold 2. See TS 36.321 [6]. If absent, there is only one NPRACH resource.

A UE that supports powerClassNB-14dBm-r14 shall correct the RSRP threshold values before applying them as follows:

RSRP threshold = Signalled RSRP threshold – min{0, (14-min(23, P-Max))} where P-Max: is the value of p-Max field in SystemInformationBlockType1-NB.

NOTE:

– If the field is absent in an entry of nprach-ParametersList in SystemInformationBlockType22-NB, the value of the same field in the corresponding entry of nprach-ParametersList in SystemInformationBlockType2-NB applies.

– If the field is absent in the entry in nprach-ParametersListEDT, the value of the same field in the corresponding entry of nprach-ParametersList on the same UL carrier applies, if present. Otherwise, the value of the same field in the corresponding entry of nprach-ParametersList in SystemInformationBlockType2-NB applies.

– If the field is absent in an entry of nprach-ParametersListTDD in SystemInformationBlockType22-NB, the value of the same field in the corresponding entry of nprach-ParametersListTDD in SystemInformationBlockType2-NB applies. The field is mandatory present in nprach-ParametersListTDD in SystemInformationBlockType2-NB.

– If the field is absent in an entry of nprach-ParametersListFmt2 in SystemInformationBlockType23-NB, the value of the same field, if present, in the corresponding entry of nprach-ParametersListFmt2 in SystemInformationBlockType2-NB applies. Otherwise the value of the same field, if present, in the corresponding entry of the first occurence of nprach-ParametersListFmt2 in the non anchor carrier list applies. Otherwise, the value of the same field in the corresponding entry of nprach-ParametersList in SystemInformationBlockType2-NB applies.

– If the field is absent in an entry of nprach-ParametersListFmt2 in SystemInformationBlockType2-NB, the value of the same field in the corresponding entry of nprach-ParametersList in SystemInformationBlockType2-NB applies.

– If the field is absent in an entry of nprach-ParametersListFmt2EDT in SystemInformationBlockType23-NB, the value of the same field, if present, in the corresponding entry of nprach-ParametersListFmt2 on the same UL carrier applies. Otherwise, the value of the same field, if present, in the corresponding entry of nprach-ParametersListFmt2 in SystemInformationBlockType2-NB applies. Otherwise the value of the same field, if present, in the corresponding entry of the first occurence of nprach-ParametersListFmt2 in the non anchor carrier list applies. Otherwise, the value of the same field in the corresponding entry of nprach-ParametersList in SystemInformationBlockType2-NB applies.

– If the field is absent in an entry of nprach-ParametersListFmt2EDT in SystemInformationBlockType2-NB, the value of the same field, if present, in the corresponding entry of nprach-ParametersListFmt2 in SystemInformationBlockType2-NB applies. Otherwise the value of the same field in the corresponding entry of nprach-ParametersList in SystemInformationBlockType2-NB applies.

Conditional presence

Explanation

EDT1

The field is mandatory present if cp-EDT or up-EDT in SystemInformationBlockType2-NB is present; otherwise the field is not present and the UE shall delete any existing value for this field.

EDT2

The field is optionally present, Need OR, if edt-Parameters is present; otherwise the field is not present and the UE shall delete any existing value for this field.

TDD

This field is mandatory present for TDD; otherwise the field is not present and the UE shall delete any existing value for this field.

NPUSCH-Config-NB

The IE NPUSCH-ConfigCommon-NB is used to specify the common NPUSCH configuration. The IE NPUSCH-ConfigDedicated-NB is used to specify the UE specific NPUSCH configuration.

NPUSCH-Config-NB information element

— ASN1START

NPUSCH-ConfigCommon-NB-r13 ::= SEQUENCE {

ack-NACK-NumRepetitions-Msg4-r13 SEQUENCE (SIZE(1..maxNPRACH-Resources-NB-r13)) OF

ACK-NACK-NumRepetitions-NB-r13,

srs-SubframeConfig-r13 ENUMERATED {

sc0, sc1, sc2, sc3, sc4, sc5, sc6, sc7,

sc8, sc9, sc10, sc11, sc12, sc13, sc14, sc15

} OPTIONAL, — Need OR

dmrs-Config-r13 SEQUENCE {

threeTone-BaseSequence-r13 INTEGER (0..12) OPTIONAL, — Need OP

threeTone-CyclicShift-r13 INTEGER (0..2),

sixTone-BaseSequence-r13 INTEGER (0..14) OPTIONAL, — Need OP

sixTone-CyclicShift-r13 INTEGER (0..3),

twelveTone-BaseSequence-r13 INTEGER (0..30) OPTIONAL — Need OP

} OPTIONAL, — Need OR

ul-ReferenceSignalsNPUSCH-r13 UL-ReferenceSignalsNPUSCH-NB-r13

}

UL-ReferenceSignalsNPUSCH-NB-r13 ::= SEQUENCE {

groupHoppingEnabled-r13 BOOLEAN,

groupAssignmentNPUSCH-r13 INTEGER (0..29)

}

NPUSCH-ConfigDedicated-NB-r13 ::= SEQUENCE {

ack-NACK-NumRepetitions-r13 ACK-NACK-NumRepetitions-NB-r13 OPTIONAL, — Need ON

npusch-AllSymbols-r13 BOOLEAN OPTIONAL, — Cond SRS

groupHoppingDisabled-r13 ENUMERATED {true} OPTIONAL — Need OR

}

ACK-NACK-NumRepetitions-NB-r13 ::= ENUMERATED {r1, r2, r4, r8, r16, r32, r64, r128}

— ASN1STOP

NPUSCH-Config-NB field descriptions

ack-NACK-NumRepetitions

Number of repetitions for the ACK NACK resource unit carrying HARQ response to NPDSCH, see TS 36.213 [23], clause 16.4.2. If this field is absent and no value was configured via dedicated signalling, the value used for reception of Msg4 is used.

ack-NACK-NumRepetitions-Msg4

Number of repetitions for ACK/NACK HARQ response to NPDSCH containing Msg4 per NPRACH resource, see TS 36.213 [23], clause 16.4.2.

groupAssignmentNPUSCH

See TS 36.211 [21], clause 10.1.4.1.3.

groupHoppingDisabled

See TS 36.211 [21], clause 10.1.4.1.3.

groupHoppingEnabled

See TS 36.211 [21], clause 10.1.4.1.3.

npusch-AllSymbols

If set to TRUE, the UE shall use all NB-IoT symbols for NPUSCH transmission. If set to FALSE, the UE punctures the NPUSCH transmissions in the symbols that collides with SRS. If the field is not present, the UE uses all NB-IoT symbols for NPUSCH transmission. See TS 36.211 [21], clause 10.1.3.6.

sixTone-BaseSequence

The base sequence of DMRS sequence in a cell for 6 tones transmission; see TS 36.211 [21], clause 10.1.4.1.2. If absent, it is given by NB-IoT CellID mod 14. Value 14 is not used.

sixTone-CyclicShift

Define 4 cyclic shifts for the 6-tone case, see TS 36.211 [21], clause 10.1.4.1.2.

srs-SubframeConfig

SRS SubframeConfiguration. See TS 36.211 [21], table 5.5.3.3-1. Value sc0 corresponds to value 0, sc1 to value 1 and so on.

threeTone-BaseSequence

The base sequence of DMRS sequence in a cell for 3 tones transmission; see TS 36.211 [21], clause 10.1.4.1.2. If absent, it is given by NB-IoT CellID mod 12. Value 12 is not used.

threeTone-CyclicShift

Define 3 cyclic shifts for the 3-tone case, see TS 36.211 [21], clause 10.1.4.1.2.

twelveTone-BaseSequence

The base sequence of DMRS sequence in a cell for 12 tones transmission; see TS 36.211 [21], clause 10.1.4.1.2. If absent, it is given by NB-IoT CellID mod 30. Value 30 is not used.

ul-ReferenceSignalsNPUSCH

Used to specify parameters needed for the transmission on NPUSCH.

Conditional presence

Explanation

SRS

This field is optionally present, need OP, if srs-SubframeConfig is broadcasted.

Otherwise, the IE is not present.

PDCP-Config-NB

The IE PDCP-Config-NB is used to set the configurable PDCP parameters for data radio bearers.

PDCP-Config-NB information element

— ASN1START

PDCP-Config-NB-r13 ::= SEQUENCE {

discardTimer-r13 ENUMERATED {

ms5120, ms10240, ms20480, ms40960,

ms81920, infinity, spare2, spare1

} OPTIONAL, — Cond Setup

headerCompression-r13 CHOICE {

notUsed NULL,

rohc SEQUENCE {

maxCID-r13 INTEGER (1..16383) DEFAULT 15,

profiles-r13 SEQUENCE {

profile0x0002 BOOLEAN,

profile0x0003 BOOLEAN,

profile0x0004 BOOLEAN,

profile0x0006 BOOLEAN,

profile0x0102 BOOLEAN,

profile0x0103 BOOLEAN,

profile0x0104 BOOLEAN

},

}

},

}

— ASN1STOP

PDCP-Config-NB field descriptions

discardTimer

Indicates the discard timer value specified in TS 36.323 [8]. Value in milliseconds. Value ms5120 means 5120 ms, ms10240 means 10240 ms and so on.

headerCompression

E-UTRAN does not reconfigure header compression except optionally upon RRC Connection Resumption.

maxCID

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

profiles

The profiles used by both compressor and decompressor in both UE and E-UTRAN. The field indicates which of the ROHC profiles specified in TS 36.323 [8] are supported, i.e. value true indicates that the profile is supported. Profile 0x0000 shall always be supported when the use of ROHC is configured. If support of two ROHC profile identifiers with the same 8 LSB’s is signalled, only the profile corresponding to the highest value shall be applied.

Conditional presence

Explanation

Setup

The field is mandatory present in case of radio bearer setup. Otherwise the field is optionally present, need ON.

PhysicalConfigDedicated-NB

The IE PhysicalConfigDedicated-NB is used to specify the UE specific physical channel configuration.

PhysicalConfigDedicated-NB information element

— ASN1START

PhysicalConfigDedicated-NB-r13 ::= SEQUENCE {

carrierConfigDedicated-r13 CarrierConfigDedicated-NB-r13 OPTIONAL, — Need ON

npdcch-ConfigDedicated-r13 NPDCCH-ConfigDedicated-NB-r13 OPTIONAL, — Need ON

npusch-ConfigDedicated-r13 NPUSCH-ConfigDedicated-NB-r13 OPTIONAL, — Need ON

uplinkPowerControlDedicated-r13 UplinkPowerControlDedicated-NB-r13 OPTIONAL, — Need ON

…,

[[ twoHARQ-ProcessesConfig-r14 ENUMERATED {true} OPTIONAL — Need OR

]],

[[ interferenceRandomisationConfig-r14 ENUMERATED {true} OPTIONAL — Need OR

]],

[[ npdcch-ConfigDedicated-v1530 NPDCCH-ConfigDedicated-NB-v1530 OPTIONAL — Cond TDD

]],

[[ additionalTxSIB1-Config-v1540 ENUMERATED {true} OPTIONAL — Cond additionalSIB1

]]

}

— ASN1STOP

PhysicalConfigDedicated-NB field descriptions

carrierConfigDedicated

Anchor/ non-anchor carrier used for all unicast transmissions.

interferenceRandomisationConfig

For FDD: Interference randomisation enabled in connected mode, except for random access procedure in connected mode, see TS 36.211 [21]. For random access in connected mode interference randomisation on non-anchor is used and is not used on anchor carrier, see TS 36.211 [21].

For TDD: the parameter is not present.

npdcch-ConfigDedicated

NPDCCH configuration.

npusch-ConfigDedicated

UL unicast configuration.

twoHARQ-ProcessesConfig

Activation of two HARQ processes, see TS 36.212 [22] and TS 36.213 [23].

uplink-PowerControlDedicated

UL power control parameter.

additionalTxSIB1-Config

Indicates if subframe #3 not containing additional SIB1 transmission is a NB-IoT DL subframe, as specified in TS 36.213 [23], clause 16.4.

Conditional presence

Explanation

TDD

The field is optionally present, Need OR, for TDD; otherwise the field is not present and the UE shall delete any existing value for this field.

additionalSIB1

This field is optionally present, Need OR, if additionalTransmissionSIB1 is set to TRUE in MasterInformationBlock-NB; otherwise it is not present.

RACH-ConfigCommon-NB

The IE RACH-ConfigCommon-NB is used to specify the generic random access parameters.

RACH-ConfigCommon-NB information element

— ASN1START

RACH-ConfigCommon-NB-r13 ::= SEQUENCE {

preambleTransMax-CE-r13 PreambleTransMax,

powerRampingParameters-r13 PowerRampingParameters,

rach-InfoList-r13 RACH-InfoList-NB-r13,

connEstFailOffset-r13 INTEGER (0..15) OPTIONAL, — Need OP

…,

[[ powerRampingParameters-v1450 PowerRampingParameters-NB-v1450 OPTIONAL — Need OR

]],

[[ rach-InfoList-v1530 RACH-InfoList-NB-v1530 OPTIONAL — Cond EDT

]]

}

RACH-InfoList-NB-r13 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF RACH-Info-NB-r13

RACH-InfoList-NB-v1530 ::= SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF RACH-Info-NB-v1530

RACH-Info-NB-r13 ::= SEQUENCE {

ra-ResponseWindowSize-r13 ENUMERATED {

pp2, pp3, pp4, pp5, pp6, pp7, pp8, pp10},

mac-ContentionResolutionTimer-r13 ENUMERATED {

pp1, pp2, pp3, pp4, pp8, pp16, pp32, pp64}

}

RACH-Info-NB-v1530 ::= SEQUENCE {

mac-ContentionResolutionTimer-r15 ENUMERATED {

pp1, pp2, pp3, pp4, pp8, pp16, pp32, pp64}

}

PowerRampingParameters-NB-v1450 ::= SEQUENCE {

preambleInitialReceivedTargetPower-v1450 ENUMERATED {

dBm-130, dBm-128, dBm-126, dBm-124, dBm-122,

dBm-88, dBm-86, dBm-84,dBm-82, dBm-80}

OPTIONAL, — Need OR

powerRampingParametersCE1-r14 SEQUENCE {

powerRampingStepCE1-r14 ENUMERATED {dB0, dB2, dB4, dB6},

preambleInitialReceivedTargetPowerCE1-r14 ENUMERATED {

dBm-130, dBm-128, dBm-126, dBm-124, dBm-122,

dBm-120, dBm-118, dBm-116, dBm-114, dBm-112,

dBm-110, dBm-108, dBm-106, dBm-104, dBm-102,

dBm-100, dBm-98, dBm-96, dBm-94, dBm-92,

dBm-90, dBm-88, dBm-86, dBm-84, dBm-82, dBm-80}

} OPTIONAL — Need OR

}

— ASN1STOP

RACH-ConfigCommon-NB field descriptions

connEstFailOffset

Parameter "Qoffsettemp" in TS 36.304 [4]. If the field is not present the value of infinity shall be used for "Qoffsettemp".

mac-ContentionResolutionTimer

Timer for contention resolution in TS 36.321 [6]. Value in PDCCH periods. Value pp1 corresponds to 1 PDCCH period, pp2 corresponds to 2 PDCCH periods and so on. mac-ContentionResolutionTimer-r15 is only applicable for EDT. UE performing EDT shall use mac-ContentionResolutionTimer-r15, if present.

For FDD: The value considered by the UE is: mac-ContentionResolutionTimer = Min (signaled value x PDCCH period, 10.24s).

For TDD: The value considered by the UE is: mac-ContentionResolutionTimer = Min (signaled value x PDCCH period, 20.48s).

powerRampingParameters, powerRampingParametersCE1

Power ramping step and preamble initial received target power – same as TS 36.213 [23] and TS 36.321 [6].

For FDD, if the UE does not support enhanced random access power control and more than one repetition level is configured in the cell, then the UE transmits NPRACH with max power except for the lowest repetition level. Otherwise, the UE uses NPRACH power ramping.

For FDD, if the UE supports enhanced random access power control and powerRampingParameters-v1450 is signalled, or for TDD, the UE uses NPRACH power ramping across repetition levels as specified in TS 36.321 [6]. If preambleInitialReceivedTargetPower-v1450 is present, the UE shall use preambleInitialReceivedTargetPower-v1450 instead of preambleInitialReceivedTargetPower (i.e. without suffix). If powerRampingParametersCE1 is present, the UE shall use powerRampingParametersCE1 instead of powerRampingParameters for NPRACH power ramping in the second repetition level.

preambleTransMax-CE

Maximum number of preamble transmission in TS 36.321 [6]. Value is an integer.

ra-ResponseWindowSize

Duration of the RA response window in TS 36.321 [6]. Value in PDCCH periods. Value pp2 corresponds to 2 PDDCH periods, pp3 corresponds to 3 PDCCH periods and so on.

For FDD: The value considered by the UE is: ra-ResponseWindowSize = Min (signaled value x PDCCH period, 10.24s).

For TDD: The value considered by the UE is: ra-ResponseWindowSize = Min (signaled value x PDCCH period, 20.48s).

Conditional presence

Explanation

EDT

The field is optionally present, Need OR, if edt-Parameters is present; otherwise the field is not present and the UE shall delete any existing value for this field.

RadioResourceConfigCommonSIB-NB

The IE RadioResourceConfigCommonSIB-NB is used to specify common radio resource configurations in the system information, e.g., the random access parameters and the static physical layer parameters.

RadioResourceConfigCommonSIB-NB information element

— ASN1START

RadioResourceConfigCommonSIB-NB-r13 ::= SEQUENCE {

rach-ConfigCommon-r13 RACH-ConfigCommon-NB-r13,

bcch-Config-r13 BCCH-Config-NB-r13,

pcch-Config-r13 PCCH-Config-NB-r13,

nprach-Config-r13 NPRACH-ConfigSIB-NB-r13,

npdsch-ConfigCommon-r13 NPDSCH-ConfigCommon-NB-r13,

npusch-ConfigCommon-r13 NPUSCH-ConfigCommon-NB-r13,

dl-Gap-r13 DL-GapConfig-NB-r13 OPTIONAL, — Need OP

uplinkPowerControlCommon-r13 UplinkPowerControlCommon-NB-r13,

…,

[[ nprach-Config-v1330 NPRACH-ConfigSIB-NB-v1330 OPTIONAL — Need OR

]],

[[ nprach-Config-v1450 NPRACH-ConfigSIB-NB-v1450 OPTIONAL — Cond EnhPowerControl

]],

[[ nprach-Config-v1530 NPRACH-ConfigSIB-NB-v1530 OPTIONAL, — Need OR

dl-Gap-v1530 DL-GapConfig-NB-v1530 OPTIONAL, — Cond TDD

wus-Config-r15 WUS-Config-NB-r15 OPTIONAL — Need OR

]],

[[ nprach-Config-v1550 NPRACH-ConfigSIB-NB-v1550 OPTIONAL — Cond TDD1

]]

}

BCCH-Config-NB-r13 ::= SEQUENCE {

modificationPeriodCoeff-r13 ENUMERATED {n16, n32, n64, n128}

}

PCCH-Config-NB-r13 ::= SEQUENCE {

defaultPagingCycle-r13 ENUMERATED {rf128, rf256, rf512, rf1024},

nB-r13 ENUMERATED {

fourT, twoT, oneT, halfT, quarterT, one8thT,

one16thT, one32ndT, one64thT,

one128thT, one256thT, one512thT, one1024thT,

spare3, spare2, spare1},

npdcch-NumRepetitionPaging-r13 ENUMERATED {

r1, r2, r4, r8, r16, r32, r64, r128,

r256, r512, r1024, r2048,

spare4, spare3, spare2, spare1}

}

— ASN1STOP

RadioResourceConfigCommonSIB-NB field descriptions

defaultPagingCycle

Default paging cycle, used to derive ‘T’ in TS 36.304 [4]. Value rf128 corresponds to 128 radio frames, rf256 corresponds to 256 radio frames and so on.

dl-Gap

Downlink transmission gap configuration for the anchor carrier. See TS 36.211 [21], clause 10.2.3.4. If the field is absent, there is no gap.

modificationPeriodCoeff

Actual modification period, expressed in number of radio frames= modificationPeriodCoeff * defaultPagingCycle. n16 corresponds to value 16, n32 corresponds to value 32, and so on. The BCCH modification period should be larger or equal to 40.96s.

nB

Parameter: nB is used as one of parameters to derive the Paging Frame and Paging Occasion according to TS 36.304 [4]. Value in multiples of ‘T’ as defined in TS 36.304 [4]. A value of fourT corresponds to 4 * T, a value of twoT corresponds to 2 * T and so on.

npdcch-NumRepetitionPaging

Maximum number of repetitions for NPDCCH common search space (CSS) for paging, see TS 36.213 [23], clause 16.6.

wus-Config

For FDD: WUS Configuration.

Conditional presence

Explanation

EnhPowerControl

This field is optional present, Need OR, if PowerRampingParameters-NB-v1450 is included in SIB2-NB. Otherwise the field is not present.

TDD

The field is optionally present, Need OR, for TDD; otherwise the field is not present and the UE shall delete any existing value for this field.

TDD1

The field is mandatory present for TDD; otherwise the field is not present and the UE shall delete any existing value for this field.

RadioResourceConfigDedicated-NB

The IE RadioResourceConfigDedicated-NB is used to setup/modify/release RBs, to modify the MAC main configuration, and to modify dedicated physical configuration.

RadioResourceConfigDedicated-NB information element

— ASN1START

RadioResourceConfigDedicated-NB-r13 ::= SEQUENCE {

srb-ToAddModList-r13 SRB-ToAddModList-NB-r13 OPTIONAL, — Need ON

drb-ToAddModList-r13 DRB-ToAddModList-NB-r13 OPTIONAL, — Need ON

drb-ToReleaseList-r13 DRB-ToReleaseList-NB-r13 OPTIONAL, — Need ON

mac-MainConfig-r13 CHOICE {

explicitValue-r13 MAC-MainConfig-NB-r13,

defaultValue-r13 NULL

} OPTIONAL, — Need ON

physicalConfigDedicated-r13 PhysicalConfigDedicated-NB-r13 OPTIONAL, — Need ON

rlf-TimersAndConstants-r13 RLF-TimersAndConstants-NB-r13 OPTIONAL, — Need ON

…,

[[ schedulingRequestConfig-r15 SchedulingRequestConfig-NB-r15 OPTIONAL — Need ON

]]

}

SRB-ToAddModList-NB-r13 ::= SEQUENCE (SIZE (1)) OF SRB-ToAddMod-NB-r13

SRB-ToAddMod-NB-r13 ::= SEQUENCE {

rlc-Config-r13 CHOICE {

explicitValue RLC-Config-NB-r13,

defaultValue NULL

} OPTIONAL, — Cond Setup

logicalChannelConfig-r13 CHOICE {

explicitValue LogicalChannelConfig-NB-r13,

defaultValue NULL

} OPTIONAL, — Cond Setup

…,

[[ rlc-Config-v1430 RLC-Config-NB-v1430 OPTIONAL — Need ON

]]

}

DRB-ToAddModList-NB-r13 ::= SEQUENCE (SIZE (1..maxDRB-NB-r13)) OF DRB-ToAddMod-NB-r13

DRB-ToAddMod-NB-r13 ::= SEQUENCE {

eps-BearerIdentity-r13 INTEGER (0..15) OPTIONAL, — Cond DRB-Setup

drb-Identity-r13 DRB-Identity,

pdcp-Config-r13 PDCP-Config-NB-r13 OPTIONAL, — Cond Setup

rlc-Config-r13 RLC-Config-NB-r13 OPTIONAL, — Cond Setup

logicalChannelIdentity-r13 INTEGER (3..10) OPTIONAL, — Cond DRB-Setup

logicalChannelConfig-r13 LogicalChannelConfig-NB-r13 OPTIONAL, — Cond Setup

…,

[[ rlc-Config-v1430 RLC-Config-NB-v1430 OPTIONAL — Need ON

]]

}

DRB-ToReleaseList-NB-r13 ::= SEQUENCE (SIZE (1..maxDRB-NB-r13)) OF DRB-Identity

— ASN1STOP

RadioResourceConfigDedicated-NB field descriptions

logicalChannelConfig

For SRB a choice is used to indicate whether the logical channel configuration is signalled explicitly or set to the default logical channel configuration for SRB1 as specified in 9.2.1.1.

logicalChannelIdentity

The logical channel identity for both UL and DL for a DRB. Value 3 is not used.

mac-MainConfig

The default MAC MAIN configuration is specified in 9.2.2.

physicalConfigDedicated

The default dedicated physical configuration is specified in 9.2.4.

rlc-Config

For SRBs a choice is used to indicate whether the RLC configuration is signalled explicitly or set to the values defined in the default RLC configuration for SRB1 in 9.2.1.1. RLC AM is the only applicable RLC mode for SRB1 and SRB1bis.

schedulingRequestConfig

For FDD: Scheduling request configuration.

Conditional presence

Explanation

DRB-Setup

The field is mandatory present if the corresponding DRB is being set up; otherwise it is not present.

Setup

The field is mandatory present if the corresponding SRB/DRB is being setup; otherwise the field is optionally present, need ON.

RLC-Config-NB

The IE RLC-Config-NB is used to specify the RLC configuration of SRBs and DRBs.

RLC-Config-NB information element

— ASN1START

RLC-Config-NB-r13 ::= CHOICE {

am SEQUENCE {

ul-AM-RLC-r13 UL-AM-RLC-NB-r13,

dl-AM-RLC-r13 DL-AM-RLC-NB-r13

},

…,

um-Bi-Directional-r15 NULL,

um-Uni-Directional-UL-r15 NULL,

um-Uni-Directional-DL-r15 NULL

}

RLC-Config-NB-v1430 ::= SEQUENCE {

t-Reordering-r14 T-Reordering OPTIONAL — Cond twoHARQ

}

UL-AM-RLC-NB-r13 ::= SEQUENCE {

t-PollRetransmit-r13 T-PollRetransmit-NB-r13,

maxRetxThreshold-r13 ENUMERATED {t1, t2, t3, t4, t6, t8, t16, t32}

}

DL-AM-RLC-NB-r13 ::= SEQUENCE {

enableStatusReportSN-Gap-r13 ENUMERATED {true} OPTIONAL

}

T-PollRetransmit-NB-r13 ::= ENUMERATED {

ms250, ms500, ms1000, ms2000, ms3000, ms4000,

ms6000, ms10000, ms15000, ms25000, ms40000, ms60000,

ms90000, ms120000, ms180000, ms300000-v1530}

— ASN1STOP

RLC-Config-NB field descriptions

enableStatusReportSN-Gap

Indicates that status reporting due to detection of reception failure is enabled, as specified in TS 36.322 [7].

maxRetxThreshold

Parameter for RLC AM in TS 36.322 [7]. Value t1 corresponds to 1 retransmission, t2 to 2 retransmissions and so on.

t-PollRetransmit

Timer for RLC AM in TS 36.322 [7], in milliseconds. Value msX means X ms, msY means Y ms and so on.

E-UTRAN may configure the value msX-v1530 (with suffix) only in TDD mode.

t-Reordering

Timer for reordering in TS 36.322 [7], in milliseconds.

Conditional presence

Explanation

twoHARQ

The field is mandatory present if twoHARQ-ProcessesConfig is set to TRUE. Otherwise, the field is not present and, if previously configured, the timer is released.

RLF-TimersAndConstants-NB

The IE RLF-TimersAndConstants-NB contains UE specific timers and constants applicable for UEs in RRC_CONNECTED.

RLF-TimersAndConstants-NB information element

— ASN1START

RLF-TimersAndConstants-NB-r13 ::= CHOICE {

release NULL,

setup SEQUENCE {

t301-r13 ENUMERATED {

ms2500, ms4000, ms6000, ms10000,

ms15000, ms25000, ms40000, ms60000},

t310-r13 ENUMERATED {

ms0, ms200, ms500, ms1000, ms2000, ms4000, ms8000},

n310-r13 ENUMERATED {

n1, n2, n3, n4, n6, n8, n10, n20},

t311-r13 ENUMERATED {

ms1000, ms3000, ms5000, ms10000, ms15000,

ms20000, ms30000},

n311-r13 ENUMERATED {

n1, n2, n3, n4, n5, n6, n8, n10},

…,

[[ t311-v1350 ENUMERATED {

ms40000, ms60000, ms90000, ms120000}

OPTIONAL — Need OR

]],

[[ t301-v1530 ENUMERATED {

ms80000, ms100000, ms120000}

OPTIONAL, — Cond TDD

t311-v1530 ENUMERATED {

ms160000, ms200000}

OPTIONAL — Cond TDD

]]

}

}

— ASN1STOP

RLF-TimersAndConstants-NB field descriptions

n3xy

Constants are described in clause 7.4. n1 corresponds with 1, n2 corresponds with 2 and so on.

t3xy

Timers are described in clause 7.3. Value ms0 corresponds with 0 ms, ms200 corresponds with 200 ms and so on. The UE shall use the extended values t311-v1350, t301-v1530 and t311-v1530, if present, and ignore the value signaled by t311-r13, t301-r13 and t311-r13 respectively.

Conditional presence

Explanation

TDD

The field is optionally present, Need OR, in TDD mode. Otherwise, the field is not present.

SchedulingRequestConfig-NB

The IE SchedulingRequestConfig-NB is used to specify the Scheduling Request related parameters.

SchedulingRequestConfig-NB information element

— ASN1START

SchedulingRequestConfig-NB-r15 ::= SEQUENCE {

sr-WithHARQ-ACK-Config-r15 ENUMERATED {true} OPTIONAL,

sr-WithoutHARQ-ACK-Config-r15 SR-WithoutHARQ-ACK-Config-NB-r15 OPTIONAL, — Need ON

sr-SPS-BSR-Config-r15 SR-SPS-BSR-Config-NB-r15 OPTIONAL, — Need ON

}

SR-WithoutHARQ-ACK-Config-NB-r15 ::= CHOICE {

release NULL,

setup SEQUENCE {

sr-ProhibitTimer-r15 INTEGER (0..7) OPTIONAL, — Need ON

sr-NPRACH-Resource-r15 SR-NPRACH-Resource-NB-r15 OPTIONAL — Need ON

}

}

SR-NPRACH-Resource-NB-r15 ::= SEQUENCE {

nprach-CarrierIndex-r15 INTEGER (0..maxNonAnchorCarriers-NB-r14),

nprach-ResourceIndex-r15 INTEGER (1..maxNPRACH-Resources-NB-r13),

nprach-SubCarrierIndex-r15 CHOICE {

nprach-Fmt0Fmt1-r15 INTEGER (0..47),

nprach-Fmt2-r15 INTEGER (0..143)

},

p0-SR-r15 INTEGER (-126..24),

alpha-r15 ENUMERATED {al0, al04, al05, al06, al07, al08, al09, al1}}

SR-SPS-BSR-Config-NB-r15 ::= CHOICE {

release NULL,

setup SEQUENCE {

semiPersistSchedC-RNTI-r15 C-RNTI,

semiPersistSchedIntervalUL-r15 ENUMERATED {sf128, sf256, sf512, sf1024,

sf1280, sf2048, sf2560, sf5120}

}

}

— ASN1STOP

SchedulingRequestConfig-NB field descriptions

alpha

Parameter: αc. Fractional power control parameter for SR without HARQ-ACK. See TS 36.213 [23], clause 16.2.1.2.1, where value al0 corresponds to 0, value al04 corresponds to 0.4, value al05 to 0.5, value al06 to 0.6, value al07 to 0.7, value al08 to 0.8, value al09 to 0.9 and value al1 corresponds to 1.

nprach-CarrierIndex

Index of the carrier in the list of UL non anchor carriers in SystemInformationBlockType22-NB. The first entry in the list has index ‘1’, the second entry has index ‘2’ and so on. Value ‘0’ indicates the anchor carrier.

nprach-ResourceIndex

Index of the NPRACH resource in the list of NPRACH resources in NPRACH-ParametersList or NPRACH-ParametersList-Fmt2 for the UL carrier indicated by nprach-CarrierIndex. The first entry in the list has index ‘1’, the second entry has index ‘2’ and so on.

E-UTRAN configures a NPRACH resource in NPRACH-ParametersList-Fmt2 only to UEs that have reported support of NPRACH resource Format2.

nprach-SubCarrierIndex

Index of the subcarrier in the NPRACH resource in NPRACH-ParametersList or or NPRACH-ParametersList-Fmt2 for the indicated UL carrier.

E-UTRAN does not configure nprach-SubcarrierIndex to a smaller value than nprach-SubcarrierOffset + nprach-NumCBRA-StartSubcarriers for the indicated NPRACH resource.

p0-SR

Parameter:. Target power for SR without HARQ-ACK. See TS 36.213 [23], clause 16.2.1.2.1, unit dBm.

semiPersistSchedC-RNTI

Semi-persistent Scheduling C-RNTI, see TS 36.321 [6].

semiPersistSchedIntervalUL

Semi-persistent scheduling interval in uplink, see TS 36.321 [6]. Value in number of sub-frames. Value sf128 corresponds to 128 sub-frames, value sf256 corresponds to 256 sub-frames and so on.

sr-SPS-BSR-Config

Activation of SR with SPS BSR, see TS 36.321 [6].

E-UTRAN cannot configure sr-SPS-BSR together with sr-WithoutHARQ-ACK-Config.

sr-NPRACH-Resource

NPRACH resource for physical layer SR without HARQ-ACK, see TS 36.211 [21] and TS 36.213 [23].

sr-ProhibitTimer

Timer for SR transmission on the NPRACH resource for SR in TS 36.321 [6]. Value in number of SR period, where the SR period is equal to the field nprach-Periodicity of the NPRACH resource. Value 0 means that behaviour as specified in 7.3.2 applies. Value 1 corresponds to one SR period, Value 2 corresponds to 2*SR period and so on.

sr-WithHARQ-ACK-Config

Activation of physical layer SR with HARQ ACK, see TS 36.213 [23].

sr-WithoutHARQ-ACK-Config

Activation of physical layer SR without HARQ ACK, see TS 36.211 [21] and TS 36.213 [23].

E-UTRAN cannot configure sr-WithoutHARQ-ACK-Config together with sr-SPS-BSR.

– TDD-Config-NB

The IE TDD-Config-NB is used to specify the TDD specific physical channel configuration.

TDD-Config information element

— ASN1START

TDD-Config-NB-r15 ::= SEQUENCE {

subframeAssignment-r15 ENUMERATED {

sa1, sa2, sa3, sa4, sa5},

specialSubframePatterns-r15 ENUMERATED {

ssp0, ssp1, ssp2, ssp3, ssp4, ssp5, ssp6, ssp7,

ssp8, ssp9, ssp10, ssp10-CRS-LessDwPTS}

}

— ASN1STOP

TDD-Config field descriptions

specialSubframePatterns

Indicates Configuration as in TS 36.211 [21], table 4.2-1 where ssp0 points to Configuration 0, ssp1 to Configuration 1 etc. Value ssp10-CRS-LessDwPTS corresponds to ssp10 without CRS transmission on the 5th symbol of DwPTS.

subframeAssignment

Indicates DL/UL subframe configuration where sa1 points to Configuration1, sa2 to Configuration 2 and so on, as specified in TS 36.211 [21], table 4.2-2.

E-UTRAN configures the same value for serving cells residing on same frequency band.

– TDD-UL-DL-AlignmentOffset-NB

The IE TDD-UL-DL-AlignmentOffset-NB is used to specify the offset between the UL carrier frequency center with respect to DL carrier frequency center. This information should be used to calculate the Mul value, see TS 36.101 [42].

TDD-UL-DL-AlignmentOffset-NB information element

— ASN1START

TDD-UL-DL-AlignmentOffset-NB-r15 ::= ENUMERATED { khz-7dot5, khz0, khz7dot5}

— ASN1STOP

UplinkPowerControl-NB

The IE UplinkPowerControlCommon-NB and IE UplinkPowerControlDedicated-NB are used to specify parameters for uplink power control in the system information and in the dedicated signalling, respectively.

UplinkPowerControl-NB information elements

— ASN1START

UplinkPowerControlCommon-NB-r13 ::= SEQUENCE {

p0-NominalNPUSCH-r13 INTEGER (-126..24),

alpha-r13 ENUMERATED {al0, al04, al05, al06, al07, al08, al09, al1},

deltaPreambleMsg3-r13 INTEGER (-1..6)

}

UplinkPowerControlDedicated-NB-r13 ::= SEQUENCE {

p0-UE-NPUSCH-r13 INTEGER (-8..7)

}

— ASN1STOP

UplinkPowerControl-NB field descriptions

alpha

Parameter: αc(1). See TS 36.213 [23], clause 16.2.1.1, where al0 corresponds to 0, al04 corresponds to value 0.4, al05 to 0.5, al06 to 0.6, al07 to 0.7, al08 to 0.8, al09 to 0.9 and al1 corresponds to 1.

deltaPreambleMsg3

Parameter: . See TS 36.213 [23], clause 16.2.1.1. Actual value = IE value * 2 [dB].

p0-NominalNPUSCH

Parameter: . See TS 36.213 [23], clause 16.2.1.1, unit dBm.

p0-UE-NPUSCH

Parameter: . See TS 36.213 [23], clause 16.2.1.1, unit dB.

– WUS-Config-NB

The IE WUS-Config-NB is used to specify the WUS configuration. For UEs supporting WUS, E-UTRAN uses WUS to indicate that the UE shall attempt to receive paging in that cell, see TS 36.304 [4].

WUS-Config-NB information element

— ASN1START

WUS-Config-NB-r15 ::= SEQUENCE {

maxDurationFactor-r15 WUS-MaxDurationFactor-NB-r15,

numPOs-r15 ENUMERATED {n1, n2, n4} DEFAULT n1,

numDRX-CyclesRelaxed-r15 ENUMERATED {n1, n2, n4, n8},

timeOffsetDRX-r15 ENUMERATED {ms40, ms80, ms160, ms240},

timeOffset-eDRX-Short-r15 ENUMERATED {ms40, ms80, ms160, ms240},

timeOffset-eDRX-Long-r15 ENUMERATED {ms1000, ms2000} OPTIONAL, — Need OP

}

WUS-ConfigPerCarrier-NB-r15 ::= SEQUENCE {

maxDurationFactor-r15 WUS-MaxDurationFactor-NB-r15

}

WUS-MaxDurationFactor-NB-r15 ::= ENUMERATED {one128th, one64th, one32th, one16th,

oneEighth, oneQuarter, oneHalf}

— ASN1STOP

WUS-Config-NB field descriptions

maxDurationFactor

Maximum WUS duration, expressed as a ratio of Rmax for Type 1-CSS. Value one128th means Rmax * 1/128, value one64th means Rmax * 1/64 and so on.

The value in TS 36.213 [23] considered by the UE is : maxDuration = Max (signalled value * Rmax, 1) where Rmax is the value of npdcch-NumRepetitionPaging for the carrier.

numDRX-CyclesRelaxed

Maximum number of consecutive DRX cycles during which the UE may use WUS for synchronisation and skip serving cell measurements, see TS 36.133 [16]. Value n1 corresponds to 1 DRX cycle, value n2 corresponds to 2 DRX cycles and so on.

numPOs

Number of consecutive Paging Occasions (PO) mapped to one Wake Up Signal (WUS), applicable to UEs configured to use extended DRX, see TS 36.304 [4]. Value n1 corresponds to 1 PO and value n2 corresponds to 2 POs and so on.

timeOffsetDRX

When DRX is used, non-zero gap from the end of the configured maximum WUS duration to the associated PO, see TS 36.304 [4], clause 7.4 and TS 36.211 [21]. In milliseconds. Value ms40 corresponds to 40ms, value ms80 corresponds to 80 ms and so on.

timeOffset-eDRX-Short

When eDRX is used, the short non-zero gap from the end of the configured maximum WUS duration to the associated PO, see TS 36.304 [4], clause 7.4 and TS 36.211 [21]. In milliseconds. Value ms40 corresponds to 40ms, value ms80 corresponds to 80 ms and so on.

E-UTRAN configures timeOffset-eDRX-Short to a value longer than or equal to timeOffsetDRX.

timeOffset-eDRX-Long

When eDRX is used, the long non-zero gap from the end of the configured maximum WUS duration to the associated PO, see TS 36.304 [4], clause 7.4 and TS 36.211 [21]. In milliseconds. Value ms1000 corresponds to 1000 ms, value ms2000 corresponds to 2000 ms.

6.7.3.3 NB-IoT Security control information elements

Void

6.7.3.4 NB-IoT Mobility control information elements

AdditionalBandInfoList-NB

AdditionalBandInfoList-NB information element

— ASN1START

AdditionalBandInfoList-NB-r14 ::= SEQUENCE (SIZE (1..maxMultiBands)) OF FreqBandIndicator-NB-r13

— ASN1STOP

FreqBandIndicator-NB

The IE FreqBandIndicator-NB indicates the E-UTRA operating band as defined in TS 36.101 [42], table 5.5-1.

FreqBandIndicator-NB information element

— ASN1START

FreqBandIndicator-NB-r13 ::= INTEGER (1..maxFBI2)

— ASN1STOP

MultiBandInfoList-NB

MultiBandInfoList-NB information element

— ASN1START

MultiBandInfoList-NB-r13 ::= SEQUENCE (SIZE (1..maxMultiBands)) OF MultiBandInfo-NB-r13

MultiBandInfo-NB-r13 ::= SEQUENCE {

freqBandIndicator-r13 FreqBandIndicator-NB-r13 OPTIONAL, — Need OR

freqBandInfo-r13 NS-PmaxList-NB-r13 OPTIONAL — Need OR

}

— ASN1STOP

– NS-PmaxList-NB

The IE NS-PmaxList-NB concerns a list of additionalPmax and additionalSpectrumEmission as defined in TS 36.101 [42], clause 6.2.4F, for a given frequency band. E-UTRAN does not include the same value of additionalSpectrumEmission in SystemInformationBlockType2-NB within this list.

NS-PmaxList-NB information element

— ASN1START

NS-PmaxList-NB-r13 ::= SEQUENCE (SIZE (1..maxNS-Pmax-NB-r13)) OF NS-PmaxValue-NB-r13

NS-PmaxValue-NB-r13 ::= SEQUENCE {

additionalPmax-r13 P-Max OPTIONAL, — Need OR

additionalSpectrumEmission-r13 AdditionalSpectrumEmission

}

— ASN1STOP

– ReselectionThreshold-NB

The IE ReselectionThreshold-NB is used to indicate an Rx level threshold for cell reselection. Actual value of threshold = field value * 2 [dB].

ReselectionThreshold-NB information element

— ASN1START

ReselectionThreshold-NB-v1360 ::= INTEGER (32..63)

— ASN1STOP

T-Reselection-NB

The IE T-Reselection-NB concerns the cell reselection timer TreselectionRAT for NB-IoT.

Value in seconds. s0 means 0 second and behaviour as specified in 7.3.2 applies, s3 means 3 seconds and so on.

T-Reselection-NB information element

— ASN1START

T-Reselection-NB-r13 ::= ENUMERATED {s0, s3, s6, s9, s12, s15, s18, s21}

— ASN1STOP

6.7.3.5 NB-IoT Measurement information elements

CQI-NPDCCH-NB

The IE CQI-NPDCCH-NB represents the downlink channel quality measurement of the NB-IoT carrier where the random access response is received. The codepoints for the CQI-NPDCCH measurements are according to the mapping table in TS 36.133 [16]. The value noMeasurements indicates no measurement reporting.

CQI-NPDCCH-NB information element

— ASN1START

CQI-NPDCCH-NB-r14 ::= ENUMERATED {

noMeasurements, candidateRep-A, candidateRep-B, candidateRep-C,

candidateRep-D, candidateRep-E, candidateRep-F, candidateRep-G,

candidateRep-H, candidateRep-I, candidateRep-J, candidateRep-K,

candidateRep-L}

— ASN1STOP

CQI-NPDCCH-Short-NB

The IE CQI-NPDCCH-Short-NB represents the short version of the downlink channel quality measurement of the NB-IoT carrier where the random access response is received. The codepoints for the CQI-NPDCCH-Short measurements are according to the mapping table in TS 36.133 [16]. The value noMeasurements indicates no measurement reporting.

CQI-NPDCCH-Short-NB information element

— ASN1START

CQI-NPDCCH-Short-NB-r14 ::= ENUMERATED {

noMeasurements, candidateRep-1, candidateRep-2, candidateRep-3}

— ASN1STOP

MeasResultServCell-NB

The IE MeasResultServCell-NB covers the measured results for the serving cell.

MeasResultServCell-NB information element

— ASN1START

MeasResultServCell-NB-r14 ::= SEQUENCE {

nrsrpResult-r14 NRSRP-Range-NB-r14,

nrsrqResult-r14 NRSRQ-Range-NB-r14

}

— ASN1STOP

– NRSRP-Range-NB

The IE NRSRP-Range-NB specifies the value range used in NRSRP measurements and thresholds. Integer value for NRSRP measurements according to mapping table in TS 36.133 [16], Table 9.1.22.9-1.

NRSRP-Range-NB information element

— ASN1START

NRSRP-Range-NB-r14 ::= INTEGER(0..113)

— ASN1STOP

– NRSRQ-Range-NB

The IE NRSRQ-Range-NB specifies the value range used in NRSRQ measurements and thresholds. Integer value for RSRQ measurements is according to mapping table in TS 36.133 [16], Table 9.1.22.14-1. The UE shall not report values 0 and 34.

NRSRQ-Range-NB information element

— ASN1START

NRSRQ-Range-NB-r14 ::= INTEGER(-30..46)

— ASN1STOP

– NSSS-RRM-Config-NB

The IE NSSS-RRM-Config-NB provides the configuration for NSSS-based RRM measurements. See TS 36.133 [16], TS 36.211 [21] and TS 36.214 [48]. The UE only perfoms NSSS-based RRM measurement on cells for which the configuration has been provided.

NSSS-RRM-Config-NB information element

— ASN1START

NSSS-RRM-Config-NB-r15 ::= SEQUENCE {

nsss-RRM-PowerOffset-r15 ENUMERATED {dB-3, db0, dB3},

nsss-NumOccDiffPrecoders-r15 ENUMERATED {n1, n2, n4, n8} OPTIONAL — Need OP

}

— ASN1STOP

NSSS-RRM-Config-NB field descriptions

nsss-RRM-PowerOffset

NSSS to NRS ratio for the serving cell as specified in TS 36.214 [48]. Value in dB. Value dB-3 corresponds to -3 dB, dB0 corresponds to 0 dB and so on.

nsss-NumOccDiffPrecoders

Number of consecutive NSSS occasions that use different precoders for NSSS transmission.See TS 36.211 [21]. Value n1 corresponds to 1 occasion, n2 corresponds to 2 occasions and so on.

For value n2, n4, and n8, UE may assume for nsss-NumOccDiffPrecoders consecutive NSSS occasions, E-UTRAN uses different precoders for NSSS transmission. For value n1, UE may assume that E-UTRAN always uses the same precoder.

If the field is absent, the UE makes no assumption on the antenna port(s) used for NSSS.

6.7.3.6 NB-IoT Other information elements

EstablishmentCause-NB

The IE EstablishmentCause-NB provides the establishment cause for the RRC connection request or the RRC connection resume request as provided by the upper layers.

EstablishmentCause-NB information element

— ASN1START

EstablishmentCause-NB-r13 ::= ENUMERATED {

mt-Access, mo-Signalling, mo-Data, mo-ExceptionData,

delayTolerantAccess-v1330, spare3, spare2, spare1}

— ASN1STOP

UE-Capability-NB

The IE UE-Capability-NB is used to convey the NB-IoT UE Radio Access Capability Parameters, see TS 36.306 [5]. The IE UE-Capability-NB is transferred in NB-IoT only.

UE-Capability-NB information element

— ASN1START

UE-Capability-NB-r13 ::= SEQUENCE {

accessStratumRelease-r13 AccessStratumRelease-NB-r13,

ue-Category-NB-r13 ENUMERATED {nb1} OPTIONAL,

multipleDRB-r13 ENUMERATED {supported} OPTIONAL,

pdcp-Parameters-r13 PDCP-Parameters-NB-r13 OPTIONAL,

phyLayerParameters-r13 PhyLayerParameters-NB-r13,

rf-Parameters-r13 RF-Parameters-NB-r13,

dummy SEQUENCE {} OPTIONAL

}

UE-Capability-NB-Ext-r14-IEs ::= SEQUENCE {

ue-Category-NB-r14 ENUMERATED {nb2} OPTIONAL,

mac-Parameters-r14 MAC-Parameters-NB-r14 OPTIONAL,

phyLayerParameters-v1430 PhyLayerParameters-NB-v1430 OPTIONAL,

rf-Parameters-v1430 RF-Parameters-NB-v1430,

nonCriticalExtension UE-Capability-NB-v1440-IEs OPTIONAL

}

UE-Capability-NB-v1440-IEs ::= SEQUENCE {

phyLayerParameters-v1440 PhyLayerParameters-NB-v1440 OPTIONAL,

nonCriticalExtension UE-Capability-NB-v14x0-IEs OPTIONAL

}

UE-Capability-NB-v14x0-IEs ::= SEQUENCE {

— Following field is only to be used for late REL-14 extensions

lateNonCriticalExtension OCTET STRING OPTIONAL,

nonCriticalExtension UE-Capability-NB-v1530-IEs OPTIONAL

}

UE-Capability-NB-v1530-IEs ::= SEQUENCE {

earlyData-UP-r15 ENUMERATED {supported} OPTIONAL,

rlc-Parameters-r15 RLC-Parameters-NB-r15,

mac-Parameters-v1530 MAC-Parameters-NB-v1530,

phyLayerParameters-v1530 PhyLayerParameters-NB-v1530 OPTIONAL,

tdd-UE-Capability-r15 TDD-UE-Capability-NB-r15 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL

}

TDD-UE-Capability-NB-r15 ::= SEQUENCE {

ue-Category-NB-r15 ENUMERATED {nb2} OPTIONAL,

phyLayerParametersRel13-r15 PhyLayerParameters-NB-r13 OPTIONAL,

phyLayerParametersRel14-r15 PhyLayerParameters-NB-v1430 OPTIONAL,

phyLayerParameters-v1530 PhyLayerParameters-NB-v1530 OPTIONAL,

}

AccessStratumRelease-NB-r13 ::= ENUMERATED {rel13, rel14, rel15, spare5, spare4, spare3, spare2, spare1, …}

PDCP-Parameters-NB-r13 ::= SEQUENCE {

supportedROHC-Profiles-r13 SEQUENCE {

profile0x0002 BOOLEAN,

profile0x0003 BOOLEAN,

profile0x0004 BOOLEAN,

profile0x0006 BOOLEAN,

profile0x0102 BOOLEAN,

profile0x0103 BOOLEAN,

profile0x0104 BOOLEAN

},

maxNumberROHC-ContextSessions-r13 ENUMERATED {cs2, cs4, cs8, cs12} DEFAULT cs2,

}

RLC-Parameters-NB-r15 ::= SEQUENCE {

rlc-UM-r15 ENUMERATED {supported} OPTIONAL

}

MAC-Parameters-NB-r14 ::= SEQUENCE {

dataInactMon-r14 ENUMERATED {supported} OPTIONAL,

rai-Support-r14 ENUMERATED {supported} OPTIONAL

}

MAC-Parameters-NB-v1530 ::= SEQUENCE {

sr-SPS-BSR-r15 ENUMERATED {supported} OPTIONAL

}

PhyLayerParameters-NB-r13 ::= SEQUENCE {

multiTone-r13 ENUMERATED {supported} OPTIONAL,

multiCarrier-r13 ENUMERATED {supported} OPTIONAL

}

PhyLayerParameters-NB-v1430 ::= SEQUENCE {

multiCarrier-NPRACH-r14 ENUMERATED {supported} OPTIONAL,

twoHARQ-Processes-r14 ENUMERATED {supported} OPTIONAL

}

PhyLayerParameters-NB-v1440 ::= SEQUENCE {

interferenceRandomisation-r14 ENUMERATED {supported} OPTIONAL

}

PhyLayerParameters-NB-v1530 ::= SEQUENCE {

mixedOperationMode-r15 ENUMERATED {supported} OPTIONAL,

sr-WithHARQ-ACK-r15 ENUMERATED {supported} OPTIONAL,

sr-WithoutHARQ-ACK-r15 ENUMERATED {supported} OPTIONAL,

nprach-Format2-r15 ENUMERATED {supported} OPTIONAL,

additionalTransmissionSIB1-r15 ENUMERATED {supported} OPTIONAL,

npusch-3dot75kHz-SCS-TDD-r15 ENUMERATED {supported} OPTIONAL

}

RF-Parameters-NB-r13 ::= SEQUENCE {

supportedBandList-r13 SupportedBandList-NB-r13,

multiNS-Pmax-r13 ENUMERATED {supported} OPTIONAL

}

RF-Parameters-NB-v1430 ::= SEQUENCE {

powerClassNB-14dBm-r14 ENUMERATED {supported} OPTIONAL

}

SupportedBandList-NB-r13 ::= SEQUENCE (SIZE (1..maxBands)) OF SupportedBand-NB-r13

SupportedBand-NB-r13 ::= SEQUENCE {

band-r13 FreqBandIndicator-NB-r13,

powerClassNB-20dBm-r13 ENUMERATED {supported} OPTIONAL

}

— ASN1STOP

UE-Capability-NB field descriptions

FDD/TDD appl

FDD/TDD diff

accessStratumRelease

Set to rel15 in this version of the specification.

FDD/TDD

No

additionalTransmissionSIB1

Indicates whether the UE supports additional SIB1 transmission as specified in TS 36.213 [23].

FDD

dataInactMon

Indicates whether the UE supports the data inactivity monitoring as specified in TS 36.321 [6].

FDD/TDD

No

dummy

This field is not used in the specification. It shall not be sent by the UE.

NA

NA

earlyData-UP

Indicates whether the UE supports EDT for User plane CIoT EPS optimisations, as defined in TS 24.301 [35].

FDD

interferenceRandomisation

For FDD: Indicates whether the UE supports interference randomisation in connected mode as defined in TS.36.211 [21].

FDD

maxNumberROHC-ContextSessions

Set to the maximum number of concurrently active ROHC contexts supported by the UE, excluding context sessions that leave all headers uncompressed. cs2 corresponds with 2 (context sessions), cs4 corresponds with 4 and so on. The network ignores this field if the UE supports none of the ROHC profiles in supportedROHC-Profiles.

FDD/TDD

No

mixedOperationMode

Defines whether the UE supports multi-carrier operation with mixed operation mode, standalone or inband/guardband, between the anchor carrier and the non-anchor carrier for unicast, paging, and random access as specified in TS 36.300 [9].

FDD

multiCarrier

Defines whether the UE supports multi -carrier operation.

FDD/TDD

Yes

multicarrier-NPRACH

Defines whether the UE supports NPRACH on non-anchor carrier as specified in TS 36.321 [6].

FDD/TDD

Yes

multipleDRB

Defines whether the UE supports multiple DRBs.

FDD/TDD

No

multiNS-Pmax

Defines whether the UE supports the mechanisms defined for NB-IoT cells broadcasting NS-PmaxList-NB.

FDD/TDD

No

multiTone

Defines whether the UE supports UL multi-tone transmissions on NPUSCH.

FDD/TDD

Yes

nprach-Format2

Defines whether the UE supports NPRACH resources using preamble format 2.

FDD

npusch-3dot75kHz-SCS-TDD

Indicates whether the UE supports NPUSCH with 3.75kHz SCS for TDD.

TDD

powerClassNB-14dBm

Defines whether the UE supports power class 14dBm in all the bands supported by the UE as specified in TS 36.101 [42].

If powerClassNB-20dBm is included, the UE shall not include the field powerClassNB-14dBm.

FDD/TDD

No

powerClassNB-20dBm

Defines whether the UE supports power class 20dBm in NB-IoT for the band, as specified in TS 36.101 [42]. If neither powerClassNB-14dBm nor powerClassNB-20dBm is included, UE supports power class 23 dBm in the NB-IoT band.

FDD/TDD

No

rai-Support

Defines whether the UE supports release assistance indication (RAI) as specified in TS 36.321 [6].

FDD/TDD

No

rlc-UM

Defines whether the UE supports RLC UM as specified in TS 36.322 [7].

FDD/TDD

No

supportedBandList

Includes the supported NB-IoT bands as defined in TS 36.101 [42].

FDD/TDD

No

sr-SPS-BSR

Defines whether the UE supports SR using SPS BSR as specified in TS 36.321 [6].

FDD

sr-withHARQ-ACK

Defines whether the UE supports physical layer SR with HARQ ACK as specified in TS 36.213 [23].

FDD

sr-withoutHARQ-ACK

Defines whether the UE supports physical layer SR without HARQ ACK as specified in TS 36.211 [21] and TS 36.213 [23].

FDD

supportedROHC-Profiles

List of supported ROHC profiles as defined in TS 36.323 [8].

FDD/TDD

No

twoHARQ-Processes

Defines whether the UE supports two HARQ processes operation in DL and UL as specified in TS 36.212 [22] and TS 36.213 [23].

FDD/TDD

Yes

ue-Category-NB

UE category as defined in TS 36.306 [5]. Value nb1 corresponds to UE category NB1, value nb2 corresponds to UE category NB2.

A UE shall always include the field ue-Category-NB-r13 in this version of the specification.

FDD/TDD

Yes

NOTE 1: The IE UE-Capability-NB does not include AS security capability information, since these are the same as the security capabilities that are signalled by NAS. Consequently AS need not provide "man-in-the-middle" protection for the security capabilities.

NOTE 2: The column ‘FDD/TDD appl’ indicates the applicability to the xDD mode: ‘FDD’ means applicable to FDD only, ‘TDD’ means applicable to TDD only and ‘FDD/TDD’ means applicable to FDD and TDD.

NOTE 3: The column ‘FDD/TDD diff’ indicates if the UE is allowed to signal a different value for FDD and TDD when the capability applies to both FDD and TDD modes. ‘-‘ is used when the capability applies to one mode only, ‘No’ is used for dual mode capabilities where a common value is signalled for both modes, and ‘Yes’ is used for dual mode capabilities where a separate value is signalled for each mode. Common capabilities and FDD capabilities are reported in the fields of UE-Capability-NB except field tdd-UE-Capability. TDD capabilities are reported in tdd-UE-Capability.

UE-RadioPagingInfo-NB

The IE UE-RadioPagingInfo-NB contains UE NB-IoT capability information needed for paging.

UE-RadioPagingInfo-NB information element

— ASN1START

UE-RadioPagingInfo-NB-r13 ::= SEQUENCE {

ue-Category-NB-r13 ENUMERATED {nb1} OPTIONAL,

…,

[[ multiCarrierPaging-r14 ENUMERATED {true} OPTIONAL

]],

[[ mixedOperationMode-r15 ENUMERATED {supported} OPTIONAL,

wakeUpSignal-r15 ENUMERATED {true} OPTIONAL,

wakeUpSignalMinGap-eDRX-r15 ENUMERATED {ms40, ms240, ms1000, ms2000} OPTIONAL,

multiCarrierPagingTDD-r15 ENUMERATED {true} OPTIONAL

]]

}

— ASN1STOP

UE-RadioPagingInfo-NB field descriptions

mixedOperationMode

Indicates whether the UE supports multi-carrier operation with mixed operation mode, standalone or inband/guardband, between the anchor carrier and non-anchor carrier for unicast, paging, and random access, as specified in TS 36.300 [9].

multiCarrierPaging

Indicates whether the UE supports paging on non-anchor carriers as defined in TS 36.304 [4].

multiCarrierPagingTDD

Indicates whether the UE supports paging on non-anchor carriers for TDD as defined in TS 36.304 [4].

ue-Category-NB

UE NB-IoT category as defined in TS 36.306 [5]. A UE shall always include the field ue-Category-NB-r13 in this version of the specification.

wakeUpSignal

Indicates whether the UE supports WUS for paging in DRX in FDD as specified in TS 36.304 [4]. If this field is included, the minimum gap between WUS and associated PO for DRX is fixed as 40 ms.

wakeUpSignalMinGap-eDRX

Indicates the minimum gap the UE supports between WUS and associated PO in case of eDRX in FDD, as specified in TS 36.304 [4]. Value ms40 corresponds to 40 ms, value ms240 corresponds to 240 ms and so on.

If this field is included, the UE shall also indicate support for WUS for paging in DRX,

UE-TimersAndConstants-NB

The IE UE-TimersAndConstants-NB contains timers and constants used by the UE in either RRC_CONNECTED or RRC_IDLE.

UE-TimersAndConstants-NB information element

— ASN1START

UE-TimersAndConstants-NB-r13 ::= SEQUENCE {

t300-r13 ENUMERATED {

ms2500, ms4000, ms6000, ms10000,

ms15000, ms25000, ms40000, ms60000},

t301-r13 ENUMERATED {

ms2500, ms4000, ms6000, ms10000,

ms15000, ms25000, ms40000, ms60000},

t310-r13 ENUMERATED {

ms0, ms200, ms500, ms1000, ms2000, ms4000, ms8000},

n310-r13 ENUMERATED {

n1, n2, n3, n4, n6, n8, n10, n20},

t311-r13 ENUMERATED {

ms1000, ms3000, ms5000, ms10000, ms15000,

ms20000, ms30000},

n311-r13 ENUMERATED {

n1, n2, n3, n4, n5, n6, n8, n10},

…,

[[ t311-v1350 ENUMERATED {

ms40000, ms60000, ms90000, ms120000}

OPTIONAL — Need OR

]],

[[ t300-v1530 ENUMERATED {

ms80000, ms100000, ms120000} OPTIONAL, — Cond TDD

t301-v1530 ENUMERATED {

ms80000, ms100000, ms120000} OPTIONAL, — Cond TDD

t311-v1530 ENUMERATED {

ms160000, ms200000} OPTIONAL, — Cond TDD

t300-r15 ENUMERATED {ms6000, ms10000, ms15000, ms25000, ms40000,

ms60000, ms80000, ms120000} OPTIONAL — Cond EDT

]]

}

— ASN1STOP

UE-TimersAndConstants-NB field descriptions

n3xy

Constants are described in clause 7.4. n1 corresponds with 1, n2 corresponds with 2 and so on.

t3xy

Timers are described in clause 7.3. Value ms0 corresponds with 0 ms, ms200 corresponds with 200 ms and so on. The UE shall use the extended values t311-v1350, t300-v1530, t301-v1530 and t311-v1530, if present, and ignore the value signaled by t311-r13, t300-r13, t301-r13 and t311-r13 respectively.

t300-r15 is only applicable for EDT. UE performing EDT shall use t300-r15, if present.

Conditional presence

Explanation

EDT

The field is optionally present, Need OR, if edt-Parameters is present in SIB2-NB; otherwise the field is not present and the UE shall delete any existing value for this field.

TDD

The field is optionally present, Need OR, in TDD mode. Otherwise, the field is not present.

6.7.3.7 NB-IoT MBMS information elements

Void

6.7.3.7a NB-IoT SC-PTM information elements

SC-MTCH-InfoList-NB

The IE SC-MTCH-InfoList-NB provides the list of ongoing MBMS sessions transmitted via SC-MRB and for each MBMS session, the associated G-RNTI and scheduling information.

SC-MTCH-InfoList-NB information element

— ASN1START

SC-MTCH-InfoList-NB-r14 ::= SEQUENCE (SIZE (0..maxSC-MTCH-NB-r14)) OF SC-MTCH-Info-NB-r14

SC-MTCH-Info-NB-r14 ::= SEQUENCE {

sc-mtch-CarrierConfig-r14 CHOICE {

dl-CarrierConfig-r14 DL-CarrierConfigCommon-NB-r14,

dl-CarrierIndex-r14 INTEGER (0..maxNonAnchorCarriers-NB-r14)

},

mbmsSessionInfo-r14 MBMSSessionInfo-r13,

g-RNTI-r14 BIT STRING(SIZE(16)),

sc-mtch-SchedulingInfo-r14 SC-MTCH-SchedulingInfo-NB-r14 OPTIONAL, — Need OP

sc-mtch-NeighbourCell-r14 BIT STRING (SIZE(maxNeighCell-SCPTM-NB-r14)) OPTIONAL, — Need OP

npdcch-NPDSCH-MaxTBS-SC-MTCH-r14 ENUMERATED {n680, n2536},

npdcch-NumRepetitions-SC-MTCH-r14 ENUMERATED {r1, r2, r4, r8, r16,

r32, r64, r128, r256,

r512, r1024, r2048, spare4,

spare3, spare2, spare1},

npdcch-StartSF-SC-MTCH-r14 ENUMERATED {v1dot5, v2, v4, v8,

v16, v32, v48, v64},

npdcch-Offset-SC-MTCH-r14 ENUMERATED {zero, oneEighth, oneQuarter,

threeEighth, oneHalf, fiveEighth,

threeQuarter, sevenEighth},

}

SC-MTCH-SchedulingInfo-NB-r14 ::= SEQUENCE {

onDurationTimerSCPTM-r14 ENUMERATED {

pp1, pp2, pp3, pp4,

pp8, pp16, pp32, spare},

drx-InactivityTimerSCPTM-r14 ENUMERATED {

pp0, pp1, pp2, pp3,

pp4, pp8, pp16, pp32},

schedulingPeriodStartOffsetSCPTM-r14 CHOICE {

sf10 INTEGER(0..9),

sf20 INTEGER(0..19),

sf32 INTEGER(0..31),

sf40 INTEGER(0..39),

sf64 INTEGER(0..63),

sf80 INTEGER(0..79),

sf128 INTEGER(0..127),

sf160 INTEGER(0..159),

sf256 INTEGER(0..255),

sf320 INTEGER(0..319),

sf512 INTEGER(0..511),

sf640 INTEGER(0..639),

sf1024 INTEGER(0..1023),

sf2048 INTEGER(0..2047),

sf4096 INTEGER(0..4095),

sf8192 INTEGER(0..8191)

},

}

— ASN1STOP

SC-MTCH-InfoList-NB field descriptions

dl-CarrierConfig

Downlink carrier used for SC-MTCH. E-UTRAN cannot configure a downlink carrier operating in mixed operation mode.

dl-CarrierIndex

Index to a downlink carrier signalled in system information. Value ‘0’ corresponds to the anchor carrier, value ‘1’ corresponds to the first entry in dl-ConfigList in SystemInformationBlockType22-NB, value ‘2’ corresponds to the second entry in dl-ConfigList and so on.

drx-InactivityTimerSCPTM

Timer for SC-MTCH reception in TS 36.321 [6]. Value in number of NPDCCH periods. Value pp1 corresponds to 1 NPDCCH period, pp2 corresponds to 2 NPDCCH periods and so on.

g-RNTI

G-RNTI used to scramble the scheduling and transmission of a SC-MTCH.

mbmsSessionInfo

Indicates the ongoing MBMS session in a SC-MTCH.

npdcch-NPDSCH-MaxTBS-SC-MTCH

Maximum NPDSCH TBS for the SC-MTCH, see TS 36.213 [23]. Value n680 corresponds to 680 bits and value n2536 corresponds to 2536 bits.

npdcch-NumRepetition-SC-MTCH

The maximum number of NPDCCH repetitions the UE needs to monitor for SC-MTCH multicast search space, see TS 36.213 [23].

npdcch-Offset-SC-MTCH

Fractional period offset of starting subframe for NPDCCH multicast search space for SC-MTCH, see TS 36.213 [23].

npdcch-startSF-SC-MTCH

Starting subframes configuration of the NPDCCH multicast search space for SC-MTCH, see TS 36.213 [23].

onDurationTimerSCPTM

Timer for SC-MTCH reception in TS 36.321 [6]. Value in number of NPDCCH periods. Value pp1 corresponds to 1 NPDCCH period, pp2 corresponds to 2 NPDCCH periods and so on.

schedulingPeriodStartOffsetSCPTM

SCPTM-SchedulingCycle and SCPTM-SchedulingOffset in TS 36.321 [6]. The value of SCPTM-SchedulingCycle is in number of sub-frames. Value sf10 corresponds to 10 sub-frames, sf20 corresponds to 20 sub-frames and so on. The value of SCPTM-SchedulingOffset is in number of sub-frames.

sc-mtch-CarrierConfig

Downlink carrier that is used for SC-MTCH.

sc-mtch-NeighbourCell

Indicates neighbour cells which also provide this service on SC-MTCH. The first bit is set to 1 if the service is provided on SC-MTCH in the first cell in scptmNeighbourCellList, otherwise it is set to 0. The second bit is set to 1 if the service is provided on SC-MTCH in the second cell in scptmNeighbourCellList, and so on. If this field is absent, the UE shall assume that this service is not available on SC-MTCH in any neighbour cell.

sc-mtch-SchedulingInfo

DRX information for the SC-MTCH.

If this field is absent, DRX is not used for the SC-MTCH.

SCPTM-NeighbourCellList-NB

The IE SCPTM-NeighbourCellList-NB indicates a list of neighbour cells where ongoing MBMS sessions provided via SC-MRB in the current cells are also provided.

— ASN1START

SCPTM-NeighbourCellList-NB-r14 ::= SEQUENCE (SIZE (1..maxNeighCell-SCPTM-NB-r14)) OF PCI-ARFCN-NB-r14

PCI-ARFCN-NB-r14 ::= SEQUENCE {

physCellId-r14 PhysCellId,

carrierFreq-r14 CarrierFreq-NB-r13 OPTIONAL — Need OP

}

— ASN1STOP

SCPTM-NeighbourCellList-NB field descriptions

physCellId

Physical Cell Identity of the neighbour cell.

carrierFreq

Carrier frequency of the neighbour cell.

Absence of the IE means that the neighbour cell is on the same frequency as the current cell.