Optimi Data Gateway User Manual

Release Version 6.2

Contents

Contents
1

Optimi Data Gateway Graphical User Interface Components

1.1

1.2

1.3
2

Optimi Data Gateway Menu Bar . . . . . . . . . . . . . . . .

1.1.1 Database management . . . . . . . . . . . . . . . . .
1.1.1.1 ID Cache . . . . . . . . . . . . . . . . . . .
1.1.1.2 Repair . . . . . . . . . . . . . . . . . . . .
1.1.1.3 Reset . . . . . . . . . . . . . . . . . . . . .
1.1.2 Sector Location . . . . . . . . . . . . . . . . . . . . .
1.1.3 Settings . . . . . . . . . . . . . . . . . . . . . . . . .
Data Collection Task Control . . . . . . . . . . . . . . . . . .
1.2.1 Optimi Data Configuration Task COnfiguration Dialog
1.2.1.1 Data Source Configuration . . . . . . . . .
1.2.1.2 Unique ID selection . . . . . . . . . . . . .
Message Log . . . . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

Optimi Data Gateway Administration Guide

2.1
2.2

2.3

Scope and Contents . . . . . . . .

Maintenance . . . . . . . . . . . .
2.2.1 Database maintenance . .
2.2.2 Integrity . . . . . . . . . .
Troubleshooting . . . . . . . . . .
2.3.1 Socket operation error . .
2.3.2 Open file limit on MySQL
2.3.3 Low disk throughtput . . .

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

18

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

External Interfaces

3.1
3.2

Scope . . . . . . . . . . . . . . .
Ericsson 2G . . . . . . . . . . . .
3.2.1 CM Interfaces . . . . . . .
3.2.1.1 CNADB (OSS)
3.2.1.2 CNAI . . . . .
3.2.2 PM Interfaces . . . . . . .
3.2.2.1 CSDDB (OSS) .
3.2.2.2 CSDDB dumps
3.2.2.3 ASN.1 . . . . .
3.2.3 Parameter Change Files .

c
Optimi Corporation 2011

5
5
5
6
7
7
8
8
10
12
15
17

18
18
18
18
18
19
19
19
20

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

20
21
21
21
21
21
21
21
22
22

Contents
3.3

Ericsson 3G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 CM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1.1 XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 PM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2.1 XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.3 Parameter Change Files . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Nokia 2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 CM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1.1 NetAct Radio Access Configurator and Topology databases
3.4.2 PM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2.1 NetAct Performance Management Database . . . . . . . .
3.4.3 Parameter Change Files . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Nokia 3G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1 CM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.1 OSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.2 XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2 PM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2.1 NetAct Performance Management Database . . . . . . . .
3.5.2.2 XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3 Parameters Change Files . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Siemens 2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.1 CM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.2 PM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.3 Parameter Change Files . . . . . . . . . . . . . . . . . . . . . . . .
3.6.4 Other Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 Siemens 3G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.1 CM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.2 PM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.3 Parameter Change Files . . . . . . . . . . . . . . . . . . . . . . . .
3.8 Huawei 2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8.1 CM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8.2 PM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.8.3 Parameter Change Files . . . . . . . . . . . . . . . . . . . . . . . .
3.9 Huawei 3G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.1 CM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.2 PM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.9.3 Parameter Change Files . . . . . . . . . . . . . . . . . . . . . . . .
3.10 Alcatel Lucent 2G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10.1 CM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10.2 PM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.10.3 Parameter Change Files . . . . . . . . . . . . . . . . . . . . . . . .
3.11 Alcatel Lucent 3G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11.1 CM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.11.2 PM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

c
Optimi Corporation 2011

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

23
23
23
23
23
23
24
24
24
24
24
24
25
25
25
25
25
25
25
25
26
26
26
26
27
28
28
28
28
29
29
29
29
30
30
30
30
31
31
32
32
33
33
33

Contents
3.11.3 Parameter Change Files
3.12 ZTE 2G . . . . . . . . . . . . .
3.12.1 CM Interfaces . . . . . .
3.12.2 PM Interfaces . . . . . .
3.12.2.1 OSS . . . . .
3.13 ZTE 3G . . . . . . . . . . . . .
3.13.1 CM Interfaces . . . . . .
3.13.2 PM Interfaces . . . . . .

c
Optimi Corporation 2011

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

33
34
34
34
34
36
36
36

1 Optimi Data Gateway Graphical User Interface Components

1 Optimi Data Gateway Graphical User

Interface Components
The Graphical User Interface (GUI) is the client that interacts with the optimizer in order to
assist the user when operating it.
After the application has been successfully launched, the main user interface window appears
(see Figure 1.1).
Figure 1.1: Initial Window

1.1 Optimi Data Gateway Menu Bar

Aside from the Help Menu, the Optimi Data Gateway Menu Bar consists of a single menu, with
the following options:

1.1.1 Database management

1.1.1.1 ID Cache

Optimi Data Gateway uses internal identifiers (integer number) to identify managed objects.
The mapping between vendor-specific RAN/OSS identifiers (e.g. full distinguished name, Cell
Global Identifier, etc.) to the internal identifier is called int_id_cache. The int_id_cache ensures
that the Optimi Data Gateway (and certain Optimi applications, e.g. xParameters) can match
managed objects in newly read CM with managed objects in previous read CM.
In releases prior to 6.2, the int_id_cache resided in the Optimi Data Gateway installation.
This caused management and maintenance problems if e.g. the cache was lost, or for certain
maintenance use cases.

