21
Driving Communications Directly Into The Web Browser 2012 / 12 / 10 NCTU CS

Driving Communications Directly Into The Web Browser

Embed Size (px)

DESCRIPTION

Driving Communications Directly Into The Web Browser with WebRTC

Citation preview

Page 1: Driving Communications Directly Into The Web Browser

Driving Communications Directly Into The Web Browser

2012 / 12 / 10 NCTU CS

Page 2: Driving Communications Directly Into The Web Browser

Outline

Introduction Architecture Demo Conclusion References

Page 3: Driving Communications Directly Into The Web Browser

Introduction Architecture Demo Conclusion References

Page 4: Driving Communications Directly Into The Web Browser

2008 Gmail Video Chat

2010 Google bought GIPS.

2011 Google Hangouts (Still a plugin-based app) WebRTC was open sourced.

WebRTC + Google

Page 5: Driving Communications Directly Into The Web Browser

Why WebRTC?

A lot of web services already use Real-time Communication (RTC), but need downloads, native apps or plugins. Skype Facebook (uses Skype) Google Hangouts (uses Google Talk) etc

Page 6: Driving Communications Directly Into The Web Browser

<video/> <audio/>

Page 7: Driving Communications Directly Into The Web Browser

Web Real-Time Communication

Open Standard Open Source GIPS Codec Engine Echo Cancellation Packet Loss Concealment NAT Traversal Jitter Buffer Cross Browser No Plugins

Pure JavaScript APIs

Page 8: Driving Communications Directly Into The Web Browser

How does WebRTC work?

Page 9: Driving Communications Directly Into The Web Browser

Introduction Architecture Demo Conclusion References

Page 10: Driving Communications Directly Into The Web Browser

Architecture

Page 11: Driving Communications Directly Into The Web Browser

WebRTC Component

API Web API

▪ MediaStream▪ PeerConnection▪ DataChannel

WebRTC Native C++ API

Transport / Session RTP Stack STUN / ICE Session Management

Page 12: Driving Communications Directly Into The Web Browser

WebRTC Component (cont.)

Voice Engine iSAC iLBC NetEQ for Voice Acoustic Echo Canceler Noise Reduction

Page 13: Driving Communications Directly Into The Web Browser

WebRTC Component (cont.)

Video Engine VP8 Video Jitter Buffer Image Enhancement

Page 14: Driving Communications Directly Into The Web Browser

Introduction Architecture Demo Conclusion References

Page 15: Driving Communications Directly Into The Web Browser

Demo

http://apprtc.appspot.com/

Page 16: Driving Communications Directly Into The Web Browser

Introduction Architecture Demo Conclusion References

Page 17: Driving Communications Directly Into The Web Browser

Conclusion

Browser-based Open source and standard Pure JavaScript and No plugins Market penetration will be almost complete!

Google、 Android、Mozilla、 Opera、Microsoft Apple is not yet involved. (due to FaceTime!?)

User’s behavior is a great wall.

Page 18: Driving Communications Directly Into The Web Browser

Conclusion (cont.)

Use Cases Browser to Phone

▪ Click to Call▪ Say good bye to PSTN

Video Conferencing P2P Video Streaming Online Gaming Customer Self Service

Page 19: Driving Communications Directly Into The Web Browser

Introduction Architecture Demo Conclusion References

Page 20: Driving Communications Directly Into The Web Browser

Reference

Real Time Communications without plugins http://www.html5rocks.com/en/tutorials/webrtc/basics/

WebRTC Project http://www.webrtc.org/home

WebRTC - @eCommConf 2011 http://www.slideshare.net/loopingrage/webrtc-ecommconf-2011

Google I/O 2012 - WebRTC: Real-time Audio/Video and P2P in HTML5 http://www.youtube.com/watch?v=E8C8ouiXHHk

What WebRTC means to Telecoms http://www.alanquayle.com/blog/2012/05/what-webrtc-means-to-telecoms.html

Page 21: Driving Communications Directly Into The Web Browser

Q&A