2.2 Nokia Cognitive Analytics Real-Time Software

NOKIA COGNITIVE
ANALYTICS REAL-
TIME SOFTWARE
May 30th 2018
Mobile Radio Governance & Tools – Owen Guiamo
Agenda
– Background about Governance & Tools department and our goals
– Network planning evolution
– MDT and GEO location
– Some use cases for Tele2
– RSRP heatmaps to detect coverage holes
– Overshooters analyses
– Crossed Feeder analyses
– Where is SRVCC triggered
– Where are HO failures occurring
– Troubleshoot Individual customer complaints
– Benefits for Tele2
The Goals for Radio Infrastructure Governance & Tools
Efficient Utilize resources in a most efficient way
Simple Use same process for all SO countries
Consolidate or eliminate redundant systems to have

Harmonize same tool in all SO countries
Improve Network Improve network stability by having configuration
Quality and Stability templates and automated consistency checks
Improve Automation Utilize data collection to improve Network optimization

Traditional Network planning
– Prediction is strongly influenced by chosen propagation model
Propagation Model 1 Propagation Model 2

Improved Granularity
Individual
Network KPI Cell level Cell footprint Grid level customer level
Better granularity makes Monitoring, Troubleshooting and Optimization easier

and faster
Traditional network planning evolution
Transformation based on new methodology and granularity
Planning Actual Cell
Predictions footprint
GEO Location
Network/Cell Grid level

level KPI s KPI ’s
Minimization of Drive Tests (MDT)
1. Logged MDT – IDLE Mode MDT - LTE1049
– Logged MDT measurements are sent in Connected Mode
– Serving and Neighboring cell information (intra- and inter frequency)
– RSRP and RSRQ per serving and neighbor cell
– PCI of the logged cell
– Location Information (Optional, if available in UE implementation)
2. Immediate MDT – Connected Mode MDT
– UE RSRP
– UE RSRQ
– UE Power Headroom - LTE2084
– UE Uplink SINR - LTE2084
– Data Volume measurement separately for DL and UL, per QCI - LTE2202
– Radio Link Failure - LTE678
– Location Information (Optional, if available in UE implementation)
MDT and GEO location
– MDT is about collecting measurements to know where the customers uses

the service, 24/7/365
– GEO location is about visualizing the data on a map up to customer level for
easier, faster and fact based troubleshooting
– MDT and GEO location are independent from each other but combined
brings a powerful combination to provide visibility on a map of where our
customers use the service, 24/7/365. This allows us to better and faster
optimize the network based on actual measurement data of users’
experiences
– Improve overall network quality and
– Enhance end-user experience
Some use cases for Tele2
– GEO Insights
– RSRP heatmaps to detect coverage holes
– Overshooters analyses
– Worst performing cells
– Crossed Feeder analyses
– Record Search
– Where is SRVCC triggered
– Where are HO failures occurring
– Troubleshoot Individual customer complaints
– User throughput issues with LTE2202
– POI search with Here maps
GEO Insights - RSRP Heatmap
Overshooters analyses
Neighbor distance Cell dominance per Geo tile
Crossed Feeders analyses in Traffica Views
Crossed Feeders analyses with Cell Footprint
Cell 82 should be 81 Cell 83 should be 82 Cell 81 should be 83

Find worst performing cells in selected area
Find worst performing cells in selected area
– Sorting per KPI possible to get worst performing cells on top
– Table view to have an overview of the KPI values
Data history
– Longer aggregation periods provides more
Optimization capabilities whereas short
term is more about
Monitoring/Troubleshooting
– It is particular of interest for MDT since at

date MDT is not supported by all phone
vendors/models. Averaging over 1 week
period will increase the number of MDT
samples, hence improving accuracy (GPS
accuracy + more samples)
Record search
– Create own queries

– Focus on specific map area
– Visualize on the map to show the invisible
Select Query and conditions
Handover failures
Unique colors per cell
Handover failures - cont´d
Change data set to visualize Failure Cause
Handover failures - cont´d
Change data set to visualize Unique customers
Table view with failure causes
Benefits and Savings
GEO LOCATION
Benefits for Tele2
– Evolve from simulations/predictions to fact based cell coverage

– Reuse existing data to visualize on a map
– Focus on network issues where it matters
– Visualization of KPI’s on a map in Real Time
– E.g. InterRAT HO, ERAB drop rate, ERAB & RRC setup success rate, etc.
– For both VoLTE and Data session
– Improve users’ experiences
– Mapping the invisible
– Interaction with other tools like Traffica Views/News
Increase NPS score
– Give customer care better tools to acknowledge customer experience
– See total number of customers having bad coverage in reported area
– Better feedback to the customer possible to prevent churn
– Give optimization team insights in actual coverage to (proactively) optimize
network to improve coverage
– Improved feedback loop between customer care and optimization team to be
aware of those customers complaints and directly see the results after
optimizations
THE
END

2.2 Nokia Cognitive Analytics Real-Time Software

Uploaded by

Copyright:

Available Formats

2.2 Nokia Cognitive Analytics Real-Time Software

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

2.2 Nokia Cognitive Analytics Real-Time Software

Uploaded by

Copyright:

Available Formats

NOKIA COGNITIVE

Efficient Utilize resources in a most efficient way

Simple Use same process for all SO countries

Consolidate or eliminate redundant systems to have

Improve Automation Utilize data collection to improve Network optimization

Propagation Model 1 Propagation Model 2

Better granularity makes Monitoring, Troubleshooting and Optimization easier

Network/Cell Grid level

– MDT is about collecting measurements to know where the customers uses

Cell 82 should be 81 Cell 83 should be 82 Cell 81 should be 83

– It is particular of interest for MDT since at

– Create own queries

– Evolve from simulations/predictions to fact based cell coverage

You might also like