1/19 3DF 01955 0084 TQZZA Ed.

03







9955 RNP
RMS V2.3
Release Notes
2/19 3DF 01955 0084 TQZZA Ed. 03
Status Released
Change Note No
Short Title RMS V2.3 Release Notes
All rights reserved. Passing on and copying of this document, use and
communication of its contents not permitted without written authorization
from ALCATEL-LUCENT

Table of Contents
3/19 3DF 01955 0084 TQZZA Ed. 03

Table of Contents


9955 RNP ..................................................................................................................................1
Table of Contents.......................................................................................................................3
PREFACE....................................................................................................................................5
1 RMS V2.3 OVERVIEW...........................................................................................................6
2 BUG FIXES SOLVED ERRORS...............................................................................................6
2.1 RMS Dummy Neighbors Management ...................................................................................... 7
2.1.1 Dummy neighbors module not counting once duplicate BCCHs ...................................................................... 7
2.1.2 Dummy cycles export concatenates channel number to neighbor name ........................................................ 7
2.2 RMS Interference Matrix Management..................................................................................... 8
2.2.1 Problem while reading PMRES files .................................................................................................................. 8
2.2.2 T180 binary files for BSS release B11 are not read correctly ............................................................................ 8
3 CHANGES AND NEW FEATURES............................................................................................8
3.1 RMS Interference Matrix management..................................................................................... 9
3.1.1 Filtering based on distance and C factor.................................................................................................... 9
3.1.2 RMS files for B11........................................................................................................................................ 9
3.1.3 RMS multivendor solution....................................................................................................................... 10
3.1.4 RMS matrix format extension.................................................................................................................. 10
3.2 RMS Neighbors Management................................................................................................. 11
3.2.1 Decrease time needed for the running several scenarios in RMS Module.............................................. 11
3.2.2 Using T180 IM as an input instead of T180 Binary files in all the relevant RMS modules ....................... 11
3.2.3 Using RMS IM as an input instead of RMS Binary files in Neighbor Cleanup........................................... 12
4 KNOWN PROBLEMS AND ERRORS...................................................................................... 12
4.1 RMS Neighbors Management................................................................................................. 13
4.1.1 Missing LAC CI in atl causes error in RMS neighbor addition .................................................................. 13
4.1.2 Warning during importing the RMS IM to the Missing Neighbors detection module............................. 13
4.2 RMS Interference Matrix Management................................................................................... 14
4.2.1 BCS_NBR field inconsistency.................................................................................................................... 14
4.2.2 Import other files than .rms, .t180 and .clc ............................................................................................. 14
4.2.3 OK button active with other errors.......................................................................................................... 14
4.3 RMS Neighbors Management................................................................................................. 15
4.3.1 Filtering options activation problem in rank neighbors........................................................................... 15
5 ERROR GRAVITY ................................................................................................................ 16
6 SUPPORT........................................................................................................................... 17
7 ABBREVIATIONS ................................................................................................................ 18

PREFACE

5/19 3DF 01955 0084 TQZZA Ed. 03
PREFACE






This document is aimed to all users of 9955 RNP V7.1.0 RMS
2.3.

This document describes the changes (bug fixes, design
change, new features) to the previous version and major known
errors in Alcatel-Lucent 9955 Radio Network Planning tool
V7.1.0 RMS Module V2.3.

















Title Reference Number
[1] 9955 V7.1.0 User Manual 3DF 01955 7180 RJZZA
[2] 9955 V7.1.0 Installation Guide 3DF019557181RJZZA
[3] 9955 Application note: RMS and T180 Module 3DF 01955 6023 BGZZA
[4] 9955 V6.9.1 Application Note: AFP 3DF 01955 6022 BGZZA
[5] RMS multivendor solution specification 3DF 01955 2014 VAZZA
[6] OMC/BSC PM File Format Specification - Release B11 3BK 11204 0446 DSZZA

Table 1: Reference Documents





Scope
Readership Profile
Contents Summary

Restrictions
Remarks
Last Minute Changes
Pre-conditions for
use
Reference
Documents
RMS V2.3 OVERVIEW
6/19 3DF 01955 0084 TQZZA Ed. 03





1 RMS V2.3 OVERVIEW



The RMS V2.3 Release Notes includes bug fixes (chapter2),
several changes and new features (chapter3) but also some
known problems (chapter4).
For details about how to use the features of RMS V 2.3 with
9955 RNP V7.1.0, please refer to the 9955 Application note: RMS
and T180 Module [1] and the online help inside 9955.
For details about GSM/EGPRS frequency planning with the 9955
RNP AFP module (current version 2.3), please refer to the
corresponding Application Note [4].




