Date post: | 06-Aug-2015 |
Category: |
Technology |
Upload: | open-mobile-alliance |
View: | 561 times |
Download: | 4 times |
Generic Open Terminal API (GotAPI) & Web-Device API Open Mobile Alliance
The information in this presentation is public. | Copyright © 2015
Ø Framework to access Web based Device APIs with Smartphones (OS-independent, Proven to work on Android and iOS)
Ø Device APIs support Web, native, and hybrid Apps ü With Web-Device API, one will have access (using standard
browsers) to external device data Ø GotAPI Source Code:
ü NTT DOCOMO contributed GotAPI project as “Device Connect”, October 2014
https://github.com/DeviceConnect/DeviceConnect
ü It is already capable of supporting various devices (See the URL for the supported devices)
ü Latest specification link:
GotAPI & Web-Device API Introduction
http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/generic-open-terminal-api-framework-1-0
GotAPI – Device API with Smartphone (Purpose)
CameraSmart Light
Glasses
Internet
Web Apps/URL
Browser
GotAPI
Device APIs Device APIs : Plug-Ins
IEEE 11073 (Data Format Standard)
Ø GotAPI provides a common adaptation layer between the devices and the applications that consolidates all common functions like security, authorization and management policies for all plug-ins
Ø GotAPI passes the end device(s) data to Browser and Web-based Applications. Ø Acts as a bridge between Web APPs
and Device APIs Ø Provides access control to Device APIs
(Devices) Ø Device APIs expose data to web
applications The Device APIs are the mediators between the GotAPI and external devices
Ø Head-Unit takes on the same function as a Smartphone, connecting Device APIs (Plug-ins) through GotAPI to Web applications
Ø Head-Unit will now communicate
with end devices such as: ü tire pressure sensor, brakes,
Oxygen level reader, and OBD
Web Apps/URL
Browser
GotAPI
Extension Plug-In Extension
Plug-In Extension
Plug-In Device APIs
Oxygen level reader
Extension Plug-In
Brakes Tire Pressure
Device APIs:
Internet
On-Board Diagnostics (OBD)
GotAPI-Device APIs with Automotive
Head Unit
Ø Host Device (Smartphone) will act as a companion to the External Device Ø One typical use case is to provide an in-vehicle infotainment (IVI) in a
Head-Unit with functionalities and contents in driver’s Smartphone.
Host Device: Smartphone
(e.g. in driver’s pocket)
External Device: Head Unit/In-Vehicle
Infotainment (IVI)
Request
Response
Web App Remote API
Content Files Driver’s profile
etc.
Navigation Web App with Driver’s Personalization
GotAPI Simplified Flows Interaction between Smartphone and Head-Unit
GotAPI & Device API – Heart Rate Monitor (Example)
1. Heart Rate Monitor (HRM) pairs with its Device API through Bluetooth
2. App/User request to access the HRM is received by the GotAPI Auth Server
3. GotAPI Auth Server authorizes access to the HRM 4. App/User requests the reading of the heart rate from the HRM 5. The heart rate reading is relayed by the Device API through the
GotAPI Server to the App/User
HRM GotAPI Server
Device API/ Plug-In App/User
Bluetooth GotAPI Auth Server
1 4
2
3
5
Ø GotAPI provides a common adaptation layer between the devices and the applications that consolidates all common functions like security, authorization and management policies for all plug-ins
Ø With GotAPI & Device API we can create an open and independent eco-system for any vertical application ü We can incrementally build our Device API portfolio by adding plug-
ins on top of the GotAPI framework Ø Some use cases of GotAPI and Device API include:
ü Linking Internet with In-Vehicle environment for Automotive Telematics
ü Linking healthcare devices with web-based applications/services
Summary
Web technology
Plug-Ins
External devices
• GotAPI Server loosely couples apps and Plug-ins (i.e., external devices)
• Adding new Plug-Ins extends the features and ext. devices
• Plug-Ins can be freely provided by device vendors & 3rd parties any time via app markets
• Apps to access services provided by Plug-Ins using web technologies, e.g., HTTP REST, JSON, etc.
• Standardized APIs and proprietary APIs can be freely implemented in Plug-Ins.
• Enabling apps running in browsers to access external devices consistently across any OS
• Currently no way for web programmers to develop apps for external devices
Help the APP Developer • to deal with fragmented
technologies and lack of open standards
• to manage different vendors and device customization
Flexible architecture
Cross platform technology
Abstract the complexity for App Developers
GotAPI/Device API solution
Smartphone
GotAPI/Device Solution Advantages