9959 NPO PCA Customer - Product - Overview PDF

NPO Per call analytics
Customer Product Overview
March 2014
NMS/NIO/INF/043090 V01/EN
9959 NPO PER CALL ANALYTICS MARCH 2014
Copyright © 2011 by Alcatel-Lucent. All Rights Reserved.
About Alcatel-Lucent
Alcatel-Lucent (Euronext Paris and NYSE: ALU) provides solutions that enable service
providers, enterprises and governments worldwide, to deliver voice, data and video
communication services to end-users. As a leader in fixed, mobile and converged broadband
networking, IP technologies, applications, and services, Alcatel-Lucent offers the end-to-end
solutions that enable compelling communications services for people at home, at work and on
the move. For more information, visit Alcatel-Lucent on the Internet: http://www.alcatel-
lucent.com
Notice
The information contained in this document is subject to change without notice. At the time
of publication, it reflects the latest information on Alcatel-Lucent’s offer, however, our policy
of continuing development may result in improvement or change to the specifications
described.
Trademarks
Alcatel, Lucent Technologies, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of
Alcatel-Lucent. All other trademarks are the property of their respective owners. Alcatel-
Lucent assumes no responsibility for inaccuracies contained herein.
Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

2 / 26
CONTENTS
1 INTRODUCTION ................................................................................................ 4
1.1 SCOPE OF THIS DOCUMENT ...................................................................................... 4
1.2 AUDIENCE FOR THIS DOCUMENT ................................................................................. 4
1.3 EXPIRY ........................................................................................................ 4
2 LTE PER CALL MEASURMENT DATA (PCMD) ............................................................... 4
2.1 WHAT IS PCMD ............................................................................................... 4
2.1 WHY THIS APPROACH ? ......................................................................................... 6
2.2 EXAMPLES USE CASES ........................................................................................... 7
2.2.1 Use case: Using PCMD to troubleshoot customer issues ...................................... 7
2.2.2 Use case: Using PCMD for device analysis ...................................................... 8
2.2.3 Use case: Real time monitoring ................................................................. 9
2.2.4 Use case: Flexible counter ......................................................................10
2.2.5 Use case: Understanding failure ...............................................................10
2.2.6 Use case: VIP monitoring .........................................................................11
2.2.7 Use case: IDENTIFYING CUSTOMER that HAVE HIGH FAILURE RATE ........................11
2.1 PCMD IN 9959 NPO .........................................................................................11
3 LTE CALL TRACE, RF TRACE AND POST PROCESSING TOOLS ........................................ 12
3.1 ENB TRACING OPTION .........................................................................................12
3.1.1 Call traces..........................................................................................12
3.1.1 RF traces ...........................................................................................14
3.1 WCDMA TRACING OPTIONS ...................................................................................14
3.1 WCDMA SMALL CELL TRACING ................................................................................15
3.2 GSM TRACING OPTIONS .......................................................................................16
3.1 DATA COLLECTING OPTION ....................................................................................16
3.1.1 WMS .................................................................................................17
3.1.2 SAM call trace auxilliary server .................................................................17
3.1.3 TCE (Trace collection Entity) ...................................................................17
3.2 9958 WTA CALL TRACE ANALYSIS .............................................................................19
4 APPENDICES .................................................................................................. 23
4.1 APPENDIX A: GLOSSARY OF TERMS .............................................................................25
4.1.1 Acronyms ...........................................................................................25

3 / 26
1 INTRODUCTION
This document describes the tracing capabilities of Alcatel-Lucent RAN, as well as analysis
tools to analyze them, the NPO per call anaytics tools:
 9959 NPO PCMD (Per Call Measurement Data)
 9959 NPO TCE (Trace Collection Entity)
 9959 NPO WCT (Wcdma Call Trace)
 9958 WTA (Wireless Trace Analysis).
1.1 Scope of this document

This document describes the tracing features of Alcatel lucent the Wireless offer up to
LR14.1L / LR14.2W as well as the post processing capability : 9959 NPO (up to NPO 6.1 and
TCE 3.1) and 9958 WTA (up to WTA 10.1).
1.2 Audience for this document

