Web 2.0 and Telco 2.0 Service orientation is about inter-operability and federation across domains.

Domain silos defeat the purpose. User wants one view of him or herself across their devices. Communication endpoints must be networked to be useful

Emerging Web 2.0 patterns are changing some SOA technologies and patterns

Pub/sub, simple eventing and inter-operability is being done thru Ajax based open social standards

Mashup’s - pushing prepackaged UI element with prepackaged logic and flow Users are empowered to dynamically create their environments and flows thru client user

integration patterns Are these new technology patterns positioned to be a strong force for the

general public and enterprise? What does this mean to Telecom? SOA for Telecom ? Are web services going to be used in different ways? REST and Ajax based patterns may be a strong force at the device ?

We need to understand these forces and align to foster universal adoption. identify emerging service patterns in next general models.

Internet Connectivity

Service Control

Applications

Content

Access Networks

Terminal

IP

IMS/SIP

Service Provider

View

WebServices

XMLREST

ServiceBrokers

ApplicationProvider

View

Mash-upsOpen Social

Google

Internet of Things

Ad HocNetworks

RFID, Sensors

BittorrentP2P

Skype

RogueView

Application Stacks Modified @ 2006 UofT

Apps Apps AppsApps

Cloud

Public Internet

Fixed Device (PC, Phone…)

MobileDevice

Fixed-MobileConv.

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)

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 BusinessFunctionality

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

Application

Domain ServiceRegistry

PublishInterface, Binding ..

StandardMeta -Data

Endpoint

DesktopBrowserPhoneMobile

Find

Find Interface, Binding ..

Media

Application

Domain ServiceRegistry

PublishInterface, Binding ..

StandardMeta -Data

Endpoint

DesktopBrowserPhoneMobile

Find

Find Interface, Binding ..

Media

Application

Domain ServiceRegistry

PublishInterface, Binding ..

StandardMeta -Data

Endpoint

DesktopBrowserPhoneMobile

Find

Find Interface, Binding ..

Media

Application

Domain ServiceRegistry

PublishInterface, Binding ..

StandardMeta -Data

Endpoint

DesktopBrowserPhoneMobile

Find

Find Interface, Binding ..

Media

Service Registries

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…

Solution BEFORE, with old-school Internet technologies

Create a servlet project in Eclipse Write a skeletal Ajax UI (using the Eclipse

Web Tools) using Java, JavaScript, HTML/CSS and XML

Use Flickr API to get all pictures and user addresses; store in data structure

Use Yahoo API to create map controls. Add each picture into an overlay using the Ajax API

etc…

Mashups/ Ajax Open Social Pattern

Solution AFTER, with the power of mashup servers (in this case, Yahoo! Pipes)

Draw a flow Use the default interactive

map Enhance!

Problem: Show Flickr pictures on a Yahoo! map

EclipseEclipse

JavaJava

JavaScript

Programmer-centered Approach

User-centered Approach