DATASAFE Technical Overview PDF

DATASAFE Technical Overview
Version 6.1
Author: AIRCOM International

Date: 08 October 2007
Ref:
Version: 2
Status: Final
Sec. Class: Commercial in confidence
Copyright 2008 AIRCOM International - All rights reserved. No part of this work, which is protected by copyright, may be reproduced in
any form or by any means - graphic, electronic or mechanical, including photocopying, recording, taping or storage in an information
retrieval system – without the written permission of the copyright owner.
Commercial in confidence
Contents
1 Document Control ...............................................................................................................3

1.1 Revision History ..........................................................................................................3
1.2 Reviewers ...................................................................................................................3
2 Introduction ..........................................................................................................................4
3 Product Positioning .............................................................................................................4
4 Benefits of DATASAFE .......................................................................................................5
5 Technical Solution ...............................................................................................................6
5.1 DATASAFE Overview .................................................................................................6
5.2 Architecture .................................................................................................................7
5.2.1 System Architecture ................................................................................................7
5.3 DATASAFE Functionality............................................................................................8
5.3.1 Inside DATASAFE ............................................................................................... 11
6 DATASAFE User Interface ............................................................................................... 13
6.1 Global Functions ...................................................................................................... 13
6.1.1 Filters ................................................................................................................... 13
6.1.2 Global Filters ........................................................................................................ 13
6.1.3 Help ...................................................................................................................... 14
6.2 User Functions ......................................................................................................... 14
6.2.1 DATASAFE Administrator .................................................................................... 14
6.2.2 Rules Engine ....................................................................................................... 16
6.2.3 The Rule Invoker ................................................................................................. 17
6.2.4 Data Import .......................................................................................................... 18
6.2.5 Violations Log ...................................................................................................... 18
6.2.6 Data Export .......................................................................................................... 19
6.2.7 Network Explorer ................................................................................................. 20
6.2.8 System Configuration .......................................................................................... 24
6.2.9 Parameter Modeller ............................................................................................. 26
6.2.10 Bulk Override Import ........................................................................................ 28
6.2.11 Cell Relations Manager ................................................................................... 29
6.2.12 Discrepancy Queue Handler............................................................................ 29
6.2.13 Automation Wizard .......................................................................................... 31
6.2.14 Task Modeller .................................................................................................. 31
6.2.15 Network History ............................................................................................... 32
6.2.16 SQL Custom Query ......................................................................................... 34
6.2.17 Custom Reports ............................................................................................... 36
6.2.18 Cell View .......................................................................................................... 36
6.2.19 Activity Planner ................................................................................................ 37
7 IT Specifications ............................................................................................................... 38
7.1.1 Oracle Licensing .................................................................................................. 38
7.1.2 Hardware ............................................................................................................. 38
Author: AIRCOM International Page 2 of 39

Date: 08 October 2007 Commercial in confidence
1 Document Control
1.1 Revision History

Revision Date Name Revision
Number
1 G Hayhurst
1.2 Reviewers
Reviewer Date Feedback