2 BUG FIXES SOLVED ERRORS
This chapter lists most important problems that appeared in
RMS V2.2 and are now solved in release V2.3. For a better
overview, the entries have been grouped into the following
categories:
RMS Interference Matrix management
RMS Dummy Neighbors management
RMS Neighbors management

If one of the above sections doesnt exist in this chapter, it
means that there are no bug fixes, bigger than G3 on that
specific functionality.




BUG FIXES SOLVED ERRORS

7/19 3DF 01955 0084 TQZZA Ed. 03
2.1 RMS Dummy Neighbors Management

2.1.1 Dummy neighbors module not counting once duplicate BCCHs


Dedicated scenario on Dummy neighbors module does not
count once the duplicate BCCHs of existing neighbors.

MJD-323592
G2

Merge manually two dummy cycle results in a single atl file.

V2.2.1.51

To be corrected in future versions

No
Yes


2.1.2 Dummy cycles export concatenates channel number to neighbor
name


When using the Export Cycles from the RMS Dummy
management add-in the name of the neighbor is truncated.
The BCCH channel of the neighbor is concatenated to its
name.

VYQ-918861
G3

V2.3.0.25

No


Error
Reference
Gravity
Workaround
Reported
Planned
Regression
Restriction
Error
Reference
Gravity
Reported
Regression
CHANGES AND NEW FEATURES
8/19 3DF 01955 0084 TQZZA Ed. 03
2.2 RMS Interference Matrix Management
2.2.1 Problem while reading PMRES files


When PMRES (RMS measurement files) extension is higher
than 256 the IM generated has no interferes.

OTU-169052
G1

V2.3.0.25

No
Yes

2.2.2 T180 binary files for BSS release B11 are not read correctly

When trying to import T180 in order to compute IM, there its
giving a warning message and this message continues to
repeat. Result is that there is no T180 IM.

RBK-871786
G3

V2.3.0.25

No
Yes



3 CHANGES AND NEW FEATURES

This chapter lists the Changes of release 9955 RNP RMS V2.3.
For a better overview, the entries have been grouped into the
following categories:
RMS Interference Matrix management
RMS Dummy Neighbors management
Error
Reference
Gravity
Reported
Regression
Restriction
Error
Reference
Gravity
Reported
Regression
Restriction
CHANGES AND NEW FEATURES

9/19 3DF 01955 0084 TQZZA Ed. 03
RMS Neighbors management

If one of the above sections doesnt exist in this chapter, it
means that there are no bug fixes on that specific
functionality.
3.1 RMS Interference Matrix management
3.1.1 Filtering based on distance and C factor

New option needed in the RMS IM creation module, called filtering
based on distance & C factor:
If enabled this option (default = FALSE disabled) it is possible to
filter out some entries in the RMS:
If the distance between the victim and interferer is > Distance Factor
1 * average (distance of cell neighbors, excluding co-site).
Or if the distance between the victim & interferer is > Distance
Factor 2 * average (distance of cell neighbors, excluding co-site) & C
factor (azimuth factor) is < 0.15 (default vAlcatel-Lucente).
Distance Factor 1 = 8 (default)
Distance Factor 2 = 5 (default)

There are some strange BCCH-BSIC mappings (happens during Cell
Identification) where very distant cells show high level of
interference (makes no sense) and thus putting more constraints on
the AFP without real need to avoid Co- or Adjacent- channels and
thus leading to decreasing the quality of the FP.
This behavior is already less severe when use PIM in cell.
identification but as PIM is sometimes very bad, the user will have to
use the old method, so the user may enhance the quality of the RMS
IM with this new option.

VFZ-554077


3.1.2 RMS files for B11

RMS file format is changed in B11MR1Ed2. The RMS modules (all that
reads T180 and RMS) have to be adjusted from B11MR1Ed2 to the new
format of binary files. RMS file format has been changed while for T180
still has to be checked. The new formats are found [6].

UMU-622836
Description
Reason
Reference
Description
Reference
CHANGES AND NEW FEATURES
10/19 3DF 01955 0084 TQZZA Ed. 03

3.1.3 RMS multivendor solution

The RMS module is able to handle multi-vendor solution, meaning it is
able to extract from a specific format the same matrix output as for the
Alcatel-Lucent solution. This format is given by Aircom (which acts as an
interface between ALCATEL-LUCENT and other vendors and adapts the
other vendors output to a certain format that is acceptable by ALCATEL-
LUCENT RMS module). More details about the specific functionality can
be found in [5]

OMZ-665205

3.1.4 RMS matrix format extension

This feature consists in adding an extra column in the RMS IM for
percentage of samples in the C/I vector situated in the negative C/I
intervals: [-63,-12], [-12,-9], [-9,-6], [-6,-3] & [-3, 0] with respect to all
the samples in the vector.

YAV-909913

