Orange/MEA/NTIS

Networks Technology
& Information Systems

Network Unavailability Ratio

NUR

1. NUR KPI: definition and computation framework

This document describes NUR definition and computation methodology for accurate benchmark.

NUR is a Key Indicator in OMEA Zone to assess networks performance through the Network Elements (NE)
unavailability measurement along a given period.

a) Definition.
 NUR is computed on Radio Access Network only (cell granularity)
 NUR weighted (NURw) is the NUR per technology weighted by the number of cells On-air related to
the given technology.
 NUR combined 2G/3G/4G is the sum of the NURw per technology divided by the total number of
cells 2G/3G/4G On-air.

b) Computation methodology
 Computation basis: NUR is computed such as it includes all sites/cells that are officially On-air and
belonging to the commercial network. This list should correspond to the official list of sites of the
company as declared in the official coverage & mobile service map shared with the national
Authorities.

 New sites not yet integrated (but present and declared in OSS) are to be excluded from NUR
computation until they become On-air (opening of commercial traffic).

 NUR is computed per technology 2G, 3G and 4G without distinction between voice and data
services from both OSS counters and alarms logs along a given period:
- OSS counters provide the total cell-downtime for the whole cells
- Alarms logs related to down cells, allow to categorize NUR per root cause linked to a given
domain: Technical Environment, Transmission, System, Works, Other only if not clear cause,
and Force Majeure (see below), after reconciliation with known incidents, present in ticketing
tool.

NUR per technology

NUR contribution value from TECHNICAL ENVIRONMENT
 NUR Sharing
 NUR Towerco
 NUR Esco
NUR contribution value from TRANSMISSION
NUR contribution value from SYSTEM
NUR contribution value from WORKS
 NUR volontary
 NUR involontary
NUR contribution value from OTHER
NUR contribution value from Force Majeure (Insecurity + Disasters)

1
Release_20190402
 Orange/MEA/NTIS
Networks Technology
& Information Systems
 Exclusions: only 2 cases are considered for Force Majeure, leading to exclusions of the NUR value
created by these cases, regarding the evaluation of objectives
(see below)

Force Majeure
2 exclusions requiring explanations
INSECURITY: Cells impacted by wars, military actions.
DISASTERS: Cells impacted by fire, flood, hurricane, lightning.

 Threshold: Objective < 400, meaning network availability > 99,6%

NUR NAR
(Network Unavailability) (Network Availability)
100 => 0,1% 99,9%
200 => 0,2% 99,8%
300 => 0,3% 99,7%
400 => 0,4% 99,6%

Legend

c) Validation Process

NUR must be validated by:

 SMC Manager : value, comments & methodology
 CTO : value and comments reported to the Group
with the list of exclusions cases (force majeure) considered in the calculation

d) Reporting Process
NUR 2G, NUR 3G, NUR 4G values must be reported on 8th of the month at latest in MORPHEUS by each
affiliate once validation process is over.

This release includes NUR formulas for 2G/3G/4G technologies related to the following vendors :
ERICSSON, HUAWEI, ALU, NOKIA, ZTE.

NB: ALU
ALU 2G : there are no relevant counters for ALU 2G and some workarounds should be found, e.g. with alarms
NB: As NOKIA 3G/4G and ALU 4G are estimated in % (cells availability), NUR= 100- Cell Availability.

2
Release_20190402
 Orange/MEA/NTIS
Networks Technology
& Information Systems

2. NUR Formula : 105 x ∑ (ni x di ) / N x D

2G RAN NUR 3G RAN NUR 4G RAN NUR

5
10 x ∑ ( ni x di ) / N x D
D =Duration of observed period (in minutes)
31 days, D = 44 640 min
30 days, D = 43 200 min
29 days, D = 41 760 min
28 days, D = 40 320 min
100 000 = coefficient to make reading 100 000 = coefficient to make reading 100 000 = coefficient to make reading
easier easier easier
ni = number of 2G cells impacted by ni = number of 3G cells impacted by ni = number of 4G cells impacted by
incident i incident i incident i
di = duration of incident i ( minutes) di = duration of incident i ( minutes) di = duration of incident i ( minutes)
N = total number of 2G cells on air N = total number of 3G cells on air N = total number of 4G cells on air
D=Duration of observation period related D=Duration of observation period related D=Duration of observation period
to unavailability ( minutes) to unavailability ( minutes) related to unavailability minutes)
Scope Scope Scope
- 2G BTS - 3G NodeB - 4G eNodeB
- BSC - RNC - S1-MME
- TRANS Abis interface - TRANS Iub interface (only) - S1-U
(only)
NURw 2G = NURw 3G = NURw 4G
NUR 2G value x nb 2G cells NUR 3G value x nb 3G cells NUR 4G value x nb 4G cells
NUR combined 2G/3G/4G
(NURw 2G+NURw 3G+NURw 4G) / Total number of cells (2G/3G/4G)

