Sie sind auf Seite 1von 85

Configuration Management

NetAct Application Delta with OSS (NetAct 8)


OS0588-80A

OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Nokia Solutions and Networks Academy

Legal notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Solutions and Networks training
documentation, product documentation and slide presentation material, all of which are
forthwith known as Nokia Solutions and Networks training material, are the exclusive
property of Nokia Solutions and Networks. Nokia Solutions and Networks owns the rights to
copying, modification, translation, adaptation or derivatives including any improvements or
developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend,
modify, develop, license, sublicense, sell, transfer and assign the Nokia Solutions and
Networks training material. Individuals can use the Nokia Solutions and Networks training
material for their own personal self-development only, those same individuals cannot
subsequently pass on that same Intellectual Property to others without the prior written
agreement of Nokia Solutions and Networks. The Nokia Solutions and Networks training
material cannot be used outside of an agreed Nokia Solutions and Networks training
session for development of groups without the prior written agreement of Nokia Solutions
and Networks.

2 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Module Objectives
At the end of this module the student will be able to:
• List the major functional changes in Configuration Management and
Optimization from OSS5 to NetAct 8.
• Explain the meaning and purpose of Configuration Management.
• List the NetAct Configurator applications and explain their purpose
and usage for network management.
• Use the Configurator tools for executing basic tasks for configuration
upload, actual plan management, plan management plan
provisioning and data export.
• Use the Configurator tools for upload, check and export of HW
Management information.
• Describe the network role of Optimizer.
• List the most important functionalities in Optimizer for NetAct 8.

4 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Module Content

 Configurator Functional Changes from OSS5


to NetAct 8

 Configuration Management in NetAct

 Configurator Applications

 Configurator Basic User


Tasks

 Optimizer

5 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Functional Changes from OSS5 to
NetAct 8
OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.
Hardware Manager Merged to CM applications
Main functionality Main changes OSS5 – NetAct 8

• Consolidated hardware configurations • Extended NetAct Configurator UI with


view of different vendors/domains Network Element hardware data
• Single or scheduled hardware • Significant increase in processing of
configuration data upload configuration objects
• Single or bulk hardware configuration • Single and mass hardware
data export to XML and CSV files for configuration upload
further processing • Single and mass export in CSV and
• Sophisticated search engine XML file format
• Hardware configuration change history • Hardware data searching
• Hardware configuration change history

Benefits

• Automatic or manual collection of network elements hardware configuration data


• Centralized place for hardware inventory information
• Keep data up-to-date by support scheduled hardware configuration upload and support for
hardware change notification

7 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Hardware Manager Merged to CM applications
Merged Configuration View

NetAct 8 Configurator:
Hardware Management merged
to Configuration Management
applications.

OSS5 Hardware Browser / TLUI:


Different tools/scripts for upload
and browsing

8 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Hardware Manager Merged to CM applications
Single or bulk upload of HW configuration data bundled with CM upload

NetAct 5:
Upload via Top Level
User Interface.

NetAct 8:
Single or bulk HW
configuration upload.

9 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Hardware Manager Merged to CM applications
Synchronization status

OSS5 TLUI:
Synchronization status in
different application.

NetAct 8:
Synchronization status available
in CM Operations Manager.

10 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Hardware Manager Merged to CM applications
Single or bulk export of hardware configuration data to XML and/or CSV

NetAct 8 Configurator:
Support for single and multiple
hardware configuration export to
CSV and XML file format.

OSS5 Hardware Browser:


Support for export of hardware
configuration data for single
element(s) in CSV format.

11 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management in
NetAct
NetAct 8

OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Overview

Configurator gives access to real


time network configuration data
and provides tools to manage the
Plan Import network configuration
Actual / Reference
Config export

Actual Config Plan Actual Config


Upload Provisioning Upload

13 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
Overview
Configuration Management
NetAct Configurator is a component in the scalable NetAct framework for operating mobile
networks. Configurator gives access to real-time network configuration data and provides tools to
manage network configuration.
The main functionalities of NetAct Configurator are:
• Storing the network parameters in the database
• Data exchange with external tools
• Setting, modifying, viewing, and comparing network configuration data
• Mass modification on the network: integrating sites, extending and optimizing the network
• Tuning of the network configuration
The network architecture can be functionally grouped into the access network and the core network.
The access network handles all radio-related functionality while the core network is responsible for
routing calls and data connections to external networks. With NetAct Configurator, the access
network and core network are managed in a centralized way.

14 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Overview

Why do we need a Configuration Management


System ?

Because:
• We need to know the actual
configuration of network
=> Upload Upload Configure

• We need to plan configuration


changes to network
=> Configure
• We need to download the Provision
changes to the network
=> Provision

15 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Core Networks
Single data storage Data analysis and
• Actual and planned data Planning Center / Network Wide CM auditing
• Run consistency checks
Data editing Northbound interface • Define user-specific consistency
• Display actual parameter values NetAct checks
• Create, modify and delete plans • Reference data management
• Direct send to network Configurator • CM Auditing – Policy based
parameter management
Data Data Data
Data management • Compare plan with actual CM
editing management analysis data
• Upload network element data
• Compare NE-NE actual and
• Provision plans to network
reference configuration
• NE command management Automation Automation
DB • CM History --- full access to
• Multipoint Configuration historical configurations all NEs at
Assistant any given time
• Control data exchange via • Provides possibility to compare
northbound interface data at two different time intervals
• Keep track of executed and
LTE-TDD /
scheduled operations GSM GSM-R WCDMA I-HSPA LTE-FDD Northbound interface
• Automatic backup plan creation • Import plans / templates
for fast rollback
• Export planned / actual /
Core Multi-
Packet vendor template / reference configuration
Automation Rel. 4 Core SDM IMS
integration • Support of XML, CVS and XLS
• Use case specific workflows (MSSPLANT Databuild) file
• Scheduled jobs, Wizards formats
• Auto-configuration workflows

16 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Core Networks
Configuration Management

