Media Services - Beyond the MCU. Richard Tworek

Size: px

Start display at page:

Download "Media Services - Beyond the MCU. Richard Tworek"

Caroline Hopkins
6 years ago
Views:

2 Media Services - Beyond the MCU Richard Tworek

3 Workshop Leaders Chad Hart Dialogic Jason Fedore Tadas Straševičius FACEmeeting

4 D3-4 Beyond the MCU Chad Hart WebRTC Expo V

5 Multi-PARTY! Video Conferencing Image source:

6 Easy & cheap approach to multi-party: Mesh Full Mesh Works for a few parties No server cost Lowest latency 6

7 Mesh does not scale for many video conferees Full Mesh Clients get overloaded Encode costs more than decode Limited uplink bandwidth Inconsistent performance across participants 7

8 Traditional Telephony Approach: MCU Multipoint Control Unit (MCU) Good at manipulating all media Transcoding Transizing Transrating Interworking Server-side CPU intensive Client can request different conference mixes Usually client friendly Downsizing & mixing can reduce bandwidth Fewer client streams to process MCU 8

9 Traditional MCU resource usage Worst-case process: 1. Each stream decoded at the MCU 2. MCU mixes each conferee 3. MCU encodes individual mix for each conferee Ingress streams MCU Egress streams 6 MCU decodes 6 MCU encodes 6 9

10 Efficient MCU resource usage Efficient process: 1. Each stream decoded at the MCU 2. MCU mixes each conferee 3. MCU shares same encoder for all conferees Ingress streams MCU Egress streams 6 MCU decodes 6 MCU encodes 1 10

11 System CPU Utilization Resource efficient MCU with encoder sharing Encoder sharing vs. multi-encode 100% 80% 60% 40% 20% 0% Conferees Traditional MCU Dialogic Evolved MCU 30%-50% reduction in compute resources

12 Newer approach: SFU Selective Forwarding Unit (SFU) routing Clients send one & receive many Client can instruct SFU which streams to send High throughput Can be lots of downlink bandwidth Low latency SFU 12

13 Newer approach: SFU Selective Forwarding Unit (SFU) routing Clients send one & receive many Client can instruct SFU which streams to send High throughput Can be lots of downlink bandwidth Low latency SFU 13

14 New WebRTC approach: Simulcast Selective Forwarding Unit (SFU) with Simulcast Clients send multiple streams to SFU one high-bit rate one or more lower-bit Client directs SFU which streams to receive Reduces bandwidth vs. SFU Simulcast in WebRTC coming SFU High bitrate Low bitrate 14

15 A look at Google Hangouts with Simulcast

16 Future Approach with VP9 SVC? Selective Forwarding Unit (SFU) with SVC Clients send layered stream to SFU Layers have varying bitrates time, size, quality SFU directs who gets what Coming to WebRTC eventually SFU Layered bitrates: High Medium Low 16

17 Multi-party video summary comparison

18 Building a compelling UX with a MCU

19 Video UX: Traditional method MCU G Device Mixed stream

20 Video UX: Traditional method MCU Active Talker 3G Device Media Server Chooses Layout Mixed stream 1 2 3

21 Integrating Intel CS for WebRTC to your Web Application Tadas Strasevicius, CTO FACEmeeting Jason Fedore, Founder of FACEmeeting

22 Agenda What is FACEmeeting? What problems we solved with Intel CS? Intel CS integration to your web app: Conference Server Installation Adding Intel CS SDK to your server side Adding Intel CS SDK to your client side

23 What is FACEmeeting? The next generation video platform

25 Why Intel CS for WebRTC? Stable multiparty video conferencing solution WebRTC compatible Signaling WebSockets Scalability Easy integration Hardware acceleration in server side

26 Why you need MCU? It is not possible to make multi-party meetings without enough device resources High local CPU consumption Bandwidth limit High battery consumption Best scenario for mobile devices

27 Peer to Peer model That s why we love WebRTC

28 MCU model Save your device resources

29 Hybrid model with Intel CS WebRTC is so great because of P2P {Leave data channel open using P2P} {Fallback to Intel MCU if needed}

31 L00ks good, h0w to st4rt? Step by step + Download and install Intel CS to your server + Using Client SDK integrate to your web application

32 Integration Steps Installing conference server Integrating Intel CS SDK to server side Integrating Intel CS SDK to client side 1 2 3

33 Intel CS modes Forwarding reducing outgoing streams Mix Mode use only one incoming and one outgoing stream

34 Install Intel CS to your server Step by step # Download from # Configure your server for Intel CS installation # Install it on your server (Ubuntu LTS* 64-bit recommended) + bin/init.sh deps # Enable hardware media acceleration # Run MCU + bin/start-all.sh # Configure MCU cluster (not necessary if you don t need scalability)

35 Fast integration to your web app Front and back ends # Server side integration with Intel CS server SDK # Front end integration with Intel CS client SDK

36 Intel CS integration to your web app server-side Step by step Add Intel CS Server API file Create Token Create Room (or use existing)

37 Intel CS integration to your web app front-end Step by step 1. Get local media 2. Get Token from server-side 3. Connect to room 4. Add event listeners 5. Subscribe mixed stream 6. Publish your local stream

38 MCU administration Awesome tool Server resources monitoring Services/Rooms management Logs monitor Users management

39 Contest Win FREE T-SHIRT!

40 THANK YOU FOR YOUR ATTENTION! Tadas Strasevicius CTO, FACEmeeting Facemeeting.com/tadas Jason Fedore Founder, FACEmeeting Facemeeting.com/jason.fedore

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.