SatSite LMI Configuration for LTE

From YateBTS
Jump to: navigation, search


The Local Management Interface (LMI) allows control and management of one Lab Kit or SatSite unit, locally.

LMI can also be used by engineers if a SatSite unit they had previously configured via the YateMMI needs local maintenance after it has been installed in the field.

To begin, you must first select the working mode. Depending on the configuration mode, select:

  • GSM nipc (for GSM Network-in-a-PC mode)
  • GSM roaming (for a GSM BTS connected to YateUCN/Hosted Core for voice and SMS services)
  • GSM dataroam (for a GSM BTS connected to YateUCN/Hosted Core for voice, SMS and data services mode)
  • LTE enb (for an LTE eNodeB connected to an MME or a Hosted Core)


LTE enb configuration

To enable the LTE enb mode click on the Modify button, select the LTE enb mode and Save.

working mode LTE enb enable.png


Minimum configuration to start your eNB

This section describes the minimum configurations that have to be done to start using eNB after enabling the LTE enb mode.

The only mandatory tab is ENB Configuration, with two sub-tabs

For the other configurations in this page, they are optional and we recommend running the default values.

Main Configuration

The YateENB configuration interface for the LTE Lab Kit/SatSite configures a single unit.

It uses a set/get JSON request to the eNodeB's configuration API from Yate. The configuration API writes/reads the .conf files.

eNodeB Radio Configuration

eNodeB

This screen allows setting the basic parameters per equipment and the unique parameters in the eNodeBs with overlapping coverage.

The parameters below are the most basic configuration parameters and the ones most likely to be changed.

1. Set an eNodeB ID, unique to every unit in the network. This value is concatenated with the PLMN ID to create a 44-bit global eNodeB identity. This value must be set; there is no default.

2. Set the Mobile Country Code.

3. Set the Mobile Network Code.

4. Set the Tracking Area Code. The value must be set, as there isn't any default.

5. Set a cell identity that must be seven digits in length.

6. Set a human readable eNodeB name. This name will be sent to the MME during the S1-MME setup.

7. Select the band according to your hardware specifications.

8. Select the LTE radio channel bandwidth.

9. Select the EARFCN for the downlink. The uplink ARFCN is selected automatically based on the downlink's value.

10. Select the NID1 and NID2. This allows setting the Physical Layer Cell ID, which can be determined through the following formula: 3*NID1 + NID2. NID1's value is between 0..167 and NID2's value is between is 0..2. This gives a Phy cell IDE range between 0..503. The combination 3*NID1+NID2 must never be the same for cells with overlapping coverage.

11. Select the Prach.RootSequence index in SIB2. Cells with overlapping coverage must have different values.

12. Select the Pusch.RefSigGroup assignment. Cells with overlapping coverage must have different values.

13. Set the OutputLevel. The valid range for SatSite 142 is between 0..43 (dBm).

14. Select the CrestFactor allowance. The valid range is between 5..20 (dBm). It defaults to 13. A lower CrestFactor value leads to a higher output power level. It can be used to push higher output levels, but can also produce a higher distortion and clipping.

15. Tick the Distributed Virtual Resource Blocks box if you want to improve multipath performance. If ticked, it also limits the resource allocations to 16 RBs (2.88 MHz).

Enb configuration.png

For more information each of these parameters, refer to the LTE openenb.conf page.

Bearers

The bearers screen allows setting the bearer parameters of the RLC and PDCP layers of the SRB and DRB default configuration.

1. SRB configuration. We recommend that you don't change these settings unless you're sure of what you're doing.

2. The DRB default configuration - for QCI 9 (???? is this missing???)

3. DRB "unacknowledged" mode - See 3GPP 36.508 - 4.8.2.1.2.1, 4.8.2.1.3.1

4. DRB "acknowledged" mode - See 3GPP 36.508 - 4.8.2.1.2.2, 4.8.2.1.3.2

5. Check that the DrbAm.pdcpStatusRequired box is ticked, which indicates whether or not the UE shall send a PDCP Status Report upon re-establishment of the PDCP entity and upon PDCP data recovery as specified in TS 36.323 [8]. The default is set to true.

ENB configuration radio bearers.png

For more information each of these parameters, refer to the LTE openenb.conf page.

Core

GTP Configuration

Click on the Core tab and go to the GTP section. This screen allows setting the S1-U (GTP) interface parameters.

1. Set the Addr4 (IPv4) address to use with the eNodeB tunnel end.

2. Set the Addr6 (IPv6) address to use with the eNodeB tunnel end.

3. Click the Submit button.

ENB configuration gtp.png

MME

