Your browser is not supported. Please update it.

25 October 2012

Ericsson takes sides in WebRTC, and won’t sit on the web sidelines any more

Significance: The initial mobile web experiences, like WAP and iMode, quickly slipped out of the operators’ control and the wireless community largely stayed on the sidelines of the next evolution of the platform, leaving the way open for Google and over-the-top players to dominate the agenda. Cellcos and their key suppliers, like Ericsson, have recognized that mistake now, and in the new wave of web standards, will aim to increase their influence and provide a superior platform for developers that harnesses the advantages of their networks. Hence Ericsson’s experimental WebRTC browser, which looks to integrate the emerging real time voice/video standard with the carriers’ IMS systems, is far more significant than its low key appearance suggests. It shows the mobile giant taking a more proactive role in new web platforms, and also taking sides in the row over the video codec for WebRTC ‘ lining up against Google.

Among the various emerging web standards surrounding HTML5, the WebRTC platform is one of the most significant for future mobile business models, and therefore one of the most hotly disputed. The technology allows programmers to build real time voice and video chat applications which execute within the browser interface without plug-ins. 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 latest contribution is the first WebRTC-enabled browser specifically for mobile devices ‘ 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.

Dubbed Bowser, the product is available as a free download for iPhone, iPad and Android devices. It has been created by Ericsson Research and Kristofer Dovstam, master researcher at the division, said in a statement: ‘We believe WebRTC is a very important part of future communication solutions in our industry, and are excited to provide developers with the first version of our experimental WebRTC-enabled browser.’ The firm has been heavily involved in the WebRTC standards process and has been developing prototype implementations for the past two years.

Bowser will enable iOS and Android developers to start experimenting with real time audio and video functionality in their mobile web applications, using standard and interoperable technologies. “It is an experimental browser that we have put out to allow us at Ericsson and developers to better understand the technology and use it in the best possible way,” said Daniel Enstr’m, director of multimedia technologies at the vendor, who stressed that the firm’s aim was not to commercialize the product per se, but to get developer feedback and increase expertise and understanding of mobile web platforms.

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.

While some operators have gone cold on IMS (IP Multimedia Subsystem), and are looking to deploy fully over-the-top services themselves, most expect full IMS-based services to be a driver of LTE differentiation and revenues. For instance, IMS-based voice (VoLTE) should promise many functions which will be hard to match in a pure OTT VoIP offering. But IP is not enough ‘ users in future will expect voice and video to be fully integrated into the browser, hence why a development like Bowser, which supports these facilities in a standard way but retains ties to IMS, is important.

It is very early days for WebRTC, which though a critical component of HTML5 – and therefore interoperability between browsers – could still be derailed by the ongoing battle over codec standards. It is currently being developed by the two main internet standards bodies, the IETF and W3C and consists of APIs for audio and video communications that developers can access when writing in Javascript. However, it has a long road to full adoption ‘ it needs to operate as one of a family of standards; and then there is the codec row between H.264 and Google-backed VP8.

Ericsson is supporting H.264 because it is more established with ‘a ton of implementations … a well-defined licensing model and many hardware platforms with integrated support for the codec,” as Enstr’m told Techworld. However, Google has favored VP8 ‘ officially as part of its support for open source and royalty-free web technologies (H.264’s administrator, the MPEG LA group, charges licensing fees); but also because it aims to control as many critical components as possible to maintain its grip on the future web platform. It acquired the WebM technology based on VP8 with the purchase of On2 Technologies, and then snapped up a string of firms specializing in real time voice and video – GrandCentral (now the basis of Google Voice), Gizmo5 (formerly SIPphone), and Global IP Solutions, maker of Skype-alike VoIP, video and conferencing products.

Google wants V8 to be mandated in the upcoming WebRTC standard, an effort in which it will be 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: “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.

Unlike Google and Mozilla, Microsoft has not implemented draft versions of WebRTC in its browsers, and it is taking a different approach with CU-RTC-Web anyway. In contrast to Google’s stance, it wants a flexible standard with no single codec specified. Instead of elements like codecs, or the way media is sent, being predetermined, there will be flexibility for developers to optimize the techniques for their own services. Microsoft says the experience it has gained from Skype has indicated the pitfalls of incompatibilities or over-rigid standards in driving uptake of VoIP.

Microsoft is not so much trying to define the future of real time web communications ‘ even with Skype, it is in a poorer position to do that than the real web powerhouses ‘ but to ensure that Google and Mozilla do not get everything their own way. It has embraced the vision of pushing everything into the browser ‘ not just apps and data, but voice and video too ‘ belatedly, and hopes to leverage Skype to ensure it has a place at the table.

As expected, the main firms defining the battle lines over WebRTC are the platform majors, but the mobile giants know that, this time around, they must be active in shaping the next generation web to the needs of their cellco customers, rather than sitting passively on the sidelines, or hoping the change just won’t happen. So just as Google’s On2 acquisition, and the codec war it sparked, are more significant than their low key announcement suggested, so the under-the-radar appearance of Bowser should not be dismissed as just another clever piece of R&D from Ericsson Research boffins. Instead, that release sees Ericsson taking sides in an escalating mobile web war which goes to the heart of its carrier customers’ service models ‘ and aligning itself against Google.