Está en la página 1de 113

MUSA Functionality

Overview
03-June-2015
Leandro Palagiano, Daniele Brancato, Rosario Colaianni, Tom Scaliatine

1
03/06/2015 Nokia 2014 - MUSA Functionality Overview
Nokia Internal Use

MUSA Functionality Overview


Revision history and metadata
Document ID: D532115485
Document location: https://sharenet-ims.inside.nsn.com/Overview/D532115485
Organization: Networks/GS/NPO/Execution Excellence
Version

Description of Changes

Date

Author

Owner

Status

Reviewed by

Reviewed
Date

Approver

Approval
Date

1.0

First released version of the document

03-06-2015

L. Palagiano

T. Scaliatine

Released

T. Scaliatine

02-06-2015

T. Scaliatine

02-06-2015

1.1

Added compliance page

03-06-2015

L. Palagiano

T. Scaliatine

Released

T. Scaliatine

03-06-2015

T. Scaliatine

03-06-2015

2 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Contents
Introduction

Neighbors Analysis

Overview
Important to know
Differentiators and Intellectual Property Rights
General information and licensing
Features

Tool Configuration

MUSA Projects concept


Environment, Maps, DTM
3D Antenna Catalog
Site DB creation

ADA module basics


System/Band Check Reports
Consistency Checks using the GUI interface
Distance Checks
Customer Strategy Checks and Automation
Checks using KPIs
Checks using Measurements
LTE Specific Checks

UE Trace Analysis

Radio Coverage Analysis (RCA) and Optimization (RCO)

Planning Features

Scanner Measurement files loading


Basic views (Maps, Servers views, single cells views, Statistics &
CDF, Time view, etc.)
Measurement merge
Measurement Pre-Processing: Pixelling
Irregular Coverage Recognition (Islands Analysis)
Coverage Pollution
Coverage simulation (Tilt/Azimuth/Power)
Static and Dynamic 3G Load Simulation
Static and Dynamic LTE Load Simulation
LTE Throughput Simulation

3 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Loading UE Log Files


Additional functionalities
L3/NAS and other Messages

Code re-usage assessment


PCI/PRACH assessment
PCI/PRACH planning
LTE Uplink Interference mitigation

Multi Layer Optimization

Multiple views
Multiple Coverage Simulation (RF Sharing)
Layers Simulation (Idle mode simulation)

MUSA
Introduction

4 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA - Overview
MUSA is a drive test post processing tool created to support mobile network planning and
optimization
-

In use since 2001

Does not focus on generic drive test post-processing


-

Rather provides series of modules covering specific analysis and optimization needs, and can integrate
information coming from other sources (e.g. Geo-Location measurement, PM counters, etc.)

For example, Coverage Simulation/Load Optimization, LTE PCI parameter planning,

Designed for GSM, WCDMA, LTE and other Technologies; Nokia or Multi-Vendor
Nokia internally developed and maintained by GSD DE NPO Automation
-

No licensing cost

Runs on laptop connected to Nokia Intranet

Easily configurable: wizards for site database creation from NetAct/PlanEditor/Excel, Geographic
maps from the web.
5 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA - Important to know

Although the tool can now read many file formats


natively (e.g. NeMo), it cannot import data from any
available commercial tool: However, MUSA has a
Text/CSV import wizard to help users import data
from unsupported sources in a generic way.

MUSA focuses on specific topics, relevant for the


network assessment and optimization, so users
can find in MUSA specific analysis and metrics not
common in other drive test analysis tools.

Conversely, it is not a complex database


programmable environment typical of other heavy
commercial tools.

6 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA - Differentiators and Intellectual Property Rights (IPR)


Measurement processing based on binning per territory square elements (pixels)
Irregular Coverage Analysis by means of the islands concept (patented)
Coverage Optimization based on measurements (patented)
Coverage Pollution analysis (on going IPR request)
Simulation for the Tilt/Azimuth optimization (patented)
3D Antenna Patterns calculation for realistic and accurate simulations
Call Trace Analysis functionalities

Load Simulation (patented)


Generic Algorithms for automatic coverage optimization (on going IPR request)
Multi Layer Coverage Simulations for RF Sharing
Advanced Multi Layer/Multi Technology Neighbors Module
State of the Art Downlink PCI/PRACH planning with Uplink Interference Optimization
7 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA - General Information and licensing

MUSA is a standalone Windows application that can be used in all NPO projects for free
- Tool Roadmap:

Runs on Nokia or equivalent laptops directly or VPN connected to the Nokia Intranet
- Minimum System Requirements:

https://sharenet-ims.inside.nsn.com/Open/525627274

https://sharenet-ims.inside.nsn.com/Overview/D529289165

Free Software License required


- License Request Form:

https://sharenet-ims.inside.nsn.com/Overview/D487910839

- License Activation:

https://sharenet-ims.inside.nsn.com/Overview/D487807283

IMS Pages
- Presentations and Videos:

https://sharenet-ims.inside.nsn.com/Open/531462853

- SW Downloads:

https://sharenet-ims.inside.nsn.com/Open/428210505

8 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Main Features Table


Functionality

Technology

Notes

Support for other vendors

LTE, WCDMA, GSM

By means of generic csv/Excel files to import data and create Site DB

DTM, Scan-Maps, Web-Maps, Vectors, Clutter maps

LTE, WCDMA, GSM

DTM/Clutter maps in Asset/.grd/.bil formats


Webmaps from HERE, Google Maps, Bing, OpenStreetMap.

LTE, WCDMA, GSM

GSM: ARFCN/BSIC (co/adj-channels)


WCDMA: UARFCN/SC
LTE: PCI Conflicts/Confusion/Mod3/Mod6/Mod30, PRACH violations

Network Code Assessment


PCI/PRACH Planning
Pixelling

LTE
LTE, WCDMA, GSM

Enables detailed planning of PCI, rootSeqIndex, grpAssigPUSCH, ulRsCs.


Uplink Interference mitigation.
1/2/5/10/20/50/100m. 1m pre-pixelling available

Irregular Coverage Recognition (ICR or Islands)

LTE, WCDMA

GSM will be available soon

Coverage Pollution

LTE, WCDMA

Pilot Pollution on WCDMA, Coverage Pollution on LTE

Neighbors Analysis and Optimization

LTE, WCDMA, GSM

Throughput Estimation/Simulation
Coverage Simulation

LTE
LTE, WCDMA, GSM

Load Simulation

LTE, WCDMA

Automatic suggestion for neighbor addition/removal (LTE/WCDMA). Split by


