Coordinated Coverage and Capacity Optimization Guide: Eden-NET 18

Eden-NET 18
Coordinated Coverage and Capacity

Optimization Guide
DN09273754
Issue: 1-0
Coordinated Coverage and Capacity Optimization Disclaimer
guide
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as
specified herein.
This document is intended for use by Nokia' customers (“You”) only, and it may not be used except for the purposes defined
in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document
may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of
Nokia. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been
terminated, You may not use this document in any manner and You are obliged to return it to Nokia and destroy or delete any
copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full
responsibility when using it. Nokia welcome Your comments as part of the process of continuous development and
improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the
suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available”
basis in this document, and Nokia reserves the right to change any such information and statements without notice. Nokia
has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and
omissions, and Nokia will correct errors that You identify in this document. But, Nokia' total liability for any errors in the
document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of the software in the
Product will be uninterrupted or error-free.
N O WA RRAN T Y OF AN Y KI ND , EI T HER E X P R E S S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D
TO A NY WAR RA NT Y OF AVAI LABI LIT Y, AC CU RA C Y, R E L I A B I L I T Y, T I T L E , N O N - I N F R I N G E M E N T,
M ER C HANTA BI LI T Y OR F IT N ESS F OR A PA RT IC UL A R P U R P O S E , I S M A D E I N R E L AT I O N TO T H E
C ONT ENT O F TH IS DO CU M EN T. IN N O E V E N T W I L L N O K I A B E L I A B L E F O R A N Y D A M A G E S ,
I NC L UDI NG BUT NOT LI M IT ED TO SPEC IA L , D IR E C T, I N D I R E C T, I N C I D E N TA L O R C O N S E Q U E N T I A L
O R ANY LO S SES , SU CH AS BU T N OT LIM I T E D TO L O S S O F P R O F I T, R E V E N U E , B U S I N E S S
I NT ER RUPTI O N, BUS INESS OPPO RT U NI T Y OR D ATA T H AT M AY A R I S E F R O M T H E U S E O F T H I S
D OCU MENT OR TH E INF O RM AT IO N IN I T, E V E N I N T H E C A S E O F E R R O R S I N O R O M I S S I O N S
F R OM T HI S DO CUM EN T O R IT S CO NT EN T.
This document is Nokia’ proprietary and confidential information, which may not be distributed or disclosed to any third
parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks
of their respective owners, and they are mentioned for identification purposes only.
Copyright © 2018 Nokia. All rights reserved.
Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having
carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part
of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like
to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please
recycle product packaging and follow the recommendations for power use and proper disposal of our products and their
components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please
contact us at Nokia for any additional information.
Coordinated Coverage and Capacity Optimization guide Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 5
2 Overview of C-CCO......................................................................................................................................... 6
2.1 Dependencies............................................................................................................................................9
2.2 Interactions................................................................................................................................................ 9
3 C-CCO functional description and guidelines............................................................................................10

3.1 Operational modes of C-CCO.................................................................................................................10
3.1.1 Closed loop mode...........................................................................................................................10
3.1.2 Open loop mode............................................................................................................................. 10
3.2 Running C-CCO...................................................................................................................................... 11
3.3 Module inputs of C-CCO........................................................................................................................ 12
3.4 Verification and rollback.......................................................................................................................... 12
4 C-CCO algorithm............................................................................................................................................16
4.1 3G standard coverage root algorithm..................................................................................................... 16
4.2 3G propagation delay based coverage root algorithm........................................................................... 17
4.3 3G capacity root algorithm......................................................................................................................17
4.4 LTE standard coverage root algorithm................................................................................................... 18
4.5 LTE capacity root algorithm.................................................................................................................... 19
4.6 LTE timing advance based coverage root algorithm.............................................................................. 19
5 Configuring and executing C-CCO..............................................................................................................20

5.1 C-CCO prerequisites............................................................................................................................... 20
5.1.1 License details................................................................................................................................ 20
5.1.2 CM data and PM data....................................................................................................................20
5.2 Accessing C-CCO................................................................................................................................... 21
5.3 Configuring targets for C-CCO............................................................................................................... 21
5.4 Configuring parameters for C-CCO........................................................................................................ 22
5.5 Selecting the configuration file for C-CCO............................................................................................. 22
5.6 Selecting execution type for C-CCO.......................................................................................................23
5.7 Confirming execution for C-CCO............................................................................................................ 23
6 C-CCO configuration parameters................................................................................................................ 25

6.1 C-CCO GUI parameters..........................................................................................................................25
6.2 C-CCO INI parameters........................................................................................................................... 28
6.2.1 Example of C-CCO configuration file............................................................................................. 37
6.3 Configuring INI parameters.....................................................................................................................38
6.4 CCO AVR configuration parameters....................................................................................................... 40
7 Viewing C-CCO reports.................................................................................................................................44

7.1 C-CCO reports........................................................................................................................................ 45
3
Coordinated Coverage and Capacity Optimization guide Table of Contents
8 Monitoring C-CCO......................................................................................................................................... 49
4
Coordinated Coverage and Capacity Optimization guide Summary of changes
1 Summary of changes
Release Summary
Eden-NET 18 No changes.
Eden-NET 17 SP1 FP1 New document.
Table 1: Summary of changes
DN09273754 1-0 © 2018 Nokia 5

Coordinated Coverage and Capacity Optimization guide Overview of C-CCO
2 Overview of C-CCO
The Eden-NET Coordinated Coverage and Capacity Optimization (C-CCO) module jointly and simulta-
neously optimizes WCDMA, LTE, and Coverage and Capacity all in one module. Antenna sharing be-
tween WCDMA and LTE is supported for the same vendor.
Through the introduction of new capacity and coverage algorithms and weighting functions, tilt scores
are developed for all cells in the target list (WCDMA and LTE). Then, prioritized tilt changes (WCDMA,
LTE) or power pilot changes (WCDMA) are recommended by the module based on the scoring.
There are a total of 6 capacity and coverage algorithms that can be enabled. They are:
• Standard coverage algorithm for WCDMA

• Standard coverage algorithm for LTE
• Propagation Delay coverage algorithm for WCDMA
• Timing Advance coverage algorithm for LTE
• Capacity algorithm for WCDMA
• Capacity algorithm for LTE
Figure 1: Cellular network
Coordinated CCO is network aware, hence the module makes estimates on the impact to the sur-
rounding neighbor cells due to a proposed tilt on the target cell and includes the scoring before recom-
mending changes. For example, in the Cellular network figure, the target cell is 2 and the surrounding
cells are 1, 3, 4, and 5.
DN09273754 1-0 © 2018 Nokia 6

The C-CCO module configuration includes dozens of parameters to tune the module and network. C-
CCO continually assesses the impact of network changes based on network KPIs. Following the ini-
tial coarse step changes, the module will enter two fine tuning stages with smaller tilt and CPICH step
sizes.
The C-CCO flowchart highlights the coordination and the fine-tuning aspects of the module.
The KPI driven coverage and capacity algorithms are fed into the cost aggregator which normalizes,
weighs, and adds scores together for every cell in the target list (UMTS and LTE). In cases of antenna
sharing, scores are created for combined cells.
Once the individual target cells (and combined cells) are prioritized, the module proceeds through the
list from the largest magnitude scores to the smallest scores that exceed the threshold. Before a cell is
proposed for a tilt recommendation, a scoring check is done to ensure that the module will provide tilt
recommendations.
The KPIs used in the continuous scoring are related to the root algorithm related to coverage and ca-
pacity. These same KPIs are used in the fine tuning as well as the coarse stages. This process is de-
scribed in more detail in the Epoch based tuning figure:
DN09273754 1-0 © 2018 Nokia 7

In the epoch based large step and fine-tuning step process, hundreds of cells can be optimized. Thus,
a single C-CCO instance can run on a large area of the network over a long period of time. At the end
of an epoch, the C-CCO module instance begins a new epoch and either moves down the list to ex-
clude cells already optimized from the prior epoch or even re-optimize all cells from the start once
again.
The fine-tuning process within an epoch will engage smaller tilt and CPICH step sizes to converge to
a better tilt setting (or CPICH setting). If the large step size (or coarse step as its parameter is called)
is 1 degree of tilt, then the fine tuning 1 step sizes is 0.5 degrees and fine tuning 2 step size is 0.5 de-
grees. Based on the initial set of coverage and capacity KPIs and scoring, it is determined that Cell A
should be downtilted 1 degree. After new KPI evaluation, it is determined that coverage and capac-
ity KPIs are better (score is lower) but not yet <= 0. Then a further 0.5 degrees of downtilt would be
applied. One more round of new KPI coverage and capacity scoring will be assessed. If the scores
are better (lower), then the last round of 0.5 degrees of downtilt is applied. That is why, for that epoch,
a total of 2 degrees of downtilt is applied. Similarly, depending on scoring in the different phases, 0,
0.5, 1.0, 1.5, or 2.0 degrees of downtilt or uptilt could be applied, with the default tilt settings described
above.
Automatic Verification and Rollback Capability
KPIs can be selected from a variety of areas such as:
DN09273754 1-0 © 2018 Nokia 8

