Amt .Net Userguide

8/11/2019 Amt .Net Userguide

1/58

Architecture Management Tool

AMT. NET

Alcatel File Reference Date Edition PageMobile Radio Division AMT .NET

UserGuide.docAMT .NET 2011-05-06 3.6 1/58

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.


AMT .NET

User Guide


2/58





TABLE OF CONTENT

1 INTRODUCTION ................................................................................................................................................ 4

2

TECHNICAL ISSUES ......................................................................................................................................... 4

3 INSTALLATION PROCESS ............................................................................................................................... 4

4 LICENSING ........................................................................................................................................................ 6

5 THE AMT .NET MENU ....................................................................................................................................... 6

5.1

AMT.NETSETTINGS .................................................................................................................................... 6

5.1.1 Database settings .................................................................................................................................... 6

5.1.2 Visual settings .......................................................................................................................................... 7

5.1.3

Runtime options ....................................................................................................................................... 8

5.1.4

Logging setting ........................................................................................................................................ 8

5.1.5 Import/Export settings .............................................................................................................................. 9

5.1.6 Advanced settings ................................................................................................................................. 10

5.1.7 Miscellaneous settings ........................................................................................................................... 10

5.2 AMT.NETPROJECTSANDVERSIONSMANAGEMENT ........................................................................... 11

5.2.1

Projects .................................................................................................................................................. 11

5.2.2 Versions ................................................................................................................................................. 12

5.3 AMT.NETNETWORKWINDOW ................................................................................................................. 13

5.3.1 The Network View .................................................................................................................................. 14

5.3.2 The Network Overview .......................................................................................................................... 14

5.3.3

The Elements View ................................................................................................................................ 14

5.3.4

The Hierarchy View ............................................................................................................................... 14

5.3.5

The PropertyView .................................................................................................................................. 15

5.3.6 The ErrorView ........................................................................................................................................ 15

6 WORKING WITH AMT .NET ........................................................................................................................... 15

6.1.1

Network Display Navigation ................................................................................................................... 15

6.1.2

Network Element Addition ..................................................................................................................... 15

6.1.3 Network Element Deletion ..................................................................................................................... 15

6.1.4 Network Element Selection .................................................................................................................... 16

6.1.5 Network Element Change ...................................................................................................................... 16

6.1.6 Network Element Search ....................................................................................................................... 16

6.1.7

Network Element Connection ................................................................................................................ 16

6.1.8

Applying layout ...................................................................................................................................... 17

6.1.9 Applying filters ....................................................................................................................................... 17

6.1.10 Checking errors ..................................................................................................................................... 18

6.1.11 Importing and exporting ......................................................................................................................... 18

6.1.12 Network elements automatic creation.................................................................................................... 21

6.1.13 AutoLink ................................................................................................................................................. 23

6.2 AUTO LINK REVIEW......................................................................................................................................... 26

6.3 REPORTING.................................................................................................................................................... 27

6.3.1

Graphical Reports .................................................................................................................................. 27

6.3.2

HW reports ............................................................................................................................................ 31

6.3.3 Network Element Report ........................................................................................................................ 31

6.3.4 Local Area Code report (LAC) ............................................................................................................... 32

6.3.5

Version Comparison Report .................................................................................................................. 32


3/58





7 DIMENSIONING METHODS ............................................................................................................................ 36

7.1

IMPORTINDICATORS ................................................................................................................................. 36

7.1.1 Import indicators from NPO ................................................................................................................... 36

7.1.2 Import indicators from AnaQoS ............................................................................................................. 45

7.2

INDICATORSINPUT .................................................................................................................................... 48

7.2.1

How to run a dimensioning method ....................................................................................................... 48

7.2.2 Dimensioning method pane ................................................................................................................... 51

7.3 MANUALINPUT ........................................................................................................................................... 54

7.3.1 How to run a dimensioning method ....................................................................................................... 54

7.3.2 Dimensioning method pane ................................................................................................................... 55

7.4 DIMENSIONINGMETHODSREPORTS ...................................................................................................... 57

7.5

BTS-SECTORDIMENSIONINGMETHODS ................................................................................................ 57

7.6

BTSDIMENSIONINGMETHODS ................................................................................................................ 57

7.7 BSCDIMENSIONINGMETHODS ................................................................................................................ 57

7.8 MXBSCDIMENSIONINGMETHODS ........................................................................................................... 58

7.9

GPU-GPBOARDDIMENSIONINGMETHODS ............................................................................................ 587.10

GBLINKDIMENSIONINGMETHODS ...................................................................................................... 58

7.11 NSVCDIMENSIONINGMETHODS .......................................................................................................... 58

7.12 SGSN-IP-ENDPOINTDIMENSIONINGMETHODS ................................................................................. 58

7.13 IPGBLINKDIMENSIONINGMETHODS ................................................................................................... 58


4/58





1 INTRODUCTION

The Architecture Management Tool (AMT .NET) is designed to help the radio network engineers in

analyzing and planning the radio networks (GSM, UMTS...). This tool is focused on checking architecture

and dimensioning according to the existing specifications.

AMT .NET can analyze an existing network, by importing the configuration from the OMC's, or assist you

in the process of designing a new network from architecture point of view. While working with AMT, you

always have the possibility of getting a look on "what if" situations. You could duplicate an existing

network topology and use AMT .NET to modify network architecture on the new created version of the

network. This will allow you to create comparisons between the two network versions and check each

version against the architecture and dimensioning rules.

This document explains the features of AMT .NET and how to use them.

Very important!

Please keep a link to the tools official website found athttp://gtp.tm.alcatel.ro/AMT.

This will help you keep up to date with the continuous evolution of this tool and in touch

with us. You will be able to find latest releases, corrections, updates and all other materials

and information needed to use this tool.

It is an important channel of communication that allows us to better support you.

2 TECHNICAL ISSUES

Supported network type:- AMT .NET is maintained to follow Alcatel-Lucent evolution. As such all type of networks are under the