technology/band/layers. Generic manipulation functions. CoLocation functions. Consistency
checks. SIB#11/Max Count. Possibility to generate new relations and edit existing ones.
Downlink Throughput
Tilt, Azimuth, Power Offset, Attenuation change allowed.
Uses 3D Antenna patterns. Can affect multiple layers.
Static and Dynamic (hour-to-hour). It is also possible to calculate the unloaded snapshot
(*) Multi Layer Simulations, VoLTE, and Carrier Aggregation features currently under development

9 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA
Tool Configuration

10 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA - Tool Configuration - Projects in MUSA


Tool projects are simply folders but with a particular structure of sub-folders. They can represents towns,
regions, clusters, or different scenarios. Many settings, legends, and configurations are project-based.

+ New Project
11 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

New Folders created in the


MUSA\Projects

MUSA - Tool Configuration Environment, Maps, DTM (1/2)


Many analysis and optimization features of MUSA will require the correct configuration of terrain height
data. The tool can work with Asset format (binary files + index) or with other formats common to other
planning tools such as .bil and .grd.
Enterprise Asset DTM configuration for MUSA

12 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA - Tool Configuration Environment, Maps, DTM (2/2)


Scan-Maps, Vectors, Polygons, Clutters files can be imported from planning tools. Backdrop maps can be
also automatically downloaded from internet (OpenStreetMap, Here, Google, Bing, etc.). A local cache is
used to speed up navigation when an internet connection is not available.
OpenStreetMaps

13 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Here Satellite Maps

MUSA - Tool Configuration 3D Antenna Catalog


Some features, such as Tilt/Azimuth simulations, requires the correct configuration of antenna files: MUSA
uses 3D antenna patterns. A rich catalog of antenna models is already present in the
MUSA\Resources\Aerials.
If an antenna type is not present, a 3D model can be generated starting from files
available from customers planning department or antenna manufacturer (*.msi files)

MUSA 3D Antenna Catalog

Correct text to be used in the Site DB creation


Excel file (3D pattern @ 1710 MHz):
5NPX1006F-1710_TE6.3dd 5NPX1006F-1710

14 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA - Tool Configuration Site DB Creation


Site DB data can be done in many ways, starting from Excel template and/or Plan Editor .mdb or NetAct .xml
files (UI values). Users will be guided by means of a dedicated Import Wizard
Some Site DB rules

Templates for Site DB creation for all technology


can be found in MUSA\Help\NetworkTemplate folder

15 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA uses SITE and SECTORS as key information


no duplicates allowed
Black columns are mandatory
Blue columns are optional or mandatory depending on the
features (e.g. Tilt and Antenna become mandatory for
simulations)
Green columns are mandatory for external cells and other
vendors

MUSA - Tool Configuration Site DB Creation LTE step by step example (1/2)

Step 2a - Select Actual


Configuration Exported
by NetAct

Step 1 - Select Import Format type

16 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Step 2b - Select additional


OSS file e.g. Sites
belonging to different OSS

MUSA - Tool Configuration Site DB Creation - LTE step by step example (2/2)

Step 3 - Select
Excel Network File

Step 4 - Select additional


Neighbor List and/or Save
Network File

17 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Check site position using maps


and parameters using the Network
Manager window

MUSA for Radio Coverage


Analysis and Optimization

18 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Scanner Measurement file loading


MUSA is able to directly load scanner drive test
data from NeMo/ANITE (so all files with extension
.nmf will work). MUSA converts all input files into
.sgf files which is a MUSA proprietary format.

In case of measurement traced with unsupported tools, it is


possible to import data as text or csv file, using the dedicated
import function and a few settings.
Configurations file can be saved to import data in the future.
Using the Generic Measurement Import function it is possible
to import in MUSA also data from Geo-location data or other
sources.
19 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA RCA/RCO Basic Views

MUSA maps

20 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

By pressing Scanner you will


open DT measurements.
Then you are able to
visualize any series of data
(e.g. LTE RSRP/RSRQ) for
first, second, third, etc..
Special series LTEID
shows the best servers(first,
second etc).
Data can be also shown on
the map by cell instead of by
server.
Measurements can be
studied also per geographical
polygon (cluster)

MUSA RCA/RCO Basic Views


Showing Cell-based info
Example: How to show PCI values on maps
In order to visualize the PCI parameter, press
the NW button then add the info phyCellId
into the Add from Network Parameters window
then from Route Properties window under the
Network Tab check the box Lb (Label).

It is possible to show
parameters,
counters and any
other cell-based
data value on the
map.
MUSA allows one to
import and display
data from generic
excel files.
Data can be shown
using labels, cell
areas and borders,
with customized
legends
21 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA RCA/RCO Basic Views

Several
distributions
available

Display mode
CDF, Distribution,
Pie

22 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Coverage Statistics
By pressing these buttons MUSA
will calculate the CDF distributions
from the loaded scanner
measurements. By playing with
the % it will be possible to show
on the chart the corresponding
value e.g. 5% correspond to 95
percentile of the measures or 95%
probability value.

MUSA RCA/RCO Basic Views


Synchronized views

Data can be studied simultaneously on many different


views, for example using a maps showing the Best
Server power, a second map showing the RSSI, Time
Charts, etc.)
All MUSA views can be synchronized with each other.

Export for Additional Analysis


In case of additional further detailed analysis, data can be
exported similar to other commercial solutions
23 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA RCA/RCO Measurement data merge


Select Nemo .nmf

Pressing Scanner
then queue files
its possible to
create a single
concatenated file
representing the
whole drive test
campaign.

Press this button to


transfer the files and
combine them into a
single file
Press Auto to
sort all files

Scanner files
to be
grouped into
one file

24 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Provide a new name for


the .sgf file which will later
be loaded via MUSA
Measurement menu

MUSA RCA/RCO Measurement Pre-Processing: Pixelling (1/2)


Prerequisite of any analysis and optimization using drive test data is the pixelling process (e.g. by 10x10 meters pixel square
territory element). This is important to fight against DT collection systematic errors (generally car spends a lot of time at the
same point of the route due to traffic jam or traffic lights. Bias issues can also be due to multiple passes at the same locations
and/or varying speeds). Pixelling also helps to mitigate fading effects.

For each pixel, an average value of the measurements is calculated and considered representative of the entire pixel

Users can decide the pixel size

For each pixel, a Best Server can be elected according to one of the following rules:

- By count the most present cell considering measurement points within the pixel
- By level the cell with the highest power value within the pixel

25 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Measurement Pre-Processing: Pixelling (2/2)

1. Load the whole campaign


(concatenated) scanner
measurement file

2. Press this button to start the Pixelling procedure which helps to provide better quality
measurements than the original scanner files.
The default pixel size is 10mx10m, i.e. a good compromise between precision and averaging
effect. A pre-processing of 1mx1m is usually applied to enhance measurement quality.
The algorithm will calculate for all points the average value of the best server RSRP and
other measured values from the scanner data. A dedicated MUSA file is created in order to
avoid the successive re-execution of the process (pixelling is time consuming and can
requires several minutes of elaboration even on powerful laptops).

