Radio Network Design for

Rollouts (RNDR)
LTE16
Configuration Management
• NPO Global

1 © Nokia 2016
 RNDR Training  Scope of This Module
Link Budget Planning Tool Acceptance Testing
− Coverage thresholds – Detailed coverage/throughput – Cluster acceptance
calculation simulations (plots) – From coverage /
− Dimensioning is out of the scope – Site database throughput targets
of this training
– PCI, neighbour planning definition
(optional)

Planning Parameters Plan Creation Mobility Management

– Site specific radio planning – Based on radio/HW inputs – Mobility types
parameters (parameters) – Mobility thresholds
– Areas: PCI, PRACH, UL DM – (Transport parameters out of (parameters)
RS scope) – Layering Strategies
– Tools/methods used in network
plan creation

Configuration
Management
2 © Nokia 2016
Contents
- Configuration Management Overview
- Parameter Planning Overview
• Required information for parameter planning:
- Site Configurations
- Market/Operator Specific Information
- Parameter settings/values
- Cell Mobility Configurations
• Parameter structure (MOC) and Site Configuration
• System Configuration Files
- Configuration Plan Creation Methods
• Overview of Different Methods for Rollout Plan Creation
- NetAct Configurator
- DAISY (LACE module)
- Plan Editor
- KISS
- Useful Links
3 © Nokia 2016
Configuration Management
Overview
• Configuration Management (CM) deals with the creation of configuration plan files (xml), required
for the integration of the sites within a network.
• Parameter Planning – site configurations and parameter settings
• Initial Site Configuration Templates – based on typical site configuration(s)
• Development of overall configuration plan files
- Various methods available to assist in generating the configuration plan files, representing the operator-
specific settings.
- Each method is based on a separate tool or tools
• NetAct Configurator
• Plan Editor
• DAISY (LACE module). It also uses Plan Editor as part of its process.
• KISS
- The selection of one or another method will depend on the project characteristics, such as number
of sites and whether plan files are created online or offline
• Implementation of the configuration plan
• NetAct uses configuration plan files to set actual parameters within a system

4 © Nokia 2016
 CM Process

Initial Parameter Planning Configuration file templates

• Radio parameter settings • For typical radio and transport configurations
• Transport parameter settings • Templates contain default settings for all parameters
• Operator-specific settings (e.g. MCC, MNC,...) (also for those not having defaults) Site parameters for SON
• Site Configurations • SCF created with BTS Site Manager or copied from Coordinates, antenna
(RF module, system module, antennas, etc.) an existing eNB bearing

Create Configuration Plan files

Various methods for creating configuration/plan files

KISS
NetAct Configurator Plan Editor DAISY (LACE module)
Uses Kiss configuration
Uses site-specific parameter Uses PE templates and SCF Uses CIQ input file and Plan
macro and Excel parameter
data file and template files Editor (running within DAISY)
inputs

Implement Plan
NetAct Integration of Sites in Network
• Based on configuration/plan information

5 © Nokia 2016
 Parameter Planning

6 © Nokia 2016
Parameter Planning
Overview
- Parameter Planning is required before developing the overall configuration plan files

- Define site configurations and parameter settings/values  used as inputs in

configuration management tools
• Radio Parameters
• Transport Parameters
• Configurations - RF module, system module, antennas, etc.
• Market/Operator-specific parameters (e.g. MCC, MNC, etc.)
• Cell mobility configurations
(Idle mode, Connected mode, and configurations for neighbours, S1 handovers, and blacklisting)

- The next two slides provide examples of the type of information that is required
before proceeding with generating configuration files.

MCC: Mobile Country Code

MNC: Mobile Network Code
7 © Nokia 2016
Parameter Planning
Example Product Hardware Site Configuration Information
- Radio Module definition
• Need to define the type of Radio Module to be used
• Number of Radio Modules per site depends on the site configuration
- System Module definition
• Need to define the type of System Module to be used (e.g. FSMF, etc.)
- Cell definition
• Number of cells
• RF modules used per cell
• Antenna Line definition (connections per cell: relation between antenna ports and antenna lines)
• MIMO settings
• Power of RF module
• (Associated parameters: antId, antlId, rModId)
- DL/UL Bandwidth & Frequency definition
• Define channel bandwidth per cell
• Define DL EARFCN per cell (UL EARFCN is automatically calculated from the DL EARFCN value)
- Optional Configuration Information
• MHA (Mast Head Amplifier) information
• RET (Remote Electrical Tilt) information