c
Optimi Corporation 2011

1 Optimi Data Gateway Graphical User Interface Components

In 6.2, in order to improve the consistency of the operdb and an Optimi Data Gateway installation, the int_id_cache is stored in the operdb. Also, menu items have been added in the GUI
in order to allow importing and exporting the cache.
Avaialble actions:
Import cache file (Optimi Data Gateway > Database Management > ID Cache).
Export cache file (Optimi Data Gateway > Database Management > ID Cache).

Figure 1.2: Database ID Cache dialog

Important
Especial use case: when upgrading an installation from 6.1 to 6.2, it needs be ensured
that the cache is kept. To that avail, the following actions must be taken:
1. Retrieve the cache file in [Optimi Data Gateway 6.1]\Optimi Data Gateway\data\<flavor>\output\int_id_cache.csv.
2. Install Optimi Data Gateway 6.2.
3. Import the int_id_cache.

1.1.1.2 Repair

Carries out a database repair/maintenance action; see Chapter 2 on page 18.

c
Optimi Corporation 2011

1 Optimi Data Gateway Graphical User Interface Components

1.1.1.3 Reset

Deletes all internal optimi database. This is meant to be done only upon request by Optimi/Ericsson personnel, in order to facilitate maintenance actions.

1.1.2 Sector Location

It provides utilities to import and export the sector location files which are needed by Optimi
Data Gateway. Sector location files provide physical information (latitude, longitude and azimuth). Also, names assigned to BTSs/cells, nodeBs/sites and RNCs/BScs may be used in the
GUI of certain applications.
Warning
The names specified in the sector location file will be used only if they are toplogically
consistent. For instance, if the name of an RNC is not the same for all of its topological
children, the name specified in the sector location will not be used (i.e. the name coming
from the OSS will be used instead).

In the sector location importing dialog, the Flavor (Infrastructure Vendor and Technology) must
be selected. The sector location information in the Optimi database and in the last imported file
can be visualized (the selection is done through the data source button). Available actions are:
Import from file.
Import from database.
Export to file (from the selected source).
Select data source (Optimi database or last imported file).
Deleted last imported sector location.
By default, all flavors support comma-separated value (csv) files as input format for the sector
location. The columns are:
BSC/RNC NAME
SITE/NODEB NAME
SECTOR/CELL NAME: Name to be used in the GUI.
SECTOR/CELL GLOBAL ID: Cell Global Id (MCC-MNC-LAC-CI)
TECHNOLOGY(2G/3G): this can have the value 2G or 3G.
LATITUDE: in format ggg.ddddddd
LONGITUDE: in format ggg.ddddddd

c
Optimi Corporation 2011

1 Optimi Data Gateway Graphical User Interface Components

Figure 1.3: Sector Location Importing Dialog

AZIMUTH: Azimuth in degrees (integer number).

BAND (optional column, included in release 6.2 in order to identify Common BCCH
BTSs in Nokia 2G infrastructure): Valid values: GSM800, GSM900, GSM1800, GSM1900.
For example:

BSC/RNC NAME,SITE/NODEB NAME,SECTOR/CELL NAME,SECTOR/CELL GLOBAL ID,TECHNOLOGY(2G/3G),LATITUDE,LONGITUDE,AZI

BSC01,SITE,SECTOR,510-1-6500-6451,2G,-6.23051,106.80697,0

1.1.3 Settings
The settings dialog allow to configure the database server connection settings:
Figure 1.4: Settings

1.2 Data Collection Task Control

The Data Collection Task Control shows as many task control components as flavors are licensed.
The component has the following items:

c
Optimi Corporation 2011

1 Optimi Data Gateway Graphical User Interface Components

Figure 1.5: Task Control

Task Enabling: This checkbox toggles the scheduling of a data collection taks for each
individual flavor. If enabled, Optimi Data Gateway will collect data for the corresponding
datasource, as configured in the task configuration dialog.
Important
Scheduled Optimi Data Gateway tasks can be run on a daily or hourly basis.

Task Status: (Ready) is shown for scheduled tasks.

Task Configuration: Brings up the Optimi Data Gateway task configuration dialog (see
section Section 1.2.1 on the next page).
Task Information: Shows a panel diaplaying:
Next execution date and time.
Mode: Indicates the situation of the task: ready (ready to be run), running.
State: shows the outcome of the last execution, if any. It can have the values: not yet
started, started, halt, completed with success, completed with exceptions.
Manual Lauch: Clicking on this button will schedule a single run of the corresponding
Optimi Data Gateway task.

c
Optimi Corporation 2011

1 Optimi Data Gateway Graphical User Interface Components

Stop button. Allows stopping the corresponding Optimi Data Gateway task, if running at
the moment.

1.2.1 Optimi Data Configuration Task COnfiguration Dialog

The data collection of the Optimi Data Gateway needs to be configured to find the OSS and to
select the portion of the network that will be sampled. The configuration of data collection is
done via the Data Collection Configuration dialog, in the xParameters menu:
Connection to the OSS databases. This is achieved via the PM Data and CM Data
tabs. The items to be configured are, depending on the vendor/technology. See Section 1.2.1.1 on page 12.
BSCs/RNCs: In this dialog, the BSCs/RNCs which will be processed by Data Collection
can be configured. Clicking on the Refresh button will update the window with the
current list of BSCs/RNCs available in the OSS. By clicking the checks boxes the selected
BSCs or RNCs will be included in the data collection.

