Good afternoon, So how cool it can be aggregating services give you the ability to create these compelling scenario we just saw .. And this is just the beginning Let’s look at the Web2.0 or next generation of the web.. The have these clouds that represent the service that are accessible via Web Service interface. You basically have everything, from Map to Search. It is a wide variety of services that an network operator will never deliver. However there are some interesting service in this list: Paypal: one lie payment that has generated between $9B and $10B of financial transaction in 2004 and which is being used by many services these days.. Skype which provide the ability to trigger phone P2P phone calls with potential termination on PSTN. This is interesting since I belive that these represents key assets for a network operator. This list is constantly growing and mashupfeed.com is tracking them and more or less look like Yahoo at the beginning of the web but at this time it is about services…
The interesting piece about Web2.0is the notion of mashups or how to combine services together. As these combination can produce the whole range of new application from funny life2life (secondlife, Amazon E-cpmmerce) to delivering a compelling user experience to powerfull tool www.zillow.com ( An interesting trend around the mashup is the fact that the interesting ones are getting incorporated into As an example Keiden created an interesting mashup of google adword and salesforce.com. This combination allows Salesforce.com customers to manage the entire Google AdWords process from creating ads, placing bids, through to tracking ROI. Keiden was acquired by Salesforce.com and is this mashup is now a feature of the CRM solution. The mashup is graet an pretty significant rate
Light reading conference
Web2.0 and the Service Network Michel Burger
HTML Client Many Services Network User Beginning 2000 Today Web Evolution HTML Client Rendering Transaction Unique component: the user 18 month Many Clients Specialized Renderings HTTP Server
The Network User is a Service Service Context Today Tomorrow User Context User Information Devices include a network representation Web Evolution Non User Devices are connected to the network Sensor (temp, pressure...) Actuator (electric meter, RFID…) … ..
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 Depending on the level of comfort of the user Or as a federation of multiple components Home Gateway SIM,USB.. Access Provider ISP Service Car
Mashups <ul><li>It is all about mashups (combining web based API to create a new services) </li></ul>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 <ul><li>But where are the operator based services </li></ul><ul><ul><li>Network: Call Control, Call Notification, Presence, Location, Messaging </li></ul></ul><ul><ul><li>OSS: Billing, Support, Order Management, Customer Care </li></ul></ul><ul><li>We need a trusted environment for running mashups at the network level: </li></ul><ul><ul><li>Cross device experience </li></ul></ul><ul><ul><li>Network Mashup metering </li></ul></ul><ul><ul><li>Subscription based services </li></ul></ul><ul><ul><li>Mashup QOS </li></ul></ul>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 Network Control Service Control IP Network Service Network Service Delivery Platforms IP Multimedia Subsystem (IMS) BSS OSS
<ul><li>Continuity Service </li></ul>An Example
Applying the physics model that enables understanding of atoms will not explain organic DNA systems A conflict in background and culture 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 Complexity Line of predictable failure Reduce Complexity Integrate few services Miss the service wave Change Culture Hire new people Adopt new business model
Conclusion <ul><li>Bridging the technology gap </li></ul><ul><li>Bridging the business gap </li></ul><ul><li>Bridging the cultural gap </li></ul><ul><li>Bridging the maturity gap </li></ul>We need a bridge between the Web2.0 and the Network Will it come from you?