How Uber Beacon Helps Improve Safety for Riders and Drivers

How Uber Beacon Helps Improve Safety for Riders and Drivers

  • December 22, 2018
Table of Contents

How Uber Beacon Helps Improve Safety for Riders and Drivers

Globally, there are approximately 1.3 million collision-related fatalities on the road every year. Crash fatalities are still the leading cause of death for people between 15-29 years old, impacting families, communities, and cities. Governments around the world are working to reduce the risks, committing more resources towards improving road safety.

At Uber, we want to do our part by committing the power of our technology to help make travel safer for everyone. We have multiple teams at Uber working on road safety, reflecting a variety of disciplines, and we’re approaching this challenge from a number of angles. On the platform itself, we have many features to help improve road safety, such as driving hour limits to help curb drowsy driving, a partnership with the GHSA to raise awareness about seatbelts, and a 911 assistance feature to make it easier for riders and drivers to receive emergency assistance.

Uber Beacon, launched in 2016, is one of our more visible safety products. This device mounts on the driver’s windshield and uses color-pairing technology to help drivers and riders connect more quickly during pick-ups. Drivers have the option to add a Beacon to their vehicle and can unpair the device at anytime.

Beyond its visual signaling, the Beacon device also contains an accelerometer and gyroscope, similar to the sensors that currently exist in most smartphones. This sensor technology makes Beacon a perfect complement to our recently announced automatic crash detection feature, a solution that harnesses the power of GPS and other sensors in the smartphone to detect possible crashes. After a possible crash is detected, Uber initiates a Ride Check by reaching out to both the rider and the driver to offer quick assistance.

Source: uber.com

Share :
comments powered by Disqus

Related Posts

Implementing the Netflix Media Database

Implementing the Netflix Media Database

In the previous blog posts in this series, we introduced the Netflix Media DataBase (NMDB) and its salient “Media Document” data model. In this post we will provide details of the NMDB system architecture beginning with the system requirements—these will serve as the necessary motivation for the architectural choices we made. A fundamental requirement for any lasting data system is that it should scale along with the growth of the business applications it wishes to serve.

Read More
Bye bye Mongo, Hello Postgres

Bye bye Mongo, Hello Postgres

In April the Guardian switched off the Mongo DB cluster used to store our content after completing a migration to PostgreSQL on Amazon RDS. This post covers why and how At the Guardian, the majority of content – including articles, live blogs, galleries and video content – is produced in our in-house CMS tool, Composer. This, until recently, was backed by a Mongo DB database running on AWS.

Read More