• LTE accessibility, retainability, traffic, IRAT volumes, physical resource block utilization and chan-
nel quality indicator distributions
• WCDMA accessibility, retainability, traffic, IRAT leakage and handover volumes
• GSM accessibility, retainability, traffic, and handover
If the module detects that KPIs are degraded following a parameter change, then the AVR (Automatic
Verification and Rollback) functionality will roll back the parameters to their previous settings. By con-
trolling the coverage footprint, or area where the cell is providing coverage at a level ensuring high
quality of service, the C-CCO module reduces interference, manages capacity and improves noise lim-
ited coverage areas.
Output reports detailing network changes taken by C-CCO can be automatically sent via e-mail to the
relevant radio frequency and performance engineers.
Table 2: C-CCO supported vendor and technology lists the module supported vendors and technolo-
gies:
Technology Supported Vendor
WCDMA, LTE Nokia
Ericsson
Table 2: C-CCO supported vendor and technology
2.1 Dependencies
The C-CCO module is a separate module from the existing WCDMA and LTE CCO modules. C-CCO
is an advanced module and a significant evolution of the previous modules. Hence, there are no de-
pendencies on the existing modules.
2.2 Interactions
Different source data can be used by the C-CCO optimization algorithm.
If an input option is selected, the corresponding source data must be available to Eden-NET. Propaga-
tion Delay and Timing Advance Counters can be used as inputs to the module.
It is recommended not to run C-CCO module concurrently with WCDMA CCO or LTE CCO modules
over the same target area.
DN09273754 1-0 © 2018 Nokia 9

Coordinated Coverage and Capacity Optimization guide C-CCO functional description and guidelines
3 C-CCO functional description and guidelines
3.1 Operational modes of C-CCO

The Eden-NET C-CCO module works in two different modes:
• Closed loop mode

• Open loop mode
Note: The module should run in closed loop only during weekdays to ensure that all scoring
is done with busy-hour data.
3.1.1 Closed loop mode

When the C-CCO module is running in closed loop mode, it receives a trigger from the Eden-NET
framework during every measurement period, typically, 15 minutes. After running the same algorithm
as in the open loop mode, changes are pushed to the live network. Once the push is complete, if pre-
vious changes impacted the network negatively beyond configurable KPI thresholds, the changes are
rolled back and the related source cells are blacklisted via AVR. A separate KPI evaluation is done in
the fine-tuning stage that evaluates capacity and coverage cost function scoring. Based on these fine-
tuning stages, further tilt modifications are made independently of any AVR evaluations. To ensure that
the module is making closed-loop decisions using the most up-to-date information available, the Eden-
NET framework updates the cached configuration information if it has been changed, or if the data has
not been read from the OSS.
Note:
• Remote Electrical Tilt is mandatory when C-CCO is used in the closed loop mode if LTE
recommendations and modifications are to be made. For WCDMA CCO, if enabled,
either changes are made to remote electrical tilt settings, or CPICH can be adjusted.
• Blacklisted cells are skipped.
3.1.2 Open loop mode

When the C-CCO module is running in open loop mode, it runs by logging actions in the output file
but does not push any tilt change to the network. The Coordinated CCO module output consists of a
list of scores for all cells (WCDMA, LTE) and recommendations to improve the network in the coarse
mode. While in open loop, the module does not perform any scoring for the fine-tuning phases or fu-
ture epochs.
The module retrieves configuration and performance data for the selected cells, which is fetched from
the Eden-NET Configuration Management Cache. It does not force any reading from the OSS for da-
ta in the cache that has been modified, or has expired. The open loop mode, therefore, places no ad-
DN09273754 1-0 © 2018 Nokia 10

ditional load on the OSS and its interfaces. This also means that the data which the module processes
in this mode may not be present in the OSS at that time.
However, depending on the activity on the OSS, if the Coordinated CCO module is the only process
making changes to related cell parameters, the cache is usually kept in synchronization with the net-
work configuration as stored in the OSS. The cache is periodically updated by the Eden-NET frame-
work. Open loop mode checks the previous change impacts (in case the module was previously run in
closed loop mode) and calculates the newly proposed changes if required.
Note:
• Remote Electrical Tilt is not necessary for C-CCO running in the open loop mode since
no changes are pushed to the network but there will be no recommendations, only the
scores are provided.
• When running open-loop, all targets are scored, regardless of blacklisting or any user/
network CM constraints unless insufficient KPIs exist to calculate scores.
3.2 Running C-CCO

The Coordinated CCO module is launched by users using the standard Eden-NET interface. Target
cells are selected by the user. Eden-NET restricts the module from making changes to only the select-
ed target cells, its co-technology co-sector cells, and antenna shared cells. C-CCO has already been
configured with thresholds for reversing network changes when the configured KPIs are degraded be-
yond the operator policy.
Note: A module may retrieve configuration and performance information for other cells in the
network that are not on the target list. For many modules, this information may be required
by the module’s core algorithms.
The user can specify an optional e-mail address list to which module reports are to be sent. E-mail
addresses can be specified when configuring C-CCO parameters. Multiple e-mail addresses are per-
mitted in the e-mail address list. The reports are sent to the addresses on the email list each time the
module has completed an iteration of C-CCO.
If the module is run in open loop, then the reports are sent after the coverage scores have been deter-
mined. If the module is run in closed loop, then the reports are sent after the module has validated that
the changes pushed to the network were successful.
While multiple instances of the C-CCO module are permitted, no overlapping target cells are allowed,
and running multiple instances that involve overlap of neighbors of target cells is strongly discouraged,
as the KPIs of neighbor cells and proximate neighbor cells are used in the C-CCO scoring calcula-
tions, and can be negatively impacted by running C-CCO in adjacent areas.
The C-CCO module uses the following KPI areas for WCDMA and LTE: KPIs (for each source cell and
its neighbors, DSR Neighbors and proximate fourth tier neighbors):
• Detected Set Reports
DN09273754 1-0 © 2018 Nokia 11

• Handover Attempts
• Active Set Reporting
• Monitored Set Reporting
• Detected Set Reporting
• Cell Capacity KPIs
• Cell Propagation Delay Statistics
• Cell Timing Advance Statistics
• Cell position (Lat/Long)
• Cell antenna azimuth
Note: Some KPIs may be ignored if root algorithms are disabled in the C-CCO configuration
file to be skipped. KPIs may vary depending on module global configuration for different
vendors.
3.3 Module inputs of C-CCO

The C-CCO module requires the following information as inputs:
• Accurate WCDMA cell location data

• WCDMA antenna azimuth, or antenna pointing direction, data for all cells in the network.
• The neighbor list configuration for each of the target cells in the network. This data is read via the
OSS interfaces.
The configuration information (latitude, longitude, neighbor lists) used by C-CCO is read from the
Eden-NET Configuration Management cache in order to minimize access to OSS. The Eden-NET
framework automatically determines if the parameter data should be read from the radio access net-
work based on timeout parameters for the cache.
The score calculations are unique to each of the six root algorithms:
• 3G_Coverage_Standard
• 3G_Coverage_Propagation_Delay
• 3G_Capacity
• LTE_Coverage_Standard
• LTE_Coverage_Timing_Advance
• LTE_Capacity
The algorithms use some combination of capacity KPIs, handover_counters, DSR counters, propaga-
tion delay counters, or timing advance counters.
This data is available for all supported users and is used in conjunction with the cell latitude, longitude,
and antenna azimuth information.
DN09273754 1-0 © 2018 Nokia 12

3.4 Verification and rollback

The C-CCO verification and rollback feature is a safety mechanism wherein the performance level of
a network is checked and any tilt change which is creating a large degradation in service quality is
rolled back. Specific KPIs of accessibility, retainability, traffic, IRAT leakage, and mobility volumes are
monitored. The temporal rules and time aggregation rules are the same as those found in legacy CCO
modules.
Each verification KPI can have one temporal and one spatial rule on how to aggregate the KPI used
for verification.
Temporal rules are used to filter desired time range from the initial range defined in the
KPI_Check_Window parameter.
Time Aggregation Rule Definition
All time For all the values within the Check_Time_Window (with the exception
of the handling of lock preemption) [ Default ].
Example: #LTE Accessibility = -0.01%, all time
Outside defined list of time For all values defined outside the blackout periods defined by the start
ranges times and end times in the list. Blackout periods refer to a defined time
frame during the check time window during which there is no KPI veri-
fication.
Example: #LTE Retainability Voice = -0.01%, sum/sum, out-

side[10:00-10:35]
Inside defined list of time For all values inside the active periods defined by the start times and
ranges end times in the list.
Example: #LTE Retainability = -0.01%, sum/sum, inside[10:00-10:30]
Exclude time when The time-aggregation will exclude all the period when KPI operator
<KPI,operator, Absolute_ Absolute_Value is true. The idea is to be able to exclude from the
Value> verification values that happen outside the normal operational range.
Example: #LTE_CQI_P50 = -0.01%, average, exclude time when LTE

Retainability > 90
Exclude defined weekdays Exclude the listed weekdays (day types are Monday, Tuesday,
Wednesday, Thursday, Friday, Saturday, Sunday).
Example: #LTE_PDCP_Vol_DL_bits = -0.01%, sum, Exclude[Monday]
Exclude defined dates Exclude the listed dates. Date can be in two formats:
• absolute: Month_DayNumber. For example: July_4, November_

