Web2.0 and the Service NetworkMichel Burger

HTMLClient

HTMLClient

Rendering

Transaction

Unique component:the user

18 month

Many Services

Network User

Many Clients

Specialized Renderings

HTTPServer

Beginning 2000 Today

Web Evolution

The Network Useris a Service

Service Context

Today Tomorrow

User Context

User Information Devicesinclude a

network representation

Non User Devicesare connectedto the network

Sensor (temp, pressure...)

Actuator (electric meter, RFID…)

…..

Web Evolution

Where is the User?

In the services as branded user

In the rendering as a web session

In the devices as personal information

Where should the User be?

Close

Medium

Far

HomeGateway

SIM,USB..

AccessProvider

ISP ServiceCar

Depending on the level of comfort of the user

Or as a federation of multiple components

Web2.0 API Cloud

23 30Boxes 411Sync 43Things A9 AIM Alexa Amazon AmazonQueue

AmazonS3 AOLMusicNowBackpack Basecamp BBC Blogger Bloglines

Buzznet CafePressDapper Del.icio.us DigitalPodcast EasyUtileBay Entrez

eSideWalk EVS EVBD Facebook Fedex FeedBurner FeedMap Findory Flickergeocoder geocoderCanada GeoNames Gigablast Google

GoogleAdSense GoogleAdWords GoogleCalendar GoogleDesktop

GoogleHomepage GoogleMaps GoogleTalk GrouperVideo hostip

HotOrNot Interfax InternetArchive Jots JotSpot Kayak LastFM LiveJournal

Map24 MapPoint MapQuest MechanicalTurk Moreover MSNMessengerMSNSearch MusicBrainz Nasa Naver NewsGator NOAA Ontok OntokWikipedia

PayPal Pixagogo Prodigem PubSub RapLeaf RawSugar Rhapsody Riya

Salesforce SecondLife Shadows Shopping.comSimpy Skype Smugmug

SplogSpot Start TagTooga Tailrank TechnoratiTelcontar Textamerica

Topicalizer Trynt TypeKey TypePad UpcomingUPS UrbanDictionary

VirtualEarthWeatherBug Weblogs WebShots WindowsLiveExpo YahooYahooAds YahooAnswers YahooAudio YahooGeocodeYahooImages

YahooMaps YahooRelatedQueryYahooLocalYahooMapImage

YahooShopping YahooTermsYahooTraffic YahooTravel YahooVideo

YouTubeZeeMaps ZoomIn Zvents

PayPalSkype

Mashups

• It is all about mashups (combining web based API to create a new services)

We know we don't have a corner on creativity. There are creative people all around the world, hundreds of millions of

them, and they are going to think of things to do with our basic platform that we didn't think of. So the mashup stuff is a wonderful way of allowing people to find new ways of

applying the basic infrastructures we're propagating.” Vint Cerf

life2life

Secondlife+Amazon E-Commerce

WeatherBug

WeatherBug+VirtualEarth

Zillow

Realestateinfo+VirtualEarth

Managed Network Mashups

• But where are the operator based services– Network: Call Control, Call Notification, Presence, Location,

Messaging

– OSS: Billing, Support, Order Management, Customer Care

• We need a trusted environment for running mashups at the network level:– Cross device experience

– Network Mashup metering

– Subscription based services

– Mashup QOS

Zillow+Location on my mobile phone -> GeoEstate

Amazon ISBN+Barcode+MMS+SMS on my mobile phone -> Instant Price Check

IPTV+Network States-> Continuity

Communications Sector Industry Landscape

NetworkControl

Service Control

IPNetwork

Service Network

Service Delivery Platforms

IP Multimedia Subsystem (IMS)

BSS

BSS

OSS

OSS

Continuity Service

An Example

A conflict in background and culture

Applying the physics model that enables understanding of atoms will not explain organic

DNA systems

Nethead View

Services are in an ordered system of

defined atomic motion

Webhead View

Services are in a loosely coupled organic system in continual adaptation

to an ever changing environment

A Maturity Problem

1 2 3 4 5

Maturity

Com

plex

ity

Line of predictable failure

Reduce ComplexityIntegrate few services Miss the service wave

Change Culture Hire new people Adopt new business model

Conclusion

• Bridging the technology gap• Bridging the business gap• Bridging the cultural gap• Bridging the maturity gap

We need a bridge between the Web2.0 and the Network

Will it come from you?