How to Dene Hardware and Cells on AirScale BTS

This course describes the LTE BTS data commissioning steps to define the Capacity Plug-in
Units, the optional Fronthaul Switch, the Radio Units, the cells, and the optional antenna line
devices.

LEAD IN

Before We Start

Learning Objectives

DEFIN E H AR DWAR E

De ne the Baseband Modules

De ne the Fronthaul Switch (optional)

De ne the Radio Modules

DEFIN E CELLS

De ne the LTE FDD and TDD Cells

 De ne the NB IoT Cells

DEFIN E OPTION AL ALD, R F SH AR IN G, AN D PASSIVE DEVICES

De ne the Optional ALD, RF Sharing, and Passive Devices

LET'S WR AP UP

Knowledge Check

Main Takeaways
Lesson 1 of 10

Before We Start

Adjust display settings Turn sound on

The content of this training is protected by Nokia. Access Nokia copyright and confidentiality disclaimer
affecting this content before proceeding.

C O NT I NU E
Lesson 2 of 10

Learning Objectives

Welcome to the Nokia AirScale LTE BTS Commissioning, Integration and OAM course.

This is the How to Define Hardware and Cells on AirScale BTS module.

After completing this learning module, you will be able to:

1 Demonstrate Nokia LTE BTS commissioning via WebEM for the Baseband Module, the
(optional) Fronthaul Switch, and the Radio Module.

2 Demonstrate Nokia LTE BTS commissioning via WebEM for the wideband LTE-FDD/TDD cells
and NB IoT cells.

3 Demonstrate Nokia LTE BTS commissioning via WebEM for the optional Antenna Line Device,
RF sharing, and Passive Devices.

C O NT I NU E
Lesson 3 of 10

Dene the Baseband Modules

This lesson describes the definition of baseband resource in Nokia AirScale LTE BTS. The related tasks in
the Configuration Wizard are:

Baseband Module

Baseband Module Settings

Baseband Module Link Configuration

Baseband Module eCPRI Transport Configuration

Baseband Module SFP Controller

Ethernet Service OAM

Operation Demonstration
This video demos the steps of Configuration Wizard in this lesson. If you might want to take notes, the
steps are also described in text and screenshots after the video.
Video Narration - 1 - Baseband Module ► Baseband Module Settings
–
The step "Baseband Module ► Baseband Module Settings" defines the Capacity Modules in the BTS.

To add the required baseband module, select the module type in the "Add BBMOD" drop-down menu,
for example, ABIA, ABIC, ABIN, or ABIO. Capacity Modules' variants in the drop-down list depend on the
Common Unit (or Units) used in this BTS, and the Site Composition Rules. For instance, with ASIA, we can
add ABIA; with ASIB, we can add ABIA, ABIN, or ABIO.
If your Common Unit is ASIL, here we can also add ABIA, ABIN, or ABIO.
ASIB can also take ABIC. Then due to some site composition rules, the other Capacity Units in this BTS can
only be ABIC or ABIA.

Then, expand the boxes for the added modules to configure them.

The “BB pools used per BB card” can be 0, 1, or 2.

If set to '0', a given baseband card is not used to host any baseband pools. All cells connected to a
given baseband card are in operational state 'disabled'.

If set to '1', only one baseband pool is used for a given baseband card. All cells connected to a given
baseband card are allocated to one baseband pool.

If set to '2', then two baseband pools are used for a given baseband card. Cells being served by
radios connected to a given baseband card are distributed to two baseband pools.
The “Radio protocol search order” parameter allows the operator to define the starting protocol for
radio detection between OBSAI and CPRI variants.
When this parameter is set, the BBMOD will start the radio protocol detection algorithm with the
specified protocol, on the first startup, or following upgrade activation, of that module. If this parameter
is not specified, the BTS will still automatically detect the type of radio protocols in use.

If "Full BB capacity in use" is checked, 100% of Baseband Module capacity is enabled. If not, only 50% of
Baseband Module capacity is enabled, and the other remaining BB capacity (50%) stays disabled.

The "Baseband pool size LTE" parameter defines the desired size of a single baseband pool instance
serving for LTE. For the ABIO and ABIN units, which are capable of multiple Radio Access Technologies,
this parameter is used only when LTE uses the card exclusively.

The "Baseband card board configuration type" choice is introduced as some variants of Capacity Units
are capable of mixed Radio Access Technologies. This option is used for BB module "board
configuration" selection, which allows for corresponding cell processing. Default value 'Auto' means that
BBMOD supports only a single RAT with a single duplex. For Capacity Units ABIO and ABIN, this parameter
is mandatory. For the other types, this parameter cannot exist.

The module position can be bottom, middle, and top. For a newly added module, we can set this value.
But for an installed module, its position is detected from the BTS and not configurable. We can recognize
a detected module from the green virtual LED on its box.

Let’s come back to our example BTS and move on.

NEXT.
[Please switch to the next tab to continue.]

Video Narration - 2 - Baseband Module ►Baseband Module Link Conguration

–
The step "Baseband Module Link Configuration" does not apply to the AirScale product family. We don’t
need to do anything here.

Next.
[Please switch to the next tab to continue.]

Video Narration - 3 - Baseband Module ►Baseband Module eCPRI Transport

Conguration
–
The step "Baseband Module eCPRI Transport Configuration" only applies to the Capacity Units that
support the eCPRI fronthaul protocol. It chooses the S-RF interface to be used for the fronthaul Ethernet
connection.

If the BTS does not use the eCPRI protocol for the fronthaul connection, we just leave the table empty.
Next.
[Please switch to the next tab to continue.]

Video Narration - 4 - Baseband Module ►Baseband Module SFP Controller

–
The step "Baseband Module SFP Controller" is optional. It allows controlling the administrative state of
SFP modules connected to the Capacity Module used in connection with Radio Units.

We may add the SFP we want to manage in this step, choose the port where it is inserted, and add a lane.
Then, the lane’s administrative state can be configured.

This step is optional. If we do not want to manage the administrative state of any SFP or QSFP on the
Capacity Unit for RU connection, we can leave the table empty and move on to the next step.

[Please switch to the next tab to continue.]

Video Narration - - Baseband Module ►

–
The step "Ethernet Service OAM" is optional.

This step will only be available when at least one eCPRI RF port is configured in the BTS.

So, if you have one or more RF ports using eCPRI, the configuration for this step will display.
It allows to run the Connectivity check in the C-Plane and U-Plane using O-RAN defined ethernet OAM CFM
Loopback.
But this feature currently applies to NR only.

So, we will not make settings in this step.

This is the last step for the Capacity Modules configuration and the digital part of the BTS.
Next, we will move to the radio part.
 2

Steps Description
Here are the same operation steps described with text and screenshots.

1 Baseband Module ► Baseband Module Settings

The step "Baseband Module ► Baseband Module Settings" only works in offline mode. The HWs are
detected automatically in online mode.

To add the required baseband module in offline mode, select the module type in the "Add BBMOD" drop-
down menu. Click "Next" when all planned BB modules are added.

