RF Network Planning and Optimization Service V100R006 LTE ASP Coverage and Capacity Site Planning Technical Guide (FDD)

Product Name Security Level
ASP INTERNAL
Product Version Total 170 pages
RF V100R006
RF Network Planning and

Optimization V100R006 - Technical
Guide to Coverage- and Capacity-
based LTE ASP (FDD)
(For internal use only)
Prepared By Hu Wei (employee ID: 00135858), Zhang Date

2015-06-27
Meijia (employee ID: 00294280)
Reviewed By Xu Xiaoze (employee ID: 00286248), Mao Date
Liming (employee ID: 00231725), Li Xiao
(employee ID: 00148426)
Reviewed By Date
Granted by Date
Huawei Technologies Co., Ltd.
All Rights Reserved
RF Network Planning and Optimization V100R006 - Technical Guide to
Coverage- and Capacity-based LTE ASP (FDD) INTERNAL
Change History
Data Issue Description Author
2014-04-10 1.0 Revised this document based on NP and the Zhu Chongming (employee ID:
comments on delivered projects. 00165470), Liu Xiaoxian
(employee ID: 00210108)
2014-06-20 1.1 Revised this document to include U-Net Li Jiaxiang (employee ID:
V300R009C01. 00280266)
2014-12-07 1.2 Added the settings and result descriptions about Li Xiaoming (employee ID:
adding LTE sites to expand capacity, and updated 00265025)
U-Net UI screenshots.
2015-01-15 1.3 Updated the descriptions and UI screenshots Li Xiaoming (employee ID:
about traffic statistics analysis, the data imported 00265025)
for coverage geographic observation, and the U-
Net plug-in version.
2015-04-25 1.4 Updated the U-Net UI screenshots based on U- Zhang Meijia (employee ID:
Net V300R010C00. 00294280)
2015-06-27 1.5 Added the principles for capacity ASP and the Hu Wei (employee ID:
delivery procedure, and modified the original 00135858)
contents this document based on the added
information.
2017-03-21 Huawei confidential. No spreading without permission. Page 3 of 170

1 Contents
1 Overview...................................................................................... 7
1.1 Background.....................................................................................................................................................................7
1.2 Delivery Tools................................................................................................................................................................7
1.2.1 U-Net Plug-in Specifications.......................................................................................................................................8
1.2.2 U-Net Specifications...................................................................................................................................................8
1.3 Model Answers for Specifications................................................................................................................................10
1.4 Data Collection Methods..............................................................................................................................................11
1.5 Principles......................................................................................................................................................................11
1.5.1 Design Roadmap........................................................................................................................................................11
1.5.2 Factors Affecting LTE ASP Accuracy.......................................................................................................................11
1.5.3 Planning of Mandatory Sites.....................................................................................................................................12
1.5.4 Site Selection Process................................................................................................................................................14
1.5.5 Coverage-based Site Planning...................................................................................................................................16
1.5.6 Capacity-based Site Planning....................................................................................................................................22
1.5.7 UMTS MR/DT-based LTE Coverage Prediction (Applicable to LTE Site Planning based on Existing UMTS
Networks)...........................................................................................................................................................................27
1.5.8 6D Principles.............................................................................................................................................................27
1.6 Principles for Distinguishing Between Indoor and Outdoor Sites...............................................................................29
2 Delivery Guidelines.....................................................................30
2.1 Introduction to LTE ASP Application...........................................................................................................................30
2.1.1 Overview...................................................................................................................................................................30
2.1.2 Scenarios....................................................................................................................................................................30
2.1.3 Methods.....................................................................................................................................................................31
2.2 Overall LTE ASP Process.............................................................................................................................................32
2.3 Data Collection.............................................................................................................................................................33
2.3.1 Data Sources..............................................................................................................................................................33
2.3.2 Network Engineering Parameters..............................................................................................................................34
2.3.3 (Optional) Antenna Files...........................................................................................................................................36
2.3.4 (Optional) Electronic Maps.......................................................................................................................................36
2.3.5 (Optional) Propagation Models.................................................................................................................................36
2.3.6 (Optional) 6D Data....................................................................................................................................................36
2.4 Data Preprocessing Through the U-Net Plug-in...........................................................................................................38
2.4.1 Collecting Data..........................................................................................................................................................38
2.4.2 Creating Tasks...........................................................................................................................................................40
2.4.3 Selecting Features......................................................................................................................................................41
2.5 Site Planning Through the U-Net.................................................................................................................................62
2.5.1 Creating a Project......................................................................................................................................................62
2.5.2 Saving a Project.........................................................................................................................................................64
2.5.3 (Optional) Importing a Map......................................................................................................................................65
2.5.4 (Optional) Setting a Propagation Model....................................................................................................................67
2.5.5 (Optional) Importing and Setting Antenna Information............................................................................................71
2.5.6 Setting Frequencies...................................................................................................................................................71
2.5.7 Importing Engineering Parameters............................................................................................................................73
2.5.8 Setting the Template for New Sites...........................................................................................................................75
2.5.9 Setting an Analysis Area............................................................................................................................................77
2.5.10 Importing MRs........................................................................................................................................................78
2.5.11 Preparing Grid-based Traffic Maps.........................................................................................................................86
2.5.12 Importing and Planning ASP Data...........................................................................................................................94
2.5.13 Analyzing Site Planning Results...........................................................................................................................109
2.5.14 (Optional) Modifying Site Planning Results.........................................................................................................117
2.5.15 (Optional) Performing Simulation After Site Planning Result Modification........................................................120
3 FDD-LTE Indoor Intensive Coverage Site Planning........................124

3.1 Indoor Planning Principles and Functions..................................................................................................................124
3.1.1 Indoor and Outdoor Traffic Differentiation.............................................................................................................124
3.1.2 Application Scenario and Market Value..................................................................................................................125
3.1.3 Feature Value...........................................................................................................................................................126
3.1.4 Training Algorithm..................................................................................................................................................126
3.1.5 Comprehensive Multi-dimensional Determination.................................................................................................126
3.1.6 Algorithm Process...................................................................................................................................................127
3.2 FDD-LTE Indoor Intensive Coverage Site Addition..................................................................................................127
3.3 Indoor Intensive Coverage Site Planning Process......................................................................................................129
3.3.1 Indoor and Outdoor Traffic Differentiation Process................................................................................................129
3.3.2 FDD-LTE Indoor Intensive Coverage Site Planning Process.................................................................................130
4 U-Net Configuration Parameters.................................................137

4.1 Site Planning Parameters............................................................................................................................................137
4.1.1 Parameters on the General Tab Page.......................................................................................................................137
4.1.2 Parameters on the Objective Tab Page....................................................................................................................141
4.1.3 Parameters on the Strategy Tab Page......................................................................................................................142
4.1.4 Parameters on the Advanced Tab Page....................................................................................................................143
4.2 Parameters for Site Planning Results.........................................................................................................................144
4.2.1 Parameters on the Statistic Tab Page.......................................................................................................................144
4.2.2 Parameters on the Site Tab Page..............................................................................................................................146
4.2.3 Parameters on the Transceiver Tab Page.................................................................................................................148
4.2.4 Parameters on the Traffic Absorption Tab Page......................................................................................................150
4.2.5 Parameters on the Changes Tab Page......................................................................................................................151
4.2.6 Parameters on the Clutter Tab Page.........................................................................................................................153
4.3 Parameters for Layers.................................................................................................................................................153
4.3.1 Quality Analysis......................................................................................................................................................153
4.3.2 Coverage Analysis...................................................................................................................................................154
4.3.3 Weight Analysis.......................................................................................................................................................154
4.4 Parameters for Data Preprocessing Result (U-Net Plug-in).......................................................................................154
4.4.1 Coverage Analysis...................................................................................................................................................154
4.4.2 Capacity Analysis....................................................................................................................................................156
5 Delivery Procedures..................................................................157
5.1 Analyzing Operators' Requirements and Guiding Operators.....................................................................................157
5.2 Starting MR Data Collection Tasks and Performing MR Data Collection.................................................................157
5.3 Preparing Data as Required........................................................................................................................................158
5.4 Holding a Project Kick-Off Meeting and Developing a Delivery Plan to Identify Potential Delivery Risks............158
5.5 Generating Coverage and Capacity Planning Results................................................................................................158
5.6 Checking and Rectifying Planning Result Manually.................................................................................................159
5.7 Reviewing the Planning Result with Regional Departments and HO and Communicating with Operators to Acquire
the Acknowledgement of Operators.................................................................................................................................159
5.8 Developing a Site Survey Plan and Executing the Plan, and Modifying the Planning Result Based on the Site Survey
Result................................................................................................................................................................................159
5.9 Developing the Delivery Plan and Acceptance Solution with Operators After the Final Planning Result and Site
Survey Report Are Approved by Operators......................................................................................................................159
5.10 Coverage and Capacity Optimization Methods........................................................................................................160
6 FAQ..........................................................................................161
6.1 How Do I Perform Parameter Settings in the Engineering Parameter List or Cell List in Batches?.........................161
6.2 How Do I Cope with the Calculation Failure When Multiple Frequency Files on an RNC Are Selected for
Geographic Display with a Message Indicating that the Coverage Is Too Large?...........................................................161
6.3 How Do I Cope with the Calculation Failure When an RNC Area Is Selected for LTE ASP with a Message
Indicating that the Coverage Range Is Too Large?..........................................................................................................162
6.4 How Do I Improve the Operation Efficiency of the U-Net by Deactivating Sites Outside the Polygon Area?.........163
7 Appendixes............................................................................... 166
7.1 UMTS MR Collection Guide (V1.4)..........................................................................................................................166
7.2 WINS V100R006C00 LTE FDD Inventory Solution Data Collection Guide............................................................166
7.3 U-Net V300R010C00SPC100 Release Notes............................................................................................................166
7.4 Difference between MR-Positioning-based Capacity Planning Scheme and Rate Planning Scheme.......................166
7.5 "White Line" on the Map...........................................................................................................................................167
7.5.1 Phenomenon............................................................................................................................................................167
7.5.2 Causes......................................................................................................................................................................167
7.5.3 Solution....................................................................................................................................................................168
7.5.4 Problem Recurrence................................................................................................................................................168
RF Network Planning and
Optimization V100R006 - Technical
Guide to Coverage- and Capacity-
based LTE ASP (FDD)
Keywords:
ASP
Abstract:
This document describes the principles and technical guidelines for coverage-based LTE ASP.
List of abbreviations
Abbreviations Full Spelling
A-GPS Assisted Global Positioning System

ASP accurate site planning
CHR call history record
DT drive test
ISD inter-site distance
IMSI international mobile subscriber identity
KPI key performance indicator
MR measurement report
OS operating system
PCHR performance call history record
RSCP received signal code power
RSRP reference signal received power
RSRQ reference signal received quality
UI user interface
1 Overview
This document describes the basic principles, application scenarios, key operations, and cases
of the LTE accurate site planning (ASP) solution, providing technical guidelines for sales
personnel.
1 Background
This document describes the network coverage requirements, principles, procedures, and
operation guidelines for selecting and adding sites based on coverage. This provides
guidelines for engineers to plan, select, and add LTE sites based on existing UMTS networks
to improve coverage or based on existing LTE networks to improve coverage and expand
capacity. Intended audience need to master radio basics, radio network planning knowledge,
propagation model principles, and antenna principles.
2 Delivery Tools
To plan sites using the LTE ASP solution, perform the following two steps:
1 Preprocess data using the U-Net plug-in, and provide network evaluation results and
measurement report (MR) location results.
2 Process the preprocessing results using the U-Net and provide final LTE network planning
results.
Tool Version Function Applying for Remarks

Licenses
U-Net plug- http://support.huawei. Network For any question, contact Yang

in com/carrier/navi#col capacity Xuping (employee ID: 00163847)
=software&path=PBI evaluation or submit trouble tickets to him.
1-7851894/PBI1- and MR
8132365/PBI1- preprocessin
8132371/PBI1- g
21395144/PBI1-
13953
U-Net http://support.huawei.c LTE site 1. If the operating system (OS) is
om/carrier/navi#col=s planning installed for the first time, non-
oftware&path=PBI1- exclude framework version is
7851894/PBI1- selected. Otherwise, the exclude
8132365/PBI1- framework version is selected.
8132371/PBI1- 2. The 32-bit OS uses the 32-bit U-
21395144/PBI1-13953 Net version and the 64-bit OS
uses the 64-bit U-Net version.
3. GENEX U-Net V300R010C00
is used.
----End
1 U-Net Plug-in Specifications

1 You are advised to run the U-Net plug-in on a common PC or laptop equipped with a
dual-core CPU and a memory of 2 GB or above. The size of source data including MR
logs cannot exceed 20 GB. This prevents memory overflow. In normal cases, the space
occupied by a decompressed MR package is three times that occupied by the original
compressed package.
2 There are no restrictions on the processing capability of high-performance servers. You
are advised to plan LTE sites on UMTS networks using high-performance servers if data
from multiple RNCs needs to be analyzed simultaneously.
3 The U-Net plug-in can process at most 10 GB UMTS MR data at a time. If the data size
exceeds 10 GB, processing results are uncontrollable. This restriction does not apply to
LTE MR data.
4 The size of MR data generated by 500 sites within 6 peak hours over three days reaches
60 GB. The U-Net plug-in takes 10 hours to analyze the data. You are advised to reserve
at least 1.5 times the storage space occupied by the MR data. The reserved storage space
is used for traffic statistics analysis.
5 The size of traffic statistics generated by 500 sites within three days reaches 2 GB. The
U-Net plug-in takes 10 hours to analyze the data. You are advised to reserve at least 30
times the storage space occupied by the traffic statistics. The reserved storage space is
used for traffic statistics analysis.
Precautions
You are advised to process data generated within one week using the U-Net plug-in. If you are
using a laptop, you are also advised to disable the sleeping mode, thereby preventing your
laptop from sleeping during data processing.
2 U-Net Specifications
The U-Net supports the coverage- and capacity-based planning of up to 1000 sites.
1 If MR or drive test (DT) data is not used for path loss matrix calibration, the U-Net can
support the planning of 1000 sites and 3000 cells in an area of up to 500 square
kilometers.
2 If MR or DT data is used for path loss matrix calibration, the U-Net can still support the
planning of up to 1000 sites in a dense urban area but the calculation time increases by
70%.
3 Larger area and area complexity indicate longer calculation time, larger memory size,
and more disk storage space.
4 A longer cell radius indicates longer calculation time and more disk storage space.
5 Higher propagation model precision indicates longer calculation time and more disk
storage space.
6 A larger number of active sites and cells indicates longer calculation time, larger memory
size, and more disk storage space.
7 A larger number of MRs indicates longer calculation time and more disk storage space.
Scenario Specifications
1 In an urban area where the average inter-site distance (ISD) ranges from 300 m to 2000
m, the maximum coverage scope reaches 500 square kilometers, the maximum
calculation precision reaches 50 m, the maximum cell radius for propagation model
calculation reaches 4000 m, and up to 2000 active sites (6000 active cells) can be
deployed. The size of MR data imported into the U-Net cannot exceed 500 MB if MR
data is available.
8 In a suburban area where the average ISD ranges from 2000 to 10,000 m, the maximum
coverage scope reaches 6000 square kilometers, the maximum calculation precision
reaches 50 m, the maximum cell radius for propagation model calculation reaches 20,000
m, and up to 300 active sites (1000 active cells) can be deployed. The size of MR data
imported into the U-Net cannot exceed 500 MB if MR data is available.
In the preceding scenarios, the LTE ASP solution works properly. The LTE ASP solution may
fail if the actual scenario exceeds the specifications for the preceding scenarios.
Performance Reference
1 Urban areas
In another Tianjin urban area, the coverage scope is 54 square kilometers, the calculation
precision is 20 m, the cell radius for propagation model calculation is 4000 m, 1004 sites
(3012 cells) need to be deployed, and no MR data is available. Using the LTE ASP
solution to select sites and deploy macro sites takes 2 hours.
In another Tianjin urban area, the coverage scope is 677 square kilometers, the
calculation precision is 50 m, the cell radius for propagation model calculation is 4000
m, 1153 sites (3459 cells) need to be deployed, and no MR data is available. Using the
LTE ASP solution to select sites and deploy macro sites takes 2 hours.
9 Suburban areas
In a Nigerian suburban area, the coverage scope is 4000 square kilometers, the
calculation precision is 50 m, the cell radius for propagation model calculation is 12,000
m, 193 sites (592 cells) need to be deployed, and no MR data is available. Using the LTE
ASP solution to select sites and deploy macro sites takes 1 hour.
Precautions
1 The planned coverage scope cannot exceed specified specifications.
According to earlier projects delivered by using the U-Net, the U-Net fails to run if the
calculation area is exceedingly large. You must determine the coverage scope properly
during ASP. In normal cases, one RNC is regarded as a processing unit. If ASP fails due
to memory insufficiency, you are advised to re-plan the calculation area by splitting it
into multiple smaller areas (polygons).
10 The U-Net is incompatible with the OS.
The U-Net is developed based on the Windows OS that complies with US standards. In
countries such as Russia and Italy, tasks may fail to be created, or projects may fail to be
created after task creation, due to OS incompatibility.
If OS incompatibility occurs, do as follows to set Format to English (United States),
and then reinstall the U-Net.
11 Projects must be saved manually in real time.

The U-Net does not automatically save projects. You must manually save projects in real
time. Otherwise, you need to start ASP from all over again if your PC or laptop restarts
or the U-Net breaks down.
3 Model Answers for Specifications

The model answers for the U-Net specifications are as follows:
Recommended maximum size of MR data: 100 GB
Maximum size of traffic statistics: 2 GB
Maximum running time: 8 hours
Data collection period: 3*8 peak hours for both traffic statistics and MR data
The model answers for the U-Net planning specifications are as follows:
Maximum number of sites/cells: 2500 cells
Maximum calculation area: 100 square kilometers
Calculation precision: 50 m
Maximum running time: 3 hours on an x230 laptop
4 Data Collection Methods
You need to collect different data, such as traffic statistics, MRs, configuration files, and
engineering parameter tables based on scenarios. For details about how to collect data, see
WINS V100R007C00SPC300T Inventory Solution Data Collection Guide and WINS
V100R007C00SPC300T Inventory Solution U2000 One-Click Data Collection Guide.
WINS
V100R007C00SPC300T Inventory Solution Data Collection Guide.xlsx
WINS
V100R007C00SPC300T Inventory Solution U2000 One-Click Data Collection Guide.xlsx
5 Principles
1 Design Roadmap
1 shows the design roadmap of LTE ASP.
1 Design roadmap of LTE ASP
2 Factors Affecting LTE ASP Accuracy

