2. AGENDA
§ Time for a change – Introducing Project Clearwater
§ Why the cloud?
§ Designing for the cloud
§ Clearwater function and architecture
§ Clearwater use cases
§ Project Clearwater Ecosystem
§ Case study
3. TIME FOR A CHANGE
§ IMS is "business as usual" for Tier 1 telco vendors
§ Complex and costly
§ Long release cycles
§ Closed and proprietary implementation
§ Typically on proprietary hardware
§ This model enables OTT providers to run rings around telcos
§ In-house software expertise
§ Continual innovation
§ Rapid release cycles
§ Creative use of Cloud technology and open source software
4. NETWORK FUNCTIONS VIRTUALIZATION
13 operators leading Industry Specification Group
on NFV under auspices of ETSI
“The new network will be built on high volume
industry-standard servers, storage elements, ethernet
switches and IT systems running software apps from
independent developers”
Operators embracing the concept of the "Software Telco"
5. ROUTES TO NETWORK FUNCTIONS VIRTUALIZATION
Proprietary
Hardware
Standard
Hardware
Virtualized
Environment
Implement all
hardware-specific
functions in
software
Design for
standard
hardware
Design for
the Cloud
Adapt software
to virtualized
environment
Project Clearwater
6. WHAT DOES IT MEAN TO DESIGN FOR THE CLOUD?
§ Using the same architectures as before is missing the point
§ “Stand on the shoulders of giants”
§ Telcos used to have the highest scale systems
§ Not so any more: Google, Amazon, Facebook etc etc
7. SCALABILITY OF TOP INTERNET PROVIDERS
§ Google
§ Served 2 trillion searches in 2012, 200 million an hour
§ Facebook
§ As of June 2013, users spent ~1 billion minutes an hour
§ Netflix
§ Streaming over 2 billion hours of video per month, 165 million minutes
an hour
§ Youtube
§ 6 billion hours a month, 500 million minutes an hour
§ Amazon
§ In 2012 EC2 estimated to consist of 100,000-1M physical servers
8. WHAT DOES IT MEAN TO DESIGN FOR THE CLOUD?
§ Using the same architectures as before is missing the point
§ “Stand on the shoulders of giants”
§ Telcos used to have the highest scale systems
§ Not so any more: Google, Amazon, Facebook etc etc
§ New ways to create massively scalable systems
§ Very well proven
§ Culture is very open
§ experiences with design patterns (blogs, conference talks, ...)
§ open source components
§ New philosophical approaches
§ APIs, APIs, APIs – it’s all about the ecosystem
§ Move fast – re-use rather then re-invent
§ Experiment – iterate and evaluate
9. PROJECT CLEARWATER – IMS IN THE CLOUD
The Cloud
Open Source
Open Standard APIs
+
+ =
Massively scalable,
very low cost,
IMS-based
mass-market VoIP
services platform
designed from the
ground up to leverage
the Cloud
Business Model
Innovation
+
www.projectclearwater.org
10. CLEARWATER – DESIGN OBJECTIVES
§ Massive scalability
§ Highly robust and resilient
§ Built-in basic calling services
§ Compliance with IMS specs
§ Standalone capability
§ Business model innovation
11. CLEARWATER – OBJECTIVES MET
§ Massive scalability
§ Tested at 10M subs, 20M BHCA: cost < €0.02 per sub per yr (EC2)
§ Elastic scalability demonstrated
§ Highly robust and resilient
§ Web-scale architecture, stateless SIP processing nodes
§ N+M pools, geo-redundancy demonstrated
§ Built-in basic calling services
§ Basic MMTel services included
§ Compliance with IMS specs
§ Tested with HSS, TASs, MGCF, AGCF, P-CSCF
§ Standalone capability
§ Built in mini-HSS used in lab trials and PoCs
§ Business model innovation
§ Released as Open Source
13. CLEARWATER APPLICATION EXAMPLES
§ Free-standing consumer voice and video comms
§ Hosted business voice
§ VoLTE
§ Developer API Ecosystem
§ PacketCable 1.x migration to 2.x
§ Class 5 switch replacement
§ RCS – Messaging
§ WebRTC
14. PROJECT CLEARWATER ECOSYSTEM
The Project Clearwater Ecosystem brings together
partners with products and expertise in
§ IMS technology
§ NFV infrastructure
§ Systems Integration
to fast track deployments of the leading
virtualized IMS solution