Etiqueta: WEBRTC

Real-Time Communications on automotive

Since Henry Ford opened the doors of his factory, innovation has been part of the manufacturing and operation process of the automotive industry. During the last years, some dramatic changes have been adopted, like the usage of electric/hybrid engines, autonomous and self-driving technologies, connected vehicles and user interactivity. 

WebRTC one of the key technologies for the next generation of cars

WebRTC can be one of the key technologies for connected cars, adding a communication layer to this challenging industry.

The global market for connected cars is expected to grow by 270 percent by 2022, according to a new report. More than 125 million passenger cars with embedded connectivity are forecast to ship worldwide between 2018 and 2022,

Internet of business

Today, most of the vehicles include some kind of onboard computer and screen, that helps the driver to control a wide range of functions of the car, including GPS and cruise control and some indicators about the performance of the car. In addition, mobile phones can be easily connected to the car (i.e., Carplay from Apple for iOS) adding more value to the user experience. For instance, it’s possible to send and receive Whatsapp messages using voice recognition tools, with no need to touch the screen while driving. 

WebRTC can be integrated into embedded devices

Today, WebRTC is one of the technologies adopted by over-the-top players and communication service providers (Google hangouts, Skype web, etc), with browser and mobile application versions. In addition, WebRTC can be integrated into embedded devices, which opens up the possibility to build new use cases in IoT, including verticals like telemedicine (adding multimedia to medical devices), intercoms, set-top-boxes, etc.

The adoption of webRTC by cars is interesting to boost user interactivity. Now, most of the onboard computers and personal mobile devices support WebRTC, so they are ready to manage real-time communications. Quobis had the chance to work in this field in the R&D project Sat2car, along with PSA Peugeot Citroen and other industry stakeholders.


Fig.1. Car to agent communications with signaling and media ciphered.

Video assistance for car-sharing, car-pooling, and rental

One of the use cases consists of providing assistance and videoconference services to users of a professional or pay-per-use fleet.

WebRTC provides functionalities like audio/video conference with customer service of the car manufacturer, assurance services or fleet manager or event audio/video conference between users. This helps drivers, that are not familiar with the car, to access the support services.

Supervisor mode

Real-time communications can be also adopted for adding a supervisor mode. As an example, the driver of a fleet or car-sharing company can be contacted from a smartphone for supervision (from parents, fleet manager, end customer, etc.). In this scenario, car information (speed, GPS, load weight, etc.) and cameras can be available for communication, so car owners can have some type of control of the behavior of the driver and performance of the car.  In this case, different cameras for specific zones (driver cabin, cargo cabin, etc.) can be used for supervision.

Emergency Calling

Another use case for WebRTC is an emergency call where a WebRTC client is running in the Car PC or onboard unit. As an example, the video from the car can be recorded in 5 minutes buffer mode. The driver or a crash sensor can activate an emergency call to customer service or emergencies, allowing them to have access to the video from the car and to the sensor’s information (speed, GPS, etc.) in real-time. Others (police, the insurance company,….) can receive automatically the recording of the last 5 minutes. In addition, in case of an emergency, drivers near the emergency location receive a notification to be careful or asking for help or assistance. 

Assistance in case of overtakes

Another possibility is real-time video transmission to provide better assistance in case of overtakes. Imagine large vehicles or vans that could transmit real-time video from frontal camera to the onboard units of vehicles just behind in order to facilitate overtaking. For instance, large vehicles can have a stick in the rear of the vehicle to notify drivers that they provide this feature (i.e. message: “Video car enabled – use my license plate number to connect to my front camera). This connection could be automatically in the car has a camera and the truck a stick with a QR code. In any case, as this communication is critical, security procedures will be included to validate the veracity of video source and remove/reduce video delays. 

WebRTC and the autonomous car

For the moment, we have been talking about traditional cars but this is even more interesting for autonomous cars. Users will be available to work from the car, so interactivity will be even more important. Provide tools for entertainment or just connectivity to work from the vehicle will be one of the demands of this new market.

There are different use cases for these vehicles. As an example, one of the use cases is when the driver recovers the car control because of working areas (or difficulties in the interpretation of video to take decisions autonomously), car information is transmitted to the central service. This video can be used as learning material, taking into account the actions of the driver. 

Source: Nvidia

Notification System

Another possibility for connected and legacy cars are notification system. For instance, some events can be detected by the camera from the car in real-time and transmitted to a notification system that generates alarms or notifications to the drivers in the same area: traffic jams, accidents, emergency, parking availability, etc. There are some current tools to expose this type of issues (i.e. Google Maps or Waze) but they lack of real-time feedback.