3
Release_20190402
 Orange/MEA/NTIS
Networks Technology
& Information Systems

COUNTERS

Computation 2G RAN NUR, 3G RAN NUR, 4G RAN NUR must be automatized from counters and alarms
provided by OSS managers.
The counters below guarantee reliability and completeness of global NUR.

VENDOR COUNTERS COUNTERS

ALARMS ALARMS (unit = minute)
2G
(TDWNACC / TDWNSCAN) * measurement period in minutes (hourly or
daily)
In 2G the counters are stepped each 10 seconds
ERICSSON
(G16B, W17, L17 3G
KPI (pmCellDowntimeAuto + pmCellDowntimeMan) / 60In 3G the counters are
and earlier)
stepped each 1 second

4G
Cell Unavailability time: pmCellDowntimeAuto + pmCellDowntimeMan in
seconds. To be divided by 60 to get NUR in minutes.
2G
Cell out of service duration – R373
1276071423 ; CELL_SERV_OOS / 60 ;
A list of alarms (from SRAN 8) is provided as a complement (to check the
counter value) in the file below:

3G
67204837 : VS.Cell.UnavailTime.Sys + 67199736: VS.Cell.UnavailTime for
HUAWEI
cells locked manually)A list of alarms (from SRAN 8) is provided as a
(SRAN 13.1 and KPI
complement (to check the counter value) in the file below:
earlier)

4G
1526727209 L.Cell.Unavail.Dur.Sys
+
1526727210 L.Cell.Unavail.Dur.Manual
+
1526737853 L.Cell.Unavail.Dur.Sys.S1Fail

ALU ALARM / KPI

2G
A list of alarms which can be used is: ‘Loss of contact with GPU’, ‘RX-TX
[10] RESTART [248], RX-TX [10] RESET [247], RX-TX [10] HW-FAILURE
[239]’.

3G
(VS.Unavailability.Cell.Sum- #73) / 60
(available from UA.8.1) ;
Other possibility in Osiris is to use “CellUnavailability_Cell018_CR” is the
sum of:
• Sub-Counter #0:Disabled due to cell specific outages such as HW
failure, SW failure. - 75_0_TOTAL_CUMULATE
• Sub-Counter #1:Disabled by Operator. - 75_1_TOTAL_CUMULATE
• Sub-Counter #2:Disabled due to Iub outage causing the cell to be
unable to process traffic. - 75_2_TOTAL_CUMULATE

4
Release_20190402
 Orange/MEA/NTIS
Networks Technology
& Information Systems

A list of alarms (the red ones might happen the most frequently) is provided
as a complement (to check the counter value) in the file below:

2G
BCCH_DOWNTIME ID: 002092
Number of seconds the cell does not have an active BCCH and the alarm
7767 (BCCH MISSING) is active.

3G
NUR = 100- Cell Availability
NOKIA
Cell Availability = 100*(AVAIL_WCELL_IN_WO_STATE/
(SRAN 18 and
AVAIL_WCELL_EXISTS_IN_RNW_DB)
earlier
ALARM / KPI 100* sum([M1000C178]) / sum([M1000C180])
only verified on
In 3G: The cell status is sampled per 5 seconds. the counter is incremented
field with SRAN
by 1 for sample
17A)
4G
NUR= 100- Cell Availability
Cell Availability =100*SAMPLES_CELL_AVAIL/DENOM_CELL_AVAIL
100*sum([M8020C3]) / sum([M8020C6])
In 4G: The cell status is sampled per 10 seconds. the counter is
incremented by 1 for sample.

2G
C901080034 - cell down time – Not checked
ZTE KPI
3G
C310464560 - Service Time of Cell

5
Release_20190402
 Orange/MEA/NTIS
Networks Technology
& Information Systems

ANNEX
A. Mobile network Architecture – NUR framework

Network elements taken into account in NUR computation

B. NUR computation example

Let’s consider 2G RAN with following incidents with the following inputs
- period observed : 1 month of 30 days (43200 min)
- network of total 2G cells on air = 2 000
- incidents:
o 1 BTS with 12 cells off during 4 hours (240 min)
o 1 BSC with 300 cells off during 2 hours (120 min)
o 1 BTS with 18 cells off due to planned work during 1 day (1440 min)

100 000 * [ (12 * 4 * 60 ) + ( 300 * 2 * 60 ) + ( 18 * 24 * 60 ) ]

NUR_2G_RAN = ――――――――――――――――――――――――― = 75
2000 * 30 * 24 * 60

C. NOTE
It could be interesting (for internal purposes) to calculate the NUR value obtained from the information
declared in the ticketing tool, in order to compare with the NUR value coming from OSS. It shows the
amount of network events that has been seen captured and reported in ticket by the operational teams
(present in the ticketing tool), giving an indication of the accuracy of their operational work (Front Office
Teams). This ratio between NUR OSS and NUR ticket is not to be reported.

End

6
Release_20190402