Description
Reference
Description
Reference
CHANGES AND NEW FEATURES

11/19 3DF 01955 0084 TQZZA Ed. 03
3.2 RMS Neighbors Management
3.2.1 Decrease time needed for the running several scenarios in
RMS Module

In the modules implementation the RMS IM & T180 Binary files are
imported while selecting the RMS and T180 SON settings, i.e. if the
user wants to change RMS or T180 settings, the user will have to wait
till the module load the RMS and T180 inputs from the beginning.
Because in missing neighbors detection the user has to run
several scenarios to get the best output and in order to save the users
time:
The user can import the RMS & T180 inputs at the very
beginning and later can specify the RMS and T180 settings. The module
will have to remember the RMS and T180 inputs as long as the ATL is
open; i.e. the user can run a scenario, close the module to view the
output, open it again to modify some thresholds. When the module
opens, it will ask the user if he/she wants to use the same RMS & T180
inputs previously imported.

The main point is that in real projects; normally have only 1
RMS input and 1 T180 input, so it is somehow time consuming to keep
importing the same data over and over again. It is better to import
them once and apply the options afterwards. In fact this is a general
request; the users want to apply the in Neighbors Clean-up, Neighbors
Ranking.


GQX-682208

3.2.2 Using T180 IM as an input instead of T180 Binary files in all
the relevant RMS modules

Using T180 IM as an input instead of T180 Binary files in all the
relevant RMS modules, because as per a previously implemented
feature, we have both HO_Request nb and HO_Request % nb.
Neighbors Clean-up and Neighbors Ranking can directly access
all the data without computing it from the beginning.
Missing neighbors detection module can read the HO_Request
to compute the SON Proximity factor.
Description
Reason
Reference
Description
KNOWN PROBLEMS AND ERRORS
12/19 3DF 01955 0084 TQZZA Ed. 03

The user will compute the T180 IM once when all the cells are
present in the ATL and use it normally afterwards even if some cells
were removed.

IQX-525007


3.2.3 Using RMS IM as an input instead of RMS Binary files in
Neighbor Cleanup

As feature YAV-909913 was implemented, it is also possible to use the
RMS matrix in Neighbor Cleanup, instead of the binary files.
This includes also the possibility to use a previously loaded RMS matrix,
request of feature GQX-682208.

URO-437019












4 KNOWN PROBLEMS AND ERRORS


This chapter lists the most important problems that are known
in RMS V2.3. Problems include knows errors, that may include
restrictions. For a better overview, the entries have been
grouped into the following categories:
RMS Interference Matrix management
RMS Dummy Neighbors management
RMS Neighbors management

Reason
Reference
Description
Reference
KNOWN PROBLEMS AND ERRORS

13/19 3DF 01955 0084 TQZZA Ed. 03
If one of the above sections doesnt exist in this chapter, it
means that there are no problems on that specific
functionality.


4.1 RMS Neighbors Management
4.1.1 Missing LAC CI in atl causes error in RMS neighbor addition

When the LAC and CI information is missing for some
transmitters, the Missing Neighbors Detection module throws
an error message at committing results step: Unable to write
detected neighbors in Neighbors table: Object reference not
set to an instance of an object. As a consequence of this, the
committing results stops before all detected neighbors are
saved in the Neighbors table.
Provide the LAC and CI information for all transmitters before
starting the missing neighbors detection. Normally this should
always be the case as this information is fulfilled during CAE
import which is a prerequisite.
EJC-293316
G3
Yes
RMS V2.3.0.25
Under study for future releases
No


4.1.2 Warning during importing the RMS IM to the Missing
Neighbors detection module

Date and time format warning on importing a RMS matrix in
Missing neighbors detection module.
GPU-433710
G3
Yes
RMS V2.2.1.39
Under study for future releases
No
Error
Workaround
Reference
Gravity
Systematic
Reported
Planned
Regression
Error
Reference
Gravity
Systematic
Reported
Planned
Regression
KNOWN PROBLEMS AND ERRORS
14/19 3DF 01955 0084 TQZZA Ed. 03

4.2 RMS Interference Matrix Management
4.2.1 BCS_NBR field inconsistency

The BSC_NBR field contains a string instead of number but
BTS_IDX, BTS_SECTOR_ID and OMC_NAME fields are empty
there is no error when loading the data in RMS IM addin. There
are just warnings that all these fields are empty and they will
be considered as 0.
If I fill in the BTS_IDX, BTS_SECTOR_ID and OMC_NAME fields
with correct Alcatel-Lucents (from the format point of view),
then I get an error: "Input string in wrong format". If I replace
string in BSC_NBR with numbers the error disappears.
HUM-726327
G3
Yes
RMS V2.3.0.16
V2.4
No

4.2.2 Import other files than .rms, .t180 and .clc

