NetActPlanner_5_0_ConfigurationIssue1-0.pdf

7/27/2019 NetActPlanner_5_0_ConfigurationIssue1-0.pdf

http://slidepdf.com/reader/full/netactplanner50configurationissue1-0pdf 1/122

Nokia NetAct Planner 5.0

Configuration

Application Note

DN04177508Issue 1-0 en

© Nokia Oyj



Nokia Netact Planner

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for theuse of Nokia Networks' customers only for the purposes of the agreement under which thedocument is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia Networks. The document has been

prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Networks welcomes customer comments aspart of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia Networks and the customer.However, Nokia Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaNetworks will, if necessary, explain issues which may not be covered by the document.

Nokia Networks' liability for any errors in the document is limited to the documentarycorrection of errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FORERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL ORCONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of thisdocument or the information in it.

This document and the product it describes are considered protected by copyright accordingto the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

SLICES -Land Use data, Copyright 2001: Ministry of Agriculture and Forestry, Ministry of Environment, National Land Survey of Finland, Finnish Environment Institute and PopulationRegister Centre. 25 m resolution height model, land cover and forest data, street network,Copyright 2001 National Land Survey. 2m resolution maps and map data integration,Copyright 2001 FM-Kartta Oy.

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

Copyright © Nokia Oyj 2004. All rights reserved.

2 © Nokia Oyj DN04177508Issue 1-0 en



Contents

Contents

1 Overview.................................................................................. 1-1 2 New in 5.0 ................................................................................ 2-1 3 MultiRadio Planner interface ................................................. 3-1 3.1 Synchronisation ........................................................................ 3-1 3.2 Transactions............................................................................. 3-4 3.3 Identifiers .................................................................................. 3-5 3.4 Radio parameters ..................................................................... 3-6 3.4.1 Generating NetAct Configuration file(s).................................... 3-6 3.4.2 Importing NetAct Configuration file(s)..................................... 3-16 3.4.3 Network model........................................................................ 3-26 3.4.4 Common parameters.............................................................. 3-27 3.4.5 2G radio parameters............................................................... 3-30 3.4.6 3G radio parameters............................................................... 3-46 3.5 Using the interface.................................................................. 3-52 3.5.1 Setting up the UMTS network................................................. 3-53 3.5.2 Setting up the GSM network................................................... 3-60 3.5.3 Planning process .................................................................... 3-72 3.5.4 Known problems in NetAct Planner core................................ 3-74 4 Transmission Planner interface ............................................ 4-1 4.1 Overview................................................................................... 4-1 4.2 Accessing the interface............................................................. 4-1 4.3 ATM AXC parameters............................................................... 4-4 4.4 COCO parameters.................................................................. 4-12 A Example of a NetAct configuration export file.....................A-1 B Example of a COCO file..........................................................B-1 C Example of an AXC file...........................................................C-1 Glossary .......................................................................................................i


© Nokia Oyj 3



Overview


© Nokia Oyj 1-1

1 Overview NetAct Configuration Export and the Import functionality link NetAct Planner to the

rest of the NetAct family products. It enables network plans to be transferred to and

from NetAct Radio Access Configurator (GSM and UMTS).Transmission data can be

exported to Plan Editor (AXC data only) to support site configuration file creation andto Plan Manager (COCO data only).

The format of configuration management files (XML) is Nokia defined. The third-party

tools that support the Nokia defined set of parameters can access the configuration

management data files. The file format is textual and can be viewed in any text editor.

However, it is best viewed in XML editors or browsers that support XML.

NetAct Planner supports RAML/CM 2.0 version 1.0 in export and RAML/CM 2.0.

WGS84 is the only supported datum. This is particularly significant if locationing

objects are transferred between NetAct Planner and RAC.

Note : The cmData name-attribute is mapped to the NetAct Planner project name.

2G/3G radio and transmission plans can be exported as a combined XML file to NetAct

Plan Editor, CM Editor (OSS3.1 ED1), or CM Plan Manager (OSS3.1 ED2->) for

further processing within NetAct Planner. 2G/3G radio plans can be imported as a

combined file to NetAct Planner.

Note : NetAct Planner version for which Interface is applicable is 5.0 IR1.



Overview

1-2 © Nokia Oyj DN04177508Issue 1-0 en

Figure 1. Data transfer between NetAct Planner and NetActConfigurator



New in 5.0


© Nokia Oyj 2-1

2 New in 5.0 The following features are introduced in NetAct Configuration Interface Base release

5.0.0.3 for NetAct Planner 5.0 IR1:

• LCSE object import and export.

• WLCSE object import and export.

• Import and export of improved flag group values

• New parameters: Ura Ids, RAC (GSM), BSC ID.

• Increased parameter limits to support BSC3i and BSC2i.

• Optional Flag selection in import and export.

• Selection of BCFs and WBTSs owned by user.



MultiRadio Planner interface


© Nokia Oyj 3-1

3 MultiRadio Planner interface

3.1 SynchronisationOne of the main concepts for this interface is 'synchronisation'. Synchronisation in this

context means that:

• plans in both sides of the interface should hold the same information

• when the plan is changed on one side, the interface can be used to transfer only the

changed information to bring the other side up-to-date.

This differs considerably from the concept of always exporting everything and then

during import, attempting to determine what has changed.

To determine what has changed since the last synchronisation (that is, by the time both

sides of the interface held, to our knowledge, the same information), changes aretracked in separate synchronisation tables. Tables are populated when an element is

created, updated, or deleted. This is implemented using database triggers.

Database triggers are implemented as database table specific. Consequently, no

information on changes to individual parameters is stored, necessitating the export of all

parameters for each changed network element (other than deleted elements). This is due

to an increase in workload and the use of database space that implementing this would

require.

Changing most parameters that are part of the interface, triggers a state change to an

element, causing it to be exported in the next synchronisation. However, some of them

are not exported - usually because they are not associated in the main element table in

the NetAct Planner database, and the connection between tables is not straightforward.

These parameters are still exported if something else triggers the export for thatelement.

Because of the way NetAct Planner saves parameters to database, changes to some

objects also trigger changes to its child, sibling, or parent objects. For example, a

change to neighbours, channels, or any subcell parameters triggers a change to all

ADCEs, ADJWs and TRXs of that BTS and the BTS itself.

The triggers must follow specific rules depending on what has happened, what has

happened before, and whether the element existed on both sides of the interface whenthe plan was last synchronised. For example:





• When a new element is created, it is set to state of 'Created' so that it is exported asa new element in next synchronisation.

• If after synchronisation an element is first deleted and then re-created, it is not set

to a state of 'Created' because to the other side, it is not considered to be a new

object. Instead, it is set a state of 'Updated', because it is likely that the element haschanged. Even if the element has not changed, there is no way of knowing that it

has not.

Another example:

• When an element is updated, it is set to a state of 'Updated' so that in next

synchronisation, it will be exported as having been updated,.

• If after synchronisation an element is first created and then updated, it is not set to a

state of 'Updated' , because the other side considers it a new object. Instead, it is set

to a state of 'Created'.

One important rule is that when an identity of an object is changed (although, you

must not do this) the old object is set to a state of 'Deleted' and the new object is set to

a state of 'Created'. In this situation, no trace of the connection between the prior and

new existence of the element is saved.

The basic rules are shown in the following table, which shows trigger actions with

regards to data in synchronisation tables and actions after export and clearing database

tables:

Event Prior State Reaction New State Comment

Create N/A Add entry Created

Create Deleted Change entry Updated

Update - Add entry Updated

Update Created No change Created

Update Updated No change Updated

Delete - Add entry Deleted

Delete Created Remove entry N/A

Delete Updated Change entry Deleted

Identity update Any Delete for old entry -Create for new entry

Use this table for reaction todelete and create actions basedon existing synchronisationentries.

Export Any Mark exported Any, exported Occurs when exporting data toan XML file. Does not clear theexisting state.

Synchronise Any, exported Remove entry N/A Occurs when clearingsynchronisation tables.

Synchronise Any, not exported None As before Ignore event.

Note : The implemented state machine will not be able to recover from all scenarios

when the identity of an object is changed. This applies to situations where another

object relies on the identity not to change.





© Nokia Oyj 3-3

For example, each adjacency starting from or ending to the object with changed identitywill not have Delete and Create operations imposed on them. Additionally, the

hierarchy of an object might be lost if the identity of a parent element is changed.

Another set of rules must be applied when importing data from the other party to match

the changes on both sides of the interface. These are shown in the table below.

Note : The table also includes invalid scenarios. This represents an attempt to correct

the state tracking system in case it becomes corrupt.

The table contains these columns:

• Operation - as defined in import file for the object (C, U, or D)

• Exists - object exists in NetAct Planner (Y, N)

• Pre-State - the object's state in NetAct Planner prior to import

• Valid - whether or not the scenario is correct or is the consequence of a statetracking error

• Action - how the data is treated during import

• Post-State - the state in which the object is left, after import.

Abbreviations are: C = Create, U = Update, D = Delete, Y = Yes, N = No, S = In

Synchronisation, I = Ignore.

Operation Exists Pre-State Valid Action Post-State

Comments

C N S Y C S

C Y S N U S

C Y C Y U S/U S if all export parameters are specified.

C Y U N U S/U S if all export parameters are specified.

C Y D N U S/U S if all export parameters are specified.

C N C N C S

C N U N C S

C N D N C S

U Y S Y U S

U Y C N U S/U S if all export parameters are specified.

U Y U Y U S/U S if all export parameters are specified.

U Y D N U S/U S if all export parameters are specified.

U N S N C S/U S if all export parameters are specified.

U N C N C S/U S if all export parameters are specified.

U N U N C S/U S if all export parameters are specified.

U N D Y I D Deletion overrides.

D Y S Y D S

D Y C N D S

D Y U Y D S

D Y D N D S Remove synch-table entry only.





Operation Exists Pre-State Valid Action Post-State

Comments

D N S N D S

D N C N D S Remove synch-table entry only.

D N U N D S Remove synch-table entry only.

D N D Y D S

As an alternative to synchronisation, there is an option to export all data as opposed to

changed elements. In this case, everything is exported as Created, without

synchronisation data. This mode of export can be used even if synchronisation tables

and triggers have not been installed for the database.

It is also possible to ignore the synchronisation information in import. This mode of import can be used even if synchronisation tables and triggers have not been installed

for the database.

Note : To keep the state machine in order, it is still necessary to remove Delete-stateinformation for Create-commands and all synchronisation information for Delete-

commands.

Exporting all elements can be used logically as part of the interface only initially, whenexporting the whole project to an empty plan elsewhere. After the whole setting has

been transferred, it is usual to revert to transferring only the changes. Because the other

side should now have the plan with the same information as in NetAct Planner,

exporting changes to another file and clearing the synchronisation tables should

calibrate the state tracking system.

The logical workflow with regards to state tracking depends on the functionality in theRAC side of the interface.

You can update previously exported plans by writing to the same file. However, do notdo this if the data was synchronised after the file was written, and do not do this to a file

produced by an application other than NetAct Planner. Data is updated if identification

and plan match, otherwise a new entry is written in the file. Usually, there is no benefit

to updating the file rather than overwriting it or using another file. Again, depending onthe functionality in the importing application, it is advised that you do not export

changed elements and all elements to the same file in update mode.

3.2 Transactions

Three possible transactions are associated with an element in data transfer:

• Create Used for new elements and when transferring elements without regard to the state

tracking information.

• Update Used for modified elements and in some cases when state tracking is unable to

determine whether or not the element is the same as it was before, and it is safer to

synchronise.







3.4 Radio parameters

MultiRadio Planner keeps track of any changes that occur since the last synchronisation.

This information is used to determine what needs to be exported. Synchronisation clearsthe exported (delta-) information from the database.

3.4.1 Generating NetAct Configuration file(s)

To run NetAct configuration plan export, access MultiRadio Planner and select File |

Export | Project Data | NetAct Configuration. The NetAct Configuration dialog box

opens.

An example dialog box is shown below:





© Nokia Oyj 3-7

Figure 1. Example: NetAct Configuration export dialog box

• Foreign Objects - Exporting selected hierarchies can result in adjacencies that

point to cells in hierarchies that are not exported. If you have selected Foreign

Objects, EGCE/EWCE objects are exported in place of BTS/WCEL for such cells.

This option cannot be selected in BCF/WBTS export.





• Deleted Objects - All deleted objects are exported through this selection.Otherwise they are exported based on hierarchy selection. This is only available in

Changes export.

• All Own SITEs - All SITEs, which belong to selection, are exported. This is only

available in Changes export.

• All SITEs - All SITEs of the project are exported. This cannot be selected for a

BCF/WBTS export.

• Inbound Nbrs - Includes inbound neighbours for sites selected for export.

• Fixed Operation - The operation associated with objects that do not automatically

receive it based on state tracking, can be set.

You can export MultiRadio Planner data (and Transmission Planner data, see Chapter 4)

simultaneously. The export is always performed to a single file.

Export specific comments can be entered in the reserved space.

A progress bar and text are used to indicate progress during the export. The export can

be interrupted while data is being gathered until a file is written at the end of operation.

Warning messages related to the data are displayed in the Message Log window.

After exporting, it is strongly advised that you upload the export information to the

network management system at the earliest opportunity and synchronise the plan

information by clicking Clear.

The synchronisation facility in the dialog box is for clearing the database of temporary

information that is kept for tracking changes between data transfers. Synchronisation

should be performed when the plan data has been successfully imported to Plan Editor,

CM Editor, or CM Plan Manager. The two-stage export and synchronisation guarantees

that data is not lost, even if an export file has become corrupted or lost. If this occurs, itis still possible to re-export the data as long as the synchronisation facility has not been

used.If the export file already exists, you are prompted to either update or overwrite the data

to the file:

Figure 2. Synchronisation message: File Already Exists

To update the data to the file, the file must be a NetAct Planner export file that was

previously exported from the Transmission Planner or MultiRadio Planner modules.The elements that are already present in the file are updated and new elements added to

existing structures in the file. Elements from two or more projects are kept separate.

3.4.1.1 Limiting the export

Export is limited to hierarchies that are selected by marking the root elements in the

adjacent display. The hierarchies contain objects under selected root elements including





© Nokia Oyj 3-9

outgoing adjacencies but not incoming adjacencies. Within selection, you can exporteither all elements or only those elements that have changed since the last

synchronisation. For the conceptual difference between exporting all or changes, see

section 3.1 Synchronisation. Another option is to select BCFs and WBTSs, which are

then exported , with their associated sub-hierarchies. The display changes to reflect thismode of export:

Figure 3. Export in BCF/WBTS mode





Note : Exporting selected hierarchies can result in adjacencies that point to cells whichare not exported, or, if Foreign Objects is selected, EWCE and EGCE objects. NetAct

Planner will not be able to import either these kinds of 'targetless' adjacencies, or EWCE

and EGCE objects.

Invalid objects are not exported as they cannot be imported to the network managementsystem. This behaviour can be used to make a distinction between objects that are ready

to be transferred to the NMS and those that are not. An object is considered invalid if its

numeric identifier is not set (e.g. local cell id is left ‘Unknown’ for a UMTS cell).

SITE elements do not logically belong to any particular hierarchy. They are, however,

treated as belonging to none or more hierarchies based on objects located on them.

To assist in object selection there are sorting, searching, id filtering, owner filtering and

quick selection functions:

• Sort in ascending/descending order by clicking column headers: Name and Id -

columns sort either RNCs and BSCs or WBTSs and BCFs based on the export

mode selection. Sorting is text based.

• Search matches substrings in Name and Id -columns. When a match is found the

object is highlighted, tree collapsed and display scrolled to show the object. The

next search continues from the point of previous match: an unsuccessful search isindicated by an error message. Searching is case sensitive.

• Id filtering by selecting ‘Exclude Invalid IDs’ removes objects with invalid IDs

from the tree display. It does not check ID ranges, but removes IDs which are not

set or ‘0’. Id filtering removes invalid objects from the selection in the display, but

does not affect the export of objects that are in the hierarchy of a selected, valid

object.

• Owner filtering by selecting WBTSs or BCFs owned by a specific user. User is

selected from a list.

• You can quickly select multiple objects for export by using the mouse, ctrl, shift,up arrow, down arrow etc. keys to highlight objects in the tree display, and space

bar to select and deselect highlighted objects.

3.4.1.2 Object and parameter selection - export

Object classes and optional parameters can be selected/deselected from export on

Radio, WCDMA, Common and Flag Option dialog boxes.





© Nokia Oyj 3-11

Figure 4. Radio Options of NetAct Configuration Export

Check-boxes:

• Select Object Select/deselect object class like BSC from export.

• Mark Exported Whether object synchronisation state is updated during export

• Version Object version information.

• ParametersSelect/deselect parameter from export.

Push buttons:

• All Select all parameters; Select Object and Mark Exported check boxes are also

selected in all tabs.

• None De-select all parameters; Select Object and Mark Exported check boxes are also de-

selected in all tabs.





• All Tab Select all parameters in the current tab; Select Object and Mark Exported check

boxes are also selected in the current tab.

• None Tab

De-select all parameters in the current tab; Select Object and Mark Exported check boxes are also de-selected in the current tab.

• Freq Select a pre-defined set of frequency planning parameters and de-select other

parameters (2G only).