Warning
This tab does not apply to file-oriented interfaces (e.g. Siemens 2G and 3G). In these
cases, data for all BSCs for which there is CM and PM information is collected.

Date Range: Optimi Data Gateway will collect data from the specified date that is selected,
the date ranges are:
Last Hour: Optimi Data Gateway will use the data from the last hour.
Last Day: Optimi Data Gateway will use the data from the day before.
Last Day + Today: Optimi Data Gateway will use the data from the day before and
the data from the current day.
Custom: Optimi Data Gateway will use the data from the date and time specified in
the fields. Please note that such data has to be available in the OSS.

Note
The Date Range tab applies only to database-oriented interfaces.
For fileoriented interfaces, all PM files in c:\Program Files\Optimi\Optimi Data Gateway\idm\data\[vendor]\pm_data will be parsed.

c
Optimi Corporation 2011

10

1 Optimi Data Gateway Graphical User Interface Components

Figure 1.6: BSCs and RNCs configuration dialog

Configuration: In this tab, the user can:

Set the launch time. Optimi Data Gateway executions scheduled via this dialog will
be periodic, with a daily periodicity. The scheduled launch time configures the hour
when this periodic execution will take place.
Collect PM data: Enables/disables the collection of PM data into the internal database.
Disabling this will result in a database with CM only information.
Set the CM and PM History Size (in days). The History Size is the maximum number
of days of CM and PM data will be stored in the internal xParameters database,
counted back from the execution date (e.g. if the Optimi Data Gateway collection
task is run on October 10th and the PM history size is set to 3, data older than
October 7th will be erased from the internal database). The PM History Size value
must be set to a value that supports the measurement period used in optimizations.
Last working day: History Size = 3 (default)
Last 5 working days: History Size = 7
Last N days: History Size = N

c
Optimi Corporation 2011

11

1 Optimi Data Gateway Graphical User Interface Components

Figure 1.7: Date Range Dialog

By default, it is recommended that the CM History Size is set to 3 days. This is required
to support daily optimization iterations.
Background: scheduled Optimi Data Gateway tasks are run daily, collecting PM from
the previous day. On Mondays data from the previous Sunday is collected; but if the
optimization is run using last working day measurement period, the algorithm will try
to read from the previous Friday, however a History Size of 3 is needed.
Sector Location: It provides utilities to import and export the sector location files which
are needed by Optimi Data Gateway. Sector location files provide physical information
(latitude, longitude and azimuth). Sector location has to be imported before the Optimi
Data Gateway executions take place. The sector location is a comma-separated value (csv)
file. Although all columns must be present, it is not compulsory to fill in data on all of
them.
1.2.1.1 Data Source Configuration

The data format filed allows the user to choose the type of interface.
If the interface is based on a database (data format is labelled OSS in that case), the user
will be prompted to enter the following information items:

c
Optimi Corporation 2011

12

1 Optimi Data Gateway Graphical User Interface Components

Figure 1.8: Scheduling configuration dialog

Figure 1.9: Sector Location dialog

c
Optimi Corporation 2011

13

1 Optimi Data Gateway Graphical User Interface Components

OSS server IP address or name (IP text box)
OSS server port
System Identifier (DB text box)
User and password
Database type: database management system of the database holding the data.

Figure 1.10: PM and CM Configuration Dialog

The user may test connection setting by clicking on the Test Connections button.
For interfaces oriented to files, the user is informed about the folder where the data files are expected in the CM Data and PM Data tabs of the Optimi Data Gateway configuration dialog.
The folder is not configurable, and the current fixed folder is: c:\Program Files\Optimi\Optimi
Data Gateway\idm\data\[vendor]\cm_data (for CM data) and c:\Program Files\Optimi\Optimi
Data Gateway\idm\data\[vendor]\pm_data (for PM data). Data files are expected in those folders organized as follows:
For vendors for which there is multi-OSS support, one folder per OSS is expected, both
for CM and PM. The name of the folder must be that of the OSS. CM and PM files must be
present in the corresponding OSS folder. The format of the file is specified in the interfaces

c
Optimi Corporation 2011

14

1 Optimi Data Gateway Graphical User Interface Components

specification of the corresponding Optimi application (please refer to the applicable user
manual).
For vendors for which there is no multi-OSS support,CM and PM files must be present directly in cm_data and pm_data folders. The format of the file is specified in the interfaces
specification of the corresponding Optimi application (please refer to the applicable user
manual).
Warning
Note that files in the fixed folders are parsed as is. This means that no additional
filtering is carried out, notably no date filtering on PM files.

Tip
Example. Optimi Data Gateway is configured to collect CM and PM data from an Ericsson 2G network that has 2 OSS: OSS1 and OSS2.CM is CNAI and PM is ASN.1. In this
situation, the CM data is organized as follows:
c:\Program Files\Optimi\Optimi Data Gateway\idm\data\Ericsson2G\cm_data\OSS1 >
Contains the CNAI file (unzipped) of BSCs in OSS1.
c:\Program Files\Optimi\Optimi Data Gateway\idm\data\Ericsson2G\cm_data\OSS2 >
Contains the CNAI file (unzipped) of BSCs in OSS2.
c:\Program Files\Optimi\Optimi Data Gateway\idm\data\Ericsson2G\pm_data\OSS1 >
Contains the ASN.1 files (unzipped) of BSCs in OSS1.
c:\Program Files\Optimi\Optimi Data Gateway\idm\data\Ericsson2G\pm_data\OSS2 >
Contains the ASN.1 files (unzipped) of BSCs in OSS2.

