parameter overview v1_6

1 © Nokia Siemens Networks Presentation / Author / DateCompany Confidential

Parameter Overview


eNodeB ParametersWhat are they?

• Constants and threshold values that define and configure the functions of the RRM

• Radio Resource Manager (RRM)– Manages the utilization of the radio resources

– Consist of different functions: i.e. Power Control, Radio Admission Control, Connection Mobility Control…

– Functions consist on algorithms that define HOW to handle the radio resources

– Algorithms use parameters that define specifically WHAT to do

Example: CMC- Handover: Better cell algorithm, A3 case

Do handover towards better cell if it is better than a3Offset=5dB for at least a3TimeToTrigger=1280ms


eNodeB ParametersWhere to find them?

• Main sources: – Parameter Dictionary Database (PDDB):

▪ http://esodts051.emea.nsn-net.net:8080/pddb/

– Parameter Knowledge Database (NetEng):

▪ https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/417780970

• Other sources:– 3GPP Specifications (36.xxx series):

▪ http://www.3gpp.org/ftp/Specs/html-info/36-series.htm

– SFS (System Feature Specifications): limited access. Instead refer to Network Engineering Enabling:


• Additional material:– LTE PAR training (RL10):


– NSN Academy:

▪ https://networks-academy.inside.nokiasiemensnetworks.com/nsnintranet/

▪ Training number/title: RA4134-15A/ LTE Radio Parameters [RL15]

▪ Academy portal search key word: “LTE Radio Parameters”


Parameter Tool Interworking (by Network Eng.)

Customer / User PerspectiveCustomer / User Perspective

What is the meaning of this parameter ‘prachconfIndex’ ?

How does the feature ‘Rate capping’ work?

I have to configure Power Control. Which parameters

are involved and what is their impact?Q

ues

tio

ns

to b

e an

swer

edQ

ues

tio

ns

to b

e an

swer

ed


Parameter Tool Interworking (by Network Eng.)

Single source of informationSingle source of information


Where to find them?PDDB

http://esodts051.emea.nsn-net.net:8080/pddb/


Selecting the appropriate Release

Inc 22 for RL10

Note: from RL20 onwards increments are called ‘feature

builds’ (FB).

RL20 will be based on FB10.08


Managed Objects Hierarchy


How to Visualize them?Three methods

A) Selecting the Manage object to list ALL parameters under that managed object

B) Doing a search for the parameter if name is known

C) Creating a Report containing all parameters• Recommended as it provides an off-

line reference list


Creating a report


• Parameter manipulation:

– eNodeB databuild contains both, RF and TRS parameters

– Databuild template for FDD LTE: https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=420184015&objAction=Browse&viewType=1

– Excel databuild is converted to XML files, e.g. (LACE process)

– Manipulation of parameter during trials is based on edit & upload xml files

• Example of eNB SCF file for RL15:

Parameter list and parameter manipulation

• Excel with RL15 parameters as created and downloaded from PDDB:

RL15_scf.xml

Rl15_pddb_export_July2011.xls


Comparison of site db creation methodsAttribute Method 1: NetAct with site

templates (supports TD-LTE)

Method 2: DAISY-LACE Method 3: Plan Editor using template sets (supports TD-LTE)

Input data format CSV or XML Excel, Customer Information Questionnaire (CIQ)

CSV

Output data Site CM data in OSS database.

eNB commissioning files (xml) or OSS database (xml)

eNB commissioning files (xml) or OSS database (xml)

SW required NetAct OSS DAISY-LACE + Plan Editor

Plan Editor

Licensing Basic NetAct functionality License for DAISY-LACE (hw dongle), Plan Editor soft license (.lf file)

Plan Editor soft license (.lf file)

On-line / Off-line On-line, connection to NetAct required to import data with CMO Manager, and to apply site template

Off-line Off-line

Optimizer SITE object creation readiness in import

Yes, allows creation of SITE object in the CSV import (OSS5.2 CD3 MP1 or later)

No, SITE object must be created afterwards in NetAct

No, SITE object must be created afterwards in NetAct

Site template data parameter customizability

Yes, site template parameters can be freely customized

No, input data is according to fixed input data format (CIQ), empty parameters replaced with PDDB defaults

Yes, site template parameters can be freely customized using PE template sets

CIQ = Customer Information Questionnaire


General DAISY LACE, LTE tool chain

NetAct Plan Editor

NetActRAC

PlanEditor

PE Templates

XML

12

3

4

XLS

(see next slide for description)

DAISY LACE

XML

TRSplanning

eng.

CIQ

Radio

planning eng.

Daisy is hiding all the activities in PE,

simplifying tasks of data creation


DAISY for LACEThe process step-by-step

The CIQ (Customer Interface Questionnaire) excel file is provided by the user to DAISY LACE. The file contains the mandatory information and parameters to be handled in DAISY–PE to build-up the final database.

DAISY LACE reads the CIQ fields and aggregates the parameters per managed object (i.e. according to the NSN RNW database structure), towards an “intermediate” output in RAML2.0 xml format. This output can be interpreted by Plan Editor.

The “intermediate” output RAML2.0 file is automatically transferred from DAISY to Plan Editor. At this stage, the “basic” parameter set handled from CIQ to DAISY is merged into the “default” parameter set already configured in PE.

The “default” parameter set to build-up the database is driven by DAISY, by specifying the proper PE template names for each managed object.

DAISY drives Plan Editor, to generate the “final” output, as either a xml Plan

1

2

3

4


DAISY is a dedicated module of MUSA tool. It can be used in all WSE and Global projects

To run the tool users need hardware dongles with an expiration date. Licenses must be requested to [email protected].

SW downloads, installation procedures, roadmap, and other documentation, can be found on IMS at:

https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/395892487

For more information and support please contact:

[email protected] [email protected]

[email protected]@nsn.com

DAISY

Tool availability and licensing

MUSA HW Key


This is the 4th procedure to create SCF files and once created the file can be directly imported to eNodeB.

The process uses a customized Excel Macro where both RF and TRS inputs are combined to generate the SCF files.

Attached is a PPT to explain step by step process for file generation and in the optional folder has the output files for reference.

SCF File Creation using inbuilt Excel Macro

Microsoft Office PowerPoint 97-2003 Prese

parameter overview v1_6

Documents