8 © Nokia 2016
Parameter Planning
Example Idle & Connected Mode Mobility Parameters
- Idle Mode Parameters (LNCEL child objects)
• IAFIM: Intra-frequency Idle Mode
• IRFIM: Inter-frequency Idle Mode
• UFFIM: Utran FDD Idle Mode
• GFIM: GERAN frequency Idle Mode
- Connected Mode Mobility Parameters
• LNCEL child objects
- LNHOIF: neighbor intra-frequency LTE cell handover
- LNHOW: neighbor WCDMA handover
- LNHOG: neighbor GSM handover
- LNREL: neighbor relation
- REDRT: redirection target
• LNBTS child objects
- ADIPNO: ADjacent IP NOde
- LNADJ: neighbor LTE cell
- LNADJG: neighbor GERAN BTS cell
- LNADJW: neighbor WCDMA cell

9 © Nokia 2016
Parameter Structure
(Managed Object Classes)
and Site Configuration

10 © Nokia 2016
Introduction

- Parameters are organized into Managed Object Classes (MOC) that follow a hierarchical structure
containing three main areas:

- Radio Network Parameters (RNW)

- Site Configuration Parameters (HW)
- LTE BTS Transport Parameters (FTM)

- Most of MOCs (and parameters under each MOC) are stable between releases, but some of them
can be added / removed between releases.
• Not all MOCs are mandatory (i.e. not all MOCs must be configured)

- Parameters per release can be found in NOLS Operating Documentation. Detailed information can
be found in NIDD (Networks Integrated Data Dictionary) or PKDB (within MINT).
(Links provided at end of slide set.)

- When creating a site configuration file, which can then be used as a site template in the
configuration plan creation, the MOCs must be configured to reflect the network characteristics.

11 © Nokia 2016
 Managed Object Hierarchy (LTE16)
PLMN MRBTS
ANTL RET
LNBTS FTM BBMOD RMOD

ANRPRL LNCSG CTRLTS LTRACE SFP

BTSSCL LCELL
ANRPRW LNHENB MTRACE SMOD
MHA GNSSE
CADPR LNMME LNADJ LNADJL
GNSSI
LNCEL
CRAN LNSENB Site Configuration Parameters
CRGPR MFBIPR AMLEPR LNHOH LNRELG

GTPU PMRNL CAPR LNHOIF LNRELW

AMGR LUAC
ISHPR PSGRP CAREL LNHOW LNRELX
BTOOTH SYNC STPG
LNADJG SCTP CDFIM LNHOX REDRT
CERTH TAC LTAC
LNADJW ULCOMP IAFIM LNNEIH UFFIM
ETHLK IPNO IEIF IVIF
LNADJX IRFIM LNREL XPARAM
LNHOG IPSECC
L2SWI BFD IPRM NTPS
GFIM GNFL OAMPRF BFDGRP IPRT QOS
PMTNL IDNS IPRTV6 RTPOL
LNM3
POE IHCP MCAPP TWAMP
PMCADM LNMCE MBSFN
SECADM PPTT INTP
MODPR MODIMP Radio Network
TRBLCADM UNIT
MOPR MODRED Parameters OAMMD OAMMA OAMMEP
TEST RFRST WIFICNF
MOIMP TOPB TOPF Transport
RFTHLD
12 © Nokia 2016 MORED TOPP Parameters
SFPRST
Managed Object Classes
Short description 1/5

13 © Nokia 2016
Managed Object Classes
Short description 2/5

14 © Nokia 2016
Managed Object Classes
Short description 3/5

15 © Nokia 2016
Managed Object Classes
Short description 4/5

16 © Nokia 2016
Managed Object Classes
Short description 5/5

17 © Nokia 2016
Parameter Configuration

• Parameter configuration can be divided into:

- Site-specific parameters:
Those that need to be planned/allocated separately for each site
- ‘Site Template’ parameters:
Those that can be assigned a value that is predefined in a template, as they don’t
vary across the sites of a network. They can be:
• Operator specific: e.g. mnc, mcc, plmnId
• ‘Default’ parameters

- References for parameter configuration are:

• NIDD (Networks Integrated Data Dictionary)
• PKDB (found within MINT tool)
• SCF: System Configuration File
• Downloaded from NOLS to get latest configuration information.
• Configuration Management IMS Folder
• Golden Master Configurations, found within the MINT tool.

18 © Nokia 2016
 System Configuration Files (SCF)
Example SCF File
Overview
• Planner needs to create the template and plan specific for their project

• The common starting point for all site template creation is the System
Configuration File (SCF):
• It already presents parameters in XML format

• Golden System Configuration Files (also known as GMC files –

Golden Master Configuration files) are xml files containing the basic
MOCs and their parameters

• Contents of the SCF files vary, depending on the LTE variant (FDD or
TDD) and on the different releases.
- Even within the same release, there are different versions of SCF files
(newer versions as more features are implemented), until P8 is reached.

- Once P8 milestone has been reached for a release,

the contents of the SCF are frozen.

- Recommendation is always to use the latest SCF available.

19 © Nokia 2016
System Configuration Files
Parameter values (SCF vs. NIDD)
- Most default parameter values in NIDD should be aligned with SCF values after
P8 milestone

- Reasons why parameter values can be different:

• SCF is focused on lab testing, low loaded trials and customer networks, whereas NIDD
values should be more generic, e.g. cell load dependent parameters
• In case of parameter discrepancies, SCF defaults are commonly used for Configuration
Management rather than NIDD parameter defaults

20 © Nokia 2016
System Configuration File (SCF)
Structure
Reasons why SCF can not be used directly as a template file for an eNB:

- MOCs and instances may need to be adapted for each case, for example:
• SCF may only have 1 LNCEL object (normally, 3 LNCEL objects are required)
• SCF may not have the required number of ANTLs defined (e.g. only ANTL-1 to ANTL-6, instead of up to ANTL-12)

- Operator-specific parameters have not been assigned (e.g. enBName, mcc, mnc, etc.)

- SCF may not contain all MOCs required or may contain MOCs that
are not required (LNADJG, UFFIM…)

When creating a template, appropriate MOCs and parameter values are incorporated to reflect the
specific site configuration and operator information.

21 © Nokia 2016
BTS Site Manager – Overview (1/2)

• The BTS Site Manager (BTS SM) tool is often used

to create or validate configuration-specific files
• For example, create a 3-sector FL16 site with specific
configuration (i.e. HW, etc.), a 1-sector FL16 site, etc.

• These files are then used as template files within other

tools (i.e. NetAct, Plan Editor, KISS) to generate
configuration plans.

• BTS SM is also used to validate xml configuration files

created with another method (e.g. DAISY) to ensure that
there are no issues before using the xml for deployment.

• BTS Site Manager is specific for each LTE Release

• Several versions of BTS SM can be installed

simultaneously (e.g. one needed per release used)

22 © Nokia 2016
BTS Site Manager – Overview (2/2)
• Tool: BTS Site Manager (BTS SM)
• Inputs:
– Existing Commissioning file (i.e. for an existing eNB) or System
Configuration File for specific release
– Site-specific parameters requiring planning (radio and transport)

• Output:
– Commissioning file to be provisioned onto the site or used as a Site
Template in configuration management tools

• Benefit:
– “Back to basics” site commissioning method. BTS SM points out
parameters that are needed.
– Popular for use in commissioning sites in small trials; OK for a small
number of cells

• Drawback:
– Manual process and time consuming; therefore, not used directly for
rollouts

23 © Nokia 2016
Creation of Site Template using BTS Site Manager (1/2)

• Site Template Creation Process within BTS SM:

• Open SCF with BTS Site Manager.
Various SCF files can be used:
• Downloaded Golden SCF file
• Existing eNB SCF file
• File previously created by Site Manager

24 © Nokia 2016
Creation of Site Template using BTS Site Manager (2/2)

• Go through BTS Site Manager screens and provide the

appropriate settings for the specific case (i.e. HW type, number
of sectors, antenna configuration, bandwidth, addition of
Managed Objects, etc.)
• Should have required site-specific parameter information available
before starting BTS SM
• Need to fill in all mandatory parameter information on a screen before
passing to next

• The configuration and parameter

information provided within BTS SM
determines the parameter settings
within the resulting xml
commissioning file.
• The commissioning file can now be
used as a Site Template in other tools.

25 © Nokia 2016
Configuration Plan Creation Methods

