NPO Product Overview

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED. ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION

1

9959 Network Performance OptimizerProduct Overview

31 July 2014

� Introduction� NPO Overview, Architecture & KeyFeatures� NPO HW Configurations� NPO Input Data & Import Scheme� NPO Client PC Pre-Requisites

� NPO User Operations & Functions� NPO Analysis Desktop & Light Web Client (no Java)� Fixed/Dynamic Clusters Sites Definition� QoS Counters/Indicators, QoS Views/Reports & QoS Alerters� Logical Parameters, Events, Tuning & Diagnosis

AGENDA

2


� Logical Parameters, Events, Tuning & Diagnosis� Cells Geographical Representation

NPO in brief

• Converged RAN

- All Radio Access technologies, ePC

• Field proven

- More than 100 customers worldwide

- Relevant OPEX reduction

Ultimate Wireless Packet Core

GERAN

GPRS, EDGEE-UTRAN

LTE, TD LTEUTRAN

UMTS, HSPASmall Cells

QoS Informationrecovering

Tuning

30%10%45% saved

3


• High Definition QoS

- Per call/per device/per subscriber (Via LTE PCMD or WCDMA call trace)

- SON enablers

Resourceconfiguration

Analysis /diagnostic

30%30%20%

15%

15%

5%

Excellence in Performance High Definition QoS Multi-standard

NPO HP-Small NPO HP-Medium

12,000 cells

HP DL380 G7 2 CPU /72Gb RAM / 12 SAS 300Gb HD /

12 SAS 600 Gb HD (D2600)

48,000 cells

HP DL580 G7 4 CPU /

256 Gb RAM / 48* SAS 600Gb

+ 1 auxiliary server for QoS loading

HP DL380 G7 2 CPU /36Gb RAM / 12 SAS 300GbHD

NPO HP-XLarge

3,000 cells

HP DL380 G7 1 CPU / 36Gb RAM /12 SAS 300Gb HD

D2600

DL380

DL380

DL5801,500 cells

NPO HW Configurations

4

DL380

DL380

DL380

DL380

D2600

D2600

D2600

D2600

D2600 DL5801,500 cells

If WCT/PCMD option is activated

(smaller capacity but without any additional hardware)

+ 1 auxiliary server for WCT/PCMD

option


+ 2 auxiliary servers for WCT/PCMD


New platforms based on proven performance-leading Intel x86 CPUs

NPO Analysis Desktop (PC Java needed):

� Cluster/CellsZone definition

� QoS Data Customization: Counters/Indicators & Reports

� Scheduling reports

� QoS Alerters

� User preferences

� Events & Parameters

� Rules Checking & Tuning Sessions

� Diagnosis

NPO Web Client (no Java needed):

NPO KeyFeatures

5


NPO Web Client (no Java needed):

� QoS analysis by Indicators & Reports

NPO Administration:

� Create users and assign profiles

� NPO processes

� Import RASTER maps

� Detailed/Log Viewer

NPO Cartography:

� Cartographic display

� Thematic Layers

NPO PCMD (optional):

� PCMD Browser and RealTime web interfaces

� PCMD Localization with Google Map (LR13.3)

NPO NUART (optional):

� Unavailability / Outages statistics

� Degradations detection

9959 NPO KPIs

QoS reports

QoS alerts

Diagnosis results

Statistics and trends

Resource Monitoring

Report builder

Geographical information systemEngineering

Geographical information

Own Metrics

NPO Input/Output Data Type

Customization Data

6

e-NodeB BSCBTSNodeB RNC MME

Call history.Measureme

ntsConfiguration Data

Alarms

P-GW

Availability statistics

Parameter Tuning

Diagnosis engine

Engineering Rules

Automatic Import Data

Output Data

Light Web ClientFull Client app(Analysis Desktop)

PCMD BrowserPCMD Real TimeIndicators & ReportsEditor

NPO Components

7

DiagnosisRule checking,

Events,Parameters tuning

Geographical representationNetwork

Unavailability

QoS Alerters

NPO License per each (sub)Component

8

5620-SAM

9959 NPO QoS-PM