26 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO ICR (Islands Analysis)


ICR = Irregular Coverage Recognition, also indicated as Islands Analysis.
It is a patented analysis method: the island concept is used to study the irregular and fragmented
coverage areas.

A cell can be the best server in different size areas that may be situated near or far from the site. If the cell
is indicated as the best server in a lot of areas distant from the site, then it could be an interfering cell.
By means of Island analysis, it is possible to find out the cells competence area.
Here we see that there are islands of unwanted or irregular coverage in
Cell A coverage area being produced by Cell B
Objective of ICR is to capture these areas
and to optimize Cell B coverage
to remove them

Cell B
Cell A
27 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA RCA/RCO ICR (Islands Analysis)


We dont need the boundaries obtained from predictions calculations!
The blue line is the route followed during the measurement campaign, after
correct pre-processing by mean of pixelling.
Red and green pixels represent different islands for the two cells of the figure.

28 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO ICR (Islands Analysis) Example


For each pixel where there are measurement samples, the best server cell is determined.
An island is defined as a set of contiguous pixels (where a cell is the best server) together with some
rules regarding the islands surface and distance between the pixels.
We use the following rules:

Distance = 1 pixel
Surface = 1 pixels
Means that one island must contain
at least 1 pixel and the distance
between them can be up to 1 pixel

Filter (1-1)
3 island total

1 island of 6 pixels
1 island of 2 pixels
1 island of 1 pixel

Filter (1-2)
2 island total

1 island of 6 pixels
1 island of 2 pixels

Filter (2-2)
1 island total

1 island of 9 pixels

Distance = 1 pixel
Surface = 2 pixels
Distance = 2 pixels,
Surface = 2 pixels

Filter (Distance, Surface)

29 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO ICR (Islands Analysis)


Islands can be used also to understand Interference origin, looking at how number of
islands changes with filter settings

If number of islands decreases changing S (surface) from 1 to 2


cell is generating interference
In fact: excluding the biggest island (proper coverage area) is the case of many little islands,
far from the cell, which will be neglected changing S from 1 to 2

If number of islands decreases changing D (distance) from 1 to 2


cell is affected by interference
In fact: many medium/big islands interrupted by gaps of 1 (or few) pixels.
Changing D from 1 to 2 a unique (or a few) islands will be grouped

Some reports are automatically generated in <YourProject>\Result\island


Basic Report

Difference Report

Comparison Report

Report_Islands 5-1-1

Islands 5-2-2 Islands 5-1-2

Comparison Islands 5-1-1 Islands 5-1-2 Islands 5-2-2

Report_Islands 5-1-2

Islands 5-2-2 Islands 5-1-1

Global Comparison Islands 5-1-1 Islands 5-1-2 Islands 5-2-2

Report_Islands 5-2-2

Islands 5-1-2 Islands 5-1-1

Critical Cells Islands 5-1-1 Islands 5-1-2 Islands 5-2-2

30 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO ICR (Islands Analysis)


MUSA provides some dedicated Island chart for each filtering criteria.
In any window in the Series drop down menu it is possible to choose between
the following several Indicators, calculated as following:
Islands: simple number of Islands per cell
Islands over mean distance: number of Islands per serving cell that are over the mean value of distance (distance of the
Islands from the relative serving cell)
Islands over mean distance excluded biggest: it is similar to the series above but, in this case, the biggest Island is excluded
from the count
Islands over mean distance weighted on Surface: number of Islands per serving cell that are over the weighted distance,
defined as:
where Di is the distance of the Island-i from the serving cell and Ai is the surface (number of pixels of the Island-i)
Islands over mean distance weighted on Surface excluded biggest: it is similar to the series above but, in this case, the
biggest Island is excluded from the count
Islands over mean distance [weighted on Surface] and Surface: number of Islands per serving cell that are over the weighted
distance AND that are over the mean value of surface (Surface of the Islands of the considered serving cell)
Islands over mean distance [weighted on Surface] and Surface excluded biggest: it is similar to the series above but, in this
case, the biggest Island is excluded from the count
31 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA RCA/RCO ICR (Islands Analysis)


MUSA calculates charts with the resulting number of islands per cell. Many indicators are provided, and in
this case cells are ranked using a weighting factor that takes into account the distance of the islands from
the originating cell and also the area of the islands itself. Its a way to isolate the worst cases.
By pressing the island button the tool will produce
reports for the filters (D=1,S=1);(D=1,S=2),(D=2,S=2)

Analyzing the Island reports, in case of a


networks which has more than 10 sites its
possible to detect abnormal coverage patterns
and cell which might be interfered with or
interfering with other cells. By sorting the charts
and reading the reports, its possible to create a
top ten list of cells for the priority to be given in
terms of optimization. The next slides will
explain the use of the islands feature.
32 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA RCA/RCO ICR (Islands Analysis) MUSA vs. Actix-1


Correlation with Actix-1 and Pollution Analysis
Not useful result

Actix-1 Event Driven analysis

Useful result

FP=MUSA First Polluter


Most Islands
identified were useful
suggestions

FP
FP

FP
FP

FP
FP

33 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Coverage Pollution UMTS Pilot Pollution (1/2)


3G Pilot pollution is identified on the basis of the number of observed scrambling codes (more than three)
We suggest warning indication thresholds based on RSCP or Ec/Io levels as shown in the example below:
Tool 3G Pilot Pollution settings

-76
Best Server P-CPICH
RSCP = -80

Class 1
Pollution

Critical: very strong


pilot pollution state

-84
Class 2
Pollution

Warning pilot
pollution state

-89

Tool 3G Pilot Pollution Enabling

Class 3
Pollution

-100
34 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

Neglectable: Low
pilot pollution state

MUSA RCA/RCO Coverage Pollution UMTS Pilot Pollution (2/2)


MUSA provides some dedicated Pollution charts, with several Indicators, allowing users to rank cells in
the Network and easily find top polluters.

35 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Coverage Pollution LTE case (1/3)


Coverage pollution has been defined based on the following information
and tables:

Number of cells in each Pixel (excluding the Best Server (BS))

Delta level in dB of each cell from the BS

Classification and equivalence of servers classes (from SINR)

Distance in meters from the BS

Minimum RSRP level of the BS

36 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

LTE Coverage Pollution map

MUSA RCA/RCO Coverage Pollution LTE case (2/3)


Class definition in terms of delta
dB from the BS Signal level
Weighting factors to calculate
equivalent Class 1 number of
servers (from SINR analysis)
Distance ranges definition in order
to address Coverage Pollution
classification (together with
equivalent Class1 number of
servers)

Minimum Signal level to apply the


