Traffica for eNB &

Traffica Insights
Telkomsel 9.2.2017
Janne Jylhä
Senior Specialist
Traffica R&D

1 09/02/2017 © Nokia 2016 - File Name - Version - Creator - DocID

Confidential
Agenda

10:00 - 10:30 Welcome & Overview of Traffica Insights Roby Wijaya

10:30 - 11:00 Traffica Insights trial project ovwerview Mahindra Sasongko
Introduction of eNB Traffica containing : Insight, Views, &
11:00 - 12:00 Janne Jylhä
News
12:00 - 13:30 Break
13:30 - 14:30 Demo of Traffica Geo Insight Capabilities Janne Jylhä
14:30 - 15:30 Use Case Demo Janne Jylhä and local Nokia Radio team
15:30 - 16:00 Question & Answer
How Traffica solution is typically used in an operational environment
Two main usage characteristics for use cases

Preset NoC Screens (Based Traffic

Real-time monitoring views and Insights reports)

What are the biggest customer Term based NoC Screens

(customized Traffic views reports)
impacting problems right now ?
Alarm Thresholds (shown on traffica
display and/or alarm forwarding to an FM
solution)

Utilizing Traffic Views/News/Insights to

Troubleshooting and analyze network planning /
Problem Analysis parametrization challenges or Utilizing
Traffic News to analyze new service
launch or customer complaint (Traffic
Rapid Fault Finding News and Database Export).
Architecture

Tier 1
Clients

Traffic Views Traffic News Traffica Insights

Tier 2
Mediation layer Interfacing On-demand content

TS
Real-time Data Analysis Secure Connections Thresholding

Tier 3 3G WCDMA
2G/3G PaCo 2G CS core DPI CS probes
Data RAN
collection

LTE RAN EPC 3G CS core CDR PS probes

TNES
 Traffica eNodeB Architecture Clients
• LTE1340 (Cell Trace IF)
• LTE1053 (RTPM) Traffica
Server (TS) Views News Insights

• Cell Trace IF provides UE

transactional data (existing
LTE1340 feature)
RTTs • LTE1053 RT PM IF provides
L3DC Traffica Traffica real-time PM information at a
TNES TNES cell and eNB level.
• Both IF’s can be active at the
Cell Trace Direct eNB same time on the eNB’s
Activation of LTE1053, Interface RT PM IF • Cell IF: up to 1000 eNBs/TNES **)
Cell Trace LTE1340
• RT PM IF: up to 5000 eNBs/TNES

**)eNB’s / L3DC-TNES depends on busy hour traffic mix

LTE: L3DC based IMSI provider solution
MME vendor independent, light weight probe that maps IMSI to Cell Trace

• L3DC probe fetches the user’s IMSI, IMEI

details from S11 (mirrored) interface
respectively
HSS S6a
• L3DC (emil) inserts the user’s IMSI, IMEI
information into the RTT reports that are
switch generated and sent towards Traffica
L3DC probe
• IMSI, IMEI information is available in Traffica
News for searching as well as other Traffica
MME applications
S11 mirrored
• One L3DC Probe Server needed per MME
switch S11
RTTs
L3DC
Traffica
SGW TNES

IMEI info
Cell Trace (radio network control plane data)
IMSI info
Traffica Functionality Database queries
(Traffic News)
Traffica
NE Traffica
Database Database Export
Server
RTTs
OFF-LINE

ON-LINE

Real-time graphs in
clients (Traffic Views)

Clear Code
Insights
Matrix
(CCMA)

Alarms on thresholds

Administration
Traffica Real Time Monitoring Solution

• Traffica focuses on live traffic and subscriber activity

• Traffica provides real-time visibility over the
end-users activity and service usage, in the whole network or
down to cell level

• How much subscribers are using the services, at what time,

from where in the network, what problems they have

• The details of activities for each subscriber (error codes etc…)

• The usage and problems per mobile type
• eNB Traffica supports also map visualization
Interworking
Analyzing geographical
context with Traffica Insights.
Get visibility on neighbors,
Monitoring with real-time
coverage and quality issues
graphs in Traffic Views.
within the cell area.
Identifying top problematic
Cells.

