one api pilot

© GSM Association 2010

1

OneAPI Canadian pilot Workshop, Mobile World Congress

16 February 2010


2

IntroductionGraham Trickey

Senior Director, GSMA

OneAPI Canadian pilot


3

Agenda – OneAPI Canadian pilot workshopm

Introduction

Connecting to the OneAPI Canadian pilot

Transaction flow model

Pilot feedback - panel

Conclusion


4

Overview – GSMA commercial and standards based initiative with the goals of :

• Addressing 3rd Party access challenges across multiple carriers• Establishing a common framework to support additional operators • Creating a viable commercial ecosystem for operator network API’s

Industry Initiative aligns with global trends

• Carrier “openness” to 3rd Parties • RESTful API standards • New Service Model creation

Implementation – GSMA hosts a Web-friendly set of APIs

• Pilots broken in geographic regions - Canada OneAPI Lead Pilot • The API abstracts the 3 Canadian pilot operators • Messaging, location and payment APIs available now

OneAPI Introduction


5

Addressable market • Widened to participating operators • Ubiquitous messaging abstracts handset technology

Service Promotion• Market to target customers via most personalized communication vehicle

– messaging • Mobile marketing campaigns are easily measurable for ROI purposes

Time to Market • One time integration to multiple carriers • Standards based technology approach

Service Offering Flexibility• Rating controlled by developer • Charging (billing event) controlled by developer

Product Enrichment • Can add location context now• Multimedia and two way text future

OneAPI Developer Value proposition


6

Increased Breadth of service offering • Mobile apps and services access available directly from the ISV's• Open Eco system of application and service development

Improved Service Discovery • Service promotion executed by 3rd Party • 3rd party targeted promotions via SMS messaging

Improved Discovery to Sale Conversion • Click to Buy (supported post pilot phase) • Removal of credit cards barrier to service purchase via Bill on Behalf of

API Monetisation• Bill on Behalf revenue share • Wholesale of bulk messaging and location

OneAPI Operator Value proposition


7

The GSMA OneAPI standard

What are the APIs?– A set of lightweight Web-friendly APIs, standardised through the OMA,

delivery Q4 2009– Messaging, location and charging APIs in phase 1

What are the dependencies?– An operator SDP with access to messaging, charging and location

enablersWhat tools will be available?

– Developer SDK: Specifications, tutorials, code wrappers Q1 2010– Operator SDK: Conformance test tool, specifications Q1 2010

What does the operator have to provide?– A OneAPI implementation (hosting of the APIs)– Terms and conditions, Policies/SLAs for access by developers


8

GSMA OneAPI Project participants

Network Operators

Platform Vendors

…plus ongoing requirements and feedback from developers


9

Payment

OneAPI first phase OMA-BASED STANDARD Q1 2010

Messaging

Web server

Send an SMS/MMSUse cases: • on-time Website password• text/photo/video alerts• trigger application on handset*

via OneAPI

Receive an MO SMS/MMSUse cases: • text/ photo/video blogging• client application updating server (games)• Get information based on text (e.g. Wikipedia definition)

Web server

Location

Web server

Get location (for individual or group)Use cases: • cross-operator buddy finder/LB gaming• Mash-ups with mapping, reviews services.

Reserve, Charge, Refund amount to userUse cases: • Seamless mobile billing• Using MNO billing for PC services

Web server

via OneAPI

via OneAPI via OneAPI


10

What’s next?

More APIs- Based on developer requests

More operators– Expanding the OneAPI footprint

Beyond APIs– Addressing other areas of

technical fragmentation:• AAA / accreditation• Policy management

Please get involved!– Feedback on the APIs– Participate in pilots– what else can we do?

www.gsmworld.com/oneapi

Web server

Whose network are you on?

Are you currently GPRS/3G/

HSPA?

Data Connection Profile

Web server

This video needs to be

jitter-free

…and I need to know you

received all of it

QoS


11

OneAPI Canadian pilot

Agreed Objectives1. Demonstrate clear demand for the commercial availability of

OneAPI from developers2. Implement a regional aggregation facility to provide a single

endpoint for developers to utilise OneAPI from any of the pilot operators

3. Ensure that the OneAPI is commercially available from the major operators in a specific geography

Pilot Operators– Bell Mobility, Rogers Communications, TELUS

Pilot Developers…so far- AirG, Mobiry, HomeCamera, Xora, Locatrix, Lifegliders


12

Commercial – Developer charged for network access– Bill on Behalf API available – Commercial Feedback loop

Functional– Location test including Privacy Management – Messaging test including spam control /Opt-in – Billing – Operation & Security – On-boarding & support process

Scale – Open up to 100 developers

Participant Selection Criteria – Cross section of market segments– Cross section of developer business maturity– Ability to execute

Schedule – The Pilot will run from February to July 2010

Pilot scope


13

OneAPI Canadian Pilot

In operation since January 2010

For further information :http://canada.oneapi.gsmworld.com


14

