GSMA 2013

All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA Seminar
Unlocking value in the mobile ecosystem with Network APIs
S
t
r
a
t
e
g
i
c


B
a
c
k
g
r
o
u
n
d

&

O
n
e

A
P
I

P
r
o
g
r
a
m

Network APIs and benets for the ecosystem Marcus Dormanns - GSMA
Exchange Service and Architecture Reinhard Kreft - GSMA PLT
Major characteristics of architecture and APIs in scope David Pollington -GSMA
One API Demonstration Dave Jordan - Apigee
Program setup, status, and on-boarding process Marcus Dormanns - GSMA
D
e
v
e
l
o
p
e
r

I
n
t
e
r
e
s
t

a
n
d

D
e
m
o
s

Developer interest Brief from ADC Manfred Bortenschlager - GSMA
Ubuntu Phone integrated with OneAPIs Identity
and Payment APIs
Stuart Langridge - Canonical / Ubuntu
Identity API / RCS API Introduction of demos Naren Karattup - Deutsche Telekom
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Strategic Background and OneAPI Program
Network APIs and benets for the ecosystem
Dr. Marcus Dormanns
GSM Association
Senior Director Product Management

GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Average time spent on various mobile functions, 1/11
10 minutes (12%)
! Web/Web Apps
27 minutes (32%)
! Phone
! Skype
! Messages
40 minutes (47%)
! Maps
! Games
! Social Networking
! Utilities
! More
7 minutes (9%)
! Mail App
Source: KPCB Top Mobile Internet Trends Report
Mobile operators are not
realising the full value potential
which those new activities offer
New Activity
Customer behaviour on smartphone usage is
evolving towards 3
rd
party services
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
What customers
do with their
phones and
how it evolves
over time
We have to enable
operators to sell core
Telco capabilities:
! to 3
rd
parties
(wholesale benet)
! through 3
rd
party
(Web)Apps to their
customers
(retail benet)
t
Share of service
portfolio
Retail Telco services:
Voice
Messaging


other (Web)Apps
3
rd
party (Web)Apps,
leveraging Telco-like
capabilities
3
rd
party services use capabilities which can also be delivered
by Telcos Network APIs enable Telcos to team-up with
developers to do so
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Telco industry needs to expose homogenous / defragmented
API layer to enable partnerships and 3
rd
party innovation
Content (music, video, games...)
Social Networks
Automotive
Smartphones
A
T
&
T

V
Z
W

V
O
D

C
M

N
T
T

C
U

T
E
F

C
U

A
M

K
D
D
I

n
e
x
t

1
0

n
e
x
t

2
0

n
e
x
t

5
0

o
t
h
e
r

2
1
2

Industry Players
addressing customers
regardless of which
network operator they
have a contract with

Telcos
have reach according to
physical regional footprint
Cross-operator
approach necessary
to facilitate
co-operation of
industries with
different structures
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Use trusted services of
telecommunication provider
in 3rd party applications
Use applications with
richer functionality
Better user experience
of applications
Have more building blocks
for applications to enhance
functionality
Smooth integration of
operator services for
best user experience
Wholesale revenues from
selling capabilities through
applications
Retail revenues from
stimulation of own services
Increase relevance of telco
services in applications
Developers Customers Operators
Benets of Network APIs
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
What is OneAPI Exchange?
Functionality
The GSMA OneAPI exchange platform provides developers with the ability to write applications and services
that can request the use of the network assets of any Operator who joins the GSMA OneAPI programme
Exchange
Exchange Core Service
The essential architecture to enable
that APIs work cross operator, across
the federation
Operator Services
A set of optional services that facilitate
operators to expose APIs and on-board the
GSMA OneAPI programme
Managed Service
The service is provided by GSMA together with technology partner Apigee via a managed service platform
Services include:
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Strategic Background and OneAPI Program
Exchange Service and Architecture
Reinhard Kreft
GSMA Network API
Project Leadership Team
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
The Network APIs challenge
! Mobile operators compete for customers on best voice & data services
and should compete for developers in their developer-facing network APIs
and have to maintain control of their API roadmap and portfolio