This document is intended to provide an overview to Alcatel-Lucent Customers during pre-
sales activities. This information is typically shared with Customers under NDA conditions
for technical clarifications during discussions and for support of tender request activities.
1.3 Expiry
This document is released on a quarterly basis, and readers should obtain the latest
version prior to use. This document version has no expiration date. However, an updated
version may be released.
2 LTE PER CALL MEASUREMENT DATA (PCMD)
2.1 What is PCMD
Per Call Measurement Data (PCMD) is an E2E solution involving Alcatel Lucent eNB and
PCMD to be able to collect data on all calls for ALL UE calls at ALL times.
The PCMD data is not a dump copy of the control plane message but a summary taking into
account many aspect of the call:

4 / 26
 Identification (which IMSI, IMEI, cell, MME, SGW…)
 Control plane (which procedure, success or failure, duration…)
 User plane (volume per QCI, retransmission)
 RF information (RF quality measurement)
The PCMD data is collected both by the MME and eNB. The part collected by eNB is sent to
the MME via the S1 link, and then the MME adds the data that it has collected and provides
a unique stream.

5 / 26
The result is a CSV file produced by MME containing details information per cell.
2.1 Why this approach ?

Instead of PCMD, some vendors propose to relies on call trace and probe instead:

6 / 26
Figure 1 Probe based design
This approach is supported by Alcatel-Lucent (via 9959 NPO TCE option) and relevant
efficient for “RAN centric” use cases, but is less efficient than PCMD for an E2E view:
 PCMD record contains a very rich set of per UE information (control plane, but
also RF information and user plane), whereas probe based solution usually focus on
user plane
 Doing real time correlation of the RAN and MME data is a complex integration
project requiring significant processing power, whereas the PCMD approach is does
not require additional integration effort nor hardware with Alcatel-Lucent eNB
and MME
 Instead of mirroring all RRC control plane to the OAM link, PCMD provide a
summary of the call : less impact on OAM backhaul
2.2 Examples use cases
2.2.1 Use case: Using PCMD to troubleshoot customer issues
Issue: A subscriber complained of repeated dropped calls. His location was noted as a high
rise building in a remote city (an area where no RF engineers are located)
Solution:
• Technicians examined PCMD call records for the previous 2 days and saw: while in
his office he had some drops due to RF (Loss of continuity in RF Traffic path) while on
sector 3 of the site xxx and earlier that day while also in his office he made calls on sector
2 of the site xxx2

7 / 26
• From the previous days data the same customer had also made calls & dropped
them on xxx3 and within a minute he had setup a new call on xxx2.
• These 2 sectors were not designated as neighbor, as past drive testing at ground
level showed these 2 sectors did not interfere with each other -- but this customer was on
level 11 of a high-rise where the cells do overlap
• The cells were designated as neighbours and neighbored the customers call
performance was monitored. No more dropped calls were noted while he was at his office.
• The technicians reported that using PCMD records “... took 2 hours to resolve.
Normally a remote issue can take up to 5 days to resolve as a drive test team would be
dispatched.”
2.2.2 Use case: Using PCMD for device analysis
Issue: Many bugs are due to interaction with specific UE type
With PCMD ,KPIs can be computed per UE type. This facilitates device troubleshooting – is
it the network or is it the device?
PCMD allows KPI per UE type tracking so new UE/device introduction can be monitored.
For example the graph show the failed attempt per device type over a few week.
It is also possible to calculate call drop rate or metrics related to RF quality per device
type.
UE Model 1 UE Model 3 UE Model 2
5.00%
4.50%
4.00%
3.50%
3.00%
2.50%
2.00%
1.50%
1.00%
0.50%
0.00%
w17 w18 w19 w20 w21 w22 w23 w24 w25 w26
UE Model 1 Attempts 10.21 10.21 10.21 15.09 19.36 19.36 29.87 44.14 50.65 56.01
Other methods cannot provide this level of visibility:

8 / 26
 Some probes have access to device type information, but don’t have access to RF
information
 Counter are not reported per device type.
