Providing VoLTE & RCS services and connecting enterprise customers to these new networks and services is an opportunity for the service providers to enhance their services and generate growth. Surveying ways in which this opportunity can be realized.

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

2. 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
Radvision Proprietary 2

3. 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
Radvision Proprietary
3
3

4. 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
Radvision Proprietary 4

5. 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
Radvision Proprietary 5

6. But will the
consumer pay
for the service?
Picture www.HikingArtist.com
Radvision Proprietary 6

7. Service providers are
looking for the
customers who will
pay for the new rich
services
Picture www.HikingArtist.com
Radvision Proprietary 7

8. VoLTE & RCS for the Enterprise
 The Enterprise is willing to pay for
– Quality
– Availability/Reliability Service
– Interoperability Provider
– Manageability
 Support B.Y.O.D trend VoLTE
& RCS
 CAPEX reduction
 Support cloud trend
 Interests of the SP and Enterprise align
Radvision Proprietary 8

9. Enterprise UC can be hooked “joyn”ed with
consumer UC
Radvision Proprietary
9
9

10. Rich Communication Suite (RCS)
 VoLTE - Voice over LTE
 RCS enables interoperable, enriched communication services
with multimedia capabilities, beyond voice and SMS
Radvision Proprietary 10

11. 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
Radvision Proprietary 11

12. 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
Radvision Proprietary 12

13. 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.
Radvision Proprietary 13

14. RCS 5.0 Major Areas
Bold Font – New Feature, *Source: GSMA – RCS 5.0
Italic – updated feature Specifications
Radvision Proprietary 14

15. 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
Radvision Proprietary 15

16. Connecting the Enterprise Use Case #1
Operator Network Enterprise
IMS/VoLTE/RCS Network
R
E
RCS APIs Proprietary UC
VoLTE & UC to
RCS S
RCS GW
T
Radvision Proprietary 16

17. Connecting the Enterprise Use Case #2
Operator Network Enterprise
IMS/VoLTE/RCS Network
Proprietary UC
VoLTE & VoLTE & RCS UC to
RCS Trunk over Trunk RCS GW
Radvision Proprietary 17

18. Connecting the Enterprise Use Case #3
Operator Network Enterprise
IMS/VoLTE/RCS Network
VoLTE & RCS based
VoLTE & VoLTE & RCS
RCS Trunk over Trunk
Radvision Proprietary 18

19. 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
Radvision Proprietary 19

20. 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)
Radvision Proprietary 20

21. A Global Market Leader
 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
Radvision Proprietary 21

22. Two Complementary Business Units
 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
Radvision Proprietary 22

23. Two Complementary Business Units
 Video Business Unit (VBU)
– Video and Voice Conferencing Solutions for the Enterprise Market
– Infrastructure, Management Software and Endpoints
Radvision Proprietary 23

24. RADVISION End-to-End Video Solution
Radvision Proprietary 24

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

26. End-to-End Product Portfolio
Turnkey Solutions - Professional Services
Media
Client Products & Projects SIP Server Products Quality
Monitoring
VoLTE & RCS Client Frameworks SIP Server Frameworks
SIP Server Presence B2BUA
Core & Events
Multimedia Terminal Framework VoLTE &
RCS
Testing &
Protocol Toolkits
Validation
SIP Developer Suite NAT Traversal MSRP A-RTP Diameter Products
IMS SIP Suite H.323 MEGACO MGCP 3G-324M
Radvision Proprietary 26

27. 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
Radvision Proprietary 27