Your browser is not supported. Please update it.

7 March 2013

WebRTC: a web standard which may help carriers nonetheless

Another example of how operators want to make their networks more attractive to developers is seen in their attempt to co-opt the key upcoming standard webRTC ‘ part of HTML5, this should be a key weapon for over-the-top services against network-based voice and video, but the operators are showing themselves keen to turn it to their own advantage. Two partners in this effort, Mozilla and Ericsson, worked with AT&T on a demonstration in Barcelona.

This showed off internet-based voice and video calls that bridged traditional telephone services and the web, using webRTC. This sets up browser-based communications between different devices and allows programmers to build real time voice and video chat applications which execute within the browser interface without plug-ins. Mozilla wrote on a blog: “The demonstration also shows how Firefox can perform many functions usually confined to a mobile device, such as voice and video calls and SMS/MMS messaging.” The demo ran on Ericsson’s Web Communication Gateway.

The Swedish giant has shown a keen interest in webRTC. Among the various emerging web standards surrounding HTML5, this is one of the most significant for future mobile business models, and therefore one of the most hotly disputed. In mobile, it has mainly been seen as a way for over-the-top suppliers to steal yet more of the operators’ points of control, such as voice traffic. This agenda was visible when Google implemented WebRTC in its Chrome browser earlier this year. But as cellcos start to engage in a fumbling embrace with OTT services, they will look to harness WebRTC rather than fight it ‘ and Ericsson will be there to help them.

The Swedish giant, like Alcatel-Lucent, has focused heavily on services and platforms to enable its carrier customers to adapt to the web world and offer ‘Telco 2.0’ services. Its recent contribution was the first WebRTC-enabled browser specifically for mobile devices ‘ the experimental Bowser, one of many products of its huge R&D effort to keep mobile operators and their suppliers, rather than Google and co, in the driving seat of the mobile web.

Ericsson says it is also working hard on methods to connect WebRTC browsers and activities into a full IMS (IP Multimedia Subsystem) framework. This is where the real agenda is seen. While Bowser could be used by any developer, its aim is to lure programmers and content producers to platforms controlled by the cellcos. Like the effort to expose carriers’ network APIs to developers, allowing them to deliver functionality which would not be possible in OTT-only environments, Bowser also looks to showcase the advantages of tying apps closely to the functionality inherent in the telco network.

Meanwhile, Google is pursuing its own route to driving WebRTC and other HTML5 platforms. Its main weapon is its WebM video format, based on the VP8 codec it acquired with ON Technologies. It open sourced WebM in 2010 and hopes to make this a standard in WebRTC, wrongfooting rivals which support the alternative H.264/5. Google opposes the H.264 codec officially because it is royalty bearing (via the MPEG LA patent pool) while WebM is free.

To this end, it is building a framework, including security, around its codec and is now starting to transfer some of its premium content offerings from Flash to WebM. It has enhanced the security layer so that videos from YouTube and Google Play rentals are delivered encrypted to an HTML5 player. This will make WebM interesting to content providers, which are grappling with the challenge of delivering video to a variety of HTML5-supporting platforms without having to customize for each one separately.

So far, H.264 is still the de facto standard, and even WebM backers like Mozilla say they cannot ignore the more established platform. However, Google claims it is gaining ground and it is already working on the next generation codec, VP9, which the firm claims will be a ‘gigantic leap forward’ on its predecessor.

In its bid to have VP8 mandated in the upcoming WebRTC standard, Google is opposed by the H.264 community and also by a separate effort from Microsoft. The draft specifications for WebRTC, released by the W3C earlier this year, do not specify a particular codec. Google wants to exclude codecs which carry royalties. Meanwhile, with echoes of previous industry splits over Flash and other technologies, Apple may go its own way. It is currently following a proprietary route in Safari and Facetime, though based on H.264, making it the most committed ‘ and powerful ‘ backer of that codec. By contrast, Firefox and Opera do not support H.264 directly because of the royalties, though they can use the H.264 codecs within Windows or Mac OS X. These two browsers, plus Google Chrome and Microsoft Internet Explorer/Skype, will all support WebRTC. All except Microsoft have expressed support for V8, but that still means a difficult road ahead for Google.

In particular, if it excludes or sidelines H.264 in Chrome, it will find itself in the position Apple was over boycotting mobile Flash ‘ Chrome and Android devices (whose browsers are converging) will not play H.264 video content perfectly, while Apple products will, handing a marketing tool to Google’s rival on a plate. Mozilla’s CTO Brendan Eich wrote in a blog post last year: “Google is in my opinion not going to ship mobile browsers this year or next that fail to play H.264 content that Apple plays perfectly. Whatever happens in the very long run, Mozilla can’t wait for such an event.’ Although Mozilla has lobbied against H.264, Eich added: “What I do know for certain is this: H.264 is absolutely required right now to compete on mobile. I do not believe that we can reject H.264 content in Firefox on Android or in B2G [Boot2Gecko] and survive the shift to mobile.”

Meanwhile, Microsoft itself is contributing its own elements to the WebRTC working group, notably CU-RTC-Web (Customizable, Ubiquitous Real Time Communication over the Web). Since the acquisition of Skype, Microsoft, like Google, has a critical interest in shaping web voice and video communications and WebRTC would certainly be an important addition to Skype’s current work on a browser-based version of its software. It would modernize the software and allow it to interoperate with other services like GoogleTalk.