• Adj Select a pre-defined set of adjacency planning parameters and de-select other


• OK Accept changed selections, store them and close the dialog box.

• Cancel Cancel changed selections and close the dialog box.

The WCDMA and Common Options dialog boxes work in the same way as the Radio

Options dialog box.

Notes :

1. Selected options are saved in a Configuration Interface .ini file.

2. If you want to ensure that all objects and parameters are exported, click the All

button and then click OK.





© Nokia Oyj 3-13

Figure 5. NetAct Configuration Export Flag Options

Check boxes:

• Select/deselect group Ids of specific objects from the export.

Push buttons:

• OK - Accept changed selections, store them and close the dialog box.

• Cancel - Cancel changed selections and close the dialog box.

3.4.1.3 Maintenance region support

The interface attempts to provide a basic support for multiple network maintenance

regions. This is reflected in the addition of external cell objects and further control over

SITE object export.

It is assumed that one NetAct Planner project may contain a network larger than a

maintenance region. If so, at export the user should restrict the export selection to the

region in the management system, and optionally specify foreign objects to be exported.

Foreign objects could be required by the management system if targetless adjacencies





are not supported, or if the management system needs to analyse the state of thenetwork. In Nokia NetAct solution, they are required by NetAct Optimiser.

Note : Exporting selected hierarchies can result in adjacencies that point to cells which

are not exported, or, if Foreign Objects is selected, EWCE and EGCE objects. NetAct

Planner will not be able to import either these kinds of 'targetless' adjacencies, or EWCEand EGCE objects.

SITE elements do not logically belong to any particular hierarchy. They are, however,treated as belonging to none or more hierarchies based on objects located on them.

3.4.1.4 Atomic data transfer

After exporting data to a file in NetAct Planner, you should check to see if there are any

warnings and correct them if necessary. When the export is 'clean', import the file into

RAC as soon as possible and clear the temporary information in NetAct Planner.

If you continue editing the plan after transferring the data into RAC without clearing the

state tracking system, the information in the system will be incorrect.

If the information in state tracking system becomes incorrect, you can calibrate it by

exporting everything (not necessarily taking the data to RAC), clearing the temporary

information and manually editing the data in RAC to correspond with the data in

NetAct Planner. Alternatively, you can make changes manually in NetAct Planner (or

both), and then clear the state tracking system afterwards with dummy Export and

Clear. It is also possible to clear all synchronisation information by using the NetAct

Interface Administrator tool.

3.4.1.5 Warnings end errors (while exporting)

The general errors that you might encounter are:

Category Example error message

Explanation Solution

Synchronisationtables notinstalled

“Warning:Synchronisationtables do not existin database”

The interface requires additionaldatabase tables and triggers. Wheneither the Import or Export dialogbox is opened, a check is performedto see whether the correct versionsare installed. If they are notinstalled, change export is notpossible.

Install NetActConfigurationInterface. See theInstallation and Admin User Guide for instructions.

Synchronisationtables are oldversions

“Warning: Oldversion of synchronisationtables exist indatabase”

The interface requires additionaldatabase tables and triggers. Importand export dialog check if correctversions are installed.

Install NetActConfigurationInterface. See theInstallation and Admin User Guide for instructions.

NetAct Planner vs. interfacecompatibility

“Error: Thedatabase version isnot supported”

This interface only works on certainversions of the NetAct Planner database.

Abort the export and import.

Obtain a compatibleversion of NetActPlanner or acompatible interface





© Nokia Oyj 3-15



version.

Invalid export file “Error: XML file loadfailed”

When updating an existing file, itmust be in RAML2 file format.

Use another file.

Database errors “Error while readingdatabaseinformation”

Database query failed.

The database may be unavailableor the connection to it may havebeen lost.

The export is aborted.

Depends on thesituation. For example, re-bootthe database or re-establish thedatabaseconnection.

Remote project “Error: Export is notsupported onremote projects”

This functionality is not supportedon remote projects.

Do not attempt toexport from aremote project.

Report file Import report is notwritten: Cannotopen report file

The user do not have writepermission to target directory,where report is written

Get writepermission to targetdirectory

Report filedirectory

Import report is notwritten: Cannot getworking directory

The working directory do not exist Check ControlPanel setting onuser PC

Abnormal errors “Error: Unidentifiederror in loadingobjects”

Due to various problems such as acorrupt database, a programmingerror, a software componentregistration problem, etc.

The export is aborted.

Case by case,depending on theerror. Could requireadministrator or product support.

Errors in configuration for UMTS parameters usually display a warning message in theMessage Log window. They do not prevent the exporting of objects, but suggest that

something may not be understood during the import to RAC.

You should always take action if you receive warning messages - correct the errors and

re-export the data until no warnings appear.

Note : Warnings are primarily displayed for the object in question and not necessarily

for a referring object (for example, invalid LcrId is reported for the WCEL in question,

not ADJs).

In UMTS there are two main categories of errors:

Category Example error

message


Parameter out of range

“Warning: Pilot power out of range inNodeB0A”

The parameter value is not withinthe acceptable range for RAC.Importing the parameter to RAC islikely to fail.

Set the value withinthe correct range.

Identifier notunique

“Warning: WBTS Id isnot unique under thecontrolling RNC inNodeB0”

Element identity is determined inRAC, based on numeric identifiers.If they do not satisfy pre-definedconstraints, elements cannot beuniquely identified.

Select an identifier that complies withthe rules of uniqueness.





Errors in configuration for GSM parameters usually display a warning message in the

Message Log window. They do not prevent the exporting of objects, but suggest that

something is not understood in RAC import.

You should always take action if you receive warning messages - correct the errors and

re-export the data until no warnings appear.

In GSM, the main categories of errors are:


Explanation To correct


Warning: MNC of cellHightStreet5 is invalid

The Parameter value is not withinthe acceptable range for RAC.Importing the parameter is likely tofail.

cellId : Only cells with cellId in the

correct range are exported.

Set the value towithin the correctrange.

Identifier not set Warning: BSC ID iszero in BSC BSC55

The ids are not set to a valid value. Set the value towithin the correctrange.

Identifier notunique

Warning: BSC ID 55of BSC BSC_55 hasduplicate in BSCBSC44

The element identity is determinedin RAC, based on numericidentifiers. If they do not satisfy pre-defined constraints, elementscannot be uniquely identified.

Select an identifier that complies withthe rules of uniqueness.

3.4.2 Importing NetAct Configuration file(s)

To run NetAct configuration plan import, access Radio/WCDMA Planner and select

File | Import | Project Data | NetAct Configuration. The NetAct Configuration import

dialog box opens.

You can import Radio Planner and WCDMA Planner data simultaneously from a singlefile.

Import is implemented as a three stage operation: load, validate and import.

1. The content of the import file is loaded and information is displayed.

2. The file contents are verified against the database to be able to identify any

problems in import in advance.

3. Data is written into the NetAct Planner database.

A progress bar and text are used to indicate progress during import.

An example dialog box is shown below:





© Nokia Oyj 3-17

Figure 6. Example: NetAct Configuration import dialog box

• Ignore State - Ignores object state information in import.

• Update Only - Allow only updating of objects in import.

• Report - Enable writing of a report file for modified parameters.

Information about the treatment of each object, if you select to go ahead with the

import, is available after validation. The Status column indicates successful import (Ok ),

successful import with a correction to the state information of the object ( Fix), if the

import to cellsite, GSM cell, NodeB or UMTS cell were denied ( Denied ) or refusal to

import ( Refuse). To access an explanation of the status, double-click the object line

anywhere to the right of the Object column. A box similar to this one appears:

Figure 7. Validation Report box





In the above example, the object already exists and the Create operation is changed toUpdate. The object has been edited on the NetAct Planner side, therefore the Flag

indicating the object status (either None, Created, Updated, or Deleted) since the latest

synchronisation, is Updated.

After validation, the operation-column changes to reflect the actual action applied onthe object in import.

These restrictions aim to prevent users from editing database tables simultaneously:

• If there are other users working on the same project, the import is refused.

• After validation begins, other users are prevented from logging in to the project

until the import has finished, a new load operation has been started, or the import

dialog box is closed.

• After validation begins, other NetAct Planner windows are frozen until validationhas failed, import has finished, a new load operation has been started, or the import

dialog box is closed.

• Simultaneous imports into one database (not just one project) are prevented.

3.4.2.1 Object and parameter selection - import

Object classes and optional parameters can be selected/deselected from export on Radio,

WCDMA and Common Option dialog box.





© Nokia Oyj 3-19

Figure 8 Radio Options of NetAct Configuration Import

Check boxes:

• Select Object Select/unselect object class like BSC from import.

• Parameters Select/deselect parameter from import.

Push buttons:

• All

Select all parameters; Select Object check box is also selected in all tabs.

• None

Deselect all parameters; Select Object check box is also de-selected in all tabs.

• All Tab

Select all parameters in the current tab; Select Object check box is also selected in

the current tab.

• None Tab

Deselect all parameters in the current tab; Select Object check box is also de-

selected in the current tab.





• Freq Select a pre-defined set of frequency planning parameters and de-select other


• Adj

Select a pre-defined set of adjacency planning parameters and de-select other parameters (2G only).



The WCDMA and Common Options dialog boxes work in the same way as the Radio

Options dialog box.

Notes :

1. Selected options are saved in Configuration Interface ini-file.

2. If you want to make sure that all objects and parameters are imported, click All

button and then click OK.





© Nokia Oyj 3-21

Figure 9 Flag Options of NetAct Configuration Import

Check-boxes:

• Select/deselect group Ids of specific object from import.

Push buttons:



3.4.2.2 Timer dialog box

Import can be timed to start at a specific time. Start time can be set 24 hours forward.





Figure 10 Timer dialog box - 'Off' state

Figure 11 Timer dialog box - 'On' state

Before the Timer dialog box can be opened, export file and import options need to be

selected. When the timed import starts, Load, Validate and Import are performed asconsecutive operations.

On the Timer dialog box, set Import Start Time as the time you want the import to start.

Clicking Start Timer starts the timer and Stop Timer stops it. Once the timer has been

started, you should leave the Timer dialog box open until the import has finished. To

cancel a timed import, stop the timer and close the dialog box.

3.4.2.3 Report parameter changes

When the Report tick box has been selected, a report about changed parameters iswritten in a text file in the directory of the import file. The name of the report is, for

example,‘PlannerConfImport20040616090145.txt’ where 20040616090145 is the date

and the time of the import in format YYYYMMDDHHMMSS.

The reported parameters are BCC, NCC, scrambling code, channels of carriers of

subcell, RAC, LAC and number of changes in neighbour list for UMTS Cells and GSMCells.

An example report file:

Nokia NetAct Planner Configuration Import Change Report 15:36:50 15\6\2004

VERSION: 5.0.0.3

PARAMETER :SYSTEM :CELLNAME :OLD :NEW :CHANGE

LAC :WCDMA :WElektroniikka-1 :1 :8300 :1SC :WCDMA :WElektroniikka-1 :121 :123 :1RAC :WCDMA :WElektroniikka-1 :1 :8 :1

ADJS :WCDMA :WElektroniikka-1 : : :2ADJS :WCDMA :WElektroniikka-2 : : :1

ADJG :WCDMA :WSuosaari-2 : : :1ADJG :WCDMA :WTelekara-1 : : :1





© Nokia Oyj 3-23

BCC :GSM :COKUTOJA000 :1 :4 :1

NCC :GSM :COKUTOJA000 :1 :7 :1LAC :GSM :COKUTOJA000 :100 :1 :1CH :GSM :COKUTOJA000\macro1800\TCHF_1800 :842,839 :842,821 :2

ADCE :GSM :COKUTOJA000 : : :1

ADJW :GSM :COKUTOJA000 : : :2ADJI :GSM :COKUTOJA000 : : :1

3.4.2.4 Deny import

Import to selected cellsite, GSM cell, NodeB or UMTS cell can be denied by creating a

flag group named ‘Deny Import’ with flag values ‘No’ and ‘Yes’. The flag group

default value should be ‘No’. Flag group should be associated to object types CellSite,

Cell (GSM), Node B and/or Cell (UMTS).

By selecting ‘Yes’ for the value of the flag in any cellsite, GSM cell, NodeB or UMTS

cell, that object and its child objects are not changed in import and their action is

displayed in the GUI as ‘ignore’ and Status as ‘Denied’.

Figure 12 Creating a flag group





Figure 13 Associating a flag group

3.4.2.5 Warnings and errors (while importing)

Warnings are usually displayed at the validation stage. A basic warning is given if thedefined operation in the file is not logical compared with the state of the database, but

this is not usually a reason to refuse the object in import.

If import is refused, for example, due to invalid or missing mandatory parameter or

invalid references, this is also displayed in the Message Log during the validation stage.

Note : If some failures to import object data cause a cascading effect, for example, if a

create operation for a WBTS fails, it is not possible to create its descendants.

Category Example error message(s)


RAML2 formaterrors. Unsupportedobjects

Unknown managedobject type. A wrong or unsupported object typewas found in the file.

The object is not imported.

If it is an unsupportedobject, no action isrequired.

Invalid Identification Error: Unidentified RNC -Will not be imported.

Error: BTS managedobject does not havecorrect distName.

Object identification is missing or obscure.

The object import is refused.

Correct the object inRAC.





© Nokia Oyj 3-25

Category Example error message(s)


Invalid reference Warning: Invalid Sitereference in RNC0.

Parent BSC not found.

There is a missing or invalidreference to another object.

The parameter or object import isrefused, depending on the referenceand import operation.

Correct the reference inRAC.


Warning: CId out of range in NodeB0A.

The parameter either does not existor its value is not within theacceptable range for RAC.

The parameter or object import isrefused.

If the value is supported,correct the value inRAC.

Invalid objecthierarchy

Warning: Valid WBTSparent not found for NodeB0A.

No valid cell layer withrequired carriers.

It is not possible to create a newWCEL without unambiguous parentdefinition. Update is possible in the3G side due to name-basedidentification.

There should be a cell layer with acarrier layer set before import. Thecarrier layer should have importedcarriers of TRXs and MALs.

If this error occurs, even if youalready have a cell layer with validcarrier layers, then check whether or not you have a slave BCF. A slaveBCF that has same carriers as amaster BTS, needs a separate celllayer from the master BTS.

The object import could be refused.

Correct the identifiers inRAC.

Add carriers,carrierlayers andcellayers.

Duplicate object Duplicate object. An object with same distName wasalready imported.


Correct the cause or update manually.

Duplicate id inNetAct Planner

Duplicate bscId in DB. Object id is not unique in NetActPlanner.


Remove duplicate IDfrom NetAct Planner.

Object refused Import for NodeB0Arefused: Unidentifiedoperation.

When the object import is refused,an error message states the reasonfor the refusal.

Correct the cause or update manually.

There are also some reasons for declining the whole import, such as:



More than oneproject login

Error: There are other users connected to theproject.

Import needs to be performedwithout other users being able toedit the project information. Notallowing multiple log-ins alsoensures that all users get an up-to-date picture of the data when theyre-connect after import.

Import at a time when noother project users arelogged in.

Remote project Error: Import notsupported on remoteprojects.

This functionality is not supportedon remote projects.

Do not attempt importingto a remote project.







Co-ordinate systemsdon't match

Error: Different co-ordinate system - import

refused.

If the co-ordinate system in RAC isdifferent from that in NetAct Planner,

location information is incompatiblebetween them. NetAct Planner doesnot support automatic conversionsin import.

Use just one system.

Make externalconversions.

Un-committed datain the project

Error: Plan containsuncommitted data.

Import is only supported when allinformation relevant in import for theuser is committed to the database.

Commit everythingbefore importing.

Invalid import file Error: XML file loadfailed - Wrong rootelement.

Error: XML file loadfailed - Wrong RAMLversion.

The XML file contains either incompatible data or it is not aRAML 2.0 file.

Alternatively, the file may contain adocument type declaration and theassociated DTD cannot be found.

Check the file type andversion.

Comment out theincompatible row or acquire the DTD.

<!—DOCTYPE ramlSYSTEM 'raml20.dtd'-->

File data belongs toanother project

Error: Project not foundin import file.

If the file does not containinformation for the open project,import does not proceed.

If the project name doesnot match that in the file,or an un-named projectcannot be found, correctone or the other.

Insufficient projectdefinition

Error: No PLMNs foundin the project.

The UMTS plan is imported to anexisting project which must includeat least one (preferably only one)PLMN object.

Create a PLMN Networkobject in the NetActPlanner Site Database.

Insufficientpermissions

Error: Insufficient importpermissions.

The user must be authorised toperform imports.

An administrator canauthorise imports.

If database errors occur during import, the changes should be rolled back to the initialstate. It is possible though, that the import lock is left on and will prevent future

imports. Should this happen, an administrator can release the import lock using the NetAct Interface Administrator tool.