scope of this tool. Please visit the website.

Software requirements:

- Microsof t Windows with latest updates (recommended: Microsoft Windows XP)

- Microso ft .NET Framework Runtim e3.5 or newer.All .NET programs require that the Microsoft .NET

Framework be installed. If you have previously installed this component either manually or from the

Windows Update site, you don't need to download this again.

- Microsof t Data Access Com ponents2.8. Provides support for connection to a variety of data sources.

If you have Windows XP or later installed, you do not need this component.

- Microsof t SQL Desktop EngineRelease A. is the data store used by AMT .NET.

You could also run AMT .NET on a machine, having a remote connection to another computer that

runs a MSDE or Microsoft SQL server. Remember that AMT .NET will not run without a connection

to a MSDE or Microsoft SQL server database.

We recommend installing MSDE local, on the machine that runs AMT .NET.

AMT .NET software:

- Is developed under Microsoft .NET Framework.

3 INSTALLATION PROCESS

Go tohttp://gtp.tm.alcatel.ro/Amt(the official website) and follow the steps below:
http://gtp.tm.alcatel.ro/AMThttp://gtp.tm.alcatel.ro/AMThttp://gtp.tm.alcatel.ro/AMThttp://gtp.tm.alcatel.ro/Amthttp://gtp.tm.alcatel.ro/Amthttp://gtp.tm.alcatel.ro/Amthttp://gtp.tm.alcatel.ro/Amthttp://gtp.tm.alcatel.ro/AMT


5/58





1. First make sure that your Windows operating system is up to date by visiting the Windows Update

website and getting all critical and recommended updates.

2. Create an empty folder

3. Download AMTNET_setup.exe in that folder

4. In the AMTNET_setup.exe folder, create a subfolder called "Common" and download all needed"Required components" there. (see below)

a. .NET Framework 3.5

Microsoft .NET Framework Runtime 3.5. All .NET programs require that the Microsoft .NET

Framework be installed. If you have previously installed this component either manually or from

the Windows Update site, you don't need to download this again. If you need to install .NET

Framework:

in common folder create a subfolder NET Framework 3.5

go tohttp://www.microsoft.com/downloads/details.aspx?FamilyID=333325fd-ae52-4e35-

b531-508d977d32a6&DisplayLang=en

go to Full Redistributable Package and follow the.NET Framework 3.5 full packagelink to

download the dotnetfx35.exe in your local NET Framework 3.5 subfolder

b. MDAC 2.8 Microsoft Data Access Components 2.8 or later.

Provides support for connection to a variety of data sources. If you have Windows XP or

later installed, you don't need this component. If you need to install MDAC:

create a subfolder MDAC 2.8 in common folder

download MDAC_TYP.exe from

http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-

185d0506396c&displaylang=enin your local MDAC 2.8 subfolder

c. MSDE 2000

Microsoft SQL Desktop Engine Release A. is the data store used by AMT .NET. If you

have another MSDE or SQL Server engines in your network and you have permission to use

them, you don't need this component. If you need to install MSDE 2000:

create a subfolder MSDE 2000 in common folder

download MSDE 2000 Release A from

http://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-

E4B278EB9147,unpack in your local MSDE 2000 subfolder

5. Run AMTNET_setup.exe

You must agree with the terms from the License Agreement by checking the box

Set the destination folder

Recommended being empty because when uninstalling the whole folder is

removed.

It is not allowed to install different versions in the same folder

If you already have installed a AMT .NET version it is not allowed to install the

same version in different folder. You can overwrite the files in existent folder

preserving license or uninstall existent version.

Select components

Components read only are required and are checked or not checked depending

on your computer

Click install
http://www.microsoft.com/downloads/details.aspx?FamilyID=333325fd-ae52-4e35-b531-508d977d32a6&DisplayLang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=333325fd-ae52-4e35-b531-508d977d32a6&DisplayLang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=333325fd-ae52-4e35-b531-508d977d32a6&DisplayLang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=333325fd-ae52-4e35-b531-508d977d32a6&DisplayLang=enhttp://download.microsoft.com/download/6/0/f/60fc5854-3cb8-4892-b6db-bd4f42510f28/dotnetfx35.exehttp://download.microsoft.com/download/6/0/f/60fc5854-3cb8-4892-b6db-bd4f42510f28/dotnetfx35.exehttp://download.microsoft.com/download/6/0/f/60fc5854-3cb8-4892-b6db-bd4f42510f28/dotnetfx35.exehttp://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-E4B278EB9147http://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-E4B278EB9147http://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-E4B278EB9147http://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-E4B278EB9147http://www.microsoft.com/downloads/details.aspx?FamilyId=413744D1-A0BC-479F-BAFA-E4B278EB9147http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=enhttp://download.microsoft.com/download/6/0/f/60fc5854-3cb8-4892-b6db-bd4f42510f28/dotnetfx35.exehttp://www.microsoft.com/downloads/details.aspx?FamilyID=333325fd-ae52-4e35-b531-508d977d32a6&DisplayLang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=333325fd-ae52-4e35-b531-508d977d32a6&DisplayLang=en


6/58





6. Upon first launch of AMT.NET, you will be required to register AMT .NET.

4 LICENSING

In order to restrict the usage of the tool, we have implemented a licensing mechanism. Licenses are

granted to Alcatel-Lucent employees that have a real need to use AMT .NET, on a time-limited manner.

Licenses can be renewed anytime provided the user has valid ALCANET credentials (CIL + CIP).

Please be aware that licenses are bound to the machine AMT .NET was first installed on. If the machine

changes, the authentication will have to be repeated, in order to obtain a new license.

DO NOT try to set the computer clock back in time or otherwise tamper with the license as this may

render your AMT .NET license invalid.

5 THE AMT .NET MENU

After you completed the registration process, when launch AMT .NET, the main menu window will

appear:

If this is f irst time when you work with AMT .NET then it is necessary to setup the tool according with your

local environment. For doing that there is a menu button called Sett ings.