Get additional details with

Views graphs, e.g. failure
causes, problematic UE
models, amount of Analyze Cell on Traffica
impacted subscribers etc. Geo Insights or event
specific Geotile on map.

Show in Traffic Views

Analyzing raw data
records with Traffic News.
Get visibility on all
parameters with targeted
queries. Session deep dive at
protocol level with
Layer 3 Data Analyzer
Traffic Views clients

Visualize KPIs
in Real-time

Fast drill-down from

failing KPI to impacted
resources and subs

Define and monitor user

specific KPIs depending
on the need

Utilize different time

resolutions and history
for visualizing trends
Traffic News clients

Traffic News clients for access to database raw records

(RTTs and all reports received and stored by the
TNESs)
• Make query to one TNES, all TNESs (network-
wide view), or any selection of TNESs
• Select records with conditions on any field or
combination of fields
• Use ready-made query templates, or define your
own templates (can be stored, can be shared)
• Define and taylor the display of the query results
• Query results can be stored to a file to be used
e.g. with Excel or any reporting application
Examples: RTPM real-time Alarms
Example alarms for RTPM

SNMP traps NetAct

Alarm Editor
(or other
OSS)

Raise active Filters to define which

alarms Alerts are sent to SNMP

Evaluate
conditions Traffica server
Define Alarm criteria, thresholds
smoothing period filtering

Cell Traces and RTPM

User Definable Alarms
Regular alarm Expression alarm
Simple KPI Intelligent alarms
X < yy Multiple KPIs together
or X > Y && IMSI_Count > Z
X/Y > xx%

Limit alarm Delta threshold Burst

with history alarm alarm
Examples: RTPM real-time Alarms
Example alarms for RTPM
Traffica for eNodeB Reporting functionality
Content of the data
eNodeB Traffica Report triggering: RRC_ERAB RTT

Depending on the LTE radio UE event, different reports are sent to Traffica by L3DC.
RRC_ERAB RTT report is triggered after following events:

 RRC only connection is established

 RRC connection is established and initial EPS Bearers (ERAB) are setup.
 Only single report sent covering both RRC and initial ERAB setup procedures

 RRC and/or ERAB connections are released.

 If both ERAB and RRC are released simultaneously, only single report is sent

 UE makes re-establishment. A report is sent both from Source and Target, if they are different.
 If re-establishment is made successfully to serving cell, no RTT report is sent, but amount of successful re-establishments is
reported when call is released (that is reported either as RRC_ERAB or HO report, depending the release cause).

 Idle mode incoming I-RAT redirection (this looks like initial ERAB or RRC establishment)
 Additional ERABs are setup to ongoing call
 Some of the ERAB(s) are released from ongoing call.
eNodeB Traffica Report triggering: Handover (HO) RTT

Handover (HO) RTT report is triggered after following events:

 Intra eNB, X2 or S1 handover; the report is received for both Source and Target cells.
 I-RAT Handover (Idle mode or Active mode)
 Failed Handover attempt
 If handover fails already in the source cell, the report is sent from source side only.
 If handover fails in the target side, there is successful HO report from source and another report from target indicating failure.

 UE makes CS fallback
 If UE is in idle mode camped in LTE when CS fallback is triggered, there is first ERAB setup report (RRC_ERAB RTT) and immediately
after that release event, which triggers Handover RTT report indicating CS fallback.
eNodeB Traffica Scenarios

Different LTE radio network UE specific scenarios can be identified with couple of key fields from
Traffica RTT reports:
- In_Cause: identifies the reason for SRB or DRB/ERAB setup (updated also in the release phase to
indicate how bearer or session was started)
- Out_Cause: identifies the reason for SRB or DRB/ERAB release (if empty means that report is
related to setup event)
- Failure_Phase: indicates at which phase the scenario failed
- More detailed listing of different scenarios in attached excel document
In Traffica 17 onwards, there is also own logical field for Scenario (see Excel)
In_Cause Out_Cause Failure_Phase Scenario
RRC establishment, ERAB setup or incoming
Value Empty Empty Handover
Value Value Empty RRC/ERAB release, outgoing Handover
Value Empty Value Failure during ERAB setup and release
Value Value Value Failure during RRC/ERAB release
 eNodeB Traffica Report triggering: Idle and Active mode MDT and Active RTT