The factors affecting LTE ASP accuracy are as follows:
Simulation accuracy, depending mainly on propagation model accuracy and also on other
factors such as antenna files, electronic maps, and site types
MR positioning precision
UMTS positioning precision
1) If the Assisted Global Positioning System (A-GPS) is enabled to report all MRs,
the positioning precision reaches 30 to 50 m.
2) If the A-GPS is enabled only to report some MRs, you can create A-GPS feature
databases, based on which the positioning precision can reach 90 m.
3) If the A-GPS is disabled and fast positioning is used, the positioning precision
reaches 180 to 300 m.
Currently most sites do not report all MRs through the A-GPS.
LTE positioning precision
If eNodeBs do not report MRs through the A-GPS and fast positioning is used, the
positioning precision reaches 100 to 150 m.
Precision of indoor-and-outdoor site differentiation
The precision of indoor-and-outdoor site differentiation reaches up to 83%.
3 Planning of Mandatory Sites

Reserve and directly activate mandatory sites. Then, perform cell simulation to update cell
coverage and capacity information.
1 Planning of mandatory sites
This process is internally implemented by the U-Net, and is invisible on user interfaces (UIs).
Mandatory sites are sites required by telecom operators due to certain reasons. Such sites
include some existing sites (for example, sites on two combined networks) and the sites that
will be deployed. Candidate sites are sites open to selection. Such sites are prioritized based
on their coverage and capacity values.
Mandatory and candidate sites involve latitudes, longitudes, and RF engineering
parameters.
Mandatory and candidate sites involve only latitudes and longitudes excluding RF
engineering parameters.
4 Site Selection Process

You do not need to manually determine whether to add or remove sites among a list of
candidate sites. The U-Net can select candidate sites based on their values. (This applies only
to coverage-based LTE site planning based on existing UMTS networks and to coverage- and
capacity-based LTE site planning based on existing LTE networks.)
The basic idea of the site selection algorithm is as follows:
The U-Net predicts the values (including the coverage scope and traffic absorption capability)
of each candidate site, sorts the candidate sites based on the predicted values, and selects the
site of the highest values as the one to be added. The U-Net repeats the preceding actions until
no site can be added or all detected coverage and capacity problems have been resolved.
1 Site selection process
LTE sites planned based on existing UMTS networks are used to absorb UMTS traffic.
LTE sites planned based on existing LTE networks are used to absorb LTE traffic.
The U-Net uses its coverage prediction function to obtain the values of each candidate site,
sorts the candidate sites based on the obtained values, and selects the candidate site of the
highest values as the one to be added. The U-Net repeats the preceding actions until no site
can be added or the selected calculation area has met specified coverage requirements.
Values of a candidate site in coverage-based site planning
Coverage value: indicates the number of weak coverage grids that can be covered by
the candidate site.
Capacity value: indicates the total volume of traffic that can be absorbed by the
candidate site from weak coverage grids.
The coverage fulfillment rate is calculated by using the following formula:
Coverage fulfillment rate = Number of traffic-detected grids whose level meets
specified requirements in the calculation area/Number of all traffic-detected grids in
the calculation area
Implemented after coverage-based site selection, capacity-based site selection aims to
analyze whether existing sites can meet the actual traffic requirements with a specific
coverage fulfillment rate ensured. The U-Net identifies overloaded cells through site
capacity evaluation. Then, the U-Net plans sites for maximally solving the problems in
overloaded cells, thereby reducing network key performance indicator (KPI)
deterioration caused by cell congestion.
Values of a candidate site in capacity-based site planning
A larger volume of traffic absorbed from overloaded cells indicates higher values.
A larger total volume of absorbed traffic indicates higher values if the volume of
traffic absorbed from overloaded cells remains unchanged.
5 Coverage-based Site Planning

The U-Net uses the weak coverage grid identification algorithm to identify the areas where
sites can be added to improve coverage. Then, the U-Net provides ASP results and RF
engineering parameter planning results.
1 shows the process of coverage-based site planning.
1 Process of coverage-based site planning
The process is as follows:

1 Identify weak coverage grids.
The U-Net identifies weak coverage grids on the live network based on data, such as MR
preprocessing results, complaint information, DT data, and coverage prediction results
obtained simulation. One grid is regarded as a calculation unit. A grid is identified as a
weak coverage one if its level is lower than the preset RSRP threshold (dBm) on the UI.
(RSRP is short for reference signal received power.) The level of a grid is calculated
through the following formula:
RSRP of a grid = Sum of the weighted levels of all cells in the grid/Total number of MRs
collected from all cells in the grid
2 Converge weak coverage grids.
The U-Net converges identified weak coverage grids into independent areas, facilitating
the subsequent identification of areas where sites can be added.
3 Prioritize independent areas.
The U-Net calculates the total volume of traffic in the weak coverage grids of each
independent area, and prioritizes all independent areas by traffic volume. Sites are
preferentially added to the area of the highest priority.
4 Select sites based on coverage
The U-Net compares the independent areas and the macro sites on the live network to
identify the areas where sites can be added. Then, the U-Net determines the areas for site
addition, plans sites in the areas where macro sites need to be added, and plans RF
parameters.
Adding macro sites to resolve weak coverage
The weak coverage center is the weighted average of the coordinates for all weak
coverage grids in the weak coverage area. The weight is the percentage of the volume of
traffic absorbed in weak coverage grids in the total volume of traffic absorbed in the
weak coverage area.
TrafficBin
xX
Traffic Bin
()
X Center =
TrafficBin
Y Center = ( xY)
Traffic Bin
Traffic Bin : indicates the traffic volume of a weak coverage grid.
Traffic Bin : indicates the sum of the traffic volumes of all weak-coverage grids in
an area.
X: indicates the horizontal coordinate of a weak coverage grid.
Y: indicates the vertical coordinate of a weak coverage grid.
TrafficBin
xX
Traffic Bin : indicates the sum of all weak coverage grids in the area.
()

The U-Net determines whether the weak coverage center is suitable for macro eNodeBs.
If the weak coverage center is not suitable for macro eNodeBs, the U-Net searches for
other sites suitable for macro eNodeBs around the weak coverage center based on
geometrical relationships.
The weak coverage center is suitable for macro eNodeBs only when it meets the
following conditions:
Terrain conditions for macro eNodeBs (You can specify the clutter types unsuitable
for macro eNodeBs, as shown in the following figure.)
Small area unsuitable for micro eNodeBs
Macro eNodeB ISD requirements
The U-Net performs the following steps to search for sites suitable for macro eNodeBs in
an area based on geometrical relationships. It stops once suitable sites are found. If no
suitable sites are found after all steps are complete, site addition in this area fails in the
current round of convergence. The U-Net will consider adding sites in this area in the
next round of convergence. If this is the last round of convergence, site addition in this
area fails for the whole task.
2 Find the nearest site of the weak coverage center. Then, check whether any site, whose
distance from the nearest site is equal to the preset macro eNodeB ISD (ISD_Macro), along
the extension line connecting the nearest site and the weak coverage center is suitable for
macro eNodeBs.
3 Find the nearest two macro sites. Then, search for any site located on the center line between
the two sites, in the same direction, and macro eNodeB ISD away from both sites, is suitable
for macro eNodeBs.
4 Find the nearest three macro sites. Then, check whether the circumcenter of the three sites is
suitable for macro eNodeBs.
Adding micro sites to resolve weak coverage
U-Net V300R010C00 supports the simulation of micro sites. It provides an internal
switch for you select micro eNodeB fan-shaped coverage or micro eNodeB simulation
coverage.
Condition for adding micro sites
No sites are deployed within 75 m around weak coverage grids. The distance
threshold can be set through the Minimum ISD of micro site(m) parameter on U-
Net UIs.
Micro site selection
The U-Net traverses all grids in an area where micro eNodeBs are densely deployed
to search for the grid that can absorb the most traffic from weak coverage grids. The
grid is then used as a micro site.
Model for micro eNodeB fan-shaped coverage
The sector radius R and angle are set on U-Net UIs. The R value is adaptively
adjusted according to different levels within the coverage scope. The coverage scopes
under typical levels are configured in the U-Net. The U-Net uses linear relationships
to match medium levels with the coverage scopes.
1 Plan RF parameters.
For macro eNodeBs
Azimuth
The U-Net calculates the azimuth of each sector within the 360-degree scope of each
new macro eNodeB based on the weak coverage center. Three standard sectors are
configured for each macro eNodeB. U-Net V300R10C00 can adaptively determine
the traffic of each sector, and does not activate the sectors from which no traffic is
transmitted. This function is controlled by internal advanced parameters, and is
disabled by default. In addition, the three-sector configuration is still used for each
new macro eNodeB in U-Net V300R10C00.
Height
The height of a new macro eNodeB is equal to the average height of three macro
eNodeBs located nearest to the new macro eNodeB, and must not exceed the
maximum antenna height, which can be set in the Scenario Definition dialog box of
the U-Net and is set to 50 m by default.
Downtilt
The U-Net calculates the downtilt based on the height and coverage. The downtilt
must not exceed the maximum antenna downtilt, which can be set the Scenario
Definition dialog box of the U-Net and is set to 0 by default.
For micro eNodeBs
Micro eNodeBs are deployed to cover weak coverage grids that cannot be covered by
macro eNodeBs. For a micro eNodeB, only a site needs to be planned, whereas RF
parameters do not.
Height, which can be set in the template for adding micro sites
Azimuth, which points to the traffic center from the micro site
2 Plan the capacity of new sites, and update traffic and weak coverage grid information.
3 Add micro sites.
The U-Net adds micro sites to cover weak coverage grid that cannot be covered by
macro sites.
1 For macro eNodeBs, the U-Net requires the advanced parameter Macro site poor
coverage grid number threshold to be properly set. This parameter is set to 5 by
default. If the number of weak coverage grids covered by a planned macro site reaches
the value of this parameter, the U-Net can successfully add the macro site. Otherwise, the
U-Net fails to add the macro site, and proceeds with site planning analysis and iteration
in other areas.
For micro eNodeBs, the U-Net requires the advanced parameter Micro site poor
coverage grid number threshold to be properly set. This parameter is set to 2 by
default. If the number of weak coverage grids covered by a planned micro site reaches
the value of this parameter, the U-Net can successfully add the micro site. Otherwise, the
U-Net fails to add the micro site.
6 Capacity-based Site Planning

The U-Net identifies the areas where sites can be added to expand capacity based on traffic
statistics and MR analysis results. Then, the U-Net provides ASP results and RF engineering
parameter planning results. Capacity-based site planning applies only when you plan LTE
sites based on existing LTE networks.
1 Basic Concepts
1 Capacity-based site selection
Implemented after coverage-based site selection, capacity-based site selection aims to
analyze whether existing sites can meet the actual traffic requirements with a specific
coverage fulfillment rate ensured. The U-Net identifies overloaded cells through site
capacity evaluation. Then, the U-Net plans sites for maximally solving the problems in
overloaded cells, thereby reducing network KPI deterioration caused by cell congestion.
2 Capacity-based site addition
The U-Net identifies the areas where sites can be added to expand capacity based on
traffic statistics and MR analysis results. Then, the U-Net provides ASP results and RF
engineering parameter planning results.
3 Traffic absorption
Both site selection and site addition cause the conditions of the network within the
coverage scope of new sites to change. If the traffic distribution remains unchanged, the
absorption of the same volume of traffic must be reallocated among the areas involved in
network changes.
4 Prioritization of new sites
The U-Net provides the priorities of new sites for telecom operators to evaluate site
values.
2 Capacity-based Site Planning Process
1 Process of capacity-based site planning

1 Predict the target network.
The U-Net considers the requirements on resources such as air interface resources and
the number of equivalent UEs. Then, the U-Net uses proper algorithms to predict the
capacity resources required by each sector on the target network.
In capacity-based site planning, capacity resource requirements are measured by total
bandwidth (TotalBW). For example, a bandwidth of 20 MHz is configured for each LTE
carrier in normal cases. This means that a total bandwidth of 50 MHz is required by all
grids in a sector. To meet the capacity resource requirement, a bandwidth of 30 MHz
needs to be added. The following describes how to allocate the 30 MHz bandwidth. The
LTE ASP solution analyzes capacity resources from the bandwidth dimension, and then
allocates the capacity resources of overloaded sectors through splitting, carrier addition,
and site addition to optimize network capacity.
2 Sort overloaded cells.
The U-Net sorts overloaded cells by traffic volume in descending order.
The following formula is used to calculate the extra required carrier bandwidth (Extra
Add CarrierBandwidth) of a sector:
Extra Add CarrierBan dwidth = Grid Total CarrierBan dwidth Max CarrierBan dwidth per Sector
i
The sum is the total bandwidth provided by the carriers in all grids covered by the sector.
The U-Net sorts cells by extra required carrier bandwidth in descending order. The
sectors whose extra required carrier bandwidth is less than or equal to 0 do not have
capacity problems, and therefore are skipped.
3 Search for areas where sites need to be added for capacity expansion.
The U-Net searches for areas where cells are most overloaded and sites need to be added
for capacity expansion.
Identify areas for adding macro sites.
For each overloaded sector, the U-Net searches for adjacent sites and other adjacent
overloaded sectors, which form an overloaded area for site addition.
As shown in the following figure, the sites nearest to the overloaded sector, and the
other adjacent overloaded sectors that have overlapping traffic with the overloaded
sector, are selected to form an overloaded area.
The U-Net distributes traffic in each cell according to the cell's MRs. The traffic of a
cell in a grid is calculated by using the following formula:
Traffic volume of a cell in a grid = Total traffic volume of the cell/Total number of
MRs for the cell x Number of MRs for the cell in the grid
If the grid has both traffic from sectors A and B, sectors A and B have overlapping
traffic.
1 Convergence of capacity-overloaded areas
Identify areas for adding micro sites.

The area with traffic in each sector of an overloaded macro eNodeB on the live
network is regarded as an independent area for site addition.
4 Calculate the traffic center of each area where sites can be added to expand capacity.
The U-Net locates overloaded sectors, and then calculates the traffic center of the area
covered by each overloaded sector. In coverage-based site planning, only weak coverage
grids are involved in traffic center calculation. In capacity-based site planning, however,
all grids are involved in the calculation. For details about the calculation method, see
section 5"Coverage-based Site Planning."
5 Select sites for adding macro eNodeBs to expand capacity.
The U-Net selects sites based on the traffic center and network topology.
6 Plan RF engineering parameters for macro eNodeBs.
The RF engineering parameter planning for capacity-based site planning is similar to that
for micro site planning except the following:
The grid level specified by the RSRP threshold for micro site(dBm) parameter must
be less than 65 dBm. If the grid level of an area is greater than 65 dBm, micro
eNodeBs are affected significantly by macro eNodeBs at the area. As a result, the
area is unsuitable for site addition.
In coverage-based site planning, only weak coverage grids are involved in traffic
center calculation. In capacity-based site planning, however, all grids are involved in
the calculation.
7 Update capacity information based on simulation results.
Once a macro NodeB site is added, the U-Net analyzes load sharing among adjacent
overloaded cells through coverage simulation and prediction, and then updates the list of
cells for which sites are to be added.
8 Add micro sites.
The U-Net adds micro sites to resolve capacity problems that cannot be resolved by
macro sites.
9 Remove all new macro and micro sites that do not absorb traffic from any overloaded
sector.
7 UMTS MR/DT-based LTE Coverage Prediction
(Applicable to LTE Site Planning based on Existing
UMTS Networks)
Before you plan LTE sites on a live UMTS network, obtain LTE coverage based on data such
as MR or DT data collected from the UMTS network. Main factors affecting the level in a
grid include the pilot signal transmit power, antenna gains, downlink transmission loss, and
path loss.
Collect MR/DT data from the live UMTS

network.
Predict LTE coverage based on the MR/DT