Fig 2. car-sharing information from front camera to feed an AI system that will launch notifications

New movements on RCS and WebRTC complementary

by iago.soto | RCS is an initiative of the GSM Association (GSMA) based on the IP Multimedia Subsystem (IMS) to help network operators to make services interoperable. RCS refers to Rich Communications Services and its brand is joyn.

RCS bris new messaging services that were not available on traditional IMS networks, like instant messaging, real presence, live video and file sharing across different devices and telcos. While VoLTE is related to access (see post “WebRTC and VoLTE”), RCS is pure application, so can be identified as part of the same segment as WebRTC.

RCS depends on your device and telco provider, because is not available in all the countries. Telcos identified RCS as the best way to compete with OTT players like Whatsapp or Viber, but the adoption was quite poor for the moment, because users don’t see a relevant advantage to OTT.

GSMA states that 32 countries and 87 operators are already supporting or will do in 2015, but the real adoption seems to be quite poor for the moment.

Screen Shot 2015-10-01 at 10.39.47

While WebRTC will be adopted by developers, internet companies and OTT players, large and tier-1 telcos seem to be exploring the potential of RCS as the technology to make collaboration a reality. In this post we’ll compare both technologies as they are application-focused in the same market (unified communications and collaboration) and explore the possibilities for telcos to support both.

COMPARING RCS TO WEBRTC

Three points are key to compare these application-layer technologies.

  • Infrastructure

WebRTC does not define the signalling mechanism, while standards are quite open and lots of different implementations (including some opensource) are available. RCS implementations are quite closed instead, as they depend on a specific implementation by the telco that needs to have an IMS core and a specific RCS implementation. That means a high investment by comparison with WebRTC.

  • Devices

While WebRTC works in any device that can run a browser (tablets, PCs, etc) or even smartphones with native applications, RCS is only supported on smartphones, some times natively in the devices or accessible from application stores.In iOS devices, WebRTC is not supported on browsers, so you need to install native or hybrid applications to have a similar functionality. Despite this, we can say that WebRTC works in more devices than RCS as you can install WebRTC-enabled browsers in almost all the devices, at no cost.

  • Quality of experience

WebRTC makes possible to build lots of user scenarios by comparison with RCS but telcos has major control over RCS services, so the quality of experience perceived by the user could be better. Telcos can control the bandwidth available and offer a better service for RCS compared to a pure internet service like WebRTC.

RCS AND WEBRTC WORKING TOGETHER

While WebRTC is designed to work on web browsers with an impressive flexibility in terms of use cases that can be implemented, some drawbacks make IMS-based RCS more acceptable and a good complement to the WebRTC offer. This is the reason why 3GPP designed standard architectures for both solutions and some gateway vendors support both technologies.

3GPP- Quobis

3GPP: Standard IMS architecture for WebRTC.

At Quobis we understand that RCS is just a use case that can be emulated by WebRTC. Smartphone Native or hybrid application are a reality with WebRTC and the type of features that RCS is providing (IM, video, etc) are part of the traditional WebRTC capabilities. The two concerns around WebRTC on smartphones are closed to be solved:

  • Access to the agenda or contact list, possible using native applications, to build communications tools accessing to the existing contact lists.

  • Access to the notification engine, that is already possible from native applications and soon is going to be available from browsers. This makes possible to have a WebRTC service closed (not open in the browser) to receive a notification (i.e an incoming call)

Depending on gateway capacities it’s possible to support both technologies including also interoperability (sharing presence, instant messaging, etc between WebRTC services and RCS). WebRTC can be the enabler to support ad-hoc value-added services like creating a telco-based over-the-top voice service, to integrate voice/data into customer’s web experiences and /or involved the developers in the telco market.

RECENT MOVEMENTS OF THE INDUSTRY

On September 3th0, 2015 Google announced the acquisition of Jibe Mobile. This cloud messaging company has a RCS-based core platform that also supported WebRTC and was used by different tier-1 telcos worldwide. This seems to be part of the strategy of Google to introduce RCS to the Android OS devices and could be a real disruption in a traditional telco-based technology as RCS.

In terms of the Google’s Android RCS software engineer, Google wants to promote RCS and build an ecosystem of developers and applications. Meanwhile, well-known analysts believe that Google is interested on building an alternative to iMessage or even Facetime.