Instavc White Paper. Future of Enterprise Communication

Size: px

Start display at page:

Download "Instavc White Paper. Future of Enterprise Communication"

Sophia Chapman
5 years ago
Views:

Future of Enterprise Communication InstaVC is a futuristic Video Collaboration platform for the organizations to achieve client-less and plugin free, real-time communication which enables

1 Future of Enterprise Communication InstaVC is a futuristic Video Collaboration platform for the organizations to achieve client-less and plugin free, real-time communication which enables peer-to-peer audio, video, and data sharing between browsers. InstaVC offer a unique and unmatched multiparty capability in the same suite of offering. Complete Customized Integration PeopleLink offers custom built Collaboration offerings with seamless integration with your web applications, ERP solutions and video enabling call center and support functions of your organization with Custom InstaVC offering on your own network and premises. Seamless Interoperability Connect with ease to the existing standard-based video systems while securing the prior invest- ments made.peoplelink ensures a seamless integration with the other Hardware based endpoints to conduct conferencing &presentation sharing to ensure much effective visual collaboration for your organization with necessary license. Page 1 of 8

Ultra High Definition (4K) Collaboration Instavc Experience Ultra High Definition video collaboration with PeopleLink's next generation software solutions.

The Solution seamlessly transforms into a full-fledged Telepresence suite with additional modules Problems with Existing WebRTC-Based RTC Solutions WebRTC-based RTC solutions change the way people

2 Ultra High Definition (4K) Collaboration Instavc Experience Ultra High Definition video collaboration with PeopleLink's next generation software solutions. Distinct team members can now connect visually with the ease of technology and opti- mized bandwidth. The Solution seamlessly transforms into a full-fledged Telepresence suite with additional modules Problems with Existing WebRTC-Based RTC Solutions WebRTC-based RTC solutions change the way people communicate, bringing real-time communication to the browser. However, as a new technology, WebRTC-based solutions require improvements in the following areas to be as complete as traditional RTC solutions. Mostly P2P communication based. The WebRTC standard itself as well as Google WebRTC open source reference implementation only focuses on peer-to-peer (P2P) communication, limiting most of the WebRTC-based solutions to two-party communication. Although some WebRTC solutions support multi-party chat, these solutions use mesh network topology, which is less efficient and can only support a few attendees for common client devices. Not fully accounting for client usage preferences. Although browsers are available for multiple platforms, not all users like browsers. That is,many mobile platform end-users prefer native apps, such as Android apps or ios apps. Additionally, some commonly used browsers, such as Internet Explorer, still do not natively support WebRTC. Lack of flexibility on MCU server. Some WebRTC-based solutions support Multipoint control unit (MCU) servers for multi-party communication. However, most of those MCU servers use a router/forward solution, which just forwards the publishers streams to the subscribers. Although this method fulfills part of the scenarios when clients have equivalent capabilities or SVC/Simul- cast is supported, it becomes a high requirement for clients to easily meet.to work with a wide variety of devices, MCU servers must do some media-specific processing, such as transcoding and mixing. Limited deployment mode choices for customers. Most of the existing WebRTC-based RTC solutions work as a service model hosted by service providers. This style provides all the benefits of a cloud service, but is not useful for service providers and those who want to host the service themselves for data sensitive consideration. Key differentiation of InstaVC InstaVC not only offers peer-to-peer WebRTC communication, but it also supports WebRTCbased multi-party video conferencing and provides the WebRTC client connectivity to other traditional video conferences, like SIP. For video conferencing, it provides router and mixer solutions simultaneously to handle complex customer scenarios. Additionally, it supports: H.264 and VP8 video codecs for input and output streams MCU multi-streaming Real-time streaming protocol (RTSP) stream input Customized video layout definition plus runtime control Flexible media recording Page 2 of 8

Easy to Deploy, Scale, and Integrate InstaVC Conference and Gateway Servers provide pluggable integration modules as well as open APIs to work with existing enterprise systems.

3 Easy to Deploy, Scale, and Integrate InstaVC Conference and Gateway Servers provide pluggable integration modules as well as open APIs to work with existing enterprise systems. They easily scale to cluster mode and serve larger number of users with an increase of cluster node numbers. In addition, InstaVC solution provides comprehensive client SDKs including JavaScript SDK, Android native SDK, ios native SDK, and Windows native SDK to help customers quickly expand their client applications with video communication capabilities. Secure, Intelligent, Reliable QoS Control Support InstaVC solution ensures video communication data security through HTTPS, secure Web- Socket, SRTP/DTLS, etc. Also the intelligent quality of service (QoS) control, e.g., NACK, FEC, and dynamic bitrate control, guarantees the communication quality between clients and servers against high packet loss and network bandwidth variance. Experiments listed in Figure 1 have shown that the Intel video engine handles up to 20% packet loss and 200ms delay. Figure 1. Packet Loss Protection Results with QoS Control Page 3 of 8

Full Functional Video Communication with InstaVC Conference Servers Flexible Communication Modes InstaVC offers both peer-to-peer video call and MCU-based multi-party video conference commu- nication

4 Full Functional Video Communication with InstaVC Conference Servers Flexible Communication Modes InstaVC offers both peer-to-peer video call and MCU-based multi-party video conference commu- nication modes. A typical WebRTC usage scenario is direct peer-to-peer video call. After connecting to the signaling server, users can invite other parties for P2P video communication. All video, audio, and data streams are transported directly between each other. Meanwhile, the sig- naling messages for discovery and control go through the signaling server. As Figure 2 shows, InstaVC provides a reference signaling server implementation called Peer Server. The client SDK also provides the customization mechanism to let users implement their own signaling channel adapter. Figure 2. P2P Video Communication with Peer Server InstaVC solution further offers the MCU-based multi-party video conference chat. All streams go through the MCU server the same as the signaling messages do as Figure 3 shows. This reduces the stream traffic and computing overhead on client devices compared to a mesh network solution Figure 3. Multi-party Video Conference Chat through MCU Server Page 4 of 8