data.
Plan LTE sites.
1 Calculate the path loss from a UMTS cell to each of its covered grid based on the
received signal code power (RSCP) information contained in UMTS pilot transmit
power, antenna gains, downlink transmission loss (such as line loss), and MR or DT data.
The calculated loss can be directly used as the path loss from an intra-frequency intra-
site co-coverage LTE cell of the UMTS cell to each of its covered grid.
2 Calculate the LTE cell RSRP based on LTE path loss, pilot transmit power, antenna
gains, and downlink transmission loss. (If the difference between UMTS and LTE
frequency bands is insignificant, you can specify a fixed compensation value to calculate
the path loss caused by the frequency band difference. The path loss conversion is
inaccurate if the frequency band difference is significant.)
Suggestions are as follows:
3 The pass loss conversion applies to the same frequency band.
4 If the difference between UMTS and LTE frequency bands (for example, 1800 MHz and
2100 MHz) is insignificant, you can manually specify a compensation value (according
to the different propagation loss caused by the frequency band difference). For details,
see section 25124"Setting Site Planning Parameters."
5 If the difference between frequency bands (for example, 900 HMz and 1800 MHz) is
significant, the pass loss conversion does not apply because it is inaccurate.
8 6D Principles
1 6D Evaluation
New sites suggested by LTE ASP must be evaluated not only in terms of coverage and
capacity but also from various dimensions, such as UE capabilities and valued services. The
evaluation results provide guidelines for telecom customers and delivery personnel to select
sites based on priorities. Sites of higher values are preferentially added according to the
project budget. Basic 6D evaluation dimensions include coverage, capacity, revenue, VIP
user, UE, and site cost. Customer-oriented 6D evaluation dimensions, such as 2G/4G high
traffic and high 4G fallback rate/redirection, introduced for indoor micro sites, can be used to
analyze the values of added sites.
1 Customer-oriented 6D evaluation dimensions
Latitude Revenue Terminal VIP User Complaint
Scenario
Collaborative site
addition
Default weight 0.1 0.1 0.1 0.1
indicates that the evaluation dimension is required and indicates that the evaluation
dimension is not required.
1 Coverage
Coverage is the sum of weak coverage grids that the new site can cover.
2 Traffic
More traffic absorbed by the new site within its primary coverage indicates a higher
priority.
3 Revenue
More revenue obtained through the new site within its primary coverage indicates a
higher priority.
4 UE capability
A larger number of UEs served by the new site within its primary coverage indicates a
higher priority.
5 Complaint against weak coverage
A larger number of complaints against weak coverage within the primary coverage of the
new sites indicates a higher the priority.
6 VIP user
A larger number of VIP users served by the new site within its primary coverage
indicates a higher priority.
2 6D Score
Total 6D score = (Weighted value of each dimension x Score of the dimension)
You can select all or some of the preceding six dimensions to calculate the 6D score.
The weighted value of each dimension is entered manually. The default weighted values of
the coverage and capacity dimensions are 1. The default weighted values of all the other
dimensions are 0.1. The score of each dimension is calculated by site. For example, traffic
absorbed by each site is collected as a sample and traffic absorbed by all sites is collected as a
sample set to calculate the score of the capacity dimension. The 6D normal distribution and
standard variance methods are used for the calculation. Standard variance indicates the
deviation of the value from the mean value.
1 Collect sample statistics.
The U-Net calculates the standard variance X, STDEVP (all samples), and the mean
value Y, AVERAGE (all samples). For details about the calculation formulas of
STDEVP and AVERGAE, see the help in EXCEL.
2 Calculates the unified sample score interval.
Minimum score interval: MIN = MAX {MIN (all samples), Y 1.96X)}
Maximum score interval: MAX = MIN {Y + 1.96X, MAX (all samples)}
The value of (Y 1.96X) corresponding to the 5% normal distribution and that of (Y +
1.96X) corresponding to the 95% normal distribution are used as the minimum and
maximum values of the score interval, respectively.
3 Generates the score N for each site from various dimensions.
N = {M MAX [(min (samples), Y 1.96X]}/{MIN [Y + 1.96X, MAX (samples)]
MAX [min (samples), Y 1.96X]} x 100
N indicates the score obtained based on sample data. Its value is calculated according the
[0, 100] score interval.
M indicates the entered sample data.
The highest score for a sample whose M value is greater than the value of MIN [Y +
1.96X, MAX (samples)] is 100.
The lowest score for a sample whose M value is less than the value of MAX [min
(samples), Y 1.96X] is 0.
6 Principles for Distinguishing Between Indoor

and Outdoor Sites
Indoor-and-outdoor site differentiation can be provided through a plug-in and presented on the
U-Net once being implemented according to specified principles. For details, see the
following sections describing operations.
2 Delivery Guidelines
1 Introduction to LTE ASP Application

1 Overview
1 For details about how to select and add sites based on existing LTE FDD networks, see
section 2"Scenarios."
2 You are advised to select and add sites preferentially in high-traffic areas, thereby
achieving higher values.
3 Mandatory sites are sites required by telecom operators due to certain reasons.
4 Site selection precedes site addition. (The U-Net can support only site selection, only site
addition, or both according to project requirements. If both site selection and site
addition are required, the U-Net firstly selects sites, and then adds sites based on site
selection results.)
5 Macro sites are planned before micro sites. (The U-Net can plan only macro sites, only
micro sites, or both according to project requirements. If both macro sites and micro sites
are required, the U-Net plans macro sites preferentially.)
6 In capacity-based site planning, the U-Net considers adding carriers preferentially. If
capacity cannot be expanded sufficiently by adding carriers, the U-Net then selects sites,
and adds macro sites, micro sites, or both based on project requirements.
2 Scenarios
LTE ASP provides scenario-specific policies, including coverage- and capacity-based site
selection and addition, to resolve weak coverage and capacity overload on existing LTE FDD
networks. Sites are selected and added preferentially in high-traffic areas. The typical process
of adding sites for capacity expansion is as follows:
1 Import mandatory sites for simulation and effect evaluation.
2 Import candidate sites, and then use the U-Net to select sites based on coverage and
capacity values.
3 Add macro sites based on coverage requirements.
4 Add micro sites based on coverage requirements.
5 Add carriers to resolve capacity problems.
6 Add macro sites to resolve capacity problems on the live network.
7 Add micro sites to resolve capacity problems on the live network.
8 Add micro sites to resolve coverage and capacity problems on the live network.
9 Add macro sites to resolve coverage and capacity problems on the live network.
The LTE ASP solution supports the following in HetNet:
Capacity-based micro eNodeB deployment.
Coverage-based micro eNodeB deployment. It is recommended that micro eNodeBs be
not deployed on a large scale to improve coverage. A micro eNodeB supports a coverage
radius ranging from 100 m to 150 m. Many micro eNodeBs will be required if only
micro eNodeBs are deployed to improve coverage.
3 Methods
1 For details about the basic principles for coverage-based site selection and addition, see
chapter 15"Principles."
2 The LTE FDD coverage level is calculated preferentially by using DT data (which is
optional), followed by MR data and then propagation model-based simulation results.
3 MRs collected from LTE FDD sites are used mainly for rasterization. After traffic data is
imported, the U-Net distributes traffic to rasterized grids based on the MR rasterization
percentage, providing reference for selecting and adding sites by priority weight.
4 For details about the MR positioning precision, see section 152"Factors Affecting LTE
ASP Accuracy."
2 Overall LTE ASP Process
1 Overall LTE ASP process

1 Prepare engineering parameters and obtain source data. For details about how to prepare
engineering parameters, see section 32"Network Engineering Parameters."
2 Obtain MR and traffic statistics files using the U-Net plug-in. For details, see section
4"Data Preprocessing Through the U-Net Plug-in."
3 Perform the following operations on the U-Net:
1) Import data by following the instructions provided in sections 54"(Optional) Setting
a Propagation Model," 510"Importing MRs," and 511"Preparing Grid-based Traffic
Maps."
2) Perform ASP by following the instructions provided in section 512"Importing and
Planning ASP Data."
For details about U-Net UIs, see section 5"Site Planning Through the U-Net."
1 Delivery timeline
Operation Workload (for 2000 LTE Sites)
Data collection 1 week

Data processing through the U-Net plug-in 2 days
Site planning through the U-Net 2 days
Verification and calibration of site planning results 1 to 2 weeks
Preparation of report materials 1 week
If the standalone U-Net is used, the delivery timeline is planned assuming that 2000 sites are added
in a dense urban area and raw data of three days needs to be processed.
Once the number of sites to be added reaches 2000, the time for the U-Net plug-in to process data
and that for the U-Net to plan sites both increase by one day, and the data collection time increases
by one week, with every 2000 more sites.
3 Data Collection
1 Data Sources
1 Data sources for LTE ASP
Scenari NE Type Data Data Format Required Function
o Type Time
Common Electronic Clutter

data maps identification
(Optional) Simulation
Antenna
files
(Optional) Simulation
Propagatio
n models
Network Positioning
engineering
parameters
LTE site RNC RNC Configuration

planning configurati data
based on on files
existing
UMTS MRs 2 days Grid-based
networks geographic
observation
(Optional) 2 days Event-based

SAU geographic
performanc observation
e call
history
records
(PCHRs)
Traffic 1 week Traffic

statistics measurement
(Optional) 6D evaluation
VIP data
Complaint
data
LTE site eNodeB eNodeB Encapsulated into ZIP packages together with traffic eNodeB
planning configurati statistics (collected through the NIC) configuration
based on on files data
existing
LTE MRs/Call 2 days Geographic
networks history observation
records
(CHRs)
Traffic 1 week Traffic

statistics measurement
VIP data
Complaint
data
For details about how to obtain the data collection guide, see section 14"Data Collection Methods."
2 Network Engineering Parameters

When you plan LTE sites based on existing UMTS networks, prepare the UMTS engineering
parameters used by the U-Net and U-Net plug-in by following the instructions provided in
section 41"Collecting Data."
When you plan LTE sites based on existing LTE networks, prepare the LTE engineering
parameters used by the U-Net and U-Net plug-in by following the instructions provided in
section 41"Collecting Data."
Attachment 3 -
LTE Engineering Parameter Template (U-Net) .xlsx
Precautions for engineering parameters are as follows:

The engineering parameters used for planning LTE sites based on existing UMTS
networks through the U-Net are included as the engineering parameters of candidate LTE
sites in the engineering parameter file. Involved source and target cells must be served by
the same site and have the same antenna height. In addition, the differences in azimuth
and downtilt between the source and target cells must not exceed 30 degrees and 5
degrees, respectively. Therefore, the antenna heights, azimuth, and downtilt angles in
UMTS engineering parameters must be included in the engineering parameters of
candidate LTE sites.
If the Active parameter is not set for each cell in the engineering parameter template, the
U-Net sets the cell status to Deactive by default. As a result, you need to manually
activate cells. Inactive cells cannot be included in any network planning task. You are
advised to set the Active parameter for each cell before importing engineering
parameters. (On UL dual-mode networks, the imported engineering parameters of LTE
candidates do not need to be activated. In addition, you do not need to consider the
impact of the sites outside the selected polygon on the sites inside the polygon. You can
deactivate the sites outside the polygon when setting a project.)
If frequency and bandwidth information cannot be found when engineering parameters
are imported into the U-Net, rectify the fault by following the instructions provided in
section 58"Setting the Template for New Sites."
The following table describes the LTE FDD engineering parameters imported into the U-
Net for LTE site planning based on existing UMTS networks.
LTE FDD engineering
parameters from the live The status of sites is set to active.
network
LTE engineering
parameters provided by
Mandatory sites must be locked if there are any. For details,
telecom operators and used
see section5124"Setting Site Planning Parameters."
for the planned sites to be
added
LTE FDD engineering
Fields including NodeBName, Transceiver Name, Cell
parameters converted from
Name, Longitude, Latitude, Azimuth, M.Tilt, and E.Tilt
UMTS engineering
can be inherited.
parameters
LTE FDD engineering
parameters converted from Fields including SiteName, CellName, Longitude,
GSM engineering Latitude, Azimuth, M.Tilt, and E.Tilt can be inherited.
parameters
In LTE site planning based on existing UMTS networks, LTE engineering parameters are
inherited from UMTS engineering parameters. The value of CellName + RNCID + CI
must be different from that of CellName + TAC + CI for each UMTS cell.
The Comments field can be used for other purposes. For example, it can be used to
identify each RNC if there are multiple RNCs. The Comments field is displayed by
RNC under Site or Transceiver on the U-Net.
3 (Optional) Antenna Files

The U-Net supports three types of 2D and 3D antenna files: .msi, .txt, and .iAntes. As an
industrially universal format, the .msi format is a text format in which files use msi as their
suffix. Each .msi file corresponds to one type of antenna. The .txt and .iAntes formats are
provided by the U-Net. The .txt format is a pure text format. Each .txt file also corresponds to
one type of antenna.
The U-Net provides some basic antenna file types. Frontline personnel must clarify antenna
types.
An antenna file example is as follows:
Attachment 4 -
Antenna File Example.rar
4 (Optional) Electronic Maps

The U-Net supports both layer-specific import and quick import of map data. Electronic maps
in standard Planet, GRC/GRD, BIL, and TAB formats can be used for site planning. Maps in
SHP and MIF formats can be imported for geographic observation.
The most commonly used map layers affecting simulation accuracy in the U-Net are the
Clutter layer, Height layer, and Buildings layer. If propagation models are used, the Vector
layer (a 3D Vector layer is preferred) is also mandatory in addition to the preceding three map
layers. The Vector layer is used only for presentation in other scenarios.
5 (Optional) Propagation Models

The U-Net supports various propagation models, such as Okumura-Hata, Cost-Hata, SPM (a
standard propagation model defined by the U-Net), ITU RP, Keenan-Montly, and Volcano.
(Before you use the Volcano model, install the Volcano plug-in and purchase the Volcano
license. The U-Net supports only Volcano 3.0.3.0.) During the planning and simulation, you
need to set propagation model parameters properly based on scenarios and areas. You also
need to set propagation model parameters for the selected planning area according to the
calibrated propagation model provided by frontline personnel. For details, see GENEX U-Net
User Guide, which can be obtained in section 73"U-Net V300R010C00SPC100 Release
Notes."
6 (Optional) 6D Data
The template is as follows:
Attachment 5 -
6D Template.xlsx
The source data for 6D evaluation is in EXCEL format and mainly includes four sheets shown
in the following figure.
The names of the sheets in the file imported into the U-Net plug-in cannot be changed. Data
fails to be read if the sheet names are changed.
1 ValuedServiceType (applicable to LTE site planning based on existing UMTS networks)
The following is an example of the valued service list. The list contains valued services
that depend on the DPI function. The DPI function requires both the SAU and NIU
boards. The U-Net supports all the services listed in the 6D valued service list. You only
need to remove unneeded valued services from the example list.
If the valued service list is empty, the U-Net regards all services identified by the NIU
board as valued services.
ValuedServiceType
VoIP
IM
File Access
Other
Streaming
Network Storage
Web Browsing
News Group
P2P
Game
Stock
Network Admin
Email
Database
Remote Connectivity
Tunnelling
2 ValuedTerminal (applicable to LTE site planning based on existing UMTS networks)

Enter the IMEI-TAC of each valued UE on this sheet. Otherwise, the U-Net regards each
iPhone, Samsung, or Huawei P6 mobile phone as a valued UE by default.
3 (Optional) VIPuser
This sheet contains the anonymized international mobile subscriber identities (IMSIs) of
all valued UEs.
If an IMSI contains more than 15 digits, EXCEL stores the IMSI as an index number. However, the U-
Net plug-in cannot parse index numbers. Such an IMSI must be stored as a character string. For details
about how to convert such an IMSI into a character string, see the following attachment:
VIPuser.xlsx
4 (Optional) Complaint
This sheet contains complaints against weak coverage. You need to sort the complaint
data provided by telecom operators according to the format shown in the following
attachment, and then import the data into the U-Net for site planning:
U-Net_User
Complaints.xlsx
5 (Optional) Site Cost

This sheet contains the site-level deployment costs of candidate sites. You need to enter
the costs of new sites after site surveys.
4 Data Preprocessing Through the U-Net Plug-

in
In LTE site planning based on existing UMTS networks, the U-Net plug-in is used to
process UMTS network data.
In LTE site planning based on existing LTE networks, the U-Net plug-in is used to
process LTE network data.
1 Collecting Data
1 LTE Site Planning based on Existing UMTS Networks
Collect the following data before you parse UMTS MRs:
Live-network UMTS engineering parameters corresponding to the MRs to be parsed
The engineering parameter template is as follows:
UMTS_MR Data
Parse_Engineering Parameter Template.xlsx
Live-network RNC MML configuration files corresponding to the MRs to be parsed

Such files can be in .zip (one-level compression) or .txt format.
MRs of a specified period that are collected based on scenarios
Such MRs support only one-level compression. This means that multiple data sources
cannot be compressed into one .mr.zip package.
(Optional) Live-network UMTS feature library files corresponding to the MRs to be
parsed
Such files in .xls, .xlsx, .csv, or .txt format can be imported.
Collect the following data before you parse UMTS 6D data:
Live-network UMTS engineering parameters corresponding to the 6D data to be parsed
UMTS_6D Data
Live-network RNC MML configuration files corresponding to the 6D data to be parsed
Such files can be in .zip (one-level compression) or .txt format.
MRs of a specified period that are collected based on scenarios
Such MRs support only one-level compression. This means that multiple data sources
cannot be compressed into one .mr.zip package.
Live-network RNC PCHR configuration files corresponding to the 6D data to be parsed
Such files can be in .log.zip format (one-level compression).
2 LTE Site Planning based on Existing LTE Networks

Collect the following data before you parse LTE FDD MRs:
1 Live-network LTE FDD engineering parameters corresponding to the MRs to be parsed
LTE FDD_MR Data

2 Live-network LTE FDD CHR configuration files corresponding to the MRs to be parsed
Such files are stored in a two-level directory. They cannot be compressed. Sub-folders
storing such files can be traversed.
Collect the following data before you parse LTE FDD traffic statistics:
Live-network LTE FDD engineering parameters corresponding to the traffic statistics to
be parsed
LTE FDD_Traffic
Data Parse_Engineering Parameter Template.xlsx
Live-network LTE FDD eNodeB configuration files corresponding to the traffic statistics
to be parsed
Such files are stored in a two-level directory and support the .xml format. They cannot
be compressed. Sub-folders storing such files can be traversed.
Live-network LTE FDD eNodeB MML configuration files corresponding to the traffic
statistics to be parsed
Such files are stored in a two-level directory and support the .txt format. They cannot be
compressed.
Live-network LTE FDD eNodeB traffic statistics files corresponding to the traffic
statistics to be parsed
No restrictions are raised on the levels of the directory for storing such files. The U-Net
plug-in preferentially processes compressed packages. Uncompressed traffic statistics
files stored in the directory cannot be parsed if there are any. Such files can be in .mrf.gz
or .csv format. Multiple traffic statistics files can be compressed into one .zip package.
To obtain typical traffic statistics, you are advised to collect data of M (M is greater than or equal to 3)
consecutive days. Data generated on a day is invalid and will not be processed if it covers less than 12
hours.
Collect the following data before you parse LTE FDD 6D data:
Live-network LTE FDD engineering parameters corresponding to the 6D data to be
parsed
LTE FDD_6D Data

Parse_UMTS Engineering Parameter Template.xlsx
Live-network RNC MML configuration files corresponding to the 6D data to be parsed

Such files are stored in a two-level directory and support the .zip (one-level
compression) and .txt formats. Sub-folders storing such files can be traversed.
UMTS MRs of a specified period that are collected based on scenarios
Such MRs are stored in a two-level directory. Sub-folders storing such MRs can be
traversed. MR files support only one-level compression in .zip or .mr format. Multiple
data sources cannot be compressed into one package.
Live-network RNC PCHR configuration files corresponding to the 6D data to be parsed
Such files support one-level compression in .log.zip or .log.gz format.
2 Creating Tasks
To create a task, start the U-Net plug-in. In the iDart Data Processor Plugin dialog box, click
in the upper left corner or choose File > New Task from the main menu.
3 Selecting Features
1 Parsing Coverage Data
1 Set basic task parameters.
Task Name: indicates the name of the new task. The task name cannot be duplicate with
the name of any existing task.
Output Path: indicates the save path of the parsed data.
Network Type: indicates the RAT of the data to be parsed. Set this parameter to UMTS.
Task Type: indicates the type of the data to be parsed. Set this parameter to
Measurement Report Analyze.
Position Type: indicates the MR positioning method. Three options are provided:
AGPS Positioning: MRs are directly parsed from raw data.
Fast Positioning: Positioning is fast but accuracy is compromised.
Feature Positioning: Positioning is slow but accuracy is high. This method is
recommended if feature library data is available.
Use AGPS Feature: specifies whether to use AGPS feature libraries. This parameter is
available only when Position Type is set to Feature Positioning.
Gird Size(m): indicates the grid precision for MR data. Set this parameter properly
based on scenarios.
2 After the basic task parameters are set, click Next to set the parameters related to UMTS MR
parsing.
Grid MR Filter Limit: indicates the threshold for filtering a grid's MRs. The value of
this parameter ranges from 0 to 99999. After MR rasterization is complete, all the MRs
of a grid are deleted if the total number of MRs for all cells in the grid is less than this
threshold.
Minimum RSCP Limit(dBm): indicates the minimum level-filtering threshold. The
value of this parameter ranges from 116 to 0. After MR rasterization is complete, all the
MRs of a cell in a grid are deleted if the average level of the cell in the grid is less than
this threshold.
Grid Cell MR Filter Limit: indicates the threshold for filtering a cell's MRs in a grid.
The value of this parameter ranges from 0 to 99999. After MR rasterization is complete,
all the MRs of a cell in a grid are deleted if the total number of MRs for the cell in the
grid is less than this threshold.
Minimum ECIO Limit(dB): indicates the minimum Ec/Io-filtering threshold. The value
of this parameter ranges from 30 to 0. After MR rasterization is complete, all the MRs
of a cell in a grid are deleted if the average Ec/Io value of the cell in the grid is less than
this threshold.
Filtering ServingCell MR: specifies whether to filter the primary serving cell's MRs.
Serving Cell MR Count Limit: indicates the threshold for filtering the primary serving
cell's MRs. The value of this parameter ranges from 0 to 9999.
Weak Coverage Limit(dBm): indicates the threshold for outdoor weak coverage. The
value of this parameter ranges from 0 to 120.
Indoor Weak Coverage Limit(dBm): indicates the threshold for indoor weak coverage.
The value of this parameter ranges from 0 to 120.
Indoor Weak Coverage MR Ratio Limit(dBm): indicates the threshold for the
proportion of indoor weak coverage MRs. The value of this parameter ranges from 0 to
100.
3 After the parameters related to UMTS MR parsing are set, click Next to import the required
data sources.
UMTS Engineering Parameters File: indicates the save path of the live-network
engineering parameter file corresponding to the UMTS MRs to be parsed.
UMTS RNC MML Path: indicates the save path of the RNC MML configuration file
corresponding to the UMTS MRs to be parsed.
UMTS MR Path: indicates the save path of the UMTS MRs to be parsed.
UMTS Feature Library Path: indicates the save path of the UMTS feature library data
to be parsed.
UMTS feature library data is mandatory if Positioning Type is set to Feature
Positioning and Use AGPS Feature is deselected.
UMTS feature library data is not required if Positioning Type is set to Feature
Positioning and Use AGPS Feature is selected.
UMTS feature library data is optional if Positioning Type is set to AGPS
Positioning or Fast Positioning.
4 Click Finish. If you want to execute the task immediately, select RunNow before you click
Finish.
5 After the task is executed, obtain the result files from the output path, and then import the files
into the U-Net.
UMTSMr_MR Data
Parse_For_Unet.xlsx
----End
2 Parsing 6D Data
1 In the iDart Data Processor Plugin dialog box, click in the upper left corner or choose
File > New Task from the main menu.

