csv interface for configuration-nsn

Nokia Siemens Networks

NetAct OSS5.2 CD Set 2 (PDF)

CSV Interface for Configuration

Management Data

DN04187131

Issue 7-0

2 DN04187131Issue 7-0

CSV Interface for Configuration Management Data

Id:0900d80580743028

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under which

the document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED

TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY

OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010/5/25. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment.

Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-

zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die

Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene

Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN04187131Issue 7-0

3


Id:0900d80580743028

Table of ContentsThis document has 48 pages.

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 NetAct compatibility and capacity information . . . . . . . . . . . . . . . . . . . . . 7

1.2 Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Changes in CSV Interface for Configuration Management Data . . . . . . . 8

2.1 Changes in OSS5.1 CD set 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 CSV file format overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1 CSV file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2 Working with profile files and CSV data files . . . . . . . . . . . . . . . . . . . . . . 9

3.2.1 Creating a profile file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.2.2 Mapping parameter values to the profile . . . . . . . . . . . . . . . . . . . . . . . . 11

3.3 Internal and UI parameter values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Required CSV interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1 Special parameters for managed object identification . . . . . . . . . . . . . . 13

4.1.1 Managed object identification by DN . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1.2 Global Identification parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1.2.1 GSM CGI (Cell Global Identity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1.2.2 WCDMA and I-HSPA GUCI (Global UTRAN Cell Identity) . . . . . . . . . . 14

4.1.3 Cell ID-based identification for cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.1.4 Name-based identification for cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.1.5 Initial Frequency-based identification for TRXs . . . . . . . . . . . . . . . . . . . 15

4.1.6 Adjacency-related identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.2 Other planning interface parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.2.1 Operation parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.2.2 List parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.2.3 Structured parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.2.4 Template Name parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.2.5 Site parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.2.5.1 SITE object’s parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.2.5.2 Site identification of a managed object . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.3 Additional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.3.1 Automatic external cell management. . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.3.2 Managed object creation using the parent object’s DN . . . . . . . . . . . . . 20

4.3.3 Using commas and quotation marks in parameter values . . . . . . . . . . . 20

4.3.4 Changing the linked cell of GCAL, WCAL and WLCSE. . . . . . . . . . . . . 21

4.3.5 WCDMA BTS site rehosting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.4 Summary tables of interface parameter usage . . . . . . . . . . . . . . . . . . . 22

4.4.1 Adjacency-related special parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.4.2 SITE object-related special parameters. . . . . . . . . . . . . . . . . . . . . . . . . 23

5 Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6 Appendix A: DTD definition for CSV mapping . . . . . . . . . . . . . . . . . . . . 26

7 Appendix B: Example files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4 DN04187131Issue 7-0


Id:0900d80580743028

7.1 Site creation (GSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

7.2 Site creation (WCDMA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

7.3 Adjacency planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

7.4 XML profile for WCDMA BTS site rehosting . . . . . . . . . . . . . . . . . . . . . . 45

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

DN04187131Issue 7-0

5


Id:0900d80580743028

List of FiguresFigure 1 Overview of the CSV Interface for Configuration Management Data . . . 9

Figure 2 Profile file and CSV mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Figure 3 Profile file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 4 CSV data example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 5 CSV data example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 6 CSV data example with empty columns . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 7 File csvmap10.dtd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Figure 8 XML profile for GSM SITE creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Figure 9 XML profile for WCDMA SITE creation . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 10 XML profile for adjacency planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 11 Rehosting profile file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

6 DN04187131Issue 7-0


Id:0900d80580743028

List of TablesTable 1 Adjacency-related parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table 2 Summary of special parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Table 3 Special parameters for adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 4 Special parameters for the SITE object . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 5 How to read the CSV examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Table 6 CSV data for GSM Site creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Table 7 CSV data for WCDMA Site creation . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Table 8 CSV data for adjacency planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

DN04187131Issue 7-0

7

CSV Interface for Configuration Management Data About this document

Id:0900d80580743025

1 About this documentCSV Interface for Configuration Management Data is an interface for transferring

network configuration data files in CSV (comma separated value) format from a planning

system to NetAct Configurator, and from Configurator to a planning system.

This document describes the structure of the CSV format data files that are used for

transferring data between a planning system and Configurator. In addition, this

document provides some useful examples of CSV files used in the planning phase.

The document is meant for users that come from a variety of areas: radio network

planning and implementation, roll-out, configuration management, and engineering

support.

1.1 NetAct compatibility and capacity information

For information on the NetAct system and capacity, and the compatibility between

NetAct and network element releases, see the NetAct Compatibility and Capacity Infor-

mation document.

1.2 Terms

If you are unfamiliar with any of the terms used in this document, refer to the Glossary.

8 DN04187131Issue 7-0


Id:0900d80580743025

Changes in CSV Interface for Configuration Manage-ment Data

2 Changes in CSV Interface for Configuration

Management DataThis chapter describes the changes in the CSV Interface for Configuration Management

Data.

2.1 Changes in OSS5.1 CD set 2

New

ADJD and ADJS adjacencies support for I-HSPA Rel2.

DN04187131Issue 7-0

9

CSV Interface for Configuration Management Data CSV file format overview

Id:0900d80580743025

3 CSV file format overviewThe CSV Interface for Configuration Management Data is an interface for transferring

network configuration data files in CSV (comma separated value) format from the

planning system to NetAct Configurator and from Configurator to the planning system.

See the following figure for an overview of the information flow.

Figure 1 Overview of the CSV Interface for Configuration Management Data

g CSV formats in CM Operations Manager and Plan Editor are not fully compatible

with each other. In Plan Editor CSV format it is possible to use the same parameter

position for more than one object. This is not supported by CM Operations Manager

CSV format.

3.1 CSV file format

A CSV file is an ASCII (that is, plain text) representation of spreadsheet data. Values in

the file are separated by commas to indicate the separating points for columns.

In NetAct Configurator, a CSV file contains data that represents the managed objects in

the network. Each line in the CSV file contains several managed objects, and each line

must have an equal amount of comma-separated columns.

Data in CSV format can be used in exporting actual configuration, importing and export-

ing plans and site information. For examples of CSV usage, see Appendix Example files.

3.2 Working with profile files and CSV data files

The structure of the CSV file comes from an XML-formatted profile file. It is a user-defin-

able XML (Extensible Markup Language) file that specifies the managed objects and

parameters that are used in planning.

NetAct Configurator

ConfiguratorDatabase

CM Data Repository

CM OperationsManager

Planning tool

Plan EditorCSV

CSV CSV

10 DN04187131Issue 7-0


Id:0900d80580743025

CSV file format overview

The profile only defines the positions for data values on a line in CSV, as shown in the

figure below. If an object does not have a value for a certain parameter, this is repre-

sented by an empty comma-separated column.

Figure 2 Profile file and CSV mapping

For more information and examples, see Creating a profile file and Mapping parameter

values to the profile.

3.2.1 Creating a profile file

The profile file is a standard XML file. It has the XML version declaration element at the

beginning of a file, and the document type declaration for assigning the DTD (Document

Type Definition). For details on the DTD of the profile file, csvmap10.dtd, see

Appendix DTD definition for CSV mapping.

Each managed object is represented by the <managedObject> element. The attri-

butes and parameters for each object are contained in the elements. In non-

unique object class, the adaptation is defined in the class abbreviation, for example,

NOKBSC:FRBC, or NOKSGSN:FRBC.

The profile file may also include a <header> tag (with rows attribute), which specifies

the number of header rows in the CSV file. Header rows are only for informative

purposes and do not contain any real parameter data. For example, if the value of the

<header> tag is 4, the first four rows in the CSV file are headers and parameter values

start from row 5. If the tag has value 1, CSV data starts from line 2. If there is no

<header> tag at all, data starts directly from the first line in CSV.

<?xml version="1.0"?>

<!DOCTYPE csvmap SYSTEM "csvmap10.dtd">

<csvmap>

<header rows="4/>

<managedObject class="BSC">

DN04187131Issue 7-0

11

CSV Interface for Configuration Management Data CSV file format overview

Id:0900d80580743025





</managedObject>

<managedObject class="NOKBSC:BCF">










</managedObject>

</csvmap>

Figure 3 Profile file example

There are also five example files for the following procedures:

GSM Site creation

WCDMA Site creation

Adjacency creation

Adjacency modification

WCDMA BTS site rehosting

These files are stored in NetAct data storage server:

/etc/opt/nokia/oss/rac/conf/profiles.

These files must be copied to a location accessible by CM Operations Manager before

they can be used with CM Operations Manager.

For more information on the RTE directories, see NetAct Configurator Technical Refer-

ence Guide.

When creating the profile, the names of managed object classes can be checked con-

veniently by browsing the network topology in CM Editor. For instructions, see Viewing

actual managed objects in CM Editor Help.

For more information on used managed objects and parameters, see Adaptation Infor-

mation Browser.

g Objects require special parameters that exist only in the planning interface and are

not available in the parameter database. These parameters are prefixed with the fol-

lowing symbol: $. For more information, see section Required CSV interface param-

eters.

3.2.2 Mapping parameter values to the profile

In figure Profile file example, the profile defines two managed objects: BSC and BCF.

In the corresponding CSV data file, a row contains values for only these two managed

objects, and looks like this (note that the data is only on one row in CSV):

update,PLMN-PLMN/BSC-212,0,testsite,update,PLMN-PLMN/BSC-212/BCF-1,1,testsite,userBCFTemplate

Figure 4 CSV data example

If data has been defined for additional BSC and BCF objects (for example, BSC-213 and

BCF-2), the CSV file would contain two rows that are equal in length:

12 DN04187131Issue 7-0


Id:0900d80580743025

CSV file format overview

update,PLMN-PLMN/BSC-212,0,site1,update,PLMN-PLMN/BSC-212/BCF-1,1,site1,userBCFTmplupdate,PLMN-PLMN/BSC-213,0,site1,update,PLMN-PLMN/BSC-212/BCF-2,1,site1,userBCFTmpl

Figure 5 CSV data example

If an object does not have a value for a parameter or several parameters, empty

columns must be placed in CSV. For example, for data that contains only one BSC but

several BCFs, the rows in CSV would look like the following:

update,PLMN-PLMN/BSC-212,0,site1,update,PLMN-PLMN/BSC-212/BCF-1,1,site1,userBCFTmpl,,,,,update,PLMN-PLMN/BSC-212/BCF-2,1,site1,userBCFTmpl

Figure 6 CSV data example with empty columns

The second row has four empty columns, separated by commas, to indicate the number

of tags for the BSC object in the profile and their position.

g For more information on managed objects and parameter values, see Adaptation

Information Browser.

Note also that there are some attributes and parameters that exist only in the

planning interface. For a quick reference of their possible values, see Section

Summary tables of interface parameter usage.

g Parameter mapping rules are different dor List and structured list parameters. For

more information and examples, see List parameters and Structured parameters.

3.3 Internal and UI parameter values

A CSV file can containinternal parameter values (that is, values in the database) or UI

values (that is, values shown in the Graphical User Interface of NetAct applications).

When importing the CSV file contents into a plan in CM Operations Manager or export-

ing a plan or actual configuration to the CSV file, you can select to use either the “UI

values” or “Internal values”. See the instructions in Importing a plan in CM Operations

Manager Help.

g If the CSV file contains UI values but the Internal values option is selected in import

(or vice versa), import in CM Operations Manager fails.

For more information on the UI values and formula for calculating the corresponding

internal values, see Adaptation Information Browser.

DN04187131Issue 7-0

13

CSV Interface for Configuration Management Data Required CSV interface parameters

Id:0900d80580743025

4 Required CSV interface parametersThis chapter describes special attributes and parameters that must be defined in the

profile file and in the CSV data file.

4.1 Special parameters for managed object identification

Every managed object should have its identification parameters specified. The most

common identification parameter is the object’s DN (Distinguished Name), such as

PLMN-PLMN/RNC-1/WBTS-1. However, there are also other identification methods

available.

Object creation may also require special parameters that exist only in the planning inter-

face. In the CSV interface, they are prefixed with the following symbol: $. For a quick

reference on the possible values of these items, see the tables in section Summary

tables of interface parameter usage.

4.1.1 Managed object identification by DN

The value of the$dn parameter defines the Distinguished Name of the managed object:

<managedObject class="NOKRNC:WBTS">




</managedObject>

The corresponding line in CSV would read as follows:

CREATE,PLMN-PLMN/RNC-100/WBTS-100

4.1.2 Global Identification parameters

This section specifies parameters for cell identity and adjacency-related parameters.

4.1.2.1 GSM CGI (Cell Global Identity)

Instead of $dn, BTS can be recognized with GSM CGI identification parameters which

are $CI, $LAC, $MCC and $MCC.

Example with $dn:

<managedObject class="NOKBSC:BTS">




</managedObject>

Example with GSM CGI:











</managedObject>

14 DN04187131Issue 7-0


Id:0900d80580743025

Required CSV interface parameters

g GSM cell identification by CGI parameters might cause problems if the option

‘Segment Usage’ is in use in the network (that is, if several BTSs are included in one

logical cell). In this case, the segment can consist of multiple BTSs having the same

CGI parameters and therefore the wrong BTS might be updated to the plan when

the CSV plan is imported. (Currently, the master BTS of the segment is always

updated to the plan.)

4.1.2.2 WCDMA and I-HSPA GUCI (Global UTRAN Cell Identity)

Instead of $dn, WCEL and EWCE can be recognized with WCDMA GUCI identification

parameters which are $CI, $RNCId, $MCC and $MNC.

Example with $dn:

<managedObject class="NOKRNC:WCEL">




</managedObject>

Example with WCDMA GUCI:











</managedObject>

Example with I-HSPA GUCI

<managedObject class="NOKIHIADA:WCEL">










</managedObject>

4.1.3 Cell ID-based identification for cells

Instead of $dn, BTS, WCEL, EWCE and WMCEL can be recognized with the $CI iden-

tification parameter.

Example with $CI:





</managedObject>

g In order to use this identification method, the Cell ID (cellId) for BTS, Cell Identifier

(Cid) for WCEL, Cell Identifier (cellId) for EWCE and Cell Identifier ($instance) for

WMCEL must be unique in the NetAct Region. For BTSs, the Cell ID must be unique

for the unlocked BTSs. You cannot create cells using this identification method.

GSM cell identification by Cell ID parameters might cause problems if the option

‘Segment Usage’ is in use in the network (that is, if several BTSs are included in one

DN04187131Issue 7-0

15


Id:0900d80580743025

logical cell). In this case, the segment can consist of multiple BTSs having the same

Cell ID parameters and therefore the wrong BTS might be updated to the plan when

the CSV plan is imported. (Currently, the master BTS of the segment is always

updated to the plan.)

4.1.4 Name-based identification for cells

Instead of $dn, BTS, WCEL, EWCE and WMCEL can be recognized with the $name

identification parameter.

Example with $name:





</managedObject>

g In order to use this identification method, the Name (name) must be unique for BTS,

WCEL, EWCE and WMCEL in the NetAct Region. For BTSs, the Name must be

unique for the unlocked BTSs. You cannot create cells using this identification

method.

4.1.5 Initial Frequency-based identification for TRXs

The TRX can be identified using the current TRX initial frequency value plus BTSId and

BSCId parameters to find the correct object:

<managedObject class="NOKBSC:TRX">








</managedObject>


UPDATE,10,3,33750

g TRXs cannot be created using this frequency-based identification method.

4.1.6 Adjacency-related identification

Identification of adjacencies can take place in different ways, depending on the adja-

cency type (ADCE, ADJW, ADJG, ADJS, ADJI and ADJD).

The adjacencies can be identified by their DN or by the parameters given in the following

table. (The parameter(s) after each bullet point are equivalent to one identification

method.)

16 DN04187131Issue 7-0


Id:0900d80580743025


Adjacency Source cell Target cell

ADCE $sourceDN

$sourceCI$sourceLAC$sourceMCC$sourceMNC

$sourceCI

$sourceName

$targetDN

$targetCI$targetLAC$targetMCC$targetMNC

$targetCI

$targetName

ADJW $sourceDN

$sourceCI$sourceLAC$sourceMCC$sourceMNC

$sourceCI

$sourceName

$targetDN

$targetCI$targetRNCId$targetMCC$targetMNC

$targetCI

$targetName

ADJG

NOKI-HIADA:ADJG

$sourceDN

$sourceCI$sourceRNCId$sourceMCC$sourceMNC

$sourceCI

$sourceName

$targetDN

$targetCI$targetLAC$targetMCC$targetMNC

$targetCI

$targetName

ADJS

NOKI-

HIADA:ADJS

$sourceDN


$sourceCI

$sourceName

$targetDN


$targetCI

$targetName

ADJI

NOKI-

HIADA:ADJI

$sourceDN


$sourceCI

$sourceName

$targetDN


$targetCI

$targetName

WMADJ $sourceDN

$sourceCI

$sourceName

$targetDN

$targetCI

$targetName

ADJD

NOKI-

HIADA:ADJD

$sourceCI

$sourceRncId

$sourceMCC

$sourceMNC

$targetCI

$targetRNCId

$targetMCC

$targetMNC

Table 1 Adjacency-related parameters

DN04187131Issue 7-0

17


Id:0900d80580743025

4.2 Other planning interface parameters

In addition to the identification of managed objects, there are also other special param-

eters and attributes needed in the CSV planning interface. They are used for defining

the operation to be performed, as well as for handling list and structure parameters, and

site parameters.

4.2.1 Operation parameter

The value of the $operation parameter defines which operation is performed:

CREATE, UPDATE or DELETE.

It is not mandatory to specify the operation attribute in the plan file unless its value is

DELETE. When specifying the operation as CREATE and the managed object already

exists then the operation will be changed automatically to UPDATE. When specifying the

operation as UPDATE and the managed object does not yet exist the operation will be

changed automatically to CREATE.

4.2.2 List parameters

Managed objects can have also list parameters, which require a list of values. In the

profile file, the list parameter should be defined so that for every element of the list, there

is a list parameter name defined. The corresponding CSV line holds only the values for

parameters, not their names.

In the example below, the parameter URAId of the WCEL object is a list parameter and

has four elements:














</managedObject>


CREATE,PLMN-PLMN/RNC-100/WBTS-100/WCEL-100,12,13,14,15,TEST_TEMPLATE

For more information and the range of parameter values for the WCEL object used in

this example, see Adaptation Information Browser.

4.2.3 Structured parameters

Managed objects can have also structured parameters, which are a set of named

parameters and their values. Whereas usually one tag in the profile file

equals one column in the CSV file, structured parameters are an exception. In this case,

one tag in the profile represents as many columns in the CSV file as there

are items in the structure.

The structure can be checked by browsing the network topology in CM Editor, or by

checking the values from parameter documentation.

18 DN04187131Issue 7-0


Id:0900d80580743025


g The items of the structured parameter hierarchy are always handled in case sensi-

tive alphabetical order.

In the following example the NOKRNC:COCO object has the structured parameter

AAL2TP:

<managedObject class="NOKRNC:COCO">





</managedObject>

The tag represents all the items in this structure, and represents

as many columns in the CSV file as there are items. In the CSV columns, the items are

sorted in case sensitive alphabetical order. For the AAL2TP structure, the following child

parameters are available:

AAL2PathId

AAL2SignATMIfld

AAL2SignLinkVCI

AAL2SignLiinkVPI

AAL2UPATMIfld

AAL2UPCDVT01Egr

AAL2UPCDVT01Ing

AAL2UPPCR01Egr

AAL2UPPCR01Ing

AAL2UPTPId

AAL2UPUsage

AAL2UPVCI

AAL2UPVPI

COCOA2EA

WAMId

To make sure that all of the items in this hierarchy are included in the CSV, the row in

the CSV file for the COCO object would read as follows:

CREATE,PLMN-PLMN/RNC-185/COCO-1,161021,40,277,277,3618,3618,1,0,120,4900161020,2

For complete list of the parameters and their definitions in the structure for the COCO

object, see Adaptation Information Browser.

4.2.4 Template Name parameter

$templateName is a CSV-specific parameter that defines the template name of the

managed object. This parameter is not mandatory when creating managed objects.

When this parameter is defined in the profile file, the template name value is read from

the CSV file and this value is set for managed objects as the $templateName param-

eter. See the example below.










</managedObject>

DN04187131Issue 7-0

19


Id:0900d80580743025

The corresponding CSV line would read as follows:

CREATE,PLMN-PLMN/RNC-100/WBTS-100/WCEL-100,12,13,TEST_TEMPLATE

4.2.5 Site parameters

The SITE object provides location information such as the coordinates and the address,

for example, BSC, BCF and BTS objects. For more information, see Site object in

NetAct Configurator Principles.

The primary identification for a SITE object is the siteId parameter. The parameter

must be provided when creating a new site, but also when defining other managed

objects that belong to a specific site. For examples, see sections SITE object’s param-

eters and Site identification of a managed object.

(The parameters illustrated in the examples are not mandatory but it is recommended

to use them if the created CSV file is later used in creating objects.)

4.2.5.1 SITE object’s parameters

Because the SITE object is not planned like other managed objects, it is prefixed with

the $ symbol in the planning interface. It is defined as $SITE, with capital letters.

This object has the following parameters (all of these must be defined in the profile file

and CSV file when creating SITE objects):

<managedObject class="$SITE">













</managedObject>

A corresponding CSV line would read as follows:

SITE_ID_3,TEST_NAME_3,ADDR_3,+"60°12’43.590""","+24°53’49.350""",14

In the above example, longitude, latitude, and ground height are presented as UI values

(degrees, minutes and seconds). They can also be presented as Internal values in a

numerical format as follows:

SITE_ID_3,TEST_NAME_3,ADDR_3,602121083,248970417,1400

See also Internal and UI parameter values.

For a summary of these special parameters and their possible values, see SITE object-

related special parameters.

4.2.5.2 Site identification of a managed object

$siteId is a CSV-specific parameter that identifies the site of the managed object. This

parameter is not mandatory when creating an object.

In the example below, the site ID is associated to a specified WBTS.

<managedObject class="NOKRNC:WBTS">

20 DN04187131Issue 7-0


Id:0900d80580743025








</managedObject>

A corresponding CSV line would read as follows:

UPDATE,PLMN-PLMN/RNC-100/WBTS-100,TEST_WBTS_NAME,2,12

4.3 Additional features

The following sections describe additional features for special cases of parameters.

4.3.1 Automatic external cell management

External cells can be imported using a BTS/WCEL profile. If the cell is identified as an

external cell by its Distinguished Name, the managed object class is converted to EWCE

(from WCEL) before object creation. A BTS class does not require class conversion.

Similarly, when a WCEL modification plan is imported using GUCI identification param-

eters, and the corresponding cell found in the NetAct database is an external cell, EWCE

is updated according to the modified WCEL parameters in the CSV file.

4.3.2 Managed object creation using the parent object’s DN

An object in a plan can be created by specifying the $dn for the parent object. The rest

of the DN is generated automatically.

For example, LAPD objects cannot be created by DN, since their instance ID must

always be generated. Thus, in the profile file the object class should be specified as

LAPD and in CSV data the DN of the parent BSC should be used.

4.3.3 Using commas and quotation marks in parameter values

If the parameter value contains commas or quotation marks (“), it must be handled dif-

ferently in CSV since commas are used to separate values from each other in CSV

format.

If the value contains comma(s) such as:

te,st

in the CSV file, it must be enclosed by quotations marks such as:

value1,value2,"te,st",value3

If the value contains a quotation mark such as:

te"st

the quotation marks must be doubled and the entire value must be enclosed with quo-

tation marks like this:

value1,value2,"te""st",value3

If value contains both commas and quotation marks, such as:

rat,,her",com""plex,te"st

the rules in previous examples are applied: the whole value is enclosed with quotation

marks and all quotation marks in the value are doubled, like this:

DN04187131Issue 7-0

21


Id:0900d80580743025

value1,value2,"rat,,her"",com""""plex,te""st",value3

4.3.4 Changing the linked cell of GCAL, WCAL and WLCSE

To identify the linked cell:

For GCAL, you can use target CGI, target CI, or target cell name.

For WCAL, you can use target GUCI, target CI, or target cell name.

WLCSE has WLCSECId, WLCSERncId, WLCSEMCC, and WLCSEMNC parame-

ters (not modifiable in metadata) that can be specified instead of LinkedCellDN to

identify the linked cell.

4.3.5 WCDMA BTS site rehosting

When you use the CSV interface for importing WCDMA BTS site rehosting plans into

NetAct Configurator, and implement the changes in the network with CM Operations

Manager’s Rehosting dialog, you need to know the following:

RNC RNW objects (WBTS, WCEL and COCO) are created as new managed

objects under the new RNC. Therefore, the WBTS, WCEL, and COCO objects’ $dn

parameter contains the object’s new distinguished name under the new RNC. For

example, if you are rehosting PLMN-PLMN/RNC-100/WBTS-100, and the target

RNC is RNC-200 and the new BTS ID is WBTS-200, the value of the $dn parameter

is PLMN-PLMN/RNC-200/WBTS-200.

The oldDN parameter must be defined for WBTS and COCO objects in the CSV file

to be imported. The oldDN parameter is a rehosting-specific non-network parame-

ter which is used for specifying the distinguished name of the managed object under

the old RNC. This information is used by the Rehosting dialog, which reads the old

parameter data and copies the unchanged parameter data from the objects to be

rehosted with the help of oldDN information. For example, if you are rehosting

PLMN-PLMN/RNC-100/WBTS-100, and the target RNC is RNC-200 and the new

BTS ID is WBTS-200, the value of the oldDN parameter is PLMN-PLMN/RNC-

100/WBTS-100.

The assumption is that the WCEL ID (Local cell resource identifier) is not changed

during the rehosting operation. If you need to change the WCEL IDs, and you want

to import the rehosting plan file using the CSV interface, you need to create a CSV

profile of your own. In this case, copy the WCDMA BTS site rehosting example CSV

profile file to your personal computer, add under the WCEL

object class, and store the profile in a location where it can be accessed by the CM

Operations Manager application.

The AXC and its child object classes are not created as new objects, but the objects

are just updated. Therefore, the AXC child objects’ $dn parameter contains the

object’s current distinguished name under the old RNC. For example, if you are

rehosting PLMN-PLMN/RNC-100/WBTS-100, and the AXC ID is AXC-100, and the

target RNC is RNC-200, the value of the $dn parameter for the IPNO object in the

AXC in question is PLMN-PLMN/RNC-100/WBTS-100/AXC-100/IPNO-1.

If you have only imported AXC/FTM data for the rehosting operation, and open the

plan with CM Operations Manager’s Rehosting dialog, you are asked to select the

new RNC from the New RNC drop-down list in Rehosting Dialog. This is because

the AXC/FTM plan contains object updates only, and no information on the new

22 DN04187131Issue 7-0


Id:0900d80580743025


RNC. If you import the RNW data first, or RNW and AXC/FTM data in the same plan

file, no further information is requested when opening the rehosting plan.

The WCDMA BTS site rehosting example CSV profile file contains the parameters

that are likely to be changed during the rehosting operation. If you want to remove

parameters from the profile, or add new parameters to it, you can create a CSV

profile of your own. In this case, copy the WCDMA BTS site rehosting example CSV

profile file to your personal computer, modify the file, and store the profile in a

location where it can be accessed by the CM Operations Manager application.

g When using the CM Operations Manager’s Rehosting dialog, you do not need to

import the adjacencies. They are automatically handled by the tool.

For more information, see XML profile for WCDMA BTS site rehosting.

4.4 Summary tables of interface parameter usage

The following tables summarise the special parameters and attributes used in the CSV

planning interface. The tables also give examples of possible parameter values and the

type of values that can be used in the CSV file.

Special parameter Description

$dn The distinguished name of the object.

Examples:

PLMN-PLMN/RNC-1/WBTS-1

PLMN-PLMN/RNC-100/WBTS-1/WCEL-1/ADJS-1

$BSCId The BSC Identifier.

$BTSId The BTS Identifier.

$RNCId The RNC Identifier.

$name The name of the cell.

$initialFrequency The initial frequency identifier of the TRX.

$CI The Cell Identifier.

$LAC The Location Area Code identifier.

$MCC The Mobile Country Code identifier.

$MNC The Mobile Network Code identifier.

$operation The operation to be performed on the object.

CREATE

UPDATE

DELETE

$templateName The name of the template.

$siteId Identification of an object’s site.

Table 2 Summary of special parameters

DN04187131Issue 7-0

23


Id:0900d80580743025

4.4.1 Adjacency-related special parameters

4.4.2 SITE object-related special parameters


$sourceDN The Distinguished Name of the source cell.

Example:

PLMN-PLMN/RNC-100/WBTS-1/WCEL-1

When creating an adjacency with the $sourceDN special parameter, the

adjacency index is generated automatically.

$sourceCI The Cell Identifier (CI) of the source cell.

$sourceLAC The Location Area Code (LAC) of the source cell.

$sourceRNCId The RNC identification of the source cell.

$sourceMCC The Mobile Country Code (MCC) of the source cell.

It must be three digits in length.

$sourceMNC The Mobile Network Code (MNC) of the source cell.

Min. 2, Max. 3

$sourceName The Name of the source cell.

$targetDN The Distinguished Name of the target cell.

Example:

PLMN-PLMN/RNC-100/WBTS-1/WCEL-2

$targetCI The Cell Identifier (CI) of the target cell.

$targetLAC The Location Area Code (LAC) of the target cell.

$targetRNCId The RNC identification of the target cell.

$targetMCC The Mobile Country Code (MCC) of the target cell.

It must be three digits in length.

$targetMNC The Mobile Network Code (MNC) of the target cell.

Min. 2, Max. 3

$targetName The Name of the target cell.

Table 3 Special parameters for adjacencies


$siteId Identification of the site.

$siteName Name of the site.

$streetAddress Street address of the site.

$longitude The longitude of the SITE object.

Coordinates in the following range:

-1800000000 ... 1800000000

Table 4 Special parameters for the SITE object

24 DN04187131Issue 7-0


Id:0900d80580743025


$latitude The latitude of the SITE object.

Coordinates in the following range:

-900000000 ... 900000000

$groundHeight Height of the physical location in meters, relative to the sea level.


Table 4 Special parameters for the SITE object (Cont.)

DN04187131Issue 7-0

25

CSV Interface for Configuration Management Data Where to find more information

Id:0900d80580743025

5 Where to find more informationFor specific issues related to this document, see the following documents:

XML Interface for Configuration Management Data

CM Operations Manager Help

For more information on parameters, see:

Adaptation Information Browser

26 DN04187131Issue 7-0


Id:0900d80580743025

Appendix A: DTD definition for CSV mapping

6 Appendix A: DTD definition for CSV mappingThe following is the DTD file for CSV mapping.

<!ELEMENT csvmap (header?,managedObject+) >

<!ATTLIST csvmap

version CDATA #FIXED ‘1.0’ >

<!ELEMENT header EMPTY >

<!ATTLIST header

rows CDATA #REQUIRED >

<!ELEMENT managedObject (p+) >

<!ATTLIST managedObject

class CDATA #REQUIRED

version CDATA #IMPLIED >

<!ELEMENT p EMPTY >

<!ATTLIST p

name CDATA #REQUIRED >

Figure 7 File csvmap10.dtd

DN04187131Issue 7-0

27

CSV Interface for Configuration Management Data Appendix B: Example files

Id:0900d80580743025

7 Appendix B: Example filesThis Appendix provides examples of XML profile files and CSV data files, which can be

used for the following operations:

Site creation for GSM and WCDMA

Adjacency planning

WCDMA BTS site rehosting.

How to read the CSV examples

In the CSV file, one row of data may contain so many items that it cannot be viewed

without scrolling. Therefore, the presentation of CSV file contents in this document may

not fully correspond with the layout of an actual file. For clarity, the examples are pre-

sented by using the following layout conventions:

7.1 Site creation (GSM)

This section presents an example of the profile file and the corresponding CSV file used

in Site creation for GSM.

XML profile for GSM Site creation


<!DOCTYPE csvmap SYSTEM "csvmap10.dtd"><csvmap>

<header rows="4"/>

<managedObject class="NOKBSC:BCF">


 


 



 

</managedObject>





 



 



WBTS,,,,,WBTS,,,,,, [...] Header row (for informative purposes)

$operation,$dn,WBTSName, [...] Header row (for informative purposes)

Blank header rows

1 CREATE,PLMN-PLMN/RNC-186/WBTS-170,TEST_WBTS_NAME,3,System,CREATE [...]

Data rows (numbers for informative purposes

to indicate the start of a new row)

Table 5 How to read the CSV examples

28 DN04187131Issue 7-0


Id:0900d80580743025

Appendix B: Example files

 



 



 



 



 



 

</managedObject>

<managedObject class="NOKBSC:TRX">


 



 

















 



</managedObject>

<managedObject class="NOKBSC:HOC">

 


 



 

</managedObject>

<managedObject class="NOKBSC:POC">

DN04187131Issue 7-0

29


Id:0900d80580743025




 



</managedObject>

<managedObject class="NOKBSC:GPC">



</managedObject>

<managedObject class="NOKBSC:LAPD"> 



 



 



 



</managedObject>

<managedObject class="NOKMSC:BTSM"> 



 



 



 

</managedObject>

<managedObject class="NOKBSC:MAL">





  



 








</managedObject>

30 DN04187131Issue 7-0


Id:0900d80580743025


<managedObject class="NOKBSC:DAP"> 



 



 



</managedObject>

<managedObject class="NOKBSC:LCSE"> 



 



 



 



 



 



 



</managedObject>

<managedObject class="NOKANTC:ANTE">




 



 



 



 



</managedObject>

<managedObject class="NOKANTC:GCAL">

DN04187131Issue 7-0

31


Id:0900d80580743025

</managedObject>

<managedObject class="NOKBSC:ADCE">







 



 



 



 



</managedObject>

<managedObject class="NOKBSC:ADJW">


 






 



 



</managedObject>

<managedObject class="$SITE"> 


 



</managedObject>

</csvmap>

Figure 8 XML profile for GSM SITE creation

CSV data for GSM Site creation

g In an actual CSV file, the values for each of the objects are on one line. Numbers

have been added to indicate the start of a new data row.

32 DN04187131Issue 7-0


Id:0900d80580743025

Appendix B: Example filesBCF,,,,,,,,,BTS,,,,,,,,,,,,,,,,TRX,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,HOC,,,,,,,,POC,,,,,,,GPC,,,,L

APD,,,,,,,,,,,,BTSM,,,,,,,,,,ADCE,,,,,,,,,,,,,,,,,,ADJW,,,,,,,,,,,,,$SITE,,,

,,

$operation,$dn,$siteId,$templateName,name,bcfType,lapdLinkName,longitude,latitude,$operation,

$dn,$siteId,$templateName,name,cellId,locationAreaIdLAC,locationAreaIdMCC,locationAreaIdMNC,r

ac,frequencyBandInUse,bsIdentityCodeBCC,bsIdentityCodeNCC,cellType,gprsEnabled,nwName,$operat

ion,$dn,$templateName,initialFrequency,channel0Type,channel0Pcm,channel0Tsl,channel1Type,chan

nel1Pcm,channel1Tsl,channel2Type,channel2Pcm,channel2Tsl,channel3Type,channel3Pcm,channel3Tsl

,channel4Type,channel4Pcm,channel4Tsl,channel5Type,channel5Pcm,channel5Tsl,channel6Type,chann

el6Pcm,channel6Tsl,channel7Type,channel7Pcm,channel7Tsl,tsc,lapdLinkName,$operation,$dn,$temp

lateName,enableIntracellHandover,enableIntraHoDl,enableIntraHoUl,enablePowerBudgetHo,enableUm

brellaHo,$operation,$dn,$templateName,bsTxPwrMax,bsTxPwrMax1x00,bsTxPwrMin,bsTxPwrOffset,$ope

ration,$dn,$templateName,acDlMinCirBcchTrx,$operation,$dn,$templateName,bitRate,abisSigChanne

lSubSlot,abisSigChannelTimeSlotPcm,abisSigChannelTimeSlotTsl,combinedSignalling,name,relatedL

apdLinkName,sapi,tei,$operation,$dn,$templateName,bscIdInMsc,cell_Id,locationAreaCode,mobileC

ountryCode,mobileNetworkCode,name,nwName,$operation,$dn,$templateName,hoMarginPbgt,adjacentCe

llIdMCC,adjacentCellIdMNC,adjacentCellIdCI,adjacentCellIdLac,frequencyBandInUse,bcchFrequency

,adjCellBsicBcc,adjCellBsicNcc,rac,gprsEnabled,msTxPwrMaxGSM,msTxPwrMaxGSM1x00,gprsMsTxpwrMax

CCH,gprsMsTxPwrMaxCCH1x00,$operation,$sourceDN,$targetDN,$templateName,minEcnoThreshold,AdjwC

Id,lac,mcc,mnc,rncId,uarfcn,scramblingCode,sac,$siteId,$siteName,$streetAddress,$longitude,$l

atitude,$groundHeight

1create,PLMN-PLMN/BSC-85964/BCF-

220,SITE220,BCF_Template,BCF220,TalkFamily,OM220,"+24º55'12.570""","+60º13'04.320""",create,P

LMN-PLMN/BSC-85964/BCF-220/BTS-222,,,BTS222,11080,59,262,03,150,GSM

900,0,0,0,TRUE,BTS222,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-222/TRX-

3,System,23,MBCCHC,38,5,TCHF,38,5,TCHF,38,5,TCHF,38,5,TCHF,38,6,TCHF,38,6,TCHF,38,6,TCHF,38,6

,0,T2203,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-221/HOC-

1,System,TRUE,FALSE,FALSE,TRUE,FALSE,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-222/POC-

1,POC_Template,28,28,30,0,,PLMN-PLMN/BSC-85964/BCF-220/BTS-221/GPC-

1,GPC_Template,15,create,PLMN-PLMN/BSC-85964,,16,6,38,30,FALSE,T2204,,Signalling

LAPD,4,create,PLMN-PLMN/MSC-50562/BTSM-

11080,System,10,11080,59,262,03,BTS222,BTS222,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-

221/ADCE-59 11080,,6,262,03,11080,59,GSM 900,23,0,0,150,TRUE,33,30,33,30,create,PLMN-

PLMN/BSC-85964/BCF-220/BTS-222,PLMN-PLMN/RNC-182/WBTS-1410/WCEL-1412,,-

15,1492,100,262,03,182,10700,2,1492,SITE220,SITE220,Hill Street 195,2222

City,FINLAND,"+24º55'12.570""","+60º13'04.320""",12.55

Ta

ble

6C

SV

da

ta f

or

GS

M S

ite

cre

atio

n

DN04187131Issue 7-0

33


Id:0900d80580743025

2,,,,,,,,,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-

221,,BTS_Template,BTS221,11070,59,262,03,150,GSM 900,0,2,0,TRUE,BTS221,create,PLMN-PLMN/BSC-

85964/BCF-220/BTS-221/TRX-

2,TRX_Template,41,TCHF,38,3,TCHF,38,3,TCHF,38,3,TCHF,38,3,TCHF,38,4,TCHF,38,4,TCHF,38,4,TCHF,

38,4,0,T2202,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-222/HOC-

1,System,TRUE,FALSE,FALSE,TRUE,FALSE,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-221/POC-

1,System,28,28,30,0,,PLMN-PLMN/BSC-85964/BCF-220/BTS-222/GPC-1,GPC_Template,15,create,PLMN-

PLMN/BSC-85964,,64,,38,31,FALSE,OM220,,O&M LAPD,1,create,PLMN-PLMN/MSC-50562/BTSM-

11070,System,10,11070,59,262,03,BTS221,BTS221,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-

222/ADCE-59 11070,,6,262,03,11070,59,GSM 900,21,0,2,150,TRUE,33,30,33,30,create,PLMN-

PLMN/BSC-85964/BCF-220/BTS-221,PLMN-PLMN/RNC-182/WBTS-1410/WCEL-1410,,-

15,1490,100,262,03,182,10600,6,1490,,,,,,

3,,,,,,,,,,,,,,,,,,,,,,,,,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-221/TRX-

1,,21,MBCCHC,38,1,TCHF,38,1,TCHF,38,1,TCHF,38,1,TCHF,38,2,TCHF,38,2,TCHF,38,2,TCHF,38,2,0,T22

01,,,,,,,,,,,,,,,,,,,,create,PLMN-PLMN/BSC-85964,,16,2,38,30,FALSE,T2202,,Signalling

LAPD,2,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

,,

4,,,,,,,,,,,,,,,,,,,,,,,,,create,PLMN-PLMN/BSC-85964/BCF-220/BTS-222/TRX-

4,TRX_Template,43,TCHF,38,7,TCHF,38,7,TCHF,38,7,TCHF,38,7,TCHF,38,8,TCHF,38,8,TCHF,38,8,TCHF,

38,8,0,T2204,,,,,,,,,,,,,,,,,,,,create,PLMN-PLMN/BSC-

85964,,16,0,38,30,FALSE,T2201,,Signalling

LAPD,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

,,

5,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,create,PLMN-

PLMN/BSC-85964,,16,4,38,30,FALSE,T2203,,Signalling

LAPD,3,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Ta

ble

6C

SV

da

ta f

or

GS

M S

ite

cre

atio

n (

Co

nt.

)

34 DN04187131Issue 7-0


Id:0900d80580743025


7.2 Site creation (WCDMA)

This section presents an example of the profile file and the corresponding CSV data file

used in Site creation for WCDMA.

XML profile for WCDMA Site creation

<?xml version="1.0"?><!DOCTYPE csvmap SYSTEM "csvmap10.dtd">

<csvmap>

<header rows="4"/>




 



 



 



 < !-- max number of list items: 6 --> 



 



 

 

 



 



 



</managedObject>

<managedObject class="NOKRNC:WBTS"> 



 



 



 





</managedObject>

DN04187131Issue 7-0

35


Id:0900d80580743025

 



 



 



 



 



 



  



 



 



 



</managedObject>

<managedObject class="NOKRNC:ADJG">




 



 



 



 



</managedObject>

<managedObject class="NOKRNC:ADJI">

36 DN04187131Issue 7-0


Id:0900d80580743025


 



 



 

</managedObject>



<managedObject class="NOKRNC:ADJS">

 



 



 



 



 



</managedObject>

<managedObject class="NOKRNC:WLCSE"> 



 



 



 



 



 

</managedObject>

<managedObject class="NOKANTC:ANTE">




 



 



 



 

</managedObject>

DN04187131Issue 7-0

37


Id:0900d80580743025

<managedObject class="NOKANTC:WCAL">





 



 



 



 



</managedObject>

<managedObject class="$SITE"> 


 



</managedObject>

</csvmap>

Figure 9 XML profile for WCDMA SITE creation

g In the <managedObject class="NOKRNC:COCO"> the following parameters

have been removed in RN3.0








The following parameters are new in RN3.0:







After parameter there are following parameters which are

new in RN3.0:

 








have been removed in RN3.0:

38 DN04187131Issue 7-0


Id:0900d80580743025




CSV data for WCDMA Site creation

DN04187131Issue 7-0

39


Id:0900d80580743025

COCO,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,WBTS,

,,,,,,,,,,WCEL,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,ADJG,,,,,,,,,,,,,,,,ADJI,,,,,,,,,,,,,,,,,ADJS,

,,,,,,,,,,,,,,$SITE,,,,

,

$operation,$dn,$templateName,ATMInterfaceID,COCOVPI,VPLTPPCR01Egr,VPLTPCDVT01Egr,CNBAPVCI,CNBA

PPCR01Egr,CNBAPPCR01Ing,CNBAPCDVT01Egr,CNBAPCDVT01Ing,AAL2SigCDVT01Egr,AAL2SigCDVT01Ing,AAL2Si

gPCR01Egr,AAL2SigPCR01Ing,AAL2SignLinkTPId,AAL2SignLinkVCI,AAL2SigCDVT01Egr,AAL2SigCDVT01Ing,A

AL2SigPCR01Egr,AAL2SigPCR01Ing,AAL2SignLinkTPId,AAL2SignLinkVCI,AAL2SigCDVT01Egr,AAL2SigCDVT01

Ing,AAL2SigPCR01Egr,AAL2SigPCR01Ing,AAL2SignLinkTPId,AAL2SignLinkVCI,AAL2PathId,AAL2SignLinkVC

I,AAL2UPCDVT01Egr,AAL2UPCDVT01Ing,AAL2UPPCR01Egr,AAL2UPPCR01Ing,AAL2UPTPId,AAL2UPVCI,COCOA2EA,

WAMId,AAL2PathId,AAL2SignLinkVCI,AAL2UPCDVT01Egr,AAL2UPCDVT01Ing,AAL2UPPCR01Egr,AAL2UPPCR01Ing

,AAL2UPTPId,AAL2UPVCI,COCOA2EA,WAMId,AAL2PathId,AAL2SignLinkVCI,AAL2UPCDVT01Egr,AAL2UPCDVT01In

g,AAL2UPPCR01Egr,AAL2UPPCR01Ing,AAL2UPTPId,AAL2UPVCI,COCOA2EA,WAMId,DNBAPCDVT01Egr,DNBAPCDVT01

Ing,DNBAPPCR01Egr,DNBAPPCR01Ing,DNBAPVCI,TTPId,DNBAPCDVT01Egr,DNBAPCDVT01Ing,DNBAPPCR01Egr,DNB

APPCR01Ing,DNBAPVCI,TTPId,DNBAPCDVT01Egr,DNBAPCDVT01Ing,DNBAPPCR01Egr,DNBAPPCR01Ing,DNBAPVCI,T

TPId,CreateATMTP,CalculateCDVT,ConformanceDef,EarlyPacketDiscard,PartialPacketDiscard,QualityO

fServiceClass,ServiceCategory,$operation,$dn,$siteId,$templateName,name,WBTSName,COCOId,ATMInt

erfaceID,VPI,VCI,BTSAdditionalInfo,$operation,$dn,$templateName,name,CId,LAC,WCELMCC,WCELMNC,R

AC,SAC,WCELCSCNId,WCELPSCNId,RtFmcsIdentifier,NrtFmcsIdentifier,RtFmciIdentifier,NrtFmciIdenti

fier,RtFmcgIdentifier,NrtFmcgIdentifier,PriScrCode,UARFCN,CellRange,URAId,URAId,URAId,URAId,UR

AId,URAId,URAId,URAId,Tcell,PtxTarget,CellAdditionalInfo,SACB,NbrOfSCCPCHs,$operation,$sourceD

N,$targetDN,$templateName,RtHopgIdentifier,NrtHopgIdentifier,AdjgMCC,AdjgMNC,AdjgCI,AdjgLAC,Ad

jgBCCH,AdjgBCC,AdjgNCC,AdjgBandIndicator,AdjgTxPwrMaxRACH,AdjgTxPwrMaxTCH,$operation,$sourceDN

,$targetDN,$templateName,NrtHopiIdentifier,RtHopiIdentifier,AdjiMCC,AdjiMNC,AdjiRNCid,AdjiCI,A

djiUARFCN,AdjiScrCode,AdjiLAC,AdjiRAC,AdjiTxPwrDPCH,AdjiTxPwrRACH,AdjiCPICHTxPwr,$operation,$s

ourceDN,$targetDN,$templateName,NrtHopsIdentifier,RtHopsIdentifier,AdjsMCC,AdjsMNC,AdjsRNCid,A

djsCI,AdjsScrCode,AdjsLAC,AdjsRAC,AdjsTxPwrRACH,AdjsCPICHTxPwr,$siteId,$siteName,$streetAddres

s,$latitude,$longitude,$groundHeight

Ta

ble

7C

SV

da

ta f

or

WC

DM

A S

ite

cre

atio

n

40 DN04187131Issue 7-0


Id:0900d80580743025

Appendix B: Example files1

create,PLMN-PLMN/RNC-185/COCO-

1410,System,1,4,20480,49,56,300,300,3334,3334,6667,6667,150,150,1,40,6667,6667,150,150,2,41,66

67,6667,150,150,3,42,1410001,40,830,830,1206,1206,1,120,49001410001,1,1410002,41,830,830,1206,

1206,2,121,49001410002,1,1410003,42,830,830,1206,1206,3,122,49001410003,1,6667,6667,150,150,72

,1,6667,6667,150,150,73,2,6667,6667,150,150,74,3,true,true,CBR1,enabled,enabled,Class1,CBR,cre

ate,PLMN-PLMN/RNC-185/WBTS-1410,SITE_1410,System,Site1410,Site1410,1410,Not Defined,Not

Defined,Not Defined,Final Testing,create,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-

1412,WCEL_Temp1,WCEL1412,1492,100,262,03,1,1492,1,2,1,1,1,1,1,1,2,10700,11000,1,2,3,4,5,6,7,8,

512 chips,40.0,Additional info,1492,3,create,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-1410,PLMN-

PLMN/BSC-85704/BCF-10/BTS-11,System,1,1,262,03,1700,49,29,0,0,GSM 450/480/850/900/900E/1800

band used,33,33,create,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-1412,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-

1410,WCEL_Temp1_WCEL_Temp1,1,1,262,03,185,1490,10600,6,100,1,24,21,33.0,create,PLMN-PLMN/RNC-

185/WBTS-1410/WCEL-1411,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-

,1410,System,1,1,262,03,185,1490,6,100,1,21,33.0,SITE_1410,SITE_1410,Hill Street 67,1234

CITY,FINLAND,"+60º12'43.590""","+24º53'49.350""",8.5

2,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

,,create,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-

1411,System,WCEL1411,1491,100,262,03,1,1491,1,2,1,1,1,1,1,1,31,10600,11000,1,2,3,4,5,6,7,8,0

chips,40.0,Additional info,1491,3,,,,,,,,,,,,,,,,,create,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-

1410,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-

1412,WCEL_Temp1_WCEL_Temp1,1,1,262,03,185,1492,10700,2,100,1,24,21,33.0,create,PLMN-PLMN/RNC-

185/WBTS-1410/WCEL-1410,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-

1411,System,1,1,262,03,185,1491,31,100,1,21,33.0,,,,,,

3,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

,,create,PLMN-PLMN/RNC-185/WBTS-1410/WCEL-

1410,WCEL_Temp1,WCEL1410,1490,100,262,03,1,1490,1,2,1,1,1,1,1,1,6,10600,11000,1,2,3,4,5,6,7,8,

0 chips,40.0,Additional info,1490,3,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Ta

ble

7C

SV

da

ta f

or

WC

DM

A S

ite

cre

atio

n (

Co

nt.

)

DN04187131Issue 7-0

41


Id:0900d80580743025

7.3 Adjacency planning

This section presents an example of the profile and the corresponding CSV data used

in adjacency creation planning (ADJS, ADJD, ADJI, ADJW, ADJG, ADCE, and ADJD).

XML profile for planning adjacency creation

<?xml version="1.0"?><!DOCTYPE csvmap SYSTEM "csvmap10.dtd">

<csvmap>

<header rows="4"/>



<managedObject class="NOKBSC:ADCE">


 



 



 


 



 



 



 

</managedObject>

<managedObject class="NOKBSC:ADJW">


 







 



 

</managedObject>

<managedObject class="NOKRNC:ADJG">

42 DN04187131Issue 7-0


Id:0900d80580743025


 



 



 



</managedObject>

<managedObject class="NOKRNC:ADJI"> 



 



 



 







 



 



</managedObject>

<managedObject class="NOKRNC:ADJS">

 


 





 


 



 



</managedObject>

<managedObject class="NOKRNC:ADJD">

DN04187131Issue 7-0

43


Id:0900d80580743025

 


 



 

</managedObject>

</csvmap>

Figure 10 XML profile for adjacency planning

CSV data for adjacency planning

44 DN04187131Issue 7-0


Id:0900d80580743025

Appendix B: Example filesADCE,,,,,,,,,,ADJW,,,,,,,,,,,,,,ADJG,,,,,,,,,,,ADJI,,,,,,,,,,,,ADJS,,,,,,,,,,,,,

$operation,$sourceCI,$sourceLAC,$sourceMCC,$sourceMNC,$targetCI,$targetLAC,$targetMCC,$t

argetMNC,hoMarginPbgt,$operation,$sourceCI,$sourceLAC,$sourceMCC,$sourceMNC,$targetCI,$t

argetRNCId,$targetMCC,$targetMNC,minEcnoThreshold,txDiversityInd,intSystemDaEcioThr,isnc

crFddQualityThr,fddReportingPriority,$operation,$sourceCI,$sourceRNCId,$sourceMCC,$sourc

eMNC,$targetCI,$targetLAC,$targetMCC,$targetMNC,RtHopgIdentifier,NrtHopgIdentifier,$oper

ation,$sourceRNCId,$sourceMCC,$sourceMNC,$sourceCI,$targetRNCId,$targetMCC,$targetMNC,$t

argetCI,NrtHopiIdentifier,RtHopiIdentifier,AdjiTxDiv,$operation,$sourceRNCId,$sourceMCC,

$sourceMNC,$sourceCI,$targetRNCId,$targetMCC,$targetMNC,$targetCI,NrtHopsIdentifier,RtHo

psIdentifier,AdjsTxDiv,AdjsEcNoOffset,AdjsDERR

1delete,20632,115,262,03,20631,115,262,03,2,update,20632,115,262,03,1,185,262,03,-

13.5,No,-14.5,-15,Reporting Priority Is Set To

Normal,update,1490,185,262,03,1700,49,262,03,2,1,update,185,262,03,1490,185,262,03,1492,

2,1,Tx Diversity in use,update,185,262,03,1490,185,262,03,1491,3,3,Tx Diversity not

used,0.5,TRUE

2,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,update,185,262,03,1491,185,262,03,1492,3,2,Tx

Diversity not used,,,,,,,,,,,,,,

Ta

ble

8C

SV

da

ta f

or

ad

jace

ncy p

lan

nin

g

DN04187131Issue 7-0

45


Id:0900d80580743025

7.4 XML profile for WCDMA BTS site rehosting

This section contains an example of a rehosting profile file.


<!DOCTYPE csvmap SYSTEM "csvmap10.dtd"><csvmap>

<header rows="4"/>



 


 

</managedObject>

<managedObject class="NOKAXC:IAIF"> 



</managedObject>

<managedObject class="NOKAXC:IEIF">




</managedObject>

<managedObject class="NOKAXC:INTP">


 

 

</managedObject>

<managedObject class="NOKAXC:IPNO"> 



 



</managedObject>

<managedObject class="NOKAXC:IPRT">


 

 



</managedObject><managedObject class="NOKRNC:WBTS">





 

</managedObject>

<managedObject class="NOKRNC:WCEL">

46 DN04187131Issue 7-0


Id:0900d80580743025


</managedObject>

<managedObject class="NOKIPA:IAIF">

 



 



</managedObject> <managedObject class="NOKIPA:IEIF">



 



 



 </managedObject>

<managedObject class="NOKIPA:IPRT">


 

 



 

</managedObject>

<managedObject class="NOKIPA:TCTT"> 


 

</managedObject>

<managedObject class="NOKIPA:ACCP"> 



<managedObject class="NOKIPA:VPCT">





<managedObject class="NOKIPA:TRDE">




 

</managedObject>

<managedObject class="NOKIPA:UNI"> 


 

</managedObject>

<managedObject class="NOKIPA:VPTT"> 


 

</managedObject>

DN04187131Issue 7-0

47


Id:0900d80580743025

<managedObject class="NOKIPA:VCCT"> 


 

</managedObject>

</csvmap>

Figure 11 Rehosting profile file example


have been removed in RN3.0




The following parameters are new in RN3.0:

48 DN04187131Issue 7-0


Id:0900d80580743028

Index

Symbols

$dn parameter 13, 22$operation parameter 17, 22$SITE parameter 19$siteId parameter 19, 22, 23$sourceCellDN parameter 23$templateName parameter 18, 22

C

checking parameter values 11, 12CM Editor 11, 17Configurator 9CSV data 9, 10CSV file format 7, 9CSV mapping 10, 11

D

DTD of profile file 10

E

elementsheader rows 10p name 10, 17

H

header rows element 10

I

identificationby source cell 15, 23by target cell 15, 23of adjacencies 13, 15of managed object site 19of managed objects 13

importing plans 12internal parameter values 12, 19

L

list parameters 17

M

managedObject element 10

N

NetAct Configurator 7, 9network topology 11, 17

P

p name element 10, 17parameter values

checking 11, 12parameters

$dn 13, 22$operation 17, 22$SITE 19$siteId 19, 22, 23$sourceCellDN 23$templateName 18, 22for SITE object 19internal values 12, 19list parameters 17Site parameters 19siteId 19structured parameters 17UI values 12, 19

planning interface 9, 11, 17profile file

creating 10elements 10overview 9parameters 11

S

SITE object 19Site parameters 19siteId parameter 19source cell identification 23special planning interface parameters 13, 17structured parameters 17

T

target cell identification 23

U

UI parameter values 12, 19

X

XML in profile file 9, 10