Unlike most existing WebRTC MCUs, which usually work as a router to forward media streams for clients, InstaVC MCU server also handles the media processing and allows a wide range of de- vices to be

5 Unlike most existing WebRTC MCUs, which usually work as a router to forward media streams for clients, InstaVC MCU server also handles the media processing and allows a wide range of de- vices to be used in the conference. Users can subscribe to either the forward streams or mixed streams from MCU server The InstaVC MCU provides more flexibility on mixed streams. You can generate multiple video resolution mixed streams to adapt to various client devices with different media processing capa- bility and network bandwidth. Flexible Conference Recording When recording in InstaVC you can select any video feed and any audio feed. You not only can record switching across different streams that the conference room is offering (such as mixed and forward streams), but also select video and audio tracks separately from different streams. You can select the audio track from the mixed stream of participants and video track from the screen- sharing stream. Scaling the MCU Conference Server InstaVC MCU server was designed to be a distributed framework with separate components, including manager node, signaling nodes, accessing nodes, media processing nodes, etc. Those components are easy to scale and suitable for cloud deployment. Figure 4 shows an example from the conference server user guide for deploying an MCU server cluster. Figure 4. MCU Conference Server Cluster Deployment Example Page 5 of 8

Interoperability with InstaVC Gateway For legacy video conference solutions to adopt the WebRTC advantage on the client side, InstaVC provides the WebRTC gateway Key Functionality Offering InstaVC

264 to ad- dress the video codec preference difference between them. In addition, the gateway keeps the sessions mapping between WebRTC and SIP to support bi-directional video calls.

6 Interoperability with InstaVC Gateway For legacy video conference solutions to adopt the WebRTC advantage on the client side, InstaVC provides the WebRTC gateway Key Functionality Offering InstaVC gateway for SIP not only provides the basic signaling and protocol translation between WebRTC and SIP, it also provides the real-time media transcoding between VP8 and H.264 to ad- dress the video codec preference difference between them. In addition, the gateway keeps the sessions mapping between WebRTC and SIP to support bi-directional video calls. Figure 5 briefly shows how SIP devices can connect with WebRTC terminals through the InstaVC Gateway Figure 5. Connect WebRTC with SIP Terminals through the Gateway NAT Traversal Interactive Connectivity Establishment (ICE) helps devices connect to each other in various complicated Network Address Translation (NAT) conditions. The client SDKs support Session Traversal Utilities for NAT (STUN) and Traversal Using Relay NAT (TURN) servers. Figure 6 and Figure 7 show how client SDKs perform NAT traversal through STUN or TURN servers. Figure 6. NAT Traversal with STUN Server Page 6 of 8

7 Figure 7. NAT Traversal with TURN Server Mixer solution This Mixer approach is the traditional solution for multiconferencing, and has been used for years with great success. This success can be credited to the fact that it requires the least amount of intelligence in the endpoints. The architecture is based on having a central point maintain a single one-to-one stream with each participant. The central element then receives and mixes each incoming audio and video stream to generate a single stream out to every participant. One common term in the video conference industry for these centralized element is Multipoint Control Unit (MCU). In practice, use of an MCU usually refers to a mixer solution. Figure 8. Mixer Solution Mixers are very good solution for inter-operating with legacy devices. They also allows for full bit rate adaption because the mixer can generate different output streams, with different qualities for each receiver. Another advantage of a mixer solution is that it can utilize hardware decoding in the device, providing that many WebRTC devices would include the capability to decode a single video channel in the chipset. The main drawbacks are the infrastructure costs in the MCU. Additionally, because mixing requires decoding and reencoding, this introduces extra delay and loss of quality. Lastly, transcoding and composition may, in theory, result in less flexibility for the UI of the application (although there are workarounds for this issue). Page 7 of 8

8 Router solution The Router (or relay) approach became popularized by H.264 infrastructures, and it is the architecture being used by most of the new WebRTC platforms that have started without any legacy baggage. The architecture is based on having a central point receiving a stream from every sender and sending out a stream to every participant for each. This central point only does packet inspection and forwarding, but not expensive encoding and decoding of the actual media. Figure 9. Router Solution Hybrid Architecture - It s an intelligent use of both the above architectures to assess the type of call or the need of User to accordingly select the most optimal architecture for establishing the call. GLOBAL HEADQUARTERS Q3 - A2,A3, 10 th Floor, Cyber Towers, Hitech City, Madhapur, Hyderabad (India) Ph: +91 (040) vc@peoplelink.in Africa : Middle East : USA : UK : Canada : Third party trademarks / products mentioned (If any) are the property of their respective owners. The use of the word partner does not imply a partnership / relationship between PeopleLink and any other company. Product Images are for representation purpose only and hence; the original product may look different. PeopleLink Public Document PeopleLink Unified Communications Pvt. Ltd. ISO 9001:2008 Certified Company. Page 8 of 8

White Paper Conquering Scalable WebRTC Conferencing

White Paper Conquering Scalable WebRTC Conferencing Conquering Scalable WebRTC Conferencing Executive Summary Developers are embracing WebRTC technology for building their next generation services but leveraging only peer-to-peer topologies may not be enough.