5.1 AMT .NET SETTINGS

5.1.1 Database settings

The most important setting option is to setup the database path. As already mentioned AMT .NET will not

work without a database connection.

If you have installed a local SQL server (MSDE) leave the option unchanged, if not specify the server

name and server connection mode.

If you have installed SQL Server Express, the named instance must be specified in the Database

Host. If you havent changed the defaultinstance name ( SQLExpress), the Database Host must

be set to ( local)\sqlexpress


7/58





5.1.2 Visual settings

In this section is possible to modify some graphic parameters for network view like grid type, appearance,

tree layout and go layout values.


8/58





We recommend the default settings (specially the Appearance section), since adding more visual

effects can significantly slow down AMT .NET.

5.1.3 Runtime options

Available options:

Template checking

Rule checkingvalidate real time rule checking for network

Logging of network operationsin AMT .NET log save all actions made on network

Automatic refreshing of computed properties by checking this option validate refreshing of

computed properties to be made each time a network element is changed.

Enable Undoif this option is enable the system will keep in memory the user actions made on

the network, depending on the level size.

5.1.4 Logging setting

Allow setting the events that you want to be logged.


9/58





This setting is mainly for debugging purposes.

5.1.5 Import/Export settings

You can select to import/export or not the computed properties.

Set the field separator used in the import/export files and the extension of the import/export files.

Also you have options to instruct AMT .NET what to do if empty fields are found in the import files, or fi

the value in the import files does not match the type of expected property (ex. abc where a percentage

is expected).


10/58





5.1.6 Advanced settings

Keeping intermediate tables at import time is used for debugging. To get access to these tables you need

to know and be able to work with the database system behind.

We recommend leaving this option unchecked.

Set the cache size bigger than 10 if you have a machine with enough memory. This will increase the

processing speed.

The speed acceleration setting will significantly increase the speed of AMT .NET at the expense of

memory (RAM).

We recommend using some acceleration (normal), but do not select the high option unless you

have a lot of memory. The high selectionwill keep the whole network in memory (RAM).

5.1.7 Miscellaneous settings


11/58





Some miscellaneous settings:

Settings for the Network Element report

o Choose to show the parent hierarchy or not

If you choose to show the parent hierarchy in the Network Element List reports, then for

each network element you will see the parents chain of network elements to which this

element is connected to.

You may see sometimes the same network element more than once. This is due to thefact that one network element may have more then one chain of parents.

5.2 AMT .NET PROJECTS AND VERSIONS MANAGEMENT

5.2.1 Projects

AMT .NET can work with one single project at a given time. Each project is based on a provided network

template. In the project window you can create, delete, import orexportprojects. In this window you have

also information available, related to template and versions of the selected project.


12/58





If you want to create a new project press New... button. A new window appears:

When you create a new project you must provide the name of the project, description, author and

template.

5.2.2 Versions

Working with versions is one of the particular features of AMT .NET.

A project can contain one or more versions. After a project is opened, the version window will pop up

automatically.


13/58





It is possible to create new versions, delete, duplicate or close old ones.

We recommend using at least two versions. One that will show the initial state of the network, and

one that will correspond to the final status.

You can also use versions to create back-ups before modifying the network.

5.3 AMT .NET NETWORK WINDOW

After selecting a given version, the Network Window will appear. The components of the Network

Window are described in the image below:

TheNetworkView

TheHierach View

ThePropertyView

NEShapeNetwork

Overview

TheErrorView


14/58





5.3.1 The Network View

Description:

The NetworkView represents the central view of the network. It is used to display a graphical

representation (the graph) of the network being edited. Each network element (NE) type (BTS, BSC) has an associated shape, and connections between

NEs are represented using arrows.

Each NE shape can be selected, mover or deleted individually or as part of a selection group. When a

shape is moved or deleted, its associated connections are also moved or deleted.

The displayed network can be automatically layout on the NetworkView, which is useful when a

network is loaded for the first time.

The default layout applied can be set in the Settings menu.

A set of network operations can be performed directly from this view, including selecting, adding,

deleting or layout NEs or groups of NEs. These operations are available via keyboard or mouse commands

or as options from the associated contextual menu.

5.3.2 The Network Overview

Description:

The Overviewis used to display a bird-eye view of the network.

It is synchronized to the NetworkView so that any changes performed in the NetworkView are

immediately visible inside the Overview.

The Overview is used only to give the user a general view of the network. Thus, the only supported

operation is the positioning on a certain location of the network.

5.3.3 The Elements View

Description:

The Elements View displays a tree containing all the NEs in the network, grouped by NE type

(category).

Like the Elements View it supports all basic operations like NE selection (only single selection is

supported), addition and removal. These operations are also available from the associated contextual

menu.

It provides a search mechanism to quickly locate (search) a NE by its label and type inside the network.

The first NE matching the search criteria will become selected and visible in the view. If you press again

search (or ENTER Key) it will locate the next matching NE.

5.3.4 The Hierarchy View

Description:

The Hierarchy Viewdisplays a tree containing all the NEs in the network, showing the links between

them (the NEs that are connectedto a certain NE will be displayed in a sub-tree of the NE).

Here you can select what NEs to view in the NetworkView. All checked NEs will be visible in the

NetworkView.

Please note:

When selecting/unselecting (checking the box) of a NE, all the sub-structure will be

automatically selected/unselected.

When selecting/unselecting a NE, all other NEs that do not belong to the current sub-structure

(are not linked to the clicked NE) will be unselected.


15/58





You can select multiple branches by holding down the CTRL key while selecting/unselecting.

Holding down CTRL will leave the other sub-structures unmodified.

Like the NetworkView it supports all basic operations like NE selection (only single selection is

supported), addition and removal. These operations are also available from the associated contextualmenu.

5.3.5 The PropertyView

Description:

The PropertyViewis used to display and change the properties associated with a single (selected) NE.

NE properties are grouped in three categories: general propert ies, which are available for all NEs,

speci f ic proper t ies, which are specific to the given NE type and comp uted proper t ies, the properties