In practical situations, CM and PM files will be available in shared resources (e.g. SFTP server,
windows shares...) organized differently from the fixed folder structure in Optimi Data Gateway.
Also, files may be compressed, and their names may not match those expected (see the interfaces
section of the corresponding Optimi application). Automation of the operation of Optimi Data
Gateway is achieved by means of the preprocess script. The preprocess script is a python script
located in c:\Program Files\Optimi\Optimi Data Gateway\idm\scripts\[vendor]\. The script is
invoked at the beginning of every Optimi Data Gateway task. It is meant to carry out the necessary action (file transfer, renaming, uncompressing, etc.) to meet the fixed folder structure and
interface expected by the Optimi Data Gateway.
The contents of the preprocess script are developed by Optimi in agreement with its customers,
to ensure proper automation of Optimi Data Gateway collection tasks.
1.2.1.2 Unique ID selection

As of release 6.2, unique identifiers can be selected for NSN 3G flavor. Please refer to the release
notes of release 6.2, feature [6032].
Optimi Data Gateway uses internal identifiers (integer number) to identify managed objects.
The mapping between vendor-specific RAN/OSS identifiers (e.g. full distinguished name, Cell

c
Optimi Corporation 2011

15

1 Optimi Data Gateway Graphical User Interface Components

Global Identifier, etc.) to the internal identifier is called int_id_cache. The int_id_cache ensures
that the Optimi Data Gateway (and certain Optimi applications, e.g. xParameters) can match
managed objects in newly read CM with managed objects in previous read CM.
In releases prior to 6.2, the RAN/OSS identifiers used to match to an internal identifier were
fixed. Many times is difficult to know from one Optimi data Gateway iteration to the following if
a certain network element is the same or not, because the criterion we are using to discriminate
this, is different from the operator criterion. For instance, some operators assign their Cell
Identifiers in such a way that they are unitque accross the whole network; others ensure that the
relative identifier in the full distinguished name of the cell is unique. Nevertheless, there is no
general rule.
In the case of xParameters, this implied that the application considered certain objects as new
even if they were not. New objects are assigned the default template, and may not be flagged as
optimized if the RNC was not configured as complete.
In release 6.2, it is possible for the user (for the supported vendors) to select the RAN/OSS
identifier that will be used to internally identify the managed objects.
Supported actions:
Select the unique identifiers per managed object.
Figure 1.11: Unique identifiers

c
Optimi Corporation 2011

16

1 Optimi Data Gateway Graphical User Interface Components

Important
Especial use case: when upgrading an installation from 6.1 to 6.2, in order to ensure that
the cache is kept, and that operdbs and xParameters projects are consistent, the following
actions must be taken strictly in order:
1. Retrieve the cache file in [Optimi Data Gateway 6.1]\Optimi Data Gateway\data\<flavor>\output\int_id_cache.csv.
2. Install Optimi Data Gateway 6.2.
3. Open the Optimi Data Gateway configuration dialog and ensure that the unique
identifier seletion are the default ones (the default selection is the one that was
implicitely used by default in 6.1). Then press OK. This will internally configure
Optimi Data Gateway to utilize the selected unique ids.
4. Import the int_id_cache.

Warning
It is not possible to ensure consistency for operdbs and projects if they were created using
the NetAct interface for CM. This is due to the fact that the OSS identifier used in 6.1 is
not available for selection as unique id, because it is NetAct CM database-specific.

1.3 Message Log

The message log functions are similar to those in xParameters and other Optimi applications.
The user possible actions in the message log are:
Save: allows saving the message log on a file.
Clear: Clears the message log.

c
Optimi Corporation 2011

17

2 Optimi Data Gateway Administration Guide

2 Optimi Data Gateway Administration Guide

2.1 Scope and Contents
This document completes the documentation of the Optimi Data Gateway module beyond the
User Manual, targeting system administrators.
This guide describes relevant aspects related to system maintenance. The objective of maintenance is to preserve system integrity and scalability.
Installation aspects are covered in the user guides of each product.

2.2 Maintenance
MySQL maintenance tasks are important in order to keep database tables performance.

2.2.1 Database maintenance

A new menu option has been included in Optimi Data Gateway: Database Management >
Repair.
It is recommended to perform that action once a week.
System defragmentation (e.g. using Windows Disk Defragmenter) is also recommended every
week additionally to the previous optimization.

2.2.2 Integrity
It is important to avoid copying or replacing files at xSQL\mysql\data if xSQL is running. Otherwise MySQL will generate unexpected errors due to lack of synchronization between tables in
memory and tables in disk.

2.3 Troubleshooting
Some guidelines on certain problems are listed here.

c
Optimi Corporation 2011

18

2 Optimi Data Gateway Administration Guide

2.3.1 Socket operation error

Caution
Error:
An operation on a socket could not be performed because the system lacked sufficient
buffer space or because a queue was full.