NetAct 8 Configurator provides view for configuration management data and workflows, with features such as:
Powerful set of tools: from the smallest change to large network retunes, Configurator tools allow end users to
proficiently and accurately perform network configuration management tasks in a systematic and efficient
manner. This provides major OPEX savings while improving the overall quality of the network. In general, the CM
applications are the same than available in NetAct OSS5 releases.
End to end coverage of network management use cases, e.g.:
• Consistency check and audit of the network
• In practice any user defined task sequence is a candidate for automated single operation with CM Workflow
Manager
Single standard integration point for other OSS systems:
• Configurator provides standard interfaces (e.g.: Bulk CM XML and CSV) for both import and export directions.
Other OSS systems do not need to care anymore about the variety of proprietary protocols used by its
different providers
Continuously developing Multi-Technology features and synchronized support also with NetAct OSS5.x systems:
• New technologies and adaptations developed on top of NetAct 8 (i.e. direct integrations to network elements)
• Existing technologies and adaptations from NetAct OSS5.x (i.e. OSS interface based integrations)
All the Configurator product functionalities are designed to meet the challenges in following a daily network
planning cycle. This is the basis of Configurator and for all different concepts and features presented in the
configuration applications.

17 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Core Networks: Supported NEs

MSC Server MGW Packet Core / CDS