M5 NPO

PCMD/1minTopo &

Alarms/dailyMME1

eNB1

eNBn

PM files: /storage/var/spool/mi/pmPCMD files: /storage/pcmd

PM/15min

PM/15min

PM/15min

SGW/PGWPM/15min

NPO Import PM/PCMD/Alarms

PCMD/1min

PCMD/1min

HSS

9


MMEn

eNB1

eNBm

NPO PCMD/NUARTM5 NPO

Client (java 1.6)

NPO imports the SAM topology every midnight.

NPO imports the MME-PCMD files every 1 min

from all MMEs.

PM files: /storage/var/spool/mi/pmPCMD files: /storage/pcmd(no intermediate SAM server for

MME-PCMD files)

••

PCMD/1min

PM/15min

PCMD/1min

NPO Main/AUX

NPO QoS-PM(General KPI Indicators / 15 min load)

through SAM to get all eNBs/MMEs/SGW/PGW - PM files

measurements

NPO PCMD

(Troubleshoot KPI indicators / 1 min load)

Directly from MMEs

NPO NUART (Stability/Availability KPI Indicators / daily load)

Through SAM-O

PCMD ACTIVATION on eNBs/MMEs:PM Files on eNBs/MMEs:LASER Files on eNBs (Alarms/Events)

NPO Import PM/PCMD/Alarms

10


PCMD Activation on MME (with its web interface):1) Login the MME CNFG node 2) Choose the "PCMD Configuration" in the left menu. Open it in the Central Panel.3) Choose the "update" in Actions option. Click Update.

PCMD Activation on eNB (by SAM):1) Choose eNB in SAM, right click to select [Property] 2) In ENB Base Configuration, click [Property] 3) In “Components” tab, select eNB instance and expand ActivationService / “ActivationService id” 4) Double-click on “ActivationService id” and set “isPCMDEnabled”=true.

By default activated on eNBs/MMEs with SAM policy.Collected by SAM each 15 min.Requires SAM Preparations.

(Alarms/Events)

Requires SAM Preparations:- SAM-O license activated- oss_client/oss_group on SAM- lteran policy

Identify the high runner(s) UEs/Vendors

high runner(s)

NPO Import Follow-Up – eNB PM files

Every 15min import

11


Lost eNB PM files can be caused by:-eNB reset/outage/ReachabilityProblem or problems with S1 transport => SAM alarm raised: missedStatsCollection.-related PM policy = stopped on SAM or even SAM server is not available.- NTP synchro lost between eNBs/Sam/NPO

NPO Import Follow-Up – ALARMS files

Daily import

12


State Change shows the SAM alarms import (ENBDown, LTECellDown, ReachabilityProblem). If 0, no NUART indicators values. Alarms/Events shows the eNB events/alarms. If 0, no events are imported => difficult to identify the root cause of an outage.Topology show the SAM snapshot files import. Hardware Inventory column is not implemented in LTE.

More details about State Change import issues in NPO server: /alcatel/muse/data/trace/LTESamData*.traces

Open the Control Panel => JavaSet Java => Network Settings => Proxy as Direction Connection (mandatory setting)

•Clear Java cache•Remote temporary Java files

For Internet Browser, disable the Block Pop-up option.Example for Mozilla Firefox (that option is not selected):

Check that Firefox Add-Ons has Java activated:

NPO AD Pre-Requisites: PC Java Settings & PC Profile Memory

13


If NPO AD doesn’t start, switch to MEDIUM memory profile for your PC:⇒ Click on the user name – already logged in.⇒ Select second option (by default, is MAX option)

� Introduction� NPO Overview, Architecture & KeyFeatures� NPO HW Configurations� NPO Input Data & Import Scheme� NPO Client PC Pre-Requisites

� NPO User Operations & Functions� NPO Analysis Desktop & Light Web Client (no Java)� Fixed/Dynamic Clusters Sites Definition� QoS Counters/Indicators, QoS Views/Reports & QoS Alerters� Logical Parameters, Events, Tuning & Diagnosis

AGENDA

14


� Logical Parameters, Events, Tuning & Diagnosis� Cells Geographical Representation

