Intro to OMA GotAPI
Open-Source Implementation
Supporting Web - Healthcare UseCases

The information in this presentation is public.

Slide #1
[OMA-Template-TPslides-20140101-I]

What is GotAPI?
Generic Open Terminal API Framework• A published specification of the Open Mobile Alliance (OMA)• A design pattern and implementation framework enabling user-

mediated web app access to arbitrary local or connected device APIs

GotAPI Open Source ProjectNTT Docomo’s DeviceConnect (see supported devices)• GotAPI open source project, launched in October 2014
• Various devices supported• Enables device vendors to reduce costs and time to develop
applications interworking with smartphones•

Device WebAPI Consortium• An industry initiative to promote device Web APIs based on OMAGotAPI• Launched in April 2015

Slide #2
[OMA-Template-TPslides-20140101-I]

Overview of GotAPI Design• Device-local web server(“GotAPI Server) acts asbridge to API plugins• Web apps discover GotAPI
support and get approved
access to APIs
• Web apps use standard web
APIs (XHR, SSE,WebSockets, WebRTC) toaccess APIs thru the GotAPI
Server or directly (if supportedby plugin)• Plugins provide access todevice-local APIs/resources orconnected devices, asapplicable for the plugin
Slide #3
[OMA-Template-TPslides-20140101-I]

DeviceConnect Implementation

Slide #4
[OMA-Template-TPslides-20140101-I]

Architecture• A “GotAPI app” implements

servers for API access authand operations• Developers create plugins
that integrate with GotAPI
thru platform-specificmethods• Devices that can beaccessed are only limited
to the types of connections
supported by the GotAPI
host device, and theopenness of connected
device interfaces

Slide #5
[OMA-Template-TPslides-20140101-I]

Basic Flow
• App seeks andgains access toGotAPI-enabledservices• App discovers

available APIs
• App requests
and is allowed
access tospecific API• App accesses

the APIs thru theGotAPI Server ordirectly
Slide #6
[OMA-Template-TPslides-20140101-I]

Specific Example

Slide #7
[OMA-Template-TPslides-20140101-I]

Focus on Security• GotAPI contains specific measures to address• Application registration and authenticity• Application spoofing by rogue apps
• Privacy (user-mediated access to plug-ins and devices)• GotAPI Server spoofing by rogue apps
• Plugin spoofing by rogue plugin• DOS attacks• GotAPI assumes• Host device is not rooted• Apps are obtained from legitimate sources (App Stores, web servers)

Slide #8
[OMA-Template-TPslides-20140101-I]

Fujitsu Implementation demo

Slide #9
[OMA-Template-TPslides-20140101-I]

Fujitsu Implementation demo

Slide #10
[OMA-Template-TPslides-20140101-I]

Next Steps for GotAPI• GotAPI 1.1 is complete specifications for WebSocket based APIs
• Device WebAPI 1.0 is developing specific plugin APIs for• Healthcare devices based upon published and implementedIEEE specs• Thermometer• Pulse Oximeter• Weight Scale and Body Composition Analyzer• Blood Pressure Monitor• Glucometer• Heart Rate Monitor• 3D Printers

Slide #11
[OMA-Template-TPslides-20140101-I]

Links –Draft TS Specification• http://member.openmobilealliance.org/ftp/Public_documents/CD/DWAPI/Permanent_documents/OMA-TS-Weight_Scale_Body_Composition_Analyzer_APIs-V1_0-20151104-D.zip• http://member.openmobilealliance.org/ftp/Public_documents/CD/DWAPI/Permanent_documents/OMA-TS-Thermometer_APIs-V1_0-20151106-D.zip• http://member.openmobilealliance.org/ftp/Public_documents/CD/DWAPI/Permanent_documents/OMA-TS-Pulse_Oximeter_APIs-V1_0-20151106-D.zip• http://member.openmobilealliance.org/ftp/Public_documents/CD/DWAPI/Permanent_documents/OMA-TS-Heart_Rate_Monitor_APIs_-V1_0-20151105-D.zip• http://member.openmobilealliance.org/ftp/Public_documents/CD/DWAPI/Permanent_documents/OMA-TS-Glucometer_APIs-V1_0-20151104-D.zip• http://member.openmobilealliance.org/ftp/Public_documents/CD/DWAPI/Permanent_documents/OMA-TS-Blood_Pressure_Monitor_APIs-V1_0-20151104-D.zip
Slide #12
[OMA-Template-TPslides-20140101-I]