RAN Sharing & Reporting · 2017-10-07 · Telefonica UK 3 3 Telefonica O2 UK O2 is the commercial...
Transcript of RAN Sharing & Reporting · 2017-10-07 · Telefonica UK 3 3 Telefonica O2 UK O2 is the commercial...
RAN Sharing & Reporting
David BensonPerformance Reporting Manager Telefonica O2 UK
Telefonica UK
22
Agenda
A-Side: Introduction & Background
• Telefonica UK• Radio Networks Reporting Team • RAN Sharing Overview • Challenges of Reporting with RAN sharing
B-Side: PrOptima™ Implementation
• Defining the data we need • Data Exchange Mechanism• Enriching the Data• Reporting
Telefonica UK
33
Telefonica O2 UK
O2 is the commercial brand of Telefónica UK Limited, a leading digital communications company with over 23 million customers.
O2 runs 2G, 3G and 4G networks across the UK, as well as operating O2 WiFi.
O2 has over 450 retail stores and sponsors The O2, O2 Academy venues and the England Rugby Union team.
Telefonica UK
44
Network Reporting Team
• Focused on RAN performance; Drive Test and PM data.
• “End to End” PM activities – Develop metrics &reporting capability.– Run reports– Perform first level analysis of performance trends
• A long partnership with MYCOM OSI • Telefonica O2 UK and MYCOM OSI headquarters are in the
same UK town!)
Telefonica UK
55
Project Beacon - RAN Sharing
• What?RAN Sharing with Vodafone (MORAN)(Multi-Operator Radio Access Network
• Where?UK Share 2G, 3G, 4G
=>West (Vodafone)=>East (Telefonica)
London Share 4G =>North (Telefonica)=>South (Vodafone)
• Why?– More cells for customers– Less cell sites (in total)– Better coverage & capacity– LTE Roll Out
• When?– Began late 2012. – Rollout continues until 2017
Telefonica UK
66
Project Beacon - Telefonica Ownership Areas
GSMUMTSLTE(UK –excluding London)
LTE(London)
Telefonica UK
77
Project Beacon Telefonica Ownership UK
Logical Area Summary & Terminology
Owner Legacy/Beacon Network Cell_Owner PM Stats visibility for TEF
Telefonica Legacy Telefonica TFinTF 100%
Telefonica Beacon Telefonica TFinTF 100%
Telefonica Beacon Vodafone VFinTF 100%
Vodafone Legacy Vodafone VFinVF None
Vodafone Beacon Vodafone VFinVF None
Vodafone Beacon Telefonica TFinVF ?
“Network” “Operated By”
Telefonica UK
88
The Challenges (Cultural)
• Partnerships & alliances are increasingly common but working with a major competitor is an interesting experience.
• (Initial) confusion from PM reporting customers…“What was last weeks traffic?” “when you say traffic do you mean, our traffic”“Yes!” “Does “our traffic” mean the traffic we manage or the trafficour customers generate?”“Can you repeat the question please!”
• Need to build networks, systems and trust!
• New confidentiality and legal obligations
Telefonica UK
99
The Technical Challenge
Agree What to Exchange
Build Exchange Mechanisms
Enrich the Data
Build Reporting Capability
Report
Telefonica UK
1010
Data Exchange – What to Exchange?
• What PM data to share, how and when?
• Initial “what” discussions - two extremes- Exchange everything – (direct OSS feeds)- Exchange only contractual KPIs
• Agreement to exchange a small number of KPIs - Help build trust and confidence in partners SLA
reporting - Enable national reporting on all OUR customers’
experience- Support SLAs with corporate customers- Help with optimisation
RAN SHARING
FORBEGINNERS
Telefonica UK
1111
Data Exchange – The Agreement
• To align these measures across the TEF and VF RAN vendors we needed agreement on formulae…
We exchange the calculated KPI not the raw
counters
Telefonica UK
1212
Data Exchange - Sending The Data
24 hourly files per Technology
Filters VFinTF data
Telefonica UK
1313
Data Exchange - Receiving The Data
Data files(.csv) receivedone per hour per technology. (Not direct from OSS so latency worse than other RAN interfaces)
Spare Slots
Numerator/Denominator
3 New Adaptors
Telefonica UK
1414
Data Exchange – Loading The Data
• Spare slots give in-house capability to map additional counters that are added to the input .csv file.
• We anticipated the need for flexibility but underestimated the extent of change - schedule currently @ Version 36
• 70 ‘KPI’s slots – increased recently to 300 slots per technology.
Telefonica UK
1515
TFinVF ‘Stand Alone’ Reporting
Prefix – S12,T,V
Simple report taking ‘raw’ 2G data
Telefonica UK
1616
TFinVF Data + CM data
We add CM data to the RAN interfaces already. This was extending for RAN sharing.
2G Cells Ref
Telefonica UK
1717
TF Customer View Reporting
TFinVF Vendor from CM data
Cell_Owner field added
JVID – Common to both operators
Report showing cells for a City with both TFinTF and TFinVF cells
Telefonica UK
1818
TEF Hosted Networks Reporting
Report showing a shared Telefonica owned 2G site with both TF & VF Cells
VFinTF sites Have ‘V’ prefix
Telefonica UK
1919
Reporting Capability – Mapped Metrics
With two radio vendors (pre-RAN share) we used mapped
metrics; the addition of TFinVF data (JVCO) means we now have three ‘vendors’ in key formulae.
Telefonica UK
2020
The Problem of Disappearing Cells @ NE Lists
Routine performance monitoring & Beacon roll-out means we scrutinise the performance trends in Cities and Towns ….
…..the Beacon Roll out gave us a problem…….
….Using lots of Dynamic NE lists
Telefonica UK
2121
Reporting Capability – Disappearing Cells @ NE Lists
Telefonica UK
2222
Reporting capability – The problem with NE lists
Telefonica UK
2323
Reporting Capability – Disappearing Cells @ NE Lists
Dynamic NE lists do not include these “Inactive” or “Disabled” sites
In this example a query run in week #25 will not include these cells. (A previously reported value cannot be replicated)
The SolutionUse the GIS system to create NE lists; with a MYCOM OSI modification so all sites including NE_STATUS “Inactive” and “Disabled” will be included in the list.
The Problem
Telefonica UK
2424
Summary – The Good & The Bad
The Good• Changing the export file is simple. • The “adaptive adaptor” also makes a change to the import easy to implement.• Mapped Metrics enable network wide reporting.• We now have a good understanding of RAN sharing.
The Bad• Life is more complicated!• More Adaptors to manage. • Missing data (in either direction) needs manual intervention.• Troubleshooting data issues is slow.• The ‘more KPI’ requests keep coming. • NE lists generation still not proven.
Telefonica UK
2525