Patrice Crutel

Bouygues Telecom WebRTC Prototypes, An interview with Patrice Crutel

Patrice CrutelPatrice Crutel is Senior Arcitect for Core and Service Network Layer at Bouygues telecom. He is deeply involved in WebRTC work at Bouygues and is also a regular contributor to our WebRTC yearly conference. I asked Patrice to give us details of current work taking place at Bouygues with regards to WebRTC.

Who are the industry partners they are working with?

How are they tackling the WebRTC for mobile challenge?

What are the obstacles to deployments they are dealing with?

How far along are you with your WebRTC projects and who are your partners?

Over the past few months, we have launched several in-house prototypes. They are being used by employees at Bouygues Telecom. Quobis and Ericsson helped us in designing these prototypes in our own lab. We are continuing to meet with various players in the webRTC domain (webRTC GW suppliers and also Unified Communication solution providers) as well as in web application development. We are making progress within the company on testing and enriching via applications revolving around webRTC.

Do you have any projects for mobile terminals?

Clearly it is a positive step to deploy WebRTC on all devices, main interest we see is to be able to access our services on tablet-type devises basically because they have greater capacity than mobile phones, mainly due to the larger screen. A mobile terminal is still “handicapped” by its small size and the battery.

As iPhone do not support ViLTE, webRTC could be seen as an alternative to offer video “natively”.

What do you see as the business case for WebRTC? For instance, do you intend to open your future platforms to other clients?

For the time being, we are not considering opening our platforms. Firstly we are concentrating on WebRTC’s contribution to the services proposed by an operator to its clients. The OTT (Over-The-Top) content providers are not out to make a profit on this type of service. But will operators be able to do so? They need to have differentiation, one of which is better QoS/QoE but there needs to be more than that. Therefore, we will look into how to make certain value-added services associated with WebRTC profitable.

What is the largest obstacle for the deployment of WebRTC?

What discourages us the most are the regular changes made by Google on its browser, which can lead to a loss of service for our subscribers. For an operator, this is inacceptable. There are also problems with the battery life of mobile devices. WebRTC applications are extremely energy-greedy. This aspect needs to be improved and we are following such developments closely.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

+ 7 = 12