LTE openenb.conf

From YateBTS
Jump to: navigation, search

This page is a DRAFT.

Contents

openenb.conf

When it starts up, the YateENB reads openenb.conf and saves its content into a global key-value associative array called gConfig, which is an instance of TelEngine::Confguration from libyate. The file has a "winconfig" format, and us organized into sections with parameters in each section.

The key for each parameter is in two parts:

  • a section name and
  • a key name within the section.

[General]

The [General] section contains the global configuration for the ENB Yate Module.

mode: string: Operation mode

The setting decides which control Javascript file to load.

Set it up to:

mode=ENB

autostart: boolean: Start the cell operation at load time

Set it up to

autostart=true

to allow cell startup.

transceiver: boolean: Start the radio transceiver (TrxManager)

Mostly used for testing.

Set it up to:

transceiver=true


[Basic]

These parameters are those you are most likely to change.

eNodeB Identity

The 20-bit ID is unique to every eNodeB in the network. To create a 44-bit global eNodeB identity, the ID has to be concatenated with the PLMN ID.

The value cannot be default.

enodebId=

Mobile Country Code part of the PLMN Identity

It is the same for every eNodeB in the network.

Example:

MCC = 001

Mobile Network Code part of the PLMN Identity

It is the same for every eNodeB in the network.

Example:

MNC = 01

Tracking Area Code

The value cannot be default.

TAC=

Cell Identity

It must be 7 digits in length.

Example:

CellIdentity = 0000001

Human readable eNodeB Name that is sent to the MME during S1-MME setup.

According to the 3GPP specifications, the parameter is optional, yet, if set, the MME can use it as the human readable name of the eNodeB.

Example:

Name=YateENB

Bandwidth

The parameter is the LTE radio channel bandwidth, in number of resource blocks in the frequency domain.

To calculate the bandwidth in MHz, use the following formula:

MHz BW = (N_RB * 2) / 10, except for 6 RBs.

Example:

Bandwidth = 25

Physical Layer Cell ID

To calculate this parameter, use the following formula:

Phy Cell ID = 3*NID1 + NID2

The value of the NID1 is between 1..167; the value of NID2 is between 0..2, giving the range of the cell ID between 0..503.

The values cannot be default.

NID1=
NID2=

EARFCN

The parameter sets the downlink ARFCN. The uplink ARFCN is selected automatically based on the uplink ARFCN.

Typically, the bandwidth should be the same for all the eNodeBs operating in the same band.

The value cannot be default.

Examples:

  • EARFCN 900, 1960 MHz, Band 2 ("PCS1900")
  • EARFCN 1575, 1842.5 MHz, Band 3 ("DCS1800")
  • EARFCN 2175, 2132,5 MHz, Band 4 ("AWS-1")
  • EARFCN 2525, 881.5 MHz, Band 5 ("850")
  • EARFCN 3100, 2655.0 MHz, Band 7 ("2600")
  • EARFCN 5790, 740.0 MHz, Band 17 ("700 b")
  • EARFCN 6300, 806.0 MHz, Band 20 ("800 DD")

The value cannot be default.

EARFCN=

Band selection

In most system the band is set by the hardware type and should not be changed.

Band=

Settable output level, dBm

The valid range for a SatSite unit is between 0..43

Example:

OutputLevel=40

OFDM crest factor allowance in dB

The valid range is between 5..20, while the default is 13.

Example:

CrestFactor = 13

PDCCH, PCFICH, VRB configuration

The values are typically the same for all the eNodeBs in the network.

The allowed values are: 1, 2, 3.

Example:

CFI=2

PHICH Ng factor (from MIB in PBCH)

The parameter determines the bandwidths used for the PHICH, and affects the available bandwidth for the PDCCH.

The allowed values are: oneSixth, half, one, two.

Example:

Ng=one

PDCCH format

As specified in the TS 136.211 Table 6.8.1-1 it is also called the aggregation level.

The allowed values are between 0..3.

Example:

PdcchFormat=2

Distributed Virtual Resource Blocks

The allowed values for this parameter are false, for localized, or true, for the distributed type.

Example:

DistributedVrbs = true

[System information repetition parameters]

Scheduler SI Window Length in milliseconds

The allowed values for this parameter are: 1, 2, 5, 10, 15, 20, 40

