LTE PCI and rootSeqIndex (RSI) planning with MUSA tool Agenda MUSA introduction MUSA “ADA” module overview LTE PCI/RSI planning using the “ADA” module PCI plan assessment with “ADA” Tool Information, support, and licenses
For internal use 2 © Nokia Siemens Networks. All rights reserved.
MUSA introduction
For internal use 3 © Nokia Siemens Networks. All rights reserved.
MUSA – Main Features MUSA is a post processing tool created with the aim to support mobile networks performances analysis and optimization MUSA has been designed for: 3G, 2G, LTE (and other technologies) Drive tests post processing (but can integrate data from other sources, e.g. PMC) NSN networks and Multivendor technologies Coverage Analysis and Optimization Neighbors Analysis and processing Radio Parameter Adjustment Load Simulation For internal use 4 © Nokia Siemens Networks. All rights reserved.
MUSA – Relevant Modules and Technologies Site Database Import Wizards
PMC Integration
UMTS
Radio Coverage Analysis
Load Simulation
GSM
Scanner Drive Test Evaluation
GSM-R
UE Drive test Evaluation
WiFi
In Building Solution
LTE
Radio Coverage Optimization
Neighbors Analysis and Optimization
Radio Parameter Analysis and Adjustment For internal use 5 © Nokia Siemens Networks. All rights reserved.
Web maps & Google Earth Exports
Generic – MV (Excel – Csv)
MUSA – Important to know… • MUSA has been developed to support drive test activities of the rising • • •
•
3G networks in 2001/2002. During years 2002-2007 the tool was actively developed to address a wide set of topics in the Network Planning and Optimization areas, with the integration of new modules and innovative concepts. Although the tool can now read many file formats natively (e.g. Nemo) it is not configured as a general post-processing tool that can do anything importing data from any available source or commercial tool. It focuses on specific topics relevant for the network assessment and optimization, so you can find in MUSA specific aspects not common in other drive test analysis tool. Conversely it is not a complex database programmable environment, typical of other “heavy” commercial tools. In case of specific needs coming from projects, customizations or further developments can be evaluated, with the advantage that the development will be internal and effective.
For internal use 6 © Nokia Siemens Networks. All rights reserved.
MUSA – Solutions and Methodologies MUSA implements original solutions and methodologies for the Network analysis and Optimization, defined by NSN in the last years. Some of these algorithms are also covered by the European Patent. Here some topics: • Measurement processing based on binning per territory square pixels • Irregular Coverage Analysis by means of the “islands” concept (patented) • Coverage Optimisation based on measurements (patented) • Simulation for the Tilt/Azimuth optimization (patented) • Call Trace analysis • Load Simulation (patented) • Genetic Algorithms for automatic coverage optimization
For internal use 7 © Nokia Siemens Networks. All rights reserved.
MUSA “ADA” module overview
For internal use 8 © Nokia Siemens Networks. All rights reserved.
ADA Ancillary neighbours analisys
ADA is a dedicated module of MUSA tool, specifically design for neighbors analysis. ADA module can work with NSN database. It can also import data from Excel sheets (in case of other vendor). ADA can display relations, highlighting different cell set (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 check are supported: missing neighbors (cell and site missing), co-location checks, SIB#11 band limitations, and maximum count checks, etc. For internal use 9 © Nokia Siemens Networks. All rights reserved.
ADA from MUSA Toolbar To activate the “ADA” module please click on the highlighted button (or select Tools menu Neighbours Analyzer)
If the button is disabled please check the licence availability by pressing the highlighted button shown below
For internal use 10 © Nokia Siemens Networks. All rights reserved.
ADA: viewing neighbours on the map…
For internal use 11 © Nokia Siemens Networks. All rights reserved.
ADA: Cell Sets
Cell Sets Cell Sets can be defined with external files, with operations, or using polygons
Operations
Cell Sets graphical representation
For internal use 12 © Nokia Siemens Networks. All rights reserved.
ADA: Neighbours Lists
Neighbours List Operations and Formulas
For internal use 13 © Nokia Siemens Networks. All rights reserved.
Neighbours List graphical representation
ADA: Neighbours List checks
Maximum Count and SIB#11 checks Missing Cells, Missing Site, Co-Location checks Neighbour List analysis with SIB#11 and Distance details
For internal use 14 © Nokia Siemens Networks. All rights reserved.
ADA: Navigation, editing and exports…
Controls to easily customize map: zoom, pan, grid, ruler, scanmap and vectors
Navigation panel to easily find critical relations
Neighbour List editing functions and exports For internal use 15 © Nokia Siemens Networks. All rights reserved.
ADA: Web maps and Google Earth Exports
For internal use 16 © Nokia Siemens Networks. All rights reserved.
LTE PCI/RSI Planning using the MUSA “ADA” module
For internal use 17 © Nokia Siemens Networks. All rights reserved.
Physical Cell Identity Planning The PCI (Physical Cell Identity) is an essential configuration parameter of a radio cell.
•it corresponds to a unique combination of one orthogonal sequence and one pseudorandom sequence; •504 unique PCI are supported. These identities are 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, representing the identity within the group. It defines the Primary Synchronisation Signal (PSS) sequence.
PCI = Gid * 3 + g
For internal use 18 © Nokia Siemens Networks. All rights reserved.
Physical Cell Identity Planning When a new e-NB is brought into the field, a PCI needs to be selected for each of its supported cells, 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).
For internal use 19 © Nokia Siemens Networks. All rights reserved.
Physical Cell Identity Planning NSN 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.
For internal use 20 © Nokia Siemens Networks. All rights reserved.
LTE 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. Currently this feature has been used on many other cases. It has been placed in the ADA module of MUSA, since it requires as input a neighbor list. 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 next 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, but taking into account also if the area is close to the site or far. Of course a neighbors list generated in a different way (e.g. from other planning tool) can also be used For internal use 21 © Nokia Siemens Networks. All rights reserved.
LTE PCI allocation overview Overlapping Coverage Triangles for neighbors list generation Global parameters can be provided with possibility to classify sites in two categories: “urban” and “rural”, depending on the number of other sites falling in a given circle (‘urban distance threshold’)
B
urban
A
A B
rural
C
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.
A For internal use 22 © Nokia Siemens Networks. All rights reserved.
B
C
LTE 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”), it the site as 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 Parity Type 0, 6, 12, 18… Even-0 1, 7, 13, 19… Even-1 2, 8, 14, 20… Even-2 3, 9, 15, 21… Odd-0 4, 10, 16, 22… Odd-1 5, 11 17, 23… Odd-2
Even-0
Even-1
Even-2
Odd-0
Odd-1
Even-0 Even-1
0.2
Even-2 Odd-0 Odd-1 Odd-2
For internal use 23 © Nokia Siemens Networks. All rights reserved.
Odd-2
PCI 16
PCI 7
LTE PCI allocation overview In the picture below other parameter that can be set in the ADA module:
A certain number of PCI group can be reserved for the future expansion, using group or interval of groups separated by commas, as in this 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) - Monosectorial site should be modelled with one sector, angle = 360°, and more than 3 triangles (e.g. 12)
For internal use 24 © Nokia Siemens Networks. All rights reserved.
LTE RSI allocation overview • The algorithm followed for RSI (RACH rootSeqIndex of the LNCEL object) planning is easier, but it uses again the dummy 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: as for the PCI case, also for the 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. For internal use 25 © Nokia Siemens Networks. All rights reserved.
ADA: available LTE planning functions 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 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) PCI plan verification: Collision = two neighbouring cells with the same PCI Confusion: one cell with at least two neighboring cells having the same PCI Mod3, Mod6: can not be avoided at all but should be minimized Mod30, checked using the Sequence Group Number “u”
For internal use 26 © Nokia Siemens Networks. All rights reserved.
ADA: LTE PCI and RSI allocation (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
For internal use 27 © Nokia Siemens Networks. All rights reserved.
ADA: LTE PCI and RSI allocation (step by step 2/4) Neighbours calculation for Cluster 1, using a “coverage triangles” overlapping method.
1
3
4
2
5
For internal use 28 © Nokia Siemens Networks. All rights reserved.
ADA: LTE PCI and RSI allocation (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
2
3
4
For internal use 29 © Nokia Siemens Networks. All rights reserved.
ADA: LTE PCI and RSI allocation (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.
For internal use 30 © Nokia Siemens Networks. All rights reserved.
ADA: PCI Plan Assessment
5 3
1 2
4
6
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 For internal use 31 © Nokia Siemens Networks. All rights reserved.
Planned Parameters: PCI/RSI/grpAssigPUSCH Indicators for the plan verification: Mod3/Mod6/Mod30(u)
Mod30 violations: Mitigating UL DM RS issues with grpAssigPUSCH
Planning can be done iteratively, giving a “prevent list” grpAssigPUSCH can be planned at LNBTS lever or at LNCEL level.
• In case of Mod30 violations, it is possible to mitigate UL DM RS issues, planning the grpAssigPUSCH parameter, in order to have no violation on the Group Sequence Number “u”
u = (PCI + grpAssigPUSCH )mod 30
grpAssigPUSCH: group assignment for PUSCH Range [0…29], step 1
• It can be planned equals for all cells belonging to the same site (LNBTS strategy) or with a different value for each cells (LNCEL strategy). • The process can be iterated giving in input a priority list, where ADA will try to avoid as much as possible Mod30 violations For internal use 32 © Nokia Siemens Networks. All rights reserved.
MUSA Tool License and Support
For internal use 33 © Nokia Siemens Networks. All rights reserved.
MUSA License Tool availability and licensing
MUSA is a standalone application that can be used in all NPO projects for free (except “pixelling” phase that is based on a different license and must be purchased separately or used in a remote way with a PIXEL Server located in Milan offices). To run the tool users need hardware dongles with an expiration date. Licenses must be requested to:
[email protected] SW downloads, installation procedures, and other documentation, can be found on IMS at: https://sharenetims.inside.nokiasiemensnetworks.com/Open/414 119537
For more information and support please contact:
[email protected] For internal use 34 © Nokia Siemens Networks. All rights reserved.
MUSA HW Key
Free for NPO
PIXEL HW Key
Approx 3-4 kEuro Or Free if remote PIXEL Server used
Thank you
For internal use 35 © Nokia Siemens Networks. All rights reserved.