Technical – Demonstrate a cross-carrier platform for billing and network abstraction

Financial

– Demonstrate via business use cases across broad enterprise market segments

Support – Demonstrate effective support processes and business scale capacity is in

place

Commercial – Gather sufficient data points to identify key ecosystem growth barriers

Success criteria


15

Connecting to the Canadian OneAPI Pilot

Mobile World Congress, 2010


16

OneAPI Canadian Pilot Architecture

Payment &Settlement Reporting

3PRM Portal

StoredValue

GSMA & CarrierFinancial

PaymentGateway

TelusTelus

SMS

Number Routing GSMA Pathfinder

Location Billing

Parlay XParlay X

SMS MMS Location Payment

OneAPISMS MMS Location Payment

OneAPI (SOAP & REST)OneAPI (SOAP & REST)

PayPal Web ServiceInterfacePayPal Web ServiceInterface

ReportsReports

NPInterfaceNPInterface

Universal Service PlatformUniversal Service Platform

PartnersPartners

BellBell

SMS Location Billing

Parlay XParlay X

RogersRogers

SMS Location Billing

Parlay XParlay X

TWS Platform


17

Technology & Business Challenges

Subscriber PermissionsPrivacy management API provided to gain subscriber permissions for your application

Subscribers can opt-out at any time

Network RoutingAllowing applications to deliver service to all subscribers without knowing their home network

Platform integrates with GSMA Pathfinder to route transactions appropriately

Commercial SolutionProviding a PayPal option for developers to pay for API usage

Collecting charges from subscribers via the operator bill


18

Developer experience

Register at http://canada.oneapi.gsmworld.com/Open registration process with standard Ts & Cs for all developers

Access to ‘Sandbox’ API services will be granted

Approval process and credit purchase required for access to live services

Further approval required to access operator payment services

Application DevelopmentSimple Web Service APIs exposed via SOAP & REST

Variety of developer support material provided (inc. sample code)

Simple prepaid usage model for APIs


19

Developer experience

Settlement ProcessOneAPI Pilot will settle with developers who use the operator payment services

Standard contracts are in place for all developers during pilot

Support during Pilot OneAPI fourm will be maintained for developer support


20

Thank You!


21

Using the pilotShane Logan, TELUS



22

“There is a need for OneAPI”

Today's challenges . . .

Carriers; faster access to cheaper innovation

Subscribers; access to more affordable niche apps

Developers; cheaper/faster access to a larger base


23

The Ecosystem . . .

Rogers

TELUS

BELL

CanadianOneAPI

One API to rule them all, One API to find them, One API to bring them all, and in darkness bind them.

GSMA

PayPal

Neustar

AePona

D ev e l

op e r

s


24

Business Stream

Developer StreamGSMA

Technical Stream

Abstraction is not easyWhat API’s to exposeLowest common denominator

Lessons learned to date . . .

Common Terms & ConditionsIndividual GSMA Contracts

No human interaction

Too much interest !

Who supports troubleshooting

Education is required


25

High Level Flow . . .

AePonaAePona NeustarNeustar

TELUS TELUS RogersRogers BellBell …… ……

PayPalPayPal

22 millions subs

Partner registers with GSMAAccess to SDK, Docs, SandboxPurchase credits for SMS/LBSRequest Access to BOBORequest Production AccessSettle with GSMA on BOBO

GS

MA

Request for consent

Carriers delivers service

SMS/LBS Settlement

Rev share on BOBO

Dev

elop

ers


26

Developer Feedback . . .

One of the strong appeals of OneAPI for us is to have one access point for mobile phones, each exception, creates more work.

In doing this I found the platform easy to use and documentation to be good and clear.

When will the payment API be available?

Any news on any other carriers (Canadian, US) joining the Canadian Pilot?


27

Developer Feedback . . .

Looking forward for MO messages – I understand that it is not a part of the pilot launch?

The promise of OneAPI is great, the details will determine its success.

One key factor in our evaluation of OneAPI is the cost for using OneAPI services, like SMS.

Developer experience of on-boarding and registration was relatively straight forward, no issues there.


28

Next steps . . .

Evaluate and share the feedback and KPI’s . . .

Encourage more developers to onboard . . .

Support the Canadian pilot that is now commercial . . .

Visit: “http://canada.oneapi.gsmworld.com/”

A rising tide lifts all boat !

Encourage the European OneAPI . . .


29

Panel DiscussionLarry Baziw, RogersJames Gazzola, Bell

Alexey Mykhaylov, Mobiry



30

Conclusion



31

App Garage stand 7APG App Planet

• OneAPI App demonstrations by :Aepona, Locatrix, LifeGliders,Livecast, Ericsson, Mobiry, Airweb

• Presentations on OneAPI apps and OneAPI Canadian pilot

• Meet project team members

Useful links:OneAPI Portal : www.gsmworld.com/oneapiCanadian pilot portal: http://canada.oneapi.gsmworld.com

one api pilot

Technology

soap amp

developer

api

apis

oneapi

access

location

feedback