2.2.3 Use case: Real time monitoring
Issue: A failure in MME, SGW or the transport network can create “black out” in large area
of the network. In some cases of silent failures no alarm may be raised;
Solution: 1 minute KPI on initial attach failure rate, call drop, service request can be
displayed in real time, as well as the last hour (with a sliding windows).
This ensures quick reaction.
• Thresholds can be adjusted (CDR, SRFR, IAFR)
• Alerter can be defined on real time monitoring (1 minute GP Alerter)
• Table summarizes Last Minute and Last Hour data, per MME Pool
• Gauge displays the 3 main KPIs using a specific coloring (Mouse over to see values)
• Individual charts display details for a given KPI (as a line) and its corresponding
“volume” KPI (bar chart) during the last 60 minutes

9 / 26
2.2.4 Use case: Flexible counter
Issue: Alcatel-Lucent RAN equipment provide thousand of counters … however there are
always dedicated counter needs that are not supported by the RAN.
Solution: “Counters” can be derived from PCMD data. This can be done by configuration
file in NPO without impacting the RAN.
2.2.5 Use case: Understanding failure
Issue: Identify the main contributors to failure (call drop…)
Solution: Use PCMD counting to dynamically drill down into the data, for example seeing
that a single UE is making repeated failed attempts, or that some specific SGW is having
high failure rate…
A more sophisticated case is to analyze the KPI for 2 RAN setting when RF condition are the
same. For that call records exhibiting the same RF data are processed separately. KPI can
then be compared more accurately: only the effect of the RAN settings are visible, they
are no more mixed with effect due to bad RF quality.

10 / 26
2.2.6 Use case: VIP monitoring
Issue: VIP needs dedicated care, identifying quickly issues.

Solution:
 KPI are calculated for a list of IMSI
 Threshold crossing alarm can be defined
 Raw PCMD data for investigation is available
2.2.7 Use case: IDENTIFYING CUSTOMER that HAVE HIGH FAILURE

RATE
Issue: a single IMSI is repeating call attempts, that are rejected by MME due to particular
configuration of this IMSI/UE.
This creates:
 Bad KPI on the cell where is the customer
 Bad experience for the customer
PCMD allows to identify the behavior, and to correct it, or at least to understand why a
particular cell has a high failure rate.
2.1 PCMD in 9959 NPO

The PCMD option of 9959 NPO is a ready to use post processing solution for PCMD.
It continuously analyze PCMD file. The use case described below are supported by 9959
NPO.

11 / 26
NPO PCMD provides ability to:
 Create counters and KPI based on PCMD
o per cell, per eNB, per SGW,
o On a select set of IMSI (“monitored IMSI”, up to 5000)
o Per device type
o Per hand over relation
 Show in real time kpi on MME health (see use case on real time monitoring)
 Store some PCMD record, related to failure or to a selected list of cells (up to
300) and IMSI (up to 5000), on these stored record, additional use case are
possible:
o Direct viewing of PCMD records
o Ad hoc query (counting & summing of the record on any criteria)
The same NPO platform is used for regular PM (NPO service assurance) and PCMD, allowing
to understanding all Qos issue from a single platform.
3 LTE CALL TRACE, RF TRACE AND POST PROCESSING

TOOLS
3.1 eNB tracing option
eNB supports a rich set of tracing option supporting both L1/L2 and L3. The tracing
capability of macro and metro eNB are the same.
3.1.1 Call traces
Alcatel Lucent implements call trace as defined by TS 32.421, TS 32.422, TS 32.423 and
related standard.
To quote 3GPP “Subscriber and equipment trace provide very detailed information at call
level on one or more specific mobile(s).
This data is an additional source of information to Performance Measurements and allows
going further in monitoring and optimisation operations.
Contrary to Performance measurements, which are a permanent source of information,

trace is activated on user demand for a limited period of time for specific analysis
purposes.