pollution analysis, otherwise
Poor Coverage condition will be
reported
Cell Polluters parameters, to
identify strongest polluter per
classes, with the possibility to
exclude cells belonging to the BS
37 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

LTE Polluter chart

MUSA RCA/RCO Coverage Pollution LTE Case (3/3)


Quick indication regarding Coverage Pollution
condition

Distribution of servers per classes, with quick


indication for Pollution condition, BS and 2
Server

Indication regarding who is the polluter, also per


pollution category (Critical, Warning, Neglectable)
and with reference to the InterSite (IS) cells
Indication regarding who is the strongest polluter,
also per class and with reference to the InterSite (IS)
cells

38 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Coverage Pollution MUSA vs. Actix-1


Correlation with Actix-1 and Island Analysis
Not useful result

Actix-1 Event Driven analysis

Useful result

Is=MUSA Island Analysis

Is
Most top Polluters
identified were useful
suggestions

Is

Is
Is

39 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Is

Is

MUSA RCA/RCO Coverage Simulation (1/2)


Press the Omega button to start the coverage simulations.
A new window will appear with information on total tilt
(mechanical + electrical), Azimuth, Power, etc.
For example, it is possible to change the tilt value by double
clicking on the desired cell and MUSA will directly show the
results on the map.
Touched cells are displayed using red circles or other
graphical symbols.
Advanced Coverage Simulation
Impact estimation on RSSI, Cell Power and Interference
Interference estimation for all surrounding cells

Azimuth Downtilt Power

Load

40 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

3D Antenna Patterns
In the coverage simulation (Tilt/Azimth
changes) MUSA uses sophisticated 3D
Antenna Patterns generated from
Horizontal and Vertical sections (usually
from .msi files from Antenna
Manufacturer).
The hit point is determined using
apparent angle between measurement
point and antenna electrical center.

MUSA RCA/RCO Coverage Simulation (2/2)


BS Area example after Antenna Tilting
Usually changes are driven by ICR and polluter analysis
and help the planner in having a wide understanding of the
potential impact of RF changes
It is also possible to re-calculate ICR and pollution after the
changes in order to verify the correctness of proposed
changes
Coverage splash
can clearly be seen
on A562 Bridge

41 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Coverage splash
remediated using ICR
detection and analysis

MUSA RCA/RCO Coverage Simulation Genetic Algorithms


Automatic Optimization using Genetic Algorithms

Available for 3G
Customizable Pool size
Fitness function calculated using ICR,
pollution, and coverage/interference KPIs

42 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Load Simulation Overview


Load Simulation methodology allows one to anticipate the impact on coverage quality
coming from traffic load leading to adequate optimization countermeasures and preparing
the network for the next steps in traffic growth.

Tasks:

Simulation of load in the network

Handling of Different Traffic Load scenarios

Reduce measurement effort for operators

Results:

Indication when the Network provides insufficient quality

Parameters tuning / optimization for loaded Network

43 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Load Simulation Advantages


Load Simulation Advantages

To follow network and traffic growth

To simulate different load scenarios

To find countermeasures by means of proven antenna tilt/azimuth/power coverage


simulations

To reduce the need of a new measurement campaign to be performed while traffic is


increasing

Optimal usage of sites and fine selection of new sites

Multi vendor applicable solution

44 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Load Simulation Scenarios

Static Load Simulations

Unloaded snapshot estimation


With uniform load distribution
With specific load at cell level

Dynamic Load Simulations

Network and traffic growth forecast


Traffic distribution from counters
Traffic distribution estimated from measurement

45 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Load

Time

MUSA RCA/RCO 3G Load Simulation


Ec/Io in call handling procedure

Soft Handover
Inter System Handover
Inter Frequency Handover

Without Load Simulation

With Load Simulation

Network load will modify Ec/Io distribution

New Ec/Io distribution can be estimated

Impact of Low Ec/Io:

Reduced Impact of Low Ec/Io

Impaired Call drop and Access figures


Reduced exploitation of new offered services

Traffic Lost
46 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

thanks to countermeasures proposed by load


simulation

Reduced Traffic Lost

MUSA RCA/RCO 3G Load Simulation


DL-PWR
100
0
%

DL-PWR
100
%

Drive Test Path

Generic Sample

RSCP
CPICH

Ec/Io =

RSCP
RSSI

47 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

DL-PWR
100
%

MUSA RCA/RCO 3G Load Simulation


The basic idea is to use the CPICH measurement as a

reference then apply Traffic Load through software simulations


based on in-field collected measurement data.
CPICH transmitted power is fixed, hence it can be used in
order to estimate the path loss between a single measurement

Pathloss 1

NodeB 1

Pathloss 2

pixel (or sample) and the transmitting NodeB


NodeB 2

The downlink quality measurement used in the UMTS is the CPICH Ec/Io:
Ec / Io

CPICH Best server


RSSI

But RSSI can be expressed as


N
M

Ec

RSSI No TxpwrCPICHi TxpwrotherCCCHi TxpwrDCH p Pathloss i f


, N DetectedCell , Level bestserverlastdet ected , Load
Io

i 1
p 1

where N is the number of detected cells per pixel and p is the number of DCH connections within the cell i
48 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA RCA/RCO LTE Load Simulation

RS transmitted power is used in order to estimate the path-loss between a single


measurement pixel (or sample) and the transmitting eNBs.

The basic idea is to calculate the effect on the drive test power measurement when a
cells total transmitted power is higher/lower due to changes in traffic load.

xloadi
Pathloss 1

NodeB 1

Pathloss 2

Drive Test Path


49 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

NodeB 2

RSRQ

RSRP
RSSI

MUSA RCA/RCO LTE Load Simulation


RSSI, RSRPs, and RSRQs are the downlink measurements used by the load simulation
algorithm implemented in MUSA. Quality is evaluated using the RSRQs or the calculated

SINRs:

RSRQ N

RSRP
RSSI

CalcSINR

RSRP serv
RSRPother I

(N is the number of Resource Blocks in the considered bandwidth)


Subframe

RSSI f ( I , TxPwrRSi , TxPwrctrl / trf , Pathloss i , RSRQi ,


N DetectedCell , LevelBS LastDetected , xLoadi )

It is of course evaluated with reference to the RS


on the Resource Block frame and on the Antenna

Resource block = 12 subcarriers

RSSI can be expressed as a function of several terms:

Configuration (e.g. 2x2 MIMO)


50 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

RS used by the antenna port 0

MUSA RCA/RCO LTE Load Simulation


Load coefficients xi are expressed in unit of Resource Elements per Resource Block and can
range between 2 and 12 (or between 4 and 20 for MIMO antenna configurations).

Since measured RSSI is a function of these load coefficients,

RS

RS

any load change can be translated as a power variation.


