ID Translation Administrator User Reference Guide.pdf

8/14/2019 ID Translation Administrator User Reference Guide.pdf

http://slidepdf.com/reader/full/id-translation-administrator-user-reference-guidepdf 1/40

ID Translation Administrator

User Reference Guide

Version 5.2



© Copyright 2006 AIRCOM InternationalAll rights reserved

ADVANTAGE, ARCHITECT, ASSET3G, CONNECT, DATASAFE, ENTERPRISE,NEPTUNE, HOMEZONE, OPTIMA, TARGET and WEBWIZARD are recognisedtrademarks of AIRCOM International. Other product names are trademarks of theirrespective companies.

Microsoft Word, Microsoft Office, Windows®, Windows 95™, Windows 98™,Windows NT® and MS-DOS™ are trademarks of the Microsoft Corporation.

This documentation is protected by copyright and contains proprietary andconfidential information. No part of the contents of this documentation may bedisclosed, used or reproduced in any form, or by any means, without the priorwritten 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 nowarranty or representation, either expressed or implied, about this documentation, itsquality or fitness for particular customer purpose. Users are solely responsible for theproper use of ENTERPRISE software and the application of the results obtained.

An electronic version of this document exists.

This User Reference Guide finalised on 19 October 2006.

Refer to the Online Help for more information.

This User Reference Guide prepared by:

AIRCOM International Ltd

Cassini CourtRandalls Research ParkRandalls WayLeatherheadSurreyKT22 7TW

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



Can You Improve

Our User Assistance?

Do the Help and User Reference Guides Help You?

AIRCOM is always working to improve the online Help and User Reference Guidesfor our products, so that your job is easier to do.

Even if you would not normally do so, please take a look at the Help or UserReference Guide next time you are unsure of how to do something and if you haveany comments or questions that could help us improve them, please email us on:[email protected].

We highly value your comments, suggestions, and criticisms. If you did not find theuser assistance you were looking for, needed more assistance than the online Helpor User Reference Guides provided, or have any suggestions for futureimprovements to our information, we want to know.

Specifically, consider:

• Is the information accurate and complete?

• Is the information helpful – does it answer your question about the program?

• Are there any words that you would like to be put into the index?

♦ ♦ ♦





ID Translation Administrator User Reference Guide Page iVersion 5.1

Contents

Chapter 1 Using ID Translation Administrator

Obtaining User Assistance 2 About the ENTERPRISE User Reference Guides 2 Using ENTERPRISE User Reference Guide PDFs 4 Obtaining Further Information and Services 4 Obtaining Support 5

Chapter 2 Before Using ID Translation Administrator Installing ID Translation Administrator 7 Creating an ID Translation Administrator Database 8

Setting Up sysdba Privilege 10 Opening ID Translation Administrator 10

Chapter 3 Configuring ID Translation Administrator Specifying Connections To Product Databases 11

Creating Links to Translation Databases from Product Databases 13 Defining Element Type Data Sources For OPTIMA Databases 15 Loading Projects From ENTERPRISE Databases 17

Managing the MCC/MNC Lookup Table 18

Chapter 4 Creating Translations Creating Translations Using the Translation Editor 19

Viewing Translations In the Translation Editor 21 Editing Translations In the Translation Editor 21 Copying Translations Between Projects 22

Creating Translations Using Algorithms 22 Creating Translations Using Excel 26

About Valid Element Types 27 Importing Translations From a File 28

Exporting Translation Information 29 Exporting Translations and Legacy Translations 29 Managing the Failed Translation Log 30 Mapping Failed Translations 31

Index



Page ii ID Translation Admini strator User Reference GuideVersion 5.1



ID Translation Administrator User Reference Guide Page 1Version 5.1

Using ID Translation Administrator

If you are using a mixture of network planning and optimisation tools, a singlenetwork element may be given a different identifier (NEI) per domain. Domains areeither:

• Network domains - for example, different real live networks

• Software product domains - for example, different AIRCOM products likeASSET3g and OPTIMA

For example, if you are using ASSET3g and OPTIMA, the same cell could have a CellID of Site0A in ASSET3g and 12345_1 in OPTIMA. When information has to be sharedbetween these two domains, you can use ID Translation Administrator to map theNEIs accordingly to ensure that the information is shared seamlessly.

You can use the ID Translation Administrator to manage translations between thefollowing AIRCOM software products:

• AIRCOM planning products, collectively referred to as ENTERPRISE fortranslation purposes

Note : Translation of elements created using DIRECT is not yet supported.

• DATASAFE

• OPTIMA

• QUALITA

In This Section

Obtaining User Assistance

C H A P T E R 1



Page 2 ID Translation Admini strator User Reference GuideVersion 5.1