11, July_14
DN09273754 1-0 © 2018 Nokia 13

Time Aggregation Rule Definition
• relative: Month_<1st...31st, First, Last>_Weekday. For example:

September_1st_Monday, November_4th_Thursday, May_Last_
Monday
Example: #LTE_PDCP_Vol_UL_bits = -0.01%, Exclude[3rd

October;27th September]
Table 3: Time Aggregation Rules
Spatial rules are used to define the cells from where the verification KPI is aggregated.
Spatial Aggregation Rules Definition
No aggregation The KPI are restricted only to the monitored cell (source cell), there is
no spatial aggregation [Default].
All neighbors The KPI are aggregated across all neighbor cells of the monitored
changed cell (source cell).
All neighbors beyond Tier N The KPIs are aggregated across all the neighbor cells beyond Tier N
(Tier N could be the value of a configuration parameter, for example,
Tx_HO for the LTE_CCO).
All neighbors between Tier The KPIs are aggregated across all the neighbor cells between Tier A
A and Tier B and Tier B (Tier A, Tier B could be the value of a configuration para-
meter, for example, Tx_HO for the LTE_CCO).
All cells between Tier A and The KPIs are aggregated across all the cells between Tier A and Tier
Tier B B (when A = B, the KPIs are aggregated across all the Tier A cells;
Tier A, Tier B could be the value of a configuration parameter, for ex-
ample, Tx_HO for the LTE_CCO).
All cells in <[cell list DNs]> The KPIs are aggregated across all the cells included in the provided
cell list (not to be mistaken with the list of cells to be monitored, which
gives the list of changed cells).
Front lobe weighted The KPIs are aggregated for a defined amount of tiers in front and
<[Front_tiers, Back_tiers]> backlobe direction, separately for:
• Intra-frequency neighbor cells

• Inter-frequency co-sector cells of Intra-frequency neighbor cells
• 4G co-sector cells of Intra-frequency neighbor cells
• 2G co-sector cells of Intra-frequency neighbor cells
Defaults: Front_tiers = 3, Back_tiers = 1
DN09273754 1-0 © 2018 Nokia 14

Spatial Aggregation Rules Definition
Note: This rule must be consistent for each KPI otherwise

the cell is left as No aggregation.
Table 4: Spatial Aggregation Rules
Rollback is initiated if the aggregated KPI of any of the four aforementioned groups exceeds a previ-
ously defined threshold. The Table 5: Operator policy KPIs documents operator policy KPI thresholds
which determine necessity for rollback.
Default KPI threshold input Unit Range Step Description
WCDMA - Voice RRC Acces- % [-100,+100] 0.01 # for 3G co-sectors. The KPI
sibility Failure Rate(AFR) = names are after [WCDMA -]
+10%, average
WCDMA - Voice RAB Access

Failures = +10%, sum
WCDMA - Voice Dropped Call

Rate = +5%, sum/sum
WCDMA - HSDPA_Drop_
Rate = +5%, sum/sum
WCDMA - Voice Erlangs =

-5%, average# (For Alca-
tel-Lucent, use average in-
stead of sum/sum: WCDMA -
HSDPA Avg User Thpt Kpbs
= -5%, average)
WCDMA - HSDPA Avg User

Thpt Kpbs = -5%, sum/sum
WCDMA - # of 3G Voice Calls

ending on 2G layer = -0%,
sum
Table 5: Operator policy KPIs
For more information on User parameters, see C-CCO GUI parameters.
DN09273754 1-0 © 2018 Nokia 15

Coordinated Coverage and Capacity Optimization guide C-CCO algorithm
4 C-CCO algorithm
C-CCO uses performance monitoring (PM) counters and Key Performance Indicators (KPIs) derived
from these counters to derive scores for each of the six root algorithms that are enabled. If certain root
algorithms are not to be used, disable the root algorithm in the parameters and set the weight to 0. If
there is a twin parameter enabled, set weight to 1. For example, the 3G capacity algorithm is disabled.
Set the weight for 3G capacity to 0, ensure that 3G coverage weight is set to 1.
The counters are used to depend on the vendor at a high level:
• 3G Standard Coverage algorithm uses: erlangs, relational handover counts, relational DSR counts
• 3G Propagation Delay Coverage algorithm uses: erlangs, handover counts, propagation delay
counts
• 3G Capacity algorithm uses: erlangs, RRC Connections, relational handover counts
• LTE Standard Coverage algorithm uses: erlangs, relational handover counts
• LTE Timing Advance Coverage algorithm uses: erlangs, handover counts, timing advance counts
• LTE Capacity algorithm uses: erlangs, DL PRB Util., Connected Users, handovers, timing advance
counts
Note: Since the types of counters that are available vary from vendor to vendor, the internal
algorithms used by the module may be adapted to the availability of specific PM counters
and KPIs.
The larger and more positive the score for a root algorithm, the greater the preference for downtilt. The
larger and more negative the score for a root algorithm, the greater the preference for uptilt. However,
it is the overall score for a cell (after aggregating all root algorithms) that will determine the tilt prefer-
ence.
4.1 3G standard coverage root algorithm

3G Standard Coverage Root algorithm uses handover relational counts, DSR relational counts, and
envelopment geometry to create scores for each cell in the target list. The scores returned for a cell af-
ter summing up constituent cells and going through normalization are in the range between -3.5 and
3.5. Most of the cell scores are less than one in magnitude.
A negative score indicates a preference for an uptilt or power increase. A positive score indicates a
preference for downtilt or power decrease.
Note:
• Scores close to zero indicate little or no preference for modification.
DN09273754 1-0 © 2018 Nokia 16

• When Standard Coverage algorithm is enabled, the 3G Propagation Delay Based Cover-
age algorithm should also be enabled. These algorithms are coverage based and com-
plementary.
The reason to enable both coverage algorithms is that the standard coverage algorithm score is not
always accurate on cell boundaries and near water because the geometry does not allow the mea-
surements of the cells to work in a full circle. The 3G Propagation Delay Based Coverage algorithm is
more accurate in these boundary cases.
4.2 3G propagation delay based coverage root algorithm

3G Propagation Delay Based Coverage Root algorithm uses propagation delay bins to project cover-
age for a source cell and neighbor and vicinity cells. From these projections of 95 percentile on top of
25 percentile coverages, overlap bins can be calculated. The scores returned for a cell after summing
up constituent cells and going through normalization are in the range between -3.5 and 3.5. Most of
the cell scores are less than one in magnitude.
Note:
• Scores near zero indicate little or no preference for modification.

age algorithm should also be enabled. These algorithms are coverage based and com-
plementary.
The reason to enable both coverage algorithms is that the standard coverage algorithm score is not
always accurate on cell boundaries and near water because the geometry does not allow the mea-
surements of the cells to work in a full circle. The 3G Propagation Delay Based Coverage algorithm is
4.3 3G capacity root algorithm

3G Capacity Root algorithms are vital additions to the CCO suite of algorithms. It is critical to know if
a cell is overutilized or underutilized relative to its neighbor cells. There are cases where the coverage
algorithm may indicate a preference to uptilt a cell for more coverage, however, there may be little ca-
pacity left in the cell to handle additional traffic. While the weight of this algorithm can be changed from
the default of 0.5, it should always remain enabled to prevent coverage changes that are at odds with
the loading of the cell or its surrounding cells.
The algorithm works as follows:
1. Calculates the 90 percentile busiest hour erlang load (HSDPA + Voice) for source and constituent.
2. Calculates the 90 percentile busiest hour RRC connection rejects for source and constituent.
DN09273754 1-0 © 2018 Nokia 17

3. Calculates the normalized ranking of erlang value in step one, relative to the universe of all target
cells plus constituent cell. A value of 1.0 indicates the highest traffic. A value of 0 indicates the
lowest traffic. Most of the values are in between 1.0 and 0.
4. Calculates the normalized ranking of RRC connection rejects in step 2, relative to the universe of
all target cells plus constituent cell. A value of 1.0 indicates the highest number of rejects. A value
of 0 indicates the lowest traffic. Most of the values are in between 1.0 and 0.
5. From step 3, calculates source_erlang_normalized_rank minus
constituent_erlang_normalized_rank, which is a value between -1 and 1. Calls e-score.
6. From step 4, calculates source_RRC_reject_normalized_rank minus
constituent_RRC_reject_normalized_rank, which is a value between -1 and 1. Calls
accelerator.
7. If either the source cell’s or constituent cell’s 90 percentile busiest hour erlang load exceeds
UMTS_Erlang_Threshold then proceeds to step 8, otherwise final_constituent_score
equals 0.
8. Takes the e-score from step 5 and applies the following equation:
• final_constituent_score = e-score*(1+accelerator) if sign of e-score is

positive.
• final_constituent_score = e-score*(1-accelerator) if sign of e-score is
negative.
4.4 LTE standard coverage root algorithm

LTE Standard Coverage Root algorithm uses handover relational counts and envelopment geometry
to create scores for each cell in the target list that is identical to the 3G coverage algorithm in 3G stan-
dard coverage root algorithm section except that no DSR counts are considered for the LTE conver-
sion.
The scores are returned for a cell, after summing up constituent cells and going through normalization,
are in the range between -3.5 and 3.5. Most of the cell scores are less than one in magnitude.
Note:
• Scores near zero indicate little or no preference for modification.

