João Barbosa, WeDo Technologies

Transcription

1 João Barbosa, WeDo Technologies

2 TECHNICAL OVERVIEW CHALLENGES AUDITING TYPICAL ISSUES

3 TECHNICAL OVERVIEW CHALLENGES AUDITING TYPICAL ISSUES

4 Source: Ericsson Mobility Report 2015 VOICE OVER LONG TERM EVOLUTION (VoLTE) 2.9 Billion Mobile Broadband Subscriptions in 1Q15 Exabytes per Month 21.7 EB 30.6 EB 55% Growth In data traffic between 1Q14 and 1Q EB 6.2 EB 9.9 EB 14.9 EB 10x Growth In smartphone between 2014 and Source: Cisco Visual Networking Index Mobile, 2016 Forecast is 30.6 Exabytes per Month of Mobile Data Traffic by LTE NW in 138 countries 393 LTE network deployments in 138 countries VoLTE: It's Not Just About Voice spectrum utilization to support the massive growth in data traffic is the primary factor that justifies the business case for voiceover-lte (VoLTE). Longer term, however, the impact of VoLTE on operator networks and business models will be profound. Source: Light Reading, Greg Collins, VoLTE available in 29 countries 46 VoLTE deployments in 29 countries

5 VOICE OVER LONGTERM EVOLUTION (VoLTE) High-Definition (HD) voice and video services Enable of Rich Communication Services (RCS) share locations, high resolution pictures, video and audio messages VoLTE works over IP-based networks and only supports packet switching (PS) VoWiFi can share the same architecture and infrastructure as VoLTE and can help solving the indoor poor cellular network coverage issues The deployment of VoLTE due to its complexity adds great challenge to telco business transformation VoLTE Guaranteed QoS IMS VoIP Best-Effort Generic IP Network Carrier grade VoLTE is deployed on the IMS subsystem rather than a generic IP network (i.e. the Internet). This fact offers a level of control that is not available otherwise

6 VOICE OVER LONG TERM EVOLUTION (VoLTE) Better user experience HD voice quality Faster call setup time when compared with Circuit Switched Fewer network resources consumption when compared with OTT voice apps Longer device battery life More efficient network with lower operational costs potential Rich communication service (RCS) enabling such as video calling, file transfer, real time language translation, video voic , etc. Generate alternative revenues on customers data packages Voice revenues declining but customers are used to pay for voice calls

7 VOICE OVER LONG TERM EVOLUTION (VoLTE) Charging Strategy Time-based? Volume-based? Event-based? Other? Time-based usually the first choice based on MNOs experience New Business Models Bundled offers: voice combined with data Differentiated services with QoE based on diferent packages and offers Roaming dynamic offers

8 VOICE OVER LONG TERM EVOLUTION (VoLTE) VoLTE Calls IMS Function Nodes I-CSCF,P-CSCF, S-CSCF, Voice & Data Applications Policy Manager PCRF Evolved Charging LTE Core Network PGW, HSS,

9 TECHNICAL OVERVIEW CHALLENGES AUDITING TYPICAL ISSUES

10 CHALLENGES THE LONG TERM EVOLUTION (LTE) New Data Sources Control of new usage types on network elements (S-GW and PDN-GW) Collection of new data formats from the new LTE network elements (I-CSCF, P-CSCF, S- CSCF, ) New Technology Trends Vulnerabilities associated with an All-IP network (AIPN) Billing rules (services split from the bearer) Billing systems likely obstructing the ability for CSPs to maximize revenues Fallback to 3G for ALL voice calls LTE DATA Fallback to 3G for voice outside LTE coverage LTE DATA + VoLTE New Services Delivery Increased bandwidth allowing the inclusion of new services offers (M2M and OTT) Roaming still an issue between operators Interconnect issues (packet billing only or bi lateral agreements) Voice issues (VoLTE) Technological update Expensive technological update and integration with legacy Voice systems 3G Circuit-Switched Voice

11 TECHNICAL OVERVIEW CHALLENGES AUDITING TYPICAL ISSUES

12 USAGE TYPICAL IMPLEMENTATION SCOPE ENSURE ALL VOLTE RECORDS ARE COLLECTED AND DELIVER ACCURATE BILLS Control mechanisms to check the path of network VoLTE events from the switch to their inclusion in the bill, guaranteeing that usage is accurately reflected in customer billing High-level real-time views of actual xdrs flow based on service type or tariff class Reconciliation of usage data at summary and individual record level Trending - automatic learning of normal traffic profiles so that unexpected variations in real-time revenue streams can be detected and acted upon quickly