Network Type: indicates the RAT of the data to be parsed. Set this parameter to UMTS.
Task Type: indicates the type of the data to be parsed. Set this parameter to 6D(VIP
User/User complaint/Value terminal) Analyze.
3 Import the 6D model file.
For details about how to edit data in the UMTS 6D model file, see the following template:
UMTS 6D Model
Template.xlsx
4 After the basic task parameters are set, click Next to set the parameters related to UMTS 6D
data parsing.
engineering parameter file corresponding to the UMTS 6D data to be parsed.
UMTS RNC MML Path: indicates the save path of the RNC MML configuration file
corresponding to the UMTS 6D data to be parsed.
UMTS RNC PCHR Path: indicates the save path of the UMTS RNC PCHRs to be
parsed.
Finish.
You can select the created task and perform operations, such as computation, storage, and
deletion, on it. To calculate 6D data, you can also click on the toolbar.
into the U-Net.
UM TS_6D Data UM TS_6D Data

ParseValue Terminal
ParseVIP User.csv
----End

1 Parsing Coverage Data
Network Type: indicates the RAT of the data to be parsed. Set this parameter to LTE-
FDD.
Task Type: indicates the type of the data to be parsed. Set this parameter to
Measurement Report Analyze.
Gird Size(m): indicates the grid precision for MR data. Set this parameter properly
based on scenarios.
2 After the basic task parameters are set, click Next to set the parameters related to LTE FDD
MR parsing.
Grid MR Filter Limit: indicates the threshold for filtering a grid's MRs. After MR
rasterization is complete, all the MRs of a grid are deleted if the total number of MRs for
all cells in the grid is less than this threshold.
Grid Cell MR Filter Limit: indicates the threshold for filtering a cell's MRs in a grid.
After MR rasterization is complete, all the MRs of a cell in a grid are deleted if the total
number of MRs for the cell in the grid is less than this threshold.
Minimum RSRP Limit(dBm): indicates the minimum level-filtering threshold. After
MR rasterization is complete, all the MRs of a cell in a grid are deleted if the average
level of the cell in the grid is less than this threshold.
Minimum RSRQ Limit(dB): indicates the minimum RSRQ-filtering threshold. After
MR rasterization is complete, all MRs of a cell in a grid are deleted if the average
reference signal received quality (RSRQ) of the cell in the grid is less than this threshold.
The sequence in which the preceding four filter criteria take effect is as follows: Grid Cell
MR Filter Limit, Minimum RSRP Limit(dBm), Minimum RSRQ Limit(dB), and Grid
MR Filter Limit.
Weak Coverage Limit(dBm): indicates the threshold for outdoor weak coverage. The
value of this parameter ranges from 0 to 120.
Indoor Weak Coverage Limit(dBm): indicates the threshold for indoor weak coverage.
The value of this parameter ranges from 0 to 120.
Indoor Weak Coverage MR Ratio Limit(dBm): indicates the threshold for the
proportion of indoor weak coverage MRs. The value of this parameter ranges from 0 to
100.
3 After the parameters related to LTE FDD MR parsing are set, click Next to import the
required data sources.
LTE-FDD Engineering Parameters File: indicates the save path of the live-network
engineering parameter file corresponding to the LTE FDD MRs to be parsed.
LTE-FDD CHR MML Path: indicates the save path of the CHR file corresponding to
the LTE FDD MRs to be parsed.
Finish.
into the U-Net.
FDD_MR Data
Parse_For_Unet 2015.xlsx
----End
2 Parsing Capacity Data

FDD.
Task Type: indicates the type of the data to be parsed. Set this parameter to Traffic
Statistics Analyze.
traffic statistics parsing.
TargetSpeed(Mbps): indicates the downlink single-UE throughput expected by telecom
operators. The value of this parameter ranges from 0.5 to 20, and affects the cell
bandwidth.
TrafficFactor: indicates the multiple for traffic growth on the live network at a specified
time in the future. The value of this parameter ranges from 0.1 to 200, and affects the
downlink cell throughput.
SubscriberFactor: indicates the multiple for UE number growth on the live network at a
specified time in the future. The value of this parameter ranges from 0.1 to 200, and
affects the cell bandwidth.
Increase Factor(File): allows you to specify the cell-level traffic growth factor and UE
number growth factor using an EXCEL file. If you specify the factors using an EXCEL
file, the factors entered on the UI become invalid.
4 After the parameters related to LTE FDD traffic statistics parsing are set, click Next to import
the required data sources.
LTE-FDD Engineering Parameters File: indicates the save path of the live-network
engineering parameter file corresponding to the LTE FDD traffic statistics to be parsed.
LTE-FDD eNodeB Config Path: indicates the save path of the live-network LTE FDD
eNodeB configuration file corresponding to the traffic statistics to be parsed.
LTE-FDD eNodeB MML Path: indicates the save path of the live-network LTE FDD
eNodeB MML configuration file corresponding to the traffic statistics to be parsed.
LTE-FDD eNodeB Performance Path: indicates the save path of the live-network LTE
FDD eNodeB traffic statistics file corresponding to the traffic statistics to be parsed.
Finish.
into the U-Net.
FDD_Traffic
Data Parse_For_Unet.xlsx
----End
3 Parsing 6D Data
FDD.
Task Type: indicates the type of the data to be parsed. Set this parameter to 6D(VIP
User/User complaint/Value terminal) Analyze.
Gird Size(m): indicates the grid precision for 6D data. Set this parameter properly based
on scenarios.
6D data parsing.
6D Model File: The file contains information about the RAT LTE and frequency band
supported by the UEs you want to analyze. Include complaint data, if there is any, into the
file.
4 After the parameters related to LTE FDD 6D data parsing are set, click Next to import the
required data sources.
engineering parameter file corresponding to the 6D data to be parsed.
UMTS RNC MML Path: indicates the RNC MML configuration file corresponding to
the UMTS MRs to be parsed.
UMTS RNC PCHR Path: indicates the save path of the live-network RNC PCHR
configuration file corresponding to the 6D data to be parsed.
Finish.
into the U-Net.
6D Data 6D Data 6D Data

ParseVIP User_For_Unet.xlsx
ParseFDD LTE Value
ParseComplaint_For_Unet.xlsx
Term.xlsx
----End
5 Site Planning Through the U-Net

1 Creating a Project
1 Start the U-Net.
2 In the U-Net window, click in the upper left corner or choose File > New from the main
menu. Then, perform either of the following operations in the displayed Project Templates
dialog box.
Select UMTS and LTE-FDD if you want to plan LTE sites based on existing UMTS
networks.
Select LTE-FDD if you want to plan LTE sites based on existing LTE networks.
3 Click OK.
----End
2 Saving a Project
You are advised to save a project immediately after it is created. Otherwise, all data about the
project will be stored in the U-Net installation directory by default, resulting in disk capacity
insufficiency. If you save the project promptly, however, the project data will be stored in the
project directory
1 Choose File > Save from the main menu of the U-Net.
2 In the displayed dialog box, enter the project name and select a save type. Two save types are
provided: U-Net file(*.ipl) and U-Net file with all data(*.ipl). U-Net file(*.ipl) is selected by
default.
----End
3 (Optional) Importing a Map
1 In the Project Explorer pane of the U-Net, click , right-click Map, and choose Quick
Import from the shortcut menu.
You can perform operations, such as importing maps by layer, calibrating maps, setting map coordinate
display methods, and setting map parameters.
For details, see GENEX U-Net User Guide.

http://support.huawei.com/carrier/navi#col=software&detailId=PBI1-21606766&path=PBI1-7851894/PBI1-
8132365/PBI1-8132371/PBI1-21395144/PBI1-13953
2 Use either of the methods shown in the following figures to select an electronic map.
The layers of the electronic map are imported into the U-Net by default, as shown in the
following figure.
3 Click OK. Then, wait until all map data is imported.
4 In the Project Explorer pane, click , and then select MAP to verify that the electronic
map has been successfully imported.
5 Choose Map > Clutter. Then, right-click Clutter and choose Parameter Management from
the shortcut menu. In the displayed Clutter Parameters Display dialog box, verify parameter
settings.
The following table describes clutter parameters.
Parameter Description Value
Clutter Class Name of a clutter type The value of this parameter is determined
by geographical data.
Clutter Height Height of a clutter The default value is 0 (unit: m).
Penetration Loss Loss caused by The default value is 0 (unit: dB). The
penetration value of this parameter varies according to
propagation environment conditions.
Model Standard Standard variance of The default value is 7 (unit: dB). The
Deviation slow fading margin value of this parameter varies according to
propagation environment conditions.
Shadow Corr Coefficient of shadow The default value is 0.5. The value of this
fading parameter varies according to propagation
environment conditions.
C/(I+N) Standard Standard variance based The default value is 4 (unit: dB).
Deviation on C/(I + N)
----End
4 (Optional) Setting a Propagation Model

The U-Net allows you to select multiple propagation models, such as Okumura-Hata, Cost-
Hata, and SPM. SPM is a standard propagation model defined by the U-Net. Set propagation
model parameters properly based on scenarios and areas.
The propagation model settings and clutter settings have great impact on planning results. You
are advised to set propagation models and clutters accurately following the experience of
frontline personnel or telecom operators.
1 In the Project Explorer pane of the U-Net, click and choose Propagation Models >
Cost231 Hata > Cost Hata(default). Then, right-click Cost Hata(default) and choose
Properties from the shortcut menu.
2 On the Parameters tab page of the displayed Cost Hata(default) dialog box, click Formula.
In the displayed Cost-Hata Formula dialog box, set parameters properly.
The following table describes propagation model parameters.
Parameter Description
Lu Lu = K1 + K2 x lg(f) K3 x lg(Hb) + [K4 K5 x lg(Hb)] x lg(d)

a(Hm) Indicates the effective antenna correction factor, which is a function based
on the coverage area size.
In a large city, the value of this parameter is calculated using the following
formula:
a(Hm) = K10 x [lg(K11 x Hm)]2 K12
In a rural area or small city, the value of this parameter is calculated using
the following formula:
a(Hm) = [K6 x lg(f) K7] x Hm [K8 x lg(f) K9)
Cm Indicates the factor for center calibration in large cities. The value of this
parameter varies in different scenarios. In addition, the value of this
parameter has been considered in KI, and therefore is not presented in
formulas.
f Indicates the frequency range. The value of this parameter ranges from 1500
MHz to 2000 MHz.
Hb Indicates the base station's antenna height. The value of this parameter
ranges from 30 m to 200 m.
d Indicates the distance between the base station and the UE. The unit is km.
If you want to plan LTE sites based on existing UMTS networks, set the propagation
model parameters of each cell.
The Cost Hata model is used by default. You can select other propagation models based on
scenarios.
If you want to plan LTE sites based on existing LTE networks, set the propagation model
parameters of each cell.
The Cost Hata model is used by default. You can select other propagation models based on
scenarios.
----End
5 (Optional) Importing and Setting Antenna

Information
The U-Net supports two types of antenna files: MSI (industrially universal format) and Text
(text format). If antenna files can be obtained, import them by following the instructions
provided in the following figure.
If antenna files cannot be obtained, you need to specify the antenna name, and manually select
a type of antenna file with the closet performance (navigation path: Network > Transceiver).
After antenna files are imported, you can view or modify antenna attributes. For details, see
GENEX U-Net User Guide, which can be obtained in section 73"U-Net
V300R010C00SPC100 Release Notes."
6 Setting Frequencies
If the imported frequencies and bandwidths do not exist in the frequency information on the
U-Net, you must define new frequencies and bandwidths that are different from the imported
ones. The defined frequency information will be applied in the cell list. You can set frequency
bands through a table or the attribute panel.
The following figure shows how to add a UMTS frequency band.
The following figure shows how to add an LTE frequency band.
You can click * to add a new frequency band by setting the following parameters:
Band Number: indicates the serial number of the frequency band.
Name: indicates the name of the frequency band.
Bandwidth(MHz): indicates the bandwidth of the site operating on the frequency band.
Actual Bandwidth(MHz): indicates the actual bandwidth, which is used when the live
network uses a non-standard bandwidth.
Start Channel Index: indicates the start index of the frequencies available on the
frequency band.
End Channel Index: indicates the end index of the frequencies available on the
frequency band.
Excluded Channels: indicates the indexes of excluded channels.
Frequency(DL)(MHz): indicates the downlink frequency provided by telecom
operators.
Frequency(UL)(MHz): indicates the uplink frequency provided by telecom operators.
Useable RB Num: indicates the number of actually available RBs. The value of this
parameter varies according to the actual bandwidth.
7 Importing Engineering Parameters

1 Choose File > Import > Engineering Parameters > RAT from the main menu of the U-Net.
RAT indicates the RAT of the engineering parameters you want to import.
In LTE site planning based on existing UMTS networks, import two files: one contains
UMTS engineering parameters and the other contains the engineering parameters about
LTE FDD candidate sites.
In LTE site planning based on existing LTE networks, import only LTE FDD engineering
parameters.
If you choose UMTS, the Data Import dialog box shown in the following figure is
displayed.
If you choose LTE-FDD, the Data Import dialog box shown in the following figure is
displayed.
You must manually reconfigure the Destination and Source fields properly if the two fields do not
match.
If the frequencies and bandwidths in the imported engineering parameters do not exist in the U-Net,
you must manually add the frequencies and bandwidths. For details, see section 6"Setting
Frequencies."
2 In the Project Explorer pane, click . Then, select Site, right-click it, and choose Open
Table from the shortcut menu to view site results.
----End
8 Setting the Template for New Sites

This section describes how to set the attributes of the new sites planned by LTE ASP using a
site template.
1 If no existing site template meets requirements, add a site template or modify an existing site
template, as shown in the following figure.
2 In the displayed Station Template Properties dialog box, click Add to add a site template, or
double-click an existing site template to modify it.
3 Set or modify the antenna and propagation model parameters of the site template.
4 Set or modify the frequency and bandwidth parameters of the site template.
----End
9 Setting an Analysis Area

1 Click on the U-Net to draw a polygon based on planning to specify an analysis area.
2 In the Project Explorer pane, click . Then, select Polygon_Draw_1, right-click it, and
choose Properties from the shortcut menu. In the displayed Polygon Properties dialog box,
set the border attributes of the polygon, as shown in the following figure.
Each polygon is drawn based on radio network conditions (for example, different propagation models
are used in urban and suburban areas). In addition, only one propagation model can be configured in the
site template for one polygon. If the new polygon you have drawn covers both urban and suburban areas,
the propagation model used by new sites is applied in the urban and suburban areas, causing inaccurate
planning results.
----End
10 Importing MRs
1 Importing Preprocessed MR Data
LTE Site Planning based on Existing UMTS Networks

1 In the Project Explorer pane of the U-Net, click , right-click Measurement Report, and
choose Import from the shortcut menu.
2 In the displayed Import Measurement Report dialog box, select the MR preprocessing
result file locationunet*.csv generated by the U-Net plug-in and click Import. For details
about the file, see section 4322"Parsing Capacity Data."
Network Type: indicates the RAT. Set this parameter to UMTS.

Resolution(m): indicates the MR grid precision. The default value of this parameter is
50.
3 In the displayed Field Mapping dialog box, verify the mapping between the fields
preprocessed by the U-Net plug-in and those supported by the U-Net. Then, click OK.
If the location files of multiple frequencies are available, you need to import all the location
files at a time for PS service geographic observation.
4 Import preprocessed MRs.
----End
LTE Site Planning based on Existing LTE Networks

1 In the Project Explorer pane of the U-Net, click , right-click Measurement Report, and
5 In the displayed Import Measurement Report dialog box, select the MR preprocessing
result file location*.csv generated by the U-Net plug-in and click Import. For details about
the file, see section 4322"Parsing Capacity Data."
6 In the displayed Field Mapping dialog box, verify the mapping between the fields
preprocessed by the U-Net plug-in and those supported by the U-Net. Then, click OK.
Focus on the following fields: MR Count, RSRP, and RSRQ.
7 Import preprocessed MRs.

----End
2 Generating MR Views
For a New MR Group in LTE Site Planning based on Existing UMTS

Networks
1 In the Project Explorer pane of the U-Net, click after an MR group is created. A node
named after the MR group is displayed under Measurement Report. Right-click the node
and choose New Query View from the shortcut menu.
2 In the displayed New Query Viewer dialog box, set the criteria for filtering MRs from
various dimensions, and then click OK. If you do not set such criteria, the U-Net does not
filter MRs.
The parameters in the New Query Viewer dialog box are as follows:
Area: indicates the desired polygon.
Max cell distance (m): indicates the distance between the cell, to which the MRs
belong, and the site. The default value of this parameter is 4,000.
Add Condition: indicates an MR filter criterion.
You can click Add to add a filter criterion.
3 Right-click UMTS MR Measurement Report1 View 1 and choose Display Full Map from
the shortcut menu. In the displayed MR Study Types dialog box, select map layers and click
OK.
4 Choose Measurement Report > Measurement Report1 > UMTS MR Measurement

Report1 View 1 > PS MR Count to view the imported MR view, including the indoor and
outdoor level distribution.
----End
For a New MR Group in LTE Site Planning based on Existing LTE