Releases Releases (Command Manager) (Command Manager)
• M15.0 , M15.1 • U5.0 EP2 • Flexi NG 3.0. Flexi NG 3.1 • M15.0 , M15.1
• M16.0 (ATCA), • U6.0 • Flexi NS 3.0 • Md 16.1
• M16.0 EP1 • Ui5.0 • Flexi NS SGSN SG8.0 DX (CD2, • Md 16.1 EP1
• Ma16.1 (ATCA ) • Ui5.0 CD3,CD3.1), ATCA (CD2, CD3,
EP1 CD4
• Md16.1 (DX)
• Ui5.0 • Flexi NS SGSN SG9.1 (DX), 9.2
• Md16.1 EP1 (DX)
(DX) EP2
• Flexi ISN 5.0 ..5.0 CD7
• M16.2 (ATCA,
DX)

18 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Radio Networks
Automation
Single data storage • Use case specific workflows
• Actual and planned data Planning Center / Network Wide CM • Scheduled jobs, SON
Northbound interface Scheduler
Data editing • Auto-configuration workflows
• Display actual parameter NetAct • Rehosting tool with Wizard
values • Site Templates
• Create, modify and delete plans Configurator
• Direct send to network
Data Data Data
Data analysis and
editing management analysis auditing
Data management • Run consistency checks
• Update via network element • Define user-specific
events or upload network
element data Automation DB Automation consistency checks
• Reference data management
• Provision plans to network
• Configuration history
• Control data exchange via
northbound interface • Policy-based parameter
management
• Keep track of executed and
scheduled operations • Compare plan with actual CM
GSM GSM-R WCDMA I-HSPA LTE data
• Automatic backup plan creation
• NE command management Northbound interface
(Core)
Core Multi- • Import plans / templates
• Multipoint Configuration Packet SDM IMS vendor
Rel. 4 Core
Assistant (Core) integration • Export planned / actual /
reference / template
configuration

19 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Radio Networks: Software compatibility

• GSM
- RG20 EP1, RG20 EP2, RG30, RG30
EP1, RGR20
• WCDMA
- RU30 EP2, RU40
• LTE
- RL40, RL50, RL35TD

20 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Quiz 1
Configuration Management
• What is the purpose of NetAct
Configurator?

21 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Basic Concepts
Network Resources MANAGED OBJECTS
Network resources are represented as managed
objects in NetAct. Configurator supports managed
object classes in GSM, WCDMA, I-HSPA, and core
network.

CM Configurations CONFIGURATION TYPES


The actual configuration refers to the current
configuration of the managed network. There is only
one actual configuration in the system. The changes
to be executed on the actual configuration are
implemented using plans. A plan contains a
configuration change that will be performed or has
been performed to the network. TEMPLATES

Templates
When the network is expanded and optimized,
templates offer ready-made parameter sets for
defining new managed objects in the network.
Templates allow using patterns in object creation
and decrease manual typing. CONSISTENCY CHECK RULES
Parameters Consistency
The consistency of the network parameters is vital
for the optimum functioning of the network.
Configurator provides rules and tools to check the
consistency of the actual configuration or a single
plan.

22 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
Basic Concepts

NetAct Configurator concepts


The Configurator applications in NetAct use a group of basic concepts which allow to describe the
network and the actions that those tools execute on it.
The Network resources are represented as managed objects in NetAct.7 Configurator supports
managed object classes in the IMS and SDM parts of the core network.
The actual configuration refers to the current configuration of the managed network. There is only one
actual configuration in the system.
The changes to be executed on the actual configuration are implemented using plans. A plan contains a
configuration change that will be performed or has been performed to the network.
The reference configuration is a data set that describes the desired or the target configuration of the
network for comparing it with the actual configuration due to consistency checks.
When the network is expanded and optimized, templates offer ready-made parameter sets for defining
new managed objects in the network. Templates allow using patterns in object creation and decrease
manual typing.
The consistency of the network parameters is vital for the optimum functioning of the network.
Configurator provides rules and tools to check the consistency of the actual configuration or a single
plan.

23 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Basic Concepts: Managed Objects
Topology
Managed Object (MO) The Managed Objects are arranged in a
Refers to an abstract representation of a hierarchical structure according to the
network resource, either a physical or Object Model.
logical entity in a network managed by
NetAct.
Distinguished Name
Managed Object Class (MOC) Distinguished name uniquely identifies an MO
Defines the characteristics of the MO, in NetAct Topology.
such as its parameters, operations, The DN consists of relative distinguished
notifications, and behavior. Class names of its superiors in the topology,
contains information on: separated by a slash (/), starting from the root
• the network resource type (for object and advancing towards the managed
example, BTS), release (for example, object that is identified (for example, PLMN-
PLMN/BSC-2318/BCF-1/BTS-3).
S14), parameter characteristics.

Site
Maintenance Region
The SITE object is a way of storing the geographical
location of the managed objects in GSM, WCDMA, I- Group of network elements and their
HSPA, and core networks. Site objects are created, subordinate managed objects, which are
deleted, and modified with CM tools, which also managed by a certain part of an organization.
provide user interface for assigning and removing Maintenance regions are modified by
managed objects in a site. assigning and removing managed objects.

24 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
Basic Concepts: Managed Objects

NetAct Configurator concepts - Managed Object


The commonly used definition of Managed Object is also applicable within the context of Configurator:
A Managed Object is understood as an abstract representation of a network resource, where the
resource can either be a physical entity or a logical entity.
A Managed Object Class defines the information model of a network resource type (e.g.: NT HLRFE
information model). Information model in this context includes:
• Overall information about the network resource (network resource type name, e.g.:
“NTHLRFE”, network resource model release, e.g.: “Release 5.0”…)
• Parameter information about the network resource (parameter name, parameter description,
parameter data type, parameter range, etc.)
A Managed Object Instance represents a specific network resource (e.g.: NTHLRFE installed in site x
in region y). The representation of the specific network resource means:
• Identification information about the specific network resource (e.g.: fully qualified distinguished
name, supplementary identification parameters such as Global ID,…)
• Parameter value data about the specific network resource

25 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Basic Concepts: Configuration Types

26 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
Basic Concepts: Configuration Types
NetAct Configurator concepts – Configuration Types
In the context of Configurator, the configuration is a set of Managed Objects. Configurator supports the following types of
Configurations:
• Actual Configuration: set of Managed Objects that represent the current configuration of the network (there is only one
Actual Configuration stored/managed in the system)
• Reference Configuration: set of Managed Objects that represent the desired configuration of the network (there is only one
Reference Configuration stored/managed in the system)
• Plan Configuration: set of Managed Objects that represent a configuration change that will be performed or has been
performed to the network (there is no theoretical limit as to how many Plan Configurations are stored/managed in the
system)
• Planned Configuration: set of Managed Objects that represent what would be the status of the network if a certain Plan
Configuration would be implemented (Planned Configurations are not stored as such in the system, but instead they are
calculated on real time)
Actual configuration
The actual configuration comprises of the following:
• Managed objects, location in topology, and object identification in topology database.
• Parameter values in Configurator database:
• Parameters with interface from Configurator to network element.
• Non-network parameters and non-network objects without a management interface from Configurator.
• Object administrative state (locked, unlocked) in topology database.
• Object state (operational, non-operational) in topology database.
Non-operational objects are stored in the topology and they are not part of the active network. The non-operational objects
may have been planned for future use, or they have been deleted from network.

27 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Basic Concepts: Configuration Types and Network Plans
Network plans hold the configuration data for transferring an
actual configuration into a target configuration and includes
• Create operations for new object instances
• Modify operations for existing object instances
• Delete operations for existing object instances

Network Plan
(abstraction)
delete
new actual configuration
actual configuration create
modify (target configuration)

Plan Provisioning

Network Element Network Element

28 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
Basic Concepts: Configuration Types and Network Plans
Configuration Management – Configuration Types and Network Plans
Reference configuration
The reference configuration is stored in the system as a separate data set from actual and planned
configurations. Reference configuration can describe the desired configuration that should be kept in
the network, but it can also describe the target configuration of the network. For both cases it is
possible to find out if there have been changes in the actual configuration in the network, and if the
changes are valid and expected.
Plans
A plan is a configuration containing a set of modifications f the actual configuration. Plan contains
only modifications and it can be viewed on top of the actual configuration.
Plan can include the following types of modifications:
• Add new managed objects with mandatory parameters (create operation).
• Remove an existing managed object (delete operation).
• Modify parameters (including administrative state) of an existing managed object in a certain
configuration (update operation). The distinguished name or version cannot be modified using a plan.
Modifying parameters of some future version of managed object in target configuration is not
possible.

29 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Basic Concepts: Actual Configuration vs. Planned Configuration

Actual configuration is a view of the live network as it exists


currently. You can modify it directly, either one object or several
objects at a time, and is designed to make rapid changes to the
network:
• There is no backup or way to fix any mistakes
• There is no way to check your changes

Planned configuration is designed to make changes to the


network, whether big or small:
• Allows you to check your changes
• Allows to reverse any mistakes and always have a backup
• Allows to schedule work during the maintenance window

30 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Basic Concepts: Templates
A template is a set of default values that are applicable to a
specific Managed Object Class.

When parameters have the


same values in different
Managed Object Instances
across the network.
When enforcement of a specific
parameter policy is required.

System Template is a set of default values that represent


the factory presets. There is one System Template per MOC
and it is not editable

User Template is a set of default values that represent default values applicable
under user defined conditions, e.g.: there can be one user template that defines
the default values applicable to a rural WBTS, while there can be another user
template that defines the default values applicable to an urban WBTS.

31 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
Basic Concepts: Templates
Configuration Templates

In the context of Configurator, template is a set of default values that are applicable to a specific Managed Object
Class. Templates are useful in several contexts:
When parameters have the same values in different Managed Object Instances across the network. In this case the
activity of populating such parameter values is extremely simplified, as the only required activity is to fill a template and
then apply the template to the needed Managed Object Instances
When enforcement of a specific parameter policy is required. In this case templates can be filled with the policy
requirements, those templates then are audited against the Actual Configuration and deviations are reported
There are two different types of Templates in Configurator:
System Template: is a set of default values that represent the factory presets. There is one System Template per
Managed Object Class and it is not user editable
User Template: is a set of default values that represent default values applicable under user defined conditions, e.g.:
there can be one user template that defines the default values applicable to a rural BTS, while there can be another
user template that defines the default values applicable to an urban BTS. There is no theoretical limit to the number of
User Templates stored/managed in the system.
Using templates
A template is primarily used to define an initial parameter set for a new managed object by assigning a template to the
object. The user can define assignments for each planned object manually. Assignment information can also be
imported as part of the plan into NetAct Configurator. The assignment is shown as the name of the template in user
interfaces. Values from the assigned template for new managed objects are automatically utilized by CM Applications
the same way as they would have been defined directly in plan.

32 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
Basic Concepts: Rules and Checks
New erroneous or incomplete plan might
Upload Configure
harm network functioning after activation to
Provision
network elements
many types of constraints and
dependencies need to be noted Plan
and taken care of.

The sets must contain an


appropriate selection of Configurator
rules that can be Predefined Rule Sets
Check Correct
meaningfully executed at
the same time User Defined Rules

Target of the Checks

Erroneous objects and violations


Actual Planned
Reference Configuration
are shown to the user in the user
Configuration
Configuration interface for corrective actions.

33 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
Basic Concepts: Rules and Checks

Configuration Rules and Checks


During network configuration planning and plan data building, many types of constraints and
dependencies need to be noted and taken care of. The risk that new erroneous or incomplete plan harms
network functioning after activation to network elements needs to be minimized. NetAct Configurator rules
and check functionality by CM Analyser can be used for that purpose.
Configurator contains predefined rule sets that can be used in different procedures with network
configuration. Also new rules can be added and tailored into the system by the user. Rules can be
collected into rule sets. The sets must contain an appropriate selection of rules that can be meaningfully
executed at the same time. Rule or rule set execution is called a check in CM Analyser.
The target of the check can be an actual network configuration, reference configuration or a plan that is
edited or built using, for example, CM Editor.
Erroneous objects and violations are shown to the user in the user interface for corrective actions. In some
cases, the correction or addition is straightforward, and CM Analyser is able to add automatic corrections
to the plan.

34 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Quiz 2
NetAct Configurator Concepts
• What is a plan in the Network
Configuration?
• What is the difference between the actual
plan and all the other plans?
• How does the system database get the
information for the actual plan?

35 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications
NetAct 8

OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications
Architecture
Northbound Mediations

•Exchange information with other OSS


Applications systems Adaptations

CM Operations Manager CM Reference Optimizer Information Models

•Perform micro-workflows (e.g.: •Audit the differences between actual • Visualize and optimize the network •Customizable network resource
upload, download, import, export, plan and reference configuration in the context of a geographical information models
actual compare) •Align differences to either actual or information system
•Perform macro-workflows (e.g.: re- reference configuration
hosting) Workflows
•Report on-going and executed
•Customizable micro and macro-
workflows
workflows

CM Editor CM Analyzer CM Workflow Manager


Rules
•Visualize the managed configurations •Check consistency of the managed •Create custom operations
•Single and mass edit the managed configurations •Create user interfaces for workflow •Customizable consistency
configurations •Enforce parameter policies data checks

Actual Configuration Reference Configuration Plan Configurations Repository

Southbound Mediations

•Exchange information with network


elements/element management
systems

37 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications
CM Editor
• Editing & browsing through
actual and planned
configuration data
• Integrated plan management
– For all network elements
(NTHLRFE, ONE NDS, MGW,
etc.)
– Parameter mass modification
– Advanced search
– Template management
• Operator can compare
between actual and planned
parameters while editing
• Find objects that match
specified criteria with
possibility to set new values
only to these objects
• Templates to minimize user
errors

38 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications, cont.
CM Editor
CM Editor
CM Editor provides intuitive parameter editing, both in minor parameter modifications and
mass modification purposes. CM Editor functionality includes the following operations:
• Managing plans: Creating, modifying, and deleting plans
• Creating, and mass creating of managed objects, editing, and mass editing parameter
values of managed objects
• Managing the actual configuration:
• Viewing actual network configuration.
• Managing administrative states of the supported core network objects
• Managing the reference configuration
• Managing planed and actual configuration with Table Editor
• Managing templates: Creating and deleting templates, Editing templates,
• Managing maintenance regions
• Visualization for:
− Locked objects
− Related objects

39 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications
CM Analyzer • Consistency checking for
– Planned and actual
configurations
– Parameter values
– Dependencies within a network
element and between network
elements
– Overview of default rule check
– Rule check result display
• Possibility to define operator-
specific consistency checks
• Scheduled start of
consistency checks
• Automatic corrections of
inconsistencies
– i.e. adjacency parameters
are corrected automatically
based on target cell
parameters
• Detection of planning errors
including human errors at an
early stage
• Higher quality of network
plans

40 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications, cont.
CM Analyzer

CM Analyzer
CM Analyzer is the tool for checking the consistency rules in radio network and
core network parameters and managed objects.
CM Analyzer functionality includes the following operations:
• Checking radio network and core network parameters and managed objects,
and ensuring that the parameters are defined according to consistency rules
• Checking for discrepancies in actual configuration, planned configurations and
in reference configuration
• Auto correction: defining a rule for automatic inconsistency correction

41 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications
CM Operations Manager

Efficient plan-based
management for large networks
• Plan provisioning to network:
Prepare, pre-activate, activate,
fallback
• Import plans from NSN or 3rd
party planning systems
• Export actual data and plans
• Compare planned with actual data
Keep NetAct Configurator up-to-
date with network element
• Upload actual configuration
Operations Management:
• Scheduling
• All operations under control Real-
time feedback on progress of
operation
• History information on executed
operations

42 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications, cont.
CM Operations Manager

CM Operations Manager
The overall function of the CM Operations Manager is to transfer configuration data between
planning tools, NetAct Configurator, and the network. It provides both real-time feedback and
history information on the operations. CM Operations Manager functionality includes the following
operations:
• Provisioning plans to the network:
• Preparing, pre-activating, activating. Validating BSC. Queuing for RNC provisioning and BSC
file-based provisioning , Scheduling provisioning operations, Generating and activating
backup plans.
• Managing actual configuration:
• Uploading actual configuration, Scheduling upload operations, Exporting actual configurations
• Managing plans:
• Creating and deleting plans, Importing and exporting network plans, Comparing plans to
actual configuration and reporting the differences, Validating plans against actual or reference
configuration
• Managing reference configuration:
• Importing and exporting reference configuration, Creating plans on top of reference
configuration
• Managing templates: Deleting templates, Importing and exporting templates
• Managing the operation execution with the workflow engine
• Visualizing MML commands for the supported core network elements
• Executing MML commands and MML command files for the supported core network elements

43 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications
CM Reference
Maintain Ideal Configuration

• Ideal network configuration Actual data upload Audit differences for


as reference configuration finished actual and reference

• Statistical summary of Generate correction


plan to align NW
actual network and
Provision plan to
reference configuration NW

• View differences (delta)


• Implement change in actual
network configuration, or
accept difference to
reference configuration
• Full control about change
process
• Backup of approved
network configuration

44 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Applications, cont.
CM Reference

CM Reference
The CM Reference application is used for managing the reference configuration.
With CM Reference you can, for example
• initialize the reference configuration
• generate and analyze deltas
• commit the needed changes in the actual or reference configuration
• Delta handling in CM Reference involves various steps. In the first stage, you
need to initialize the reference configuration. After this, deltas are generated
for visualizing and analyzing. You can select the deltas for a closer analysis
and decide on the necessary actions to correct them. These corrective actions
are called alignments. Updates can then be implemented either in the actual
configuration or in the reference configuration.

45 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Quiz 3
NetAct Configurator Applications

• What is the difference between CM Editor and


CM Operations Manager?
• What CM application would you use to make a
direct change to the Actual Configuration?
What tool should you use to provision a plan
to change the Actual configuration?
• What is the main purpose of the CM Reference
Application?

46 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configurator Basic User Tasks
NetAct 8

OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
General Data Flow

Configurator Applications
CM Editor 2 Create and edit plans
2 4

CM Analyzer Check plans NetAct


3 3 Database

CM Operations Manager

1 5 4 Make corrections to
plans

1 NE
5
Upload Actual NE Database Provision
configuration plan to NE

48 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
CM Operations Manager: Actual Configuration Upload

1 2

49 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
CM Operations Manager: Actual Configuration Upload
Uploading actual configurations
In the Upload dialog you can upload actual configurations and schedule an upload
operation.
To upload actual configurations
1. From any view, click Upload > New Upload....The Upload dialog opens.
2. In the Upload dialog, select the target objects you want to upload under the tabs. Under
each tab there is a tree listing the possible objects you can select.
Note: If you do not have the correct license, some upload options are disabled.
3. The selected objects are shown in the Scope of Upload pane.
4. In the Upload Information pane, enter a name of the upload operation (optional).
5. In the Upload Information pane, enter a description of the upload operation (optional).
6. In the Upload Information pane, select the level of information shown in the Feedback
dialog.
7. To start the upload, click Start.
8. A confirmation dialog opens. Click Yes.
The Feedback dialog opens and the status of the upload operation changes to Started.
You can monitor the progress of the operation on the Operation History tab or the
Feedback dialog.

50 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
CM Editor: Display of Current Configuration

Actual Configuration:
• The parameters of a
selected MOI are
displayed alphabetically
in a list
• Several MOIs can be
presented in a table.
• The views can be
customized regarding
displayed parameters
• Online help for all
parameters

MOI - Managed Object Instance

51 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
CM Editor: Display of Current Configuration
Viewing actual managed objects
Actual configuration contains actual values from the network. These values can be edited to change
actualls in the network or they can be used as planned values.
The Actual Configuration node contains all objects in the topology, both operational (actual objects)
and non-operational objects that exist in the topology. You can view actual parameter values only for
the operational objects. Note that the MO classes and their parent objects that are selected in the
Editor View are shown in the navigation tree under the Opened Plans node.
To view actual managed objects
1. Select Target Configuration > Actual Configuration.
2. Expand the Actual Configuration node in the navigation tree.
3. A list of root objects is shown. They are sorted alphabetically in ascending order based on class
and object instance.
4. Expand the root objects.
5. A list of managed objects is shown.
When expanding the managed objects, the hierarchy is shown first. The names of the managed
objects are fetched separately and added to the tree when they are available.
Select the objects that you want to view.
The Parameters by Actual Managed Object view opens. Here you can see the values for the actual
managed objects in the network.

52 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Quiz 4
NetAct Configurator Applications
• Upload the configuration for one of the Managed
Objects in the system by using the appropriate
Configurator Application.

• Please see the procedure in the chapter material.


For additional information see the Online help for
this application

53 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Quiz 5
NetAct Configurator Applications

• Use the appropriate tool of NetAct Configurator to


revise the configuration for the Managed Object you
selected in Quiz 3.
• Please provide a list of some of the configuration
parameters for this MO.
• For additional information, please see the Online
help for this application

54 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
CM Operations Manager: Actual Configuration Export
Exchange actual and planned configurations
with external planning systems
Export of configuration data:
 CSV format
 XML format (RAML2)
Export granularity:
• Single MOC or selected MOCs or all
MOCs of a single NE
• All MOCs of a set of NEs
• All MOCs of all NEs
The CSV export enables selection of
specific parameters and parameter ordering
according to user-definable profiles

Import of configuration data:


 Identical format as for export
 GUI option with same granularity for
data import as for the data export
 Imported data is handled as planned Integration of Configurator into a planning
configuration system or network-wide configuration
 Imported data as delta import management system

55 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
CM Operations Manager: Actual Configuration Export
Exporting Configuration
From the File menu, open the Export dialog.
In the Scope of Export pane, click Options. The Export Options dialog opens.
To select Actual or Reference Configuration
From the Export drop-down list, select either Actual Configuration or Reference Configuration.
The plan is exported on the top of actual or reference configuration.
To select Export format, profile file, and parameters
From the Export Format drop-down list, select either RAML2.0 or CSV (comma-separated values).
If you have selected RAML2.0, Profile File is not active.
If you have selected CSV, click the ... button next to the Profile File field.
A file selection dialog opens.
Select the profile that you want to use. For information about profile files, see Working with profile files
and CSV data files in CSV Interface for Configuration Management Data.
In the Export pane, select the parameter values that you want to use.
Internal values - These are values used in the database.
Or
UI values - These are the values that you can see in other applications (for example, CM Editor).
The selected format will be used for the export, and for CSV export, the selected profile file and
parameters will be used.

56 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
CM Editor: Display of Plans

Plans are populated


through
• Copy from actual
configuration
• CM Operations
Manager feature
'Import via
Northbound I/F‘
• Editor features are
provided

MOI - Managed Object Instance

57 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
CM Editor: Display of Plans
Opening plans
When you open a plan, it is shown in the navigation tree under the Opened Plans node.
To open a plan
Choose one of the following alternatives:
Click Plan > Open Plan.
Or
Right-click the Opened Plans node in the navigation tree and select Open Plan from the pop-up
menu.
Or
On the toolbar, click the Open Plan icon.
Or
Try to expand the Opened Plans node when it does not contain any opened plans.
The Open Plan dialog opens containing a list of plans in the NetAct Configurator database. The
plans are sorted alphabetically in ascending order based on the plan name. The table also contains
the plans you have already opened in the navigation tree.
The table contains the following information on each plan:
• Plan
• Owner
• Created
You can filter the listed plans by selecting the check box on the left and entering the filter criteria in
the Filter Plans by: field.
58 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.
Configuration Management
CM Editor: Mass Parameter change and Plan Creation

Parameter values can be changed for all selected MOIs in the table view:

Mass parameter changes also


through 'search & modify' feature

• Possibility for complex search criteria


• Search criteria used as criteria for
mass modification cases

59 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


NetAct Configurator Applications
CM Editor – Plan Details

Operations are indicated by icons


and colors

Object to be deleted

Object to be modified

Object to be created

60 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Quiz 6
NetAct Configurator Applications

• Use one of the tools of Configurator to see the plans


created in the system.
• Open one of those plans and provide a list of
some of the configuration changes. What MOs
are involved?

61 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
CM Analyzer Usage

Check procedure:
1. Start a new check
2. Select target for the check
(plan/ actuals)
3. Select one or several rules
for the check
4. Define post-check activities
5. Run the check
6. Analyze the results

High flexibility to check configurations

62 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
CM Operations Manager: Plan Provisioning

1 Open he Provision Dialog by selecting the Plan in the Plans list on


the CM Operations Manager  pop-up menu or by selecting
“Provision” from the Operations Menu

63 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
CM Operations Manager: Plan Provisioning
Provisioning plans
You can prepare a plan, provision a plan, schedule a provision operation, and create a backup plan in
the Provision dialog. The provisioning operations are: Activate , Pre-Activate , Activate Pre-Activated
Plan, Validate
Plan preparation can be run as part of the provisioning operation or it can also be run before
provisioning as a separate operation. In the Plans list, you can see the preparation status for your plan.
It is recommended that the entire plan is provisioned as one operation.
To prepare a plan
1. In the Plans tab, select the plan you want to prepare.
2. Open the Provision dialog. Click Plan > Provision.... Or
1. Right-click the plan and select Provision... in the pop-up menu. The Provision dialog opens.
3. In the Provision pane, enter an optional name and description for the provisioning operation.
4. In the Operation pane of the Provision dialog, check Prepare Plan operation and uncheck Provision
operation.
Note:
The provision operation is checked by default. If the plan has not been prepared yet, the prepare
plan operation is also checked by default.
5. Click the Start button. A confirmation dialog opens.
6. In the confirmation dialog, click Yes.

The Feedback dialog opens and the status of the operation changes to Started. You can monitor the
progress of the operation on the Operation History tab or in the Feedback dialog.
64 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.
Configuration Management, cont.
CM Operations Manager: Plan Provisioning
To provision plans
1. On the Plans tab, select the plan you want to provision.
2. Open the Provision dialog. Click Plan > Provision.... Or
Right-click the plan and select Provision... in the pop-up menu. The Provision dialog opens.
3. In the Provision pane, enter an optional name and description for the provision operation.
4. In the Scheduling pane, you can define a schedule for the operation.
5. In the Backup pane, you can create a backup plan for your plan.
6. By using the backup plan, you can roll back the network changes made by your original plan.
7. The backup plan is always created for the entire plan. The default name of the backup plan is derived from the plan
name: <planname>_backup_<date>_<time>. In the default name, <date> is the current date in yyyymmdd format,
and <time> is the activation time in hhmm format.
8. Another backup plan is automatically created for a GSM plan when file-based provisioning is not used.
9. In the Operation pane, select the provisioning operation you want to run.
10. In the Scope pane, Entire Plan is selected by default. If you want to provision the plan partially, deselect Entire Plan
and select the objects to be included in the operation from each tab.
Note:
Select the Upload after activation checkbox in the Options pane to automatically upload actual configuration from
network after provisioning operation.
11. Click the Start button. A confirmation dialog opens.
12. In the confirmation dialog, click Yes.
The Feedback dialog opens and the status of the provision operation changes to Started. You can monitor the progress
of the operation on the Operation History tab or in the Feedback dialog.

65 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
CM Operations Manager: Plan Provisioning
2

You can prepare a plan,


provision a plan, schedule a
provision operation, and
create a backup plan in the
Provision dialog.

66 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management
CM Operations Manager: Plan Actual Compare
Reports differences between selected
plan and actual configuration:
• Definable feedback level
• Summary, object or parameter level
Delta plan generation & provisioning
• Update the network according to the plan
Operation supported in command line
interface
Review changes
• Checking the plan effects to the network
before provisioning the plan
Verify plan implementation
• Verifying that the plan has been
provisioned correctly to the network
Review history
• To check if something changed after the
plan was provisioned to the network

67 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Configuration Management, cont.
CM Operations Manager: Plan Actual Compare
Comparing plans to actual configuration
You can compare your plans to the actual configuration by using the Compare dialog. You can
review radio network change plans, compare reports and configuration data history as well as verify
that all planned changes were implemented correctly.
To compare plans to actual configuration
1. Click Plan > Compare. The Compare dialog opens.
2. Enter the name of the operation to the Name field (optional).
3. Enter a short description for the operation in the Description field (optional).
4. Check the Generate Delta Plan check box (optional).
When checked, a delta plan of the differences between the plan and actual configuration will be
generated. Plan will contain the actual configuration values of the differences. You can give a new
name to the delta plan, or accept the default name that is given in the Name field.
Select Level of Feedback.
The possible values are Summary, Object, or Parameter. The default value is Summary.
• Summary: Gives a short summary in a format of number of differences found from the plan against
the actual configuration.
• Object: Lists the managed object differences and number of parameter differences against the
actual configuration. One feedback summarizes non-existing managed objects in the actual
configuration or the number of differences found in parameters per managed object in the plan
against the actual configuration.
• Parameter Gives feedback about non-existing managed objects in actual configuration
and parameters whose values are different in the plan against the actual configuration.
5. Click the Start button. A confirmation dialog opens.
6. In the confirmation dialog, click Yes.
The Feedback dialog opens and the status of the operation changes to Started. You can monitor
the progress of the operation on the Operation History tab or the feedback dialog.
68 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.
Optimizer
NetAct 8

OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


NetAct Optimizer
Functionality Overview
Main functionality Main changes OSS5 – NetAct 8

• Intelligent optimization in multi- • No major changes in NetAct


vendor, multi-technology networks Optimizer functionality between
• Holistic view and full control of the OSS 5 and NetAct 8.
automated optimization network- • Support for new NSN network
wide element releases
• Automated handling of routine
tasks • Easy trial and test bed licensing
with new and simple license
• Inbuilt intellligence in analysis and structure.
algorithms
• Optimizer is compatible with NetAct
Benefits Advanced Configurator enabling
faster multi-vendor integrations
• Automated, measurement based • KPI formulas aligned with NetAct
optimization for operational GSM, reporting functionality
WCDMA and LTE radio networks.

70 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


NetAct Optimizer
Functionality Overview

Functional Changes in NetAct 8 compared to OSS5


• Data model is unified with Advanced Configurator. This is especially
important in multi-vendor cases.
• KPIs formulas are no longer hardcoded in Optimizer. Optimizer does not
calculate the KPIs any more but gets them via NetAct reporting
functionality. Any changes done to KPI formulas are immediately effective in
Optimizer.

71 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


NetAct Optimizer concept

Automation through NetAct Efficiency of shared NetAct


integration installation
• Actual CM data uploaded • Common HW, administration, look and
automatically from NetAct feel, documentation
• Automated access to KPIs • Access to optimization functionality
• Optimisation results stored as plans can be controlled
in NetAct database

Visualization and analysis Measurement based optimization


functionality • GSM frequency and BSIC plan
• Topology, parameters, KPIs in one optimization
view • Interference analysis for WCDMA
• Antenna tilt optimization for WCDMA
• Seamless adjacency and handover
management for GSM & WCDMA
• Capacity and QoS optimization
• Call Location Analysis for WCDMA

72 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Efficient visualization and analysis
NetAct Optimizer provides a wide range of efficient visualization functionality –
from network wide overview to drill down into details

• Fast overview on a geographical


map
• Problematic areas of the
network
• Latest changes
• Automated root cause analysis
• Helps in choosing the right
corrective actions
• Details in tables
• Counters and parameters
• Alarm history
• Call specific details

73 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Common functionality for GSM and WCDMA
Geographical Visualization and Graphical adjacency management
Analysis • Actual adjacencies on map
• Manual or automated distance based
• KPIs and parameters management of all adjacency types
automatically on map • Border area adjacencies
• Customized quality thresholds • Parameters from templates
automatically
• Scrambling code collision check and
correction

Powerful parameter
management with Browser
• KPIs and parameters in the same view
• Dedicated, customized views per task Management of plans between
• One-by-one or mass editing of NetAct Configurator and
parameters NetAct Optimizer
• Change tracking

74 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Measurement based GSM optimization

1 Interference Matrix generation


based on mobile measurements BSC

2 Interference root cause analysis


Serving
BTS

3 Automated Adjacency
Management

4 Performance optimization

5 Capacity analysis

6 Call location analysis

75 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Measurement based GSM optimization, cont.
Interference Matrix generation based on mobile measurements
Control for the BSS measurements
Generation of interference matrix
Verification of interference validity
Interference root cause analysis
Complemented with Timing Advance analysis
Automated Adjacency Management
Automated algorithm to propose optimal adjacencies
Unused adjacency deletion based on HO statistics
Missing ones created based on interference matrix
Performance optimization
Frequency allocation based on
measured interference
All hopping modes supported
All RF hopping types supported
Allocation completed with BSIC allocation
and other parameters

Capacity Analysis
End-to-end analysis of the actual and near future capacity utilization level
Seamless view from radio to SGSN
Separately for speech and data traffic

Call Location Analysis


Geographical KPIs based on single call data
Drop call locations, locations of data traffic, certain mobile type etc
For network optimization, troubleshooting and service management

76 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Measurement based WCDMA optimization
1 Interference Matrix generation
based on mobile measurements

2 Interference analysis

3 Automated Adjacency
Optimization

4 Scrambling Code management

5 Antenna Tilt Optimization

6 Capacity analysis

7 Call location analysis

77 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Measurement based WCDMA optimization, cont.
Interference matrix generation based on mobile measurements
• Based on Detected Set Reporting (DSR) data
• Propagation delay data collected
Interference analysis
• Root cause analysis
• Complemented with Propagation Delay
analysis
• Corrective parameter modifications
Automated Adjacency optimisation
• Deletion of adjacencies based on KPIs
HO statistics
Ec/No difference
BSIC verification time
Creation of adjacencies based on
interference or KPIs
Support for all 3G and 3G-2G adjacency types
Scrambling Code management
Collision detection
Collision correction
Full allocation
Antenna Tilt Optimisation
Identification of cells, which require tilt optimization
Calculation for the new values of electrical tilt
Automated change provisioning
Feedback loop for iterative optimization

Capacity Analysis
End-to-end analysis of the actual and near future
capacity utilization level
Seamless view from radio and transmission
Separately for speech and data traffic
Call Location Analysis
78 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.
New Feature: 3G Call Location Analysis for all calls
Call Location Analysis takes network optimization below
cell level
• More accuracy in traffic analysis
• Area level performance
• User group or UE type performance per area
• Faster optimization process as drive tests are no more needed
• All active calls contribute in measurements
• All statistics available as L3 messages
• Data collected and processed centrally in NetAct
• Complemented with network information for root cause
Analysis.
• All data seamlessly available in geographical map
• Optimization actions taken immediately

Call Location Analysis collects data from


RNCs via L3 Data Collector
- Location of calls estimated with RTT based
algorithm

79 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


LTE optimization

NetAct
Optimizer supports also LTE
• Contributes in LTE Auto-configuration
SON Workflow Coordinator Optimizer assigns the initial PCIs and LTE
neighbors for the roll-out phase
Initial Optimized • Supports the roll-out phase review and
adjacencies adjacencies corrections
PCI allocation and neighbor setting checks and
corrections

GSM
Operational LTE Optimizer provides means for
measurement based optimization

As part of SON Suite:


• Contribution to ANR
WCDMA LTE
• Cell outage compensation
• Interference, coverage and capacity
optimization
• Load balancing
ANR

80 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


New Feature: Optimization of Inter-RAT (UTRAN, GERAN)
Neighbor Relations

Less OPEX: Automatic neighbour relationship evaluation

NetAct Optimizer provides the functionality Optimizer


for analyzing and managing LTE neighbors CM
PM
• Quality of handovers visualized Configurator

• Blacklisting the unnecessary neighbors


• Based on actual neighbor data
– Parameters
– HO Attempt amount
– HO success ratio KPIs
• Blacklisting can be removed later No HO
if HO KPIs for the neighbor relation
is needed

81 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


New Feature
RACH Optimization for consistency management

Automatic Optimization of RACH parameter assignments for


network performance increase
External Radio
Network Planning

Optimize PRACH / RACH parameter Optimizer


values in order to maintain
consistency of the 4 related NetAct
CM
parameters
SON PM
Coordinator

Detect / Visualize / Remove Workflow Engine


(Business Process Execution Language)

• PRACH/RACH Inconsistencies
• PRACH/RACH Collisions Topology
Manager
SW
Manager
Config.
License
manager
Inventory

Based on configuration data of eNBs


as e.g. geo-location Download dynamically
created plan file

Run on need basis or scheduled

82 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


New Feature:
RACH Optimization for consistency management
Collisions
• PRACH/RACH allocation of the cells of two eNBs within the PRACH reuse distance
collide, as e.g. Two cells within a PRACH reuse distance having the same PRACH
parameter configuration

Inconsistencies
• PRACH/RACH allocation not in line with other own cell parameters
Collisions / Inconsistencies may happen when
• eNB is/was manual configured
• eNB parameters relevant for PRACH/RACH allocation are changed after auto-
configuration process of eNB
• Change of network topology
─ Add new eNBs without auto-configuration process
─ Change of antenna location e.g.: use of distributed sites
With Optimization Conflicts and Inconsistencies are avoided that may lead to
• Decreased PRACH/RACH detection probability
• Interference to and from other cells and physical channels

83 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


New Feature:
RACH Optimization for consistency management

The optimization for the conflicts / inconsistency resolution can be applied for
• Single eNB and all its subordinate cells or individual cells
• Dedicated List of eNBs and all their subordinate cells
• all eNBs of NetAct Region

PRACH settings which shall not be changed by the optimization can be marked
by operator and especially PRACH settings which are not managed by this
NetAct regional cluster are taken into consideration without proposal to change.

It can be executed by
• Manual trigger with using NetAct user interface

84 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


New Feature: Automatic Cell Combination Assignment for
Carrier Aggregation
Carrier Aggregation (CA) feature helps operators to offer good performance
(throughput) with fragmented LTE bandwidth by providing means to use
cells from different carriers together
• 5+5 MHz (LTE1089 only) or 10+10 MHz or 5+10 MHz carriers only can offer 10/15/20
MHz bandwidth with same Customer Experience
• Carrier Aggregation 3GPP requirements are gradually implemented in NSN LTE
• LN5.0 BTS version in RL50 is the first one supporting CA for FDD, in DL direction
• In RL50 only specific inter-frequency combinations are supported

Optimizer finds the best candidate cells for combination in CA


• Based on available CM data, including cell location
• Cells with highly overlapping service area
• Optimizer sets needed parameter values for both
Primary Cell (PCell) and Secondary Cell (SCell)
• Provisioning and consistency checking done in Configurator
and eNodeB
• Run in auto-configuration and on need basis from Optimizer UI

85 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.


Seamless multi-vendor network optimization

Main functionality NetAct Optimizer is able


to manage also other
• Measurement based frequency vendors’ network
allocation elements
• GSM, WCDMA and inter-system
adjacency optimization
Integration Environment
• Scrambling code allocation
• WCDMA interference analysis and • Additional license and vendor-specific
antenna tilt optimization converter packages are needed.
• Capacity analysis • Delivery with an integration project
• GEO-located KPIs with Call • Other vendor’s data retrieved for the
Location Analysis vendor’s OSS or operator’s preferred tools
via file-based integration.
• Also vendor-specific 2G and 3G
interference measurements collected.
• Border areas can be handled seamlessly.

86 OS05885EN80GLA0 ©2014 Nokia Solutions and Networks. All rights reserved.