which are computed at runtime, depending of the network status (links and property values).

5.3.6 The ErrorView

This view will show errors in realtime. If real-time checking is on, and a (dimensioning) rule is broken,then you will see the errors in this list.

If no NE is selected, then you will see all the errors from all NEs in the network (visible or not).

If you select one NE, then the ErrorViewwill show only the errors belonging to that particular NE.

If you select one error in the list of errors provided by the ErrorView, then the corresponding NE will be

selected.

6 WORKING WITH AMT .NET

Launch the AMT .NET application and open an existing project and one of its versions.

6.1.1 Network Display Navigation

Steps:

Ensure that the Overviewis visible, by left clicking on the Overviewtab in the views docking area. The

overview should display a thumbnail view of the network displayed in detail by the NetworkView.

Clicking inside the Overviewwill center the NetworkViewon the same location as the overview.

Move a NE inside the NetworkView. The image shown in the Overview is change accordingly. The

Overviewis synchronized to the NetworkViewin terms of displayed data.

6.1.2 Network Element Addition

Steps:

Click on an empty area of the NetworkViewor the Hierarchy Viewto move the focus to one of theseviews.

Right-click on the view and select Create NEfrom the context menu or press the Insert key to show

the Add Network Elementdialog window.

Select the NE type and optionally enter the NE label, then press OK.

The new NE will appear in the views.

6.1.3 Network Element Deletion

Steps:

Select one or more NEs in the NetworkViewor Hierarchy View.


16/58





Right-click on the view and select Delete NE(s)from the contextual menu or press the Deletekey to

delete selected NE or select Delete NE(s) with children from contextual menu to delete selected NE

and all children elements connected to it.

The selected NEs disappears from all the views.

The connections for the deleted NEs should be removed from the views. The PropertyViewshould be empty (no NEs selected).

6.1.4 Network Element Selection

Steps:

Left-click on a NE representation in the NetworkViewor Hierarchy Viewto select that NE.

In the NetworkView you can CTRL-click several NEs to expand the selection.

The selected NE properties should appear in the PropertyView(if there is just one NE selected).

6.1.5 Network Element Change

Steps:

Left-click on a NE representation in the NetworkView or Hierarchy View to select that NE. The

properties of that NE should appear in the PropertyView.

If there is more than one NE, then the PropertyView will be empty.

Modify editable properties of the NE using the PropertyView.

You cannot change properties of several NEs at once, even if the NEs are the same type.

You can use Massive Import for a similar functionality.

6.1.6 Network Element Search

Steps: In the Elements View, choose a NE type in the Typecombo box located in the Network Element

Searchsection.

Type the first letters of the NE name to search for, inside the Nameedit box.

Press Enter or click the Searchbutton to search for the desired NE.

The type combo box should display all the NE types (templates) currently available in the network.

The first NE that matches the search criteria should become selected in the Hierarchy View(if visible)

and in the NetworkView. Its properties should be displayed inside the PropertyView.

If no such NE exists, a message should appear notifying the user that no NE matching the search

criteria was found.

When the search found several NEs and has finished searching, a message will notify you that other

elements where not found. If you continue to search the search will start again from the beginning.

6.1.7 Network Element Connection

Steps:

Hold the mouse on the edge of the shape from which to start the connection until a hand mouse pointer

appears

Click the left mouse button and hold to start making the connection. Now, when the mouse is moved, a

dashed line originating from the starting NE should follow the cursor.

Left-click on the shape of the connections terminating NE to mark the ending point of the connection.

The new connection should appear in the form of an arrow originating from the starting NE shape and

pointing to the terminating NE shape.


17/58





Please no te thattheconnection does not depend on the direction. For example, NE A is

connectable to NE B and also B is connectable to A. So it matters which is the first (originating) NE

and the last (terminating) NE only when the Template of both elements is the same.

If a connection is duplicated or the two NEs cannot be connected, a message box describing the nature

of the error should appear.

6.1.8 Applying layout

Steps:

Right-click on the NetworkViewto display the contextual menu and choose Auto Layoutand select

one layout type.

Available layouts: tree.

Example of tree layout.

To ensure that all changes were properly saved, please close the currently opened AMT .NET project and

then reopen it again. The network should be in the same state as it was when the project was last closed.

6.1.9 Applying filters

From main menu go on Filter and select a filter if available. Filters allow seeing a more simplify view for

a network. Note that if a filter is selected this will be apply in all views.


18/58





The fact that some NEs will not be seen (filtered out) when a certain filter is applied, does not

mean that the other NEs do not exist,not taken into account or that you can connect NEs

available in the filter that you could not before.

6.1.10 Checking errors

From main menu go on Version -> Checking...and rules window is popped up:

Before starting a checking campaign it is necessary to reset checking engine. This will clear the checking

window. Select rules that you want to check and start a campaign. If during this some rules are going to

generate errors, they will be displayed in the errors list below. Each error will provide you a message associatedwith it.

Also there is a real time checking option available. You can enable or disable it. When real time checking is

enabled the entire network is checked and if some errors are generated from braking rules, these errors will be

displayed in the error view.

6.1.11 Importing and exporting

1. GSM ACIE fi les imp ort

It allows importing ACIE CSV (EML and RNL) files received from GSM OMC-R. At import

time the user is asked to select the Network version (B7, B8, B9).


19/58





The OMC ACIE files must be obtained (and preprocessed) via a special OMC Script, available on

the website.The complete path of the folder where the import files reside must be specified as seen in the

figure above. The folder specified contains separate folders for each BSC and for each MFS, and there

are some common files.

An example of how the files and subfolders look like:

BSS folders contain subfolders named:

ACIE_BSSnexport_DirmACIE_MFSnexport_Dirmn = 1, 2,

m = 10,1

The folder "ACIE_BSSnexport_Dirm" contains:Alcatel2MbTTP.csv,

AlcatelAbisChainRing.csv,

AlcatelAbisChainRingCoordinator.csv,