Networks
1 In the Project Explorer pane of the U-Net, click after an MR group is created. A node
named after the MR group is displayed under Measurement Report. Right-click the node
and choose New Query View from the shortcut menu.
5 In the displayed New Query Viewer dialog box, set the criteria for filtering MRs from
various dimensions, and then click OK. If you do not set such criteria, the U-Net does not
filter MRs.
You are advised to select the MR count, longitude, or latitude criterion. This enables the U-
Net to filter out the MRs in each grid, whose number of MRs is less than 5, and those whose
longitude or latitude exceeds a preset range. If you do not do so, a large number of MRs may
need to be processed. As a result, the U-Net cannot generate traffic geographic observation
results or ASP results. In addition, you can specify the maximum distance between the cell, to
which MRs belong, and the site. This enables the U-Net to filter out the MRs of each cell,
whose distance to the site exceeds the maximum distance.
6 Right-click LTE FDD Measurement Report1 View 1 and choose Display Full Map from
the shortcut menu. In the displayed MR Study Types dialog box, select map layers and click
OK.
7 Choose Measurement Report > Measurement Report1 > LTE FDD Measurement
Report1 View 1 > MR Count to view the imported MR view, including the indoor and
outdoor level distribution.
----End
11 Preparing Grid-based Traffic Maps
A grid-based traffic map contains information about the traffic in each grid. The U-Net
distributes traffic onto grids based on the MR preprocessing results and live-network traffic
statistics to generate a grid-based traffic map. A grid-based traffic map represents network-
wide traffic information in the U-Net functions, such as ASP. If you plan LTE sites on a live
UMTS network and the UMTS PS traffic will become LTE PS traffic after the planning, the
PS traffic will be absorbed by the existing and new LTE cells on the live network, and will be
used to calculate LTE site values and traffic centers.
1 Importing Traffic Data

1 In the Project Explorer pane of the U-Net, click . Then, right-click Traffic Statistics and
2 In the displayed Import Traffic Statistics dialog box, select the preprocessed traffic data file
Rnc_*Capacity audit result*.csv and click Import. For details about the file, see section
4322"Parsing Capacity Data."
3 In the displayed Field Mapping dialog box, verify field mapping and click OK. If the file
fails to be imported, select ignore for each empty column.
4 Import traffic data.
RNCID, CI, and Cell Name uniquely identify a cell. They must be consistent with the imported
engineering parameters. Otherwise, grid-based traffic maps cannot be generated and the volume of
traffic in each grid is 0.
----End

1 In the Project Explorer pane of the U-Net, click . Then, right-click Traffic Statistics and
5 In the displayed Import Traffic Statistics dialog box, select the preprocessed traffic data file
LTETraffic_*.csv and click Import. For details about the file, see section 4322"Parsing
Capacity Data."
Network Type: indicates the RAT. Set this parameter to LTE-FDD.

Select Files: allows you to select the preprocessed traffic data file you want to import.
6 In the displayed Field Mapping dialog box, verify the mapping of fields, such as
CELLNAME, TAC, CELLID, PS TRAFFIC, and TOTALBW.
Focus on the fields shown in the following figures.
7 Import traffic data.
TAC, CI, and Cell Name uniquely identify a cell. They must be consistent with the imported
engineering parameters. Otherwise, grid-based traffic maps cannot be generated and the volume of
traffic in each grid is 0.
----End
2 Generating Traffic Views

1 In the Project Explorer pane of the U-Net, click after a traffic map is created. A node
named after the traffic map is displayed under Traffic Statistics. Right-click the node and
choose New Query View from the shortcut menu.
2 In the displayed New Query Viewer dialog box, set the criteria for filtering traffic statistics
from various dimensions, and then click OK. If you do not set such criteria, the U-Net does
not filter traffic statistics.
The parameters in the New Query Viewer dialog box are as follows:
Add Condition: indicates a traffic statistics filter criterion.
You can click Add to add a filter criterion.
----End

1 In the Project Explorer pane of the U-Net, click after a traffic map is created. A node
named after the traffic map is displayed under Traffic Statistics. Right-click the node and
choose New Query View from the shortcut menu.
3 In the displayed dialog box, set the criteria for filtering traffic statistics from various
dimensions, and then click OK. If you do not set such criteria, the U-Net does not filter traffic
statistics.
----End
3 Generating MR Grid-based Traffic Maps

1 Create a traffic map group on the U-Net, as shown in the following figure.
2 Create a traffic map, as shown in the following figure.
Traffic statistic data Indicates the desired traffic view.

Create Traffic Map Based On Specifies whether the traffic map will be created based on clutters or MRs.
Measurement Report Setting Specifies the MR view used for generating the traffic distribution.
The traffic map is similar to that shown in the following figure after being created.
----End

1 Create a traffic map group on the U-Net, as shown in the following figure.
3 Create a traffic map, as shown in the following figure.

Traffic statistic data Indicates the desired traffic view.

Create Traffic Map Based On Specifies whether the traffic map will be created based on clutters or MRs.
Measurement Report Setting Specifies the MR view used for generating the traffic distribution.
The traffic map is similar to that shown in the following figure after being created.
----End
12 Importing and Planning ASP Data

Coverage and traffic data
Such data has been imported in sections 10"Importing MRs" and 11"Preparing Grid-
based Traffic Maps."
Data about UEs and valued services
If data about UEs and valued services is available, the U-Net automatically matches the
data in the result file Rnc_*Capacity audit result*.csv, which is generated in section
43"Selecting Features," with valued UEs and services when importing the file in
11"Preparing Grid-based Traffic Maps."
Data about VIP users and complaining users
VIP user data is imported through the VIP user data.csv file generated in section
36"(Optional) 6D Data." Complaining user data is imported through the Complaint
sheet described in section 36"(Optional) 6D Data."
Valued service data

The valued service dimension is not used for 6D evaluation if the value of revenue of PS
per kBytes is 0.

Coverage and traffic data
Such data has been imported in sections 10"Importing MRs" and 11"Preparing Grid-
based Traffic Maps."
Data about VIP users and complaining users
Such data is imported as follows:
LTE eNodeBs cannot identify IMSIs. In LTE site planning based on existing LTE networks, the U-Net
cannot identify users or UEs based on the data reported by eNodeBs. As a result, the VIP user and
complaint dimensions cannot be used in LTE site planning.
Valued service data
The valued service dimension is not used for 6D evaluation if the value of revenue of PS
per kBytes is 0.
3 Site Planning Through ASP
1 In the Project Explorer pane of the U-Net, click . Then, choose ASP > LTE, right-click
LTE, and choose New from the shortcut menu.
2 In the displayed New Site Planning dialog box, set Group Name to LTE Site Planning 1.
----End
4 Setting Site Planning Parameters

For details about site planning parameters, see section 41"Site Planning Parameters."
The parameters for LTE site planning based on existing UMTS networks are the same as
those for LTE site planning based on existing LTE networks except the following: In LTE site
planning based on existing UMTS networks, one more parameter MR/DT Conversion is
provided for setting the conversion of level values between frequency bands.
Parameters on the General Tab Page

For details about the definitions of the parameters used for LTE site planning based on
existing UMTS networks, see section 411"Parameters on the General Tab Page."
UMTS MR/DT data can be converted into LTE MR/DT data, involving inter-system inter-band
conversion. The U-Net can obtain the LTE coverage for dense or common urban areas based on UMTS
DT data. It supports only the inter- or intra-band conversion between the frequency bands from 1.8 GHz
to 2.6 GHz and between the frequency bands from 900 MHz to 800 MHz. In addition, the U-Net
requires that the azimuth difference be less than 5 degrees.
Set parameters on the General tab page as follows:

1 (Mandatory) Select data sources, such as MR and traffic map (
).
2 (Mandatory) Enable MR/DT conversion ( ).
If Resolve coverage hole ( ) is
selected, you must enable inter-system MR/DT ( ), which uses

LTE MRs as the data source. Specify the polygon, scenario, source UMTS network,
target LTE network, and offset (dB). (Use the default offset or set a new one. For intra-
band conversion, the default offset is 0. If frequency band conversion shows a deviation,
you need to set the offset based on network conditions.)
3 (Optional) Specify the scenario and precision.
Set the parameters based on network conditions. For details, see section 41"Site Planning
Parameters." Skip this section if the parameters do not need to be set.
4 (Optional) Set parameters for hotspot areas separately.
If two or more polygons are displayed in the Computation area region, you can activate
each polygon separately and specify a different scenario for each polygon in the Focus
area region.
For details about the definitions of the parameters used for LTE site planning based on
existing LTE networks, see section 411"Parameters on the General Tab Page."
Parameters on the Objective Tab Page

The Objective tab page contains the parameters for setting expected coverage and capacity,
and for defining weak coverage grids. You are allowed to set only the parameters for
coverage-based ASP. If there are multiple polygons, you can set the expected coverage of
each polygon separately.
If coverage-based site planning is used, select Resolve poor coverage. If capacity-based site
planning is used, select Resolve capacity overload. To add carriers to a frequency band,
select the frequency band in the Expansion Settings area.
In LTE site planning based on existing UMTS networks, you only need to select Resolve coverage hole
if the coverage hole-resolving function is enabled.
Parameters on the Strategy Tab Page
For details about the parameter definitions, see section 413"Parameters on the Strategy Tab
Page."
The Strategy tab page provides the parameters for selecting site addition policies, covering
macro sites, micro sites, and candidate sites.
1 Select site addition policies.
Four site addition policies are provided: Allow macro site addition, Allow micro site
addition, Allow site selection, and Allow add indoor site. Allow site selection
specifies whether site selection is allowed. To provide LTE deep coverage, select Allow
macro site addition, Allow micro site addition, and Allow add indoor site, and decide
whether to select Allow site selection based on network conditions.
5 Specify candidate sites and mandatory sites.
If Allow site selection is selected, set Planning Status (Locked for mandatory sites and
Candidate for candidate sites). In normal cases, LTE sites that have been planned are
mandatory sites and reusable GSM and TD-SCDMA sites are candidate sites.
In LTE site planning based on existing UMTS networks, you need to set Original Status to Deactive for
all sites if no LTE sites are previously deployed. (You can set Original Status to Deactive only for the
first site, and then press Ctrl+D to change the value of Original Status to Deactive for all the other
sites.)
6 Specify the clutters where sites will not be added (the default parameter settings are
recommended).
Click Set Clutter Constraint. In the displayed Clutter Constraint dialog box, you can
specify the clutters where sites will not be added.
7 (Optional and required for site selection) Set the costs of candidate sites.
You can enter the costs of candidate sites according to 6D evaluation results. Site costs
must be discussed and determined together with frontline delivery personnel.
8 Set site priorities.
If 3D maps are available, the default sequence of adding sites is as follows: selecting
indoor micro sites, adding indoor micro sites, selecting outdoor macro and micro sites,
adding macro sites, adding outdoor micro sites, and adding outdoor micro sites for
improving indoor coverage. If no 3D maps are available, the default sequence of adding
sites is as follows: selecting indoor micro sites, selecting macro and outdoor micro sites,
adding macro sites, adding outdoor micro sites, and adding indoor micro sites.
Parameters on the Advanced Tab Page

For details about the parameter definitions, see section 414"Parameters on the Advanced Tab
Page."
5 Executing Site Planning
In the Project Explorer pane of the U-Net, click . Then, right-click LTE Site Planning 1
and choose Calculate from the shortcut menu.
You can right-click LTE Site Planning 1 and choose Stop from the shortcut menu to stop the
project during project execution.
13 Analyzing Site Planning Results
The U-Net provides two methods of displaying site planning results: through tables or in the
GIS. You can check whether the ASP results are proper by analyzing the coverage fulfillment
rate, coverage improvement, coverage maps, number of added sites, and traffic absorption.
1 Viewing Site Planning Results

and choose Open Result from the shortcut menu. In the LTE Site Planning 1 Result area of
the right pane, you can click Export to export the statistics tables.
For details about the parameters on each tab page in the preceding figure, see section
42"Parameters for Site Planning Results."
2 Analyzing Coverage Maps
Creating a Coverage Map

1 In the Project Explorer pane of the U-Net, click . Then, choose ASP > LTE > LTE Site
Planning 1 > Coverage Map, right-click Coverage Map, and choose New from the shortcut
menu.
2 In the displayed Study Types dialog box, select map layers and click OK. For details about
the parameters, see section 43"Parameters for Layers." The selected layers will be displayed
under Coverage Map in the Project Explorer pane and in the GIS in the right pane. Deselect
the layers you do not want to view in the GIS.
----End
Viewing a Coverage Map

In the Project Explorer pane of the U-Net, click . Then, select layers, which you want to
view, under Coverage Map.
3 Associating Tables with the GIS Through Open Result
The U-Net can display site planning results in the GIS. To view the results of a project in the
GIS, select the project, right-click it, and choose Open Result from the shortcut menu. This
section uses LTE Site Planning 1 as an example.
In the LTE Site Planning 1 Result area displayed in the right pane, the Site tab page is
associated with the GIS. Select a site on the Site tab page, and the site is selected and
displayed in blue in the center of the GIS.
The Transceiver tab page is associated with the GIS. Select a cell on the Transceiver tab
page, and the cell is selected and displayed in blue in the center of the GIS.
The Traffic Absorption tab page is associated with the GIS. Select a cell on the Traffic
Absorption tab page, and the coverage of the cell is displayed in the GIS.
If you right-click LTE Site Planning 1 and choose Display Setting from the shortcut menu,
the Display Setting dialog box is displayed.
On the Symbols tab page, you can set the size and symbol of each new site, and specify
whether to display traffic absorption relationships and whether to hide the names of new
sites.
On the Cell Coverage tab page, you can specify whether to display absorbed traffic in
different colors and select colors.
If you choose LTE Site Planning 1 > Transceiver Color > Final Status, right-click Final
Status, and choose Properties from the shortcut menu, the Final Status Properties dialog
box is displayed.
On the Display tab page, you can specify whether to display the transceivers in different
states, and set the colors in which you want the transceivers to be displayed. A transceiver will
be displayed if it is selected.
4 Verifying Site Planning Results

Verify coverage-based site planning results from the following aspects:
1 All new sites are located in weak coverage areas.
2 All new sites are located in the weak coverage centers of hotspot areas.
3 New sites are added in all weak coverage areas.
4 The expected coverage fulfillment rate is reached.
For aspects 1 and 2, you need to manually correct site planning results by moving or
removing improperly selected sites.
For aspect 3, sites may fail to be added in an area because the expected coverage fulfillment
rate has been reached or the distance between sites does not meet requirements. In such a
situation, manually check whether sites can be added, and then add sites to resolve weak
coverage if possible.
For aspect 4, you can manually plan new sites in a weak coverage area based on traffic maps
if the expected coverage fulfillment rate is not reached.
14 (Optional) Modifying Site Planning Results
1 Submitting Site Planning Results
For new sites added through ASP, submit ASP results before the modification. For existing
sites, do as follows to directly modify them:
and choose Commit from the shortcut menu.
After the site planning results are submitted, new sites are added to the engineering parameter
lists for the Site and Transceiver nodes on the tab page in the Project Explorer pane.
2 Adding and Removing Sites
Select on the toolbar. Then, you can click anywhere in the GIS to add a new site. You can
also right-click a site and choose Delete from the shortcut menu in the GIS to remove the site.
3 Moving Sites
Select a site. Then, select the black dot in the center of the site symbol and hold the left mouse
button to move the site.
4 Modifying Sector Azimuths

Select the sector of a site. Then, select the green dot and hold the left mouse button to adjust
the azimuth to any degree within the 360-degree range.
5 Reconfiguring Other Parameters

In the Project Explorer pane of the U-Net, click . Then, right-click Site or Transceiver
and choose Cells > Open Table > RAT (UMTS or LTE-FDD) from the shortcut menu. Then,
you can reconfigure other parameters, such as the azimuth and propagation model, for one site
or for multiple sites in batches.
In the right pane of the U-Net, you can right-click a site and choose Site Properties,
Transceiver Properties, or Cell Properties from the shortcut menu to reconfigure desired
parameters.
15 (Optional) Performing Simulation After Site
Planning Result Modification
1 Submit site planning results.
If site planning results have not been submitted, submit the results before simulation. For
details, see section141"Submitting Site Planning Results."
2 Reconfigure site planning parameters.
Right-click an existing ASP project and choose Properties from the shortcut menu. This
section uses LTE Site Planning 1 as an example. On the Strategy tab page of the
displayed LTE Site Planning 1 dialog box, set Original Status to Active for live-
network sites (to calculate initial live-network coverage), and set Original Status to
Deactive for the new sites added through ASP and those manually added (to exclude
non-live-network sites from the calculation of initial live-network coverage).
Set Planning Status to Excluded for the live-network sites not selected in earlier site
planning results. By doing so, you exclude the sites not covered by ASP. In addition, set
Planning Status to Locked for the other sites, including the live-network sites selected
by ASP, sites added through ASP, and sites you have manually added.
You can set Original Status to a specific value only for one site, and then press Ctrl+D
to set Original Status to this value for all the other desired sites.
Deselect all the options for adding new sites. Select only Allow site selection.
3 Execute the project and update simulation results.

Right-click the project and choose Calculate from the shortcut menu to start another
simulation calculation. After the calculation is complete, the U-Net updates the site
planning results.
Right-click the project and choose Open Result from the shortcut menu. Then, you can
view the updated site planning results on the Table and Coverage Map tab pages in the
project result area of the right pane.
3 FDD-LTE Indoor Intensive
Coverage Site Planning
1 Indoor Planning Principles and Functions

1 Indoor and Outdoor Traffic Differentiation
All or several measurement reports (MRs) of a single call can be used to determine whether
the traffic is generated inside or outside a building. Based on the differentiation results and the
signal strength data of a call, the radio transmission environment features and the user
communication demands of an area can be better analyzed with various dimensions, making
network planning and optimization methods better meet the requirements of operators.
Specific fields, whose structures are applicable to the following feature dimensions, are
extracted from the MRs and engineering parameters to determine whether a call occurs in an
indoor or outdoor area. Feature dimensions for indoor and outdoor traffic differentiation are as
follows:
Signal level features
Signal level when a call is received
Around a position in a macro site area, the signal level of an outdoor call is stronger
than that of an indoor call.
Stability level when a call is received
The indoor transmission environment is stable. Therefore, the indoor signals are more
stable than the outdoor signals.
Call features
Call duration
A long call is more likely to occur in an indoor area.
Call time
A call at night is more likely to occur in an indoor area.
Call inertia
When a subscriber is in a call at a specific position, the subscriber's common position
can be identified based on subscriber behavior. The call is more likely to occur in an
indoor area.
Service features
Service types, such as the voice call and data service
Based on subscriber behavior, a data card service is more likely to occur in an indoor
area.
Motion features
Moving distance and speed of a subscriber
This dimension requires the assistance of geographic location. If a subscriber is
moving at a high speed or the subscriber's location changes quickly during a call, the
call is more likely to occur in an outdoor area.
Cell features
Serving cell type, such as the macro base station and indoor distributed base station
(DBS)
An indoor DBS is deployed to cover indoor areas. A call served by an indoor DBS is
more likely to occur in an indoor area.
Number of serving cells
If multiple serving cells are involved during a call, the call is more likely to occur in
an outdoor area and the subscriber in the call may move. If only one serving cell is
involved during a call, the call is more likely to occur in an indoor area because the
indoor signal is more stable.
Handover features
Ping-pong handover between two cells and among three cells
If a ping-pong handover occurs during a call, there is a high probability that the
subscriber does not move during the handover. This feature can be used with other
dimensions to identify whether a call occurs in an indoor or outdoor area.
Handover among multiple cells
If multiple cells are involved in a handover, a call is more likely to occur in an
outdoor area.
Neighboring cell features
The number of cells whose signals are received by a UE during an indoor call is less than
that during an outdoor call. A cell's signals that can be received in the outdoor area may
exceed the demodulation threshold in the indoor area, which reduces the number of cells
whose signals are received by a UE during an indoor call.
The confidence level of each feature dimension is different. A single dimension cannot
ensure that the differentiation is correct, and some dimensions even conflict with others.
The conflict must be considered and each dimension should have a proper weight to
obtain a comprehensive differentiation result.
2 Application Scenario and Market Value