Example:

SiWindowLength = 20

Scheduler SI Periodicity

The allowed values are: powers of two between 8 and 512.

Example:

SiPeriodicity = 8 

Scheduler SI Redundancy

The allowed value for this parameter is a range between 1 to 8 but the default is 2.

The value should be larger for cells with a larger coverage area.

Example:

SiRedundancy = 2 

Default Paging Cycle for UE DRX

The allowed values are: powers of two between 32 and 256.

Example:

DefaultPagingCycle = 32

Minimum power level for cell reselection, dBm ("q_RxLevMin" in SIB1)

The allowed range for this parameter is between -70..-22.

Example:

RxLevelMinimum=-70

PRACH (random access channel) configuration

This parameter defines the number of PRACH preambles.

The allowed values are multiples of 4: 4..64. Larger values reduce PRACH contention at the expense of computational load.

Example:

Prach.Preambles=4

Power ramping step, dB

The allowed values for this parameter are multiples of 2: 0..6.

Example:

Prach.PowerStep=4

Initial RSSI Target, dBm

The allowed values are multiple of 2: -90..-120.

Example:

Prach.InitialTarget=-90

Maximum transmissions

The allowed values for this parameter are: 3, 4, 5, 6, 7, 8, 10, 20, 50, 100, 200.

Example:

Prach.TransMax=200

Response window size in subframes

In the spec the allowed values are: 2..8, 10 (not 9). We only support 10.

Example:

Prach.ResponseWindow=10

Contention Resolution Timer in subframes

The allowed values are multiples of 8: 8..64.

Example:

Prach.ContentionTimer=64

Root Sequence Index

Cells with overlapping coverage should have different values.

The allowed values for this parameter are between 0..837.

Example:

Prach.RootSequence=0

Configuration Index

The allowed values are between 0..63.

Example:

Prach.ConfigIndex=14

Zero Correlation Zone

The allowed values for this parameter are between 0..15.

Example:

Prach.ZeroCorr=1

Frequency Offset

Cells with overlapping coverage should have different values.

The allowed values for this parameter are between 0..94.

Example:

Prach.FreqOffset=9

PDSCH (downlink traffic channel) configuration

The allowed values for this parameter are between: -60..50.

Example:

Pdsch.RefPower=-20

PUSCH (uplink traffic channel) configuration

This parameter allows the use of QAM64 in the uplink boolean.

Example:

Pusch.Qam64=false

Reference Signal Group Assignment

Cells with overlapping coverage should have different values.

The allowed values for this parameter are between 0..29.

Example:

Pusch.RefSigGroup=2

Reference Signal Cyclic Shift

The allowed values for this parameter are between 0..7.

Example:

Pusch.CyclicShift=3

PUCCH (uplink control channel) configuration

This parameter refers to the Delta Shift.

The allowed values are: 1, 2, 3.

Example:

Pucch.Delta=1

Bandwidth available for use by PUCCH formats 2/2a/2b, in RBs

The allowed values for this parameter are between 0..98, but must not exceed the number RBs in system bandwidth.

Larger values support larger number of connected UEs at the expense of uplink bandwidth.

Example:

Pucch.RbCqi=3

Number of cyclic shifts used for PUCCH formats 1/1a/1b in a resource block with a mix of formats 1/1a/1b and 2/2a/2b

The allowed values for this parameter are between 0..7.

Example:

Pucch.CsAn=3

Resource allocation offset parameter

The allowed values for this parameter are between 0..2047.

Example:

Pucch.An=45

[scheduler]

These parameters are related to the MAC scheduler.

SibModulationRate

This parameter refers to the Sib modulation rate.

The allowed interval for this parameter is 1-16. The default value is 2.

Example:

SibModulationRate=2

SibDci

This parameter refers to the DCI for SIB.

The allowed values for this parameter are: dci0, dci1, dci1a, dci1a_pdcch, dci1b, dci1c, dci1d, dci2, dci2a, dci3, dci3a.

The default value is: dci1a.

Example:

SibDci=dci1a

PcchMcs

This parameter refers to the PCCH MCS.

The default value is 2.

Example:

PcchMcs=2

PcchDci

This parameter refers to the DCI for PCCH.