MUSA can then estimate the impact of this change and
recalculate RSRQs creating a new

interference picture thus highlighting

Unloaded Resource Block


with RS Resource Elements

critical situations in network coverage.

xloadi

RSRQ

RSRP
RSSI
t

51 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Load Simulation Tool Cockpit


Collected measurement from drive test scanner or other sources

Antenna
tilt / azimuth/
power
simulations

New
Coverage
Interference
Picture

Load
Simulations

Unloaded Snapshot Cell specific load profile


Uniform load

52 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Dynamic load simulation

MUSA RCA/RCO Load Simulation Interference Estimation

53 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Load Simulation 3G Example (1/4)

54 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Load Simulation 3G Example (2/4)

55 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Load Simulation 3G Example (3/4)

56 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO Load Simulation 3G Example (3/4)

57 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA RCA/RCO LTE Throughput Simulation


When UE data is not available, MUSA can generate
and keep updated LTE throughput view.

Downlink throughput can be estimated starting


from current coverage condition.

It is re-calculated when a variable (Tilt, Azimuth,


Power, etc.) is modified by coverage simulation.

MUSA can also evaluate the impact on throughput


of any load profile applied by means of
static/dynamic simulations.

Current implementation is based on configuration files


per project located in <MUSAProject>\UserSettings\
ThroughputMapping.xlsx.

58 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA for
Neighbors Analysis

59 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis Adjacency Detailed Analysis (ADA) Module Basics


What is checked and analyzed?
Automated creation, validation and checking of neighbor relations prior to new or optimized plan
deployment
Tool prepares and checks the neighbor plan based on generated plan and customer rules
All types of neighbor relationship between different layers and different technologies are supported
Consistency Checks
-

Maximum number of allowed relationships , with reference to general System/Band limitations and Source and Target cell
types

Two-way relationships , Co-Location relationships, Intra-Site relationships

Distance checking

Missing neighbors identification from measurements or new generated lists

Customer-defined neighbor and parameter set rules with highlighting or automatic correction of mistakes

Parameter conditions that would block handovers

For LTE eNodeB controlled adjacencies, the tool can create the eNB look-up tables

60 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis ADA Module Basics


ADA is a dedicated module of MUSA tool specifically
designed for neighbors analysis.
ADA module can work with Nokia database. It can also
import data from Excel sheets (for other vendors).
ADA can graphically display relations, highlighting
different cell sets (LTE, 3G, 2G, Layers, clusters, etc.)
and neighbors using raster, vectors or web maps (e.g.
OpenStreetMaps, Google maps, Bing,etc).

Several operations can be applied to neighbor lists and


cell sets (union, intersection, difference, filtering, sorting,
etc.)
Powerful neighbor list checks are supported: missing
neighbors (cell and site missing), co-location checks,
SIB#11 and band limitations, and maximum count
checks, etc.
ADA module activation: quick button or from Tools menu Neighbours Analyzer)

61 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis ADA Module Basics Maps

Intuitive
graphical
viewing of
neighbours
on maps

62 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis ADA Module Basics Cell Sets

Cell Sets

Cell Sets can be defined


with external files, with
operations, or using
polygons

Operations

Cell Sets graphical


representation

63 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis ADA Module Basics Neighbours Lists

Neighbors
List

Operations and
Formulas
Neighbors List
graphical
representation

64 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis ADA Module Basics Navigation,Editing,Tables...

Controls to easily
customize map:
zoom, pan, grid,
ruler, backdrops,
web-maps, vectors

Navigation
panel to easily
find critical
relations

Neighbor List
editing
functions and
exports

Table View

65 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis ADA Module Basics


3D Exports on Google Earth

Representation on
several web maps
(street, satellite,
hybrid maps, terrain,
vectors, )

66 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis System/Band Check Reports


MUSA can generate reports to check SIB#11 and other
System/Layer/Band constraints
Neighbors Reports are
live: after their initial
generation, users can
modify settings and
thresholds and check
violations

Report on 2G Network, with ADCE/ADJW checks

Report on 3G Network,
with SIB#11 checks
67 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Neighbors Analysis Consistency Checks using the GUI interface


Maximum
Count and
SIB#11
checks

Reciprocal Missing,
Missing Intra-Site,
Co-Location checks
Neighbor List
analysis with
SIB#11 and
Distance details

68 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Neighbors Analysis Distance Checks


ADA module allows users to check neighbors,
filtering existing lists by distance (or using other
properties, KPIs, etc.)

Another strategy for the detection of missing/new


relations which involves distance calculation is
the following:
Generation of a totally new neighbors list using cell coordinates,
antenna directions, coverage radius, etc.
Difference calculation between existing lists and the new
generated one Candidate relations to be added
Difference calculation between the generated list and existing
ones Candidate relations to be deleted
Check of the delta list on the maps or using other features
69 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

Calculation of the delta neighbor list


Let A and B be two lists, (A - B) returns the
elements belonging to A and not present in B.
Note that the difference function doesnt
benefit of the commutative property, that
means (A - B) (B - A).
A

A-B=blue area

Neighbors generation: Co-located


relations, Intra site relations,
overlapping triangles
(details in the next slide)

MUSA Neighbors Analysis Distance Checks


Overlapping Coverage Triangles for neighbors list generation: cell coverage is
approximated using triangles and a relation is created for each overlapping area
Global parameters can be provided with the possibility to classify sites using two categories:
Either urban or rural depending on the number of other sites falling in a given circle
(urban distance threshold)

urban

B
A

rural

C
A

70 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Possibility to define
algorithm parameters cellby-cell, in the input file
using dedicated columns.
For any empty value, a
default will be used from
global parameters.

MUSA Neighbors Analysis Customer Strategy Checks and Automation


ADA module allows users to check
for specific neighbor strategies.
For example, a customer wants to forbid
3G F22G (except for co-located sites)
and needs always 3G F2F1 and 3G
F1 GSM.
Using ADA operators (Union,
Intersection, Difference, Filters by
source and/or target cells, Filter by
property, co-location function, etc.)
users can create complex check
functions.
Once built, it is possible to extract
general formulas and store them in
order to be able to quickly recall
them for other projects
71 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

ADA Formula
Manager

Set of built
in Formulas

Load
Formulas
from an .aff
file

Save
Formulas
into an .aff
file

To
customize
an existing
Formula
Set of
imported
Formulas

MUSA Neighbors Analysis Checks using KPIs


PM Counters, KPIs, and other information at neighbor relation level can be imported in ADA
using generic csv files.

Once imported, new neighbors lists


are created.

Users can show them on maps


(included information values), filter
by properties, and combine them
with all other standard functions
For example, it is possible to
identify relations belonging to the
network dump but with HO Attempt
= 0 or higher drop rates
72 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

Counters visualization on ADA map