12 / 26
Trace plays a major role in activities such as determination of the root cause of a
malfunctioning mobile, advanced troubleshooting, optimisation of resource usage and
quality, RF coverage control and capacity improvement, dropped call analysis, Core
Network and UTRAN end-to-end UMTS procedure validation.
The capability to log data on any interface at call level for a specific user (e.g. IMSI) or
mobile type (e.g. IMEI or IMEISV) allows getting information which cannot be deduced
from Performance measurements such as perception of end-user QoS during his call (e.g.
requested QoS vs. provided QoS), correlation between protocol messages and RF
measurements, or interoperability with specific mobile vendors.”
An important thing to notice is that per 3GPP design, the eNB is not aware of the
IMSI/IMEI, hence tracing on a specific IMSI/IMEI can only be done via MME via an S1
signaling message.
Alcatel Lucent eNB and MME supports this standard message, so tracing on a specific
IMSI/IMEI works:
 When Alcatel Lucent provides eNB and MME
 When Alcatel Lucent provides the eNB (in this case the MME must send the S1
message to start call trace)
 When Alcatel Lucent provides the MME (in this case the eNB must correctly handle
this S1 message)
eNB support the minimum and maximal level of tracing, the difference being that the
minimum level does not trace RRC measurement report.
It is possible select the list of interface traced:
 RRC
 S1
 X2
It is possible to trace all calls of the eNB or to set a limit on the number being traced;
As per 3GPP, call trace is related to “a mobile”, so only message associated to a mobile
are traced (RF Trace should be used for common message)
The file format is compliant with 3GPP TS 32.422 R11 XML “type A”
To collect the call trace (i.e. to provide the XML file), it is needed to have either:
 SAM call trace auxiliary server

13 / 26
 9959 NPO TCE option
3.1.1 RF traces
RF trace is a new tracing mechanism available on eNB, it has several advantage over call
trace:
 It contains a correlation structure indicating the MME S1AP Id used, enabling
correlation with data captured by probe at core network level
 It contains also the cellId, allowing to know to which cell is related a given call
(with call trace a decoding of the S1 message is needed to know the cell)
 It contains L1 and L2 information
 At RRC level, it is possible to trace only the measurement report or all calls,
depending on what is needed.
RF trace can also be enabled on all eNB all the time (if enough backhauling capacity and
enough hardware at TCE level to post process it)
3.2 WCDMA tracing options

WCDMA provides rich tracing capabilities:
 Geographical Call Trace (CTg) & Access Invoked Call Trace (CTb)
o Activated on a list of cells (or the whole RNC), sample calls that are traced
or on a given IMSI (CTb). 10 calls per TMU
o Contains control plane and optionally some user plane
o Optionally contains geographical position (GPS)
 Real Time Call Trace (RTCT):
o Similar to CTb but content reported in real time
o In WCE, CTb is reported in real time, so CTb is used instead of RFCT
 Call failure trace
o Snapshop generating at each failure (drop or other failure)
o Contains all the information known by RNC at this time
 Neighbouring Call Trace (CTn);
o Used to monitor and optimize neighboring relations;

14 / 26
o For tracing calls moving inside a defined area;
o Calls are traced as soon as the RNC remains the SRNC and the session is
active.
 Object Trace (OT) – Cell, IuCS, IuPS, IuR, IuBC;
o Used to trace events related to network elements or interfaces (not to

calls);
o Several type of OT: Cell, IuCS, IuPS, IuR, IuBC;
 Emergency call tracing (Call trace A)
o Emergency calls are traces (typically in a permanent basis)
 Protocol Trace (PT)
o Control plane message for 100% of the calls
o For 9370 RNC only
It is also possible to have localization data in the CTG & CTb call trace. This feature
leverage the SMLC embedded in RNC : control plane message are send to traced UE to
request them to report periodically their position (typically obtained by AGPS/GPS). A
fallback method based on cellID and RTT is also available in the UE does not support
reporting its position via control plane.
3.1 WCDMA small cell tracing
Small cell 3G support IMSI call trace
 Subscriber trace is activated per UE (IMSI)
• It is not possible to collect call trace on a given access point without

knowing the IMSI of a customer
• Max 100 concurrent traces per BSR GW, 100 per IPC and 64 per Small Cell.
• Trace reporting time is configurable: Real Time (30s), 15s, 30s or 60s.
• It has impact on traffic capacity and CPU usage
• BCR3.0 provide 3GPP standard XML Call Trace Files for :

15 / 26
BSR: RRC (UU) & RANAP (IU)
BSR Gateway : RANAP (IU)
Iu Protocol Converter (IPC) :RANAP (Iu), ALCAP (IuCS)
• Note:
Inter BSR communication (BSRAP) are not traced
3.2 GSM tracing options