Drag and Drop

NPO Analysis Desktop (AD): Complete GUI

15


Drag and Drop

2 reportDrop zones

Propagation

Network

objectsFunctions

Cartography, Diagnosis,

Modes

NPO AD: Simplified GUI

16


Executed

View

Cartography, Diagnosis,

Tuning Session & Reports

Auto-refresh

Excel Export

NPO AD: Simplified GUI / Views

17


Excel Export

NPO Web Client: Views (PC w/o Java)

Network elements

https://<NpoMain_IP_addr>:8443/maat/webclient

18


Function: view template

Output: tabular/ graphical chart

NPO AD: Preparing a View Template

19


Drag and Drop

You can change the user display by font type ,font size, TZ, show deleted objects or not, shortcuts to add cells into reports, default chart format, adjacencies links color, allow interpolation, etc.

NPO AD: User Preferences

20


Typical KPIs Dashboard for Network Performance

PM RRC Connection Setup Success Rate 99.41% 99.25% 99.55% 99.85% 99.93% 97.81% 98.23% 99.15%

PM RRC Connection Blocking Rate 0.00% 0.00% 0.02% 0.05% 0.00% 0.00% 0.00% 0.01%

PM ERAB Initial Setup Success Rate 99.44% 99.49% 99.28% 99.37% 99.72% 99.24% 99.22% 99.39%

PM S1 Connection Estab. Success Rate 99.42% 99.70% 99.41% 99.20% 98.37% 96.57% 97.89% 98.65%

PM UE Context Setup Success Rate 99.44% 99.49% 99.28% 99.37% 99.72% 99.24% 99.22% 99.39%

PM ERABs All Drop Rate 0.13% 0.39% 0.12% 0.14% 0.15% 0.29% 0.15% 0.20%

PM UEs Context Drop Rate 0.39% 0.54% 0.19% 0.30% 0.19% 0.59% 0.20% 0.34%

PM Total HO Success Rate [%] 96.93% 95.16% 97.07% 96.43% 98.50% 97.86% 96.82% 96.97%

PM S1-Interface Handover Success Rate [%] 98.28% 98.40% 98.26% 98.40% 98.02% 93.74% 95.42% 97.22%

PM X2-Interface Handover Success Rate [%] 99.41% 99.25% 99.55% 99.85% 99.93% 97.81% 98.23% 99.15%

PCMD Tracking Area Update Fail Rate [%] 0.15% 0.13% 0.33% 0.43% 0.81% 1.55% 0.26% 0.52%

PCMD Paging No Response Rate [%] 0.13% 0.23% 0.48% 0.44% 0.91% 1.35% 0.21% 0.54%

PM DL MIMO Ratio [%] 33.18% 43.10% 28.18% 35.77% 33.82% 47.18% 21.18% 34.63%

PM DL RLC Retransmission Rate [%] 1.18% 2.13% 1.17% 1.16% 1.15% 1.17% 1.16% 1.30%

PCMD DL HARQ Retrans Rate [%] 0.18% 0.13% 0.17% 0.16% 0.15% 0.17% 0.16% 0.16%

Past 7

days

ACCESSIBILITY

RETAINABILITY

MOBILITY

QUALITY

11/4KPI / eNB_clusterKPI ClassNPO 11/711/1 11/2 11/3 11/5 11/6

21


PCMD DL HARQ Retrans Rate [%] 0.18% 0.13% 0.17% 0.16% 0.15% 0.17% 0.16% 0.16%

PM DL Block Error Rate [%] 0.18% 0.53% 0.17% 0.56% 0.15% 0.57% 0.16% 0.33%

PM UL Block Error Rate [%] 0.78% 0.83% 0.70% 0.65% 0.15% 0.57% 0.96% 0.66%

PM Avg RRC Connected per AllCells 11.4 11.3 17.5 13.7 9.2 10.3 11.2 12.1

PM Max RRC Connected Users 19 22 32 25 28 16 18 22.9

PM DL RLC Traffic Volume [GB] 26.75 18.24 51.87 46.71 59.58 47.50 23.92 39.22