Idle mode MDT (LTE1049) report is triggered after following events:

 UE establishes session (returns to active mode) and reports all the measurement samples collected in idle
mode.
 Every sample triggers own RTT report.

Active Mode MDT (LTE1308) with periodical measurement supports GPS location for
 If measurement report (MR) is less than 5secs old and it contains GPS position, L3DC adds GPS LAT and
LONG to RRC_ERAB and HO Reports

Active RTT (LTE2202, in FL16A or FL17 (FSMr4)) report is triggered after following events:
 Periodically every 4 seconds from the start of the session for every UE to whom the reporting is enabled
in eNodeB / Cell.
 The possible leftovers between last report and end of session (0-4 second period) are not reported.
eNodeB Traffica: RRC_ERAB_Report includes e.g:
• Report time
• PLMN, MCC, MNC
• Serving eNodeB ID, eNodeB software version
• Serving Cell ID and frequency
• IMSI, IMEI, phone model (When IMSI Provider available)
• In Cause, Out Cause, Failure Phase
• EUTRAN Trace ID
• QCI, ARP (traffic type) information per E-RAB
• Configured Bit rates (DL,UL) for E-RAB connections
• Call Failure causes, Detailed failure cause (for Radio Interface failures)
• TMSI, MME S1AP UE ID (unique call identifier), SGW TEID, MME ID
• S1AP setup and release causes
• Serving Cell UE signal quality and distance (TA) from eNodeB for RRC connections
• UE Capability information
• Successful Re-est Count
• L3 Message ID (L3DC report triggering reason)
• Optionally: Latitude, Longitude, Geohash and used location algorithm
eNodeB Traffica: HO_Report includes e.g:
• Report time, HO Type
• PLMN, MCC, MNC
• Serving eNodeB ID, eNodeB software version
• Serving and target Cell ID and frequency, PCI etc
• IMSI, IMEI, phone model (When IMSI Provider available)
• In Cause, Out Cause, Failure Phase
• EUTRAN Trace ID
• QCI, ARP (traffic type) information per E-RAB
• Max Bit rates (DL,UL) for E-RAB connections
• Call Failure causes and X2 causes
• TMSI, MME S1AP UE ID (unique call identifier), SGW TEID, MME ID
• S1AP setup and release causes
• Serving Cell UE signal quality and distance (TA) from eNodeB for RRC connections
• Neighbor cell signal quality measurements during handovers (4 targets: RSRP, RSRQ)
• UE Capability information
• L3 Message ID (L3DC report triggering reason)
• Optionally: Latitude, Longitude, Geohash and used location algorithm
eNodeB Traffica
eNodeB Traffica Idle Mode MDT report content (LTE1049)
Measurement sample specific fields EUTRAN_Target_cell_count
(reported for every PCI_Measurement_Report_Target1
Common fields (identical for all sample separately in dedicated container) Target1_DL_EARFCN
samples RSRP_Measurement_Report_Target1
recorded during single idle mode Report_Time Target1_RSRQ_dB
period): Report_Date PCI_Measurement_Report_Target2
Latitude Target2_DL_EARFCN
Report_Id Longitude RSRP_Measurement_Report_Target2
Report_Length Altitude Target2_RSRQ_dB
Report_Count Location_Algorithm
EUTRAN_Trace_ID PLMN_ID UTRAN_Target_cell_count
IMSI_Length UTRAN_Cell_ID_Target1
IMSI SRB_Source_CELL_ID Target1_DL_UARFCN
IMEI SRB_Source_DL_EARFCN RSCP_Measurement_Report_Target1
eNB_ID RSRP_Measurement_Report_Source1 Target1_EcNo_dB
SRB_Source_LCR_ID Source_RSRQ UTRAN_Cell_ID_Target2
Number_of_Containers Source_RSRQ_dB Target2_DL_UARFCN
RSCP_Measurement_Report_Target2
Target2_EcNo_dB
PCI_Measurement_Report_Target3
Target3_DL_EARFCN GERAN_Target_cell_count
RSRP_Measurement_Report_Target3 GERAN_Cell_ID_Target1
Target3_RSRQ_dB Target1_DL_ARFCN
PCI_Measurement_Report_Target4 RxLevel_Measurement_Report_Target1
Target4_DL_EARFCN GERAN_Cell_ID_Target2
RSRP_Measurement_Report_Target4 Target2_DL_ARFCN
Target4_RSRQ_dB RxLevel_Measurement_Report_Target2
eNodeB Traffica Idle Mode MDT report examples (LTE1049)

