oma strategy on open api standardization

Next Generation Mobile Technology & Standardization Conference OMA Strategy on Open API Standardization

17 November 2010 Seoul, Republic of Korea

Musa Unmehopa OMA Technical Plenary Chairman Distinguished Member of Technical Staff at Alcatel-Lucent

www.openmobilealliance.org

OMA is where Telecom APIs get standardized

The Telecom API landscape appears complex, but is harmonized

OMA plays a lead role in the harmonization and consolidation

OMA has the resources and the expertise

OMA technical specifications provide the practical implementation of the commercial goals and go-to-market strategies of industry partners

2 OMA Strategies on Open API Standardization , 17 November 2010

Use Application Programming Interfaces (APIs) to open up

service capabilities and assets in the core network to

application developers

The APIs provide an abstracted view of these capabilities

Application developers do not require comprehensive knowledge of arcane telecommunication signaling protocols and call state models

Applications built towards the API can be ported across network types and access technologies


Core network service capabilities

Location Identity Payment Presence Network Control

Exposure layer

Developer Program

Content Provider

Systems Integrator

APIs

Native network signaling protocols

Service Provider

Advertiser

Abstract APIs

Focus on functional aspects

Protocol independent

API Binding Technologies

SOAP/WSDL web services

HTTP protocol binding using REST architectural style

Network APIs & Device APIs

Network API – exposed by a resource residing in the Network

Device API – exposed by a resource residing/running on a Device


OMA has released several APIs

Parlay Service Access (PSA) – completes 3GPP Release 8

Profile of Parlay X Web Services – GSMA OneAPI profile for SOAP

ParlayREST v1.0 – GSMA OneAPI profile for REST

Next Generation Service Interfaces (NGSI) – Parlay X extensions

Service User Profile – API bindings for SOAP, REST and LDAP

API work under development in OMA

ParlayREST v2.0 – GSMA OneAPI profile for REST

NGSI-S – SOAP/WSDL bindings for NGSI

RESTful binding for OMA Push Access Protocol (PushREST)   All targeted for completion in December 2010

  Device Management Client Side API Framework   Targeted for completion in Summer of 2011


OMA is (considering) starting up new work on APIs

APIs for Mobile Augmented Reality

APIs for Mobile Advertizing

APIs for Mobile Social Networking

APIs for Games Services

APIs for Web Runtime environment

APIs for GSMA Rich Communications Suite (RCS)


Consistency in design and documentation

Improves marketing message

Facilitates developer uptake

Use of Best Practices

Industry Best Practices

OMA REST Guidelines

Promote re-use and avoid duplication

Common namespace, common data types, common design patterns

No competing APIs for the same function/use-case

Common authorization framework using OAuth for REST APIs work area currently being considered as part of new RCS API work item


Industry Best Practices

How industry best practices apply to REST API development in OMA

REST design patterns

Guidelines developed by OMA

Content-type negotiation (XML, JSON, form-urlencoding)

API versioning

API documentation

Error handling

Serialization and internationalization

Backwards and forwards compatibility, extensibility

Encoding and Serialization Details for MIME format

Looking to extend these to include Device API guidelines as well



Parlay Service Access

OMA: Has adopted the API work from 3GPP/ETSI Has affiliated the API activities from Parlay

ParlayREST v1.0 ParlayREST v2.0

PXPROF v1.0

GSMA: Developer outreach Go-to-market Business models

OMA: Technical Specifications Standards publication (draft) RCS API

work item

GSMA: Requirements

OMA: Technical Specifications

Standards publication

Referencing OMA API specifications


Referencing OMA Network APIs


Focus on •   commercial/regulatory aspects •   developer outreach •   payments reconciliation •   commercial strategies •   business models

Especially the latter three cannot be discussed in standards for a, for reasons of Antitrust and neutrality.

Focus on •   technical innovation •   specification development •   correctness and validation •   standards publication

ParlayREST v1.0 Enabler Release Package

•  OMA ParlayREST Technical Specification •  OMA ParlayREST WSDL SUP files

•   SMS •   MMS •   Payment •   Location

•  OMA Test Requirements •  OMA Conformance Requirements •  OMA REST Best Practices

GSMA OneAPI •  Developer guides •  Reference implementation •  WiKi •  Commercial trial/pilot

OMA TS ParlayREST OneAPI Profile OMA TS OneAPI Profile

OMA is where Telecom APIs get standardized

The Telecom API landscape appears complex, but is harmonized

OMA plays a lead role in the harmonization and consolidation

OMA has the resources and the expertise

OMA technical specifications provide the practical implementation of the commercial goals and go-to-market strategies of industry partners


Musa Unmehopa OMA Technical Plenary Chairman [email protected]


oma strategy on open api standardization

Technology

apis apis

api framework

api activities

open api standardization17

network device api

rest api development

device api guidelines

harmonized oma