commander user reference guide.pdf

Commander User Reference Guide

Software Version 6.1

Reference Guide Edition 1

© Copyright 2008 AIRCOM International All rights reserved

ADVANTAGE, ASSET, CONNECT, DATASAFE, DIRECT ENTERPRISE, NEPTUNE, ARRAYWIZARD, OPTIMA, OSSEXPERT, and WEBWIZARD are recognised trademarks of AIRCOM International. Other product names are trademarks of their respective companies.

Microsoft Excel , .NET™, Microsoft Office, Outlook , Visual Basic Windows®,

Windows XP™, Windows Vista™ and Word are trademarks of the Microsoft Corporation.

This documentation is protected by copyright and contains proprietary and confidential information. No part of the contents of this documentation may be disclosed, used or reproduced in any form, or by any means, without the prior written consent of AIRCOM International.

Although AIRCOM International has collated this documentation to reflect the features and capabilities supported in the software products, the company makes no warranty or representation, either expressed or implied, about this documentation, its quality or fitness for particular customer purpose. Users are solely responsible for the proper use of ENTERPRISE software and the application of the results obtained.

An electronic version of this document exists.

This User Reference Guide finalised on 13 May 2008.

Refer to the Online Help for more information.

This User Reference Guide prepared by:

AIRCOM International Ltd Cassini Court Randalls Research Park Randalls Way Leatherhead Surrey KT22 7TW

Telephone: +44 (0) 1932 442000 Support Hotline: +44 (0) 1932 442345 Fax: +44 (0) 1932 442005 Web: www.aircominternational.com

Commander User Reference Guide Version 6.1

Contents

Chapter 1 Introduction 7

Explanation of Symbols ..................................................................................... 8

Obtaining User Assistance ................................................................................. 8

Who is This User Reference Guide For? ..................................................................... 9 About the ENTERPRISE User Reference Guides .................................................... 10 Can You Improve Our User Assistance? ................................................................... 11 Obtaining Support ...................................................................................................... 11 Obtaining Further Information and Services .............................................................. 13

Chapter 2 Using Commander 15

Creating a Command File for Commander....................................................... 15

Creating the Execute Section of your Command File ............................................... 16 Creating the Function Section of your Command File ............................................... 17

Running your Command File ........................................................................... 18

Running the Command File from the Command Prompt .......................................... 18 Running the Command File Using a Batch File......................................................... 19

Viewing the Log File Generated by Commander .............................................. 20

About the Available Command Parameters and Values ................................... 21

Using the Export Planet Command in a Command File ............................................ 21 Using the Export ENTERPRISE Tables Command in a Command File ................... 22 Using the Export XML Command in a Command File ............................................... 23 Using the Import XML Command in a Command File ............................................... 28 Using the Import Planet Command in a Command File ............................................ 30 Using the Commit Network Elements Command in a Command File ....................... 30 Using the Auto Cu Generation Command in a Command File.................................. 31

Index 33


Introduction

Commander enables you to add functions into a command file and run the file either from Commander or from a batch file. You can also access your project's database, without having to run ENTERPRISE.

You can set up Commander to:

Export and import PlaNet/EET data

Export ENTERPRISE tables

Export and import XML

Commit network elements

Automatically create and export Cu plots

Before using Commander, you must have a correctly configured Oracle database and ENTERPRISE project. For further information on configuring your database and setting up a project, see the ENTERPRISE Installation and Administration Guide.

In This Section

Explanation of Symbols 8 Obtaining User Assistance 8

C H A P T E R 1


Explanation of Symbols

Throughout this guide, where appropriate, some symbols are used to highlight particular pieces of text. Three different symbols are in use, and are explained as follows:

Symbol Brief Description Full Description

Note Signifies text that should be noted or carefully considered.

Tip Signifies text that may help you do something in an easier or

quicker way.

Warning or Important Signifies text that is intended as a warning or something

important.

Obtaining User Assistance

Using Online Help

ENTERPRISE products come with a complete system of online Help which you can access in three ways:

From the Help menu, click Help Contents. Scroll through the table of contents and choose a relevant topic to display.

To search for something particular, from the Help menu, click Help Contents and using the Index tab or Search tab, type in a letter or word to start searching for relevant topics.

Press F1 in a dialog box to view context-sensitive help (available for most dialog boxes).

If you are using ENTERPRISE within a CITRIX environment, to ensure that the Help graphics are displayed, you should ensure that your visualisation settings are configured to display greater than 256 colours.

Using ENTERPRISE User Reference Guides

If you prefer to read printed content, we also provide User Reference Guides. To view or print these as PDFs (Adobe Acrobat portable document format):