Possible solution:
Tune Windows TcpTimedWaitDelay TCP parameter in order to decrease the time that
connections spend on TIME_WAIT state
Using Windows regedit.exe tool:
Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters
Create a new key for REG_DWORD, and specify the name TcpTimedWaitDelay
Type the minimum decimal value 30 (which is 0x0000001e in hexadecimal)
Computer has to be restarted to make the change take effect.

2.3.2 Open file limit on MySQL

MySQL can handle a maximum of 2048 file descriptors (limit imposed by the underlying C runtime library). Also, MyISAM database engine (used in xSQL) needs to open two file descriptors
for each unique open table.
That limit needs to be taken into account when configuring the number of subpartitions in the
Optimi Data Gateway\idm\configuration\pm.writer.properties Optimi Data Gateway configuration file.

2.3.3 Low disk throughtput

If disk throughput is low in long I/O operations, and fragmentation is discarded as possible
reason, then it can be checked if Windows file cache performance is good enough.
To monitor the file cache the counter \\hostname\Memory\System Cache Resident Bytes can
be visualized using perfmon.msc (Control Panel > Administrative Tools > Performance).

c
Optimi Corporation 2011

19

3 External Interfaces

3 External Interfaces
3.1 Scope
This document describes read and write interfaces:
Read interface: input data to xParameters.
Input data is provided to xParameters by Optimi Data Gateway. Optimi Data Gateway can
read configuration (CM) and perfomance (PM) data from a variety of interfaces, which
will be refered to as Optimi Data Gateway Standard Interfaces. This section describes interfaces from a user point of view, for xParameters use (note that other Optimi applications
may have different interfaces).
Write interface: paramater change files used to implement the iterative optimization output
by xParameters.
Also, the RAN and OSS versions that the interfaces are valid for are listed in this document.
Please note that in some cases, operators may furnish the data files in a format different from
the xParameters Standard Interfaces in terms of:
Filenames
Locations: files may be located in complex folder structures, in file or FTP servers, etc.
Compression: files may be compressed in a variety of formats
etc.

c
Optimi Corporation 2011

20

3 External Interfaces

3.2 Ericsson 2G
BSC Sotfware releases supported are R10, R11, R12, R06B, R07B, R08B, G10A.

3.2.1 CM Interfaces
3.2.1.1 CNADB (OSS)

OSS CNADB Sybase databases are directly queried to retrieve the needed CM information.
Please refer to the installation guide for details about configuring the access to the database.
3.2.1.2 CNAI

CM can be provided as CNAI old format exports, at the location indicated in the Optimi Data
Gateway configuration dialog, "CM Data", as "Input Folder. Two possibilities exist:
One single CNAI file, named single.cnai. This CNAI file must inlcude confiuration of all
Ericsson objects, from cell (internal_cell) down to neighbor relation.
One file per supported managed object: bsc.cnai, site.cnai, bts.cnai (this CNAI file must
inlcude confiuration of all Ericsson objects from cell down to neighbor relation) and
pp.cnai.

3.2.2 PM Interfaces
3.2.2.1 CSDDB (OSS)

OSS CSDDB Sybase databases are directly queried to retrieve the needed PM information.
Please refer to the installation guide for details about configuring the access to the database.
3.2.2.2 CSDDB dumps

CSDDB dumps are read. One file per CSDDB table is expected, at the location indicated in the
Optimi Data Gateway configuration dialog, "PM Data", as "Input Folder. The file names must
have the format: [Table_name].csv. Columns are semicolon-separated. The columns are:
NE: BSC name
MO: Cell name (for cell tables), or [source_cell]-[target_cell] (for neighbor tables)
TIME: measurement period, yyyy-mm-dd HH24:mm:ss.s
[counters]

c
Optimi Corporation 2011

21

3 External Interfaces
3.2.2.3 ASN.1

ASN.1 files according to Ericsson specifications (STS on APG, which is based on 3GPP TS
32.104 V3.4.0 (2000-12), 3rd Generation Partnership Project Technical Specification Group
Services and System Aspects Telecommunication Management 3G Performance Management,
Annex A.2. STS on APG is supported by BSCs equipped with APG40) are expected at the location indicated in the Optimi Data Gateway configuration dialog, "PM Data", as "Input Folder.
Files names must start by the string "C20", and include the BSC name between _ characters.
For instance: C20090422.2300-20090423.0000_BSCNAME_1000.
Warning
If ASN.1 files are collected via FTP, the transfer mode must be set to binary. ASCII FTP
will change certain control characters, which will render the files not compliant to the
ASN.1 standard.

3.2.3 Parameter Change Files

The following formats are generated:
MML. This format is generated if parameter generateMML is set to true in:
<intall_folder>\xparameters\algorithms\EricssonTrafficBalance.config.
CNAI. This format is generated if parameter generateXML is set to true in:
<intall_folder>\xparameters\algorithms\EricssonTrafficBalance.config .

c
Optimi Corporation 2011

22

3 External Interfaces

3.3 Ericsson 3G
Supported RAN versions: P5, P6, P7, P7.1, W10.

3.3.1 CM Interfaces
3.3.1.1 XML