For other general error categories, see the equivalent section in export (3-14 W arnings

end errors.

3.4.3 Network model

The interface is based on this network model:





© Nokia Oyj 3-27

Figure 14. Interface network model

The network model is idealistic and does not represent the underlying NetAct Planner network model, so a mapping between the two is necessary. The main difference is the

position of antenna instance (ANTE), which is shown as being system-independent but

has not yet matured to that level in NetAct Planner. The following sections describe the

information stored in the objects of this network model.

Note : Although it is not reflected in the picture, EGCE and EWCE reference SITE.

3.4.4 Common parameters

During export, header data and network elements with their associated parameters are

written to an XML file. During import, these are displayed in the user interface.

Metadata includes the name of the current project, the logged-in user, the date/ time of

creation of the XML-file and a description of the project/export.

NetworkElement

InterfaceName

Values Comments

cmData type “plan” Fixed default value.

cmData scope “changes”, “all”, “selection” Changes to the plan.

All elements (changed or not).

All elements in selected hierarchies.

cmData name string Project name.

log action “created”, “modified” Initial export for the project in the file or amodification to an earlier export.

log date string Date and time of export.





NetworkElement

InterfaceName

Values Comments

log user string User name.

log appInfo “NetAct Planner 5.0.0.3” Value showing the NetAct Planner andinterface version.

log string User's export specific comments.

Each cmData-section contains a structure to describe the co-ordinate system that is

used. It is presented as an object to comply with the RAML2 file format specification. Itis written in each file. Its purpose is to provide some information about the used co-

ordinate system in case RAC is not using the same system as NetAct Planner. This

structure is not mandatory for NetAct Planner import, but if specified, it is verified

against project co-ordinate system before allowing import to proceed.

COSY

Interface Name Values Comments

group string, for example, “UTM” If present in import, verified against project settings.

coordinateSystem string, for example, “UTM-35N” If present in import, verified against project settings.

datum string, for example, “WGS84” If present in import, verified against project settings.

unit string, for example, “METERS” If present in import, verified against project settings.

The common network elements supported by MultiRadio Planner are: ANTE (antenna

instance), and SITE (property).

Parameter values in tables are either character data or integers. Decimals are converted

to integers by multiplying by 10 per each decimal (for example, 35.25 -> 3525). The

number of decimal places is denoted in parenthesis after the range.

Managed objects have these properties:

All Elements


operation create, update, delete Instructing RAC to create a new element, or update or delete anexisting element.

version “NAP1.0” etc… User-defined.

class “RNC”, “BTS”, etc..

ANTE


antennaId 1..2147483647 db key of antenna, unique identification - in distName.

If the configurator does not provide an acceptable db key atelement creation, the db key created in import is echoed in theMessage Log window (3G).

technology 0, 1 (GSM, UMTS) Indicates the technology in which the antenna is used. Sharedantennas are not yet supported.

siteId 1..32 characters Location reference (export only).





© Nokia Oyj 3-29

ANTE


typeName 1..63 characters idname of antenna type.

bearing 0..360 (1)

tilt -90..90 (1)

height -1000..1000 (2)

corrFactor -100..100 (1)

latitude -90..90 (7) Decimal longitude latitude (DLL), absolute value

longitude -180..180 (7) DLL, absolute value

wbtsName 1..15 characters Parent WBTS (3G only)

index 0..127 Index within parent WBTS (3G only)

propagationModelName

1..32 characters Name of propagation model (3G only)

predictionRadius 100, 200, 300, 400, 500,1000, 2000, 3000, 4000,5000, 6000, 7000, 8000,9000, 10000, 15000, 20000,25000, 30000, 35000,40000, 45000, 50000,60000, 70000, 80000,90000, 100000, 120000,140000, 160000, 180000,200000

Enumerated list of accepted values in metres (3G only)

SITE


siteId 1..32 characters SITE is identified by siteId

streetAddress 0..148 characters Address1;Address2;Town;County;Post Code

groundHeight -500..10000 (2) Not present if map data should be used

siteCode 0..32 characters

longitude -180..180 (7) DLL format

latitude -90..90 (7) DLL format

siteNotes 0..255 characters

candidateStatus “Candidate”, “Nominal”,

“Preferred Candidate”

Taken from Candidate Status Flag. Not exported if “Not Used”.

nominalSite 1..32 characters Only if Candidate Status is in use. Reference to nominal site for candidate sites.

<Other user defined flags>

User defined enumeration Exported for all other flags not set to the default setting. Importallows selecting another existing flag value, not creating newflag values.

If the parameter values are out-of-range, a warning is displayed in the Message Log

window. You should always correct any errors before attempting to import the exported

data into RAC.





Notes :

Some of the elements or their parameters cannot be exported to or imported from RAC.

For more information, refer to the RAC documentation.

It is risky to rename a SITE object because the links in objects located on the SITE arenot automatically updated. If renaming a SITE object cannot be avoided, it is safer if

each object linked to the SITE is 'touched' to ensure they are exported in the next

synchronisation.

3.4.5 2G radio parameters

The 2G network elements supported in MultiRadio Planner are: BSC, BCF, BTS, TRX,

ADCE, ADJW, LMU, GCAL, EGCE, LCSE and MAL. Additionally, the common

parameters described above are supported.

Notes :

1. If the network has super layer TRXs, super TRXs and their parameters require their

own subcell, NetAct Planner recognises that a cell layer is a super layer when the cell

layer name contains the string 'Super'. GSM 1800 super layer should be named as

'Super1800'. If cell has both a regular subcell and a super subcell, their BTS IDs and

BCFs must be same.

2. If a BCF does not have a siteId or latitude and longitude parameters, or if these areinvalid (for example, the siteId is empty and latitude and longitude are 0), then the BCF

and all its child objects are refused during import.

Managed objects have the properties listed below.

BSC


distName 1..999999 BSC-<BSC ID> - RAC requires that C number of BSCis used as BSC ID. The BSC ID is obtained fromtheBSC ID field. This is mandatory in import.

A BSC is not exported if the BSC ID is invalid.

name 1..32 characters The BSC name in RAC can be up to 80 characters inlength. In NetAct Planner, the length of the name islimited to a maximum of 32 characters. NetAct Planner obtains the value from the BSC idname field.

siteId 1..32 characters This is mandatory in import. It is used to find the SITE.The SITE must either have been imported or mustalready exist in the database.

<Flag group name> 1..32 characters This can be any other status flag except 'RACTemplate'.

defaults 1..32 characters If there is a flag group named “RAC Template”, whichhas its value set to BSC, then that status in the BSC isexported.

BCF






© Nokia Oyj 3-31

BCF


distName 1..999999 / 1..660 BSC-<BSC ID>/

BCF-<BCF ID>

This is mandatory in import. NetAct Planner obtainsthe BCF ID value from the BCF ID field. The BCF isnot exported if the BSC ID or the BCF ID are invalid.

name 1..80 characters NetAct Planner obtains the value from the BCF Namefield.

Empty parameters are not exported.

address 0..148 characters Address1 ; Address2 ; Town ; County ; Post Code.NetAct Planner obtains the value from the propertyinformation fields.

Export only.


bcfType 0..65535 0 = 2nd

Gen.Base Station

(B-type)

1 = TalkFamily (D-type)

2 = PrimeSite (F-type)

3 = MetroSite (C-type)

4 = InSite (I-type)

5 = UltraSite

NetAct Planner obtains the value from the NMS Codein the BCF Type.

This is optional in import.

If the parameter is missing, the default value in importis 0 (2

ndGen.Base Station).

Invalid parameters are not exported.

siteId 1..32 characters Reference to SITE object.

This is mandatory in import.

latitude -90..90 (7) Absolute value. Used only if siteId is missing.

Used to find the correct property in import.


longitude -180..180 (7) Absolute value. Used only if siteId is missing.

Used to find the correct property in import.


groundHeight -500..10000 (2) Export only.


<Flag group name> 1..32 characters Any other status flag except 'RAC Template'.

defaults 1..32 characters If there is a flag group named 'RAC Template, whichhas a value set to Site, then that status in the site isexported.





BTS


distName 1..999999 /

1..660 /

1..660

BSC-<BSC ID>/

BCF-<BCF ID>/

BTS-<BTS ID>

This is mandatory in import. NetAct Planner obtainsthe BTS ID value from the BTS ID field in the subcell.

The BTS is not exported if the BSC ID, BCF ID or BTSID are invalid.

name 1..32 characters NetAct Planner obtains the value from the Subcellname field in the subcell. If the field is empty, then thevalue is obtained from the idname in the cell. NetActPlanner imports the value to the subcell name increation and update, and to the idname of the cell in

creation.

Empty parameter is not exported.

cellId 0..65535 This is unique.

NetAct Planner obtains the value from the GSM IDfield in the cell.

The BTS is not exported if the value is unknown.


locationAreaIdLAC 0..65535 NetAct Planner obtains the value from the LAC field inthe cell.


This is optional in import.

segmentId 1..660 NetAct Planner obtains the value from the Segment IDfield in the cell


segmentName 0..15 characters NetAct Planner obtains the value from the Segmentname field in the cell. Use capital letters only(automatically converted if not).


masterBcf 0..1 0 = Slave1 = Master

NetAct Planner obtains the value from the Master BTSfield in the subcell.

If the parameter is missing, the default value is 1.nonBCCHLayerOffset -40..40 NetAct Planner obtains the value from the Non BCCH

Offset field in the subcell.


bsIdentityCodeBCC 0..7 NetAct Planner obtains the value from the BCC field inthe cell.






© Nokia Oyj 3-33

BTS


bsIdentityCodeNCC 0..7 NetAct Planner obtains the value from the NCC field in

the cell.Invalid parameters are not exported.

locationAreaIdMCC 000..999, 3 digits NetAct Planner obtains the value from the MCC field inthe cell.


locationAreaIdMNC 00..999, 2(default) or 3 digits

NetAct Planner obtains the value from the MNC field inthe cell.


rac 0..255 NetAct Planner obtains the value from the RAC field inthe cell.


cellType 0..999999 pico = 50micro = 100macro = 150

NetAct Planner obtains the value from the Cell Typefield in the cell.

The value is also used in import to select the specifiedcell layer for the subcell.


frequencyBandInUse 0..5 0 = GSM1 = GSM18002 = GSM19003 = MultiBand4 = GSM400

5 = GSM850NetAct Planner obtains the value from the Frequencyband field in the Carrier Layer Configuration.


For importing BTSs, carrier layers must exist in the celllayer, which must have the correct frequency band:

“E-GSM 900 Band” = 0“GSM 900 Band” = 0“GSM 1800 Band” = 1“GSM 1900 Band” = 2“GSM 450 Band” = 4“GSM 480 Band” = 4“GSM 850 Band” = 5


hoppingSequenceNumber1 0..63 NetAct Planner obtains the value from the HSN field inthe regular layer subcell.


hoppingSequenceNumber2 0..63 NetAct Planner obtains the value from the HSN field inthe regular layer subcell. Export only.






BTS


hoppingSequenceNumber3 0..63 NetAct Planner obtains the value from the HSN field in

the super layer subcell.Invalid parameters are not exported.

hoppingMode 0..2 0 = non-hopping1= Baseband2 = RF

NetAct Planner obtains the value from the frequencyhopping fields in the regular layer subcell.


usedMobileAllocIdUsed 0..1 0 = No1 = Yes

Regular layer subcell has malist.


Imported when hoppingMode = RF.

usedMobileAllocation 1..660 MAL ID for regular layer.

Only exported when usedMobileAllocIdUsed=1.



maioOffset 0..62 NetAct Planner obtains the value from the MAIO Offsetfield in the regular layer subcell.




maioStep 1..62 NetAct Planner obtains the value from the MAIO Stepfield in the regular layer subcell.




underlayHoppingMode 0..2 0 = non-hopping1= Baseband2 = RF

NetAct Planner obtains the value from the frequencyhopping fields in the super layer subcell.



underlayMaIdUsed 0..1 0 = No1 = Yes

Super layer subcell has malist.


Imported when underlayHoppingMode = RF.





© Nokia Oyj 3-35

BTS


underlayMaAllocationId 1..660 MAL id for super layer.

Only exported when underlayMaIdUsed =1.



underlayMaioOffset 0..62 NetAct Planner obtains the value from the MAIO Offsetfield in the super layer subcell.




underlayMaioStep 1..62 NetAct Planner obtains the value from the MAIO Stepfield in the super layer subcell.




insiteGateway 0..2 0 = none1 = in/in gateway2 = in/out gatewaydefault = 0

Used only for insite.

NetAct Planner obtains the value from the Info field inBCF.


Only imported or exported when parent bcf's bcftype

=4.

insiteGroup 0..999 default = 0


NetAct Planner obtains the value from the 2nd

field inthe site.


Only imported or exported when parent bcf's bcftype=4.

insiteBuilding upper case letters A..Z,

numbers 0..9,

0..20 characters

default = null


NetAct Planner obtains the value from the 1st Name

field in the site.

Empty parameter is not exported.

Only imported or exported when parent bcf's bcftype=4.

egprsEnabled 0..1 0 = No1 = Yes

NetAct Planner obtains the value from the EnableEGPRS field in the subcell.





BTS


gprsEnabled 0..1 0 = No

1 = YesNetAct Planner obtains the value from the EnableGPRS field in the subcell.

antennaHopping 0..1 NetAct Planner obtains the value from the Enable Antenna Hopping field in the cell

corrFactor -100..100 (1) NetAct Planner obtains the value from the Corr'n (dB)field in the cell.

cellEquipmentName Text 1..32 NetAct Planner obtains the value from the Equipmentfield in the cell.

outputPower 0..100 (1) NetAct Planner obtains the value from the PA Outputfield in the subcell.

dedicatedGprsCapacity 0..100 Unit is %, Export only.


propagationModelName Text 1..32 NetAct Planner obtains the value from the Model fieldin the cell.

<Flag group name> 1..32 characters Any other status flag except “RAC Template”.

defaults 1..32 characters If there is flag group named “RAC Template”, whichvalue is set to Cell, then that status in Cell is exported.

TRX



1..660 /

1..660 /

1..16

BSC-<BSC ID> /

BCF-<BCF ID>

BTS-<BTS ID> /

TRX-<TRX ID>

There must be as many TRX IDs selected for carrier layer as there are carriers selected. Exceptions aresynthesiser and site hopping, where there must bemore carriers in malist than in TRXs.


NetAct Planner obtains value from TRX Ids selectionin subcell.

TRX is not exported if BSC ID, BCF ID, BTS ID or TRXID are invalid.

initialFrequency 1..1023, 65535 65535 = InSite.

NetAct Planner obtains the value from the Carrier fields in subcell.






© Nokia Oyj 3-37

TRX


channel0Type 0-11, 12, 13 Mandatory in Import when export file is from OSS3.1

ED3 or later.0 (TCHF), 1 (TCHH), 2 (TCHD), 3 (SDCCH), 4(MBCCH), 5 (MBCCHC), 6 (CCH), 7 (MBCCB), 8(SDCCB), 9 (Not In Use), 10 (E-RACH), 12 (CPBCH),13 (MPBCCH)

ChannelParameters

-chType

0..11, 12, 13 This is mandatory in import when export file is fromOSS3.1 ED2 or earlier.

Parameter is imported if channel0Type do not exist inimported file.

channel type chTypeTCHF 0TCHH 1

TCHD 2SDCCH 3MBCCH 4MBCCHC 5CCH 6MBCCB 7SDCCB 8NotInUse 9ERACH 10CPBCH 12MPBCCH 13

trxFrequencyType 0..16 0 = regular layer trx

1..16 = super layer trx

This is mandatory in import..

“defaults” User definedenumeration

Exported for all child-TRXs, if a flag group called 'RACTRX Template' is defined on GSMCell-level and thevalue set to something other than the default-setting.

(Export only.)

GCAL


distName 1..2147483647 /

1001..65535248 /

ANTE-<antennaId> /

GCAL-<gcalId>


gcalId = cellidbtsId

If cellId or linkedCellDN is missing in impored file thengcalId is read to find GSMcell and subcell.

feederType 1..32 characters idname of feeder

Empty parameter is not exported

antennaId 1..2147483647 Export only.





GCAL


cellId 0..65535 NetAct Planner obtains the value from GSM Id No field

in the cell.Import use parameter to find GSM cell.

GCAL is not exported if CELL ID is invalid.

linkedCellDN related BTSdistName

Import use btsId of parameter to find subcell.

GCAL is not exported if BSC ID, BCF ID or BTS ID inlinkedCellDN are invalid.

LAC 0..65535 Export only.


MCC 000..999, 3 digits Export only.


MNC 00..999, 2(default) or 3 digits Export only.Invalid parameters are not exported.

feederLossPerMetre 0..100 (2) Export only.


feederLength 0..1000 (2) Invalid parameters are not exported.

feederLoss 0.. 100 (2) Export only.


EGCE


siteId 1..32 char Reference to SITE object.

Export only.

bscld 1..999999 BSCID

bcfld 1..660 BCF ID

btsld 1..660 BTS ID

name 1..32 char NetAct Planner obtains the value from the Subcellname field in the subcell. If the field is empty, then thevalue is obtained from idname in the cell.

Export only.

cellId 0..65535 NetAct Planner obtains the value from GSM Id No fieldin the cell.

Export only.

locationAreaIdLAC 0..65535 NetAct Planner obtains the value from the LAC field inthe cell.

-1 = not defined.

Export only.





© Nokia Oyj 3-39

EGCE


locationAreaIdMCC 000..999, 3 digits NetAct Planner obtains the value from the MCC field in

the cell.Export only.

bsIdentityCodeBCC 0..7 NetAct Planner obtains the value from the BCC field inthe cell.

bsIdentityCodeNCC 0..7 NetAct Planner obtains the value from the NCC field inthe cell.

locationAreaIdMNC 00..999, 2(default) or 3 digits

NetAct Planner obtains the value from the MNC field inthe cell.

Export only.

initialFrequency 1..1023, 65535 NetAct Planner obtains the value from the BCCH TRX.

Export only.

frequencyBandInUse 0..5 0 = GSM1 = GSM18002 = GSM19003 = MultiBand4 = GSM4005 = GSM850

NetAct Planner obtains the value from the Frequencyband field in the Carrier Layer Configuration.

For importing BTSs, carrier layers must exist in the celllayer, which must have the correct frequency band:

“E-GSM 900 Band” = 0

“GSM 900 Band” = 0

“GSM 1800 Band” = 1

“GSM 1900 Band” = 2

“GSM 450 Band” = 4

“GSM 480 Band” = 4

“GSM 850 Band” = 5

Export only.

cellType 0..999999 pico = 50micro = 100macro = 150

NetAct Planner obtains the value from the Cell Typefield in the cell.

Export only.

egprsEnabled 0..1 0 = No1 = Yes

NetAct Planner obtains the value from the EnableEGPRS field in the subcell.

Export only.





EGCE


gprsEnabled 0..1 0 = No

1 = YesNetAct Planner obtains the value from the EnableGPRS field in the subcell.

Export only.

defaults 1..32 characters If there is a flag group named 'RAC Template', thathas its value set to Cell, then that status in Cell isexported.

Export only.

ADCE



1..660 /

1..660 /

0..65535 0..65535

BSC-<BSC ID> /

BCF-<BCF ID> /

BTS-<BTS ID> /

ADCE-<LAC><Cell ID>

<LAC> must be a string of 5 characters. If the LAClength is less then space is added on the right.


ADCE is not exported if BSC ID, BCF ID, BTS ID,neighbour CELL ID or neighbour LAC are invalid.

adjCellBsicBcc 0..7 NetAct Planner obtains the value from the BCC field inthe adjacent cell.

Export only.


adjCellBsicNcc 0..7 NetAct Planner obtains the value from the NCC field inthe adjacent cell.

Export only.


adjacentCellIdMcc 00..999, 3 digits NetAct Planner obtains the value from the MCC field inthe adjacent cell.

Export only.


adjacentCellIdMnc 00..999, 2(default) or 3 digits

NetAct Planner obtains the value from the MNC field inthe adjacent cell.

Export only.


bcchFrequency 1..1023 Export only.






© Nokia Oyj 3-41

ADCE


hoMarginPbgt -24..63 unit is dB.

NetAct Planner obtains the value from the margin fieldin neighbour.



Exported for all child-ADCEs, if a flag group called“RAC ADCE Template” is defined on GSMCell-leveland the value set to other than default-setting. (Exportonly.)

ADJW



1..660 /

1..660 /

1..64

BSC-<BSC ID> /

BCF-<BCF ID> /

BTS-<BTS ID> /

ADJW-<index>

If parameters bscId, bcfId or btsId are missing thenparameters are read from distName.

distName is not exported.

ADJW is not exported if BSC ID, BCF ID, BTS ID or neighbour CELL name are invalid.

bscId 1..999999 This is mandatory in import.

bcfId 1..660 This is mandatory in import.

btsId 1..660 This is mandatory in import.

lcrId 0.. 268435455 This is mandatory in import.

NetAct Planner obtains the lcrId value from the LocalCell ID in WCEL.

targetCellName 1..32 characters This is mandatory in import.

rncId 1..4095 Export only.

wbtsId 1..65534 Export only.

mcc 00..999, 3 digits Export only.


mnc 00..999, 2(default) or 3 digits

Export only.


AdjwCId 1..65535 Export only.


lac 1..65535 Export only.






ADJW


sac 0..65535 Export only.


uarfcn 0..16383 Export only.


scramblingCode 0..511 Export only.



Exported for all child-ADJWs, if a flag group called“RAC ADJW Template” is defined on GSMCell-leveland the value set to other than default-setting. (Exportonly.)

LMU



1..660 /

1..65535 /

BSC-<BSC ID> /

BCF-<BCF ID> /

LMU-<Area ID>

This is mandatory in import. NetAct Planner obtains Area ID value from LMU Area ID field.

LMU is not exported if BSC ID, BCF ID or Area ID areinvalid.

lmuName 1..15 characters NetAct Planner obtains the value from the LMU

idname field.


lmuType 0..15 characters NetAct Planner obtains the value from the LMU namefield.


lmuQ1Address 1..3999 NetAct Planner obtains the value from the LMU Address field.


lmuGSMAntennaLatitudeLocation -90..90 (7) NetAct Planner obtains the value from the LMU Antenna location latitude field.


lmuGSMAntennaLongitudeLocation -180..180 (7) NetAct Planner obtains the value from the LMU Antenna location longitude field.






© Nokia Oyj 3-43

LMU


lmuGSMAntennaAltitude 0..1000 heightMode=0 absolute lmu height, heightMode=1 lmu

height is above lowest serving antenna. Servingantenna is antenna of cell of same site first in lmuneighbour list.

NetAct Planner obtains the value from the LMU Heightfield.


rxIsolation 0..1000 (2) NetAct Planner obtains the value from the LMU Total Antenna isolation field.


rxAntennaType 1..63 characters NetAct Planner obtains the value from the LMU Antenna Type field.


lmuBTSAntennaLongitudeLocation -180..180 (7) Serving cell(=first cell in default neighbour list)longitude.

Export only.


lmuBTSAntennaLatitudeLocation -90..90 (7) Serving cell(=first cell in default neighbour list) latitude.

Export only.


lmuBTSAntennaAltitude 0..65535 Serving cell(=first cell in default neighbour list) height.Export only.


lmuGPSAntennaLongitudeLocation -180..180 (7) NetAct Planner obtains the value from the LMU GPS Antenna longitude field.


lmuGPSAntennaLatitudeLocation -90..90 (7) NetAct Planner obtains the value from the LMU GPS Antenna latitude field.


LmuDefaultNeighbourList

-bcchFrequency

-bsicNCC

-bsicBCC

-LAC

-CellID

1..1023

0..7

0..7

0..65535

0..65535

NetAct Planner obtains the values from the LMUMeasured Cells list and from fields in correspondingcells.

Import uses CellID to find neighbour cell. Other parameters are ignored.


siteId 1..32 characters Export only.

<Flag group name> 1..32 characters Any other status flag except “RAC Template”.

defaults 1..32 characters If there is flag group named “RAC Template”, whichvalue is set to Lmu, then that status in Lmu isexported.





MAL



1..660

BSC-<BSC ID> /

MAL-<MAL ID>

This is mandatory in import. NetAct Planner obtainsthe MAL ID value from the subcell.

name 0..32 characters Not supported

frequencyBandInUse 0..5 0 = GSM

1 = GSM1800

2 = GSM1900

3 = MultiBand

4 = GSM400

5 = GSM850

NetAct Planner obtains the value from the FrequencyBand field in carrier layer configuration.


frequency Arr(n), max(n)=63,1..1023

NetAct Planner obtains the values from carriersassigned in subcell. This is mandatory in import.

LCSE



1..999999 /

0..65535 0..65535

BSC-<BSC ID> /

SMLC-<BSC ID>/

LCSE-<LAC><Cell ID>

<LAC> must be a string of 5 characters. If the LAClength is less then space is added on the right.


LCSE is not exported if BSC ID, CELL ID or LAC areinvalid.

bsicBcc 0..7 Export only.


bsicNcc 0..7 Export only.


bCCHFrequency 1..1023 Export only.Invalid parameters are not exported.

antBearing 0..359 º (0) Export only.


altitude 0..1000 (0) Export only.


antHeight 0..1000 (0) Export only.






© Nokia Oyj 3-45

LCSE


antTiltAngle 0..180 º (0) -90..90 º

Export only.


antTiltType 1 (Mechanical), 2(Electrical)

Export only.


lcsGlobalIdCi 0..65535 Export only.

lcsGlobalIdLac 0..65535 Export only.

lcsNeighbors

list of items {lcseListCi, lcseListLac}

0..32 {0..65535,0..65535}

NetAct Planner obtains the values from the LCSEneighbour list in GSM cell.


longitude -180..180 (7) Export only.


latitude -90..90 (7) Export only.


antHorHalfPwrBeam 0..360 º (0) Export only.


latDegrees 0..90 (0) Export only.


latFractions 0..99 (0) Export only.


latMinutes 0..59 (0) Export only.Invalid parameters are not exported.

latSeconds 0..59 (0) Export only.


latSign 0 (+ (positive)), 1(- (negative))

Export only.


lonDegrees 0..90 (0) Export only.


lonFractions 0..99 (0) Export only.


lonMinutes 0..59 (0) Export only.


lonSeconds 0..59 (0) Export only.


lonSign 0 (+ (positive)), 1(- (negative))

Export only.






LCSE


defaults 1..32 characters If there is flag group named “RAC LCSE Template”,

which value is set to LCSE, then that status in LCSE isexported.

If the parameter values are out-of-range, a warning is displayed in the Message Log

window. You should always correct the errors before attempting to import the exported

data into RAC.

If the subcell is not said to be a super layer subcell in the above text, then it is expected

to be a regular layer subcell.

If bscIds, bcfId, btsId, and cellId are changed, the whole plan should be exported or

imported instead of a partial plan.

3.4.6 3G radio parameters

The supported 3G network elements are: RNC, WBTS, WCEL, ADJS (Intra-frequency

Adjacency), ADJI (Inter-frequency Adjacency), ADJG (Inter-system Adjacency to

GSM), WCAL (WCDMA Cell_Antenna_Link), WLCSE and EWCE (External WCEL).

Additionally, the common parameters described earlier are supported.

All the elements have an operation and version. RNC and WBTS network elements

have mainly identifying information.

RNC

NetworkElement


RNC distName / RNCId 1..4095 RNC ID - keep unique.

RNC RNCName 1..15 characters RNC Identity limited to maximum 15characters. Used as identifier in theinterface.

RNC siteId 1..32 characters Reference to location.

RNC / WBTS “defaults” User definedenumeration

Exported if a flag group called “RACTemplate” is defined and the valueset to other than default-setting.(Export only.)

RNC / WBTS <Other user defined flags> User definedenumeration

Exported for all other flags not set todefault-setting. Import allowsselecting another existing flag value,

not creating new flag values.

WBTS


distName / WBTSId 1..65534 NodeB Id - Keep unique under controlling RNC.

WBTSName 1..15 characters WBTS Identity limited to maximum 15 characters.Used as identifier in the interface.





© Nokia Oyj 3-47

WBTS


siteId 1..32 characters Reference to location.

Notes :

1. It is best to keep the entire RAN under a single PLMN. Any object topmost in the

hierarchy (RNC or orphan WBTS) is added to the first (in order of creation) PLMN

network. Other objects added to the hierarchies follow their parents in the PLMN

selection. It is important to remember that it is not possible to re-use numeric IDs by

utilising multiple PLMNs.

2. Additionally, this interface will not work properly if PLMN and logical networks

form a hierarchy, that is, if there is more than a single PLMN network above RNCs (and

WBTSs).

The other managed objects have the properties listed in the table below. (Bold italic

typeface indicates a change/addition since the previous release):

WCEL/EWCE

NetworkElement


WCEL / EWCE RncId 1..4095 In distName for WCEL.

WCEL / EWCE WBTSId 1..65534 In distName for WCEL.

WCEL / EWCE LcrId 0..268435455 Local Cell Id - In distName for WCEL, keep unique.

WCEL / EWCE name 1..80 characters WCEL Idname. Used as an identifier in the interface.

WCEL / EWCE WCELMCC/MCC 000..999 Mobile Country Code - use numericvalues in the text field (export only.).Zeros can be added to the left if necessary.

WCEL / EWCE WCELMNC/MNC 00..999 Mobile Network Code - use numericvalues in text field (export only).Zeros can be added to the left if necessary. The default length is twodigits.

WCEL / EWCE CId 1..65535 UMTS Cell Id.

WCEL / EWCE LAC 1..65535 Location Area Code.

WCEL / EWCE RAC 0..255 Routing Area Code. WCEL / EWCE SAC 0..65535 Service Area Code.

WCEL AdditionWindow 0..14.5 -> 0..29 Soft Handover Search Window .

WCEL PrxNoise -130..-50 (1) Cell Background Noise.

WCEL / EWCE PtxPrimaryCPICH -10..50 (1) Pilot Power.

WCEL Orthogonality 0..1 (2) Orthogonality.

WCEL / EWCE PriScrCode 0..511 Scrambling Code.





WCEL/EWCE

NetworkElement


WCEL PtxTarget -10..50 (1) DL Traffic Power. Mapping changedto another NetAct Planner parameter.

WCEL MaxActiveSetSize 1..3 Active Set Size.

WCEL PrxTarget 0..30 (1) Noise Rise. Mapping changed toanother NetAct Planner parameter.

WCEL PtxOffset 0..6 (1) PtxOffset = Maximum TransmissionPower - DL Traffic Power. Activateload balancing for NodeB type.

WCEL PrxOffset 0..6 (1) PrxOffset = Noise Rise Limit - NoiseRise. Activate load balancing for NodeB type.

WCEL CPICHtoRefRABoffset -10..17 (1) Link Power Offset. Activate

automatic calculation for maximumpower per service for NodeB type.

WCEL DLreferenceBitRate 0.01..16000 (2) Reference DL Bitrate. Activateautomatic calculation for maximumpower per service for NodeB type.

WCEL DLReferenceEbNo -4..16 (1) Reference DL Eb/No. Activateautomatic calculation for maximumpower per service for NodeB type.

WCEL PtxPrimaryCCPCH -35..15 (1) Primary Common Control PhysicalChannel Transmission Power. Thevalue is relative to Pilot channelstrength.

WCEL PtxSCCPCH1 -35..15 (1) Secondary Common Control

Physical Channel TransmissionPower. The value is relative to Pilotchannel strength.

WCEL PtxPrimarySCH -35..15 (1) Primary Synchronisation ChannelTransmission Power. The value isrelative to Pilot channel strength.

WCEL PtxSecSCH -35..15 (1) Secondary Synchronisation ChannelTransmission Power. The value isrelative to Pilot channel strength.

WCEL / EWCE UARFCN / UarfcnDl 0..16383 Downlink Channel Number - UTRA Absolute Radio Frequency ChannelNumber.

WCEL / EWCE UEtxPowerMaxDPCH -50..33 Maximum UE transmission power on

DPCH - Maximum terminaltransmission power, through alldefined terminals using the cell, thatis, cell's carrier. (Export only.)

WCEL / EWCE UEtxPowerMaxPRACH /UEtxPowerMaxRACH

-50..33 Maximum UE transmission power onDRACH - Maximum terminaltransmission power of which alldefined terminals using the cell arecapable. (Export only.)





© Nokia Oyj 3-49

WCEL/EWCE

NetworkElement


WCEL URAId Arr(8) each havevalue range1..65535

The URA identity is the identity of the UTRAN Registration Area.Overlapping URAs can be defined. Amaximum of eight URA identitiescan be defined per cell.

WCEL / EWCE “defaults” User definedenumeration

Exported if a flag group called “RACTemplate” is defined and the valueset to other than default-setting.(Export only.)

WCEL / EWCE <Other user defined flags> User definedenumeration

Exported for all other flags not set todefault-setting. Import allowsselecting another existing flag value,not creating new flag values.

EWCE siteId 1..32 characters Location reference.

ADJS/ADJI/ADJG

Network Element Interface Name Values Comments

ADJS / ADJI / ADJG SourceCellName 1..32 characters Parent WCEL.

ADJS / ADJI TargetCellName 1..32 characters Neighbour WCEL.

ADJS / ADJI / ADJG RNCId 1..4095 For Parent WCEL.

ADJS / ADJI / ADJG WBTSId 1..65534 For Parent WCEL.

ADJS / ADJI / ADJG LcrId 0..268435455 For Parent WCEL.

ADJS / ADJI AdjsRNCid/ AdjiRNCid 1..4095 For Neighbour WCEL.

ADJS / ADJI AdjsWbtsId/ AdjiWbtsId 1..65534 For Neighbour WCEL.

ADJS / ADJI AdjsLcrId/AdjiLcrId 0..268435455 For Neighbour WCEL.

ADJS / ADJI / ADJG AdjsMCC/AdjiMCC/AdjgMCC 000..999 For Neighbour WCEL.

ADJS / ADJI / ADJG AdjsMNC/AdjiMNC/AdjgMNC 00..999 For Neighbour WCEL.

ADJS / ADJI / ADJG AdjsCI/AdjiCI/AdjgCI 1..65535 For Neighbour WCEL.

ADJS / ADJI / ADJG AdjsLAC/AdjiLAC/AdjgLAC 1..65535 For Neighbour WCEL.

ADJS / ADJI AdjsRAC/AdjiRAC 0..255 For Neighbour WCEL.

ADJS / ADJI AdjsCPICHTxPwr/ AdjiCPICHTxPwr

-10..50 (1) For Neighbour WCEL.

ADJS / ADJI AdjsScrCode/ AdjiScrCode 0..511 For Neighbour WCEL.

ADJI AdjiUARFCN 0..16383 For Neighbour WCEL.

ADJS / ADJI AdjsTxPwrRACH / AdjiTxPwrRACH

-50..33 For Neighbour WCEL.

ADJI AdjiTxPwrDPCH -50..33 For Neighbour WCEL.

ADJG AdjgBCCH 1..1023

ADJG AdjgBCC 0..7





ADJS/ADJI/ADJG


ADJG AdjgNCC 0..7

ADJS / ADJI / ADJG “defaults” User definedenumeration

Exported for all child-adjacencies, if a flag groupcalled 'RAC ADJS/I/G Template'is defined on WCEL-level andthe value set to other thandefault-setting. (Export only.)

WCAL


antennaId 1..2147483647 Antenna reference - part of identification, in distName

lcrId 0..268435455 For Target WCEL - In distName

RncId 1..4095 For Target WCEL

WBTSId 1..65534 For Target WCEL

LcrId 0..268435455 Duplicate of lcrId, not in distName

antennaName 1..2147483647 Antenna reference - part of identification, same as antennaId,legacy support only.

cellName 1..32 characters WCEL reference - part of identification.

feederType 1..32 characters Feeder cable reference.

feederLoss 0..100 dB (2) Copied from feeder cable information. (Export only.)

feederLossPerMetre 0..100 dB (2) Copied from feeder cable information. (Export only.)

feederLength 0..1000 m (2)

mha 1, 0 1 = ON0 = OFF

mhaType 1..32 characters If mha is'ON', reference to MHA.

mhaNoise 0..100 dB (1) If mha is 'ON', copied from mha information. (Export only.)

mhaGain 0..100 dB (1) If mha is 'ON'.

rxDiversity 1, 0 1 = ON0 = OFF

txDiversity 1, 0 1 = ON0 = OFF

WLCSE


distName 1..4095/

1..65535

RNC-<RncId>/

WLCSE-<WLCSEid>






© Nokia Oyj 3-51

WLCSE


WLCSEMCC digits ‘000’..’999’ Mobile Country Code - use numeric values in the text field

(export only.). Zeros can be added to the left if necessary.Export only. Invalid parameters are not exported.

WLCSEMNC digits ‘00’..’999’ Mobile Network Code - use numeric values in text field (exportonly). Zeros can be added to the left if necessary. The defaultlength is two digits.

Export only. Invalid parameters are not exported.

WLCSERncId 1..4095 RNC Identifier used for WLCSE hierarchy

Export only.

WLCSECId 1..65535 Cell Identifier


CellName 1..80 characters Name of the parent WCEL, used as identity.

Mandatory in import.

name 1..80 characters Name of the parent WCEL

CovType 1 (outdoor) or 2(indoor)

Coverage Type

EnvCharact 1..3 Environmental characterisation

1=possibly heavy multipath and NLOS conditions 2=no or light multipath and usually LOS conditions 3=not defined or mixed environment

RepeaterExist 0 (No) or 1 (Yes) Informs if repeater exists in the cell . Export only.

MaxCellRad 1..64001 meter,step 10 meter

Maximum radius of antenna main radiation beam in metres.

MaxCellBackRad 0..64000 meter,step 10 meter

Maximum radius of antenna back radiation beam in metres.

AntennaCoordAltitudeGround -500..10000 (2) Ground height at SITE location


AntennaCoordLongitude -180..180 (7) Longitude in DLL


AntennaCoordLatitude -90..90 (7) Latitude in DLL


AntBearing 0..360 º (1) Antenna bearing. Export only.

AntHPBW 1..360 - 360 is

omni

Antenna half power beam width


defaults 1..32 characters If there is flag group named “RAC WLCSE Template”, whichvalue is set to WLCSE, then that status in WLCSE is exported.

Note : Not all the parameters are strictly tied to the WCEL element. Therefore,

changing them does not trigger update information to be stored. When elements are

exported, the changed values for these parameters are retrieved. This relates to





UEtxPowerMaxDPCH and UEtxPowerMaxPRACH. Some parameters not associatedwith WCEL in NetAct Planner cannot be imported. These include PLMN parameters

MCC and MNC, and Terminal Type parameters UEtxPowerMaxDPCH and

UetxPowerMaxPRACH.

If the parameter values are out-of-range, a warning is displayed in the Message Logwindow. You should always correct any errors in the export before attempting to import

the data into Plan Editor or Plan Manager.

3.5 Using the interface

This section describes how to use the interface to make NetAct Planner work together

with RAC.

You must be aware of RAC when using NetAct Planner, and that it is equally important

to set the properties required by RAC as it is to set the properties required by NetActPlanner itself. Additionally, the parameter values should comply with the constraints in

RAC.

Note : To access on-line help information about export, import or options dialogs you

can press F1 and the help system will open a help window, for example:





© Nokia Oyj 3-53

3.5.1 Setting up the UMTS network

3.5.1.1 PLMN

The root node in NetAct Planner is PLMN-network:

Use a single PLMN - do not create hierarchies of PLMN and logical networks, as theinterface does not include information about these, and will not work correctly in such a

case.

In export, MCC and MNC parameters are included in WCEL (NetAct Planner's UMTSCell) level from the NetAct Planner PLMN-object, and a PLMN must exist for the

import to proceed. Filling in MCC and MNC in the PLMN, reduces manual work in

RAC import at least for adjacency objects (ADJS, ADJI and ADJW).

3.5.1.2 Other UMTS equipment and settings

Set Feeders, Mast Head Amplifiers (WCAL) and Antenna Types (ANTE). In export,

their names are sent as references and in import, they are allocated to objects based on

this reference.

Set NodeB Types, allocate them to NodeBs (WBTSs) then activate their load control

and automatic maximum power calculation, unless you have a reason to plan without

using them. This enables the transfer of PtxOffset, PrxOffset, PtxTarget, PrxTarget,

CPICHtoRefRABoffset, DLreferenceBitrate, and DLReferenceEbNo.

Note : RAC might ignore the DLReferenceEbNo-parameter.

Set the downlink channel number for each UMTS carrier used in the network plan. The

corresponding uplink channel number is optional and not transferred in the interface.

The DL channel number (UARFCN) is exported in WCEL, EWCE and ADJI objects. In

WCEL import, a new carrier is added to the parent WBTS and allocated for the WCEL

if the WCEL has an acceptable UARFCN (that is, found in UMTS carriers) not already

allocated for the WBTS.

3.5.1.3 RNC

The root element under PLMN is RNC. This is a key element in RAC, but has limited

use in WCDMA Planner. Due to its role in RAC, it is mandatory that RNCName:

and RNCId:





are set according to the constraints of RAC. In NetAct Planner, an RNC is located on a

SITE (property), which is why new RNCs, imported from RAC, must also have a SITEreference, and the SITE must exist, or be imported at the same time.

3.5.1.4 WBTS

NodeB is under RNC in network hierarchy.

Although NetAct Planner allows you to create NodeBs (WBTSs) that have no parent

RNC, this is not acceptable for RAC. You should always parent your NodeBs before

sending them to RAC for the first time.

Note : Moving a NodeB under a new RNC after it has been transferred to RAC is a re-

hosting operation, which is reasonably complicated for RAC. The data transfer required

for re-hosting does not work automatically using this interface; a manual operation is

needed on both sides of the interface.

Similarly to RNC, the WBTSName:

and the WBTSId:

must be set according to the constraints of RAC. WBTS also requires SITE information

on creation.

To make a meaningful network plan to be simulated in NetAct Planner, you must set up

carriers, antennas and channel resources on NodeB-level. This does not affect WBTS

parameters, but affects other objects such as WCEL, ANTE and adjacencies.

3.5.1.5 SITE

The common term 'SITE' is used to denote the physical location in this interface. In NetAct Planner, the term used is 'property'. For a UMTS network, RNCs and WBTSs

are located on a SITE. The mandatory parameters are siteId:

which as identity, is always required, and co-ordinates:





© Nokia Oyj 3-55

which are needed for creation.

In NetAct Planner, these are always available. In RAC, SITE must be either manually

added or imported. In CM Plan Manager export, you must select Export also site

information to export SITE objects.

To export ground height for the SITE, you must override the map setting, even if it is

just with the same value:

,

3.5.1.6 ANTE

Antennas are not visible in NetAct Planner's Site Database, but are tied to, and childrento, NodeBs:

There are no specific requirements for setting ANTE information in NetAct Planner. In

RAC, it is important to remember to set the identity of the antennas (this is not visible in

the NetAct Planner interface) and include a WCAL link for each new ANTE in export.





3.5.1.7 WCEL (EWCE)

UMTS cell needs its identities. For NetAct Planner the name:

must be set separately for new objects and specified to be included in RAC export. For

RAC, set the numeric identifiers LcrId:

and CId:

.

and also set LAC, RAC, URA 1-8 and SAC.

Under Cell Parameters, set values in UMTS Parameters in the same way that you wouldto prepare the cell for simulation and assign the carrier:

Do the same under Load & Power Control unless you do not want to use them:





© Nokia Oyj 3-57

,

The remaining user equipment parameters (UEtxPowerMaxDPCH and

UEtxPowerMaxPRACH) exported with WCEL are included after you have set theTerminal Types, Bearers and Services, which you would normally do in preparation for

simulating the network.

3.5.1.8 WCAL

The many-to-many connection between ANTEs and WCELs is modelled with Feeders

in NetAct Planner. You create a feeder instance under WCEL by assigning an antenna

for use in the cell.





The identity is formed by the links to the WCEL and ANTE, which is unambiguous.

Some of the data is exported (not imported) from the Feeder and MHA type objects if

they have been assigned. When exporting WCALs from RAC, the WCEL name must be

set in the referenced WCEL and the reference specified to be exported.

To export WCAL from Plan Manager, select the Export to NetAct Planner check box:

3.5.1.9 Adjacencies

Adjacencies are listed under WCELs in NetAct Planner. They are not independent

objects and they do not have their own identity or parameters. In NetAct Planner, the

link is the information. Only outward neighbours are considered (as shown below)

where an ADJI, ADJG and ADJS are specified:





© Nokia Oyj 3-59

You cannot set any information for UMTS adjacencies in NetAct Planner; in RAC, you

should ensure that the parent and target WCEL names are set and included in export.

Note : The identity and hierarchy of ADJG's target GSM BTS must be correctly set in

NetAct Planner.

3.5.1.10 WLCSE

In the interface, WLCSE is identified by RNC ID and WLCSE ID. The RNC ID is

located on the parent RNC and the WLCSE ID is located on parent UMTS Cell.

The import of the WLCSE will update WLCSE parameters.

Export will export WLCSEs which have a valid WLCSE ID.

3.5.1.11 Flags - 3G

NetAct Planner flags are utilised to support some of the functionality that is not

otherwise available for the interface. You can use them for:

• Applying RAC import templates to the objects.

• Creating unsupported parameters for the interface.

• Denying import to selected WBTS or WCEL.

To assign an RAC import template to SITE, RNC, WBTS, and WCEL, use NetAct

Planner Administrator to create a flag group called 'RAC Template'. Set the first flag as'N/A' (or something similar that denotes it is not specified), then name the following

flags as defined for the import templates in RAC. Assign the flag group for SITE, RNC,

WBTS, and WCEL.

To activate the import template for an object (or many objects, in global editor), set the

status flag to a value other than the first, to export it as the template.

To set the template for ADJS (ADJI & ADJG similarly), create a flag group called

'RAC ADJS Template' (ADJI/ADJG) and set it for the parent WCEL. As the template





can only be set for the parent WCEL, all child ADJSs (ADJIs/ADJGs) will share thesame template.

Templates are not supported in NetAct Planner import.

There are two ways to create a new parameter for the interface for SITE, RNC, WBTS,or WCEL:

• The first way is to create a flag group in NetAct Planner Administrator with the

name of the parameter you want to create (for example, Tcell). Set the first flag as

'N/A' (or something similar that denotes it is not specified), and then give the

following flags the values that the parameter can obtain. (For example, 0, 256,

512, 768, 1024, 1280, 1536, 1792, 2048, and 2304). Assign the flag group for

SITE, RNC, WBTS or WCEL (for example, WCEL).

To activate the parameter for the interface, set it for the elements to a value other

than the first.

• The second way is to create a flag group in NetAct Planner Administrator with the

name of the parameter you want to create (for example, Tcell). Then double click picklist of selected flag group and select type of parameter from list. Assign the flag

group for SITE, RNC, WBTS or WCEL (for example, WCEL).

The parameter is now activated for assigned objects and can be edited.

You can change the parameter values for existing flag groups in import (provided the

value itself is specified as a flag or parameter type is same), but you cannot create new

flag groups.

Creating templates and parameters in NetAct Planner as opposed to creating them in

RAC is in effect, only moving the responsibility to the other end of the interface. It

increases the amount of manual work in NetAct Planner, but decreases it in RAC.

3.5.2 Setting up the GSM network

3.5.2.1 Preferences

In the Preferences dialog box, select Frequency Bands to be used. This enables you to

set the correct frequency band for specific carrier layers. It is required for GSM 1800,

GSM1900, GSM 450, GSM 480, GSM 850, GSM R-900, and GSM E-900 carrier

layers.





© Nokia Oyj 3-61

3.5.2.2 Carriers

Select carriers, which are allowed to be used in network, in the System Carriers dialog

box. It is possible to select all carriers of a specific band such as GSM 900 or GSM

1800:





3.5.2.3 Carrier Layers

Create carrier layers for the project. There must be separate BCCH and TCH carrier

layer for each system.

Set the bcch carrier layer as control layer:

Set the frequency band of the carrier layer. For example, GSM 1800 Band for a GSM

1800 carrier layer:

Set the maximum number of carriers allowed to be allocated to carrier layer:

Select the carrier for the carrier layer:





© Nokia Oyj 3-63

After setting the carrier layer values, apply and commit the changes.

3.5.2.4 Cell layers

Create cell layers for the project. At least one cell layer per system is needed. Select the

carrier layers for the cell layer. The system carriers of the selected carrier layers must

belong to the same system.





If slave BTS are used in the network, then more than one cell layer is needed. For example, if there are GSM 900 slave BTSs, add a second GSM 900 cell layer with the

same carrier layers as in the first GSM 900 cell layer.

It is possible to specify which cell layer is selected in the import of a BTS, to create a

subcell. The BTS parameter cell type can be coded to the name of a cell layer in thisway:

“[“ + [cell type] + “]”

The import of the BTS will first try to select the cell layer which has its cell type coded

in the name. For example, if the cell type is 56, then the cell layer with the name

'macro900[56]' is selected if it exists, the BTS's carriers are included in the allowed

carriers list of the carrier layers, and the frequency band of BTS is the same as carrier

layers frequency bands.

3.5.2.5 Other GSM equipment and settings

Set Feeders, Cell Equipment, Propagation Models and Antenna Types. In export, their names are sent as references, and in import, they are allocated to objects based on this

reference.

3.5.2.6 SITE

The common term 'SITE' is used to denote the physical location in this interface. In

NetAct Planner, the term used is 'property'. For a GSM network, BSCs and BCFs are

located on a SITE.

The mandatory parameters are siteId, which as identity, is always required:

and co-ordinates, which are needed for creation:

In NetAct Planner, these are always available. In RAC, SITE must be either manually

added or imported. In CM Plan Manager export, you must select Export also site

information to export SITE objects:

To export ground height for the SITE, you must override the map setting, even if it is just with the same value:

,





© Nokia Oyj 3-65

3.5.2.7 BSC

BSC in interface is identified by BSC ID. In NetAct Planner, the BSC ID is in the field

BSC ID of the BSC:

In NetAct Planner, the BSC parameter name is in the Identity field of the BSC:

Import finds the existing BSC using the BSC ID. If the BSC is found, it is updated,

otherwise a new BSC is created. Creation of a new BSC in import requires that the BSC

has the parameter siteId. SiteId is the identity of the SITE object, which must also exist

either in NetAct Planner or the imported file.

The import of the delete operation removes the childless BSC with with BSC ID.

Export only exports BSC objects which have a valid BSC ID. If a BSC is not exported,

then neither are its child objects.

3.5.2.8 BCF

In the interface, BCF is identified by BSC ID, and BCF ID. The BSC ID is located on

the parent BSC. The BCF ID is located in the BCF ID field of BCF:

The BCF is located on a site.

BCF objects are imported on the site of property, which is selected by the latitude andlongitude parameters of the SITE object to which the BCF siteId parameter refers. If a

BCF does not have a siteId parameter, the BCF's latitude and longitude parameters are

used to find the correct property. If a property cannot be not found by using the BCF

latitude and longitude parameters, then a new property and site are created. If the BCFlatitude or longitude parameters are zero, then the BCF or its child objects are not

imported. If there is a BCF with same BCF ID and BSC ID in a different site, then the

BCF is moved to the correct site.

Import of the delete operation removes the childless BCF with the BSC ID and BCF ID.

Additionally, empty sites are removed.

Export only exports the BCF objects which have a valid BSC ID and BCF ID. If a BCFis not exported, its child objects are not exported.

3.5.2.9 BTS

In the interface, BTS is identified by BSC ID, BCF ID, and BTS ID. The BSC ID is

located on the parent BSC and the BCF ID is located the parent BCF. The BTS ID is

located in the BTS ID field of a subcell.

In the interface, the BTS object has subcell in NetAct Planner as an equivalent object.

Segment, which in the interface consists of one master BTS and from 0 to n slave BTSs,

has a GSM cell in NetAct Planner as an equivalent object. For example, one master





BTS in the interface has one GSM cell and one subcell in NetAct Planner. Subcellshave the master BTS flag of true. If there is one master BTS and one slave BTS in the

interface, then NetAct Planner has a GSM cell with two subcells. One subcell has a

master BTS flag of true and other false.

The parent BCF of a BTS (subcell) is selected by the BCF Configuration parameter inthe subcell.

The BTS of the same segment has the same CELL ID. The CELL ID is located in the

GSM ID field of the GSM cell:

The import of the BTS searches for a GSM cell with the same cell identity as the BTS

Cell ID. If found, the cell is updated, otherwise a new cell is created. If necessary, the

cell is moved under the parent BCF. If a cell has valid subcell then it is used, otherwisea new subcell is created if possible. If necessary, the BTS ID and the parent BCF of a

subcell are updated. In the cell, the parameters LAC, RAC, MCC, MNC, BCC, NCC are

also updated. A dummy antenna is created for a new cell if the ANTE object is notimported for the cell.

The import of the delete operation removes subcells with a BSC ID, a BCF ID and a

BTS ID. Additionally, cells with no subcells are removed.

The export will export the BTS and its child objects only if the cell has a valid CELL ID

and LAC, and the subcell has the BTS ID and the parent BCF selected.

3.5.2.10 TRX

In the interface, TRX is identified by BSC ID, BCF ID, BTS ID, and TRX ID. The BSCID is located on the parent BSC and the BCF ID is located on the parent BCF. The BTS

ID is located in parent subcell and the TRX ID is located in the carrier layer of subcell.





© Nokia Oyj 3-67

TRX ID(s) can be selected by selecting carrier layer and channel type for it.

Because TRX IDs and carriers are listed separated in NetAct Planner, the import selects

the carrier layer to which the initial carrier layer of TRX will be imported. This

selection is made by using the 'system of carrier layer', 'is carrier layer control layer' and'carriers allocated to carrier layer'. If a carrier layer already has a TRX ID, then the

existing carrier is changed to the initial Frequency parameter in the TRX. Otherwise, a

new carrier is added. Import also updated channel type if nessessary.

The import of the Plan Manager Actual export file removes the existing TRXs of a

subcell if import finds new TRXs, the new TRXs replace any existing TRXs in a

subcell.

The import of the delete operation removes the TRX ID and carrier from the subcell

with the BSC ID, BCF ID and BTS ID.

The export will export TRXs that have both a TRX ID and a fixed carrier.





3.5.2.11 ADCE

ADCE in interface is identified by BSC ID, BCF ID, BTS ID and neighbour Cell ID.

The BSC ID is located on the parent BSC and the BCF ID is located parent BCF. The

BTS ID is located in the parent subcell and the Neighbour Cell ID is located inneighbour cell's GSM ID field:

If there is no neighbour between two GSM cells, the import creates one.

The import of the delete operation removes neighbours that are between GSM cells.

The export will export ADCEs which have valid parent BSC ID, BCF ID, and BTS ID,

and a neighbour Cell ID and LAC.

3.5.2.12 ADJW

In the interface, ADJW is identified by BSC ID, BCF ID, BTS ID and neighbour

WCEL's name. The BSC ID is located on the parent BSC and the BCF ID is located on

the parent BCF. The BTS ID is located in the parent subcell and the Neighbour WCEL's

name is located in the neighbour UMTS Cell's Identity field.

If there is no neighbour from a GSM cell to a UMTS cell, the import creates one.

The import of the delete operation removes neighbours from the GSM cell to the UMTS

cell.

Export will export ADJWs which have a valid parent BSC ID, BCF ID, and BTS ID,

and a neighbour UMTS Cell Identity.

3.5.2.13 ANTE

In the interface, ANTE is identified by anteId. In NetAct Planner, antenna do not have

their own identity. For the antennaId interface, the database cellantennakey is exported.

To export ANTE from Plan Manager, select the Export to NetAct Planner option:

The import tries to find the antenna with the same cellantennakey as anteId. If such an

antenna is found, then it is updated. Otherwise, the import tries to find a GCAL with the





© Nokia Oyj 3-69

same anteId. If such a GCAL is found, then it is used to find a GSM cell, to which anew antenna is created. Otherwise, the ANTE is not imported.

The import of the delete operation removes the antenna from the GSM cell.

The export will export the ANTE using cellantennakey as anteId.

3.5.2.14 GCAL

In the interface, GCAL is identified by anteId and gcalId. gcalId consists of a

concatenated string of the BTS ID and Cell ID. GCAL in NetAct Planner is the antenna

slot of the subcell:

To export GCAL from Plan Manager, select the Export to NetAct Planner option:

The import tries to find the antenna slot of the antenna with an anteId and subcell that

have the same BSC ID, BCF ID, and BTS ID as in the linkedCellDN parameter. If such

an antenna slot is not found, a new antenna slot is added.

The import of the delete operation removes the antenna slot from the subcell.

The export will export GCAL using cellantennakey as anteId, and combinations of BTS

ID and CELL ID as gcalId.

3.5.2.15 MAL

In the interface, MAL is identified by BSC ID and MAL ID. MAL in NetAct Planner is

represented by allocated and fixed carriers of synthesised and site hopping subcells.

When a subcell is synthesised or site hopping, then its MALID is editable.





The import replaces the existing carriers of a subcell with carriers of MAL, for any

subcells that have the same BSC ID and MAL ID.

The import of the delete operation removes carriers from the subcell.

The export will export MAL if a subcell has a valid parent BSC ID and MAL ID, and

the fixed carriers of the subcells with the same BSC ID and MAL ID are the same.

3.5.2.16 LMU

In the interface, LMU is identified by BSC ID, BCF ID, and areaId. In NetAct Planner,

LMU is an object under site. There can be no more than one LMU per site. AreaId have

the field Area ID in the LMU:

The import tries to find the LMU in the site of the BCF with the BSC ID and BCF ID. If

an existing LMU is found, it is updated, including the Area ID. Otherwise, a new LMU

is created.

The import of the delete operation removes the LMU under the parent BCF.

The export will export an LMU if it has a valid BSC ID, BCF ID, and Area ID.

3.5.2.17 LCSE

In the interface, LCSE is identified by BSC ID, Cell ID and LAC. The BSC ID is

located on the parent BSC and the Cell ID and LAC are located on parent GSM Cell.

The import of the LCSE replaces LCSE neighbours.

Export will export LCSEs which have a valid parent BSC ID, Cell ID, and LAC, and

have at least on LCSE neighbour.





© Nokia Oyj 3-71

3.5.2.18 Flags - 2G

NetAct Planner flags are utilised to support some of the functionality not otherwise

available for the interface. You can use them for two things:

• For applying RAC import templates to the objects.

• For creating unsupported parameters for the interface.

• Denying import to selected BCF or BTS.

To assign an RAC import template to a BSC, BCF and BTS create a flag group named

'RAC Template', in NetAct Planner Administrator. Set the first flag as 'N/A' (or

something similar that denotes it is not specified), and then name the following flags as

defined for import templates in RAC. Assign the flag group for BSC, Site and GSM

Cell.

To activate the import template for an object (or many objects, in the global editor), set

the status flag to a value other than the first, so that it is exported as the template.

To set the template for ADCE, create a flag group called 'RAC ADCE Template' and setit for the parent GSM Cell. As the template can only be set for the parent GSM Cell, all

child ADCEs will share the same template.

To set the template for ADJW, create a flag group called 'RAC ADJW Template' and

set it for the parent GSM Cell. As the template can only be set for the parent GSM Cell,

all child ADJWs will share the same template.

To set the template for TRX, create a flag group called 'RAC TRX Template' and set it

for the parent GSM Cell. As the template can only be set for the parent GSM Cell, all

child TRXs will share the same template.

Templates are not supported in NetAct Planner import.

There are two way to create a new parameter for the interface for a BSC, BCF, or BTS:

• The first one is to create a flag group in NetAct Planner Administrator, using the

name of the parameter you want to create (for example, Tcell). Set the first flag as

'N/A' (or something similar that denotes it is not specified), and give the following

flags the values that this parameter can obtain (for example, 0, 256, 512, 768, 1024,

1280, 1536, 1792, 2048, and 2304). Assign the flag group for BSC, Site and GSM

Cell.

To activate the parameter for the interface, set it for the elements, to a value other than the first.

• Second way is to create a flag group in NetAct Planner Administrator with the

name of the parameter you want to create (for example, nsei). Then double click

picklist of selected flag group and select type of parameter from list. Assign the flag

group for SITE, BSC, BCF or BTS (for example, BTS).

The parameter is now activated for assigned objects and can be edited.

You can change the parameter values for existing flag groups in import (provided the

value itself is specified as a flag), but you cannot create new flag groups.

Creating templates and parameters in NetAct Planner as opposed to creating them in

RAC is in effect, only moving the responsibility to the other end of the interface. It

increases the amount of manual work in NetAct Planner, but decreases it in RAC.

For more information about deny import flags, see chapter 3.4.2.4.





3.5.3 Planning process

The planning process is a procedure to be followed to enable using this interface for

updating both sides of the interface with relevant data. It is likely to be quite different

depending on whether or not the synchronisation functionality is used, and on thefunctionality in RAC.

3.5.3.1 Setting up GSM network configuration

The setting up of the network configuration is a procedure for setting the same planning

object identification and data for first time in both NetAct Planner and RAC. The same

identification enables smooth data transfer between tools. The same planning data (such

as sites and antennas) is required for the interface. If planning data is missing, it mightresult in the user creating duplicate data with identification differing from that in the

other tool.

Step 1:The first step is to have planning data such as antennas, sites, and cells in NetAct

Planner. The existing GSM cells must have a unique CELL ID parameter. Otherwise,the first import to NetAct Planner creates duplicate cells as import identity cells with

CELL ID. The BSC ID should also be set if the BSC object in RAC does not yet have a

SITE object. The non-element data, (such as NodeB types, Feeder types, MHA types,

Cell Equipment, Propagation models, Antenna types, Carriers, Carrier layers and Cell

layers) also need to be set. For information on how to do this, refer to Chapter 3.

Step 2 (conditional):

A second step is required if the BCFs and BSCs in RAC do not yet have correct SITE

objects. In this case, you have two options:• either create SITE objects in RAC with the same siteId as the property names of

same objects in NetAct Planner, and then set the siteId parameters to point those

SITE objects in RAC, or

• set same BCF latitude and longitude parameter values in RAC as the BCF

properties have in NetAct Planner.

Step 3:

Ensure that the CELL ID parameter is used only once per master BTS. If there are twomaster BTSs with the same CELL ID, even if they have a different LAC, then one of

CELL IDs must be changed. NetAct Planner does not import the master BTS if the

CELL ID is used already by another master BTS.

Step 4:

From RAC, export the actual plan of all the BSCs. Exported objects include: BSC,BCF, BTS, TRX, ADCE, ADJW, and MAL. The exported file is imported to NetAct

Planner. If the import displays errors or warnings in the Message Log window, you

must fix them in RAC and repeat step 4.





© Nokia Oyj 3-73

Import creates BCF objects with a BCF ID, update BTS ID, TRX ID, LAC and other parameters. With those ids, you can export objects from NetAct Planner because only

objects with valid ids are exported. See section 3.5.2 Setting up GSM Network.

Step 5:

Export all the BSCs of project from NetAct Planner. You can also perform a BCF

export and select all BCFs which do exist in RAC. If there are new cells in NetAct

Planner which are not yet in RAC, then either their BCF is unselected from export (BCF

export) or their CELL ID is set to zero. GSM cells with a zero CELL ID are not

exported. Neighbours between a cell with a valid CELL ID and LAC, and cells without

valid CELL ID or LAC are not exported. The export file also includes site and antenna

data (SITE, ANTE, GCAL objects). If some objects do not have valid id, then either itor its child objects are not exported. All errors and warning are written to the Message

Log window. If there are errors in cells and the errors also exist in RAC, then those

errors should be fixed in NetAct Planner and you should repeat step five.

Step 6:

Import the NetAct Planner export file to RAC.

3.5.3.2 Setting up WCDMA Network Configuration

Initially, the NetAct Planner project should be populated with the current network

configuration. To prepare for this, set the non-element data such as NodeB types, Feeder

types, MHA types, Antenna types and Carriers, and create the root PLMN node.

3.5.3.3 Importing actual network configurationThe procedure to import an actual network configuration to NetAct Planner should

happen fairly often, to ensure that the NetAct Planner data is synchronised with RAC.

Export the actual network configuration using CM Plan Manager as described in theRAC documentation, including the non-network data required by NetAct Planner, and

import it into NetAct Planner. If any mandatory information is missing, you might need

to go back and edit the data in RAC. The validation stage in the NetAct Planner import

informs you of any discrepancies before the actual import.

Note : If there are planned changes to the actual network configuration which are notyet in the network but which should be included as assumptions for further planning,

they should manually be updated in the NetAct Planner project (unless RAC supports

exporting information about planned changes).

3.5.3.4 Exporting changes to the network configuration

There are several ways to export changes to the network configuration, depending on

the planning practices and preferences of the users. The different methods are:

• Automatic

Automatic mode means that the object selection is mostly left to the state tracking

system, to determine the objects that have changed.





You can select the WBTSs and BCFs you want to transfer, and only the parts of

their hierarchy that have changed are exported. Alternatively, you can select the

RNCs and BSCs, but then they should not include data that is not meant to be

transferred to RAC. If your plan includes such information, either keep it under separate RNCs and BSCs, leave their network identifiers un-set, or make the

selection on WBTS/BCF level.

• Semi-automatic

In semi-automatic mode, a track of all the changes made to the plan can be

discarded by cleaning the state tracking system. After this, 'touching' the objects

that need to be exported, marks them for the state tracking system. If you

occasionally commit all the data, this enables you to update the NetAct Planner

project from RAC. In this mode, you will need to know and manually select the

objects for export.

• Manual:

In manual mode, the synchronisation information is not utilised. The separate

installation can also be ignored. You can select the whole RNC or BSC hierarchy

for export, or more usually, any number of WBTSs or BCFs, which are exported

with all their related objects. This will not change the situation in import, where the

existing project can only be updated if all data for the user has been committed.

Which ever method you use, remember that if the data in NetAct Planner is not up-to-

date, there is a risk of overwriting the correct data that is in RAC. Additionally, NetAct

Planner must have up-to-date information, otherwise the planning assumptions (input)and the results (output) will be incorrect. Therefore, it is important that you update

information on both sides of the interface.

3.5.4 Known problems in NetAct Planner core

3.5.4.1 Wastebasket

If synchronisation is used with the Configuration Interface then GSM objects in the

wastebasket need to be deleted in this order: Neighbours, Subcells, Cells, BCFs, Sites

and BSCs.

3.5.4.2 Standard XML interface

The standard XML interface does not import or export BCF objects. BCF objects areneeded by the NetAct Configuration Interface and must be added manually on projects

transferred by the standard XML interface before you use the NetAct Configuration

Interface.



Transmission Planner interface


© Nokia Oyj 4-1

4 Transmission Planner interface

4.1 OverviewThe NetAct Configuration interface for export contains a section for exporting

transmission parameters. Within the Transmission Module of the export interface is a

check box that enables the creation of an AXC configuration file in XML format, which

can then be exported to NetAct Plan Editor. NetAct Plan Editor sends the configuration

data to the relevant network element via Element Managers. The Transmission Module

of the interface also contains a check box that enables the creation of COCO parameters

in XML format, which can then be exported to Plan Manager (Radio Access

Configurator). Only AXC or COCO can be selected for export – they cannot both be

selected at the same time.

4.2 Accessing the interface

The export functionality is accessed via the main menu in NetAct Planner. The export

option is accessed by selecting File | Export | Project Data | NetAct Configuration:





If you select the NetAct Configuration option, the export interface dialog appears.

Below is an example of the interface after the controls in the Transmission module pane

have been selected:





© Nokia Oyj 4-3

Figure 1. NetAct Configuration export interface with controls in theTransmission module selected

The Transmission pane comprises these controls:





When the Transmission module is first selected, AXC is automatically selected for

export. When AXC is selected for export, all AXC nodes in the ATM module of

Transmission Planner are displayed in the tree view. These can be selected individually

for export. You can use the 'Check All' check box to select all AXC nodes in the dialog

box. This may be useful if there are many AXC nodes appearing in the dialog box.

If you select the COCO check box, the AXC check is automatically deselected and the

AXC nodes no longer appear in the dialog box. A COCO object is exported in XMLwhen a connection between A WBTS and RNC is found; every existing COCO object is

exported.

In the File Path pane, you can specify either a new file or an existing NetAct XML file:

When you have selected either a new or an existing file, click the Export button to begin

the export.

If you are exporting to an existing file, the whole configuration can either be appended

to the end of the existing file, or the contents of the file can be overwritten. If you

specified an existing file, you are prompted to make an appropriate selection:

Figure 2. Confirmation to append or overwrite an existing NetAct Planner XML file

Finally, Transmission Planner writes the AXC or COCO configuration, depending on

which check box you selected, into the specified XML file. After successfully exportingthe configuration, the XML file can be read directly into the relevant tool depending on

whether AXC or COCO has been exported.

4.3 ATM AXC parameters

In the XML file, a full range of data is displayed. Default values are those that are

required for importing into Nokia NetAct Plan Editor. For descriptions of these, refer to

the PlanEditor user documentation .

This table details the properties that are shown for each class:








spttStmLevel Value depends on the type of SDH Edge.

Edge Type: “VC3-SDH”

Value =“STM_SIGNAL_LEVEL_1”

Edge Type: “VC4”

Value =“STM_SIGNAL_LEVEL_2”

Edge Type: Other

Value = “NULL”

Describes the type of SDH edge.Depending on the capacity of theedge, a specific value is used.

srttExpTraceID NULL Default value.

srttXmtTraceID NULL Default value.

smttBerMode BER_MODE_3 Default value.

smttRdiOnExcessiveBer TRUE Default value.

svttExpTraceID NULL Default value.

svttXmtTraceID NULL Default value.

svttRdiMode RDI_MODE_AUTOMATIC Default value.

IMAL (InverseMultiplexing for Atm Link)

slotNumber Integer. Defaults to zero if novalue found

Describes the numeric position of the card to which the edge isconnected in the Detail Module.

interfaceNumber Integer. Defaults to zero if novalue found

Describes the port to which theedge is connected in the DetailModule.

IMAG (Inverse

Multiplexing for Atm Group)


Describes the numeric position of the card to which all ima links areconnected in the Detail Module.

imaGroupId Integer. Represents the IMA Group IDwhich you can specify in the vptdialog box.

imaLinkPtrs Contains a list of slotNumbersand interfaceNumbers for IMALobjects in the IMAG

Each IMAL object with the sameIMAG will appear in the list.

minNumLinks 1 Default value.

txTimingRefLink Integer, one of the followingvalues: 32, 64, 128, 256.

This is the first interfaceNumber found in the imaLinkPtrs list.

txFrameLength Integer. One of the followingfour values: 32, 64, 128, or

256.

The length of the transmittedframes. You can specify this setting

in the vpt dialog box.

diffDelayMax 5 Default value.

ACCP (AccessProfile)





maxNumVPIBitsSupported 4 Default value.





© Nokia Oyj 4-7


maxNumVCIBitsSupported 7 Default value.

ingressBandwidth Integer.

If the edge is routed on to PDHthen values are as follows:

Edge: “1.5M”

Values = 4528

Edge: “2M”

Value = 3622

Edge: “6M”

Value = 14490

If the edge is routed throughSDH then the values are asfollows:

Edge: “VC3”

Values = 114113

Edge: “VC4”

Value = 353207

Ingress Bandwidth for the physicaledge.

egressBandwidth Same as above Same as above.

upcNpc FALSE Default value.

TRDE (TrafficDescriptor)

serviceCategory String. Can either be “UBR” or “CBR”

The service category for vcc edgescontaining traffic can be set fromthe VCC Group dialog box in the ATM Module.

conformanceDefinition String. Can be either “CBR1” or

“UBR1”

This value relates to the one above.

If the service category is 'UBR',then the conformance definition is'UBR1'. The same for CBR.

egressPeakCellRate Integer Tx traffic capacity in the cells/s.This value can be seen in the VCCGroup dialog box in the ATMModule.

ingressPeakCellRate Integer Rx traffic capacity in the cells/s.This value can be seen in the VCCGroup dialog box in the ATMModule.

egressCLR 9 Default value.

ingressCLR 9 Default value.

egressCDVT Integer. This value is the resultof a calculation on theegressPeakCellRate parameter

This value is calculated by dividingthe egressPeakCellRate parameter into 1000000. The result is thenrounded down. If this figure isgreater than 2, then it is used for the value. If it is less than 2, then 2is used as the value.






ingressCDVT Integer. This value is the resultof a calculation on theingressPeakCellRate

parameter

This value is calculated by dividingthe ingressPeakCellRate parameter into 1000000. The result is then

rounded down. If this figure isgreater than 2, then it is used for the value. If it is less than 2, then 2is used as the value.

FRLI (FractionalE1)





maxTimeslot16 Integer. Range: 1 to 31 This value relates to the maximumnumber of 64kb connections in thevpt dialog box of the ATM Module.

useTimeslot16 Boolean. Values TRUE or FALSE.

If the maxTimeSlot is 15 then timeslot 16 is checked to see if it isused. If it is, then the value isTRUE, otherwise the value isFALSE.

IPRT (IP RoutingTable)

destIpAddr IP V4 Address in decimalformat

This value is the IP Address of theRNC Node to which this AXC Nodeis connected.

netmask IP V4 Address in decimalformat

This value represents the SubnetMask of this AXC Node.

gateway IP V4 Address in decimalformat

This value is the IP Address of thepenultimate Node to the RNCNode.

IAIF (ATM

Interface Network)

slotNumber Integer. Defaults to zero if no

value found

Describes the numeric position of

the card to which the edge isconnected in the Detail Module.



connectivityPtrVpi Integer Vci number of the edge, can beseen in the VCC Group dialog boxin the ATM Module.

connectivityPtrVci Integer Vpi number of the edge, can beseen in the VCC Group dialog boxin the ATM Module.

destIpAddr IP V4 Address in decimalformat

This is the IP Address of the other Node to which this edge is

connected.

localIpAddr IP V4 Address in decimalformat

This is the IP Address of this AXCNode.

IEIF (EthernetInterface Network)

discardPublic TRUE Default value.

broadcast IP V4 Address in decimalformat

This is calculated using thenetmask address.

localIpAddr IP V4 Address in decimalformat

This value is the IP Address of this AXC Node.





© Nokia Oyj 4-9


netmask IP V4 Address in decimalformat

This value is the Subnet Mask of this AXC Node.

VCTT (VirtualChannel TrailTermination)





vpi Integer This value represents the VPInumber of the terminating edge.

vci Integer This value represents the VCInumber of the terminating edge.

aalProfilePtr 1 Default value.

VPCT (Virtual PathConnection

Termination Point)


Describes the numeric position of the card to which the edge is

connected in the Detail Module.



vpi Integer Vpi number of the edge, can beseen in the VCC Group dialog boxin the ATM Module.

trafficDescriptorPtr Integer. Values starting at 200. This value is the identifier of thetraffic descriptor of this edge.

VPTT (Virtual PathTrail TerminationPoint)


Describes the numeric position of the card to which the edge isconnected to in the Detail Module.

interfaceNumber Integer. Defaults to zero if no

value found

Describes the port to which the

edge is connected to in the DetailModule.

vpi VPI value of the correspondingVPPT object

Vpi number of the edge, can beseen in the VCC Group dialog boxin the ATM Module

supportedServiceCategories CBR,UBR Default value.

VCCT (VirtualChannelConnectionTermination Point)





vpi Integer Vpi number of the edge, can beseen in the VCC Group dialog boxin the ATM Module.

vci Integer Vci number of the edge, can beseen in the VCC Group dialog boxin the ATM Module.

trafficDescriptorPtr Integer. Values starting at 200. This value is the identifier of thetraffic descriptor of this edge.

segmentEndPoint FALSE Default value.






egressFrameDiscardEnabled FALSE Default value.

ingressFrameDiscardEnabled FALSE Default value.

BTS-Info String. Type of vcc connectionand unique edge name. Typeof vcc connection can be one of the following values:

“NBAP-C”, “NBAP-D”, “User Plane”, “User Plane AAL2 Sig”

The values for the type of vccconnection and unique name canbe found in the VCC Group dialogbox in the ATM Module.

XCON (CrossConnection)

fromSlotNumber Integer. Defaults to zero if novalue found

Describes the numeric position of the card to which the from edge isconnected in the Detail Module.

fromInterfaceNumber Integer. Defaults to zero if novalue found

Describes the port to which thefrom edge is connected in the DetailModule.

fromVPI Integer Vpi number of the from edge, can

be seen in the vpc dialog box in the ATM Module.

fromVCI Integer Vci number of the from edge, canbe seen in the VCC Group dialogbox in the ATM Module. Output onlyif cross connection of VC level.

toSlotNumber Integer. Defaults to zero if novalue found

Describes the numeric position of the card to which the to edge isconnected in the Detail Module.

toInterfaceNumber Integer. Defaults to zero if novalue found

Describes the port to which the toedge is connected in the DetailModule.

toVPI Integer Vpi number of the to edge, can be

seen in the vpc dialog box in the ATM Module.

toVCI Integer Vci number of the to edge, can beseen in the VCC Group dialog boxin the ATM Module. Output only if cross connection of VC level.

CIWT (CESInterworkingFunction)

fromSlotNumber Integer. Defaults to zero if novalue found

Describes the numeric position of the card to which the from edge isconnected in the Detail Module.

fromInterfaceNumber Integer. Defaults to zero if novalue found

Describes the port to which thefrom edge is connected in the DetailModule.

toSlotNumber Integer. Defaults to zero if no

value found

Describes the numeric position of

the card to which the to edge isconnected in the Detail Module.

toInterfaceNumber Integer. Defaults to zero if novalue found

Describes the port to which the toedge is connected in the DetailModule.

toVPI Integer Vpi number of the to edge, can beseen in the vpc dialog box in the ATM Module.

toVCI Integer Vci number of the to edge, can beseen in the VCC Group dialog boxin the ATM Module.





© Nokia Oyj 4-11


cesService UNSTRUCTURED Default value.

cesTimeSlotSequenceCbrIf NULL Default value.

cesPartialFill 47 Default value.

IFPU (IFP Unit) slotNumber Integer. Defaults to zero if novalue found




IFPG (IFP Group) mspProtocol mspOn Default value.

revertiveOperation Values can be either “nonRevertive” or “revertive”

If there exactly two items in thetransIfPuPtrs list the value is“nonRevertive” otherwise it is“revertive”.

transIfPuPtrs List of IFPU objects This list structure contains all theIFPU objects.

A2ST (AAL2Signalling Traffic)

ani NULL Default value.





vpi Integer Vpi number of the edge, can beseen in the vpc dialog box in the ATM Module.


aal2sigTTPenablePm FALSE Default value.

stcAlarmEnable FALSE Default value.

a2ea String A calculation of the RNC IDandBTS ID.

A2UT (AAL2 User Traffic)





vpi Integer Vpi number of the edge, can beseen in the vpc dialog box in the ATM Module.


pid Integer Calcualated using AXC Nodespecific parameters.

timerCu 2 Default value.






aal2pathTTPenablePm FALSE Default value.

Note : If you have SDH connections, SRTT, SMTT, SVTT, and SPTT classes areshown in the XML file. If you have PDH connections, the PPTT class is shown.

4.4 COCO parameters

In the XML file, a full range of data is displayed. Default values are those that are

required for importing into Nokia NetAct PlanManager. For descriptions of these, refer

to the Nokia NetAct PlanManager user documentation. This table details the properties

that are shown for each class:


COCO(ConnectionConfiguration)

AAL2LossRatio 3 Default value.

AAL2MuxDelay 100 Default value.

ATMInterfaceID Integer This is the ID of the BTS. Can befound in the NodeB dialog box in theTraffic Module.

CalculateCDVT 1 Default value.

CNBAPPCR01Egr Integer Egress Peak Cell Rate value for allNBAP-C in cell/s. Can be found as a

total in the VCC Group dialog box inthe ATM Module.

CNBAPPCR01Ing Integer Ingress Peak Cell Rate value for allNBAP-C in cell/s. Can be found as atotal in the VCC Group dialog box inthe ATM Module.

CNBAPVCI Integer Vci number of the first NBAP-Cedge found, can be seen as the topvcc edge dialog in the ATM Module.

COCOVPI Integer The VPI number that connects thevcc of this BTS.

VPLTPPCR01Egr Integer Total of the vcc edge.

VPLTPTrafficShaping 1 Default value.

ConformanceDef 0 Default value.

EarlyPacketDiscard 0 Default value.

PartialPacketDiscard 0 Default value.

QualityOfServiceClass 1 Default value.

ServiceCategory 0 Default value.





© Nokia Oyj 4-13


CreateATMTP 1 Default value.

GenerateAAL2Num 1 Default value.

AAL2SignLinkTP List structure. Each itemcontains the following four parameters as can be seenbelow. These are“AAL2SignLinkTPId”,“AAL2SignLinkVCI”,“AAL2SigPCR01Egr”, and“AAL2SigPCR01Ing”

This list describes vcc edges of type AAL2 in the control plane (NBAP-C).

AAL2SignLinkTPId Integer. A value between 1 and6

A unique identifier assigned as theitem is created.

AAL2SignLinkVCI Integer Vci number of the edge, can beseen in the VCC Group dialog box inthe ATM Module.

AAL2SigPCR01Egr Integer Egress Peak Cell Rate value for vccedge in cell/s. Can be found as atotal in the VCC Group dialog box inthe ATM Module.

AAL2SigPCR01Ing Integer Ingress Peak Cell Rate value for vccedge in cell/s. Can be found as atotal in the VCC Group dialog box inthe ATM Module.

AAL2TP List structure. Each itemcontains the following fiveparameters as can be seenbelow. These are“AAL2SignLinkVCI”,“AAL2UPPCR01Egr”,“AAL2UPPCR01Ing”,“AAL2UPTPId” and“AAL2UPVCI”

This list describes vcc edges of type AAL2 in the User Plane. Thereshould be the same amount of AAL2User Plane edges as AAL2 ControlPlane edges.

AAL2SignLinkVCI Integer This value represents thecorresponding AAL2 Control PlaneVCI number.

AAL2UPPCR01Egr Integer Egress Peak Cell Rate value for thisvcc edge in cell/s. Can be found inthe VCC Group dialog box in the ATM Module.

AAL2UPPCR01Ing Integer Ingress Peak Cell Rate value for thisvcc edge in cell/s. Can be found inthe VCC Group dialog box in the ATM Module.

AAL2UPTPId Integer. A value between 1 and18

A unique identifier assigned as theitem is created.

AAL2UPVCI Integer Vci number of the edge, can beseen in the VCC Group dialog box inthe ATM Module.






DNBAPTP List structure. Each itemcontains the following fiveparameters as can be seen

below. These are“DNBAPPCR01Egr”,“DNBAPPCR01Ing”,“DNBAPVCI”, and “TTPId”

This list contains parameters for each NBAP-D vcc edge found.

DNBAPPCR01Egr Integer Egress Peak Cell Rate value for thisvcc edge in cell/s. Can be found inthe VCC Group dialog box in the ATM Module.

DNBAPPCR01Ing Integer Ingress Peak Cell Rate value for thisvcc edge in cell/s. Can be found inthe VCC Group dialog box in the ATM Module.

DNBAPVCI Integer Vci number of the edge, can beseen in the VCC Group dialog box in

the ATM Module.

TTPId Integer This value is the same as the AAL2SignLinkTPId in the AAL2SignLinkTP list.



Example of a NetAct configuration export file


© Nokia Oyj A-1

A Example of a NetAct configurationexport file

This appendix shows an example of a NetAct configuration export file. The file includes

MultiRadio Planner 2G/2.5G and 3G parameters.

<?xml version="1.0" ?>- <raml xmlns="raml20.xsd" version="2.0"><cmData type="plan" scope="selection" name="Example"><header><log dateTime="2005-1-10T23:14:02" action="created" user="t" appInfo="NetAct Planner 5.0.0.3">Example Export for Planner

5.0</log></header><managedObject class="COSY" version="NAP1.0">

UTMUTM-34NWGS84METERS

</managedObject><managedObject class="RNC" operation="create" version="NAP1.0" distName="RNC-6"><defaults name="RNCType1" />

HaagaRNC02Haaga5

</managedObject><managedObject class="WBTS" operation="create" version="NAP1.0" distName="RNC-6/WBTS-14"><defaults name="Ultrasite" />

HaagaHaaga6

</managedObject><managedObject class="WCEL" operation="create" version="NAP1.0" distName="RNC-6/WBTS-14/WCEL-14"><defaults name="Micro" />

HaagaA1400244

31211<list name="URAId">

678912

</list>6-1031330




A-2 © Nokia Oyj DN04177508Issue 1-0 en

65283-30-60-30-6010612212130122040400302010

</managedObject><managedObject class="WCEL" operation="create" version="NAP1.0" distName="RNC-6/WBTS-14/WCEL-1">

HaagaC700244312116-103133065153-30-50-30-601061221

2160120040380402030

</managedObject><managedObject class="WCEL" operation="create" version="NAP1.0" distName="RNC-6/WBTS-14/WCEL-13">

HaagaB3300244312

118-104133065213-30-60-30-601063750





© Nokia Oyj A-3

120040380502020

</managedObject><managedObject class="WLCSE" operation="create" version="NAP1.0" distName="RNC-6/WLCSE-3333">

<defaults name="Type1" />HaagaBHaagaB633002441110101333000360188781640602453653200

</managedObject><managedObject class="ADJS" operation="create" version="NAP1.0"><defaults name="ADJSTemplate" />

61414HaagaAHaagaC614100244

73123301521

</managedObject><managedObject class="ADJI" operation="create" version="NAP1.0">

61414HaagaAHaagaB61413

002443331233021106372127

</managedObject><managedObject class="ADJS" operation="create" version="NAP1.0"><defaults name="ADJSTemplate" />





61414HaagaAHuopalahtiA25564740024447421333054

</managedObject><managedObject class="ADJG" operation="create" version="NAP1.0">

61414HaagaA2110054302224

</managedObject><managedObject class="ANTE" operation="create" version="NAP1.0" distName="ANTE-28973588">

1Haaga67413160015000188781640

602453653Haaga0Nokia OH10000


1Haaga67413241200015000188790490602456489

Haaga1Nokia OH10000


1Haaga674131624005015000





© Nokia Oyj A-5

188781640602453653Haaga2Nokia OH10000

</managedObject><managedObject class="WCAL" operation="create" version="NAP1.0" distName="ANTE-28973588/WCAL-14">

28973588HaagaA61414FeederLong1001002001MastHeadAmp564403001


28973861HaagaB61413000010

</managedObject>

<managedObject class="WCAL" operation="create" version="NAP1.0" distName="ANTE-28973779/WCAL-13">28973779HaagaB61413000000


28973861

HaagaC6141000000

</managedObject><managedObject class="BSC" operation="create" version="NAP1.0" distName="BSC-3030">





<defaults name="BSC Template"/>HHBSC03Rome

</managedObject><managedObject class="BCF" operation="create" version="NAP1.0" distName="BSC-3030/BCF-6">

<defaults name="BCF Template"/>Kataja3189643963602425755Rome

</managedObject><managedObject class="BCF" operation="create" version="NAP1.0" distName="BSC-3030/BCF-8">

Kontio3189047191602231077Hamburg

</managedObject><managedObject class="BTS" operation="create" version="NAP1.0" distName="BSC-3030/BCF-6/BTS-3">

<defaults name="BTS template"/>HiomoA211006FGHE10225430260500000

000011000CellEquipOne200Nokia OH

</managedObject><managedObject class="BTS" operation="create" version="NAP1.0" distName="BSC-3030/BCF-8/BTS-4">

SorviA23

1005KJYG103354302605005





© Nokia Oyj A-7

50214260000000CellEquipOne200Nokia OH

</managedObject><managedObject class="TRX" operation="create" version="NAP1.0" distName="BSC-3030/BCF-6/BTS-3/TRX-1 ">

<defaults name="TRX Template"/>44<list name="channelParameters">

<item>4

</item></list>0


<defaults name="TRX Template"/>550<list name="channelParameters">


</item></list>

0</managedObject><managedObject class="TRX" operation="create" version="NAP1.0" distName="BSC-3030/BCF-8/BTS-4/TRX-1 ">

34<list name="channelParameters">










</item>





</list>0

</managedObject><managedObject class="MAL" operation="create" version="NAP1.0" distName="BSC-3030/MAL-4">

0<list name="frequency">

505254565860

</list></managedObject><managedObject class="ADCE" operation="create" version="NAP1.0" distName="BSC-3030/BCF-6/BTS-3/ADCE-100 23">

<defaults name="ADCE Template"/>231005430233

</managedObject><managedObject class="ADCE" operation="create" version="NAP1.0" distName="BSC-3030/BCF-8/BTS-4/ADCE-100 21">

<defaults name="ADCE Template"/>21100225430234

</managedObject><managedObject class="LMU" operation="create" version="NAP1.0" distName="BSC-3030/BCF-6/LMU-45 ">

<defaults name="LMU Template"/>LMU0

2218964396360242575540100741316<list name="lmuDefaultNeighbourList ">

<item>42210021

</item></list>189643963

60242575525189643963602425755Rome


0Rome217413165050





© Nokia Oyj A-9

250010602425755189643963


0Hamburg23741316120050250010602231077189047191

</managedObject><managedObject class="GCAL" operation="create" version="NAP1.0" distName="ANTE-20645525/GCAL-21003 ">

20645525BSC-3030/BCF-6BTS-32110054302FeederLong100100200

</managedObject><managedObject class="GCAL" operation="create" version="NAP1.0" distName="ANTE-20649003/GCAL-23004 ">

20649003BSC-3030/BCF-8BTS-42310054302FeederLong100

100100

</managedObject><managedObject class="ADJW" operation="create" version="NAP1.0">

<defaults name="ADJW Template"/>303063HaagaA6141400244143

1128106122121

</managedObject><managedObject class="EGCE" operation="create" version="NAP1.0">

<defaults name="BTS template"/>5668877344100





5554302100000Milano

</managedObject>

<managedObject class="EWCE" operation="create" version="NAP1.0">2556474HuopalahtiA4740024421313305410612PROPERTY8

</managedObject><managedObject class="LCSE" operation="create" version="NAP1.0" distName="BSC-3030/SLMC-3030/LCSE-100 23">

<defaults name="Type2" />231003320452531

5630249034055602695583<list name="lcsNeighbors">20

<item>405100

</item></list>

60161040024

5412250

</managedObject><managedObject class="SITE" operation="create" version="NAP1.0">

Rome;;;;189643963602425755

</managedObject>





© Nokia Oyj A-11

<managedObject class="SITE" operation="create" version="NAP1.0">Hamburg;;;;189047191602231077


Haaga5;;;;19005188617890602556924


Haaga6;;;;20006188781640602453653


PROPERTY8;;;;188796623602361647

</managedObject>

</cmData></raml>



Example of a COCO file


© Nokia Oyj B-1

B Example of a COCO file <?xml version="1.0"?><raml xmlns="raml20.xsd" version="2.0">

<cmData type="plan" scope="all" name="cocoTesting"><header><log dateTime="2005-1-10T15:50:25" action="created" user="bosley" appInfo="NetAct Planner 5.0.0.3"></log></header>

<managedObject class="COSY" version="NAP1.0">BRITISHNATIONAL-GRIDORD SURV GBMETERS

</managedObject>

<managedObject class="COCO" version="1.0" operation="create" distName="RNC-2/COCO-12">31001

14528452834016000010001011

<list name="AAL2SignLinkTPList">

<item>13445284528

</item></list><<

<list name="AAL2TPList"><item>

34150943150943



Example of a COCO file

B-2 © Nokia Oyj DN04177508Issue 1-0 en

133

</item></list><

<list name="DNBAPTPList"><item>

45284528351

</item></list><

</managedObject></cmData></raml>



Example of an AXC file


© Nokia Oyj C-1

C Example of an AXC file <?xml version="1.0"?><raml xmlns="raml20.xsd" version="2.0"><cmData type="plan" scope="all" name="AXCPDHSDH">

<header><log dateTime="2005-1-10T14:32:58" action="created" user="bosley" appInfo="NetAct Planner 5.0.0.3"></log></header>

<managedObject class="COSY" version="NAP1.0">UTMUTM-35NWGS84METERS

</managedObject>

<managedObject class="AXC" version="1.0" operation="create" distName="AXC-1">AXC1

</managedObject>

<managedObject class="PPTT" version="1.0" operation="create" distName="AXC-1/PPTT-1">72PDH_LINE_TYPE_MULTI_FRAME_G704PDH_SHORT_HAULDISABLEDQ1_TS16

</managedObject>

<managedObject class="IMAL" version="1.0" operation="create" distName="AXC-1/IMAL-1">72

</managedObject>

<managedObject class="IMAL" version="1.0" operation="create" distName="AXC-1/IMAL-2">7

3</managedObject>

<managedObject class="IMAG" version="1.0" operation="create" distName="AXC-1/IMAG-1">73<list name="imaLinkPtrs">

<item>72

</item><item>

7




C-2 © Nokia Oyj DN04177508Issue 1-0 en

3</item>

</list><12m645

</managedObject>

<managedObject class="ACCP" version="1.0" operation="create" distName="AXC-1/ACCP-1">724789108910FALSE

</managedObject>

<managedObject class="PPTT" version="1.0" operation="create" distName="AXC-1/PPTT-2">74PDH_LINE_TYPE_MULTI_FRAME_G704PDH_SHORT_HAULDISABLEDQ1_TS16

</managedObject>


</managedObject>


</managedObject>

<managedObject class="IMAG" version="1.0" operation="create" distName="AXC-1/IMAG-2">74<list name="imaLinkPtrs">


</item><item>

75

</item></list><13m128

5</managedObject>


</managedObject>





© Nokia Oyj C-3

<managedObject class="TRDE" version="1.0" operation="create" distName="AXC-1/TRDE-200">CBRCBR13103109932253225

</managedObject>

<managedObject class="FRLI" version="1.0" operation="create" distName="AXC-1/FRLI-1">7431TRUE

</managedObject>

<managedObject class="VPCT" version="1.0" operation="create" distName="AXC-1/VPCT-1">710200

</managedObject>

<managedObject class="VPTT" version="1.0" operation="create" distName="AXC-1/VPTT-1">710CBR,UBR

</managedObject>


</managedObject>


</managedObject>


</managedObject>

<managedObject class="VPCT" version="1.0" operation="create" distName="AXC-1/VPCT-2">

740200

</managedObject>

<managedObject class="XCON" version="1.0" operation="create" distName="AXC-1/XCON-1">720740





</managedObject>

<managedObject class="CIWT" version="1.0" operation="create" distName="AXC-1/CIWT-1">724033UNSTRUCTUREDNULL47

</managedObject>

<managedObject class="IFPU" version="1.0" operation="create" distName="AXC-1/IFPU-1">72

</managedObject>

<managedObject class="IFPU" version="1.0" operation="create" distName="AXC-1/IFPU-1">74

</managedObject>

<managedObject class="IFPG" version="1.0" operation="create" distName="AXC-1/IFPG-1">mspOnnonRevertive<list name="transIfPuPtrs">


</item><item>

74

</item></list><

</managedObject>

<managedObject class="A2ST" version="1.0" operation="create" distName="AXC-1/A2ST-1">NULL72034FALSEFALSE0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F

</managedObject>

<managedObject class="A2ST" version="1.0" operation="create" distName="AXC-1/A2ST-2">NULL72

035FALSEFALSE0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F

</managedObject>

<managedObject class="A2UT" version="1.0" operation="create" distName="AXC-1/A2UT-1">720330





© Nokia Oyj C-5

2FALSE

</managedObject>

<managedObject class="A2UT" version="1.0" operation="create" distName="AXC-1/A2UT-2">7203302FALSE

</managedObject>


</managedObject>

<managedObject class="AXCSDH" version="1.0" operation="create" distName="AXC-2/AXCSDH-1">91LASER_MODE_ONSTM_SIGNAL_LEVEL_2NULLNULLBER_MODE_3TRUENULLNULLRDI_MODE_AUTOMATIC

</managedObject>

<managedObject class="ACCP" version="1.0" operation="create" distName="AXC-2/ACCP-1">9147353207

353207FALSE

</managedObject>

<managedObject class="AXCSDH" version="1.0" operation="create" distName="AXC-2/AXCSDH-2">94LASER_MODE_ONSTM_SIGNAL_LEVEL_2NULLNULLBER_MODE_3TRUENULLNULLRDI_MODE_AUTOMATIC

</managedObject>


</managedObject>

<managedObject class="TRDE" version="1.0" operation="create" distName="AXC-2/TRDE-200">





CBRCBR13013019933223322

</managedObject>


</managedObject>


</managedObject>

<managedObject class="TRDE" version="1.0" operation="create" distName="AXC-2/TRDE-203">CBRCBR1999

9111111111111

</managedObject>

<managedObject class="VCTT" version="1.0" operation="create" distName="AXC-2/VCTT-1">940331

</managedObject>

<managedObject class="VCTT" version="1.0" operation="create" distName="AXC-2/VCTT-2">94

0331

</managedObject>


</managedObject>





© Nokia Oyj C-7


</managedObject>


</managedObject>


</managedObject>


</managedObject>


</managedObject>

<managedObject class="VCCT" version="1.0" operation="create" distName="AXC-2/VCCT-1">9

4033200FALSEFALSEFALSEUser Plane VCC_1

</managedObject>

<managedObject class="VCCT" version="1.0" operation="create" distName="AXC-2/VCCT-2">92033200

FALSEFALSEFALSEUser Plane VCC_1

</managedObject>

<managedObject class="XCON" version="1.0" operation="create" distName="AXC-2/XCON-1">9103394





033

</managedObject>


</managedObject>


</managedObject>


</managedObject>


</managedObject>

<managedObject class="VCCT" version="1.0" operation="create" distName="AXC-2/VCCT-1">940360

FALSEFALSEFALSEUser Plane AAL2 Sig VCC_1

</managedObject>

<managedObject class="VCCT" version="1.0" operation="create" distName="AXC-2/VCCT-2">920360FALSEFALSEFALSEUser Plane AAL2 Sig VCC_1

</managedObject>

<managedObject class="XCON" version="1.0" operation="create" distName="AXC-2/XCON-2">9103694036

</managedObject>





© Nokia Oyj C-9


</managedObject>


</managedObject>


</managedObject>

<managedObject class="VPTT" version="1.0" operation="create" name="slotNumber">920CBR,UBR

</managedObject>

<managedObject class="VCCT" version="1.0" operation="create" distName="AXC-2/VCCT-1">94034202FALSEFALSEFALSENBAP-C VCC_1

</managedObject>

<managedObject class="VCCT" version="1.0" operation="create" distName="AXC-2/VCCT-2">92034202FALSEFALSEFALSENBAP-C VCC_1

</managedObject>

<managedObject class="XCON" version="1.0" operation="create" distName="AXC-2/XCON-3">91

03494034

</managedObject>






</managedObject>


</managedObject>


</managedObject>


</managedObject>

<managedObject class="VCCT" version="1.0" operation="create" distName="AXC-2/VCCT-1">94035203FALSEFALSEFALSENBAP-D VCC_1

</managedObject>

<managedObject class="VCCT" version="1.0" operation="create" distName="AXC-2/VCCT-2">92

035203FALSEFALSEFALSENBAP-D VCC_1

</managedObject>

<managedObject class="XCON" version="1.0" operation="create" distName="AXC-2/XCON-4">9103594

035

</managedObject>






© Nokia Oyj C-11

</managedObject>


</managedObject>


</managedObject>


</managedObject>


</managedObject>

<managedObject class="TRDE" version="1.0" operation="create" distName="AXC-3/TRDE-200">

UBRUBR13103109932253225

</managedObject>

<managedObject class="IPRT" version="1.0" operation="create" distName="AXC-3/IPRT-1">192.34.87.98255.254.0.0192.34.87.99

</managedObject>

<managedObject class="IAIF" version="1.0" operation="create" distName="AXC-3/IAIF-1">32033192.34.87.98192.34.87.99

</managedObject>

<managedObject class="IAIF" version="1.0" operation="create" distName="AXC-3/IAIF-1">330





34192.34.87.100192.34.87.99

</managedObject>

<managedObject class="IEIF" version="1.0" operation="create" distName="AXC-3/IEIF-1">TRUE192.34.87.255192.34.87.99255.254.0.0

</managedObject>


</managedObject>


</managedObject>


</managedObject>


</managedObject>


</managedObject>


</managedObject>

<managedObject class="XCON" version="1.0" operation="create" distName="AXC-3/XCON-1">320330

</managedObject>

<managedObject class="A2ST" version="1.0" operation="create" distName="AXC-3/A2ST-1">NULL33





© Nokia Oyj C-13

034FALSEFALSE0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F0F

</managedObject>


</managedObject>

</cmData></raml>



Glossary


© Nokia Oyj i

Glossary

2.5G The data services in 2G networks

2G Generation of mobile networks - digital technology, frequency division

3G Third mobile network generation

ADCE Adjacent Cell managed object in NetAct

ADJG GSM adjacency for a UMTS WCEL

ADJI Intra-frequency adjacency in UMTS

ADJS Inter-frequency adjacency in UMTS

ADJW UMTS adjacency in GSM

ANTE Antenna Instance

ATM Asychronous Transfer Mode

AXC ATM Cross Connect

BCF Basic Control Function

BER Bit Error Ratio

BSC Base Station Controller

BTS Base Transceiver Station

COSY Co-ordinate System

DTD Document Type Definition

EDGE Enhanced Data Rate for GSM Evolution

EGCE External BTS

EOC Embedded Operations Channel

EWCE External WCEL

GCAL GSM Cell Antenna Link

GPRS General Packet Radio Service

GSM Global Standard for Mobile communications

HSCSD High Speed Circuit Switched data

IMA Inverse Multiplexing for ATM

LAC Location Area Code

LMU Location Measurement Unit

MAIO Mobile Allocation Index Offset

MAL Mobile Allocation List

MCC Mobile Country Code



Glossary

MNC Mobile Network Code

NCC Network Colour Code

NMS Network Management System

PLMN Public Land Mobile Network

RAC NetAct Radio Access Configurator, Nokia's Network Management System

RAML/CM Radio Access Markup Language / Configuration Management

RAN Radio Access Network

RDI Redirection Index

RNC Radio Network Controller

SDH Synchronous Digital Hierarchy

SITE Corresponds to physical location

TRX Transmit/Receiver unit

WBTS WCDMA Base Station

WCAL WCDMA Cell Antenna Link

WCDMA Wideband Code Division Multiple Access - a 3G mobile network standard

LCSE Location Services Element

WLCSE Location Services Entity

WCEL UMTS Cell

XML Extensible Markup Language

Documents

NetActPlanner_5_0_ConfigurationIssue1-0.pdf