Obtaining User Assistance

Using Online Help

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

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

• To search for something particular, from the Help menu, click Help Contents andon the Index tab, type in a word.

• Context-sensitive help is available for most of the dialog boxes. Therefore, to getrelevant Help about using a dialog box, in the dialog box, press F1.

We value your comments, suggestions, and criticisms. If you did not find the Help

you were looking for, needed more assistance than the online Help provided, or haveany suggestions for future improvements to our online information, we want toknow. Please email your comments with the subject 'ENTERPRISE Manuals' to theappropriate address as described in Obtaining Support on page 5.

Using ENTERPRISE User Reference Guides

AIRCOM also provides a series of User Reference Guides for its software tools. Forinformation on the full range available, see About the ENTERPRISE User ReferenceGuides on page 2.

You can view the manuals supplied as PDFs (Adobe portable document format) on

the ENTERPRISE CD, or print out your own copies of them on a postscript printer.

Tip : You can choose to install the PDFs on your PC when installing.

Note : Adobe and Acrobat are trademarks of Adobe Systems, Incorporated.

For any further documentation, such as application notes and extra referenceinformation, please email the support team at the address described in ObtainingSupport on page 5.

About the ENTERPRISE User Reference Guides

This table describes the manuals:This Manual Contains Information On

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

ENTERPRISE Administration and Installation Guide Installing and configuring ENTERPRISE, your network, and Oracledatabases. Using Administrator to create users and groups, and setpermissions.

Also contains information on software licensing.

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

Also contains reference information about file formats.

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




This Manual Contains Information On

ADVANTAGE User Reference Using ADVANTAGE to plan and optimise networks automatically, analysenetwork performance, identify problem cells/areas, use networkperformance data and more.

Array Wizard User Reference Using Array Wizard to automatically generate coverage predictions andbest server arrays, which gives you instantaneous display of coverage andinterference information for pre-selected filters when loaded into ASSET3g.

ASSET3g User Reference Using ASSET3g, the network planning and analysis tool, to design a rangeof 2g and 3g networks.

Includes information on hierarchical network planning, propagationmodelling, service and bearer definition, coverage analysis, traffic planning,neighbour planning, frequency planning, CW data analysis, detailedreporting, analysis arrays and simulation of network performance.

ASSET3g Technical Reference A separate technical reference for ASSET3g, which contains a list of arraydescriptions and information on many of the algorithms used.

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 smalland large scale changes to networks

DIRECT User Reference Using DIRECT to design telecommunications networks of different networklayers. Explains how to plan cellular, PSTN and data networks at a bothgeneral and strategic level.

Also contains DIRECT specific reference information.

NEPTUNE User Reference Using NEPTUNE to collect, import and analyse testmobile data and usingthe 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 withENTERPRISE and standalone using OPTIMA Lite.

QUALITA User Reference Using QUALITA including information on how to create Service Level Agreements, setting Quality of Service filters and benchmarks, configuringreports and enabling QoS degradation analysis.

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

TARGET User Reference Using TARGET as an administrator to design forms, Gantt charts andreports. Using TARGET to view and edit information about your networkand its roll out.

Also contains TARGET reference information.

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






Obtaining Support

Logging Support Requests Online

To log a support request online:

1 Go to the AIRCOM website, at http://www.aircom.co.uk.

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.

Logging Support Requests via Telephone or Email

Alternatively, this table shows the contact details for any support or assistance you

may require:Type of Query Contact Email

You have a difficulty you cannot resolveyourself using the Online Help

North AmericaTel : +214 576 2700Fax : +1 214 576 2794

[email protected]

South AmericaTel : +55 12 39412199Fax :+55 12 39113727

[email protected]

You have found a possible fault in thesoftware

SingaporeTel : +65 6372 0548Fax : +65 6372 0350

[email protected]

Middle East and AfricaTel : +971 4 391 2640Fax : +971 4 391 8660

[email protected]

South AfricaTel : +27 11 745 1475Fax : +27 11 465 1517

[email protected]

Europe and Rest of WorldTel : +44 1932 442345

Fax : +44 1932 442005

[email protected]

You cannot find the Help you were lookingfor

You would like to suggest future

improvements to the online information

You require further documentation, such asapplication notes and further referenceinformation

UK Documentation [email protected]

You require updated versions of PDF files Visit the AIRCOM website athttp://www.aircom.co.uk

You require details of mobile and fixednetwork training courses run by AIRCOM

