VoLTE Playing the Enterprise Game Amir Zmora VP Marketing & Products, TBU

2 Radvision Proprietary

2 Types of User Experience Approaches

Dedicated application (Lync, Viber, Skype etc…)   Allows using proprietary methods, signaling, features…   UI/experience separate from common phone usage

My UC App

3 Radvision Proprietary

2 Types of User Experience Approaches

Part of the phone (“true UC”)   VoLTE & RCS are changing phone user experience   All rich communication services available on contact list

3

4 Radvision Proprietary

The LTE Threat

  LTE makes OTT a bigger threat to the SP – SP sees increase in data, decrease in voice & SMS

revenue – Better & faster network…higher quality OTT services

5 Radvision Proprietary

VoLTE + RCS = Opportunity

  VoLTE & RCS will bring the rich communication services users are looking for

  In a different way than OTT –  Interoperable across networks – Part of their phone….pre-installed –  In managed quality

6 Radvision Proprietary

But will the consumer pay for the service?

Picture www.HikingArtist.com

7 Radvision Proprietary

Service providers are looking for the customers who will pay for the new rich services

Picture www.HikingArtist.com

8 Radvision Proprietary

VoLTE & RCS for the Enterprise

  The Enterprise is willing to pay for – Quality – Availability/Reliability –  Interoperability – Manageability

  Support B.Y.O.D trend   CAPEX reduction   Support cloud trend

  Interests of the SP and Enterprise align

Service Provider

VoLTE & RCS

9 Radvision Proprietary

Enterprise UC can be hooked “joyn”ed with consumer UC

9

10 Radvision Proprietary

Rich Communication Suite (RCS)

  VoLTE - Voice over LTE

  RCS enables interoperable, enriched communication services with multimedia capabilities, beyond voice and SMS

11 Radvision Proprietary

Interoperability Checkpoint

 Today only (switched) voice, SMS or e-mail, are really interoperable

 Existing enriched communication services are not standard or interoperable

 RCS is an evolution of operator’s legacy services focusing on user experience

 Agreed set of protocols and standards, based on IMS, allowing full interoperability with different operators and vendors

12 Radvision Proprietary

Evolution of RCS

 RCS 1.0 –  Enhanced Phonebook - Contacts enhanced with capabilities and

rich presence

–  Enriched Call - Call enriched with multimedia Sharing

–  Enhanced Messaging - Conversational messaging experience –  Based on session mode messaging as defined by OMA IM

SIMPLE 1.0

 RCS-e –  Presence based on SIP OPTIONS Message –  joyn Initiative

13 Radvision Proprietary

Evolution of RCS

 RCS 5.0 – Global interoperability is a key aspect of these

specifications – Backward compatible with RCS-e V1.2 – Presence based on SIMPLE or SIP OPTIONS – Supports both OMA CPM and OMA SIMPLE IM.

14 Radvision Proprietary

RCS 5.0 Major Areas

Bold Font – New Feature, Italic – updated feature

*Source: GSMA – RCS 5.0 Specifications

15 Radvision Proprietary

Integration with the Enterprise

  Enabling enterprise UC as part of the regular smartphone experience

  Connecting with existing enterprise UC solution

*Source: GSMA RCS API Detailed Requirements 1.1

16 Radvision Proprietary

Connecting the Enterprise Use Case #1

Operator Network IMS/VoLTE/RCS

Enterprise Network

Proprietary UC RCS APIs VoLTE &

RCS

REST

UC to RCS GW

17 Radvision Proprietary

Connecting the Enterprise Use Case #2

Operator Network IMS/VoLTE/RCS

Enterprise Network

Proprietary UC VoLTE & RCS over Trunk

UC to RCS GW

VoLTE & RCS Trunk

18 Radvision Proprietary

Connecting the Enterprise Use Case #3

Operator Network IMS/VoLTE/RCS

Enterprise Network

VoLTE & RCS based VoLTE & RCS over Trunk

VoLTE & RCS Trunk

19 Radvision Proprietary

Why is RCS good for the enterprise

 No need to invent the wheel – leveraging on services that the operators provide

 No need to maintain – the operators take care of reliability, scalability, QoS

 Seamless interoperability – between any device, any network, anywhere (including roaming)

 Can focus on the additional capabilities unique to the enterprise

 CAPEX reduction

20 Radvision Proprietary

Why is RCS good for the Service Provider

 Will continue to be a “Service Provider” and not a “dumb pipe”

 Enhances the SP value proposition to the Enterprise  Increase revenue from customers willing to pay for

quality and reliability (Enterprise)

21 Radvision Proprietary

 Industry Leader in Video communications over IP products and technologies since 1992

 First to market with VoIP technology solutions

 (was) Listed on NASDAQ:RVSN March 2000

 440 Employees Worldwide  Acquired by Avaya June

2012

A Global Market Leader

22 Radvision Proprietary

  Technology Business Unit (TBU) –  Advanced HD Video Client Products and Frameworks –  Enabling Technology for Developers of Video and Voice over IP (V2oIP), IMS/

VoLTE/RCS Client/Server solutions –  Market Share Leader in Protocol Stacks (H.323, SIP, IMS) –  Professional Services Group

Two Complementary Business Units

23 Radvision Proprietary

  Video Business Unit (VBU) –  Video and Voice Conferencing Solutions for the Enterprise Market –  Infrastructure, Management Software and Endpoints

Two Complementary Business Units

24 Radvision Proprietary

RADVISION End-to-End Video Solution

25 Radvision Proprietary

Technology Business Unit Mission Making high-quality interactive multimedia communications products and services a reality

26 Radvision Proprietary

End-to-End Product Portfolio

Client Products & Projects

Turnkey Solutions - Professional Services

VoLTE & RCS Client Frameworks

SIP Server Frameworks

Multimedia Terminal Framework

SIP Server Core

Presence & Events

B2BUA

NAT Traversal MSRP A-RTP

Protocol Toolkits Diameter

IMS SIP Suite H.323 MEGACO MGCP 3G-324M

Media Quality

Monitoring

VoLTE & RCS

Testing & Validation Products SIP Developer Suite

SIP Server Products

27 Radvision Proprietary

Conclusion

 Service Providers can’t afford not to deploy VoLTE & RCS

 Connecting enterprise UC with RCS will – Give the user a unified interface (consumer/enterprise) – $ for the Service Provider – Simplify things for the enterprise

 There are different ways to create such a connection: – REST APIs or Trunk – GW at the Service Provider/Enterprise – Native support by the Enterprise