age algorithm should also be enabled. This algorithms are coverage based and comple-
mentary.
The reason to enable both coverage algorithms is that the standard coverage algorithm score is not al-
ways accurate on cell boundaries and near water because the geometry does not allow the measure-
ments of the cells to work in a full circle. The LTE Timing Advance Delay Based Coverage algorithm is
DN09273754 1-0 © 2018 Nokia 18

4.5 LTE capacity root algorithm

The LTE Capacity Root algorithms are vital additions to the CCO suite of algorithms. It is critical to
know if a cell is overutilized or underutilized relative to its neighbor cells. There are cases where the
coverage algorithm may indicate a preference to uptilt a cell for more coverage, however there may be
little capacity left in the cell to handle additional traffic.
While the weight of this algorithm can be changed from the default of 0.5, it should always remain en-
abled to prevent coverage changes that are odds with the loading of the cell or its surrounding cells.
The LTE Timing Advance Based Coverage root algorithm is identical to its UMTS counterpart de-
scribed in the 3G capacity root algorithm section.
4.6 LTE timing advance based coverage root algorithm

The LTE Timing Advance Based Coverage Root algorithm uses timing advance counts and overlap to
create scores for each cell in the target list. This algorithm is identical to the 3G Propagation Delay al-
gorithm, except that LTE Timing Advance percentiles are used instead of propagation delay counts.
For more details, see the 3G propagation delay based coverage root algorithm section.
Note: When LTE Standard Coverage algorithm is enabled the LTE timing advance based
coverage algorithm should also be enabled. These algorithms are coverage based and com-
plementary. The reason to enable both coverage algorithms is that the standard coverage al-
gorithm score is not always accurate on cell boundaries and near water because the geom-
etry does not allow the measurements of the cells to work in a full circle. The LTE Timing Ad-
vance Based Coverage algorithm is more accurate in these boundary cases.
DN09273754 1-0 © 2018 Nokia 19

Coordinated Coverage and Capacity Optimization guide Configuring and executing C-CCO
5 Configuring and executing C-CCO

Configure and execute the C-CCO module in the following order:
1. Accessing C-CCO
2. Configuring targets for C-CCO
3. Configuring parameters for C-CCO
4. Selecting the configuration file for C-CCO
5. Selecting execution type for C-CCO
6. Confirming execution for C-CCO
C-CCO is executed based on the configuration parameters and as per the defined schedule.
5.1 C-CCO prerequisites

The Coordinated-CCO module is adjusting antenna tilts and CPICH settings according to the root al-
gorithm scoring and other constraints.
The following prerequisites should be met:
• C-CCO license should be installed. For more information, see License details.
• CM data and PM data
• Remote Electrical Tilt (RET) equipped antennas.
• Cell neighbor lists.
• Google Chrome or Mozilla Firefox are the recommended browsers to access Eden-NET.
Note: Since C-CCO inputs are based on handovers, it is best for optimization to have
clean neighbor lists; otherwise, the module may conclude that a cell has a non-optimal tilt
coverage, when in fact the cell is handing over some of its traffic to wrong neighbors.
5.1.1 License details
Table 6: C-CCO license table lists the license required to access C-CCO module in Eden-NET.
LK item code LK item object name Licensed feature component code
ENSW0017CLK Coordinated CCO CLK 0000047978
Table 6: C-CCO license
For more details about licensing, see Eden-NET User and Administration Guide document.
DN09273754 1-0 © 2018 Nokia 20

5.1.2 CM data and PM data
PM and CM data used by the module for each vendor are listed in the following documents:
• Eden-NET Module Specific Data For Nokia document

• Eden-NET Module Specific Data For Ericsson document
5.2 Accessing C-CCO

Log in to the Eden-NET application and access the LTE CCO module to perform any action on the module.
Prerequisites
Prerequisites mentioned in the C-CCO prerequisites section must be met.
1. Log in to the Eden-NET application:

a) In the address field of your Internet browser, type the following URL (for 2VM, 5VM, and Cross-
OSS):
https://<Eden-NET GUI_SERVERS IP>
where <Eden-NET GUI_SERVERS IP> is the IP address of the GUI server provided during
the installation of Eden-NET.
The Eden-NET login page appears.

b) In the Username field, type the username.
c) In the Password field, type the password.
d) Click Log In.
The SON Activity page appears.
2. Click the Configure tab.
The list of active SON modules appears in the left pane.
3. Select the Coordinated CCO module.
Expected outcome
The Configure Targets page appears.
4. Proceed with Configuring targets for C-CCO.
5.3 Configuring targets for C-CCO

In Eden-NET, a module can only be configured and executed on a scope of cells. In Configure Targets page, you can select
cells on the map.
Prerequisites
DN09273754 1-0 © 2018 Nokia 21

Successful completion of Accessing C-CCO.
To configure the target cells, perform the following steps:
1. Select the cells for configuration by using:
• map-based or cell ID search selection tools from the map toolbar

• existing clusters
For more information about selecting cells, see the Select cells section in the Eden-NET User and
Administration Guide.
2. Click Next.
Expected outcome
The Configure Parameters page appears.
3. Proceed with Configuring parameters for C-CCO.
5.4 Configuring parameters for C-CCO

To execute a module, you must configure a set of parameters. In the Configuration Parameter page, a list of parameters,
along with the descriptions and default values are displayed.
Prerequisites
• Successful completion of Configuring targets for C-CCO.
You can retain the default values or select the values from the drop-down list.
1. Define the configuration parameters values. For the list of parameters, see C-CCO GUI
parameters values.
2. Click Next.
Expected outcome
The Select Configuration File page appears.
3. Proceed with Selecting the configuration file for C-CCO.
5.5 Selecting the configuration file for C-CCO

You can select configuration files from the list of available active configurations.
DN09273754 1-0 © 2018 Nokia 22

Prerequisites
• Successful completion of Configuring parameters for C-CCO.

• Ensure that the required configuration files are activated. For more details, see Configuring INI pa-
rameters.
1. Select the required configuration file from the available categories. If configuration files are not
available, proceed to the next step.
Note: You can select only one configuration file from each category.
2. Click Next.
Expected outcome
The Execution Type page appears.
3. Continue with Selecting execution type for C-CCO.
5.6 Selecting execution type for C-CCO

In the Execution type page, you can schedule when the module must be executed. Depending on the type of execution, such
as, immediately, later, or during a specific date and time, the module is scheduled and executed.
Prerequisites
• Successful completion of Selecting the configuration file for C-CCO.
1. To schedule the module execution, select one of the following options:
• Activate Now - to activate the module immediately.

• Activate Later - to activate the module at a later time.
• Schedule Execution - to schedule the module for execution during a certain date and time.
Note: For more information about Activate Later and Schedule Execution, see the
Schedule execution section in the Eden-NET User and Administration Guide.
2. Click Next.
3. Proceed with Confirming execution for C-CCO.
DN09273754 1-0 © 2018 Nokia 23

5.7 Confirming execution for C-CCO

In the Confirm Execution page, you can view the summary of the operation setup and start the operation. The operation is
executed as per the defined schedule.
Prerequisites
• Successful completion of Selecting execution type for C-CCO.
Procedure
• After verifying the configuration summary, click Finish.
Expected outcome
The module starts execution as per the defined schedule.
You can monitor the operation. For more information, see Monitoring C-CCO.
DN09273754 1-0 © 2018 Nokia 24

Coordinated Coverage and Capacity Optimization guide C-CCO configuration parameters
6 C-CCO configuration parameters
6.1 C-CCO GUI parameters

The following parameters are configurable in the Eden-NET graphical user interface.
Parameter Name Description Range Step Default Value
LTE_Enabled Select True to enable optimization for [True/False] True

LTE cells.
LTE_Capacity_En- Select True to enable capacity opti- [True/False] True

abled mization for LTE cells.
LTE_Coverage_En- Select True to enable coverage opti- [True/False] True

abled mization for LTE cells.
LTE_Coverage_ Select True to enable standard cover- [True/False] True

Standard_Enabled age optimization for LTE cells.
LTE_Coverage_TA_ Select True to enable Timing Ad- [True/False] True

Enabled vance optimization for LTE cells.
UMTS_Enabled Select True to enable optimization for [True/False] True

UMTS cells.
UMTS_Capacity_En- Select True to enable capacity opti- [True/False] True

abled mization for UMTS cells.
UMTS_Coverage_ Select True to enable coverage opti- [True/False] True

Enabled mization for UMTS cells.
UMTS_Coverage_ Select True to enable standard cover- [True/False] True

Standard_Enabled age optimization for UMTS cells.
UMTS_Coverage_ Select True to enable coverage prop- [True/False] True

PD_Enabled agation delay optimization for UMTS
cells.
LTE_Weight This parameter is used in cost func- [0..1] Float 0.5

tion to multiply LTE score when LTE_
Enabled is set to True.
LTE_Capacity_ This parameter is used in cost func- [0..1] Float 0.5

Weight tion to multiply LTE Capacity score
when LTE_Capacity_Enabled is
set to True.
DN09273754 1-0 © 2018 Nokia 25

