.svg){kind=small}
For the first time it is possible to use the Auto API to access information
- from the Advanced Driver Assistance Systems (ADAS) of cars,
- about the charging sessions of electric vehicles, and
- and about car crashes.
The High Mobility platform and marketplace allows hardware-free access of live vehicle data. Our platform is connected to the cloud systems of an ever growing list of vehicle manufacturers, which in turn get their data directly and often in real-time from the vehicles.
The Auto API is the data protocol that is used to access data from our platform. The data points of the Auto API are universal and not specific to certain manufacturers. This allows development teams, software companies and startups to build cross-brand services without having to integrate with each manufacturer separately.
The addition of new data points to the Auto API, also in combination with the existing ones (click here for the full table), will enable a whole range of new connected car services, mobility applications and business opportunities.
Advanced driver-assistance systems (ADAS)
Advanced driver-assistance systems (ADAS) are electronic systems that support drivers in certain critical or dangerous situations. The earliest ADAS is the anti-lock braking system (ABS), which was first presented at the IAA 1969. Over the past 50 years quite a few more advanced driver-assistance systems have been developed. These include adaptive cruise control (ACC), driver drowsiness detection or intelligent speed adaptation.
The new ADAS data points of Auto API Level 13 include driver alertness, blind spot and collision warnings, and lane departure warning system.
These technologies and systems are outstanding engineering feats in their own rights, with great benefits for drivers and vehicle owners, but putting them onto the cloud elevates them to a whole new level.
For example, being able to provide insurance companies and fleet management systems access to ADAS data, gives them opportunities to improve risk assessments and cost estimates. Ultimately, drivers and fleet operators will benefit from lower costs and contributions.
Other use cases, aimed at driver security or infrastructure planning, are conceivable. The ability to better evaluate driving behaviour might improve road safety for drivers as well as for cyclists and pedestrians. Detailed insights into how cars move on roads could lead to better infrastructure and more efficient mobility in general.
The ADAS data points
Alertness system status - Indicates if the driver alertness warning is active or inactive
Automated parking brake - Automatic brake state
Blind spot warning state - Indicates whether the blind spot warning system is active or not
Blind spot warning system - Indicates whether the blind spot warning system is turned on or not
Blind spot warning system coverage - Blind spot warning system coverage, regular, trailer
Forward collision warning system - Indicates whether the forward collision warning system is active or inactive
Lane keep assist system - Indicates if the lane keep assist system is turned on or not
Lane keep assists states - Lane keeping assist state indicating the vehicle is actively controlling the wheels
Park assists - If the alarm is active and the driver has muted or not park assists
Rear cross warning system - Indicates whether the rear cross warning system is active or not
Status - Indicates whether the driver assistance system is active or not
For more detailed specifications, please go to our documentation.
Charging session
The charging session data points provide information on the charging sessions of electric vehicles. These include information on location, time, duration, the charging states and the costs of charging sessions.
Services and applications built on top of these data points will allow a tighter integration and more efficient utilisation of charging infrastructure and charging and driving activity. The Auto API will be particularly useful when fleet or energy management systems need to access data from vehicles from a number of different manufacturers.
The charging session data points
Business errors
Calculated energy charged - Calculated amount of energy charged during the session
Charging cost - Charging cost information
Displayed start state of charge - Displayed state of charge at start to the driver
Displayed state of charge - Displayed state of charge to the driver
End time - End time of the charging session
Energy charged - Energy charged during the session
Location - Charging location address
Odometer - The vehicle odometer value in a given units
Preconditioning state - Preconditioning is active or not
Public charging points - Matching public charging points
Start time - Start time of the charging session
Time zone - Time zone of the charging session
Total charging duration - Total time charging was active during the session
Charging session at the moment is available for BMW and MINI.
For more detailed specifications, please go to our documentation.
Crash
Crash data is the third group of data points added with the Auto API Level 13 update. In the event of a crash these data interfaces will provide information about the type, severity and impact zones of the crash as well as whether an automatic emergency call was released.
Crash data will especially be interesting for insurance companies, but also for auto repair workshops and emergency and breakdown services.
After an accident or car crash, insurance companies will have to pay for roadside assistance and for emergency and car repair services. Insurance companies will have a decisive advantage, if crash data is transmitted to them in real time. This will give them the time to select the best and most cost-efficient services for each situation.
On the other hand, if car repair workshops, breakdown and emergency services are notified about car crashes or accidents in their area in real time, including vital information about their severity and nature, they will be able to make offers for their services exactly when they are needed.
The crash data points
Automatic eCall - automatic emergency call enabled state
Impact zone - impact zone of the crash: side_passeger_side, side_driver_side, rollover, rear_passenger_side, rear_driver_side, predestrian_protection, front_passenger_side, front_driver_side
Incidents
Severity - severity of the crash (from 0 to 7 - very high severity)
Tipped state - tipped_over, not_tipped
Type - pedestrian, non_pedestrian
For more detailed specifications, please go to our documentation.
Further information
Auto API Level 13 is fully backwards compatible with Level 12. The full change-log can be found on GitHub. To see the full list of data points that are defined in the protocol, please click here.
The car simulators on our platform provide a full test environment for the Auto API. To access a free version of our car simulators please create an account here.