AlcatelBasebandTransceiver.csv,

AlcatelBsc.csv,

AlcatelBssFunction.csv,

AlcatelBts_Sector.csv,

AlcatelBtsSiteManager.csv,

AlcatelCircuitPack.csv,

AlcatelConnectionR1.csv,

AlcatelFunction.csv,

AlcatelLapdLink.csv,

AlcatelManagedElement.csv,

AlcatelManagedElementComplex.csv,

AlcatelOperatingSoftwareUnit.csv,

AlcatelRadioCarrier.csv,

AlcatelReplaceableSoftwareUnit.csv,

AlcatelSignLinkN7.csv,

AlcatelSignLinkSetTp.csv,

AlcatelX25Coordinator.csv,

AlcatelX25Link.csv,

EquipmentHolder.csv,

ExecutableSoftwareUnit.csv,


20/58





MtpSignPoint.csv

The folder ACIE_MFSnexport_Dirm contains:

AGprs2MbTTP.csvAGprsBearerChannel.csv

AGprsNse.csv

AGprsNsvc.csv

AGprsPvc.csv

NetworkElement.csv

The Common files in the specified import folder are :

Adjacency.csv

Adjacency2gTo3g.csv

Cell.csv

ExternalOmc3gCell.csv

ExternalOmcCell.csv

HoControl.csv

RnlAlcatelBSC.csv

RnlAlcatelMFS.csv

RnlAlcatelSector.csv

RnlAlcatelSiteManager.csv

RnlBasebandTransceiver.csv

RnlFrequencyHoppingSystem.csv

RnlPowerControl.csv

SubNetwork.csv

If the user does not want to import all the files from the specified folder, the unwanted BSS foldercan be deleted.

2. UMTS XML

It allows importing xml files (topology and transport) received from UMTS OMC release R4.

At import time the user is asked to select the folder where the files reside.

3. Massive imp ort and export


21/58





Massive import and export is a special type of import/export operation. There is a file for each

network element type and a links file that defines how network elements are connected. Each

file has a list of parameters separated by semi-column ;. On the first line there is a file

description (NE type, project name, version name, related template description, template ID,

template version, etc), in the second line we have NE properties name and on next linesfollow NE properties values. Then there is a line for each NE (of the type corresponding to

that file).

To obtain a set of empty import files create an empty version and export it. The files created

contain on the first line the file description and in the second line the properties name.

The properties (CSV columns) named ID and Label are mandatory. ID will identify uniquely the

NE in this version. Label is the display name that you see in the various AMT .NET views.

Please no te thatLabelis a virtual property, it actually is pointing to a certain other property (for

example for the NE type BTS the Label property takes its value from the UserLabel property).

As such, please take care that these properties have the same value in the Massive CSV files.

Otherwise, at import time, the value for the two properties is unpredictable.

It can be used to define a network from scratch in (e.g.) Excel, to export it in CSV format

described above, according to network template, and to import this network in AMT .NET to

make architecture simulations.

Also it is possible to import first a network from the OMC as described in the previous chapter

(for example from GSM or UMTS specific files), and then to perform a massive export of this

network in massive format. Loading those NE files in Excel allow to update some

parameters values and to re-import network back in AMT .NET. This is very useful when one

wants to change massively some network parameters values.

Since all the projects are stored internally by AMT .NET in the database, the Massive

import/export will allow you to move one project from one place to another one, or to archive

a project or version.

6.1.12 Network elements automatic creation

This functionality will give the possibility to create all children for a given network elements based on a

network element configuration defined in network template.

To access automatic creation window go on menu Tools->Auto-Creation.


22/58





You can start auto creation process in 2 ways:

Manual, by choosing the configuration to be created for selected NEs, from Available

Configurations list. User my chose to override or not root NEs properties with the values defined in

configuration by checking or un-checking the option Override root properties values. Also if in

selected configuration there is also a sub-network defined user my chose to not create the sub-network

and only to apply the values for properties defined in configuration by un-checking the option Create

sub-network. Another option is to specify the last level to be created for selected configuration. For

example if for a BSCthere is a configuration declared down to AbisTSUportlevel and we want to create

just the AbisTSU level then select the level name Level list. If no level is selected or is selected a

wrong one then the entire sub-network is created.

Automatic, by selecting the option Use AutomaticConfiguration property. In this casethe configuration will be tacked from property AutomaticConfiguration. This property is a string

property and may be filled either with a configuration name declared for this NE type, either with a string

that contains configurations declared at children NE level. In the second case the string must have a

specific syntax:

down {List_of_configurations}Where:

List_of_configurations = {Down_config_1}, {Down_config_2}, {Down_config_n}

Where:


23/58





Down_config_n = {down NE template name}, {number of elements to create}, {aconfiguration name declared for this down NE}

Example:

Directly specifying the configuration for root NEs:

AutomaticConfiguration = BSC conf3 in case of a BSC NE.

By specifying down connectable NEs configurations:

AutomaticConfiguration = down {{{BTS_Sector}, {1}, {BTS_Sector_with_1TRX}},

{{BTS_Sector}, {2}, {BTS_Sector_with_6TRX}}}in case of a BTS NE.

In this example we will have 1 sector in configuration BTS_Sector_with_1TRX and 2

sectors in configuration BTS_Sector_with_6TRX, linked from my root BTS.

6.1.13 AutoLink

Is a feature used to link free BTS/Abis, or re-link them (unlink and link again) to a chosen BSC. The goal

of the Autolink feature is to evenly spread the load of BTSs to the BSC, trying to link as many BTS / Abis

as possible while respecting all dimensioning rules.


24/58





Manual selection:

You have 2 lists, one with BSC elements and one with BTS and Abis elements.From the first list you can select only one BSC, from the second list you can select one or more elements.

If you have some network elements selected before launching auto link those elements will appear

selected in that lists.

Link Options:

Allow multidrop creationpermits Autolink to create chains of BTSs.

- Individual BTS onlylinks only BTS to BTS, not Abiss to already linked BTSs.