26 © Nokia 2016
Configuration Plan Creation Methods
Overview
- As mentioned, there are multiple methods/tools that can be used to
create a configuration plan for deployment.
• NetAct Configurator
• Plan Editor
• DAISY (LACE module)
• KISS

- The following slides provide an overview of each of these methods

• These slides include links to more detailed information for each of the
methods.
• This information also provides benefits and drawbacks for each method,
to help one choose which method to use.

27 © Nokia 2016
Method 1: NetAct Configurator
Overview
• Tool: NetAct Configurator
- Inputs:
• Site Data file (XML or CSV input file)
• It contains ‘site specific’ parameters, i.e. those that need to be planned/allocated separately for each
site
• One site-specific parameter per column; parameters for one site per row
• •Import
MapsProfile (XML)
the column - Only necessary
information of the if Site Data file is in CSV format
CSV file into XML
• Site Template
- Output:
• Plan to be provisioned to the
network
- Benefit:
• Simple and fast (once data files
are ready)
- Drawback:
• It is necessary to have online
connection to NetAct
28 © Nokia 2016
Method 1: NetAct Compatibility and NetAct Configurator
• NetAct Compatibility

• Plan is created with a combination of CM Operations Manager and CM Editor

• CM Operations Manager: Import site data (start of plan creation), import of site templates, and CM workflow
• CM Editor: Edit site templates and site(s)/plan inputs

29 © Nokia 2016
Method 1: NetAct Configurator and Optimizer
SITE Object

• NetAct Optimizer can be used to create the PCI and the

neighbour relations

• Optimizer requires the creation of the NetAct internal SITE

object
• Creation of SITE object cannot be done with most other CM methods
(i.e. Plan Editor, macros, etc.).
• DAISY can create SITE objects.
• Creation can be done in conjunction with CSV import or as a separate
SITE import

- $siteId should be the same in SITE, MRBTS and LNBTS

objects in order to associate MRBTS and LNBTS to the
correct SITE object

30 © Nokia 2016
Method 1: NetAct Configurator
Process
1. Create and import a Site Template into NetAct CM Operations Manager (part of NetAct
Configurator)

2. Import into CM Operations Manager the site input file, i.e. the site data file
- Planner decides which parameters to include in the input file.
These parameters should be ones that need to be specific for each site and for which it is not
possible to use a template.
- Within the input file, it is necessary to identify the Site Template to be used
(i.e. the name in the file needs to match the existing Site Template within NetAct).
3. Assign an import profile to the csv input file
- Only required if the input file is in csv format. Not needed if the input file is already in xml format
- The import profile is needed to create an xml file from the csv input file.
4. Apply a Site Template to the plan (or input file)
- For those parameters not included in the input file, the values of the Site Template are used
5. Validate the plan and provision it.
31
NOTE: Provisioning
© Nokia 2016
the plans is not part of Radio planning (and not discussed here)
Method 1: NetAct Configurator
Site Input File
• CSV site data input file contains site-specific parameters
• Each column contains one site-specific parameter and
each row contains the site-specific parameters for one site
• User Interface (UI) or Internal parameter values can be used
(Internal values preferred, as UI are case and space sensitive)
• A unique Distinguished Name (dn) is needed for every object created in the CSV file. It uniquely
identifies a Managed Object in the database.
– The only site-specific id in the DN is the MRBTS/mrBtsId, which must be equal to LNBTS/lnBtsId
- Example DN for LNCEL of sector #1: PLMN-PLMN/MRBTS-9876/LNBTS-9876/LNCEL-1

Site Template name provided in

One site per row
this Site Input file must match the
Site Template name within NetAct.

32 © Nokia 2016 One parameter per column

 Sample Import Profile Information
Method 1: NetAct Configurator
Import Profile and Site Template
Import Profile
• Import profile is created manually in a text editor. It must contain the same
inputs (MOC and site-specific parameters) defined in the site input file.

Site Template
- It contains the parameters that don’t need to be planned for every site
and can be assigned a predefined value.
- Two ways to create the Site Template:
– Import an existing template using CM Operations Manager (NetAct
Configurator).
– Create a Site Template from an existing site in the NetAct OSS database
using CM Editor (part of NetAct Configurator).
• Site Template values can be browsed and modified with any text editor or
in CM Editor

Further Details can be found in Plan Creation with NetAct CM