Capacity Module options in the "Add BBMOD" drop-down list depend on the AirScale BTS Site
Composition Rules and the Common Unit(s) selected for this BTS (in the "System Module
Configuration" step).
 Step - Baseband Module - Baseband Module Settings: BBMOD available options rely on the
SMOD variant

Step - Baseband Module Settings - BBMOD for dual-SMODs.

An explanation of the parameters is provided below.

BB pools used per BB card
–

If set to '0', a given baseband card is not used to host any baseband pools. All cells connected to a
given baseband card are in operational state 'disabled';

If set to '1', only one baseband pool is used for a given baseband card. All cells connected to a given
baseband card are allocated to one baseband pool.

If set to '2', then two baseband pools are used for a given baseband card. Cells being served by
radios connected to a given baseband card are distributed to two baseband pools.

Radio protocol search order

–

This parameter allows the operator to define the starting protocol for radio detection between
OBSAI and CPRI variants.

When this parameter is set, the BBMOD will start the radio protocol detection algorithm with the
specified protocol on the first startup or following upgrade activation of that module. This
parameter can reduce the radio detection time in configurations where the Operator knows the
type of radio deployment. If this parameter is not specified, the BTS will still automatically detect
the type of radio protocols in use. However, it may take longer to detect the radios for certain
exceptional cases. In this scenario, the BTS will attempt to use prior radio detection information to
select the starting point for protocol searches.

Full BB capacity in use

–

If set to ‘true,’ the full BB capacity (100% of Baseband Module capacity) is enabled.

If set to ‘false,’ the basic BB capacity (50% of Baseband Module capacity) is enabled, and the other
remaining BB capacity (50%) stays disabled.
Baseband pool size LTE
–
This defines the desired size of a single baseband pool instance serving for LTE.
For the ABIO and ABIN units, which are capable of multiple Radio Access Technologies, this parameter is
used only when LTE uses the card exclusively.

Baseband card board conguration type

–
This choice is introduced as some variants of Capacity Units are capable of mixed Radio Access
Technologies.
This option is used for BB module "board configuration" selection, which allows for corresponding cell
processing:

Auto (default)

LTEFDD

LTETDD

NRFDD

NRTDD

LTEFDD_LTETDD

NRFDD_NRTDD

LTEFDD_NRFDD

LTETDD_NRTDD

LTETDD_NRFDD

LTEFDD_NRTDD

Default value 'Auto' means that BBMOD supports only a single RAT with a single duplex.

For Capacity Units ABIO and ABIN, this parameter is mandatory. For the other types, this parameter
cannot exist.
One Thing More: Commissioned or Detected?

Commissioned Module v.s. Detected Module

Commissioned Module v.s. Detected Module

00:57

Commissioned or Detected?
Narration - Commissioned or Detected?
–
Sometimes the upright corner of the BB module configuration box shows a green virtual LED next to a
grey trash bin icon. Sometimes it only shows a black trash bin icon.
The different states of the module cause the difference. Please click the "+" marks in the accordion below
to find the meaning of each state.

The green dot means the board is successfully detected by BTS software.

The trash bin icon removes the module.

This way only works before the module is physically detected. For example, a module just
declared in the commissioning wizard can be removed in this way.

A module that carries a green virtual LED can not be removed in this way, so the trash bin icon
is greyed out.

Maybe you'll also meet a "wrench" icon next to the green virtual LED or an "+" icon in some other
case. That wrench icon means the module needs your action. For example, a module is just physically
inserted into the BTS but not yet logically provisioned, and then it will show that wrench icon.

2 Baseband Module ► Baseband Module Link

Configuration

The step "Baseband Module ► Baseband Module Link Configuration" does not apply to the AirScale
product family.
 Step - Baseband Module - Baseband Module Link Configuration: BBMOD links (toward the
Common Units) are not used for AirScale family.

3 Baseband Module ► Baseband Module eCPRI

Transport Configuration

In step "Baseband Module ► Baseband Module eCPRI Transport Configuration", select the S-RF interface
to be used for fronthaul Ethernet connection and click "Next".

For ABIC, you can also define if VLAN should be used. If you mark the VLAN Usage checkbox, fill in the
VLAN ID field.

Note: This step applies only to the Capacity PiUs that support the eCPRI fronthaul protocol.
 Step - Baseband Module - Baseband Module eCPRI Transport Configuration

4 Baseband Module ► Baseband Module SFP

Controller

The step "Baseband Module ► Baseband Module SFP Controller" is optional.

If QSFP is used, click "Add SFP" and choose the "HW port identifier" to indicate where the [Q]SFP module is
inserted.
 Step - Baseband Module - Baseband Module SFP Controller

5 Baseband Module ► Ethernet Service OAM

The step "Baseband Module ► Ethernet Service OAM" is optional.

The function introduces connectivity check in the C/U-Plane using O-RAN defined eth OAM CFM Loopback.
The Loopback message allows supervising an ethernet network, via connectivity fault detection or
verification and isolation.

It only applies to classical gNB in the current release. The configuration is only effective for the eCPRI
fronthaul ports serving NR cells. We will include its details when this function extends to LTE.

Step - Baseband Module - Ethernet Service OAM

 Step - Baseband Module - Ethernet Service OAM

This lesson introduced the steps related to Capacity Plug-in Units configuration, or say baseband
modules, In WebEM Configuration Wizard.

The next lesson will introduce the insertion of the optional Front Haul Switch (FHS) Modules for the BTS.

You may click this button to jump over to the lesson after that to see how to add Radio Modules for the
BTS.

Dene the Radio Modules

Click the button to jump over to the lesson for Radio Modules.

RADIO MODULES

C O NT I NU E
Lesson 4 of 10

Dene the Fronthaul Switch (optional)

This lesson introduces the tasks related to Fronthaul Switch in the Configuration Wizard. FHS is optional in
the BTS, so are all these steps:

FHS Module

FHS Module Settings

FHS Link Configuration

FHS EAC Configuration

Background of Fronthaul Switch (FHS)

 Fronthaul Switch (FHS) between the baseband and the radio units

00:36

Background Story: Fronthaul Switch (FHS)

Narration - Background Story: Fronthaul Switch (FHS)

–
Fronthaul Switch is an optional module providing a hub/switching functionality at the interface between
Nokia AirScale System Module and several RF Modules or RRHs.
Front Haul Switch (FHS) works only for AirScale System Module with at least one ABIA.

FHS is seen as an additional node in radio networks providing radio interface connectivity
functionalities without radio functionality.

FHS is controlled like a remote radio head with connectivity functions and without radio
functionality.

Additional functionalities can be added on top of the connectivity functions, e.g., delay adjustment,
compressions, etc.
 2

Operation Demonstration
This video demos the steps of Configuration Wizard in this lesson. If you might want to take notes, the
steps are also described in text and screenshots after the video.

Video Narration - 1 - FHS Module ► FHS Module Settings

–
The step "FHS Module ► FHS Module Settings" defines the optional module, Fronthaul Switch, which works
like a hub/switching between the Nokia AirScale System Module and several RF Modules or RRHs.

To add an FHS, select the planned variant from the "Select FHS module" dropdown menu, and check its
setting in the appeared box.
More than one FHS is allowed in the BTS. The added Fronthaul Switches are listed in the table below.

The following two steps will be activated when at least one FHS is added in this step. Let’s keep an FHS in
this step and see what is required in the next two steps.

Next.
[Please switch to the next tab to continue.]

Video Narration - 2 - FHS Module ► FHS Link Conguration

–
The step "FHS Link Configuration" is available only when FHS was added in the previous step, "FHS
Module Settings". This step configures the connections of FHS.

The upper box defines the FHS connection to the digital part. For each used FHS interface, select its
connected BBMOD and port.

The lower box defines the FHS connection to the Radio Modules. For each used FHS interface, select its
connected Radio Module and port.
The options will be available when Radio Modules are added. Or in the online mode, the connection will
be detected automatically.

NexT.
[Please switch to the next tab to continue.]

Video Narration - 3 - FHS Module ► FHS EAC Conguration

–
The step "FHS EAC Configuration" is available only when FHS was added in the previous step, "FHS
Module Settings". This step is optional.

To configure the FHS module external fault and control sets, click "+" and provide the settings. If you
don’t use EAC on FHS, leave the tables alone.

This is the last step for the configuration of the Fronthaul Switch. As we do not really have it in our
example BTS, let’s go back to remove it.
Again, the whole group of FHS configurations is optional. If you don’t use it in your BTS, you don’t need to
do anything in these steps.
Next, we will go to define the Radio Modules.

Steps Description
Here are the same operation steps described with text and screenshots.

1 FHS Module ► FHS Module Settings

The step "FHS Module ► FHS Module Settings" is optional.

To add FHS, select the planned variant from the "Select FHS module" dropdown menu, and then click
"Next".

The following two steps will be activated when at least one FHS is added in this step.
 Step - FHS Module - FHS Module Settings

2 FHS Module ► FHS Link Configuration

The step "FHS Module ► FHS Link Configuration" is available only when FHS was added in the previous
step, "FHS Module ► FHS Module Settings".

Configure the connections between FHS and the baseband module, and then click "Next".
 Step - FHS Module - FHS Link Configuratiion

The explanation of the parameters is provided below.

FHS-BBMOD Link Conguration

–

Module: This is the first endpoint distinguished name. The parameter describes the distinguished
name of the connected Module. It must point to one of the following objects: SMOD, BBMOD,
RMOD, FHS, ASIRMOD, SMOD_EXT.

Module Port ID: This is the first endpoint port identifier. The parameter contains the first endpoint
port identifier.

Link Speed: This parameter defines the speed between the system module/baseband module and
the first radio module/FHS. It should be set only for OBSAI/CPRI/eCPRI links.
Speed limitation is based on the modules and SFP hardware variants.

IQ Compression: This parameter describes if IQ compression is used for related cable. The
parameter can be set only for CPRI and eCPRI links.
FHS-RMOD Link Conguration
–

Module: This is the second endpoint distinguished name. The parameter describes the distinguished
name of the connected Module.

Module Port ID: This is the second endpoint port identifier. The parameter contains the second
endpoint port identifier. For better resiliency, if two ABIAs are connected to the same FHS, it is
better to connect ports 1,2, to two separate ABIAs.

Link Speed: This parameter defines the speed between the FHS and a radio module. It should be set
only for OBSAI/CPRI/eCPRI links.
Speed limitation is based on the modules and SFP hardware variants.

IQ Compression: This parameter describes if IQ compression is used for related cable. The
parameter can be set only for CPRI and eCPRI links.

3 FHS Module ► FHS EAC Configuration

The step "FHS Module ► FHS EAC Configuration" is available only when FHS was added in the previous
step, "FHS Module ► FHS Module Settings". This step is optional.

To configure the FHS module external fault and control settings, click "+" and provide the settings, and
then click "Next".
 Step - FHS Module - FHS EAC Configuratiion

This lesson introduced the steps related to the optional FHS Modules configuration.

The next lesson will introduce how to add Radio Modules for the BTS.

C O NT I NU E
Lesson 5 of 10

Dene the Radio Modules

This lesson introduces the tasks related to the Radio Module in the Configuration Wizard of WebEM. They
are:

Radio Module

Radio Module Settings

Radio Module Link Configuration

Antenna Line Management

Antenna Line Settings

EAC Configuration

Synchronization

Operation Demonstration
This video demos the steps of Configuration Wizard in this lesson. If you might want to take notes, the
steps are also described in text and screenshots after the video.
Video Narration - 1 - Radio Module ► Radio Module Settings
–
In step "Radio Module ► Radio Module Settings", select the planned radio module type in the "Add
RMOD" dropdown menu and provide its basic settings.

The "Abnormal memory threshold" parameter defines the abnormal memory threshold on the radio
module. When the memory consumption on the radio module exceeds the abnormal threshold, an alarm
with fault "Radio memory consumption exceeds abnormal threshold" is raised. So, the operator may
know the trend of memory shortage before it really used out. This parameter is defined as a relative
value, where the lower bound value of 0% indicates the expected average memory consumption. The
default value is 50%.

The "link Speed" parameter defines the desired optical link speed on the port of a radio module used to
connect to the next radio module in a chain. It's not the data rate toward the digital part.
By default, it's set to "Auto", which means the BTS takes into use the highest line rate supported by HW
and SW capabilities.

Click Next when all expected radio modules are added.

[Please switch to the next tab to continue.]

Video Narration - 2 - Radio Module ► Radio Module Link Conguration
–
In step "Radio Module Link Configuration", verify or configure the radio modules' links.

Each configuration box on this page represents a Capacity Module, and each row in its table represents a
fronthaul port. If an RF port on a Capacity Module is used, the connected Radio Module and port are
specified in the row. To change the setting, delete the row and choose the peer point again.

In online mode, the connected peering points are detected from the BTS, and thus, not configurable.

Let's come back to our example site and move on.

Next.
[Please switch to the next tab to continue.]

Video Narration - 3 - Radio Module ► Antenna Line Management

–
The step "Antenna Line Management" is optional. DC power and AISG communication are required to
operate the connected antenna line devices or to detect them in the future.

Verify the configuration and modify if necessary.

The "3GPP/AISG communication" column defines if communication with AISG-compliant devices is enabled
or disabled for an antenna line.

The “DC Voltage level” can be OFF, LOW, HIGH, or AUTO. This column defines the voltage level supplied to
the antenna line.

The feature flag "SW update for antenna line devices in use" chooses whether to enable or disable the
monitoring for ALD software management.

The feature flag "MHA auto-configuration in use" chooses whether to activate the MHA auto-
configuration function. When the function is activated, there is no need to include MHAs manually in the
plan file.

Next.
[Please switch to the next tab to continue.]
Video Narration - 4 - Radio Module ► Antenna Line Settings
–
In step "Antenna Line Settings", verify the configuration for the Antenna Line to each port on the radio
modules.

The VSWR alarm thresholds parameter defines the VSWR (voltage standing wave ratio) Minor and Major
alarm levels.
The occurrence of the VSWR Major fault will block all the associated cells.
The default threshold for VSWR minor fault is 1 point 9. And that for VSWR major fault is 2 point 6.

If you agree with the default thresholds, you don’t need to do anything in this step.

Next.
[Please switch to the next tab to continue.]

Video Narration - 5 - Radio Module ► EAC Conguration

–
The step " EAC Configuration" is optional.

To add External fault lines and External control lines, click "+" and give the settings. If there is no EAC used
on the Radio Module, we just leave the tables empty.

Next.
[Please switch to the next tab to continue.]

Video Narration - 6 - Radio Module ► Synchronization

–
The step "Radio Module ► Synchronization" is optional. It is tended for the eCPRI Radio Modules. Each
eCPRI Radio Module will need a sync configuration.
If you don’t have any eCPRI Radio Module in your BTS, you don’t need to do anything in this step.

Let's assume that we have a radio module using the eCPRI fronthaul. We would configure the RF port and
connect the Radio Module to the RF port.
It's possible to see some warning here. Don't worry, it's reminding us to define the synchronization object
for this Radio Module.

Let's go to the Synchronization step to configure it.

To define the synchronization for an eCPRI Radio Module, click the "Add Synchronization" button and set
the parameters.

Mark the tended Radio Module in the "Sync slave radio list".
And go down a little bit to configure its corresponding TOPP object.
Provide the settings as planned.
And set the Time zone.

This is the last step in the configuration of the Radio Modules. Next, we will move on to the cells.

Steps Description
Here are the same operation steps described with text and screenshots.

1 Radio Module ► Radio Module Settings

In step "Radio Module ► Radio Module Settings", select the planned radio module type in the "Add RMOD"
dropdown menu and provide its basic settings.

Click "Next" when all expected radio modules are added.

 step - Radio Module ► Radio Module Settings

The explanation of the parameters is provided below.

Climate control prole

–
This climate control profiling parameter only applies to certain radio module types. It defines fan speed
will be controlled according to module temperature and desired BTS fan profile.

Abnormal memory threshold

–
This parameter defines the abnormal memory threshold on the radio module. When the memory
consumption on the radio module exceeds the abnormal threshold, an alarm with fault ‘Radio memory
consumption exceeds abnormal threshold’ is raised.
Link speed
–
This link Speed parameter defines the desired optical link speed on the port of a radio module used to
connect to the next radio module in a chain.
This parameter can be set only for radio modules that have HW support for that speed. Usually, the
default value "Auto" is an optimal selection for all configurations.

Optional fans installed

–
Parameter defines whether optional FAN modules e.g. FMND are installed in RF Unit.

When parameter is set to true, then BTS expects that optional FAN modules are installed in RF unit. Fault
1932 "No module fan detected" is raised at RF unit startup when optional FANs are configured but not
detected.

2 Radio Module ► Radio Module Link Configuration

In step "Radio Module ► Radio Module Link Configuration", verify or configure the radio modules' links,
then click "Next".
 step - Radio Module ► Radio Module Link Configuration

3 Radio Module ► Antenna Line Management

The step "Radio Module ► Antenna Line Management" is optional. DC power and AISG communication are
required to operate currently connected or detect antenna line devices added in the future. For un-
commissioned eNBs, both the AISG communication and DC power (24V) are active on all supporting ports.

To configure antenna line device support, verify the configuration. Then click "Next".

step - Radio Module ► Antenna Line Management

The explanation of the parameters is provided below.

3GPP/AISG communication
–

Defines if communication with AISG compliant devices is enabled/disabled for an antenna line.

For antenna lines to which Antenna Line Devices (ALDs) are connected, mark the check-box to
enable 3GPP/AISG communication.
DC voltage level
–

Defines the voltage level supplied to the antenna line. If an MHA device is on the line, the values
entered for this parameter depend on the MHA type.

Non-AISG NSN MHAs: WMHA, WMHB: LOW; WMHC: BTS1 AUTO, BTS2 LOW

Non-AISG Other (3rd party) MHA: OFF (The user can change the line voltage to LOW)

AISG MHAs: Currently, for all AISG MHA AUTO value is used.

If there is ALD connected to the antenna line, change the DC voltage level value from OFF to AUTO,
LOW, or HIGH. If ALD is connected to RET port, set the DC voltage level to true.

If no MHA is present, then DC power shall turn off to reduce the power consumption of the eNB.

SW update for antenna line devices in use

–
This is a feature flag to enable or disable monitoring for ALD software management.

MHA auto-conguration in use

–
This flag activates the MHA auto-configuration function when it's set to true. When MHA auto-
configuration is activated, there is no need to include MHAs manually in the plan file. The BTS shall
support the auto-configuration of the MHAs with the following conditions:

MHA supports AISG 2.0,

MHA does not have any LNA marked as external,

MHA is a single band,

MHA is used with 2 LNAs,

MHA is connected to a shared radio, and BTS is the master.

 4 Radio Module ► Antenna Line Settings

In step "Radio Module ► Antenna Line Settings", verify the configuration, and then click "Next".

step - Radio Module ► Antenna Line Settings

The explanation of the parameters is provided below.

VSWR minor fault

–

This VSWR alarm threshold parameter defines a VSWR (voltage standing wave ratio) minor alarm
level. Radio module/RRH rel. 4 shall use the restricted range 1.5 - 2.9. (If ANTL is connected to a
radio with cpriARfSharing set to SECONDARY, VSWR alarms cannot be set.)

VSWR minor fault = 1.9

VSWR major fault
–

This VSWR alarm threshold parameter defines a VSWR (voltage standing wave ratio) major alarm
level. Radio module/RRH rel. 4 shall use the restricted range 2.7 - 3.5. (If ANTL is connected to a
radio with cpriARfSharing set to SECONDARY, VSWR alarms cannot be set.)

VSWR major fault = 2.6

The occurrence of the VSWR major fault will block all the associated cells.

Total loss
–
This parameter contains the total loss.

RTT delay in uplink/downlink path

–

RTT delay in uplink path: The sum of signal delays between antenna port on Radio Module and
antenna device port in the uplink direction

RTT delay in download path: The sum of signal delays between antenna port on Radio Module and
antenna device port in the downlink direction

Uplink delay
–
This parameter defines the Antenna Line Uplink Delay in nanoseconds. It compensates for the antenna
line UL delay difference between main and diverse Rx branches of the cell. This is needed to avoid gain
(i.e., performance) loss due to the time difference between Rx branches' data.
 5 Radio Module ► EAC Configuration

The step "Radio Module ► EAC Configuration" is optional.

To add External fault lines and External control lines, click "+" and give the settings. Then click "Next".

step - Radio Module ► EAC Configuration

6 Radio Module ► Synchronization

The step "Radio Module ► Synchronization" is optional. It applies to the eCPRI Radio Modules. Each eCPRI
Radio Module must have a sync configuration.

To define the synchronization for an eCPRI Radio Module, click the “Add Synchronization” button and set
the parameters. Mark the tended Radio Module in the “Sync slave radio list”, and configure its
corresponding TOPP object.

step - Radio Module ► Synchronization

The explanation of the parameters is provided below.

Sync slave radio list

–
Every creative endeavor requires that you take risks. If you try and don't succeed, you've still learned
something. It took Thomas Edison more than 10,000 tries to invent a viable lightbulb. You're not failing.
You're discovering what doesn't work.
ToPP parameters
–

ToP standard profile

This parameter is used to select the profile to be used for phase synchronization (Telecom2008,
G.8275.1, G.8275.2, CCSA YD/T 2375). The selection of the profile determines if unicast
(Telecom2008 and G.8275.2) or multicast (G.8275.1 and CCSA YD/T 2375) communication mode is
used, and also determines the range of configurable values for the acceptedClockClass parameter.

Ethernet multicast address

This parameter configures the standard Multicast Ethernet MAC address to be used as the
destination address in Timing over Packet Ethernet frames sent by the BTS.

Accepted clock classes

This parameter indicates the accepted clock classes.
The allowed values represent the Telecom2008, ITU-T G.8275.1, ITU-T G.8275.2, CCSA YD/T 2375
defined clock classes applicable to clocks related to phase/time synchronization, and which a
boundary clock might use in case it loses traceability to the original grandmaster clock.
Note: When phase/time synchronizing a BTS by a ToP master using an arbitrary time scale (CC 13,
14, 58, 193, 248), the System Frame Numbers generated by that BTS will not be aligned with BTSs
synchronized by other ToP masters or GNSS receivers.

ToP domain number

This parameter selects the ToP domain number the BTS integrated slave clock belongs to.

This lesson introduced the steps related to Radio Modules configuration.

The next lesson will introduce the operation to declare wideband (legacy) LTE-FDD and LTE-TDD cells.
C O NT I NU E
Lesson 6 of 10

Dene the LTE FDD and TDD Cells

This lesson introduces the tasks related to Cells Configuration in the Configuration Wizard. They are:

Cells Configuration

Cell Parameter Restriction Configuration

LTE FDD

Basic Cell Settings

Cell Carriers

LTE TDD

Basic Cell Settings

Cell Carriers

NB-IoT cells' set-up tasks are covered in another lesson.

Operation Demonstration
This video demos the steps of Configuration Wizard in this lesson. If you might want to take notes, the
steps are also described in text and screenshots after the video.
Video Narration - 1 - Cells Conguration
–
The "Cells Configuration" task group provides the fundamental setting for not only LTE cells, but also NR,
WCDMA, and GSM cells now, as a consequence of the harmonized Single RAN BTS configuration model. We
focus on the LTE cells in this course. So, this video will introduce the settings of the LTE FDD and LTE TDD
cells, and leave the other steps aside.

The step “Cell Parameter Restriction Configuration” applies to all the cells in the BTS. The step will be
available when at least one cell is declared in the BTS. Now the example BTS has no cell, so it is greyed
out. We will come back to see its configuration after we create the cells.

[Please switch to the next tab to continue.]

Video Narration - 2 - Cells Conguration ► LTE FDD ► Basic Cell Settings

–
The step "Cells Configuration ► LTE FDD ► Basic Cell Settings" declares the LTE FDD cells for the BTS. If
your site works with TDD only, please jump to the "Basic Cell Setting" step for LTE TDD.

Our example BTS has both LTE FDD and TDD cells, so that I will fill both steps.
This step sets up the very basic objects and parameters for the LTE FDD cells. We provide some
fundamental data here and probably will need to provide more in the Configuration tree for the specific
features we want for the cells. We will introduce the data setting operation with the Parameter Editor tool
in another lesson.

To add a new LTE FDD cell, click the "Add LTE FDD cell" button. A new configuration box shows up with the
cell's basic settings.

Then, fill in the mandatory parameters according to your data plan. The parameters here are either
essential in network management or crucial in the cell's telecommunication function.

The parameter "Cell ID" is the instance identifier of the object LNCEL in the BTS configuration, which is
used only for O&M purposes.
The "Local cell resource ID" is the ID of the Local Cell Resource. The value for each cell shall be unique in
the eNB.
And the "Cell name" allows the operator to give a cell a unique name. We don't need it in our lab, so leave
it empty.

"Specific cell configuration" defines if the cell works with specific features of Supercell, Combined
SuperCell, or Massive MIMO. Corresponding antenna mapping settings are required, and furthers detailed
settings should be provided in the Parameter Editor. The example cells are normal, so we leave it with the
default value, "None".
Then with "MIMO mode", we choose the transmission mode of the cell.

"Physical layer cell ID", also known as PCI, is an essential value to identify the cell on the air interface. We all
know how important it is to the cell. Fill in the value carefully according to your data plan.
"Tracking area code" identifies the cell's tracking area. Copy from your data plan.

"PRACH frequency offset" defines the location in frequency for the PRACH transmissions. Due to the
characteristic of the LTE UL resource allocation scheme, it is recommended to set the value such that
PRACH does not overlap with the PUCCH RBs, and locates adjacent to PUCCH.
"RACH root sequence" is the number pointing to a root sequence to generate the preambles for the cell.
If one root is not enough to generate all the 64 preambles, the consecutive number is selected until the
whole set is generated. RACH root sequence is cell-specific, and neighboring cells should have a different
value. Fill in the values according to your data plan.

Again, this small set of parameters only sets up a fundamental structure of the cell. We still need a lot of
more detailed settings in the BTS configuration tree. We may later do it in the Parameter Editor. That's
also why we may move on even with yellow warning tags in the wizard.

Here we keep going with the settings on this page.

An LTE FDD cell may work with an NR cell in Dynamic Spectrum Sharing. If it does, choose the sharing
mode and the associated NR cell. Again, here we only set the fundamental points for the cell. There are a
lot of other details required to make this feature work.

Then, map the radio antenna ports to the cell. This setting should match the radio plan and the physical
cable connection. WebEM will also check if the choice matches the specific configuration choice and MIMO
mode choice above. Choose the module, port, and direction carefully according to your plan.

At the bottom of the configuration box, we can see the choice to set up an NB-IoT inband or guardband
cell. We will introduce that in another lesson.

Repeat the procedure until all the planned cells are added. And move on to the next step.

Next.
[Please switch to the next tab to continue.]

Video Narration - 3 - Cells Conguration ► LTE FDD ► Cell Carriers

–
In step "Cell Carriers", continue the cell setting with the Bandwidth, DL EARFCN, and Cell power [dBm] for
every cell. We will not review the LTE radio technology here, but I believe we all understand these are basic
cell settings. Make sure you follow your data plan strictly.

Do this for all the added cells, and then move on.

Now we've set up the very basic objects and parameters for the LTE FDD cells. More details are to be
filled in later. But in the wizard, the cell creation is done now.

If your site has FDD cells only, please jump over the next two steps for the LTE TDD cell creation. Also, if
your site has no LTE Standalone NB IoT cells, please hop over those steps too.
In our example BTS, we have both LTE FDD and TDD cells, so, I'm going to the next step to declare the LTE
TDD cells.

Next.
[Please switch to the next tab to continue.]

Video Narration - 4 - Cells Conguration ► LTE TDD ► Basic Cell Settings

–
The step "Cells Configuration ► LTE TDD ► Basic Cell Settings" declares the LTE TDD cells for the BTS. As
for the LTE FDD cells, only basic LTE TDD cell settings are asked here; further works are waiting in later
steps and other tools.

The operation here is almost the same as it for the LTE FDD cells.
First, to add a new LTE TDD cell, click the "Add LTE TDD cell" button. Then, fill in the mandatory
parameters in the box according to your data plan.

The "Cell ID" and "Local cell resource ID" are used for management purposes to identify the configuration
objects of the logical cell and physical resource. The "Cell Name" helps the operators to recognize the
cell.

If the cell uses Massive MIMO, set it in the "Specific cell configuration" and select a profile and the antenna
array mode.

Choose the MIMO mode.

And fill in the cell's PCI, TAC, and PRACH frequency offset.

Then map the cell to the radio module, antenna ports.

Again, only key settings are made here, so it's normal to see warning tags when creating new cells. Some
missing data will be set in the later steps; more others will be fixed with the Parameter Editor.

Next.
[Please switch to the next tab to continue.]

Video Narration - 5 - Cells Conguration ► LTE TDD ► Cell Carriers

–
In step "Cell Carriers", continue the cell setting with the Bandwidth, EARFCN, and Cell power [dBm] for
every cell. Please follow your data plan strictly.

Do this for all the added cells, and then move on.

With this step, we have created the LTE TDD cells for the BTS.

Now let's go back to the "Cell Parameter Restriction Configuration" step.

[Please switch to the next tab to continue.]

Video Narration - 6 - Cells Conguration ►Cell Parameter Restriction Conguration

–
The task is accessible now, and we can see the cells in the dropdown list on the left side.
This list is for us to choose the cells we want to apply the parameter access restriction function. If we do
not make a choice here, BTS will apply the restriction to all the cells.

To make the function work, we also need to tell the BTS which parameters in the selected cells are
protected. To do so, we choose the tended parameters from the dropdown list on the right side.
If this configuration is later sent to BTS, it will raise an alarm when someone modifies any of these
parameters and rejects the operation.
In our example BTS, I’m not tended to restrict parameter modification. In this case, we just leave the
"restricted parameters" list empty.

Now we have set up the LTE cells' essential settings.

The following two steps create Standalone NB IoT cells. If you don’t have them on your site, please jump
over to the later steps.

Steps Description
Here are the same operation steps described with text and screenshots.

1 Cells Configuration ► Cell Parameter Restriction

Configuration

The step "Cells Configuration ► Cell Parameter Restriction Configuration" is optional. It is available when
the BTS has at least one cell.
To configure the Parameter restrict rules, select the cells from the "Restricted cells" list, and the
parameters from the "Restricted parameters" list, and then click "Next".

The selected parameters of the selected cells are protected. When someone modifies them, the BTS will
reject the change and raise an alarm.

step - Cells Configuration ► Cell Parameter Restriction Configuration

2 Cells Configuration ► LTE FDD ► Basic Cell Settings

In step "Cells Configuration ► LTE FDD ► Basic Cell Settings", configure the cells as the following sub-steps,
and then click "Next".

1. Click the "Add LTE FDD cell" button,

2. Fill in the mandatory parameters.

3. Choose the radio module and configure its connection with the cell.
 step - Cells Configuration ► LTE FDD ► Basic Cell Settings

The explanation of the parameters is provided below.

Cell ID, Local cell resource ID, and Cell name

–

Cell ID: Instance identifier of the object LNCEL. This parameter is used only for O&M purposes.
Range: 0...65535
 Local cell resource ID: ID of the Local Cell Resource. The value for each cell shall be unique in the
eNB. Note: This parameter is used in the NB-IoT cell also.
Range: 0...255

Cell name: This parameter allows the operator to give a cell a unique name.

Specic cell conguration

–
This parameter defines if the Radio Module support:

Supercell

Combined Super Cell

Massive MIMO

Massive MIMO horizontal sector beamforming prole

–

This parameter specifies massive MIMO horizontal sector beamforming profile:

SingleSectorBFProf(0 degree)

DualSectorBFProf(-30 degree)

DualSectorBFProf(+30 degree)

If actMMimo is 'true', mMimoHorizontalSectorBFProf must be configured.

MIMO mode
–
Cell-specific downlink transmission/MIMO mode. The used DL MIMO mode for each physical channel
is the following:

Single TX: Single Stream Downlink: All downlink physical channels are transmitted using this
mode;

TXDiv: Single Stream Downlink Transmit Diversity for two antennas using Transmission Mode 2.

4-way TXDiv: Single Stream Downlink Transmit Diversity for four antennas using Transmission
Mode 2.

Dynamic Open Loop MIMO (2x): Dynamic Open Loop MIMO: SRB1 (DCCH) and RBs(DTCH) on
PDSCH are transmitted using either Single Stream Downlink Transmit Diversity or Dual Stream
MIMO with spatial multiplexing depending on radio conditions; SRB0(CCCH), BCCH and PCCH
on PDSCH and all other physical channels are transmitted using Single Stream Downlink
Transmit Diversity.

Closed Loop Mimo: Dynamic Closed-Loop MIMO: SRB1 (DCCH) and RBs(DTCH) on PDSCH are
transmitted using either Single Stream Downlink Transmit Diversity or Single or Dual Stream
MIMO with Closed Loop spatial multiplexing depending on radio conditions and UE category;
SRB0 (CCCH), BCCH and PCCH on PDSCH and all other physical channels are transmitted using
Single Stream Downlink Transmit Diversity.

Closed-Loop MIMO (4x2): Fast Adaptive Closed Loop MIMO4x2: SRB1(DCCH) and RBs(DTCH)
on PDSCH are transmitted using either Single Stream Downlink Transmit Diversity or Single or
Dual Stream MIMO with Closed Loop spatial multiplexing depending on radio conditions and
UE category; SRB0(CCCH), BCCH and PCCH on PDSCH and all other physical channels are
transmitted using Single Stream Downlink Transmit Diversity.

Closed-Loop MIMO (4x4): Fast Adaptive Closed Loop MIMO4x4: SRB1(DCCH) and RBs(DTCH)
on PDSCH are transmitted using either Single Stream Downlink Transmit Diversity or Single or
Dual Stream MIMO with Closed Loop spatial multiplexing depending on radio conditions and
UE category; SRB0(CCCH), BCCH and PCCH on PDSCH and all other physical channels are
transmitted using Single Stream Downlink Transmit Diversity.

Closed-Loop MIMO (8x2): Fast Adaptive Closed Loop MIMO8x2: SRB1(DCCH) and RBs(DTCH)
on PDSCH are transmitted using either Single Stream Downlink Transmit Diversity or Single or
Dual Stream MIMO with Closed Loop spatial multiplexing depending on radio conditions and
UE category; SRB0(CCCH), BCCH and PCCH on PDSCH and all other physical channels are
transmitted using Single Stream Downlink Transmit Diversity.

Closed-Loop MIMO (16x2): Fast Adaptive Closed Loop MIMO16x2: SRB1(DCCH) and
RBs(DTCH) on PDSCH are transmitted using either Single Stream Downlink Transmit Diversity
or Single or Dual Stream MIMO with Closed Loop spatial multiplexing depending on radio
conditions and UE category; SRB0(CCCH), BCCH and PCCH on PDSCH and all other physical
channels are transmitted using Single Stream Downlink Transmit Diversity.
Physical layer cell ID and Tracking area code
–

Physical layer cell ID: Physical layer cell identity defines a cell uniquely. It consists of two parts;
physical layer cell identity group and physical layer identity and is calculated with the following
formula: physical layer cell identity = 3 x physical layer cell identity group + physical layer identity.
Note: This parameter is used in the NB-IoT cell also.

Tracking area code: Identifies the tracking area for this cell. A code that commonly identifies the
tracking area for all PLMNs listed for this cell.

PRACH frequency offset and RACH root sequence

–

PRACH frequency offset: Defines the location in frequency for the PRACH transmissions. It is
recommended to set the value such that PRACH does not overlap with PUCCH RBs and is located
adjacent to PUCCH.

RACH root sequence: The preamble generation starts from the Root Sequence, pointed by the
logical root sequence number. Sixty-four preambles can be transmitted in the PRACH frame.

LTE-NR Dynamic Spectrum Sharing settings

–

LTE-NR dynamic spectrum sharing mode: This parameter specifies the LTE-NR dynamic spectrum
sharing mode. If LteNrDssMode is set to 'none', LTE-NR spectrum sharing is disabled for this cell
The Following options are supported:

None (default) -- no spectrum sharing.

DSS_Phase_I -- pre-defined sharing pattern will be used.

DL_CRS_TDM_UL_FDM -- DSS in DL TDM based with CRS rate matching and DSS in UL FDM
based DSS.

DSS_Phase_III -- improved allocation range and superfast coordination.

 NR cell for dynamic spectrum sharing: Specifies the LNRELGNBCELL instance, which shall be used for
dynamic spectrum sharing with NR.

 The creation and conguration of NB-IoT cells (inband, guardband, and standalone NB-IoT cells)
are described in another course in this circular.

3 Cells Configuration ► LTE FDD ► Cell Carriers

In step "Cells Configuration ► LTE FDD ► Cell Carriers", choose Bandwidth, insert EARFCN and select Cell
power [dBm] for every cell, and then click "Next".
An explanation of the parameters is provided below.

Bandwidth
–
Channel Bandwidth defines the Downlink and Uplink bandwidth for the eNode-B transmission in a cell.
Also, it defines the number of available Physical Resource Blocks which is transmitted in the MIB.

The Channel Bandwidth mapping to Number of Physical Resource Blocks is: 1.4 MHz = 6 PRB; 3.0
MHz = 15 PRB; 5.0 MHz = 25 PRB; 10.0 MHz = 50 PRB; 15.0 MHz = 75 PRB; 20.0 MHz = 100 PRB.

EARFCN
–
E-UTRA Absolute Radio Frequency Channel Number

Cell power [dBm]

–
This parameter defines the maximum output power of the cell per antenna carrier in dBm. The maximum
output power is the maximum value for the linear sum of the power of all downlink physical channels that
are allowed in a cell. The reference point is the antenna connector.

4 Cells Configuration ► LTE TDD ► Basic Cell Settings

In step "Cells Configuration ► LTE TDD ► Basic Cell Settings", configure the cells as the following sub-steps,
and then click "Next".

1. Click the “Add LTE TDD cell” button.

2. Choose the radio module and configure its connection with the cell.

3. Fill in the mandatory parameters.

step - Cells Configuration ► LTE TDD ► Basic Cell Settings

The explanation of the parameters is provided below.

Cell ID, Local cell resource ID and Cell name
–

Cell ID: Instance identifier of the object LNCEL. This parameter is used only for O&M purposes.
Range: 0...65535

Local cell resource ID: ID of the Local Cell Resource. The value for each cell shall be unique in the
eNB. Note: This parameter is used in the NB-IoT cell also.
Range: 0...255

Cell name: This parameter allows the operator to give a cell a unique name.

Specic cell conguration

–

This parameter defines if the Radio Module supports Massive MIMO or not.

Massive MIMO prole name

–

This parameter specifies the profile name of the assigned MMIMOCPR profile or Vendor Specific
profile.

Currently, there are 32 options:

Macro-0 Electrical Tilt-(x), x=-2...8

Highbuilding0

customized profile x, x=1..20

Massive MIMO antenna array mode

–
 Massive MIMO antenna array mode: This parameter indicates the mMIMO antenna array mode on 64
pipes mMIMO MAA.

If set to "0:Full 64TRX Array (4x8x2)", the 64 TRX antennas are connected and configured as:

64 LCELL/CHANNELGROUP/CHANNEL instances with direction value set to 'RX'

64 LCELL/CHANNELGROUP/CHANNEL instances with direction value set to 'TX'

If set to "1:Left 32TRX Array (4x4x2)", or "2:Right 32TRX Array (4x4x2)", or "3:Top 32TRX
Array (2x8x2)", or "4:Bottom 32TRX Array (2x8x2)", the 32 TRX antennas are connected and
configured as:

32 LCELL/CHANNELGROUP/CHANNEL instances with direction value set to 'RX'

32 LCELL/CHANNELGROUP/CHANNEL instances with direction value set to 'TX'

MIMO mode
–
Cell-specific downlink transmission/MIMO mode. The used DL MIMO mode for each physical channel is the
following:

Closed-Loop MIMO (8x2): Fast Adaptive Closed Loop MIMO8x2: SRB1(DCCH) and RBs(DTCH) on
PDSCH are transmitted using either Single Stream Downlink Transmit Diversity or Single or Dual
Stream MIMO with Closed Loop spatial multiplexing depending on radio conditions and UE
category; SRB0(CCCH), BCCH, and PCCH on PDSCH and all other physical channels are transmitted
using Single Stream Downlink Transmit Diversity.

Closed-Loop MIMO (8x4): Fast Adaptive Closed Loop MIMO8x4: SRB1(DCCH) and RBs(DTCH) on
PDSCH are transmitted using either Single Stream Downlink Transmit Diversity or Single or Dual
Stream MIMO with Closed Loop spatial multiplexing depending on radio conditions and UE
category; SRB0(CCCH), BCCH and PCCH on PDSCH, and all other physical channels are transmitted
using Single Stream Downlink Transmit Diversity.

Dynamic Open Loop MIMO: Dynamic Open Loop MIMO: SRB1 (DCCH) and RBs(DTCH) on PDSCH are
transmitted using either Single Stream Downlink Transmit Diversity or Dual Stream MIMO with
spatial multiplexing depending on radio conditions; SRB0(CCCH), BCCH, and PCCH on PDSCH, and
all other physical channels are transmitted using Single Stream Downlink Transmit Diversity.

Single Stream Beamforming: SRB1(DCCH) and RBs(DTCH) on PDSCH are transmitted using Single
Stream Beamforming depending on radio conditions and UE category; SRB0(CCCH), BCCH, and
PCCH on PDSCH, and all other physical channels are transmitted using Single Stream Downlink
Transmit Diversity.
 Dual Stream Beamforming: SRB1(DCCH) and RBs(DTCH) on PDSCH are transmitted using Dual
Stream Beamforming depending on radio conditions and UE category; SRB0(CCCH), BCCH, and
PCCH on PDSCH, and all other physical channels are transmitted using Single Stream Downlink
Transmit Diversity.

Physical layer cell ID and Tracking area code

–

Physical layer cell ID: Physical layer cell identity defines a cell uniquely. It consists of two parts;
physical layer cell identity group and physical layer identity and is calculated with the following
formula: physical layer cell identity = 3 x physical layer cell identity group + physical layer identity.
Note: This parameter is used in the NB-IoT cell also.

Tracking area code: Identifies the tracking area for this cell. A code that commonly identifies the
tracking area for all PLMNs listed for this cell.

PRACH frequency offset

–

PRACH frequency offset: Defines the location in frequency for the PRACH transmissions. For UL
scheduling, it's recommended that PRACH is located next to PUCCH either on the lower or upper
edge of the bandwidth because UL PRB allocation for UE consists of consecutive PRBs. If there is a
small gap between PUCCH and PRACH PRBs, the UL scheduler cannot utilize those PRBs effectively.

5 Cells Configuration ► LTE TDD ► Cell Carriers

In step "Cells Configuration ► LTE TDD ► Cell Carriers", choose Bandwidth, insert EARFCN and select Cell
power [dBm] for every cell, and then Click "Next".

step - Cells Configuration ► LTE TDD ► Cell Carriers

The explanation of the parameters is provided below.

Bandwidth
–
Channel Bandwidth defines the Downlink and Uplink bandwidth for the eNode-B transmission in a cell and
also defines the number of available Physical Resource Blocks which is transmitted in the MIB.

The Channel Bandwidth mapping to Number of Physical Resource Blocks is: 1.4 MHz = 6 PRB; 3.0
MHz = 15 PRB; 5.0 MHz = 25 PRB; 10.0 MHz = 50 PRB; 15.0 MHz = 75 PRB; 20.0 MHz = 100 PRB.

EARFCN
–
E-UTRA Absolute Radio Frequency Channel Number

Cell power [dBm]

–
This parameter defines the maximum output power of the cell per antenna carrier in dBm. The maximum
output power is the maximum value for the linear sum of the power of all downlink physical channels that
are allowed to be used in a cell. The reference point is the antenna connector.

This time we introduced the steps related to LTE-FDD and LTE-TDD cell configuration.

The next lesson will introduce the steps to create the NB-IoT cells.

C O NT I NU E
Lesson 7 of 10

Dene the NB IoT Cells

This lesson introduces the tasks related to Cells Configuration for NB-IoT in the Configuration Wizard.
They are:

Cells Configuration

LTE FDD

Basic Cell Settings

LTE Standalone NB IoT

Basic Cell Settings

Cell Carriers

Why go back to "LTE-FDD cell" step for the setting of NB-IoT cell?
–

For an inband/guardband NB-IoT cell, it needs to be created in its host cell. The creation operation
starts from the button “Add NB-IoT cell” at the bottom of the FDD-LTE cell's configuration box.

A standalone NB-IoT cell is configured in its dedicated step in the wizard, at the same level as the
LTE FDD cell and LTE TDD cell.

We will first introduce the Inband and Guardband NB-IoT cell configuration in their host cell and then
move on to the Standalone NB-IoT cell in its own step.
 1

Operatioin Demonstration
This video demos the steps of Configuration Wizard in this lesson. If you might want to take notes, the
steps are also described in text and screenshots after the video.

Video Narrtion - 1 - Cells Conguration ► LTE Standalone NB IoT ► Basic Cell Settings
–
The step "Cells Configuration ► LTE Standalone NB IoT ► Basic Cell Settings" is optional. It declares the
Standalone NB IoT cells. If there is not standalone NB IoT cells planned on your site, please jump over.

To add a Standalone NB IoT cell, click the "Add Standalone NB IoT FDD cell" button, and Fill in the
mandatory parameters in its box.
We've introduced the basic cell parameters in the previous steps. Please fill in according to your plan
data.

We don't have a standalone NBIoT cell in our example BTS, so I'll remove this dummy one.

And let's jump back a little bit to see how to declare an NB IoT inband or guardband cell.

[Please switch to the next tab to continue.]

Video Narration - 2 - "NB-IoT Inband" or "NB-IoT Guardband" cells

–
To configure the "NB-IoT Inband" or "NB-IoT Guardband" cells, in step "Cells Configuration ► LTE FDD ►
Basic Cell Settings", click the "Add NB-IoT cell" button, and set the parameter as planned.

We need first to expand the configuration box of the planned host cell and scroll down to the bottom.

Then choose either "NB-IoT Inband" or "NB-IoT Guardband" from the dropdown menu "Add NB-IoT cell".

And set the necessary parameters.

Besides the common settings as for the wideband LTE cells, there are NB-IoT-specific parameters.

It allows defining two NB-IoT carriers in one host cell. The first one is referred to as the "anchor" carrier.
Thus, the second one, which provides additional user plane resources, is referred to as the "non-anchor"
one. In one same host cell, the anchor and non-anchor carriers must be both Inband, or both guardband.
Here we set the number of non-anchor carriers as 0, which means we only define one NB-IoT carrier in the
host cell.

"PRB index" defines the frequency domain location of the NB-IoT inband or guardband cell. It must be
planned according to NB-IoT theory. Copy your planned value here.

If you have the non-anchor carrier, its frequency location is calculated from the anchor one, so we do not
need to configure its PRB index.
But we may configure its power offset against the anchor carrier. Usually, we take the default value in the
beginning and then optimize it based on their performance.

This is the creation of an NB-IoT inband or guardband cell. More features are to be configured in the
Configuration tree.
 2

Steps Description
Here are the same operation steps described with text and screenshots. Either the Inband/Guardband
NB-IoT cells or the Standalone NB-IoT cell, pick the type as used in your site.

1 Cells Configuration ► LTE FDD ► Basic Cell Settings

To configure the "NB IoT Inband" or "NB IoT Guardband" cells, in the step "Cells Configuration ► LTE FDD ►
Basic Cell Settings", click the "Add NB-IoT cell" button, set the parameter as planned, and then click "Next".

1. Expand the configuration box of the planned host cell and scroll down to the bottom;

2. Choose either "NB-IoT Inband" or "NB-IoT Guardband" from the dropdown menu "Add NB-IoT cell"
at the bottom of the host FDD-LTE cell's configuration box;

3. Set the necessary parameters

The screenshots for inband and guardband NB-IoT cell creation are given separately in the tabs
below. Please switch among the tabs to find more details.

NB I OT I NB A ND NB I OT G U A RDB A ND
NB I OT I NB A ND NB I OT G U A RDB A ND
The explanation of the parameters is provided below.

NB IoT Cell ID, Local cell resource ID, and Cell name
–

NB IoT Cell ID: Instance identifier of the object LNCEL

This parameter is used only for O&M purposes.

Local cell resource ID: ID of the Local Cell Resource

The value for each cell shall be unique in the eNB. Note: This parameter is used in the NB-IoT cell
also. Range: 0...255.

Cell name: This parameter allows the operator to give a cell a name. The cell name is just a text
string and may have any value.

Extend LTE FDD to NB-IoT

–

With this parameter, choose between "NB IoT Inband" and "NB IoT Guardband".

Number of NB-IoT cell DL/UL Non-Anchor carriers

–
This parameter indicates the number of NB-IoT downlink Non-Anchor carriers.

Currently, the value could be 0 or 1 for NB-IoT inband or guardband cell.

If nbIoTMode is set to 'standalone' then numDlNonAnchCarrierNB must be set to '0'.

Physical layer cell ID and Tracking area code
–

Physical layer cell ID: Physical layer cell identity defines a cell uniquely. It consists of two parts;
physical layer cell identity group and physical layer identity and is calculated with the following
formula: physical layer cell identity = 3 x physical layer cell identity group + physical layer identity.

Tracking area code: Identifies the tracking area for this cell. A code that commonly identifies the
tracking area for all PLMNs listed for this cell.

NB-IoT DL/UL PRB index

–

NB-IoT DL PRB index: This parameter indicates the PRB index of the host LTE cell used for the NB-
IoT inband downlink anchor carrier. Only the following anchor PRB indices are allowed to be used for
inband NB-IoT based on the bandwidth of the host LTE cell:

5MHz: 2, 7, 17, 22

10MHz: 4, 9, 14, 19, 30, 35, 40, 45

15MHz: 2, 7, 12, 17, 22, 27, 32, 42, 47, 52, 57, 62, 67, 72

20MHz: 4, 9, 14, 19, 24, 29, 34, 39, 44, 55, 60, 65, 70, 75, 80, 85, 90, 95

NB-IoT UL PRB index: This parameter indicates the Anchor PRB index of the host LTE cell used for
NB-IoT inband uplink. The PRB index used for NB-IoT must NOT be configured to the resources used
by PUCCH and PRACH in the host LTE cell.
 2 Cells Configuration ► LTE Standalone NB IoT ►
Basic Cell Settings

In step "Cells Configuration ► LTE Standalone NB IoT ► Basic Cell Settings", configure the cells as the
following sub-steps, and then click "Next".

1. Click the "Add Standalone NB IoT FDD cell" button.

2. Fill in the mandatory parameters.

3. Choose the radio module and configure its connection with the cell.

step - Cells Configuration ► LTE Standalone NB IoT ► Basic Cell Settings

The explanation of the parameters is provided below.

Cell ID, Local cell resource ID, and Cell name
–

Cell ID: Instance identifier of the object LNCEL. This parameter is used only for O&M purposes.
Range: 0...65535

Local cell resource ID: ID of the Local Cell Resource. The value for each cell shall be unique in the
eNB. Note: This parameter is used in the NB-IoT cell also.
Range: 0...255

Cell name: This parameter allows the operator to give a cell a unique name. The cell name is just a
text string and may have any value.

MIMO mode
–
This parameter defines the cell-specific downlink transmission/MIMO mode. The used DL MIMO mode for
each physical channel is the following:

SingleTx: Single Stream Downlink: All downlink physical channels are transmitted using this mode.

TxDiv: Single Stream Downlink Transmit Diversity for two antennas using Transmission Mode 2.

Physical layer cell ID and Tracking area code

–

Physical layer cell ID: Physical layer cell identity defines a cell uniquely. It consists of two parts;
physical layer cell identity group and physical layer identity and is calculated with the following
formula: physical layer cell identity = 3 x physical layer cell identity group + physical layer identity.
Note: This parameter is used in the NB-IoT cell also.

Tracking area code: Identifies the tracking area for this cell. A code that commonly identifies the
tracking area for all PLMNs listed for this cell.
PRACH frequency offset
–
This parameter defines the location in frequency for the PRACH transmissions. For UL scheduling its
recommended that PRACH is located next to PUCCH either on the lower or upper edge of the bandwidth
because UL PRB allocation for UE consists of consecutive PRBs. If there is a small gap between PUCCH
and PRACH PRBs, the UL scheduler cannot utilize those PRBs effectively.

2 Cells Configuration ► LTE Standalone NB IoT ► Cell

Carriers

In step "Cells Configuration ► LTE Standalone NB IoT ► Cell Carriers", insert EARFCN and select Cell power
[dBm] for every cell, and then click "Next".

step - Cells Configuration ► LTE Standalone NB IoT ► Cell Carriers

The explanation of the parameters is provided below.

EARFCN
–
This parameter is the E-UTRA Absolute Radio Frequency Channel Number.

Cell power [dBm]

–
This parameter defines the maximum output power of the cell per antenna carrier in dBm. The maximum
output power is the maximum value for the linear sum of the power of all downlink physical channels that
are allowed to be used in a cell. The reference point is the antenna connector.

This lesson introduced the steps related to NB-IoT cell configuration.

The next lesson will introduce some optional objects for the BTS: Antenna Line Devices, the RF sharing
feature, and Passive Devices configuration.

C O NT I NU E
Lesson 8 of 10

Dene the Optional ALD, RF Sharing, and Passive Devices

This lesson introduces the optional tasks related to the optional Antenna Line Devices, RF sharing, and
Passive Devices in the Configuration Wizard. They are:

Antenna Line Devices

Antenna Line Devices MHA

Antenna Line Devices RET

Antenna Line Devices RET

RF Sharing

RF Sharing with FHS

Passive Devices

Operation Demonstration
This video demos the steps of Configuration Wizard in this lesson. If you might want to take notes, the
steps are also described in text and screenshots after the video.
Video Narration - 1 - Antenna Line Devices > Antenna Line Devices MHA
–
The step "Antenna Line Devices MHA" is optional. It defines the optional Masthead Amplifiers.

If the BTS doesn't use MHA, we can skip this step.

If the MHA is installed, it is detected and listed in the table automatically.
Our example BTS has no MHA at all. Here I'll declare a dummy one to show you the key attributes of an
MHA. If you plan to install the MHA later but prepare the SCF earlier, you may also do this.

To manually add a MastHead Amplifier, click the "Add MHA" button.

Select the added MHA object and choose its Controlling port. For an installed MHA, it may also need us to
choose the Controlling port for it.

Then, choose the LNA object and select its Amplified antenna line and DC power sources. Again, we can
change these parameters for an existing MHA.

We may repeat the steps to add other MHAs. But now let's remove this dummy MHA and move on.
[Please switch to the next tab to continue.]

Video Narration - 2 - Antenna Line Devices > Antenna Line Devices RET
–
The step "Antenna Line Devices RET" is optional. It defines the optional Remote Electrical Tilt Devices.

If the BTS doesn't use RET, we can skip this step.

If the RET is installed, it is detected and listed in the table.

To manually add a Remote Electrical Tilt device, click the "Add RET" button.
Then select the RET and set its Controlling port and DC power source to the same port. For an installed
RET, the Controlling port is selected by the BTS. We should set the DC power source to the same antenna
line.
Then click the RETU to set the Served antenna lines, and fill in the additional parameters.

We may also repeat the above steps for the other RETs.
As RET is not used in our example BTS, I'll remove this dummy one and move on.

[Please switch to the next tab to continue.]

Video Narration - 3 - Antenna Line Devices > Antenna Line Devices RAE
–
The step "Antenna Line Devices RAE" is optional. We can skip this step if no Remote Antenna Extension
device is used in the BTS.

Again, let's set a dummy to see what shall be configured for an RAE.
Click the "Add RAE" button, select the RAE, and set the Controlling port and the DC power source to the
same radio port.
Then click the RAEU, select its Served antenna lines, and fill in the additional parameters.

For an installed RAE, we may also check and change these settings.

Say goodbye to the dummy RAE.

And goodbye to the steps for the optional Antenna Line Devices.

Again, all the ALD types are optional. We don’t need to do anything if no ALD is used.
Next.

[Please switch to the next tab to continue.]

Video Narration - 4 - RF Sharing

–
The step "RF Sharing" is optional. We can skip it if the BTS does not work with RF sharing.
In the RF Sharing mode, one single RF Module is connected to two system modules simultaneously, using
two RATs.

To configure RF sharing on the BTS, select the companion RAT in the "Add RF Sharing" dropdown menu
and fill in the mandatory parameters.

I'll select the options to show you what will be asked for each companion RAT.
2G.
3G.
4G.
And 5G.

Next.
[Please switch to the next tab to continue.]

Video Narration - 5 - RF Sharing with FHS

–
It's also possible to configure RF Sharing with a 5G BTS for the Radio Units using a Fronthaul Switch (FHS).
This step is optional. And it's only available when FHS is configured in the BTS.

If no FHS is defined in the BTS, the step is greyed out.

Or, if the FHS used does not support this function, let's take an example. We can see the step "RF Sharing
with FHS" is accessible now, but it tells us that "This step is not available for current type of FHS".

Let's change to another type of FHS.

And this time, we can try its configuring.
Add RF Sharing with FHS. And put in some settings.
There are still some warnings. We can give the required details in the Parameter Editor.

To disable the function, de-check the "Sharing RHS" option. It seems that we have something left here.
But, if we go to another step and come back, we will see it's the same state as we did not add anything
here.

[Please switch to the next tab to continue.]

Video Narration - 6 - Passive Devices

–
The step "Passive Devices" is optional, too. We skip this step if no passive device is used in the BTS.
To add passive devices, click "Add Passive Device" and configure the devices. Or, for a detected device,
we may select it and check the configuration.

Till now, we've gone through consecutive optional steps. Thank you for staying with me. If you don't have
any to configure in these steps, it's no need to repeat "NEXT" all the time. We can select our next hop in
the steps list directly.

Steps Description
Here are the same operation steps described with text and screenshots.

1 Antenna Line Devices ► Antenna Line Devices MHA

The step "Antenna Line Devices ► Antenna Line Devices MHA" is optional. To configure the MastHead
Amplifiers, follow the steps and then click "Next".

1. Add the MHAs already installed.

2. Add the MHAs not yet installed.

3. Select MHA-1, and choose Controlling port.

4. Click the LNA-1 and select Amplified antenna line and DC power sources.

5. Repeat the above steps for the rest of the MHAs.

The details of the steps are described in the Process Flow below. Please use the ">" and "<" arrows to go
through all the steps.
 Introduction

This procedure describes the steps to configure the Antenna Line Device MHA.
 Step 1

Add the MHAs already installed

If the MHA is already physically installed and detected by the BTS system, click the "+" button
next to un-commissioned MHAs.

The green LED indicates that the BTS system has detected the MHA;

The wrench icon next to the green LED means that the MHA is waiting for your further
action.

If there was no MHA installed yet, skip this step, and add planned ones in the next step.
 Step 2

Add the MHAs not yet installed

If the MHA is not yet installed, add it either in Topology View or in this step of Configuration
Wizard by clicking the "Add MHA" button.

If all the MHAs needed have been installed and detected, there is no need to add them in this
step manually. In this case, skip this step.
 Step 3

Cong Controlling port for the MHA

Select MHA-1, choose the Controlling port from the drop-down list.

If the MHA is already detected, the Controlling port is filled automatically.

 Step 4

Connect LNA-1/2

Click the LNA-1 and select Amplified antenna line and DC power sources from the drop-down
lists. Fill in the additional parameters.

Repeat this for LNA-2.

 Summary

One MHA is added successfully with the four steps.

If there are more MHAs to be configured, repeat the steps for the next one.

2 Antenna Line Devices ► Antenna Line Devices RET

The step "Antenna Line Devices ► Antenna Line Devices RET" is optional. To configure the Remote
Electrical Tilt devices, take the following steps and then click "Next".

1. Add the RETs already installed.

2. Add the RETs not yet installed.

3. Select one added RET, check which antenna line is automatically set in the Controlling port field, and
choose the same one for DC power sources.

4. Click RETU-1 and select Served antenna lines. Fill in the additional parameters.

5. Repeat the above steps for the rest of the RETs.

The details of the sub-steps are described in the Process Flow below. Please use the ">" and "<" arrows to
go through all the steps.
 Introduction

This procedure describes the steps to configure the Antenna Line Device RET.
 Step 1

Add the RETs already installed

If the RET is already physically installed and detected by the BTS system, click the "+" button
next to un-commissioned RETs.

The green LED indicates that the BTS system has detected the RET;

the wrench icon next to the green LED indicates that the RET is waiting for your further
action.

If there was no RET installed yet, skip this step, and add them in the next step.
 Step 2

Add the RETs not yet installed

If the RET is not yet installed, add it either in Topology View or in this step of Configuration
Wizard by clicking the "Add RET" button.

If all the RETs needed have been installed and detected, there is no need to add them in this
step manually. In this case, skip this step.
 Step 3

Cong Controlling port for the RET

Select RET-1, check which antenna lines are automatically set in the Controlling port field, and
choose the same one for DC power sources.

If the RET is already detected, the Controlling port is filled automatically.

 Step 4

Connect RETU-1

Click RETU-1 and select Served antenna lines. Fill in the additional parameters.
 Summary

One RET is added successfully with the four steps.

If there are more RETs to be configured, repeat the steps for the next one.

3 Antenna Line Devices ► Antenna Line Devices RAE

The step "Antenna Line Devices ► Antenna Line Devices RAE" is optional. To configure Remote Antenna
Extension Device(RAE), take the following steps, if required, and then click "Next".

1. Add the RAEs already installed.

2. Add the RAEs not yet installed.

3. Select one added RAE, Check which antenna line is automatically set in the Controlling port field and
choose the same one for DC power sources.

4. Click RAEU-1 and select Served antenna lines. Fill in the additional parameters.

The details of the sub-steps are described in the Process Flow below. Please use the ">" and "<" arrows to
go through all the steps.
 Introduction

This procedure describes the steps to configure the Antenna Line Device RAE.
 Step 1

Add the RAEs already installed

If the RAE is already physically installed and detected by the BTS system, click the "+" button
next to un-commissioned RAEs.

The green LED indicates that the BTS system has detected the RAE;

the wrench icon next to the green LED indicates that the RAE is waiting for your further
action.

If there was no RAE installed yet, skip this step, and add them in the next step.
 Step 2

Add the RAEs not yet installed

If the RAE is not yet installed, add it either in Topology View or in this step of Configuration
Wizard by clicking the "Add RAE" button.

If all the RAEs needed have been installed and detected, there is no need to add them in this
step manually. In this case, skip this step.
 Step 3

Cong Controlling port for the RAE

Select RAE-1, Check which antenna line is automatically set in Controlling port field and
choose the same one for DC power sources.

If the RAE is already detected, Controlling port is filled automatically.

 Step 4

Connect RAEU-1

Click RAEU-1 and select Served antenna lines. Fill in the additional parameters.
 Summary

One RAE is added successfully with the steps.

If there are more RAEs to be configured, repeat the steps for the next one.

4 RF Sharing

The step "RF Sharing" is optional. To configure RF sharing on the BTS, select the Add RF Sharing to enable
RF sharing, fill in the mandatory parameters, and click "Next".

One single RF Module is connected to two system modules in the RF Sharing mode using two RATs
simultaneously.

Step - RF Sharing
SHA RI NG 4 G SHA RI NG 5 G SHA RI NG 2 G SHA RI NG 3 G

SHA RI NG 4 G SHA RI NG 5 G SHA RI NG 2 G SHA RI NG 3 G

SHA RI NG 4 G SHA RI NG 5 G SHA RI NG 2 G SHA RI NG 3 G

SHA RI NG 4 G SHA RI NG 5 G SHA RI NG 2 G SHA RI NG 3 G

 5 RF Sharing with FHS

The step "RF Sharing with FHS" is optional. It’s only available when FHS is configured and at least one cell is
created in the BTS.

To add passive devices, click "Add Passive Device" and configure the devices. Then click "Next".
 Step - RF Sharing with FHS

6 Passive Devices

The step "Passive Devices" is optional. To add passive devices, click "Add Passive Device" and configure
the devices. Then click "Next".

Step - Passive Devices

This lesson introduced the steps related to Antenna Line Devices, RF sharing, and Passive Devices
configuration.
Please move on to take the knowledge check.

C O NT I NU E
Lesson 9 of 10

Knowledge Check
Question

01/05

Suppose an SBTS has three Capacity Units: an ABIA, an ABIO, and an ABIN. Which of the
following Common Units can be used with them in this site?

ASIA

ASIB

ASIK

ASIL
Question

02/05

How many RF ports on an ABIA support IQ Compression?

9
Question

03/05

The "Cell power" parameter defines the maximum output power of the LTE cell ( ) in
dBm.

for all its antenna paths

per antenna carrier

per RB per antenna carrier

per RE per antenna carrier

Question

04/05

Which of the following parameter is only required for standalone NB-IoT cells but not for
inband NB-IoT cells?

bandwidth

MIMO mode

Physical layer Cell ID

Tracking area code

Question

05/05

An Airscale BTS for LTE can work in RF sharing with another BTS for ( ).

2G

3G

4G

5G
Lesson 10 of 10

Main Takeaways

What are the key takeaways of this course?

The module described the LTE BTS data commissioning steps of the Capacity Plug-in Units,
Radio Units, cells, some optional hardware, and RF Sharing.

The Capacity Plug-in Units are added in the step "Baseband Module
Settings". Its pool usage and concurrent mode can also be set in the
step.

Certain variants support eCPRI for the fronthaul interface, and the RF
ports in use can be configured in the step "Baseband Module eCPRI
Transport Configuration".

To manage the SFPs on the Capacity Units, add those SFPs in the step
"Baseband Module SFP Controller".

The Radio Units are added in the step "Radio Module Settings".

Their connection toward the baseband part, either to the Capacity

Units or a Core Unit, is configured in the step "Radio Module Link
Configuration".

The wideband cells are declared in the step "Basic Cell Settings" for
LTE FDD and LTE TDD respectively. The very basic settings are settled
in these steps and the "Cell Carrier" steps. Some details about feature
 usage will be found in the later steps and more in the Parameter
Editor.

Inband and Guardband NB-IoT cells are added in the same wizard step
to add their host LTE FDD cell.

Standalone NB-IoT cells are added in the step "Basic Cell Settings" in
the LTE Standalone NB IoT group.

Find attached a printable of the content covered in this course.

This concludes your current training module.

Thank you for attending this course.

Check out [Link] for more.