PM UL RLC Traffic Volume [GB] 24.81 13.73 25.61 24.18 39.19 32.71 11.32 24.51

PM Peak DL Throughput [kbit/s] 23,456 27,656 23,456 27,656 23,456 27,656 27,656 25,856

PM Peak DL Throughput >5Mbps Ratio [%] 32.18% 25.53% 73.17% 54.56% 23.15% 67.57% 12.16% 41.19%

PM Peak UL Throughput [kbit/s] 13,436 7,656 3,456 7,856 9,456 8,656 5,656 8,025

PM Peak UL Throughput >5Mbps Ratio [%] 7.18% 5.53% 3.17% 4.56% 2.15% 6.57% 1.16% 4.33%

PCMD Avg UE Attach Duration [msec] 980 785 1024 947 969 983 997 955

PCMD Avg UE Auth Duration [msec] 234 250 243 247 252 255 258 248

PCMD Avg UE Service Request Duration [msec] 190 212 202 205 198 199 218 203

NUART Avg Global Availability per eNB [%] 100.000% 99.939% 100.000% 100.000% 100.000% 99.805% 99.521% 99.895%

NUART Avg Unplan Availability Rate per eNB [%] 100.000% 100.000% 100.000% 100.000% 100.000% 99.984% 99.990% 99.996%

NUART Avg S1 Transport Downtime Rate per eNB 0.00% 0.00% 0.00% 0.00% 0.00% 0.10% 0.32% 0.06%

NUART Avg X2 Downtime Rate per eNB 0.00% 0.00% 0.00% 0.00% 0.00% 0.05% 0.07% 0.02%

STABILITY

QUALITY

CAPACITY

LATENCY

KPIs Availability Domains

� Measurements Constraints� Some measurements are present only per Cell (RSRP/RSRQ, HARQ & Avg RLC Tput)� Some measurements are present only per eNB (CPU/RAM, Transport, Alarms, S1/X2 traffic)� Some measurements are present only per MME (Attach, Paging, TAU, Auth, Bearers).

� NPO-PCMD has extended domains per many indicators (Paging, TAU, Auth, HARQ) also at CELL/IMSI levels.

� Solution is to use the MultiNET option.� Create cellzone(s), eNB object zone(s)

& MME Pools� Drag-drop them on MultiNET basket.

22


Typical KPIs Dashboard for Network Performance

23


KPIs Analysis Domains – by PM /PCMD / NUART

KPI Class Default Indicators / PM Data Additional Indicators / PCMD Data Stability NUART Data

Accessibility RRC Cnx Success/Fail Rate -

RRC Cnx Blocking CAC Fail Rate -

ERAB Setup Success/Fail Rate -

S1AP Estab Success/Fail Rate - check S1CINTERFACE_SOU_available_rate

UE Context Setup Success/Fail Rate Initial Attach, UE/HSS Authentications, PDN conn

Capacity RRC Connected Avg -

RRC Connected Tmax -

Retainability ERAB Context Drop Rate per QCIx UE Context Releases: Normal/Abnormal

Radio Link Failures per cell UE Context Releases: root causes details check CELLLTE_SOU_available_rate

UE Context Release: IRAT Redirection, RLF,

User Inactivity, Congestion

Mobility all Intra-Inter eNB/MME/SGW HO HO Interruption Time Distribution (daily/cell) check CELLLTE_SOU_available_rate

Cell reselections HO Succ/Fail per every adjacency

24


Cell reselections HO Succ/Fail per every adjacency

RRC ReEstablishments Setup

Paging/TAU per MME Paging/TAU per cell/cellzone/eNB/MME

RADIO MIMO Eligibility DL MIMO/TxDiv ratio per UE scheduled

Quality Modulation: QPSK/QAM16/QAM64 ratio RSRP/RSRQ/RTD Distribution (daily)/cell

Modulations/Trans. mode (MIMO, TxDiv) RF Vector Matrix - RSRP/RSRQ & RSRP/RTD

BLER/HARQ/RLC Retransmissions BLER/HARQ per cell/IMSI

UL Noise Interferences

UL Power Headroom