- BTS and Abiswill treat Abiss as entities, and link them(all subsequent BTSs)to create multidrops.


25/58





Force to link all elements ignores dimensioning rules. It will continue to link NEs even if rules are being

broken.

Multidrop:

- Link to existing multidropswill allow linking to existing multidrops in the selected BSC- Link to free AbisTSUport onlywill only link to a TSU port if this port is free (no other NE) is linked

there when starting the autolinking.

Selection from file:

Click Load file button and load csv file.

BSC elements will appear in the left list.

If you click on one BSC, the BTSes and Abises that will be linked to that BSC will appear in the right list.

You can edit link options for each BSC or for all BSC (Apply options to all).

If there are elements with the same name (Example: NoLabel (BTS)), all elements with that name will

appear in the lists.

Select from the left list those elements that you want to run auto link algorithm and click Link.

Auto link gives a review after linking is finished.

CSV file:

Label1;Label2 - lines

Label1the value of the property that is defined as Label to BSC elements

Label2the value of the property that is defined as Label to BTS and Abis elements

In the next example Label is UserLabel property.

Example of csv file:

bsc;bts_ad

bsc;bts_df

bsc;NoLabel

bsc;Abis NoLabel

bsc1;1

bsc1;2

bsc1;tyty

bsc2;tyty23

bsc2;abis_ab

bsc2;abts


26/58





6.2 AUTO LINK REVIEW

In the end of the algorithm, Auto Link gives a review that contains for each BSC, elements that are linked

and that are not linked.

There is also a check box named Delete unused Abises.If this is checked then Auto Link will delete all unused and unlinked Abis s that have been created by

Autolink.


27/58





After you click ok the version is reopened.

6.3 REPORTING

To access the reports menu select Reports.

6.3.1 Graphical Reports

These reports are specialized reports. BSC, MFS, TCU and BTS reports are currently available.

a) BSC report

When BSC report is selected, a window will show you all available BSCsand MxBSCsfrom the network

(selected version). After selecting one or several elements, press ok.


28/58





In the resulting Excel file, a new sheet is created for each element. For BSC, the report will draw all

TSU->PCM ports related to the selected element and BTSs connected at those ports. For MxBSC, the

report will draw all LIU->PCM ports related to the selected element and BTSs connected at those ports.

In the next picture is shown a sample of such an Excel based BSC report.


29/58





b) MFS report

When MFS report is selected, a window will show you all available MFSs from the network. After

selecting one or several elements, the MFS report will show the relation between MFS, GPU/GP,

AterMux and BSC.

c) TCU report

TCU report is available only for B10 and B11 releases. The TCU report extracts at BSC level the number

of TCU used and the LAPD load on each TCU.


30/58





d) BTS report

BTS report is available only for B10 and B11 releases. When BTS report is selected, a window will show

you all available BSCsand MxBSCsfrom the network. After selecting one element, a list of all BTSs

connected to that BSC (or MxBSC) is shown. After selecting one or several BTSs, press ok.

In the resulting Excel file, a new sheet is created for each element. Besides the BTS general information,

the report shows the HW TRE related to the selected BTS and for each HW TRE the hosted TRXs are

displayed. The report also shows the BTS_Sectors connected to the selected BTS.


31/58





6.3.2 HW reports

These reports display the hardware properties of network elements. BTS, BSC and MFS HW reports are

currently available and can be generated only for B10 and B11 releases.

The hardware report can be exported in a .csv file.

6.3.3 Network Element Report

The user can choose the template for which to display the network elements.

All the elements for the chosen template will appear with their corresponding properties.

It is possible to export the elements in a .csv file.

In the settings part it is possible to choose to display or not the parent hierarchy for the elements.


32/58





6.3.4 Local Area Code report (LAC)

This report is available only for GSM networks. The following fields are displayed in the report:

LAC - Local Area Code of the cell

Number of cellsin that LAC

Number of cells per BSC

Related BSC

6.3.5 Version Comparison Report

There are two types of version comparison reports.

- Hierarchy Changes Report

- Property Changes Report


33/58





Select the versions that you want to compare, the network elements types to be shown in reports and

select the type of the reports you want to create.

Select one version from Compare version list and one or more versions from with list.

Click Create reports.

Hierarchy Changes Report

Compare two or more versionshierarchy comparison

There is a comments column for each version that indicates the place where the modifications were

made in that version (the template and the name for that element which is different in hierarchy path).

If there is a new element in that version in the comments column appears added.

If there is an element that was removed in the comments column appears removed.


34/58





Property Changes Report

Compare two or more versionsproperty comparison.

This report compares network elements after properties.

There are two types:

Row report

Column report


35/58





The version selected in compare version (in the previous example: v1) is the reference version.

All elements from the reference version, which have one or more modified properties in other

version, appear in the reports.

Property Changes ReportRow report

The versions that have network elements with modified properties are displayed on rows one

below the other. The row with the reference version is marked.

The fields with differences are marked with orange color.

Property Changes ReportColumn report

The versions that have network elements with modified properties are displayed on the same row.

The fields with differences are marked with orange color.


36/58





7 DIMENSIONING METHODS

The dimensioning module is designed to help the network engineers in monitoring the radio networks

under the B10 and B11 Release.

There are two approaches for running the dimensioning methods:

Using indicators imported from either NPO or AnaQoS

Using manual input

7.1 IMPORT INDICATORS

In order to run the dimensioning methods, you must first import all the indicators needed for the network

elements. These indicators are defined in the related network template.

7.1.1 Import indicators from NPO

In order to run all the dimensioning methods defined inside AMT .NET you have to export reports from

NPO at:

CELL2G level (has three group of indicators - favourites)

BSC level

GPU level

PVC level

SGSN_IP_NSVC level

MSC level (only for B11 release)

Inside of AMT .NET these indicators will be imported at:

BTS_Sector (Cell) level

BTS (indicators are consolidated from BTS_Sector) level

BSC level (include also indicators consolidated from MSC in B11 networks)