MUSA Neighbors Analysis Checks using Measurements


Scanner measurements can be used to
identify new neighbors and relations to
be removed, of course only with
reference to the area of collection.

List and Cell Set


from measurements

Using information coming from pixelling


(and dedicated settings), ADA can import
and process Scanned Detected cells,
Pixel Add neighbor list, Pixel Remove
neighbor list.
Pixelling settings related to addition and removal
of neighbors

73 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Pre-defined formulas for


measurements suggestion

Measurements in ADA and an


example of Add suggestion (green)

MUSA Neighbors Analysis LTE Specific Checks


Specific checks have been integrated in ADA to identify useless relations created with ANR
function (ANR cleanup).
The main Idea of this function is to
identify LNADJ from Site A to Site B
where there are no LNREL from
each cell of Site A to every cell of
Site B and vice-versa

Example procedure (X2 cleanup):


KPIs from Reporting Suite have been imported in ADA
A list with Inter-eNB HO attempt = 0 has been filtered from LNREL
LNREL Filtered has been closed with reciprocal relatios
MUSA generates a list on inactive LNADJL where all cells belonging to Source Site do not have
any LNREL to any cells of Target Site
No LNREL list has been created via LNADJL LNREL CLOSED WITH RECIPROCAL
The latest candidate list has been analyzed graphically in MUSA, and confirmed site by site
(see red lines)
74 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA for the


UE Trace Analysis

75 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA UE Trace Analysis Loading UE Log File


UE traces from NeMo/Anite can be imported in
MUSA (.nmf file and export files)
User can select interested/relevant
information/events to be imported to MUSA
Data can be synchronized with scanner
measurements for a joint analysis

In the NeMo file format, there is the


description of the events recorded by the
tracing tool
If something is missing request might be
addressed to MUSA development team
UE data files can be concatenated
(see next slide)
76 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA UE Trace Analysis Additional Functionalities


UE data files can be merged together in order to encompass the whole drive test campaign
UE files which
want to be
grouped into
one file
Pressing Mobile
then queue files
its possible to
create a single file
import from UE DT
data.

Press this button to


transfer the files to
combine to a single one
Select Nemo .nmf

Press auto
to sort all
files
Provide a new
name to the mgf file
which will be the
one to load later
from Measurement
menu

77 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA UE Trace Analysis Additional Functionalities


All imported events and UE specific entities can be plotted
on maps (Throughput, BER, L3/NAS messages, etc.)

78 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA UE Trace Analysis Additional Functionalities


UE entities can be analyzed as scanner measurements, with Time Charts, CDF and
Distribution, etc.

79 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA UE Trace Analysis Additional Functionalities


MUSA can post process some UE data
and calculates automatically additional
information
Examples of Carrier Aggregation maps calculated by MUSA

80 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA UE Trace Analysis Additional Functionalities


Time between events and messages can be
computed and statistically represented
New columns are
added and data can
be exported or used
in MUSA Distribution
Graphs

81 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA UE Trace Analysis L3/NAS and other Messages


MUSA can show Level 3, NAS, MM and other messages recorded in the UE data, plot them
on maps, calculates time between events, and finally correlate them to radio conditions.
Dedicated functionalities are implemented to analyze
message flow and calculate 3G, 2G, and LTE CSFB
statistics

82 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA UE Trace Analysis L3/NAS and other Messages


CSFB Tuning example
CS Fallback is today the most used method to perform CS calls when connected to an LTE network
-

CSFB needs to be carefully tested and optimized especially from the call setup time point of view

Nokia has created MUSA functionality to analyze overall CSFB performance and time spent in the
different phases of CSFB

83 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA
Planning Features

84 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Planning Code Re-Usage Assessment


After the Site DB creation procedure, it is possible to check 2G/3G/LTE networks and verify
code assignments by means of the generation of some dedicated Excel reports

A critical distance can be defined to highlight in


red such conditions in the generated reports

Reports available on GSM networks

Reports can be generated as standard table or as


matrix. Below, an example of a matrix report
ARFCN (Adj-Channel): yellow cells represents
when the frequency is used as BCCH
ARFCN BCCH (Co-Channel)

Frequency reuse for the BCCH Co-channel

ARFCN BCCH(Adj-Channel)

Frequency reuse for the BCCH Adj-channel

ARFCN BCCH/BSIC

Frequency reuse for the BCCH/BSIC

ARFCN Co-Channel
Frequency reuse for traffic and BCCH Co-Channel
85 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Frequency reuse for traffic and Adj Co-Channel
NokiaARFCN
InternalAdj-Channel
Use

MUSA Planning LTE PCI/PRACH Assessment in the ADA module


Existing PCI/PRACH planning is extracted from the
Site DB and represented in ADA by means of
neighbors lists (LNADJL/G/W and LNREL/G/W) and
several Cell Set (per frequency layer)
Site DB
re-import

Important Note
LNADJ Concept is lost. At moment Is not possible to have site to site
representation therefore parameter like x2LinkStatus and
cPlaneIpAddrCtrl cannot be visulized

Deletion of
empty list

Each cell of eNB has neighbor with


all cells of target eNB if LNADJ is
there.
This means that a LNADJL might be
implicitly created by MUSA

Cell Set per Carrier are created


and per the attribute Group
defined in Excel Network File
86 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH Assessment in the ADA module


PCI / PRACH Assessment functionalities
ADA module can be used to verify an already
available PCI/RSI plan (made by MUSA or by
other tools)
LNADJL or any other imported neighbor lists
can be used for the check. If unavailable, the
tool will allow users to generate a list from
scratch
Calculation of several PCI indicators to be
shown on the map or used in the filters (e.g.
Mod3, Mod6, Mod30)

PCI Collision = two neighboring cells with the


same PCI
PCI Confusion: one cell with at least two
neighboring cells having the same PCI
PCI Mod3, Mod6: cannot be totally avoided
but should be minimized
PCI Mod30, checked using the
Sequence Group Number u
RSI collision, two neighboring cells with the
same rootSeqIndex
87 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH Assessment Collision/Confusion


Defined in the same way as Optimizer

Type1 - Collision

Type2 - Confusion

One site has been found as having Adj


towards two sites with the same PCI

88 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Planning LTE PCI/PRACH Assessment Neighbors creation


A neighbor list is necessary to assess the plan. If LNADJL or other neighbor lists are not available, a new list can
be generated by the tool using the triangles methods which creates relations for each coverage areas overlap.
Global parameters can be provided with the possibility to classify sites using two
categories: Either urban or rural depending on the number of other sites falling in a
given circle (urban distance threshold)

urban

B
A

rural

C
A

89 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Possibility to define
algorithm parameters cellby-cell, in the input file
using dedicated columns.
For any empty value, a
default will be used from
global parameters.