All types of files can be imported using IM Management addin
from RMS
GRI-354695
G3
Yes
RMS V2.3
Under study for future releases
No

4.2.3 OK button active with other errors

OK button from OMC measurements can be pressed even when
having errors on the page.
UGW-717267
G4
Yes
RMS V2.3
Under study for future releases
Error
Reference
Gravity
Systematic
Reported
Planned
Regression
Error
Reference
Gravity
Systematic
Reported
Planned
Regression
Error
Reference
Gravity
Systematic
Reported
Planned
KNOWN PROBLEMS AND ERRORS

15/19 3DF 01955 0084 TQZZA Ed. 03
No

4.3 RMS Neighbors Management
4.3.1 Filtering options activation problem in rank neighbors

Filtering options status doesn't refresh on Back pressed. If
selecting one method of filtering in rank neighbors module,
then pressing next until the percentage of neighbors appears,
then go back to the filtering options (Overlap or Distance)
selecting the other option than the one selected before, then
pressing next, no options are available, the whole page is
greyed out. Workaround is to press back then next again.
VUY-846223
G3
Yes
RMS V2.2.1.39
V2.4
No
Regression
Error
Reference
Gravity
Systematic
Reported
Planned
Regression
ERROR GRAVITY
16/19 3DF 01955 0084 TQZZA Ed. 03

5 ERROR GRAVITY
In case that error occurs during the acceptance test, they have
to be noted in detail. The gravity (severity) of the error is rated
from G0 (critical) to G4 (cosmetic) according to the following
definition:
Table 1: Error Gravities
G0 critical
Critical error which completely blocks the
usage of the product
G1 major
Major fault which has a significant impact on
the commercial use or a key function of the
product
G2 workaround
Partial or full operation of a key function is
possible only by using a temporary solution
G3 minor
Minor fault which does not unduly impact the
normal operation
G4 cosmetic
Minor fault which has no consequence on the
product or its use, but would improve the
image of the product

9955 RNP is constantly being improved, and it is possible that
the test descriptions in this document don't match exactly the
handling of the tool under test. These tests must not be
considered as failed, if the required user actions are intuitively
clear.




















SUPPORT

17/19 3DF 01955 0084 TQZZA Ed. 03
6 SUPPORT

This document has been set up by the 9955 RNP support team
of Alcatel-Lucent with much care. If there are still problems,
and you fail to solve them by carefully reading the manuals,
don't hesitate to contact the 9955 RNP Support:
Tel: +40 256 303 135
Fax: +40 256 250 316
Mail: RadioTools.Support@alcatel-lucent.com

Telephone support is provided from 09:00 to 18:00 Romanian
time on Romanian business days.
When contacting us via e-mail, which is the preferred method,
please help us helping you by being as specific as possible.
The hotlines email address is RadioTools.Support@alcatel-
lucent.com.
Also you can find below the web address which can be access
by the users.
http://pcs-toolscenter.tm.alcatel.ro/support/
Any feedback is appreciated. For comments, bug-reports,
feature proposals or any related question, don't hesitate to
contact us.























There is support
Telephone
E-mail address
Give your feedback
ABBREVIATIONS
18/19 3DF 01955 0084 TQZZA Ed. 03












7 ABBREVIATIONS


9955 Alcatel-Lucents Radio Network Planning tool
AFP Automatic Frequency Planning
BCCH Broadcast Control Channel
BSS Base Station System
CDMA Carrier Division Multiplex Access
CGI Common Gateway Interface
C/(I+N) Carrier over Interference and Noise
COF CMA Offsite
CSV Comma Separated VAlcatel-Lucentes
DFH Discrete Frequency Hopping
DL Downlink
EDGE Enhanced Data-rates for GSM or Global Evolution
EPO Error Performance Objectives
FP Frequency Planning
GSM Global System for Mobile communication
GPRS General Packet Radio Service
HARQ Hybrid Automatic Repeat Request
HO Handover
HSDPA High Speed Downlink Packet Access
HSPA High Speed Packet Access
HSUPA High Speed Uplink Packet Access
LTE Long Term Evolution
MIMO Multiple Input Multiple Output
OMC-R Operation & Maintenance Centre - Radio
PI Performance Indicator
PRC Provisioning Radio Configuration
RMS Radio Measurement System
RNP Radio Network Planning tool

ABBREVIATIONS

19/19 3DF 01955 0084 TQZZA Ed. 03

RNP2OMC Import/Export configuration to/from WiMAX, W-CDMA or LTE
OMC
TD-SCDMA Time Division- Synchronous CDMA
TRX Transceiver
UL Uplink
UMTS Universal Mobile Telecommunication System
XML Extensible Markup Language
WiMAX Worldwide Interoperability for Microwave Access

END OF DOCUMENT