wims 2.0: converging web 2.0 with the telco world designing rest apis for the exposure of...

WIMS 2.0: Converging Web 2.0 with the Telco worldDesigning REST APIs for the exposure of session-based

IMS capabilities

David Lozano - TELEFÓNICA I+D (Reference Architectures for New Network Platforms)Luis A. Galindo - TELEFÓNICA SPAINLuis García de la Iglesia – HI IBERIADate: 17/09/2008

© 2008 Telefónica Investigación y Desarrollo, S.A. Unipersonal

2TELEFÓNICA I+D


01 Motivations for WIMS 2.0

02 Objectives and convergence strategies in WIMS 2.0

03 Technical principles

- WIMS 2.0 Service Platform

- Open Web APIs

04 Session-based IMS capabilities through REST APIs

05 Conclusions and next steps

Index

3TELEFÓNICA I+D


01

Web 2.0

Recommendation

Affiliation

Audio

Viral Marketing

User decides

The Long TailWeb standards

Perpetual Beta

Data

AJAX

Wikis

Social Software

Blogs

CSS DesignMobility

RSS

Folksonomy

Video

IMS

Open APIs

Share

Simplicity Service

User is the core

Microformats

Economy

Usability

ParticipationRemixability

StandardizationTeleco 2.0

Design

WiMAX

Widgets

Simplicity

VC

SOAP

Syndication

Videocasting

XHTML‘Podcasting’

Granularity

Aggregation

Ruby on Rails

‘Data Inside’

Collaboration

UMTS LTE

IM

‘Page Rank’

Optimization for search engines

Presence

Cost per Click

Modularity

SEO

Trust

XFN

FOAF

Web 2.0Web 2.0

Wikipedia

GMail

CSS Beauty

GMail

eBay

Delicious

LinkedID

Itunes

PayPal

LinkedId

Jabber

Google

Wasp

Writely

Google Maps

Google News

Yahoo Maps

BaseCamp

CastPost

TrendMapper Pandora

Blogger

Live.Com

CreativeCommons

Amazon

Delicious

BitTorrent

Skype

PayPal

Flickr

OpenBC

Technorati

AdSense

Fotolia

TagCloud

YouTube

Mozilla

Dodge Ball

MTurk

Ipodder

A9

Friendster

Upcoming Squidoo

GTalk

RSSReader

OrkutBackpack

Kiko

ZenGarden

StyleGala

SimpleBits

EtsyFlock

Gmaps Mashups

IceRocket

9Rules

Zimbra

Tadalist ProtoPage MyYahooRememberTheMilk

BlinkSale

Zoozio

Netvibes

UnwieldlyMeebo

AlistapartAlexa Chalk.IT

GTDCloudalicious

StumbleUpon

TrendMapper

Rollyo

PubSub

Wink

InOrder

BuzzTracker

FeedBurner

Feedster

NewsGator

Rojo

Plazes

Vimeo

LastFMMeasureMap

WordPress

TypePad

MintPlanzo

Upcoming

SoFLow

Ning

43Things

Digg

TagTagger

Taggling

luis

angel.galin

do@

gm

ail.

com

cc u

nd

er

licen

se c

c 2

.5 e

s o

f att

rib

uti

on

0

4.1

1.0

6Motivations for WIMS 2.0Web 2.0 main concepts

The user is the centre: give users what they want. They create the service content, they customize service features and they even participate in the service development. The user is now regarded

as the main active driver.

Combination and flexibility: the Internet becomes the platform for developing and delivering new cost-effective services. It enables the mixture of service functionalities (mashups) and content (syndication).

The user is the centre: give users what they want. They create the service content, they customize service features and they even participate in the service development. The user is now regarded

as the main active driver.

Combination and flexibility: the Internet becomes the platform for developing and delivering new cost-effective services. It enables the mixture of service functionalities (mashups) and content (syndication).

Web 2.0

mailto:[email protected]

4TELEFÓNICA I+D


Initiatives such as Telco 2.0 point out that there is a need to change the telecom market:

— Differentiating the offer with traditional services is difficult.

— From “take what you are given” to “take what you want”.

— Operators need to reconsider its position and strategic role

An interesting role: service capabilities providers

IMS, and its service enablers, represents the right platform to enable this change in mid-term. Legacy capabilities should be considered as well, especially for the short-term.

01

Motivations for WIMS 2.0 Changing the philosophy of telecom markets

5TELEFÓNICA I+D


Objectives of WIMS 2.0 What do we want and Why?

02

Identify and analyse the mechanisms, within the current service architecture, that enable the new generation of Web 2.0-convergent telecom services

Result: convergence guidelines, technological analysis and definition of the WIMS 2.0

Services Platform

Telefónica follows a two-sided approach:

The Operator offers its services capabilities to the Web 2.0 community. This exposure of capabilities enables the construction of final services by Third Parties.

The operator exploits the Web 2.0 world (concepts, contents, technologies…) to enrich its own services.

6TELEFÓNICA I+D


Convergence strategies in WIMS 2.0A two-sided strategy for convergence

02Following a two-sided approach:

1. Offering IMS capabilities to the Web 2.0 environment:— Incorporation of telco capabilities into Web 2.0 services