The allowed values are: dci0, dci1, dci1a, dci1a_pdcch, dci1b, dci1c, dci1d, dci2, dci2a, dci3, dci3a

The default value is: dci1a

Example:

PcchDci=dci1a

RarMcs

This parameter refers to the RAR MCS.

The default value is: 2.

Example:

RarMcs=2

RarDci

This parameter refers to the DCI for RAR.

The allowed values are: ci0, dci1, dci1a, dci1a_pdcch, dci1b, dci1c, dci1d, dci2, dci2a, dci3, dci3a.

The default value is: dci1a.

Example:

RarDci=dci1a

DCI for downlink

The allowed values for this parameter are: dci0, dci1, dci1a, dci1a_pdcch, dci1b, dci1c, dci1d, dci2, dci2a, dci3, dci3a.

The default is:

downlinkDci=dci1a

DCI for uplink

The allowed values for this parameter are: dci0, dci1, dci1a, dci1a_pdcch, dci1b, dci1c, dci1d, dci2, dci2a, dci3, dci3a.

The default is:

uplinkDci=dci0

Uplink resource blocks

UplinkRbs=

UplinkRbStartIndex

This parameter refers to the index if the first RB that can be scheduled for uplink.

UplinkRbStartIndex

DistributedVrbs

This parameter is true if the resource blocks are distributed.

DistributedVrbs=

PrachResponseDelay

This parameter refers to the response delay for PRACH events in subrames.

PrachResponseDelay=

[measurements]

These parameters refer to the KPI-related performance measurements.

Measurement reporting period in minute

Example:

reportingPeriod=15

Path to store XML measurement file for FTP access

If this parameter is not set, then the file will not be written.

reportingPath=

[bearers]

These parameters are related to the RLC and PDCP layers.

SRB default configuration

Example:

Srb1.mode = default
;Srb2.mode = default

;alternately, specify "unacknowledged" mode configuration for SRBx (x = 1 or 2):
;Srbx.mode = unacknowledged
;Srbx.rlcSnFieldLength = 10
;Srbx.rlcTReordering = 35

;alternately, specify "acknowledged" mode configuration for SRBx (x = 1 or 2):
;Srbx.mode = acknowledged
;Srbx.rlcTPollRetransmit = 45
;Srbx.rlcTReordering = 35
;Srbx.rlcTStatusProhibit = 0
;Srbx.rlcMaxRetxThreshold = 4
;Srbx.rlcPollPdu = 0
;Srbx.rlcPollByte = 0


DRB default configuration

Example:

; DRB "unacknowledged" mode. See 3GPP 36.508 - 4.8.2.1.2.1, 4.8.2.1.3.1.
;DrbUm.rlcSnFieldLength = 10
;DrbUm.rlcTReordering = 50
;DrbUm.pdcpSnFieldLength = 12
;DrbUm.pdcpDiscardTimer = 100 

;DRB "acknowledged" mode. See 3GPP 36.508 - 4.8.2.1.2.2, 4.8.2.1.3.2.
;DrbAm.rlcTPollRetransmit = 80
;DrbAm.rlcTReordering = 80
;DrbAm.rlcTStatusProhibit = 60
;DrbAm.rlcMaxRetxThreshold = 4
;DrbAm.rlcPollPdu = 128
;DrbAm.rlcPollByte = 125
;DrbAm.pdcpSnFieldLength = 12
;DrbAm.pdcpDiscardTimer = 0
;DrbAm.pdcpStatusRequired = true

[mme1]

The eNodeB normally selects and MME using DNS, but explicit MME selection is also possible. Bellow you can see an example for explicit MME configuration.

This section configures an MME defined as mme1

Example:

;address = 192.168.56.62
;local = 192.168.56.1
;streams = 5
;dscp = expedited

[radio hardware]

The following parameters control the lower PHY layer.

Radio maximum output power, dBm

This parameter is set by the calibration and should not be changed.

The default value for the SatSite is 43 dBm.

Example:

MaximumOutput=43

Receiver saturation point at full gain, referenced to the antenna port

This parameter is set by the calibration and should not be changed.

The default value for the SatSite is -20 dBm.

It needs to be checked with Nuand before setting. The worst case saturation point of the bladeRF is our LNA gain + duplexer loss.

Example:

ReceiverReference=-20