13 USAGE TYPICAL IMPLEMENTATION SCOPE CONTROL POINTS M1 IMS Voice Output M2 IP SMS Output M3 PGW Output BILLING M4 PCRF Usage CS Voice (MSC) IMS Voice M1 T1 F1 X4 X1 X2 X3 RATING M5 F5 X7 BILLING M6 Invoices M5 Rating Input M6 Rating Output M7 IN Output M8 Roaming M9 Interconnect M10 TAP IN M11 TAP OUT IP SMS PGW M2 M3 T2 T3 F2 F3 X5 MEDIATION M7 T7 F7 X8 X9 M9 T9 F9 INTERCONNECT ROAMING M8 F8 T8 VALIDATIONS X1 IMS Voice vs Rating In X2 IP SMS vs Rating In X3 PGW vs Rating In X4 IMS Voice vs IN X5 IP SMS vs IN X6 PGW vs IN X7 Rating IN vs Rating Out PCRF M4 T4 F4 X6 X10 M9 T9 TAP IN F9 IN Roaming Cleaning House M10 T10 F10 TAP OUT X11 X T M F Inter-system Trending Control Point FileSequence Check X8 Network vs Roaming X9 Network vs Interconnect X10 TAP IN vs IN X11 Roaming vs TAP OUT X12 TAP IN vs Roaming

14 USAGE KEY CONTROLS/ IMPACTS Controls Switch to Bill Event Count and Event Duration for VoLTE/VoWiFi Switch to Bill Event Count for IP SMS (LTE and Wi-Fi) Switch to Bill Data Volume monitoring Key business rules Business logic in the IMS control points to separate LTE and Wi-Fi CDRs typically based on accessnetworkinformation/cell ID Info fields Identification of IMS rating groups on LTE network elements (e.g.: PGW) Which CDRs will be used for interconnection? From CS network elements? From IMS network elements? Roaming: New TAP record types and fields No single network element will contain all charging elements: Correlation of data from SGSN/S-GW/P-CSCF Impacts on existing solution Additional MSC CDRs might be generated and necessary to discard from existing CS control/reconciliations Existing reconciliations might need to be updated to discard IMS traffic from systems like CBS, IN, Interconnection, etc, e.g.: IN IMS traffic identification based on Camel MSC Addresses Interconnection IP traffic identification

15 PLATFORM CONTROLLING CUSTOMER PROVISIONING AND SERVICES Subscriber Lifecycle + Services + QoS Canceled Pre-Active Active Barred HSS PCRF CRM Process Reconciliation Process Searching Process History Duplicate Handling Customer Report RAID TELECOM Tune Change Provisioning Lifecycle, Rules, Processes, etc Results Tune Correct Configure Investigation

16 PLATFORM TYPICAL IMPLEMENTATION SCOPE HSS M1 X1 M2 RATING CRM IMS PCRF M3 M4 X2 X3 X M LEGEND Inter-system Control Point CONTROL POINTS M01 HSS M02 CRM M03 IMS M04 PCRF VALIDATIONS X01 HSS vs CRM X02 IMS vs CRM X03 PCRF vs CRM

17 PLATFORM KEY CONTROLS Assure that LTE QoS levels (Quota & Bandwidth) are accurately provisioned on the platforms Perform integrity checks for new VoLTE customers and services Increased information synchronization span (new core NE s included on existing infrastructure) Customer data and services integrity between platforms (HSS vs. CRM) LTE policy & charging rules consistency between platforms (PCRF vs. CRM) Service parameters consistency between platforms (e.g., user and group profiles, subscription data) Customer unified identification between platforms (GSM IMSI, MSISDN, IMEI, LTE USIM)

18 RATING AND BILLING ASSURING RATING CHARGES AND INVOICE GENERATION Re-rating solution verifies the accuracy of the amount charged of the provided VoLTE services (e.g. discounts, taxes, billing rules, activation fees, late/missing or duplicate invoices) Isolation off all the VoLTE traffic for the rating and billing purposes, so it avoids double-charging the subscriber. Usually that is applied to Telco Operators using the zero-rate charging instead of any other rating algorithm to charge VoLTE traffic (volume-based, event-based, others)

19 TECHNICAL OVERVIEW CHALLENGES AUDITING TYPICAL ISSUES

20 TYPICAL SOURCES OF REVENUE LEAKAGE IN VOLTE Double charging for data and voice for the same call Charging based on incorrect record (e.g.: based on network data CDR instead on IMS voice CDR) Settlement issues leading to incorrect call charging Bearer manipulation for fraudulent data (typically zero-rated for IMS) abuse

21