– 1.1 Widget-based mashups or PSEs– 1.2 APIs-based mashups

— News ways of publishing content in the Web 2.0– 1.3 User-generated content publishing

2. The operator uses Web 2.0 services and technologies to enrich its own telecom services:

— Inclusion of Web 2.0 content and events into operator’s services– 2.1 Subscription management and Web 2.0 content & events distribution

— Web Interfaces for the provision of IMS services– 2.2 Creating IMS on-line application (virtual terminal)

7TELEFÓNICA I+D


03

Enablers LayerEnablers Layer

Telco/IMS Exposure Layer (APIs)Telco/IMS Exposure Layer (APIs)

Content & Events Distributi

on

Subscription

Management

RSS/Atom APIs

Access control

Web 2.0 domain

Operator’s open APIs 2.0

APIs for publicationtowards Web 2.0 sites APIs for access to content

from Web 2.0 sites

http/AJAX

IMS Thin

Client

async channel

media

ID & Prefs

User-Generate

d Content

Direct interaction(SIP, XCAP, media, other protocols)

Interactionthrough APIs

Direct interaction (SIP, XCAP, others)

Server-to-Server

Client-to-Server

Server-to-Server

Incrusted PSE

Client-to-Server

IMSIMS

PoC PresenceIM XDMCC OthersOTHER TELCOCAPABILITIES

Telco/IMS 2.0 PSEs Platform

Telco/IMS 2.0 PSEs Platform

PSE#NPSE#1

Technical principles A Reference Model for WIMS 2.0 Service Platform

8TELEFÓNICA I+D


In order to maximize the adoption:

— Focus on simplicity and understandability for developers

— Assimilate current Web 2.0 technologies

REST (Representational State Transfer) as alternative to RPC technologies (e.g. Parlay X):

— Simpler and more efficient for tactical integration over the Web (á la Mashup)

— AtomPub as reference protocol and Atom as basis for data representation => easy syndication of information, integration with current feed readers, etc

03

Technical principles Open Web APIs

But….exposing session-based capabilities through REST is NOT

obvious!!!

9TELEFÓNICA I+D


Descriptive approach instead of procedural approach: modeling IMS sessions as web resources with attributes:

— Session state, list of participants, media description, etc

— Changes in attributes (through HTTP standard operations) are translated into appropriate procedures on the IMS side.

— Need for “complete” descriptions, to capture the essential attributes of the session.

The API resources represent the control plane of IMS sessions

User plane only possible for discrete media types, but not for continuous.

04

Session-based IMS capabilities through REST APIs General approach

10TELEFÓNICA I+D


Resources organized in hierarchical levels.

From user’s subscription down to the services activated for each IMPU

Each service, for a given IMPU, is a collection of resources, e.g IMS sessions

04

Session-based IMS capabilities through REST APIs Organization of resources and URIs

This structure is also reflected in URIs

— http://open-telefonica.net/[email protected]/MMTel/SessionID

11TELEFÓNICA I+D


Atom (XML) as base for data representation:

— Atom Feed Documents: collections associated to a service

— Atom Entry Documents: sessions within that service

04

Session-based IMS capabilities through REST APIs Representation of resources (data format)<?xml version="1.0" encoding="utf-8"?>

<feed xmlns="http://www.w3.org/2005/Atom"> <title> IM Feed with multiple messages from user [email protected] </title> <id>urn:uuid:60a76c80-d399-11d9-b93c-000393e0af6</id> <link href="http://open-apis.telefonica.net/messaging/[email protected]"/> <updated>2008-09-11T12:07:41</updated> <entry>First single resource</entry> <entry>Second single resource</entry> <entry>N single resource</entry></feed> For each entry, meta-data representing the session is

included

— within some Atom elements (summary, title, etc)

— within <content>: freedom for defining the data model

Is caching of feeds content possible? Yes, but only if it refers to “call history”, not active calls. Anyway, only one interface with a single data model.

12TELEFÓNICA I+D


Assumption: continuous polling of feeds with active call information, in order to receive incoming events

— Drawback for mobile handsets: polling period is a trade-off decision (battery vs spontaneity)

1st step: creation of new resource by the API client or directly from the network

Next steps: action on resources through HTTP standard methods and semantics

04

Session-based IMS capabilities through REST APIs API Operation

13TELEFÓNICA I+D


04

Session-based IMS capabilities through REST APIs API Operation

14TELEFÓNICA I+D


05

Conclusions and next steps

Need for a change in the Telecom industry: open up!!

Convergence requires an “adaptation layer”: the WIMS 2.0 Service Platform

Consider web-friendly technologies and focus on simplicity:

— REST as alternative to RPC techniques

— Maximize the re-use of open Web standards

Descriptive approach to expose session-based capabilities through REST: only control plane and user plane for discrete media types

Issues that need further study:

— Alternatives to polling: bidirectional APIs, asynchronous channel, etc

— Integrate control plane with the exchange of continuous media types

The design is currently under implementation/validation

wims 2.0: converging web 2.0 with the telco world designing rest apis for the exposure of...

Documents

services platform telefnica

services capabilities

service content

inclusion of web

converging web

service features

service development

new generation of web