SDCCH congestion

Abnormal SDCCH traffic Too much SDCCH tr

Check if the SDCCH congestion is not coming from abnormal SDCCH traffi Check if congestion
Check if the load of the cell in term SDCCH traffic (SDCCH_load_BH) is less Test if the load (SDC
than 80%. traffic is greater than

Spurious RACH due to wrong Channel Re

Check if 2 adjacent cells do not have a clo
Spurious RACH due to adjacent handover (BCCH,BSIC) couple.
Check if 2 adjacent cells do not have a close
(BCCH,BSIC) couple.

Spurious RACH due to noise decoding

Check if Spurious RACH might come from noise
decoding.
Check the rate of SDCCH assignment failure due to
radio problem during the night
ACTION: Check on Abis interface if the CHANNEL
REQUEST messages have a random distribution of
Timing Advance
estion

SDCCH always busy

Too much SDCCH traffic Check if SDCCH channels are always busy.
Check if congestion is coming from normal SDCCH traffic. Check if SDCCH duration average
Test if the load (SDCCH_load_BH) of the cell in term of SDCCH (SDCCH_duration_avg/TRX) is greater than 10
traffic is greater than 100% seconds.
Try to reinitialize active CPRA for BSC G1 and
TCHRM for BSC G2.

RACH due to wrong Channel Request:

2 adjacent cells do not have a close
SIC) couple.

Signalisation ratio too high

The ratio of signalisation is too high compared to the TCH
traffic.
Test if ratio SDCCH success (SDCCH_assign_success)
over TCH success (RTCH_assign_success) is greater than
5.

SDCCH channel configuration

Check if the number of SDCCH channels is Bad settings of LU parameters
correctly dimensioned. Check if parameters for triggering Location Up
Check the rules on SDCCH channel configuration according to reference values
according to the number of TRXs Check if timers T3101, T3111 and parameter C
ACTION: are out of recommended range
Reconfigure your number of SDCCH channels.
ACTION:If Location Update traffic is too high a
by logical parameter tuning, identify cell couple
with biggest number of handove

Problem of incorrect T3101 .Problem of incorrect T3111

Check if timer T3101 has a correct value. Check if timer T3111 has correct value.
Check if timer T3101 is out of recommended range Check if timers T3111 is out of recommended
[Pop < Pmin or Pop > Pmax] range
ACTION:Correct the value of timer T3111.
ACTION:Correct the value of timer T3101.
Problem of incorrect T3101 .Problem of incorrect T3111
Check if timer T3101 has a correct value. Check if timer T3111 has correct value.
Check if timer T3101 is out of recommended range Check if timers T3111 is out of recommended
[Pop < Pmin or Pop > Pmax] range
ACTION:Correct the value of timer T3111.
ACTION:Correct the value of timer T3101.
sy Loss of SDCCH resources:
hannels are always busy. Check if radio SDCCH resources are missing.
uration average Check if the number of SDCCH time slots unavailable
avg/TRX) is greater than 10 is greater than 0.

tive CPRA for BSC G1 and Try to reinitialize SBL RTS. If not working, reconfigure
2. SDCCH from CHANNELS menu

Inadequate LA design
Check the ratio of Location Update on the cell.

Check if the ratio of Location Update compare to Mobile

Originating Traffic is higher than 80%

ACTION: Redesign your LA in order to decrease Location

Update on your cel

f LU parameters
meters for triggering Location Update are correct
eference values
s T3101, T3111 and parameter CELL_RESELECTHYST
ommended range

cation Update traffic is too high and can not be decrease

ameter tuning, identify cell couples in different LAC and
umber of handove

ncorrect T3111 .Problem of incorrect CELL_RESELECTHYST

r T3111 has correct value. Test if parameter CELL_RESELECTHYST is
rs T3111 is out of recommended correct
Test if parameter CELL_RESELECTHYST is out of
rect the value of timer T3111. recommended range
Correct the value of parameter
CELL_RESELECTHYST. Increase the value up to
10 (or even more) on the cell facing SDCCH
congestion and also on its neighbor cells with
different LAC
ncorrect T3111 .Problem of incorrect CELL_RESELECTHYST
r T3111 has correct value. Test if parameter CELL_RESELECTHYST is
rs T3111 is out of recommended correct
Test if parameter CELL_RESELECTHYST is out of
rect the value of timer T3111. recommended range
Correct the value of parameter
CELL_RESELECTHYST. Increase the value up to
10 (or even more) on the cell facing SDCCH
congestion and also on its neighbor cells with
different LAC
 Check if SDCCH access problem is coming from a
radio problem.
Test if the ratio of SDCCH access problem due to
radio problem is higher than 40%:
SDCCH_assign_fail_radio_ratio>0.4

Check if Spurious RACH might come from noise decoding:

Check the rate of SDCCH assignment failure due to radio problem
during the night (if this is the case, might be due to noise
decoding)
Action: Check on Abis interface if the CHANNEL REQUEST
messages have a random distribution of Timing Advance

Spurious RACH due to wrong Channel Request

Check close BCCH BSIC couple:

Check adjacent cells having same BSIC and BCCH
frequencies equal or adjacent:
Action: Modify the (BCCH,BSIC) couple from one of
the cells.
Check close BCCH BSIC couple:
Check adjacent cells having same BSIC and BCCH
frequencies equal or adjacent:
Action: Modify the (BCCH,BSIC) couple from one of
the cells.
 SDCCH_assign_fail_rate

SDCCH system access

Check if SDCCH access problem is coming from a Check if SDCCH access
radio problem. problem.
Test if the ratio of SDCCH access problem due to Test if the ratio of SDCC
radio problem is higher than 40%: problem is (SDCCH_ass
SDCCH_assign_fail_radio_ratio>0.4

e from noise decoding:

nt failure due to radio problem
might be due to noise Spurious RACH due to adjacent handover

e CHANNEL REQUEST
n of Timing Advance

Interfered cell:
Check if the cell seems to be interfered thus has
Spurious RACH due to wrong Channel Request high rate of handover on quality

Adjacent cell (Freq, BCC):

Give the cells who have a (Freq, BSIC) couple
SIC and BCCH identical to (BCCH, BCC) couple of congested cell
Action:Perform an Abis measurement on cell $c to
ple from one of check if CHANNEL REQUIRED messages with
identical reference and subsequent frame number are
present. In that case, change the BSIC of cell $c or
$nc
 Adjacent cell (Freq, BCC):
Give the cells who have a (Freq, BSIC) couple
SIC and BCCH identical to (BCCH, BCC) couple of congested cell
Action:Perform an Abis measurement on cell $c to
ple from one of check if CHANNEL REQUIRED messages with
identical reference and subsequent frame number are
present. In that case, change the BSIC of cell $c or
$nc
te

SDCCH system access problem:

Check if SDCCH access problem is coming from a system
problem.
Test if the ratio of SDCCH access problem due to system
problem is (SDCCH_assign_fail_BSS_ratio) higher than 20%

l seems to be interfered thus has a

ndover on quality Unbalanced Power Budget:
Check the Power Budget between uplink and
downlink is balanced.

Check if the difference between UL and DL handovers

on level compare to the total number of handover on
level is greater than the 40%
Or
Use RMS

Action:Check your theoritical Power Budget or your

aerials.
 Coverage problem:
plink and Check if there is a potential problem of coverage
hole on the cell.
Check if the rate of handovers on level
and DL handovers (CHO_level_rate)is greater than 40% with a
of handover on handover reversion rate
(HO_Out_2G_2G_ROC_rate) less than 3%
Or
Use RMS
Action:
Budget or your Confirm with coverage map the potential coverage
hole.
 SDCCH drop

SDCCH drop HO
Check if SDCCH dropped are coming from a SDCCH drop radio
handover problem. Check if SDCCH dropped are coming from a
Test if SDCCH dropped due to handover radio problem.
problem (SDCCH_drop_HO_ratio)represent Test if SDCCH dropped due to radio problem
more than 40% of all SDCCH dropped (SDCCH_drop_radio_ratio) represent more than
40% of all SDCCH dropped

TCH HO problem SDCCH HO not activated

Check if there is also TCH call drop coming from a Check if handovers on SDCCH are
handover problem. activated.Test if handovers on SDCCH are
Test if call drop rate due to handover problem DISABLE.
(Call_drop_HO_rate) is higher than 3%. Activate handover on SDCCH and check
Action:A correlation may be made between the 2 for improvement. Reduce averaging
problems, you should run a RNO diagnosis on TCH window if necessary
call drop for cell

Standalone SDCCH HO problem

Check if there is no TCH call drop coming from a handover

problem.

Action:Try to move SDCCH channels to a cleaner TRX-TS

or disable handovers on SDCCH and check the impact on
global SDCCH drop and particularly on SDCCH drop radio
 SDCCH drop

adio
H dropped are coming from a SDCCH drop system
Check if SDCCH dropped are
dropped due to radio problem coming from a system problem.
_radio_ratio) represent more than Test if SDCCH dropped due to
CH dropped system problem represent more than
40% of all SDCCH dropped

tivated TCH radio problem

s on SDCCH are Check if there is also TCH call drop coming from
ndovers on SDCCH are a radio (Call_drop_radio_rate) problem.
Test if call drop rate due to radio problem is
on SDCCH and check higher than 3%.
Reduce averaging A correlation may be made between the 2
ry problems, you should run a RNO diagnosis on
TCH call drop for cell

BSS internal problem Link failure

Check if no LAPD, TCU and Check LAPD alarms cause "link
BTS/FU alarms are present. failures", "link re-establishment".
Action: Call Technical Support for Check on-site the transmission
level 3 investigation. settings and stability.
 system
CH dropped are
a system problem.
H dropped due to
m represent more than
CCH dropped

Processor restart
alarms cause "link Check TCU alarms or BTS/FU
k re-establishment". alarms cause "restart", "reset",
e the transmission "Access failure"
stability. Check causes of processor
alarms using additional
information field of each alarm
and call maintenance for
exchange of faulty boards if
problem is recurrent.
 GSM TCH congestion

1) 2) 3)
RTCH always busy FU blocked: Sleeping TRX Loss of TCH reso

1)
RTCH always busy 2)
FU blocked
Check if RTCH are always busy:
RTCH seizures very low with a Check if FUs are handling traffic.
normal RTCH occupancy
Test if the number of TRX with an
Test if ratio RTCH seizure success average duration
divided by RTCH assign request is (RTCH_duration_avg) of 0 second is
less than 5 % with RTCH occupancy greater than 0
greater than 20 seconds
ACTION: Reinitialize SBLs affecting
(RTCH_assign_success/RTCH_assig the FU (CU, FU, RTS).
n_request < 0.05) AND
(RTCH_duration_avg > 20);

ACTION:Try to reinitialize active

CPRA for BSC G1 and TCHRM for
BSC G2.

3)
Loss of TCH resources Check if Forced Direc
feature is activated.

Check if radio TCH resources are Check if parameter

missing. EN_FORCED_DR is
Check if the number of radio TCH
time slots unavailable is greater than Check the overlappin
cells and activate For
0 Retry.

ACTION:Try to reinitialize SBL RTS.

If not working, reconfigure TCH from
CHANNELS menu
Check if there has been 2 possibilities:
some O&M configuration  Drag and drop in QoS
change Notebook again for several
weeks including “yesterday”
the same Daily Mono QoS
Evolution report including
the
RTCH_assign_cong_max_r
ate indicator but select the
“Correlation with network
events” option after having
setup the Show event filter
 Drag and drop in
Spreadsheet the O&M
events of the cells for the
last 7 days

Check if the number of Drag and drop in Spreadsheet

available TCH is maximum for the last 7 days the QoS
indicator
RTCH_unavailable_nb_avg

Check if the TCH traffic Compare RTCH traffic evolution

increase is not due to TCH between the bad cells and its
traffic decrease in neighbors over the last 7 days
neighboring cells 2 possibilities:
 Execute Unhighlight all
objects in the map window,
Select the bad cell in the
Object window,
Drag and drop in the map,
Select the bad cell in the

map using or just

move the mouse over the
cell icon,
 Select the bad cell in the
Object window,
Drag and drop in the map,
Select the bad cell in the

map using or just

move the mouse over the
cell icon,
Execute Highlight target
cells in the map,
Execute Select highlighted
objects in the map,
Execute Propagate
selection,
Select the
RTCH_Erlang_BH indicator,
Drag and drop in the
spreadsheet by selecting
the last 7 days period of
time
 Select the bad cell in the
Object window,
Select the
RTCH_Erlang_BH indicator,
Drag and drop in the

button by selecting
the last 7 days period of
time

Check if some O&M Drag and drop in the

configuration change has spreadsheet the cell logical
been done on neighbor cells parameters
or on adjacencies CELL_BAR_ACCESS and
(ex: cell barring, CELL_BAR_QUALIFY
BS_TXPWR_MAX)

Thanks to RMS, check if 2 possibilities:

path balance of neighbor  Drag and drop the
BS_TXPWR_MAX)

Thanks to RMS, check if 2 possibilities:

path balance of neighbor  Drag and drop the
cells has become bad RMS_PathBalance_avg
indicator in the
Spreadsheet
 Drag and drop te
RMS_radio_link_detailed
report in the QoS
Notebook

Check if the some RTCH TS Impossible with RNO

are never busy

Check if the some RTCH Impossible with RNO

TS are always busy
Find a solution to a problem of TCH congestion which is “normal”, i.e. which is
demand compared to the cell capacity

trainer first recalls the different actions to be carried out if the TCH congestion i
too high subscriber traffic demand compared to the cell capacity. He writes them
If it is a system problem then BSS O&M team or BSS site engineering team ha
according to the output of the analysis:
o unbar neighbor cell
o restart BSC boards (CPRA, DTC, TCU) or BTS (SUM, TRX)
o disable and re-enable traffic on the bad cell
o replace HW components on BSC or BTS or Antenna systems
o modify radio configuration parameter

If it is a real traffic problem then BSS planning team has to add TRX capacity in
optimization team can improve the QoS before TRX extension by:
o Implementing Forced Directed Retry if not used
o Implementing Fast Traffic HO if not used
o Implementing Traffic HO if not used
o Implementing Half Rate if not used

But some risks have to be considered.

For Forced Directed Retry and Fast Traffic HO:

· FDR is a feature that can decrease RTCH congestion but that can degrade th
a conventional network (not hierarchical).
· FRD is a feature activated per cell towards any of its target neighbors. The on
and forbid FDR to others is to tune the FDR parameter of the target cell: L_RXL
forbids any FDR towards that cell. The drawback is that in this case no incomin
specific cell.
· QoS degradation will be limited if FDR is activated towards neighboring cells
with the serving cell in RTCH congestion
· The best neighboring cells are usually those to which the highest ratio of hand
more than 20% of the total number of outgoing handovers).

For Traffic HO:

· THO (HO cause 23) is a feature that can decrease RTCH congestion but that
meantime especially in a conventional network (not hierarchical). However the
because the mobile who will handed over to the neighbour cells are located at
the triggering condition is based on the PBGT value.
· Contrary to FDR, THO is a feature activated per adjacency. It is therefore pos
with the serving cell in RTCH congestion
· The best neighboring cells are usually those to which the highest ratio of hand
more than 20% of the total number of outgoing handovers).

For Traffic HO:

· THO (HO cause 23) is a feature that can decrease RTCH congestion but that
meantime especially in a conventional network (not hierarchical). However the
because the mobile who will handed over to the neighbour cells are located at
the triggering condition is based on the PBGT value.
· Contrary to FDR, THO is a feature activated per adjacency. It is therefore pos
neighbors and forbids it to others.
· It is also interesting to activate THO towards neighbors which have no RTCH

Find which actions can be run on the RNO tool to activate Fast Traffic HO
Retry to solve the TCH congestion problem of a specific cell?

Task RNO action

Implement Forced Directed  Select the bad cell in the 

Retry and Fast Trafic HO Adjacency tab of the Object
from the cell in congestion to window,
its main neighbours (for Execute Add Reverse
instance the ones that count Adjacency,
for more than 20% of the Select the
outgoing handovers) Matrix_Inc_Request_dist_s
up indicator,
Drag and drop in the
Spreadsheet,
Sort the cells in the
spreadsheet according to
the indicator value in
descending order
 Select the outgoing 
adjacencies representing
more than 20% of all the
outgoing handovers
performed from the cell in
 spreadsheet according to
the indicator value in
descending order
 Select the outgoing 
adjacencies representing
more than 20% of all the
outgoing handovers
performed from the cell in
congestion,
Execute Propagate
selection,
Drag and drop in the Cell
Object window,
Unselect the cell in
congestion
 Open a tuning session,
Select the 
L_RXLEV_NCELL_DR(n)
parameter,
Drag and drop in the Tuning
Operation Manager
spreadsheet,
Choose the parameter
values in dBm,
Select the cell in
congestion,
Select the EN_DR,
EN_FORCED_DR and
EN_FAST_TRAFFIC_HO
parameters,
Drag and drop in the Tuning
Operation Manager
spreadsheet,
Set the parameter values to
“ENABLE”,
Apply the tuning session
Remark: The lower the L_RXLEV_NCELL_DR(neighbor) value, the better the c
congestion but the worse the possible quality degradation.

Task RNO action

Implement Traffic HO  Select the cell in congestion 

from the cell in in the Cell Object window,
congestion to the Drag and drop in the
neighbors which are not Adjacency Object window,
 Task RNO action

Implement Traffic HO  Select the cell in congestion 

from the cell in in the Cell Object window,
congestion to the Drag and drop in the
neighbors which are not Adjacency Object window,
in congestion Drag and drop in the map,
Execute Unhighlight all
objects
 Drag and drop the cell in 
congestion from the Cell
Object window to the map,
Change the Highlight
display color,
Execute Highlight target
cell, Execute select
Highlighted objects,
Execute Propagate
selection 
 Select
RTCH_assign_cong_max_r
ate in QoS Indicators
window,
Drag and drop in the
Spreadsheet the weekly
values of last week,
Click on Filter mode, 
Click on Refresh Carto
 Click on Adjacency object
window,
Select one by one in the

map using all the

adjacencies between the
cell in congestion and all its
target neighbors displayed
in green color,
execute propagate selection
from the map 
 Open a tuning session,
Select the
EN_TRAFFIC_HO(0,n)
 cell in congestion and all its
target neighbors displayed
in green color,
execute propagate selection
from the map 
 Open a tuning session,
Select the
EN_TRAFFIC_HO(0,n)
parameter,
Drag and drop in the Tuning
Operation Manager
spreadsheet,
Set the value to “ENABLE”,
Apply the tuning session

Remark: QoS degradation will be limited when implementing Traffic HO with re

DELTA_DEC_HO_MARGIN(congested cell) and DELTA_INC_HO_MARGIN(ne
the values the better the congestion decrease in the cell in congestion but the w
degradation.
CH congestion

4)
3) Too much TCH traffic
Loss of TCH resources

4)
Too much TCH traffic
Check if congestion is coming from
TCH traffic.

Test if the RTCH traffic load is greater

than 1.
RTCH_load_BH > 1

ACTION: Add TRXs to the cell

3)
1) 2) Queuing failures due to tim
Forced Directed Retry activation Queuing failures due to queue full expiry

Check if queuing requests are failed

Check if Forced Directed Retry Check if queuing requests are failed because timer T11 or TQHO is
feature is activated. because the queue is full. expiring

Check if parameter Check if the ratio of queuing requests Check if the ratio of queuing requests
EN_FORCED_DR is DISABLE. failed due to queue full is greater failed due to timer T11 or TQHO
than 40% expiry is greater than 40%.
Check the overlapping with neighbor
cells and activate Forced Directed RTCH_queued_fail_full_ratio > 0.4 RTCH_queued_fail_timeout_ratio>0.
Retry. 4
drop in QoS
again for several If some events are present,
uding “yesterday”
Daily Mono QoS
click on Legend button
eport including
and show events’ details
sign_cong_max_r
Then relay the problem to
or but select the
BSS O&M team
n with network
tion after having
Show event filter
drop in
eet the O&M
he cells for the

in Spreadsheet If value is not 0 then relay to

ays the QoS BSS O&M team

able_nb_avg

H traffic evolution If a neighbor cell had a

ad cells and its noticeable decrease of its
r the last 7 days RTCH traffic:
check if some O&M
nhighlight all configuration change has
he map window, been done on neighbor
bad cell in the cells or on adjacencies
dow, (ex: cell barring,
drop in the map, BS_TXPWR_MAX)
bad cell in the thanks to RMS, check if
path balance of neighbor
cells has become bad
or just
mouse over the
 bad cell in the
dow, (ex: cell barring,
drop in the map, BS_TXPWR_MAX)
bad cell in the thanks to RMS, check if
path balance of neighbor
cells has become bad
or just
mouse over the

ighlight target
map,
elect highlighted
he map,
ropagate

ang_BH indicator,
drop in the
et by selecting
days period of

bad cell in the

dow,

ang_BH indicator,
drop in the

on by selecting
days period of

op in the If cell is barred then the

the cell logical RTCH_HO_ per_Call
indicator value of the bad cell
_ACCESS and may have increased because
_QUALIFY some incoming better cell
handovers are likely to be
performed to the barred cell
after call set-up
Then relay the problem to
BSS O&M team

s: If cell path balance value is

d drop the bad then relay the problem to
 handovers are likely to be
performed to the barred cell
after call set-up
Then relay the problem to
BSS O&M team

s: If cell path balance value is

d drop the bad then relay the problem to
athBalance_avg BSS Site engineering team
in the
heet
d drop te
dio_link_detailed
the QoS
k

with RNO Activate BSS PM Type 5 for

this cell (GP=1h) providing
counters per TCH TS and
check from counters that
some TS are never allocated
(C370A+C370B=0) and
always used for traffic
(C380A+C380B=0s)
and relay the problem to BSS
O&M team

with RNO 2 possibilities:

 activate BSS PM Type 5
for this cell (GP=1h)
providing counters per
TCH TS and
check from counters that
some TS are never
allocated
(C370A+C370B=0) and
never used for traffic
(C380A+C380B=3600)
 check MPM QoS Alerters
“TCH hanging” per TRX:
(MC380a(b)/3600) >=
0.95 && (MC370a(b) <
20)
a for FR / b for HR
and relay the problem to BSS
 (C380A+C380B=3600)
 check MPM QoS Alerters
“TCH hanging” per TRX:
(MC380a(b)/3600) >=
0.95 && (MC370a(b) <
20)
a for FR / b for HR
and relay the problem to BSS
O&M team

s “normal”, i.e. which is due to a too high subscriber traffic

if the TCH congestion is not “normal”, i.e. is not due to a

capacity. He writes them on the board as below:
te engineering team has to perform recovering actions

, TRX)

systems

s to add TRX capacity in the cell in congestion or BSS

ension by:

but that can degrade the QoS in the meantime especially in

arget neighbors. The only way to allow FDR to some cells

of the target cell: L_RXLEV_NCELL_DR(n) set to –47dBm
in this case no incoming FDR can be performed to that

ards neighboring cells having the best coverage overlap

he highest ratio of handovers are performed (for instance

ers).

CH congestion but that can degrade the QoS in the

archical). However the QoS degradation should be less
our cells are located at the border of the serving cell since

ency. It is therefore possible to allow THO towards some

 he highest ratio of handovers are performed (for instance
ers).

CH congestion but that can degrade the QoS in the

archical). However the QoS degradation should be less
our cells are located at the border of the serving cell since

ency. It is therefore possible to allow THO towards some

s which have no RTCH congestion problem.

ctivate Fast Traffic HO, Traffic HO and Forced Directed

cific cell?

action Result

bad cell in the  Outgoing adjacencies

tab of the Object are displayed and sorted
according the ratio of
dd Reverse outgoing handovers
which is also displayed

_Request_dist_s
r,
rop in the
et,
lls in the
et according to
or value in
g order
outgoing  All neighbor cells to
s representing which more than 20% of
20% of all the the outgoing handovers
andovers are performed are
from the cell in selected
et according to
or value in
g order
outgoing  All neighbor cells to
s representing which more than 20% of
20% of all the the outgoing handovers
andovers are performed are
from the cell in selected
,
opagate

rop in the Cell

dow,
e cell in

ing session,
 Forced Directed Retry
NCELL_DR(n) and Fast Traffic HO are
implemented
rop in the Tuning
Manager
et,
e parameter
Bm,
cell in
,
EN_DR,
ED_DR and
_TRAFFIC_HO
s,
rop in the Tuning
Manager
et,
ameter values to

uning session
r) value, the better the congestion decrease in the cell in
on.

tion Result

in congestion  All outgoing adjacencies of

ect window, the cell in congestion are
in the displayed on the map
ect window,
 tion Result

in congestion  All outgoing adjacencies of

ect window, the cell in congestion are
in the displayed on the map
ect window,
in the map,
hlight all

the cell in  All neighbor cells of the cell

m the Cell in congestion are selected
w to the map, in the Cell Object Window
ghlight

ght target
elect
jects,
agate
 All neighbor cells are
colored on the map
_cong_max_r according to their
icators RTCH_assign_cong_max_r
ate indicator value
in the
he weekly
week,
mode,  All outgoing adjacendies to
sh Carto neighbor cells having no
ency object TCH congestion problem
(RTCH_assign_cong_max_r
one in the ate indicator value lower
than the yellow threshold)
all the are selected in the
etween the Adjacency Object window
ion and all its
rs displayed

gate selection
 Traffic HO is implemented
session,

_HO(0,n)
ion and all its
rs displayed

gate selection
 Traffic HO is implemented
session,

_HO(0,n)

in the Tuning
nager

o “ENABLE”,
ng session

nting Traffic HO with reasonably low value of

A_INC_HO_MARGIN(neighbor) parameters. The higher
l in congestion but the worse the possible quality
 4)
3) Bad settings of queuing
Queuing failures due to timer parameters
expiry

Check if queuing parameters have a

ueuing requests are failed correct value.
imer T11 or TQHO is
Check if parameters T11, TQHO and
BTS_Q_LENGTH are out of
he ratio of queuing requests recommended range
to timer T11 or TQHO
reater than 40%.

eued_fail_timeout_ratio>0.

3)
1) Check if parameter
Check if timer T11 has a correct BTS_Q_LENGTH has a correct
value. value.

ACTION:Correct the value of timer ACTION:

T11. Correct the value of parameter
BTS_Q_LENGTH.
 Check if timer T11 has a correct BTS_Q_LENGTH has a correct
value. value.

ACTION:Correct the value of timer ACTION:

T11. Correct the value of parameter
BTS_Q_LENGTH.
2)
Check if timer TQHO has a
correct value.

ACTION:Correct the value of

timer TQHO.
 TCH assignment failure
1)
TCH assignment fail congestion
2)
TCH assignment failure system

check if TCH congestion rate is higher

than 2%.
RTCH_assign_cong_rate>0.02 1)
Check if TCH assignment failure is
coming from system problem.

Test if TCH assignment failures due

to system problem represent more
than 40% of failures

RTCH_assign_fail_BSS_ratio>0.4

ACTION:
check alarms on LAPD links and
processors. Check status of TCH
channels and reconfigure if
necessary
1)
Too much TCH traffic
Check if congestion is coming from
TCH traffic.

Test if the RTCH traffic load is greater

than 1.
RTCH_load_BH > 1
2)
ACTION: Add TRXs to the cell RTCH always busy

Check if RTCH are always busy:

RTCH seizures very low with a
normal RTCH occupancy

Test if ratio RTCH seizure success

divided by RTCH assign request is
less than 5 % with RTCH occupancy
greater than 20 seconds

(RTCH_assign_success/RTCH_assig
n_request < 0.05) AND 3)
(RTCH_duration_avg > 20); Loss of TCH resources

ACTION:Try to reinitialize active Check if radio TCH resources ar

CPRA for BSC G1 and TCHRM for missing.
Check if the number of radio TCH
 divided by RTCH assign request is
less than 5 % with RTCH occupancy
greater than 20 seconds

(RTCH_assign_success/RTCH_assig
n_request < 0.05) AND 3)
(RTCH_duration_avg > 20); Loss of TCH resources

ACTION:Try to reinitialize active Check if radio TCH resources ar

CPRA for BSC G1 and TCHRM for missing.
BSC G2. Check if the number of radio TCH
time slots unavailable is greater th
0

ACTION:Try to reinitialize SBL RT

If not working, reconfigure TCH fro
CHANNELS menu
gnment failure

3)
2)
TCH assignment failure radio
ment failure system

1)
1)
Abis programming problem
assignment failure is
m system problem.
Check if RTCHs with communication 2)
duration very short are 0 to 3 and 4 FU blocked
signment failures due
to 7 for a same FU i.e. TCHs which
blem represent more
are on the Abis PCM timeslot Check if FUs are handling traffic.
0% of failures
Test which RTCHs have an average Test if the number of TRX with an
_fail_BSS_ratio>0.4
communication duration less than average duration
10s (RTCH_duration_avg) of 0 second is
CTION:
on LAPD links and greater than 0
ACTION:
Check status of TCH
Check and reprogram equipment at ACTION
and reconfigure if
both ends if necessary. Reinitialize SBLs affecting the FU
ecessary
(CU, FU, RTS).

3)
Radio equipment problem

Check if radio equipment commun to

the entire BTS is working properly.

Test if average communication

duration (RTCH_duration_avg) is
less than 10s on all cells of BTS

Check with site maintenance the

status of CPLG, combiners, aerial,
transmission power or receiving
sensibility
3)
Loss of TCH resources

heck if radio TCH resources are

missing.
heck if the number of radio TCH
 Check with site maintenance the
status of CPLG, combiners, aerial,
transmission power or receiving
sensibility
3)
Loss of TCH resources

heck if radio TCH resources are

missing.
heck if the number of radio TCH
e slots unavailable is greater than
0

TION:Try to reinitialize SBL RTS.

ot working, reconfigure TCH from
CHANNELS menu
4)
FU blocked

Check if FUs are handling traffic.

Test if the number of TRX with an

average duration
(RTCH_duration_avg) of 0 second is
greater than 0

ACTION: Reinitialize SBLs affecting

the FU (CU, FU, RTS).
 2)
FU blocked

s are handling traffic.

umber of TRX with an

rage duration
ion_avg) of 0 second is
eater than 0

ACTION
SBLs affecting the FU
U, FU, RTS).
 Call Drop
Check if dropped call are coming
Call_drop_radio_ratio >
from a radio problem.

Check if there is a drift of the reference clock: Check if

the rate of handover on interference is higher than 5% Check if CHO_interference_rate > 5%
check if the ratio of outgoing HO request divided
by Assign request is less than 5%
Check if the cell is isolated i.e. does not have enough (HO_Out_2G_2G_request/
neighbors. RTCH_assign_request) < 0.05
Check if the isolated cell is not due to too high
intersite distance that does not allow overlap
between cells
Check if planning of neighbor cellLIST is done
correctly

Wrong HO relationship declarations

Check if RTCH_duration_avg on a TRX is less
Check if communication duration on a TRX is less than than 15 seconds than the maximum value on
others. other TRXs
Check if the cell seems to be interfered thus has
a high rate of handover on quality
Bad settings of Handover algorithm
Bad settings of Power Control algorithm

For each neighbour cell of same frequency range

and same type as the serving cell, the
C/I overlap between the neighbour cell and the
serving cell is taken from RMS indicators.

This C/I overlap is compared to a threshold that

Possible interference problems detemines if same or adjacen

Check if dropped calls are coming

from a system problem. Call_drop_BSS_ratio >
Check if there are some dropped calls due to remote Check if the rate of remote transcoder failures is
transcoder failures higher than 0.5%
Check if there are some dropped calls due to BSS Check if the rate of BSS internal failures is higher
internal failures than 0.5%

Check if the system problem involves the whole

BSC

Check if the system problem involves mainly the

concerned cell.
Check if dropped calls are coming
from a handover problem Call_drop_HO_ratio > 4
Duplicate (BCCH, BSIC)
Check if potential target cells are congested
which can create radio problems after
unsuccessful handovers

Check if clock problem:

Wrong HO relationship declarations

Coverage problem: Check if there is a potential

problem of coverage hole on the cell.

Bad settings of Power Control algorithm

Check if the cell seems to be interfered thus has

a high rate of handover on quality.

Bad settings of Handover algorithm

ll Drop Diag
ll_drop_radio_ratio > 40%

if CHO_interference_rate > 5% A clocking problem is

suspected. If reference clock has drifted, MS may have
problem to synchronize causing bad quality Check
oscillator's drift and adjust it to its reference 13MHz. If
problem persists, replace the faulty eq

Test if there is at least one neighbour cell in a range of

twice the maximum timing advance detected in the serving
cell 2*(RMS_TimingAdvance_max*550.0)

Test if there are less than 10 planned neighbor cells

Test if there are HO relationships planned but not declared
at OMC-R level or if there are HO relationships declared at
OMC-R level but not planned or if there are non
symmetrical HO relationships

Check if CHO_quality_rate is greater than 20%

RMS_CI_overlap_per_Neighbour < CI_THRESHOLD =12

all_drop_BSS_ratio > 40%

check if Call_drop_BSS_remote_TC_rate > 0.005 =>
Dropped calls due to Remote Transcoder failures are too
high
 check if Call_drop_BSS_int_failure_rate > 0.005
Dropped calls due to Remote Transcoder failures are too
high

Test if more than 60% of cells in the BSC have a ratio of

dropped calls due to system problem higher than 40%.

TC16 problem

DTC problem

Access Switch DTC Board

TRCU transmission problem

BSC instabilities

Abis programming problem

Transmission equipment failure

Access Switch TCU Board

BTS instabilities

FU problem
all_drop_HO_ratio > 40%
Check duplicate (BCCH, BSIC) declarations in OMC

Check if radio TCH resources are missing.

Check if congestion is coming from TCH traffic.
Check if RTCH are always busy: RTCH seizures very low
with a normal RTCH occupancy
Check if FUs are handling traffic.
Check if the rate of handover on interference is higher
than 5%CHO_interference_rate > 5%
A clocking problem is suspected. If
reference clock has drifted, MS may have problem to
synchronize caus
Test if there are HO relationships planned but not declared
at OMC-R level or if there are HO relationships declared at
OMC-R level but not planned or if there are non
symmetrical HO relationships

Check if the rate of handovers on level is greater than 40%

with a handover reversion rate less than 3%
Check if parameters for triggering Power Control are
correct
Check if threshold L_RXQUAL_UL_P is correct.
Check if threshold L_RXQUAL_DL_P is correct.
Check if threshold L_RXLEV_UL_P is correct.
Check if threshold L_RXLEV_DL_P is correct.
Check if window A_LEV_PC is correct
Check if parameter POWER_INC_STEP is correct.
Check if parameter POWER_INC_STEP is correct.
Check if the rate of handover on quality is greater than
20%.

Check if parameters for triggering handovers are correct.

Check if L_RXLEV_UL_H is correct
Check if L_RXLEV_DL_H is correct
Check if U_TIME_ADVANCE is correct
Check if L_RXQUAL_UL_H is correct
Check if L_RXQUAL_DL_H is correct
g
Check if affected circuits are irregularly distributed on TS 1 to 15
and 17 to 31 of the same PCM investigations needed: A interface
measurement is necessary to conclude
It may be a software or hardware pro
Check if affected circuits are irregularly distributed on all timeslots of
the same PCM Further investigations needed: A interface
measurement is necessary to conclude
It may be a softwar
Check if affected circuits are distributed on all timeslots of all PCMs
Further investigations needed: A interface measurement is
necessary to conclude
It may be a h
Check if affected circuits are a few numbers and distributed over
one or more A interface PCMs Further
investigations needed: A interface measurement is necessary to
conclude
Check if an important part of system problem is coming from OMC-R
counter C14c (other BSS problems) Further investigations needed:
data are not available It may be a
hardware problem on BSC which can be
Check if RTCHs with an average call duration (OMC-R counters
type 5) less than 5s are RTCH number 0 to 3 and 4 to 7 i.e. TCHs
which are on the Abis PCM timeslot and on the same FU
Further investigations needed: indica
Check after an Abis measurement, if there is a correlation with
alarms CONNECTION FAIL IND \"Remote Transcoder Alarm\" on
the same Abis PCM managing one or more BTS or FU
Further investigations needed: Abis measur
Check after an Abis measurement, if there is a correlation with
alarms on ACCESS SWITCH board of the BSC
Further investigations needed: Abis measurement is
necessary to conclude

Check if an important part of system problem is coming from OMC-R

counter C14c (other BSS problems). Further investigation is needed
Further investigations needed: data are not available
It may be a hardware problem on B

Check if RTCHs with an average call duration (OMC-R counters

type 5) less than 5s are RTCH number 0 and 4, or 1 and 5, or 2 and
6 or 3 and 7 on the same FU Further investigations needed:
indicators per RTCH are not available It may be a software or
Check oscillator's drift and adjust it to its reference 13MHz. If
problem persists, replace the faulty equipment. If problem still
persists, check other radio equipment: duplexer, coaxes, LNA…

(CHO_level_rate> 40%) AND (HO_Out_2G_2G_ROC_rate < 3%)

Confirm with coverage map the potential coverage hole

CHO_quality_rate > 20%

 Alcatel 9156 RNO operation advanced le
Tasks How to do
Global
Tasks Locate the impacted zone
1- Detect Identify symptoms
QoS PB degradation Identify reports
Identify Global KPI
->congest,call,HO,traff(sleep cell)

Control Qos indicators

2- Analyse Identify cause(s) suspected
To solve a QOS problem search the causes ->Radio, Interfer, congest , coverage, HO, Sys..
Recurrent Pb?
HW Pb?
By TRX? / for the Busy hour?

3- Find the PB: Diagnosis usage; Quick Diag

Diagnoses Planning Pb: Frq; Bsic, Coverage, Ncell
Drive test => RMS

4- Improve: Tune List impacted elements

Param., Indic., Rep.,Map Class the prirority
Identify algo. and parameters
To Improve the performance Modify algo.,param.,design

5- Check Control QOS indicators

Improvement or degradation?

6- Experience Capitalization
Customise RNO

1- Detect QoS PB degradation

1.1 Overview of the main BSS GSM QoS problems and thei

Question:
List the main BSS GSM QoS problems?

Ø No service
Ø Call setup fails
Question:
List the main BSS GSM QoS problems?

Ø No service
Ø Call setup fails
Ø Call drops
Ø Call of bad voice quality
-----------------------------------------------------------------------------------------------------------------------
List the causes of the main BSS GSM QoS problems identified above ?
Answer:
First step: Causes are given as seen from the mobile side

Ø No service
ü No signal
ü No decoding of System Information messages (bad radio quality (RXQUAL))

Ø Call setup fails

ü Lack of SDCCH resource
ü SDCCH access failure
ü Radio link failure on SDCCH (SDCCH drop)
ü Lack of TCH resource
ü TCH access failure
ü No answer from called party
ü Called party busy

Ø Call drops
ü Radio link failure on TCH (TCH drop)
ü No handover performed
ü Handover drop

Ø Call of bad voice quality

ü Bad radio quality (RXQUAL)
ü Bad voice quality only
-----------------------------------------------------------------------------------------------------------------------
Second step: The trainer asks the trainees if “congestion”, “bad coverage”, “interference”
be possible reasons of the previously listed causes.

“Congestion” has to be understood as a lack of any resource needed (BSS (radio) or NS

“System problem” has to be understood as any:
- Equipment dysfunction (mobile, TMA, REK, BTS, BSC, TC, Abis transmission, IPE, in th
- Bad installation (of antenna systems, of BTS-antennas cables connections)
- Bad configuration (radio parameter, adjacency, BSS/NSS mismatch regarding Signalling
resources)
“System problem” has to be understood as any:
- Equipment dysfunction (mobile, TMA, REK, BTS, BSC, TC, Abis transmission, IPE, in th
- Bad installation (of antenna systems, of BTS-antennas cables connections)
- Bad configuration (radio parameter, adjacency, BSS/NSS mismatch regarding Signalling
resources)

End user Congestion Coverage Interfer

pb
(1)
No service No signal X
No X X
decoding of
SI
messages
Call set-up Lack of X
fails SDCCH
resource
SDCCH X X
access
failure
Radio link X X
failure on
SDCCH
Lack of X
TCH
resource
TCH X X
access
failure
No answer
from called
party (ring
tone) (6)
Called party
busy (busy
tone) (6)
Call drops Radio link X X
failure on
 from called
party (ring
tone) (6)
Called party
busy (busy
tone) (6)
Call drops Radio link X X
failure on
TCH
No(outdoor or indoor): X (8)
(1) Bad network design X (9) X (1

- Missing site handover

- Missing repeater toperformed
cover a black zone
(2) No signal can come from system problem:
Handover
- TMA or REK dysfunction X (12) X (1

drop
- BTS hardware problem (TRE board, ANC board)
(14) (1
Call of
- Wrong badsystems
antenna Bad installation
radio (tilt, azimuth, antenna type,X
cables) X
(3)voice
No decoding of SI messages can come from system problem:
quality
- REK dysfunction
quality
- BTS hardware problem (TRE board, ANC board)
Bad voice
(4) Lack of SDCCH resource can come from :
quality only
- BTS software problem
- BSC software problem
(5) Radio link failure on SDCCH can come from :
- BTS or BSC software problem
- Lack of SCCP resource between BSC and MSC
- Lack of any other needed internal network resource (in BSS, NSS or PSTN)
- NSS or PSTN software problem
(6) No answer from called party and call party busy are “user failures”. They are not netwo

(7) Radio link failure on TCH can come from a TC hardware problem or an Abis microwav

No handover performed can come from:

(8) TCH congestion in the target cell
(9) the fact that the downlink HANDOVER COMMAND message has not been decoded d
downlink
(10) the fact that the downlink HANDOVER COMMAND message has not been decoded
in downlink
(11) the fact that some internal network resource needed for an inter-BSC handover is no
a software problem also

Handover drop can be due to:

(12) a too bad coverage in uplink in the target cell followed by a mobile failure to return to
(13) a too high interference in uplink in the target cell followed by a mobile failure to return

Bad radio quality at the origin of the voice quality degradation can be due to:
(14) bad radio coverage (BER/RXQUAL degrades when RXLEV decreases)
(15) interference (BER/RXQUAL degrades when interference increases)
(16) interference (BER/RXQUAL degrades when interference increases)
Handover drop can be due to:
(12) a too bad coverage in uplink in the target cell followed by a mobile failure to return to
(13) a too high interference in uplink in the target cell followed by a mobile failure to return

Bad radio quality at the origin of the voice quality degradation can be due to:
(14) bad radio coverage (BER/RXQUAL degrades when RXLEV decreases)
(15) interference (BER/RXQUAL degrades when interference increases)
(16) interference (BER/RXQUAL degrades when interference increases)

(17) Bad voice quality can come from any hardware or software problem in the voice data
BTS, TC, IPE (echo canceller for instance), NSS, PSTN).

1.2 Detect QoS PROBLEM

Find a way to detect a problem of TCH congestion in a cell of the network for yester

3 Methods:
o drag & drop in the spreadsheet the RTCH_cong_max_rate indicator for all cells of the n
§ Result: the indicator value is displayed for all cells. Then ask the trainee to use the B9 fe
sorting in spreadsheet” to identify the cell having the highest peak of TCH congestion rate
This method allows to sort the cells according to the peak of TCH congestion rate indicato

o drag and drop in QoS Notebook for “yesterday” a Daily Warning Red Threshold Report
Warning Indicator is RTCH_assign_cong_max_rate
If such a Warning Report does not exist, ask the trainee to create it from a copy of an exis
Alc_RTCH_assign_preparation in Warning_Threshold_RTCH or View Alc_RTCH_conges
Warning_Threshold_congestion).
§ Result: the indicator value is displayed for all cells. Then ask the trainee to use the B9 fe
sorting in spreadsheet” to identify the cell having the highest peak of TCH congestion rate
This method allows to sort the cells according to the peak of TCH congestion rate indicato

o drag and drop in QoS Notebook for “yesterday” a Daily Warning Red Threshold Report
Warning Indicator is RTCH_assign_cong_max_rate
If such a Warning Report does not exist, ask the trainee to create it from a copy of an exis
Alc_RTCH_assign_preparation in Warning_Threshold_RTCH or View Alc_RTCH_conges
Warning_Threshold_congestion).
§ Result: all cells having their RTCH_assign_max_cong_rate indicator value over the Re
report.
This method allows to identify the cell in which the highest number of TCH assignment req
due to congestion provided that the Sorting indicator is the total number of RTCH assignm
(RTCH_assign_request).

o drag & drop a warning evolution top worst report including a view whose warning indica
RTCH_cong_max_rate indicator for all cells of the network for “yesterday”
§ Result: the cells having the greatest relative increase of their RTCH_assign_max_cong_
This method allows to identify the cell in which the highest rate of congestion increase hav
not be the one having the highest congestion rate nor the highest number of TCH assignm
rejected due to congestion.

2- Analyse/INVISTIGATE: search the cause

Check or task RNO action Ne

Check if the TCH Drag and drop in QoS Notebook Confi

congestion has been for several weeks including ”norm
increasing regularly for the “yesterday” a Daily Mono QoS
last weeks Evolution report including the
RTCH_assign_cong_max_rate
indicator
Check if the TCH Drag and drop in QoS Notebook Confi
congestion has been for several weeks including ”norm
increasing regularly for the “yesterday” a Daily Mono QoS
last weeks Evolution report including the
RTCH_assign_cong_max_rate
indicator

Confirm that congestion is Check that the Find

”normal” RTCH_time_system_conges TCH
tion hourly indicator value is Ques
not always 0 during the day
(provides the number of
seconds all RTCH TS are
busy during the GP)
Check that the
RTCH_Erlang_BH daily
indicator value is over the
Traffic capacity of the cell at
the GoS corresponding to
the value of the Red
Threshold attached to the
RTCH_assign_cong_max_r
ate warning indicator
Create a QoS Mono-
evolution report with a view
including:
o in the bar chart part:
RTCH_nb_avg and
RTCH_Erlang_total
o in the curve part:
RTCH_time_system
_congestion

Check if the Daily indicator Drag and drop in QoS Notebook If the
is bad because of a PM for several days including repor
counter reporting “yesterday” an Hourly Mono hourl
QoS Evolution report including day w
 RTCH_time_system
_congestion

Check if the Daily indicator Drag and drop in QoS Notebook If the
is bad because of a PM for several days including repor
counter reporting “yesterday” an Hourly Mono hourl
QoS Evolution report including day w
the RTCH_assign_cong_rate extra
indicator the d
(for example Alc_Mono_QoS wrong
can be copied removing all the
RTCH_assign_cong_max_rate same
from Alc_RTCH_congestion
view and Then
SDCCH_cong_max_rate from BSS
Alc_SDCCH_total_congestion
view since these 2 indicators are
not available per hour)

Check if there has been 2 possibilities:

some O&M configuration  Drag and drop in QoS
change Notebook again for several If som
weeks including “yesterday”
the same Daily Mono QoS
click o
Evolution report including
and sh
the
RTCH_assign_cong_max_r
Then
ate indicator but select the
BSS O
“Correlation with network
events” option after having
setup the Show event filter
 Drag and drop in
Spreadsheet the O&M
events of the cells for the
last 7 days

Check if the number of Drag and drop in Spreadsheet If valu

available TCH is maximum for the last 7 days the QoS BSS O
 setup the Show event filter
 Drag and drop in
Spreadsheet the O&M
events of the cells for the
last 7 days

Check if the number of Drag and drop in Spreadsheet If valu

available TCH is maximum for the last 7 days the QoS BSS O
indicator
RTCH_unavailable_nb_avg

Check if the TCH traffic Compare RTCH traffic evolution If a ne

increase is not due to TCH between the bad cells and its notice
traffic decrease in neighbors over the last 7 days RTCH
neighboring cells 2 possibilities: ch
 Execute Unhighlight all co
objects in the map window, be
Select the bad cell in the ce
Object window, (e
Drag and drop in the map, BS
Select the bad cell in the th
pa
ce
map using or just
move the mouse over the
cell icon,
Execute Highlight target
cells in the map,
Execute Select highlighted
objects in the map,
Execute Propagate
selection,
Select the
RTCH_Erlang_BH indicator,
Drag and drop in the
spreadsheet by selecting
the last 7 days period of
time
 Select the bad cell in the
Object window,
Select the
RTCH_Erlang_BH indicator,
Drag and drop in the
 the last 7 days period of
time
 Select the bad cell in the
Object window,
Select the
RTCH_Erlang_BH indicator,
Drag and drop in the

button by selecting
the last 7 days period of
time

Check if some O&M Drag and drop in the If cell i

configuration change has spreadsheet the cell logical RTCH
been done on neighbor cells parameters indicat
or on adjacencies CELL_BAR_ACCESS and may ha
(ex: cell barring, CELL_BAR_QUALIFY some
BS_TXPWR_MAX) hando
perform
after c
Then r
BSS O

Thanks to RMS, check if 2 possibilities: If cell p

path balance of neighbor  Drag and drop the bad th
cells has become bad RMS_PathBalance_avg BSS S
indicator in the
Spreadsheet
 Drag and drop te
RMS_radio_link_detailed
report in the QoS
Notebook

Check if the some RTCH TS Impossible with RNO Activat

are never busy this ce
counte
check
some
(C370
always
(C380
and re
 are never busy this ce
counte
check
some
(C370
always
(C380
and re
O&M t

Check if the some RTCH Impossible with RNO 2 poss

TS are always busy  ac
for
pro
TC
ch
so
all
(C
ne
(C
 ch
“T
(M
0.9
20
af
and re
O&M t

4- Improve: Tune Param., Indic., Rep.,Map

Find a solution to a problem of TCH congestion which is “normal”, i.e. which is due to a to
demand compared to the cell capacity

trainer first recalls the different actions to be carried out if the TCH congestion is not “nor
high subscriber traffic demand compared to the cell capacity. He writes them on the board
If it is a system problem then BSS O&M team or BSS site engineering team has to perform
according to the output of the analysis:
o unbar neighbor cell
o restart BSC boards (CPRA, DTC, TCU) or BTS (SUM, TRX)
o disable and re-enable traffic on the bad cell
o replace HW components on BSC or BTS or Antenna systems
o modify radio configuration parameter
trainer first recalls the different actions to be carried out if the TCH congestion is not “nor
high subscriber traffic demand compared to the cell capacity. He writes them on the board
If it is a system problem then BSS O&M team or BSS site engineering team has to perform
according to the output of the analysis:
o unbar neighbor cell
o restart BSC boards (CPRA, DTC, TCU) or BTS (SUM, TRX)
o disable and re-enable traffic on the bad cell
o replace HW components on BSC or BTS or Antenna systems
o modify radio configuration parameter

If it is a real traffic problem then BSS planning team has to add TRX capacity in the cell in
optimization team can improve the QoS before TRX extension by:
o Implementing Forced Directed Retry if not used
o Implementing Fast Traffic HO if not used
o Implementing Traffic HO if not used
o Implementing Half Rate if not used

But some risks have to be considered.

For Forced Directed Retry and Fast Traffic HO:

· FDR is a feature that can decrease RTCH congestion but that can degrade the QoS in t
conventional network (not hierarchical).
· FRD is a feature activated per cell towards any of its target neighbors. The only way to a
forbid FDR to others is to tune the FDR parameter of the target cell: L_RXLEV_NCELL_D
any FDR towards that cell. The drawback is that in this case no incoming FDR can be per
· QoS degradation will be limited if FDR is activated towards neighboring cells having the
the serving cell in RTCH congestion
· The best neighboring cells are usually those to which the highest ratio of handovers are
more than 20% of the total number of outgoing handovers).

For Traffic HO:

· THO (HO cause 23) is a feature that can decrease RTCH congestion but that can degra
especially in a conventional network (not hierarchical). However the QoS degradation sho
mobile who will handed over to the neighbour cells are located at the border of the serving
condition is based on the PBGT value.
· Contrary to FDR, THO is a feature activated per adjacency. It is therefore possible to allo
neighbors and forbids it to others.
· It is also interesting to activate THO towards neighbors which have no RTCH congestion

Find which actions can be run on the RNO tool to activate Fast Traffic HO, Traffic H
Retry to solve the TCH congestion problem of a specific cell?
 Task RNO action

Implement Forced Directed  Select the bad cell in the  Out

Retry and Fast Trafic HO Adjacency tab of the Object are
from the cell in congestion to window, acc
its main neighbours (for Execute Add Reverse outg
instance the ones that count Adjacency, whic
for more than 20% of the Select the
outgoing handovers) Matrix_Inc_Request_dist_s
up indicator,
Drag and drop in the
Spreadsheet,
Sort the cells in the
spreadsheet according to
the indicator value in
descending order
 Select the outgoing  All n
adjacencies representing whic
more than 20% of all the the
outgoing handovers are
performed from the cell in sele
congestion,
Execute Propagate
selection,
Drag and drop in the Cell
Object window,
Unselect the cell in
congestion
 Open a tuning session,
Select the  For
L_RXLEV_NCELL_DR(n) and
parameter, imp
Drag and drop in the Tuning
 Object window,
Unselect the cell in
congestion
 Open a tuning session,
Select the  For
L_RXLEV_NCELL_DR(n) and
parameter, imp
Drag and drop in the Tuning
Operation Manager
spreadsheet,
Choose the parameter
values in dBm,
Select the cell in
congestion,
Select the EN_DR,
EN_FORCED_DR and
EN_FAST_TRAFFIC_HO
parameters,
Drag and drop in the Tuning
Operation Manager
spreadsheet,
Set the parameter values to
“ENABLE”,
Apply the tuning session
Remark: The lower the L_RXLEV_NCELL_DR(neighbor) value, the better the congestio
congestion but the worse the possible quality degradation.

Task RNO action

Implement Traffic HO  Select the cell in congestion  All out

from the cell in in the Cell Object window, the ce
congestion to the Drag and drop in the displa
neighbors which are not Adjacency Object window,
in congestion Drag and drop in the map,
Execute Unhighlight all
objects
 Drag and drop the cell in  All nei
congestion from the Cell in con
Object window to the map, in the
Change the Highlight
display color,
Execute Highlight target
 Execute Unhighlight all
objects
 Drag and drop the cell in  All nei
congestion from the Cell in con
Object window to the map, in the
Change the Highlight
display color,
Execute Highlight target
cell, Execute select
Highlighted objects,
Execute Propagate
selection  All nei
 Select colore
RTCH_assign_cong_max_r accord
ate in QoS Indicators RTCH
window, ate ind
Drag and drop in the
Spreadsheet the weekly
values of last week,
Click on Filter mode,  All out
Click on Refresh Carto neighb
 Click on Adjacency object TCH c
window, (RTCH
Select one by one in the ate ind
than th
map using all the are se
adjacencies between the Adjace
cell in congestion and all its
target neighbors displayed
in green color,
execute propagate selection
from the map  Traffic
 Open a tuning session,
Select the
EN_TRAFFIC_HO(0,n)
parameter,
Drag and drop in the Tuning
Operation Manager
spreadsheet,
Set the value to “ENABLE”,
Apply the tuning session
 parameter,
Drag and drop in the Tuning
Operation Manager
spreadsheet,
Set the value to “ENABLE”,
Apply the tuning session

Remark: QoS degradation will be limited when implementing Traffic HO with reasonably
DELTA_DEC_HO_MARGIN(congested cell) and DELTA_INC_HO_MARGIN(neighbor) p
values the better the congestion decrease in the cell in congestion but the worse the po

coverage problem

Detect coverage problem

Find a way to detect a problem of coverage in a cell of the network for yesterday

Method 1: Quick DIAG

Create a Quick diagnosis which will have a TRUE value when the following condition bas
fulfilled:
Call_drop_radio_rate > 5%
And SDCCH_drop_radio_rate > 2%
And RTCH_assign_fail_radio_rate > 2%
And CHO_EM_standard_rate > 50%

/* *****************************************************************
* back-up of scenario : Coverage problem
* created on 08/17/2005 03:43:08 PM
* *****************************************************************/
QUICK_SCENARIO "Coverage problem"
DESCRIPTION "Detecting a cell coverage problem" ;
// NO associated indicator
OWNER "rno" ;
END_QUICK_SCENARIO

// ------------------------------------------------------
NODE "Coverage problem":"Bad indicators combination"
DESCRIPTION {"Quick diagnosis node"}
CONTEXT { CELL c;
DATE d;
PERIOD p;
OWNER "rno" ;
END_QUICK_SCENARIO

// ------------------------------------------------------
NODE "Coverage problem":"Bad indicators combination"
DESCRIPTION {"Quick diagnosis node"}
CONTEXT { CELL c;
DATE d;
PERIOD p;
}
LOCAL {BOOLEAN call_drop_radio_rate = I:CHO_EM_standard_rate( c, d, p ) > 0.05;
BOOLEAN SDCCH_drop_radio_rate = I:SDCCH_drop_radio_rate( c, d, p ) > 0.02;
BOOLEAN RTCH_assign_fail_radio_rate = I:RTCH_assign_fail_radio_rate( c, d, p ) > 0.0
BOOLEAN CHO_EM_standard_rate = I:CHO_EM_standard_rate( c, d, p ) > 0.5;
BOOLEAN coverage_problem = FALSE;}
ACTION {""}
TEST_DESCRIPTION {"Identify cells having at the same time:
- high call drop radio rate
- high SDCCH drop radio rate
- high TCH assignment failure radio rate
- high percentage of emergency handovers"}
TEST_VALUE { coverage_problem == call_drop_radio_rate AND SDCCH_drop_radio_ra
RTCH_assign_fail_radio_rate AND CHO_EM_standard_rate;
}
END_NODE

// ------------------------------------------------------
FIRST_NODE "Coverage problem":"Coverage problem"
DESCRIPTION {"No description"}
CONTEXT {CELL c;
DATE d;
PERIOD p;}
LOCAL {}
ACTION {""}
END_NODE

// links
LINK "Coverage problem":"Bad indicators combination" "Coverage problem":"Coverage
DESCRIPTION {"No description"}
CALLING {
c = c;d = d;p = p; }
RESTRICTION { }
END_LINK
RESTRICTION { }
END_LINK

Method 2: RMS

A coverage problem is identified when a considerable amount of calls are experiencing a

too low level of radio signal. Such a problem can easily be detected using the radio statis
equipements on a per TRX basis

Alc_Warning_Top_Worst_RMS_Radio_Link

o select all cells and drag & drop the Alc_Warning_Top_Worst_RMS_Radio_Link Warning
Notebook for “yesterday”
§ Result: the cells having the lowest Average RxLevel UL and the cells having the worst A
displayed

If some cells belong to both top worst lists then they are candidate for being degraded du

It can also happen that the Average RxLevel DL is bad whereas the UL RxLevel is not. Al
can be bad whereas the UL RxQual is not. A good idea at this stage of the exercise is to
more views in the warning report.
The first view being a copy of the Alc_RMS_RxLevel_avg view where the Filtering and So
by RMS_DL_RxLevel_avg

The second view being a copy of the Alc_RMS_RxQuality_avg view where the Filtering a
replaced by RMS_DL_RxLevel_avg
 Analyze the problem of coverage

Check or task RNO action Ne

Thanks to RMS, check if Select the bad cell and Drag and Chec
bad radio quality can be drop in the QoS Notebook for cons
characterized as a bad “yesterday” both sam
coverage problem Alc_Mono_DL_RxQuality_Rxlevel bad
and 90 d
Alc_Mono_UL_RxQuality_Rxlevel (see
QoS Mono-Object Distribution I
reports t
i
a
I
b
o
o

Thanks to RMS, check if  Select the bad cell and Drag Chec
bad coverage problem is and drop it in the TRX’s tab the s
observed for all TRXs of the  Drag and drop in the QoS matr
cell Notebook for “yesterday” TRX
both
Alc_Mono_DL_RxQuality_Rxl I
evel and i
Alc_Mono_UL_RxQuality_Rxl s
evel QoS Mono-Object I
Distribution reports P
 both
Alc_Mono_DL_RxQuality_Rxl I
evel and i
Alc_Mono_UL_RxQuality_Rxl s
evel QoS Mono-Object I
Distribution reports P

Thanks to RMS, check if  Select the bad cell and Drag  C

path balance of the cell is and drop in the QoS v
bad Notebook for “yesterday” a
both a
Alc_Mono_Radio_Link_detail
ed QoS Mono-Object
Distribution reports
 Or Select the bad cell and
Drag and drop in the  O
Spreadsheet for “yesterday” P
the RMS_PathBalance_avg b
QoS indicator
I
e
b
t
I
t
p

Thanks to RMS, check if  Select the bad cell and Drag  O

each of the path balance of and drop it in the TRX’s tab T
the TRXs of the cell is bad  Drag and drop in the B
Spreadsheet for “yesterday” o
the RMS_PathBalance_avg [
QoS indicator
I
t
s
I
t
p
s
 t
s
I
t
p
s

Check that the Number of Select the bad cell and Drag and Check
Handover per Call is low drop in the Spreadsheet for
(< 0,3 for instance) “yesterday” the If “
RTCH_HO_per_Call Ai
QoS indicator If “
inc
de

Check if some incoming Select the bad cell and Drag and If a
adjacency is not defined as drop the Quick diagnosis that de
outgoing checks if an adjacency is Ch
declared in both ways (if this sh
quick diag does not exist then ne
create it as described in Annex3) Els

Check if a surrounding cell  Display on the map the HO If t

should be declared as a traffic flow indicators to check ne
neighbour where most of the handovers ad
are taking place
(see Annex4) If t
ne
 Check the distribution of TA ex
values to check where the mo
traffic is located in the cell:
?
 Use drive tests and RNP
coverage and best server
maps if available

Create the adjacency Create and Export a Tuning 

Session to the OMC-R (see
Annex5)

Find if the existing coverage Use RMS indicators based on TA Confirm

 maps if available

Create the adjacency Create and Export a Tuning 

Session to the OMC-R (see
Annex5)

Find if the existing coverage Use RMS indicators based on TA Confirm

problem is more indoor or values (see Annex6) team
outdoor
If R
co
en
an
tilt

If R
Pla
an
tilt
aT
Quick diagnosis used to detect non symmetrical incoming adjacency

/* *****************************************************************
* back-up of scenario : Non symmetrical incoming adjacency
* created on 08/18/2005 03:50:26 PM
* *****************************************************************/
QUICK_SCENARIO "Non symmetrical incoming adjacency"
DESCRIPTION "" ;
// NO associated indicator
OWNER "rno" ;
END_QUICK_SCENARIO

// ------------------------------------------------------
NODE "Non symmetrical incoming adjacency":"neighbours list"
DESCRIPTION {"No description"}
CONTEXT { CELL c;
PERIOD p;
DATE d;
}
LOCAL {LIST CELL neighbours_list = N:Serving_Cells( c, OPER );

}
ACTION {""}
TEST_DESCRIPTION {"No description"}
TEST_VALUE { }
 PERIOD p;
DATE d;
}
LOCAL {LIST CELL neighbours_list = N:Serving_Cells( c, OPER );

}
ACTION {""}
TEST_DESCRIPTION {"No description"}
TEST_VALUE { }
END_NODE

// ------------------------------------------------------
NODE "Non symmetrical incoming adjacency":"check adjacency symmetry"
DESCRIPTION {"No description"}
CONTEXT {CELL c;
CELL neighbours_list;}
LOCAL {LIST CELL serving_of_neighbours = N:Serving_Cells ( neighbours_list, OPER )
BOOLEAN ok = c IN serving_of_neighbours;}
ACTION {""}
TEST_DESCRIPTION {"No description"}
TEST_VALUE { NOT ok; }
END_NODE

// ------------------------------------------------------
FIRST_NODE "Non symmetrical incoming adjacency":"Non symmetrical incoming adjace
DESCRIPTION {"No description"}
CONTEXT {CELL c;
DATE d;
PERIOD p;}
LOCAL {}
ACTION {""}
END_NODE

// links
LINK "Non symmetrical incoming adjacency":"neighbours list" "Non symmetrical incom
symmetrical incoming adjacency"
DESCRIPTION {"No description"}
CALLING {
c = c;p = p;d = d; }
RESTRICTION { }
END_LINK
LINK "Non symmetrical incoming adjacency":"check adjacency symmetry" "Non symme
adjacency":"neighbours list"
DESCRIPTION {"No description"}
CALLING {
c = c;neighbours_list = neighbours_list; }
RESTRICTION { }
END_LINK
 RESTRICTION { }
END_LINK
LINK "Non symmetrical incoming adjacency":"check adjacency symmetry" "Non symme
adjacency":"neighbours list"
DESCRIPTION {"No description"}
CALLING {
c = c;neighbours_list = neighbours_list; }
RESTRICTION { }
END_LINK
 on advanced level / B8
w to do Exo on RNO

the impacted zone WZ: Freefield, QOS High/Low; WZ cell

y symptoms Reports: Warn,Multi, Degradation?
y reports Define Indicators KPI (Methode; Best of)
y Global KPI Create a Warn report KPI
est,call,HO,traff(sleep cell)

l Qos indicators Reports: Mono, RMS, Warning RMS

y cause(s) suspected Correlation with events
o, Interfer, congest , coverage, HO, Sys.. Indicators details: distributed KPI;reliability
ent Pb? HO distribution / HO Causes (without Susc
b? Map: Thematic Layer; Traffic localisation
X? / for the Busy hour?

RMS (RMS / MAFA report creation???)

osis usage; Quick Diag Diag / Quick Diag: HO no Symetrique
ng Pb: Frq; Bsic, Coverage, Ncell OmcR / Laser
est => RMS Map /Frq reuse / Mafa / Neighbourhood
Thematic layer sur TA
Rules; Events
GPRS

Map: Create new project

Find Planned cell on the map
pacted elements Manual Import
he prirority Parm -> Table; Rules
y algo. and parameters Tuning session: Frequencies /Design
algo.,param.,design HW
Create new QOS Ind
RMS template
l QOS indicators
ement or degradation?
Export: Diag, Indic, Design, Excel
Matrix (send to RNP)
ustomise RNO Save report
Extractor
Customise RNO.ini / Settings
Save profile on another client
CITRIX?

Red= new in B8

degradation

QoS problems and their causes

----------------------------------------------------------------------
d above ?

uality (RXQUAL))

----------------------------------------------------------------------
ad coverage”, “interference” and “system problem” can

e needed (BSS (radio) or NSS or PSTN).

Abis transmission, IPE, in the NSS, in the PSTN)

es connections)
smatch regarding Signalling and Traffic channel
Abis transmission, IPE, in the NSS, in the PSTN)
es connections)
smatch regarding Signalling and Traffic channel

Coverage Interference System pb

(1) (2)
X X
(3)
X X X

(4)
X

X X X

(5)
X X X

X X X

(7)
X X X
 (7)
X X X

(9) (10) (11)

X X X

(12) (13)
X X
(14) (15) (16)
ype,Xcables) X X
em:

(17)
X

, NSS or PSTN)

failures”. They are not network problems.

roblem or an Abis microwave problem.

age has not been decoded due to a too bad coverage in

sage has not been decoded due a too high interference

an inter-BSC handover is not available or can be due to

a mobile failure to return to the old channel

by a mobile failure to return to the old channel

can be due to:

EV decreases)
increases)
increases)
 a mobile failure to return to the old channel
by a mobile failure to return to the old channel

can be due to:

EV decreases)
increases)
increases)

re problem in the voice data processing algorithms (MS,

PROBLEM

ll of the network for yesterday?

indicator for all cells of the network for “yesterday”

k the trainee to use the B9 feature “column and row
peak of TCH congestion rate.
TCH congestion rate indicator from worst to best.

ning Red Threshold Report including a view where the

eate it from a copy of an existing one similar (View

or View Alc_RTCH_congestion in
k the trainee to use the B9 feature “column and row
peak of TCH congestion rate.
TCH congestion rate indicator from worst to best.

ning Red Threshold Report including a view where the

eate it from a copy of an existing one similar (View

or View Alc_RTCH_congestion in

e indicator value over the Red Threshold will be in the

mber of TCH assignment requests have been rejected

al number of RTCH assignment requests

a view whose warning indicator is

r “yesterday”
r RTCH_assign_max_cong_rate indicator value.
e of congestion increase have occured. This cells might
hest number of TCH assignment requests having been

TE: search the causes

action Next check or task

QoS Notebook Confirm that congestion is

s including ”normal”
ily Mono QoS
including the
ong_max_rate
 QoS Notebook Confirm that congestion is
s including ”normal”
ily Mono QoS
including the
ong_max_rate

he Find a solution to reduce the

_system_conges TCH congestion (see
dicator value is Question3)
during the day
e number of
RTCH TS are
the GP)
he
g_BH daily
ue is over the
city of the cell at
esponding to
the Red
tached to the
n_cong_max_r
ndicator
S Mono-
port with a view

e bar chart part:

H_nb_avg and
H_Erlang_total
e curve part:
H_time_system
ngestion

QoS Notebook If there was a PM counter

including reporting problem the last
ourly Mono hourly indicator values of the
eport including day will be the same (NPA
 H_time_system
ngestion

QoS Notebook If there was a PM counter

including reporting problem the last
ourly Mono hourly indicator values of the
eport including day will be the same (NPA
n_cong_rate extrapolation) and this is why
the daily indicator value is
_Mono_QoS wrong as it is computed from
moving all the hourly values of the
ong_max_rate same day.
_congestion
Then relay the problem to
max_rate from BSS O&M team
al_congestion
2 indicators are
hour)

op in QoS
ain for several If some events are present,
ing “yesterday”
ily Mono QoS
click on Legend button
port including
and show events’ details
n_cong_max_r
Then relay the problem to
but select the
BSS O&M team
with network
n after having
ow event filter
op in
the O&M
cells for the

Spreadsheet If value is not 0 then relay to

s the QoS BSS O&M team
 ow event filter
op in
the O&M
cells for the

Spreadsheet If value is not 0 then relay to

s the QoS BSS O&M team

ble_nb_avg

traffic evolution If a neighbor cell had a

cells and its noticeable decrease of its
he last 7 days RTCH traffic:
check if some O&M
ighlight all configuration change has
e map window, been done on neighbor
ad cell in the cells or on adjacencies
w, (ex: cell barring,
op in the map, BS_TXPWR_MAX)
ad cell in the thanks to RMS, check if
path balance of neighbor
cells has become bad
or just
ouse over the

hlight target
map,
ect highlighted
e map,
pagate

g_BH indicator,
op in the
by selecting
ys period of

ad cell in the
w,

g_BH indicator,
op in the
ys period of

ad cell in the
w,

g_BH indicator,
op in the

n by selecting
ys period of

n the If cell is barred then the

e cell logical RTCH_HO_ per_Call
indicator value of the bad cell
CESS and may have increased because
UALIFY some incoming better cell
handovers are likely to be
performed to the barred cell
after call set-up
Then relay the problem to
BSS O&M team

If cell path balance value is

op the bad then relay the problem to
Balance_avg BSS Site engineering team
the
et
op te
_link_detailed
e QoS

RNO Activate BSS PM Type 5 for

this cell (GP=1h) providing
counters per TCH TS and
check from counters that
some TS are never allocated
(C370A+C370B=0) and
always used for traffic
(C380A+C380B=0s)
and relay the problem to BSS
 this cell (GP=1h) providing
counters per TCH TS and
check from counters that
some TS are never allocated
(C370A+C370B=0) and
always used for traffic
(C380A+C380B=0s)
and relay the problem to BSS
O&M team

RNO 2 possibilities:
 activate BSS PM Type 5
for this cell (GP=1h)
providing counters per
TCH TS and
check from counters that
some TS are never
allocated
(C370A+C370B=0) and
never used for traffic
(C380A+C380B=3600)
 check MPM QoS Alerters
“TCH hanging” per TRX:
(MC380a(b)/3600) >=
0.95 && (MC370a(b) <
20)
a for FR / b for HR
and relay the problem to BSS
O&M team

ram., Indic., Rep.,Map

mal”, i.e. which is due to a too high subscriber traffic

TCH congestion is not “normal”, i.e. is not due to a too

He writes them on the board as below:
gineering team has to perform recovering actions

ms
 TCH congestion is not “normal”, i.e. is not due to a too
He writes them on the board as below:
gineering team has to perform recovering actions

ms

d TRX capacity in the cell in congestion or BSS

n by:

at can degrade the QoS in the meantime especially in a

neighbors. The only way to allow FDR to some cells and

et cell: L_RXLEV_NCELL_DR(n) set to –47dBm forbids
no incoming FDR can be performed to that specific cell.
neighboring cells having the best coverage overlap with

ghest ratio of handovers are performed (for instance

ongestion but that can degrade the QoS in the meantime

ver the QoS degradation should be less because the
d at the border of the serving cell since the triggering

It is therefore possible to allow THO towards some

h have no RTCH congestion problem.

e Fast Traffic HO, Traffic HO and Forced Directed

cell?
ction Result

d cell in the  Outgoing adjacencies

of the Object are displayed and sorted
according the ratio of
Reverse outgoing handovers
which is also displayed

equest_dist_s

p in the

n the
according to
alue in
der
going  All neighbor cells to
epresenting which more than 20% of
% of all the the outgoing handovers
dovers are performed are
m the cell in selected
agate

p in the Cell
w,
cell in

session,
 Forced Directed Retry
CELL_DR(n) and Fast Traffic HO are
implemented
p in the Tuning
w,
cell in

session,
 Forced Directed Retry
CELL_DR(n) and Fast Traffic HO are
implemented
p in the Tuning
nager

arameter
,
in

_DR,
_DR and
RAFFIC_HO

p in the Tuning
nager

eter values to

ng session
lue, the better the congestion decrease in the cell in

on Result

congestion  All outgoing adjacencies of

window, the cell in congestion are
the displayed on the map
t window,
the map,
ght all

e cell in  All neighbor cells of the cell

he Cell in congestion are selected
the map, in the Cell Object Window
light

t target
ght all

e cell in  All neighbor cells of the cell

he Cell in congestion are selected
the map, in the Cell Object Window
light

t target
ect
ts,
te
 All neighbor cells are
colored on the map
ong_max_r according to their
tors RTCH_assign_cong_max_r
ate indicator value
the
weekly
ek,
ode,  All outgoing adjacendies to
Carto neighbor cells having no
cy object TCH congestion problem
(RTCH_assign_cong_max_r
e in the ate indicator value lower
than the yellow threshold)
all the are selected in the
een the Adjacency Object window
and all its
displayed

te selection
 Traffic HO is implemented
ssion,

O(0,n)

the Tuning
ger

ENABLE”,
session
 the Tuning
ger

ENABLE”,
session

g Traffic HO with reasonably low value of

C_HO_MARGIN(neighbor) parameters. The higher the
gestion but the worse the possible quality degradation.

problem

ge problem

twork for yesterday

n the following condition based on QoS indicators is

dard_rate( c, d, p ) > 0.05;
_rate( c, d, p ) > 0.02;
ail_radio_rate( c, d, p ) > 0.02;
_rate( c, d, p ) > 0.5;

me:

AND SDCCH_drop_radio_rate AND

overage problem":"Coverage problem"

 t of calls are experiencing a bad radio quality due to a
etected using the radio statistics reported by the BTS

t_RMS_Radio_Link Warning QoS report in the QoS

d the cells having the worst Average RXQual DL are

didate for being degraded due to a coverage problem.

eas the UL RxLevel is not. Also the Average RxQual UL

s stage of the exercise is to ask the trainees to add 2

w where the Filtering and Sorting indicator is replaced

vg view where the Filtering and Sorting indicator is

m of coverage

action Next check or task

ll and Drag and Check if there is a zone of

Notebook for considerable traffic (nb of
samples) where quality is
xQuality_Rxlevel bad (>4) and level is low (<-
90 dBm)
xQuality_Rxlevel (see Annex2)
t Distribution If “no” then Carry out
the investigation of an
interference problem or
a system problem
If “yes” then Check if
bad coverage is
observed for all TRXs
of the cell

d cell and Drag Check if the distribution of

the TRX’s tab the samples in the cell
p in the QoS matrix is the observed in all
“yesterday” TRX’s matrixes

L_RxQuality_Rxl If “no” then carry out the

investigation of a
L_RxQuality_Rxl system problem
no-Object If “yes” then Check
eports Path Balance of the cell
L_RxQuality_Rxl If “no” then carry out the
investigation of a
L_RxQuality_Rxl system problem
no-Object If “yes” then Check
eports Path Balance of the cell

d cell and Drag  Check if Path Balance

he QoS vector indicator values
“yesterday” are well distributed
around 0dB
adio_Link_detail
o-Object
eports
bad cell and
p in the  Or Check if the Average
for “yesterday” Path Balance value is
thBalance_avg between –3dB and 3dB
r
If “no” then Check if
each of the path
balance of the TRXs of
the cell is bad
If “yes” then Check if
the number of handover
per call is low

d cell and Drag  Or Check if the all the

the TRX’s tab TRX Average Path
p in the Balance values are
for “yesterday” outside the
thBalance_avg [–3dB, 3dB] interval
r
If “no” then Carry out
the investigation of a
system problem
If “yes” then Carry out
the investigation of
problem on the antenna
systems
 the investigation of a
system problem
If “yes” then Carry out
the investigation of
problem on the antenna
systems

ll and Drag and Check if the value is low (< 0,3)

dsheet for
If “no” then Trace Abis and
Call A interface and analyze
If “yes” then Check if some
incoming adjacency is not
defined as outgoing

ll and Drag and If all adjacencies are

agnosis that declared in both ways then
cency is Check if a surrounding cell
ways (if this should be declared as a
not exist then neighbour
ibed in Annex3) Else declare the incoming

e map the HO If there is a missing

dicators to check neighbour then Create the
of the handovers adjacency
ace
If there is no missing
neighbour then Find if the
stribution of TA existing coverage problem is
ck where the more indoor or outdoor
ed in the cell:

ts and RNP
d best server
able

rt a Tuning 
MC-R (see

ors based on TA Confirm the problem with RNP

able

rt a Tuning 
MC-R (see

ors based on TA Confirm the problem with RNP

x6) team

If RNP team does not

confirm then Ask the site
engineering team to check
antenna height, azimuth and
tilt

If RNP does not confirm then

Plan a new site or Change
antenna height, azimuth or
tilt or Add a repeater or Add
a TMA if UL limited
jacency

st"

PER );
PER );

ncy symmetry"

ls ( neighbours_list, OPER );

symmetrical incoming adjacency"

st" "Non symmetrical incoming adjacency":"Non

ncy symmetry" "Non symmetrical incoming

ncy symmetry" "Non symmetrical incoming
 Usage of RMS for optimization purposes

RMS activation

RMS counters (type 31) should be activated for the OMC, as PM

period that will include the busy hours.

check if the RMS measurement is enough

Cell RMS_meas_results_total RMS_seized_TCH_tota

Cell_A 920785 12930
Cell_B 156743 1306
Cell_C 13776 16

Global analysis of the RMS results

extracte the main RMS unit indicators and the main QoS indicato
zone and two frequency bands (to compare the 2 bands If the net
dual band network

Main RMS unit indicators WORKING ZONE (49 Cells) 1800 (24 Cells
RMS_meas_results_total (RMMSALN) ( nb ) 29016080 23172767
RMS_seized_TCH_total (RMMSTSN) ( nb ) 471944 337140
RMS_UL_ConsecutiveFrameErasure_RxLevel_total (RMFETN) ( nb ) 28392992 22770957
RMS_UL_ConsecutiveFrameErasure_avg (RMFEAN) ( nb ) 0,16 0,14
RMS_PathBalance_avg (RMPBAN) ( dB ) -9,3 -11.9 (corrected :
RMS_PathBalance_total (RMPBTN) ( nb ) 28577949 22898963
RMS_DL_Power_avg (RMQLDPWAN) ( dBm ) 40,9 40
RMS_UL_Power_avg (RMQLUPWAN) ( dBm ) 31,9 35.2 (corrected :
RMS_RadioLinkCounter_avg (RMRLAN) ( nb ) 75 75
RMS_RadioLinkCounter_total (RMRLTN) ( nb ) 28940120 23144994
RMS_DL_RxLevel_avg (RMQLDLVAN) ( dBm ) -73,72 -72,23
RMS_DL_RxQuality_RxLevel_total (RMQLDSATN) ( nb ) 28729949 23037294
RMS_DL_RxQuality_avg (RMQLDQUAN) ( nb ) 0,3 0,3
RMS_UL_RxLevel_avg (RMQLULVAN) ( dBm ) -88,78 -88,17
RMS_UL_RxQuality_RxLevel_total (RMQLUSATN) ( nb ) 29021816 23217397
RMS_UL_RxQuality_avg (RMQLUQUAN) ( nb ) 0,29 0,23
RMS_TimingAdvance_avg (RMQLUTAAN) ( nb ) 47,66 22,32
RMS_TimingAdvance_greater_threshold (RMTAGTN) ( nb ) 0 0
RMS_TimingAdvance_greater_threshold_rate (RMTAGTR) ( % ) 0 0
RMS_TimingAdvance_max (RMTAMXN) ( nb ) 522 239
RMS_TimingAdvance_threshold (RMAXTAN) ( nb ) 8 8
RMS_RadioLinkCounter_total (RMRLTN) ( nb ) 28940120 23144994
RMS_DL_RxLevel_avg (RMQLDLVAN) ( dBm ) -73,72 -72,23
RMS_DL_RxQuality_RxLevel_total (RMQLDSATN) ( nb ) 28729949 23037294
RMS_DL_RxQuality_avg (RMQLDQUAN) ( nb ) 0,3 0,3
RMS_UL_RxLevel_avg (RMQLULVAN) ( dBm ) -88,78 -88,17
RMS_UL_RxQuality_RxLevel_total (RMQLUSATN) ( nb ) 29021816 23217397
RMS_UL_RxQuality_avg (RMQLUQUAN) ( nb ) 0,29 0,23
RMS_TimingAdvance_avg (RMQLUTAAN) ( nb ) 47,66 22,32
RMS_TimingAdvance_greater_threshold (RMTAGTN) ( nb ) 0 0
RMS_TimingAdvance_greater_threshold_rate (RMTAGTR) ( % ) 0 0
RMS_TimingAdvance_max (RMTAMXN) ( nb ) 522 239
RMS_TimingAdvance_threshold (RMAXTAN) ( nb ) 8 8
RMS_call_abnormal_bad_FER (RMVQFEAN) ( nb ) 137166 82752
RMS_call_abnormal_bad_FER_rate (RMVQFEAR) ( % ) 29,06 24,55
RMS_call_noisy_DL (RMVQDNON) ( nb ) 17011 13519
RMS_call_noisy_DL_bad_coverage (RMVQDLVN) ( nb ) 4564 3182
RMS_call_noisy_DL_bad_coverage_rate (RMVQDLVR) ( % ) 0,97 0,94
RMS_call_noisy_DL_interference (RMVQDIFN) ( nb ) 12387 10315
RMS_call_noisy_DL_interference_rate (RMVQDIFR) ( % ) 2,62 3,06
RMS_call_noisy_DL_rate (RMVQDNOR) ( % ) 3,6 4,01
RMS_call_noisy_DL_undefined (RMVQDUKN) ( nb ) 60 22
RMS_call_noisy_DL_undefined_rate (RMVQDUKR) ( % ) 0,01 0,01
RMS_call_noisy_UL (RMVQUNON) ( nb ) 19857 10902
RMS_call_noisy_UL_bad_coverage (RMVQULVN) ( nb ) 13302 8117
RMS_call_noisy_UL_bad_coverage_rate (RMVQULVR) ( % ) 2,82 2,41
RMS_call_noisy_UL_interference (RMVQUIFN) ( nb ) 6426 2728
RMS_call_noisy_UL_interference_rate (RMVQUIFR) ( % ) 1,36 0,81
RMS_call_noisy_UL_rate (RMVQUNOR) ( % ) 4,21 3,23
RMS_call_noisy_UL_undefined (RMVQUUKN) ( nb ) 129 57
RMS_call_noisy_UL_undefined_rate (RMVQUUKR) ( % ) 0,03 0,02
RMS_call_noisy_bad_FER (RMVQFEBN) ( nb ) 14882 8582
RMS_call_noisy_bad_FER_rate (RMVQFEBR) ( % ) 3,15 2,55
RMS_call_noisy_good_FER (RMVQFEGN) ( nb ) 5683 2583
RMS_call_noisy_good_FER_rate (RMVQFEGR) ( % ) 1,2 0,77

· 1800 cells take almost three times more traffic (in terms of TCH
measurements) than the 900 cells: more capacity in 1800, and pre
from 900 to 1800.

· The average received level on downlink and uplink path on 900

on 1800 cells: around 7.5 dB lower in downlink and 3 dB lower in

· This lower received level in 900 cells do not bring quality proble
path: on 1800 and 900 cells, average DL RxQual is fair (consideri
RxQual starting at 0.5) and noisy call rate on downlink path is rat
1800 cells, 2.59 % on 900 cells (indicating that quality problems o
perhaps more in 1800 cells, perhaps due to a tighter frequency p
distribution causes of noisy calls on DL path)).

· On the contrary, on the uplink path, lower received level in 900 c

problematic:

¨ The average UL RxQual is higher than 0.5 in 900 cells, twice the
RxQual in 1800 cells.
distribution causes of noisy calls on DL path)).

· On the contrary, on the uplink path, lower received level in 900 c

problematic:

¨ The average UL RxQual is higher than 0.5 in 900 cells, twice the
RxQual in 1800 cells.

¨ The average Consecutive Frame Erasure is 0.24 in 900 cells, 0.1

¨ The noisy call rate on uplink path is 6.64% in 900 cells, more tha
1800 cells and the main cause of this UL noisy calls in 900 cells i

¨ 70% of these UL noisy calls in 900 cells suffer from bad Frame E
compared to 6.64%), indicating probable voice quality problems (
high UL Consecutive Frame Erasure

¨ Abnormal bad Frame Erasure Rate is more than 40% in 900 cells
around 25% in 1800 cells (however, these high values are quite s
due to a wrong tuning of the voice quality counters, i.e., the thres
be put higher).

· The good values of average path balance (close to 0 dB) in 900

seem to show that there is neither hardware nor installation prob
that could explain such UL quality problems (however, to be sure
analysis on a per TRX basis on each cell should be performed).

· The power control settings does not seem to be suspicious as i

average MS and BTS power in 900 cells are rather high, proving t
be often at maximum level, so as to compensate coverage proble
Control is also often – always ? - disabled).

· The average Radio Link Counter could also be applied to charac

link quality in 900 cells. However, the corresponding thresholds i
are wrongly tuned, giving always the same value for this average

· One explanation for these UL quality problems in 900 band coul

the 900 bands are the ones that could not be captured by 1800 ce
mobiles have naturally low received levels (especially when 900 a
· The average Radio Link Counter could also be applied to charac
link quality in 900 cells. However, the corresponding thresholds i
are wrongly tuned, giving always the same value for this average

· One explanation for these UL quality problems in 900 band coul

the 900 bands are the ones that could not be captured by 1800 ce
mobiles have naturally low received levels (especially when 900 a
co-located) and are more likely to suffer from interference (in cas
reappearance). Timing advance indicators could also show that m
are further from the sites, compared to mobiles in 1800 cells. How
and average timing advance are wrongly consolidated on a per c
problem has been reported to TD but no FR has been written on i
advance greater threshold rate could be applied with a lower thre
example) in order to get this information.

· More investigations can be performed while selecting the worst

analyzing deeper RMS data for this cell.

· When looking at the main QoS indicators on a per BSC and a pe

Table 4), it can be clearly seen that the UL quality problems in 900
through RMS has a major impact on QoS figures in this band (ho
reasons for this bad QoS could also be found, as outgoing hando
to high congestion rate in 900 cells).
 Main QoS indicators WORKING ZONE (49 Cells) 1800 (24 Cell
SDCCH_drop_BSS_rate (SDCDBR) ( % ) 0 0
SDCCH_drop_HO_rate (SDCDHR) ( % ) 0.06 0.04
SDCCH_drop_radio_rate (SDCDRR) ( % ) 0.73 0.38
SDCCH_drop_rate (SDCDR) ( % ) 0.79 0.42
call_cong_rate (QSCGR) ( % ) 2.74 2.1
call_drop_BSS_rate (QSCDBR) ( % ) 0.04 0.03
call_drop_HO_rate (QSCDHR) ( % ) 0.22 0.14
call_drop_radio_rate (QSCDRR) ( % ) 0.54 0.3
call_drop_rate (QSCDR) ( % ) 0.8 0.48
call_setup_success_rate (QSCSSR) ( % ) 98.49 99.07
call_success_rate (QSCCR) ( % ) 97.7 98.6

Next step (or the first step for a mono-band network) is a global a
network/working zone should be performed with the Top Worst R
order to detect the main problems in terms of radio link quality an
· Alc_warning_top_worst_rms_radio_link
· Alc_warning_top_worst_rms_ul_voice_quality
· Alc_warning_top_worst_rms_dl_voice_quality
From Alc_warning_top_worst_rms_radio_link, the worst cells can
· Average RxLevel (UL/DL)
· Average RxQuality (UL/DL)
· Average Power (UL/DL)
· Average PathBalance
· Average Uplink RadioLinkCounter
· Average Timing Advance
· Average Uplink Consecutive Frame Erasure

From Alc_warning_top_worst_rms_ul/dl_voice_quality, the worst

by:
· Split of uplink/downlink noisy calls causes
¨ Bad Coverage
¨ Interference
¨ Undefined

On important investigation, are the UL quality problems; the wors

in the UL voice quality report (and also in some specific UL meas
· Split of uplink/downlink noisy calls causes
¨ Bad Coverage
¨ Interference
¨ Undefined

On important investigation, are the UL quality problems; the wors

in the UL voice quality report (and also in some specific UL meas
Consecutive Frame Erasure and Radio Link Counter, that can be
link report).

Let’s take the next example:

CI UL noisy call rate … … due to bad coverage … due to interference … with bad FER
11075 12,8% 10,55% < 2% 10,72%
12175 11,7% 4,72% 6,83% 7,39%
13463 10,3% 7,93% < 2% 8,89%

Note: It is also important that these figures are based on sufficien

reliable statistics. In the case of the three cells above, each of the
5000 calls during the RMS job. It is seen as quite sufficient to get

From Table 5, it can already been seen that cell 11075 and 13643
coverage problems (perhaps due to some coverage holes) where
to suffer more from interference (for example due to coverage re-

For example, cell CI 13647 shows the highest average CFE (0.42)
suffer from bad RxQuality: they suffer only from bad frame Erasu
for this cell, UL noisy call rate is low (below 5 %) but calls sufferi
FER (bad FER while RxQual is fair) are a lot: more than half of the
suffer from bad FER. It is not quite clear in which radio condition
found.

From the QoS point of view (even if it’s not presented here), it see
11075 that is the worst cell:
· In terms of call drop rate, cells 11075 and 12175 are respectively
second and the fourth worst cell in the BSC (with call drop rate e
suffer from bad FER. It is not quite clear in which radio condition
found.

From the QoS point of view (even if it’s not presented here), it see
11075 that is the worst cell:
· In terms of call drop rate, cells 11075 and 12175 are respectively
second and the fourth worst cell in the BSC (with call drop rate e
3.48% and 2.95%, with a large part due to radio problems)
· In terms of call setup success rate, cells 11075 and 12175 are re
the second and the eighth worst cell in the BSC (with a call setup
to respectively 95.24% and 96.11%).
· In terms of incoming HO unsuccess rate, cell 11075 is ranked as
cell (with the highest incoming handover failure rate, equal to 7.7
· In terms of outgoing HO unsuccess rate, these cells are not see
cells. This can be seen as normal as radio problems in one cell d
outgoing HO success rate.

So, it seems more valuable to investigate RMS on the cell 11075,

improve not only the radio link quality in this cell but also the qua
provided to subscribers (another important criteria to take into ac
the amount of traffic in this cell compared to the total traffic in th
not done in this example).

Detailed analysis of the worst cell

The worst cell detected on the previous example (cell 11075) is a

only one TRX.
From the UL RxLevel distribution, it can be seen that a lot of
measurements show low received level on uplink path in this cel
of the measurements show an uplink received level lower than –9
The worst cell detected on the previous example (cell 11075) is a
only one TRX.
From the UL RxLevel distribution, it can be seen that a lot of
measurements show low received level on uplink path in this cel
of the measurements show an uplink received level lower than –9

Uplink RxLevel distribution

40

35

30

25

20

15

10

0
[-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]
RxLevel ( dBm )

According to the Average UL RxQuality according to UL RxLevel

received levels correspond to high RxQual: 0.8 between –91 dBm
between –97 dBm and –103 dBm, 5.2 between –104 dBm and –11

Uplink RxQuality per RxLevel

0
[-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]
RxLe vel ( dBm )
 2

0
[-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]
RxLe vel ( dBm )

This can be seen also on the average Consecutive Frame Erasure

RxLevel (See Figure 3): the average CFE is higher than 1 between
dBm and higher than 2 between –104 dBm and –110 dBm and thi
the measurements.

Uplink CFE per RxLevel

140000

120000

100000

80000

60000

40000

20000

0
[-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]
RxLevel ( dBm )

So, these low UL received levels are not acceptable, from the rad
point of view. It can be deduced that these low UL received levels
expected (like in an open area, with sensitivity limited environme
to coverage hole (bad network design) and/or interference (bad fr
The Average Timing Advance according to UL RxLevel graph (Se
that these low received levels do not correspond to high Timing A
more than 1 unit, that is 550 meters, for UL received level below –

Uplink Timing Advance per RxLevel

1.4

1.2
 Uplink Timing Advance per RxLevel

1.4

1.2

0.8

0.6

0.4

0.2

0
[-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]
RxLevel ( dBm )

This means that the coverage and/or interference problem should

border (cell environment is not dense and intersite distance mus
kilometer) but they are more likely to be in the service area of the

This is confirmed by the Average Timing Advance according to U

(Figure 5), where it can be seen that the highest Timing Advance
RxQual = 4, indicating that the quality should be rather fair at cell

Uplink Timing Advance per RxQuality

1.4

1.2

0.8

0.6

0.4

0.2

0
0 1 2 3 4 5 6 7
RxQuality ( nb )
 0.2

0
0 1 2 3 4 5 6 7
RxQuality ( nb )

On the contrary, RxQual higher than 4 correspond to lower avera

indicating that coverage and/or interference problems are not at
At this level, it can be interesting to look at the power control beh
does not reduce too much MS power, leading to this quality prob
levels on the uplink path.
For this to be possible, it is interesting to look at the Average MS
UL RxLevel graph and the Average MS power according to UL Rx

Uplink Power per RxLevel

35

30

25

20

15

10

0
[-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]
RxLevel ( dBm )

Uplink Power per RxQuality

33
32.5
32
31.5
31
30.5
30
29.5
29
28.5
28
0 1 2 3 4 5 6 7
RxQuality ( nb )
 31
30.5
30
29.5
29
28.5
28
0 1 2 3 4 5 6 7
RxQuality ( nb )

These graphs show that the MS power is not at maximum level at

level (32 dBm) and at highest RxQual (32.4 dBm and 32.2 dBm at
RXQUAL =5 and 6). The case of RxQual = 7 is particular for the M
is often linked to the Minimum Coupling loss.
So, it could be interesting to modify power control settings, so th
maximum MS power in the bad radio conditions. However, the po
is already very conservative:
Upper and lower thresholds are high (upper at –80 dBm and lowe
POW_INC_FACTOR and POW_RED_FACTOR (Power increase an
have default tuning (0.8 for the increase, 0.5 for the reduction).
POW_INC_STEP_SIZE and POW_RED_STEP_SIZE (Power increa
step size in case of only quality problems) are equal respectively
One could imagine to make the power control more reactive whil
POW_INC_FACTOR to 1.0, so that the MS power is quicker increa
level problems occur.

However, power control fine tuning does not seem to be the suffi
this problem. The good solution would be to identify the coverag
interference occur (one could for example, imagine a high buildin
not well covered and interfered by many cells at high floors).
So as to identify the possible interferers on cell 11075, it can be q
study the C/I overlap according to neighbour cells

CI overlap per Neighbour cells

40
35
 CI overlap per Neighbour cells

40
35
30
25
20
15
10
5
0

Neighbour cells ( nb )

The C/I overlap correspond to the average C/I computed from C/I
called “overlap” because more than interference, it shows the ov
that may or cannot interfere (for example, co-located 900 and 180
very low C/I but it does not mean they interfere each other, it only
have a strong overlap between them).
From Figure 10, it is possible to see that several 900 cells have la
cell 11075 (leading to possible interference). However, these cells
low C/I (it is higher than 12 dB) but this could be due to the C/I th
template: indeed this one does not really allow precise value at lo
Moreover, as these cells will low C/I are not identified as neighbo
(they are not expressed in CI but in (BSIC, BCC)), a search should
the vicinity of the cell 11075, so as to identify these possible inter

RMS template modification

Based on the first analysis of RMS results, it would be possible t

applied to all the cells where RMS was activated in order to have
between the samples. Let’s take the following example (this chan
according to the network in analysis):
Based on the first analysis of RMS results, it would be possible t
applied to all the cells where RMS was activated in order to have
between the samples. Let’s take the following example (this chan
according to the network in analysis):

C/I : changed from -63, -9, 1, 7, 11, 14, 17, 19, 21, 23, 63
to -63, -6, 4, 10, 14, 17, 20, 23, 26, 33, 63

CFE : changed from 0, 1, 2, 3, 4, 5, 8, 10, 12, 15, 25

to 0, 1, 3, 5, 7, 9, 12, 15, 18, 21, 25

Path Balance : changed from -110, -20, -19, -16, -11, 0, 11, 16, 19,
To -110, -15, -11, -7, -4, 0, 4, 7, 11, 15, 110

Radio Link Counter : changed from 0, 1, 4, 8, 12, 14, 16, 18, 20, 2
To 0, 1, 9, 13, 20, 21, 22, 23, 24, 25, 128

After these modifications, the same analysis as before should be

Example of some improvements after template modification:
· C/I: The samples are better distributed between the bands but s
samples in highest band for some cells
· CFE: The samples in the high bands are better evaluated but the
low values of CFE is reduced. This leads to higher CFE average
· Path Balance: Intervals smaller around 0 make average more pr
variable
· Radio Link counter: No modification in the results

There are 16 possible templates and each parameter can have a d

each template. Depending on the cell characteristics, the operato
different thresholds. For example, it is interesting to associate to
coverage limit, intervals that would provide an accurate computa
of measurements in low values of the RxLev, whereas, for a micr
more sense to look accurately at higher levels distribution.
different thresholds. For example, it is interesting to associate to
coverage limit, intervals that would provide an accurate computa
of measurements in low values of the RxLev, whereas, for a micr
more sense to look accurately at higher levels distribution.

General QoS analysis with RMS in RNO

mization purposes

vation

d for the OMC, as PMC, during a larger

de the busy hours.

surement is enough

RMS_seized_TCH_total
12930
1306
16

the RMS results

e main QoS indicators for whole working

he 2 bands If the network in analysis is a

ONE (49 Cells) 1800 (24 Cells) 900 (25 Cells)

16080 23172767 5843313
1944 337140 134804
92992 22770957 5622035
,16 0,14 0,24
9,3 -11.9 (corrected : 1.1) 1
77949 22898963 5678986
0,9 40 41,9
1,9 35.2 (corrected : 22.2) 29,2
75 75 75
40120 23144994 5795126
3,72 -72,23 -79,73
29949 23037294 5692655
0,3 0,3 0,33
8,78 -88,17 -91,21
21816 23217397 5804419
,29 0,23 0,54
7,66 22,32 26,12
0 0 0
0 0 0
22 239 283
8 8 8
40120 23144994 5795126
3,72 -72,23 -79,73
29949 23037294 5692655
0,3 0,3 0,33
8,78 -88,17 -91,21
21816 23217397 5804419
,29 0,23 0,54
7,66 22,32 26,12
0 0 0
0 0 0
22 239 283
8 8 8
7166 82752 54414
9,06 24,55 40,37
011 13519 3492
564 3182 1382
,97 0,94 1,03
387 10315 2072
,62 3,06 1,54
3,6 4,01 2,59
60 22 38
,01 0,01 0,03
857 10902 8955
302 8117 5185
,82 2,41 3,85
426 2728 3698
,36 0,81 2,74
,21 3,23 6,64
29 57 72
,03 0,02 0,05
882 8582 6300
,15 2,55 4,67
683 2583 3100
1,2 0,77 2,3

ffic (in terms of TCH seizures and

acity in 1800, and preferred band HO go

d uplink path on 900 cells is lower than

ink and 3 dB lower in uplink.

t bring quality problems on the downlink

ual is fair (considering a bad average
downlink path is rather low: 4.01 % on
at quality problems on downlink path are
a tighter frequency planning (ref. also to
)).

eceived level in 900 cells seem quite

n 900 cells, twice the value of average UL

 )).

eceived level in 900 cells seem quite

n 900 cells, twice the value of average UL

0.24 in 900 cells, 0.14 in 1800cells

n 900 cells, more than twice the value in

sy calls in 900 cells is bad coverage.

fer from bad Frame Erasure Rate (4.67%

ce quality problems (also shown by the

than 40% in 900 cells, whereas it is

gh values are quite suspicious, perhaps
unters, i.e., the threshold on FER should

close to 0 dB) in 900 cells and 1800 cells

nor installation problem at BTS sites
(however, to be sure on that, a deeper
ould be performed).

to be suspicious as it can be seen that

ather high, proving that the powers must
sate coverage problems (BTS Power

be applied to characterize uplink radio

ponding thresholds in the RMS templates
alue for this average

ems in 900 band could be that mobiles in

captured by 1800 cells. So these
especially when 900 and 1800 cells are
 be applied to characterize uplink radio
ponding thresholds in the RMS templates
alue for this average

ems in 900 band could be that mobiles in

captured by 1800 cells. So these
especially when 900 and 1800 cells are
m interference (in case of coverage
ould also show that mobiles in 900 cells
les in 1800 cells. However, the maximum
nsolidated on a per cell zone basis (this
has been written on it). The timing
lied with a lower threshold (2 for

e selecting the worst cell in 900 band and

n a per BSC and a per band basis (ref. to

uality problems in 900 cells detected
ures in this band (however, others
d, as outgoing handover problems due
ONE (49 Cells) 1800 (24 Cells) 900 (25 Cells)
0 0 0
.06 0.04 0.09
.73 0.38 1.52
.79 0.42 1.61
.74 2.1 4.28
.04 0.03 0.07
.22 0.14 0.53
.54 0.3 1.44
0.8 0.48 2.03
8.49 99.07 96.86
7.7 98.6 94.89

network) is a global analysis on the

with the Top Worst RNO reports in
f radio link quality and voice quality:

lity
lity
k, the worst cells can be filtered by:

ce_quality, the worst cells can be detected

y problems; the worst cell is to be found

me specific UL measurements as
y problems; the worst cell is to be found
me specific UL measurements as
Counter, that can be found in the radio

to interference … with bad FER Average CFE average RLC

< 2% 10,72% 0,32 74,8
6,83% 7,39% 0,3 74,5
< 2% 8,89% < 0.3 75

re based on sufficient calls, so as to give

ls above, each of them had more than
quite sufficient to get reliable results.

ell 11075 and 13643 suffers from serious

overage holes) whereas cell 12175 seems
e due to coverage re-appearance).

t average CFE (0.42) but calls do not

rom bad frame Erasure Rate. That’s why,
5 %) but calls suffering from abnormal bad
more than half of the calls (exactly 54 %)
hich radio conditions such results can be

resented here), it seems that it is the cell

2175 are respectively ranked as the

(with call drop rate equal to respectively
 hich radio conditions such results can be

resented here), it seems that it is the cell

2175 are respectively ranked as the

(with call drop rate equal to respectively
dio problems)
075 and 12175 are respectively ranked as
SC (with a call setup success rate equal

ell 11075 is ranked as the seventh worst

ure rate, equal to 7.72%).
ese cells are not seen in the 10 worst
oblems in one cell do not really impact its

MS on the cell 11075, so as to try to

s cell but also the quality of service
criteria to take into account would also be
the total traffic in the BSC, but this was

of the worst cell

mple (cell 11075) is a 900 cell with

een that a lot of

plink path in this cell: almost 50%
ed level lower than –90 dBm.
mple (cell 11075) is a 900 cell with

een that a lot of

plink path in this cell: almost 50%
ed level lower than –90 dBm.

vel distribution

% RxLev distrib

[-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]

rding to UL RxLevel graph , these low UL

0.8 between –91 dBm and –96 dBm, 2.7
n –104 dBm and –110 dBm.

ality per RxLevel

140000

120000

100000

80000
RxQuality Avg
60000
Nb Lev Samples
40000

20000

0
72,-66[ [-66,-60[ [-60,-53[ [-53,-47]
 60000
Nb Lev Samples
40000

20000

0
72,-66[ [-66,-60[ [-60,-53[ [-53,-47]

cutive Frame Erasure according to UL

igher than 1 between –96 dBm and –103
nd –110 dBm and this concerns 18% of

E per RxLevel

4
Nb Lev Samples
3
CFE Avg
2 RxQuality Avg

0
-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]

eptable, from the radio and voice quality

w UL received levels are not to be
ty limited environment) but they are due
r interference (bad frequency planning).
L RxLevel graph (See Figure 4) indicates
pond to high Timing Advance: a little
eceived level below –90 dBm.

dvance per RxLevel

140000

120000
dvance per RxLevel

140000

120000

100000

80000
TA Avg
60000
Nb Lev Samples
40000

20000

0
-72,-66[ [-66,-60[ [-60,-53[ [-53,-47]

ence problem should not be at cell

tersite distance must be more than 1
he service area of the cell.

vance according to UL RxQuality graph

est Timing Advance is obtained at
d be rather fair at cell border.

ance per RxQuality

300000

250000

200000

150000 TA Avg
Nb Samples
100000

50000

0
5 6 7
 50000

0
5 6 7

spond to lower average Timing advance,

problems are not at cell border ….
he power control behavior, to check if it
g to this quality problems at low received

ok at the Average MS power according to

r according to UL RxQuality graph.

er per RxLevel

140000

120000

100000

80000
MS Power Avg
60000
Nb Lev Samples
40000

20000

0
72,-66[ [-66,-60[ [-60,-53[ [-53,-47]

r per RxQuality

300000

250000

200000

150000 MS Power Avg

100000
Nb Qual
Samples
50000

0
5 6 7
 200000

150000 MS Power Avg

100000
Nb Qual
Samples
50000

0
5 6 7

at maximum level at the lowest received

Bm and 32.2 dBm at respectively
s particular for the MS power because it
.
ontrol settings, so that it ensures
ons. However, the power control settings

at –80 dBm and lower at –90 dBm).

R (Power increase and reduction factor)
for the reduction).
_SIZE (Power increase and reduction
re equal respectively to 6 dB and 2 dB.
ol more reactive while putting
wer is quicker increase when quality and

seem to be the sufficient solution for

identify the coverage hole where UL
magine a high building where indoor is
s at high floors).
cell 11075, it can be quite interesting to
r cells

Neighbour cells

300000

250000
 Neighbour cells

300000

250000

200000

150000
C/I overlap
Nb C/I Samples
100000

50000

/I computed from C/I distribution. It is

ence, it shows the overlap between cells,
-located 900 and 1800 cells will have a
ere each other, it only means that they

eral 900 cells have large overlap with 900

However, these cells do not show very
d be due to the C/I thresholds in the RMS
ow precise value at low C/I.
dentified as neighbour cells by RNO
CC)), a search should be performed in
y these possible interferers.

modification

would be possible to change the RMS

ated in order to have a better distribution
g example (this change is very specific
 would be possible to change the RMS
ated in order to have a better distribution
g example (this change is very specific

9, 21, 23, 63

, 15, 25

-16, -11, 0, 11, 16, 19, 20, 110

8, 12, 14, 16, 18, 20, 22, 128

as before should be performed.

ate modification:
ween the bands but still high number of

tter evaluated but the precision on the

higher CFE average
ake average more precise and more

results

rameter can have a different value on

teristics, the operator could apply
sting to associate to a rural cell in
an accurate computation of the number
whereas, for a micro cell, it would make
ls distribution.
 sting to associate to a rural cell in
an accurate computation of the number
whereas, for a micro cell, it would make
ls distribution.

with RMS in RNO

 Indicator Sensitivity
High sensitivity
RMS_UL_ConsecutiveFrameErasure_avg Medium sensitivity

Low sensitivity

High sensitivity
RMS_DL_RxLevel_avg Medium sensitivity

Low sensitivity

High sensitivity
RMS_DL_RxQuality_avg Medium sensitivity
Low sensitivity
High sensitivity
RMS_UL_RxLevel_avg Medium sensitivity
Low sensitivity
High sensitivity
RMS_UL_RxQuality_avg Medium sensitivity
Low sensitivity
High sensitivity
RMS_Call_abnormal_bad_FER_rate Medium sensitivity
Low sensitivity
High sensitivity
RMS_Call_noisy_DL_bad_coverage_rate Medium sensitivity
Low sensitivity
High sensitivity
RMS_Call_noisy_DL_interference_rate Medium sensitivity
Low sensitivity
High sensitivity
RMS_Call_noisy_DL_rate Medium sensitivity
Low sensitivity
High sensitivity
RMS_Call_noisy_UL_bad_coverage_rate Medium sensitivity
Low sensitivity
High sensitivity
RMS_Call_noisy_UL_interference_rate Medium sensitivity
Low sensitivity
 High sensitivity
RMS_Call_noisy_UL_rate Medium sensitivity
Low sensitivity
High sensitivity
RMS_Call_noisy_bad_FER_rate Medium sensitivity
Low sensitivity
Red threshold Orange threshold Yellow threshold
0.4 0.3 0.2
0.5 0.4 0.3
0.6 0.5 0.4
-85 -80 -75
-90 -85 -80
-95 -90 -85
0.7 0.4 0.2
0.8 0.5 0.3
0.9 0.6 0.4
-90 -85 -80
-95 -90 -85
-100 -95 -90
0.7 0.4 0.2
0.8 0.5 0.3
0.9 0.6 0.4
0.4 0.2 0.1
0.4 0.2 0.1
0.4 0.2 0.1
0.08 0.06 0.04
0.1 0.08 0.06
0.12 0.1 0.08
0.08 0.06 0.04
0.1 0.08 0.06
0.12 0.1 0.08
0.08 0.06 0.04
0.1 0.08 0.06
0.12 0.1 0.08
0.08 0.06 0.04
0.1 0.08 0.06
0.12 0.1 0.08
0.08 0.06 0.04
0.1 0.08 0.06
0.12 0.1 0.08
0.08 0.06 0.04
0.1 0.08 0.06
0.12 0.1 0.08
0.08 0.06 0.04
0.1 0.08 0.06
0.12 0.1 0.08
 KPI - Network Management Statistics GLOBAL PRE-REQUISITES
- Usual coverage probability (outdoor environment / typical topology)
- Inter-sites distance on the drive test route as recommanded by design Thresold condition valid for:
- Enough available spectrum in relation with requested threshold
- Bandwidth free of internal and external interferences - Thresohld after 6 to12 months optimisation services minimum
- Network in a stable state (network frozen / no maintenance actions during the tests) (depends on NW size, KPIs thresholds)
- Cells impacted by network element or transmission problems excluded from statistics - RNO Consolidation at Working Zone or Network level
- Consolidation unit: week or month
KPI Computation - Tests performed within an area with low traffic / no congestion - Inter-sites distance
- Tests performed outside busy hour - Dense Urban: from 300 to 2000m - average 1000m
- Isolated cells (border coverage) as well as road tunnels and other non-significant cells impacted significantly the KPI to be excluded - Urban: from 800 to 5000m - average 2000m
from statistics - Sub-urban: from 1000 to 15000m - average 4000m
- All missing sites on the drive test route to test (from Alcatel design) will be excluded from statistics and a redefinition of drive Test - Rural: >2000m - average 8000m
routes, adaptation or weave of associated KPI commitments will be discussed with customer
- Threshold computation at network or BSC level per week

STANDARD KPIs VALUES OVER-COMMITTED KPIs VALUES

BSS GSM KPI

DESCRIPTION B8 FORMULA Common Dense
Urban Sub urban Rural
NETWORK OPTIM PROJECT NETWORK OPTIM PROJECT Remarks
Threshold urban DESIGN SERVICE PLANNING DESIGN SERVICE PLANNING

Call Drop
Rate of call drop : % of TCH dropped after successful assignment. .
(MC736+MC621+MC14c+MC739+MC921c)/
% Call Drop Incoming HO are added and outgoing HO are removed from the 1.50% 1.2% - 1.3% 1.3% - 1.5% 1.5% - 1.8% 1.8% - 2 % LOW LOW MEDIUM MEDIUM HIGH HIGH - KPI highly linked to frequency bandwidth availability , Initial RNP and roll-out pace
(MC718+MC717a+MC717b-MC712)
number
Rate of TCH call drops due to radio problem, handover failure or BSS
problem (MC736+MC621+MC14c+MC739+MC921c)/
% RTCH drop 1.20% 1 % - 1.1% 1.1% - 1.3% 1.3% - 1.5% 1.5% - 2 % LOW LOW MEDIUM MEDIUM HIGH HIGH - KPI highly linked to frequency bandwidth availability , Initial RNP and roll-out pace
Number of TCH dropped on a cell (Radio / System/HO) among the (MC718+MC717a+MC717b-MC662)
number of TCH seized within the cell
Call Establishment
[ 1 - ( MC138 + MC07 + MC137) / ( MC01 + MC02 ) ] * [ 1 -
i.e from SDCCH seizure till TCH seizure (SDCCH failures not
% Call Setup Success Rate (Alcatel formula) ( ( MC140a - (MC142e+MC142f) - MC718) / ( MC140a - 97% 97.50% 97% 96.50% 95% LOW LOW MEDIUM HIGH MEDIUM HIGH
counted)
(MC142e+MC142f) ) ) ]
[ 1 - ( MC138 + MC07 + MC137) / ( MC01 + MC02 ) ] * [ 1 - - Major KPI , a special care on final formula (include or not SDCCH Congestion and SDCCH
i.e from SDCCH seizure till TCH seizure (SDCCH Congestion is Assign fail)
% Call Setup Success Rate (1st optional formula) ( ( MC140a - (MC142e+MC142f) - MC718) / ( MC140a - 96.5% 97% 96.50% 96% 94% LOW LOW MEDIUM HIGH MEDIUM HIGH
counted but not SDCCH Assign failures) - Risk linked with available capacity and roll-out pace
(MC142e+MC142f) ) ) ]
[ 1 - ( MC138 + MC07 + MC137) / ( MC01 + MC02 ) ] * [ 1 -
i.e from SDCCH Assignment till TCH seizure (BOTH SDCCH Cong
% Call Setup Success Rate (2nd optional formula) ( ( MC140a - (MC142e+MC142f) - MC718) / ( MC140a - 96% 96.50% 96% 95.5% 94% LOW LOW MEDIUM HIGH MEDIUM HIGH
and SDCCH Assign failures are counted)
(MC142e+MC142f) ) ) ]
- Network design ensure a very low blocking rate : maximum 0.5 % for the high thresold
commitment
% RTCH_Assign_Cong % RTCH assign failure Congestion MC812 / MC140a 2% 1% 0.70% 0.50% 0.20% MEDIUM LOW MEDIUM HIGH MEDIUM HIGH
- Average congestion computed at network level
- Commit on a % of cells under congestion is not recommended
Rate of RTCH assignment failure due to BSS problems or Radio Link
%RTCH Assign Fail ((MC140a-MC812-MC718-MC746b+MC746B)/(MC703+MC812) 1.50% 1% 1.5% 2% 3% LOW LOW MEDIUM HIGH HIGH MEDIUM - KPI highly linked to frequency bandwidth availability , Initial RNP and roll-out pace
Failure. If no call on the cell, the rate is set to 0.
Rate of SDCCH drop due to BSS Problems, Radio Link Failure or
during HO procedure. If no SDCCH traffic, the rate is set to 0. HO
% SDCCH drop (MC07+MC137+MC138,MC01+MC02) 0.50% 0.5% 0.8% 1% 1.5% LOW LOW MEDIUM MEDIUM HIGH MEDIUM - KPI highly linked to frequency bandwidth availability , Initial RNP and roll-out pace
incoming and outgoing are omitted at denominator because of low
probability to occur.
SDCCH Congestion and Assignment Failures
- Network design ensure a very low blocking rate : maximum 0.5 % for the high thresold
Rate of SDCCH not allocated during radio link establishment due to commitment
%SDCCH_Assign_Cong (MC04) / (MC04+MC148) 1% 0.5% 0.8% 0.8% 0.8% MEDIUM LOW MEDIUM HIGH MEDIUM HIGH
congestion on Air interface. - Average congestion computed at network level

Rate of SDCCH unsuccessful seizures during radio link establishment - KPI not easy to optimise due to aspects out of radio control (Ghost RACH, over-shooting
%SDCCH_Assign_Fail (MC04 + MC148 – MC01 - MC02) /(MC04+MC148) 3% 2% 2.5% 3% >3% LOW LOW MEDIUM LOW MEDIUM LOW
(congestion, radio access problem, BSS Problem) sites…). Avoid to commit on this KPI , AND to include it in CSSR formula.
Intra+Inter BSC incoming handovers
Rate of successful incoming external and internal intercell SDCCH - KPI highly linked to finla BSS/TX/NSS architecture and topology. Can be affected during
% Success (MC642 + MC652) / (MC820 + MC830) 96% 96.5% 96% 95% 94% LOW LOW MEDIUM HIGH HIGH MEDIUM
and TCH handover. roll-out and hence should be considered in a stable topology.
Intra+Inter BSC outgoing handovers
Use Efficiency rate instead of Success rate (exclude preparation phase)
Rate of successful outgoing external and internal intercell SDCCH
% Efficiency (MC646 + MC656) / (MC650 + MC660) 96% 96.5% 96% 95% 94% LOW LOW MEDIUM MEDIUM HIGH MEDIUM KPI highly linked to finla BSS/TX/NSS architecture and topology. Can be affected during
and TCH handovers
roll-out and hence should be considered in a stable topology.
Paging Success Rate

(First_Page_Success +
% PSR Percentage of succesful paging requests . Meaured at NSS Level 90% 92% 90% 88% 85% LOW LOW MEDIUM HIGH LOW MEDIUM Depends mainly on MSC/BSC topology and on LAC planning.
Repeated_Page_Success)/First_Page_Attempt
 GSM KPI's name RNO QOS indicator Ref Name B8 formula B9 Formula
SDCCH Congestion and Assignment Failures
Requests SDCCH_Assign_Request SDNARQN MC04+MC148 MC04+MC148
SDCCH assign cong SDCCH_assign_cong SDNACGN
%SDCCH_Assign_Cong SDCCH_Assign_Cong_Rate SDNACGR MC04/(MC04+MC148) MC04/(MC04+MC148)
SDCCH assign fail BSS SDCCH_assign_fail_BSS SDNAFLBN
SDCCH assign fail radio SDCCH_assign_fail_radio SDNAFLRN
SDCCH assign succ SDCCH_assign_success SDNASUN

%SDCCH_Assign_Fail SDCCH_Assign_Fail_Rate SDNAFLR (MC148 - MC01 - MC02) / (MC04 + MC148) (MC148 - MC01 - MC02) / (MC04 + MC148)
SDCCH Drop (Call Estab)
SDCCH drop BSS SDCCH_drop_BSS SDCDBN
SDCCH drop HO SDCCH_drop_HO SDCDHN
SDCCH drop radio SDCCH_drop_radio SDCDRN
( ( [MC138] + [MC07] + [MC137]) / [MC01 + ( ( [MC138] + [MC07] + [MC137]) / [MC01
% SDCCH drop SDCCH_Drop_Rate SDCDR MC02]) + MC02])
RTCH preparation (Call Estab)
Requests RTCH_Assign_Request TCNARQN [MC140a-(MC142e+MC142f)] [MC140a-(MC142e+MC142f)]
Allocated RTCH_assign_allocated TCNACAN
Command RTCH_assign_command TCNACMN
RTCH assign cong RTCH_assign_cong TCNACGN
% RTCH_Assign_Cong RTCH_Assign_Cong_Rate TCNACGR ( [MC812] / [MC140a-(MC142e+MC142f)]) ( [MC812] / [MC140a-(MC142e+MC142f)])

RTCH prep fail BSS RTCH_assign_prep_fail_BSS TCNAFLPBN

%RTCH prep fail BSS RTCH_assign_prep_fail_BSS_rate TCNAFLPBR

RTCH execution (Call Estab)
RTCH assign succ RTCH_assign_success TCNASUN
%RTCH assign succ RTCH_assign_success_rate TCNASUR

RTCH exe fail BSS RTCH_assign_exe_fail_BSS TCNAFLEBN

% RTCH exe fail BSS RTCH_assign_exe_fail_BSS_rate TCNAFLEBR

RTCH fail radio RTCH_assign_fail_radio TCNAFLRN

% RTCH fail radio RTCH_assign_execution_fail_radio_rate TCNAFLRTR

( ( [MC746b] + [MC140b-MC718-MC746b]) / ( ( [MC746b] + [MC140b-MC718-
%RTCH Assign Fail RTCH_Assign_Fail_Rate TCNAFLR [MC140a-(MC142e+MC142f)]) MC746b]) / [MC140a-(MC142e+MC142f)])
( ( 1 - ( ( [MC138] + [MC07] + [MC137]) / ( ( 1 - ( ( [MC138] + [MC07] + [MC137]) /
[MC01 + MC02])) * ( 1 - ( ( [MC140a- [MC01 + MC02])) * ( 1 - ( ( [MC140a-
(MC142e+MC142f)] - [MC718]) / [MC140a- (MC142e+MC142f)] - [MC718]) / [MC140a-
%Call Setup success Call_setup_success_rate QSCSSR (MC142e+MC142f)]) )) (MC142e+MC142f)]) ))
Call Drop
Calls RTCH_Success_End TCAHCCN MC718+MC717a+MC717b-MC712 MC718+MC717a+MC717b-MC712
Drop BSS-int Call_drop_BSS_int_failure QSCDBIN
Drop BSS-RTC Call_drop_BSS_remote_TC QSCDBTN
Drop BSS Call_Drop_BSS QSCDBN ( [MC14C] + [MC739]) ( [MC14C] + [MC739])
( ( [MC14C] + [MC739]) / ( ( [MC718] + ( ( [MC14C] + [MC739]) / ( ( [MC718] +
% Drop BSS Call_Drop_BSS_Rate QSCDBR [MC717a + MC717b]) - [MC712])) [MC717a + MC717b]) - [MC712]))
Drop HO Call_Drop_HO QSCDHN MC621 MC621
( [MC621] / ( ( [MC718] + [MC717a + ( [MC621] / ( ( [MC718] + [MC717a +
% Drop HO Call_Drop_HO_Rate QSCDHR MC717b]) - [MC712])) MC717b]) - [MC712]))
Drop Radio Call_Drop_Radio QSCDRN MC736 MC736
( [MC736] / ( ( [MC718] + [MC717a + ( [MC736] / ( ( [MC718] + [MC717a +
% Drop Radio Call_Drop_Radio_Rate QSCDRR MC717b]) - [MC712])) MC717b]) - [MC712]))
Preemption Call_drop_preemption QSCDPN
( ( [MC736] + [MC621] + ( [MC14C] + ( ( [MC736] + [MC621] + ( [MC14C] +
[MC739]) + [MC921c]) / ( ( [MC718] + [MC739]) + [MC921c]) / ( ( [MC718] +
% Call Drop Call_Drop_Rate QSCDR [MC717a + MC717b]) - [MC712])) [MC717a + MC717b]) - [MC712]))
( ( [MC736] + [MC621] + ( [MC14C] + ( ( [MC736] + [MC621] + ( [MC14C] +
[MC739]) + [MC921c]) / ( ( [MC718] + [MC739]) + [MC921c]) / ( ( [MC718] +
% RTCH drop RTCH_Drop_Rate QSTCCDR [MC717a + MC717b]) - [MC662])) [MC717a + MC717b]) - [MC662]))
Intra BSC incoming handovers
Request HO_Inc_BSC_Request HOIBRQN MC830 MC830
Success HO_Inc_BSC_Success HOIBSUN MC652 MC652
fail BSS HO_Inc_BSC_fail_BSS HOIBFLBN
fail radio HO_Inc_BSC_fail_radio HOIBFLRN
Prep fail HO_Inc_BSC_prep_fail HOIBPFN
Cong HO_Inc_BSC_cong HOIBCGN
% Cong HO_Inc_BSC_Cong_Rate HOIBCGR ( [MC91 +MC551] / [MC830]) ( [MC91 +MC551] / [MC830])
( ( [MC653] + ( [MC831] - [MC652] - ( ( [MC653] + ( [MC831] - [MC652] -
% Fail HO_Inc_BSC_Fail_Rate HOIBFLR [MC653])) / [MC830]) [MC653])) / [MC830])
% Success HO_Inc_BSC_Success_Rate HOIBSUR ( [MC652] / [MC830]) ( [MC652] / [MC830])
Intra BSC outgoing handovers
Request HO_Out_BSC_Request HOOBRQN [MC660] [MC660]
Success HO_Out_BSC_success HOOBSUN [MC656] [MC656]
Drop BSS HO_Out_BSC_drop_BSS HOOBCDBN
Drop Radio HO_Out_BSC_drop_radio HOOBCDRN
ROC HO_Out_BSC_ROC HOOBOCN
Prep fail HO_Out_BSC_prep_fail HOOBFLPN
% Efficiency HO_Out_BSC_efficiency_rate HOOBEFR
% Success HO_Out_BSC_Success_Rate HOOBSUR
% ROC (return to old channel) HO_Out_BSC_ROC_Rate HOOBOCR ( [MC657] / [MC660]) ( [MC657] / [MC660])
( ( [MC658] + [MC660-MC656-MC657- ( ( [MC658] + [MC660-MC656-MC657-
% Drop HO_Out_BSC_Drop_Rate HOOBCDR MC658]) / [MC660]) MC658]) / [MC660])
Inter BSC incoming handovers
Request HO_Inc_MSC_Request HOIMRQN MC820 MC820
Success HO_Inc_MSC_Success HOIMSUN MC642 MC642
fail BSS HO_Inc_MSC_fail_BSS HOIMFLBN
fail radio HO_Inc_MSC_fail_radio HOIMFLRN
No CIC alloc HO_Inc_MSC_no_cic_alloc HOIMAMN
Prep fail HO_Inc_MSC_prep_fail HOIMPFN
Cong HO_Inc_MSC_cong HOIMCGN
% Cong HO_Inc_MSC_Cong_Rate HOIMCGR ((MC541a+MC81)/(MC820)) ((MC541a+MC81)/(MC820))
( (MC643) + ( (MC821) - (MC642) - (MC643) ( (MC643) + ( (MC821) - (MC642) - (MC643)
% Fail HO_Inc_MSC_Fail_Rate HOIMFLR ) ) / (MC820) ) ) / (MC820)
% Success HO_Inc_MSC_Success_Rate HOIMSUR ( [MC642] / [MC820]) ( [MC642] / [MC820])
Inter BSC outgoing handovers
Request HO_Out_MSC_Request HOOMRQN MC650 MC650
Success HO_Out_MSC_Success HOOMSUN MC646 MC646
HOOMCDB
Drop BSS HO_Out_MSC_drop_BSS N

472965020.xls - B8_B9_GSM_Indicators 134 / 535 04/28/2020

 GSM KPI's name RNO QOS indicator Ref Name B8 formula B9 Formula
HOOMCDR
Drop Radio HO_Out_MSC_drop_radio N
ROC HO_Out_MSC_ROC HOOMOCN
Prep fail HO_Out_MSC_prep_fail HOOMFLPN
% Efficiency HO_Out_MSC_efficiency_rate HOOMEFR
% Success HO_Out_MSC_Success_Rate HOOMSUR
% ROC (return to old channel) HO_Out_MSC_ROC_Rate HOOMOCR ( [MC647] / [MC650]) ( [MC647] / [MC650])
( ( [MC648] + [MC650-MC646-MC647- ( ( [MC648] + [MC650-MC646-MC647-
% Drop HO_Out_MSC_Drop_Rate HOOMCDR MC648]) / [MC650]) MC648]) / [MC650])
Intracell handovers
Request HO_Cell_request HOCLRQN
Drop radio HO_Cell_drop_radio HOCLCDRN
Drop BSS HO_Cell_drop_BSS HOCLCDBN
ROC HO_Cell_ROC HOCLOCN
Success HO_Cell_success HOCLSUN
Prep fail HO_Cell_prep_fail HOCLPFN
Cong HO_Cell_cong HOCLCGN
% Drop HO_Cell_drop_rate HOCLCDR
% ROC (return to old channel) HO_Cell_ROC_rate HOCLOCR
Handover
Handover success rate

( [MC673] /
[MC670+MC671+MC672+MC673+MC674+ ( [MC673] /
MC675+MC676+MC677+MC678+MC679+ [MC670+MC671+MC672+MC673+MC674+MC67
MC785A+MC785D+MC785E+MC785F+MC 5+MC676+MC677+MC678+MC679+MC785A+M
586A+MC586B+MC586C+MC1040+MC104 C785D+MC785E+MC785F+MC586A+MC586B+
HCSTELVD 4+MC1050+MC461+MC448a MC586C+MC1040+MC1044+MC1050+MC461+
% CHO_DL_Level CHO_DL_level_rate R +MC448b+MC449]) MC448a +MC448b+MC449+MC481])
HCSTELVD
CHO_DL_Level CHO_DL_level N MC673 MC673

( [MC671] /
[MC670+MC671+MC672+MC673+MC674+ ( [MC671] /
MC675+MC676+MC677+MC678+MC679+ [MC670+MC671+MC672+MC673+MC674+MC67
MC785A+MC785D+MC785E+MC785F+MC 5+MC676+MC677+MC678+MC679+MC785A+M
586A+MC586B+MC586C+MC1040+MC104 C785D+MC785E+MC785F+MC586A+MC586B+
4+MC1050+MC461+MC448a MC586C+MC1040+MC1044+MC1050+MC461+
% CHO_UL_Level CHO_UL_level_rate HCSTELVUR +MC448b+MC449]) MC448a +MC448b+MC449+MC481])
HCSTELVU
CHO_UL_Level CHO_UL_level N MC671 MC671

( [MC672] /
[MC670+MC671+MC672+MC673+MC674+ ( [MC672] /
MC675+MC676+MC677+MC678+MC679+ [MC670+MC671+MC672+MC673+MC674+MC67
MC785A+MC785D+MC785E+MC785F+MC 5+MC676+MC677+MC678+MC679+MC785A+M
586A+MC586B+MC586C+MC1040+MC104 C785D+MC785E+MC785F+MC586A+MC586B+
HCSTEQLD 4+MC1050+MC461+MC448a MC586C+MC1040+MC1044+MC1050+MC461+
% CHO_DL_Quality CHO_DL_quality_rate R +MC448b+MC449]) MC448a +MC448b+MC449+MC481])
HCSTEQLD
CHO_DL_Quality CHO_DL_quality N MC672 MC672

( [MC670] /
[MC670+MC671+MC672+MC673+MC674+ ( [MC670] /
MC675+MC676+MC677+MC678+MC679+ [MC670+MC671+MC672+MC673+MC674+MC67
MC785A+MC785D+MC785E+MC785F+MC 5+MC676+MC677+MC678+MC679+MC785A+M
586A+MC586B+MC586C+MC1040+MC104 C785D+MC785E+MC785F+MC586A+MC586B+
HCSTEQLU 4+MC1050+MC461+MC448a MC586C+MC1040+MC1044+MC1050+MC461+
% CHO_UL_ Quality CHO_UL_quality_rate R +MC448b+MC449]) MC448a +MC448b+MC449+MC481])
HCSTEQLU
CHO_UL_ Quality CHO_UL_quality N MC670 MC670

( [MC678] /
[MC670+MC671+MC672+MC673+MC674+ ( [MC678] /
MC675+MC676+MC677+MC678+MC679+ [MC670+MC671+MC672+MC673+MC674+MC67
MC785A+MC785D+MC785E+MC785F+MC 5+MC676+MC677+MC678+MC679+MC785A+M
586A+MC586B+MC586C+MC1040+MC104 C785D+MC785E+MC785F+MC586A+MC586B+
4+MC1050+MC461+MC448a MC586C+MC1040+MC1044+MC1050+MC461+
% CHO_Better_Cell CHO_Better_Cell_rate HCSTBPBR +MC448b+MC449]) MC448a +MC448b+MC449+MC481])
CHO_better_cell CHO_better_cell HCSTBPBN
% CHO Interference CHO_interference_rate HCSTEIFR
CHO_interference CHO_interference HCSTEIFN
Traffic
SDCCH traffic in Erlang SDCCH_Erlang_total SDTRE ((MC400)/(3600)) ((MC400)/(3600))
RTCH traffic in Erlang RTCH_Erlang_Total TCTRE ((MC380a+MC380b)/(3600)) ((MC380a+MC380b)/(3600))
RTCH mean holding time RTCH_duration_avg TCTRMHT ((MC380a+MC380b)/(MC370a+MC370b)) ((MC380a+MC380b)/(MC370a+MC370b))
SDCCH mean holding time SDCCH_duration_avg SDTRMHT ((MC400)/(MC390)) ((MC400)/(MC390))

472965020.xls - B8_B9_GSM_Indicators 135 / 535 04/28/2020

 Indicator name Reference name Unit

RTCH drop rate QSTCCDR %

call drop QSCDN nb

call drop BSS int failure rate QSCDBIR %

call drop BSS remote TC rate QSCDBTR %

call drop HO rate QSCDHR %
call drop radio rate QSCDRR %

call drop rate QSCDR %

call setup success rate QSCSSR %

SDCCH drop SDCDN nb

SDCCH drop BSS rate SDCDBR %
SDCCH drop radio rate SDCDRR %

SDCCH drop rate SDCDR %

CHO CC Out zone lev rate HCCCBCPR %

CHO CC inn zone lev rate HCCCELVR %

CHO DL interference rate HCSTEIFDR %

CHO DL level rate HCSTELVDR %

CHO DL quality rate HCSTEQLDR %

CHO UL interference rate HCSTEIFUR %

CHO UL level rate HCSTELVUR %

CHO UL quality rate HCSTEQLUR %

CHO all HCN nb

CHO MB preferred band rate HCMBBCPR %

CHO DR forced rate HCSTBDRR %

CHO better cell rate HCSTBPBR %

CHO general capture rate HCBCPR %

CHO traffic rate HCSTBTRR %

HO Inc MSC success HOIMSUN nb

HO Inc MSC allocated HOIMCAN nb

HO Inc MSC request HOIMRQN nb

HO Inc BSC success HOIBSUN nb

HO Inc BSC allocated HOIBCAN nb

HO Inc BSC request HOIBRQN nb

HO Inc request HOIRRQN nb

HO Inc efficiency rate HOIREFR %

HO Inc allocated rate HOIRCAR %

HO Out MSC success HOOMSUN nb

HO Out MSC request HOOMRQN nb

HO Out MSC required HOOMRDN nb

HO Out BSC success HOOBSUN nb

HO Out BSC request HOOBRQN nb

HO Out BSC required HOOBRDN nb

HO Out request HOORRQN nb

HO Out efficiency rate HOOREFR %

HO Out prep success rate HOORRQR %

RTCH assign fail BSS rate TCNAFLBR %

RTCH assign fail radio rate TCNAFLRR %

RTCH assign fail rate TCNAFLR %

RTCH assign cong max rate TCNACGR_MA %

RTCH assign cong rate TCNACGR %

RTCH assign request TCNARQN nb

RTCH HO cong rate TCHOCGR %

RTCH Erlang BH TCTRE_BH Er

RTCH Erlang total TCTRE Er

RTCH duration avg TCTRMHT s

RTCH Erlang capacity TCTROFE Er

SDCCH assign cong rate SDNACGR %

SDCCH assign fail BSS rate SDNAFLBR %

SDCCH assign fail radio rate SDNAFLRR %

SDCCH assign fail rate SDNAFLR %

SDCCH assign request SDNARQN nb

SDCCH Erlang capacity SDTROFE Er

SDCCH Erlang total SDTRE Er

SDCCH duration avg SDTRMHT s

RTCH HO per call TMHOCO nb

RMS PathBalance avg RMPBAN dB

RMS DL RxLevel avg RMQLDLVAN dBm
RMS DL RxQuality avg RMQLDQUAN nb
RMS UL RxLevel avg RMQLULVAN dBm
RMS UL RxQuality avg RMQLUQUAN nb
RMS TimingAdvance avg RMQLUTAAN nb
 Cell Threshold
Limited
Definition Comments Coverage Open Coverage
Equivalent to the call drop rate, but to be used at
the cell level 1.2% 3.0%
Number of call drops for BSS int + TC + HO + Radio
causes
Rate of call drops due to "miscellaneous" causes, usually
due to cell restart or other O&M activities.
Rate of call drop due to Abis links, BSC boards or
Transcoder boards 1.0% 1.0%
Rate of call drop happening during a handover
Rate of call drop due to degraded radio link
Cumulated rate of call drops due to BSS int, TC, Ho and
radio, to be used at the BSC level (or above)

(1- SDCCH drop rate) * (1- TCH assignment failure rate) 99.0% 96.0%
Number of drops occuring during the SDCCH phase (call
setup)
Rate of SDCCH drops due to miscellaneous causes
Rate of SDCCH drops due to degraded radio link

Cumulated rate of SDCCH drops due to BSS & Radio 0.5% 2.0%
Rate of outer --> inner handovers in a multiband cells
(out of total outgoing HO) Better cell HO
approx. CHO CC approx. CHO CC
Rate of inner --> outer handovers in a multiband cells Out zone lev Out zone lev
(out of total outgoing HO) Emergency HO rate / 2 rate / 2
Rate of handovers due to interference on the downlink
signal (out of total outgoing HO) Emergency HO 10.0% 10.0%
Rate of handovers due to low level on the downlink signal
(out of total outgoing HO) Emergency HO 30.0% n/a
Rate of handovers due to poor quality on the downlink
signal (out of total outgoing HO) Emergency HO 20.0% 40.0%
Rate of handovers due to interference on the uplink signal
(out of total outgoing HO) Emergency HO 10.0% 10.0%
Rate of handovers due to low level on the uplink signal
(out of total outgoing HO) Emergency HO 30.0% n/a
Rate of handovers due to poor quality on the uplink signal
(out of total outgoing HO) Emergency HO 20.0% 40.0%
Total number of outgoing HO

Rate of "preferred band" handover from serving (900) cell

to neighbor (1800) cell (out of total outgoing HO) Better cell HO

Rate of "forced directed retry" handover from serving cell

to neighbor cell (out of total outgoing HO) Better cell HO

Rate of "power budget" handover = when neighbor with

better signal than serving (out of total outgoing HO) Better cell HO
Rate of "general capture" handover (not used in Celcom !)
(out of total outgoing HO) Better cell HO
Rate of "Traffic HO" from high traffic load serving to low
traffic load neighbor (out of total outgoing HO) Better cell HO
Number of succesfully performed incoming HO from
neighbor cells from different BSC External HO
Number of succesfully allocated incoming HO from
neighbor cells from different BSC External HO
Number of requested incoming HO from neighbor cells
from different BSC External HO
Number of succesfully performed incoming HO from
neighbor cells in the same BSC Internal HO >0
Number of succesfully allocated incoming HO from
neighbor cells in the same BSC Internal HO >0
Number of requested incoming HO from neighbor cells in
the same BSC Internal HO >0
Total amount of incoming handovers requests Int + Ext HO
Rate of success incoming HO / allocated incoming HO
(usual failure : radio or configuration) Int + Ext HO 75.0% 70.0%
Rate of allocated incoming HO / requested incoming HO
(usual failure : congestion) Int + Ext HO
Number of succesfully performed outgoing HO from
neighbor cells from different BSC External HO
Number of succesfully allocated outgoing HO from
neighbor cells from different BSC External HO
Number of requested outgoing HO from neighbor cells
from different BSC External HO
Number of succesfully performed outgoing HO from
neighbor cells in the same BSC Internal HO >0
Number of succesfully allocated outgoing HO from
neighbor cells in the same BSC Internal HO >0
Number of requested outgoing HO from neighbor cells in
the same BSC Internal HO >0
Total amount of outgoing handovers requests Int + Ext HO
Rate of success outgoing HO / allocated outgoing HO
(usual failure : radio or configuration) Int + Ext HO 80.0% 75.0%
Rate of allocated outgoing HO / requested outgoing HO
(usual failure : congestion) Int + Ext HO
Rate of TCH not assigned due to a BSS faillure (O&M
operation, Abis faulty,…) (out of TCH NA requests) Call setup only 0.5% 0.5%
Rate of TCH not assigned due to a degraded radio link
(TRX faulty, path balance, interference, ...) (out of TCH
NA requests) Call setup only
Cumulated rate of TCH not assigned due to BSS +
Radio Call setup only 1.0% 2.5%
Rate of TCH not assigned due to congestion in the
cell, measured at the busy hour only ! Call setup only 2.0% 2.0%
Rate of TCH not assigned due to congestion in the cell,
average value on 24h Call setup only
Number of TCH Normal Assignment requests (NA = call
setup only, not incoming handover) Call setup only >0 >0
Rate of TCH "for inc. HO" not assigned due to congestion
in the cell, average value on 24h Incoming HO only
Traffic on the TCH channels at the busy hour in the cell, in
Erlang >0 >0
Cumulated traffic on the TCH channels during the day, in
Erlang
Average duration of a TCH seizure (allocations by call
setup or incoming HO) > 20s > 20s

Theoretical capacity of the cell in Erlang, during one hour.

Rate of SDCCH not assigned due to congestion in
the cell, average value on 24h Call setup only 0.5% 1.0%

Rate of SDCCH not assigned due to a BSS faillure (O&M

operation, Abis faulty,…) (out of TCH NA requests) Call setup only 0.2% 0.2%
Rate of SDCCH not assigned due to a degraded radio link
(TRX faulty, path balance, interference, ...) (out of TCH
NA requests) Call setup only
Cumulated rate of SDCCH not assigned due to BSS
+ Radio Call setup only 4.0% 10.0%
Number of SDCCH Normal Assignment requests (NA = call
setup only, not incoming handover) Call setup only >0 >0
Traffic on the SDCCH channels at the busy hour in the
cell, in Erlang
Cumulated traffic on the SDCCH channels during the day,
in Erlang >0 >0
Average duration of a SDCCH seizure < 5s < 5s
Ratio of TCH assigned for incoming HO / TCH assigned for
call setup

Path balance (not valid if the RTCH_Erlang_BH < >9 >9

0.2 Erl) RMS < -7 < -7
Average downlink RxLev measured by the mobiles RMS > - 85dBm < -90dBm
Average downlink RxQual measured by the mobiles RMS < 2.5 < 2.5
Average uplink RxLev measured by the BTS RMS
Average uplink RxQual measured by the BTS RMS < 2.5 < 2.5
Average time advance of the mobiles in the cell RMS >4 > 10
 GLOBAL PRE-REQUISITES

TESTS CONDITIONS

KPI Computation

KPI

Call Drop

% Call Drop

Call Establishment

% Call Setup Success Rate

Intra+Inter BSC outgoing handovers

% Success

RXQual

DL RxQual

RxLev

DL RxLev

Voice Quality (Optional)

MOS or PACE

Call Set-up Time (Optional)

CST
2 types of measurements :

Periodic calls
Continuous calls

Any measurement for which the failures will not be due to Alcatel system will be excluded from the KPI computa
For example :
- Failures due to the Core Network problems
- Transmission problems
- Electric alimentation problems
- Congestion (Radio, Ater or on other interfaces) ; radio congestion can be verified on RNO/NPA.
The removal of those failures will be jointly decided by the customer and Alcatel following analysis.

DESCRIPTION

Rate of call drop : % of dropped calls after successful assignment.

Percentage of succesfull mobile originating call attempts

Percentage of succesfull handover

Percentage of collected samples presenting a RxQual value (typical >5)

above a certain thresold

Distribution of RxLev samples

Indicator that measures the voice quality as perceived by end users

Measures the duration of call set-up. from call initiation (dialing) at
originiating part until alerting (ringing) at terminating part
Alcatel system will be excluded from the KPI computations.

ngestion can be verified on RNO/NPA.

customer and Alcatel following analysis.

FORMULA SPECIFIC PRE-REQUISITES

(drop call events/ Alerting)*100%. Periodic Call

(Alerting / (channel requests - location update

Periodic Call
requests))*100%.

(1- Handover Failure Rate/HO Command)*100%. Continuous call

N/A Continuous call

N/A Continuous call

N/A Periodic Call

sum(time duration of each call) / number of samples Periodic Call
 STANDARD KPIs VALUES

Common Dense
Urban Sub urban Rural
NETWORK OPTIM
Threshold urban DESIGN SERVICE

1.3% - 1.5 1.5% - 2.0 1.5% - 2.0

1.50% >2.0% LOW LOW
% % %

97% 97% 96.5% 96.5% 96.5% LOW LOW

95% 95% 94% 93% 90% LOW LOW

95% 95% 92% 90% 90% LOW LOW

LOW LOW

LOW LOW
3 seconds 3s 3.5 s 4s >4s LOW LOW
D KPIs VALUES OVER-COMMITTED KPIs VALUES

PROJECT NETWORK OPTIM PROJECT

PLANNING DESIGN SERVICE PLANNING

MEDIUM MEDIUM HIGH HIGH

MEDIUM MEDIUM HIGH HIGH

LOW MEDIUM HIGH MEDIUM

MEDIUM HIGH HIGH HIGH

MEDIUM HIGH MEDIUM HIGH

MEDIUM HIGH HIGH HIGH

MEDIUM LOW MEDIUM LOW
Remarks
End-To-End Performances

TESTS CONDITIONS

Upper Layers and Aplication

MOBILE

PC

KPI Computation
 FTP SERVICE

SPECIFIC PRE-REQUISITES for FTP Service:

- The threshols presented in the table below could be obtained :
=> in downlink path if a reference file of 3 MB is used.
=> in uplink path if a reference file of 1 MB is used.
- The Reference File will be downloaded from a local server, i.e not a commercial server.
- This local server should be placed just behind the GGSN on Gi interface.
- The TCP packet cannot be fragmented in routers between client and server.
- The application used for FTP service need to be validated by Alcatel in case of not using DEUT

NB:
- B8 values presented in the table below are based on experience a on EDGE Golden Clusten pr
A deeper analysis is necessary to see if it is possible to optimise those values according to last
- B9 values presented in the table below are the same as B8 ones except for the UL throughput
According to first B9 field results, those values should be re-analysed and maybe optimised.

KPI

FTP Failure Rate

FTP Drop Rate

Average DL FTP Throughput (in kbits/s)
in good radio conditions

Average DL FTP Throughput (in kbits/s)

in medium radio conditions

Distribution DL FTP Throughput (in kbits/s)

on a CLUSTER

Average DL FTP Throughput (in kbits/s)

on a CLUSTER

Average UL FTP Throughput (in kbits/s)

in good radio conditions

Average UL FTP Throughput (in kbits/s)

in medium radio conditions

Distribution of UL FTP Throughput (in kbits/s)

on a CLUSTER
Average UL FTP Throughput (in kbits/s)
on a CLUSTER

acessibility test

SPECIFIC PRE-REQUISITES for PING Service:

- For this measurement, the service has to be established, i.e PDP context activated.
- As to avoid the time needed to reserve radio packet resources during the first request, the sta
- The IP datagrams cannot be fragmented in diferent routers between Client and Server.
- The server must be located in Gi interface
- To make in Good radio Conditions

NB:
- B8 values presented in the table below are representative of values obtained on field in B8 rele
A deeper analysis is necessary to see if it is possible to optimise those values according to last
- B9 values presented in the table below are based on commitments taken with Orange France.

KPI

Server Accessibility Success Rate

Round Trip Time (in ms)

Round Trip Time (in ms)

HTTP SERVICE

SPECIFIC PRE-REQUISITES for HTTP Service :

'- A Reference Page with the following characteristics should be used:
* Total Page Size : around 260 kB
* Total Picture Size : around 190 kB (20 kB of GIF pictures & 3 JPG pictures)
* Total HTML Page Size : around 70 kB
- The Reference Page will be downloaded from a local server, i.e not a commercial server.
- The client PC should enable multiples Downloads at same time (PC parameter)
- This local server should be placed just behind the GGSN on Gi interface.
- The TCP packets cannot be fragmented in diferent routers between Client and Server.
- Test made in good radio conditions.

NB:
- B8 values presented in the table below are based on experience and commitments taken on E
A deeper analysis is necessary to see if it is possible to optimise those values according to last
- B9 values presented in the table below are the same as B8 ones except for the UL throughput
According to first B9 field results, those values should be re-analysed and maybe optimised.

KPI

HTTP Failure Rate

HTTP Drop Rate

Average DL Throughput (in kbits/s)

WAP SERVICE
SPECIFIC PRE-REQUISITES for WAP Service :
- The Reference Page should be the page from the customer WAP portal.
- This Reference Page should not exceed 15 kB (XHML Page + pictures)
- Test made in Good Radio condition.

NB:
- B8 values presented in the table below are based on experience and commitments taken on E
A deeper analysis is necessary to see if it is possible to optimise those values according to last
- B9 values presented in the table below are the same as B8 ones except for the UL throughput
According to first B9 field results, those values should be re-analysed and maybe optimised.

KPI

WAP Failure Rate

Access Time to the WAP Home Page (in s)

MMS SERVICE
SPECIFIC PRE-REQUISITES :
- A Reference Video of 100 ko will be used.
- The tests can be done from the commercial server
- Test made in good radio condition.

NB:
- B8 values presented in the table below are based on experience and commitments taken on E
A deeper analysis is necessary to see if it is possible to optimise those values according to last
- B9 values presented in the table below are the same as B8 ones except for the UL throughput
According to first B9 field results, those values should be re-analysed and maybe optimised.

KPI

MMS Sending Failure Rate

MMS Received Failure Rate (End to End)

MMS Receiving Time ( in s) (End to End)

STREAMING SERVICE
SPECIFIC PRE-REQUISITES :
- A Reference Video of 3 minutes maximum encoded in 56 kbps will be used.
- The tests can be done from the commercial server
- Test made in Good radio condition.

NB:
- B8 values presented in the table below are based on experience and commitments taken on E
A deeper analysis is necessary to see if it is possible to optimise those values according to last
- B9 values presented in the table below are the same as B8 ones except for the UL throughput
According to first B9 field results, those values should be re-analysed and maybe optimised.

KPI

Non-Quality Streaming Rate

2G/3G INTEROPERABIL

SPECIFIC PRE-REQUISITES :
The choice of the 2G / 3G mobile should be validated by the supplier, admitting that the mobile
Alcatel 3G and 2G network.
The 3G Network must be in higher version than R4 and have the RNC evolution
For this tests will be necessary to use radio trace tool (Like Agilent Nitro, TEMS, etc..)
NB:
- B8 values presented in the table below are based on experience and commitments taken on E
tests.
- The RAB used in 3G are: Background, Maximum bit rate Uplink = 64kbps; Maximum bit rate Do
- The filesizes used are 1Mo in Uplink and 5Mo in downlink in ISHO tests, and 1Mo in reselection

KPI

Failure Rate of PDP context non interruption

Success Rate of 3G to 2G ISHO during UL PS transfer

Mean interruption Time during 3G to 2G ISHO during UL

PS transfer

Success Rate of 3G to 2G ISHO during DL PS transfer

Mean interruption Time during 3G to 2G ISHO during DL

PS transfer

Mean interruption Time during 2G to 3G Reselection

during PS transfer.

GPRS / EDGE INTEROPERA

NB:
- B8 values presented in the table below are based on experience and commitments taken on E
A deeper analysis is necessary to see if it is possible to optimise those values according to last
- B9 values presented in the table below are the same as B8 ones except for the UL throughput
According to first B9 field results, those values should be re-analysed and maybe optimised.
- NC0 is considered

KPI

Reselection Failure Rate

Average Transfer Time of interruption

GPRS / GPRS and EDGE/EDGE INTE

NB:
- B9 values presented in the table below are the same as B8 ones except for the UL throughput
According to first B9 field results, those values should be re-analysed and maybe optimised.
- NC0 is considered

KPI

Average Transfer Time of interruption

- All the KPIs will be measured in STATIC POINTS, except for KPI "Average DL/UL FTP throughput on a CLUSTER" : this
- The choosen cells be Single type and need to have at least 2TRX.
- The measurements will be performed INCAR without external antenna.
- All the KPIs will be measured in GOOD RADIO CONDITIONS, i.e :
* no cell reselections during the transfer
* Rxlev > -70 dBm , Rxqual < 2 for GPRS measurements
* Rxlev > -70 dBm, 25 < MeanBEP < 31 for EDGE measurements
* Best server > Best neighbour + 10 dB
except for KPI "Average DL/UL FTP throughput in medium radio condition".

- The MEDIUM RADIO CONDITIONS is defined as:

* no cell reselections during the transfer
* Rxlev [-85dBm; -75dBm] , Rxqual < 3 for GPRS measurements
* Rxlev [-85dBm; -75dBm] , MeanBEP > 15 for EDGE measurements

- All the B8 GPRS & EDGE thresholds presented could be obtained with CLASS 5 TRXs.
- No congestion (in all interfaces) and low traffic should be observed in the cells chosen for the tests, and especially :
Four timeslots free for downlink tests and Two timeslots free for uplink tests.
- The B8/B9 GPRS thresholds presented in the table below are obtained with CS3/CS4 feature activated
=> MAX CS = CS4 and INIT CS = CS2.
- The B8 EDGE thresholds presented in the table below are obtained with :
=> MAX MCS = MCS9 in Downlink path and MAX MCS = MCS4 in Uplink path
=> INIT MCS = MCS3 in Downlink path & Uplink path.
- The B9 EDGE thresholds presented in this table below are obtained with :
=> MAX MCS = MCS9 in Downlink path & Uplink path
=> INIT MCS = MCS3 in Downlink path & Uplink path.

- For throughput measurements it will be used FTP application

- The routers and the server existing must have a MTU size of 1500 bytes
- The mobile should be a EDGE / UMTS mobile class 10 (DL : 4+1 ; UL : 3+2).
- The mobile must be a trace mobile in order to be compatible with the trace tool chain used by Alcatel measurement team
- The mobile must be agreed between Alcatel and the CUSTOMER.
- Alcatel recommendation : the NOKIA 6630 mobile.

'- The PC environment will be : MS WINDOWS, MS Internet Explorer, appropriate drivers.

- A suitable TCP parameters setting should be used:
o TcpWindowSize= “FF00” (65280 bytes in decimal)
o Tcp1323Opts="1"
o DefaultTTL="80" (128 in decimal)
o EnablePMTUDiscovery="1"
o EnablePMTUBHDetect="0"
o SackOpts="1"
MTU size of 1500bytes
During KPI computation, the failures out of Alcatel Scope will be elegible for exclusion from the computation.

For example :
- Failures due to the Core Network problems
- Transmission problems
- Electric alimentation problems
- Congestion (Radio, Ater or on other interfaces) ; radio congestion can be verified on traces by the non availability of the 4

The removal of those failures will be jointly decided by the customer and Alcatel following analysis.
 FTP SERVICE

P Service:
ble below could be obtained :
e file of 3 MB is used.
e of 1 MB is used.
oaded from a local server, i.e not a commercial server.
d just behind the GGSN on Gi interface.
ented in routers between client and server.
vice need to be validated by Alcatel in case of not using DEUTRIP tool.

below are based on experience a on EDGE Golden Clusten project (SFR), Vimpelcom Edge Optimisation p
see if it is possible to optimise those values according to last results obtained on B8 release.
below are the same as B8 ones except for the UL throughput with EDGE, as 8PSK modulation is introduce
those values should be re-analysed and maybe optimised.

DESCRIPTION

Rate of failure to access to the FTP service.

A connection to the FTP server is considered as failed if it is established in more than 1
minute.

Rate of FTP drop during the download of the files.

The file is considered as received when the file is completely received without drop
during the connection, within a period of 6 minutes after the connection to the GPRS
network and if the content is correct. The test is made in good radio conditions.
Average DL FTP Throughput (in kbits/s) in good radio conditions, measured in
Application Layer.

Average DL FTP Throughput (in kbits/s) in medium radio conditions. Measured in

application Layer.

Percentile at X% of the file download throughputs in the radio conditions of the

CLUSTER.

Average of the file download throughputs in the radio conditions of the CLUSTER.

Average UL FTP Throughput (in kbits/s) in good radio conditions. Measured in

application Layer.

Average UL FTP Throughput (in kbits/s) in Medium radio conditions. Measured

in Application Layer.

Percentile at X% of the file upload throughputs in the radio conditions of the CLUSTER.
 average of the file upload throughputs in the radio conditions of the CLUSTER.

acessibility test

NG Service:
e has to be established, i.e PDP context activated.
serve radio packet resources during the first request, the statistics don't integrate the first iteration of the
mented in diferent routers between Client and Server.
interface
s

below are representative of values obtained on field in B8 release.

see if it is possible to optimise those values according to last results obtained on B8 release.
below are based on commitments taken with Orange France.

DESCRIPTION

Probability that the application server is reachable.

This state is measured at TCP/IP layers thanks to the ICMP packet.

Time between a Ping Request to a server and its associated Ping Response.
 Ping transfer with 32 bytes payload and an interval between 2 pings of 0 s ; timeout=3seconds

Ping transfer with 32 bytes payload and an interval between 2 pings of 15 s ; timeout=3seconds

Ping transfer with 1460 bytes payload and an interval between 2 pings of 0 s ; timeout=5seconds

Ping transfer with 1460 bytes payload and an interval between 2 pings of 15 s ; timeout=5seconds

HTTP SERVICE

TTP Service :
wing characteristics should be used:
B
kB (20 kB of GIF pictures & 3 JPG pictures)
70 kB
loaded from a local server, i.e not a commercial server.
iples Downloads at same time (PC parameter)
d just behind the GGSN on Gi interface.
mented in diferent routers between Client and Server.
ns.

below are based on experience and commitments taken on EDGE Golden Clusten project (SFR).
see if it is possible to optimise those values according to last results obtained on B8 release.
below are the same as B8 ones except for the UL throughput with EDGE, as 8PSK modulation is introduce
those values should be re-analysed and maybe optimised.

DESCRIPTION

Rate of non access to the WEB service with the following causes :
- PDP Context Activation Failure
- Service Access Failure
 Rate of WEB service drops during data transfer.

Average throughput of download as felt by the end user from the connexion to the WEB
service.

WAP SERVICE
AP Service :
e page from the customer WAP portal.
exceed 15 kB (XHML Page + pictures)
on.

below are based on experience and commitments taken on EDGE Golden Clusten project (SFR).
see if it is possible to optimise those values according to last results obtained on B8 release.
below are the same as B8 ones except for the UL throughput with EDGE, as 8PSK modulation is introduce
those values should be re-analysed and maybe optimised.

DESCRIPTION

Failure rate of the sessions accessing to the Home Page, start when PDP Context is not
established, cache memory empty.
One connexion is considered as failed if it is established in more than 1 minute (out of
time).

Time between the start of the connexion and the complete download (complete display)
of the Home Page

MMS SERVICE
be used.
ommercial server
n.

below are based on experience and commitments taken on EDGE Golden Clusten project (SFR).
see if it is possible to optimise those values according to last results obtained on B8 release.
below are the same as B8 ones except for the UL throughput with EDGE, as 8PSK modulation is introduce
those values should be re-analysed and maybe optimised.

DESCRIPTION

Failure Rate of MMS sent from a mobile A to a mobile B

Failure Rate of MMS received by a mobile B following a sending from a mobile

A.

Percentile of MMS receiving time from the MMS sending by a mobile A till the MMS
receiving by the mobile B.

STREAMING SERVICE
maximum encoded in 56 kbps will be used.
ommercial server
on.

below are based on experience and commitments taken on EDGE Golden Clusten project (SFR).
see if it is possible to optimise those values according to last results obtained on B8 release.
below are the same as B8 ones except for the UL throughput with EDGE, as 8PSK modulation is introduce
those values should be re-analysed and maybe optimised.

DESCRIPTION

Rate of non-quality during the sessions since the stream request from the portal WAP
until the end of the video (including the problems of the video quality).
3 possible causes:
· Failures = a failure message has appeared
· Drops = drops during the reading
· Problems of audio or video quality = "jerks" (number of times that audio and video
streams stop more than 3 seconds and start again)

2G/3G INTEROPERABILITY

hould be validated by the supplier, admitting that the mobile has a behaviour in 2G => 3G reselection align

version than R4 and have the RNC evolution

use radio trace tool (Like Agilent Nitro, TEMS, etc..)
below are based on experience and commitments taken on EDGE Golden Clusten project (SFR), and in Or

ound, Maximum bit rate Uplink = 64kbps; Maximum bit rate Downlink=384kbps
ink and 5Mo in downlink in ISHO tests, and 1Mo in reselection tests

DESCRIPTION

Percentage of PDP context interrupted or cut after the re-selection of a EDGE cell
towards a UMTS cell

Percentage of successfull ISHO (3G->2G) during FTP upload. The MS need to

be at least 30 seconds on 3G and finish the transfer in 2G.

interruption time in FTP upload during successfull ISHO (3G->2G). The MS

need to be at least 30 seconds on 3G and finish the transfer in 2G.

Percentage of successfull ISHO (3G->2G) during FTP download. The MS need

to be at least 30 seconds on 3G and finish the transfer in 2G.

interruption time in FTP download during successfull ISHO (3G->2G). The MS

need to be at least 30 seconds on 3G and finish the transfer in 2G.

interruption time in FTP download during successfull ISHO (3G->2G). The MS

need to be at least 30 seconds on 2G and finish the transfer in 3G. The target
area will be 3G only area.

GPRS / EDGE INTEROPERABILITY

below are based on experience and commitments taken on EDGE Golden Clusten project (SFR).
see if it is possible to optimise those values according to last results obtained on B8 release.
below are the same as B8 ones except for the UL throughput with EDGE, as 8PSK modulation is introduce
those values should be re-analysed and maybe optimised.

DESCRIPTION

Failure rate of re-selection from EDGE layer to GPRS layer. A re-selection is

considered as failed if it is established in more than 20 seconds.

Average time of the interruption of the FTP transfer during a re-selection of the
layer 2G EDGE towards the layer GPRS

GPRS / GPRS and EDGE/EDGE INTEROPERABILITY

below are the same as B8 ones except for the UL throughput with EDGE, as 8PSK modulation is introduce
those values should be re-analysed and maybe optimised.

DESCRIPTION

Average time of the interruption of the FTP transfer during a re-selection

 Validity Range for End user performance KP

"Average DL/UL FTP throughput on a CLUSTER" : this one will be measured in mobility in good and medium radio conditions(clusters o
.
enna.
:

ts

ndition".

nts

with CLASS 5 TRXs.

rved in the cells chosen for the tests, and especially :
nk tests.
ained with CS3/CS4 feature activated

d with :
Uplink path

ed with :

bytes
; UL : 3+2).
he trace tool chain used by Alcatel measurement team.
.

Explorer, appropriate drivers.

gible for exclusion from the computation.

can be verified on traces by the non availability of the 4 TS in DL and 2 TS in UL or on RNO/NPA.

r and Alcatel following analysis.

RIP tool.

ject (SFR), Vimpelcom Edge Optimisation project.

esults obtained on B8 release.
ith EDGE, as 8PSK modulation is introduced in UL path in B9 release.

NUMBER
FORMULA OF
TESTS

100 * [ Number of failures to access to the FTP service / Number of connexion

attempts]
500
- PDP context already established

100 * Number of file download drops / Number of attempts 500

AVERAGE [ Size of the file (in kbits) / Period of download (in s) ]

- START = Start of the download 500

- END = File correctly downloaded
- Only the succeed downloads are taken into account

AVERAGE [ Size of the file (in kbits) / Period of download (in s) ]

- START = Start of the download 200

- END = File correctly downloaded
- Only the succeed downloads are taken into account

Percentile at X% of the file download throughputs.

Throughput = File Size / Period of upload

200
- START = Start of the upload
- END = File correctly uploaded
- Only the succeed uploads are taken into account

average of the file download throughputs.

Throughput = File Size / Period of upload

200
- START = Start of the upload
- END = File correctly uploaded
- Only the succeed uploads are taken into account

AVERAGE [ Size of the file (in kbits) / Period of upload (in s) ]

- START = Start of the upload 500

- END = File correctly uploaded
- Only the succeed uploads are taken into account

AVERAGE [ Size of the file (in kbits) / Period of upload (in s) ]

- START = Start of the upload 200

- END = File correctly uploaded
- Only the succeed uploads are taken into account

Percentile at X% of the file download throughputs.

Throughput = File Size / Period of download

200
- START = Start of the download
- END = File correctly downloaded
- Only the succeed downloads are taken into account
 average of the file download throughputs.

Throughput = File Size / Period of download

200
- START = Start of the download
- END = File correctly downloaded
- Only the succeed downloads are taken into account

stics don't integrate the first iteration of the ping.

se.
esults obtained on B8 release.

NUMBER
FORMULA OF
ATTEMPTS

100 * [ Ping Response / Ping Request] 501

Round_Trip_Time = Time Packet_receive - Time Packet_send

With :
- Time Packet_Receive is the time when the sender receives the ICMP echo reply
- Time Packet_Send is the time when the ICMP echo request is sent.
s of 0 s ; timeout=3seconds 101

s of 15 s ; timeout=3seconds 101

ngs of 0 s ; timeout=5seconds 101

ngs of 15 s ; timeout=5seconds 101

GE Golden Clusten project (SFR).

esults obtained on B8 release.
ith EDGE, as 8PSK modulation is introduced in UL path in B9 release.

NUMBER
FORMULA OF
ATTEMPTS

100 * [ Number of access failures to WEB service / Number of attempts ]

500
 100 * [ Number of Web page not completely downloaded / Number of 500
attempts ]

AVERAGE [ Page Size (in kbit) / Duration of the download of the page (in s) ]

GE Golden Clusten project (SFR).

esults obtained on B8 release.
ith EDGE, as 8PSK modulation is introduced in UL path in B9 release.

NUMBER
FORMULA OF
ATTEMPTS

100 * Number of failures in downloading the Home Page / Number of Attempts

500

Only the successes are taken into account in the computation.

GE Golden Clusten project (SFR).
esults obtained on B8 release.
ith EDGE, as 8PSK modulation is introduced in UL path in B9 release.

NUMBER
FORMULA OF
ATTEMPTS

Number of MMS not sent by the mobile A or not acknowledged by the MMS
-Center / Number of sending attempts.
PDP context not established.

100 * (1 – Number of MMS received in less than 15 minutes by the mobile B /

Number of MMS sending attempts by the mobile A)

- START = MMS sent by the mobile A

100
- END = MMS received by the mobile B

Number of MMS received in less than XX seconds / Total number of MMS received.

- START = MMS sent by the mobile A

- END = MMS received by the mobile B
GE Golden Clusten project (SFR).
esults obtained on B8 release.
ith EDGE, as 8PSK modulation is introduced in UL path in B9 release.

NUMBER
FORMULA OF
ATTEMPTS

100 * Number of sessions with quality problems / Number of attempts

100
- START = STREAM request from the portal WAP
- END = End of the stream watching (end of the clip or stop of the user)

as a behaviour in 2G => 3G reselection aligned with 3GPP standards.

GE Golden Clusten project (SFR), and in Orange 2G/3G reselection

wnlink=384kbps
tests

NUMBER
FORMULA OF
ATTEMPTS

100 x Number of PDP context interrupted or cut after the re-selection of a

EDGE cell towards a UMTS cell divided by the number of re-selection EDGE / 200
UMTS

200

mean time between the last packet sent in 3G and first packet sent in 2G.
200
Measured in RLC layer.

200

mean time between the last packet received in 3G and first packet received in
200
2G. Measured in RLC layer.

mean time between the last packet received in 2G and first packet received in
200
3G. Measured in RLC layer.

ILITY
GE Golden Clusten project (SFR).
esults obtained on B8 release.
ith EDGE, as 8PSK modulation is introduced in UL path in B9 release.

NUMBER
FORMULA OF
ATTEMPTS

100 x (no of Data transfer request in EDGE - no of resume transfer in GPRS) /

100
no of Data transfer request in EDGE.

100 x Number of samples for which the transfer average time of interruption is
lower than XX / Number of Attempts
(the time could be measured between the "routing area update attempt"
100
message and "routing area update success"

Only successful re-selection are taken into account

OPERABILITY

ith EDGE, as 8PSK modulation is introduced in UL path in B9 release.

NUMBER
FORMULA OF
ATTEMPTS

100 x Number of samples for which the transfer average time of interruption is
lower than XX / Number of Attempts
100
Only successful re-selection are taken into account
nd user performance KPIs

medium radio conditions(clusters of Dense Urban, Urban and suburban), other samples will be removed from analysis.
 GPRS B8 GPRS B9

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

1.50% > 1% 1.50% > 1%

1% > 0,5% 1% > 0,5%

 70 kbps < 77 kbits 70 kbits < 77 kbits

65 kbits < 70 kbits 65 kbits < 70 kbits

90 % > 60
90 % > 60 kbits 80 % > 60
80 % > 60 kbits Without NC2 kbits
kbits

65 kbps < 70 kbps Without NC2 65 kbps < 70 kbps

20 kbits < 28 kbits 20 kbits < 34 kbits

18 kbits < 25 kbits 18 kbits < 27 kbits

80 % > 23 kbits 90 % > 23 kbits 90 % > 23 kbits

Without NC2 80 % > 23 kbits
 18 kbps < 25 kbps Without NC2 18 kbps < 25 kbps

GPRS B8 GPRS B9

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

98% <99% 98% <99%

 750 ms > 550 ms 750 ms > 550 ms

1000 ms > 750 ms 1000 ms > 750 ms

2400 ms > 2000 ms 2400 ms > 2000 ms

3100 ms > 2900 ms 3100 ms > 2900 ms

GPRS B8 GPRS B9

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

1.50% > 1% 1.50% > 1%

 1% > 0,5% 1% > 0,5%

35 kbits < 40 kbits 35 kbits < 40 kbits

GPRS B8 GPRS B9

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

2% > 1,5% 2% > 1,5%

95% < 12 s 95% < 10 s 95% < 12 s 95% < 10 s

 GPRS B8 GPRS B9

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

1% >1% 1% >1%

2% >1% 2% >1%

80% < 120 s 90% < 120 s 80% < 120 s 90% < 120 s
 GPRS B8 GPRS B9

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

10% >5% 10% >5%

 EDGE B8 EDGE B9

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

5% > 3% 5% > 3%

-- -- 95% < 99%

-- -- 35 sec > 31 sec

-- -- 95% < 99%

-- -- 30 sec > 27 sec

-- -- 30sec > 17 sec

 B8 GPRS / EDGE B9 GPRS / EDGE

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

3% >2% 3% >2%

95% < 6 s 95% < 5 s 95% < 6 s 95% < 5 s

B8 GPRS / EDGE B9 GPRS / EDGE

Common MAX Common MAX

Comments
Threshold Threshold Threshold Threshold

95% < 6 s 95% < 6 s

be removed from analysis.
GPRS B9 GPRS B10 EDGE B8

Proposed Common MAX

Comments Comments Comments
Threshold Threshold Threshold

> 1,5% > 1%

>1% > 0,5%

 165 kbits 190 kbits

130 kbits 140 kbits

90 % > 100 kbits

Without NC2 80 % > 100 kbits Without NC2

Without NC2 130 kbits 140 kbits Without NC2

20 kbits < 30 kbits

18 kbits < 27 kbits

Without NC2 80 % > 23 kbits 90 % > 23 kbits Without NC2

 Without NC2 18 kbps < 25 kbps Without NC2

GPRS B9 GPRS B10 EDGE B8

Common Common MAX

Comments Comments Comments
Threshold Threshold Threshold

98% <99%
 700 ms > 600 ms

1300 ms > 1000 ms

2000 ms > 1700 ms

2700 ms > 2500 ms

GPRS B9 GPRS B10 EDGE B8

Common Common MAX

Comments Comments Comments
Threshold Threshold Threshold

1.50% >1%
 1% > 0,5%

60 kbits < 80 kbits

GPRS B9 GPRS B10 EDGE B8

Common Common MAX

Comments Comments Comments
Threshold Threshold Threshold

2% > 1,5%

95% < 12 s 95% < 10 s

GPRS B9 EDGE B10 EDGE B8

Common Common MAX

Comments Comments Comments
Threshold Threshold Threshold

1% >1 %

2% >1%

80% < 120 s 90% < 120 s

GPRS B9 GPRS B10 EDGE B8

Common Common MAX

comments comments comments
Threshold Threshold Threshold

6% >4%
EDGE B9 IMPACTS / RISK ASSESSMENT
EDGE B10

Common NETWORK OPTIM PROJECT

Comments Comments
Threshold DESIGN SERVICE PLANNING

LOW HIGH HIGH

LOW HIGH HIGH

LOW HIGH HIGH

LOW MEDIUM HIGH

LOW MEDIUM HIGH

LOW MEDIUM HIGH

GPRS / EDGE B10 GPRS/EDGE IMPACTS / RISK ASSESSMENT

Common NETWORK OPTIM PROJECT

Comments Comments
Threshold DESIGN SERVICE PLANNING

HIGH HIGH HIGH

LOW HIGH HIGH

GPRS / EDGE B10 GPRS/EDGE IMPACTS / RISK ASSESSMENT

Common NETWORK OPTIM PROJECT

Comments Comments
Threshold DESIGN SERVICE PLANNING

LOW HIGH HIGH

 EDGE B9 EDGE B10

Common MAX Common

Comments Comments
Threshold Threshold Threshold

> 1,5% > 1%

>1% > 0,5%

 165 kbits < 190 kbits

130 kbits < 140 kbits

80 % > 100 kbits 90 % > 100 kbits

Without NC2

130 kbits < 140 kbits Without NC2

70 kbps < 75kbps

65 kbits < 70 kbits

80 % > 65 kbits 90 % > 65 kbits Without NC2

 65 kbps < 70 kbps Without NC2

EDGE B9 EDGE B10

Common MAX Common

Comments Comments
Threshold Threshold Threshold

98% <99%
 700 ms > 550 ms

1000 ms > 750 ms

2000ms > 1700 ms

2500 ms > 2000 ms

EDGE B9 EDGE B10

Common MAX Common

Comments Comments
Threshold Threshold Threshold

1.50% >1%
 1% > 0,5%

60 kbits < 80 kbits

EDGE B9 EDGE B10

Common MAX Common

Comments Comments
Threshold Threshold Threshold

2% > 1,5%

95% < 12 s 95% < 10 s

 EDGE B9 EDGE B10

Common MAX Common

Comments Comments
Threshold Threshold Threshold

1% >1%

2% >1%

80% < 120 s 90% < 120 s

 EDGE B9 EDGE B10

Common MAX Common

comments comments
Threshold Threshold Threshold

6% >4%
Remarks

-dependent on optimisation
service.
- highly dependent on 3G
and core network Vendor

-dependent on optimisation
service.
- highly dependent on 3G
and core network Vendor

-dependent on optimisation
service.
- highly dependent on 3G
and core network Vendor

-dependent on optimisation
service.
- highly dependent on 3G
and core network Vendor

-dependent on optimisation
service.
- highly dependent on 3G
and core network Vendor

-dependent on optimisation
service.
- highly dependent on 3G
and core network Vendor
Remarks

Remarks
 IMPACTS / RISK ASSESSMENT

NETWORK OPTIM PROJECT

DESIGN SERVICE PLANNING

LOW MEDIUM MEDIUM

LOW MEDIUM MEDIUM

LOW MEDIUM HIGH

LOW MEDIUM HIGH

HIGH HIGH HIGH

HIGH HIGH HIGH

LOW MEDIUM HIGH

LOW MEDIUM HIGH

HIGH HIGH HIGH

 HIGH HIGH HIGH

IMPACTS / RISK ASSESSMENT

NETWORK OPTIM PROJECT

DESIGN SERVICE PLANNING

LOW MEDIUM HIGH

 LOW MEDIUM HIGH

LOW MEDIUM HIGH

LOW MEDIUM HIGH

LOW MEDIUM HIGH

IMPACTS / RISK ASSESSMENT

NETWORK OPTIM PROJECT

DESIGN SERVICE PLANNING

LOW HIGH HIGH

 LOW HIGH HIGH

LOW HIGH HIGH

IMPACTS / RISK ASSESSMENT

NETWORK OPTIM PROJECT

DESIGN SERVICE PLANNING

LOW MEDIUM HIGH

LOW MEDIUM HIGH

 IMPACTS / RISK ASSESSMENT

NETWORK OPTIM PROJECT

DESIGN SERVICE PLANNING

LOW MEDIUM HIGH

LOW MEDIUM HIGH

LOW MEDIUM HIGH

 IMPACTS / RISK ASSESSMENT

NETWORK OPTIM PROJECT

DESIGN SERVICE PLANNING

LOW MEDIUM HIGH

Remarks

for optimization of this KPI it could be needed some Core network expert.
Normally is more linked with core network.

for optimization of this KPI it could be needed some Core network expert.
Normally is more linked with core network.
highly dependent on TRX class and Maximum coding scheme used

highly dependent on TRX class and Maximum coding scheme used

=>highly dependent on TRX class and Maximum coding scheme used.

=> optimization service also have a major role.
=> highly dependent on 2nd Global assumption: bandwitdh availability.

=>highly dependent on TRX class and Maximum coding scheme used.

=> optimization service also have a major role.
=> highly dependent on 2nd Global assumption: bandwitdh availability.

highly dependent on TRX class and Maximum coding scheme used

highly dependent on TRX class and Maximum coding scheme used

=>highly dependent on TRX class and Maximum coding scheme used.

=> optimization service also have a major role.
=> highly dependent on 2nd Global assumption: bandwitdh availability.
=>highly dependent on TRX class and Maximum coding scheme used.
=> optimization service also have a major role.
=> highly dependent on 2nd Global assumption: bandwitdh availability.

Remark

- impacted by core network. It could be needed Core optimization expert.

- impacted by core network. It could be needed Core optimization expert.
- dependent on optimization service
- The Fast initial GPRS access should be active
- impacted by core network. It could be needed Core optimization expert.
- dependent on optimization service
- The Fast initial GPRS access should be active

- impacted by core network. It could be needed Core optimization expert.

- dependent on optimization service
- Dependent on TRX Class and maximum coding scheme used
- Dependent on assumption on MTU size of 1500bytes
- The Fast initial GPRS access should be active

- impacted by core network. It could be needed Core optimization expert.

- dependent on optimization service
- Dependent on TRX Class and maximum coding scheme used
- Dependent on assumption on MTU size of 1500bytes
- The Fast initial GPRS access should be active

Remarks

- Optimization on service platform could be needed

- Optimization on service platform could be needed

- Optimization on service platform could be needed

Remarks

- Optimization on service platform could be needed

- Optimization on service platform could be needed

Remarks

- Optimization on service platform could be needed

- Optimization on service platform could be needed

- Optimization on service platform could be needed

Remarks

- Optimization on service platform could be needed

 PREREQUISITES

DESIGN PREREQUISITES :
- Network or area composed by at least 120 cells in monoband network or 240 cells in multiband network
- Bandwidth and number of TRX per cell respecting in each band (GSM or DCS) the following criteria Load_factor_modifie
area) > 12
- At least one TS for data will be reserved (in case of high data traffic, the number of TS reserved for data should be highe
- The average daily traffic must be higher than 30Mo/cell (RLC layer) in consolidation area and for the considered KPI
(UL GPRS, DL GPRS,UL EDGE,DL EDGE) in order to have statistical validity
- Network or area should be composed of Dense Urban / Urban and Suburban clutters (if numerous, rural sites should not
- The backbone links (Abis,Gb and A interfaces) shall not introduce long delay (ie Satellite links or similar transmission solu
- Equipments should be mainly new hardware (at least G3 equipment and new TRE's)

CONTRACT & ENVIRONMENT PREREQUISITES :

- Consolidation unit : week or month
- In case of use of shared sites it should be garanteed that radiation from other systems will not impact Costumer network.
- Bandwidth free of external interferences: measured below -120dBm/200kHz
- KPI commitment under the condition of a optimization service contract (cf MSO for service definition) : for complex netwo
- Planning of 3 months / 12 months necessary to reach the KPI target depending of the size and the complexity of the netw
- Within this service contract, Alcatel teams should be fully responsible of the optimization activities
- Cells impacted by network element or transmission problems not included in the computation

PS :
(1) Usual coverage probability: In dense Urban environment>-70dBm; urban> -75dBm; Suburban>-80dBm; Rural>-90dBm
With the usual intersite distances, below an example:
- Dense Urban: from 300 to 1000m - average 500m
- Urban: from 800 to 2000m - average 1000m
- Sub-urban: from 1000 to 4000m - average 2000m
- Rural: >2000m

BSS GPRS KPI

% DL TBF establishment success (major KPI)

RNO Name :
GPRS_DL_TBF_success_rate

% DL TBF normal release

RNO Name : GPRS_DL_TBF_normal_release_rate

% DL TBF acceptable release
RNO Name :
GPRS_DL_TBF_acceptable_release_rate

% DL TBF drop (major KPI)

RNO Name :
GPRS_DL_TBF_drop_rate

% DL PDTCH RLC block retransmission - CS usage

RNO name :
GPRS_DL_RLC_bytes_PDTCH_CSx_retransmissing_ratio

% DL PDTCH RLC block retransmission - MCS usage

RNO name :
GPRS_DL_RLC_bytes_PDTCH_MCSx_retrans_ack_ratio

% UL TBF establishment success (major KPI)

RNO Name :
GPRS_UL_TBF_success_rate

% UL TBF normal release

RNO Name:
GPRS_DL_TBF_normal_release_rate
% UL TBF acceptable release

RNO Name :
GPRS_DL_TBF_acceptable_release_rate

% UL TBF drop (major KPI)

RNO Name :
GPRS_DL_TBF_drop_rate

% UL PDTCH RLC block retransmission - CS usage

RNO name :
GPRS_UL_RLC_bytes_CSx_retransmissing_ack_ratio

% UL PDTCH RLC block retransmission - MCS usage

RNO name :
GPRS_UL_RLC_bytes_PDTCH_MCSx_retrans_ack_ratio

For information some identified GSS KPI

GSS GPRS KPI
% GPRS attach success

% PDP context activation success

% RA update success rate

 PREREQUISITES

etwork or 240 cells in multiband network

(GSM or DCS) the following criteria Load_factor_modified = (Total bandwidth in number of 200kHz channels) / (average TRX per cell i

affic, the number of TS reserved for data should be higher)

yer) in consolidation area and for the considered KPI
stical validity
and Suburban clutters (if numerous, rural sites should not be considered in the KPI computation) with the clutter type defined in (1)
ce long delay (ie Satellite links or similar transmission solutions)
ment and new TRE's)

ion from other systems will not impact Costumer network. To avoid this situation enough antenna spacing shall be used in shared sites
dBm/200kHz
ontract (cf MSO for service definition) : for complex networks, an additional Core expertise should be part of the service proposed by Alc
arget depending of the size and the complexity of the network
nsible of the optimization activities
ot included in the computation

dBm; urban> -75dBm; Suburban>-80dBm; Rural>-90dBm.

DESCRIPTION
(from RNO Tool)

Rate of DL TBF establishment successes (seized by the mobile).

Rate of DL TBF normal release.

Reference: Number of DL TBF establishment successes.
Rate of DL TBF release due to :
- Radio Preemption
- Suspend Resume Procedure
- Cell Reselection.
Reference : Number of DL TBF establishment successes.

Rate of DL TBF drops.

Reference: Number of DL TBF establishment successes.

Ratio of downlink RLC retransmitted data bytes sent on PDTCH

and encoded in CS-x in RLC acknowledged mode.
Reference : overall number of DL RLC data bytes transmitted in
RLC ack mode mode and in GPRS mode.

Ratio of DL RLC data bytes encoded in MCS-x and retransmitted

due to unacknowledgement of the MS, in RLC acknowledged
mode.
RLC blocks containing LLC dummy UI commands are not counted.
Reference : overall number of DL RLC data bytes transmitted in
EGPRS mode.

Rate of UL TBF establishment successes.

Reference: time during which MSs are engaged in uplink-biased

transfers and served by UL TBFs.
Rate of UL TBF release due to :
- Radio Preemption
- Suspend Resume Procedure
- Cell Reselection.
Reference : Number of UL TBF establishment successes.

Rate of UL TBF drops.

Reference: Number of UL TBF establishment successes.

Ratio of uplink RLC bytes retransmitted on PDTCH and encoded in

CS-x in RLC acknowledged mode.
Reference : total number of UL RLC data bytes sent on PDTCH in
RLC ack mode mode and in GPRS mode .

Ratio of UL RLC data bytes encoded in MCS-x and retransmitted

due to unacknowledgement of the MFS, in acknowledged mode.
Reference : overall number of UL RLC data bytes sent on PDTCH
in RLC ack mode and in EGPRS mode.

Level
Mobility Management

Session Management

Mobility Management
andwidth in number of 200kHz channels) / (average TRX per cell in consolidation

red in the KPI computation) with the clutter type defined in (1)

is situation enough antenna spacing shall be used in shared sites

itional Core expertise should be part of the service proposed by Alcatel

B8 RELEASE

FORMULA
(from RNO Tool) Common
Threshold

B8 Formula : (P90a + P90b + P90c + P90d + P90e + P90f) / (P91a +

P91b + P91c + P91d + P91e + P91f)
95%
B9 Formula : (P90a + P90b + P90c + P90d + P90e + P90f) / (P91a +
P91b + P91c + P91d + P91e + P91f)

B8 Formula : P9 / (P90a + P90b + P90c + P90d + P90e + P90f)

93%
B9 Formula : P9 / (P90a + P90b + P90c + P90d + P90e + P90f)
B8 Formula : (P146 + P98c + P434b + P434d) / (P90a + P90b +
P90c + P90d + P90e + P90f)
2%
B9 Formula : (P146 + P98c + P434b + P434d + P481) / (P90a +
P90b + P90c + P90d + P90e + P90f)

(SUCCESS - NORMAL RELEASE - ACCEPTABLE RELEASE) /

SUCCESS

B8 Formula : ( (P90a + P90b + P90c + P90d + P90e + P90f) -

( P146 + P98c + P434b + P434d) - P9 ) / (P90a + P90b + P90c +
7%
P90d + P90e + P90f)

B9 Formula : ( (P90a + P90b + P90c + P90d + P90e + P90f) -

( P146 + P98c + P434b + P434d + P481) - P9 ) / (P90a + P90b +
P90c + P90d + P90e + P90f)

DL RETRANS(CSx) / [DL USEFUL(CSx) + DL RETRANS(CSx)]

B8 Formula : [ (P20a*160 + P20b*240 + P20c*288 + P20d*400) /

3 % (in case CS3/4
8 ] / [ (P20a*160 + P20b*240 + P20c*288 + P20d*400+ P55a*160 +
deactivated)
P55b*240+ P55c*288 + P55d*400) / 8 ]
4 % (in case of
CS3/4 activated)
B9 Formula : [ (P20a*160 + P20b*240 + P20c*288 + P20d*400) / 8 ] /
[ (P20a*160 + P20b*240 + P20c*288 + P20d*400+ P55a*160 +
P55b*240+ P55c*288 + P55d*400) / 8 ]

DL RETRANS(MCSx) / [ DL USEFUL(MCSx) + DL
RETRANS(MCSx) ]

B8 Formula : P20e / [ P20e+

(P55e*176+P55f*224+P55g*296+P55h*352+ P55i*448+P55j*592+ 10%
(P55k*896+P55l*1088+P55m*1184)/2 ) / 8 ]

B9 Formula : P20e / [ P20e+

(P55e*176+P55f*224+P55g*296+P55h*352+ P55i*448+P55j*592+
(P55k*896+P55l*1088+P55m*1184)/2 ) / 8 ]

B8 Formula : (P30a + P30b + P30c) / (P62a + P62b + P62c - P438c)

85%
B9 Formula : (P30a + P30b + P30c) / (P62a + P62b + P62c - P438c)

B8 Formula : P22 / (P30a + P30b + P30c)

95%
B9 Formula : P22 / (P30a + P30b + P30c)
B8 Formula: (P147 + P98d + P434a + P434c) / (P30a + P30b +
P30c)
0.50%
B9 Formula: (P147 + P98d + P434a + P434c + P482) / (P30a + P30b
+ P30c)

(SUCCESS - NORMAL RELEASE - ACCEPTABLE RELEASE) /

SUCCESS

B8 Formula : ( (P30a + P30b + P30c) - P22 - ( P147 + P98d +

5%
P434a + P434c) ) / (P30a + P30b + P30c)

B9 Formula : ( (P30a + P30b + P30c) - P22 - ( P147 + P98d +

P434a + P434c + P482) ) / (P30a + P30b + P30c)

UL RETRANS(CSx) / [UL USEFUL(CSx) + UL RETRANS(CSx)]

B8 Formula : [ (P21a*160 + P21b*240 + P21c*288 + P21d*400) / 8 ] /

[ (P21a*160 + P21b*240 + P21c*288 + P21d*400 + P57a*160 + 3 % (in case CS3/4
P57b*240 + P57c*288 + P57d*400) / 8 ] deactivated)
4 % (in case of
B9 Formula : ( ( ( [p21a]*160 + [p21b]*240 + [p21c]*288 + CS3/4 activated)
[p21d]*400) / 8) /(( ( [p21a]*160 + [p21b]*240 + [p21c]*288 +
[p21d]*400) / 8)+( ( [P57a]*160 + [P57b]*240 + [P57c]*288 +
[P57d]*400) / 8)))

UL RETRANS(MCSx) / [UL USEFUL(MCSx) + UL

RETRANS(MCSx)]

B8 Formula : P21e / [ P21e +

5%
(P57e*176+P57f*224+P57g*296+P57h*352)/ 8 ]

B9 Formula : P21e / [ P21e +

(P57e*176+P57f*224+P57g*296+P57h*352+P57i*448+P57j*592+
(P57k*896+P57l*1088+P57m*1184)/2 ) / 8 ]

Interest
Shows the ability to access the GPRS service
Shows the ability to open a point to point subscription to the GGSN in
order to send and receive data
Shows the ability to update the RA information in the SGSN
 B8 RELEASE B9 RELEASE

MAX Common MAX

Threshold Comments Threshold Threshold

< 98,5 % 95% < 98,5 %

Dependent on Traffic mix, could

be risky to commit on this KPI.
< 98 % 94% < 98 %
Usage of E2E KPIs for services
instead.
 Dependent on Traffic mix, could
be risky to commit on this KPI.
>1% 2% > 0,5 %
Usage of E2E KPIs for services
instead.

>3% 7% >2%

> 2 % (in case 3 % (in case CS3/4 > 2 % (in case CS3/4
CS3/4 deactivated) deactivated) deactivated)
> 3 % (in case of 4 % (in case of CS3/4 > 3 % (in case of
CS3/4 activated) activated) CS3/4 activated)

> 8% only when EDGE is activated 10% > 8%

< 98 % 85% < 98 %

Dependent on Traffic mix, could

be risky to commit on this KPI.
< 95% 94% < 98%
Usage of E2E KPIs for services
instead.
 Dependent on Traffic mix, could
be risky to commit on this KPI.
> 0,5 % 1.5% > 0,5 %
Usage of E2E KPIs for services
instead.

>4% 5% > 1,5 %

> 2 % (in case 3 % (in case CS3/4 > 2 % (in case CS3/4
CS3/4 deactivated) deactivated) deactivated)
> 3 % (in case of 4 % (in case of CS3/4 > 3 % (in case of
CS3/4 activated) activated) CS3/4 activated)

>4% only when EDGE is activated 9% > 4%

RELEASE B10 Release

Comments Proposed Threshold Comments

The DTM feature could

degrade this KPI

Dependent on Traffic mix, could

be risky to commit on this KPI.
Usage of E2E KPIs for services
instead.
Dependent on Traffic mix, could
The usage of DTM feature
be risky to commit on this KPI.
could increase this
Usage of E2E KPIs for services
indicator
instead.

only when EDGE is

only when EDGE is activated
activated

Dependent on Traffic mix, could

be risky to commit on this KPI.
Usage of E2E KPIs for services
instead.
Dependent on Traffic mix, could
be risky to commit on this KPI.
Usage of E2E KPIs for services
instead.

only when EDGE is

only when EDGE is activated
activated
 IMPACTS / RISK ASSESSMENT
PROJECT
NETWORK OPTIM
PLANNING
DESIGN SERVICE
(penalities)

HIGH HIGH HIGH

LOW HIGH HIGH

 LOW HIGH HIGH

HIGH HIGH HIGH

MEDIUM MEDIUM HIGH

MEDIUM MEDIUM HIGH

HIGH HIGH HIGH

MEDIUM HIGH HIGH

MEDIUM HIGH HIGH

LOW HIGH HIGH

MEDIUM MEDIUM HIGH

MEDIUM MEDIUM HIGH

 Remarks
DL TBF establisment can be impacted by the following kind of failures :
- CONGESTION
=> Radio/CPU/DSP/Abis/Ater congestion
=> Depends on Network Design
- RADIO
=> Depends on Optimisation Service
- BSS
=> Depends on the supervision of the network
- GB
=> Depends on Network Design and Optim Service.
DL TBF drops :
- RADIO
=> Depends on Optimisation Service
- BSS
=> Depends on the supervision of the network
- GB
=> Depends on Network Design and Optim Service

=> This KPI is highly dependent on 2nd Global Assumption: availability of

bandwidth.

=> This KPI is highly dependent on 2nd Global Assumption: availability of

bandwidth.

=> This KPI is highly dependent on 2nd Global Assumption: availability of

bandwidth.
=> Highly dependent on the TRX class and MAX_EGPRS_MCS

UL TBF establisment can be impacted by the following kind of failures :

- CONGESTION
=> Radio/CPU/DSP/Abis/Ater congestion
=> Depends on Network Design
- RADIO
=> Depends on Optimisation Service
- BSS
=> Depends on the supervision of the network
- GB
=> Depends on Network Design and Optim Service.
As precised in the description the releases due to the three following procedures
are taken into account by this KPI :
- Radio Preemption => Depends on Optimisation Service
- Suspend Resume => Depends on Optimisation Service
- Cell Reselection => Depends on Network Design and Optim Service.

DL TBF drops :
- RADIO
=> Depends on Optimisation Service
- BSS
=> Depends on the supervision of the network
- GB
=> Depends on Network Design and Optim Service

=> This KPI is highly dependent on 2nd Global Assumption: availability of

bandwidth.

=> This KPI is highly dependent on 2nd Global Assumption: availability of

bandwidth.

=> This KPI is highly dependent on 2nd Global Assumption: availability of

bandwidth.
=> Highly dependent on the TRX class and MAX_EGPRS_MCS
 P r o b le m d e te c te d o n R M S _ m o n o _ m u lti _ w a r n in g r e p o r ts (p e r c e
A lc _ m o n o _ R M S _ R a d io _ lin k _ q u a lit y A lc _ m o n o _ R M S _ D L /U L _ V o ic e _ Q
A lc _ m u lt i_ R M S _ R a d io _ lin k _ q u a lit y A lc _ m u lti_ R M S _ D L /U L _ V o ic e _ Q u
A lc _ w a r n in g _ t o p _ b e s t _ R M S _ R a d io _ lin k _ q u a lit y A lc _ w a r n in g _ to p _ b e s t_ R M S _ D L /U
A lc _ w a r n in g _ t o p _ w o r s t _ R M S _ R a d io _ lin k _ q u a lit y A lc _ w a r n in g _ to p _ w o r s t_ R M S _ D L

P r o b le m N o t
C o n fir m e d
R a d io p r o b le m V o ic e Q u a lity
o n o n e c e ll o r o n o n e T R X , o n e d a te , o n o n e c e ll o r o n o n e T
fo r o n e o r s e v e ra l m e a s u re m e n ts fo r o n e o r s e v e ra l m
( D L /U L R x Q u a l, D L /U L R x L e v , M S P o w e r , B T S ( D l/ U L n o is y c a lls , U L F
P o w e r , T im in g a d v a n c e , C F E , R L C , P a t h b a la n c e )

D L /U L R x Q u a l, D L /U L R x L e v , R L C , P a th b a la n c e P r o b le m s o n
M S P o w e r, B T S P o w e r, T A , n o is y c a lls
C FE

C h e c k c o r r e s p o n d in g
d is tr ib u tio n r e p o r t
A lc _ m o n o _ D L /U L _ R x Q u a lity _ R x L e v e l
A lc _ m o n o _ P o w e r _ 9 0 0 /1 8 0 0
A lc _ m o n o _ T im in g _ A d v a n c e
A lc _ M o n o _ C o n s e c u t iv e _ F r a m e _ E r a s u r e

P r o b le m C o n f ir m e d
( R x Q u a l, R x L e v , P o w e r , T A ) P r o b le m C o n fir m e d
(C F E )
P r o b le m N o t
C o n fir m e d

C h e c k A lc _ m o n o _ R x Q u a lity _ R x L e v e l_ d e ta ile d Chec

B a d p a r a m e t e r t u n in g
( R x Q u a l, R x L e v e l, H ig h v a lu e s o f P a th
B a d c o v e ra g e (T A , B a la n c e ( o n a p e r
P o w e r)
P a th B a la n c e ) T R X b a s is )
B a d r a d io ( R x L e v ,
R x Q u a l, R L C )
C h e c k p a ra m e te r Check h
Check
s e ttin g s (H O ,P C )
A lc _ m o n o _ C a r r ie r _
o v e r _ In te r fe r e n c e
T o o h ig h C /I
T o o h ig h o v e r la p b e tw e e n c e lls u s in g
b e tw e e n c e lls s a m e fr e q u e n c ie s

C h e c k n e tw o rk
d e s ig n C h e c k fr e q u e n c y p la n n i
 u lti _ w a r n in g r e p o r ts (p e r c e ll, p e r T R X )
A lc _ m o n o _ R M S _ D L / U L _ V o ic e _ Q u a lit y
A lc _ m u lt i_ R M S _ D L / U L _ V o ic e _ Q u a lit y
A lc _ w a r n in g _ to p _ b e s t _ R M S _ D L / U L _ V o ic e _ Q u a lity
A lc _ w a r n in g _ to p _ w o r s t _ R M S _ D L / U L _ V o ic e _ Q u a lity

V o ic e Q u a lity p r o b le m
o n o n e c e ll o r o n o n e T R X , o n e d a te ,
fo r o n e o r s e v e ra l m e a s u re m e n ts
( D l/ U L n o is y c a lls , U L F E R b a s e d c a lls )

P r o b le m s o n
n o is y c a lls
P r o b le m s o n F E R
m e a s u re m e n ts

P r o b le m C o n fir m e d
(C F E )

v e l_ d e ta ile d C h e c k v o ic e q u a lity

H ig h v a lu e s o f P a th
B a la n c e ( o n a p e r
T R X b a s is )

Check C h e c k h a rd w a re
o n o _ C a r r ie r _
_ In te r fe r e n c e
T o o h ig h C /I
la p b e tw e e n c e lls u s in g
s a m e fr e q u e n c ie s

C h e c k fr e q u e n c y p la n n in g
Basis of traffic theory: Erlang B abacus

>Cell dimensioning from measurement (re-plan

•one is measuring a traffic of 15 Erlangs, with a bloc

%
•how to dimension the cell?

Offered traffic = 15 / (1-10%) = 16.7 Erlangs!!!!

Channels (16.7;2%) -> 25 TCHs -> 4 TRXs needed
•one is measuring a traffic of 15 Erlangs, with a bloc
%
•how to dimension the cell?

Offered traffic = 15 / (1-10%) = 16.7 Erlangs!!!!

Channels (16.7;2%) -> 25 TCHs -> 4 TRXs needed
g B abacus

urement (re-planning)

langs, with a blocking rate of 10

.7 Erlangs!!!!
4 TRXs needed
langs, with a blocking rate of 10

.7 Erlangs!!!!
4 TRXs needed
 RNO Trainings
Log in RNO client as trainer/rno, to access specific Best Of, etc
that can’t be deleted by trainees.

Presentation of the platform

Lahost2 : OMCR of lannion, B9 MR4 ed2, ip: 172.25.212.206
Daily updates of the ACIE: possible to see events, logical param
tuning browser, etc.
Cartography is done on Lannion with worldmap and google im
There is no QoS available (except Idle Measurements)

Omcr9 : omcr from velizy, B9. IP: 139.54.74.20

Contains QoS for end of 2006

Omcr11 : omcr from velizy, B9. IP: 139.54.74.134

Contains QoS for end of 2006

NPA : 172.25.212.236 (snpala01)

Contains QoS for velizy OMCR (end of 2006 only)
Deactivate the Scheduler and Archiver, to avoid loosing data:
Open terminal
Enter: crontab –r
This command stops all NPA activities

Presentation of the data

Data for OMCR 9 and OMCR 11 are available from W44 2005 till
more than one year of data available.

On OMCR11 : only BSC s304 has data (from W22 2006 only)
Cells per day: from 18/07/2006
Cells per hour: from 2/12/2006 till 20/12/2006
Data for OMCR 9 and OMCR 11 are available from W44 2005 till
more than one year of data available.

On OMCR11 : only BSC s304 has data (from W22 2006 only)
Cells per day: from 18/07/2006
Cells per hour: from 2/12/2006 till 20/12/2006
On OMCR 9 : BSC s221 has data (from W44 2005)
Cells per day: from 17/06/2006 (with some blanks)
Cells per hour: from 01/12/2006 till 20/12/2006

RMS are available (only the “static avg”, not the matrix reports
24/11/2006 for:

In BSC s221 (omcr11):

BTS_1_S1, BTS_1_S2, BTS_1_S3
BTS_DRFU_S1
BTS_143_S1, BTS_144_S1
BTS_TWIN_S1, BTS_TWIN_S2, BTS_TWIN_S3, BTS_TWIN_S4,

Use CITRIX to velizy in order to have fresh RMS data, and repo

Required “QOS” exercises

Typical QOS problem : call drop, tch congestion, sdcch drop, s

(R110)

QoS problem linked to RMS : path balance, low RxLev, poor Rx

QoS problem linked to neighbor : use of adjacency QoS (R180)

QoS change linked to Events : a modification of logical parame

in QoS

Diagnosis : Use of diagnosis to analyse one typical QoS proble

QoS problem linked to RMS : path balance, low RxLev, poor Rx

QoS problem linked to neighbor : use of adjacency QoS (R180)

QoS change linked to Events : a modification of logical parame

in QoS

Diagnosis : Use of diagnosis to analyse one typical QoS proble

Cartography : Use of cartography to detect frequency interfere

neighbors

Required “Customization” exercis

Import a RNP project

Import map
Import .cof files

à should be done on VELIZY OMCR, since LANNION RNP alrea

be modified. It is needed to create a file with (dummy) coordina

Create graphs

Create indicators

Typical QOS problem

BSC S304:
9/9: call drop due to BSS
the drop is occuring for a long period, but gets really bad at 8/9
with graph ALC MONO CALL.
BSC S304:
9/9: call drop due to BSS
the drop is occuring for a long period, but gets really bad at 8/9
with graph ALC MONO CALL.

Call drop

400000

350000

300000

250000

200000

150000

100000

50000

Find if it is due to BSS internal or BSS REMOTE TC ?

AND
Find if it is common to all cells in this BSC or only few cells ?
ALL CELLS
=> BSC problem or Transcoder problem
Internal : due to operation and maintenance actions, or a very f
reset, probably software issue)
Remote TC : due to faulty board (degraded functions, probably

SOME CELLS => Per BTS ? Per TCU ? Per LAC ?

Internal : due to O&M actions, or a very faulty board (reset/rest
BTS in BSSUSM)
Remote TC : due to degraded ABIS link or faulty SUM card, or a
equipment among the group of faulty cell

SOME CELLS => just one cell ?

Internal : due to operation and maintenance actions, or a very f
(reset/restart the TRX, lock the RSL)
Remote TC : due to degraded TRE board, or faulty antenna sys

In this case, the whole BSC is impacted, with call drop HO and
Call drop HO certainly caused by call drop BSS, so in priority, f
Drag n drop all cells from BSC S304, with indicators
Call drop BSS int (in family QoS / Call Drop)
Call drop BSS int rate (in family QoS / Call Drop)
Call drop BSS rate dist BSS (in distribution indicators family :
In this case, the whole BSC is impacted, with call drop HO and
Call drop HO certainly caused by call drop BSS, so in priority, f
Drag n drop all cells from BSC S304, with indicators
Call drop BSS int (in family QoS / Call Drop)
Call drop BSS int rate (in family QoS / Call Drop)
Call drop BSS rate dist BSS (in distribution indicators family :

Then use the Spreadsheet function (ascending sort) to find the

having the highest number of drops due to BSS. But all cells ar
action has to be performed on the BSC.

2/10: tch assignment failures

15/11: tch assignment failures
19/11: tch assignment failures
16/12: sdcch assignment failures
15/11: tch assignment failures
19/11: tch assignment failures
16/12: sdcch assignment failures

S254
Call drop and TCH assignment failure on one cell only:
1st cell : not enough traffic
2nd cell : good candidate for optim : CI = 7801
call drop radio+tch assignment failure
do a daily ALC MONO CALL from 20/11 to 8/12
notice : SDCCH DROP RATE, TCH ASSIGN FAILURE RATE, CA

analyse per TRX (warning : graph QOS TRX doesn’t work)

use spreadsheet with drop indicators and tch assign indicators
29/11 à notice all traffic is on TRX4.
Why ? because voice goes on last trx first, even if it is faulty !
Problem can be linked to trx4 or the whole cell.

analyse per hour (useless though)

13/10: sdcch drop rate

18/10: call drop rate

Cell Zone creation

-----------------------------------------------------------------------------------------
Absolute date without specific weekday:
cell with Call_DRop_Rate >= 2%
Freq_RANGE= GSM900
Absolute date: 15/12/2006 (Friday)– Specific weekday: None
Date formula in the CellZone Editor Panel after validating: ?
-----------------------------------------------------------------------------------------
Absolute date with a specific weekday
cell with Call_DRop_Rate >= 2%
Freq_RANGE= GSM900
Freq_RANGE= GSM900
Absolute date: 15/12/2006 (Friday)– Specific weekday: None
Date formula in the CellZone Editor Panel after validating: ?
-----------------------------------------------------------------------------------------
Absolute date with a specific weekday
cell with Call_DRop_Rate >= 2%
Freq_RANGE= GSM900
Absolute date: 15/12/2006 (Friday) – Specific weekday: Last Mo
Date formula date in the CellZone Editor Panel after validating:
-----------------------------------------------------------------------------------------
Relative date without specific weekday
cell with Call_DRop_Rate >= 3%
Freq_RANGE= GSM900
EN_EGPRS = ENABLE
Relative date: - 133 Days – Specific weekday: None
Formula date in the CellZone Editor Panel after validating:?
-----------------------------------------------------------------------------------------
Relative date with a specific weekday
cell with Call_DRop_Rate >= 3%
Freq_RANGE= GSM900
EN_EGPRS = ENABLE
Relative date: - 133 – Specific weekday: Last Monday
Formula date in the CellZone Editor Panel after validating:?
-----------------------------------------------------------------------------------------

Absolute date without specific weekday:

cells with RTCH_assign_cong_max_rate >= 3%
AND (EN_FDR = DISABLE or EN_DR = DISABLE)
Absolute date: 15/12/2006 (Friday)– Specific weekday: None
Date formula in the CellZone Editor Panel after validating:

Absolute date with a specific weekday

cells with RTCH_assign_cong_max_rate >= 3%
AND (EN_FDR = DISABLE or EN_DR = DISABLE)
Absolute date: 15/12/2006 (Friday) – Specific weekday: Last M
Date formula date in the CellZone Editor Panel after validating
Date formula in the CellZone Editor Panel after validating:

Absolute date with a specific weekday

cells with RTCH_assign_cong_max_rate >= 3%
AND (EN_FDR = DISABLE or EN_DR = DISABLE)
Absolute date: 15/12/2006 (Friday) – Specific weekday: Last M
Date formula date in the CellZone Editor Panel after validating

Relative date without specific weekday

cells with RTCH_assign_cong_max_rate >= 3%
AND (EN_FDR = DISABLE or EN_DR = DISABLE)
Relative date: - 133 Days – Specific weekday: None
Formula date in the CellZone Editor Panel after validating:

Relative date with a specific weekday

cells with RTCH_assign_cong_max_rate >= 3%
AND (EN_FDR = DISABLE or EN_DR = DISABLE)
Relative date: - 133 – Specific weekday: Last Monday
Formula date in the CellZone Editor Panel after validating: Las

Rules:
IF GPRS OR EGPRS ENABLED, Check: MAX_PDCH > 0

Create an QOS INDICATOR:

 Create an QOS INDICATOR:
Creation of a global call setup success %, taking into account
SDCCH request (for normal assignment) to TCH assignment su
assignment)

Close all RNO clients

Open QoS Indicator Descriptor Manager
Right-Click à “Create”

Name: _Global_CSSR
Reference Name: G_CSSR
Formula: SDNARQN / TCNASUN
(= RTCH_assign_success / SDCCH_assign_request
(= Number of SDCCH seizure requests during radio link establi
Number of RTCH succesfully seized by the mobile during norm
procedure)
Description: This indicator is not taking into account the “subs
retries of a MS on the RACH.
inings
pecific Best Of, etc, and create graphs

f the platform
172.25.212.206
vents, logical parameters, perform rno

map and google image.

urements)

134

only)
void loosing data:

of the data
from W44 2005 till W50 2006. So there is

W22 2006 only)

6
 from W44 2005 till W50 2006. So there is

W22 2006 only)

6
2005)
lanks)
06

the matrix reports) from 26/09/2006 to

S3, BTS_TWIN_S4, BTS_TWIN_S5

MS data, and reports.

S” exercises

tion, sdcch drop, short call duration, etc.

ow RxLev, poor RxQual (R31)

acency QoS (R180)

n of logical parameters leads to a change

typical QoS problem

ow RxLev, poor RxQual (R31)

acency QoS (R180)

n of logical parameters leads to a change

typical QoS problem

requency interference and missing

zation” exercises

ANNION RNP already exists and shouldn’t

(dummy) coordinates for VELIZY cells.

S problem

ets really bad at 8/9 till 14/09. Show BSC

ets really bad at 8/9 till 14/09. Show BSC

Call drop

8
Preemption
7
Drop - BSS RTC
6
Drop BSS Intern
5
Drop - HO
4
Drop - Radio
3
% RTCH drop
2 % Call Drop
1

OTE TC ?

r only few cells ?

actions, or a very faulty board (automatic

unctions, probably hardware issue)

AC ?
y board (reset/restart the SUM card or the

ulty SUM card, or any common

actions, or a very faulty board

faulty antenna system, etc.

h call drop HO and call drop BSS internal :

SS, so in priority, fix the call drop BSS !
dicators

rop)
indicators family : QSCDBR_DZB1)
h call drop HO and call drop BSS internal :
SS, so in priority, fix the call drop BSS !
dicators

rop)
indicators family : QSCDBR_DZB1)

ng sort) to find the worst cell: CI 51906 is

BSS. But all cells are actually impacted, an
e cell only:

01

12
AILURE RATE, CALL DROP RATE

doesn’t work)
h assign indicators and tch traffic, on

ven if it is faulty !
ell.

creation
----------------------------------------------------

weekday: None
ter validating: ?
----------------------------------------------------
 weekday: None
ter validating: ?
----------------------------------------------------

c weekday: Last Monday

nel after validating: ?
----------------------------------------------------

y: None
fter validating:?
---------------------------------------------------

st Monday
fter validating:?
--------------------------------------------------

3%
BLE)
c weekday: None
fter validating:

3%
BLE)
c weekday: Last Monday
nel after validating:
fter validating:

3%
BLE)
c weekday: Last Monday
nel after validating:

3%
BLE)
y: None
fter validating:

3%
BLE)
st Monday
fter validating: Last Thu (Today –

es:
_PDCH > 0

INDICATOR:
 INDICATOR:
king into account all phases : from
TCH assignment success (for normal

_request
g radio link establishment procedure /
mobile during normal assignment

account the “subscriber-transparent”

 RNO V4 features hig

History of indicators in the spreadsheet and the reports

Warning on QoS indicators variation
Display of indicator reliability
Management of QoS on Other objects
Cell zone editor improvement
TRX parameters management
GSM RNO external cells management
Client shutdown on timer expiry
Parameters consistency with the OMC
Massive tuning sessions for realignment on the
reference
Cell class assignment
Voronoi patterns change

RNO V5 features high

Migration from CI mode to LAC-CI m

Direct connection of RNO to the OM
Synchronization of LCS configuratio
Abort Quick diag operation
Column and row sorting in spreadsh
Spreadsheet snapshot
Use relative date in Cell Zone
Cell Notes
MNC MCC criteria in WZ definition
GPRS Distribution Threshold Manage
1 Alcatel 9156 RNO Overview
1.1 Alcatel 9156 RNO aims in the “toolchai
 Direct connection of RNO to the OMC-R (
1.2 Software and hardware presentation 1

2 Operating Modes 26
2.1 Starting Alcatel 9156 RNO 28
 Possibility to create the working zone fro
2.2 Alcatel 9156 RNO main screen 33
2.3 Graphical User Interfaces facilities 35
2.4 Main Menu bar 39
 Parameters consistency with the OMC (B
2.5 Network objects windows 47
 Management of QoS on Other objects (B8
 Cell class assignment (B8)
 Cell Notes (B9)
 Cell zone editor improvement (B8)
 Use relative date in Cell Zone (B9)

3 Parameters and Design analysis 62

3.1 Parameters and Functions window 64
 TRX parameters management (B8)
3.2 Spreadsheet window 76
 Spreadsheet snapshot (B9)
 Export to Excel improved (B8)
 Extractor (B8)
 Column and row sorting in spreadsheet (
 Abort Quick diag operation

4 Quality of Service analysis 86

 Spreadsheet snapshot (B9)
 Export to Excel improved (B8)
 Extractor (B8)
 Column and row sorting in spreadsheet (
 Abort Quick diag operation

4 Quality of Service analysis 86

4.1 QoS Counters 88
 History of indicators in the spreadsheet a
(multi-object Evolution)
4.2 QoS Indicators -> Diagnosis analysis 93
 QoS at Busy Hour (B8)
 Display of indicator reliability (B8)
 Administrative tool to create indicators i
 Multi-objects evolution charts (B8)
 Warning on QoS indicators variation (B8)
4.3 Help presentation 105
4.4 QoS Reports 107

5 Cartographic zone analysis 141

5.1 Presentation 143
 Voronoi patterns change (B8)
 Support of raster images
5.2 RNP files format 147
 Synchronization of LCS configuration dat
5.3 Extended Cartography Facilities 152
 THL for MS Position (B8)

6 Tuning session / Tuning Browser 170

6.1 Tuning session 172
 Ability to use a reference cell and inhibit
 Massive tuning sessions for realignment
 GSM RNO external cells management (B8
6.2 Tuning Browser 185

7 Common user functions 194

7.1 Working Zone Manager 196
 Ability to use a reference cell and inhibit
 Massive tuning sessions for realignment
 GSM RNO external cells management (B8
6.2 Tuning Browser 185

7 Common user functions 194

7.1 Working Zone Manager 196
 MNC MCC criteria in WZ definition (B9)
7.2 QoS Report & View Template Manager
 Multi-objects evolution charts (B8)
 Warning on QoS indicators variation (B8)
7.3 Diagnosis Scenario Manager 210
7.4 RMS template manager 216
7.5 GPRS Distribution Threshold Manager
 GPRS Distribution Threshold Manager(B9

8 Administrator functions presentation 225

8.1 Reference value manager 227
8.2 Rule Manager 233
8.3 RNP Project Configuration 239
 Synchronization of LCS configuration dat
 Support of raster images(B8)
8.4 QoS Indicator Descriptor Manager 246
 Administrative tool to create indicators i
8.5 User Manager 251
Logged user manager
8.6 Batch Manager 254
8.7 Cell Class Manager 259
8.8 Topology Manager 263
8.9 Import / Export Manager 268
 QoS Customer indicators I/E (B8)
 Export real C/I values in the RMS experie
 MMI for extractor (B8)

9 RNO Server Administration 278

9.1 RNO Server Architecture 280
 AACS (B8)
 QoS Customer indicators I/E (B8)
 Export real C/I values in the RMS experie
 MMI for extractor (B8)

9 RNO Server Administration 278

9.1 RNO Server Architecture 280
 AACS (B8)
 Client shutdown on timer expiry (B8)
9.2 Import administration Tasks 289
9.3 RNO-NPA Service Administration tasks
9.4 Troubleshooting 315
9.5 Backup and Restore Management 322
9.6 CI to LAC/CI Migration 335
 Migration from CI mode to LAC-CI mode (

APPENDIX 338
GLOSSARY 360
4 features highlight (B8)

the reports MMI for extractor

Abort of RNO request
Ability to use a reference cell and inhibit a cell tuning
QoS at Busy Hour
Multi-objects evolution charts
Possibility to create the working zone from the cells
list
Logged user manager
Administrative tool to create indicators in RNO
the Export real C/I values in the RMS experience matrix
Support of raster images

features highlight (B9)

CI mode to LAC-CI mode

n of RNO to the OMC-R
of LCS configuration data with OMC
g operation
sorting in spreadsheet
apshot
e in Cell Zone

a in WZ definition
n Threshold Manager
w
n the “toolchain” 9
o the OMC-R (B9)
presentation 19

O 28
orking zone from the cells list (B8)
creen 33
s facilities 35

th the OMC (B8)

s 47
her objects (B8)

ent (B8)
ne (B9)

alysis 62
ns window 64
ent (B8)

)
B8)

spreadsheet (B9)

86
)
B8)

spreadsheet (B9)

86

spreadsheet and the reports (B8)

osis analysis 93

ity (B8)
te indicators in RNO (B8)
arts (B8)
variation (B8)

s 141

B8)

nfiguration data with OMC (B9)

acilities 152

owser 170

ell and inhibit a cell tuning (B8)

r realignment on the reference (B8)
anagement (B8)

4
196
 ell and inhibit a cell tuning (B8)
r realignment on the reference (B8)
anagement (B8)

4
196
finition (B9)
late Manager 203
arts (B8)
variation (B8)
ager 210
216
hold Manager 220
ld Manager(B9)

esentation 225
r 227

n 239
nfiguration data with OMC (B9)
B8)
Manager 246
te indicators in RNO (B8)

268
E (B8)
e RMS experience matrix (B8)

n 278
280
E (B8)
e RMS experience matrix (B8)

n 278
280

expiry (B8)
sks 289
stration tasks 301

agement 322
5
LAC-CI mode (B9)
bit a cell tuning

rom the cells

in RNO
rience matrix
 3.4.11 RNO at 8500 cells – RFD 112234 - [4.11

All components of the toolchain i.e. RNO, NPA and LASER must support 8500 cells.
A Load&Stress campaign is performed to test the capacity of RNO to manage the new t
this feature.
All software modifications will be treated as CRQ Thalès.

3.3.7 RNO parameters consistency with the OMC-R - RF

RFD 106822

REASON FOR For historical reasons, the name of the parameters managed in RNO and the O
CHANGE causes some troubles for people having to use both RNO and the OMC-R. Some
Orange France has identified the most confusing names, the list has been sent t
Arnaud Bonnefond from Orange France.
DESCRIPTION See below

(A) - Optional use of OMC label for RNO parameters

The RNO application lists the logical parameter names. For historical reason, the RNO pa
OMC-R parameter names are sometime different. The aim of the feature is to add a displ
parameters with the RNO name and the OMC-R name following the rules below:

· If the RNO parameter name and the OMC-R parameter name are different, RNO display
OMC-R parameter name.
· In the other case, it displays the RNO parameter name.

The RNO OMC-R parameter name display is only done in the logical parameter tab objec
logical parameters what ever the selected mode (cell...). The value display is always the R
to display the ACIE values.
The new display type (RNO + OMC-R name or RNO name only) is a user settings option
by default.
 3.3.5 QoS for non-RNO objects - RFD 110425 - [
RFD 110425

REASON FOR One big drawback of RNO for QoS follow-up, is that RNO is only able to address
CHANGE TRX. Thus MFS, N7, A interface indicators are not available, while it could be u
several customers) to provide powerful RNO facilities. 7 new RNO elements co
Channel, PVC, Sub-BSS/GPU, MFS, N7, A interface channel).
Second big drawback is: some indicators existing in B6 release and defined as Cell
release because their validity domain will be changed to sub-BSS (which is not re
have the same problem between B7 and B8. This issue can be perceived as a regre
DESCRIPTION See below

One big drawback of RNO for QoS follow-up, is that RNO is only able to address objects
TRX…Thus GPU, N7, LapD indicators are not available, while it could be useful to provi

Second big drawback is: some indicators existing in B6 release and defined as Cell valid
disappeared in B7 release because their validity domain will be changed to sub-BSS (wh
RNO). And the same problem exists between B7 and B8.
To solve the problem:
a) Non-RNO objects are described in a configuration file (same file on the RNO sever an
b) At the first request, the NPA topology is loaded.
c) Only the QoS function and the one bound to them are impacted (QoS counters, QoS
Excel export, csv export and copy)
One mode for all non-RNO objects, with one page in the NoteBook of the NO per non-R
Solution:
1) In ‘non-RNO Object’ mode, on the first NoteBook page selection:
- The client asks the object list to NPA database (send a query to the NPA daemon, the
the name, the NPA key and a small description).
2) Each time the entire network NoteBook page is selected, the Qos indicators and repo
refreshed and filtered on the availability domain depending on the non-RNO object.
3) At each Qos actions, the control in the period choice view is based on the non-RNO o
the network NoteBook page selected.
4) After the period selection, all the actions are the same like a normal mode (QoS query

Editor and properties:

Ø For all the QoS editors and properties, the availability domain view displays all the RN
table.
Ø For availability domain empty, the type is not displayed.

Configuration data:
Ø This data are loaded in the RNO database at the RNO installation.
Ø For example, the non-RNO object configuration file gives (to be define at specification
Editor and properties:
Ø For all the QoS editors and properties, the availability domain view displays all the RN
table.
Ø For availability domain empty, the type is not displayed.

Configuration data:
Ø This data are loaded in the RNO database at the RNO installation.
Ø For example, the non-RNO object configuration file gives (to be define at specification
- Position in the non-RNO object mode
- Sort name (ex.: GPU)

- Long name (es.: Sub-BSS GPU)

- Position in the availability domain (ex. 10)
- NPA index column(s) name(s) (ex.: CELLID)
- NPA index column(s) type(s) (ex.: CHAR (5))
- QoSIndicator for the object name

The entire QoS configuration data files are synchronized with the non-RNO object config
This feature needs to :
- Add new configuration file for the QoS daemon:
- Define a network object per configuration file (network object with their indexes).
Assumptions:
1) Only up to two key columns is allowed for non-RNO object
2) Column type for key column of non-RNO object is String and only String

New objects in RNO:

5 new RNO elements are now assessable:
- LapD,
- Bearer Channel,
- PVC,
- Sub-BSS/GPU,
- N7.

3.4.3 Operational class resulting from cell zone evaluation

 3.4.3 Operational class resulting from cell zone evaluation
RFD 106861

REASON FOR The cell class notion of RNO is a powerful attribute. However, it cannot be easily c
CHANGE the RNP ASCII interface). Introducing the notion of "operational class" in opposition
would be a great help. This is one of the key features of RNO in UMTS.
DESCRIPTION See below

Modification of the cell class attribute management to allow a "planed usage" (as it is done
"operational usage" including the user edition (a specific user right is requested).
In case of "planed usage" setting:
The cell class definition and usage is equivalent to the RNO B7 implementation. Any RNP
operational import will reset the cell class attribute to the planed value.
In case of "operational usage" setting:
The cell class definition is done and handled by the user itself via the RNO HMI and it is th
cell class. No import RNP or operational can modify the cell class.
The cell class edition management shall introduce the facility to modify this attribute on a l
selection). Such of facility allows the creation of a cell zone, its computation, the propagat
cells mode and the attribution of the "operational class" to the cell list which results from th
The cell class has to be available in the reference value editor (as it is done today). The n
classes shall be extended to 64 requested in B8 (16 in B7).

3.4.8 Cell Zone Editor Improvement - [4.8]

More design parameters are proposed to define a Cell Zone. These parameters are disp
(same than the one proposed for parameter design),
Following categories of parameters are out of the scope of this feature:
- The parameter lists (frequencies, neighbor,LSA)
- The Planned Logical Parameters category
- The Antenna Design
- The Location categories that work only on planned cell (Cell Zone filter works only on o
- The Planned Logical Parameters category
- The Antenna Design
- The Location categories that work only on planned cell (Cell Zone filter works only on o

3.4.9 Reshuffle of cell properties panel - [4.9]

3.4.9.1 Neighbourhood Tab

The neighbor are displayed in a matrix with the following columns:

Operational Planed Name Serving Target

Name
Operational Planed icon Operational Planed icon
icon icon

An icon is displayed if the serving/target cell is planed.

An icon is displayed if the serving/target cell is operational.

3.4.9.2 Frequencies Tab

3.3.6 TRX parameters management - RFD 10680

RFD 106809

REASON FOR RNO doesn't provide TRX parameters

CHANGE
DESCRIPTION See below

An analysis has to be launched with OSY/PCS/RNE to check what are the missing TRX
should display.
TRX logical parameters can only be used in RNO, and Parameter Reference Value Mana
TRX parameters are not used as criteria for Cell zone and are not used in a tuning sessi
The TRX parameters are managed as logical parameters with historic.
All cell design parameters implemented in the previous release redundant with the new T
An analysis has to be launched with OSY/PCS/RNE to check what are the missing TRX
should display.
TRX logical parameters can only be used in RNO, and Parameter Reference Value Mana
TRX parameters are not used as criteria for Cell zone and are not used in a tuning sessi
The TRX parameters are managed as logical parameters with historic.
All cell design parameters implemented in the previous release redundant with the new T
removed.
This feature requires to update the RNO traffic model (see section 5. V4 performance ob
Parameters Example: TRX_PREF_MARK ,GPRS_PREF_MARK

3.4.4 MMI to configure extractor - RFD 111374 - [

Configure extractor:
It shall automatically build the RNO extractor input file following the [3] specification (extra
the other modes).
· Add a button in the spreadsheet (ToolTip clearly state the way to use it: click or drag & d
· When you drop a request to that button or if you click that button when the spreadsheet
request result, it propose you to generate the RNO extractor input file associated to the d
propose you to chose the file name and directory where to save it.
If the file already exist, it shall be grown by the new extract command (the user have to be
For QOS and Histo, the selected dates and periods have to be relative to the date of the d
we are the 20/04/02. the period is 05/04/02 - 10/04/02
the period shall be: D-15 to D-10

3.5.2 Various MMI facilities to speed up problems identificatio

RFD 128274

REASON FOR This RFD is a set of small features that represent various customer requirements. A
CHANGE optimizer life and are, for most of them, very old requests.
DESCRIPTION See below

3.5.2.1 RNO Object propagation from QoS reports

QoS reports return objects or indicators on which the optimizer would like to make a furt
way to select these objects and propagate them to the relevant tree gadgets to make furt
Request:
Selected Indicators and/or objects displayed in a QoS report in graphic mode are propag
A select all entry in the contextual menu is also required.
Assumptions
3.5.2.1 RNO Object propagation from QoS reports
QoS reports return objects or indicators on which the optimizer would like to make a furt
way to select these objects and propagate them to the relevant tree gadgets to make furt
Request:
Selected Indicators and/or objects displayed in a QoS report in graphic mode are propag
A select all entry in the contextual menu is also required.
Assumptions
- The RNO distribution reports are not impacted by this feature
- The QoS report must have values.

3.5.2.2 RNO Enhanced spreadsheet export

Users complain that the whole RNO spreadsheet is exported and not what has been filte
Request:
The export to excel feature respects the filter done in the spreadsheet.
In term of MMI, it is requested to add in spreadsheet a contextual menu with 2 actions:
- Export to Excel (full)
- Export to Excel (display)

- First one allows to export full spreadsheet to excel as it is already done with "export" bu
- Second one enables the new export feature : what is displayed on spreadsheet.

The current "export" button is let unchanged.

Assumptions:
- This feature export filters done in spreadsheet (not highlighted cells).
- The extractor is not impacted by this feature.

3.5.2.3 RNO new cell zone filter

In RNO, it is not possible to consolidate QoS on an existing WZ, except on the current o
operator wants to compare QoS between different Working zones, it is not possible
Request:
In cell zone editor, the working zone attribute is available as a new cell zone filter, and is
The Global Working Zone can not be used to create a cell zone.

3.5.2.4 RNO automatic creation of working zone

The working zone manager of RNO doesn't allow an easy creation of WZ based on an a
selection
Request:
Add a contextual menu in tree gadget of cell mode and BSS mode in order to create aut
(without working zone manager) a new Working Zone.
Assumptions:
- Once the working Zone is created, user can load it via button "Open another Working Z

3.5.2.5 RNO add reverse adjacency selection

When looking at QoS, it is sometimes needed to select adjacencies and reverse adjacen
compare them. RNO doesn't provide a simple facility to do that.
Request:
In tree gadget of adjacency mode, add contextual menu in order to add to the selection r
adjacencies of the selected adjacencies (only reverse adjacencies which belong to the c
zone will be added).
Assumptions:
- Once the working Zone is created, user can load it via button "Open another Working Z

3.5.2.5 RNO add reverse adjacency selection

When looking at QoS, it is sometimes needed to select adjacencies and reverse adjacen
compare them. RNO doesn't provide a simple facility to do that.
Request:
In tree gadget of adjacency mode, add contextual menu in order to add to the selection r
adjacencies of the selected adjacencies (only reverse adjacencies which belong to the c
zone will be added).
If no reverse adjacency is found in the current Working Zone, a warning message is disp
Warning: performance impact.

3.3.2 Abort of RNO request - RFD 101619

RFD 101619

REASON FOR Long actions in RNO client cannot be interrupted if a user has made a mistake.
CHANGE
DESCRIPTION See below

The RNO request mechanism is impacted by the abort feature:

1. QoS indicators & reports
A progress window is displayed for each RNO request with a cancel button. A click Canc
down aborts the request. During the abort process, the progress window displays the me
Please wait"
The progress window locks all other user interaction.

3.4.2 Historical of indicators (Qos multi-evolution) - RFD 1

RFD 106812

REASON FOR There is no simple way for looking the history of an indicator/counter. The only way
CHANGE is a painful operation if to be done several times a day.
DESCRIPTION See below

The aim of the feature is to introduce the history management of an indicator and counter.
1. QoS Multi-Evolution (1), Query system
New RNO Query (impact the Rno client, QoS service and daemon) to introduce the histor
2. QoS Multi-Evolution (2), basic application in spreadsheet
"QoS Multi-Evolution (1), Query system" is mandatory
Depending on the user choice:
- n net. Objet & n indicator/cpt. => 1 date (no changes)
- 1 net. Objet & n indiator/cpt; => 1 period (new)
- n net. Objet & 1 indiator/cpt; => 1 period (new)
The NPA application is impacted:
The Feature requires to implement a new NPA macro to merge String and Date.

3.5.5 QoS at Busy Hour – RFD 128096

RFD 128096

REASON FOR When doieng QoS analysis, it is sometimes more relavant to analyse data at the bu
CHANGE on an average of the day.
DESCRIPTION See below

All reports and indicators available by hour are displayed by day at GSM busy hour or GP
The user can select 2 new periodicity (BH GSM and BH GPRS )
The RNO daemon selects the corresponding values.
This feature is applicable on:
- Reports (Mono-object evolution, Multi-Object Comparison, Multi-Object Evolution)
- Spreadsheet indicators (all cases)

- Extractor (performance mode)

- Thematic Layer.
The RNO daemon selects the corresponding values.
This feature is applicable on:
- Reports (Mono-object evolution, Multi-Object Comparison, Multi-Object Evolution)
- Spreadsheet indicators (all cases)

- Extractor (performance mode)

- Thematic Layer.

Busy Hour query principle

Function BH for the indicator I with the Indicator reference Iref:

BusyHour (Iref, I) = I[ MAXPOS (Iref)]

Example:
SELECT NTOTDAY( MC01, STARTTIME, ENDTIME, 24) As Iref, NTOTDAY( MC02, STA
As I1, NTOTDAY( MC03, STARTTIME, ENDTIME, 24) As I2
FROM COC110H WHERE DAY=[23/06/03] AN (CELLID="03000" OR CELLID="03001" O
SELECT Iref, I1, I2, MAXPOS(Iref) As BH_POS
DISPLAY I1[BH_POS] as I1_BH, I2[BH_POS] as I2_BH

Assumptions
- The 2 indicators used for BH GSM and BH GPRS are put in RnoAdmin.ini

3.3.4 Display of indicator reliability (from PM reporting) -

RFD 106834

REASON FOR When some data reported in the PM is wrong, some extrapolation is done by NPA
CHANGE (daily, weekly and monthly). There is no easy way for the user to know how confid
consolidated indicator value.
DESCRIPTION See below

When some data reported in the PM are wrong, some extrapolation is done by NPA when
(daily, weekly and monthly). There is no easy way for the user to know how confident he
consolidated indicator value. The purpose of the feature is to update NPA and RNO appli
which validate the counters.

2 kind of data may be lost and must be detected:

- period lost during a day (ex.: 1 half-hour on the day),
- object lost on the consolidated object (ex.:1 TRX on the Cell).

To detect the lost data we use a specific reliability indicator, ex.:

Reliability_call_drop_rate =
consolidated indicator value. The purpose of the feature is to update NPA and RNO appli
which validate the counters.

2 kind of data may be lost and must be detected:

- period lost during a day (ex.: 1 half-hour on the day),
- object lost on the consolidated object (ex.:1 TRX on the Cell).

To detect the lost data we use a specific reliability indicator, ex.:

Reliability_call_drop_rate =
((Reliability_cell / nb_cell) + (Reliability_TRX / nb_TRX)) / (PERIOD * 2)
We divide by nb_cell or nb_TRX to detect the object lost.
We divide by PERIOD for detect the period lost.
3.3.4.1 NPA:
Only relability indicators on Type 110 are computed. The blocks Cell and TRX of the type
group of counters (depends on BSC hardware).
One reference counter is computed for each group of counters. Then, a reference counte
or several stored reliability indicator.
Principle: stored 1 PM Validity indicator by counters group
In PM import, for the entire counters group the validity is controlled.
- if block OK: I_PMValidity_blk_n = real measurement time
- else: I_PMValidity_blk_n = 0 or NULL
These indicators are normalized with ZTOTDAY (0 for the missing value) and consolidate
SUM (ZTOTDAY ())).
The nb_cell (GSM), nb_TRX, nb_cell_GPRS and nb_GPU must be stored in NPA.
This data come from the OMC or MFS and they are never consolidated.

3.3.4.2 RNO:
The indicators I_PMValidity_blk_n are use like standard stored indicators and new validity
created (I_PMValidity_blk_n_rate = I_PMValidity_blk_n / PERIOD) according to counters
formula
The direct indicator interaction solution is chosen:
In the indicators data-model, a validity measurement indicator is added(NULL is possible)
Unlike the sampling indicator, the validity measurement indicator uses it owns threshold.
For indicator spreadsheet and QoS report (not Mono-distribution report):
In the date select window, 2 options are added:
1. "sampling"
2. “test validity measurement”.

If the "validity measurement" or "sampling" indicator is N/A, the result is shown in normal
If one of the "validity measurement" or "sampling" option is selected, the spreadsheet col
Assumption:
- The message queue length in the metrica kernel has to be enough wide to handle the re
solution.
- No Diagnosis primitives and no Warning query reports improvement.
- Historic of each Qos view shall not be impacted by this feature.
Feature restrictions:
- The lost cell in a CellZone can not be detect (the number cell of the CellZone is not know
issue is not yet solved. Any solution may be treated as THALES CRQ.
- If the nb_cell_GPRS or/and the nb_GPU can not be stored in NPA, the reliability GPRS
Assumption:
- The message queue length in the metrica kernel has to be enough wide to handle the re
solution.
- No Diagnosis primitives and no Warning query reports improvement.
- Historic of each Qos view shall not be impacted by this feature.
Feature restrictions:
- The lost cell in a CellZone can not be detect (the number cell of the CellZone is not know
issue is not yet solved. Any solution may be treated as THALES CRQ.
- If the nb_cell_GPRS or/and the nb_GPU can not be stored in NPA, the reliability GPRS
can not be detected.

3.4.6 Administrator tool to create new indicators in RN

The RNO Administrator has the possibility to create, and delete standard QoS indicators
Administration Tool (access in the administration tool bar).
These user-defined indicators can be composed of stored indicators and calculated indic
Administrator) .
3.4.6.1 Indicators Administration tool
The new editor is an extension of the QoS threshold editor. As the tool is launched, a tree
Standard indicators, vectors, matrix, and axes appears. Each indicator is classified in its f
families and sub-families, which does not contain any indicator are not displayed.
An indicator is either system (non-editable), either administrator. In the tree gadget, the ic
that the indicator is system. The icon I (white lock) indicates that the indicator is administr

When the user right-click on an indicator, a contextual menu appears:

If the indicator is system the following menu appears:
- Search
- Properties
- Update threshold (if threshold define)
- Create
- Create by copy
If the indicator is admin the following menu appears:
- Search
- Properties
- Create
- Create by copy
- Delete
- Update threshold (if threshold define)
- Create
- Create by copy
If the indicator is admin the following menu appears:
- Search
- Properties
- Create
- Create by copy
- Delete

3.4.6.2 Indicator Editor Panel

The panel contains the following fields:
- Name : the name is unique and can not be empty. The first character of the name is fixe
- Ref Name : it can not be empty.
- Formula: it can not be empty. A button permits to display a tree gadget containing all ind
A double click on an indicator inserts it where the cursor is located.
- Family/Sub-family : it can not be empty. The list of the existing family/sub-family is propo
- Unit: it can not be empty. The administrator chooses the unit in a list (build from list of un
- Severity: a radio button (True, False) allows the administrator to choose the severity ver
graphic is automatically updated).
- Availability domain : automatically computed (logical AND with all the indicator used in th
indicator and the reliability indicator).
- Reliability/Sampling indicator: the administrator can choose the indicator in a list (same
- Thresholds: a checkbox enables the threshold matrix.
- Sampling value: not empty if the sampling indicator is defined (de-de-correlated of thres

1.1.1.1.13.4.6.2.1 Create and create by copy

When the editor is opened in Create Mode,
As the user clicks on button <OK>, following checks are performed:
- The fields described in above section are controlled,
- check of the syntax of the formula,
- check that the availability domain is not null (logic AND of the availability domain of the i
formula)

A progress bar allows the user to follow the different steps of the checking phase.
In case of error or warning, a window appears. It contains all the error and warning messa
If the indicator is correct, the daemon is refreshed when the QoS indicator manager is clo
3.4.6.2.2 Edit Mode
The user has no possibility to edit or modify an indicator.
3.4.6.2.3 Delete Mode
Before deleting an indicator, a confirmation message is displayed. If the user confirms tha
deleted, the following checks must be done:
- Check that the indicator is not used in other indicators formula, Views, CZ, THL, O&M e
filter), diagnosis (only the indicator that launch the diagnosis).
3.4.6.3 Indicator Import/Export tool
A new mode Import/Export is added. It only allows managing Admin indicators. The check
indicator edition are also done during the import.
- In case of error during the import, the formula is set to NULL, the error message and the
the description.
This import mode has only one possibility: add indicator.
- Check that the indicator is not used in other indicators formula, Views, CZ, THL, O&M e
filter), diagnosis (only the indicator that launch the diagnosis).
3.4.6.3 Indicator Import/Export tool
A new mode Import/Export is added. It only allows managing Admin indicators. The check
indicator edition are also done during the import.
- In case of error during the import, the formula is set to NULL, the error message and the
the description.
This import mode has only one possibility: add indicator.

A new NPA function that return NULL is implemented in NPA.

3.5.6 Multi-objects evolution charts – RFD 1280

RFD 128095

REASON FOR RNO doesn't allow to follow the QoS on many cells over a given period.
CHANGE
DESCRIPTION See below

This is a pure MMI development knowing that the corresponding queries in RNO-NPA da
developed in RNO step 2 with RFD 106812.
A new type of report (Multi-objects evolution report) is added: need to be able to create,
Excel a report for which each view contains several objects, several dates and one indica
Editor: same as for the mono-object evolution report with only 1 indicators per view (Tree
only views with 1 indicator).
There is one color/pattern per object for all the views of the report.
A scroll-bar is added in the legend.

Assumptions:
- no correlation with events available.
- Maximum number of cells will be defined in function of number of combinations of patte
A scroll-bar is added in the legend.

Assumptions:
- no correlation with events available.
- Maximum number of cells will be defined in function of number of combinations of patte

3.3.1 Warnings on QoS indicators variation - RFD 1

RFD 101627

REASON FOR RNO QoS warning reports are triggered only on absolute indicators values and not look on variation from o
CHANGE to another for example. For instance, if call drop on one cell goes from 1% to 2% or if its traffic is divided
optimizer will not be alerted.
DESCRIPTION See below

This feature introduces a warning report on Qos indicators variation in RNO V4.
It consists to add a new set of sub-type in the warning report package. It avoids the creat
and is simplest to be integrated.

The present sub-types that already exist in RNO V3 in the warning report package are lis
· Threshold on value with color.
· Top n best on value.
· Top n worst on value.

To implement the feature, the six following new sub-types are added:

· Relative threshold on variation with a percentage.

· Absolute threshold on variation with a percentage.
· Relative top n best on variation.
· Absolute top n best on variation.
· Relative top n worst on variation.
· Absolute top n worst on variation.

Moreover, the warning report behavior is modified to integrate the new set of behavior de
Main impact:
1. In the warning query, the object selection is not on the warning indicator value but the w
following the formula below:
warning indicator variation = (warning date) - (warning date - n period).
2. The report editor shall add a variability flag and the percentage edit box. When the sub
threshold, the user does not select an alarm color but put a percentage. Moreover the be
new sub-types above.
3. The report display add the variation value in the table view (between the indicator valu
Low impact:
4. This report type use the same view that the warning report.
5. The data model is updated, by adding of new fields/attributes in an existing object.
6. The Tree Gadget integrates a new overlay icon to show the variation attribute.
warning indicator variation = (warning date) - (warning date - n period).
2. The report editor shall add a variability flag and the percentage edit box. When the sub
threshold, the user does not select an alarm color but put a percentage. Moreover the be
new sub-types above.
3. The report display add the variation value in the table view (between the indicator valu
Low impact:
4. This report type use the same view that the warning report.
5. The data model is updated, by adding of new fields/attributes in an existing object.
6. The Tree Gadget integrates a new overlay icon to show the variation attribute.
7. The Report reader software is updated
8. The migration process puts no variation by default.

3.4.7 Voronoi Boundaries patterns - [4.7]

In the cartography mode, a new combo box allows the user to choose the pattern used in
set of 15 patterns is proposed to the user.
This pattern is common to all the users.
This modification takes effect at next RNO startup.
After best server pattern modification, a message box request the user to restart RNO to
account.

3.5.3 Support of Raster images - RFD 128103

RFD 128103

REASON FOR From the very beginning, RNO did not support raster maps and customers required t
CHANGE
DESCRIPTION See below

RNO only supports MIF vector files as input data. It is requested to support in a complem
which would complete the cartographic data representation in RNO.
Indeed, numerous results produced by radio engineering products such as RNP tools are
The best way to support raster maps would be to rely on well-know (and shared!) raster fo
referencing (grounding) information (it seems less mandatory to integrated a dedicated ed
and maps geo-referencing management).
RNO only supports MIF vector files as input data. It is requested to support in a complem
which would complete the cartographic data representation in RNO.
Indeed, numerous results produced by radio engineering products such as RNP tools are
The best way to support raster maps would be to rely on well-know (and shared!) raster fo
referencing (grounding) information (it seems less mandatory to integrated a dedicated ed
and maps geo-referencing management).

For the format of ASCII geo-referencing file, the one used by the MAPINFO GIS shall be

Example of geo-referencing file:

3.4.5 Massive tuning sessions for realignment on the referen

RFD 110428

REASON FOR Tuning sessions on parameters are limited to parameter per parameter. Some cus
CHANGE wants a more massive way i.e. multi NEs and multi-parameters. This is also the only
network if massive reference values changes are to be performed. Such case will
benefit of operational class facility.
DESCRIPTION See below

Multi selection in the tuning session (only for tunable parameters).

Drop the multi selection into tuning session -> create all the mono parameter sessions by
session if applied to the omc-r shall set the reference values (if the parameter is tunable a
Such facility allows to set any kind of value allowed to the parameter (as it is today) and n
value.
The maximum number of tuning operation is limited by the variable MaxOperations locate

The drag & drop between the logical parameter tab and the tuning tab is allowed. This fea
Tuning Browser tool.

3.3.9 Tuning Browser update - [3.9]

The tuning browser tool is used to display the tuning session created in the RNO applica
the PRC files generated by RNO application (tuning session). The [3.3] and [3.6] features
type and parameters to handle at the tuning browser tool.
The tuning browser tool is used to display the tuning session created in the RNO applica
the PRC files generated by RNO application (tuning session). The [3.3] and [3.6] features
type and parameters to handle at the tuning browser tool.

3.5.4 Inhibition of cell tuning & copy cell - RFD 12

RFD 128097

REASON FOR There are cells in networks that are tuned once for all and that nee
CHANGE
overriding of parameter values by other users. RNO does not provi
on these cells. Moreover, once a cell has been properly tuned, it is
is as a reference and copy its parameter values to other cells.
DESCRIPTION See below

For inhibition:
1) A flag is added on cell object to classify non-tunable cells. The non-tunable cells are h
gadget of the cell mode (in italic).
2) A contextual menu in the tree gadget is used to set a cell as non-tunable cell. This fea
users with tuning rights.
3) Users who has set this flag (owner) is registered in database.
4) An editable comment is also added on cell object (if the administrator modifies the co
modified)..
5) The new flag, the editable comment, and owner are displayed in a new tab of the cell
for reference flag and inhibited flag). The cell name is displayed with the same highlightin
gadget of the cell mode. The modification of the flag and of the editable comment is allo
and the owner.
6) These non-tunable cells are ignored during tuning session. Moreover, an error messa
tunable cell is used in a tuning session (1 error message in case of all selected cells are
If tuning session including one or more cells for which flag inhibiting tuning has been set
expected:
- On session opening (edit / show) a warning message is displayed: it indicates "inhibited
flag.
The HMI may look like warning message for not planned cells drag & drop in map.
Session opens with all operations whatever state of "inhibited" flag. No automatic cleanin
- On export session, PRC generation fails if one cell is "inhibited" and error is mentioned
automatically displayed.

For reference:
1) A flag is added on cell object to classify non-tunable cells. The non-tunable cells are
gadget of the cell mode (in blue).
2) A contextual menu in the tree gadget is used to set a cell as non-tunable cell. This fea
users with tuning rights.
3) Users who has set this flag (owner) is registered in database.
4) An editable comment is also added on cell object (if the administrator modifies the com
 - On export session, PRC generation fails if one cell is "inhibited" and error is mentioned
automatically displayed.

For reference:
1) A flag is added on cell object to classify non-tunable cells. The non-tunable cells are
gadget of the cell mode (in blue).
2) A contextual menu in the tree gadget is used to set a cell as non-tunable cell. This fea
users with tuning rights.
3) Users who has set this flag (owner) is registered in database.
4) An editable comment is also added on cell object (if the administrator modifies the com
modified).
5) The new flag, the editable comment, and owner are displayed in a new tab of the cell
for reference flag and inhibited flag). The cell name is displayed with the same highlightin
gadget of the cell mode. The modification of the flag and of the editable comment is allow
and the owner.

6) During a parameter tuning session, the parameter of the reference cell is used if it exi
reference value is used.
It is required that this operation can be done on many parameters and many cells at the
RFD 110428 : Massive tuning, that has already been developed in RNO B8.
The two flags described above can be set independently.

3.3.3 GSM RNO external cells management - RFD 1

RFD 106810

REASON FOR External cells are poorly managed by RNO

CHANGE
DESCRIPTION See below

The purpose of the "GSM RNO external cells management" feature is to introduce the cre
external cells in RNO applications. Moreover, in case of an adjacency between a cell and
feature allows to display the Qos of the reverse adjacencies of that cell if it exist in NPA.
(A) Creation of external Cells / Adjacencies.
(A) Creation of external Cells / Adjacencies.

In the adjacency tuning:

A.1/ In the Added field, add an item in the contextual menu: "Add Adj. to a NEW RNO Ext
This menu open a window to fill the new external cell info (lac, ci, bcch arfn, frequency ran
Create the external cell in RNO database with a LAC CI check consistency.
Create the Adjacency by default between the cell and the created external cell.
A.2/ In Added field, add an item in the contextual menu: "Add Adj. to external cell"
This menu opens a window that list all external cells existing in RNO database.
User selects an external cell.
Create the Adjacency by default between the cell and the created external cell.

Note:
At Adjacency creation, the logical parameters are set to reference values. They won't be m
Tuning browser must be upgraded ([3.9][3.9]).
(B) Display the reversed adjacencies.
The Adjacency mode is modified to introduce a "RNO external cells" filter at the HMI leve
adjacencies between RNO external cells.
The Qos request is modified to take the adjacencies to RNO external cells into account. T
the user has to select a set of adjacencies, select Qos request and drop these selections
(spreadsheet, Qos report). When the adjacencies selected are all of them based on RNO
user shall be prompted to perform the Qos request on the adjacencies (as it is implement
reversed adjacencies.
If the user chooses to perform the Qos request on the reversed adjacencies, the Qos req
adjacencies. The adjacencies IDs are swapped to identify the reversed one. The result di
zone and report zone) the adjacencies swapped IDs and the properties are disabled.
 3.4.10 Display logged users in the user manager-

When logged on as administrator, the user should be able to view the number of users l
is logged
In the user manager, a new button permits to display a modeless window containing all
showing:
· user name
· IP address
· Application name.
This window is refreshed when the user clicks on <refresh> button.

3.4.1 RNO Client shutdown on timer expiry - RFD 1016

The feature requests 2 kinds of shutdown:
1. RNO Client logoff after non activity timer (like screen saver behavior).
The RNO client have to be logoff after a non activity timer expiration following the RNO n
below). This timer is set to 1 hour by default on the server side. However the timer has to
side. Both of timer configuration, server side and client side have to be hidden and non d
The feature requests 2 kinds of shutdown:
1. RNO Client logoff after non activity timer (like screen saver behavior).
The RNO client have to be logoff after a non activity timer expiration following the RNO n
below). This timer is set to 1 hour by default on the server side. However the timer has to
side. Both of timer configuration, server side and client side have to be hidden and non d
The minimum value shall be 15 minutes. 5 minutes before the logoff, a system modal dia
count down before logoff. At this level, the user shall be able to interrupt the logoff proce
After logoff timer expiration, the flexlm token is revoked and the login panel appears.
2. RNO Client shutdown before night maintenance.
RNO clients shutdown automatically before night maintenance actions (backup, PRC file
shutdown is defined at the server side and modifiable by the server administrator (the mo
account only after restarting clients). 5 minutes before the shutdown, a topmost dialog bo
down before final shutdown. At this level, the user shall not be able to interrupt the shutd
RNO application is usable until the shutdown.
In both cases, by default the countdown timer is set to 5 minutes on the server side. if the
greater than the main timer, it will be automatically reset to 5 minutes..
Handle conflict between the two cases (in term of timer : priority to the shutdown timer). T
have to be corrupted if a tuning session, cell zone manager, thematic layers manager or
modified or not saved...
Any extra RNO application like tuning session, batch manager, thematic layer or batch w
The RNO Client shutdown on timer expiry feature shall be by default activated. However,
hidden option. Pay attention to correctly implement and test such of hidden option.

RNO non activity definition:

RNO application is considerate as non active (or in IDLE mode) when:
Ø No request are running (what ever the request is),
Ø No user action (mouse and keyboard),

3.3.8 RNO applications access control service - [

The aim of the feature is to implement a login restriction server at the RNO server applica
handle any RNO user login at the RNO server side and implement some restriction mana

At server side a service checks and memorizes each client access to the server. This ser
(Applications Access Control Service).
At client side, each RNO application handles a connection to the AACS. Before connectin
application sends a logon request to the AACS.
The aim of the feature is to implement a login restriction server at the RNO server applica
handle any RNO user login at the RNO server side and implement some restriction mana

At server side a service checks and memorizes each client access to the server. This ser
(Applications Access Control Service).
At client side, each RNO application handles a connection to the AACS. Before connectin
application sends a logon request to the AACS.
Once the connection is established, the application sends the following information:
Ø IP address (Physical Address is better to avoid IP address conflict) and client name,
Ø software version,
Ø user name and password,
Ø application name or identifier.
Ø process ID (see warning above).
Then the AACS has to
1) Check the equality between the client version and the database version,
2) Check the user name and the password,
3) Check the logon rules (see below),
4) Send the database name in order to permit the client to connect to the database (this c
connections, see feature 4.4),
5) Store the connection information
If only one check is wrong, the AACS refuses the logon by sending an error message.
Logon rules :
1) At a given time, only one couple {user, tool} is allowed, except for Batch Scheduler.
2) At a given time, the administrator has an exclusive access to a tool.
3) The system user has an exclusive access to the database.
4) All the import tools run manually use the system user login.
5) All the export tools run manually use the administrator login.
6) At a given time, no more than one tool can modify, delete or reference a given resourc
7) The same application cannot be launched several times on the same computer (proce
Before an RNO application closes, it sends a message to disconnect from the AACS.
The connection established between an application and the AACS is permanent in order
disconnection (not indicated by message). In case of brutal disconnection, the logged ap
All connection / disconnection must be written in a log file with the following information :
Ø date/time,
Ø IP address (Physical Address is better to avoid IP address conflict) and client name,
Ø user name,
Ø application name or identifier,
Ø error message in case of refused connection or in case of brutal disconnection.
If the application cannot connect to the AACS, the login is refused.
The AACS responds to the following application requests :
Ø get all the user connected (useful for User Manager : user deletion forbidden if current
Ø get all the applications connected (see feature[4.10])
The AACS responds to the following application requests :
Ø get all the user connected (useful for User Manager : user deletion forbidden if current
Ø get all the applications connected (see feature[4.10])
 – RFD 112234 - [4.11]

must support 8500 cells.

of RNO to manage the new traffic model induced by

with the OMC-R - RFD 106822

ers managed in RNO and the OMC-R are not consistent. This
oth RNO and the OMC-R. Some harmonization has to be done.
names, the list has been sent to MNO team through a mail of

istorical reason, the RNO parameter names and the

the feature is to add a display option to show all
ing the rules below:

me are different, RNO displays the both: RNO and

e logical parameter tab object. This is done for all the

value display is always the RNO one. There is no need

nly) is a user settings option is set as "RNO name only"

 cts - RFD 110425 - [3.5]

hat RNO is only able to address objects he manages, e.g. cells,

not available, while it could be useful (and already required by
ilities. 7 new RNO elements could be available (LapD, Bearer
ce channel).
n B6 release and defined as Cell validity domain disappear in B7
ged to sub-BSS (which is not recognized by RNO). And we will
ssue can be perceived as a regression by some customers

only able to address objects he manages, e.g. cells,

le it could be useful to provide powerful RNO facilities.

ase and defined as Cell validity domain will be

be changed to sub-BSS (which is not recognized by

me file on the RNO sever and the NPA server).

pacted (QoS counters, QoS indicators, QoS report,

eBook of the NO per non-RNO object.

lection:
ery to the NPA daemon, the result give for the object:

the Qos indicators and reports tree gadgets are

n the non-RNO object.
is based on the non-RNO object availability domain of

e a normal mode (QoS query, display or Export).

main view displays all the RNO and non-RNO type on a

tallation.
(to be define at specification level):
main view displays all the RNO and non-RNO type on a

tallation.
(to be define at specification level):

h the non-RNO object configuration file.

ct with their indexes).

t
and only String

cell zone evaluation - RFD 106861

cell zone evaluation - RFD 106861

e. However, it cannot be easily changed (need to modify it from

f "operational class" in opposition to the existing "planned class"
es of RNO in UMTS.

"planed usage" (as it is done in RNO B7) or an

right is requested).

7 implementation. Any RNP import followed by

ed value.

via the RNO HMI and it is the only way to modify the
ass.
to modify this attribute on a list of cells (multiple
s computation, the propagation of the cell zone to the
cell list which results from the cell zone computation.
(as it is done today). The number of available cell

mprovement - [4.8]

These parameters are displayed in a tree gadget

his feature:

l Zone filter works only on operational cell).

l Zone filter works only on operational cell).

operties panel - [4.9]

umns:

Target

d icon Operational Planed icon

icon

agement - RFD 106809

k what are the missing TRX parameters that RNO

meter Reference Value Manager

e not used in a tuning session.
h historic.
se redundant with the new TRX parameters are not
k what are the missing TRX parameters that RNO

meter Reference Value Manager

e not used in a tuning session.
h historic.
se redundant with the new TRX parameters are not

ection 5. V4 performance objectives).

ARK

ctor - RFD 111374 - [4.4]

ng the [3] specification (extractor section only and not

ay to use it: click or drag & drop).

utton when the spreadsheet window is filled with
nput file associated to the data dropped. It will also
ve it.
ommand (the user have to been aware).
e relative to the date of the day:

problems identification – RFD 128274

various customer requirements. All these features aim at easying

quests.

zer would like to make a further analysis. There is no

ant tree gadgets to make further investigation

in graphic mode are propagated to the object window.

zer would like to make a further analysis. There is no
ant tree gadgets to make further investigation

in graphic mode are propagated to the object window.

re

d and not what has been filtered at display level.

eadsheet.
xtual menu with 2 actions:

ready done with "export" button

ayed on spreadsheet.

ed cells).

WZ, except on the current one. If an

zones, it is not possible

a new cell zone filter, and is displayed in a new tab.

ne.

eation of WZ based on an arbitrary cell

mode in order to create automatically

n "Open another Working Zone".

cencies and reverse adjacencies to

hat.

rder to add to the selection reverse

encies which belong to the current working
n "Open another Working Zone".

cencies and reverse adjacencies to

hat.

rder to add to the selection reverse

encies which belong to the current working

, a warning message is displayed.

uest - RFD 101619

user has made a mistake.

re:

cancel button. A click Cancel button or a ESC key

ess window displays the message "Abort processing.

lti-evolution) - RFD 106812 - [4.2]

n indicator/counter. The only way is to create a QoS report which
day.

of an indicator and counter.

mon) to introduce the history management.

e String and Date.

our – RFD 128096

elavant to analyse data at the busy hour of the day rather that

ay at GSM busy hour or GPRS busy hour.

S)

Multi-Object Evolution)
Multi-Object Evolution)

ref, NTOTDAY( MC02, STARTTIME, ENDTIME, 24)

000" OR CELLID="03001" OR CELLID="03002")

RnoAdmin.ini

from PM reporting) - RFD 106834

me extrapolation is done by NPA when consolidating this data

for the user to know how confident he can be in the reported

olation is done by NPA when consolidating this data

r to know how confident he can be in the reported
update NPA and RNO applications with the PM flags

l).

x.:
 update NPA and RNO applications with the PM flags

l).

x.:

ERIOD * 2)

ks Cell and TRX of the type 110 are divided in several

rs. Then, a reference counter is used to compute one

rolled.

ssing value) and consolidated by SUM (GP -> D with

ust be stored in NPA.

nsolidated.

d indicators and new validity indicator are automatically

RIOD) according to counters (in NPA) and indicators

r is added(NULL is possible).
ator uses it owns threshold.
ion report):

he result is shown in normal color.

elected, the spreadsheet color filter is activated.

enough wide to handle the request generated by this

ovement.
ure.

ll of the CellZone is not know by the daemon) (this

ES CRQ.
in NPA, the reliability GPRS cell or/and GPRS GPU
enough wide to handle the request generated by this

ovement.
ure.

ll of the CellZone is not know by the daemon) (this

ES CRQ.
in NPA, the reliability GPRS cell or/and GPRS GPU

new indicators in RNO - [4.6]

te standard QoS indicators via a new QoS Indicator

dicators and calculated indicators (system or

s the tool is launched, a tree gadget containing

indicator is classified in its family and sub-family. The
or are not displayed.
tor. In the tree gadget, the icon H (black lock) indicates
hat the indicator is administrator.

appears:
character of the name is fixed to “_”.

ree gadget containing all indicators present in database.

cated.
ng family/sub-family is proposed to the administrator.
t in a list (build from list of unit existing in the database).
or to choose the severity versus value reading (the

ith all the indicator used in the formula, the sampling

the indicator in a list (same as formula).

ed (de-de-correlated of threshold).

ormed:

e availability domain of the indicators presents in the

the checking phase.

the error and warning messages.
QoS indicator manager is closed.

ayed. If the user confirms that the indicator has to be

ula, Views, CZ, THL, O&M events, Cartography (HO

.

Admin indicators. The checks performed after an

L, the error message and the formula is concatenated to

ula, Views, CZ, THL, O&M events, Cartography (HO
.

Admin indicators. The checks performed after an

L, the error message and the formula is concatenated to

on charts – RFD 128095

over a given period.

ding queries in RNO-NPA daemon have already been

: need to be able to create, display and export to

several dates and one indicator.
y 1 indicators per view (Tree gadget in editor contains

eport.

ber of combinations of pattern/color.

ber of combinations of pattern/color.

ors variation - RFD 101627

cators values and not look on variation from one week

goes from 1% to 2% or if its traffic is divided by 2, the

ariation in RNO V4.

package. It avoids the creation of a new type of report

arning report package are listed below:

e added:

e the new set of behavior described below:

ning indicator value but the warning indicator variation

n period).
tage edit box. When the sub-report type is variability and
ercentage. Moreover the behavior has to follow the three

(between the indicator value and the historical value).

.
es in an existing object.
e variation attribute.
n period).
tage edit box. When the sub-report type is variability and
ercentage. Moreover the behavior has to follow the three

(between the indicator value and the historical value).

.
es in an existing object.
e variation attribute.

ries patterns - [4.7]

o choose the pattern used in the best server maps. A

st the user to restart RNO to take the modification into

mages - RFD 128103

er maps and customers required this.

ted to support in a complementary way raster map,

n RNO.
ducts such as RNP tools are saved in a raster format.
-know (and shared!) raster formats including geo-
to integrated a dedicated editor for grounding points
 ted to support in a complementary way raster map,
n RNO.
ducts such as RNP tools are saved in a raster format.
-know (and shared!) raster formats including geo-
to integrated a dedicated editor for grounding points

the MAPINFO GIS shall be used.

nment on the reference - RFD 110428

ameter per parameter. Some customers, especially Dutchtone,

-parameters. This is also the only convenient way to realign the
o be performed. Such case will occur if the operator takes full

ers).
mono parameter sessions by default. Then this tuning
if the parameter is tunable at omc-r).
ameter (as it is today) and not only the reference

riable MaxOperations located in the file RnoAdmin.ini.

ning tab is allowed. This feature does not impact the

er update - [3.9]
created in the RNO application and to un-compress
). The [3.3] and [3.6] features introduce new adjacency
 created in the RNO application and to un-compress
). The [3.3] and [3.6] features introduce new adjacency

& copy cell - RFD 128097

d once for all and that need to be frozen to prevent

users. RNO does not provide a way to inhibit tuning
s been properly tuned, it is required to be able to set
values to other cells.

. The non-tunable cells are highlighted in the tree

as non-tunable cell. This feature is available for all

ase.
administrator modifies the comment, the owner is not

ayed in a new tab of the cell properties (common tab

yed with the same highlighting effect than in the tree
the editable comment is allowed for the Administator

n. Moreover, an error message is displayed if a non-

case of all selected cells are inhibited).
hibiting tuning has been set. Following behavior is

played: it indicates "inhibited" cells with owner of the

ls drag & drop in map.

d" flag. No automatic cleaning is required.
ited" and error is mentioned in log file that is

s. The non-tunable cells are highlighted in the tree

as non-tunable cell. This feature is available for all

ase.
dministrator modifies the comment, the owner is not
 ited" and error is mentioned in log file that is

s. The non-tunable cells are highlighted in the tree

as non-tunable cell. This feature is available for all

ase.
dministrator modifies the comment, the owner is not

ayed in a new tab of the cell properties (common tab

yed with the same highlighting effect than in the tree
he editable comment is allowed for the Administrator

eference cell is used if it exists, otherwise the

meters and many cells at the same time thanks to the

ped in RNO B8.

management - RFD 106810

eature is to introduce the creation of adjacencies to

djacency between a cell and an external cell, the
of that cell if it exist in NPA.
Add Adj. to a NEW RNO External Cell"
, ci, bcch arfn, frequency range, cell type).
k consistency.
ated external cell.
d Adj. to external cell"
n RNO database.

ated external cell.

ence values. They won't be modified at all.

al cells" filter at the HMI level. This filter points out the

external cells into account. To perform a Qos request,

st and drop these selections into a sensitive zone
e all of them based on RNO external cells then the
acencies (as it is implemented today) or on the

ed adjacencies, the Qos request is built on reverse

reversed one. The result displays (in spreadsheet
properties are disabled.
n the user manager- [4.10]

o view the number of users logged on as well as who

eless window containing all the users connected:

button.

mer expiry - RFD 101617 - [4.1]

r behavior).
piration following the RNO non activity definition (see
de. However the timer has to be configured at the client
have to be hidden and non documented (.ini file entries).
 r behavior).
piration following the RNO non activity definition (see
de. However the timer has to be configured at the client
have to be hidden and non documented (.ini file entries).
e logoff, a system modal dialog box shall display the
to interrupt the logoff process.
he login panel appears.

ce actions (backup, PRC files export). The hour of

server administrator (the modification is taken into
utdown, a topmost dialog box shall display the count
be able to interrupt the shutdown process. However the

utes on the server side. if the countdown timer value is

minutes..
rity to the shutdown timer). The RNO database don't
thematic layers manager or batch manager are opened,

er, thematic layer or batch will be closed.

default activated. However, it may be disabled using an
such of hidden option.

de) when:

ss control service - [3.8]

er at the RNO server application. Such of feature shall

ement some restriction management.

ccess to the server. This service is called “AACS”

the AACS. Before connecting to database, the

er at the RNO server application. Such of feature shall
ement some restriction management.

ccess to the server. This service is called “AACS”

the AACS. Before connecting to database, the

e following information:
conflict) and client name,

abase version,

nnect to the database (this can be useful for remote

ending an error message.

cept for Batch Scheduler.

to a tool.
.
.
n.
or reference a given resource.
n the same computer (process ID check).
connect from the AACS.
AACS is permanent in order to detect a brutal
isconnection, the logged application have to be closed.
h the following information :

conflict) and client name,

brutal disconnection.
used.

deletion forbidden if current connection)

deletion forbidden if current connection)
 New Security concept

Azimute,Positions(X,Y)
PM used by the MFS
BSS PM
/Alctel/var/share/AFTR/APME/BSC
/Alctel/var/share/AFTR/APME/MFS
1

2200- [crontab]
OMC-R
RunPeriodicExpor -all 2200- [crontab]
/alcatel/omc3/omc3rno/script/run_periodicExport -all RunPeriodicExpor -laser
1
---> /Alctel/var/share/AFTR/RNO 2300- Services (Get info)
Cell design
2 Alarms;ope cde
(1h)ftp=>d:/Laser/Import/omc_N
Logical
Drive test Conf.
RMS: nprstartpa_bss_rms
Radio 0031-/rms_loader.sh
Measurements 3

5’- [crontab]
Put in RNO db 1 /npr/bin/nprstartpmXfer (
NLSCExport.tgz get>Alctel/var/share/mpm
PM

2 (2’)-Binary
put>/spool/bss/parse_pm/Omc
2
RNP Planned
Cell.cof
design 0100- [at]- ImpRun.bat
Map/(X;Y)
Planned Paraml ImpOmc.cfg
Cell Class

LAN connection Service: RNO-NPA-re

RMS+Laser: no Paser
MFS: Parser and Load_r7g

A9156 RNO
/metrica/flexlm/licences
/npr/logs
Add OMC-R: /npr/bin/npr-conf-OMC.pl

OMCR: BSC: RNO:

SUN UNIX PC Server 2003
DB: OODB, Object Oriented DB DB: DLS, Data Load Segment DB: ORACLE DB
- RNO clients
OPMC: On Demand Measurment - using CITRIX/Citrix ser
compain - u can use VNC (Virtuel
PMC: Performance Measurment Connection) but is not s
Compain
-MPM can support from
(PM: Type 110 Cell/ervery hour according to the OMC-R
Type 180 Adjacency/every 4 hours MPM is based on Metric

Type 31: RMS: it can be scheduled on

demand
define a periode/ BTS store measuement
into BSC at the end of that period

MPM: Metrica Performance Management

Compain
-MPM can support from
(PM: Type 110 Cell/ervery hour according to the OMC-R
Type 180 Adjacency/every 4 hours MPM is based on Metric

Type 31: RMS: it can be scheduled on

demand
define a periode/ BTS store measuement
into BSC at the end of that period

MPM: Metrica Performance Management

obsynt: 4 days on the omcs?

 A-GPS

MSC
SMLC GMLC
in GPU
AFTR/APME/MFS
LCS Client
MFS Counters; Positions(X,Y)
CI,TA: Ellipsoide Arc OSP
crontab] OSP
HLR
riodicExpor -laser
0- Services (Get info)
Unavailability
Alarms;ope cde 5’- [crontab]
Indicators + Events
>d:/Laser/Import/omc_N nprstartmfsXfer
put/spool/bss/laser/
Laser
3 INDLASER.xx.tgz
RMS: nprstartpa_bss_rms GPRS
031-/rms_loader.sh 0105-LaserFileLoader.pl
Parser
5’- [crontab] 4 Loader
/npr/bin/nprstartpmXfer (cfg) Scheduler
get>Alctel/var/share/mpm Parsers 5 Loaders
pm;conf 3 -Loadmap- 4
(2’)-Binary ASCII
put>/spool/bss/parse_pm/Omc_N put>spool/BSS/load_r7
NPA
QoS-On request(TQL)

Daemon:
/metrica/RNO/RNO_NPAd
(alcatel/npa/var/RNO)
Service: RNO-NPA-request

B8 Creation Flex Ind

Admin:Import/output/QOSIndicator.csv /npr/tmp/QOSIndicator.csv
/npr/loadmap/flexind.def

RNO: NPA:
PC Server 2003 SUN Unix
DB: ORACLE DB DB: Metrica, DICO/ tool develpped by
- RNO clients Metrica for Alcatel (storage: 2 years)
- using CITRIX/Citrix server since B8
- u can use VNC (Virtuel Network
Connection) but is not secured

-MPM can support from 250 to 6000 cells

according to the OMC-R Configuration
MPM is based on Metrica NPR 3.3
-MPM can support from 250 to 6000 cells
according to the OMC-R Configuration
MPM is based on Metrica NPR 3.3
 INTERFACES BETWEEN A9156 RNO AND OTHER INVOL

1 BSS release compatibility

A9156 RNO V5 is designed for the Alcatel BSS release B9.

It remains compatible with Alcatel BSS B8

2 Retrieval of the operational logical configuration:

The operational logical configuration of the network managed by RNO V5 is ex

OMC-R G3 database(s).
Both of them produce information in a PRC format, which is object-oriented s
object classes (called MOC) with their properties.
Impact on each OMC-R for operational logical configuration retrieval is limited t
night.

3 Upload of a tuning session

When an optimiser wants to propose a change in the network operational state
he describes a tuning session within RNO, which is a series of operations to a
This tuning session is then converted to PRC commands into files downloaded
Both of them produce information in a PRC format, which is object-oriented s
object classes (called MOC) with their properties.
Impact on each OMC-R for operational logical configuration retrieval is limited t
night.

3 Upload of a tuning session

When an optimiser wants to propose a change in the network operational state
he describes a tuning session within RNO, which is a series of operations to a
This tuning session is then converted to PRC commands into files downloaded
OMC-R operators are then responsible for application of the command file(s) ont
The operator can use an external tool called Tuning Browser to easily display an
tuning session before application. Note however that some information given in
not reflected in the PRC files. It concerns mainly the tuning advice operation
apply to other OMC-Rs, as seen from one OMC-R server.
Impact on the OMC-R server from RNO is thus limited to the download of com
directory.

3. RNP:
- Retrieval of the planned cell design
Radio network planning, which is an upstream activity, provides the cell design
for handover, frequency map, etc.) to the build production in a format called POL

- Update of the RNP database from RNO

The planned network is not always the same than the operational network, for m
difference can result in problems when assigning to operational cells
Furthermore, whereas the planned frequency plan relies on a theoretical wa
operational network can bring practical interferences into prominence. Bo
between the RNP inputs and the actual network, RNO enables to export the pla
operational values of the cells, and also an automatically computed experience
the RNP tool to set a stronger gap requirement between frequencies (ARFCNs) o

4 NPA:
- Access to QoS counters and indicators
The BSS event counters managed by an Alcatel system are loaded, through OM
NPA statistical database. From these unitary counters, NPA tool computes, con
QoS indicators.
NPA provides powerful data historical management and a quick data access. In
efficiency, A9156 RNO gets the QoS data via a request mechanism based
indicators, using the specific query language called TQL

To query the NPA database, RNO needs to create a dedicated client applicat
database management system does not manage remote client applications,
called NPA daemon, is installed on the NPA server. Since RNO V5, the NPA Daem
OMC that have MPM application installed on
 RNO ACTIVITY MODEL

The major operation during the night consists in updating the RNO database from the operat
network as given by each OMC-R. The operational logical configuration import is automatica
during the night, via a daily batch mode process.
For this operation, each declared OMC-R must be reachable via its Internet address and mus
time in a predefined directory the required PRC files from its local database.
The diagram below illustrates the mechanism implemented within A9156 RNO to manage OM
configuration data retrieval and processing:

OMC-R / A9156 RNO communication proce

The PRC file extractor is launched at T0 (T0 was customised by the OMC-R adm
with the RNO administrator and taking into account his own operating constrai
At end of PRC file generation

on each OMC-R, a tag file "done" is generated that means that PRC files can be
server.
At T2 (T2 was previously defined by the RNO administrator taking into account
filegeneration), RNO launches a sequential procedure to transfer files and to im
database, one OMC-R after the other.

SOFTWARE AND NETWORK ARCHITECTU

1. Global view
As shown above, the A9156 RNO server is connected via a LAN on one hand to the NPA machin
other hand to each OMC-R client(s). The communication protocol is TCP/IP.

Data exchanges with the OMC-Rs are done via an assisted file transfer mechanism, using the F

Data exchanges with the NPA server are based on a specific protocol.

Exchanges with the Radio Network Planning tool are manual. Imports in the RNO system are m
previously installed on a RNO workstation, and outputs from RNO for the network planning too
a RNO workstation too.

A permanent link between A9156 RNO and NPA is mandatory during connections of RNO client
and for batch activities.
A permanent link with the managed OMC-R servers is highly recommended. It is mandatory du
update the RNO database with operational information retrieved from OMC-R databases, and it
to download tuning session files onto target OMC-R servers.

2. RNO database

RNO database is an Oracle database, with a traditional client-server architecture through a TCP
but it is accessed through an object-oriented layer called CPO that eases software developmen
model definition with respect to the Managed Object Classes of telecommunication application
also offers facilities to store and retrieve geographical objects such as strongest server cell co

3. NPA request driver

A9156 RNO / NPA communication process ove
 3. NPA request driver
A9156 RNO / NPA communication process ove
QoS data are retrieved thanks to a TQL request driver installed on NPA UNIX server, called RN
daemon, or simply NPA daemon.
The A9156 RNO server receives requests from client workstations, manages the request queu
sequencing thanks to a dedicated Windows Server 2003 service, that in turn establishes a com
a NPA demon.
The NPA daemon process that runs on the NPA Unix server is in charge to:
1. Format RNO requests into TQL queries and send them to the NPA database server,
2. Send the result to the A9156 RNO server.

Whereas QoS requests were processed one at a time in previous versions of RNO, a new com
protocol is now implemented since RNO V3 to take benefit from the multi-processor architectu
server and from its ability to execute parallel queries.
Consequently, several NPA daemons can run simultaneously on the NPA server, each one hav
communication stream with the RNO server. Each NPA daemon requires an API licence token
Metrica database server. Since RNO V5, there is a limitation in case of the RNO is connected to
application installed on the OMC, only one NPA daemons is launched.
The diagram below illustrates the communication process implemented within A9156 RNO to m
access.

A9156 RNO / NPA communication process overview (figure):

AND OTHER INVOLVED TOOLS

9.

naged by RNO V5 is extracted from one to several

ich is object-oriented since it describes managed

ion retrieval is limited to one database export each

etwork operational state to correct a misbehaviour,

eries of operations to apply on network elements.
s into files downloaded to concerned OMC-Rs. The
 ich is object-oriented since it describes managed

ion retrieval is limited to one database export each

etwork operational state to correct a misbehaviour,

eries of operations to apply on network elements.
s into files downloaded to concerned OMC-Rs. The
the command file(s) onto the operational network
wser to easily display and analyse the content of the
me information given in the tuning session file are
uning advice operations and tuning operations to

to the download of command files in a predefined

provides the cell design (planned cells, adjacencies

n in a format called POLO interface

erational network, for many possible reasons. This

to operational cells the planned frequencies.
es on a theoretical wave propagation model, the
into prominence. Both of these discrepancies
nables to export the planned cell design based on
ly computed experience matrix that enables inside
requencies (ARFCNs) of two neighbouring cells.

are loaded, through OMC-R services, into a unique

NPA tool computes, consolidates and stores basic

a quick data access. In order to benefit from NPA

est mechanism based on these NPA basic QoS

edicated client application. Because the statistical

ote client applications, the dedicated application,
RNO V5, the NPA Daemon shall be installed on the
TY MODEL

O database from the operational state of the

ration import is automatically launched,

s Internet address and must produce in due

l database.
n A9156 RNO to manage OMC-R

mmunication process:
mised by the OMC-R administrator in accordance
own operating constraints).

ns that PRC files can be downloaded by the RNO

ator taking into account a sufficient delay for PRC

o transfer files and to import them into the RNO

ORK ARCHITECTURE

l view
one hand to the NPA machine, and on the
TCP/IP.

sfer mechanism, using the FTP protocol.

ol.

ts in the RNO system are made from files

or the network planning tool are written on

g connections of RNO client applications

mended. It is mandatory during the night to

m OMC-R databases, and it is necessary

tabase

r architecture through a TCP/IP protocol,

eases software development and data
ecommunication applications. This layer
h as strongest server cell contours.

est driver
cation process overview
est driver
cation process overview
NPA UNIX server, called RNO-NPA

manages the request queuing and

hat in turn establishes a communication with

harge to:
A database server,

ersions of RNO, a new communication

e multi-processor architecture of the NPA

e NPA server, each one having its own

quires an API licence token from the
e of the RNO is connected to the MPM
ed.
ented within A9156 RNO to manage data
 1. A9156-RNO Functional Description

2. A9156-RNO Possible Configurations

3. A9156-RNO THIRD PARTY SOFTWARE

the complete list of external software used to run A9156-RNO:

3.1 Windows 2003 Server and Windows XP Professional

3.2 Oracle Standard One Edition
3.3 Office 2000 and Office XP
3.4 Internet Explorer and Acrobat Reader
3.5 ARCserve
3.6 Ilog Views
3.7 CPO
3.8 FlexLM
3.9 Java Runtime Engine:
A9156-RNO includes a Java application called RNO tuning browser that will be ab
of RNO tuning session output and run under PC and Unix Environment. To run it,
Environment is necessary.

3.10 Metrica:
Part of RNO software (called NPA daemon) is dedicated to NPA interface and runs
It is interfaced with Metrica NPR 3.2 through specific libraries and is compiled to r
Later, in B9 release, Metrica NPR 3.3 will be used.

3.11 Citrix Metaframe:

This software can be used optionally with A9156 RNO B9 Release for remote acce
application.
 4 A9156-RNO GENERIC CONFIGURATIONS
4.1 RNO COnfigurations
4.2 RNO PC minimum characteristics
4.3 External devices for RNO configurations

4.4 LAN connections

By default, a LAN connection is mandatory for communication between RNO server and
and OMC-R, RNO and A1985-NPA, or with terminal CITRIX server solution. Nevertheles
following points need to be added:
- OMC-R / RNO connection can be done through WAN with a minimum rate of 64 kbits/s
- A remote access to the RNO Client application is only supported via terminal server sol
based on Citrix software. A 128 kbit/s connection is mandatory between ICA client and C
server.
- LAN connection between RNO and A9185-NPA, and between RNO Client and RNO Se
absolutely mandatory to get expected performance.
Ethernet switch and connection kit can be proposed to customers that have no infrastruc
all OMC-R configurations through Ethernet interface: servers, workstations and printers.
To ensure proper communications operation and performance between units a "true" IP E
should be used (not a common hub unit) with:
- 24(or more) RJ45 ports with 10/100 Mbps base Tx auto detection flow rate,
- IP multicast switching full duplex capacities
- 1000 MAC address (or more), plug and play installation facilities.

4.5 Terminal Services (Citrix) server option

4.5 Terminal Services (Citrix) server option

4.6 Mapping of RNO “Third party software” on PC configurations

onal Description

e Configurations

ARTY SOFTWARE
-RNO:

ng browser that will be able to display content

ix Environment. To run it, Java Runtime

to NPA interface and runs on NPA machine.

raries and is compiled to run under Solaris.

9 Release for remote access to RNO client

CONFIGURATIONS
n between RNO server and clients, RNO
server solution. Nevertheless, the

a minimum rate of 64 kbits/s.

orted via terminal server solution
ry between ICA client and Citrix

en RNO Client and RNO Server is

mers that have no infrastructure to connect

, workstations and printers.
e between units a "true" IP Ethernet switch

ection flow rate,

lities.
urations
 RLE counters
REQUEST

GPRS causes
GSM/GPRS invalid causes

ATTEMPT

SUCCESS

SDCCH phase counters

 SDCCH phase counters

SDCCH connection

Normal release TCH assignment phase

2.3 Typical call failures

TCH assignment - counters

REQUEST

ATTEMPT Preparation Failure

SUCCESS Execution Failure

Radio access
failure
 Radio access
failure

BSS problem

2.3 Typical call failures

TCH phase - counters

TCH connection

NSS abnormal release Normal release Outgoing HO success

 User BSS

-1-
Radio
Link
Establi

-2-
SDCCH
Phase Call CSSR
Establish Call
Establish

-3-
TCH
Assign. CSR

-4-
Alerting
Connect
DROP

DROP
nters

GSM valid causes

ATTEMPT Preparation Failure

Execution Failure
Congestion

BSS problem

Radio access failure

BSS problem

counters
 counters

connection

ment phase SDCCH drop

Drop radio

Drop BSS

Drop HO

Preparation Failure

ution Failure Congestion

BSS problem
 BSS problem

Call drop

Call drop preemption

Call drop radio

Call drop radio

Call drop BSS TC

Call drop HO BSS internal

 Tuning session / Tuning Browser
A tuning session is an ordered list of tuning operations. Tuning oper
network modification requests. For example, one tuning operation c
a change of parameter for one cell of the network.

The A9156 RNO Tuning Browser is designed to:

Browse the contents of a tuning session file(enables you to read tun
Extract the corresponding compressed file
Export the extraction to specified OMC-Rs.(and export their tuning p
R.)

Tuning Session Files

Tuning session files are generated in the A9156 RNO Tuning Manage
exported to the A9156 RNO Tuning Browser.
The tuning session exports contain three files:

A .tun file, containing all the tuning information for all the OMC-Rs
A .tgz file, containing the compressed tuning parameter files for a sp
OMC-R
A .rno file, which points to a specific OMC-R.

A9156 RNO Tuning Browser Proce

/alcatel/var/share/AFTR/RNO/xxxx.TUN
 /alcatel/var/share/AFTR/RNO/xxxx.TUN

/alcatel/var/share/AFTR/ACIE/ACIE_Nlimport_Dirxx

Frequency table description

Blue -> BCCH frequency of the cell. You cannot deselect this frequency.
Green -> Selected frequency to monitor.
Red -> BCCH of a neighboring cell. We do not recommend you to select this freq
dedicated to the study of possible interference with non-neighbors.
Frequency table description

Blue -> BCCH frequency of the cell. You cannot deselect this frequency.
Green -> Selected frequency to monitor.
Red -> BCCH of a neighboring cell. We do not recommend you to select this freq
dedicated to the study of possible interference with non-neighbors.
Grey -> Frequency declared unusable by the Administrator.
White -> Not selected.

The overall process to manage MAFA jobs in RNO is the following:

While tuning frequencies in RNO (FrequencyTuning operation), an optimize
statistics on tuned frequencies to assess for instance the risk of interference
such statistics are not available, it is possible to ask the network to force the
measurements for some extra-frequencies thanks to MAFA jobs. In RNO, a
the optimizer to prepare a MafaTuning operation when such statistics are no
A MafaTuning operation applies on a cell. It consists of declaring up to 21 fr
BCCH frequency of the cell is implicitly selected and is included in the set o
frequencies are the ones of a predefined range spectrum (i.e. set of frequen
RnoAdmin.ini file. A pre-filtering is also performed on the BCCH frequency o
BCCH frequency is managed by default by the OMC-R but RNO should
BCCH frequency into the PRC files.
Once QoS statistics are available, the frequency tuning process can go
MAFA jobs enable to study the behavior of some frequencies in a give
frequency/neighborhood environment. It is therefore not suggested to
cell and at the same time changing its BCCH frequency or its HO relati
Tuning Browser
erations. Tuning operations are
ne tuning operation can concern
rk.

ables you to read tuning session files)

export their tuning parameters to an OMC-

sion Files
RNO Tuning Manager and

for all the OMC-Rs

arameter files for a specific

Browser Process
 this frequency.

nd you to select this frequency as MAFA is

on-neighbors.
 this frequency.

nd you to select this frequency as MAFA is

on-neighbors.
trator.

the following:
operation), an optimizer may need some QoS
the risk of interference on a frequency. When
he network to force the mobiles to report
MAFA jobs. In RNO, a warning message advises
n such statistics are not available.
of declaring up to 21 frequencies to monitor (the
s included in the set of 21 frequencies). Allowed
rum (i.e. set of frequencies) defined in the
the BCCH frequency of neighboring cells. The
MC-R but RNO should however export this

uning process can go on.

frequencies in a given
ore not suggested to perform MAFA jobs on a
uency or its HO relationships.
 Extractor (B9)
The automatically Extract mode can be performed using Extractor icon from spreadsheet window

The manually Extract mode carries out, in the .csv files format, the spreadsheet generated with the selections
made.

To use the Extract mode, you must ensure that the following login name and
password have been created by the Administrator:
Login Name: ExtractUser
Password: ExtractUser

Recommendations
1. Before running the Extract mode, ensure that:

You are outside the normal RNO working cycle.

No RNO application is running.
No import operation is running.
No Batch job is running.

you need to create:

1- A directory named RnoExtract which must contain three directories named as follows:
Logs
Input
Output
you need to create:

1- A directory named RnoExtract which must contain three directories named as follows:
Logs
Input
Output

D:\Program Files\Alcatel\RnoExtract.

2- A file named Extract.ini. You must place this file at the following address: <RnoHome>\RnoClient\Resources

3- A file named <Input>.des. You must place this file at the following
address: D:\Program Files\Alcatel\RNOExtract\Input (This file describes your extraction operation)

4. To avoid overflow memory, it is recommended to extract, at a time, no more

than 140 Logical parameters or 40 Design parameters or 60 QoS indicators.

Run an Extraction:

1. In the Extract.ini file, type the output path for the extraction.

2. In the <Input>.des file, type a line of description for each type of object you want to extract the information from.
Run an Extraction:

1. In the Extract.ini file, type the output path for the extraction.

2. In the <Input>.des file, type a line of description for each type of object you want to extract the information from.

3. Open a Command Promptwindow, and set the current directory to:

D:\> cd D:\Program Files\Alcatel\RnoClient\Programs\Client

4. Type the following command for extractor:

Rno.exe -extract -file "D:\Program Files\Alcatel\RNOExtract\Input" -workingzone <myWorkingZone> [-

outputdirectory <outputDirPath>]
window

d with the selections

RnoClient\Resources

peration)

ract the information from.

ract the information from.

kingZone> [-
Projet RNP Lannion Date: Fevrier 2005 pdlm

Projet MAP/CARTO: Lahost1 / Lahost2 omc1Tunis / omc2Tunis

B8_Projet_RNP_Lannion
Ci: 121, 122,
Map: Reunion.MIF Tunisie.MIF
V:/ImportExport/Maps/*.MIF Lahost1; Lahost2
Remarques: Coordonee de La Reunion: Coordo de Tunis
de 1 a 30 =>Project_Tunisiana_B7
PRC=> Conf Radio: PRC every night PRComc1tunis
PRComc2tunis
Cell Class: CityMarket
Metro
Data QOS: YES QOS rep Mono_Idle NO

Exemples Interessants sur la Maquette de Lannion:

Backup du 25/02/2005 TLO Vz omcr19/S221 (BSC) Day du 01/07/2004 au 30/12/2004

Hour du 19/12/2004 au 30/12/2004

QOS: omcr19/S221/Cell 3509 du 15/12/04 au 30/12/04

=> Alc_mono_Ana_QoS=96% a 2.8% le 20/12/04 V4CDR
A quel heure le 20/12/04? => meme report par hour

QOS Reliability/Sampling Ci = 3509 Call_Drop_Rate per Hour from 20/12/04 to 23/12/04

Bsc 221 call_drop_rate du 17au30/12/04 par hour

DIAG: Cell 3669 le 23/12/04 => call_drop_rate=4.49% V4CDR => DTC suspected (WZ High)
Cell 3509 le 17/12/04 => call_drop_rate=95.9% V4CDR => HO PB

QuickDiag: Ci 13221 OK Neighbour Frequencies Check

Ci 13222 NOK
Ci 13223 NOK

Events / Historic: Prendre les BSCs de Lannion (90 jours d'historic)

MAP: Projet: B8_Projet_RNP_Lannion / LannionB8_V01

cel_lanB8.cof => Plusieurs cartes Tunis/Portugal
to import raster, see dedicated section below

RMS: Cell Date

Omcr19->s221-> 3501 20/12/04
3671, 3674, 3675 20/12/04
3669, 3670 20/12/04
Comparer 3671 et 3670 20/12/04
Voir TRX?

LCS: Omcr37->s222-> 15,16,17 le 12/07/04

 Omcr37->s222-> 16a34 04/07/04 au 22/07/04
Voir aussi Log Param Omcr Parameter, Lat;
Long…

Distributed Indicators 1-Select all cells for the Bsc s221

2-QOS rep->Alc_Multi_call_dist_BSS: 20/12/2004 /Day
3-Cell xxxx et xxxx => Grand nb=>grde importance/BSC
4-Cell xxx ->Alc_Mono_call_dist_BSS: du xxx/2003 au 26/06/2003 /Day

Adjacencies xxx Matrix_Inc_success Nb

GPRS QoS

Administrator / Tricks

EXCEL: gerer les .cof Open cell.cof ou FreeField.csv, puis => Data>Text to Columns> choisir comma delem

Process RNO NPA sur NPA: Bien se mettre dans le repertoire : /metrica/RNO et lancer
sur RNO: dans >comtrol Panel> Admintool>Services stop puis star
Attendre 1mn
Rem: creation de process fils sur NPA quand on demarre des c

Display of QoS indicators reliability

QoS indicators are results of aggregation of raw information. Optimization is usuall

indicators aggregated per day. It sometimes happens in the BSS that part of the raw
missing, due to maintenance actions on the network elements for instance. It is thu
important for the optimizer to know the relevancy of a QoS indicator, especially to d
value is relevant or not. To address such request, the “Display of QoS indicators re
been developed. It highlights a non relevant value in QoS spreadsheet and QoS rep
optimizer to decide whether or not to take into account some QoS indicators.

Reliability Indicators :

What you have to explain to the customers:

1- PM are impacted by 3 things :
- BSS operator commands BSS or BSS PB (RESET BOARD etc..)
- PM not uploaded in OMCR/NPA or loss due to overload (or bug)
- metrica Impact: due to the structure of metrica, the quantity of data not stored (so
data really loss – Some data we got in OMCR are imported in NPA but rejected and
data for an other group of counters are loss or not valid – due to the structure in tab
the good data will be loss also !!
2- Normalisation (grouping and extrapolations)
Reliable (not in italic ) means 100 % reliable

If there are 15 TRX for which data are OK for 16 TRX on one cell ==> data are cons
the cell.
- metrica Impact: due to the structure of metrica, the quantity of data not stored (so
data really loss – Some data we got in OMCR are imported in NPA but rejected and
data for an other group of counters are loss or not valid – due to the structure in tab
the good data will be loss also !!
2- Normalisation (grouping and extrapolations)
Reliable (not in italic ) means 100 % reliable

If there are 15 TRX for which data are OK for 16 TRX on one cell ==> data are cons
the cell.

Data for 1 TRX NOK (not reliable) => data for QoS on Network are « not reliable »

Reliability indicators themself are not visible on RNO (May on platform only for the
(Tests)

It exists stored reliability indicators (NPA) And computed (RNO)

A RELIABILITY INDICATOR IS LINKED TO WHAT ??

HW groups (groups of boards, equipment) have been defined in BSS
Groups of tables linked to counters have beendefined in NPA (eg : RTCH, HO etc.)
For each cross (between a group of card and a group of counters /table ) a reliabilit
created and stored on NPA.
All are created even there is no need for that (eg: SDCCH Resources and HO counte
because there is no SDCCH HO) . By the way, we are ready for evolution !

HOW THE VALUE OF RELIABILITY INDICATOR IS DETERMINED ?

For one reliability indicator, we compute :

in french !! :

And the result must be 100% to have the result OK (indicators reliable)
The “expected number of object” is based on the configuration file imported from
this file the number of TRX, the number of cells and the number of GPRS cells)
Computed :
Some pour tous les objets mesurés du temps réelement mesuré
You understand that a stored reliability indicator is linked to a counter and not a ind
nombre dobjets attendus X temps demandé
When we link a reliability indic to an indicator, we take care to the formulae of this i
account all the reliability values of all the counters used in the formulae by comput
And the result must be 100% to have the result OK (indicators reliable)

COMPUTED RELIABILITY INDICATORS

In RNO, we make the same think for RNO indicators (there are about 3000 RNO ind
“recursive” (indicators computed from indicators)) – We take into account the relia
used in the formulae – this is why we can have such formulae for “computed reliab
RS1 G1 + RS1 G2 + RS6 G8 / 3 (RS : stored reliability indic , G : group of « boards
account all the reliability values of all the counters used in the formulae by comput
And the result must be 100% to have the result OK (indicators reliable)

COMPUTED RELIABILITY INDICATORS

In RNO, we make the same think for RNO indicators (there are about 3000 RNO ind
“recursive” (indicators computed from indicators)) – We take into account the relia
used in the formulae – this is why we can have such formulae for “computed reliab
RS1 G1 + RS1 G2 + RS6 G8 / 3 (RS : stored reliability indic , G : group of « boards

Given all the averages and computations performed in spatial and time views on di
reliability at 100 % has good sense .After all these operations, other values have no
But of course, this is not because a reliability is NOK for an indicator than the value
(Remember the Mud of Soisson !! hum sorry, remember Data for 1 TRX not reliable
are not reliable )

Be Careful : For each new Tool chain software delivery, with modification in the for
indicators, the reliability indicators are created again automatically and their names
automatically by the Access Database. That means there is no history and no poss
documentation about these formulae to the customer.
Anyway, reliability indicators are not visible on tool chain … (almost !!…).

Flexible Indicators :

NPA Flexible indicator continues to exist but it is not more possible to import them in RNO
In fact the import of flex indic (QoSIndicators.csv file) used in B7 was only useful to make
these indicators in RNO but has no impact on the functionality.
In Import/export window of the RNO Administration Tool , an icon “QoS Customer indica
Flex import” icon allows the user not to import Flex indic from NPA but import or export
with the new indicator editor in B8 in order to make easier the exchanges of these indicat
(different RNO server).
In fact the import of flex indic (QoSIndicators.csv file) used in B7 was only useful to make
these indicators in RNO but has no impact on the functionality.
In Import/export window of the RNO Administration Tool , an icon “QoS Customer indica
Flex import” icon allows the user not to import Flex indic from NPA but import or export
with the new indicator editor in B8 in order to make easier the exchanges of these indicat
(different RNO server).

Indicator formulae

Indicator thresholds
Thresholds allow A9156 RNO to raise an alarm on an object. The type of alarm depends on the ind
depend on the importance of the object. A9156 RNO is using three different alarm
sensitivity levels:

High,
Medium,
Low.

For each sensitivity level, there are three alarm thresholds:

Red,
Orange,
Yellow.

Use relative date in Cell Zone (B9)

 omcr19 omcr37

3500…3670 7,8,9,…84
Portugal.MIF Portugal.MIF

BSC: s221 BSC: s222

=> Coordo Portugal => Coordo Portugal
PRC_omcr19 PRC_omcr37

CityMarket no
Metro
YES: S221 Data LCS

2004 au 30/12/2004
2004 au 30/12/2004

12/04 V4CDR

20/12/04 to 23/12/04

9% V4CDR => DTC suspected (WZ High)

9% V4CDR => HO PB

quencies Check

Problem
AV Path + Bad Cov
AV Path
Bad Cov
Consecutive Frame Eras

MPS_deviation_longitude_avrg
portance/BSC
xx/2003 au 26/06/2003 /Day

Creer une Thematic layer xxx/xx/xx per day

Data>Text to Columns> choisir comma delemited

dans le repertoire : /metrica/RNO et lancer RNO-NPAd depuis ce repertoire

Panel> Admintool>Services stop puis start du RNO-Request-Service

de process fils sur NPA quand on demarre des clients (plusieurs RNO-NPAd)

formation. Optimization is usually done on

ns in the BSS that part of the raw information is
rk elements for instance. It is thus very
of a QoS indicator, especially to decide if the
he “Display of QoS indicators reliability” has
n QoS spreadsheet and QoS reports allowing the
ount some QoS indicators.

BOARD etc..)
erload (or bug)
he quantity of data not stored (so, loss) is greater than the
mported in NPA but rejected and not stored because other
valid – due to the structure in tables by group of counters,

RX on one cell ==> data are considered as not reliable for

he quantity of data not stored (so, loss) is greater than the
mported in NPA but rejected and not stored because other
valid – due to the structure in tables by group of counters,

RX on one cell ==> data are considered as not reliable for

n Network are « not reliable »

NO (May on platform only for the needs of developers

puted (RNO)

?
en defined in BSS
ned in NPA (eg : RTCH, HO etc.)
up of counters /table ) a reliability indicator has been

DCCH Resources and HO counters are not necessary

re ready for evolution !

DETERMINED ?

(indicators reliable)
configuration file imported from OMCR (in B8 , we add in
d the number of GPRS cells)

esurés du temps réelement mesuré

linked to a counter andnot a indicator.
temps demandé
ake care to the formulae of this indicator and we take into
used in the formulae by computing an average.
(indicators reliable)

s (there are about 3000 RNO indicators, and all are

– We take into account the reliability indic of all indicators
h formulae for “computed reliability indicator” :
ility indic , G : group of « boards » (HW side) )
 used in the formulae by computing an average.
(indicators reliable)

s (there are about 3000 RNO indicators, and all are

– We take into account the reliability indic of all indicators
h formulae for “computed reliability indicator” :
ility indic , G : group of « boards » (HW side) )

d in spatial and time views on different objects, only a

operations, other values have no sense !
OK for an indicator than the value cannot be used
mber Data for 1 TRX not reliable => QoS data for Network

very, with modification in the formulae of reliability

in automatically and their names also are given
there is no history and no possibility to provide updated
mer.
l chain … (almost !!…).

ore possible to import them in RNO.

sed in B7 was only useful to make available the properties of
tionality.
ol , an icon “QoS Customer indicator” taking place of “NPA
dic from NPA but import or export indicator created by the user
sier the exchanges of these indicators between regions
 sed in B7 was only useful to make available the properties of
tionality.
ol , an icon “QoS Customer indicator” taking place of “NPA
dic from NPA but import or export indicator created by the user
sier the exchanges of these indicators between regions

ator formulae

or thresholds
 The type of alarm depends on the indicator value. Alarms also
g three different alarm

ate in Cell Zone (B9)

 Define Free Fields
You can define up to 10 Free Fields to be used in the A9156 RNO Tool for
addresses, postal codes, maintenance center codes, or any administrative data
associated with network operations.

To define these Free Fields:

1. Create a comma or semi-colon delimited file from your database information.

Line 1 is the header for the file. Begin that line with FREE FIELD in capital letters t
description for the file.

Line 2 contains the name of the free fields. Begin that line with CELL_ID in capital
names of your free fields (up to ten). If A9156 RNO is installed in LAC/CI mode, th
LAC_ID.

2. Give a .csv extension to the file.

3. Place the file in the FreeFields directory.

4. Import the file in the RNO Tool, using the Import/Export Manager
e Fields
156 RNO Tool for
any administrative data

ur database information.

E FIELD in capital letters then, if necessary, type a

ne with CELL_ID in capital letters, then type the

stalled in LAC/CI mode, then begin the line by

ort Manager
 2. Operating Modes
1-Create quickly a Working Zone containing some cells of your choice
Select cells or BSC (use shift and CTRL keys) right click , create Working Zone (User guide 11

2-Get OMC-R parameter names

Menu Option -> Settings --> General --> select “RNO and OMCR Name when different”

3-Strike out objects not managed in “Non RNO objects”

Bearer Channel, BTS, GPU, DTC, LapD_MFS, Abis, N7, MS, PVC
From the Network objects window, select Other Objects.
If it is The first time, select from the list the object to be displayed
See “notes” of “Network objects windows” Slide

4- For one cell, give planned and operational values or name of Serving, Target, Frequency an
Select one Cell, select “Design” tab in “Properties & functions view” , select “HSn” and “Freq

Drag and Drop it on this icon then this one located the spreadsheet itself.

It is possible to switch from operational to planned values inside the spreadsheet itself.

5- Create a cell zone filtered on 4 criteria:

design: Cell class
WZ: from 3 different WZs
QoS: Call drop rate:date--->
Absolute date without specific weekday
Absolute date: 23/02/2007 – Specific weekday: None
Date formula in the CellZone Editor Panel after validating: 23/02/2007

Absolute date with a specific weekday

Absolute date: 30/04/2007 (Monday) – Specific weekday: Last tuesday
Date formula date in the CellZone Editor Panel after validating:

Relative date without specific weekday

Relative date: - 10 Days – Specific weekday: None
Formula date in the CellZone Editor Panel after validating: Today – 10 Day

Relative date with a specific weekday

Relative date: - 2 Months – Specific weekday: Last Thursday
Formula date in the CellZone Editor Panel after validating: Last Thu (Today – 2 Month)

6- Rx_Lev_min for all target neighboring cells of one cell?

=> Use the icon in the spreadsheet

7- Sort all Indoor cells of the Global zone

=> Indoor cell type new from B7

8- Using the HTML Help - RNO table,

Give the description of:
call_drop_radio_rate
NPA Ref name=?
RNO Ref name=?
RNO formula=?
MC736 Counter definition =?
MC250
=> Click on one counter
7- Sort all Indoor cells of the Global zone
=> Indoor cell type new from B7

8- Using the HTML Help - RNO table,

Give the description of:
call_drop_radio_rate
NPA Ref name=?
RNO Ref name=?
RNO formula=?
MC736 Counter definition =?
MC250
=> Click on one counter
LASER_GSM_BSC_available_rate

3. Parameters and Design analysis

In the objects window:
1- Property of the Working Zone? (check the Free Field information)
Right Click then Property
Parameters and Functions window
2- Create a “Best Of” lists:
=>Right click then Crreate
List 1: several Logical Parameters

List 2: several Rules

List 3: several QoS reports

List 4: several QoS indicators

Modify a list by adding some new objects in

3- When can we use this button What is the result ?

=> History; new date window appear.
Spreadsheet window
4- How many BTS a cell can be split over ?
=> 2

5- On how many TRXs is Packet traffic allowed (TRX PrefMark = 0 )?

=> Select all TRXs and parameter TRX_PREF_MARK
=> Ascending sort on Column in spreadsheet
=> Select all with “0”
=> Propagate selection
=> The number of TRX is displayed

6- How many cells are using their ‘SWAP’ radio configuration?

=> Idem with “Is Nominal”
4- How many BTS a cell can be split over ?
=> 2

5- On how many TRXs is Packet traffic allowed (TRX PrefMark = 0 )?

=> Select all TRXs and parameter TRX_PREF_MARK
=> Ascending sort on Column in spreadsheet
=> Select all with “0”
=> Propagate selection
=> The number of TRX is displayed

6- How many cells are using their ‘SWAP’ radio configuration?

=> Idem with “Is Nominal”

7- Are there MAFA cells?

=> Design

8- Run Neighbor frequencies check Quick diagnosis

9- Check the A_LEV_HO value for 1 cell. Push the history button.

Check again (what happens?)

10- Check the HO_MARGIN value

=> Adj
11- Check the AMR_FR_12200bps value
=> BSC
12- Check Events on all cells over the last week
=> User
13- Choose a cell having some Events and identify the detailed modifications

14- Choose one modified parameter in the Events details (=> like BS_TX_PWR ) and Drag and
spreadsheet
=> Use History

3. Quality of Service analysis

1- Display in the spreadsheet the Evolution of several Counters then Indicators during one we

2- Display in the spreadsheet the Evolution of a Counter then an Indicator during one week fo

3- Generate a Report Showing the Evolution of an indicator for 10 cells over one month.
Explain how to read it

4- Display in the spreadsheet the Evolution of several Counters then Indicators during one we

5- Test the reverse adjacencies selection for a report in the spreadsheet (one indicator over a

6- Why is MAFA interesting?

2- Display in the spreadsheet the Evolution of a Counter then an Indicator during one week fo

3- Generate a Report Showing the Evolution of an indicator for 10 cells over one month.
Explain how to read it

4- Display in the spreadsheet the Evolution of several Counters then Indicators during one we

5- Test the reverse adjacencies selection for a report in the spreadsheet (one indicator over a

6- Why is MAFA interesting?

7- Give all steps to activate the Radio Measurement Statistics

8- Open the properties of a cell and give its RMS parameters

9- Display the Alc_Mono_QoS_Trx report with the daily indicators of a TRX Zone?

10-Produce a multi object evolution report CDR for some cells

11- Compare the CSSR of one cell in a classic report (day average) with BH results for the sam

12- Are there some external cells declared in your Network?

13-Test the possibility to abort a report production

14-Extract the 10 cells with the biggest variation for HO cause “better cell”

15-a Drag and drop in spreadsheet all Events over one month for all cells of a BSS

15-b Choose a cell having some Events and Drag and drop a Mono-Object Evolution report o
over the same month

15-c Check with Legend that the Events are the same than in the spreadsheet

16- Display the distribution of the TCH traffic among all cells of a BSS for one day

17-a Find quickly a cell having some RMS indicators

17-b For this cell, display all QoS Distribution reports and analyze each view
Is it a good cell?

18a- Display for aWorking Zone on one day the Alc_Warning_Threshold_QoS report Which is

18b- Display the values of the indicators of the previous report in the spreadsheet for another
from QoS reports)

19- Could you find some examples of reliability “NOK”? What does that mean? Do it in sprea

20- Create a daily Event Batch Job

21- Give the definition of:

RMS_RadioLinkCounter_avg
MC02i and Call Setup Success Rate
21- Give the definition of:
RMS_RadioLinkCounter_avg
MC02i and Call Setup Success Rate

RTCH_UNSUCCESS_RATE =

(RTCH_assign_request - DR_Out_Success - RTCH_assign_succe

+RTCH_HO_unsuccess ) / (RTCH_assign_request - DR_Out_Succ
RTCH_HO_request)
g Modes
oice
Working Zone (User guide 11.2)

Name when different”

rving, Target, Frequency and HSN

w” , select “HSn” and “Frequencies” design parameters.

d the spreadsheet itself.

he spreadsheet itself.

007

day

– 10 Day

u (Today – 2 Month)
Design analysis

n)

)?
)?

odifications

BS_TX_PWR ) and Drag and drop it over the last month in the

vice analysis
en Indicators during one week for a specific cell

ndicator during one week for 5 cells

cells over one month.

en Indicators during one week for a specific cell

sheet (one indicator over a period)

ndicator during one week for 5 cells

cells over one month.

en Indicators during one week for a specific cell

sheet (one indicator over a period)

of a TRX Zone?

) with BH results for the same period.

tter cell”

all cells of a BSS

o-Object Evolution report on this cell with daily indicators

preadsheet

BSS for one day

each view

shold_QoS report Which is the worst cell?

he spreadsheet for another specific cell (use propagation

s that mean? Do it in spreadsheet and in QoS Report.

TCH_assign_success
uest - DR_Out_Success -
 GSM B9 RNO QOS indicator IncType
SDCCH Congestion and Assignment Failures
%SDCCH_Assign_Cong SDCCH_Assign_Cong_Rate GSM
%SDCCH_Assign_Fail SDCCH_Assign_Fail_Rate GSM
Call Establishment
% SDCCH drop SDCCH_Drop_Rate GSM
% RTCH_Assign_Cong RTCH_Assign_Cong_Rate GSM
%RTCH Assign Fail RTCH_Assign_Fail_Rate GSM
%Call Setup success Call_setup_success_rate GSM
Call Drop
% RTCH drop RTCH_Drop_Rate GSM
% Call Drop Call_Drop_Rate GSM
% Drop Radio Call_Drop_Radio_Rate GSM
% Drop HO Call_Drop_HO_Rate GSM
% Drop BSS Call_Drop_BSS_Rate GSM
Intra BSC incoming
handovers
Request HO_Inc_BSC_Request GSM
% Cong HO_Inc_BSC_Cong_Rate GSM
% Success HO_Inc_BSC_Success_Rate GSM
Intra BSC outgoing
handovers
Request HO_Out_BSC_Request GSM
%ROC HO_Out_BSC_ROC_Rate GSM
% Success HO_Out_BSC_Efficiency_Rate GSM
Inter BSC incoming
handovers
Request HO_Inc_MSC_Request GSM
% Cong HO_Inc_MSC_Cong_Rate GSM
% Success HO_Inc_MSC_Success_Rate GSM
Inter BSC outgoing
handovers
Request HO_Out_MSC_Request GSM
% Success HO_Out_MSC_efficiency_Rate GSM
% ROC (return to old
channel) HO_Out_MSC_ROC_Rate GSM
Hand Over
% CHO_DL_Level CHO_DL_level_rate GSM
% CHO_UL_Level CHO_UL_level_rate GSM
% CHO_DL_Quality CHO_DL_quality_rate GSM
% CHO_UL_ Quality CHO_UL_quality_rate GSM
% CHO_Better_Cell CHO_Better_Cell_rate GSM
Traffic
SDCCH traffic in Erlang SDCCH_Erlang_total GSM
RTCH traffic in Erlang RTCH_Erlang_Total GSM
RTCH mean holding time RTCH_duration_avg GSM
SDCCH mean holding time SDCCH_duration_avg GSM
GPRS/Edge B9 RNO QOS indicator IncType
DL TBF Establishment
Request GPRS_DL_TBF_Request GPRS
% allocated GPRS_DL_TBF_estab_allocated_rate GPRS
Only if significant degradation of
previous indicator
% Congestion GPRS_DL_TBF_estab_fail_cong_rate GPRS
% Ater Cong GPRS_DL_TBF_estab_fail_ater_cong_rate GPRS
% CPU Cong GPRS_DL_TBF_estab_fail_cpu_cong_rate GPRS
% DSP Cong GPRS_DL_TBF_estab_fail_dsp_cong_rate GPRS
% Success GPRS_DL_TBF_success_rate GPRS
%Realloc Success GPRS_DL_TBF_realloc_success_rate GPRS
Only if significant degradation of
previous indicator
DL_TBF_Realloc_T1_success_
rate GPRS_DL_TBF_realloc_T1_success_rate GPRS
DL_TBF_Realloc_T2_success_
rate GPRS_DL_TBF_realloc_T2_success_rate GPRS
DL_TBF_Realloc_T3_success_
rate GPRS_DL_TBF_realloc_T3_success_rate GPRS
DL_TBF_Realloc_T4_success_
rate GPRS_DL_TBF_realloc_T4_success_rate GPRS
UL TBF Establishment
Request GPRS_UL_TBF_request GPRS
% allocated GPRS_UL_TBF_estab_allocated_rate GPRS
Only if significant degradation of
previous indicator
% Congestion GPRS_UL_TBF_estab_fail_cong_rate GPRS
% Ater Cong GPRS_UL_TBF_estab_fail_ater_cong_rate GPRS
% CPU Cong GPRS_UL_TBF_estab_fail_cpu_cong_rate GPRS
% DSP Cong GPRS_UL_TBF_estab_fail_dsp_cong_rate GPRS
% Success GPRS_UL_TBF_success_rate GPRS
%Realloc Success GPRS_UL_TBF_realloc_success_rate GPRS
Only if significant degradation of
previous indicator
UL_TBF_Realloc_T1_success_
rate GPRS_UL_TBF_realloc_T1_success_rate GPRS
UL_TBF_Realloc_T2_success_
rate GPRS_UL_TBF_realloc_T2_success_rate GPRS
UL_TBF_Realloc_T3_success_
rate GPRS_UL_TBF_realloc_T3_success_rate GPRS
UL_TBF_Realloc_T4_success_
rate GPRS_UL_TBF_realloc_T4_success_rate GPRS
DL data transfert
Success GPRS_DL_TBF_success GPRS
% Normal Release GPRS_DL_TBF_normal_release_rate GPRS
% Acc release GPRS_DL_TBF_acceptable_release_rate GPRS
% drop TBF DL GPRS_DL_TBF_drop_rate GPRS
UL data transfert
Success GPRS_DL_TBF_success GPRS
% Normal Release GPRS_UL_TBF_normal_release_rate GPRS
% Acc release GPRS_UL_TBF_acceptable_release_rate GPRS
% drop TBF UL GPRS_UL_TBF_drop_rate GPRS
DL Coding Scheme Usage
%CS1 GPRS_DL_useful_RLC_blocks_CS1_ack_ratio GPRS
%CS2 GPRS_DL_useful_RLC_blocks_CS2_ack_ratio GPRS
%CS3 GPRS_DL_useful_RLC_blocks_CS3_ack_ratio GPRS
%CS4 GPRS_DL_useful_RLC_blocks_CS4_ack_ratio GPRS
%MCS1 GPRS_DL_useful_RLC_blocks_MCS1_ack_ratioGPRS
%MCS2 GPRS_DL_useful_RLC_blocks_MCS2_ack_ratioGPRS
%MCS3 GPRS_DL_useful_RLC_blocks_MCS3_ack_ratioGPRS
%MCS4 GPRS_DL_useful_RLC_blocks_MCS4_ack_ratioGPRS
%MCS5 GPRS_DL_useful_RLC_blocks_MCS5_ack_ratioGPRS
%MCS6 GPRS_DL_useful_RLC_blocks_MCS6_ack_ratioGPRS
%MCS7 GPRS_DL_useful_RLC_blocks_MCS7_ack_ratioGPRS
%MCS8 GPRS_DL_useful_RLC_blocks_MCS8_ack_ratioGPRS
%MCS9 GPRS_DL_useful_RLC_blocks_MCS9_ack_ratioGPRS
UL Coding Scheme Usage
%CS1 GPRS_UL_useful_RLC_blocks_CS1_ack_ratio GPRS
%CS2 GPRS_UL_useful_RLC_blocks_CS2_ack_ratio GPRS
%CS3 GPRS_UL_useful_RLC_blocks_CS3_ack_ratio GPRS
%CS4 GPRS_UL_useful_RLC_blocks_CS4_ack_ratio GPRS
The following indicators are
indicative (the B9 results can
not be compared to B8)
%MCS1 GPRS_UL_useful_RLC_blocks_MCS1_ack_ratioGPRS
%MCS2 GPRS_UL_useful_RLC_blocks_MCS2_ack_ratioGPRS
%MCS3 GPRS_UL_useful_RLC_blocks_MCS3_ack_ratioGPRS
%MCS4 GPRS_UL_useful_RLC_blocks_MCS4_ack_ratioGPRS
%MCS5 (not in B8) GPRS_UL_useful_RLC_blocks_MCS5_ack_ratioGPRS
%MCS6 (not in B8) GPRS_UL_useful_RLC_blocks_MCS6_ack_ratioGPRS
%MCS7 (not in B8) GPRS_UL_useful_RLC_blocks_MCS7_ack_ratioGPRS
%MCS8 (not in B8) GPRS_UL_useful_RLC_blocks_MCS8_ack_ratioGPRS
%MCS9 (not in B8) GPRS_UL_useful_RLC_blocks_MCS9_ack_ratioGPRS
DL RLC trafific
CSx Useful Bytes GPRS_DL_useful_bytes_CSx_ack GPRS
MCSx Useful Bytes GPRS_DL_useful_bytes_MCSx_ack GPRS
GPRS_DL_RLC_bytes_PDTCH_CSx_retransmi
CSx Retrans ssing_ack GPRS
GPRS_DL_RLC_bytes_PDTCH_MCSx_retrans
MCSx retrans missing_ack GPRS
GPRS_DL_RLC_bytes_PDTCH_CSx_retransmi
%CSx Retrans ssion_ratio GPRS
GPRS_DL_RLC_bytes_PDTCH_MCSx_retrans_
%MCSx retrans ack_ratio GPRS
UL RLC trafic
CSx Useful Bytes GPRS_UL_useful_bytes_CSx_ack GPRS
MCSx Useful Bytes GPRS_UL_useful_bytes_MCSx_ack GPRS
GPRS_UL_RLC_bytes_PDTCH_CSx_retransmi
CSx Retrans ssing_ack GPRS
GPRS_UL_RLC_bytes_PDTCH_MCSx_retrans
MCSx retrans missing_ack GPRS
GPRS_UL_RLC_bytes_CSx_retransmissing_a
%CSx Retrans ck_ratio
GPRS_UL_RLC_bytes_PDTCH_MCSx_retrans_
%MCSx retrans ack_rate
Radio Preemption
Soft Preemption GPRS_PDCH_soft_Preempted GPRS
PDCH Allocation
Alloc SPDCH GPRS_MAX_PDCH_Dyn_avg GPRS
Ater congestion
Ater Cong Perc GPRS_GPU_Ater_cong_percent GPRS
GPU DSP Cong Perc GPRS_GPU_DSP_cong_percent GPRS
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente

M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente

M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente

M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente

M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente

M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente

M Nom RNO modifié en MR1Ed4 mais formule identique à release précédente
M Nom RNO modifié en MR1Ed4
M Nom RNO modifié en MR1Ed4
 Maquette NPA / RNO Plan de Salle 3
Tableau

Bureau
192.1.5.24

USER4-RNO
PC Win2000
192.1.5.23 192.1.5.22

USER3-RNO USER2-RNO
PC Win2000 PC Win2000
Hub Intranet

Salle 334 – NPA / RNO

Maquette Server OMCR / RNO / La

Plan de Salle 338

192.1.5.67
Laser: LASERSERVER
PC Win2000
Parallèle
 192.1.5.67
Laser: LASERSERVER
PC Win2000

Printer Lexmark 192.1.5.20

Optra SC1275 Color RNO Server: ALCATEL
PC Win2000 Server

Arcserve

192.1.5.33
Lahost2 OMCr Server
Hub

192.1.5.1
Lahost1 OMCr Server

Salle 338 – Serveur OMCR / RNO / NPA

NO Plan de Salle 334

Porte

192.1.5.60

Hub
Snpala01
NPA Server
192.1.5.54
192.1.5.21
Printer HP
LaserJet 5M

ER2-RNO USER1-RNO
Win2000 PC Win2000
Salle 338

– NPA / RNO

MCR / RNO / Laser

alle 338

Porte
CATEL
ver RNO Server B7

Bureau
 472965020.xls
CONFIGURATION MAQUETTES NPA/RNO Lannion
Date: 25/02/05

N° de Salle 334
Nom de la salle Salle RNO-NPA

Type de l'équipement Nom Equipement Adresse IP Ouverture Windows 2000 Pro Open RNO V4 Caractéristiques ma
User Name Password Domain Login Password nbre CPUs
PC NT Compaq AP400 USER1-RNO 192.1.5.21 rno rno ALCATEL user1 rno 1 à 400 Mhz
Administrator admin USER1_RNO Administrator admin
PC NT Compaq AP400 USER2-RNO 192.1.5.22 rno rno ALCATEL user2 rno 1 à 400 Mhz
Administrator admin USER2_RNO Administrator admin
PC NT Compaq AP400 USER3-RNO 192.1.5.23 rno rno ALCATEL user3 rno 1 à 400 Mhz
Administrator admin USER3_RNO Administrator admin
PC NT Compaq AP400 USER4-RNO 192.1.5.24 rno rno ALCATEL user4 rno 1 à 400 Mhz
Administrator admin USER4_RNO Administrator admin

Type de l'équipement Nom Equipement Adresse IP Ouverture session Open NPA - Dico Caractéristiques ma
User Name Password Domain Login Password nbre CPUs
Station SUN Serveur NPA : snpala01 192.1.5.60 metrica metrica lancer npr & metrica metrica
Licence metrica: npa.lic hostid: 80b14d78 dba dba
/metrica/flexlm/licences su - //root vision
fin le 15-aug-2005

PC RNO Exceed Broadcast Client NPA1: user1-rno 192.1.5.21 metrica metrica npr & metrica metrica
PC RNO Exceed Broadcast Client NPA2: user2-rno 192.1.5.22 metrica metrica npr & metrica metrica
PC RNO Exceed Broadcast Client NPA3: user3-rno 192.1.5.23 metrica metrica npr & metrica metrica
PC RNO Exceed Broadcast Client NPA4: user4-rno 192.1.5.24 metrica metrica npr & metrica metrica

Printer LaserJet 5M lprn31 En panne 192.1.5.54

Remarques:
Bande de sauvegarde NPA chez LAB
Ref: NPA - 25 Fev 2005 - Full Backup B8 - Data TLO Vélizy (01/07/03 to 03/01/05)

le responsable du développement RNO B9 à Timisoara: Ovidiu SOLOMON <[email protected]>.

 472965020.xls

Caractéristiques matérielles
RAM Disk version logicielle
256 Mo 8 Go (C+D) Win 2000 Pro

256 Mo 8 Go (C+D) Win 2000 Pro

256 Mo 8 Go (C+D) Win 2000 Pro

256 Mo 8 Go (C+D) Win 2000 Pro

Caractéristiques matérielles
RAM Disk version logicielle
N° de Salle 338
Nom de la salle Salle Serveur

Type de l'équipement Nom Equipement Version Adresse IP Ouverture Windows 2000 Serveur APPLICATION Caractéristiques ma
User Name Password Domain Login Password nbre CPUs
PC W2000 Compaq SERVER_RNO RNO 4.0 - B8 192.1.5.20 Administrator admin ALCATEL no no 2 x 2.8GHz
Serveur RNO RNOSAV21P
MAC Adress:
000E7FB00AA4

Printer // RNO Server Lexmark SC1275 color Parallèle

OMC1 SUN E450 lahost1 B8 192.1.5.1 axadmin root root axadmin

OMC2 SUN E450 lahost2 B7 192.1.5.33 axadmin omc3 root vision

lahmi1 lahmi1 192.1.5.2 axadmin omc3

Type de l'équipement Nom Equipement Version Adresse IP Ouverture Windows 2000 Pro Laser Client Caractéristiques ma
User Name Password Domain Login Password nbre CPUs
PC W2000 Compaq LASERSERVER B7 192.1.5.67 Laser
Serveur LASER
Laser Admin
Login Password

Printer HP 4050N lprn11 192.1.5.51 a été déplacée de salle

Caractéristiques matérielles
RAM Disk version logicielle
1.5 Go 4 x 18.6 Go Win 2000 Server
(3 + 1spare)

Caractéristiques matérielles
RAM Disk version logicielle
Support de cours Pour toutes opérations site,
se conformer aux méthodes
UNIX
ATTENTION
Ce document est non validé par les services d'ALCATEL
Il est un aide mémoire incomplet et ne peut en aucun cas servir de méthode.
Il est obligatoire, pour chaque utilisateur de l'OMC-R, d'avoir à disposition, la documentation officielle d'Alcatel.

Chapitre 1 : INSTALL OMC-R B7.2 Page 2

1 - Dé-locker un compte Page 2
2 - Changer le HOSTID (temporaire) Page 2
3 - Changer le HOSTID (permanent) Page 2
4 - Changer les licences OSI et X25 Page 2
5 - Changer la licence HPOV Page 2
6 - Changer la licence VERITAS (VxFS) pour OMC-R E4500 Page 2
7 - Contrôler la licence ALCATEL Page 3
8 - X25 Templates d'un BSC Page 3
9 - Déclarer un OMC-R dans un autre OMC-R Page 3
10 - Changer le MCC et MNC de l'OMC-R Page 3
11 - Modification de la CRONTAB Page 3
12 - Modification du Password Page 3
13 - Contrôle des scripts de démarrage du CD1 de commissioning Page 3

Chapitre 2 : ADMINISTRATION de l'OMC-R Page 4

1 - Locker ou dé-locker l'adresse IP d'un OMC-R Page 4
2 - Backup et Restore de l'OMC-R Page 4
3 - Supprimer les spools d'une imprimante Page 4
4 - Gérér la connexion d'une imprimante Page 4
5 - Enlever le banner de l'imprimante Page 4
6 - Déclarer le lecteur de disquette sous CMA Page 5
7 - Déclarer un lecteur de tape Page 5
8 - Dé-locker une X-Station Page 5
9 - Re-créer une X-Station Page 5
10 - Changer le mot de passe d'un user Page 5
11 - Mise à jour du mot de passe d'un user Page 5
12 - Supression de l'expiration d'un mot de passe d'un user Page 6
13 - Rechercher un mot dans tous les fichiers d'un répertoir Page 6
14 - Fonctionement et configuration de l'OST 36110 pour les liaisons X25 Page 6
15 - Consultation des fichiers "LOG" Page 7
16 - Consultation du fonctionnement de "DSMUSM" Page 8
17 - Ré-installation d'un Soft de "SWLIST" Page 8
18 - Configurer les autorisations réseau Page 8
19 - Contrôler les process utilisés par un loggin Page 8
20 - Contrôler le déroulement d'un script pendant son exécution Page 8
21 - Arret propre du server bloqué sous Solaris Page 9
22 - Controler les fichiers d'installation des OMC & HMI Page 9
23 - Gérer un terminal NCD sur un OMC-R en B8 Page 9

Draft - Edition 06/08/03 Documentation interne FST Page 429/535

Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes
24 - Re-créer un HMI sur un OMC-R Page 9

Chapitre 1 : INSTALL OMC-R

ok 1 - Dé-locker un compte
root
cd /alcatel/omc3/bin
./unlockaccount affiche les loggins lockés
./unlockaccount "nom_du_loggin_locké" pour dé-locker le compte

ok 2 - Changer le HOSTID (temporaire)

root
/usr/sbin/hid2 "hostid" pour changer le HOSTID temporairement--> ne marche plus après un reboot.

ok 3 - Changer le HOSTID (permanent)

root
vi /etc/rc1.d/SO1MOUNTFSYS
chercher la ligne sous les " # " et inserrer sous VI :
/usr/sbin/hid2 "hostid" > /dev/null le HOSTID est changer en dur dans la machine.

ok 4 - Changer les licences OSI et X25

root
- cd /etc/rc2.d
./s90run_osinet stop pour arréter la licence OSI.
./s87x25net stop pour arréter la licence X25.
- cd /etc/opt/licenses
./lit saisir les licences OSI et X25 (voir methode doc Commissioning)
- cd /etc/rc2.d
./s87x25net start pour redémarrer la licence X25.
./s90run_osinet start pour redémarrer la licence OSI.
ps -ef | grep x25 pour vérifier que la licence X25 fonctionne.
ps -ef | grep osi pour vérifier que la licence OSI fonctionne.
- init 6 cette commande n'est pas obligatoire. A faire si besoin.
- vi /etc/opt/licenses/licenses_combined pour controler les deux licences et les modifier.

ok 5 - Changer la licence HPOV

root
cd /var/netls/
vi nodelock fichier contenant la licence HPOV.
saisir la licence HPOV permanante (première ligne de la licence).

ok 6 - Changer la licence VERITAS (VxFS) pour OMC-R E4500

root
vxfsserial -c (vxlicense -c sur certains cas) pour changer directment la licence VERITAS
saisir la licence. Un message avec OK s'affiche si cette licence correspond au Hostid.
cd /etc/vx/elm
more 80 pour contrôler le fichier "80", de la licence.
Draft - Edition 06/08/03 Documentation interne FST Page 430/535
Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes
(SOLUVY02 - 80bd1419 = "3569 7601 3192 2130 3185 8096 41 41 7" sans espaces)
vxfsserial -p (vxlicense -p sur certains cas) pour contrôler l'installation de la licence.

ok 7 - Contrôler la licence ALCATEL

root
cd /alcatel/var/share/netconf
more oflcf.in contrôler la clée et le hostid en fin de fichier.

ok 8 - X25 Templates d'un BSC

axadmin
- cd /etc/opt/SUNWconn/x25/config
more link_config_0000.cfg fichier contenant les X25 Templates.
Contrôler dans "Section Link" : "Device = /dev/hih0"
"Local adress = ' X25_OMC-R_adress' "
"Description = 'nom_du_script_lancé_par_X25TOOL' "
- pad "X25_BSC_adress" pour vérifier la connection
- x25tool& pour vérifier que le script est bien lancé.

ok 9 - Déclarer un OMC-R dans un autre OMC-R

root
chmod 777 hosts à faire si besoin avant de faire le VI.
vi /etc/hosts ajouter l'adresse IP et le Hostname
vi / .rhosts ajouter l'adresse IP et le Hostname

ok 10 - Changer le MCC et MNC de l'OMC-R

axadmin
cd /alcatel/omc3/script
./opcode.sh affiche le script qui permet de changer MCC et MNC.
/alcatel/omc3/rn/im/conf/parm.cfg fichier contenant le MCC & MNC

ok 11 - Modification de la CRONTAB
root
crontab -l pour afficher le contenu de la CRONTAB.
crontab -l > "modif" pour placer le contenu de la CRONTAB dans un fichier "modif".
vi "modif" pour modifier, ajouter, suprimer ….
crontab modif pour recopier le de "modif" vers CRONTAB.
crontab -l pour afficher le contenu de la CRONTAB.

ok 12 - Modification du Password
root
passwd root saisir deux fois le nouveau mot de passe (ex : vision)

13 - Contrôle des scripts de démarrage du CD1 de commissioning

root
cd /cdrom/cdrom0/s0/.install_config/ permet de regarder les configs et les scripts lancés
more rules lors de la détection du hradware par le CD1 de commissioning
Draft - Edition 06/08/03 Documentation interne FST Page 431/535
Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes

Chapitre 2 : ADMINISTRATION de l'OMC-R

ok 1 - Locker ou dé-locker l'adresse IP d'un OMC-R
root
ifconfig hme down lock l'adresse IP de l'OMC-R
ifconfig hme up dé-lock l'adresse IP de l'OMC-R

ok 2 - Backup et Restore de l'OMC-R

axadmin
cd /alcatel/omc3/osm/script
vi MF-improved_backup_OMC.sh --> "set -x" inserrer en 1ière ligne "set -x" pour afficher le déroulement du script
/ KEEPLOG --> yes modifier le paramètre "KEEPLOG" pour garder les log dans /alcatel/var/maintenance/log/endlog…

./MF-improved_backup_OMC.sh pour effectuer un backup complet de l'OMC-R.

./MF-improved_restore_OMC.sh pour effectuer le restore complet sur l'OMC-R.

ok 3 - Supprimer les spools d'une imprimante

root
lpstat -t pour afficher le status de l'imprimante.
cd /usr/ucb
./lpc se met en status LPC.
? affiche la liste des commandes.
status affiche les spools en attente.
clean all efface tous les spools.
quit quitte LPC.

4 - Gérér la connexion d'une imprimante

root
ping 139.54.78.100 teste de connexion à l'imprimante.
S'il n'y a pas des connexion, vérifier le cable IP, imprimer la page de test "Self Test/Configuration" et vérifier
l'adresse IP de l'imprimante et celle DEF. GATEWAY (server). S'ils ne sont pas correctement
renseignés, il faut les changer sur l'imprimante. (voir doc Alcatel).
telnet 139.54.78.100 connexion vers l'imprimante.
? pour afficher les paramètres possibles de l'imprimante.
/ pour afficher les options déjà paramètrées sur l'imprimante.
"nom du paramètre":"valeur du paramètre" pour donner une nouvelle valeur au paramètre.
cd /etc/rc2.d
./S80lpstop pour arrêter le process de gestion des imprimantes.
./S80lpstart pour redémarrer le process de gestion des imprimantes.

5 - Enlever le banner de l'imprimante

Draft - Edition 06/08/03 Documentation interne FST Page 432/535

Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes

6 - Déclarer le lecteur de disquette sous CMA

cma_sys pwd = omc3
cd /alcatel/var/home/cma_sys/INSTALL
./cma_inst.sh - d pour lancer le script d'installation des devices.
1 (add new device) option à lancer, et suivre les instructions.
ex : hmivzy01, 139.54.78.111, cma_sys, floppy, /dev/fd0
Démarrer "CMA admin" de l'Icon Box pour contrôler.

7 - Déclarer un lecteur de tape

axadmin
mt -f /dev/rmt/0n rew pour déclarer le lecteur /dev/rmt/0 avec l'option rewind.

8 - Dé-locker une X-Station

axadmin
cd /alcatel/var/share/nterm
ls pour afficher la liste des stations connectées.
rm .omc3_session_"hostname"_"login"_… supprimer le fichier pour dé-locker la station.

9 - Re-créer une X-Station

axadmin
cd /alcatel/omc3/osm/conf
more wslist.cfg affiche les X-stations et les Workstations crées avec OSM
En cas de problème, supprimer la ligne de déclaration de la station avec VI, dans ce fichier "wslist.cfg", puis
il faut la recréer avec la procédure standard, avec OSM, dans l'icon box.
En cas de problème, pour la déclaration de la X-station, faire :
ps -ef | grep osmd taper cette commande pour afficher le process OSMD
kill -9 "numéro de process" pour detruire ce process. Il redémarre automatiquement.
Recommencer l'opération au début. La création doit se passer maintenant sans problèmes.

10 - Changer le mot de passe d'un user

root
passwd "nom du user"
Entrer le nouveau mot de passe deux fois de suite

11 - Mise à jour du mot de passe d'un user

root
Si compte AXADMIN est locker, aller sur ROOT et faire : " /alcatel/omc3/bin/unlockaccount axadmin "
Du loggin ROOT, aller sur le loggin AXADMIN
axadmin
/alcatel/omc3/inconbox/script/run_iconbox
Lancer OSM à partir de la fenêtre Iconbox. Loggin axadmin et password omc3 fonctionnent quand même
Draft - Edition 06/08/03 Documentation interne FST Page 433/535
Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes
Administration --> User Management --> Rest User Password
Choisir "axadmin" et entrer le password 2 fois puis cliquer sur [Change Password]
Sync HTTP server/SEC pour mise à jour base sec

12 - Supression de l'expiration d'un mot de passe d'un user

Si le password du compte axadmin expire dans un nombre x de jours, on peut modifier x
root
vi /alcatel/var/share/nterm/shadow
Transformer la ligne :
"axadmin:9XldblnuCef2.:11863::90:8::12051: " ===> "axadmin:9XldblnuCef2.:11863::990:8::12051: "

13 - Rechercher un mot dans tous les fichiers d'un répertoir

root
find / -type f -exec grep "xxxxx" {} \; -print recherche à l'inérieur de tous les fichiers existant, à partir
de la racine, le mot xxxxx, et affiche le chemin et son fichier.

14 - Fonctionement et configuration de l'OST 36110 pour les liaisons X25

A - Fonctionement
Les ports, où arrivent les cables X25 venant des BSC, et où partent les cables vers les OMC-R, sont
paramétrés dans le menu CFG (configuration) et associés à une "table de routage" dans le menu RTG (routage).
Cette "table de routage" est elle-même associée à une "table d'adresse X25" dans RTG.

Table N°1 : Table N°2 : Table N°3 :

Port 010X Table de routage Table d'adresses X25
contient : contient : contient :
- MNEmonic X - MNEmonic Y -2 premiers caractères
- tous les paramètres - PR de l'adresse X25
X25 - numéro de Port - MNEmonic Y

[ menu CFG ] [ menu RTG ] [ menu RTG ]

[ affichage avec : [ affichage avec : "aot" ] [ affichage avec : "dis xx" ]
"dis <n°port>" ]
avec "MNEmonic" : nom de l'équipement connecté à l'OST sur le Port 010X.
L' "Identifiant" commun entre la Table N°1 et la Table N°2 est le Port "010X" (numéro de Port).
L' "Identifiant" commun entre la Table N°2 et la Table N°3 est le "MNEmonic" . Il n'est pas obligatoirement
identique à celui de la Table N°1, mais c'est préférable pour un meilleur suivi du routage.

B - Configuration
axadmin
pad 0.0009
"connecting" et "connected" apparaissent : taper le password
fstv2 password (en fançais) ou "hello" password en anglais
help ou hlp pour afficher les menus disponibles
Draft - Edition 06/08/03 Documentation interne FST Page 434/535
Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes
CFG pour arriver au menu "CFG" (Config.) et au prompt "CFG>"
help ou hlp pour afficher les commandes disponibles sur le menu
hlp "nom de la commande" pour afficher le rôle et la syntaxe de la commande
dis 010x pour afficher les paramètres du port "0x" sur la FEP 01

B - Configuration (suite)
Pour modifier un des paramètre qui configure le port, prendre les 3 lettres en MAJUSCULE dans ce nom
de paramètre et appliquer la syntaxe : <3 lettres> <n°port>,<nouvelle valeur>
MNE 0107,velizy03 donne au paramètre "MNEmonic" du port 0107, la valeur "velizy03"
CN2 0103,N donne au paramètre "Counter N2" du port 0103, la valeur "Non"
CLK 0104,8 donne au paramètre "CLoK" du port 0104, la valeur "8=64kbits/s"
Pour dupliquer tous les paramètres qui configure un port, vers un autre port, utiliser la commande "DUP".
hlp DUP pour afficher le rôle et la syntaxe de la commande DUP
syntaxe = DUP <n°port destination>, <n°port source>
DUP 0103,0107 pour dupliquer les param. Du port 0107 sur le port 0103
rst pour enregistrer les changement réalisés dans le menu "CFG"
off pour sortir du menu "CFG"
RTG pour arriver au menu "RTG" (routage) et au prompt "RTG>"
help ou hlp pour afficher les commandes disponibles sur le menu
hlp "nom de la cmmande" pour afficher le rôle et la syntaxe de la commande
aot affiche la Table N°2 contenant : <MNEmonic> PR,<n°port>
dis xx affiche la Table N°3 contenant : <2 car. Adres. x25> <MNEmonic>
Les Tables N°1, N°2, N°3 sont liés par le MNEmonic.
hlp aot affiche les syntaxes de visualisation, de suppression, de création
de la commande
aot <MNEmonic>,del supprime dans les Tables N°2 et N°3 les occurences concernant
le MNEmonic
aot <MNEmonic>,PR,<n°port> pour créer dans la Table N°2, le lien entre le MNEmonic et le Port
aot affiche la Table N°2 contenant : <MNEmonic> PR,<n°port>
hlp out affiche les syntaxes de création de la commande
out <2 car. Adres. X25>,<MNEmonic> pour créer dans la Table N°3, le lien entre les 2 premiers caractères
de l'adresse X25 de l'équipent et le MNEmonic
dis xx affiche la Table N°3 contenant : <2 car. Adres. x25> <MNEmonic>
rst pour enregistrer les changement réalisés dans le menu "RTG"
off pour sortir du menu "RTG"
MPM pour arriver au menu "MPM" (xxxxx) et au prompt "MPM>"
rst 010x pour enregistrer définitivement tous les changements réalisés
dans tous les menu, sur la FEP 01, Port 03
rst 01 pour enregistrer définitivement tous les changements réalisés
dans tous les menu, sur la FEP 01, tous les Ports
off pour sortir du menu "MPM"
off pour quitter les menu de l'OST 36110 et revenir au prompt axadmin

15 - Consultation des fichiers "LOG"

Draft - Edition 06/08/03 Documentation interne FST Page 435/535
Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes
axadmin
cd /alcatel/var/maintenance/log
Consulter les fichiers "rnusm.log.axadmin"; "bssusm.log.axadmin".

16 - Consultation du fonctionnement de "DSMUSM"

axadmin
cd /alcatel/omc3/dsm/bin/solaris
./dsmparser /alcatel/omc3/dsm/conf/dsm.cfg pour afficher les erreurs éventuelles dans DSMUSM.

17 - Ré-installation d'un Soft de "SWLIST"

root
swlist pour afficher la liste des "Softs" installer
swremove <nom-colonne-de-gauche>,r=<nom-colonne-du-milieu> pour supprimer le soft mal installer
avec <nom-colonne-de-gauche> = nom du soft
avec <nom-colonne-du-milieu> = version du soft
cd /install/data
vi OMC3_instPrd.lst pour enlever toutes les lignes concernant le soft et sa version
cd /install/script et mettre le CD dans le lecteur CDROM
./install_mng -s pour installer de nouveau le soft (avec un contrôle des autres softs)

18 - Configurer les autorisations réseau

root
cd /etc/rc3.d
vi S98addroute avec S98addroute = nom aléatoire significatif
inserrer la ligne : route add net 155.132.191.0 139.54.78.254 1 pour un réseau 155… qui vient sur 139…
avec : net : identifiant réseau
155.132.191.0 : réseau distant qui vient sur mon réseau
139.54.78.254 : mon réseau
1 : obligatoire
route add host 155.132.191.46 139.54.78.254 1 pour un seul PC qui vient sur 139…
avec : host : identifiant PC
155.132.191.46 : PC distant qui vient sur mon réseau
139.54.78.254 : mon réseau
1 : obligatoire
chmod +x S98addroute pour rendre exécutable le fichier S98addroute
./S98addroute pour exécuter le fichier S98addroute
netstat -r pour contrôler le résultat du routage autorisé

19 - Contrôler les process utilisés par un loggin

axadmin
Draft - Edition 06/08/03 Documentation interne FST Page 436/535
Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes
ps -U axadmin pour contrôler les process lancer et fonctionnant pour axadmin

20 - Contrôler le déroulement d'un script pendant son exécution

root
vi "nom du script" + O ouverture du fichier avec vi et insserer une ligne au tout début
set -x option d'exécution qui affiche toutes les lignes du script et le résultat

21 - Arret propre du server bloqué sous Solaris

root
uadmin 2 0 arrête proprement le server bloqué, et le ramène au prompte OK

22 - Controler les fichiers d'installation des OMC & HMI

root
cd /var/sadm/system/logs
more begin.log affiche les infos fournis lors de l'install du CD1 (CPU, RAM, taille…)

23 - Gérer un terminal NCD sur un OMC-R en B8

root
Installer le package " NCDWARE " à partir du CD2 B7.2
cd /install/script
./install_xterm -l affiche la liste des NCD terminaux existant
./install_xterm -a ncd_name,type_ncd,adresse_IP,MAC_adresse,netmask,Master_OMC_IP_adresse
ex : ./install_xterm -a ncdvzy01,Explora700,139.54.78.141,00:00:A7:04:8C:66,255.255.255.0,139.54.78.220
cd /tftpboot/usr/lib/X11/ncd/configs
ls -ltr affiche les fichiers ".stp"
vi 8B364E8F.stp
remplacer dans " exec-startup-commands = { " ncdclock -analog " } "
par : " exec-startup-commands = { "login 139.54.78.220" } "

./install_xterm -d ncd_name supprime le NCD terminal

24 - Re-créer un HMI sur un OMC-R

root sur OMC-R
vi /alcatel/omc3/osm/conf/wslist.cfg enlever la ligne concernant le HMI
vi /etc/hosts + vi .rhosts enlever la ligne concernant le HMI
root sur HMI
vi /etc/hosts + vi .rhosts enlever la ligne concernant l'OMC-R
vi /alcatel/omc3/osm/conf/wslist.cfg enlever la ligne concernant l'OMC-R
vi /etc/inet/hosts enlever la ligne concernant l'OMC-R
vi /alcatel/omc3/dsm/conf/host.cfg enlever tout le paragraphe concernant l'OMC-R ( voir les "{" et "}" )
axadmin sur OMC-R
sur OSM, re-déclarer le HMI

24 - Gérer un terminal NCD manuellement

Draft - Edition 06/08/03 Documentation interne FST Page 437/535
Rédacteur : S.Pellerin
Support de cours Pour toutes opérations site,
se conformer aux méthodes
axadmin sur OMC-R
déclarer le NCD terminal sur OSM
cd /tftpboot/usr/lib/X11/ncd/configs
vi 8B364E8F.stp (dernier fichier ".stp" créé)
NCD terminal sur NCD en local
UP /tftpboot/usr/lib/X11/ncd/configs/8B364E8F <IP NCD> <IP OMC-R> <IP Gateway> <net mask>
ex : UP /tftpboot/usr/lib/X11/ncd/configs/8B364E8F 139.54.78.141 139.54.78.220 139.54.78.220 255.255.255.0

Draft - Edition 06/08/03 Documentation interne FST Page 438/535

Rédacteur : S.Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes

ioning)

Draft - Edition 06/08/03 Documentation interne FST Page 439/535

Rédacteur : S.Pellerin
 the NPA System overview

GSM
1. Performance Management binary files are transferred from the OMC-R to NPA
2. Binary files are parsed to ASCII files. The output files from the Parser are sav
3. The Patolo script further concatenates these files by raw type, time and BSC
files are moved to the load directory.
4. The Loader computes hourly cell indicators. It loads raw counters and hourly
into the performance database.
5. The Scheduler normalizes the period to 24 hours: Daily, Weekly, Monthly indi
aggregated per object (Cell, Area, BSS, Network).The Archiver removes the old
storage duration).
6. Data are available for reports and graphs.

GPRS
1. GPRS ASCII files are transferred from the MFS to NPA.
2. GPRS ASCII files are parsed (suspected flag checking).
4. GPRS files are loaded (per period) into the performance database.
5. The Scheduler normalizes the period to 24 hours. The Archiver removes the
5. The Scheduler normalizes the period to 24 hours: Daily, Weekly, Monthly indi
aggregated per object (Cell, Area, BSS, Network).The Archiver removes the old
storage duration).
6. Data are available for reports and graphs.

GPRS
1. GPRS ASCII files are transferred from the MFS to NPA.
2. GPRS ASCII files are parsed (suspected flag checking).
4. GPRS files are loaded (per period) into the performance database.
5. The Scheduler normalizes the period to 24 hours. The Archiver removes the
6. Data are available for reports and graph.

Laser Interface
1. Laser alarm ASCII files are transferred from the Laser Interface to NPA.
4. ASCII files are loaded (per period) into the performance database.
5. The Scheduler normalizes the period to 24 hours. The Archiver removes the
6. Data are available for reports and graph.

TSL / TQL Tcl / TK

TQL is the language used to work on the Data Bases : Requests/Reports (e.g:
col1 = fafa”)
TSL is the Metrica proprietary Language to create Human Machine interfaces (W

The PM Browser introduced in B8 doesn’t use TSL / TQL but Tcl / TK which
source)

Locate the main NPA directories Glob

em overview

d from the OMC-R to NPA.

from the Parser are saved in the Patolo directory.
raw type, time and BSC number. The concatenated

raw counters and hourly cell indicators (per period)

ily, Weekly, Monthly indicators are computed and

rchiver removes the old data (following the tuned

A.
g).
nce database.
e Archiver removes the old data.
ily, Weekly, Monthly indicators are computed and
rchiver removes the old data (following the tuned

A.
g).
nce database.
e Archiver removes the old data.

r Interface to NPA.
ce database.
e Archiver removes the old data.

Requests/Reports (e.g: “select * from yoyo where

an Machine interfaces (Windows)

QL but Tcl / TK which is stable and free (open

rectories Global view

Change the ref logical parmameters>> Rxlev_access_min ?

More then 400 logical parameters

NPA is data base for all counter and indicators, based on metrica DB --> DICO

RNO usage:
- QoS
- parameters
- tuning session
- cartographie (MAP)

RNO training : 5 days

RNO advanced: 3 days

Diagnosis?

External interface: to check all differents interfaces between ...

?

etrica DB --> DICO

n ...
BCIQ BCIQ Definition

BCIQ1 Taux de coupure SDCCH

Taux d'échec de prises

BCIQ2
SDCCH

BCIQ3 Taux de coupure TCH

BCIQ4 Taux d'échec de prises TCH

Taux d'echec de HO intra

BCIQ5
BSC entrant
Taux d'échec de HO inter
BCIQ6
BSC entrant
Taux d'echec de HO intra
BCIQ7
BSC sortant
 Taux d'échec de HO inter
BCIQ8
BSC sortant

BCIQ9 Trafic en erlang

Taux de coupure DQT

BCIQ10
système

BCIQ11 Taux de coupure DQT radio

BCIQ12 Taux d'échecs DQT

B7 BCIQ FORMULA

(MC138 + MC07 + MC137)

/ (MC01+MC02+MC10)

(MC390 - (MC01 + MC02 + MC10) + MC04)

/ (MC04 + MC390)

(MC736 + MC621 + MC739 + MC14c)

/ (MC718+MC717a + MC717b)

(MC15a + MC15B + MC703 - MC718 - MC717a -

MC717b
+ MC812 + MC41b + MC541a + MC551 + MC561)
/ (MC15a + MC15B + MC703 + MC812 + MC541a
+ MC551 + MC561 + MC41b)

(MC830 - MC652) / MC830

(MC820 - MC642) / MC820

(MC655a - MC656) / MC655a

(MC645a - MC646) / MC645a

MC380a + MC380b

(MC739 + MC14c) / (MC718)

(MC736 + MC621) / (MC718)

1-
(1-(MC138+MC137)/(MC1+MC2))*(1-
((MC812+MC746B+MC14B)
/(MC703+MC812))
RNO Indicator used in B7 release

SDCCH_DROP_RATE

SDCCH_ASSIGN_UNSUCCESS_RATE

RTCH_DROP_RATE

RTCH_UNSUCCESS_RATE

HO_INC_BSC_UNSUCCESS_RATE

HO_INC_MSC_UNSUCCESS_RATE

HO_OUT_BSC_UNSUCCESS_RATE
HO_OUT_MSC_UNSUCCESS_RATE

RTCH_Erlang_total

NONE - It should be computed via excel using the

following formula :
call_drop_BSS / RTCH_assign_success

NONE - It should be computed via excel using the

following formula :
(call_drop_radio + call_drop_HO)
/ RTCH_assign_success

NONE - It should be computed via excel using the

following formula :
1 - call_setup_success_NPA_rate
B8 BCIQ FORMULA

Same As B7 one

Same As B7 one

Same As B7 one

( MC140a - (MC142e +MC142f ) MC703 + MC812 -

MC718 - MC717a - MC717b
+ MC15a + MC15B + MC41b + MC541a + MC551
+ MC561)
/ ( MC140a - (MC142e +MC142f ) MC703 + MC812
+MC15a + MC15B +MC541a + MC551 + MC561 +
MC41b)

Same As B7 one

Same As B7 one

Same As B7 one
Same As B7 one

Same As B7 one

Same As B7 one

Same As B7 one

1-
(1-(MC138+MC137)/(MC1+MC2))*(1-
((MC812+MC746B+MC140b - MC718 - MC746b
MC14B)
/(MC703+MC812) (MC140a - (MC142e +MC142f ))
RNO Indicator to use in B8 release

SDCCH_DROP_RATE

SDCCH_ASSIGN_UNSUCCESS_RATE

RTCH_DROP_RATE

In B8, it is possible to create customize indicators.

Use this new feature to create an indicator - throught the RNO
Administration tool- with the following formula :
(RTCH_assign_request - DR_Out_Success - RTCH_assign_success
+RTCH_HO_unsuccess ) / (RTCH_assign_request -
DR_Out_Success - RTCH_HO_request) => to use before B8 MR6
After B8 MR6 : RTCH_UNSUCCESS_RATE

HO_INC_BSC_UNSUCCESS_RATE

HO_INC_MSC_UNSUCCESS_RATE

HO_OUT_BSC_UNSUCCESS_RATE
HO_OUT_MSC_UNSUCCESS_RATE

RTCH_Erlang_total

NONE - In B8, it is possible to create customize indicators.

Use this new feature to create this indicator - throught the RNO
Administration tool.
Same formula as in B7
NONE - In B8, it is possible to create customize indicators.
Use this new feature to create this indicator - throught the RNO
Administration tool
Same formula as in B7

NONE - In B8, it is possible to create customize indicators.

Use this new feature to create this indicator - throught the RNO
Administration tool
Formula to use :
***Before B8 MR6 : 1 - (1 - SDCCH_drop_rate) *
(1 - (RTCH_assign_cong + RTCH_assign_fail_radio +
RTCH_assign_fail_BSS)/(RTCH_assign_request - DR_Out_success))
***After B8 MR6 : 1 - (1 - SDCCH_drop_rate) *
(1 - (RTCH_assign_cong + RTCH_assign_fail_radio +
RTCH_assign_fail_BSS)/RTCH_assign_request)
COMMENTS
If SDCCH HO not activated, it is effectively possible to mapped on the
following RNO indicator
SDCCH_drop_rate = (MC138+MC137+MC07)/(MC01+MC02)
If SDCCH HO not activated, this indicator is equivalent to the RNO
one : SDCCH_assign_unsuccess_rate even if not exactly the same
counters are used …
If the Preemption feature is not activated, the formula used is
correct.
If not : the MC921c should be added at the numerator.
Note that this comment was already true in B7 release.
At TRX level => correspondent RNO indicator : RTCH_drop_rate
At cell level => the RTCH_drop_rate indicator could be also used
even if it is not exactly the same formula. Indeed, at cell level, the
incoming intracell handover successes (MC662) are removed at the
denominator of the RTCH_drop_rate :
(MC736+MC621+MC739+MC14c+MC921c)/(MC718+MC717a+MC71
7b-MC662).

*** In B7 release, this BCIQ was considered equivalent to the RNO

indicator : RTCH_unsuccess_rate even if there was a little difference :
the RTCH_unsuccess_rate doesn't take into account the MC41b
counter ...
MC41b : Number of incoming external TCH (in HR or FR usage)
handover -preparation failures due to A-traffic-channel status
mismatch between the BSC and the MSC.
*** In B8 release, a counter for the ASSIGNMENT REQUEST messages
received at BSC side from MSC has been introduced : MC140a.
So, no more needed to compute the number of assign requests
adding the attempts (MC703) and the congestion (MC812).
It can be computed as follows : MC140a - (MC142e +MC142f)
(MC142e +MC142f) => Number of outgoing directed retry successes.
It should be removed from the MC140a as it represents the number
of requests received but served in a neighbour cell throught directed
retry.
*** Before B8 MR6 : the RTCH_assign_request indicator has been
mapped directly on MC140a without taking into account the specific
case of cells congested with DR activated. => Not correct and all the
indicator using RTCH_assign_request impacted and not valid.
The correction has been introduced in B8 MR6.
It is the reason why two different indicators should be used for this
BCIQ
in RNO before and after B8 MR6.

3G => 2G HO taken into account

In B8 release, if the SDCCH Dynamic feature is activated :
the static TCH radio timeslots and the dynamic SDCCH/8 timeslots
allocated as TCH are taken into account.

The counter MC14b has been removed in B8 release.

It can be replaced by the following formula :
MC140b (new in B8 => ASSIGN COMMAND) - MC718 (ASSIGN
SUCCESS) - MC746b (ASSIGN FAIL RADIO)
In fact, thanks to the introduction of the MC140a and MC140b
counters in B8 release, it is also possible to evaluate the number of
failures due to system problems during the preparation phase of a
normal assignment procedure as follows : [MC140a - (MC142e
+MC142f)] (REQUEST) - MC140b (COMMAND) - MC812
(CONGESTION).
If this new kind of failure is taken into account in this indicator the
formula becomes :
1-
(1-(MC138+MC137)/(MC1+MC2))*
(1-( MC140a - (MC142e +MC142f) - MC718) /(MC140a -
(MC142e +MC142f)) ) =1 - call_setup_success_rate after B8
MR6.
Before B8 MR6 => 1 - (1-SDCCH_drop_rate)*(1-
(RTCH_assign_request - DR_Out_success -
RTCH_assign_success)/(RTCH_assign_request -
DR_Out_success))
BCIQ BCIQ Definition

BGIQ1D Taux de succès d'établissement de TBF

BGIQ1U Taux de succès d'établissement de TBF

BGIQ2D Taux de relâchement normal de TBF DL

BGIQ2U Taux de relâchement normal de TBF UL
BGIQ3D Nombre de TBF request DL

BGIQ3U Nombre de TBF request UL

BGIQ4D Taux de retransmission de blocks RLC D

BGIQ4U Taux de retransmission de blocks RLC U

BGIQ5D Ratio d’utilisation de blocks CS1/CS2 DL

BGIQ5U Ratio d’utilisation de blocks CS1/CS2 UL

%DL TBF establishment requests

BGIQ6D requesting 1;2;3;4;5 slot which are
totally satisfied

%UL TBF establishment requests

BGIQ6U requesting 1;2;3;4;5 slot which are
totally satisfied

%DL TBF establishment requests

BGIQ7D requesting 2;3;4;5 slots which are
partially sastified

%UL TBF establishment requests

BGIQ7U requesting 2;3;4;5 slots which are
partially sastified
BGIQ8 Volumetrie BSS sans retransmission U
B7 BCIQ FORMULA
(P90a+P90b+P90c+P90d+P90e+P90f)
/ (P91a+P91b+P91c+P91d+P91e+P91f)

(P30a+P30b+P30c) / (P62a+P62b+P62c)

P9 / (P90a+P90b+P90c+P90d+P90e+P90f)
P22 / (P30a+P30b+P30c)
P91a+P91b+P91c+P91d+P91e+P91f

P62a+P62b+P62c

(P20a + P20b)
/ (P55a+P55b+P20a+P20b+P72a + P72b)

(P21a + P21b)
/ (P57a+P57b+P21a+P21b+P73a + P73b)
(P20a + P55a + P72a)
/ (P20a + P55a + P72a + P20b + P55b +
P72b)

(P21a + P57a + P73a)

/ (P21a + P57a + P73a + P21b + P57b +
P73b)

(p160+p162p+p164)
/ (p90a+p90b+p90c+p90d+p90e+p90f)

(p161+p163+p165) / (p30a+p30b+p30c)

(p166+p168)
/ (p90a+p90b+p90c+p90d+p90e+p90f)

(p167+p169)
/ (p30a+p30b+p30c)
(181*p57a + 268*p57b) / 1024
+(181*p55a + 268*p55b) / 1024
RNO Indicator used in B7 release

GPRS_DL_TBF_SUCCESS_RATE

GPRS_UL_TBF_SUCCESS_RATE

GPRS_DL_TBF_NORMAL_RELEASE_RATE
GPRS_UL_TBF_NORMAL_RELEASE_RATE
GPRS_DL_TBF_REQUEST

GPRS_UL_TBF_REQUEST

GPRS_DL_RLC_block_CS1_CS2_retransmissing
_rate

GPRS_UL_RLC_block_CS1_CS2_retransmissing
_rate
GPRS_DL_RLC_block_PDTCH_CS2_ratio

GPRS_UL_RLC_block_PDTCH_CS2_ratio

NONE - It should be computed via excel using

the following formula :
(GPRS_DL_TBF_1_TS_success +
GPRS_DL_TBF_2_OR_3_TS_success +
GPRS_DL_TBF_4_OR_5_success) /
GPRS_DL_TBF_success

NONE - It should be computed via excel using

the following formula :
(GPRS_UL_TBF_1_TS_success +
GPRS_UL_TBF_2_OR_3_TS_success +
GPRS_UL_TBF_4_OR_5_success) /
GPRS_UL_TBF_success

NONE - It should be computed via excel using

the following formula :
(GPRS_DL_TBF_2_OR_3_TS_partial_success +
GPRS_DL_TBF_4_OR_5_partial_success) /
GPRS_DL_TBF_success

NONE - It should be computed via excel using

the following formula :
(GPRS_UL_TBF_2_OR_3_TS_partial_success +
GPRS_UL_TBF_4_OR_5_partial_success) /
GPRS_UL_TBF_success
NONE - It should be computed via excel using
the following indicators :
P55a =>
GPRS_DL_useful_throughput_CS1_ack
P55b =>
GPRS_DL_useful_throughput_CS2_ack
P57a =>
GPRS_UL_useful_throughput_CS1_ack
P57b =>
GPRS_UL_useful_throughput_CS2_ack
B8 BCIQ FORMULA

Same as B7 one

(P30a + P30b + P30c) / (P62a + P62b + P62c - P438c)

Same as B7 one
Same as B7 one
Same as B7 one

P62a + P62b + P62c - P438c

(P20a+P20b)
/ (P55a+P55b+P20a+P20b +P72a + P72b)

(P21a+P21b)
/ (P57a+P57b+P21a+P21b +P73a + P73b)
(P20a + P55a + P72a)
/ (P20a + P55a + P72a + P20b + P55b + P72b)

(P21a + P57a + P73a)

/ (P21a + P57a + P73a + P21b + P57b + P73b)

Same as B7 one

Same as B7 one

Same as B7 one

Same as B7 one
Same as B7 one
RNO Indicator to use in B8 release

GPRS_DL_TBF_SUCCESS_RATE

GPRS_UL_TBF_SUCCESS_RATE

GPRS_DL_TBF_NORMAL_RELEASE_RATE
GPRS_UL_TBF_NORMAL_RELEASE_RATE
GPRS_DL_TBF_REQUEST

GPRS_UL_TBF_REQUEST

NONE - In B8, it is possible to create customize

indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool
P20a =>
GPRS_DL_RLC_block_PDTCH_CS1_retransmissing_ac
k
P20b =>
GPRS_DL_RLC_block_PDTCH_CS2_retransmissing_ac
k
P55a => GPRS_DL_useful_throughput_CS1_ack
P55b => GPRS_DL_useful_throughput_CS2_ack

NONE - In B8, it is possible to create customize

indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool
P21a =>
GPRS_UL_RLC_block_PDTCH_CS1_retransmissing_ac
k
P21b =>
GPRS_UL_RLC_block_PDTCH_CS2_retransmissing_ac
kP57a => GPRS_UL_useful_throughput_CS1_ack
P57b => GPRS_UL_useful_throughput_CS2_ack
NONE - In B8, it is possible to create customize
indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool
P20a =>
GPRS_DL_RLC_block_PDTCH_CS1_retransmissing_ac
k
P20b =>
GPRS_DL_RLC_block_PDTCH_CS2_retransmissing_ac
k
P55a => GPRS_DL_useful_throughput_CS1_ack
P55b => GPRS_DL_useful_throughput_CS2_ack

NONE - In B8, it is possible to create customize

indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool
P21a =>
GPRS_UL_RLC_block_PDTCH_CS1_retransmissing_ac
k
P21b =>
GPRS_UL_RLC_block_PDTCH_CS2_retransmissing_ac
kP57a => GPRS_UL_useful_throughput_CS1_ack
P57b => GPRS_UL_useful_throughput_CS2_ack

NONE - In B8, it is possible to create customize

indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool

NONE - In B8, it is possible to create customize

indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool

NONE - In B8, it is possible to create customize

indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool

NONE - In B8, it is possible to create customize

indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool
NONE - In B8, it is possible to create customize
indicators.
Use this new feature to create this indicator -
throught the RNO Administration tool
COMMENTS

P438c => New B8 counter

The counter P438c is taken into account in P62x counters
and it doesn't correspond to UL TBF establishment attempts for traffic.
So, it is necessary to subtract it.
(P438c :Number of UL RLC control blocks received on PACCH/U for MS
in packet idle mode and used to carry NC2 signalling messages (when
no PCCCH is established in the cell)

P438c => New B8 counter

The counter P438c is taken into account in P62x counters
and it doesn't correspond to UL TBF establishment attempts for traffic.
So, it is necessary to subtract it.
(P438c :Number of UL RLC control blocks received on PACCH/U for MS
in packet idle mode and used to carry NC2 signalling messages (when
no PCCCH is established in the cell)

The counters P72a and P72b have been removed in B8.

P72a and P72b are in fact replaced by a new counter P72c taking into
account all DL RLC blocks encoded in GPRS CS (CS1, CS2, CS3 and
CS4) that are lost.
Moreover, the lost blocks are counted in RLC unacknowledged mode
whereas the useful and the retransmitted are evalutaed in RLC
acknowledged mode.

The counters P73a and P73b have been removed in B8.

P73a and P73b are in fact replaced by a new counter P73c taking into
account all UL RLC blocks encoded in GPRS CS (CS1, CS2, CS3 and
CS4) that are lost.
Moreover, the lost blocks are counted in RLC unacknowledged mode
whereas the useful and the retransmitted are evalutaed in RLC
acknowledged mode.
The counters P72a and P72b have been removed in B8.
P72a and P72b are in fact replaced by a new counter P72c taking into
account all DL RLC blocks encoded in GPRS CS (CS1, CS2, CS3 and
CS4) that are lost.
Moreover, the lost blocks are counted in RLC unacknowledged mode
whereas the useful and the retransmitted are evalutaed in RLC
acknowledged mode.

The counters P73a and P73b have been removed in B8.

P73a and P73b are in fact replaced by a new counter P73c taking into
account all UL RLC blocks encoded in GPRS CS (CS1, CS2, CS3 and
CS4) that are lost.
Moreover, the lost blocks are counted in RLC unacknowledged mode
whereas the useful and the retransmitted are evalutaed in RLC
acknowledged mode.
RMS job management at RNO side
RMS job activation process

RNO tool deals with :

Templates definition
Templates application
RMS Parameter tuning
OMC-R deals with :
RMS job definition Templates

RMS job creation

NPA tool deals with :
RMS counters reception
Indicators computation
RMS ind. Storage
RMS ind. Consolidation
RNO tool deal with :
Integration of RMS
indicators on usual QoS
follow-up process (RMS QoS
reports, ….)

1 RNO defines and sends

RMS templates to the OMC-R
The OMC-R activates RMS campaign
2
in the BSS
RMS counters are transferred to
3 the OMC
RMS counters are
stored in NPA
RMS indicators
requested by RNO
 in the BSS
RMS counters are transferred to
3 the OMC
RMS counters are
stored in NPA
4
RMS indicators
requested by RNO
5 RMS QoS report
displayed RNP
6
RNO calculates and exports 7
Experience interference matrix Calculate experience matrix

to RNP
7
RNO side

Benefit to whole RNO

Templates

PM

BSS

3
paign PM
2

4 PM
OMC-R
 4 PM
OMC-R
NPA
5

1
Template

Calculate experience matrix 6

RNO
 RNP Project Directory Structure

The minimum MIF version supported is 300.

The RAST format :
supports bitmap files (*.bmp) with 8 or 24 bits of colors.
must be calibrated in UTM geographical coordinates system.

How to import RNP design into A9155 RNO

Data Preparation:
1. Create a new project version:

Open V:\Data\Project_cellplus

In this folder, copy the latest version and rename it:

V:\Data\Project_cellplus\Version_1_2007\cell_des
check the presence of the 3 files (cel.cof, frq.cof, adj.cof) whithin this
If those folders and files are not present, create them from scratch.

Final structure should be:

V:\Data\Project_cellplus\Version_1_2007\cell_des
V:\Data\Project_cellplus\Version_1_2007\cell_des
V:\Data\Project_cellplus\Version_1_2007\cell_des
In this folder, copy the latest version and rename it:
V:\Data\Project_cellplus\Version_1_2007\cell_des
check the presence of the 3 files (cel.cof, frq.cof, adj.cof) whithin this
If those folders and files are not present, create them from scratch.

Final structure should be:

V:\Data\Project_cellplus\Version_1_2007\cell_des
V:\Data\Project_cellplus\Version_1_2007\cell_des
V:\Data\Project_cellplus\Version_1_2007\cell_des

2. update cel.cof, frq.cof, adj.cof:

using Notepad, open cel.cof and update the version's name and the d
copy this header (only the first line)
open frq.cof, delete the fist line and paste the copied header instead s
open adj.cof delete the fist line and paste the copied header instead, s

3. Open the file cel.cof with EXCEL and update it

if needed, use DATA > TEXT TO COLUMNS > SEPARATOR =;
Modify cells parameters, cell coordinates or add new cells if needed.

FILE > SAVE AS > save the file as cel.cof and choose CSV format
open cel.cof with NOTEPAD, remove the extra ";" in the first 2 lines

4. Open frq.cof with EXCEL and update it accordingly to cel.cof.

IMPORT TNE NEW VERSION IN RNO:

5. Open RNO ADMINISTRATION WORKSHOP

6. Open the module 'RNP Configuration' (Login: Administrator, pwd:...

7. Right Click on the main project (upper window), choose "Add new p

8. Fill up the form, choose the path of the project: V:\Data\Project_UM

version.

9. Click on "Start import"

10. The Log file wll be saved in "D:\programFiles\Alcatel\Rnoclient\ou

check that all cells have been correctly imported.

11. If errors: correct the input files accordingly and re-import

12. Modifications will not be visible in the RNO client until an OMCR im
performed.

Manual import is possible, otherwise simply wait for the next day (sch
 10. The Log file wll be saved in "D:\programFiles\Alcatel\Rnoclient\ou
check that all cells have been correctly imported.

11. If errors: correct the input files accordingly and re-import

12. Modifications will not be visible in the RNO client until an OMCR im
performed.

Manual import is possible, otherwise simply wait for the next day (sch
automatically run during the night)

Import Raster from GOOGLE EARTH

Open google earth, position above the area you want to Import
Verify the north is pointing upwards (0 deg.)
Clear all status bars, side bar, etc. in order to have a clean and large image
Wait for the image to be 100% refreshed
Go to tools (outils), options and modify 2 options :
1. Detail zone = large image (1024 x 1024)
2. Coordinates (rendu) to Degrees (Degres) instead of Degres mimutes secondes)
Go to file / save / save image (fichier / enregistrer / enregistrer l'image)
Save the image in JPG
Do not modify anything in GOOGLE EARTH !!! Do not move the image !!
Open the image with Microsoft PAINT and save it as a bitmap (BMP) image (24bits).. Conversion makes the
The BMP file is now open in MS-Paint. Open "Image / Attributes" and write down the width and the height of
Close MS-Paint

Return to Google earth, show the status bar (affichage / Barre d'etat)
This status bar displays the coordinates of the cursor. Note the absolute value coordinates of
1. Point 1 = extreme top-left
2. Point 2 = extreme top-right
3. Point 3 = extreme bottom-left
4. Point 4 = extreme bottom-right
TIPS : Move the "MS-windows desktop bar" to the top of the screen.
TIPS : To catch the correct coordinates, move the mouse slowly along the right or left side of
TIPS : Write down the values just before the sudden change : Lat. And Long. The value after

Translate the values into UTM (meters). To do so, use the excel macro located in V:
In the pink area, in the "DECIMAL" input table, modify N/S and E/W accordingly to the country where you're
i) Input the coordinates of point 1.
ii) Write down the 2 output values (in the pink area, EASTING and NORTHING) and the zone
iii) Repeat i and ii
Open a text file ".rast" (use an existing one, i.e. the portugal.rast) and make a copy for your project
Modify the image name after Fil, so it is linked to the BMP file you saved earlier (include the .bmp, and MUS
Modify the coordinates of each point (point 1,2,3,4) by using the UTM coordinates (in green)
Modify the size of the image, starting from point 1 to point 4 (follow the logic of current file, point 1 at (0,0) …
Replace the ZONE CM of the file by the ZONE CM from the excel macro (in pink)

!table
!version 300
!charset WindowsLatin1

Definition Table
File "CascaisR.bmp"
Type "RASTER"
(460661,4285039) (0,0) Label "Pt 1",
(464700,4285000) (1024,0) Label "Pt 2",
(460651,4282298) (0,695) Label "Pt 3",
(464698,4282275) (1024,695) Label "Pt 4"
CoordSys Earth Projection 8, 104, "m", -9, 0, 0.9996, 500000, 0
Units "m"

Save and close everything

Import the RAST file in the RNP module of RNP administration workshop …

Note : the coordinates must be in meters

the size image is in pixels
in case the raster is not located where it should be, you can troubleshoot by comparing the RNO coordinate
(to compare coordinates, look at the map window in RNO, bottom of the screen, select "Geographical"… com
tory Structure

gn into A9155 RNO:

it:
sion_1_2007\cell_des
adj.cof) whithin this new folder
hem from scratch.

sion_1_2007\cell_des\cel.cof
sion_1_2007\cell_des\adj.cof
sion_1_2007\cell_des\frq.cof
 it:
sion_1_2007\cell_des
adj.cof) whithin this new folder
hem from scratch.

sion_1_2007\cell_des\cel.cof
sion_1_2007\cell_des\adj.cof
sion_1_2007\cell_des\frq.cof

on's name and the date in file header

pied header instead save it

pied header instead, save it

ARATOR =;
new cells if needed.

oose CSV format

in the first 2 lines

ngly to cel.cof.

RNO:

Administrator, pwd:...)

), choose "Add new project version"

: V:\Data\Project_UMC, cosse the latest

Alcatel\Rnoclient\outputs\logs\XNP.log

nd re-import

ient until an OMCR import have been

for the next day (scheduled import will be

Alcatel\Rnoclient\outputs\logs\XNP.log

nd re-import

ient until an OMCR import have been

for the next day (scheduled import will be

gres mimutes secondes)

ge (24bits).. Conversion makes the image go from 200kb to 2Mb.

te down the width and the height of the image.

value coordinates of each corner of the image (without the possible negative signs)

slowly along the right or left side of the screen till the corner, until the coordinates change suddenly.
ge : Lat. And Long. The value after the sudden change is WRONG !!!

rdingly to the country where you're in, compared to Equator and Greenwich meridian

NG and NORTHING) and the zone CM.

ke a copy for your project
earlier (include the .bmp, and MUST be located in same folder as image) (in red, in the text below)
ordinates (in green)
gic of current file, point 1 at (0,0) … etc.) in orange

by comparing the RNO coordinates between a correct map and the raster map.
screen, select "Geographical"… compare both couples of coordinates, to see what is the main difference (a minus sign ? First digits are
ence (a minus sign ? First digits are uncorrect ?)
 RMS Feature Description
Radio Measurements Statistics (RMS) is a feature in
BSS software release
Designed to make far easier the work for planning a
a network
Allowing to constantly check pure network QoS and
network parameters:
Ÿ Provides useful statistics on reported radio measurements
Ÿ Based on real field measurements and not in predictions
Ÿ Users mobiles and BTSs are acting as measurement equip
RMS are performed by mobiles and BTSs and made
OMC-R through the usual PM application.

RMS allows to:

Ÿ Detect interfered frequencies and interferes
Ÿ Assess quality of the cell coverage
Ÿ Assess radio link quality
Ÿ Evaluate the voice quality
Ÿ Assess the traffic distribution from statistics
– On reported neighbour cells
– Based in Timing advance statistics
RMS results usage:
Ÿ Optimize the neighbourhood and frequency planning
Ÿ Detection of the origin of a bad QoS in order to optimize
network parameters.

RMS Feature – How it wor

 RMS Feature – How it wor
Radio Measurement Statistics are performed by mo
TCH channels
The BTS format those requested statistics and store
At the end of observation period, BTS builds a repo
BSC
BSC forwards the measurement to the OMC-R thoug
RMS results can be exported from OMC-R to a post-
RMS results are retrieved once per job

RMS Feature Activation

RMS feature can be activated from OMC-R v
methods:
Permanent Measurement Campaign
Ÿ Provide start & stop time
Ÿ RMS job is launched automatically
– every day
– between the same hours
– on all the cells of the OMC-R
On demand measurement campaign
Ÿ Provide start & stop time
Ÿ Provide BSS identity & object list
Ÿ Accumulation period
Ÿ Must be restarted after the RMS stop time, so as to get new RMS
Ÿ On demand RMS job is launched only once

RMS Feature - Flow scena

At the beginning of the RMS job, the TRE receives f
message START_RMS_REQ
Ÿ including the RMS_BTS_PARAMETERS , the Neighbour ce
frequency list
If at this time, there is already a RMS observation o
aborted
At the beginning of the RMS job, the TRE receives f
message START_RMS_REQ
Ÿ including the RMS_BTS_PARAMETERS , the Neighbour ce
frequency list
If at this time, there is already a RMS observation o
aborted
TRE after checking the memory availability, use th
included in START_RMS_REQ for the statistics related
cells/frequencies
TRE open each MEASUREMENT REPORT sent by the
the DL measurements, MS power level, the TA
TRE keeps in memory the UL measurements, BS po
Ÿ measured in the same period as the measurements in th
REPORT

TRE perform measurements on the number of BFI

corresponding SACCH multiframe
Ÿ multiframe where the UL and DL measurements have be
End of the RMS collecting period (STOP_RMS_REQ)
report format with all the statistics
Ÿ Computes the averages of MS power, BS power and Tim
considered in the RXLEV/RXQUAL matrixes
End of the measurement period (RMS_DATA_REQ),
the RMS statistics and transmit them to the BSC via
In exceptional cases (‘immediate stop’) the STOP_R
message is received
Ÿ TRE interpret this as an abort of the current job and be r
start of a new RMS-job
 MAFA: Mobile Assisted Frequency
In order to help also the operator find "clean" frequ
also provide information based on the MAFA feature
Mobile Assisted Frequency Allocation (MAFA) or Ex
Measurement Reporting:
Ÿ Is a standardized GSM feature
Ÿ Provides a way for the system to ask each MS to measu
frequencies of non-neighbour cells
Ÿ Mobile dependent feature
Ÿ MAFA can also be used to check interferences from non-
Ÿ Frequencies will be reported even if they are received w
the BCCH frequency of neighbour cells

MAFA – How it works?

Inside a RMS job is possible to apply the “Mobile A
Allocation” (MAFA) or “Extended Measurement Repo
Ÿ Consists in sending an “Extended Measurement Order”
mobiles
Ÿ Mobile takes one SACCH multiframe to perform measure
frequencies
Ÿ These measurements are reported via the
“EXTENDED_MEASUREMENT_REPORT” message

The EMO is only sent once per call.

Specific actions are required at the OMC-R and BSC
launch the MAFA procedure
The statistics related to MAFA will be collected in t
integrated in the RMS results
Specific actions are required at the OMC-R and BSC
launch the MAFA procedure
The statistics related to MAFA will be collected in t
integrated in the RMS results

MAFA – Activation
MAFA job is included in the RMS job
Ÿ MAFA job that allows measurements of specific frequenc
mobiles during the RMS job
Two aspects on MAFA job definition:
Ÿ The activation of the MAFA feature, that can be done th
EN_EXT_MEAS_REP
Ÿ The definition of the frequencies to be monitored by the
(called MAFA frequencies)
The definition of the MAFA frequencies and EN_EXT
can be performed thought RNO also

MAFA vs. Dummy Neighbou

Another way to measure non-neighbours is throug
measurements with dummy neighbours
ŸThis procedure will be present in detail later in Frequenc
algorithm
ŸAll cells close to the serving cell are measured and repor
ŸDummy neighbors:
–Not real neighbors
–Different BCCH than Serving cell and Neighbor Cells
MAFA characteristics : Dummy neighbour c
ŸMAFA frequencies are reported even ŸDummy neighbours are
if the RxLevel is low the RxLevel is one of the
ŸMAFA measurements are reported neighbours
just once per call ŸDummy neighbours are
ŸFor MAFA, specific mobiles MEASUREMENT REPORT
supporting this standardized GSM ŸEvery Mobile Station (M
feature are needed provide RMS
ŸMAFA measurements identify ŸDummy neighbours ide
ŸMAFA frequencies are reported even ŸDummy neighbours are
if the RxLevel is low the RxLevel is one of the
ŸMAFA measurements are reported neighbours
just once per call ŸDummy neighbours are
ŸFor MAFA, specific mobiles MEASUREMENT REPORT
supporting this standardized GSM ŸEvery Mobile Station (M
feature are needed provide RMS
ŸMAFA measurements identify ŸDummy neighbours ide
interfering frequencies cells

RMS Feature - Template

Template contains the job parameters:
ŸThese data give the way RMS counters should be increm

Example:
ŸRMS provides a facility to obtain the distribution of the R
ŸThis distribution represents the number of measuremen
the value of the RxLev is within different intervals, for ea
ŸThe interval bounds are defined by thresholds, which ar
template

Template contents
Radio level bands configuration (MEAS_STAT_LEV_
Ÿ9 parameters from -48 dBm to -109 dBm (1 dB step)
Radio C/I bands configuration (MEAS_STAT_C_I_1 t
Ÿ9 parameters from -62 dB to 62 dB (1 dB step)
Radio CFE bands configuration (MEAS_STAT_BFI_1
Ÿ9 parameters from 1 to 24 (step 1)
Radio Link Counter S configuration (MEAS_STAT_R
Ÿ9 parameters from 0 to 127 SACCH multiframes (step 1
Radio Path balance bands configuration (PATH_BA
Ÿ9 parameters from -109 dBm to 109 dBm (1 dB step)
EN_BALANCED_CI to take care of PWR Control for
EMO flag to take care of MAFA
Ÿ9 parameters from 0 to 127 SACCH multiframes (step 1
Radio Path balance bands configuration (PATH_BA
Ÿ9 parameters from -109 dBm to 109 dBm (1 dB step)
EN_BALANCED_CI to take care of PWR Control for
EMO flag to take care of MAFA

Voice Quality statistics are based on non-sliding averages of RxQual an

and FER measurements on uplink
Voice Quality configuration
ŸVQ_AVERAGE parameter from 0 to 128 SACCH multiframes
ŸVQ_RXLEV from -47 dBm to -110 dBm (1 dB step)
ŸVQ_RXQUAL from 0.0 to 7.0 (step 0.1)
ŸVQ_RXQUAL_VS_RXFER from 0.0 to 7.0 (step 0.1)
ŸVQ_GOOD_RXFER from 0.0% to 20.0% (step 0.1%)
ŸVQ_BAD_RXFER from 0.0% to 20.0% (step 0.1%)
ŸVQ_INTF_THRESHOLD from 0% to 100% (step 1%)
ŸVQ_FER_THRESHOLD from 0% to 100% (step 1%)

16 templates to play with; 54 parameters per template

RMS Feature - Parameters

Other RMS parameters besides th
Parameter Description

RMS_TEMPLATE_INDEX Template of values of RMS parameters to be applied to the concerned cell;

T_RMS_BSC General supervision of RMS in the BSC

T_RMS_BSC_RECONF Delay to restart RMS job after reconfiguration

T_RMS_BSC_RESTART Delay to restart RMS job after TRE restart

T_RMS_BTS Time interval between BTS transfer of 2 successive RMS blocks of measure

EN_EXT_MEAS_REP This flag enables/disables the extended measurement reporting for Mobile A

TA_STAT Threshold on timing advance to define the cell limit used for Radio Measure
 TA_STAT Threshold on timing advance to define the cell limit used for Radio Measure

EN_BALANCED_CI This flag enables/disables to balance the C/I measure

RMS Feature - Outputs

Statistics related to the TRXs

ŸC/I distribution on neighbour cells
–Traffic distribution on the cell border: number of samples repor
neighbour cell
–Detection of interfered frequencies as well as interfering cells
–Computation of experience matrix
ŸC/I distribution on reported frequency (MAFA)
–Measurements on any ARFCN (BCCH or TCH)
–Detection of an interferer not declared as neighbour cell
–Search of clean frequencies
ŸDistribution of quality samples in function of level (DL &
–Assessment of the quality of the cell coverage
–Checking the HO parameter settings

>3 main RMS statistics types

•Call Quality Statistics which qualify calls accordin
coverage/interference criteria
–based on samples corresponding to measurement resu
number of SACCH multi-frames

•Radio Quality Statistics:

–UL/DL level, UL/DL qual
–CFE
–AMR (Analyse the coded values)
–Timing Advance

•C/I Statistics on neighboring freq/MAFA freq

–last 2 statistics types based on samples corresponding
 –UL/DL level, UL/DL qual
–CFE
–AMR (Analyse the coded values)
–Timing Advance

•C/I Statistics on neighboring freq/MAFA freq

–last 2 statistics types based on samples corresponding
results

How to qualify the quality of a call? By looking at the repartition

quality
7

bad quality & level bad quality + good level

bad coverage CQS interfered CQS

VQ_RXQUAL

0
-110 VQ_RXLEV

6.4.2 Call quality parameters

RMS parameters
Call Quality Statistics:
Parameters used to determine if a call is noisy
RXQUAL) and of bad voice quality (according t

>VQ_AVERAGE: averaging window size on me

results to obtain Call Quality Samples (CQSs) (
128 Smf)
>VQ_RXLEV: radio level threshold to specify a
CQS for noisy call statistics (-110 to -65 dBm)
>VQ_RXQUAL: radio quality threshold to speci
(RXQUAL) CQS for noisy call statistics (0 to 7)
>VQ_RXQUAL_VS_RXFER: radio quality thresh
bad or a good quality CQS correlated to bad o
measurements for noisy call statistics (0 to 7)

Call Quality Statistics

>VQ_GOOD_RXFER: Frame Erasure Rate thres

good FER CQS for noisy call statistics (0 to 20
>VQ_BAD_RXFER: FER threshold to specify a b
noisy call statistics (0 to 20%)
>VQ_INTF_THRESHOLD: Call Quality Samples
characterize a call as noisy (0 to 100%)
>VQ_FER_THRESHOLD: Call Quality Samples t
characterize a call as “of bad or good” voice q
100%)
characterize a call as noisy (0 to 100%)
>VQ_FER_THRESHOLD: Call Quality Samples t
characterize a call as “of bad or good” voice q
100%)

>VQ_NOISY_UL_INTERFERENCE = RMS10
Number of calls suffering from interference pr
uplink path

>VQ_NOISY_UL_INTERFERENCE is incremente
call verifies:
100*(INTERFERED_UL_SAMPLES / NUM_UL_SAMPLES) >
VQ_INTF_THRESHOLD
•with
INTERFERED_UL_SAMPLES = nb of times where AV
> VQ_RXQUAL
and AV_RXLEV_UL_VQ>VQ_RXLEV
 Description
S) is a feature introduced since B7

k for planning and optimisation of

etwork QoS and optimize various

dio measurements
not in predictions
easurement equipments
BTSs and made available at the
on.

eres

stics

ency planning
order to optimize consequently the

How it works?
How it works?
erformed by mobiles and BTSs on

atistics and stores all the results

TS builds a report and sends it to

the OMC-R thought PM application

OMC-R to a post-processing tool
job

e Activation
from OMC-R via two

o as to get new RMS data.

Flow scenario
e TRE receives from BSC the

the Neighbour cell list and extra

MS observation ongoing, this is

e TRE receives from BSC the

the Neighbour cell list and extra

MS observation ongoing, this is

ailability, use the parameters

statistics related to the neighbour

ORT sent by the MSs, collect all

el, the TA
urements, BS power level
easurements in the MEASUREMENT

number of BFI on the

urements have been performed

TOP_RMS_REQ), TRE build the

BS power and Timing advance

es
MS_DATA_REQ), the TRE segment
m to the BSC via the RSL
top’) the STOP_RMS_REQ

rrent job and be ready to accept the

 Frequency Allocation
find "clean" frequencies, RMS will
he MAFA feature
on (MAFA) or Extended

ach MS to measure extra-frequencies -

erences from non-neighbour cells

ey are received with a lower level than

w it works?
ly the “Mobile Assisted Frequency
asurement Reporting”:
surement Order” (EMO) to the

o perform measurements on specific

the
message

.
OMC-R and BSC side in order to

be collected in the BTS and

 OMC-R and BSC side in order to

be collected in the BTS and

ctivation
b
f specific frequencies by MAFA

n:
at can be done through the flag

monitored by the MAFA mobiles

cies and EN_EXT_MEAS_REP flag

y Neighbours
hbours is through RMS
ours
later in Frequency planning

easured and reported to the OMC-R

or Cells
mmy neighbour characteristics :
mmy neighbours are reported just if
xLevel is one of the 6 strongest
bours
mmy neighbours are reported every
UREMENT REPORT
ry Mobile Station (MS) is able to
de RMS
mmy neighbours identify interfering
mmy neighbours are reported just if
xLevel is one of the 6 strongest
bours
mmy neighbours are reported every
UREMENT REPORT
ry Mobile Station (MS) is able to
de RMS
mmy neighbours identify interfering

- Template
ters:
s should be incremented

istribution of the RxLev

er of measurement reports for which
t intervals, for each TRX
esholds, which are they defined in a

MEAS_STAT_LEV_1 to _9)
Bm (1 dB step)
AS_STAT_C_I_1 to _9)
dB step)
EAS_STAT_BFI_1 to _9)

n (MEAS_STAT_RLC_1 to _9)
ultiframes (step 1)
ration (PATH_BALANCE_1 to _9)
Bm (1 dB step)
PWR Control for C/I (boolean)
ultiframes (step 1)
ration (PATH_BALANCE_1 to _9)
Bm (1 dB step)
PWR Control for C/I (boolean)

averages of RxQual and RxLev on both paths

per template

ers
besides the templates:

o be applied to the concerned cell; presented in the slides before

ation

rt

successive RMS blocks of measurements

measurement reporting for Mobile Assisted Frequency Allocation

he cell limit used for Radio Measurements Statistics

he cell limit used for Radio Measurements Statistics

e C/I measure

e - Outputs

er of samples reported for each

as interfering cells

(MAFA)
H)
eighbour cell

tion of level (DL & UL)

age

fy calls according to

measurement results averaged over a

MAFA freq
es corresponding to measurement
MAFA freq
es corresponding to measurement

ng at the repartition of the CQS!:

+ good level

CQS
CQS

Level (dBm)
-47

ers
f a call is noisy (according to
ty (according to FER)

ow size on measurement
mples (CQSs) (0 SACCH mfr to

old to specify a bad coverage

0 to -65 dBm)
eshold to specify a bad quality
tistics (0 to 7)
quality threshold to specify a
elated to bad or good FER
atistics (0 to 7)

sure Rate threshold to specify a

tistics (0 to 20%)
d to specify a bad FER CQS for

uality Samples threshold to

o 100%)
ality Samples threshold to
good” voice quality (0 to
o 100%)
ality Samples threshold to
good” voice quality (0 to

= RMS10
nterference problem on the

is incremented whenever a

_UL_SAMPLES) >

times where AV_RXQUAL_UL_VQ

Support de cours Pour toutes opérations site,
se conformer aux méthodes
UNIX - Administration SUN

ATTENTION
Ce document est non validé par les services d'ALCATEL
Il résume de façon incomplète, quelques procédures d'administration de l'OMC-R
Il est un aide mémoire et ne peut en aucun cas servir de méthode.

Il est obligatoire, pour chaque utilisateur de l'OMC-R, d'avoir à disposition, la documentation officielle d'Alcatel.
Celle-ci doit donc être utilisée pour chaque procédure.
Elle s'installe grâce au CD-Rom "BSS CUSTOMER DOCUMENTATION - B6.2 - INSPAQxx".
Cette documentation officielle d'Alcatel, est donc la seule à servir de méthode.
Il faut retrouver les dernières versions valides, sur la base "DIAMS".

Chapitre 1 : Informations machine Page 2

1 - Info système Page 2
2 - Reconfigurer les paramètres de démarrage : ASR Page 3
3 - Devenir le serveur Page 3
4 - Créer un net server Page 4

Chapitre 2 : Gestion du Harware Page 4

1 - Dynamic Reconfiguration Page 4
2 - Contrôle de l'environement Page 5
3 - Réparer le disque de boot Page 5

Draft - Edition 06/08/03 Documentation interne FST Page 519/535

Rédacteur : S. Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes

Chapitre 1 : Informations machine

1 - Info système
root : #
cfgadm affiche les éléments disponibles: cartes PCI, CPU et DD
uname -p affiche l'architecture de la machine (SPARC, …)
uname -m affiche la gamme de la machine (Sun4c, …, Sun4u)
uname -i affiche le type de machine
uname -sr affiche l'OS : Solaris ( SUN OS x.y)
psrinfo -v affiche le num, le type de CPU et sa fréq. (4 lignes par proc.)
psradm -n -v "num_CPU" redémarre la CPU
psradm -f -v "num_CPU" arrête la CPU
more messages | grep CPU affiche infos sur CPU
prtconf -V affiche l'open boot prom (bios) : OBP x.y
prtconf | grep Memory affiche la taille de la RAM
prtconf -v affiche des infos sur la config
more /etc/path_to_inst affiche des infos sur la config
prtconf | grep -v not affiche prtconf sans les ligne qui ont "not"
/usr/lib/picl/picld contrôle les cartes pluggée ou non

/usr/platform/sun4u/sbin/prtdiag -v affiche un diagnostique de l'état de la machine

eeprom affiche les paramètres de boot

ttya -mode affiche les paramètres de boot

isainfo -v affiche le noyau de démarrage

who -r affiche le niveau de démarrage

* format affiche les disques durs internes E4000 (identifiés par "sd@"), et
tous les disques de la baie de disque SSA (identifiés par "ssd@").
format# partition pour aficher la taille d'un disque dur, plus précisément pour un
E4000 et sa baie de disque SSA
partition# print
* format affiche les disques durs internes E4500 et les contrôleurs

de la baie de disque A1000

drivutil -i "contrôleur 1 de la baie de disque A1000 + <s0>" affiches les infos des disques durs

de la baie de disk A1000

rm6 --> [Configuration] --> Module --> Profile --> [Drives] affiches les infos des disques durs

de la baie de disk A1000 (B7.2)

metastat affiche les partions + état des disques pour E4500 & A1000

fsck -F ufs /dev/md/rdsk/d10 répare le disque de boot

Draft - Edition 06/08/03 Documentation interne FST Page 520/535

Rédacteur : S. Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes

>OK
sync re-démarre la machine en mettant à jour les disks

help diag affiche la liste des testes disponibles

test-all teste tous les péripériques disponibles
test <device> teste un périphérique particulier (floppy, net, scsi)
.asr affiche la liste des composants validés
probe-scsi teste la chaine scsi de la carte mère
probe-scsi-all teste toutes les chaines scsi
printenv ce qui est en vert est à faire si besoin avant "probe-scsi-all"
setenv auto-boot? false pour démarrer au prompt OK ("true" demmarre au loggin)
reset-all pour prendre en compte les modifs précédentes
watch-clock teste l'horloge
watch-net teste l'interface réseau
show-devs accède à l'arborescence hardware de la machine
.properties affiche la propriété d'un nœud (arborescence harware)
sifting probe affiche toutes les commandes Probe
.version affiche la version de l'OBP, des POST et OBDIAG
.env affiche l'environement
.speed affiche la vitesse desCPU
banner affiche les informations sur CPU et RAM

2 - Reconfigurer les paramètres de démarrage : Automatique System Recovery (ASR)

root : #
init 0 pout venir sur #OK
#OK
setenv auto-boot? true modifie le paramètre "auto-boot" à "true"
setenv auto-boot-on-error? true modifie le paramètre "auto-boot-on error" à "true"
reset-all pour prendre en compte les modifs précédentes
.asr affiche la liste des composants validés et dévalidés
asr-enable <nom_du_device> valide <nom_du_device>
asr-disable <nom_du_device> dé-valide <nom_du_device>

3 - Devenir le serveur
root : #
tip hardwire si le serveur est sur "#OK", on se retrouve sur "#OK"
Draft - Edition 06/08/03 Documentation interne FST Page 521/535
Rédacteur : S. Pellerin
 Support de cours Pour toutes opérations site,
si le serveur est sur Solaris, on seseretrouve
conformer
suraux méthodes
Solaris
par défaut, le port série B est connecté
tip hardwire:/dev/term/a pour se connecter sur le port série A
~? affiche la liste des commandes TIP
~. ferme la session TIP
~# envoye un [Stop] [A]

4 - Créer un net server

root de la machine distante: #
share -F nfs -o ro,anon=0 /cdrom/cdrom0 à faire directement sur le serveur distant.
root : #
vi /etc/hosts ajouter l'IP adresse et le hostname de la machine distante.
cd /net/<hostname machine distante>/cdrom/<nom du cdrom>
Lancer les commandes normalement. L'accès au lecteur CD distant est automatique.

Selon le CD à installer, certain contenu de fichiers, faisant référence au chemin du cdrom, sont à modifier.
Par exemple, "/install/data/depot.loc", contient le chemin du lecteur CD, pour l'install du CD n°2. Il faut donc

remplacer "/cdrom/cdrom0" par "cd /net/<hostname machine distante>/cdrom/<nom du cdrom>"

root de la machine distante: #

unshare /cdrom/cdrom0 à faire directement sur le serveur distant, pour dévalider l'accès

distant du net server

Chapitre 2 : Gestion du Harware

1 - Dynamic Reconfiguration
root : # pour les cartes PCI, et les CPU à 900Mhz
cfgadm affiche les éléments disponibles: cartes PCI, CPU et DD
cfgadm -c unconfigure <nom_élément> arrête les entrées/sorties de <nom_élément>
cfgadm -c disconnect <nom_élément> déconnecte <nom_élément>
controler la led : - "ok-to-remove" est allumé
cfgadm affiche les éléments disponibles: cartes PCI, CPU et DD
cfgadm -c connect <nom_élément> connecte <nom_élément> après son insertion physique
cfgadm -c configure <nom_élément> démarre les entrées/sorties de <nom_élément>
cfgadm affiche les éléments disponibles: cartes PCI, CPU et DD

root : # pour les disques durs

luxadm probe affiche le nom des boucles FC-AL (noter le nom)
cd /dev/dsk + ls affiche la liste des disques
luxadm display <nom_boucle_FCAL> affiche le nom des disques durs et leur Slot de positionement
df -k affiche le système de fichier par disque (ex : /…/…/)
unmount <system_fichier> démonte le système de fichier du disque concerné
luxadm remove_device <boucle_FCAL,sx> désactive le disque Y situé sur le slot x, dans la

Draft - Edition 06/08/03 Documentation interne FST Page 522/535

Rédacteur : S. Pellerin
 Support de cours Pour toutes opérations site,
se conformer aux méthodes
la boucle FC-AL (ex : FCLoop,s2)
luxadm insert_device <boucle_FCAL,sx> active le disque Y situé sur le slot x, dans la boucle
luxadm probe affiche le nom des boucles FC-AL (noter le nom)

devfsadm résultat idem à ci-dessus

2 - Contrôle de l'environement
root : #
picld Daemon controlant l'evironement lors de l'enlèvement ou

l'insertion d'un composant en hot-plug

.env idem "picld" mais sous #OK

3 - Réparer le disque de boot

root : #
fsck -F ufs /dev/md/rdsk/d10
#OK
sync

Draft - Edition 06/08/03 Documentation interne FST Page 523/535

Rédacteur : S. Pellerin
 BSC ULIS1 B7.2

BSC G2
OSI SYS BC Position Position
TSC TSC TSC 1 1 1 1 2
1 2 3 OSI SYS BC
2 2 2
ULIS_BT07 - Qmux = 1007 (SUMP)
Ater TSU 1 Abis TSU 1 A9100 Evolium Medi Indoor
CI :
4071 4072
TRX :
1 2
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1 Freq :
900 1800
ARFN 1 :
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2 50 610
TRE type :
TRGM TRDM
ARFN 2 :
ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 TRE type :
620
TRDM
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4

Abis 5
Abis 6
ULIS_BT02 - Qmux = 1002 (SUMA)
A9100 Evolium (MBO1)
Ater TSU 2 Abis TSU 2
CI :
TRX : 4021 4022
Freq : 2 2
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1 900 900
ARFN 1 :
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2 TRE type : 10 30
ARFN 2: TRGM TRGM
TRE type :
ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 20 40
ARFN3 :
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 TRE type : TRGM TRGM

Abis 5
Abis 6
ULIS_BT06 - Qmux = 1006 (SUMA)
Ater TSU 3 Abis TSU 3 A9100 Evolium Evolution Indoor
CI :
TRX : 4061 4062 4063
Freq : 1 3 2
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1
ARFN 1 : G850 EGSM 1900
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2 TRE type : 130 5
ARFN 2: TRAL TRGM 520
TRE type : TRAP
ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 975 530
ARFN3 :
TRE type : TRGM TRAP
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4
120
TRGM
Abis 5
Abis 6

Ater TSU 4 Abis TSU 4

ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1

1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 Connecté sur OMC-R E4500 : SOLUVY02
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 Release B7.2 - MR6 ed03 - SDPPackage : SDPTAT46.07T

Abis 5 Product delivery name : BSSSAT02G ed03

Abis 6 BSC configuration : config. 4 Submultiplexing : 4:1

Ater TSU 5 Abis TSU 5 Paramètres Radio : CAE Templates génériques

*CRC4 : OFF
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1 *MCC : 258 *SPC MSC
connecté : 11500
sur : TC G2
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2 *MNC : 51 *SPC BSC : 420

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3

2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 LAC : 4000

Abis 5 OMC-R X25 adresse : 222 2222

Abis 6 BSC X25 adresse : 4444 4444
 BSC ULIS2 B8

BSC G2
OSI SYS BC Position Position
TSC TSC TSC 1 1 1 1 2
1 2 3 OSI SYS BC
2 2 2

Ater TSU 1 Abis TSU 1

ULIS_BT08 - Qmux = 1008 (SUMA)

ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1 A9100 Evolium Evolution Indoor (MBI)
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2 CI :
TRX : 3081 3082 3083
Freq : 1 1 1
ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 ARFN 1 : 900 900 900
TRE type : 95 105 115
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4
ARFN 2 : TRAG TRAG TRAG
TRE type :
Abis 5 ARFN 3 :
TRE type :
Abis 6 ARFN 4 :
TRE type :
Ater TSU 2 Abis TSU 2

ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1

1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2 ULIS_BT01 - Qmux = 1001 (SUMA)
A9100 Evolium Evolution Outdoor (MBO)
CI :
ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 3011 3012
TRX :
Freq : 2 4
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4
ARFN 1 : 1800 900
TRE type : 710 5
Abis 5 ARFN 2 : TRDM TRAG
TRE type : 15
Abis 6 720 TRAG
ARFN 3 :
TRE type : TRDM 25
Ater TSU 3 Abis TSU 3 ARFN 4 : TRGM
TRE type : 35
TRGM
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 ULIS_BT05 - Qmux = 1005 (SUMP)
A9100 Evolium Medi Indoor N3
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 CI :
3051 3052 3053
TRX :
2 2 1
Abis 5 Freq :
900 900 900
ARFN 1 :
Abis 6 45 65 85
TRE type :
TRGM TRGM TRGM
ARFN 2 :
55
TRE type :
Ater TSU 4 Abis TSU 4 TRGM 75
TRGM

ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1

1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 Connecté sur OMC-R V880 : FSTB8
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 Product delivery name : BSSSAV01C ed01

Abis 5 Release B8 - MR5 ed02 - SDPPackage : SDPTAV71.03B

Abis 6 BSC configuration : config. 4 Submultiplexing : 4:1

Ater TSU 5 Abis TSU 5 Paramètres Radio : CAE Templates génériques

*CRC4 : OFF
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1 *MCC : 258 *SPC MSC
connecté : 11500
sur : TC G2
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2 *MNC : 51 *SPC BSC : 400

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3

2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 LAC : 3000

Abis 5 OMC-R X25 adresse : 111 1111

Abis 6 BSC X25 adresse : 3333 3333
 BSC ULIS3 B8

BSC G2
OSI SYS BC Position Position
TSC TSC TSC 1 1 1 1 2
1 2 3 OSI SYS BC
2 2 2

Ater TSU 1 Abis TSU 1

ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1

1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3

2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4

Abis 5
Abis 6

Ater TSU 2 Abis TSU 2

ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1

1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3

2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4
ULIS_BT04 - Qmux = 1004 (SUMP)
Abis 5 A9100 Evolium Medi Outdoor N1
CI :
Abis 6 9041 9042 9043
TRX :
1 1 1
Freq :
900 900 900
ARFN 1 :
Ater TSU 3 Abis TSU 3 50 60 70
TRE type :
TRGM TRGM TRGM
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2
ULIS_BT03 - Qmux = 1003 (SUMA)
ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3 A9100 Evolium Evolution Outdoor
CI :
TRX : 9031 9032 9033 9034
2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 2 2 2 4
Freq :
ARFN 1 : 1800 900 900 1800
Abis 5 TRE type : 810 10 30 830
Abis 6 ARFN 2: TRDM TRAG TRGM TRAD
TRE type : 20 840
ARFN3 : 820 TRAG 40 TRDM
Ater TSU 4 Abis TSU 4 TRE type : TRDM TRGM 850
ARFN4 : TRAD
TRE type : 860
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1 TRDM

1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3

2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 Connecté sur OMC-R V880 : FSTB8

Abis 5 Product delivery name : BSSSAV01C ed01

Abis 6 Release B8 - MR5 ed02 - SDPPackage : SDPTAV71.03B

Ater TSU 5 Abis TSU 5 Paramètres Radio : CAE Templates génériques

*MCC : 258 *SPC MSC : 4
ASMB DTC 1 DTC 2 TCU 2 TCU 1 Abis 1 *MNC : 51 *SPC BSC : 2
1 DTC 3 DTC 4 TCU 4 TCU 3 Abis 2 BSC configuration : config. 4

ASMB DTC 5 DTC 6 TCU 6 TCU 5 Abis 3

2 DTC 7 DTC 8 TCU 8 TCU 7 Abis 4 LAC : 9000

Abis 5 OMC-R X25 adresse : 111 1111

Abis 6 BSC X25 adresse : 9999 9999
 UNIX - Information - Fonctionement

Script de backup = www.sun.com/bigadmin/scripts/index.html

ATTENTION
Ce document est non validé par les services d'ALCATEL
Il résume de façon incomplète, quelques procédures d'administration de l'OMC-R
Il est un aide mémoire et ne peut en aucun cas servir de méthode.

Il est obligatoire, pour chaque utilisateur de l'OMC-R, d'avoir à disposition, la documentation officielle d'Alcatel.
Celle-ci doit donc être utilisée pour chaque procédure.
Elle s'installe grâce au CD-Rom "BSS CUSTOMER DOCUMENTATION - B6.2 - INSPAQxx".
Cette documentation officielle d'Alcatel, est donc la seule à servir de méthode.
Il faut retrouver les dernières versions valides, sur la base "DIAMS".

Chapitre 1 : xxx Page 2

1- Page 2
2- Page 2
3- Page 2
4- Page 2
5- Page 2
6- Page 2
7- Page 3
Page 3
Page 3
Page 3
Page 3
Page 3

Chapitre 2 : yyy Page 4

1- Page 4
2- Page 4
3- Page 4
4- Page 4
5- Page 4
6- Page 5
7- Page 5
Page 5
Page 5
Chapitre 1 : Informations Générale
1 - Info

FIELD ENGINEER HANDBOOK

Volume 1 : liste de FRU Field Remplacable Unit (pièces détachées).

Volume 2 : vue éclatée des différentes machines : Part Break Down.

Chaque FRU possède :

Part Number : Calss Code + Base Number (ex : 501 1877)

Serial Number : Année fabrication (1 car.) + Semaine fabrication (2 car.) + Usine (2 car.) + Num Série (4 car.)

2 - Principaux composants d'une machine

CPUs RAM NVRAM OBP

Bus principal de données

Controleur SCSI Controleur Port Série Audio Graphique Ethernet

Floppy A B

lecteur CD

CPU

Micro SPARC : 50 Mhz --> 125 Mhz (prosseur 32 bits)

Super SPARC : 33 Mhz --> 150 Mhz (prosseur 32 bits)

Ultra SPARC I, II, III : 143 Mhz --> 900 Mhz (prosseur 64 bits)

NVRAM

Hostid

adresse Ethernet de la machine

Time of the day

paramètres de boot courant

pile

OBP

POST (Power On Self Test )

Pilotes intégrés (drivers pour chaque cartes)

Langage de programmation : FORTH

Interpréteur FORTH (il donne accès au prompt OK et permet de taper des commandesde boot, d'information

et de diagnostique.

Valeurs par défaut des paramètres de boot.

Chapitre 1 : Informations Générale
2 - Principaux composants d'une machine (suite)

BUS

SBUS : (16 - 25 Mhz) 32 bits

MBUS : (33 - 50 Mhz) 64 bits

UPA : (100 - 120 Mhz) 64 bits

PCI : (33 - 66 Mhz) 32 ou 64 bits

SCSI : Ultra Wide SCSI (68 broches)

FC-AL : Fiber Chanel A… Loop (100 Mo / s)

i2C : Environement de la machine (température, …)

RAM memory

SIMM : 60 nano sec barrette de 32 Mo à 1 Go

DIMM :

Chapitre 2 : SUN BLADE 100

1 - Description

Processeur Ultra Sparc 2e 502 Mhz

Bus PCI (pci@1f)

Controleur IDE

PMU : permet l'accès au bus i2c

Environemental Ebus : permet l'accès aux Prts Série + OBP + Port Parallèle + floppy + NVRAM

ERI : bus permettant l'accès à la carte réseau

M64 : carte graphique

Controleur A B

Floppy Port Série NVRAM OBP //

ebus

CPUs

Bus PCI@1f

eri

Controleur ide RAM Bridge Audio M64 graph

IDE t0 t1 PMU Ethernet

lecteur CD
PCI 1 2 3

M S

i2c
Chapitre 3 : SUN FIRE V880
1 - Description

2 à 8 CPU Ultra Sparc III (750 ou 900 Mhz) - 2 CPU par carte : max 4 cartes

1 à 32 Go de RAM

3 à 12 Disques durs en FC-AL de 36 ou 72 Go

1 interface ERI pour carte Ethernet 10/100 Mbits

1 sortie Giga Bit Ethernet

9 slot PCI (2 en 66 Mhz et 7 en 33 Mhz )

Carte RSC pour accès à distance même si V880 est éteint (Doc SUN V880, page 2-6 et 2-7)

Solaris 8 07/01 + OBP 4.5.6 + Patches 112 186-03 (config minimum)

Carte Mère
SAFARI bus avec une bande passante de 9,6 Go/s avec une fréquence de 150 Mhz.

Connexion de maximum 4 cartes CPU (CPU board).

CPU Board

2 CPU par carte numérotées : CPU 5 / 7 haut

CPU 4 / 6

CPU 1 / 3

CPU 0 / 2 bas

Seules les CPU à 900 Mhz peuvent se plugger/ dé-plugger à chaud.

Contient les barrettes mémoires en "double face" de capacité de 128 Mo, 256 Mo ou 512 Mo.

2 groupes de 4 barrettes pour chaque CPU.

A0 A1 B0 B1 Toujours remplir le groupe 1, composé de

A0 et B0 en premier.
Si besoin, remplir A1 et B1.

0 2 1 3 0 2 1 3

G1 G2 G1 G2

Ajouter 4 par 4 les barettes (de même capacité par groupe de 4) ex : A0B0 avec 4x512 et A1B1 avec 4x256

Carte I / O

8 slot PCI

2 ports série

1 connecteur HDM pour relier la carte mère et le bus PCI

SCSI subsystem

Super IO

Serial Prom
Arborescence Hardware

(Doc SUN V880, page 3-46)

Contrôle de l'environement

Un daemon fonctionne en permanance pour contrôler l'environement : "PICLD".

Picld met 30 secondes à détecter l'insertion ou l'enlèvement d'un composant hot-plug.

Disques Durs 1 1
9 0 1
Position des disques durs : Possibilité de plugger ou dé-plugger un disque dur
6 7 8
à chaud.
3 4 5

0 1 2

Architecture SUN FIRE V880

SAFARI Bus

eri

SCHIZO 0 SCHIZO

@8,7 33Mhz @9,6 66Mhz

@8,6 66Mhz @1

SCSI PCI PCI PCI PCI PCI PCI

3 2 1 0 7 8

DVD Rom Crystal PCI

@9,7 33Mhz

Giga Bit Ethernet

RIO PCI PCI PCI ERI

4 5 6
Sun WQLG Contrôleur FC-AL ebus
i2c bus @2 SCSI

Loop A---- ----Loop B SCSI

FE HG

AB DC
La Crystal PCI card est en option sur la SUN FIRE 880. La Loop B qu'elle génère n'est donc pas toujours existante.