Facilitating indoor site acquisition in hotspots
Indoor and outdoor traffic evaluation results with geographic location distribution in
hotspots minimize the number and capacity of new indoor or outdoor base stations and
provide accurate site location.
Simplifying and speeding up the complaint handling process
Location-based indoor and outdoor traffic differentiation helps maintenance personnel
quickly identify the fault location and develop handling solutions specific for outdoor or
indoor scenarios.
Providing network-level, controller-level, and cluster-level outdoor and indoor traffic
evaluation
Indoor and outdoor traffic evaluation at different levels helps operators determine
whether the proportions of existing indoor and outdoor base stations are reasonable.
Facilitating weak coverage analysis
Location-based weak coverage analysis of indoor and outdoor traffic helps operators
develop network optimization solutions, such as outdoor or indoor site addition.
Providing indoor traffic evaluation
Indoor traffic evaluation helps determine whether the indoor traffic proportion meets the
expectation and whether the location and number of indoor base stations need to be
adjusted.
3 Feature Value
1 Site type of the primary serving cell
Use the engineering parameter table to determine the site type of the primary serving cell
(whether it is an indoor DBS).
2 User moving speed
Calculate the average moving speed of the user based on the displacement during a call
and call duration.
3 Handover rate of the primary serving cell
Calculate the handover rate based on the number of handovers of the primary serving
cell during each call.
4 User displacement
Determine the user displacement based on the MR positioning results.
5 Receive level of the primary serving cell
Determine whether the penetration loss of the signal level at the place where the user is
located occurs according to the propagation model and delay.
6 Overall receive level fluctuation of the primary serving cell
Calculate the overall level fluctuation of the primary serving cell and provide related
waveform parameters.
7 Receive level step fluctuation of the primary serving cell
Calculate the frequency of step level during a call.
8 Total number of primary serving cells
Count the number of primary serving cells during a call.
4 Training Algorithm
Based on collected DT data, use the algorithm to generate an indoor and outdoor
differentiation determination threshold and sequence of each element, to establish a new
comprehensive multi-dimensional determination model. The algorithm is currently under pre-
research. Therefore, if any modification is required for the algorithm, contact Jia Mingbo
(employee ID: 00295291).
5 Comprehensive Multi-dimensional Determination

The machine learning algorithm is used for comprehensive multi-dimensional determination.
The determination threshold of feature values is based on DT data. If no DT data is available,
default parameter values can also be used for determination.
Due to different natural environment, building structure, distance between base stations, and
radio signals, different sites has different indoor and outdoor features. Therefore, to achieve
the optimal accuracy of the algorithm, it is recommended that the comprehensive
determination model be trained by using DT data during indoor and outdoor traffic
differentiation. The more training sets are provided, the more accurate the calculated feature
value is.
To achieve the real-time optimal state of the algorithm, online training based on AGPS and
MDT data of white list users will be used to improve the comprehensive determination model.
6 Algorithm Process
The following figure shows the indoor and outdoor traffic differentiation algorithm process.
1 Indoor and outdoor traffic differentiation algorithm process
Indoor site addition is based on the indoor and outdoor differentiation results. MR data and
engineering parameters can be used to determine whether the communication occurs in indoor
or outdoor scenarios. Based on the differentiation results and the signal strength data of a call,
the radio transmission environment features and the user communication demands of an area
can be better analyzed with various dimensions, making network planning and optimization
methods better meet the requirements of operators.
2 FDD-LTE Indoor Intensive Coverage Site
Addition
Indoor site addition, outdoor macro site addition, and outdoor micro site addition can be
performed in a customized sequence.
Signals are attenuated significantly due to walls in the buildings. Therefore, indoor intensive
coverage is performed to avoid weak coverage. To maximize operator' return on investment,
indoor traffic hotspots are considered during indoor site addition based on intensive coverage.
Base stations are only added at the traffic hotspots with weak coverage. The indoor coverage
fulfillment rate will not be considered.
Cell-level analysis
Intensive coverage site addition is performed when the grid indoor level is lower than the
value (such as 110 dBm) of indoor RSRP threshold to solve the indoor weak coverage
problem.
The coverage-based indoor site addition process is as follows:
1 Pre-process MRs and traffic statistics.
Position MR data and differentiate indoor and outdoor traffic to obtain rasterized MR data, the
number of indoor MRs, the number of outdoor MRs, indoor and outdoor level strength, and
the confidence of indoor MRs. Use traffic statistics to obtain cell-level traffic volume and
evaluate the load capacity of cells for capacity-oriented site addition.
2 Screen candidate grids for site addition.
A candidate grid for indoor site addition must meet the following conditions:
The indoor coverage is weak.
Heavy indoor traffic exists.
The number of indoor MRs is greater than that of outdoor MRs.
An indoor heavy traffic grid must meet the following conditions:
The number of indoor MRs in the grid is greater than or equal to Z times the average
number of indoor MRs of grids with at least one MR.
Indoor traffic volume in the grid is greater than or equal to a certain threshold to ensure
operators' return on investment.
3 Locate candidate buildings.
A 3D e-map is required to locate candidate buildings. On the 3D e-map with candidate grid
information, locate buildings with the required height (for example, 6 m) in continuous grids
(5 m x 5 m) and calculate the floor area and maximum height. A candidate building is one
whose floor area is equal to or greater than the value of Indoor 3D related building area(m)
and whose height is equal to or greater than the value of Indoor 3D related building
height(m).
If no 3D e-map is available, export the information on the planning point, import the
information to Google Earth, and screen indoor sites on the map.
4 Perform traffic absorption simulation and provide suggestions on capacity configuration.
Based on the 3D e-map, perform traffic absorption simulation to evaluate the traffic of indoor
sites to be added. Calculate the capacity of these sites or the number of required carriers based
on the relationship of the equivalent number and the MR number.
5 Prioritize candidate sites.
Prioritize candidate sites based on the traffic volume of indoor planning points.
----End
3 Indoor Intensive Coverage Site Planning
Process
1 Indoor and Outdoor Traffic Differentiation Process
1 Collect MR data. For details, see WINS V100R006C00 LTE FDD Inventory Solution Data
Collection Guide.
2 Prepare DT data for typical scenarios.
Software: GENEX Probe or GENEX PHU
Scenario: Buildings not deployed with the indoor distributed system and areas around the
buildings
Type: classified into indoor and outdoor areas with test data saved
Requirement: all floors involved in the indoor test
Scale and duration: 1 or 2 typical buildings with test duration of 1 to 2 hours
3 Train algorithm: Deliver typical original tests to the R&D engineer Jia Mingbo (employee ID:
00295291). Before algorithm training, identify the proportion of indoor traffic to outdoor
traffic. Normally, the proportion is 8:2. The proportion of indoor traffic to outdoor traffic and
the proportion of indoor MRs to outdoor MRs cannot be modified after they are identified.
The parameter engineer informs the user of the modified configurations of advanced
parameters after algorithm training.
4 Check U-Net plug-in output: Check whether the number of indoor MRs, the number of
outdoor MRs, average RSCP, and average Ec/Io are consistent with the actual situation.
5 Check the result: The indoor and outdoor traffic differentiation process is finished if the
preceding values are consistent with the actual situation. Otherwise, the algorithm training has
to be performed again.
----End
2 FDD-LTE Indoor Intensive Coverage Site Planning

Process
The site planning process for FDD-LTE indoor intensive coverage is as follows:
1 Prepare the data source of MRs and traffic statistics. For details, see WINS V100R006C00
LTE FDD Inventory Solution Data Collection Guide.
2 Use the U-Net plug-in to process data.
1 Configure parameters according to the configurations provided by the R&D engineer.
2 Preset Indoor Weak Coverage Limit(dBm) and Indoor Weak Coverage MR Ratio
Limit(%) before data processing.
Presetting the two preceding parameters will affect the planning result and cannot be modified during U-
Net planning. Use the U-Net plug-in to process data again if the two parameters need to be modified.
Indoor Weak Coverage Limit(dBm): This parameter has to be set according to the
requirements of the planning provided by the operator or Huawei.
Indoor Weak Coverage MR Ratio Limit(%): Changing the value of this parameter
affects the number of identified grids with weak coverage. The U-Net plug-in regards
a grid as a weak-coverage grid if the ratio of MRs with the level less than the defined
threshold is greater than the defined value of this parameter. Otherwise, the U-Net
plug-in regards a grid as a non-weak-coverage grid. According experience in X site in
China, it is recommended Indoor Weak Coverage MR Ratio Limit(%) be set to 20.
3 Use the U-Net to perform the site planning.

For details, see section 25"Site Planning Through the U-Net." Considerations during planning
are as follows:
Penetration loss setting: The following table shows the recommended clutter penetration
loss model in China. The model can be replaced as required in other areas.
Clutter
Penetration Loss Setting.xlsx
Propagation model selecting: Select a propagation model matched with the clutter, such
as Clutter Related Cost Hata, according to the on-site test.
Matched model setting:
Clutter-related
Propagation Model Matching.xlsx
Distribution of indoor and outdoor MRs:
1 Geographic distribution of outdoor MRs

2 Geographic distribution of indoor MRs
Indoor Weak Coverage Limit(dBm): This parameter has to be set to a value the same
as the threshold set by the U-Net plug-in. If the two values are not the same, use the U-
Net plug-in to reprocess data.
Advanced parameter configuration:

Grid traffic: The grid traffic should be set to a proper threshold according to the
network status during peak hours.
Building: The covered area and height of a building should be set a threshold.
Number of indoor grid MRs: The number of indoor grid MRs should be times the
average number of indoor grid MRs.
Number of indoor grid MRs for weak coverage: The number of indoor grid MRs for
weak coverage should be times the average number of indoor grid MRs for weak
coverage.
The following figure is for reference only.
4 Check out the planning result.
Planning site checking: The geographic planning result may involve non-weak-coverage
grids. This is probably caused by map inaccuracy, positioning deviation during
correlation of the U-Net with buildings. It is recommended that the building information
be deleted from the map during indoor site addition planning.
Planning scale checking: Related parameters have a significant impact on indoor site
planning by using the U-Net. Therefore, the number of added sites may be much greater
or less than the number of sites that actually need to be added. You can determine the
number according to construction scale of the operator or experience.
5 Perform the site survey.
Geographic checking for planning sites: U-Net geographic checking should be
performed for planning sites because of planning precision limit. Identify weak-coverage
grids around the location with sites to be added. The sites to be added can be deleted
according the number of weak-coverage grids. It is recommended that the sites covering
only one weak-coverage grid be deleted
GE checking: Draw a polygon area based on weak-coverage grids in and around
planning sites. Then, add the polygon area to Google Earth or other maps to correctly
identify the buildings with high confidence level matched with weak-coverage grids.
Site survey: Perform the site survey for the buildings with high confidence level.
Site survey result submitting: Submit the site survey result of identifying weak-coverage
buildings.
6 Develop a plan:
Develop a proper solution for different scenarios according to the site survey. Typical
scenarios are as follows:
Commercial buildings and market places: The LampSite indoor distributed base station
is recommended.
Areas with obviously tidal effect: The micro base station is recommended.
Areas with building of lower height: The macro base station is recommended.
7 Submit the plan.
Submit the plan according to the planning result, including the site position, equipment
model, deployment mode, and other matched solutions.
----End
4 U-Net Configuration Parameters
1 Site Planning Parameters

1 Parameters on the General Tab Page
The General tab page is used to set Computation area, Focus area, Scenario Definition, and
Data Source (including basic data and 6D data). Computation area and Frequency Band
settings define the scope of site planning. Focus area and Scenario Definition support using
different scenario parameters in different areas. The site planning is close to the actual
situation, and the planning result is reasonable. The basic data includes traffic map data, MR
data, and DT data. These data helps to provide more accurate site planning result. The 6D data
includes user complaint data and VIP user data.
Group Name: name of the site planning group. If a new group is successfully created, a new
node named after the group will be generated under ASP > LTE on the Operation tab page
of the U-Net.
Resolution(m): calculation precision of site planning. The default value is 50.
Scenario Definition: scenario definition. It can be used to set the site template
parameters, antenna parameters, ISD parameters, and other threshold values in different
scenarios. For details, see the following figures.
Set Prediction Parameters: coverage prediction parameter setting. It can be used to set
the parameters for coverage prediction during coverage prediction. For details, see see
the following figures.
Computation area: computation area, which is a polygon area drawn by the user on the
U-Net
Computation area scenario: scenario used in the computation area
Focus area: focus area, which includes other polygon areas in a computation area
Explanations of the Focus area table:
Polygon: name of a polygon area
Enable: whether to activate a polygon area
Scenario: scenario used for a polygon area
Frequency Band Settings: frequency band setting
Explanations of the Frequency Band Settings table:
Frequency Band: name of a frequency band
Enable: whether the frequency band is available
Number of Sites: number of sites corresponding to the frequency band.
Number of Bandwidth: total available bandwidth of the live network
Data Source: data sources used in site planning
Traffic map: whether to use the traffic map data. You can choose the generated traffic
map.
Measurement report data: whether to use the MR data. Select the MR data. Select an
MR group in the drop-down list box. The MR data is used to correct link loss data.
Inter-system MR Settings: whether to import inter-system MR data for the G/U/L
multimode base station
DT: whether to use the DT data. Select the traffic map. Select the DT group in the drop-
down list box. The DT data is used to correct link loss data.
User complaint: whether to use the user throughput
User complaint: whether to use the user complaint data. Select this option to use the
user complaint data. Click Browse to choose the user complaint data file, and click Get
Template to obtain the user complaint data template. The user complaint data is used for
6D value rating.
VIP User: whether to use the VIP user data. Select this option to use the VIP user data.
Click Browse to choose the VIP user data file, and click Get Template to obtain the VIP
user data template. The VIP user data is used for 6D value rating.
Value terminal: whether to use terminal data
Calculate now: whether to execute calculation immediately after you click OK
Parameters in the Definition Scenarios Dialog Box
Parameters in the Definition Scenarios dialog box:

Scenarios: scenario list, including Dense Urban, Urban, Suburban, and Rural. You
can specify different parameters for different scenarios.
New Site: parameters for new sites in specific scenarios
New Site Template: template for a new site. For details about template configurations,
see section 258"Setting the Template for New Sites."
Macro site template: template for a new macro site
Micro site template: template for a new micro site
Min ANT height(m): minimum antenna height at a site
Max ANT height(m): maximum antenna height at a site
Max M.Tilt: maximum mechanical tilt of an antenna
Max M.Tilt: maximum electrical tilt of an antenna
Macro site cost: costs of a macro site. The default value is 0.
Micro site cost: costs of a micro site. The default value is 0.
Minimum azimuth interval: minimum azimuth interval between transmitters of a new
site
Coverage angle of micro site: coverage angle of a micro site. The grids can be covered
by a micro site within a certain range.
RSRP threshold for micro site(dBm): RSRP threshold for a micro site. When the signal
level in a grid exceeds the threshold, no micro site can be added to the grid.
Candidate Sites: parameters for a candidate site
Macro site ISD(m): minimum distance between macro sites. When the area boundary is
smaller than the specified distance, the coverage-based site selection will be stopped.
Micro site ISD(m): minimum distance between micro sites. When other sites exist
within the specified distance around a grid, no micro site can be added to this grid.
Macro site poor coverage grid number threshold: grid number threshold for macro
site weak coverage. If the number of grids for macro site weak coverage is less than the
threshold, this site cannot be selected.
Micro site poor coverage grid number threshold: grid number threshold for micro site
weak coverage. If the number of grids for micro site weak coverage is less than the
threshold, this site cannot be selected.
New Planning Sites: parameters for a new site
Macro site ISD(m): minimum distance between macro sites. When the area boundary is
smaller than the specified distance, the coverage-based site selection will be stopped.
Micro site ISD(m): minimum distance between micro sites. When other sites exist
within the specified distance around a grid, no micro site can be added to this grid.
Macro site poor coverage grid number threshold: grid number threshold for macro
site weak coverage. If the number of grids for macro site weak coverage is less than the
threshold, this site cannot be added.
Micro site poor coverage grid number threshold: grid number threshold for micro site
weak coverage. If the number of grids for micro site weak coverage is less than the
threshold, this site cannot be added.
New Sector: parameters for a new sector in specific scenarios
Frequency Band: frequency band for a new sector
Antenna: antenna type for a new sector
Propagation Model: propagation model for a new sector
Max BandWidth per Sector: maximum bandwidth for a single sector
Parameters in the Prediction Parameters Dialog Box

Parameters in the Prediction Parameters dialog box (Use the default values unless otherwise
specified):
Minimum RSCP(dBm): minimum valid signal level in coverage prediction. Signals with a
level lower than the threshold are considered as invalid signals and therefore are filtered.
With shadow: whether to consider shadow fading. If this parameter is selected, you can set
Cell edge coverage probability(%). After Cell edge coverage probability(%) is set, the U-
Net automatically calculates the shadow fading margin and adds the shadow fading margin to
the signal propagation loss to minimize the impact of shadow fading on signal strength.
Cell edge coverage probability(%): cell edge coverage probability. When this parameter is
set to 50, the shadow fading margin is 0. A higher edge coverage rate indicates a larger
shadow fading margin and a smaller cell coverage area. The recommended value of this
parameter is 75.
Terminal: terminal selected by a user
Service: service selected by a user
Mobility: mobility of a user
Indoor coverage: whether to consider indoor coverage. When indoor coverage is considered,
a subscriber stays indoors at any position. The U-Net reserves the penetration loss of different
clutters for the signal propagation loss.
Interference Reception Threshold(dBm): interference reception threshold
Neighbour PDSCH Load(%): proportion of neighbor PDSCH load when SINR is
calculated. Enter the proportion in the input field.
2 Parameters on the Objective Tab Page