2 Introduction
DATASAFE is a powerful, PC-based, radio network systems configuration tool. It
enables controlled management of multi-technology, multi-vendor network system
parameters.
DATASAFE supports two main processes:
The parameter 'data fill' for roll out of new equipment
The operational configuration change management control process for
making changes and upgrades to existing equipment in the network.
It is an advanced network configuration tool enabling automated comparisons and
configurations between the live and planned network domains. DATASAFE has
been developed to meet the configuration management needs of large operators
including:
Facilitating easy tuning and implementation of cell parameter changes into
the network
Allowing parallel optimisation of the network while maintaining consistency
across any geographic partitioning of the network
Easy integration and data sharing with other network optimisation tools
such as performance monitoring, radio planning, frequency planning
Automated synchronization of the Live network to the Planned network.
3 Product Positioning
DATASAFE's product positioning is represented on the Tele Management Forum
Telecoms Operations Map (TOM) Model in the diagram below
(http://www.tmforum.org). The portion coloured in green shows where DATASAFE
sits with typical outputs servicing wider business functions indicated via the yellow
arrows and orange boxes.

Figure 1: Telecoms Operations Map (TOM)
DATASAFE supports Network Provisioning and Network Data Management. Input

to DATASAFE comes from the live connection with the Network System
Management Process area and the network planning tools.
4 Benefits of DATASAFE
Key Technical Features of DATASAFE include:
Easy to use, PC Windows network configuration management system.
Robust and scalable IT platform architecture with choice of PC or UNIX
Servers to suit IT policy and existing IT investments.
Powerful ORACLE data 'warehouse' able to maintain and retrieve network
system configuration sets for large network systems for many years.
Capacity to cater for multiple equipment vendors and network system
technologies (2G and 3G).
Ability to interface to a wide range of equipment types of different vendors
and technologies.
Option to implement MML command modules for direct implementation of
network system parameter changes.
Structured method of maintaining and managing system parameter
settings across differing network system equipment and technology layers
o Advanced Parameter Configuration - Advanced parameter alias
model.

o Parameter/command handling catering for multiple value

parameters, multiple entry nodes per parameter, multiple
commands per parameter.
Powerful data and configuration imports from file and/or database
sources.
Extensive AIRCOM software and services support infrastructure,
according to defined Service Level Agreement.
Rapid product roadmap developments and supported upgrade paths.
5 Technical Solution
5.1 DATASAFE Overview

DATASAFE is a network configuration tool that provides a streamlined mechanism
for implementing both small and large-scale planned network configuration
changes. This market-leading tool gives you the ability to manage and rapidly
tune BSS/RNS parameters, from one simple, yet empowering console.
DATASAFE consists of three main parts: A user interface, a server engine and a
relational database. The user interface consists of several modules described in
the sections that follow. The server engine has the function of automatically
updating the Live network database and synchronising the Live and Planned
networks, where allowed. Input into the DATASAFE planned database is from the
radio planning tool (e.g. ASSET), and manual data entry by the radio optimisation,
data transcript and switch engineers. Input to the live database on the other hand
is via the Switching Network Management systems.
Network configurations can be downloaded from the BSC/RNC, modified and
implemented. User-defined site configuration templates can be created to enable
the widespread configuration of large groups of cells.
The flexibility and user-friendliness of the tool allows the operator to extend the
command set of the basic application without any specialised developers and to
implement business rules specific to the operator.
The DATASAFE system is based on the following principles:
Two distinct copies of the parameters exist: the Planned Network (i.e. the
set of parameter values indicating the desired network configuration) and
the Live Network (i.e. the set of parameter values that reflect the real
network values.)
All changes made in the Planned network or imported from the Live
network are recorded within DATASAFE.
The Planned Network is always assumed to be correct when compared to
the Live Network.
All changes in the Planned Network are checked for logical errors using a
rules engine.

Figure 2: Planned vs. Live Network
The main objectives of this tool are to:

Facilitate easy tuning and implementation of cell parameter changes into
the network.
Handle parameters for many cells in a multi-technology environment.
Allow parallel optimisation of the network and still maintain consistency
across any geographic partitioning of the network.
Facilitate easy integration and data sharing with other network
optimisation tools such as performance monitoring, radio planning,
frequency planning, drive test data.
Allow automated synchronisation of the Live network to the Planned
network.
5.2 Architecture
5.2.1 System Architecture

Figure 3: System Architecture of a DATASAFE implementation
The diagram above shows the typical physical architecture of a DATASAFE

installation.
Typically, data is extracted from the BSC/RNC/Node B's at specified intervals, and
stored on the Server. A Windows Scheduled task runs on the DATASAFE
Process Machine to get these files and then automatically import them into
DATASAFE.
Ideally the Import Machine is pre-installed with Windows 2000, ORACLE (10g
recommended) and the DATASAFE Application. The Import Machine is
connected to the dedicated LAN network and the DATASAFE, ENTERPRISE
databases as well as any additional databases containing Planned and Network
data.
The DATASAFE database server can be based on either a UNIX or Windows
platform depending on the operator's preference. This would be dimensioned as
part of the solution development depending on the number of network elements,
data storage requirements and expected use of the system.
The DATASAFE Import module on the Import Machine is configured to poll and
extract Live network data daily. Planned data from the planning tool /
ENTERPRISE is extracted and imported at regular intervals during the day.
The client PCs will have the DATASAFE application installed and be able to
connect to the DATASAFE database.
5.3 DATASAFE Functionality

DATASAFE is integrated into the ENTERPRISE toolbar and is also available
Standalone.

The latest DATASAFE Administrator is a separate application launched from

outside the DATASAFE console. This application contains the following
functionality:
Setting up and configuring the DATASAFE database.
Creating the DATASAFE schema in a database.
Loading Vendor Specific Data.
Viewing Database Information.
Managing DATASAFE Users and Authority Groups.
Log Book Maintenance Tasks.
Upgrading the database for new ENTERPRISE releases and patches.
The latest release of DATASAFE contains the following functionality:

Parameter Modeller
Create and edit parameters and their attributes.
Assign advanced user privileges to parameters and nodes.
A view of both the planned and live network parameters.
Assign predefined reasons to parameters that can be selected when
changes are made to parameter values.
Preferences
OSS Preferences enable you to set preferences for the delivery of
command files and the receipt of response files. These preferences affect
all users and are stored in the database. Separate preference settings
can be created so that transcript files for a specific node/s can be sent to a
specific FTP location. Separate specific preferences can be set up for
different vendors.
Local Preferences enable you to set preferences that are user specific.
Network History
A history log which records changes from the planned and live imports,
overrides, discrepancy handling, system configuration changes and
administrator changes.
History maintenance module responsible for the maintenance of all logged
history i.e. the duration for which data should be kept and deleted.
Display of recorded network changes is also possible with Optima –
enables you to see the effect of the changes.
Cell View
Cell View enables you to view all cell information stored within DATASAFE
including planned cell definitions, neighbours/adjacencies, live logical
definitions and parameter settings.
Enables parameter overrides and cloning of cells.
Message log
This keeps a log of any actions performed in DATASAFE and displays
messages when actions are not allowed together with the module
information, date and time that the action was performed.
Violations log

A Violations log, which displays data outside the parameter ranges, as

well as data which has violated any rules.
Network Explorer
Displays the network’s relations and node hierarchy in the form of a
network node tree view.
Cell Relations
A cell relations manager to create planned cell relations within DATASAFE
as well as to monitor the relations that exist in the live network but not in
the planned, with the option to create/import them in the planned
environment.
Discrepancies Handler
A discrepancy handler indicates differences between the planned and live
environments. This includes parameter discrepancies, logical cell
definition discrepancies, neighbour discrepancies and external/outer cell
parameter discrepancies.
An MML command generator to handle discrepancies.
Automated parsing of network response files enables handled
discrepancies to be cleared without waiting for import of the latest Network
data. This is possible with the introduction of ParseResponseFile.vbs and
Responsfileparsercmd.exe. The Visual Basic Script is added in the
Windows Scheduler and runs intermittently, to parse the response files for
all discrepancies executed.
Automatic FTP of parameter changes into the live network using the
DATASAFE File Manager.
Viewing and handling Custom discrepancies.
Specific inconsistency presentations can be made within this module.
Useful for reporting on network inconsistencies and tracking roll out and
re-parenting.
Custom Reports
Allows for Queries created in the SQL Custom Query module to be
displayed in multiple tabs and exported in various formats.
Task Modeller
A Task Modeller for coding tasks associated to Logical discrepancies for
the generation of MML.
Rule Invoker
A Rule Invoker, which enables you to run consistency checks and rules on
specific nodes or cells. The rules run on the planned data values in the
DATASAFE database.
Rule Editor
Automatic checking of logical consistency of planned network parameters
and generation of the required transcripts necessary to remove the
discrepancies.
Customisable consistency checker – reducing the chances of allowing the
user to send inconsistent or invalid information into the network.
Automatic range checking of planned parameters.

Global Filter
Global Filters enabling filtering on network nodes. Filters can be applied
on a user basis.
Bulk Override Import
Allows for the bulk override of parameters on different affect levels taking
into consideration ranges and specific rules.
Activity Planner
The Activity Planner gives the network planner/optimisation engineer the
ability to pre-plan any network configuration changes and schedule these
changes to take place at an appropriate time.
Automation Wizard
Automation Wizard enables automated configuration of a number of radio
parameters.
Data Export
Flexible export capabilities to various other tools requiring radio network
parameters.
Ericsson GSM Hardware Module (Beta)
Handles Transceiver Group functionality.
Help
Screen specific help using the F1 key.
User Reference Guide.
Cygwin Import Module
The Cygwin Import module is able to transfer information from a variety of
different data sources. It is used to import data from the planned
environment and the live environment into DATASAFE.
A basic scheduler to automate the import of data as well as configuration
of the operational network.
Automated import of parameters from Asset and various other radio
planning tools.
Automated import of the live network parameters.
5.3.1 Inside DATASAFE

The following diagram illustrates the processes adopted within DATASAFE in
dealing with parameter values from the live and planned network environments:

DATASAFE Discrepancy Module
Data
Transcripts
Clears Discrepancy
Planned Network No Response
Data Live Network
Discrepancy Queue
ODBC, delimited text, Are the

XML, etc databases
equal
MML, XML,
CNA, ASCII
DATASAFE Planned Environment DATASAFE Live Environment
Are the Are the

databases databases
equal equal
New Planned Network Current Planned Network Current Live Network New Live Network
Update Update
No No
Changes to Changes to
Planned Live
Network Network
Figure 4: Inside DATASAFE
The detail in the diagram above can is described below

New Planned data
1 Planned network data is imported into a New Planned data store
2 This New Planned data store is compared with the Current Planned data
store.
3 If there are changes in the planned data these are updated to the Current
Planned data store.
4 The current planned and current live data stores are compared
New Live Data
1 Live network data is imported into a New Live data store
2 This New Live data store is compared with the Current Live data store.
3 If there are changes in the live data these are updated to the Current Live data
store.
4 The current planned and current live data stores are compared
Compare Current Planned and Current Live data
1 Data in the Current Planned data store is compared with data in the Current
Live data store.
2 The planned data store is assumed to be the correct data store
3 Differences in the planned and live data are written to a Discrepancies queue.
4 Discrepancies are resolved, creating transcripts which are sent to the live
network to update it with the changes.
5 The live network will acknowledge receipt of the transcript files and the
discrepancies will be cleared.

6 DATASAFE User Interface
6.1 Global Functions

6.1.1 Filters
Various filters can be applied to the data viewed within DATASAFE. It is possible
to filter parameters and data on the following attributes:
Vendor and vendor group
Technology
Cell / carrier layers / cell relation, sub cell and Node parameters
Parameter groups
Nodes (e.g. RNC, NodeB, MSC, BSC, region, LAC, planner etc.)
Geographical location
The other types of filters allow you to view the selected nodes or layers. If no filter
is set, where practical, all the data is presented. The applied filter is visible at all
times on the filter bar if tabs are not maximised. Filtering is an AND function of the
following:
MSC
BSC
LAC
REGION
CELL
Additionally, different parameter settings and overrides can exist on different
nodes within a network. It is also convenient to be able to search on network
entities and nodes. A node relationship filter is used for this, represented as a tree
view of the network nodes for easy navigation.
6.1.2 Global Filters

Global filters can be defined in the Global Filter dialog and applied to all modules
in DATASAFE. The Global Filter dialog enables you to create and modify filters
and apply existing DATASAFE Global filters.
There are two ways to add nodes to a filter namely, selecting nodes and sub
nodes from the network hierarchy or loading entities and nodes from a text file
source. Loading a text file is subject to the nodes and parameters existing in
DATASAFE.

Figure 5: Create a Filter on Nodes ABCMSC1 and ABCMSC2
Figure 6: Toolbar shows that a filter is applied
As in the above figure, the filter applied is visible on all the module toolbars.
6.1.3 Help
The application guides you with a description of the function of the button or tab
where the cursor is currently positioned if it remains stationary for a short period of
time. Pressing the <F1> function key opens the online help file displaying a topic
relevant to the active module, tab or field. You can also perform a keyword or
index search to navigate to the required help topic.
6.2 User Functions

6.2.1 DATASAFE Administrator
The DATASAFE Administrator module controls DATASAFE users, their access
rights, the groups they belong to, and the roles they are included in, as well as
how some of the data is stored. This module gives the DBA control over the
database and user privileges.
It incorporates the following functions:
Creation of a new DATASAFE database.
Loading of vendor specific data.
Upgrading an existing database.

User rights and authority groups for parameter privileges.

User rights and authority groups for module privileges.
Enable password expiry.
Authority groups can be set up to prevent users in one area affecting data
in other areas.
Permissions on Nodes (e.g. RNC, NodeB, MSC, BSC etc.).
A global view listing the mappings of users, authority groups and nodes
History / Log Book maintenance module.
Database Information highlights the table spaces storage and database
version number.
A utility to facilitate the release of patches.
Figure 7: DATASAFE Administrator

Figure 8: Assign System Privileges to a User
The DATASAFE Administrator is responsible for maintaining existing as well as

new data objects and entities within the DATASAFE environment. These data
objects and entities are imperative to retrieve data across DATASAFE due to the
implementation of the vertical table structures. The DATASAFE Administrator
provides a single environment for maintaining high-level data without involving the
users with the actual tables involved in all the mappings.
This serves to define new data objects/entities as well as new object types to be
used within the DATASAFE environment. Entities are accessed by a high level
description rather than by the actual mapping, as they exist in the tables thereby
providing an interface to the actual data. Applications invoke operations on the
mapping from a more abstract level but at the same time, this is more descriptive
to general users.
6.2.2 Rules Engine

Logical errors detected in the planned environment and violations of business
rules are detected with this tool. These errors can be corrected by making
changes in the applicable planning tool.

Figure 9: Rules Engine
The Rules Engine assists you in governing your network by invoking a set of rules
that are user configurable in Visual Basic Script to check for inconsistencies in
your network.
These rules are invoked/mapped to parameters and can be fired during data
imports and parameter overrides. The Rules are coded in VB Script and are easily
maintained within the tool.
A message log will provide you with details of violations or warning messages
when certain actions are performed in DATASAFE. For example, overrides on
certain parameters.
6.2.3 The Rule Invoker

The Rule Invoker enables you to run rules defined in the Rules Engine on data in
the DATASAFE database. This enables you to ensure the integrity of data
imported or entered before a rule has been defined. If a new rule is defined, you
can apply the new rule to existing DATASAFE data.
The Rule Invoker applies the selected rule to the Planned data in the DATASAFE
database. Discrepancies are re-evaluated if the rule changes the values of
planned parameters.

Figure 10: Invoking a Rule
6.2.4 Data Import

DATASAFE is able to import data from a variety of vendor network element
managers. This includes printout/XML files (such as Ericsson MML, Siemens ACL
etc.) and OSS databases (such as Nokia) for both GSM and UMTS technologies.
The DATASAFE Command Line Environment
Data Imports are done using the DATASAFE Command Line Environment (DSX).
The DSX system uses a combination of small command line programs and batch
scripts, each scheduled to periodically execute as discrete processes.
DSX makes use of Cygwin software which is compatible with the POSIX (UNIX)
standard. DSX uses XML as its text interchange format and Bash as its scripting
language - although this is not prescriptive. Non-POSIX scripting languages (e.g.
Visual Basic) can be used but are not recommended. The File System Hierarchy
Standard is used for its directory and file naming conventions. All database
access is via ODBC.
The DSX system is specifically designed to operate independently of a graphical
user interface. This allows the operator almost infinite customisation and
automation with a series of Bash windows offering a convenient and powerful
interface.
The DATASAFE DSX import is agnostic as to how DSX files are generated,
however most planned data is sourced from either relational databases or
delimited text files. Planned import scripts are scheduled to execute periodically
by the cron. Vendor import files must be converted to DSX XML before they can
be imported, this can be automated.
6.2.5 Violations Log

Planned data ranges are automatically checked when data is imported. Any
anomalies are logged in the Violations Log.

Figure 11: Violation log
6.2.6 Data Export

The Data Export module enables you to export DATASAFE data in a text file
format. The data can then be opened in a third-party program or imported into
DATASAFE again.
The Data Export module allows for the export of any planned or live parameter
values into a text file (CSV/CNA). You specify the type of export data, nodes and
parameters that data should be exported for and then specify the format of the
output (CSV/CNA).
The following types of data can be exported from the planned or live network
environment:
Cell attributes data.
Cell relations data.
Channel group data.
Sub-cell attributes data.
Node attributes data.

Figure 12: Data Export Module
On selection of the data type and network nodes the user wants to export data for,
the available parameters is displayed. The user can then select which of the
parameters must be included in the export data.
6.2.7 Network Explorer

This module displays the physical and logical network entities in the form of a
hierarchical and logical grouping of network nodes. This tree view structure is
used for filter and navigational purposes, as well as for defining parameter
override levels.
A GSM network has predefined physical nodes onto which cells are mapped.
DATASAFE incorporates these and allows you to customise the mapping to suit
your requirements. The Network Explorer module is used to configure and
customise the network nodes tree to suit your specific requirements regarding
clusters or groupings of cells. The radio-planning tool used (for example, ASSET)
provides the basic mapping of cells to BSCs. Other nodes can be parented and
mapped.
In order to create a new node, an entity representing the type of node has to exist.
An entity is a generic name used to refer to a type of node. For example, it could
be an MSC, BSC, REGION, LAC, PLANNER and so on. Entities are mapped (or
parented) together to make up an entity relationship, which is used as a base for
the network relationships. A Node can be defined as an instance of an entity.
The following functionality is included:
Grouping of nodes into logical and physical groups.
Creation of new nodes.
Assigning of software releases/versions to nodes.
Equipment type configuration.
Configuration and display of site location, description, vendor.
Intersection Entities enables you to create an INTERSECT join between
multiple entities. This can be used as grouping of related nodes.
Overrides can be created on this intersection Entity. All Cells/Nodes in the
Intersection will assume the new override value.
A history of all changes made to the network and nodes that can be
displayed in the Network History module.
Re-parenting of nodes should changes to the network configuration
require this.
A recycle bin – used for restoring deleted nodes, cells etc. When nodes
are deleted due to changes in planned or live data imported, they are
moved to the recycle bin. You can permanently delete these nodes by
clearing the recycle bin. Alternatively, if imported data was invalid, nodes
and relations can be restored from the recycle bin.

Figure 13: Network Explorer
Example: This picture of the Network Explorer's Network Relations pane shows
the Nodes that exist for the Entity 'MSC':
Figure 14: Network Relations pane displaying nodes created on Entity, MSC
The Network Explorer user interface contains the following:

Entity Explorer
Allows you to view the existing
Network elements. The way you
configure the Network hierarchy tree
on the Entity Explorer and Planned
tabs will determine how it is
displayed throughout the other
DATASAFE modules.
You are able to create, edit and
delete entities

Planned Network
Displays all cells that have been
defined in the network. The
Planned Network tab logically
groups all cells together according
to similar attributes.
The tree view separates Physical
(network) and Logical entities.
The way you configure the Network
hierarchy tree on the Entity Explorer
and Planned tabs will determine
how it is displayed throughout the
other DATASAFE modules.
This tab enables you to create
nodes and to parent new nodes that
were populated during data imports
to the correct Entity types and
parent nodes. There is a facility to
re-parent nodes should changes to
the network configuration require
this.

Live Network
Displays the Nodes as they exist in
the Live Network. A recycle bin is
available on this tab Cells that have
been deleted on the live network
since the last import will be placed
in the recycle bin when there is a
new import. This is a precautionary
measure in case cells were deleted
in error or the import file was
corrupted. You can also manually
delete cells and place them in the
recycle bin.
6.2.8 System Configuration

The System Configuration is a user-friendly interface, which enables the user to
configure the pre-requisites required to successfully set-up the customer Network
with DATASAFE.
It allows the user to: Create, Edit and Delete:
User parameters.
Parameter groups.
Vendor parameters.
Parameter and Commands formats.
Technology (GSM, UMTS etc.).
Vendors.
Global default values.
Affect levels.
Software versions.
Certain parameters are used in many vendors’ equipment, but may be named
differently for different vendors. In the DATASAFE environment, you may want to
refer to the same parameter by the same name regardless of vendor conventions.
You are able to create User parameters/Aliases for those parameters.

The Diagram below illustrates the concept behind User and Vendor Parameters.
Figure 15: User Vendor Parameter Concept
Figure 16: System Configuration dialog
Each Parameter is managed as a resource by its alias, with the following

configurable attributes:
Vendor Parameters: Vendor parameters are the names the vendors use
to refer to parameters on their own hardware. DATASAFE needs to know

what these parameters are called in the vendor’s environment to be able

to change them when required.
Parameter Groups: You can group parameters according to a common
functionality, or any other commonality such as vendors.
Parameter Command Relation: You will need to map parameters and
commands to one another to enable DATASAFE to generate
discrepancies for the parameters.
MML Commands: The MML command/parameter format editor enables
you to define the MML formats for parameters and command formats
using VB Script.
Vendor Commands: For every vendor DATASAFE has a record of, it is
necessary that DATASAFE has a record of what commands to issue to
the hardware in the field to keep the live network and planned network
consistent with each other.
Parameter Software Version Relation: The Parameter Software Version
Relation enables the user to map software versions to individual
parameters.
For example: Nodes need to identify with parameters of the same software
version. Certain parameters are supported by certain versions of a particular
vendor only, and certain nodes that have a software version (e.g. R11) should only
support parameters that are supported by that version (R11).
Affect Levels: An Affect Level is the level of the network hierarchy and its
associated parameters as referred to by the operator that will be affected
when a command is executed. This is the first level to be affected by
command.
Parameter Description: The Parameter Description page enables the
user to specify custom operator parameter names. Operator parameter
names are the generic names the operator uses to refer to certain
hardware parameters.
Vendor Information: Users on a multi-vendor network are able to define
all the vendors used in the network. Entering information on this page
enables the user to group or filter by Vendors in other areas of
DATASAFE.
Software Versions: Certain hardware only supports certain software
versions. You are now able to map parameters, tasks and templates etc.
to software versions. In order to be able to do this, the Software Versions
have to be defined in the System Configuration module.
Technology: Enables the user to enter custom text descriptions of the
Technologies available.
Adding a new Software Version is as simple as removing parameters that are no
longer supported and adding the new parameters that are supported.
6.2.9 Parameter Modeller

The Parameter Modeller enables the user to view and modify parameter values in
the planned network database. It enables editing of the cell parameters in the
planned network. These are the parameters that are not part of the planning tool,
but need to be tweaked in order to improve the performance of the network. Only
the planned model is editable, the live network model is viewable but can only be
modified via the discrepancy update process.

The primary interface of the Parameter Modeller is a pair of tree-views that

encapsulate selectable parameters and network nodes. It can be explained as
follows:
A complete list of parameters, arranged into logical groups that can be
defined by a network engineer, is displayed.
A hierarchical organisation of network nodes that are grouped by entity.
This information is presented in the form of a navigable tree that can be
expanded all the way down to the cell level.
A hierarchical organisation of nodes that are grouped by entity. This
information is presented in the form of a navigable tree that only shows
the nodes.
This enables you to view values of cell parameters in cells and compare
the values of the selected parameter in the planned environment against
corresponding parameter values from the live environment. By using
filters, you can specify which cells to select for viewing, and which
parameters on those cells to view.
Figure 17: Parameter Modeller
The Parameter Override Editor forms part of the Modeller but is launched
separately correlating with the grid display of the Parameter Modeller. This
interface provides users with the ability to modify data in the current planned
network database and forms one of the most fundamental components of
DATASAFE. It incorporates changes to cell parameters, switch devices and
transmission routes, according to the following priority levels:
Priority Level Overrides/Affect Level
6(Highest) Cell

Priority Level Overrides/Affect Level
5 Region
4 BSC
3 Location area
2 MSC
1 Group profile
0(Lowest) Network default (Global)
Priority 6 is the highest priority within the system. Any change made to a
parameter at cell level will override all other settings that may be entered at a
lower priority level for that cell, including the network default. The overrides table
is searched from priority level 6 downwards until an override is encountered. If no
override is found, then the network default it used.
Note: Priorities are configured in the Network Explorer module and are only
allocated to entities, not to nodes.
6.2.10 Bulk Override Import

This module allows for the bulk import of parameters on different affect levels to
perform bulk overrides. Data is read from csv files. Both the range checker and the
rules are run to ensure data integrity. All violations are recorded in the message
log. There is also an option to cancel an import should the data being imported
violate a range or rule. Both user and vendor parameters can be imported as well
as logical entities. Fall option is available wherein an XML file is produced to
permit fallback to previous design values
Figure 18: Bulk Override Imports

6.2.11 Cell Relations Manager

This module allows the user to manipulate the cell relations including the addition,
deletion and manipulation of neighbour relations. The user is able to define
neighbour relations, and modify parameters related to neighbour relations. Adding
and removing a neighbour cell is done through a simple drag and drop technique.
The user can import neighbour configurations through the import module. It is also
possible to automatically import co-sites as neighbours and to import neighbours
as they are defined in the live network. Every time a change is made, an entry into
the history log is made.
Figure 19: Cell Relations
The Cell Relations Manager enables the user to perform the following basic
functions:
Addition of new Neighbour cells.
Deletion of existing Neighbour relations.
Optimisation of Neighbour relation parameters.
Automatic adjustment of relations based on statistics is also possible.
Importing Network Neighbours from the live network.
All neighbour relations pertaining to a cell can be defined. This includes both
single and mutual relations as well as all parameters associated with the relation
on an individual relation level. Settings entered here will override any settings
entered at any other priority level. All relations defined in the planned that are
missing in the live and vice versa are highlighted in red.
6.2.12 Discrepancy Queue Handler

This module compares the Live network and Planned network databases and
detects differences between the databases. Discrepancies arise from these
differences and are presented to the user in a grid where data is easily filtered.
The filter view is stored on a per user basis.
The Discrepancy Queue Handler will run in the event of a change to either the live
or planned database models during an import or an override and will generate
discrepancies where necessary. In the event of a change to the planned model,
the Discrepancy Queue Handler enables you to generate the configuration data

(MML) needed to clear the discrepancies. Discrepancies are also cleared via the
Parameter Override Editor in the case where the planned network is incorrect.
Usually, a consistency check will be performed before the discrepancy is handled.
This is dependent on the Parameter being handled or the type of discrepancy.
Depending on the state of a discrepancy or the permissions of the user, the grid
background colour changes to alert the user of discrepancies that need attention.
DATASAFE makes use of the concept of higher order logical discrepancies to
assist the radio engineer with the commissioning, migration and decommissioning
of cells. A higher order discrepancy is one that needs to be handled before other
discrepancies can be handled, it will in turn handle all associated lower order
discrepancies
Figure 20: Discrepancy Queue Handler
Discrepancies are displayed on separate tabs for the following:

Cell Definition Discrepancies - This tab enables you to view logical
discrepancies in the network, which result from incorrect parenting (for example, a
cell being defined as belonging to BSC1, but in the live Network is defined with
BSC2 as its parent)
Parameters Discrepancies – This enables you to view and handle discrepancies
relating to cell parameter discrepancies (comparing planned vs. live parameter
values).
Neighbours Discrepancies - This shows discrepancies as they occur between
planned neighbour relations and the actual neighbour relations that exist in the
network
Custom Discrepancies – This displays data from user constructed queries.
You are able to export the list of discrepancies in one of the following file formats,
CSV and CNA. It is possible to add a Job reference when handling a discrepancy.
This can be switched on or off depending on the relevant settings. It is possible to
change the Extension of an MML file to mml rather than the node name.

Fallback files can be generated for all parameter and neighbour discrepancies for
all output formats except CNA. This is possible by selecting the option in the
Discrepancy queue tab.
6.2.13 Automation Wizard

The Automation wizard allows you to set the system up to automatically handle
discrepancies that arise for parameters that you have selected.
When discrepancies arise for these parameters, data transcripts are automatically
created by DATASAFE and sent to the network in order to handle the discrepancy.
This process can be scheduled to run at specified intervals.
Figure 21: The Automation Wizard
6.2.14 Task Modeller

The Task Modeller enables you to create tasks (programmed in VB Script) used
for generating data to handle discrepancies.
When configuring a network, it is very likely that certain tasks might regularly be
used, for example, to deal with discrepancies arising when creating a new cell
relation. Instead of creating a new task every time the discrepancy occurs, you
can create, define and map the task to a logical/parameter discrepancy
Tasks are repetitive functions, for example, creation of a new cell, cell relations
etc. that can be performed in DATASAFE. These tasks will then be used to
generate the MML commands needed to handle the discrepancies.
The Task Modeller has a user-friendly interface to allow the user to map task to
logical and parameter discrepancies as well as to create, modify and test tasks
before mapping them by using the Task Editor.

Figure 22: Task Modeller
Figure 23: Task Editor
6.2.15 Network History

The Network History enables the user to track the history of changes within the
DATASAFE planned environment.

Overrides to parameters can be made at different override levels in DATASAFE. It

is convenient to be able to track and monitor the history of these override settings
as they are changed by other users. This module allows the user to view the
history of these changes and all details of the change itself, including affect level,
node, date and time, the user who made the change, the old value, the new value
and the reason the change was made. Data changed as a result of the override is
also recorded. In turn any discrepancies created or deleted are recorded.
All changes made in the System Configuration are logged in the History Module.
These include creation, deletion and modification of the following:
Parameters
Commands
Global values
Ranges
Software versions
Technologies
Vendors
The History Module also records changes made in the Administrator. These
include keeping track of Parameter privileges, User privileges, DATASAFE module
permissions and user management.
Figure 24: History Module
Data is recorded per user with description indicating the type of action that was
executed i.e. Parameter Overrides, discrepancies cleared, new parameter added
etc.

Figure 25: Log Book Maintenance
Depending on User permissions the History maintenance module can be launched

from within the History Module or the Administrator to flush or archive data at
specific/selected times. Archived data is stored in comma-separated files.
6.2.16 SQL Custom Query

The SQL Custom Query module enables you to create and edit custom queries on
the DATASAFE database using SQL. You are able to grant privileges to users to
create custom SQL queries and grant privileges to users to edit specific queries.
The SQL Custom Query dialog displays information on the created queries, such
as owner, the duration it last took to run the query and the scope of the query.
When a query is run, the results are displayed in the bottom pane of the SQL
Custom Query dialog. You are able to export the query results in Excel, XML and
HTML format for external use.

Figure 26: SQL Custom Query
Figure 27: Edit SQL Custom Query

6.2.17 Custom Reports

The Custom Reports Module allows for queries created in the SQL Custom Query
Module to be viewed in multiple tabs and exported in various formats. The SQL
Custom Query Module can be called from with the Custom Reports.
Figure 28: Custom Reports
6.2.18 Cell View

The Cell View module allows you to view all cell information stored within
DATASAFE including planned cell definitions, neighbour/adjacencies, live logical
definitions and parameter settings. Information such as the internal and external
definitions on physical nodes as well as logical nodes is displayed on the Planned
tab in the Definitions panel. Neighbour/Adjacent Cell information is displayed in the
Neighbours/Adjacencies panel.
Parameter data is displayed in the grid for the selected cell based on the affect
levels, Cell, Cell Relations, Sub Cell, Channel Group. Parameters that have
discrepancies between planned and live parameter settings are displayed in red in
the grid.
You are able to perform parameter overrides from the Cell View dialog. The
override option available from the Cell View dialog only allows you to perform an
override for the Cell currently displayed in the Cell View. You are able to export
data displayed in the Cell View in CSV, Excel and HTML format.

Figure 29: Cell View
6.2.19 Activity Planner

Feature Highlights:
Allows users to create their personal list of activities.
Activities can be scheduled at certain date and time in the future.
Activities can be Planned, Approved and Scheduled.
Overview of status of each item in plan, including error detection and
status of successful execution.
Automated scheduling from a central server.
Familiar Microsoft Outlook like look and feel.
Ability to Fallback to previous known planned values at a scheduled date
and time, useful for specific trial changes.
Another practical use is to set network feature related parameters to take
effect at certain periods during the day, based on traffic profiles.
Allows users to optionally define if a fallback to original values should
occur automatically at a scheduled time.
Rules and Validation checks occur after the desired changes have been
loaded.
The Activity Planner gives the network planner/optimisation engineer the ability to
pre-plan any network configuration changes and schedule these changes to take
place at an appropriate time. For example, a special event might need additional
network changes performed for a particular time period. Without the Activity
Planner, the network planner would need to manually make the required network
changes at the time required. With the Activity Planner, the network planner can
automatically schedule the network configuration changes to occur at a particular
time and date.

Figure 30: Activity Planner
7 IT Specifications
Aircom recommend a separate machine for the database server and a separate
machine as the 'DATASAFE Process Machine' (see section 5.2 Architecture
above). The database server can reside on either a UNIX or a Windows platform,
while the Process machine and DATASAFE clients operate on a Windows
platform.
Exact machine specifications would be determined on a customer specific basis as
part of the solution design.
7.1.1 Oracle Licensing

DATASAFE 6.1 supports Oracle 9i and 10g although 10g is recommended for
superior performance. Oracle licenses are not included in the DATASAFE
package and need to be arranged separately by the DATASAFE customer.
7.1.2 Hardware
The dimension of hardware is largely dependent on the size of network and the
required number of concurrent users. The hardware requirements can be defined
after analysis of specific customer needs. Typically the minimal requirement is a
database server with sufficient memory, CPU and disk space to support the
volume of data and number of concurrent users. Typically a process machine for
mediation services i.e. parsing and loading data and interfacing to planning and
Live network is required. The dimensions can be defined based on the size of

network and throughput requirements. The client is able to run on a CITRIX

application server and Aircom can assist in the dimensioning and implementation
services for the CITRIX environment.
The latest DATASAFE Hardware Specifications document details the hardware
requirements for running DATASAFE. Since this document changes regularly it is
not embedded here, if a copy did not accompany this document please request it
from your Aircom representative.


DATASAFE Technical Overview PDF

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

DATASAFE Technical Overview PDF

Uploaded by

Copyright:

Available Formats

DATASAFE Technical Overview

Author: AIRCOM International

Sec. Class: Commercial in confidence

1 Document Control ...............................................................................................................3

Author: AIRCOM International Page 2 of 39

1.1 Revision History

Author: AIRCOM International Page 3 of 39

Author: AIRCOM International Page 4 of 39

Figure 1: Telecoms Operations Map (TOM)

DATASAFE supports Network Provisioning and Network Data Management. Input

Author: AIRCOM International Page 5 of 39

o Parameter/command handling catering for multiple value

5.1 DATASAFE Overview

Author: AIRCOM International Page 6 of 39

Figure 2: Planned vs. Live Network

The main objectives of this tool are to:

Author: AIRCOM International Page 7 of 39

Figure 3: System Architecture of a DATASAFE implementation

The diagram above shows the typical physical architecture of a DATASAFE

5.3 DATASAFE Functionality

Author: AIRCOM International Page 8 of 39

The latest DATASAFE Administrator is a separate application launched from

The latest release of DATASAFE contains the following functionality:

Author: AIRCOM International Page 9 of 39

A Violations log, which displays data outside the parameter ranges, as

Author: AIRCOM International Page 10 of 39

5.3.1 Inside DATASAFE

Author: AIRCOM International Page 11 of 39

DATASAFE Discrepancy Module

ODBC, delimited text, Are the

DATASAFE Planned Environment DATASAFE Live Environment

Are the Are the

Figure 4: Inside DATASAFE

The detail in the diagram above can is described below

Author: AIRCOM International Page 12 of 39

6 DATASAFE User Interface

6.1 Global Functions

6.1.2 Global Filters

Author: AIRCOM International Page 13 of 39

Figure 5: Create a Filter on Nodes ABCMSC1 and ABCMSC2

Figure 6: Toolbar shows that a filter is applied

6.2 User Functions

Author: AIRCOM International Page 14 of 39

User rights and authority groups for parameter privileges.

Figure 7: DATASAFE Administrator

Author: AIRCOM International Page 15 of 39

Figure 8: Assign System Privileges to a User

The DATASAFE Administrator is responsible for maintaining existing as well as

6.2.2 Rules Engine

Author: AIRCOM International Page 16 of 39

Figure 9: Rules Engine

6.2.3 The Rule Invoker

Author: AIRCOM International Page 17 of 39

Figure 10: Invoking a Rule

6.2.4 Data Import

6.2.5 Violations Log

Author: AIRCOM International Page 18 of 39

Figure 11: Violation log

6.2.6 Data Export

Author: AIRCOM International Page 19 of 39

Figure 12: Data Export Module

6.2.7 Network Explorer

Author: AIRCOM International Page 20 of 39