Tracing is also supported in GSM : the core network can request to trace a specific mobile.
When the BSC received this request, it traces RxLev & RxQual periodically.
Up to 10 UE can be traced per OMCR.
3.3 Data collecting option
Technology Network element Collection
WCDMA 9370 RNC WMS

16 / 26
WCDMA 9370 RNC WMS
WCDMA Small cells SCMS File server
GSM BSC OMC-R
LTE eNB SAM AUX server (call trace

only, up to LR14.3L)
MME
NPO TCE (all traces)
SGW/PGW
CDMA/EVDO RNC OMP
3.3.1 WMS
WMS provide call trace collection capability for 9370 RNC
Dimensioning limits are detailed in WMS engineering guide
3.3.2 SAM call trace auxilliary server
SAM provide a call trace auxiliary server, this server provide basic call trace collection
function:
 Up to 50 eNB per server sending call trace simultaneously
 Up to 2 auxiliary call trace server per SAM
3.3.3 TCE (Trace collection Entity)
TCE is a call trace collection option, part of 9959 NPO product.
Its goal is collect call trace from eNB, to transform and store them.
It supports the following input from eNB:

 3GPP compliant call trace
 RF trace : a new tracing mechanism providing richer data than 3GPP call trace

17 / 26
It supports the following output:

 3GPP XML call trace file (based on eNB call trace)
 Call trace PCAP file (based on eNB call trace)
 RF trace PCAP file (based on eNB RF trace)
 Measurement report counter file (based on eNB RF trace)
 Measurement report sample file (based on eNB RF trace)
TCE is composed of one or more server, called “TCE Unit”. The eNB managed by 5620 SAM
need to be split to have roughly the same number assigned to each TCE Unit, this ensure
that each TCE Unit get more or less the same amount of traffic.
TCE is also in communication to SAM to retrieve the configuration of the network (CM
XML). This is need for proper post processing of the call trace.
It provides the following output:
 Call trace in XML format
 PCAP file (based on RF Trace or call trace)
 Measurement report statistics file: XML file containing counter calculated from RF
Trace providing precise distribution
 Measurement report sample file: XML file containing decoded L1/L2 and L3
measurement report.

18 / 26
3.4 9958 WTA call trace analysis

WTA is the client based application to analyze call trace. It post process call trace
data
o Supports Per Call Analysis
o Combine Call Trace files by IMSI, Trace Reference, Time
o Decode 3GPP Protocol Messages
o Data Analysis of Call Traces
o Support a wide range of ALU RAN product
o Either collect directly the trace on the network element or do it via

the EMS.
o For some RAN product, trace can be activated directly from WTA
It runs on Windows OS (XP or 7) based PC, as well as Windows server 2003/2008.
It supports the following call traces

19 / 26
9958 WTA capability supports:
 Connectivity to browse/retrieve call trace files from
o 5620 SAM-AUX (9412 eNodeB, 9471 WMM/MME) for LTE
o 9471 WMM/MME/MME-SGSN for LTE
o 7750 SGW, 7750 PGW and 7750 S/P-GW for LTE
o TCE (9412 eNodeB, 9471 WMM/MME, 7750 SGW, 7750 PGW

and 7750 S/P-GW) for LTE
o 9353 WMS for WCDMA
o SCMS for Small Cell
o OMP for CDMA/EVDO
 Management and signaling based call trace activation methods for LTE only.
 Set up of call traces (start/stop and specifying associated call trace parameters)
by connecting with 5620 SAM (9412 eNodeB, 9471 WMM/MME) and 7750 SGW,
7750 PGW, 7750 S/P-GW.
 Set up Real Time Call Trace (RTCT) for 9771 WCE via TCE
The 9958 WTA GUI offers the user an easy way to input Call Trace activation
parameters and the call analysis output is seamlessly provided back to the user in
the Message Explorer and Message Flow views.
 Signaling Based Traces – MME & eNB
 Management Based Traces – MME, eNB & SGW, PGW, S/P-GW
 Cell Traffic Traces – Per eNB
 Event Based Traces – Per eNB
 Activate, Retrieve, Process & Output Call Analysis
9958 WTA Call Analysis offers:
 Correlate & Decode 3GPP Signaling Messages specified in TS 32.421, TS 32.422