MUSA Planning LTE PCI/PRACH Assessment in the ADA module

5
3

2
4

NOTE: It is possible to verify an already planned


PCI/RSI NSN plan using the MUSA Site DB Import
Wizard and selecting in input the NetAct xml dump
90 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

Planned Parameters: PCI/RSI/grpAssigPUSCH


Indicators for the plan verification: Mod3/Mod6/Mod30(u)

MUSA Planning LTE PCI/PRACH Assessment


Collision, Confusion, Mod30 and all other kind of violations can be analyzed on the ADA maps, further
processed using ADA functionalities (e.g. filtering to find violations in 3 Km), and finally exported in Excel
format.
PCI Confusion Detection Example

91 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

RSI Collision Example (based on rootSeqIndex/Earfcn)

MUSA Planning LTE PCI/PRACH Assessment Mod3 collisions

Case: UE at the border of two cells who have the same PCImod3, RSRP from both cells = -67dBm in
both measurement cases (only PCI changed)
NSN 7210 TD dongle, 2.6GHz, 10MHz bandwidth
16
14

tput, Mbps

12
10

no PCImod3 collision

PCImod3 collision

6
4
2
0
1

9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53

seconds
92 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning


The PCI (Physical Cell Identity) is an essential configuration parameter of a radio cell.
Corresponds to a unique combination of one orthogonal sequence and one pseudo-random
sequence
504 unique PCI values are supported
Organised in 168 groups of 3 codes

A physical layer cell identity is thus uniquely defined by a group number (Gid) in the range of
0 to 167, representing the physical layer cell identity group. It defines the Secondary
Synchronisation Signal (SSS) sequence.
A second number (g) in the range of 0 to 2, represents the identity within the group. It defines
the Primary Synchronisation Signal (PSS) sequence.
PCI = Gid * 3 + g
93 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning


When a new e-NB is brought into the field, a PCI needs to be selected for each of its supported
cells while avoiding collision with respective neighbouring cells.

The PCI has an impact upon the allocation of Resource Elements to the Reference Signal and the set
of physical channels. The picture below illustrates the impact upon the allocation of resource elements
to the reference signal. All PCI within adjacent groups have a different allocation of resource elements
to the reference signal. The allocation pattern repeats every 6th PCI (every 2nd physical layer cell
identity group).

94 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning Nokia Recommendation


PCI Planning suggested rules are:
The isolation between cells which are assigned the same physical layer cell identity should be
maximised and should be sufficiently great to ensure that UE never simultaneously receive the
same identity from more than a single cell.
Whenever possible, cells belonging to the same eNodeB should be allocated identities from within
the same group (modulo 3 rule).
The neighbour cell will use PCI of the consecutive group or a PCI which is not interfering in DL
(modulo 6 rule)
Specific physical layer cell identities should be excluded from the plan to allow for future network
expansion.

There should be some level of co-ordination across international borders when allocating physical
layer cell identities.

95 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning PCI allocation overview


This feature was developed in 2010 to face the first LTE planning case in WSE, when no tools were
available for LTE. This feature has been used in many other cases. Since it requires a neighbor list as an
input, it has been placed in the ADA module of MUSA.
The planning can be done from scratch for the whole network, or per cluster, using an iterative process.
Already planned PCI will be considered in order to get the best possible planning.
In details, below and in the following slides, the processing steps will be summarized.
Sites without a PCI are sorted from North-West to
South-East
Generation of a preliminary neighbor list: we have to know which
cells can be reached from any cell to be planned. Other cells
belonging to the same site are managed in a different way, since
they have to share PCI of the same group.
=> Neighbors list generation by means of overlapping coverage
triangles (see next slide)
Each relation will be characterized with a weight, proportional to the
overlapping area, while also taking into account if the area is close to
or far away from the site.
Of course, a neighbors list generated in a different way (e.g. from other
planning tool) can also be used
96 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning PCI allocation overview


Overlapping Coverage Triangles for neighbors list generation
Global parameters can be provided with the possibility to classify sites using two
categories: Either urban or rural depending on the number of other sites falling in a
given circle (urban distance threshold)

B
Urban

A
B

Rural

The tool calculates the polygon center of the overlap area and the distance
from the overlapping polygon center to the site. The distance exponent is used
to distinguish the overlapping area close to or far from the site. So if I increase
the exponent, I consider more the near overlapping areas. If I decrease it, I
consider more the far overlapping areas. Setting it to 0 disables it.

Possibility to define algorithm


parameters cell-by-cell, in the
input file using dedicated
columns. For any empty
value, a default will be used
from global parameters.
97 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning PCI allocation overview


Selection of one even PCI group candidate and one odd PCI group candidate (range 0..167) for each cell, trying to
satisfy the minimum re-use distance (e.g. 25km).
Each PCI group contains 3 PCI codes (range 0..503).
If the site has up to 3 sectors, at the end only one PCI will be selected (the even or the odd), if the site has up to 6
sectors, both candidate will be used.
Selection of the best possible distribution of the PCI codes among the sectors of the site, considering the selected
candidates.
If the site has 3 sectors, and we have selected PCI group candidate 0 and 1, we will have 12 possible permutations:
0
0
5
.
2
1
1
2
3
4
If the site has 6 sectors, we have more possibilities, since all the 6 PCI codes can be mixed.
The selection is based on the minimization of the impact generated by the adjacent PCIs (as they can be reached using
the dummy neighbors list), using a dedicated lookup matrix and weights calculated for each adjacent relation.
PCI Codes
0, 6, 12, 18
1, 7, 13, 19
2, 8, 14, 20
3, 9, 15, 21
4, 10, 16, 22
5, 11 17, 23

Parity Type
Even-0
Even-1
Even-2
Odd-0
Odd-1
Odd-2

98 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Even-0

Even-1

Even-2

Odd-0

Odd-1

Odd-2

Even-0

Even-1

0.2

Even-2
Odd-0
Odd-1
Odd-2

PCI 16

PCI 7

MUSA Planning LTE PCI/PRACH planning PCI allocation overview


In the picture below other parameter that can be set in the ADA module:

A certain number of PCI groups


can be reserved for future
expansion using group or interval
of groups separated by commas
as in the following example:
3,5,7,10..20,75

Usage Notes:
ADA module consider SITENAME + SECTOR (e.g. AB0001_3) as the key information to uniquely identify a cell.
The tool can manage only up to 6 cells per site. In case you have more cells belonging to the same site, more sites (with a
different SITENAME) should be created.
Sector 0 can not be used (accepted values range from 1 to 9)
Single sectored site should be modeled with one sector, angle = 360, and more than 3 triangles (e.g. 12)
99 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning RSI allocation overview