Click on the Core tab and go to the MME section. This is the screen for hand-configuring the MME. The eNodeB normally selects an MME using DNS, but explicit MME selection is also possible.

core-mme.png


Hand-configured MME

For the hand-configured MME follow these steps:

1. Insert the MME's IP address.

2. Insert the MME's local address.

3. Insert the streams number.

4. Insert the DSCP status. (?!)

5. Click the Submit button.

You must fill in similar data for the second and third hand-configured MMEs.

Access Channels Configuration

Click on the Access channels tab and go trough all the sections below.

PRACH

This screen sets the parameter values for the [prach] section.

Follow these steps:

1. Set the number of PRACH preambles. The allowed values are multiples of 4 (4..6). The default value is 4.

2. Set the Prach.PowerStep (power ramping step). The value is expressed in dB.

3. Set the Initial RSSI Target. The allowed values are multiples of 2 (-90..-120), and are expressed in dBm. The default value is -90.

4. Set the number of maximum transmissions.

5. Set the Prach.ResponseWindow value in subframes. The allowed values are 2..8, 10 (not 9), as defined in the specifications. SatSite only supports 10.

6. Set the Prach.ContentionTimer value in subframes.

7. Set the Prach.ConfigIndex value.

8. Set the Prach.ZeroCorr value.

9. Click the Submit button.

PDSCH

This screen sets the parameter values for the [pdsch] section.


Follow these steps:

1. Set the Pdsch.RefPower value, expressed in dB. The allowed values are -60..50. The default value is -20.

2. Click the Submit button.

PUSCH

This screen sets the parameter values for the [pusch] section.

Follow these steps:

1. Set the Pusch.Qam64 , which allows the use of QAM64 in uplink. The default is false.

2. Set the Pusch.CyclicShift value. The default value is 3.

2. Click the Submit button.

PUCCH

This screen sets the parameter values for the [pucch] section.

Follow these steps:

1. Set the Pucch.Delta value. The default value is 1.

2. Set the Pucch.RbCqi value, which defines the bandwidth available for use by PUCCH formats 2/2a/2b, expressed in RBs. The allowed values are 0..98, but must not exceed number of RBs in system bandwidth. The default value is 3.

3. Set the Pucch.CsAn value, which defines the 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 default value is 3.

4. Set the Resource allocation offset parameter value. The allowed values are 0..2047. The default value is 45.

5. Click the Submit button.

PDCCH

This screen sets the parameters values for the [pdcch] section.

Follow these steps:

1. Set the CFI (Control format indicator) value that determines the available bandwidth for the PDCCH.

2. Set the PHICH Ng factor that determines the bandwidth used for PHICH, and affects the available bandwidth for PDCCH.

3. Set the PdcchFormat value as specified in TS 136.211 Table 6.8.1-1, also known as the aggregation level. A large aggregation level gives a more robust PDCCH transmission at the expense of PDCCH capacity.

4. Click the Submit button.

Hardware

Click on the Hardware tab and first go through the sections below.

Site info

The site info contains site specific information.

1. Set the site's GPS location.

2. Add the site's name.

3. Insert the antenna's direction, in degrees, from the North.

4. Insert the antenna's beam width in degrees.

5. Add the reporting period in minutes, for the hardware status. The default is 15 minutes.

6. Click the Submit button.

Site equipment

This screen contains information about customer-specific parameters for other site equipment, such as antennas, cables, power supply, etc.

site-equipment.png


Shutdown

This screen includes the parameters for safely shutting down SatSite components. Raising these parameters above their default values may result in damage to the eNodeB hardware or reduced equipment life.

Screenshot from 2018-08-30 13-47-48.png

System

Click on the System tab and first go through the sections below.

System information

The screen allows setting parameters for the system.

Follow the steps below:

1. Set the Scheduler SI Window Length in milliseconds.

2. Set the SiPeriodicity. The allowed values are the powers of two between 8 and 512.

3. Set the SiRedundancy. The value should be larger for cell with large coverage area.

4. Set the DefaultPagingCycle for the UE's DRX.

5. Set the minimum power level for cell reselection. The value is expressed in dBm. The allowed range is Allowed range is between -70 .. -22. The default value is -70.

6. Click the Submit button.


Scheduler

This screen allows setting the parameters related to the MAC Scheduler.

1. Set the SIB modulation rate.

2. Set the SCI for the SIB.

3. Set the PCCH MCS.

4. Set the DCI for PCCH.

5. Set the RAR MCS.

6. Set the DCI for RAR.

7. Set the DCI for downlink.

8. Set the DCI for uplink.

9. Leave the DistributedVrbs box ticked.

10. Set the response delay for PRACH events in subframes.

11. Click the Submit button.