keynote presentation: hybrid deployment for rtc paas

Hybrid Deployment for RTC PaaS

PETER DUNKLEY

HYBRID DEPLOYMENT FOR RTC PAAS | 04.08.162 |

Agenda

About Xura

Our view of RTC

On-premise deployment

RTC PaaS


Opaque identities

|

heritage global presence

innovation excellence

• #1 messaging provider in the world

• #1 voicemail provider• 20+ year history

• Intelligent, secure and personalized two-way dialogue across any device, website and app

• OTT like service with connectivity to legacy comms systems

• Cloud & virtualised services

• 35+ offices across 6 continents• 350+ customers globally• Powering 8 / 10 global operator groups

• Data insights• Carrier grade security• 24/7 support

Who are we?

|

As consumers communicate in richer ways, an Enterprise opportunity emerges – 63% of U.S. Enterprises are adopting or planning to adopt WebRTC services within the next year (Forrester October 2015)

Disrupting and improving real time communications is our mission

Growing consumer demand Opportunity for revenue growth

Changing how people communicate and interact

Bringing context and intimacy to an often impersonal mobile world

Building customer loyalty and retention with differentiated services

6+ Billion WebRTC Capable Devices by 2018


Agenda

About Xura

Our view of RTC


RTC PaaS


Opaque identities

| HYBRID DEPLOYMENT FOR RTC PAAS | 04.08.166

RTC (Real Time Communications)

Xura views RTC as the super-set of instantaneous and contextual, bi-directional, and embeddable, audio, video, messaging, and presence.

RTC can be used within native mobile apps and web-apps and is built on a variety of technologies including (but certainly not limited to) WebRTC, WebSockets, REST, APNS, and GCMS.

Enterprises can add RTC to existing or new applications to create new ways to engage with customers, build whole new apps and use-cases, and generally improve their services.


(RTC != WebRTC) but (WebRTC == RTC)

WebRTC and RTC are not the same thing!

While all WebRTC is RTC not all RTC is WebRTC.

RTC may not involve audio or video at all. Messaging can be implemented either using WebRTC (DataChannel) or without it.


forge beyond communications

forge by Xura is a feature rich award winning RTC platform

Basic Capabilities

• WebRTC audio• WebRTC video• WebRTC and non-WebRTC messaging• WebRTC and non-WebRTC file transfer• Presence• TURN

Advanced Capabilities

• Audio and video conferencing• Messaging, file transfer, and group chat• Offline message and file transfer store• APNS and GCMS notifications• Audio, video, messaging, file transfer, and

presence update recording• Messaging and file transfer archiving• Legacy fallback to telephony audio, SMS,

and MMS (available by special request)• Advanced TURN


forge client libraries

forge by Xura supports many device types

forgeAS


Agenda

About Xura

Our view of RTC


RTC PaaS


Opaque identities



Enterprise’s Data Centre


On-premise pro’s and con’s

Pro’s

• Regional and industry vertical regulation• (usually unfounded) security concerns• (usually unfounded) performance concerns• (usually unfounded) reliability concerns• Potential savings for very large deployments• Job security


On-premise pro’s and con’s

Pro’s

• Regional and industry vertical regulation• (usually unfounded) security concerns• (usually unfounded) performance concerns• (usually unfounded) reliability concerns• Potential savings for very large deployments• Job security

Con’s

• (usually) worse security• (usually) worse performance• (usually) less reliable• Much more expensive for most deployments• Job security


Agenda

About Xura

Our view of RTC


RTC PaaS


Opaque identities


RTC PaaS

PaaS Cloud


Pro’s

• (usually) better security• (usually) better performance• (usually) more reliable• Much less expensive for most deployments• Job security

RTC PaaS pro’s and con’s


Pro’s

• (usually) better security• (usually) better performance• (usually) more reliable• Much less expensive for most deployments• Job security

RTC PaaS pro’s and con’s

Con’s

• Regional and industry vertical regulation• (usually unfounded) security concerns• (usually unfounded) performance concerns• (usually unfounded) reliability concerns• May be expensive for very large deployments• Job security


Agenda

About Xura

Our view of RTC


RTC PaaS


Opaque identities


Hybrid deployment

PaaS Cloud Enterprise’s Data Centre

Media and other sensitive data is held in the

enterprise’s data center


Hybrid deployment benefits

• Manage regional and industry vertical regulatory issues and use the cloud

• Choose which data is in the cloud and in your data-center to manage security, performance, and reliability in a way that suits your needs

• Take advantage of the economies of scale that the cloud offers and make use of your own data-center investments

• Job security


Hybrid deployment use cases

• Retail banking and other finance applications

• Government applications

• Healthcare

• Education (and other verticals with “safe guarding” requirements)

• Big apps


forge advanced capabilities can be deployed on-premise

Advanced Capabilities

• Audio and video conferencing• Messaging, file transfer, and group chat• Offline message and file transfer store• APNS and GCMS notifications• Audio, video, messaging, file transfer, and

presence update recording• Messaging and file transfer archiving• Legacy fallback to telephony audio, SMS,

and MMS (available by special request)• Advanced TURN

forgeAS

powered by


Xura Elements powered by forge

Off-the-shelf widgets for rapid application development

• Click-2-call• Click-2-chat• Recording• Conferencing• Queue management


Agenda

About Xura

Our view of RTC


RTC PaaS


Opaque identities


What are opaque identities

• An online identity that does not obviously map back to the users real identity• For example, xfu1987e3sjk instead of

[email protected]

• Ideally, the user can log on with something easy to remember (like an email address of phone number) but is known on the platform by the opaque identity

• Technologies such as OAuth 2 can support opaque identities

• Using an external OAuth 2 provider means the platform might never have access to the users credentials

mailto:[email protected]


OAuth 2 and forge

Xura Cloud

IdentityProvider

Authentication Page*

Authentication Code

Authentication Code

Auth

entic

ation

Cod

e

Acce

ss To

ken

Requ

est I

denti

ty Iden

tity*

Identity

1

2

5

6

7

3

8

4

* the identity returned in step 8 may be completely unrelated to the credentials entered in step 1, the Xura Cloud never sees these credentials


MFA and OAuth 2

• The login process can have as many steps as you want

• Any combination of:• username• password• SMS• token authentication• biometrics

|

Summary

HYBRID DEPLOYMENT FOR RTC PAAS | 04.08.1628

• Hybrid deployment combines the benefits of on-premise deployment• Control over data handling• Cost effective for big apps

• and PaaS• Someone else handles monitoring and scaling• Cost effective for small apps

• Opaque identities• Hide the user’s real identity from the cloud

• Use MFA if you can


forge beyond communicationshttps://forge.xura.com

[email protected]

Presented at Real Time Web Solutions Conference

keynote presentation: hybrid deployment for rtc paas

Mobile