Web 2.0 and Telco 2.0 n Service orientation is about inter-operability and federation across domains. l Domain silos defeat the purpose. l User wants one view of him or herself across their devices. l Communication endpoints must be networked to be useful n Emerging Web 2.0 patterns are changing some SOA technologies and patterns l Pub/sub, simple eventing and inter-operability is being done thru Ajax based open social standards l Mashup’s - pushing prepackaged UI element with prepackaged logic and flow n Users are empowered to dynamically create their environments and flows thru client user integration patterns n Are these new technology patterns positioned to be a strong force for the general public and enterprise? l What does this mean to Telecom? SOA for Telecom ? l Are web services going to be used in different ways? l REST and Ajax based patterns may be a strong force at the device ? n We need to understand these forces and align to foster universal adoption. l identify emerging service patterns in next general models.

Internet Connectivity Service Control Applications Content Access Networks Terminal IP IMS/SIP Service Provider View Web Services XML REST Service Brokers Application Provider View Mash-ups Open Social Google Internet of Things Ad Hoc Networks RFID, Sensors Bittorrent P2P Skype Rogue View Application Stacks 2006 UofT Apps Cloud Public Internet Fixed Device (PC, Phone…) Mobile Device Fixed- Mobile Conv. Thin, RIA, FAT Client Consistency and standardization in access models (seamless view & interoperation for user across domains mobile and internet systems Consistency and standardization in sharing/ securing across domain (service integration, SLA’s,pricing, discovery, reporting)

n With a collaborative, social mashup approach, workers can focus on what they do best USE CASE - Collaborative Mashups: Leveraging the Inherent Value of Enterprise Social Networks “Sure, Lin! I’ll add it to the tool palette once it’s done.” “IT, can we get access to Opportunity Actual Revenue?” New Components New Business Functionality Umberto: I need to see opportunity actual revenue! Lin: We all do :) Ray: stop that Lin: I’ll add it to the app. Where should it show up? Sales Mashup Chat Mashup Server Sales Mashup

Backup

Standardize inter-domain relationships, hand- offs… (SLA,s, pricing, accounting, security, monitoring…) Standards on access patterns, discovery, device models and network types Standardize on application and media access paths, interoperability and service models…

n Solution BEFORE, with old- school Internet technologies l Create a servlet project in Eclipse l Write a skeletal Ajax UI (using the Eclipse Web Tools) using Java, JavaScript, HTML/CSS and XML l Use Flickr API to get all pictures and user addresses; store in data structure l Use Yahoo API to create map controls. Add each picture into an overlay using the Ajax API l etc… Mashups/ Ajax Open Social Pattern n Solution AFTER, with the power of mashup servers (in this case, Yahoo! Pipes) l Draw a flow l Use the default interactive map l Enhance! Problem: Show Flickr pictures on a Yahoo! map Eclipse Java JavaScript Programmer-centered Approach User-centered Approach