...
5. Automotive Opportunity
5.1 DM
5.
...
2 OMA Device APIs
...
Through OMA enablers focused on device APIs, we can enable automotive (Auto) systems to offer API services to apps running in app environments provided by the Auto system, or running in connected devices. Such API services can enable apps to access vehicle information/services or other connected devices. These OMA enabler APIs are based upon the Generic Open Terminal API (GotAPI) enabler framework described in section 6.2, and the Web Device API (WDAPI) enabler based upon GotAPI. At a high level, GotAPI leverages widely supported Web technologies to enable a GotAPI server host (e.g. the Auto system) to provide an easy-to-integrate framework for apps to register and authenticate, discover available API services, access those API services, and secure the data exchanged between apps and other devices/services accessed through the GotAPI server. Without GotAPI, apps typically would have be designed to support the specific methods through which other devices/services are accessed, e.g. a variety of APIs, protocols, and connection bearers.
5.2.1 Example Use Cases for OMA Device API use in the Auto Environment
OMA device APIs can enable synergy between app use cases in the Auto environment
The goal is to have to user can access and share information with anyone, anywhere. The problem today is Mobile apps, self-contained (lock off their data) from the wider internet. User information is effectively walled off from the rest of the Internet - they keep you in their world.
- Devices web APIs: open the gates to the content from external that enable web developers to interact with a particular platform. Enable third parties apps developer to take data from different sources (e.g. external devices) and leverage its data in new and interesting ways
- GotAPIs/Device APIs is a well-designed framework that expose data to third parties in a consistent way by providing for registration, discovery, access, security, authentication, etc. for apps and ext. devices.
- Without GotAPIs, we would have to implement these methods for each device independently
5.2.1 OMA Enablers: Example of possible work for Automotive
We need to find the synergy between what is happening in Mobile application (e.g. driver safety, etc.), IoT, etc. with the evolving technology in the car environment. OMA device APIs: Web-based application, for example, an application in the car that have access to the car information and external sensors, driver vital signs (including your ) and evolving Auto technologies. For example:
- An Auto system app can monitor driver vital signs (heartbeat, breathing rate, temperature,
...
- blood pressure, etc)
...
- RVI example: A user can download an RVI app providing Mobile Keyless Entry , download app to their smartphone, and use it to unlock the vehicle.
- Such Auto system apps or user smartphone apps can also discover other Also the application can discover external sensors, example, e.g. road sensors, outside air quality sensors, etc.
Overview: Various External Devices Work with GotAPI and Applications
(Web app case)
GotAPI Architecture
5.1.1 Example of RVI and OMA Devices APIs
The RVI will have two roles with respect to GotAPI server. These are: Plug-in and App Client. We think these two roles will support both 3rd party Web Applications in the car that have access to external devices and car data through its internal device APIs. In the second role, RVI as defined will support external devices by interacting with GotAPI server (Device API).
...
Through the two basic roles below, Auto systems (e.g. an RVI) that host a GotAPI-based API server can support a wide variety of use cases for apps running in the Auto system or in connected devices:
- the Auto system can offer vehicle information/services to apps running in an Auto Web runtime environment, or running in connected devices
- the Auto system can offer interfaces (e.g. bluetooth, WiFi, ...) through which apps in GotAPI-enabled devices (e.g. smartphones) can access vehicle information/services
In use Case A, we are leveraging the existing work done in OMA (GotAPI V1.1 and DWAPI*) that is championed by NTT DoCoMo, KDDI, etc.
Use case A
Any 3rd party Web developers can access the RVI data and external device data through GotAPI/Device API. Ex: Auto Driving Lessons Coach.
3rd party App in this use case does not need to implement RVI.
Use Case A
Use Case B
External devices supplying data to RVI. Ex: RVI exposing access to home lighting system.
6. Automotive Industry API definition projects comparison
...
6.2.1 Overview and objective of project...
The Generic Open Terminal API Framework (GotAPI) v1.1 enabler ... (editing in progress)
Overview: Various External Devices Working with Apps Through GotAPI
GotAPI Architecture
6.2.2 API's defined
6.3 LWM2M (AMIT S / PADHU)
...