MxBSC level (include also indicators consolidated from MSC in B11 networks)GPU_GP board level (include also indicators consolidated from NSVC and SgsnIpEndPoint)

NSVC level

GbLink (indicators are consolidated from NSVC) level

SgsnIpEndPoint level

IPGBLink (indicators are consolidated from SgsnIpEndPoint) level

MSC level (only for B11 release)

Prerequisites

In order to import Favourites inside NPO, first you have to down load them from AMT .NET web

site (http://gtp.tm.alcatel.ro/amt).In NPO, CELL must have next format: *** (LAC / CI) (e.g. cell04457_44507 (4457/44507))

In NPO, BSC must have next format: BSC Name (e.g. BA12BSC)

In NPO, GPU must have next format: OMC Hostname/BSS/FABRIC (e.g. omcrx02/2/16778752)

In NPO, PVC must have next format: OMC Name/MFS ID/TP/BEARER/PVC (e.g.

omcrx02/523/16778752/31/16)

In NPO, SGSN_IP_NSVC has two different formats depending on the value of

RelatedGbConfigurationType (static or dynamic)

In NPO, MSC must have next format: MSC_MSC Name-BSC Name (e.g. MSC_MSC_1-s307)

In some cases, the network elements are identified in NPO based on their friendly names. In this

situation, the friendly names file is imported in AMT .NET together with ACIE files.
http://gtp.tm.alcatel.ro/amthttp://gtp.tm.alcatel.ro/amthttp://gtp.tm.alcatel.ro/amthttp://gtp.tm.alcatel.ro/amt


37/58





However, there may be special cases when neither the NPO format nor friendly names match the

data from ACIE files. In these situations, you have to manually update the Friendly Name property

of each network element in AMT .NET and then import the indicators.

How to export indicators from NPO

Steps:

First of all you must import the Favorites into NPO. Launch NPO and go to Data ->Favorites ->

Organize.

In the new opened window, press the Import button and select the Favorites files that can be

downloaded from the official AMT .NET website (http://gtp.tm.alcatel.ro/Amt). After importing, the files will

be grouped by type, as shown in the picture below:
http://gtp.tm.alcatel.ro/Amthttp://gtp.tm.alcatel.ro/Amthttp://gtp.tm.alcatel.ro/Amthttp://gtp.tm.alcatel.ro/Amt


38/58





After saving the Favorites, you must export from NPO all the indicators contained in those files.

In the left tab of the pane select the desired network elements (Cells, BTS, ...). For the chosen

network elements, select the indicators using Favorites (In the right section of the pane select

the Indicator tab, right click on the pane and choose Favorites). For each category of

Favorites you must select the Whole Group of indicators.


39/58





Drag and drop the selected indicators in Reports tab.

In the Execution Contextwindow that appears, set the Periodicityto Hour and select the

export date. We recommend to select a period of one week.


40/58





After pressing the Execute button,all the indicators for the selected network elements will be

displayed in the Reportspane.


41/58





From the top right corner of the tab, click the Export Report button and savethe report in csv

format.


42/58





All the exported csv files must be placed in the same folder.

Import indicators in AMT .NET

In AMT .NET go to Version->Import->Indicators->NPO. In the new opened window select the folder

where the indicators exported from NPO reside. You must also select the date format corresponding to

the format chosen in NPO.


43/58





Before the import, you must verify that all the indicators needed for the network elements are available in

the chosen folder and there are no duplicate indicators in the files. Press the Check Importbutton inorder to verify the import consistency.

There are three possible situations:

If the consistency is checked successfully, you can start the import by pressing the Import

button.

The list of network elements for which indicators have been imported is displayed in the window.


44/58





If there are indicators missing from the import files, the list of these indicators and the associated

network elements types is displayed in the window. Import cannot continue until the consistency

is checked successfully.

If there are indicators that appear more than once in the import files, the list of these indicators

and the associated network elements types is displayed in the window. Import cannot continue

until the consistency is checked successfully.


45/58





7.1.2 Import indicators from AnaQoS

In order to run all the dimensioning methods defined inside AMT .NET you have to export reports from

AnaQoS at:

CELL level

BSC level

GPU level

PVC level

SGSN_IP_ENDPOINT levelInside of AMT .NET these indicators will be imported at:

BTS_Sector (Cell) level

BTS (indicators are consolidated from BTS_Sector) level

BSC level

MxBSC level

GPU_GP board level (include also indicators consolidated from NSVC)

NSVC level

GbLink (indicators are consolidated from NSVC) level

SgsnIpEndPoint level

IPGBLink (indicators are consolidated from SgsnIpEndPoint) level

Prerequisites

In AnaQoS, CELL must have next format: LAC / CI (e.g. 4457/44507)

In AnaQoS, BSC must have next format: BSC ID / BSC Name (e.g. 1/BA12BSC)

In AnaQoS, GPU must have next format: MFS ID / BSS ID / BSS Name / FABRIC (e.g.

523/2/omcrx02/16778752)

In AnaQoS, PVC must have next format: MFS ID / TP / BEARER / PVC ID (e.g.

523/16778752/10/16)

In AnaQoS, SGSN_IP_ENDPOINT must have next format: MFS ID / BSS ID / GPU FABRIC / IP

Address Decimal/ SGSN_IP_ENDPOINT ID (e.g. 523/4/16779520/2887517452/1)


46/58





How to export indicators from AnaQoS

Steps:

Launch AnaQoS and go to Data ->Export.

Select successively the network element types that you want to import in AMT .NET (CELL, BSC,

GPU, PVC, SGSN_IP_ENDPOINT).

In the window opened for the selected network element type, choose the folder path where the

file containing indicators data will be exported. Select also the start and the end dates of the

export time interval.

Place all the exported XML files in the same folder.

Import indicators in AMT .NET

In AMT .NET go to Version->Import->Indicators->AnaQoS. In the new opened window select the folder

where the indicators exported from AnaQoS reside.


47/58





Before the import, you must verify that all the indicators needed for the network elements are available in

the chosen folder and there are no duplicate indicators in the files. Press the Check Importbutton in

order to verify the import consistency.

There are three possible situations:

If the consistency is checked successfully, you can start the import by pressing the Import

button.

The list of network elements for which indicators have been imported is displayed in the window.


48/58





If there are indicators missing from the import files, the list of these indicators is displayed in a

window similar to the one presented in the case of importing from NPO. Import cannot continue

until the consistency is checked successfully.

If there are indicators that appear more than once in the import files, the list of these indicators is

displayed in a window similar to the one presented in the case of importing from NPO. Import

cannot continue until the consistency is checked successfully.

7.2 INDICATORS INPUT

7.2.1 How to run a dimensioning method

In the Network View (Hierarchy View and Elements View) the network elements that have imported

indicators are colored in blue.


49/58





Right click on the network element that you want to run a dimensioning method for and select

Dimensioning Methodsfrom the context menu.


50/58





In the new opened window choose Indicator input type. The list of dimensioning methods that have

imported indicators is displayed. Select the dimensioning method that you want to run and press OK.


51/58





7.2.2 Dimensioning method pane

For each selected dimensioning method associated with a desired network element, a new tab is created

in the main window. The pane is separated in three parts:

Traffic analysis pane User input pane

Dimensioning method results

You can resize the three panes by moving the separation bars with the mouse.The selected tab can be closed by pressing the button from the top-right corner of the pane.

Traffic analysis pane

The traffic analysis pane allows you to view the indicators graphs for the selected network element. Checkthe indicators that you want to display curves for. Different scales are available to display graphs accordingto a specific measurement unit.

Traffic analysis pane

User input paneDimensioning method

results

The selected

dimensioningmethod Close button


52/58





By right-clicking the graph, you launch a context menu that allows you to: Copy the graph as an image Save the graph as an image Print the graph Show point values Un-zoom Undo All Zoom/Pan Set Scale to Default

The Busy Hourtab from the right side of the pane displays the busy hour indicators values used in the

dimensioning method algorithm:

Scale

Busy Hour


53/58





User input pane

The user input pane provides the fields that must be completed with values in order to run the dimensioningmethod. After loading, the pane displays the default values for each variable. You can change theparameters values and make various simulations.

The data container can be collapsed / expanded as necessary by pressing the button from the top-rightcorner of the pane.

Dimensioning method pane

This pane displays the results of the formulas involved in the selected dimensioning method.

In order to perform the dimensioning method, you must click the Runbutton from the top-left corner of

the main pane.The data container can be collapsed / expanded as necessary by pressing the button from the top-rightcorner of the pane.

Collapse /

expand button


54/58





7.3 MANUAL INPUT

7.3.1 How to run a dimensioning method

In the Network View (Hierarchy View or Elements View), right click on the network element that you want

to run a dimensioning method for and select Dimensioning Methods from the context menu. The

selected network element can have imported indicators, but this is not necessary.

Collapse /

expand button


55/58





In the new opened window choose Manual input type. The list of dimensioning methods is displayed.

Select the dimensioning method that you want to run and press OK.

7.3.2 Dimensioning method pane

For each selected dimensioning method associated with a desired network element, a new tab is created

in the main window. The pane is separated in three parts:

Indicators pane

User input pane

Dimensioning method results

You can resize the three panes by moving the separation bars with the mouse.The selected tab can be closed by pressing the button from the top-right corner of the pane.


56/58





Indicators pane

The indicators pane allows you to manually introduce values for the indicators needed to run the selecteddimensioning method. If there are imported indicators for the chosen network element, the default indicatorsvalues are equal with the busy hour values.

User input pane

The user input pane provides the fields that must be completed with values in order to run the dimensioningmethod. This pane is similar to the one presented in case of importing indicators. However, it could provideadditional fields in case of dimensioning methods whose results depend upon other dimensioning methods.

Dimensioning method pane

This pane displays the results of the formulas involved in the selected dimensioning method. This pane is

similar to the one presented in case of importing indicators.

In order to perform the dimensioning method, you must click the Run button from the top-left corner of

the main pane.

Indicators pane

User input pane Dimensioning method

results

The selected

dimensioningmethod

Close button


57/58


58/58


UL ThroughputGb over IP case (LLC level)

Asig over IP Dimensioning method (only for B11 release)

7.8 MXBSC DIMENSIONING METHODS

AterMux CS SCCP Interface DimensioningAterMux CS TCH Interface Dimensioning

AterMux PS GSL Interface Dimensioning

AterMux PS GCH Interface Dimensioning

AterMux Interface Dimensioning

GPU/GP Board Dimensioning

DL ThroughputGb over FR case (LLC level)

UL ThroughputGb over FR case (LLC level)

DL ThroughputGb over IP case (LLC level)

UL ThroughputGb over IP case (LLC level)

Asig over IP Dimensioning method (only for B11 release)

7.9 GPU-GP BOARD DIMENSIONING METHODSGCH traffic load

GPU power limitation from PTU (DSP/CPU)

GPU power limitation from PMU (CPU)

GPU memory limitation from PMU (CPU)

Final number of required GPU/GP boards

AterMux GSL Links per GPU Dimensioning

AterMux GCH Links per GPU Dimensioning

AterMux Links per GPU Dimensioning

DL ThroughputGb over FR case (SNS level)

UL ThroughputGb over FR case (SNS level)

DL ThroughputGb over IP case (SNS level)UL ThroughputGb over IP case (SNS level)

7.10 GB LINK DIMENSIONING METHODS

GB Interface Dimensioning at GPU level

7.11 NSVC DIMENSIONING METHODS

DL Throughput

UL Throughput

7.12 SGSN-IP-ENDPOINT DIMENSIONING METHODS

DL Throughput

UL Throughput

7.13 IPGBLINK DIMENSIONING METHODS

DL Throughput

UL Throughput

END OF DOCUMENT

Documents

Amt .Net Userguide