Bulk CM XML files (as per 3GPP TS 32.615 V4.5) are read for CM. Each CM file may contain
information from one or several RNCs. Files are expected at the location specified in the Optimi
Data Gateway configuration dialog, "CM Data", as "Input Folder. XML files for CM must have
".xml" extension.
Certain Managed Objects are optional in Bulk CM files, although certain Optimi products
features may require such information. Please refer to the product documentation for details.
Note
CM files must include the configuration of Node B (RBS) Managed Objects. As of Optimi
Data Gateway 6.0, Node B configuration is compulsory ONLY if PM data is collected (i.e.
if Collect PM data in the configuration dialog of Optimi Data Gateway is checked).

3.3.2 PM Interfaces
3.3.2.1 XML

XML files (as per 3GPP TS 32.401) are read. XML files for PM must have ".xml" extension.
WNCS reports are read in order to support intra-frequency neighbor list optimization. A file
wncs.csv is expected in the PM data folder. The columns expected are:
period_start_time, period_stop_time, servingCell, unmonitoredNeighbour, scramblingCode,
frequency, NbType, numberOfDetections radioLinkAdditionAttempts, timeInActiveSet, numberOfEvents, numberOfDrops, successfulRLAdditions, failedRLAdditions, operationalState, selectionPriority, averageCPICHEcNo, averageRSCP
Note
The columns in italics are standard in WNCS msmt files. Period_start_time and period_stop_time may be added through customization (see customization chapter).

3.3.3 Parameter Change Files

XML files are generated.

c
Optimi Corporation 2011

23

3 External Interfaces

3.4 Nokia 2G
BSC Software releases supported are BSS10, BSS11, BSS11.5, BSS12, BSS13, RG10. OSS up
to release 5.2.

3.4.1 CM Interfaces
3.4.1.1 NetAct Radio Access Configurator and Topology databases

NetAct RAC and Topologydatabases are directly queried to retrieve the needed CM information.
Please refer to the installation guide for details about configuring the access to the database.

3.4.2 PM Interfaces
3.4.2.1 NetAct Performance Management Database

NetAct PM database for BSC raw measurements is directly queried to retrieve the needed PM
information. Please refer to the installation guide for details about configuring the access to the
database.

3.4.3 Parameter Change Files

The following formats are generated:
MML. This format is generated if parameter generateMML is set to true in:
<intall_folder>\xparameters\algorithms\NokiaTrafficBalance.config.
Warning
This interface is OBSOLETE.

XML. This format is generated if parameter generateXML is set to true in:

<intall_folder>\xparameters\algorithms\NokiaTrafficBalance.config.

c
Optimi Corporation 2011

24

3 External Interfaces

3.5 Nokia 3G
RAN supported versions are RAN5.1, RAN6.0, RU10, RU20.

3.5.1 CM Interfaces
3.5.1.1 OSS

OSS databases are directly queried to retrieve the needed CM information. Please refer to the
installation guide for details about configuring the access to the database.
3.5.1.2 XML

XML files are read for CM. Each CM file may contain information from one or several RNCs.
Files are expected at the location specified in the Optimi Data Gateway configuration dialog,
"CM Data", as "Input Folder. XML files for CM must have ".xml" extension.

3.5.2 PM Interfaces
3.5.2.1 NetAct Performance Management Database

NetAct PM database for RNC raw measurements is directly queried to retrieve the needed PM
information. Please refer to the installation guide for details about configuring the access to the
database.
3.5.2.2 XML

For PM, the supported formats are:

Open Measurement Standard (OMeS) XML files.
Performance Measurements compliant with the "CORBA Solution Set specifications of
the Itf-N interface between Operations Systems", 3GPP R6 (32.412 6.4.0 and 32.413
6.4.0), with XML schema defined by 3GPP TS 32.435. XML files for PM must start
by "PM".
Files are expected at the location specified in the Optimi Data Gateway configuration dialog,
"PM Data", as "Input Folder

3.5.3 Parameters Change Files

XML files are generated.

c
Optimi Corporation 2011

25

3 External Interfaces

3.6 Siemens 2G
BSC Sotfware releases supported are BR7.0, BR8.0, BR9.0 and BR10.

3.6.1 CM Interfaces
Siemens DB-files are read. One file is expected per BSC, at the location specified in the Optimi
Data Gateway configuration dialog, "CM Data", as "Input Folder. The filenames must be: [BSC
ID].cm, where BSC ID is an alphanumeric identifier for the BSC.

3.6.2 PM Interfaces
Siemens Performance Measurement in ASCII (BR7.0, BR8.0 and BR9.0) or XML (BR10.0)
records are read, at the location specified in the Optimi Data Gateway configuration dialog, "PM
Data", as "Input Folder. The filenames must be:
[BSC ID]_[BR version]_[StartingDateTime]_[EndingDateTime].pm,
where:
BSC ID is an alphanumeric identifier for the BSC.
BR Version is the BSS software release (BR90 for Base Release 9.0, BR80 for Base Release
8.0, etc).
StartingDateTime: Start of the sampling period, in yyyymmddHHMMSS format.
EndngDateTime: End of the sampling period, in yyyymmddHHMMSS format.
Note
Please note that symbolic names are not supported for monitored objects.

Important
The date and time of the counter registers inside the files must be in dd/mm/yyyy
HH:MM format. If other formats are used, external processing must reforat the dates.
External procesing is normally handled via extension installer. Please contact Optimi
support for details.

3.6.3 Parameter Change Files

Siemens MML files are generated, per Radio Commander.