33 © Nokia 2016
Method 2: Plan Editor
Overview
- Tool:
• NetAct Plan Editor with SW license (.lf file)
- Inputs:
• Site Data file (csv)
• Plan Editor templates
- Output:
• Either a Commissioning file per site (suitable for BTS SM) or OSS
plan for multiple sites, depending on the export profile selected
- Benefit:
• Offline tool
• Nokia tool developed as part of NetAct package
• This method generates plans and tracks changes
- Drawback:
• Generation of templates and template sets may not be straightforward
• It doesn’t support SITE object creation (needed for Optimizer and Auto configuration)

34 © Nokia 2016
Method 2: Plan Editor
Tool Overview

• NetAct Plan Editor is a Windows-based graphical tool that is part of NetAct Configurator
• It is an independent tool that facilitates offline editing of radio network parameters.
• General Plan Editor work flow:
• Import configuration data
(generated from NetAct or from radio network planning systems)
• Edit the data appropriately for a given network
• Export the completed plan file
• Plan Editor is not directly used for implementation to the network
• Implementation is done with network management systems, such as NetAct, after the
parameter data is imported into NetAct databases

35 © Nokia 2016
Method 2: Plan Editor
Functionalities (1/2)
• Offline plan administration -
Network data changes stored in
plans/sub-plans
• Offline plan import/export
(supports XML or CSV format)
• Object management - Ability to
view/create/delete/edit objects
• Parameter management
• Ability to view/edit
parameter data
• Tool maintains history of
changes made to actual
network configuration or
plans.

36 © Nokia 2016
Method 2: Plan Editor
Functionalities (2/2)
• Queries and mass modification
• User-specific checks of parameter data and
updating multiple objects

• Network configuration snapshot

• Allows for viewing snapshot of network and
preparing/performing updates

• Template management
• Templates enable definition of predefined
default parameter values for different
object classes.
• Template sets can be used to group
templates of different object classes
together.
• Templates and template sets speed and
simplify the object creation and reduce
errors.
37 © Nokia 2016
Method 2: Plan Editor
Useful Links

- NetAct Plan Editor Information

• General Plan Editor information (software and documentation)

• Plan Editor FAQ

- Detailed Instructions regarding Plan Editor

38 © Nokia 2016
Method 3: DAISY – LACE Module
Overview
CM Tool used most often with LTE rollouts.

• Tools:
• DAISY (Nokia internal tool) with SW license
• Plan Editor (PE) with SW license (.lf file) - integrated into DAISY
process
• Inputs:
• CIQ (Customer Information Questionnaire) Excel
• Plan Editor database
• Output:
• XML file for each eNB or unique XML containing the actual plan
(multiple eNBs)
• Benefit:
• Offline
• Supports creation of Site object
• Drawback:
• Availability depends on availability of PE database and CIQ
creation/verification

39 © Nokia 2016
Method 3: DAISY – LACE Module
Process (1/7)
Preparation phase:
- Download and install latest DAISY SW and Plan Editor SW
- Request DAISY and Plan Editor licenses
- Obtain and fill in the appropriate CIQ parameter information.

Links to DAISY Information: (see previous slides for links to Plan Editor information)
- DAISY Instructions
- Official DAISY Tool Suite Space
• DAISY SW
- An empty Plan Editor (PE) database and the valid CIQ file for that DAISY version is part of the package, within folder
LACE/Input
[e.g. \My Documents\NOKIA\DAISY\PROJECTS\LTE_LACE_FL16\WorkDir\LACE\Input]

• DAISY License Request form

• DAISY LTE CIQs

40 © Nokia 2016
Method 3: DAISY – LACE Module
Process (2/7)
Transport DAISY (LACE module) Deployment
Planning OSS formatted NetAct
Information XML files
Configurator
Plan
CIQ XLS Interim
XML File Editor
XML
XML Validation 8
BTS Site
Radio 1 2 3 4 5 6 Manager
Planning LNx.0/LNTx.0
Information
DAISY internally utilizes Plan Editor
formatted
XML files 7

Process Introduction (1/2):

1. Customer Information Questionnaire (CIQ) is filled in by Nokia customer team
2. CIQ is provided as input into DAISY.
3. DAISY reads the CIQ fields and develops parameters per Managed Object.
4. DAISY automatically transfers information to Plan Editor to merge the CIQ parameter information with “Default” parameter
settings from within PE. (The “default” parameter set, which is used to build up the database, is driven by DAISY. This is
done by specifying the proper PE template names for each Managed Object, within the CIQ file.)

