OMA Overview of the Organization & Work

OPEN MOBILE ALLIANCE OVERVIEW Mobile World Congress 2015, Barcelona, Spain

The information in this presentation is public. | Copyright © 2015

WHY IS A STANDARDS ORGANIZATION HERE?

Ø  Train tracks, keyboards, screwdrivers, stop lights, and mobile phones… What do they all have in common?

Ø  None of these would work without standards.

Ø  If the companies who have an interest in these didn’t contributes to standards… none of these would work.

Ø  Mobile data applications are no different. Ø  To continue to innovate, our industry must

continue to deliver standards at the services layer.

The information in this presentation is public. | Copyright © 2015 Open Mobile Alliance Ltd. All rights reserved.

Standards Matter!


WHAT DOES OMA DO?

Ø  At OMA, members develop specifications for the application layer called Service Enablers, which provide a standardized approach to tasks such as data gathering and transporting information from a network to a device and/or server.

Ø  OMA Enablers are network agnostic, meaning they are designed to be deployable over any type of network.

Ø  OMA Application Programming Interfaces (API) provide standardized interfaces to, fundamental capabilities such as SMS, MMS, Location Services, Presence Services, Payment and other core network assets are now exposed in a standardized way.

Ø  The OMA Developer Toolkit provides test, tools, code and community to facilitate development with OMA Enablers and APIs.

OMA enables technology development from requirements, to standardization to implementation.


WORLD CLASS PARTICIPATION

More than 176 unique specifications addressing global industry needs. Ø  APIs – How can application developers best take advantage of network resources in a

standardized way? Ø  M2M/IoT – How can network operators efficiently manage the billions of devices that will

come online in the coming years? Ø  Public Safety – Can next generation networks enable international standards for

mission critical communications? Ø  Device Management – How can we deliver software updates to automobiles as

efficiently as we do to mobile phones? Ø  Location based services – How do we locate devices indoors as accurately as we can

outdoors?


PROBLEMS OMA IS SOLVING

OMA ENABLERS


Devices Ø  Device Management

•  Device Capability Management Object •  DM Firmware Update Management Object •  DM Gateway Management Object •  Management Object Design Guidelines

Ø  DM Diagnostic Monitoring

M2M Ø  M2M Gateway Ø  M2M Device Classification Ø  Lightweight M2M protocol

OMA ENABLERS


Person-to-Person Ø  SIP/SIMPLE Based IM Service Definition Ø  Converged IP Messaging Ø  Enhanced Visual Voice Mail Service

Location Ø  Secure User Plane Location Services

User Profile Management Ø  Mobile Location Service Ø  Dynamic Navigation Ø  LPP Extensions (LPPe)

OMA APIs – Everyone Benefits

Ø  Network APIs

Ø  Device APIs •  Generic Open Terminal API

(GotAPI)

Ø  Standardized APIs •  Operators benefit •  Developers benefit •  Users benefit


Available to any developer community

independent of the development pla:orm

Expose network assets independent of the signaling protocols, network pla:orms, or access technology

Reduces development cost

and Bme-‐to-‐market for new applicaBons

and services

Simplifies and fuels wider deployment of exisBng applicaBons

and services

Ø  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 Open Source project:

ü  NTT DOCOMO open sourced 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

CameraSmart Light

Glasses

Internet

Web Apps/URL

Browser

GotAPI

Device APIs Device APIs : Plug-Ins

IEEE 11073 (Data Format Standard)

Ø  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) Ø  GotAPI consolidates all common central

functions like security, authorization and management policies for all plug-ins

Ø  Device APIs expose data to web applications based on policies

The Device APIs are the mediators between the GotAPI and external devices

The Challenge …

Standards Development Organizations

DEVELOPERS

Traditional Output

Needs

OMA Developer Toolkit

OMA DEVELOPER TOOLKIT


OMA DEVELOPER TOOLKIT


Ø Web-based specification Ø  Technical summary Ø Developer tools Ø Object Registry Ø Community

Ø Open source projects Ø  Test servers Ø Reference code Ø  Lab Kit and Demos


1.  Be a part of an international community working to solve a common set of technical problems.

2.  Shape the future of what will be standardized. 3.  Exercise your company’s voice in the development of next generation

specifications for mobile data services. 4.  Bring the power of standardized solutions to solve real world implementation

challenges. 5.  Help connect the world of standards development to the world of the

application developers. 6.  Connect with other members of the global mobile ecosystem. 7.  Become a globally recognized technical expert in your field. 8.  Easy to join, easy to participate.

WHY JOIN OMA?

OMA Overview of the Organization & Work

Technology

Transcript of OMA Overview of the Organization & Work