Tput DL/UL RLC Throughput per cell DL/UL RLC Throughput per IMSI

Traffic DL/UL RLC Traffic Volume per cell DL/UL RLC Traffic Volume per IMSI

Analysis High runner cells Breakdown CELL -> IMSI

Breakdown CELL -> UE Vendor (iPhone, Samsung)

No eNB PM files loaded (due eNB isolated) check ENODEB_LOS_unavailable_rate

KPIs – Linear Trend Evolution

Right click on chart and choose

25


and choose Dynamic Trends

Trend of AvgConnected userswith DL traffic .

KPIs – Dynamic Trend Evolution with Sliding Window

Right click on chart and choose

26


and choose Dynamic Trends

Trend of AvgConnected userswith DL traffic .

NPO Dashboard

Since LR13.1: entire network dashboard

27


dashboard

Busy Hours Topic

Busy Hours is the period of day when there is

- Max/Intensive RLC traffic (downtown between 8:00 – 18:00)

- Many nb of users per cell (near a stadium)

- Many HOs in a short time – closing the stadium game

Detection of the Busy Hours

28

- Max Hour Position

Execution of Indicator at the Busy Hours

Busy Hours – Identify Max Hour Position for All RLC Traffic

29

NPO / Hourly RRC Connected State Tmax

30

NPO / RRC Connected State Tmax at RLC Traffic Busy Hours

31

RRC Connected State Tmax at

Busy Hours for all RLC Traffic.

Daily monitoring with NPO allow to detect issues/degradation on the network

• Once a failure type is detected with QoS-PM, investigation is required by:

- Checking if the issue is due to a single/few cells or if it’s all over the network

- Identifying the time period of the degradation

- Breakdown (per UE/vendor) to a specific failure cause (Initial Attach Reject Failed)

NPO Monitoring Guidelines

32

Further troubleshooting can be done with NPO-PCMD (or NPO-NUART)

- PCMD allows a breakdown to a specific UE type or IMSI.

Example: UE Context Drop Rate has a higher value on Nokia Lumia 920.

- NUART useful to correlate degradations seen with alarms raised at that time (e.g. eNB SW upgrade, cell = locked, eNB/CEMx is down, etc). Example: maintenance tasks on a given site can create a high HO failure rate.

NPO includes a functionality called CellZone/ObjectZone to define a cluster/market of cells or eNBs - which allows user to check QoS Indicators, Reports, etc.

Static Cellzone having a fix number of cells

Dynamic Cellzone having an Indicator condition:

RRC cnx succ rate < 98%

NPO Clusters Definition

33

Variable number of cells in this Cluster

Dynamic Cellzone-2 quickly identified the 3 worst sites.

QoS Indicators with Thresholds: Quick Problem Detection

34


CELLLTE_SOU_supp_unavailabile_rate with thresholds:Example: <0.05% - green, <0.1% - yellow, <0.2% - orange, >=0.2% red

Drag and Drop

Auto SelectOf Interesting

Objects

• They are defined to detect QoS problems and generate QoS alarms, depending on reported eNB Performance Measurement data.

NPO QoS Alerters

QoS Alerters are used to highlight no data import or dense urban areas with no

traffic.

35


• Variation detection (taking into account average values) at 15 min granularity.

• Resulting QoS alert is integrated into SAM active alarm flow.

NPO QoS Alerters

QoS Alerters based on this indicator: no RRC/S1AP/HO.

36


QoS Alerter topology

cells/eNBs list.

NPO QoS Alerters

QoS Alerters list & definition.

37


QoS Alerter status.

View

Report Indicators or

• NPO is natively provided with a rich set of views so you have notto create new views in NPO

• More than 120 views for LTECell and 180 views for the MME are

NPO AD: Reports Content

38


View

Report Indicators or parameters

the MME are available !!!

• If there are not exactly the required views you can modify an existing views.

Mono-Obj. Evolution

• It is the evolution of one Network Object (MME, LTECell) in function of the time.

Multi-Obj. Comparison

• It is the comparison of several Network Object in a fixed window of observation

Week21Week22Week23Success rate comparison between Cell1, 2 and 3