41 © Nokia 2016
Method 3: DAISY – LACE Module
Process (3/7)
Transport DAISY (LACE module) Deployment
Planning OSS formatted NetAct
Information XML files
Configurator
Plan
CIQ XLS Interim
XML File Editor
XML
XML Validation 8
BTS Site
Radio 1 2 3 4 5 6 Manager
Planning LNx.0/LNTx.0
Information
DAISY internally utilizes Plan Editor
formatted
XML files 7

Process Introduction (2/2):

5. DAISY drives Plan Editor to generate the “final” output XML information: a combination of CIQ and PE parameter settings.
6. Outputs are then exported from DAISY (in either LNx.0/LNTx.0 XML format or in OSS XML format).
7. XML Validation of output file in BTS Site Manager (LNx.0/LNTx.0 XML formatted files used in BTS SM for validation)
8. Deployment in NetAct (using OSS formatted XML output)

42 © Nokia 2016
Method 3: DAISY – LACE Module
Process (4/7)
Customer Information Questionnaire (CIQ):
• The CIQ is the starting point for the DAISY process
– Excel spreadsheet that contains key project/parameter values
 e.g. site configuration parameters, RF module parameters, system module parameters, transmission sub-
module parameters, and parameters which are pointers to CIQ or PE templates that define additional
configurations.
– CIQ provides parameters in more readable format for user
– CIQ is divided into various worksheets, associated with different LTE objects
– Questionnaire needs to be filled in with customer-specific information before starting DAISY process

43 © Nokia 2016
Example “SiteMainPar” sheet within CIQ
Method 3: DAISY – LACE Module
Process (5/7)
DAISY Handling
- DAISY is used for multiple modernization and rollout
technologies, so it is important to select the LACE
module and LTE technology.
- When launching DAISY, it requires the user to
select an available Project or create a new empty
project.

• DAISY works in three steps:

– Data generation:
Generation of interim xml files from the CIQ excel
– Data Upload:
Upload of interim xml files into Plan Editor
(Note: PE, in this instance, is driven by DAISY)
– Data export:
Generates xml plan - combination of CIQ and PE
44 parameters
© Nokia 2016
Method 3: DAISY – LACE Module
Process (6/7)
DAISY Handling (cont)

• Data Generation: Uploading the CIQ

• Validates the CIQ
• Note: CIQ must be closed (not opened in Excel)
when importing it into DAISY

• Data Upload: Import in Plan Editor  Straightforward

after uploading the CIQ
• Import of data into Plan Editor is done internally in
DAISY process
• Input: xml files generated in the previous step. It is
enough to point to the folder

• Data Export: Export to xml using either Default LTE

FLxx/TLxx or Default OSS format

45 © Nokia 2016
Method 3: DAISY – LACE Module
Process (7/7)
Plan Validation & Deployment
• Once DAISY provides the plan, it is recommended to validate it before
provisioning (BTS SM checks things that DAISY and Plan Editor do not)
• Two possible DAISY outputs depending on the export profile
1. Default LTE FLxx (FDD) or LTE TLxx (TDD) format
2. Default OSS format

Default LTE FLxx or LTE TLxx format

• Generates an xml file for each eNB  validation for each site can be done
individually with BTS Site Manager

Default OSS for NetAct Deployment

• Generates one xml for deployment in NetAct Configurator, containing all
sites (i.e. the whole plan).

46 © Nokia 2016
Method 4: KISS Databuild Creation Macro
Overview (KISS: Keep It Short and Simple)

• Tool:
• Excel macro TRS Data BTS Data
• Inputs:
• Excel spreadsheet with radio and transport parameters that need to be
planned (i.e. those that are different for each site) Input Data in Macro Tool
• Release-specific Template
• BTS SM for file validation (recommended)

• Output: Run Macro to create

• Commissioning file(s) to be provisioned commissioning file (XML)
• Benefit:
• Flexibility to adapt the macro for different releases and different inputs
• Mass validation of sites in BTS SM with just one click (driven by macro)
Validate multiple
• Drawback: commissioning files with
• It doesn’t support SITE object creation (needed for Optimizer and Auto BTS Site Manager
configuration)

