XParameters 5.6 Release Notes

xParameters 5.6 Release Notes

Contents

Contents

1 Introduction 4

2 Release 5.6 52.1 Core Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1.1 Implementation Server . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Optimization Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.2.1 Huawei 3G RAN11 Support . . . . . . . . . . . . . . . . . . . . . . . 62.2.2 Ericsson 3G P7 Support . . . . . . . . . . . . . . . . . . . . . . . . . 62.2.3 Alcatel 2G Optimization . . . . . . . . . . . . . . . . . . . . . . . . . 62.2.4 ZTE 2G Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2.5 Neighbor List and Scrambling Code Optimization for Huawei 3G (op-

tional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3 Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3.1 High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.3.1.1 Optimi Data Gateway Scalability Improvements . . . . . . . 82.3.1.2 Project Backward Compatibility . . . . . . . . . . . . . . . 82.3.1.3 [5141] GIS Views Refactoring: Complete CM Views for all

supported vendors . . . . . . . . . . . . . . . . . . . . . . . 82.3.1.4 Optimi Data Gateway Audit . . . . . . . . . . . . . . . . . . 9

2.3.2 Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3.2.1 [5064, 5624] Size Increase in Application logs . . . . . . . . 92.3.2.2 [5172] Message Log Improvements . . . . . . . . . . . . . . 92.3.2.3 [5575][48699] Error in execution if RNC has no defined ad-

jacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3.2.4 [5396][48641] Consistency rule added: nhs_min

Contents

2.4.3.3 [5607][48703] Project cannot be edited if BSC removed dueto unavailable CM . . . . . . . . . . . . . . . . . . . . . . . 11

2.4.3.4 [5301] Fix in format for ADJG identification of target cell . . 112.5 Known Bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.5.1 Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.5.1.1 [4622] Same user can open two instances in different ma-

chines and have access to all tasks in database . . . . . . . . 122.5.1.2 [5710] Out of Memory Exception when dragging fields in

OLAP "Specific Adjacency Report" . . . . . . . . . . . . . . 12

3 Contact Information 13

Optimi Corporation c2009 3

1 Introduction

1 Introduction

Optimi is pleased to release the 5.6 version of our xParameters product. This release featuressupport of ZTE 2G and Alcatel 2G infrastructure. Also, new functionality has been added to au-tomatically implement parameter change scripts and provide implementation information to theuser. This functionality is made available in a new module called Implementation Server, cur-rently supporting Nokia 3G OSS. Finally, significant performance and scalability improvementshave been done on Optimi Data Gateway. .

Please contact mailto:[email protected] for assistance regarding licensing of Op-timi applications.

Optimi appreciates your continued involvement in the evolution of our products, so continueto submit feature requests and any other concerns to http://www.optimi.com.

The document is divided into five formal categories:

Core Functionality: major new features, not related to optimization.

Optimization Functionality: major new features, related to optimization.

Improvements: on existing features, related to accuracy, usability or stability.

Bug fixes from previous releases. Bugfixes include the internal issue tracking ID, as wellas the Visual Intercept ID where available.

Known issues.


mailto:[email protected]: //www.optimi.com

2 Release 5.6

2 Release 5.6

2.1 Core Functionality

2.1.1 Implementation Server

Description: The Implementation Server integrates with Optimi applications to schedule andimplement parameter change files in the OSS system. The parameter change scripts are pro-duced by Optimi applications, and sent to the Implementation Server for activation in the net-work; the status of the activation is provided, parameter change scripts for implementation,implementation successful or with errors. Activation logs are made available.

Figure 2.1: Implementation Server

Vendors and Interfaces: Nokia OSS 5.1.Affected modules: The Implementation Server is a new application. Optimi products making

use of the Implementation Server need be updated (via extension installer).User inputs: Credentials in the OSS (administrative settings), attributes for the implementa-

tion tasks scheduling (implementation time).User outputs: Implementation task status (pending, finished with success or finished with

errors), implementation logs.External requirements: Access to OSS with appropriate credentials.


2 Release 5.6

2.2 Optimization Functionality

2.2.1 Huawei 3G RAN11 Support

xParameters and Optimi Data Gateway 5.6 support Huawei 3G RAN11. Vendor release transi-tion and RNC release mix are seamlessly supported (no user intervention needed).

Affected modules: Optimi Data Gateway, optimization..User inputs: No new inputs.User outputs: No new inputs.External requirements: N/A.

2.2.2 Ericsson 3G P7 Support

xParameters and Optimi Data Gateway 5.6 support Ericsson 3G P7. Vendor release transitionand RNC release mix are seamlessly supported (no user intervention needed).

Affected modules: Optimi Data Gateway, optimization..User inputs: No new inputs.User outputs: No new inputs.External requirements: N/A.

2.2.3 Alcatel 2G Optimization

Description: Alcatel 2G infrastructure optimization is supported.Affected modules: Optimi Data Gateway, templates, optimization, parameter change gener-

ation, GIS, OLAP, licensing.User inputs: Interface are NICS exports for CM, ASCII PM for MFS and types 110 and 180,

and binary PM for type 31.User outputs: MML.External requirements: N/A.

2.2.4 ZTE 2G Optimization

Description: ZTE 2G infrastructure optimization is supported.Affected modules: Optimi Data Gateway, templates, optimization, parameter change gener-

ation, GIS, OLAP, licensing.User inputs: Interface are csv CM dumps and SQL access to minos_pm databases.User outputs: csv files.External requirements: N/A.

2.2.5 Neighbor List and Scrambling Code Optimization for Huawei 3G (optional)

Description: Regular 3G optimization in enhanced by adding 3G intrafrequency neighbor list(NL Opt) and Scrambling Code optimization. This ensures changes in CPICH power and E-tiltmeet the adequate NL and SC planning in the network to ensure optimum optimization results.


2 Release 5.6

.

Warning

This functionality is optional and requires a special license.

Affected modules: Optimi Data Gateway, templates, optimization, parameter change genera-tion, GIS, OLAP, licensing.

User inputs: Additional settings in templates: new setting groups NL Optimization createdin Global and RNC levels.

User outputs: New OLAP reports. Scripts include neighbor relation adding and removal.External requirements: N/A.


2 Release 5.6

2.3 Improvements

Selected improvements in xParameters 5.6.

2.3.1 High

2.3.1.1 Optimi Data Gateway Scalability Improvements

Description: Internal refactorization and improvements have been carried out in several areas,yielding benefits in terms of the maximum network size that can be processed by Optimi DataGateway, especially for several file-oriented interfaces (Siemens 2G, Ericsson 3G, etc.); the limitin terms of network size is pushed to the 10,000 cell limit thanks to this.

Caution

This enhancement requires updating SQL to 5.6.

Affected modules: Optimi Data Gateway.User inputs: N/A.User outputs: N/A.External requirements: N/A.

2.3.1.2 Project Backward Compatibility

Description: xParameters 5.6 can open and utilize existing 5.5 projects. Opening a 5.5 projectfrom xParameters 5.6 will automatically upgrade the project to 5.6 format.

Caution

Upgrading a 5.5 deployment to 5.6 affects Optimi Data Gateway and xParameters; SQLmust not be updated, since this deletes existing projects.The Optimi Data Gateway database is not automatically upgraded. Therefore, the firstOptimi Data Gateway execution after upgrading to 5.6 needs be run with CM history sizeset to zero.

Affected modules: Core.User inputs: N/A.User outputs: N/A.External requirements: N/A.

2.3.1.3 [5141] GIS Views Refactoring: Complete CM Views for all supported vendors

Affected modules: GIS.Effect: For all supported vendors, for each optimized parameter, the original and optimized

values are shown, together with the variation (optimized minus original).


2 Release 5.6

2.3.1.4 Optimi Data Gateway Audit

Affected modules: xParameters.Effect: Optimization executions produce, in the reports folder of the corresponding optimiza-

tion task, a folder operdbAudit, which contains the following files:

requiredParameters: List of required parameters.

requiredCounters: List of required counters.

missingParameters: List of parameters not found in the Optimi Data Gateway database.

missingParameters: List of counters not found in the Optimi Data Gateway database.

For each entry, it is indicated if the information item is mandatory or not.

2.3.2 Medium

2.3.2.1 [5064, 5624] Size Increase in Application logs

Affected modules: Optimi Data Gateway, xParameters.Effect: Optimi Data Gateway can store up to 10X20MB in log information. xParameters can

store up to 10X80MB in log information.

2.3.2.2 [5172] Message Log Improvements

Affected modules: Optimi Data Gateway, xParameters.Effect: Improvements:

Summary of duplicated/incorrect sector names in sector location.

2.3.2.3 [5575][48699] Error in execution if RNC has no defined adjacencies

Affected modules: xParameters Nokia 3G.Effect: Error fixed in optimization when RNC has no defined adjacencies.

2.3.2.4 [5396][48641] Consistency rule added: nhs_min

2 Release 5.6

2.4 Bugfixes

Selected bugfixes in xParameters 5.6.

2.4.1 Critical

No critical bugfixes in xParameters 5.6.

2.4.2 High

2.4.2.1 [5356, 5036][48616] Project sector location data update

Affected modules: Optimi Data Gateway.Effect: Updating sector location (new import) updates existing projects.

2.4.2.2 [5317] Exception when opening xParameters in a machine where xNetManageris installed

Affected modules: xNetManager.Effect: Exception does not happen anymore.

2.4.2.3 [5504][48680] Duplicated task output folders

Affected modules: xParameters.Effect: When GUI was closed abnormally, not all application processes were duly closed.

These cause duplicated task output folders.

2.4.2.4 [5433] FMCS Loading Error

Affected modules: xParameters (Nokia 3G)Effect: An incorrect XML script was being generated in FMCS object creation (duplicated

FMCS-0).

2.4.3 Medium

2.4.3.1 [5295] Correction in calculation of GPRS TSLs

Affected modules: xParameters (Siemens 2G).Effect: Modifications in calculation of GPRS TSLs:

A TRX will not be considered if GEXTS = 0 and the TRX band is DCS.

TSL 0 not to be considered if HOPP=TRUE && HOPMODE=BBHOP


2 Release 5.6

2.4.3.2 [5564] Inconsistent CM (LAR)

Affected modules: xParameters (Nokia 2G).Effect: Cells are not unduly discarded when optional feature non BCCH layer access is not

activated in the OSS.

2.4.3.3 [5607][48703] Project cannot be edited if BSC removed due to unavailable CM

Affected modules: xParameters (Siemens 2G).Effect: Bug caused project to be non editable after a BSC had been removed due to unavail-

able CM (when CM is unavailable, the corresponding node is automatically removed).

2.4.3.4 [5301] Fix in format for ADJG identification of target cell

Affected modules: xParameters (Nokia 3G).Effect: Syntax changed in XML related to ADJG object, for the 3G/2G traffic steering feature.

This caused the ADJG changes not being successful.


2 Release 5.6

2.5 Known Bugs

Selected known bugs in xParameters 5.6.

2.5.1 Medium

2.5.1.1 [4622] Same user can open two instances in different machines and haveaccess to all tasks in database

Affected modules: xParameters.Effect: If a user logs in 2 different machines, both logins will see the same tasks in the

scheduler.

2.5.1.2 [5710] Out of Memory Exception when dragging fields in OLAP "SpecificAdjacency Report"

Affected modules: xParameters, OLAP reports.Effect: Any Change in the layout of the table freezes the application for some minutes and at

the end I get Popup Window with Memory exception.


3 Contact Information

3 Contact Information

If you have any questions, comments or suggestions, we would like to hear from you:

Optimi General Support email: [email protected]

Support Live Chat: http://messenger.providesupport.com/messenger/optimi.html

Optimi Web: http://www.optimi.com

Copyright (c) 2009 Optimi Corporation. All rights reserved.


[email protected]://messenger.providesupport.com/messenger/optimi.htmlhttp://messenger.providesupport.com/messenger/optimi.htmlhttp://www.optimi.com

Contents1 Introduction2 Release 5.62.1 Core Functionality2.1.1 Implementation Server

2.2 Optimization Functionality2.2.1 Huawei 3G RAN11 Support2.2.2 Ericsson 3G P7 Support2.2.3 Alcatel 2G Optimization2.2.4 ZTE 2G Optimization2.2.5 Neighbor List and Scrambling Code Optimization for Huawei 3G (optional)

2.3 Improvements2.3.1 High2.3.1.1 Optimi Data Gateway Scalability Improvements2.3.1.2 Project Backward Compatibility2.3.1.3 [5141] GIS Views Refactoring: Complete CM Views for all supported vendors2.3.1.4 Optimi Data Gateway Audit

2.3.2 Medium2.3.2.1 [5064, 5624] Size Increase in Application logs2.3.2.2 [5172] Message Log Improvements2.3.2.3 [5575][48699] Error in execution if RNC has no defined adjacencies2.3.2.4 [5396][48641] Consistency rule added: nhs_min

Documents

XParameters 5.6 Release Notes