Resolve poor coverage: whether to resolve the weak coverage problem. If this parameter is
selected, the site selection or addition process is started to resolve the coverage problem.
Coverage Settings: different coverage target for different areas
Polygon: name of a polygon area
Area Type: type of a polygon area (Computation Area or Focus Area)
RSRP threshold(dBm): threshold for signal levels of downlink signals. If the signal
level is lower than the threshold, the coverage is considered to be weak.
Target Coverage(%): percentage of the area that reaches the coverage threshold to the
total area. The coverage requirements are met only when the actual coverage percentage
reaches the specified value of Target Coverage.
Resolve capacity overload: whether to resolve the capacity overload. If this parameter
is selected, the site selection or addition process is started to resolve the capacity
overload problem.
Expansion Settings: frequency expansion settings
Frequency Band: name of the band that requires expansion
Expansion: whether to perform capacity expansion on the frequency band
Resolve low service rate coverage: whether to solve the problem that the service rate
does not meet requirements. If this parameter is selected, the site selection or addition
process is started to resolve the problem that the service rate does not meet requirements.
Low service rate threshold(kbps): low service rate threshold. If the service rate is
lower than the threshold, the service rate does not meet requirements.
3 Parameters on the Strategy Tab Page
Max site number: maximum number of sites. This parameter restricts the number of
activated and new sites during site planning. If the number of activated and new sites exceeds
the threshold, the site planning is stopped.
Allow macro site addition: whether to add macro sites
Allow micro site addition: whether to add micro sites
Allow Site Selection: whether to select sites from candidate sites. If this parameter is
selected, the Candidate Sites list can be set, and the Import Site Status and Set Site Value
Items buttons become visible. You can click the Import Site Status button to import all sites
with locked and excluded status on the Candidate Sites table. You can click the Set Site
Value Items button to set the extra value items of a site.
Candidate Sites: all the existing LTE sites in the U-Net project. Candidate sites are
configured by users
Parameter Description Default Value Range

Value
Site Name Site name. This parameter is included in the None Unconfigurable
engineering parameters and is listed if the site
is in the planned polygon area.
Frequency Band Frequency bands of a site. If there are cells None Unconfigurable
with multiple frequency bands on a site, all
frequency band names are listed.
Original Status Original status of a site, indicating whether Active Active/Deactive
the existing site is activated. The coverage
data of deactivated sites are not calculated.
When Allow Site Selection is selected, this
parameter takes effect.
Planning Status Site planning status. This parameter can be set Candidate Candidate/Locked/Excluded
to Candidate, Locked, and Exclude.
Site Type Site type (Macro/Micro) None Unconfigurable
Site Cost Site cost (used to evaluate a site) None Selected in Set Site Value
Items
Site Priority Site priority (used to evaluate a site) None Selected in Set Site Value
Items
User Define 1 User-defined value item 1 (used to evaluate a None Selected in Set Site Value
site) Items
site) Items
site) Items
Comments Site comments None Unconfigurable
4 Parameters on the Advanced Tab Page
Customized weight: 6D weight setting. If this parameter is set to True, 6D planning

parameters are displayed. The weight indicates the percentage of scores on different value
assessment items. If the weight of a value assessment item is 0, this value assessment item is
not considered in the total score. If the weight is too large, the scores of other value
assessment items have little impact on the total score.
Revenue of PS per KByte: revenue per kbyte for PS services. The default value is 0,
indicating that the revenue is not considered in site evaluation.
Signal level gap of active set(dB): threshold for sharing traffic. In an area covered by
multiple cells, if the signal level difference between the cell and primary serving cell is within
this range, the cell shares traffic load. The default value is 4. This parameter can be used to
select the number of cells in traffic load sharing during capacity-based site addition. A larger
value indicates that more cells are involved in traffic load sharing, and a smaller value
indicates that fewer cells are involved in traffic load sharing.
Maximum split width(m): maximum search range during weak coverage grid aggregation
when coverage-based site addition is performed. This parameter affects the site addition
effect, and the default value is 1200. Each iteration gradually decreases with a step of 100 m
to locate the most suitable site position. If the distance is iterated to the minimum distance
between sites, a larger value indicates more iterations and longer duration, and a smaller value
indicates fewer iterations and shorter duration. In addition, the search distance also affects the
location for adding a site. If the site location is improper, you can modify this parameter to
generate better results.
Minimum split width(m): minimum search range during weak coverage grid aggregation
when coverage-based site addition is performed. The default value is 300.
You can click to calculate the radius of a cell in the planning area.
2 Parameters for Site Planning Results
1 Parameters on the Statistic Tab Page
This page is for the statistical data for entire network coverage and capacity target, number of
added sites, and number of selected sites. Click Export to export the site planning results to
an Excel file.
Duration: running time for site addition. This parameter is in the format of
XXhXXmXXs. Users can obtain the total running time for site planning.
Coverage Statistic: coverage statistics. Coverage statistics provide the coverage of
different areas based on coverage counters. Coverage indicators include the coverage
target, original coverage status, and coverage status after site selection.
Explanations of coverage indicators:
RSRP threshold(dBm): lowest signal level value. The grid whose level is lower than the
threshold will be considered as a weak-coverage grid.
Target coverage ratio(%): proportion of targeted coverage. You can set different
targeted coverage for different areas.
Total area(km)/Grid number: total area/number of grids in the computation area
(square kilometers/number)
Total area(km)/Grid number(with traffic): total area/number of grids in the
computation area with traffic (square kilometers/number)
Original coverage ratio(%): initial coverage percentage. When the candidate sites can
be selected, the initial coverage refers to coverage of existing sites whose original status
is Active before site planning. When the candidate sites cannot be selected, the initial
coverage refers to coverage of all existing sites before site planning.
Original poor coverage area(km)/Grid number: initial weak-coverage area/number
of grids (square kilometers/number)
Final coverage ratio(%): final coverage ratio. When the candidate sites can be selected,
final coverage refers to the coverage of all selected sites and new macro sites and micro
sites after site planning. When the candidate sites cannot be selected, final coverage
refers to the coverage of all existing sites and new macro sites and micro sites after site
planning.
Final poor coverage area(km)/Grid number: final weak-coverage area/number of
grids (square kilometers/number)
Improvement(%): coverage improvement ratio of each area after site planning
Improvement area(km)/Grid number: coverage improvement area/number of grids in
each area after site planning
Achieve coverage target: whether the coverage target is reached
Yes: reached
No: not reached
Capacity Statistic: capacity statistics. If the traffic map is selected in site planning, the
U-Net calculates traffic absorbed at each site and collects traffic absorption statistics on
the traffic map after site planning. Currently, LTE does not support capacity-based site
selection and sites addition, and therefore the improvement ratio is 0%.
Explanations of capacity counters:
Total PS traffic volume(KByte): PS traffic (kbyte) on the traffic map selected by users
Original PS traffic volume(KByte): PS traffic absorbed by existing sites before site
planning
Final PS traffic volume(KByte): PS traffic absorbed by all selected and new sites after
site planning
Original overload transceivers: number of original overloaded sectors
Final overload transceivers: number of final overloaded sectors
Original overload traffic need bandwidth(MHz): bandwidth for original overloaded
traffic
Final overload traffic need bandwidth(MHz): bandwidth for final overloaded traffic
PS traffic offload of new site(KByte): overloaded traffic for PS services of new sites
Site Number Statistic: statistics of the number of sites, including the number of macro
sites, micro sites, sectors, and carriers before and after site planning to help users better
understand the site planning results
Explanations of site number counters:
Original number: number of sites, sectors, and carriers in the area before site planning
Added macro number: number of selected and new macro sites, sectors, and carriers
during site planning
Added micro number: number of selected and new micro sites, sectors, and carriers
during site planning
Final number: number of sites, sectors, and carriers in each area after site planning
2 Parameters on the Site Tab Page
The Site tab page provides the coverage, traffic volume, and carrier configuration data
(including candidate sites and new sites) before and after site planning, and provides
frequency band, type, and the cause of each site included in the site planning. Site information
helps users analyze site planning result at the site level.
Click the row header on the Site table to quickly locate the site on the map, view the actual
geographic location and surrounding environment of the site, and analyze the relationship of
the site and the surrounding sites.
Right-click any area of the Site table to perform customized display on the table. Select the
column header on the Site table to freeze, hide, or unfreeze a column.
The table contains the statistical data for site addition and selection, including the following
fields:
Site Name: site name
Longitude: longitude of the site
Latitude: latitude of the site
Frequency Band: frequency band in all sectors at a site. If a sector in a site belongs to
multiple frequency bands, the names of multiple frequency bands are displayed as 2110 FDD
- 1.4 MHz or 2110 FDD - 10 MHz.
Scenario: scenarios adopted at the site
Original Status: original status of a site (Active/Deactive)
Final Status: final status of a site, including Excluded by user, Unselected, No change,
Locked by user, Expansion, Selected by coverage, Selected by capacity, Selected by
service rate, Added by coverage, Added by capacity, and Added by service rate
Site Type: type of a site, including Macro and Micro
Original Coverage Area(km): total coverage area of all sectors at a site before site planning
(square kilometers). If Allow site selection is selected but the original status of a site is
Deactive, the site does not have coverage area.
Final Coverage Area(km2): total coverage area of all sectors at a site after site planning
(square kilometers). If site selection is allowed, sites that are selected after site planning,
locked sites, and new sites are involved in the coverage analysis. If site selection is not
allowed, all the existing sites and new sites on the live network are involved in the coverage
analysis to calculate the coverage area.
Original Coverage Grid Number: total number of coverage grids of all sectors at a site before
site planning
Final Coverage Grid Number: total number of coverage grids of all sectors at a site after
site planning
Original Poor Coverage Grid Number: total number of weak-coverage grids of all sectors
at a site before site planning
Final Poor Coverage Grid Number: total number of weak-coverage grids of all sectors at a
site after site planning
Poor Coverage Ratio(%): percentage of weak coverage area after site planning. A higher
proportion of weak-coverage indicates worse coverage at the site. In this situation, optimize
the site parameters or add sites.
Original Imported PS Traffic(KByte): PS traffic absorbed by all sectors at the site before
site planning
Final PS Traffic Volume(KByte): PS traffic absorbed by all sectors at the site after site
planning
Total Revenue: total revenue at a site
Final Poor Coverage Grid Number Total number of weak-coverage grids at a site after site planning
Imported PS Traffic(KByte) Imported PS traffic volume from the traffic map of a site
Imported Bandwidth(MHz) Imported bandwidth from the traffic map of a site
Original PS Traffic Volume(KByte) PS traffic volume required by all sectors or cells of a site before site
planning
Original Traffic Overflow Ratio(%) Ratio of exceeded traffic volume to maximum carried traffic volume
before site planning
A larger value indicates that the capacity of the site needs to be
expanded.
Final Traffic PS Volume(KByte) PS traffic volume required by all sectors or cells of a site after site
planning
Final Traffic Overflow Ratio(%) Ratio of exceeded traffic volume to maximum carried traffic volume
after site planning
Original Bandwidth(MHz) Total bandwidth of all cells at a site before site planning
Final Required Bandwidth(MHz) Total bandwidth that is calculated based on the traffic volume required
by all cells at a site after site planning
Final Configured Bandwidth(MHz) Recommended bandwidth that is calculated based on the maximum
allowed bandwidth of each cell at a site and the bandwidth required by
each cell after site planning
Capacity Load Ratio(%) Capacity load of a site after site planning
Required Bandwidth(MHz) to Add Bandwidth that needs to be added for all cells at a site after site planning
Near Transmission Types Type of a transmission node nearest to the site
3 Parameters on the Transceiver Tab Page
The Transceiver tab page provides the coverage, traffic volume, carrier configuration data
before and after site planning, and frequency band and type of each transceiver, and the cause
of each of them included in the site planning. Transceiver information helps users analyze site
planning results at the sector level.
Click the row header on the Transceiver table to quickly locate the sector on the map, view
the actual geographic location and surrounding environment of the site, and analyze the
relationship of the transceiver and the surrounding transceivers.
Right-click any area on the Transceiver table to perform customized display on the table.
Select the column header on the Site table to freeze, hide, or unfreeze a column.
Some parameters are the same as the parameters on the Site tab page. You can refer to the
description of these parameters on the Site tab page.
Site Name: name of the site where the transceiver is located
Transceiver Name: name of the transceiver
Cell Name: name of the cell served by the transceiver. If a transceiver serves multiple cells,
the names of multiple cells are listed.
Frequency Band: frequency band of a cell served by the transceiver. If a transceiver serves
cells on different frequency bands, all the frequency bands are listed.
Scenario: scenario for a transmitter
Original Status: original status of the site served by the transceiver (Active/Deactive)
Original Coverage Area(km): total coverage area of all cells served by the transceiver
before site planning (square kilometers). If the transceiver is not activated before site
planning, the site does not have coverage area
Final Coverage Area(km): total coverage area of all cells served by the transceiver after site
planning (square kilometers). If site selection is allowed, transceivers that serve sites selected
after site planning, locked sites, and new sites are involved in the coverage analysis. If site
selection is not allowed, transceivers that serve all the existing sites and new sites on the live
network are involved in the coverage analysis to calculate the coverage area.
Original Coverage Grid Number: total number of coverage grids of all cells served by the
transceiver before site planning
Final Coverage Grid Number: total number of coverage grids of all cells served by the
transceiver after site planning
Original Poor Coverage Grid Number: total number of weak coverage grids of all cells
served by the transceiver before site planning
Final Poor Coverage Grid Number: total number of weak coverage grids of all cells served
by the transceiver after site planning
Original Imported PS Traffic(KByte): PS traffic absorbed by all cells served by the
transceiver before site planning
Final PS Traffic Volume(KByte): PS traffic absorbed by all cells served by the transceiver
after site planning
Antenna Type: antenna type
Azimuth: azimuth of the antenna
Height: antenna height
Mechanical Downtilt: mechanical downtilt of the antenna
Electrical Downtilt: electrical downtilt of the antenna
Original BandWidth: original bandwidth of a sector
Final Required BandWidth: bandwidth required for a sector
Final Required BandWidth: bandwidth configured for a sector
Final BandWidth to Add: final added bandwidth
Max BandWidth Allowed: maximum allowed bandwidth
4 Parameters on the Traffic Absorption Tab Page
This tab page displays cell traffic absorption relationships. The left pane lists all the activated
transceivers and the causes after site planning. The right pane lists the traffic volume absorbed
by sites and sectors served by the selected transceiver on the live network.
Related Cell: names of related cells. The cells whose traffic is absorbed to or from the cells
on the left are listed here.
Original Status: original status of a site (Active/Deactive)
Absorbed PS Traffic(KByte): absorbed PS traffic. This parameter specifies the traffic
absorbed to or from the selected cell.
Original Imported PS Traffic(KByte): original PS traffic data. This parameter specifies the
traffic absorbed to or from the selected cell before site planning.
5 Parameters on the Changes Tab Page
The Changes tab page provides the site name and scores of all selected sites and new sites
during site planning. Users can modify the score weight of each value assessment item by
clicking the Score Setting button, update the site score and sequence the sites, and determine
selected sites in the site planning results.
Right-click any area on the Changes table to perform customized display on the table. Select
the column header on the Site table to freeze, hide, or unfreeze a column.
Priority: priority. The priorities sequenced in ascending order. A smaller value of this
parameter indicates a higher priority.
Site Name: site name
Scenario: site scenario
Site Type: type of a site, including Macro and Micro
Cause: site selection causes. This parameter has the same meaning as the Final Status field
on the Site tab page.
Coverage Score: coverage score of a site, which is calculated based on the percentage of the
coverage area of the site to the maximum coverage area of all sites. A higher score indicates a
higher priority.
Traffic Score: traffic score of a site, which is calculated based on the percentage of the traffic
absorbed by the cell to the maximum traffic of all sites. The calculation method is the same as
that of Coverage Score. A higher score indicates a higher priority.
Revenue Score: revenue score of a site. Higher revenues indicate higher scores. The
calculation method is the same as that of Coverage Score. A higher score indicates a higher
priority.
Site Priority Score: site priority score. The calculation method is the same as that of
Coverage Score. A higher priority indicates a higher score. If this parameter is not selected,
the site priority score is not displayed.
Site Cost Score: cost score of a site. The calculation method is the same as that of Coverage
Score. A lower cost indicates a higher score. If this parameter is not selected, the site cost
score is not displayed.
Service Rate Score: service rate score of a site. The rate score is calculated based on the
service rate experienced by users in a simulation test. A higher score indicates that higher rate
and better user experience. If rate-based site addition is not selected, the rate score is not
displayed. Currently, the LTE does not support rate-based site addition.
Total Score: total score calculated based on the score and weight of each value assessment
item. A higher total score indicates a higher site priority. A site with a high priority is
recommended.
Number of Resolved Poor Coverage Grid: number of grids where weak coverage is
resolved at the site
Resolved Poor Coverage Ratio(%): proportion of the weak coverage that is solved at the
site
Traffic Volume of Resolved Poor Coverage Grid(Erlang): traffic volume in the resolved
weak coverage grids
Enable: whether the site is available. If this parameter is selected, the site status is submitted
to the engineering parameters of the U-Net when the site planning results are submitted. If
this parameter is not selected, the site status is not submitted.
Score Setting: weight setting for scores of different value assessment items. After the
setting is completed, the sites are sequenced again.
If you do not select the check box in the Use column, the factor is not considered in site score
calculation. After the weight of each value assessment item is set, click OK. The U-Net
calculates the total scores and priorities of all sites on the Changes tab page again.
6 Parameters on the Clutter Tab Page
The Clutter tab page lists statistical results based on clutter types. Users can view counters of
each clutter type throughout the calculation area under each polygon. Counters include clutter
area, weak-coverage ratio, total traffic, and absorbed traffic.
Explanations of each measurement counter under each polygon:
Coverage Area(km): coverage area of each clutter in the polygon
Poor Coverage Ratio(%): weak coverage ratio of each clutter in the polygon
Absorbed PS Traffic(KByte): PS traffic that is absorbed of each clutter in the polygon (unit:
kbyte)
3 Parameters for Layers

1 Quality Analysis
Original RSRP: original RSRP level coverage layer on the entire network
Final RSRP: final RSRP level coverage layer on the entire network
RSRP Gain: RSRP gain on the entire network
Original SINR: original SINR interference layer on the entire network
Final SINR: final SINR interference layer on the entire network
SINR Gain: SINR interference layer on the entire network
Original Service Rate: original service rate layer on the entire network
Final Service Rate: final service rate layer on the entire network
Service Rate Variation: service rate gain layer on the entire network
2 Coverage Analysis
Original Best Server: distribution of primary serving cells on the entire network before site
planning
Final Best Server: distribution of primary serving cells on the entire network after site
planning
Best Server Variation: distribution of primary serving cells on the entire network before and
after site planning
3 Weight Analysis
Terminal Count: terminal count layer on the entire network
Value Service Count: value service count on the entire network
VIP User Count: VIP user count layer on the entire network
Complaint Count: User complaint count layer on the entire network
Service Revenue: service revenue layer on the entire network
Total Score: total score layer on the entire network
4 Parameters for Data Preprocessing Result