1 Make sure you have Adobe Acrobat Reader installed on your PC. If you do not have this, you can install it from the ENTERPRISE CD, or get it from the Adobe website.

Adobe and Acrobat are trademarks of Adobe Systems, Incorporated.

2 Click Start on the taskbar, point to Programs, then AIRCOM International, then ENTERPRISE, then Docs.

- or -

Navigate to the Docs folder in the location where you installed the product.

If neither of these exists, please contact your administrator.


3 Double-click the PDF file that you want to view.

If you have a customer web account, you can also download the latest User Reference Guides from our website.

Checking Release Notes

Each release of the ENTERPRISE software is accompanied by Release Notes, giving important information on system requirements, installation, known issues, upgrades and so on. These notes are included in the ENTERPRISE CD, or you can download them from our website.

For any further documentation, such as application notes and extra reference information, please email the support team at the address described in Obtaining Support on page 11.

Who is This User Reference Guide For?

The ENTERPRISE User Reference Guides are intended for different audiences, depending on the particular product. Typical prerequisites include a good understanding of the following:

The appropriate telecoms technologies and the associated network planning methods (for planning software)

Relational database management, and in particular Oracle database creation and administration procedures (for administrative software)

The various parameters utilised for monitoring and optimising networks (for OSS software)

Irrespective of the particular product, the following basic knowledge is required:

Microsoft Windows concepts

The functions of the Microsoft Office suite of tools, in particular Excel


About the ENTERPRISE User Reference Guides

This table describes our range of User Reference Guides:

This Guide Contains Information On

What's New The main difference between the latest versions of the ENTERPRISE suite.

ENTERPRISE Installation and Administration Installing and configuring ENTERPRISE, your network, and Oracle databases. Using Administrator to create users and groups, and set permissions.

Also contains information on software licensing.

ENTERPRISE Database Reference The relationships between tables in the database and the contents of each table.

ENTERPRISE User Reference Functionality that is common to most of the products in the ENTERPRISE suite, including how to access, view, edit and store data.

ENTERPRISE Technical Reference File formats, as well as antenna and diffraction calculations.

ADVANTAGE User Reference Using ADVANTAGE to plan and optimise networks automatically, consider measured data in analysis/optimisation, analyse network performance, identify problematic areas/cells, and more.

ARRAYWIZARD User Reference Using ARRAYWIZARD to automatically generate coverage predictions and best server arrays, which gives you instantaneous display of coverage and interference information for pre-selected filters when loaded into ASSET.

ASSET User Reference Using ASSET, the network planning and analysis tool, to design a range of cellular networks.

Includes information on hierarchical network planning, propagation modelling, service and bearer definition, coverage analysis, traffic planning, neighbour planning, frequency planning, CW data analysis, detailed reporting, analysis arrays and simulation of network performance.

ASSET Technical Reference Array descriptions and information on some of the algorithms used in ASSET.

CONNECT User Reference Using CONNECT, the network transmission and microwave link planning software for full network physical link design and logical link design.

Also contains CONNECT-specific reference information.

DATASAFE User Reference Using DATASAFE, our network configuration tool to implement both small and large scale changes to networks

DIRECT User Reference Using DIRECT to design telecommunications networks of different network layers. Explains how to plan cellular, PSTN and data networks at a both general and strategic level.

Also contains DIRECT-specific reference information.

NEPTUNE User Reference Using NEPTUNE to collect, import and analyse testmobile data and using the optional module, PROBE for additional analysis.

Also contains reference information on NEPTUNE file formats.

OPTIMA User Reference Using OPTIMA to view performance data and statistics both with ENTERPRISE and standalone using OPTIMA Lite.

OSSEXPERT User Reference Using OSSEXPERT to manage optimisation tasks in wireless networks.

RANOPT User Reference Using RANOPT to efficiently find faults in your network, optimise and validate its performance prior to commercial launch.

WEBWIZARD User Reference Using WEBWIZARD to display GIS and report information of network data, including creating layers, regions, nodes, layer types, administering and configuring the system and using the GIS view, explorer and report viewers.


Can You Improve Our User Assistance?

We are always trying to improve the online Help and User Reference Guides.

If you cannot find the Help you were looking for, need more information, or have any suggestions for improvements, we would be grateful for your feedback.

Also, if you are generally satisfied with these resources, we would appreciate any positive feedback.

Online Questionnaire