LTE Coverage This parameter is used in cost func- [0..1] Float 0.5
Weight tion to multiply LTE Coverage score
when LTE_Coverage_Enabled is
set to True.
LTE_Coverage_ This parameter is used in cost func- [0..1] Float 0.5

Standard_Weight tion to multiply LTE Coverage Stan-
dard score when LTE_Coverage_
Standard_Enabled is set to True.
LTE_Coverage_TA_ This parameter is used in cost func- [0..1] Float 0.5

Weight tion to multiply LTE Coverage Timing
Advance score when LTE_Cover-
age_TA_Enabled is set to True.
UMTS_Weight This parameter is used in cost func- [0..1] Float 0.5

tion to multiply UMTS score when
UMTS_Enabled is set to True.
UMTS_Capacity_ This parameter is used in cost func- [0..1] Float 0.5

Weight tion to multiply UMTS Capacity score
when UMTS_Capacity_Enabled is
set to True.
UMTS_Coverage_ This parameter is used in cost func- [0..1] Float 0.5

Weight tion to multiply UMTS Coverage score
when UMTS_Coverage_Enabled is
set to True.

Standard_Weight tion to multiply UMTS Coverage Stan-
dard score when UMTS_Coverage_
Standard_Enabled is set to True.

PD_Weight tion to multiply UMTS Coverage Prop-
agation Delay score when UMTS_
Coverage_PD_Enabled is set to
True.
LTE_Allow_RET_ This parameter indicates when LTE [True/False] True

Mod cell has RET available and if the cells
are eligible for tilt modification.
UMTS_Allow_RET_ This parameter indicates when a [True/False] True

Mod UMTS cell has RET available and if
DN09273754 1-0 © 2018 Nokia 26

the cells are eligible for tilt modifica-

tion.
UMTS_Allow_ This parameter indicates if RET is [True/False] True

CPICH_Mod unavailable for modification and if
CPICH modification allowed.
Large_Step_Data_ The number of days of input data [1..14] Integer 5

Interval evaluated for the large step phase in
each Epoch.
Fine_Tune_1_Data_ The number of days of input da- [1..7] Integer 2

Interval ta evaluated for the first fine tuning
phase in each Epoch.
Fine_Tune_2_Data_ The number of days of input data [1..14] Integer 2

Interval evaluated for the second fine tuning
phase in each Epoch.
KPI_Check_Window Time-span for the KPI evaluation be- [30 min Enumerated 8 hours
fore vs. after changes to decide of a
1,4,8,12hrs
possible roll-back.
1-7 days]
Exclude_Weekends Select True to exclude the weekends. [True/False] False
Time_Maintenance_ Start time of the maintenance window. Valid Hour Min- 00:00
Window_Start utes
Time_Maintenance_ End time of the maintenance window. Valid Hour Min- 00:30
Window_End utes
Email Addresses Email Addresses to which the op- -

(Optional) timization reports should be sent.
Separate email addresses with se-
mi-colon or comma.
Epoch_Management Method of convergence before mod- Fixed_Epochs Enumerated Fixed_Epochs

ule exits. Epoch Minimum Improve- or Epoch Mini-
ments will allow the module to exit mum Improve-
prior to maximum Epoch settings if a ments
minimum improvement in cost func-
tion is seen.
SON Operation Set to Open Loop to run module in [Open Loop/ Open Loop
Mode open loop mode. Set to Closed Loop Closed Loop]
to run module in closed loop mode. In
closed loop mode, changes are auto-
DN09273754 1-0 © 2018 Nokia 27

matically pushed to the network with-

out user intervention. In Open Loop
mode, the module will not automati-
cally push parameter changes to the
network. User has to manually provi-
sion the plans to push changes to the
network.
Plan Name Tag Value will be added to the names of

all plans that will be provisioned by
this module. If the target of the mod-
ule is a whole specific cluster, then
the cluster name will also be added to
the plan name.
Table 7: User accessible and graphical interface parameters
6.2 C-CCO INI parameters

The following parameters are common to all instances of the Coordinated Coverage and Capacity Op-
timization module. They are to be set at the module configuration and are not supposed to be changed
for each module launch. They may be revisited from time to time and should be changed only by mod-
ule administrators. Description of the module configuration parameters:
Antenna_Share_In- Enables antenna sharing to be [True/False] True

ter_Tech_Enabled evaluated between LTE and
UMTS. For instances of cells
with inter-technology sharing,
combined cells are created for
purposes of scoring. Only two
cells can be ganged togeth-
er, if more than two, then the
two chosen are those closest
in center frequency.
Antenna_Share_In- Enables antenna sharing to [True/False] True

tra_Tech_Enabled be evaluated within technolo-
gies (UMTS to UMTS or LTE
to LTE). For instances of cells
with intra-technology sharing,
combined cells are created for
DN09273754 1-0 © 2018 Nokia 28

purposes of scoring and mod-

ifications. Only two cells can
be ganged to together for scor-
ing, if more than two, then the
two chosen are those closest
in center frequency.
Cosector_Intra_ Enables co-sector sharing [True/False] True

Tech_Enabled to be evaluated within tech-
nologies if two cells are not al-
ready antenna sharing. On-
ly intra-technology is support-
ed. For instances of cells with
co-sector sharing, combined
cells are created for purposes
of scoring and modifications.
Only two cells can be ganged
together for scoring, if more
than two, then the two chosen
are those closest in center fre-
quency.
Epoch_Exclude_ Exclude cells that have been [True/False] True

Old_Cells optimized in previous epoch
from being considered in sub-
sequent epochs. This allows
2nd set of cells to be opti-
mized. If set to False, then all
cells in the original target list
can be re-evaluated in the 2nd
(or subsequent) epoch.
Fixed_Epochs This value is used to limit the [1..4] Integer 3

total number of epochs than
can be run for one instance.
This is true whether the GUI
parameter Epoch Manage-
ment is set to Fixed_Epochs
or Epoch Minimum Improve-
ments. Either option will use
Fixed_Epochs as the max
limit for total epochs in an in-
stance. This is because we
DN09273754 1-0 © 2018 Nokia 29

do not want the module in-

stance to run forever if the
minimum improvement cannot
be achieved.
Epoch_Minimum_ The percentage of reduction in [1..100] In percent val- 20 %

Improvements cost function between epochs ues
if Epoch_Minimum_Improve-
ments is selected for Epoch_
Management.
LTE_Maximum_Al- This parameter is used to fur- [4..10] 0.1 deg 8

lowable_Tilt ther constrain allowable range
for cell if LTE RET max tilt is
not read as M.O. Essentially
the module will take the min-
imum of (LTE_Maximum_Al-
lowable_Tilt, Actual Max Ret
value).
LTE_Minimum_Al- This parameter is used to fur- [0..4] 0.1 deg 0

lowable_Tilt ther constrain the allowable
range for cell if LTE RET max
tilt is not read as M.O. Essen-
tially the module will take the
maximum of (LTE_Minimum_
Allowable_Tilt, Actual Min Ret
value).
UMTS_Maximum_ This parameter is used to fur- [4..10] 0.1 deg 8

Allowable_Tilt ther constrain allowable range
for cell if UMTS RET max tilt
is not read as M.O. Essential-
ly the module will take the min-
imum of (UMTS_Maximum_Al-
lowable_Tilt, Actual Max Ret
value).
UMTS_Minimum_Al- This parameter is used to fur- [0..4] 0.1 deg 0

lowable_Tilt ther constrain the allowable
range for cell if UMTS RET
max tilt is not read as M.O. Es-
sentially the module will take
the maximum of (UMTS_Min-
DN09273754 1-0 © 2018 Nokia 30

imum_Allowable_Tilt, Actual
Min Ret value).
LTE_large_step_up- The amount of uptilt change [0..2.0] 0.1 deg 1.0

tilt applied to LTE cell in coarse
phase.
LTE_large_step_ The amount of downtilt change [0..2.0] 0.1 deg 1.0

downtilt applied to LTE cell in coarse
phase.
LTE_fine_tune_ The amount of uptilt change [0..2.0] 0.1 deg 0.5

step_1_uptilt applied to LTE cell in fine tune
phase 1 should never be larger
than LTE_large_step_uptilt.
LTE_fine_tune_ The amount of downtilt change [0..2.0] 0.1 deg 0.5

step_1_downtilt applied to LTE cell in fine tune
than LTE_large_step_downtilt.
LTE_fine_tune_ The amount of uptilt change [0..2.0] 0.1 deg 0.3

step_2_uptilt applied to LTE cell in fine tune
than LTE_large_step_uptilt or
LTE_fine_tune_step_1_uptilt.
LTE_fine_tune_ The amount of downtilt change [0..2.0] 0.1 deg 0.3

step_2_downtilt applied to LTE cell in fine tune
phase 2 should never be larg-
er than LTE_large_step_down-
tilt or LTE_fine_tune_step_1_
downtilt.
UMTS_large_step_ The amount of uptilt change [0..2.0] 0.1 deg 1.0

uptilt applied to UMTS cell in coarse
phase.
UMTS_large_step_ The amount of downtilt change [0..2.0] 0.1 deg 1.0

downtilt applied to UMTS cell in coarse
phase.
UMTS_fine_tune_ The amount of uptilt change [0..2.0] 0.1 deg 0.5