c
Optimi Corporation 2011

26

3 External Interfaces

3.6.4 Other Interfaces

In certain cases, the Radio Commander each BSC is assigned to needs to be furnished in a
file called rc_mapping.csv, whose location can be especified in the "CM Data" tab of the Data
Collection Configuration dialog. The contents of this simple file are:
bsc_id,rc_id
[BSC_ID_1],[RC_ID_of_BSC_ID_1]
...
This information is used mainly to generate MML files per Radio Commander.

c
Optimi Corporation 2011

27

3 External Interfaces

3.7 Siemens 3G
UMR6.0 is supported.

3.7.1 CM Interfaces
Siemens DB-files are read. One file is expected per RNC, at the location specified in the Optimi
Data Gateway configuration dialog, "CM Data", as "Input Folder. The filenames must be:
aclu_rnc_[RNC ID].cm.

3.7.2 PM Interfaces
Siemens Measurement Results files in ASN.1 format (which comply with 3GPP TS 32.104).
Only "transferred files" (i.e. starting with "C) are supported.
The filenames must be exactly as issued from the RNC.
Files must be uncompressed, and its extension must be ".pm".
All files are expected to be found at the location specified in the Optimi Data Gateway configuration dialog, "PM Data", as "Input Folder.

3.7.3 Parameter Change Files

CLI files are generated.

c
Optimi Corporation 2011

28

3 External Interfaces

3.8 Huawei 2G
BSC Software release supported are BSC6000 V900R003 through V900R008, on BSC6000
Hardware. M2000 release must be up to V200R008.

3.8.1 CM Interfaces
XML dumps from M2000.

3.8.2 PM Interfaces
The following interfaces are supported:
XML dumps from M2000.
CSV dumps from M2000.

3.8.3 Parameter Change Files

MML files are generated.

c
Optimi Corporation 2011

29

3 External Interfaces

3.9 Huawei 3G
RAN Software releases supported are R6.0, R6.1, R10.0 and RAN11. RNC BSC6810 is supported.

3.9.1 CM Interfaces
MML dumps from RNC. The file names are expected to comply with the following naming
convention:
RNC[RCN ID].txt
Warning
All object identifiers in PM files are expected to use RNC[RNC ID] to identify the RNC.
For instance, if the CM file is RNC123, a cell object identified is expected to be, e.g.
RNC123/Label=SomeLabel, CellID=10000.

3.9.2 PM Interfaces
Counter dumps from RNC, in csv format, are read. All files are expected to be found at the location specified in the Optimi Data Gateway configuration dialog, "PM Data", as "Input Folder.
The counters are divided by Function Subset, as per the table below; filenames must be as in the
column labelled Name in PM_DATA:
The columns in the counter files are the following:
start time: yyyy-MM-dd HH24:mm format.
period: period duration in minutes.
Object Name.
reliability. Reserved for future use.
Counters columns. Counters are identified by the Counter ID (e.g. "67180673") or the
counter name (e.g. VS.HSDPA.CellChg.AttOutIur). The order of the counter columns
is irrelevant. There can be counters not read by xParameters. Please refer to the Huawei
3G documentation for the list of counters needed by xParameteres.

3.9.3 Parameter Change Files

MML files are generated.

c
Optimi Corporation 2011

30

3 External Interfaces

Table 3.1: Optimi Data Gateway Huawei 3G PM interface

FunctionSubSet Name

FunctionSubSet ID

Name in PM_DATA

Cell TX and RX Power Measurement per cell

67109385

TxRxPower.csv

Cell Update Measurement per cell

67109382

CellUpdate.csv

HSDPA Measurement per cell

67109390

HSDPAMeasCell.csv

HSDPA measurements per local cell

50331648

HSDPAMeasLocalCell.csv

HSUPA Measurement per cell

67109471

HUSPAMeasCell.csv

InterRAT Handover Measurement per cell

67109381

IRATHOMeas.csv

Measurement between a cell and a UMTS cell

67109395

Between_cell_UMTS.csv

Measurement of CS RAB assignment failure per cell

67109369

CSRAB_Failure.csv

Measurement of CS RAB assignment setup per cell

67109368

CSRAB_Setup.csv

Measurement of PS RAB assignment failure per cell

67109373

PSRAB_Failure.csv

Measurement of PS RAB assignment setup per cell

67109372

PSRAB_Setup.csv

Measurement of RAB release triggered by UTRAN per cell

67109376

RABRelByUTRAN.csv

Measurement of RB Procedure per cell

67109378

RB_Procedure.csv

Measurement related to Algorithm per cell

67109391

AlgorithmMeas.csv

Measurement related to SIRTARGET per cell

67109505

SirTarget.csv

Measurement related to throughput per cell

67109508

ThputMeas1.csv

RRC connection reject measurement per cell

67109367

RRC_Reject.csv

RRC connection release measurement per cell

67109366

RRC_Release.csv

RRC connection setup measurement per cell

67109365

RRC_Setup.csv

RRC Reporting Measurement per cell

67109384

RRCRepMeas.csv

Soft Handover Measurement per cell

67109379

SHO.csv

3.10 Alcatel Lucent 2G

RAN release B9, B11 is supported.

3.10.1 CM Interfaces
ACIE files are read. The export files are:
Adjacency.csv
Adjacency2gTo3g.csv
Cell.csv
ExternalOmc3gCell.csv
ExternalOmcCell.csv
HoControl.csv
RnlAlcatelBSC.csv
RnlAlcatelMFS.csv
RnlAlcatelSector.csv
RnlAlcatelSiteManager.csv
RnlBasebandTransceiver.csv

c
Optimi Corporation 2011

31

3 External Interfaces
RnlFrequencyHoppingSystem.csv
RnlPowerControl.csv
SubNetwork.csv

3.10.2 PM Interfaces
The following files are read:
Binary PM: Type 31. Files must start with the string PMRES-31.
ASCII or binary PM: Type 110 and 180. ASCII (OBSYNT interface) and binary files are
accepted:
Binary: Files must start with the string PMRES-xxx, where xxx=110 or 180.
ASCII: Files must start with the string Rxxx, where xxx=110 or 180.
GPRS counters: either ASCII PM through OBSYNT interface (files must start with the
string RMFS) or ASCII PM not through OBSYNT interface (files must start with GPMRES).
For counters of type 110, 180 and 31, the name of the BSC must be included in the filename
between dots (.). The position in the filename is not relevant. For instance, for binary format,
the files must be named: PMRES-31%.[BSC name].%.

3.10.3 Parameter Change Files

ACIE Import files are generated.

c
Optimi Corporation 2011

32

3 External Interfaces

3.11 Alcatel Lucent 3G

Supported hardware: Nortel 9370 RNC and OneBTS Lucent 939x Node Bs
UTRAN V6.0 and OAM V6.0 are supported..

3.11.1 CM Interface
WMS Snapshot in XML format.

3.11.2 PM Interface
RNC Observation counters in XML format compliant with 3GPP 32.401-02 DTD.
Performance Measurements in XML format compliant with 3GPP 32.401-02 DTD.

3.11.3 Parameter Change Files

No native parameter change files are genereted in xParameters 6.1.

c
Optimi Corporation 2011

33

3 External Interfaces

3.12 ZTE 2G
3.12.1 CM Interfaces
Csv CM dumps are read. These files must be located in [Optimi Data Gateway]/idm/data/ZTE2G/cm_data.
The following files are expected:
[BSCID]_Adjacent_Cell_Handover[...].csv
[BSCID]_Adjacent_Cell_Hores[...].csv
[BSCID]_Adjacent_Cell_Reselection[...].csv
[BSCID]_Adjacent_Interference_Cell[...].csv
[BSCID]_BSC_Function[...].csv
[BSCID]_Cell[...].csv
[BSCID]_Channel[...].csv
[BSCID]_eMLPP_Set[...].csv
[BSCID]_Frequency_Hopping_System[...].csv
[BSCID]_GERAN_External_Cell[...].csv
[BSCID]_Handover_Control[...].csv
[BSCID]_Power_Control[...].csv
[BSCID]_Timer_Config[...].csv
[BSCID]_TRX[...].csv
[BSCID]_UTRAN_Adjacent_Cell_Handover[...].csv
[BSCID]_UTRAN_Adjacent_Cell_Hores[...].csv
[BSCID]_UTRAN_Adjacent_Cell_Reselection[...].csv
[BSCID]_UTRAN_Cell_Control[...].csv
[BSCID]_UTRAN_External_Cell[...].csv
[BSCID]_UTRAN_Handover_Control[...].csv

3.12.2 PM Interfaces
3.12.2.1 OSS

Minos_pm OSS database (Oracle) is directly queried to retrieve the needed PM information.
Please refer to the installation guide for details about configuring the access to databases.
The following minos_pm tables are read. The counter family (C90110??? includes counters
C90110001, C90110002...) expected in each table is indicated, as well as the table keys.

c
Optimi Corporation 2011

34

3 External Interfaces

Table 3.2: ZTE 2G minos pm tables

Table

Counter family

Keys

A_BSC_ADJCELLHMEAS

C90110????

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),GSMRELATION
(VARCHAR2)