You can help us by completing our brief online questionnaire (http://tinyurl.com/y47rqn).

Alternatively, you can contact us directly at [email protected].

Obtaining Support

If you have a difficulty you cannot resolve yourself using the online Help or Reference Guides, or you have found a possible fault in the software, you can log a support request as described below. You may also wish to contact us if you want to:

Register for a customer web account to access the Support area

Obtain further documentation, such as application notes and extra reference information

Logging Support Requests Online

To log a support request online:

1 Go to the AIRCOM website, at www.aircominternational.com.

2 Click the link to Support.

3 Log in, using your customer web account username and password.

4 In the Technical Support pane, click Online Helpdesk System.

5 Click Log New.

6 Enter the details of your request, and then click Log.


Contacting us via Telephone or Email

If you wish to contact us directly, here are the contact details of our regional offices:

Location Regional Office Contact Details

Europe United Kingdom Tel : +44 (0) 01932 442345 Fax :+44 (0) 01932 442005

[email protected]

Sweden [email protected]

France [email protected]

Italy [email protected]

Germany [email protected]

Belgium [email protected]

Middle East, Africa and Central Asia United Arab Emirates Tel : +971 4 391 2642 Fax :+971 4 391 8660

[email protected]

South Africa Tel : +27 11 3243600 Fax : +27 11 7848027

[email protected]

Americas Mexico [email protected]

USA Tel : +1 866 207 8083 Fax : +1 214 360 7241

[email protected]

Brazil Tel : +55 12 3941-2199 Fax : +55 12 3911-3727

[email protected]

Asia and Oceania Australia [email protected]

Singapore [email protected]

China [email protected]

Taiwan [email protected]

India [email protected]

When contacting us with a support query, it would help us if you:

Give us as much information as possible about the problem and the context in which it occurred

State the version and build you are using

Have all the details of your query to hand

Are logged into the ENTERPRISE application

Can send extracts of your data sets if we need them to reproduce your problem


Obtaining Further Information and Services

As well as comprehensive online Help and User Reference Guides and dedicated Product Support, AIRCOM additionally provides:

Online Knowledgebase of Articles

If you register for a customer web account, you can view our searchable technical database in the Product Support section of the AIRCOM website. This Knowledgebase contains articles created by our support professionals who have resolved issues for our customers, and is constantly updated, expanded, and refined to ensure that you have access to the very latest information.

Online Technical Forum

You can obtain useful information from our online problem-solving technical forum.

The URL address is: http://www2.aircom.co.uk/techforum

If you would like permission to access to this resource, please email the support team at the address described in Obtaining Support on page 11.

Power Tools

If you register for a customer web account, you can download from a selection of useful power tools, such as file conversion utilities.

Latest Copies of the User Reference Guides

If you register for a customer web account, you can download the latest User Reference Guides (PDFs) from our website. If you do this, please check the back of the reference guides for any additions or corrections.

Consultancy Services

AIRCOM also provide full radio consultancy services in Network Audits, Business Planning Support, Licence Applications, Radio Network Planning, Telecommunications Research and System Modelling and Propagation Analysis and Modelling.

Training

There is a wide variety of courses run by AIRCOM. These courses range from tool training to technology training. For details, contact Competence Development Solutions ([email protected]).


Using Commander

Before you can start to use Commander, you must consider the connection to the data source that your ENTERPRISE project uses. You must know:

The name of your Oracle data source

The number of the project you will be working on

Your project user name and password

In This Section

Creating a Command File for Commander 15 Running your Command File 18 Viewing the Log File Generated by Commander 20 About the Available Command Parameters and Values 21

Creating a Command File for Commander

Your command file contains all the functions you can perform on your ENTERPRISE data and is executed from the command prompt or by using a batch file. The command file contains two sections:

Execute section

Function section

This example shows a command file. The first three lines are the Execute section, the remainder is the Function section. The Function section shows the commands that will be carried out by the functions listed in the Execute section.

[EXECUTE]

1=PLANET_export_example

2=export_example

3=XML_Export

C H A P T E R 2


[PLANET_export_example]

COMMAND=EXPORT_PLANET

VERSION=PLANET28

FILTER=ALL

FLAGS=d:\temp\dbcmd\flags.txt

SITES=d:\temp\dbcmd\sites.txt

CARRIERS=d:\temp\dbcmd\carriers.txt

NBRS=d:\temp\dbcmd\nbrs.txt

CARRIER_TYPES=d:\temp\dbcmd\carriers

[export_example]

COMMAND=EXPORT_TABLES

VERSION=PLANET28

FILE=C:\command\table\jersey.aii

[XML_Export]

COMMAND=EXPORT_XML

FILTER=ALL

FOLDER=c:\xml

PROJECT_ITEMS=PROPERTY MSC BSC CELL-SITE

LOCATION_UNIT=GRID

Creating the Execute Section of your Command File

The Execute section of your command file specifies the functions to be executed. It is denoted by the string EXECUTE on the first line and numbered statements denoting functions to call, on the proceeding lines.

To create the Execute section of your command file:

1 Open a text editor, for example, Microsoft Notepad.

2 Type [EXECUTE].

3 Type a sequence number, starting from 1, followed by a function name to execute. For example:

[EXECUTE]


2=export_example

You can list as many function names as you need. The process will terminate once all the functions have been run.

4 Now you can create the Function section of the file.


Creating the Function Section of your Command File

The Function section comes directly after the Execute section in your command file. Use it to name your functions and assign parameter values to command types.

To create the Function section of your command file:

1 Open your command file and ensure your cursor is below the Execute section.

2 Type in brackets a name for your function. For the command file to run correctly, this name must correspond to those present in the Execute section. For example:


3 Type command= followed by the command type. For example:


The complete list of command parameters and associated values is shown under About the Available Command Parameters and Values on page 21.

4 Type parameters and parameter values associated to the command type entered. For example, using the EXPORT_PLANET example, you might type:

Version=PLANET28

FILTER=ALL


You may list any number of parameters associated to a command type. The process will finish when all the parameters have been run.

5 Save the file as Export_co.txt in a suitable location.

When creating command files for different projects choose meaningful names.

This example shows the Function section of a command file:

[XML_Export]

COMMAND=EXPORT_XML

FILTER=ALL

FOLDER=c:\xml


LOCATION_UNIT=GRID



VERSION=PLANET28

FILTER=ALL







Running your Command File

You can run your command file in two ways:

From the command prompt

Using a batch file

As part of running your command file, you have to provide the path to where you installed the product. This can be done manually, as described in the running instructions, or automatically by running the CommandPrompt.bat, which can be run using the shortcut in Start>Programs>AIRCOM International>ENTERPRISE>Misc.

Running the Command File from the Command Prompt

To run your command file from the command prompt:

1 Open the Command Prompt and if you haven't used the CommandPrompt.bat, change the directory to the Common folder under the folder where you installed your product.

2 Type the following information all on one line with a space between each item:

..\DBCMDnn where nn is the ENTERPRISE version number

the name of your Oracle datasource

your project number (for more information contact your administrator)

your project name

your project password

the full path name of your command file

The following example shows a command prompt line which would be correct for ENTERPRISE version 6.0:

C:\Program Files\AIRCOM

International\ENTERPRISE\Common>..\DBCMD60 asset60 1

username password "c:\temp\cmd.txt"


Running the Command File Using a Batch File

As well as running your command file from the command prompt you can create a batch file to execute your command file. To do this:

1 Open a text editor, for example Notepad.

2 Type @echo off and then press Enter.

3 Type echo Running Commander Export and press the Return key.

4 If you have not used CommandPrompt.bat, type cd then the full path to the Common subfolder of the ENTERPRISE folder where you installed the product to, in quotation marks, and press the Return key.

5 Type the following information all on one line:

..\DBCMDnn where nn is the ENTERPRISE version number

the name of your Oracle datasource.

your project number. If you are unsure of this, ask your system administrator.

your user name and password.

the full path name of your command file in quotation marks.

6 Now press Enter.

7 Type echo End of BatchFileName.

Use the name of your own batch file instead of the word BatchFileName.

8 Save your file as a *.bat file, using the name you have used in the file.

9 In Windows Explorer, browse for your file then double-click it to run it.

The following example shows a batch file that could be used for ENTERPRISE 6.0:

@echo off

echo Running Commander Export

cd "C:\Program Files\AIRCOM International\ENTERPRISE\Common"

..\DBCMD60 asset60 1 username password

"c:\command\Export_co.txt"

echo End of Export Batch


Viewing the Log File Generated by Commander

A log file is generated when you run a command file. To locate and view the log file:

1 In Windows Explorer, browse to the folder where you saved your command file.

2 Double-click on the log file, whose filename will contain its creation date and time.

3 View the file. It contains a complete list of what occurred and what failed. An example file is shown here:

2005-10-08 11:58:29: ENTERPRISECommander Starting...

2005-10-08 11:58:29: Using command file

d:\commander\export_config.txt

2005-10-08 11:58:29: Connecting to ora92 as user1

2005-10-08 11:58:32: Read 4 project(s):

2005-10-08 11:58:32: Starting Project 1: UKProject...

2005-10-08 11:58:42: No 'Building Height Dir' entry. No

building height raster data available

2005-10-08 11:58:44: The Vector added was A Roads

2005-10-08 11:58:44: The Vector added was B Roads

2005-10-08 11:58:44: The Vector added was Motorways

2005-10-08 11:58:44: Vector B Roads was removed because file

\\Dbs\Cd3_mapdata\vector\broads_bin.vbf was not found

2005-10-08 11:59:02: Ready

2005-10-08 11:59:02: Reading Command File

d:\commander\export_config.txt

2005-10-08 11:59:02: Running EXPORT_XML [ENTERPRISE Export]

2005-10-08 11:59:02: Using Filter: ALL

2005-10-08 11:59:02: Exporting to d:\commander\xml

2005-10-08 11:59:05: Saved d:\commander\xml\PROPERTY-

LIST001.xml

2005-10-08 11:59:05: Saved d:\commander\xml\MSC-LIST001.xml

2005-10-08 11:59:05: Saved d:\commander\xml\BSC-LIST001.xml

2005-10-08 11:59:05: Saved d:\commander\xml\CELL-SITE-

LIST001.xml

2005-10-08 11:59:07: Saved d:\commander\xml\GSM-CELL-SITE-

LIST001.xml

2005-10-08 11:59:09: Saved d:\commander\xml\MODEL-

LIST001.xml

2005-10-08 11:59:09: Saved d:\commander\xml\INDEX001.xml

2005-10-08 11:59:05: Completed EXPORT_XML [ENTERPRISE

Export] successfully

2005-10-08 11:59:05: Closing Project1: UKProject...

2005-10-08 11:59:05: ENTERPRISECommander Terminating...


About the Available Command Parameters and Values

This section describes the parameters and values that apply to these command types.

Export Planet

Export ENTERPRISE Tables

Export XML

Import XML

Import Planet

Commit Network Elements

Auto Cu Generation

Using the Export Planet Command in a Command File

Before entering command parameters and values, ensure you have included the command type COMMAND=EXPORT_PLANET.

The following table shows all available command parameters and values that apply to the Export Planet command type:

Parameter Parameter Values

VERSION The desired Planet export version:

2.5 PLANET25

2.6 PLANET26

2.7 PLANET27

2.8 PLANET28

FILTER The name of the filter from which to derive a subset of sites. The name should be exactly the same as that displayed in ENTERPRISE.

If no specific filter is required use All.

FLAGS The full pathname in which to store the site status flags. If this parameter is omitted or no filename is specified then this information will not be exported.

SITES The full pathname in which to store site and cell data. If this parameter is omitted or no filename is specified then this information will not be exported.

CARRIERS The full pathname in which to store the carrier information. If this parameter is omitted or no filename is specified then this information will not be exported.

NBRS The full pathname in which to store neighbour relations. If this parameter is omitted or no filename is specified then this information will not be exported

CARRIER_ TYPES

The full pathname without file-extension in which to store carrier types, groups and names information. The file extensions *.types, *.groups and *.names will be appended automatically.

Due to the support for multiple frequency reuse patterns, the groups filename is modified to include the name of the carrier layer to which it corresponds. Note that this is different to exporting in ENTERPRISE where you are prompted for a specific carrier layer for which the reuse pattern should be exported.

If this parameter is omitted or no filename is specified then this information will not be exported.


This example shows a command file including EXPORT_PLANET, EXPORT_TABLES and EXPORT_XML commands:

[EXECUTE]


2=export_example

3=XML_Export



VERSION=PLANET28

FILTER=ALL






[export_example]

COMMAND=EXPORT_TABLES

VERSION=PLANET28

FILE=C:\command\table\jersey.aii

[XML_Export]

COMMAND=EXPORT_XML

FILTER=ALL

FOLDER=c:\xml


LOCATION_UNIT=GRID

Using the Export ENTERPRISE Tables Command in a Command File

Before entering command parameters and values, ensure you have included the command type COMMAND=EXPORT_TABLES.

When writing a command file for Commander, and using the Export ENTERPRISE Tables command type, the only parameter that applies is:


FILE This should reference the full pathname of the export index file.

The filename should have the file extension *.aii. If you specify no extension or a different extension, then Commander will replaced it with *.aii.

In the same folder as the index file, a number of other *.aid files are created containing table data.

If this parameter is omitted or you do not specify a filename then no information is exported.


Using the Export XML Command in a Command File

Before entering command parameters and values, ensure you have included the command type COMMAND=EXPORT_XML.

The following table shows all available command parameters and values that apply to the Export XML command type:


FILTER The name of the filter from which to derive a subset of network elements, either PROJECT_ITEMS or CONFIG_ITEMS. The name should be exactly the same as that displayed in ENTERPRISE.


FOLDER The full pathname of the directory into which the XML files will be written.

If this parameter is omitted no information will be exported.

MAX_NODES_ INDEX

Can be used to override the setting for the limit of XML nodes available in the File option for each type of item (such as property or MSC). It applies to all elements being exported regardless of type (Project, Config, Templates and so on).

If this parameter is not present in the file, Commander uses the configured values from ENTERPRISE if they exist. If they do not exist, the default value of Unlimited is used.

The following values are accepted:

-1 = Unlimited

0 = 500

1 = 1000

2 = 2000

3 = 4000

4 = 8000

5 = 16000

6 = 32000

7 = 64000

PREDICTION_ FILENAME

YES or No to indicate whether or not the PRED-SYS-INFO-RO & ANT-INFO-RO sections are output in the XML data. These sections provide information which helps to locate the appropriate prediction file. The default setting is NO.



PROJECT_ITEMS This is a space-separated list of the project data items that will be exported. Leave this blank or omit the field if you do not want to export project data items.

The following items are accepted:

BSC - GSM BSC

BTS-ROUTE – BTS route

CARRIERS-PMP – PMP carriers

CDMA-BS – CDMA BS

CDMA-BSC – CDMA BSC

CDMA-MSC – CDMA MSC

CDMA-REPEATER – CDMA repeater

CDMA-SECTOR – CDMA sector

CDMA-TRAFFIC – CDMA BS simulated traffic

CELLULAR-CONN – Logical cellular connection

CELL-SITE - GSM/AMPS cell site

DNODE - GSM distribution node

GSM-CELL – GSM/AMPS cell

HUB-LINKEND-PMP – PMP hub linkend

HUB-PMP – PMP hub

MSC - GSM/AMPS MSC

LCSE-NEIGHBOUR – LCSE neighbours

LINKEND-PTP – PTP linkend

LMU – LMU node

LOGICAL-CONN – Logical connection

LOG-NODE – 3G logical node

NEIGHBOUR – Neighbours

NETWORK – 3G network

NODE – UMTS node

NODE-TRAFFIC – UMTS node simulated traffic

PMP-INTERCON – PMP interconnection

PRL-BACKTOBACK – Back to back PRL

PRL-REFLECTOR – Reflector PRL

PROPERTY - Property

PROPERTY-CONSTRAINTS – Property constraints

PTP-INTERCON – PTP interconnection

REPEATER – GSM/AMPS repeater

RNC – RNC

SECTOR-PMP – PMP sector

SGSN – UMTS SGSN

SITE-CONSTRAINTS – Site constraints

UMTS-CELL – UMTS cell

UMTS-REPEATER – UMTS repeater

WMSC – UMTS WMSC



LOCATION_UNIT Specifies the output type of co-ordinates. The following items are accepted:

GRID - Easting/Northing

LL - Longitude/Latitude

DLL - Decimal Longitude/Latitude

If this parameter is not specified a default equivalent to a setting of DLL is assumed.



CONFIG_ITEMS This is a space-separated list of the configuration data items that will be exported. Leave this blank or omit the field if you do not want to export configuration data items. The following items are accepted:

ANTENNA – Antenna

BAND – Band channels

BCF-TYPE – BCF Type

BEARERS – Bearers

BK-BK-PRL-NF-CURVE

BTS – BTS type

CABIN – Cabin

CAR-LAYER – GSM/AMPS carrier layer

CARRIER-CDMA – CDMA carrier

CARRIERS – GSM/AMPS carriers

CARRIER-UMTS – UMTS carrier

CELL-EQUIP – Cell equipment

CELL-LAYER – GSM/AMPS cell layer

CHAN-TRX-SETUP – Channel transmitter/receiver setup

CI-BER-CONVERSION – C/I BER conversion

CI-OBJECTIVE – C/I objectives

CONTACT – Contact person

ECSD-MCS-CURVE

EGPRS-MCS-CURVE

FEEDER – Feeder

FREQ-HOP-DIV-GAIN – Frequency hopping division gain

GPRS-MCS-CURVE

EV-DO-DL-PARAMETERS – EV-DO downlink parameters

HSCSD-MCS-CURVE

TIMESLOT-OCCUPANCY

LINK-TERMINAL – Link terminal type

LINK-TYPE – Link type

MANAGED-PREDICTIONS-MODEL – Managed predictions model

MAST – Mast

MAST-HEAD-AMPLIFIER – Mast head amplifier

MODEL – Prediction model

MW-ANTENNA – Microwave antenna

NODE-TYPE – Node type

PROJECT-SETTINGS – User settings for a project

RADIO – Radio equipment

RFL-PRL-NF-CURVE

SERVICES – Services

SPLITTER – Splitter

SUPPLIER – Equipment supplier

TERMINAL TYPES - Terminal types

UMTS-RESOURCE – UMTS resource



TEMPLATE_ITEMS This is a space-separated list of the template data items that will be exported. Leave this blank or omit the field if you do not want to export template data items.


MSC – GSM/AMPS MSC

BSC – GSM BSC

CELL-SITE – GSM/AMPS cell site

DNODE – GSM distribution node


PROPERTY – Property

LMU – LMU node

WMSC – UMTS WMSC

SGSN – UMTS SGSN

RNC – UMTS RNC

NODE – UMTS node




CDMA-BS – CDMA BS


HUB-PMP – PMP hub


CARRIERS-PMP – PMP carrier





PRL-BACKTOBACK – Back to back PRL

PRL-REFLECTOR – Reflector PRL

FILTER_(n) (n) must be replaced with a number. You can include this parameter more than once provided that each instance is on a separate line. For example:

FILTER_1 = NAME

FILTER_2 = NAME

FILTER_3 = NAME

where NAME represents a valid filter name.


Using the Import XML Command in a Command File

Before entering command parameters and values, ensure you have included the command type COMMAND=IMPORT_XML.

The following table shows all available command parameters and values that apply to the Import XML command type:


FOLDER The full pathname of the directory from which the XML files will be read. All files with the .xml extension will be read.

CONFLICTS This field instructs the program what to do when a conflict is detected during importing configuration or project items and can be set to one of the following:

STOP

LEAVE

MERGE

REPLACE

If any error occurs such as inadequate permissions, missing object IDs, missing dependencies (eg missing MSC when importing BSC), database errors, propagation model not registered and so on, the import will be aborted.

PROJECT_ITEMS This is a space separated list of the project data items that shall be imported. Leave blank or omit this field if no project data items will be imported. The same items are accepted as for export.

CONFIG_ITEMS This is a space separated list of the configuration data items that shall be imported. Leave blank or omit this field if no configuration data items are to be imported. The same items are accepted as for export.



TEMPLATE_ITEMS This is a space-separated list of the template data items that will be imported. Leave this blank or omit the field if you do not want to import project data items.


MSC – GSM/AMPS MSC

BSC – GSM BSC

CELL-SITE – GSM/AMPS cell site

DNODE – GSM distribution node


PROPERTY – Property

LMU – LMU node

WMSC – UMTS WMSC

SGSN – UMTS SGSN

RNC – UMTS RNC

NODE – UMTS node




CDMA-BS – CDMA BS


HUB-PMP – PMP hub


CARRIERS-PMP – PMP carrier





PRL-INTERCON – PTP interconnection

ON_MERGE_ REPLACE_LISTS

Binary flag controlling the behaviour of the Merge functionality:

NO=default behaviour as per the GUI merge functionality

YES=replaces list data with that in the XML file rather than adding to existing lists

Individual data types that require Replace-on-Merge have the REPLACE command appended to the end:

CONFIG_ITEMS=ANTENNA BANDS=REPLACE

PROJECT_ITEMS=PROPERTY GSM-CELL=REPLACE

These tell the database commander to replace the sub lists of BANDS and GSM-Cell data types on import.

FILTER_ITEMS The only value for this item is 'all' - an attempt will be made to import all filters present in the XML file. Unlike the export version of this parameter, the import version should be present only once.


Using the Import Planet Command in a Command File

Before entering command parameters and values, ensure you have included the command type COMMAND=IMPORT_PLANET.

The following table shows all available command parameters and values that apply to the Import Planet command type:


FOLDER The full pathname of the directory from which the Planet files will be read. All files with the .txt extension will be read.

CONFLICTS This field instructs the program what to do when a conflict is detected during importing configuration or project items and can be set to one of the following:

STOP

LEAVE

MERGE

REPLACE

If any error occurs the import will be aborted. Such errors include inadequate permissions, missing object IDs, missing dependencies (eg missing MSC when importing BSC), database errors, propagation model not registered, etc

PROJECT_ITEMS This is a space separated list of the project data items that shall be imported. Leave blank or omit this field if no project data items will be imported. The same items are accepted as for export.

CONFIG_ITEMS This is a space separated list of the configuration data items that shall be imported. Leave blank or omit this field if no configuration data items are to be imported. The same items are accepted as for export.

ON_MERGE_ REPLACE_LISTS

Binary flag controlling the behaviour of the Merge functionality.

NO = default behaviour as per the GUI merge functionality.

YES = replaces list data with that in the Planet file rather than adding to existing lists.

Using the Commit Network Elements Command in a Command File

Before entering command parameters and values, ensure you have included the command type COMMAND=COMMIT_NETWORK.

This command enables you to commit all outstanding applies from a central function in the correct order, in the same way as the Global Commit All function in the ENTERPRISE user interface.

The following table shows all available command parameters and values that apply to the Commit Network Elements command type:


FILTER The name of the filter from which to derive a subset of elements that will be committed. The name should be exactly the same as that displayed in ENTERPRISE.



Using the Auto Cu Generation Command in a Command File

The Auto Cu Generation command enables you to:

Automatically create Nominal Downlink Received Level (Cd) plots for 2g cells.

Automatically create Nominal Uplink Received Level (Cu) plots for 3g cells.

Export these plots to vector (MID/MIF) format.

You can use it to produce both active and provisional plots. The active plot will show all the cells in a live network for a specified unit region, whereas the provisional plot will show new cells planned to be activated within three months for a specified unit region.

Before entering command parameters and values, ensure you have included the command type COMMAND=AUTO_CU_GEN.

The following table shows all available command parameters and values that apply to the Auto Cu Generation command type:


UNITREGION The co-ordinates of the region to be considered in the order East Min, East Max, North Min, North Max.

RESOLUTION INMETERS

The required resolution of the coverage plot in meters.

VECTORFILE COORDINATESYS

The vector co-ordinate system to be used for mid/mif files.

ACTIVEFILTER You can specify only one filter here, which will contain all the active cells under one unit region.

ACTIVECu THRESHOLDSindBM

Produces a separate MID/MIF file for each specified threshold.

ACTIVEURN VECTORFILEDIR

Specifies the folder where details for the unitRegion will be stored. Appropriate sub folders will be generated.

Example.

If ACTIVEURNVECTORFILEDIR = C:\CUOUTPUTS\South East Region then:

for active umts cells with a threshold of -131.5 the subfolder will be C:\CUOUTPUTS\South East Region\ACTIVE\UMTS\carrier1\131.5DBM

for all active GSM900 and GSM1800 cells the subfolders will be C:\CUOUTPUTS\South East Region\ACTIVE\GSM\GSM900\131.5DBM and C:\CUOUTPUTS\South East Region\ACTIVE\GSM\GSM1800\131.5DBM

PROVISIONAL FILTER

You can specify only one filter here, which will contain all the provisional cells under one unit region.

PROVISIONAL CuTHRESHOLDSindBM

Produces a separate MID/MIF file for each specified threshold.

PROVISIONAL URNVECTOR FILEDIR

Specifies the folder where details for the unitRegion will be stored. Appropriate sub folders will be generated in the same way as for active plots described above.


This example shows an Auto Cu Generation Command file:

[EXECUTE]

1=North_Region_Cu_Generation

[North_Region_Cu_Generation]

COMMAND=AUTO_CU_GEN

UNITREGION = 550195 572566 5440785 5460166

RESOLUTIONINMETRES = 100

VECTORFILECORDINATESYS = ""UTM Zone 30, Northern Hemisphere

(WGS 84)\p32630", 8, 104, 7, -3, 0, 0.9996, 500000, 0"

ACTIVEFILTER = All

ACTIVECuTHRESHOLDSindBM = -70 -160 -135 -113.97

ACTIVEURNVECTORFILEDIR = C:\ENT5Release\inputfiles\Jersey

PROVISIONALFILTER= Profilter

PROVISIONALCuTHRESHOLDSindBM = -160 -70 -113.97

PROVISIONALURNVECTORFILEDR = C:\ENT5Release\inputfiles\Jersey

To avoid memory issues for big regions, the tool splits the whole region into small tiles. By default, the tool considers 20 tiles. However you can specify the number of tiles to be used via the registry. To do this:

1 Open Regedit.

2 Under HKEY_CURRENT_USER\Software\AIRCOM International\ENTERPRISE\Settings\All Servers\All Instances\All Projects\All Users create a new key called AutoOutputGen.

3 Create a new String Value called NumTiles for the AutoOutputGen key.

4 Modify the Numtiles String Value to specify the number of tiles you require.

5 Close Regedit.


Index

A

Auto CU Generation • 31

B

Batch files, running • 19

C

Command file creating • 15, 16, 17 format • 21 parameters • 22, 23, 28, 30 running • 18

Commander, about • 7

F

File formats command file • 21

L

Log Files viewing • 20

P

Parameters command file • 22, 23, 28, 30

R

Running command files • 18

S

Symbols used in Help/Guide • 8

commander user reference guide.pdf

Documents

command file

user assistance

reference guide edition

batch file

log file

command prompt

windows xp

windows vista