step_1_uptilt applied to UMTS cell in fine
tune phase 1 should never be
larger than UMTS large_step_
uptilt.
DN09273754 1-0 © 2018 Nokia 31

UMTS_fine_tune_ The amount of downtilt change [0..2.0] 0.1 deg 0.5

step_1_downtilt applied to UMTS cell in fine
larger than UMTS_large_step_
downtilt.
UMTS_fine_tune_ The amount of uptilt change [0..2.0] 0.1 deg 0.3

step_2_uptilt applied to UMTS cell in fine
uptilt or UMTS_fine_tune_
step_1_uptilt.
UMTS_fine_tune_ The amount of downtilt change [0..2.0] 0.1 deg 0.3

step_2_downtilt applied to UMTS cell in fine
downtilt or UMTS_fine_tune_
step_1_downtilt.
UMTS_large_step_ The amount of CPICH de- [0..2.0] 0.1 dB 1.0

CPICH_decrease crease applied to UMTS cell in
coarse phase.
UMTS_large_step_ The amount of CPICH in- [0..2.0] 0.1 dB 1.0

CPICH_increase crease applied to UMTS cell in
coarse phase.
UMTS_fine_tune_ The amount of CPICH de- [0..2.0] 0.1 dB 0.5

step_1_CPICH_de- crease applied to UMTS cell in
crease fine tune phase 1 should nev-
er be larger than UMTS large_
step_CPICH_decrease.
UMTS_fine_tune_ The amount of CPICH in- [0..2.0] 0.1 dB 0.5

step_1_CPICH_in- crease applied to UMTS cell in
crease fine tune phase 1 should nev-
er be larger than UMTS_large_
step_CPICH_increase.
UMTS_fine_tune_ The amount of CPICH de- [0..2.0] 0.1 dB 0.3

step_2_CPICH_de- crease applied to UMTS cell
crease in fine tune phase 2 should
never be larger than UMTS_
large_step_CPICH_decrease
DN09273754 1-0 © 2018 Nokia 32

or UMTS_fine_tune_step_1_
CPICH_decrease.
UMTS_fine_tune_ The amount of CPICH in- [0..2.0] 0.1 dB 0.3

step_2_CPICH_in- crease applied to UMTS cell
crease in fine tune phase 2 should
never be larger than UMTS_
large_step_CPICH_increase
or UMTS_fine_tune_step_1_
CPICH_increase.
Max_CPICH_Setting The highest CPICH setting al- [28..40] 0.1 dBm 40

lowed for a cell. If a proposed
change would result in high-
er CPICH than this threshold,
then change will not be recom-
mended.
Min_CPICH_Setting The lowest CPICH setting al- [28..40] 0.1 dBm 28

lowed for a cell. If a proposed
change would result in a low-
er CPICH than this threshold,
then change will not be recom-
mended.
Max_Percentage_ Maximum level of CPICH per- [10..15] 1% 12

CPICH_Pwr_of_To- centage of total PA power. If a
tal_Pwr proposed change exceeds this
threshold, then change will not
be recommended.
Min_Percentage_ Minimum level of CPICH per- [5..10] 1% 5

CPICH_Pwr_of_To- centage of total PA power.
tal_Pwr If a proposed change does
not meet this threshold, then
change will not be recom-
mended.
CPICH_Change_ 1. Manage each cell indepen- [1,2,3] Integer 1

Handling dently.
2. Apply same value of CPICH

power co-band and co-sector
cells.
DN09273754 1-0 © 2018 Nokia 33

3. Apply the same CPICH

power increment/decrement
for co-band and co-sector
cells.
Downtilt_Scoring_ Minimum cost threshold to [0..1] Float 0.1

Threshold allow an antenna downtilt or
CPICH decrease.
Uptilt_Scoring_ Maximum cost threshold to al- [-1..-1] Float -0.1

Threshold low an antenna uptilt or CPICH
increase.
Max_Percentage_ Maximum number of cells [0..100] % 20

Cells_Modified_Per_ that can be modified within an
Epoch epoch, expressed in percent-
age of target cells.
UMTS_LTE_En- Forces a nearly equal number [True/False] False

able_Mods_Equally of LTE and UMTS modifica-
tions.
Cost_Function_Con- Expected relational cost func- [0.6..1] Float 0.8

verge_Power tion change for every two dB of
power change. This parameter
should not be changed without
consultation.
Cost_Function_Con- Expected relational cost func- [0.6..1] Float 0.8

verge_Tilt tion change for every two de-
grees of tilt change. This para-
meter should not be changed
without consultation.
Traffic_Scalar_Value Select a value greater than [1..5] Integer 1

one to favor cells that have
higher traffic. This helps to fa-
vor changes towards cells and
clusters with higher traffic.
Flexible_Weighting_ Select True to enable auto [True/False] True

Enabled weighting across root algo-
rithms.
Coarse_Step_KPI_ KPI resolution: 1=15 minutes, [1,2,3] Enum. 2

Resolution 2=hourly, 3=daily
DN09273754 1-0 © 2018 Nokia 34

LTE_Downlink_ For the LTE_Capacity root al- [0..100] % 65

PRB_Threshold gorithm, this is the minimum
PRB_Percentile BH value for
which a source cell and/or its
target will have a non-zero re-
lational cost function score.
LTE_Downlink_ For the LTE_Capacity root al- [0..100] % 90

PRB_Percentile gorithm, this is the BH per-
centile for which the DL PRB
% is calculated above.
LTE_Coverage_HO_ This is the minimum HO over [0..1000] Integer 50

Min_Count the evaluation period where a
constituent cell will be consid-
ered for scoring.
UMTS_Conn_Re- For the UMTS capacity root [0..100] % 90

ject_Percentile algorithm, this is the BH per-
centile for which the connec-
tion rejects are appplied.
LTE_User_Per- For the LTE algorithms, the ac- [0..100] % 90

centile tive user percentile for which
the normalization is deter-
mined.
UMTS_Erlang_Per- For the UMTS algorithms, the [0..100] % 90

centile erlang percentile for which the
normalization is determined.
UMTS_Erlang_ The minimum raw value for [0..40] Integer 10

Threshold which a cell is considered as
loaded.
UMTS_Coverage_ For the UMTS algorithms, the [0..1000] % 100

HO_DSR_Min_ minimum number of HO+DSR/
Count 5 counts a constituent cell
needs to qualify for scoring.
Wide_Beamwidth_ For the 3G PD coverage algo- [0..180] degrees 100

Default rithm and the LTE TA coverage
algorithm, this is the default
antenna beamwidth. It is not
recommened to change this
parameter.
DN09273754 1-0 © 2018 Nokia 35

Beamwidth_Default For the standard coverage [0..180] degrees 60

= 60 algorithms this is the default
antenna beamwidth. It is not
recommened to change this
parameter.
Minimum_Tier This is the minimum Tier for [0..4] Integer 0

which 3G PD or LTE TA cover-
age algorithms will consider. A
0 indicates that 0th tier neigh-
bors will not be included in the
overshooting or undershooting
calcs.
Maximum_Tier This is the maximum Tier for [3..6] Integer 4

which 3G PD or LTE TA cov-
erage algorithms will consider
a neighbor or proximate non-
neighbor in the calculations for
overlap.
Maximum_Proxi- For the 3G PD coverage and [16..48] Integer 32

mate_Non_Neighbor LTE TA coverage algorithms,
this is the maximum number of
proximate neighbors that will
be calculated for overlap.
Note: Increasing this

value may require
longer periods of
processing time to
retrieve scores.
Lower_PD_TA_Per- This value represents the cell [10..40] Integer 25

centile being overlapped. These val-
ues should not be changed
without consultation.
Upper_PD_TA_Per- This value represents the over- [75..95] Integer 95

centile lapping cell. These values
should not be changed without
consultation.
Data_Reliability_ This is the minimum % of data [75..100] % 90

Threshold hours present for a KPI in or-
DN09273754 1-0 © 2018 Nokia 36

der for a KPI to be used in the

module
Run_With_Profiler Used for software developer [True/False] False

debugging
Diagnostic_Data_ Used for software developer [True/False] True

Enabled debugging
[patype] Format is patype = nominal, 39 = 28, 0.8, 1 Enum examples

difference to upper bound in
40 = 29, 0.8, 1
positive value, difference to
lower bound in positive value 41.8_rru = 29.1,
0.8, 0.8
for RRU, add _rru after patype
[cell tilts] To change cell's min or max * = 0, 10

tilts.
where * is cell
# format is cell name pattern = name
min tilt, max tilt
# If one of them is not needed,

leave it empty, but comma is
always needed
Table 8: Module configuration file parameters
6.2.1 Example of C-CCO configuration file
The .ini file is created using configuration parameters. The example of configuration file for C-CCO
module with default values:
[global]
Coarse_Step_KPI_Resolution = 2
LTE_Downlink_PRB_Threshold = 65
LTE_Downlink_PRB_Percentile = 90
LTE_Coverage_HO_Min_Count = 50
LTE_User_Percentile = 90
UMTS_Erlang_Percentile = 90
UMTS_Erlang_Threshold = 2
UMTS_Coverage_HO_DSR_Min_Count = 100
UMTS_Conn_Reject_Percentile = 90
Beamwidth_Default = 60
Wide_Beamwidth_Default = 100
Minimum_Tier = 0
Maximum_Tier = 4
DN09273754 1-0 © 2018 Nokia 37