47 © Nokia 2016
Method 4: KISS Databuild Creation Macro
General Information

• The offline Excel macro can be used for rollouts

(simultaneous creation of multiple commissioning files)
• It is valid for any release (FDD and TDD), providing the right template is used

General idea behind the tool:

• Macro works by replacing $parameter tags in the defined template with parameter
values defined in the input sheets
• User sets up the $parameter tags within the given template
• User defines the parameter values within the input sheets

• KISS Information – includes tool, instructions, and examples

48 © Nokia 2016
Method 4: KISS Databuild Creation Macro
Process
1. Template creation: Create a template file using BTS Site Manager or use an existing site configuration file as a
template file
2. Template adaptation: In the template file, replace site-specific parameters or parameter lists with $parameter tags,
such as ‘$pci1’
3. KISS handling: Within the KISS Excel worksheets, define the $parameter tags and the parameter values that
should replace them, one site per Excel row
4. Run macro: KISS replaces tags with the parameter values in the template file and produces a commissioning file
per site
5. Run validation: KISS drives BTS SM to validate each of the created commissioning files

Example KISS Macro Example Template screenshots

with basic MO inputs:

49 © Nokia 2016
Comparison of Plan Creation Methods for Rollouts
Attribute Method 1: NetAct with LTE site Method 2: Plan Editor using template
templates sets

Input data format CSV or XML CSV

Output data Site CM data in OSS database. Can be eNB commissioning files (xml) or
exported in XML format using CM OSS database (xml)
Operations Manager
SW required NetAct OSS Plan Editor
Licensing Basic NetAct functionality Plan Editor soft license (.lf file)
Online / Offline Online: connection to NetAct required to Offline
import data with CM Operations Manager
and to apply site template

Optimizer SITE object Yes, allows creation of SITE object in the No, SITE object must be created afterwards
creation readiness in CSV import in NetAct
import
Site template data Yes, site template parameters can be freely Yes, site template parameters can be freely
parameter customizability customized customized using PE template sets

50 © Nokia 2016
Comparison of Plan Creation Methods for Rollouts
Attribute Method 3: DAISY - LACE Module Method 4: KISS Databuild Creation Macro
(Tool used most often with rollouts) Tool
Input data format Excel: Customer Information Questionnaire Excel
(CIQ)
Output data eNB commissioning files (xml) or eNB commissioning files (xml)
OSS database (xml)

SW required DAISY + Plan Editor None specific. Excel

Licensing License for DAISY (SW .lic file) & None.
Plan Editor software license (.lf file)
Online / Offline Offline Offline
Optimizer SITE object Yes, allows creation of SITE object No, SITE object must be created afterwards
creation readiness in in NetAct
import
Site template data No, input data is according to fixed input Yes, site template parameters can be freely
parameter customizability data format (CIQ), empty parameters customized
replaced with Plan Editor defaults

51 © Nokia 2016
Useful Links

52 © Nokia 2016
Useful Links

- Configuration Management Information:

• Configuration Management Guidance material
• LTE Radio Network Design for Rollout (RNDR) Training information

- Parameter Configuration References

• NIDD (Networks Integrated Data Dictionary)
• PKDB (found within MINT tool)
• System configuration files

53 © Nokia 2016
Useful Links
- BTS SM Information:
• Instructions for using BTS SM File Creation

• NOLS – used to download BTS SM software

( access required to NOLS and to download software) : Radio Network -> Base Stations ->
Flexi Multiradio BTS LTE and Flexi Multiradio BTS TD-LTE

• Some example copies of BTS Site Managers

54 © Nokia 2016
Useful Links

- Plan Creation with NetAct CM

- NetAct Plan Editor Information

• Instructions for using Plan Editor:

• General Plan Editor information (software and documentation)

• Plan Editor FAQ:

- KISS Information – includes tool, instructions, and examples

55 © Nokia 2016
Useful Links
• DAISY Information:
• DAISY Instructions

• Official DAISY Tool Suite Space

- DAISY SW
• An empty Plan Editor (PE) database and the valid CIQ file for that DAISY version is part of the
package, within folder LACE/Input
[e.g. \My Documents\NOKIA\DAISY\PROJECTS\LTE_LACE_RL70\WorkDir\LACE\Input]
- DAISY License Request form
- DAISY LTE CIQs

56 © Nokia 2016