Competence Development Solutions [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 inwhich 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




Before Using ID Translation Administrator

Before you begin using ID Translation Administrator you must set it up, by:• Installing ID Translation Administrator

• Creating an ID Translation Administrator database

In This Section

Installing ID Translation AdministratorCreating an ID Translation Administrator DatabaseOpening ID Translation Administrator

Install ing ID Translation Administrator

ID Translation Administrator is not installed automatically as part of the typicalinstallation package, and you must install it yourself.

To do this if you already have ENTERPRISE installed:

1 Ensure you have installed Microsoft.NET framework 1.1. This should be doneautomatically when you install the Core ENTERPRISE application.

2 Open the Control Panel.

(For example, from the Start menu, point to Settings, and click Control Panel).

3 In the window that appears, double-click Add or Remove Programs.

4 Select ENTERPRISE from the list of currently installed programs.

5 Click the Change/Remove button.

6 Ensure the Modify option is selected, and then click Next.

7 Click Next.

C H A P T E R 2




8 In the Core Application list, expand the Optional list and select ID TranslationAdministrator:

9 Click Next, and then click Finish when the installation is complete.

After you have installed ID Translation Administrator, you can now create adatabase.

To install ID Translation Administrator if you do not have ENTERPRISE installed yet:

1 During the installation process, select the Custom Setup Type.

2 Click Next.

3 In the Core Application list, expand the Optional list and select ID TranslationAdministrator:

4 Continue installing as before.

Creating an ID Translation Administrator Database

After you have installed the ID Translation Administrator, you must identify adatabase in which to store the mappings of the NEIs. This could be an entirely newOracle database that you have created just for this purpose, or an existing one (forexample, your ENTERPRISE or OPTIMA database.

Important : You must have database administrator (sysdba) privilege for the Oracledatabase that you want to use. If you do not have this, you can set it up using anOracle tool. For more information on this, see Setting Up sysdba Privilege on page 10.

For more information on creating Oracle databases, see the ENTERPRISE Installationand Administration Guide.




To create an ID Translation Administrator database:

1 From the Start menu, point to Programs, AIRCOM International, ENTERPRISE,Misc and then click ID Translation Administrator.

2 In the dialog box that appears, click Login.3 In the drop down box, select the Data Source for your database.

If the required data source is not listed, click Setup to configure it.

Note : This data source is used by all ENTERPRISE products to connect to thetranslation database when they need to translate NEIs. The last data source thatyou setup is the one that will be used, even if old ones that you have previouslysetup still exist.

4 Connect to the database using a username and password that has sysdbaprivilege.

The Database Creation Wizard appears.

5 You are prompted for the three tablespace names required by ID TranslationAdministrator, which you will have created when you created your Oracledatabase. Select the Permanent, Index and Temporary tablespaces in therespective fields.

6 Click Next.

7 You are then prompted for two passwords, one for each user account. There aretwo ID Translation Administrator user accounts, which are described in thefollowing table:

This User Account CanTranslationAdmin Make changes to the data in the translation database, including:

Defining general settings

Importing and exporting translation data

Editing translations

Creating and editing translation contexts and algorithms

Viewing translations

Establish only one database session at any given time (in otherwords, can only log in once).

TranslationInspector Export translation data

View all data

Establish multiple database sessions at any given time (in otherwords, can log in multiple times).

Important : TranslationInspectors cannot make any changes tothe data in the translation data.

8 Click Finish.

Administrator now configures the database. This can take a few minutesdepending on the speed of your machine.

If your database is created successfully, you are automatically logged in with the

TranslationAdmin account.




In the unlikely event that the database installation process failed, you will get amessage explaining this. Please contact Product Support for assistance, using thecontact details provided in Obtaining AIRCOM Support on page 5.

Setting Up sysdba Privilege

To create an ID Translation Administrator database, you must have an Oracle accountthat has sysdba privilege. If you do not have this privilege, you can set this up usingan Oracle tool. To do this:

1 Open your preferred Oracle tool, for example Toad.

2 Login as sysdba using the sys account.

3 Execute the following statement:

GRANT SYSDBA TO <USERNAME>

where <USERNAME>is the required user account name.

Opening ID Translation Administrator

Providing that you have installed ID Translation Administrator and created an IDTranslation Administrator database, you can open ID Translation Administrator atany time by following these steps:

1 From the Start menu, point to Programs, AIRCOM International, ENTERPRISE,Misc and then click ID Translation Administrator.

2 In the dialog box that appears, click Login.3 In the drop down box, select the Data Source for your database.

If the required data source is not listed, click Setup to configure it.

Note : This data source is used by all ENTERPRISE products to connect to thetranslation database when they need to translate NEIs.

4 In the User ID field, select the username you want to log into the database with.This can be either TranslationAdmin or TranslationInspector. For moreinformation on the separate permissions for these users, see Creating an IDTranslation Administrator Database on page 8.

5 In the Password field, type the password associated with the username.

6 Click Login.




Configuring ID Translation Administrator

After you have installed ID Translation Administrator and created a database, youshould login with the TranslationAdmin account, and configure the tool in thefollowing ways:

• Specify connections to product databases.

• If you want to create translations involving ENTERPRISE network elements, youmust load ENTERPRISE projects from the ENTERPRISE database into the IDtranslation database.

• If you want to create translations involving OPTIMA network elements, you mustdefine a data source for each OPTIMA element type that you want to translate.This enables ID Translation Administrator to locate information in the OPTIMA

database.

In This Section

Specifying Connections To Product DatabasesManaging the MCC/MNC Lookup Table

Specifying Connections To Product Databases

When you first open ID Translation Administrator, you must specify a database for

each product that you want to include in translations. To do this:

1 From the File menu, point to Product Database Configuration and then clickDatabase Connection.

- or -

In the right pane of the main ID Translation Administrator window, double-clickthe required product:

C H A P T E R 3




The Product Database Connection dialog box appears:

2 From the Name drop-down list, select the product, for example, OPTIMA.

The Internal ID is a number representing the product domain, which is used laterin importing and exporting translations. The following numbers are used:

Internal ID Product Domain Name

1 ENTERPRISE

2 RANOPT

3 DATASAFE

4 OPTIMA

5 QUALITA

3 In the Oracle Service Name field, type the SID of the database.

4 Complete the connection details by typing the appropriate information in the UserName, Password and Host Server fields.

If the database is on your local machine, the Host Server is localhost.




5 To verify the connection to the product database, click the Test Link to ProductDatabase button.

6 If it is successful, click OK, and then click Commit to save the changes.

- or -If it is unsuccessful, check the connection details are correct, and click TestConnection again.

In the right pane of the main ID Translation Administrator window, a correctlyconnected product database is denoted by a (green) arrow:

Successful Database Connection

If the connection details are present but the database cannot be connected to for anyreason, this is denoted by a (yellow) star:

Unsuccessful Database Connection

If no details have been entered, this is denoted by a (blue) cross:

Database Connection Not Attempted

You can also create links within the product database to the translation database. Forinformation on how to do this, see Creating Links to Translation Databases fromProduct Databases on page 13.

After you have specified the connections to product databases, you may have to

perform several other administrative tasks:• If you have specified a connection to an ENTERPRISE database, you can now load

ENTERPRISE projects from the ENTERPRISE database into the ID Translationdatabase

• If you have specified a connection to an OPTIMA database, you can now define adata source for each OPTIMA Element Type you want to translate

Creating Links to Translation Databases from ProductDatabases

You can create a link from a product database (for example, an OPTIMA database) toa translation database. This is useful when you want to translate NEIs from withinstored procedures running to a product database. The translation databasefunctionality can be used via the link created, which always has the nameCoreIntegration_Db_Link.Aircom.Co.Uk.

Before you do this, you must ensure you have the correct privilege. To define thisprivilege:

1 Open your preferred Oracle tool, for example Toad.

2 Login to the product database using the sys account, or another account that cangrant the privilege.




3 Execute the following statement:

GRANT CREATE PUBLI C DATABASE LI NK TO <USERNAME>

where <USERNAME>is the required user account name.

To create the link from a product database to a translation database:

1 In the Product Database Connection dialog box, ensure that you have created aconnection from the translation database to the product database.

2 Click Commit.

3 Click the Create Link to Translation Database button.

4 In the dialog box that appears, click OK.

The link is created, and a dialog box appears, telling you the name of the link (asgiven above).

5 Click OK.Important : This will only link the databases; the product itself (for example,ENTERPRISE) also needs to locate the translation database. For more information onthis, see Specifying Connections To Translation Databases for Products on page 14.

Specifying Connections To Translation Databases for Products

As well, as linking the product database to the translation database, you must alsolink the product application to the translation database. To do this, either:

• Ensure that ID Translation Administrator is installed on the same machine as the

product application, and then set up the correct data source when you open IDTranslation Administrator

- or -

• Copy the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\AIRCOMInternational\ENTERPRISE\5.1\ID Translation\Login Information' from amachine with the correct data source already set up, and paste it into the registryon the required machine

You must do this for each machine on which you want to use ID TranslationAdministrator.




Defining Element Type Data Sources For OPTIMA Databases

Because ENTERPRISE databases have a fixed structure, ID Translation Administratorcan read them directly. However, OPTIMA databases only become fixed at the pointof installation. Therefore if you have specified a connection to an OPTIMA database,

you must also specify where within that database the ID Translation Administratorcan find the required data. This information is the element type data source.

The ID Translation Administrator recognises a predefined set of attributes for allelement types, which are described in the following table:

Att ribute Name Descr ipt ion Optional?

IDKey Unique key that refers to the element. Yes

IDName The name of the element. If no IDKey is given, then this is used as the key.This must be defined for translation to take place.

No

MCC The MCC of the element (UMTS and GSM cells only). Yes

MNC The MNC of the element (UMTS and GSM cells only). YesLAC The LAC of the element (UMTS and GSM cells only). Yes

NetworkCI The Network CI of the element (UMTS and GSM cells only). Yes

You can configure the element type data sources in the Product Database Descriptiondialog box, by binding these pre-defined attributes to the corresponding tablecolumns in the database. ID Translation Administrator can then use these attributebindings to locate data in the OPTIMA database.

Note : If elements of a particular type are stored in multiple database tables, you canconfigure more than one element type data source.

To set up an element type data source for your OPTIMA database:1 From the File menu, point to Product Database Configuration and then click

Database Description.

The Product Database Description dialog box appears.

2 From the Product drop-down list, select the OPTIMA database.

3 From the Element Type drop-down list, select the element type for which youwant to create an element type data source.

4 In the Element Type Data Sources pane, click Add. A suggested name isdisplayed, which you can edit.

5 Click OK.

In the Element Type Attribute Bindings window, a list of the different attributesfor this element type appears. The attribute name will be specified, but you mustspecify the following locations:

Item Description

Schema Name The schema in the OPTIMA database that contains the attribute.

Table Name The table in the chosen schema that contains the attribute.

Column Name The column in the chosen table that contains the attribute.




This picture shows an example attribute binding for an element type data sourcecalled GSM_MSC. It specifies that the attribute IDKey can be found in theNode_ID column of the MODULE_NODE table, in the AIRCOM schema of theOPTIMA database.

6 Click Test to check that the correct information is retrieved from the OPTIMAdatabase for the setup. If the test is successful, a dialog box appears, listing all of

the information it was able to retrieve:

7 Click Close.

8 Create at least one element type data source for each element type that you want

to create translations for, and then click Commit.




Loading Projects From ENTERPRISE Databases

If you have specified a connection to an ENTERPRISE database, you must also loadENTERPRISE projects from the ENTERPRISE database into the ID Translationdatabase. To do this:

1 From the File menu, point to General Settings and click Manage Projects.

2 In the dialog box that appears, click Synchronise from DB.

A list of the available projects for the ENTERPRISE database appears:

3 If you want to, you can also remove orphaned projects from the selection list.Orphaned projects are those which have been deleted from the ENTERPRISEdatabase (using ENTERPRISE Administrator) but still remain in the translationdatabase:

Select the orphans that you want to remove, and then click Remove SelectedOrphans

- or -

Click Remove All Orphans

Warning : If you delete a project, all of the data in that project will be permanentlydeleted.

4 Click Commit to save the list of projects, and then click Close.




Managing the MCC/MNC Lookup Table

In the Manage MCC/MNC Lookup Table dialog box, you can manage the definedmobile network MCC and MNC values.

Important : All changes are temporary until you click Commit.

To add an MCC node to the Mobile Networks tree, click Add MCC.

To add an MNC to a selected MCC node, click Add MNC.

To edit a selected node, click Edit.

To remove a selected node (which is not referenced by any elements in the database),in the Mobile Networks group box, click Remove.




Creating Translations

After you have configured ID Translation Administrator, you can create the actualtranslations, which define how the NEIs are mapped from one product database toanother. There are a number of ways to create a translation:

• Using the Translation Editor

• Using an algorithm

• Using Excel and csv file format

In This Section

Creating Translations Using the Translation EditorCreating Translations Using AlgorithmsCreating Translations Using ExcelExporting Translation InformationManaging the Failed Translation Log

Creating Translations Using the Translation Editor

You can create translations manually by specifying the mappings directly in theTranslation Editor, rather than using an algorithm or importing them from file.

To do this:

1 From the Translations menu, point to Lookup Tables and click Edit.

The Translation Editor dialog box appears.

2 Click the Edit tab.

3 From the drop-down list, select the Element Type for which you want to create thetranslations.

4 Select the Show Unmapped Network Element IDs option.

5 Choose the Source Product (and if required, the ENTERPRISE project name).

6 Choose the Target Product (and if required, the ENTERPRISE project name).

7 Click Refresh Table.

C H A P T E R 4




For the first ID that you want to create a translation for, select its equivalent in thetarget product database:

In the example above, the ENTERPRISE MSC0 has been mapped to OPTIMA'sOPT_MSC0, ENTERPRISE MSC2 to OPTIMA's OPT_MSC2 and so on.

8 Click Commit to save the translations.Click Refresh Table. Each successful translation is removed from the list ofunmapped NEIs.

You can now view your translations on the View tab.




Viewing Translations In the Translation Editor

On the View tab of the Translation Editor, you can view all the translations for allproduct databases in a convenient format.

In the Filter pane, you can to restrict the translations displayed. To do this:1 If you want to filter based on a particular element type, select it from the Element

Type drop-down list.

Note : When the Element Type is set to <ALL>, GSM Subcell and AMPS Subcelltypes are not included. You must select these element types separately.

2 If you want to filter based on a particular ENTERPRISE project, select thecheckbox and choose the required project from the drop-down list.

3 Click Apply Filter to refresh the display.

Important : The ID name field in the display grid is the internal ID assigned to the

element by the planning tool. Any planning tool element in the grid that does nothave this internal ID will not be used for translation, so you should check that allplanning elements have an ID name value. If any are missing, from theTranslation menu, point to Lookup Tables and click Update Radio Planning IDs.Note that when you display Subcell translations there will be two “id key” fields;one for the cell and another for the cell layer.

To export the translations into an XML file format, click Export.

Note : You can load this file into MS Excel. To do this, open the file in MS Excel and ifprompted, select to open it as a read only work book.

Important : You cannot import MS Excel files directly into ID TranslationAdministrator. You must copy the data into a *.csv file and import this instead.

Editing Translations In the Translation Editor

To edit (unmap) a translation that you have created in the Translation Editor:

1 From the Translations menu, point to Lookup Tables and click Edit.

2 In the Translation Editor, click the Edit tab.

3 From the drop-down list, select the Element Type for which you want to edit thetranslation(s).

4 If you want to edit an existing successful translation, select the Show MappedNetwork Element IDs option.

Select the translations that you want to edit, and click Unmap Selection, or to clearall translations so that they can be edited, click Unmap All.

- or -

If you want to edit a translation that has failed, select the Show Network ElementIDs from Failed Translation Log option.

5 Choose the Source Product (and if required, the ENTERPRISE project name).

6 Choose the Target Product (and if required, the ENTERPRISE project name).





8 Edit the translations as required, and then click Commit to save the changes.

Copying Translations Between Projects

In the Translation Editor, if you have created a translation for a particularENTERPRISE project, you can copy it for use with another ENTERPRISE project.

To do this:

1 Click the Copy tab.

2 Select the element type of the translation that you want to copy.

3 In the Copy From pane, select the ENTERPRISE project for which the translation iscurrently used.


All of the existing translations for this project appear.5 Select the checkboxes for the translations that you want to copy. By default all

translations are ticked.

Tip : To select or un-select a contiguous number of translations, click the first andlast one in the list while holding down the Shift key, and then click either Copy ->Yes or Copy -> No as appropriate.

6 In the Copy To pane, select the ENTERPRISE project into which you want to copyand use the translation.

7 Click Copy.

The selected translations are copied for use in the required project.8 Click Commit.

Creating Translations Using Algorithms

As well as creating translations manually or importing them, you can createtranslations using specific algorithms, which apply logic to the NEIs in one productdatabase to translate them into NEIs in another product database.

For example, cellids from the ENTERPRISE database may be prefixed with opt_ in theOPTIMA product database, and this can be expressed in an algorithm. Translationalgorithms are created in specified translation contexts, which define the elementtypes, projects and the databases involved.

To create a translation context:

1 From the Translation menu, click Configure Algorithms.

The Configure Translations Options dialog box appears.

2 Click Add New, and specify the details for the translation context:

The element type (for example, GSM Cell)

The source product (the database from which you want to translate the NEI)

The target product (the database into which you want to translate the NEI)




The ENTERPRISE project name, if applicable

3 Click OK.

The translation context is added to the list. In this example, this translation context

is for translating GSM Cell IDs between ENTERPRISE project ent 5117 andOPTIMA:

4 To create the underlying algorithm for this translation context, click EditAlgorithm.

The Translation Algorithm Editor appears.

5 In the Command Line Specification pane, create the first line of the algorithmusing one of the following options:

Algori thm name Descr ipt ion

Replace Replaces occurrences of the first value with the second.

In this example, ENT will be replaced with OPT:

Add Adds the first value to either the beginning or end of the ID.

In this example, OPT will be added to the beginning of the ID:

Trim Removes the first value from either the beginning or end of the ID.

In this example, _3g will be removed from the end of the ID:

Delete Removes a specified number of characters from the ID, from a chosen character position.

In this example, 3 characters will be removed from character 2 onwards:

If this was applied to the ID 1optcell, the translation would be 1cell.

Insert Inserts the first value at a chosen character position.

In this example, the value opt would be added at position 2:

If this was applied to the ID 1cell, the translation would be 1optcell.

Remove Removes either all non-numeric or all numeric characters from the ID.




Algori thm name Descr ipt ion

Convert Converts the character at a chosen position into a specific number or letter. In thisexample, the character at position 2 would be converted using the rule that A <=> 1, B<=> 2 and so on:

If this was applied to the ID 1A, the translation would be 11.

6 After you have defined your first line, click the Add button to add it to thealgorithm.

The algorithm is displayed in the right-hand pane.

7 Continue to add lines to the algorithm using steps 5 and 6. You can edit the lines

(operations) of your algorithm in the following ways:To Do This

Replace an existing line in the algorithm Select the line in the algorithm, and in the Command Line SpecificationPane edit this line or create the new line and then click the Modify button.

Remove a line from the algorithm Select the line in the algorithm, and then click the Delete button.

Move a line in the algorithm up one line Select the line in the algorithm, and then click the Move Up button.

Move a line in the algorithm down one line Select the line in the algorithm, and then click the Move Down button.

8 To check if your completed algorithm works correctly, in the Algorithm Test pane,type a sample NEI and click Test. The current algorithm is applied to NEI and thetranslated NEI is displayed in the pane.

In this example, a simple algorithm has been created, to replace the OPT prefixwith ASS3g, and then add Jersey to the beginning to indicate the project:




9 When you are satisfied, click OK to accept the changes. The algorithm for theselected context appears in the bottom pane:

10 Click Commit to save the ID Translation Context and associated algorithm.

11 To use the algorithm to create the translations, select the required context and clickApply Algorithm.




Creating Translations Using Excel

As well as creating translations within ID Translation Administrator (either using theTranslation Editor, or using an algorithm), you can also create them using Excel, and

then import this as a *.csv file.Tip : Your ENTERPRISE installation includes an example ID translation file (SampleNetwork Element ID Translation File.csv). You can find it in the ID Translation sub-folder of the Common folder.

To create a translation file:

1 In Excel, open a blank Excel worksheet or the example ID translation fileprovided.

The file must use the following header names for the columns:

Item Description

Source Product ID The ID code for the source database - ENTERPRISE (1), RANOPT (2), DATASAFE(3), OPTIMA (4), QUALITA (5).

Target Product ID The ID code for the target database - ENTERPRISE (1), RANOPT (2), DATASAFE (3),OPTIMA (4), QUALITA (5).

Element Type The element type to be translated.

Source Element ID The element ID in the source database.

Target Element ID The translated element ID in the target database.

Cell Layer The cell layer, used to translate GSM/AMPS subcell IDs.

Mobile Country Code The MCC, used when translating GSM cell data.

Mobile Network Code The MNC, used when translating GSM cell data.

Location Area Code The LAC, used when translating GSM cell data.

Network Cell ID The network cell ID, used when translating GSM cell data.

Project Name The name of the project, if the source or target database is an ENTERPRISE one.

This picture shows an example:




2 Edit the file as required.

Important : When editing the Excel file, you must bear in mind the following rules:

The header names are case-insensitive, but must be spelt exactly as they are

given in the table above. The header names can be placed in any order, providing they are all on the

first row.

Source Product ID, Target Product ID, Element Type, Source Element ID andTarget Element ID are all mandatory, and must all contain a value. For theProduct ID, you must use the corresponding numeric Internal ID, as describedin Specifying Connections To Product Databases on page 11.

Element Type is case-insensitive, but must be spelt correctly. For a list of validelement types, see About Valid Element Types on page 27.

Mobile Country Code, Mobile Network Code, Location Area Code andNetwork Cell ID columns together represent CGI, and only apply to recordswhere the Element Type is GSM Cell or UMTS Cell. They must always bepresent or absent. When present they must always have values or be blank.

Project Name is only mandatory if either the source or target database is anENTERPRISE one. It is case-insensitive, but must be spelt exactly as it is in theENTERPRISE database.

Any row that starts with a # character is treated as a comment and will not beprocessed.

Blank lines can be used in the file but will not be processed.

3 When you have finished editing the Excel file, save it as a *.csv file with anappropriate filename.

You can now import these translations into ID Translation Administrator.

About Valid Element Types

The valid element types that can be used in an Excel translation file are listed in thefollowing table, and are grouped by technology area:

Technology Element Type Element ID

UMTS UMTS WMSC 1

UMTS MGW 2

UMTS GGSN 3

UMTS SGSN 4

UMTS RNC 5

UMTS Node B 6

UMTS Cell 7

UMTS Repeater 8

UMTS LMU 9

GSM GSM MSC 10

GSM GGSN 11




GSM SGSN 12

GSM BSC 13

GSM Cell Site 14

GSM Cell 15

GSM Repeater 16

GSM SubCell 17

GSM LMU 18

AMPS AMPS MSC 19

AMPS Cell Site 20

AMPS Cell 21

AMPS Repeater 22

AMPS SubCell 23

CDMA CDMA MSC 24CDMA BSC 25

CDMA BS 26

CDMA Sector 27

CDMA Repeater 28

Import ing Translations From a File

If you have an ID translation *.csv file (for example, one that you have createdyourself), you can import it into ID Translation Administrator.

To do this:

1 In the ID Translation Administrator window, from the File menu, click Import.

2 In the dialog box that appears, click the Browse button, locate the required file andclick Open.

3 In the Element Types pane, select the element types for which you want to importtranslations.

4 If you are using an ENTERPRISE database as the source or the target, select theEnterprise projects checkbox and specify which projects you want to importtranslations for.

5 Click Import.

6 Select whether or not you want to back up the ID Translation Administratordatabase before importing. If you do this, the translation is exported from thedatabase to another file.

The selected translations are imported. To view them, from the Translation menu,click Edit.

You can view the imported translations on the View tab.




Exporting Translation Information

In the ID Translation Administrator, you can export information in the following

ways:

• Export translations and legacy translations to a *.csv file

• Export translation data to a *.xml file

Export ing Translations and Legacy Translations

In ID Translation Administrator, you can export translations to *.csv files.

To export translations:

1 From the File menu, point to Export and click Translations to CSV file.

2 In the dialog box that appears, select the element types whose translations youwant to export.

3 If you are using any ENTERPRISE projects, select the Enterprise Projectscheckbox, and select the projects whose translation data you want to export.

4 Click Export.

5 In the dialog box that appears, locate the required file location, type the required*.csv filename and click Save.

The required translations are exported.

You may also have translations that you have created using the old CI translation tool(cixlat.exe). If so, you can convert them into translations compatible for ID TranslationAdministrator. To do this:

1 From the File menu, point to Export and click Legacy Translations to CSV file.

2 In the dialog box that appears, click the Browse button and locate the file that youwant to export to.

3 Click Save, and then click Export.

The translations created in cixlat.exe are exported to this file.

4 Click OK.

Now you can import these translations for use in ID Translation Administrator.




Managing the Failed Translation Log

The Failed Translation Log displays all entries of failed translation requests madeupon the translation database by products like OPTIMA.

To open the Failed Translation Log:

From the Logs menu, click Failed Translation Log.

This picture shows an example:

The log is divided into three different failed translation types:• Network Element Identifiers

• CGIs

• Scrambling codes

Select the appropriate radio button in the Display Options pane to view theinformation for that type. You can then use this information to map the NEIs thatfailed to translate.

To delete one or more log entries:

Select the required entries and then click Delete Selected Log Entries.




To delete all of the failed entries that you have subsequently re-mapped:

Click Delete Mapped Entries.

To delete all log entries:

Click Delete All Log Entries.

To export the data in the translation log to an XML file, click Export.

Note : You can load this file into MS Excel. To do this, open the file in MS Excel and ifprompted, select to open it as a read only work book.

Important : You cannot import MS Excel files directly into ID TranslationAdministrator. You must copy the data into a *.csv file and import this instead.

Mapping Failed Translations

In the Failed Translation Log, you can map translations that have initially failed. Todo this:

1 Ensure that you are viewing the correct data.

2 In the top pane, select the failed translation that you want to re-map.

The IDs that could not be translated appear in the Map Failed Translations pane.

Note : All IDs that failed to translate in the same context as the selected one aredisplayed for mapping.

3 For each required ID in the first column, select the correctly translated ID in thesecond column:

4 When you have chosen all of the required IDs, click the Re-map FailedTranslation(s) button.






ID Translation Administrator User Reference Guide Page iVersion 5.1

Index

A Algorithms

ID translation • 22

C Configuring

ID Translation Administrator • 11Connections

to ID Translation Administrator databases • 13to product databases • 11

CopyingID translations • 22

CreatingID Translation Administrator databases • 8ID translations • 19, 22, 26

D Databases

connecting to ID Translation Administrator • 13connecting to product • 11

E Editing

ID translations • 21Exporting

ID translations • 29

F Failed translations

re-mapping • 31viewing • 30

I ID Translation Administrator

configuring • 11databases • 8, 11, 13installing • 7opening • 10Translation Editor • 19, 21, 22

ID translationscopying • 22creating • 19, 22, 26

editing • 21exporting • 29failed • 30, 31

importing • 28using algorithms • 22using Excel • 26viewing • 21

ImportingID translations • 28

InstallingID Translation Administrator • 7

M Managing

Failed Translation Log • 30MCC/MNC lookup table • 18

MCC/MNC lookup table, managing • 18

O Opening

ID Translation Administrator • 10

V Viewing

ID translations • 21



Documents

ID Translation Administrator User Reference Guide.pdf