LTE1049 MDT data fromTrafficNews

manuallyaddedon top of map
dot = phoneidle LTE1049 MDT data Used in Traffica Insights
Gap = phoneactive To calculate coverage heat map
Reporting in active mode per UE (LTE2202 in LTE16A)
time
UE Measurement
report ERAB holding time
TA TA
Active Transfer time (TTIs)

Transfer speed bit/s

MAC report refers to periodical User

MAC MAC MAC MAC plane performance report provided
report report report report through LTE2202 feature
ACT RTT ACT RTT
report report
New Traffica RTT report from
L3DC
Active mode report (LTE2202)
Content
Report contains following information per session (only most important fields listed below):

- Cell and eNodeB id:s, timestamp, IMSI, IMEI, TMSI, EUTRAN trace id
- UE location
- Measurement report data for serving and up to 4 neighbor cells, latest Timing advance
value
- Serving and neighbor cell PCI, ECI and frequency values
- Transferred bytes and used TTI for GBR and non GBR traffic (uplink and downlink)
- Retransmission counts (UL and DL)
- Buffer occupancy
- Mean channel quality indicator (CQI) Downlink mean (WB and delta),
- Uplink MCS, PUSCH RSSI, PUSCH SINR, PUCCH RSSI, Power headroom
- Uplink and downlink mean aggregation grant
Traffica for LTE
RTPM based interface
 Traffica eNodeB Architecture Clients
• LTE1340 (Cell Trace IF)
• LTE1053 (RTPM) Traffica
Server (TS) Views News Insigts

• Cell Trace IF provides UE

transactional data (existing
LTE1340 feature)
RTTs • LTE1053 RT PM IF provides
L3DC Traffica Traffica real-time PM information at a
TNES TNES cell and eNB level.
• Both IF’s can be active at the
Cell Trace Direct eNB same time on the eNB’s
Activation of LTE1053, Interface RT PM IF • Cell IF: up to 1000 eNBs/TNES **)
Cell Trace LTE1340
• RT PM IF: up to 5000 eNBs/TNES

**)eNB’s / L3DC-TNES depends on busy hour traffic mix

Traffica for eNodeB: RTPM contents, monitoring capabilities
Real-time PM
(1 min)
The Measurement / report types:
1. S1AP (M8000)
2. Cell Load (M8001)
3. Transport Load (M8004)
4. Power and Quality UL (M8005)
5. EPS Bearer (M8006)
6. Radio Bearer (M8007)
7. RRC (M8008)
8. Intra eNB Handover (M8009)
9. Power and Quality DL (M8010)
10. Cell Resource (M8011)
11. Cell Throughput (M8012)
12. UE State (M8013)
13. Inter eNB Handover (M8014)
14. Neighbor Cell Related Handover (M8015)
15. Inter System Handover (M8016)
16. ISHO to UTRAN per Neighbor Cell (M8017)
17. eNB Load (M8018)
18. ISHO to GSM per Neighbor Cell (M8019)
19. Cell Availability (M8020)
20. Handover (M8021)
• Real-time performance measurements collected via RTPM feature
LTE1053 (similar to NetAct counters)
• Real-time measurements at eNB and Cell
21. X2AP (M8022)
22. UE and Service Differentiation (M8023)
23. Network Sharing (M8024)
24. HO to eHRPD per eHRPD Bandclass (M8025)
25. QoS (M8026)
26. RLF triggered Handover (M8027)
27. MAC (M8029)
28. SINR (M8031)
29. MBMS (M8030)
30. MRO UTRAN Frequency Related (M8032)
31. Mobility Events (M8033)
32. EUTRA Carrier Frequency (M8034)
33. S1 SCTP Statistics (M8035)
34. X2 SCTP Statistics (M8036)
35. M3 SCTP Statistics (M8037)
36. RAN Sharing (M8038)
37. GNSS (M8039)
39. FZAP GNSS (M8041)
40. RIBS Statistic (M8044)
Traffica functionality – a quick recap
Database queries
(Traffic News)
TNES Traffica DB Export functions
Database
RTTs OFF-LINE
ON-LINE