Maximum_Proximate_Non_Neighbor = 32
Lower_PD_TA_Percentile = 25
Upper_PD_TA_Percentile = 95
Run_With_Profiler = False
Diagnostic_Data_Enabled = True
[patype]
# To be used when selecting PA type for cpich range.
# format is patype = nominal, difference to upper bound in positive value,
difference to lower bound in positive value
# for RRU, add _rru after patype
39 = 28, 0.8, 1
40 = 29, 0.8, 1
41.8 = 32.1, 0.8, 1
43 = 32.1, 0.8, 1
44.8 = 35.1, 0.8, 1
41.8_rru = 29.1, 0.8, 0.8
43_rru = 29.1, 0.8, 0.8
[cell tilts]
# To change cell's min or max tilts.
# format is cell name pattern = min tilt, max tilt
# If one of them is not needed, leave it empty, but comma is always needed
* = 0, 10
[Operator policy]
# The format is KPI name = +/-number%, Aggregation Rule, Spatial
Aggregation Rule, Time Aggregation Rule
# + means the tolerance can go up to that number
# - means the tolerance can go down to that number
# Aggregation Rules can be sum, average, or sum/sum
# sum/sum is implemented in mdk for summation of all pegs before division
# Spatial Aggregation Rules
# Time Aggregation Rules
LTE IRAT Count = -0.01%, sum
LTE_CQI_P50 = -0.01%, average
# for 3G cosectors. The KPI names are after WCDMA -
WCDMA - Voice RRC Accessibility Failure Rate(AFR) = +10%, average
WCDMA - Voice RAB Access Failures = +10%, sum
# for 2G cosectors. The KPI names are after GSM -
GSM - TCH_Traffic_Erl = -10%, average
GSM - TCH Traffic Erlang = -10%, sum
6.3 Configuring INI parameters

INI parameters can be modified to change the default settings of a module. You can also import, export, delete, activate, and
deactivate configuration files.
Only users with admin privileges have permissions to modify the INI parameters.
DN09273754 1-0 © 2018 Nokia 38

OSS):

d) Click Log In.
2. Click Administration → Modules.
A list of SON modules appears in the left pane.
3. Select the Coordinated CCO module.
4. Click Configure → Module Configuration.
The Coordinated_CCO Configuration Manager dialog box appears.
5. Click Module Global Configuration.
A list of configuration files appears.
You can click:
• Import And Activate: to import a file and activate it immediately.

• Import: to import a file.
• Export: to export the selected file to your system.
• Delete: to delete the selected file from the list.
Note: Users with Administrator or SON Module Manager permissions can delete
the configuration files. The configuration files can be deleted only if it is not used by
other modules.
• Activate: to activate the selected file from the list.
Note: Multiple configurations can be activated.
• Deactivate: to deactivate the activated file.
Note: A file can be deactivated only when it is not used by other modules listed
under Active SON Modules or Module History.
DN09273754 1-0 © 2018 Nokia 39

• Set As Default: to set the selected file as the default configuration.

• Reset: to reset the edited parameter values in the selected INI file.
• Save: to save the new version of the configuration after editing the parameter values in the
selected INI file.
• Save As: to save the configuration with a different name.
Note: For more details, see the Configuring a module section in Eden-NET User and
Administration Guide.
For the INI file parameters, see C-CCO INI parameters.
6.4 CCO AVR configuration parameters

The following parameters are for CCO AVR of the C-CCO module.
Parameter
Description Range Step Default Value
Name
Action_When_ Monitoring behavior when the [Continue, n/a Continue

Preempted lock related to the changes under Abort, Delay]
verification is preempted.
Benchmark_ Start of the time period used as a n/a

[0..365] days
Time_Start reference for the KPI degradation
evaluation: the same time as the
parameter change, but N days
before (N days).
• 0 means comparing the pe-

riod just before the changes
with the period after the
changes (example: 2 hours
after vs. 2 hours before)
• 1 allows to compare with the
same time period the day be-
fore
• 7 allows to compare with the
same time period, the same
day of the week before
Blacklist_Time_ Duration during which a blacklist- [1.365] days 1 day 7 days

Window ing is taking effect.
DN09273754 1-0 © 2018 Nokia 40

Parameter
Name
Check_Time_ Time window during which the [1..1440] 1h 2h

Window KPI values need to be aggregat- hours
ed.
Completeness_ Percentage of the Check Time [0..100] % 1% 80%

Ratio Window or the current Measure-
ment Period, during which valid
KPIs are collected, to consider
that the amount of data is suffi-
cient for the related Time Window
or Measurement Period.
Counter_Granu- The time between two Perfor- [0..10080] mn 1 mn 15 mn

larity mance Management Files deliv-
ery. It may have a different name
depending on the vendors: Re-
sult Output Period (ROP), Mea-
surement Period, Granularity Pe-
riod and so on.
Data_Stabiliza- Delay for getting a complete da- [0..1440] mn 15 mn • 15 mn for

tion_Time ta set (letting all the OSS PM 15mn-gran-
files being produced, fetched ulrity
and loaded in the PM database) • 1h for
that reflects the impact of the hourly
changes made to the network counters
(the next measurement period af-
ter the changes were made).
KPI_Validity_ Minimum proportion of the time [0..100] % 1% 80%

Time% window that should return non-
NONE values.
KPI_Validity_Nb_ Minimum number of samples to [100, 200, n/a 200

Samples consider a ratio as statistically 400, 1000,
significant. 10000]
Max_Delay_Time Maximum time delay to complete [1..1440 ] 1h 4h

the KPI values after discarding hours
the values during the lock pre-
emption.
(for Action_When_Preempted =
Delay)
DN09273754 1-0 © 2018 Nokia 41

Parameter
Name
Reset_Window_ Toggle to restart the KPI collec- [True/False] n/a False

Required tion from scratch (TRUE) when
the lock was pre-empted or to
complete the set already com-
pleted (FALSE) discarding the
period during which the lock was
pre-empted.
Retry_Failed_ In case the rollback plan failed, [True/False] n/a True

Pushes the failed pushes should be retry
once if this parameter is True.
In case of partial failures, a new

plan is created with only the
failed pushes and the plan is
push once if this parameter is
True.
If the parameter is False, there is

no retried.
Table 9: CCO AVR Configuration Parameters
Monitoring of KPIs is required for AVR. The following table shows Monitored KPI Configuration File.
The input can be also obtained from other ways, either through a more complex input files including
other information specific to a module calling this function or through thresholds calculated within the
calling module.
Spatial Time Ag-

RollBack Aggrega-
Name = Degradation Aggrega- gregation
Threshold tion Rule
tion Rule Rule
KPI1 = + (plus sign) if the degra- deltaRB_ sum, aver- all neigh- outside <list
dation translates into an KPI1% age, min, bors [start_time-
increase of the KPI value max end_time]>
- (minus sign) if the sum/sum

degradation translates in- (for ratios)
to a decrease of the KPI
value
KPI2 = + (plus sign) if the degra- deltaRB_ sum, aver- all cells Exclude
dation translates into an KPI2% age, min, between time
increase of the KPI value max when <list
[KPI,operator,
DN09273754 1-0 © 2018 Nokia 42

Spatial Time Ag-

RollBack Aggrega-
Name = Degradation Aggrega- gregation
Threshold tion Rule
tion Rule Rule
- (minus sign) if the sum/sum Tier A and Absolute_
degradation translates in- (for ratios) Tier B Value]>
to a decrease of the KPI
value
Table 10: Monitored KPI Configuration File
The KPIs can be from different technologies, allowing some degradation on older technologies to give
priority to newer technologies.
DN09273754 1-0 © 2018 Nokia 43

Coordinated Coverage and Capacity Optimization guide Viewing C-CCO reports
7 Viewing C-CCO reports

For every execution, the C-CCO module generates multiple reports in .xlsx format.
To view logs for C-CCO cells in the Eden-NET user interface, perform the following:

OSS):

d) Click Log In.
2. Click SON Modules → Status.
Active SON Modules and Module History appears in the left pane, and Execution Status
appears in the right pane.
3. In the left pane, click a module either from Active SON Modules or Module History.
The module execution status appears in the right pane.
Note: The Active SON Modules area displays all active SON module instances which
are in a state other than stopped, completed, or failed. The Module History area of the
Status tab displays SON modules in various states of inactivity like recently stopped,
completed, or failed.
4. In the right pane, click Logs.
5. Click the user name next to User Outputs.
Directory Listing For dialog box with the list of file with module name appears.
6. Select the module file name.
A set of related Excel files are listed in the Directory Listing For dialog box.
7. Select a file and open or save it.
DN09273754 1-0 © 2018 Nokia 44

The module generates an Excel spreadsheet. For information on the contents of the report, see C-
CCO reports.
7.1 C-CCO reports

After execution of a module instance, the C-CCO generates a report. The report contains the following
details:
• detecting under- and over-shooting cells