! However this makes use of network APIs cumbersome for developers, as
multiple programs to register with
and settle with
each operator can only provide access to their own customer base
1. Reducing development effort, time to market, and ease of settlement
2. Extending the reach of network APIs to other operators customers
3. Whilst supporting network API competition and differentiation
CHALLENGE:
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Solution: Network API Federation
I register with a
developer portal
agree to terms of
chosen operators
use the same API
code for common
functions
and settle across
all from a single
place
I manage
my own
developer portal
and API
roadmap
I still control
who can access
my users
and at the
same time
extend my
API reach
1. I enable an interconnection model for Network APIs
2. I validate requests from developers registered elsewhere in the federation
3. I broker the Ts &Cs documents and API analytics
whilst respecting developer, operator and customer privacy
DEVELOPER
OPERATOR
WEB APIs
Non-operator developer portals can connect too and allow their developers to
mash-up Web APIs with Network APIs without leaving their portal
EXCHANGE
I still can continue to use any differentiated Custom APIs that my portal offers exclusively
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Why a federated model?
! Scalability. The model scales organically with any new Network API
operator coming on board
! Loose coupling: No single point of failure or exclusive platform
! No membership restriction each operator or Web API provider brings
their own portal and connects to the GSMA Exchange. Web API providers
can participate too, driving network API consumption from new channels
! High quality tools and specications via OneAPI specications
! Operators can also expose their own, differentiated Custom APIs
those will either be mediated to OneAPI to support customers of other
operators, or the Exchange will throw a graceful error to the developer
(function not available via this customers operator)
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Its made easy to join the federation
operators need
! A developer portal either your own, via an SDP partner, or as a hosted service from GSMA
! To register your network API endpoints, terms & conditions, and any constraints you wish
to apply, to the Exchange (operators only)
! To update your SDP to query the Exchange to validate incoming requests from developers
registered elsewhere in the federation
! To clear settlements for revenue share and any other payments between yourself and other
federation members (for APIs involving payments only)
The value of network APIs increases with customer reach.
Joining the federation will improve your developer offering, and
generate trafc to your APIs from other developer portals.
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Register Developer &
Application
Agree Ts & Cs:
" Operator 1
" Operator 2
Register
Exchange Architecture
Provisioning
Core Service
Operator Registry
API Request
Validation
Developer
Registry
Discovery
Consent
Mediation
Logs
Developer
Portal
Operator 1
(Developer Operator)
Operator 2
(Serving Operator
Exchange
Platform
Get Ts & Cs
Register APIs,
and Ts & Cs
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Exchange Architecture
Runtime
Core Service
API Request
Validation
Developer
Registry
Discovery
Consent
Mediati
on
Operator
Registry
Logs
API
Request
Exchange
Platform
Which Operator?
Customer of Operator 2 uses App using APIs
exposed by Operator 1
API endpoint + token
API endpoint +
token
Operator 1
(Developer Operator)
Validate token
API Request + token
Operator 2
(Serving Operator
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Call to action for all operators
! Dont wait any longer
! Its here and now
Join the Federation
grow your reach
and Business
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Strategic Background and OneAPI Program
Major Characteristics of Architecture and APIs in Scope
David Pollington
GSM Association
Senior Director Web Technology
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Key architectural principles
! All Operators expose standard OneAPIs to other Operators
! For Developers, Operators can either:
expose these same APIs to Developers within their Developer Program
or expose the same capabilities by their own
differentiated Custom APIs
Those Operators exposing Custom APIs will need to mediate API calls
to the equivalent standard OneAPI to ensure that the API calls can be
served by another Operator
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Operator 1
Developer
Portal
Standard
OneAPIs
App written against
OneAPIs being used by
Customer of Operator 1
Default case:
Operator exposing standard OneAPIs themself
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Operator
backend
systems
Operator Services
Standard
OneAPIs
SACL
Standard OneAPI Connector
Layer (SACL) offered as a
service by the GSMA Exchange
platform
Enables Operator to expose
Standard OneAPIs to Developers
and other Operators
Standard OneAPIs can also be exposed as a managed
service by the GSMA Exchange platform
Exchange Core Service
API Request
Validation
Developer
Registry
Discovery
Consent
Mediation
Logs
Operator
Registry
Exchange
Platform
Operator
SACL
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Operator 1
XOCL
Developer
Portal
Standard
OneAPIs
Custom APIs
Operator 2
Cross-Operator Connector Layer
(XOCL) provides mediation from
Custom to Standard OneAPIs
App written against the Custom
APIs of Operator 1 can now be
used by Customer of Operator 2
Special Case: Operator exposes Custom APIs to their
Developers and mediates to provide interoperability
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Operator Services
Developer
Portal
Standard
OneAPIs
Custom APIs
Mediation of Custom API
can also be provided as a
service by the GSMA
Exchange platform
Exchange Core Service
API Request
Validation
Developer
Registry
Discovery
Consent
Mediation
Logs
Operator
Registry
Exchange
Platform
Operator 2
Operator
XOCL
XOCL
Operator 1
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Recap: Optional Services available from GSMA
! SACL: Exposure of set of standard OneAPIs on behalf of operator by
integration with operators backend systems
! XOCL: Mediation between Custom APIs of an Operator and Standard
OneAPIs provided by every Operator within the federated architecture
! Hosted Developer Portal for operators that do not wish to run
their own portal
! Clearing with Operators and Developers
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Overview on APIs:
Operator
Identity
Anonymous authentication of user to an application by the users Operator
Messaging
Send messages on behalf of the user within applications
Operator
Billing
Bring Operator billing capability to applications (both native and web apps)
Location
Determine location of terminal / user (with user consent)
RCS
Access RCS capabilities via web APIs (chat, le sharing, and live video)
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Strategic Background and OneAPI Program
One API Deminstration
Dave Jordan
Apigee
Chief Marketing Ofcer
29 2012 Aplgee. Condenual - All 8lghLs 8eserved.
GSMA OneAPI Exchange
Exchange Management

30 2012 Aplgee. Condenual - All 8lghLs 8eserved.
Cross-Operator Meta-data management
Manage developer/apps access to
your network
Help operationalize bi-lateral operator agreements
Coordinate transaction data for settlement
and revenue reports
Analytics for developers, apps and APIs
with cross operator context
GSMA OneAPI Exchange Operator Portal
31 2012 Aplgee. Condenual - All 8lghLs 8eserved.
Partner Management
Manage Apps access to your network and subscribers

Business Operations
Manage plans and transaction reports

API Product Team

Optimize the business#
GSMA OneAPI Exchange Operator Portal Roles
32 2012 Aplgee. Condenual - All 8lghLs 8eserved.
View cross-operator developers and apps
Which applications have access to my network
Reputation of applications across operators#
#
Control operator/apps access
to your subscribers
Enable/disable outside network access #Enable/
disable outside developers and applications #
Partner Management
33 2012 Aplgee. Condenual - All 8lghLs 8eserved.
Set and Manage Rate Plans
Set your standard rate plans#
Manage negotiated plans with other networks #
Run Transaction Reports
Trafc from other outside developers on your network#
Trafc from your developers on other networks#
Run Billing Process
Reconcile and post adjustments #
Generate and publish documents #
Business Operations
34 2012 Aplgee. Condenual - All 8lghLs 8eserved.
Understand Cross-operator API Business
Reports by API product, developer operator,
developer, application#
Trafc from other outside developers
on your network#
Trafc from your developers on other networks#
API Product Team
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Strategic Background and OneAPI Program
Program setup, status and on-boarding process
Dr. Marcus Dormanns
GSM Association
Senior Director Product Management, GSMA
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Setup of Program and Operator Involvement
Fast Track Project
Overall solution architecture for
rst set of APIs
Project Interest Group
For interested operators
Inform on scope and progress of project
Now April 2013
User Groups
Operators who are on-boarded or in process to do so
N-API product & platform business-as usual user group
Architecture, implementation, processes, contracts for N-API Exchange
Development and implementation of existing APIs (Operator ID)
Operator and partner on-boarding
Network API marketing user group
Joint communication and marketing activities with involvement of GSMA
OneAPI standardization group
Open to all GSMA members (also non-operators)
Capture + improve input from FT projects and feed to OMA for standardization
Project Interest Group
Same as before, but open to all GSMA members (also non-operators)
After April 2013 (tbc)
N-API product & platform development work streams
Finalising of APIs in development (payment, messaging)
Specication and development of new APIs (e.g. RCS, Location, etc.)
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Network API Fast Track Project Achievements
Workstream Status
Architecture " Architecture for GSMA OneAPI Exchange fully dened
Infrastructure " Infrastructure delivered and ready to on-board
APIs
" Identity, Payment and Messaging APIs dened and
delivered in different stages (POC Beta)
Business
Processes
" Business processes dened in phased approach
subject to implementation
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
On-boarding process high level overview
Joint
Implementation
Working Group
GSMA
Operator
Outreach
Commercial /
Contractual
Technical
Team incl.
Vendor
Product
Denition
GSMA/ Vendor
deliver
optional
services
Decide which optional
Operator Services are
needed
Dene joint
approach on
API exposure
Agree on fee for
exchange and
optional components
Expose and
market APIs
and federation
Scope Integrate Launch Run / Market
Select
APIs
Contracts with GSMA on Exchange
and optional services
Multilateral agreements with
participating operators
Set rate plans for APIs
Sign Contracts with
developers
Operator
expose
standard API
endpoints
Operator to
register with One
API Exchange
Act as SPOC, ensure that whole process works smoothly
N-API
Marketing
User Group
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Developer Interest and Demos
Developer Interest Brief from ADC
Manfred Bortenschlager
GSM Association
Developer Outreach Manager
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Developer Day

Objective: Raise awareness among developers
4h, 6 Partner, 7 presentations
2,445 expressions of interest
250 attendees
Structured outreach, follow-up communication
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Ubuntu Phone integrated with
OneAPIs Identity and Payment APIs
Stuart Langridge
Canonical / Ubuntu
stuart.langridge@canonical.com
www.canonical.com
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Ubuntu Phone and OneAPI
! Identity
Sign in to phone identity system via operator
! Access to operator services
! Seamlessness
! Payment
! Payment on phone bill
! Integrate existing payment systems
! Consumers more closely tied to operator
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Developer Interest and Demos
Identity API / RCS API Introduction of Demos
Naren Karattup
Deutsche Telekom
Head of Cross Industry APIs
Developer Garden
Unlocking Value
in the Mobile Ecosystem
with Network APIs
Naren Karattup, Head of Cross Industry APIs
Developer Garden. The ecosystem for software innovation.
NETWORK APIs: OPERATOR-ID
Reliable user identication
Great, I can re-use my existing
username & password!
Not yet another credential set.
External Log-in`s have improved my
service sign-up/conversion-rate
by more than 20%
My ID is more relevant & valuable as
more services beyond Operator-
branded offerings accept my Login
Login
Login
Login
Register here
Login
Login
Login
Register here
3rd party service
! Easy registration and access to
3rd-party services from mobile
! No need to hand over credentials
to mistrusted 3rd-parties
! Data privacy control
! Tailored User Experience
Customer Benets
! Operator-IDs beta authentication
service will soon be enhanced to
provide a first set of user attributes
! Operator-ID API is part of GSMAs
OneAPI delivery plan
Future Development
Operator-ID within GSMAs OneAPI Programme
! Strategic enabler to compete OTTs
! Sustainable CRM & trust
! Increase relevance and usage of
DTs own identity service and
associated products
Business Benets
Great, I can re-use my existing
username and password!
Not yet another credential set.
Great, I can re-use my existing
username & password!
Not yet another credential set.
External Log-in`s have improved my
service sign-up/conversion-rate
by more than 20%
My ID is more relevant & valuable as
more services beyond Operator-
branded offerings accept my Login
Login
Login
Login
Register here
Login
Login
Login
Register here
3rd party service
External Log-ins have improved
my service sign-up/conversion-rate
by more than 20%
My ID is more relevant & valuable as
more services beyond Operator
branded offerings accept my Login
Limited Beta launch
Anonymous Authentication
(ACR)
First Pilot Partners
Initial reach
Deutsche Telekom & Orange
in France and Germany
Op-ID R0
(February 2013)
Full Beta launch
First profile attributes set
Open to more Pilot Partners
Reach improvement
Further Operators
on-boarding
Full commercial launch
Extended profile attributes set
Unlimited number of partners
Migration to Open ID
Connect (tbc)
Full reach relevance
Full coverage of at list one country
Op-ID R1
(Q2 2013)
Op-ID R2
(Q4 2013)
NETWORK APIs: OPERATOR-ID AND PAYMENT
In app ID and Payment pictures illustrative
Developer Garden. The ecosystem for software innovation.
USE CASES
NETWORK APIs: RCSe API / JOYN ENABLING
Device embedded discovery, chat, le share and video calls
! Foster attractiveness of service entertaining
Joyn users while penetration is low
! Generate direct revenues innovating current
messaging business with Joyn features
! Gain competitive advantage getting traffic
through 3rd parties to increase Joyn
relevance
Business Benets
! For developers, enable access to the RCS-e
capabilities in their apps /services
/ business processes
! For end-users, enhance the service value
through useful applications
Customer Benets
! Joyn Enabling will be enhanced to support
further RCS-e functionalities
! RCS API is part of GSMAs cross-operator N-
API delivery plan
Future Development
Developer Garden. The ecosystem for software innovation.
! This API enables third parties (developers, publishers,
content providers) to gain access to Operators
RCS functionalities
! joyn Enabling extends the core value of joyn and
allows for additional Monetization e.g.
NETWORK APIs: RCSe API / JOYN ENABLING
Solaiemes collaboration: bots for maps, weather until full M2M
! Enter an address of a location
(like you would do on Google
Maps)
! You get back a picture of
the location
! Demonstrators made for:
- weather info
- soccer scores
- stock quotes
- Wikipedia info
- full M2M with
environment sensor input
Usage:
USE CASES
Developer Garden. The ecosystem for software innovation.
Deutsche Telekom is actively involved in the
OneAPI Exchange Initiative. Please join us @ http://
www.gsma.com/oneapi/gsma-oneapi-exchange
! "The OneAPI Programme enables DT's
Developer Garden to expand the reach
of its APIs by providing developers
and partners with access to Operator
network capabilities worldwide,"
saidAvner Mor,Vice President,B2B2x
atDeutsche Telekom.

! DTAG is currently planning to release
several APIs in 2013 that will be fully
integrated to the OneAPI Exchange
platform, amongst which an Identity
API and an In-App Payment API
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
Please get in touch to nd out more!
Marcus Dormanns
Senior Director Product
Management
mdormanns@gsma.com
Mobile: +491707809096
Stefan Weil
Lead Operator Outreach
Manager Europe
sweil@gsma.com
Mobile: +491727411373
Carlos Bosch
Lead Operator Outreach
Manager Americas
cbosch@gsma.com
Mobile: +14046413963
Terence Wong
Lead Operator Outreach
Manager Asia
twong@gsma.com
Mobile: +85290256550
www.gsma.com/oneapi
And contact us directly!
Visit out website at:
GSMA 2013
All GSMA meetings are conducted in full compliance with the GSMAs anti-trust compliance policy
GSMA OneAPI Seminar