This is a draft of the report being created by the OMAuto Incubator Group at OMA. Feel free to edit this report if you have something of value to contribute.

If you want to add or edit an image on this page, download the file OMAuto Incubator Report Diagrams.pptx PowerPoint deck and follow the instructions. If you don't have PowerPoint, follow these instructions:

• Images in source format other than Microsoft Office Graphic (Powerpoint) should be edited by other tools and uploaded to the wiki in the source format, for future updates. Once finished editing, save the image as a PNG with filename per the caption of the image in the report.
• Edit the wiki page, and use the “Files” tool to upload the image. If you are updating an image with the same name, you don’t need to re-insert it, so deselect the checkbox on the image and select close.

Table of Contents

1.     Scope

1.1          OMAuto Goal

• Establish a venue for discussion between telecom and automotive at a technical and industry level to establish any network, any automobile connectivity.
• Adapt select current specifications to optimize for the needs of the Automotive market.
• Create a path for Auto industry to interface with the rest of IoT via standardized enablers.
• Bridge existing standards with standardization efforts in the Automotive sector.

Enable a path for automakers and operators to encourage communications interoperability across automotive and wireless industries.

1.2          Deliverables

Medium = technical report with a set of agreed recommendations to drive future standardization work (25-50 pages)

• Get agreement across participating parties as to what work needs to be done and where (which SDO) it needs to be done.
• Examine landscape across mobile and automotive environment
• Identify areas of overlap across industry work groups (RVI, W3C, GSMA, 3GPP, OMA, Smart Device Link, Apple CarPlay and Android Auto, OCF, etc…)
• Produce use cases/examples including interaction between IoT and automobile
• Roadmap and proposed timeline of future work needed, for example
  • Security-related issues
  • Enabler creation or reuse to facilitate development of enhanced services
  • Work with additional verticals (environmental, safety, healthcare)
• Deliverables publication to be public and available online
• Reference code-based projects already underway
• Clarify what should be standardized, open source vs. proprietary to encourage interoperability
• Other TBD

2.     References 

3.     Terminology and Conventions

3.1          Conventions

This is an informative document, which is not intended to provide testable requirements to implementations.

3.2          Definitions 

3.3     Abbreviations

4.     Introduction

4.1          Observed Problem

• Problem statement 1
  • There are a series of initiatives in the automotive industry that will touch the mobile environment
  • There is work going on in the mobile/IoT industry that will need to interoperate with automobiles
    • It is important for all not to waste resources by “reinventing the wheel”
    • Use good protocols that already exist and are deployed
  • There are a number of one-to-one company level programs underway, there is NOT a conversation happening at the industry-to-industry level to insure standards-based interoperability and reduce fragmentation of protocols across automotive interacting with IoT and mobile services
  • The overall needs of the automotive industry are not being translated into mobile/IoT industry developments – harmonization of requirements and solutions between the mobile and the automobile environments.  What are the problems the automotive industry are trying to solve?
• Problem statement 2
  • The auto industry wants to ensure openness and mobile device interoperability in relation to the automotive telematics systems
  • Automakers run the risk of becoming a “dumb device” with no control over user data
  • Operators and automakers could be forced to the sidelines where consumer touch, data collection and ownership are no longer future revenue sources
  • Existing automotive approach of proprietary implementations is no longer working
• SDL - Smart Device Link, an open source implementation of Ford’s AppLink (Ford Sync) software libraries enabling smartphone integration across all radio levels and brands of devices (Apple, Android, Windows, etc.)
• RVI - Remote Vehicle Interaction, an open source project by JLR Research Centre in Portland, OR. Enables universal connectivity to the vehicle bus transparently across LTE, Wi-Fi, Bluetooth, 3G, NFC and future networking technologies by embedding a standard software module in the vehicle head unit.
• SOTA - Software Over The Air (included in RVI above) through the entire vehicle (ASIL grade Safety and Security)

4.2          Hot Projects in Open Automotive

• SDL - Smart Device Link, an open source implementation of Ford’s AppLink (Ford Sync) software libraries enabling smartphone integration across all radio levels and brands of devices (Apple, Android, Windows, etc.)
• RVI - Remote Vehicle Interaction, an open source project by JLR Research Centre in Portland, OR. Enables universal connectivity to the vehicle bus transparently across LTE, Wi-Fi, Bluetooth, 3G, NFC and future networking technologies by embedding a standard software module in the vehicle head unit.
• SOTA - Software Over The Air (included in RVI above) through the entire vehicle (ASIL grade Safety and Security)

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 (e.g. driver safety, IoT, etc) and evolving Auto technologies. For example:

• An Auto system app can monitor driver vital signs (heartbeat, breathing rate, temperature, blood pressure, etc)
• A user can download an RVI app providing Mobile Keyless Entry to their smartphone, and use it to unlock the vehicle
• Such Auto system apps or user smartphone apps can also discover other external sensors, e.g. road sensors, outside air quality sensors, etc

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 3^rd party Web developers can access the RVI data and external device data through GotAPI/Device API. Ex: Auto Driving Lessons Coach.

3^rd 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.1 W3C Automotive Web API (PAUL B / TED)

6.1.1 Overview and objective of project...

6.1.2 API's defined

6.2 OMA GotAPI (BRYAN S)

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)

6.3.1 Overview and objective of project...

6.3.2 API's defined

6.4 OneM2M (ELIZABETH to identify lead)

6.4.1 Overview and objective of project...

6.4.2 API's defined

6.5 GENIVI Remote Vehicle Interaction (RUDI S to collaborate with Magnus/Magnus)

6.5.1 Overview and objective of project...

6.5.2 API's defined

6.6 OCF IoTivity (SANJEEV)

6.6.1 Overview and objective of project...

6.6.2 API's defined

Please focus on overall expected penetration of OSS work in IoT market

6.7 OMA-DM and vehicle security (YAIR N)

6.7.1 Overview and objective of project...

6.7.2 API's defined

7. Analysis and recommendations to achieve interoperability (JOEL H)