• overloaded cells and underloaded cells to determine tilt directions
• details for cells found to have scores beyond thresholds
The report also creates the summary tabs for LTE and WCDMA for each algorithm that is enabled.
The weighting scalars are also provided for each root algorithm and technology. Finally, a column with
a value for the calculated auto-divisors for each root algorithm and technology is recorded. These au-
to-divisor values are calculated once per epoch and are used to ensure that root algorithms and tech-
nology scores and weights are properly and consistently normalized and added in the aggregation
phase to create a single score per cell (or combined cell).
Note: If co-sector or antenna sharing parameters are enabled, it is possible to have

combined cells. For score ranking, a combined cell is a simple addition of the scores from
the two contributing cells. In this way, combined cells can have larger scores than single
cells when prioritizing the most important tilt (or CPICH) changes. This is by design. If two
cells with large scores are part of a combined cell, a system benefit that combines cells
is modified before the others. Currently, only two cells can form a combined cell. In cases
where more than 2 cells are attached to the same RET or more than 2 are attached to the
same co-sector, the module will pick the 2 cells that are closest in frequency.
For each cell, the report shows the current tilt value in OSS, the recommended change, recommend-
ed final value, verified value (if change applied), and tilt limits for the cell. If there is an issue with the
Remote Electrical Tilt (RET), the module then tries to apply corresponding changes to the CPICH pow-
er level for 3G cells. There are no alternative modifications to LTE cells if RET is unavailable. The LTE
cells without RET will still be scored but not recommended for modification.
The scoring report lists the following tabs:
Tabs Description
C-CCO Parameters Module parameters and values that are part of the GUI and INI parameters.
LTE Cells Recommen- LTE cells that are recommended for modification along with scoring and oth-
dation er information.
LTE Cells Excluded LTE cells that are excluded from recommendations and the reasons why
they are excluded.
DN09273754 1-0 © 2018 Nokia 45

Tabs Description
UMTS Cells Recom- UMTS cells that are recommended for modification along with scoring and
mendation other information.
UMTS Cells Excluded UMTS cells that are excluded from recommendations and the reasons why
they are excluded.
LTE Cells Score Sum- Scoring and weights for each of the LTE root algorithms and the final scor-
mary ing.
UMTS Cells Score Scoring and weights for each of the UMTS root algorithms and the final
Summary scoring.
Errors and Info Error tabs related to KPIs and other warnings that came from the module
execution.
Table 11: C-CCO report
The C-CCO Parameters tab provides the following information in the worksheet:
• Epoch number
• Phase number
• All Module GUI parameter names
• All Module GUI parameter values
• All Config.ini parameter names
• All Config.ini parameter names
The LTE Cells Recommendation tab provides the following information in the worksheet:
• Cell Column
• Cell Action Column - Uptilt or Downtilt
• Combined with Column – paired cell (if any)
• Total C-CCO Score Column
• Individual Cell C-CCO Score Column
• LTE Weight Column
• Traffic Scalar Adjustment Column
• LTE Coverage_Standard Score Column
• LTE_Coverage_Timing_Advance Score Column
• LTE_Capacity Score Column
• Current Electrical Tilt Column
• Increment Column
• Recommended E Tilt Column
• Verified E Tilt Column
• Minimum E Tilt Column
• Maximum E Tilt Column
DN09273754 1-0 © 2018 Nokia 46

• Cumulative Changes Column

• Frequency Column
The LTE Cells Excluded tab provides the following information in the worksheet:
• Cell Column
• Cell Cause Column
• LTE Weight Column
• LTE Coverage_Standard Score Column
• LTE_Coverage_Timing_Advance Score Column
• Current Electrical Tilt Column
• Increment Column
• Recommended E Tilt Colum
• Verified E Tilt Column
• Minimum E Tilt Column
• Maximum E Tilt Column
The LTE Cells Score Summary tab provides the following information in the worksheet:
• Cell Column
• LTE Weight ColumnTraffic Scalar Adjustment Column
• LTE Coverage Overall Weight Column
• LTE Coverage Standard Weight Column
• LTE Coverage TA Weight Column
• LTE Capacity Weight Column
• LTE_Coverage_Standard Score Column
• LTE Coverage Timing Advance Score Column
• Auto Divisor ColumnFrequency Column
The UMTS Cells Score Summary tab provides the following information in the worksheet:
• Cell Column
• Combined with ColumnTotal C-CCO Score Column
DN09273754 1-0 © 2018 Nokia 47

• UMTS Weight Column

• UMTS Coverage Overall Weight Column
• UMTS Coverage Standard Weight Column
• UMTS Coverage Propagation Delay Weight Column
• UMTS Capacity Weight Column
• UMTS_Coverage_Standard Score Column
• UMTS Coverage Timing Advance Score Column
• UMTS Capacity Score Column
• Auto Divisor Column
Errors and Info tab provides Cell Columns names and Errors or Comments Column.
Note: If a cell is missing KPIs for an enabled root algorithm or missing traffic KPI for normal-
ization, then that missing KPI should be listed in the Errors or Comments Column. Other er-
rors may also be listed in this column.
In addition to the module reports, the Eden-NET framework logs module activity. These logs may be
retrieved and reviewed by the user. For more information, see the Logs section in the Eden-NET User
and Administration Guide.
DN09273754 1-0 © 2018 Nokia 48

Coordinated Coverage and Capacity Optimization guide Monitoring C-CCO
8 Monitoring C-CCO
You can monitor the C-CCO module's:
• activities
• status
• events
For more information, see the Monitoring SON Modules section in the Eden-NET User and Administra-
tion Guide.
C-CCO RAN KPIs
For each vendor, the list of RAN KPIs is listed in the RAN KPIs section of the following documents:
• Eden-NET Module Specific Data For Nokia

• Eden-NET Module Specific Data For Ericsson
C-CCO impact on the network
For each vendor, the managed object that is created, deleted, or modified in a network is mentioned in
the Actions column of the CM objects or parameters section in the following documents:
• Eden-NET Module Specific Data For Nokia

• Eden-NET Module Specific Data For Ericsson
DN09273754 1-0 © 2018 Nokia 49

Coordinated Coverage and Capacity Optimization Guide: Eden-NET 18

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Coordinated Coverage and Capacity Optimization Guide: Eden-NET 18

Uploaded by

Copyright:

Available Formats

Eden-NET 18

Coordinated Coverage and Capacity

Copyright © 2018 Nokia. All rights reserved.

Important Notice on Product Safety

3 C-CCO functional description and guidelines............................................................................................10

5 Configuring and executing C-CCO..............................................................................................................20

6 C-CCO configuration parameters................................................................................................................ 25

7 Viewing C-CCO reports.................................................................................................................................44

Eden-NET 17 SP1 FP1 New document.

Table 1: Summary of changes

DN09273754 1-0 © 2018 Nokia 5

• Standard coverage algorithm for WCDMA

Figure 1: Cellular network

DN09273754 1-0 © 2018 Nokia 6

DN09273754 1-0 © 2018 Nokia 7

Automatic Verification and Rollback Capability

KPIs can be selected from a variety of areas such as:

DN09273754 1-0 © 2018 Nokia 8

Technology Supported Vendor

WCDMA, LTE Nokia

Table 2: C-CCO supported vendor and technology

DN09273754 1-0 © 2018 Nokia 9

3 C-CCO functional description and guidelines

3.1 Operational modes of C-CCO

• Closed loop mode

3.1.1 Closed loop mode

3.1.2 Open loop mode

DN09273754 1-0 © 2018 Nokia 10

3.2 Running C-CCO

• Detected Set Reports

DN09273754 1-0 © 2018 Nokia 11

3.3 Module inputs of C-CCO

• Accurate WCDMA cell location data

DN09273754 1-0 © 2018 Nokia 12

3.4 Verification and rollback

Time Aggregation Rule Definition

Example: #LTE Accessibility = -0.01%, all time

Example: #LTE Retainability Voice = -0.01%, sum/sum, out-

Example: #LTE Retainability = -0.01%, sum/sum, inside[10:00-10:30]

Example: #LTE_CQI_P50 = -0.01%, average, exclude time when LTE

Example: #LTE_PDCP_Vol_DL_bits = -0.01%, sum, Exclude[Monday]

• absolute: Month_DayNumber. For example: July_4, November_

DN09273754 1-0 © 2018 Nokia 13

Time Aggregation Rule Definition

• relative: Month_<1st...31st, First, Last>_Weekday. For example:

Example: #LTE_PDCP_Vol_UL_bits = -0.01%, Exclude[3rd

Table 3: Time Aggregation Rules

Spatial Aggregation Rules Definition

• Intra-frequency neighbor cells

Defaults: Front_tiers = 3, Back_tiers = 1

DN09273754 1-0 © 2018 Nokia 14

Spatial Aggregation Rules Definition

Note: This rule must be consistent for each KPI otherwise

Table 4: Spatial Aggregation Rules

Default KPI threshold input Unit Range Step Description

WCDMA - Voice RAB Access

WCDMA - Voice Dropped Call

WCDMA - Voice Erlangs =

WCDMA - HSDPA Avg User

WCDMA - # of 3G Voice Calls

Table 5: Operator policy KPIs

For more information on User parameters, see C-CCO GUI parameters.

DN09273754 1-0 © 2018 Nokia 15