Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Ame r ic a s H e a d q u a r te r s
Cisco Systems, Inc.
170 West Tasman Dr ive
San Jose, CA 95134- 1706
USA
http://www.cisco.com
Tel:
408 526- 4000
800 553- NET S ( 6387)
Fax: 408 527- 0883
Cont e nt s
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT
NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE
BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY
FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE
INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU
ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR
A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB)
as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of
California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE
PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED
OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL
DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR
INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's
trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use
of the word partner does not imply a partnership relationship between Cisco and any other company.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any
examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes
only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Cisco Quantum SON Suite Automatic Parameter Organization for UMTS Macro Cells
2014 Cisco Systems, Inc. All rights reserved.
For details on licenses pertaining to open source used in the SON system, please refer to the Open
Source Used In Cisco Quantum SON Suite document.
O L- 3 2 3 9 0 - 0 1
CONTENTS
1. Automatic Par ameter s O ptimization ( APO ) Theor y of O per ation
Priority Management
13
14
15
15
16
17
iii
Cont e nt s
18
19
O L- 3 2 3 9 0 - 0 1
1.
The APO application is part of the Cisco Quantum SON framework. These applications enable the
Operators to maximize their network resources by offering a quick response to network and
environmental changes. This dynamic optimization technology uses a unique Network Visibility
capability to check the current conditions of the network (Snapshot), fine tune the configuration
(Action), and test the results (Feedback).
The APO operates before the ANR starts its cycle:
Figure 1: APO-ANR Cycle
By default, a new cell is configured to be activated for all applications except MEH.
If the APO application is set to OFF, the operational state of a new cell will automatically change from
"New" to "Exist" to enable the various applications to work on it. This is the only case in which APO
will not work on a cell.
O L- 3 2 3 9 0 - 0 1
Automatic activation: When the application is Enabled, it will run automatically and autonomously
creating an initial neighbor list for new cells as they are identified by the system during the
periodic synchronization process. The new cells must be configured in the OSS with their location
ID, azimuth, coordinates (which must be within the network/market's geographical area).
Manual activation: Cells that change locations within the network, e.g. mobile cells (COWs) used
in mass event venues or for disaster recovery, need to be reconfigured for their new location.
However, as they are not new cells in the network, the automatic Plug & Play will not be triggered
on them. APO enables to manually change the cell's operational status to "new", causing Plug &
Play to run on it on the next snapshot (see Viewing and Changing the Operational Status of Cells
on page16).
Cell Name
Location ID
Longitude
Latitude
Azimuth
If the new cell is in a new RBS, even if the RBS is in the same location as an existing RBS.
If all other cells in the RBS are also missing the long/lat values.
It will attempt to create symmetrical relations. If it cannot, the relation will not be created. See
Maintaining Symmetric Relations on page6
The relations are created from the nearest (co-located) to the farthest cells (up to the configured
distance in the Max Distance for Neighbor Relations from Outdoor Cell and Max Distance for Neighbor
Relations from Indoor Cell parameters).
Blocked cells, or cells in the forbidden relations list will not be affected.
Cells which do not have beam overlap will not be affected (the Plug & Play cells beam radius is the
configured radius parameter).
Candidate neighbors that do not have a cell radius (e.g. nearby new cells), but are within the cell
radius of the source Plug & Play cell, will receive a default radius of 3 km in order to check beam
overlap.
Cells which already have relations with the same scrambling code as the Plug & Play cell will not
be affected (these are cases of second order scrambling code).
O L- 3 2 3 9 0 - 0 1
If possible, the entire intra-frequency neighbor list will be defined (up to the number of relations set
by Max Number of Intra-frequency Neighbor Relations) - as long as they are within the configured
maximum distance.
In symmetric relations, if a cells neighbor list is full, the system will attempt to delete a relation that
fulfills the following requirements:
o
The cell has a weight lower than the configured Max Weight for Neighbor Deletion
If relations have no weight, the farthest cells from the source cell are deleted first
If no such cell exists, the relation to/from the relation will not be created.
The priority of cells that are off air will not change.
When introducing a cluster of cells into the network, the nearby cells may not yet be defined in the
OSS at the time the application creates neighbor relations for the plug & play cell. In this case, the
application will add the number of relations defined by Max Number of Intra-frequency Neighbor
Relations) and it will also add relations to the nearby cells as they are introduced into the system, even
if the cell and/or the candidate neighbors are off-air. In this case, the number of neighbors may exceed
Max Number of Intra-frequency Neighbor Relations. If the number of relations reaches the maximum
number of relations allowed in the neighbor list, the farthest relations will be deleted to make room for
these new relations.
Ex ample - Adding Multiple Plug & Play C ells
Three new cells are to be introduced into the network: A, B, and C. For illustration purposes, the cells
are defined in the OSSin consecutive days.
Cells A, B, and C are off-air and stay off-air for the next three consecutive days.
In Day 1, cell A is defined in the OSS. Plug & Play is activated as the cell status is "new", and 15
neighbors (Max Number of Intra-frequency Neighbor Relations) are created in its neighbor list.
In Day 2, Cell B is defined in the OSS. Plug & Play is activated as the cell status is "new", and 15
neighbors (Max Number of Intra-frequency Neighbor Relations) are created in its neighbor list. At this
point, a relation to cell B is also created in Cell A's neighbor list, totaling the number of relations in A's
neighbor list to 16 (i.e. above Max Number of Intra-frequency Neighbor Relations).
In Day 3, Cell C is defined in the OSS. Here too, relations are added in both A's and B's neighbor lists.
The result is that the NL of cell A and cell B have more neighbor relations created by the application
than defined by Max Number of Intra-frequency Neighbor Relations.
For all relations created the APO Plug & Play creates the reciprocal relation as well
If the neighbor list that the new cell is to be added to (the to-target) is full, a weaker neighbor
relation will be deleted to make room for the new relation
The same deletion holds true for second order neighbor deletions
If Plug & Play runs on a cell with existing relations, the application will create any reciprocal
relations required in order to ensure that all relations are symmetrical
O L- 3 2 3 9 0 - 0 1
For all new relations created the APO Plug & Play creates relations according to the LMS
Any pre-existing relations on the cell that do not comply with LMS are removed.
Priority Management
When compiling a monitored set, the UE compiles the list from the neighbors of the active set cells
with the highest relation priority.Cell relations that do not have the proper priority will not be added
to the monitored set. Priority change is generally based on the intra-frequency weights, with the
exception of co-sectors and co-location, which are assigned a higher priority.
The ANR has an option of enhancing the priorities used by the RNC in generating the union set in Soft
Handover situations, thus indirectly optimizing the Monitored Set. The application checks the Detected
Set and Unmonitored Set messages as they are created by the RNC. The application then re-evaluates
the priorities based on the relative weight of the neighbors as reported by UEs connected to the cell
being checked. This in turn will move required cells from the unmonitored to the monitored set, to
become available for use as an active cell in the Active Set.
If the priorities are not set correctly, a cell in the unmonitored set could become a strong candidate for
handover, but would be rejected by the RNC since it is not in the Monitored Set. Additionally, cells in
the unmonitored set are more seldom sampled by the UE, therefore it is more likely, especially in fast
moving scenario, that a call could be dropped due to cell not monitored in time.
This module is activated through the Priority application settings.
Newly added intra-frequency relations and newly added Inter relations with Femto cells are assigned
the highest available priority. The priorities assignment application sets relation priorities according to
the weight of the relations which is derived from the handover attempts to each of the relations.
A new neighbor is initially assigned the highest available priority (either by ANR or by APO. The
initial priority is then recalculated by ANR.
To avoid excessive priority reordering, the existing priority is compared to the new priority. The
neighbor priorities will be updated only in case of a significant change.
The application sets priorities per vendor, as follows:
Vendor
Ericsson
ALU
Huawei
NSN
ANR Intra
1-31
0-30
0-30
Not used
ANR Inter
32-63
31-62
31-62
Co-sector cells
Co-located cells
A new neighbor is initially assigned the highest available priority (either by ANR or by APO. The
initial priority is then recalculated by ANR.
To avoid excessive priority reordering, the existing priority is compared to the new priority. The
neighbor priorities will be updated only in case of a significant change.
The application sets priorities per vendor, as follows:
Table 2: SON Priority Ranges per Vendor
Vendor
Ericsson
ALU
Huawei
NSN
ANR Intra
1-31
0-30
0-30
Not used
ANR Inter
32-63
31-62
31-62
O L- 3 2 3 9 0 - 0 1
2 . S e t t ing up t he AP O P roc e s s
Ma nua l Re - hom ing
Manual Re-homing
Quantum SON offers support to the process of changing the parent RNC of Node Bs, known as rehoming, including all the required changes in the neighbor lists. During the re-homing process, the
configuration (profiles) of the re-homed cells are copied to the new cells. KPIs are also preserved in
order to maintain the history of SON actions performed before the re-homing.
Supported Vendors
The following equipment vendors are supported:
2.
Ericsson
Alcatel-Lucent (ALU)
NSN
Huawei
2 . S e t t ing up t he AP O P roc e s s
Ac t iv a t ing a nd Bloc k ing Module s
Search Criterion
Cell Name
RNC Name
Type
Vendor
Is Repeater
Indoor
DAS
Location USID
Description
Search for cells according to the name
Search for cells served by a specific RNC
Search for cells according to the type (macro, femto, etc.)
Search for cells according to equipment vendor
Search for cells that serve (or do not serve) as repeaters
Search for indoor cells (or exclude them)
Search for DAS cells (or exclude them)
Search for cells according to location ID (enter a number)
O L- 3 2 3 9 0 - 0 1
2 . S e t t ing up t he AP O P roc e s s
Ac t iv a t ing a nd Bloc k ing Module s
Search Criterion
Azimuth
Beam Width
HO Type
Carrier
CPICH
Profile Name
Application Status
Face
Description
Search for cells according to the azimuth (enter an angle)
Search for cells according to the beam width (enter an angle)
Search for cells according to defined handover type (IFHO, GSM)
Search for cells according to the carrier UARFCNDL (frequency)
Search for cells according to CPICH (enter a number)
Search for cells according to the associated profile (per application)
Search for cells according to the status of the SON applications for
the cell - Blocked/Unblocked (per application or All Applications)
Search for cells belonging to a specific face
iii. Select an operator from the drop-down list. The available operators are:
Table 4: Search Operators
Operator
Equals
Contains
Not equals
In
Not in
Less than
Greater than
Description
Search for an exact string
Search for the search criterion containing the specified string
Search for all cells except those that match the exact string
Search for any cell in the specified list. The list can be copied from an
external file (Excel/Word/Notepad). Alternatively, you can enter the
list of items separated by a space.
Search for all cells that are not in the specified list. The list can be
copied from an external file (Excel/Word/Notepad). Alternatively, you
can enter the list of items separated by a space.
(Where applicable) Search for values smaller than the specified value
(Where applicable) Search for values larger than the specified value
iv. Enter the value to search in the free text field. Click on the Expand Textbox icon to open a
larger window. You can enter a list of values separated by spaces.
v. (Optional) You can add more filters by clicking on the + sign. This opens another line of
search criteria which you can use to expand the search (using the OR logical operator) or
narrow down the results (using the AND logical operator). To remove a specific filter, click
on the - sign next to the filter row to be removed.
vi. Click on Apply Filter. The cells matching the search criteria are listed in the cells table. You
can export the results to a CSV file to be saved on your file system by clicking on the
button.
l
If you have an external list of cells (e.g. a list of cell names, azimuths, etc.) in an external
application (e.g. Excel, Word, Notepad, etc.), you can copy the list and enter it in the free text
field. Make sure that the search criterion matches the values specified in the list. For example, if
the list includes names of cells, make sure that the selected search criterion is Cell Name. If the
list includes several azimuths, make sure that the selected search criterion is Azimuth.
You can also type the list inside the free text field. Separate the list items by using spaces.
11
2 . S e t t ing up t he AP O P roc e s s
Ac t iv a t ing a nd Bloc k ing Module s
4. After selecting the search criteria, click on the Apply Filter button. The list of cells are listed in the
cells table. You can export the results to a CSV file to be saved on your file system by clicking on
the
button.
5. Select the cells from the resulting list by clicking in the check-boxes next to each cell name. Note
the Application Status and also All Applications Status columns for each cell. These indicate
whether the specific application is enabled for the cell. If the All Applications Status indicates
"Unblocked", this means that at least one application is enabled for this cell.
6. Click on the Modify Module Activation button. The Module Activation configuration window opens.
Figure 7: Module Activation Configuration Window
Element
Cell Type
Application: Enable
Application: Disable
SON: Block
Description
The cell type selected in the cell search (UMTS or LTE)
Activates the application on the selected cells. The selected cell may
trigger the action of the specific application and it may be affected by an
action performed by the application on another cell.
Deactivates the application on the selected cells. When disabled, the cell
will not trigger any action of the specific application and will not be
affected by any action performed by the application on another cell.
No SON actions will be performed on the selected cells. Used for limited
O L- 3 2 3 9 0 - 0 1
2 . S e t t ing up t he AP O P roc e s s
Ac t iv a t ing a nd Bloc k ing Module s
Element
Description
periods when you want to perform maintenance tasks on these cells (e.g.
re-homing) and you don't want any action performed on them until the
task has completed.
Unblock to allow enabled SON applications to operate on the selected
cells. Disabled applications will not operate on the selected cells even if
SON is unblocked.
Displays the list of selected cells with the current activation settings for
each application and for all SON.
SON: Unblock
Affected Cells
7. Select the activation settings for each application and for SON. The SON Enable/Disable
configuration overrides the other settings without affecting them. You can thus disable SON on a
cell, but have the different applications enabled and ready for when SON is eventually enabled.
8. Click on Approve to save these settings. Alternatively, click on the X button on the window's topright corner to close the window without changing the settings.
Note the status change in the Status and All Applications Status columns.
Application
Module Activation
(on Group A)
App Settings
App Settings
App1
App2
App3
App4
App5
App6
App7
App8
App9
Enabled
Enabled
Enabled
Enabled
Disabled
Disabled
Disabled
Disabled
Enabled
On
Off
On
Off
On
Off
On
Off
On
On
On
Off
Off
On
On
Off
Off
On
Application
App1
App2
Operation
App1 will operate on Group A only.
App2 will not operate on any cell. The application is disabled.
13
2 . S e t t ing up t he AP O P roc e s s
S e t t ing up G e ne ra l Applic a t ion P a ra m e t e rs
Application
App3
App4
App5
App6
App7
App8
App9
Operation
App3 will operate on Group A in Dry mode. It will not operate on all other cells.
App4 will not operate on any cell. The application is disabled.
App5 will operate on all cells except Group A.
App6 will not operate on any cell. The application is disabled.
App7 will operate in Dry mode on all cells except Group A. It will not operate on
Group A at all.
App8 will not operate on any cell. The application is disabled.
None of the applications will operate on any cell. SON is blocked on all cells.
Parameter
Description
Globally enables/disables the application.
When disabled, the application will not
run even if it is enabled for specific cells.
After the application is turned off
(disabled), it will continue running the
feedback.
Enables/disables live run. When enabled,
the calculated changes are executed and
the commands are sent to the OSS. When
disabled, the actions are calculated, but no
commands are sent to the OSS (the
application operates in Dry Run mode).
Application Priority Sets the order in which SON applications
will run. Applications with a higher
priority will run before applications with
a lower priority.
Units
Toggle
Range
Checked
Value
Unchecked
Unchecked
Toggle
Checked
Unchecked
Unchecked
Integer
0-100
O L- 3 2 3 9 0 - 0 1
2 . S e t t ing up t he AP O P roc e s s
Re - hom ing Us ing a n E x t e rna l S y s t e m
Parameter
Create Intrafrequency Neighbor
Relations
Create Interfrequency Neighbor
Relations
Max Number of
Intra-frequency
Neighbor Relations
Max Distance for
Neighbor Relations
from Indoor Cells
Max Distance for
Neighbor Relations
from Outdoor Cells
Max Weight for
Neighbor Deletion
Work on Locked
Candidate Cells
Description
When checked, intra-frequency neighbor
relations will be created for new cells
Units
Toggle
Toggle
Range
Checked
Unchecked
Checked
Checked
Unchecked
Value
Checked
Km
15
0.5-30
15
0.1-5.0
0.3
Checked
Checked
Unchecked
15
2 . S e t t ing up t he AP O P roc e s s
V ie w ing a nd Cha nging t he O pe ra t iona l S t a t us of Ce lls
O L- 3 2 3 9 0 - 0 1
2 . S e t t ing up t he AP O P roc e s s
V ie w ing a nd Cha nging t he O pe ra t iona l S t a t us of Ce lls
operational status. Select a new status from the New Operational Status list.
7. Click Apply. The new operational status is applied to the selected cells.
Figure 9: Change Operational Status
Status
New
Initialize
Exist
Rehome
Rehome source
Description
A newly identified cell. These are new cells that have been added to the OSS and
have not been added to the SON database before. The APO Plug & Play feature
will operate on new cells in its next cycle and create neighbor relations for them.
Cells on which the APO Plug & Play feature has started working.
Cells that are in the SON database and APO has finished working on them.
During the rehoming process, this status identifies the new cell (the cell in the new
location). APO will not work on these cells, so there is no need to disable APO on
cells involved in rehoming. After the rehoming is complete, the status changes to
"exist".
During the rehoming process, this status identifies the cell that is being rehomed
17
3 . Monit oring t he Q ua nt um S O N Ac t iv it ie s
V ie w ing a nd Cha nging t he O pe ra t iona l S t a t us of Ce lls
Status
Obsolete
3.
Description
(i.e. the cell in the old location). APO will not work on these cells, so there is no
need to disable APO on cells involved in rehoming. After the rehoming is
complete, the status changes to "obsolete".
Cells that exist in the database, but no longer exist in the OSS (possibly as a result
of rehoming). These cells are kept in the database to enable monitoring of KPI
history. None of the SON applications will operate on these cells.
O L- 3 2 3 9 0 - 0 1
3 . Monit oring t he Q ua nt um S O N Ac t iv it ie s
Ana ly zing a n AP O Ac t ion
Change the date range - this affects both the chart display and the actions displayed in the actions
table.
Display actions by application - this affects only the actions table.
Display only specific network elements - this affects both the chart display and the actions displayed
in the actions table.
View the OSSchanges for a selected action set and the affected cells by clicking on the Info icon.
View the OSS changes on the KPI chart by clicking on the Graph icon.
19
3 . Monit oring t he Q ua nt um S O N Ac t iv it ie s
Ana ly zing a n AP O Ac t ion
Ex ample
Figure 12: APO Action Analysis Example
O L- 3 2 3 9 0 - 0 1