The algorithm followed for RSI (RACH rootSeqIndex of the LNCEL object) planning is easier but, it does use the neighbors list
generated for the PCI.
Depending on the selected Cell Range parameter, a certain number of root sequence indexes will be reserved to each cell (see table
below). The final RSI assigned to each cell will be the first of the range.
The tool will try to satisfy the minimum re-use distance for this parameter (e.g. 10km).

Note: Similar to the PCI case, with regards to RSI allocation, it is possible to reserve a certain number of RSI codes for
future expansion.
In case of TDD LTE PrachCS format 4, range 138..837 must be reserved.
100 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning ADA Module


ADA module can be used to verify an already
available PCI/RSI plan (made by MUSA or by
other tools)
or to create a new PCI/RSI plan from scratch,
in clusters or for the whole network.
New PCI / RSI plan
Plan of grpAssigPUSCH/ulRsCs to mitigate
Mod 30 issues on the UL DM RS.
Calculation of several PCI indicator to be
shown on the map or used in the filters (e.g.
Mod3, Mod6, Mod30)

101 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

PCI/RSI plan verification


PCI Collision = two neighboring cells with the
same PCI
PCI Confusion: one cell with at least two
neighboring cells having the same PCI
PCI Mod3, Mod6: can not be avoided at all
but should be minimized
PCI Mod30, checked using the
Sequence Group Number u
RSI collision, two neighboring cells with the
same rootSeqIndex

MUSA Planning LTE PCI/PRACH planning ADA Module (step by step 1/4)
Cluster 1 specification by means of excel file, with coverage radius,
azimuth, beamwidth, etc.

4
2

5
1
3

6
102 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning ADA Module (step by step 2/4)
Neighbours calculation for Cluster 1, using a coverage triangles overlapping method.

5
103 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning ADA Module (step by step 3/4)
Physical Cell ID and Root Sequence Index calculation, considering minimum guard
distances and with the possibility to reserve some groups for future use
1

4
104 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA Planning LTE PCI/PRACH planning ADA Module (step by step 4/4)
The process can be iterative: after the specification of a new second cluster, it possible to add new PCIs and RSIs without changes in the
previous Cluster 1 allocation.

105 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Planning LTE Uplink Interference Mitigation


Mod30 violations: Mitigating UL DM RS issues with grpAssigPUSCH and ulRsCs

Planning can be done


iteratively and include
a prevent list.

grpAssigPUSCH can
be planned at LNBTS
or at LNCEL level, or
equal for the whole
site (SITE_U mode).

In case of Mod30 violations, it is possible to mitigate UL DM RS issues, planning the grpAssigPUSCH and/or ulRsCs
parameters, in order to have no violation on the Group Sequence Number u

u PCI grpAssigPUSCH mod 30

grpAssigPUSCH: group assignment for


PUSCH Range [029], step 1

It can be planned equally for all cells belonging to the same site (LNBTS strategy) or with a different values for each cell
(LNCEL strategy) or together with the ulRsCl - to have the same u for the site (SITE_U strategy).
The process can be iterated with an input priority list where ADA will try to avoid as much as possible Mod30 violations
106 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA for
Multi Layer Optimization
v.5.7 Feature

107 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA Multilayer Optimization Multiple Views


New version of MUSA can import multiple measurement files from different technology and frequency
layer, e.g. LTE FDD1900Mhz, TDDLTE2500Mhz, WCDMA1900Mhz. A new data table MUSA plane
is created for each of them.
MUSA planes
are created for
each technology
and frequency
layer

In that way, users can plot, analyze, and compare data in the same MUSA project using standard views,
maps, time chart, CDF, etc.

108 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

MUSA - Multilayer Optimization Multilayer Coverage Simulation (RF Sharing)


Coverage Simulation has been extended in order to estimate impact on all layers where a shared antenna
is used

WCDMA 1900

LTE 1900

Evaluation of the tilt/azimuth change on co-sites with an antenna shared between multiple technologies
109 03/06/2015 Nokia 2015 - MUSA Functionality Overview
Nokia Internal Use

MUSA - Multilayer Optimization Layer Simulation (Idle Mode Simulation)


Import of multiple scanner files from different technologies and visualization of the statistics on global cell
selection/reselection based on standard 3GPP parameters

MUSA planes (technologies and


frequency layers)

110 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

Visualization of selections and


reselections in the DT route
(Statistics available for the global
view or per EARFCN)

MUSA Other Features & Dev. Preview CDMA to LTE impact


Evaluation of the RF impact when refarming from CDMA to LTE

111 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

11
03/06/2015 Nokia 2014 - MUSA Functionality Overview
2
Nokia
Internal Use

Copyright and confidentiality

The contents of this document are proprietary and


confidential property of Nokia Solutions and Networks.
This document is provided subject to confidentiality
obligations of the applicable agreement(s).
This document is intended for use of Nokia Solutions
and Networks customers and collaborators only for the
purpose for which this document is submitted by Nokia
Solution and Networks. No part of this document may
be reproduced or made available to the public or to any
third party in any form or means without the prior
written permission of Nokia Solutions and Networks.
This document is to be used by properly trained
professional personnel. Any use of the contents in this
document is limited strictly to the use(s) specifically
created in the applicable agreement(s) under which the
document is submitted. The user of this document may
voluntarily provide suggestions, comments or other
feedback to Nokia Solutions and Networks in respect of
the contents of this document ("Feedback"). Such
Feedback may be used in Nokia Solutions and

Networks products and related specifications or other


documentation. Accordingly, if the user of this
document gives Nokia Solutions and Networks
Feedback on the contents of this document, Nokia
Solutions and Networks may freely use, disclose,
reproduce, license, distribute and otherwise
commercialize the feedback in any Nokia Solutions and
Networks product, technology, service, specification or
other documentation.
Nokia Solutions and Networks operates a policy of
ongoing development. Nokia Solutions and Networks
reserves the right to make changes and improvements
to any of the products and/or services described in this
document or withdraw this document at any time
without prior notice.
The contents of this document are provided "as is".
Except as required by applicable law, no warranties of
any kind, either express or implied, including, but not
limited to, the implied warranties of merchantability and

113 03/06/2015 Nokia 2015 - MUSA Functionality Overview


Nokia Internal Use

fitness for a particular purpose, are made in relation to


the accuracy, reliability or contents of this document.
NOKIA SOLUTIONS AND NETWORKS SHALL NOT
BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN
THIS DOCUMENT or for any loss of data or income or
any special, incidental, consequential, indirect or direct
damages howsoever caused, that might arise from the
use of this document or any contents of this document.
This document and the product(s) it describes are
protected by copyright according to the
applicable laws.
Nokia is a registered trademark of Nokia Corporation.
Other product and company names mentioned herein
may be trademarks or trade names of their respective
owners.
Nokia Solutions and Networks 2014