Cell1 Cell2 Cell3

NPO AD: Types of Reports

39


Evolution of the Success rate for Cell1

Week21Week22Week23Success rate comparison between Cell1, 2 and 3 for the Week 22

Warning

• Specific TopN report where each view is filtered according to its filtering indicator and sorted according to its sorting indicator.

Warning Reports Top N

Filtering onvariation Value

Best / Worst

Filtering oncolor Value

Additional function allows to detect eNB SW changes

NPO AD: Events

40


This function allows to detect eNB parameters changes

NPO AD: Parameters Change

41


ModifiedParam

This function checks the activation of some features with operational values.

NPO AD: Rules

42


Modification of network parameters and create the Work order file (like WiPS).

WorkOrder file is sent to SAM (to be applied / double-checked with WiPS).

SAM server location: /opt/5620sam/server/nms/activation/wo_import

NPO AD: Tuning Sessions

43


• Diagnosis are useful to diagnose and provide a solution to network problems

• Trigger can be linked to:

• Indicators (Diagnosis)

• Parameters (Complex Rules)

• Diagnosis results can be:

• No problem found ( )

NPO AD: Diagnosis

44


• No problem found ( )

• Unknown ( )

• Problem found ( )

Import a RASTER map (with local city/market) in NPO Cartography and drag-drop the cells on the map based on chosen thematic layer (colorized model).

NPO AD: Geographical Representation

45


Capacity & Mobility

L1/L2 Traffic and Throughput

RRC connection

UE context managementX2

NPO Counters Families

46


SCTP / S1 Transport

Paging

MME

SGW

Counter Highlights:

• Periodically (each GP – Granularity Period of 5mn, 15mn, 30mn, 1h), a network element generates a PM XML file (Performance Management file in xml format) – SAM collects all the XML files from all network elements.

- Network elements are eNodeB, MME, MI, S-GW and P-GW

- 15mn GP is the recommended value (NPO capacity for 5min will decrease due to storage increase)

• PM XML file:

NPO Counters

47


• PM XML file:

- Contain counter names and values

- Counters are compliant with 3GPP standard (TS 32.404)

- PM XML file is based on GMT time

- If processed manually, local time zone shift must be applied to have it on local time

- In NPO counters are available with local time.

A counter is specified with:

• Name: follows 3GPP format (TS 32.404) and is present in PM XML file (ex: RRC.ConnEstab.Cause)

• Reference identity: used by NPO mainly to have better process performances

• Type: Cumulative, Discrete Event Registration (or VALUE) and Load

• Unit: KiBytes, kbits/s, %, Packet, Event, Bearer, User

A counter can be:

NPO Counters

48


A counter can be:

• A simple counter. The reference identity is LCXyyyyy.

- Ex: VS.RrcConnectionSuccessSum (LC12302)

• A subcounter. The reference identity is LCXyyyyy_zz.

- Ex:

- VS.RrcConnectionRequest.EmergencyCallAttempts (LC12311_0), VS.RrcConnectionRequest.HighPriorityAccessAttempts (LC12311_1)

Mobility

X2 Traffic and Throughput

NPO Indicators Families & Storage Duration

Storage Duration:

49


Storage Duration:

• The periodicity for indicators is 5mn, 15mn, 30mn, 1h, 1day, 1week, 1month

• History kept per periodicity is:

- Periodicity <=1hour � 32 days in the past

- Periodicity Day � 400 days

- Periodicity week � 14 months

- Periodicity month � 36 months

Indicator Highlights:

• NPO processes PM XML file to extract the counters values (also called raw data) => each counter is associated to one basic indicator

• Indicators are specified with a name and reference identity

• From NPO point of view, there are 2 types of indicators:

- Stored indicators: Counter with a different set of temporal/spatial aggregation => NPO stores those values in the database

NPO Indicators

50


- Calculated indicators: these indicators are formula of indicators and are computed “On Live” (never stored)

• Each basic indicator has its associated spatial and temporal aggregation method

• NPO has predefined indicators (system indicators updated for each ALU LTE SW release)

• Any rate indicator can apply thresholds.

Documents

NPO Product Overview