(U-Net Plug-in)
1 Coverage Analysis
1 Planning LTE based on UMTS
RNCID ID of the RNC serving a cell
CI ID of a cell
Longitude Grid longitude
Latitude Grid Latitude
Number of periodic MRs generated by CS services of the primary serving cell on a
ServeCellCSMRCount
grid
Number of periodic MRs generated by PS services of the primary serving cell on a
ServeCellPSMRCount
grid
Total number of MRs (including periodical MRs and incident MRs) of the primary
ServeCellMRCount
serving cell on a grid (regardless of service type)
CellMRCount Number of times of a cell on a grid (regardless of cell type) being measured
CellRSCP Average RSCP of a cell on a grid (regardless of service type and cell type)
CellEcIo Average Ec/Io of a cell on a grid (regardless of service type and cell type)
Total number of periodical MRs generated by indoor PS services of the primary
CellIndoorPSMRCount
serving cell
Total number of periodical MRs generated by indoor CS services of the primary
CellIndoorCSMRCount
serving cell
Total number of periodical MRs generated by outdoor PS services of the primary
CellOutdoorPSMRCount
serving cell
CellOutdoorCSMRCoun Total number of periodical MRs generated by outdoor CS services of the primary
t serving cell
Average confidence level of indoor MRs of a cell as a primary serving cell on a
CellIndoorCredit
grid
RSCP of indoor MRs (including periodical MRs and incident MRs) of a cell as a
CellIndoorRSCP
primary serving cell on a grid
RSCP of outdoor MRs (including periodical MRs and incident MRs) of a cell as a
CellOutdoorRSCP
primary serving cell on a grid
2 Planning LTE based on LTE

TAC Tracing area code of a cell
ID of a cell. A cell can be uniquely identified by TAC and CI. CI is
CI
EnodeBID+CELLID.
Longitude Grid longitude
Latitude Grid Latitude
ServeCellMRCount Number of MRs of a cell as a serving primary cell on the current grid
Number of times of a cell being measured as a primary serving cell and a
CellMRCount
neighboring cell on the current grid
Average RSRP of a cell as a primary serving cell and a neighboring cell on the
CellRSRP
current grid
ServingCellRSRP Average RSRP of a cell as the primary cell on the current grid
Average RSRQ of a cell as a primary serving cell and a neighboring cell on the
CellRSRQ
current grid
Number of indoor MRs generated by PS services of the same primary cell on the
CellIndoorPSMRCount
same grid. If the number is 0, no value is specified for this parameter.
ServingCellRSRQ Average RSRQ of a cell as the primary cell on the current grid
CellOutdoorPSMRCoun Number of outdoor MRs generated by PS services of the same primary cell on the
t same grid. If the number is 0, no value is specified for this parameter.
CellIndoorCredit Average confidence level of indoor MRs of the same primary cell on the same grid.
If the confidence level is 0, no value is specified for this parameter.
Average RSRP of indoor MRs of the same primary cell on the same grid. If the
CellIndoorRSRP
PSRP is 0, no value is specified for this parameter.
Average RSRP of outdoor MRs of the same primary cell on the same grid. If the
CellOutdoorRSRP
PSRP is 0, no value is specified for this parameter.
2 Capacity Analysis
1 Planning LTE based on LTE
Cell Name Name of a cell
TAC Tracing area code of a cell
ID of a cell. A cell can be uniquely identified by TAC and CI. CI is
CI
EnodeBID+CELLID.
PS Traffic(KByte) DL traffic (kbyte)
RB Utilization DL PRB usage of a cell
Total
Total bandwidth
Bandwidth(MHz)
User Count Number of UEs
Active User Number Number of online UEs
Active User Number
Growth factor of on line UEs
Growth Factor
Total RB Used Average number of used RBs of a cell
Value Service Value service
5 Delivery Procedures
1 Analyzing Operators' Requirements and

Guiding Operators
Coverage planning and capacity planning are new planning schemes developed by Huawei,
featuring high efficiency, accuracy, and convenience. Multiple successful communications
with operators are required to make operators accept and acknowledge our planning schemes
and control the requirements of operators, thereby controlling delivery risks.
Generally, coverage planning and capacity planning are performed based on each grid on the
whole network. The maximum value of the two planning schemes lies in directly improving
user experience of operators' networks. Before communicating with operators, we have to
understand the problems and demands of the operators, to prepare specific communication
documents. In addition, we have to be familiar with the style of operators, to provide
emergency solutions for operators during communication. Communication range and
commitments must be controlled strictly to avoid increasing delivery costs and risks caused
by new requirements of operators.
Therefore, we have to strictly control the requirements of operators and guide operators
according to our communication documents and procedures prepared previously. The aim is
to make operators acknowledge our planning schemes.
2 Starting MR Data Collection Tasks and

Performing MR Data Collection
MR data must be used for coverage planning and capacity planning. Before collecting MR
data, you have to start the collection task.
After the schemes are acknowledged by operators, identify operation actions and steps with
operators to meet network security requirements. Then, start the MR data collection task to
obtain MR data. For details, see the attachment in section 14"Data Collection Methods."
3 Preparing Data as Required
According to section 23"Data Collection," engineering parameters, propagation models,
maps, and antenna files must be prepared for running the project. The accuracy of these data
has a direct impact on final planning result.
All engineering parameters used must be checked at least four times to avoid invalid
parameters, wrong parameters, and incorrect parameter values.
A rectified propagation model acknowledged by operators and a map with precision of 5 m
are recommended. The antenna file must be correct.
4 Holding a Project Kick-Off Meeting and

Developing a Delivery Plan to Identify
Potential Delivery Risks
Hold a project analysis meeting with TMO and regional departments and develop a delivery
plan to identify potential risks. The differences and similarities between coverage/capacity
planning and RF planning shall be considered.
A project kick-off meeting must be convoked for frontline engineers to prepare resources,
organize works, and encourage frontline engineers. Then, execute the project according to the
established plan.
5 Generating Coverage and Capacity Planning

Results
Perform coverage and capacity planning after preparing data. For details of planning
procedures, see sections 24"Data Preprocessing Through the U-Net Plug-in" and 25"Site
Planning Through the U-Net." Parameter settings have an impact on planning results. You
have to understand the meaning of parameters involved in this document before performing
coverage and capacity planning.
Save data in time during operation to avoid operation failures or crash faults.
When planning in batches, ensure that all polygon areas are adjacent seamlessly, as shown in
the following figure.
Planning area: planning site area
Activated area: planning site area and the area of its adjacent sites.
Ensure that all polygon areas are adjacent seamlessly to avoid some areas being missed from the
planning result.
6 Checking and Rectifying Planning Result

Manually
Pay more attention to whether the result is reasonable and reaches the expectations. For
details, see chapter 3"FDD-LTE Indoor Intensive Coverage Site Planning."
If the result is reasonable, rectify the planning result manually. Engineers need to check the
sites to be added one by one to check whether the value is considerable, the position is
reasonable, and the functions are fully used. A site with small value or close to its neighboring
sites should be deleted or adjusted.
After manual rectification, you can output the draft plan.
7 Reviewing the Planning Result with Regional

Departments and HO and Communicating with
Operators to Acquire the Acknowledgement of
Operators
Hold a project analysis meeting to review the planning result with regional departments and
HO. Develop the second draft plan based on the modified result. Then, provide the second
draft plan for operators and communicate with operators until the plan is finalized.
8 Developing a Site Survey Plan and Executing
the Plan, and Modifying the Planning Result
Based on the Site Survey Result
Prepare a site survey plan based on the final plan and start the site survey. The principles and
requirements of the site survey are similar to the survey procedures of normal project delivery.
The operators' demands and special requirements of the project must be fulfilled. Then,
generate a site survey report.
9 Developing the Delivery Plan and

Acceptance Solution with Operators After the
Final Planning Result and Site Survey Report
Are Approved by Operators
Develop the delivery plan and acceptance solution after the site survey report is approved by
operators. It is recommended that the acceptance solution is not performed for coverage and
capacity planning independently. The product and service orders of the project should be
delivered with other products and services to perform traditional DT and or traffic acceptance.
If an operator requires performing acceptance for coverage planning and capacity planning
independently. We recommend the following acceptance method.
10 Coverage and Capacity Optimization

Methods
Network optimization is recommended during project delivering. The main optimization
methods are as follows:
1 DT RF optimization
This is the most traditional and effective optimization method, solving RF problems by
adjust antenna azimuth and downtilt after identifying weak-coverage areas with severe
interference.
2 Project quality control
Training and management for subcontractors must be strictly performed at the beginning
of the project. Ensure the network quality by developing specific project quality control
solutions and spot check methods. The spot check and project quality rectification must
be performed to control network performance.
3 Parameter check
Most network performance problems are caused by improper configurations. The
OMStar must be used to check parameters to eliminate all improper configurations.
4 Parameter optimization
Determine a parameter optimization action with the help of R&D engineers according to
parameter manuals and X solutions. This action must be done with parameter check to
ensure accuracy of parameter configurations. Non-personalized parameters are the same
on the whole network. Personalized parameters should be adjusted and recorded
properly.
5 Feature activation
Features such as ICIC can be activated to improve network performance. For details, see
related feature guides.
6 Neighboring cell optimization
Use the SmartRNO to check neighboring cells for correct and reasonable neighboring
cell configurations.
7 Traffic monitoring
Locate and analyze poor KPIs and solve the problems to ensure that all KPIs are normal
and steady.
8 Find out and solve problems of the network to improve network performance.
9 Eliminate inter-system interference based on interference-related counters.
6 FAQ
1 How Do I Perform Parameter Settings in the

Engineering Parameter List or Cell List in
Batches?
Take modifying Frequency Band as an example. Choose 2110 FDD - 3 MHz, click the table
header, and press CTRL+D. The frequency band is changed to 2110 FDD - 3 MHz in
batches.
2 How Do I Cope with the Calculation Failure

When Multiple Frequency Files on an RNC Are
Selected for Geographic Display with a
Message Indicating that the Coverage Is Too
Large?
A: When you use the U-Net to perform traffic geographic analysis, a matrix file of all MRs
needs to be generated. Therefore, the MR coverage area cannot be too large.
Causes are as follows:
The MR distribution range is too large because the frequency policies are different in
each frequency file.
The RNC coverage range is too large. For example, areas A and B are covered, but area
C that lies between A and B is not covered.
Solutions:
Do not import multiple frequency files at a time. Generate a traffic map for each
frequency file at a time, and combine all traffic maps together. If the combined traffic
map is too large, the calculation fails.
When the New Query Viewer dialog box is displayed, the MR data can be queried or
filtered based on CI, latitude, or longitude. For configuration details, see the following
figure.
3 How Do I Cope with the Calculation Failure
When an RNC Area Is Selected for LTE ASP with
a Message Indicating that the Coverage Range
Is Too Large?
A: It is recommended that you take the following operations:
1 Restart the PC to release all memories. LTE ASP requires a large memory.
2 Change the value of Main Calculation Radius(m) in the cell parameter table from 4000
to 2000.
3 If the coverage area of the RNC is too large, it is recommended that you divide a large
area into multiple small areas to generate multiple polygon areas.
4 If the RNC coverage area is too scattered, it is recommended that you distribute each
small area to generate a polygon area and then combine all scattered polygon areas to
generate a union polygon area.
4 How Do I Improve the Operation Efficiency of
the U-Net by Deactivating Sites Outside the
Polygon Area?
If the polygon area is too large, the U-Net reports memory insufficiency and operation failure.
In this case, the memory is precious. Sites outside the polygon area also consume
considerable memory during simulation tests. By deactivating these sites, the memory
consumption can be reduced. Perform the following operations to deactivate the sites outside
the polygon area.
1 Specify a polygon area.
2 Group transceivers by the polygon area.

Right-click Transceiver and choose Group By > Polygon from the shortcut menu.
The result is shown in the following figure.

3 Deactivate sites outside the polygon area.
Right-click Polygon:Other Field and choose Deactivate Transceivers from the shortcut
menu.
The result is shown in the following figure. The areas in gray are the deactivated sites.
----End
7 Appendixes
1 UMTS MR Collection Guide (V1.4)

http://3ms.huawei.com/hi/index.php?
app=group&mod=File&act=showList&gid=1008601&cid=1056979
2 WINS V100R006C00 LTE FDD Inventory

Solution Data Collection Guide
http://3ms.huawei.com/hi/group/2032023/blog_1637571.html?
mapId=2361247&for_statistic_from=all_group_blog
3 U-Net V300R010C00SPC100 Release Notes

This document is released with U-Net. The U-Net version path is as follows:
http://support.huawei.com/carrier/navi#col=software&detailId=PBI1-21606766&path=PBI1-
7851894/PBI1-8132365/PBI1-8132371/PBI1-21395144/PBI1-13953
4 Difference between MR-Positioning-based

Capacity Planning Scheme and Rate Planning
Scheme
Both schemes are based on MR positioning. However, the targets and implementation
methods of the two schemes are different for different requirements of operators and different
scenarios.
Therefore, there is significant difference between the results of the two schemes even though
the two schemes are performed on the same network. If you have no idea which scheme you
should choose, contact Huawei technique support engineers or the author of this document.
Difference in target
Capacity planning is designed to solve insufficient power and RBs through carrier
expansion, sector division, macro site addition, and micro site addition.
Rate planning is designed to achieve a certain download rate through carrier
expansion, sector division, macro site addition, and micro site addition.
Difference in implementation method
Capacity planning is performed based on power evaluation and RB usage.
Rate planning is performed based on mapping between the download rate and the
CQI, power, code resources, RBs, number of UEs simultaneously performing data
transmission. That is, check whether the root cause of low rate is weak signal
strength, poor signal quality, large number of UEs simultaneously performing data
transmission, or insufficient power, and then perform the planning based on
difference between the actual rate and target rate. MRs of PS services are selected to
perform MR positioning and rasterizing for the UTRAN network.
Difference in application scenario
Capacity planning is a common planning method comparing with rate planning. The
common planning is oriented based on coverage-related indicators and performance
KPIs.
Rate planning is an innovated panning for MBB data services to achieve a higher
rate, such as 1 Mbit/s for the UTRAN network and 3 to 10 Mbit/s for the E-UTRAN
network (5 Mbit/s is commonly used).
Generally, MR-positioning-based coverage planning and capacity planning are not
used with rate planning at the same time. That is, you can use MR-positioning-based
coverage planning and capacity planning or rate planning.
5 "White Line" on the Map

1 Phenomenon
When importing the MR data analyzed by the U-Net plug-in into the U-Net, a "white line"
appears on the MR layer displayed by the GIS, as shown in the following picture. The number
of the white spots constituting the "white line" is based on the data and site position.
2 Causes
The versions earlier than WINS iDart V100R007C00SPC200T do not support the projection
system. The U-Net plug-in also does not support the projection system (the version of the
iDart CBB is 100T). The longitude and latitude of MR data provided by the versions earlier
than 200T are generated by the spheroidal coordinate system. The U-Net uses plane
coordinate system. The longitude and latitude are converted to geodetic coordinates when the
result provided by the U-Net plug-in is imported into the U-Net. Grid deviation occurs when
converting spheroidal coordinates to geodetic coordinates. That is, the size of a grid (50 m)
will be changed after coordinate conversion, thereby leading to a "white line" on the MR layer
displayed by the GIS.
3 Solution
The WINS iDart V100R007C00SPC200T, instead of the U-Net plug-in, is used to analyze
data. The WINS iDart V100R007C00SPC200T only supports the UTM coordinate system.
When the U-Net also uses the UTM coordinate system, no "white line" appears. If you have
any questions on operations, contact U-Net support engineer Xiang Jie (employee ID:
00223444) or Liao Haiqiao (employee ID: 00223434).
4 Problem Recurrence
This problem reoccurs on the Jinan site. The "white line" appears after the processing result of
the U-Net plug-in is imported into the U-Net. No "white line" appears after the processing
result of the WINS iDart V100R007C00SPC200T is imported into the U-Net. The parameter
imported into the U-Net is engineering parameter A and imported into the U-Net plug-in is
engineering parameter B, not leading to "white line" recurrence. The "white line" reoccurs
when the parameter imported into the U-Net is engineering parameter A.

RF Network Planning and Optimization Service V100R006 LTE ASP Coverage and Capacity Site Planning Technical Guide (FDD)

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RF Network Planning and Optimization Service V100R006 LTE ASP Coverage and Capacity Site Planning Technical Guide (FDD)

Загружено:

Авторское право:

Доступные форматы

Product Name Security Level

RF Network Planning and

Prepared By Hu Wei (employee ID: 00135858), Zhang Date

2017-03-21 Huawei confidential. No spreading without permission. Page 3 of 170

3 FDD-LTE Indoor Intensive Coverage Site Planning........................124

4 U-Net Configuration Parameters.................................................137

Abbreviations Full Spelling

A-GPS Assisted Global Positioning System

Tool Version Function Applying for Remarks

U-Net plug- http://support.huawei. Network For any question, contact Yang

1 U-Net Plug-in Specifications

11 Projects must be saved manually in real time.

3 Model Answers for Specifications

1 Design roadmap of LTE ASP

2 Factors Affecting LTE ASP Accuracy

3 Planning of Mandatory Sites

4 Site Selection Process

5 Coverage-based Site Planning

The process is as follows:

6 Capacity-based Site Planning

1 Process of capacity-based site planning

The process is as follows:

Identify areas for adding micro sites.

Collect MR/DT data from the live UMTS

Predict LTE coverage based on the MR/DT

Plan LTE sites.

6 Principles for Distinguishing Between Indoor

1 Introduction to LTE ASP Application

The process is as follows:

Data collection 1 week

Common Electronic Clutter

LTE site RNC RNC Configuration

(Optional) 2 days Event-based

Traffic 1 week Traffic

Traffic 1 week Traffic

2 Network Engineering Parameters

Precautions for engineering parameters are as follows:

3 (Optional) Antenna Files

4 (Optional) Electronic Maps

5 (Optional) Propagation Models

2 ValuedTerminal (applicable to LTE site planning based on existing UMTS networks)

5 (Optional) Site Cost

4 Data Preprocessing Through the U-Net Plug-

Live-network RNC MML configuration files corresponding to the MRs to be parsed

2 LTE Site Planning based on Existing LTE Networks

LTE FDD_MR Data

LTE FDD_6D Data

Live-network RNC MML configuration files corresponding to the 6D data to be parsed

2 Set basic task parameters.

UM TS_6D Data UM TS_6D Data

2 LTE Site Planning based on Existing LTE Networks

2 Parsing Capacity Data

2 Set basic task parameters.

6D Data 6D Data 6D Data

5 Site Planning Through the U-Net

For details, see GENEX U-Net User Guide.

Parameter Description Value

4 (Optional) Setting a Propagation Model

The following table describes propagation model parameters.

Lu Lu = K1 + K2 x lg(f) K3 x lg(Hb) + [K4 K5 x lg(Hb)] x lg(d)

5 (Optional) Importing and Setting Antenna

7 Importing Engineering Parameters

8 Setting the Template for New Sites

9 Setting an Analysis Area