Real-time graphs in
clients (Traffic Views)
Clear Code
Matrix
(CCMA – KPI rule tree)
Alarms on thresholds
Traffica Insights
 GUI Overview
Data filters
Map layer management, Site and cell Performance information on each geographical location (geotile) is updated in 1 min, 15 min or
locations on the map 1 hour interval. Aggregated values for current day and previous day are also available.
KPI selection

Geotile
details, KPIs,
serving and
Network candidate
element cells
details,
basic
parameters,
parent info,
configured
neighbors,
cell level
KPIs

Cell
drilldown to
Views real
time graphs Geotile level KPI based heatmap
The geographical map is able to display a selection
KPIs that contribute to cell performance.
Data table of all visible These KPIs are calculated and displayed at the geotile
level (not on the level of single subscribers or network
cells for case priorisation elements)
Solution components
Traffica real time analytics solution News
LTE1053: Direct
RTPM interface

TS
L3DA
eNodeB TNES
Geo KPI-s
Geo
LTE1340: L3 enriched
session details RTTs

LTE1049: Idle Insights

mode MDT
Topology
eNodeB L3DC TNES (RAML) *)
• Traffica for eNodeB (Cell Trace based IF) IMSI/
IMEI
• L3DC - requires TSS17
• eNB – with LTE1340, LTE1049
• Optional: TSS IMSI provider (SIMCA) Views
• Optional: Traffica for Real-time PM SIMCA
• Optional: L3DA (Emil) IMSI

OSS
*) NetAct topology integration is mandatory pre-requirement
for RF fingerprinting algorithms with following objects: SITE,
MRBTS, LNBTS, LNCEL, LNREL, ANTL, BTSSCL and LCELL.
Note: The SITE and ANTL Objects must have Coordinates. MME NetAct
Traffica Insights KPIs at geotile level, cell level and TA sector level
QCI QCI
Group Counter / KPI Name Data source Dimensions Group Counter / KPI Name Data source Dimensions
filtering filtering
Retainability Affected users ERAB drops eNodeB cell trace Cell Yes
Accessibility Affected users ERAB setup failures eNodeB cell trace Cell Yes
Retainability ERAB all releases eNodeB cell trace Geotile / Cell / Cell-TA Yes
Accessibility Cell availability RTPM Cell No Retainability ERAB drop count eNodeB cell trace Geotile / Cell / Cell-TA Yes
Accessibility ERAB setup attempts eNodeB cell trace Cell / Cell-TA Yes Retainability ERAB drop rate eNodeB cell trace Geotile / Cell / Cell-TA Yes
Accessibility ERAB setup failures eNodeB cell trace Cell / Cell-TA Yes Signal quality Number of RSRP samples eNodeB cell trace Geotile Yes
Accessibility ERAB setup success rate eNodeB cell trace Cell / Cell-TA Yes Signal quality Number of RSRQ samples eNodeB cell trace Geotile Yes
Accessibility RACH setup attempts RTPM Cell Yes Signal quality RSRP average eNodeB cell trace Geotile No
Accessibility RACH setup completions RTPM Cell Yes Signal quality RSRP median eNodeB cell trace Geotile No
Accessibility RACH success rate RTPM Cell Yes Signal quality RSRQ average eNodeB cell trace Geotile No
Accessibility RRC re-establishments eNodeB cell trace Cell / Cell-TA Yes Signal quality RSRQ median eNodeB cell trace Geotile No
Accessibility RRC setup attempts eNodeB cell trace Cell / Cell-TA No Usage Active user count avg RTPM Cell No
Usage Active user count max avg RTPM Cell No
Accessibility RRC setup failures eNodeB cell trace Cell / Cell-TA No
Usage Cell throughput DL RTPM Cell No
Accessibility RRC setup success rate eNodeB cell trace Cell / Cell-TA No
Usage Cell throughput UL RTPM Cell No
Mobility Affected users HO failures eNodeB cell trace Cell Yes
Mobility HO attempts eNodeB cell trace Geotile / Cell / Cell-TA Yes
Mobility HO attempts inter eNB S1 eNodeB cell trace Geotile / Cell / Cell-TA Yes
Mobility HO attempts inter eNB X2 eNodeB cell trace Geotile / Cell / Cell-TA Yes
Mobility HO attempts inter RAT eNodeB cell trace Cell / Cell-TA Yes
Mobility HO attempts intra eNB eNodeB cell trace Geotile / Cell / Cell-TA Yes
Mobility HO failures eNodeB cell trace Geotile / Cell / Cell-TA Yes
Mobility HO failures inter eNB S1 eNodeB cell trace Geotile / Cell / Cell-TA Yes
Mobility HO failures inter eNB X2 eNodeB cell trace Geotile / Cell / Cell-TA Yes
Mobility HO failures inter RAT eNodeB cell trace Cell / Cell-TA Yes
Mobility HO failures intra eNB eNodeB cell trace Geotile / Cell / Cell-TA Yes
Mobility HO success rate eNodeB cell trace Geotile / Cell / Cell-TA Yes
Geo enriched RTTs in eNodeB Traffica

