C* Summit EU 2013: Capitalizing on Data in Telecommunications: The Cassandra Way

Rokesh Jankie |CTO, QAFE Inc. , [email protected] Hallo Khaznadar |CAO, QAFE Inc. , [email protected]

Capitalizing on Data in Telecommunications: The Cassandra way

#CASSANDRAEU CASSANDRASUMMITEU@QAFE www.qafe.com

mailto:[email protected]


http://www.qafe.com

#CASSANDRAEU CASSANDRASUMMITEU@QAFE

*Introduction

*Business Case

*Solution Direction

*The Cassandra Way

*Improvements and Future Directions

*ConclusionsThe name of the Telecommunications Company cannot be mentioned due to NDA.

Agenda


IntroductionQAFE & Qualogy


*Qualogy is Oracle Platinum Partner

*Qualogy was founded in 1998

*QAFE is a Qualogy subsidiary founded in 2007

*QAFE is a development Platform focussed on

- Integration

- Front-end technologies

- Oracle Forms Modernization

Qualogy and QAFE

Visit www.qualogy.com and www.qafe.com for more information

http://www.qualogy.com

http://www.qafe.com


Business CaseCustomer driven situation


Telecommunications and core Business*Billing is core business

*Input for billing are “CDR”s

*Call Data Records (CDR) contain information on calls made (besides Voice, also for Data).

*The process of handling CDRs is called Mediation


Mediation!

!

!

“Telecom Mediation is a system which acts as an interface or a middle layer between network elements and billing system/down stream applications like Fraud Management Systems, Revenue Assurance, Data Ware house etc.”


Call Data Records*Processing and parsing

*Dependent on switches and configuration


Solution DirectionSetting up a scalable architecture


Complexity and setup with Cassandra

CS#

R7#

R8#

R9#

Rx#

MEDIATION# Target#Sys.#

BSS#

DWH#

ICT#

ERS#

