This document discusses the history and architecture of WebRTC, a free, open-source project that enables real-time communication via simple web APIs. It began with Gmail video chat in 2008 and was open-sourced by Google in 2011. WebRTC uses open standards and requires no plugins, with media transfer happening directly in JavaScript. The architecture includes APIs, transport/session layers, voice/video engines, and support for NAT traversal, codecs, and error concealment. A demo of WebRTC is available at apprtc.appspot.com. While adoption is growing, Apple has not participated due to FaceTime. WebRTC could eventually replace PSTN phone systems and enable new applications like video conferencing.

1. 2012 / 12 / 10
NCTU CS

2.  Introduction
 Architecture
 Demo
 Conclusion
 References

3.  Introduction
 Architecture
 Demo
 Conclusion
 References

4.  2008
 Gmail Video Chat
 2010
 Google bought GIPS.
 2011
 Google Hangouts (Still a plugin-based app)
 WebRTC was open sourced.

5.  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

6. <video/> <audio/>

7.  Open Standard
 Open Source
 GIPS Codec Engine
 Echo Cancellation
 Packet Loss Concealment
 NAT Traversal
 Jitter Buffer
 Cross Browser
 No Plugins
 Pure JavaScript APIs

9.  Introduction
 Architecture
 Demo
 Conclusion
 References

11.  API
 Web API
▪ MediaStream
▪ PeerConnection
▪ DataChannel
 WebRTC Native C++ API
 Transport / Session
 RTP Stack
 STUN / ICE
 Session Management

12.  Voice Engine
 iSAC
 iLBC
 NetEQ for Voice
 Acoustic Echo Canceler
 Noise Reduction

13.  Video Engine
 VP8
 Video Jitter Buffer
 Image Enhancement

14.  Introduction
 Architecture
 Demo
 Conclusion
 References

15.  http://apprtc.appspot.com/

16.  Introduction
 Architecture
 Demo
 Conclusion
 References

17.  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.

18.  Use Cases
 Browser to Phone
▪ Click to Call
▪ Say good bye to PSTN
 Video Conferencing
 P2P Video Streaming
 Online Gaming
 Customer Self Service

19.  Introduction
 Architecture
 Demo
 Conclusion
 References

20.  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