and TS 32.423
 LTE Interface (Protocol) supported :
o eNodeB : S1-MME (S1AP), Uu(RRC), X2 (X2AP)

20 / 26
o MME : S1-MME (S1AP & NAS), S10 (GTPv2-C), S11 (GTPv2-C) , S6a
(Diameter), S13 (Diameter), Gn (GTP-C), SGs(SGSAP), Sv(GTPv2-C),
SLs(LCSAP), SLg(Diameter), S3(GTPv2-C)
o SGW : S11 (GTPv2-C), S5/S8 (GTPv2-C), Ga(Diameter)
o PGW : Gx (Diameter), S5/S8 (GTPv2-C), Rf*(Diameter), Gn*(GTPv2-C),

Ga*(Diameter), Gy*(Diameter)
* Activation only
 Per Call Analysis
 Call Flows
o Message Explorer
o Message Flow
o Timeline Explorer
 Metrics & Statistics
 Events & Call States
 User Defined Reports
WTA is able to combine different call trace (for example 3G and 4G call trace for an hand
over) and to display a combined view:

21 / 26
WTA support geographical call traces:

22 / 26
3.5 WCT (Wcdma call trace)

Whereas WTA focus on call-per-call analysis, WCT focus on statistical analysis of call
trace.
This is why it build on the NPO platform, which provide a scalable platform.
WCT module is able to analyze the following Wcdma Call Trace:
 CTn (Neighboring Call Traces): Those traces are used to monitor and optimize
neighboring relations by tracing information related to calls’ mobility. The
RNC logs events related to a traced call only when the call is inside the
configured area (when the call leaves the area the RNC stops tracing, and
when the call comes back into the configured area, the RNC resumes the
tracing). A CTn session is created and activated on a geographic area (a cell,
a set of cells or all the cells in the RNS)
 CFT (Call Failure Trace): This feature is used to troubleshoot and investigate
call drops on a specific network area. When the Call Failure Trace (CFT) is
activated the RNC logs a snapshot for all the call drops that occur on the
configured area. A CFT session is activated on a geographic area (a cell, a set
of cells or all the cells in the RNS) that needs to be investigated thanks to a
CTg session activation with additional sub-function.
23 / 26
The WCT module collects CTn and produces counters and indicators per handover
relation. They allow analyzing the success/failure rate of each relation, as well as
analyzing the active set size.
The WCT CTn module also allows analyzing the ping-pong behaviour, i.e. when the
primary cells moved back and forth between 2 cells in a very short timeframe, or
similarly when radio link are added and removed too rapidly.
WCT module collects CFT and produce counters. They provide several advantages
over classical RNC counters, they provide combination of criteria:
 Drop cause versus cell mode (FACH/DCH), with 15 different causes
 DCH: drop statistics versus DL/UP bandwidth
 HO drop cause split per CS/PS/CS+PS, 3G=>2G, 3G=>3F...
 RAB establishment failure per type of RAB and the number of RAB already
allocated
 Stats on RRC connection failure with 15 different causes
4 PLATFORM
The WCT and PCMD option of PCMD are based on the same NPO kernel as the NPO service
assurance:
 Oracle database is shared.
 The user interface is the same (analysis desktop, export tools..)
 Alerter can also be used from PM generated from WCT / PCMD.
 It is possible to mix & match data coming from NPO service assurance and
PCMD/WCT
 For the hardware, enabling PCMD/WCT require additional auxiliary server (except
on the small configuration where it run on the same hardware, but with reduced
number of cells)
TCE can run on:
 On HP DL380 G8 or HP Blade BL460 G8+P2000, i.e. the same type of server used by
NPO service assurance
 Or other hardware supporting minimal requirement on RAM/disk/CPU …
WTA is a PC application.

24 / 26
5 APPENDICES
5.1 Appendix A: Glossary of Terms
5.1.1 Acronyms