SWITCHES(

CS#

R7#

R8#

R9#

Rx#

Decoding# Media3on#Rules# Adap3ng#


BSS#

DWH#

ICT#

ERS#

SWITCHES(

CS#

R7#

R8#

R9#

Rx#

Decoder# Filtering# Enrichment# Adapter#

Decoding# Media<on#Rules# Adap<ng#


BSS#

DWH#

ICT#

ERS#

SWITCHES(

CS#

R7#

R8#

R9#

Rx#




BSS#

DWH#

ICT#

ERS#

SWITCHES(

CS#

R7#

R8#

R9#

Rx#

Decoder#

Decoder#

Filtering# Enrichment# Adapter#


MEDIATION#


Target#Sys.#

BSS#

DWH#

ICT#

ERS#

SWITCHES(

CS#

R7#

R8#

R9#

Rx#

Decoder#

Decoder#

Decoder#



MEDIATION#



Target#Sys.#

BSS#

DWH#

ICT#

ERS#

SWITCHES(

CS#

R7#

R8#

R9#

Rx#

Decoder#

Decoder#

Decoder#



MEDIATION#




Target#Sys.#

BSS#

DWH#

ICT#

ERS#

SWITCHES(

IMS$

CS$

R7$

R8$

R9$

R7$

Rx$

Rx$

Decoder$

Decoder$

Decoder$

Filtering$ Enrichment$ Adapter$

Decoding$ Media=on$Rules$ Adap=ng$

MEDIATION$



Decoder$ Filtering$ Enrichment$ Adapter$

Target$Sys.$

BSS$

DWH$

ICT$

ERS$

SWITCHES(

IMS$

EPC$

CS$

R7$

R8$

R9$

R7$

Rx$

Rx$

R7$

Rx$

X$ Rx$

Decoder$

Decoder$

Decoder$


Decoding$ Media?on$Rules$ Adap?ng$

MEDIATION$




Target$Sys.$

BSS$

DWH$

ICT$

ERS$

SWITCHES(

IMS$

EPC$

CS$

R7$

R8$

R9$

R7$

Rx$

Rx$

R7$

Rx$

X$ Rx$

Decoder$

Decoder$

Decoder$


Decoding$ Media?on$Rules$ Adap?ng$

MEDIATION$




Target$Sys.$

BSS$

DWH$

ICT$

ERS$

SWITCHES(


Think about hardware

*Next Generation Data Center Appliance

*Scalable

*Hardware and Software Engineered to work together


Solution Direction: Data modelSetting up a scalable architecture


DataModel AbstractCREATE TABLE cdr_<recordType>_<mainIdentifier>By<subIdentifier1>And<subIdentifier2>...And<subIdentifierN>_Index ( mainIdentifier <anyType>, (callingNumber text,) date text, subIdentifier1 <anyType>, (answerTime timestamp,) subIdentifier2 <anyType>, (numberingPlan text,) . . subIdentifierN <anyType>, (natureOfAddress text,) recordId uuid PRIMARY KEY ((mainIdentifier, date), subIdentifier1, subIdentifier2, subIdentifierN) };!!INSERT INTO cdr_<recordType>_<mainIdentifier>By<subIdentifier1>And<subIdentifier2>...And<subIdentifierN>_Index(mainIdentifier,date,subIdentifier1,...,subIdentifierN, recordId) VALUES('59995611994','2013-10-01','subIdentifier1Value' ...,'subIdentifierNValue','c4e1ee6f-e053-41f5-9890-6746e6d51095')


DataModel: IndexesCREATE TABLE cdr_MoCallRecord_CallingNumberByAnswerTime_Index ( callingNumber text, date text, answerTime timestamp, recordId uuid PRIMARY KEY ((mainIdentifier, date), subIdentifier1, subIdentifier2, subIdentifierN) }; !

!INSERT INTO cdr_MoCallRecord_CallingNumberByAnswerTime_Index(mainIdentifier,date,answerTime,recordId) VALUES('59995611994','2013-10-01','13:43:40','c4e1ee6f-e053-41f5-9890-6746e6d51095') !SELECT recordId FROM cdr_MoCallRecord_CallingNumberByAnswerTime_Index WHERE callingNumber='59995611994' AND date='2013-10-01' AND answerTime > '13:00:00' AND answerTime < '14:00:00' !SELECT * FROM cdr_MoCallRecord IN (<list of recordId's>)


DataModel Visual/Implementation

UUID$ Da_P2$Da_P1$Id_Pn$Id_P1$ Da_Pn$

Actual'Data'


uuid_v1$ Da_P2_v$Da_P1_v$Id_Pn_v$Id_P1_v$ Da_Pn_v$

Actual'Data'


uuid_v1$ Da_P2_v$Da_P1_v$Id_Pn_v$Id_P1_v$ Da_Pn_v$uuid_v2$ Da_P2_v$Da_P1_v$Id_Pn_v$Id_P1_v$ Da_Pn_v$

Actual'Data'



uuid_vn$ Da_P2_v$Da_P1_v$Id_Pn_v$Id_P1_v$ Da_Pn_v$

Actual'Data'


uuid_v1$Id_P2$Id_P1$ Id_P3_v1$



uuid_v2$Id_P3_v2$

uuid_vn$Id_P3_vn$

Index&A&

Actual&Data&


uuid_v1$Id_P2$Id_P1$ Id_P3_v1$



uuid_v2$Id_P3_v2$

uuid_vn$Id_P3_vn$

Index&A&

Actual&Data&

uuid_v1$Id_P4$Id_P3$ Id_P5_v1$uuid_v2$Id_P5_v2$

uuid_vn$Id_P5_vn$

Index&Z&

UUID$ callType$dura/on$StartTime$Date$

Actual'Data'

CallingNm$UUID$ callType$dura/on$StartTime$Date$

73s7jabe$ Interna/onal$00:03:10$13:07:34$2013@01@03$

Actual'Data'

98asd23h$ local$00:01:23$22:18:09$2013@01@03$

kjbnfd72$ 00:12:02$08:10:03$2013@03@07$

CallingNm$

065782391$065782391$

069035802$ local$


73s7jabe$ Interna/onal$00:03:10$13:07:34$2013@01@03$

Index&CallingNm_By_Date_And_StartTime&

Actual&Data&

98asd23h$ local$00:01:23$22:18:09$2013@01@03$

kjbnfd72$ 00:12:02$08:10:03$2013@03@07$

CallingNm$

065782391$065782391$

069035802$ local$


73s7jabe$2013>01>03$065782391$ 13:07:34$

73s7jabe$ Interna/onal$00:03:10$13:07:34$2013>01>03$


Actual&Data&

98asd23h$ local$00:01:23$22:18:09$2013>01>03$

kjbnfd72$ 00:12:02$08:10:03$2013>03>07$

CallingNm$

065782391$065782391$

069035802$

22:18:09$98asd23h$

local$


73s7jabe$2013>01>03$065782391$ 13:07:34$

73s7jabe$ Interna/onal$00:03:10$13:07:34$2013>01>03$


Actual&Data&

98asd23h$ local$00:01:23$22:18:09$2013>01>03$

kjbnfd72$ 00:12:02$08:10:03$2013>03>07$

CallingNm$

065782391$065782391$

069035802$

22:18:09$98asd23h$

kjbnfd72$2013>03>07$069035802$ 08:10:03$

local$


Specifying Cassandra ClusterImplementation of scaling plan


Considerations*Datasize per month

*Time window for scaling up

*Replication Factor

*Decoding Factor

*Node size

*Cassandra Cluster size

!

* Technical note: Cassandra is not certified for Oracle Linux (yet)


Planning on Data growth*Number of Nodes = 4

*HDD per node = 8TB

*RAM = minimum of 32 GB

*CPUs = 4 cores (at least 16 GB ram per core, so increasing this one requires increasing in RAM).

*Every 6 months we’ll have to add 4 nodes!


The Cassandra wayWhy choose Cassandra


Requirements *Large Scale Storage

*Predictable Scalability

*High Availability

*Robustness of Mission Critical Application


What we found in Cassandra*Meets all our requirements!

*No compromise on performance (during data write)

*No single point of failure

*Easy to adopt TimeSeries

*Proven Technology

*Trusted High End Specialists you can count on!


Dramatic Performance *When Hardware and software were combined!


Improvements and Future DirectionsThings that can make a difference


Using the ExaBus Optimization*ExaBus built on top of Oracle Infiniband

*Extreme Performance and Resource Efficient

*Socket Direct Protocol rather than TCP-IP

*APIs are available

!

*QAFE created solution to make this work in SDP and non-SDP environments.


Conclusions


Creating more Business Value from Data*Create more valuable customer relations

*Reduction of Churn

*Tuned offerings for customers

*Targeted marketing

*Advanced network analyzing


*Business case is real!

*Complexity that results in architecture choices

As well as Hardware as Software

*Very Promising (technology and business-wise)

*Room for improvement and more efficiency

What we discussed today...

Rokesh Jankie |CTO, QAFE Inc. , [email protected] Hallo Khaznadar |CAO, QAFE Inc. , [email protected]

Capitalizing on Data in Telecommunications: The Cassandra way

#CASSANDRAEU CASSANDRASUMMITEU@QAFE www.qafe.com



http://www.qafe.com

Date post:	20-Jun-2015
Category:	Technology
Upload:	planet-cassandra
View:	626 times
Download:	0 times