A_BSC_CELL_PSBASICMEAS

C900040???

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),

A_BSC_CSBASICMEAS

C900060???

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),

A_BSC_DLDATATBFMEAS

C901000???

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),

A_BSC_HCMEAS

C901060???

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),

A_BSC_PSRESUSEDSTAT

C901040???

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),

A_BSC_RADIOMEAS

C901120???

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),

A_BSC_RRAVAILMEAS

C901080???

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),

A_BSC_SUBCELLSTAT

C901130???

A_BSC_UPDOWNRLCSTAT C901030??? COLLECTTIME

(DATE),GRANULARITY (NUMBER),STATUS
(NUMBER),SUBNETWORKID (NUMBER),IBSCMEID
(NUMBER),SITEID (NUMBER),BTSID (NUMBER)

A_BSC_UPDOWNRLCSTAT

C901030???

COLLECTTIME (DATE),GRANULARITY
(NUMBER),STATUS (NUMBER),SUBNETWORKID
(NUMBER),IBSCMEID (NUMBER),SITEID
(NUMBER),BTSID (NUMBER),

c
Optimi Corporation 2011

35

3 External Interfaces

3.13 ZTE 3G
ZTE RNC V3.70.300 is supported.

3.13.1 CM Interfaces
XLS files are processed.

3.13.2 PM Interfaces
Minos_pm database is accessed to retrieve counter information.

c
Optimi Corporation 2011

36