UE GPS receiver based information Location based

• GPS receiver based location in device is sent to
eNodeB part of signaling messages and eNodeB
adds the information to cell trace
• Timing advance and RSRP values are used for L3DC algorithms to estimate the
location of device.
• This method is called triangular or RF fingerprint based location in some
references
• Location based method require NetAct topology integration to Traffica with
required co-ordinate information

The used location method is indicated in the RTT report with “location algorithm” field, which can have
following values (the bigger the value the more accurate it is assumed to be):
120 = UE GPS based location
70 = Inter site TA + 2RSRP (3 sites), periodic measurements
60 = Inter site TA + 2RSRP (3 sites), non-periodic measurements
50 = Intra site TA + 2RSRP, periodic measurements
40 = Intra site TA + 2RSRP, non-periodic measurements
20 = Serving cell location with small TA (0-156 m)
10 = Serving cell location
Traffica Insights: Data Table

Data Table can be found on

the bottom of screen, below
map.

Data Table shows additional

information about objects
visible on map. For
example:

• ECI and eNodeB ID

• RRC Setup Success Rate
• ERAB Setup Success Rate
• ERAB drop rate
• HO success rate
• HO Attempts
• Cell availability
• Active user count average
• RACH success rate
Network Element Details
Information in Cell Details Window
• ECI
• Cell name
• ECGI
• LNCEL
• LCR ID
• PCI
• MO DN
• Bearing
• Frequency band
• Street address
• Site name
• eNodeB ID
• eNodeB name
• eNodeB software version
• List of configured neighbors
• List of cell KPIs
• List of Timing Advance (TA) KPIs (if
a cell KPI is selected)
Network Element Details – Basic Info
Bearing is given in degrees
from north, where:
• 0 is north
• 90 is east
• 180 is south
• 270 is west
Network Element Details – Configured Neighbors

Available Information:
• ECI (E-UTRAN Cell Id)
• PCI (Physical Cell Id)
• Band (frequency)
• Distance in kilometers.
Network Element Details – Cell KPIs

Examples of KPIs
• Cell Availability %
• ERAB setup failures
• RACH success rate
• etc
Network Element Details – Cell KPIs at Timing Advance Level
Network Element Details – Show Cell in Traffic Views
Use Case. Identifying Overshooting Cells

1. In Traffica Insights the

physical cell location in
respect to other cells can
be inspected

2. Coverage and success

rates in tabular format
can be seen at the
bottom of screen for all
the visible cells

3. Overshoot situation is
clearly visible as call
drop happening where
there should be no
coverage
46 09/02/2017 © Nokia 2016 - File Name - Version - Creator - DocID
Confidential