25 / 26
2G 2nd Generation radio network system eg. GSM
3G 3rd Generation radio network system eg. UTRAN
BSC Base Station Controller
CDMA Code Division Multiple Aspect
CFT Call Failure Trace (WCDMA call trace)
CT Call Trace
CTb Call Trace ‘b’ (IMSI base call trace in WCDMA)
CTg Call Trace geographic (Call trace on a list of cell in WCDMA)
CTN Call Trace Neighbourhood (Call trace on hand over for WCDMA)
EMS Element Management System
EVDO Evolution – Data Only (evolution of CDMA)
FTP File Transfer Protocol
FM Fault Management
GSM Global System for Mobile communication
GUI Graphical User Interface
IP Internet Protocol
LAN Local Area Network
MME Mobility Management Element
NE Network Element
NPO Network Performance Optimizer
NodeB UTRAN Basestation
Operation and Maintenance Centre - Radio part (Usually refers to GSM
OMC-R
O&M system)
O&M Operation and Maintenance
OPEX Operational Expenditures
PCAP Packet Capture (file format defined by Wireshark)

RNC Radio Network Controller
RNO Alcatel Radio Network Optimization software
RNS Radio Network Subsystem (RNC + associated NodeBs)
SAM Service Aware Manager (Alcatel-Lucent LTE, IP management system)
TCE Trace Collection Entity
UMTS Universal Mobile Telecommunications System
UTRAN UMTS Terrestrial Radio Access Network
WCDMA Wideband CDMA (=UMTS)
WCT Wcdma Call Trace (NPO option)
WMS – Proprietary
Alcatel-Lucent Wireless Management System (Alcatel-Lucent
NMS/NIO/INF/043090 V1/EN 3G O&M system)
26 / 26
WTA Wireless Trace Analyzer (Alcatel-Lucent product)
XML eXtensible Markup Language

9959 NPO PCA Customer - Product - Overview PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9959 NPO PCA Customer - Product - Overview PDF

Uploaded by

Copyright:

Available Formats

NPO Per call analytics

Customer Product Overview

Copyright © 2011 by Alcatel-Lucent. All Rights Reserved.

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

 9959 NPO PCMD (Per Call Measurement Data)

 9959 NPO TCE (Trace Collection Entity)

 9959 NPO WCT (Wcdma Call Trace)

 9958 WTA (Wireless Trace Analysis).

1.1 Scope of this document

1.2 Audience for this document

2 LTE PER CALL MEASUREMENT DATA (PCMD)

2.1 What is PCMD

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

 Identification (which IMSI, IMEI, cell, MME, SGW…)

 Control plane (which procedure, success or failure, duration…)

 User plane (volume per QCI, retransmission)

 RF information (RF quality measurement)

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

2.1 Why this approach ?

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

Figure 1 Probe based design

2.2 Examples use cases

2.2.1 Use case: Using PCMD to troubleshoot customer issues

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

2.2.2 Use case: Using PCMD for device analysis

Issue: Many bugs are due to interaction with specific UE type

Other methods cannot provide this level of visibility:

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

 Counter are not reported per device type.

2.2.3 Use case: Real time monitoring

This ensures quick reaction.

• Thresholds can be adjusted (CDR, SRFR, IAFR)

• Alerter can be defined on real time monitoring (1 minute GP Alerter)

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

2.2.4 Use case: Flexible counter

2.2.5 Use case: Understanding failure

Issue: Identify the main contributors to failure (call drop…)

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

2.2.6 Use case: VIP monitoring

Issue: VIP needs dedicated care, identifying quickly issues.

2.2.7 Use case: IDENTIFYING CUSTOMER that HAVE HIGH FAILURE

 Bad KPI on the cell where is the customer

 Bad experience for the customer

2.1 PCMD in 9959 NPO

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

NPO PCMD provides ability to:

 Create counters and KPI based on PCMD

o per cell, per eNB, per SGW,

o On a select set of IMSI (“monitored IMSI”, up to 5000)

o Per device type

o Per hand over relation

o Direct viewing of PCMD records

o Ad hoc query (counting & summing of the record on any criteria)

3 LTE CALL TRACE, RF TRACE AND POST PROCESSING

3.1 eNB tracing option

3.1.1 Call traces

Contrary to Performance measurements, which are a permanent source of information,

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN

 When Alcatel Lucent provides eNB and MME

It is possible select the list of interface traced:

 SAM call trace auxiliary server

Alcatel-Lucent – Proprietary NMS/NIO/INF/043090 V1/EN