IMS Convergent Multimedia Services


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • ITU-T definition: NGN is a packet based network able to provide services (incl. telecom. Services) and able to make use of multiple broadband, QoS-enabled transport technologies and in which service-related functions are independent from underlaying transport-related technologies. It offers unrestricted access by users to different service providers and generalized mobility. NGN can be defined by following main features: - Consolidation of transport networks into one core transport network (often based on IP and Ethernet) => migration from PSTN to VoIP and from legacy services such as X.25, Frame Relay to IP VPN In wired access NGN implies the migration from legacy voice + xDSL in the Local Exchanges to a converged setup in which DSLAMs integrate voice ports or VoIP allowing to remove the voice switching infrastructure from the exchange. In cable access, NGN convergence implies migration of constant bit rate voice to CableLabs PacketCable standards that provide VoIP and SIP services over DOCSIS. NGN are based on IP and MPLS (Multiprotocol Label Switching) and at application level on SIP which took over the ITU-T H.323. H.323 originally popular in the “local loop” decreased in popularity due to its poor traversal of NAT and firewalls. More recently H.323 has been improved in this sense but as SIP has been selected as signaling protocol for IMS, it is not sure H.323 would come back again as an option. The NGN use Softswitches to control VoIP calls. A softswitch creates an interface to existing PSTN through SG (Signalling Gateways) and MG (Media Gateways) HSPA = HSDPA, HSUPA, HSPA+ (Evolved), HSOPA or OFDMA MBWA (Mobile Broadband Wireless Access) = 802.20 WiMAX = 802.16-2004(d)/-2005(e); Fixed WiMAX = 802.16-2004(d); Mobile WiMAX = 802.16e WiFi = 802.11a/g
  • Fixed applications Person-to-Content: Games, Internet, News, Corporate access Person-to-Person: Games, E-mails, Voice calls, Video calls The NGN architecture provides the foundation for the integration of Person-to-Content and Person-to-Person communication paradigms. Thus, irrespective of the fact that the end point is a user controlled device or an AS hosting content, same packet-based access and transport network, control plane and service layer are used. The asynchronous delivery of content to an user is similar to requesting a person-to-person session for that user. The session setup, control, content sharing management, instantiation of other interactive services while accessing the content can/need to be handled in a unified way. Besides the efficient network implementation, the real-time aspect matters also to very large extent. The NGN architecture and implicitly IMS provide a framework for both Person-to-Person and Person-to-Content application. Same infrastructure is used to deploy new innovative services at a fast pace. Community services can be much faster developed and deployed.
  • IMS is a standard-based way of creating a Next Generation Network. IMS specifications also define ways of creating and delivering applications on that network, together with managing related functions like QoS and charging. Why operators are interested in IMS: Bottom-up reason: operators decided to move towards NGN and IP and IMS is an “off the shelf” and well-defined way of achieving this. This reason weighs over the second one as low-level infrastructure stories have much easier ROI in terms of opex/capex than predicting future growth of services. Top down reason: application-centric view where IMS is a solution to the improvement of flexibility, costs and deployment speed of providing services to subscribers. IMS follows the success story of the Internet and enterprise IT which have shown the benefits of having shared functions in the network and shared capabilities on the device. Also the “open” and “platform-based” nature of the Internet means that a vast array of developers can write applications. IMS attractions go beyond unifying different “downloadables” into one architecture as they provide real-time/interactive features and of course is based on IP. IMS is based on SIP and it seems that both have gained a lot from this “joint-venture” The opinion is that SIP may not have gained so much popularity and credibility should have been not adopted by IMS. Opinions on IMS: IMS is complex and there will be various “shades of grey” ranging from best-effort Internet architecture, through the more pragmatic IMS-like-NGN-embracing approach. There will be some decent “top-down” applications that will share various common functions IMS provides support for emergency services, lawful intercept and priority services The problems start when one considers GSMA solution with purely operator-controlled IMS domain. Internet model is on the other hand best effort, completely open to any appl. provider plus the promise the users or advertisers will pay for “premium, even better stuff”
  • Phase 1: The P- removes any potential route and replaces it with a route to S-CSCF. This route is defined during IMS registration and may traverse an I-CSCF (topology hiding) Phase 2: The S-CSCF applies the service profile for originating IMPU. This profile consists of a set of IFCs which give a list of services to apply by originating network. It is possible that one of invoked AS’ terminates the SIP request (SIP UA). This happens when the request was addressed to a PSI, or when the request was sent to itself (ex. PUBLISH for presence event package is addressed to user’s own IMPU) Phase 3: Routing to terminating network according to the RequestURI. In case the Request-URI is a TelURI, the S-CSCF will route to PSTN if the TEL URI is not resolved to a SIP URI by the DNS ENUM. Through the DNS, the S- also determines if the request is for a non-IMS network (Internet) Phase 4: Routing the request to S-CSCF in terminating network. It is necessary to reach B S-CSCF as some of B party’s services may have to be invoked when B is not available (e.g. presence) Phase 5: The terminating S-CSCF applies terminating side service profile associated with the IMPU or PSI corresponding to the Request URI. Phase 6: Delivery to terminating party Note: IMS routes based on UserIDs and ServiceIDs whereas SOA routes based on ServiceIDs only.
  • RDF is a framework for the creation of statements (triplets) which enables to represent information about the resources as a graph => Semantic Web is know as the “Giant Global Graph” RDFS provides a basic vocabulary for RDF. It allows the definition of hierarchies of classes and properties RIF and SWRL brings support of rules. It adds semantic description to relations which could not be described in OWL. OWL extends RDFS by adding more advanced constructs to describe semantics of RDF statements. It allows stating additional constrains (cardinality, restrictions of values, properties such as transitivity). It brings reasoning power to the semantic web. SPARQL is a RDF query language
  • Message Oriented Middleware (MOM) is a client/server architecture which isolates the application developer from underlying OS details by making use of APIs which extend across multiple platforms and networks. Java Message Service (JMS) is an API implemented by most MOM vendors. SOC inherently promotes SOA, though it is not the same as SOA. Due to language and platform independent Web Service standards, SOC/SOP embraces all existing programming paradigms, languages and platforms. In SOP, the design of the programs pivots around the semantics of service calls, logical routing and data flow description across well-defined service interfaces. A service can be an externalized component from another system accessed either through using Web Service standards or any proprietary API through an in-memory plug-in mechanism. Composite Service A composite service implementation in SOC is the semantic definition of a service module based on SOP techniques and concepts. A Composite service may have a recursive definition meaning that any service inside (“inner service”) may be another atomic or composite service. An inner service may be a recursive reference to the same containing composite service. Atomic Service An Atomic service is an in-memory extension of the SOP runtime environment through a Service Native Interface (SNI). Service Discovery Web 1.0/2.0, generation of Web services is manual in the sense that a registry (UDDI) is searched by developers of client systems, rather than middle agents / user during execution. In contrast, semantic matchmakers use semantic relations to find services described using Semantic Web languages (OWL, WSML, WSMO)
  • Web 2.0 is a term that describes a trend in World Wide Web that fosters creativity, information sharing and most notably collaboration among the users . Main Web 2.0 services are web-based communities and hosted services such as: social-networking sites, wikis, blogs, folksonomies . Although it suggests a new version of the Web, it does not refer to an update to any technical specifications. It is rather a move towards the Internet as a distributed platform. Web 2.0 can also be characterized as a transition from isolated information silos to interlinked computing platforms as data is aggregated from various servers in the network. Web 2.0 also addresses the social element where users can generate and distribute content. Architecture components: Server software, Content syndication, Messaging protocols, Standards-oriented browsers with plugins and extensions, and Client applications. Web 2.0 site features: CSS, Folksonomies (social tagging, indexing), Semantic microformats (sometimes), REST and/or XML and/or JSON based APIs, Rich Internet Application typically based on AJAX, XHTML/HTML semantically valid, Syndication/aggregation/notification of data with RSS or Atom feeds, Mashups merging content from various sources, Weblog for publishing sites, Wiki or Forum for user-generated content, Internet privacy to allow user manage their own privacy Web 2.0 Criticism Web 2.0 is not something new. Protocols like AJAX do not replace HTTP, but add an abstraction layer on top of it. Many of the ideas claimed in Web 2.0 have already been featured in networked systems implementations well before 2.0 emerged (ex. Amazon allowed a form of self-publishing since 1995). Tim Berners-Lee, the father of the Semantic Web and founder of W3C, characterized Web 2.0 as: “if Web 2.0 for you is blogs and wikis, then that is people to people (communication). But that was what the Web was supposed to be all along” . Other criticism has included the term “a second bubble” in reference to Dot-com bubble 1995-2001. The analogy is based on the fact that too many companies attempt to develop the same product with lack of proven business model. In the end, the winners will be only those who own data mashed-up in successful applications. Software development will not pay back.
  • Representational State Transfer (REST) = Collection of Network Architecture Principles which outline how resources are defined and addressed. Good response times due to use of caching. Defines: uniquely addressable resources, an uniform interface, a client-server protocol stateless, cacheable and layered. Rich Internet Applications (RIA) = Applications that execute on the client, typically in the Web Browser (i.e. do not rely on server runtime code). They are more user friendly than HTML widgets and exhibit a desktop environment look and feel. The client engine can interact with the server without waiting for the user’s command, so data can be pre-fetched. RIAs run in a sandbox (security mechanism for safely running programs) therefore they do not have access to all platform resources. Asynchronous JavaScript and XML (AJAX) = Cross-platform technique based on JavaScript and Document Object Model (DOM). It uses XMLHttpRequest object to request data without a re-load (the application behaves more like a tightly coupled. Pages are dynamically generated, therefore browser back function may not work as expected unless techniques like IFrame (InvisibleFrame) are used. AJAX and RIA replace DOM (Document Object Model) web page manipulation model with Widget model (Dojo). Really Simple Syndication (for RSS 2.0) = Web feed format used to publish frequently updated content (blog entries, news, podcasts). Widget = Element of a GUI that displays information arrangement changeable by the user. Examples of Widgets are: slider, check box, drop-down list, menu bar, tool bar, text box etc. Gadget = Interactive mini-applications that can be placed anywhere on Google Desktop. OpenSocial = Set of APIs for the development of Web-based social network applications developed by Google (response to Facebook platform). Uses HTML, JavaScript and Google Gadgets to allow interoperability with any social network system that supports OpenSocial APIs.
  • Web Service Choreography (WSCI) = W3C specification defining a XML business process modeling language which describes the interaction protocols between Web Service participants that. Services act as peers and interactions may be long-lived and stateful. WS-BPEL (Web Services Business Process Execution Language) or simply BPEL = Language for describing business process behavior based on Web Services. BPEL is an Orchestration language, not a Choreography Language. BPEL is based on messages and provides structured-programming constructs and encapsulation of logic with variables, handlers etc. All BPEL implementations must support XPath 1.0 (language for the selection of nodes from a XML document) as default language. Note : Apple iPhone has 620 Mhz CPU and 128 MB RAM.
  • Neurocommons = RDF DB developed by Science Commons compiled from major life sciences databases with focus on neurology. It is accessible with SPARQL query language. OWL-S = An ontology built using Ontology Web Language (OWL) for the Semantic Web. It has three parts: Service profile = describes what the service does (this info is primarily for human reading) Process model = describes how to interact with the service (i.e. inputs, outputs, pre-conditions etc.) Service Grounding = details on interaction (communication protocols, message formats, ports) SWSF = Semantic Web Services Framework contains an ontology (SWSO) and a language (SWSL). The SWSO is an extension of OWL-S. SWSF does not clearly define how the elements of the framework work together. SWSF contains language description for both static and dynamic behavior. IRS-III = Internet Reasoning Service is a broker handling mediation between clients and deployed services. Does not define an actual FW. Instead it reuses WSMO. It consists of an IRS Server, IRS Publisher and IRS Client. WSMO = Web Service Modeling Ontology is formalized using Web Service Modeling Language (WDML). It is based on: Capabilities - what the service can do, preconditions/postconditions; Interfaces - how to access the service, choreography/orchestration; Goals ; Mediation – data, protocol, process mediation. WSML allows description of both the static and dynamic behavior. Services described in WSMO execute in WSMX environment. WSMX can be seen as reference implementation of WSMO and a SOA using dynamic binding. The Semantic Web allows automatic : Service Discovery Service Execution = i f executing the service is a multi-step procedure, the software needs to know how to interact with the service to complete the necessary sequence. A Semantic Web service provides a descriptive list of what an agent needs to be able to do to execute and fulfill the service. Service Composition = how to select and combine a number of Web services to complete a certain objective. Service Monitoring = Agents need to be able to verify and monitor the service properties during run-time.
  • Communication Handler = Protocol handler and parser which terminates all communication session from external nodes. Service Mediation = Handles data, protocol and business process mediation (adaptation to a specific format/syntax) using pre-defined mappings. Data refers to ontologies, while processes refer to rules. Mediation can be used in various execution stages: discovery, composition, invocation. Semantic/Ontology Reasoning = The reasoning engine (ex. IRIS, KAON2, MINS, PELLET) evaluates queries over a knowledge database. For each query, the engine returns the variable bindings (set of all tuples that can be found or inferred from the knowledge database that satisfy the query) Web Service Discovery = Finds the services which fulfill the formulated goal. Ranks services discovered based on a given criteria (ex. QoS) and interacts with the Matchmaker (Broker) to select one of them. Composition Engine = Selects the composition paradigm, i.e. Orchestration or Choreography. Choreography is a stateful, public process. It selects the service to invoke by analyzing state transitions and requester’s goal in relation to service provider’s description. Service instantiation steps : Late binding: WS Discovery: a WS which can satisfy the goal is found in the WS repository Service Selection: discovered services are ranked based on criteria like QoS Execution: Mediation: handles data/protocol/process adaptations between requester and provider. Process mediation refers to actually performing the composition (orchestration or choreography) Service invocation and grounding: data is transformed from ontology format to the XML message format.
  • Xplan Composition Preliminary processing = preparing input data, creation of type-hierarchies, filtering relevant operator instances. Connectivity graph = generation of a dependency graph Goal determination = setting-up of a (reachable) goal Planning Graph Generation = Upper modules are part of the re-planning sub-system. This engine generates the relaxed planning graph where operators have no delete lists and extracts relevant operators. Enforced Hill Climbing Engine = Is a Hill-Climbing procedure (which is a of Fast Forward Chaining heuristics) that, in each intermediate state, uses breadth first search to find a strictly better, possibly indirect, successor. Relaxed plans can be used to prune (clean-up) the search space. The main drawback of EHC is that the search heuristics sometimes can not escape from a plateau in one step therefore exhaustive search periods is then required bridged by relatively quick periods of heuristic descent. PDDXML = Planning Domain Definition XML
  • IMS Convergent Multimedia Services

    1. 1. Advanced Paradigms for Building Convergent Next Generation Services. Service Composition and Service Brokerage in Multimedia Architectures Dr. Sorin Georgescu [email_address]
    2. 2. Agenda <ul><li>NG Service Platform </li></ul><ul><li>Multimedia Services Ontology </li></ul><ul><li>Service Composition Patterns </li></ul><ul><li>Adding Semantics to Service Composition </li></ul><ul><li>Enhancing the Business Model through Service Brokerage </li></ul>
    3. 3. Next Generation Networks Evolution Drivers <ul><li>Societal and Business trends </li></ul><ul><li>Internet is becoming a major enabler of communications </li></ul><ul><li>Consumers are embracing computing, mobile and digital technology in their everyday life </li></ul><ul><li>Evolution of Business models require increased levels of personal mobility </li></ul><ul><li>Access Technology Enhancements </li></ul><ul><li>HSPA (High Speed Packet Access) – evolved WCDMA </li></ul><ul><li>OFDMA (Orthogonal Frequency Division Multiple Access) – 3GPP LTE, WiMAX, MBWA, ADSL/VDSL, DVB-T/H etc. </li></ul><ul><li>Spatial Processing – multi-antennas Base Stations supporting advanced spatial processing </li></ul><ul><li>Convergence </li></ul><ul><li>Converged devices (Mobile, WLAN, Internet etc.)  Connectivity </li></ul><ul><li>Converged services  Ease of use </li></ul><ul><li>Converged networks  Reliability, Security, Reduced OPEX/CAPEX </li></ul><ul><li>Converged business models  Increased margins, Avoidance of twin pitfalls risk </li></ul>
    4. 4. The Evolution to Multimedia Applications A Mobile View Non-Interactive Multimedia Image SMS MMS Presence Active phonebook Push-To-Talk Text Voice Voice P2P Calls Video Person-to-Person dominates traffic growth Movies Photos Internet Text/Pictures SMS/MMS HTTP Streaming Download Video Music Ring tone Person-to-Content known usability patterns Interactive Multimedia Multimedia Content Social Networking
    5. 5. IMS – 3GPP Architecture for Convergent Next Generation Services <ul><li>IMS is an open IP-based architecture using the Client-Server Network Computing model. </li></ul><ul><li>3GPP originally specified IMS to enable real-time multimedia services over the IP bearer, in GSM and W-CDMA networks. </li></ul><ul><li>Later, 3GPP2 specified the MMD architecture for CDMA2000 networks based on IMS. 3GPP2 requirements are part of Common IMS in IMS release 8. </li></ul><ul><li>The xDSL access, specified by TISPAN, is integrated into IMS. </li></ul><ul><li>The cable access, specified by CableLabs in PacketCable 2.0, is part of IMS release 8. </li></ul><ul><li>Interworking with WLAN was specified in IMS release 6, while the mobility with WiMAX has been addressed in EPC specifications. </li></ul><ul><li>If IMS is not used: </li></ul><ul><ul><li>Multimedia communication at best effort </li></ul></ul><ul><ul><li>Service roaming can be difficult to implement </li></ul></ul><ul><ul><li>Provisioning and charging are service specific </li></ul></ul><ul><ul><li>Compliance with LI requirements can be an issue </li></ul></ul>
    6. 6. IMS Service Routing – the IFCs P-CSCF Visited A P-CSCF Visited B S-CSCF IMS AS HSS S-CSCF IMS AS HSS I-CSCF 1 2 3 4 Home A Home B 5 6 7 8 9 10 11 <ul><li>In comparison to IETF SIP Routing where the originator of SIP request may specify a preferred path in the Route header, in IMS the P-CSCF removes this path and ensures that IMS SIP Routing is followed. </li></ul><ul><li>SIP requests in IMS architecture are always routed to the Home S-CSCF, in both the originating and terminating network. </li></ul><ul><li>The S-CSCF uses subscriber’s Service Profile (downloaded during registration), to link-in the SIP AS’ which will process the SIP request. </li></ul><ul><li>The Initial Filter Criteria (IFC) within the Subscriber Profile provide a simple service logic to decide which AS shall be linked-in. These rules are of static nature i.e. they do not change frequently. </li></ul>IMS Service Routing = Service Profile based Routing
    7. 7. Limitations of ISC Service Orchestration Model <ul><li>The application server decides whether to remain linked-in for the whole session by adding its address to the Record-Route SIP header. </li></ul><ul><li>Application Servers are unaware of the existence of other AS', and whether these will be linked-in. </li></ul><ul><li>No service or session state will be passed between application servers unless they use proprietary extensions i.e. are co-designed. </li></ul><ul><li>Response messages are routed to the AS’s in the reverse order </li></ul>S-CSCF HSS SIP-AS SIP-AS SIP-AS I-CSCF S-CSCF HSS SIP-AS SIP-AS SIP-AS I-CSCF <ul><li>If during call handling procedure an AS retargets the SIP request by changing the Request URI, subsequent filter analysis in the S-CSCF is stopped and the S-CSCF forwards the request towards the new target without linking-in the other AS’ specified by IFC. </li></ul>Req URI = A Req URI = B 1 2
    8. 8. NG Service Platform The IMS-based Design
    9. 10. NG Service Platform Functional Description <ul><li>Service Composition: </li></ul><ul><li>Invokes the services published by external Service Providers which are interconnected in a Service Overlay Network. </li></ul><ul><li>Services can be linked in statically (BPEL workflows) or dynamically, using their semantic description (OWL-S) </li></ul><ul><li>Corresponds to the network-centric composition model => lower complexity of client implementation. </li></ul><ul><li>Service Mediation: </li></ul><ul><li>Mediates service protocols, data format, identity, security features, business processes </li></ul><ul><li>Service Brokerage: </li></ul><ul><li>Negotiates with other brokers in the Service Overlay Network the services which the Service Composition function will invoke. </li></ul><ul><li>Uses context information to bind services based on dynamic conditions. </li></ul><ul><li>Service Discovery: </li></ul><ul><li>Publishes local services and performs service searches in the Service Overlay Network. </li></ul><ul><li>Searches can be static (UDDI queries) or dynamic (UDDI queries with constrains, SWS Proxy queries). </li></ul>
    10. 11. Agenda <ul><li>NG Service Platform </li></ul><ul><li>Multimedia Services Ontology </li></ul><ul><li>Service Composition Patterns </li></ul><ul><li>Adding Semantics to Service Composition </li></ul><ul><li>Enhancing the Business Model through Service Brokerage </li></ul>
    11. 12. Service Modeling using Ontologies <ul><li>Gruber, 1993: </li></ul><ul><li>“ An Ontology is a formal, explicit specification of a shared conceptualization of a domain.” </li></ul><ul><li>Formal = unambiguous, machine understandable, described using a formal language </li></ul><ul><li>Explicit = precise, clarifying the subject </li></ul><ul><li>Conceptualization = abstract representation of the object of study </li></ul><ul><li>Ontologies consist of a set of axioms which place constrains on classes of individuals, and the types of relationships allowed between them. </li></ul><ul><li>Can be described in graphical form (ex. RDF, UML) or logical form (ex. Description Logic, Rules). </li></ul>RDF/S = Resource Description Framework / Schema OWL = Ontology Web Language SWRL = Semantic Web Rule Language RIF = Rules Interchange Format Semantic Web Stack User Interface and Applications Trust Encryption Proof RIF/ SWRL OWL Logic RDFS SPARQL RDF XML URI Unicode
    12. 13. Multimedia Services Ontology <ul><li>Multimedia Services Ontology is a sub-ontology of Multimedia Ontology which is associated to Multimedia Communication domain. </li></ul><ul><li>Multimedia Ontology makes multimedia services provided by various Service Providers (Telecom, IT, Web 2.0) interoperable. </li></ul><ul><li>Constructs of the ontology: </li></ul><ul><li>Syntactic/semantic description of offered services (WSDL/OWL) </li></ul><ul><li>Description of mediation functions that can be linked-in at run-time </li></ul><ul><li>Description of data published </li></ul><ul><li>Specification of communication protocols </li></ul><ul><li>Description of Service Composition framework. Should include, if applicable, the description of the language used to specify the semantic composition </li></ul>Multimedia Ontology Services Sub-ontology Identity Sub-ontology Presence Sub-ontology Content Sub-ontology Security Sub-ontology Context Sub-ontology
    13. 14. Agenda <ul><li>NG Service Platform </li></ul><ul><li>Multimedia Services Ontology </li></ul><ul><li>Service Composition Patterns </li></ul><ul><li>Adding Semantics to Service Composition </li></ul><ul><li>Enhancing the Business Model through Service Brokerage </li></ul>
    14. 15. Service Oriented Computing (SOC) Service composition types: Service Orchestration = centralized engine which coordinates composed services according to a set of rules (workflow specification) Service Choreography = multiple actors/agents participate at the implementation of service composition (orchestration between every pair of choreographers) <ul><li>In SOC, applications are statically/dynamically composed using services deployed in the network. The collaboration model can be t ransactional (synchronous), or workflow-based (asynchronous) </li></ul><ul><li>SOA is one possible realization framework of SOC. The communication paradigm typically used in SOA is Web Services </li></ul><ul><li>Web Services are: </li></ul><ul><ul><li>Published (WSDL, OWL, SWSF) </li></ul></ul><ul><ul><li>Deployed </li></ul></ul><ul><ul><li>Discovered (UDDI, WSMO) </li></ul></ul><ul><ul><li>Invoked (SOAP) </li></ul></ul>Distributed Computing Evolution Message Driven (MOM) Components (Corba, EJB) Client/Server Service Oriented (SOA, Web 3.0)
    15. 16. Service Oriented Computing (cont.) Static Service Composition Developer Studio End User Studio Service Creation Environment Publish UDDI Composition Engine Discover User / Service Profile User context BPEL Rules Ambient context Service Discovery and Publication Temporal context Broker Context
    16. 17. Web 2.0 in SOC landscape <ul><li>Tim O’Reilly Web 2.0 definition: </li></ul><ul><li>The Web as a platform </li></ul><ul><li>Leverages customer data management (mash-ups) and user interaction model. Hence the challenge is to own core data (presence, location, identity, namespaces) </li></ul><ul><li>Promotes service evolution through user contributions. </li></ul><ul><li>The API’s exposed are simple enough so anybody can innovate. </li></ul><ul><li>No more software release cycles. Services are permanently in beta release. </li></ul><ul><li>Syndication of data instead of control. The data owner is actually paid by the advertisers. </li></ul><ul><li>Multi-device client (ex. Google/Open Handset Alliance Android mobile platform) </li></ul><ul><li>Rich user experience </li></ul>
    17. 18. Web 2.0 Design Elements <ul><li>Blogs, Wikis, IM & Chat </li></ul><ul><li>Buddy List, Mashups </li></ul><ul><li>Publishing, Content Sharing </li></ul><ul><li>Open APIs: REST, RSS, JSON, SOAP, XML </li></ul><ul><li>Widgets: OpenSocial, Web Widgets, Gadgets, Badges </li></ul><ul><li>Syndication: RSS, ATOM </li></ul><ul><li>OpenSocial highlights: </li></ul><ul><li>Based on open standards (XML, HTML, Javascript, ATOM and REST). Uses Google Gadgets FW. </li></ul><ul><li>Can be combined with OpenID (common identity framework). </li></ul><ul><li>Personal data moves from site to site. </li></ul><ul><li>Each API addresses one area: People & Friends, Activities, Persistence, General API. </li></ul><ul><li>Mashup highlights: </li></ul><ul><li>Aggregation of data centric network services using asynchronous interactions (AJAX) </li></ul><ul><li>Implemented with client/server or three-tier architectures: </li></ul><ul><ul><li>Content/API provider: shares mashable data objects typically retrieved using RSS, ATOM, SOAP, REST interfaces or “ Screen Scraping” </li></ul></ul><ul><ul><li>Mashup hosting site (in three-tier architecture): server which aggregates data using Java Servlets, CGI, PHP or ASP. </li></ul></ul><ul><ul><li>Mashup client: uses client scripts (JavaScript) or applets to allow support of Rich Internet Applications (RIA) </li></ul></ul><ul><li>Data may be cached in the client device (SQLite) </li></ul>Devices Transport / Control Layer Service Enablers Application Social APIs Social Applications Social Network Diagram
    18. 19. Service Composition in Web 2.0 <ul><li>Compared to BPEL/WSCI developer-centric composition, Web 2.0 uses ad-hoc composition . The user builds the composite service “on-the-fly” from data retrieved from the network. Mobile devices (Smartphones) now have 128MB of RAM and 620 Mhz CPU, so Web 2.0 clients can now be mobile. </li></ul><ul><li>Web 2.0 application design is performed by the end user who in essence, has low programming skills. The service composition is defined through interaction with a GUI. </li></ul><ul><li>Client controlled composition </li></ul><ul><li>Development: client components use APIs to access server data </li></ul><ul><li>Execution: components run on the client and pre-fetch data from the server </li></ul><ul><li>Server controlled composition (early stage) </li></ul><ul><li>Development: the server uses public APIs to link services into new services </li></ul><ul><li>Execution: the client invokes the server which acts as an orchestrator </li></ul>Photo Storage Data Base Node Service Application Logic Page Logic API Templates Endpoints Email 3PP Appl. Flickr Appl Flicker Architecture
    19. 20. SOA Reference Model <ul><li>What is SOA: </li></ul><ul><li>A paradigm which defines concepts and general techniques for the design, encapsulation and instantiation of reusable business functions using loosely coupled service interactions </li></ul><ul><li>SOA Reference Model: </li></ul><ul><ul><li>Service </li></ul></ul><ul><ul><li>Service description </li></ul></ul><ul><ul><li>Interaction </li></ul></ul><ul><ul><li>Contract & Policy </li></ul></ul><ul><ul><li>Visibility </li></ul></ul><ul><ul><li>Execution Context </li></ul></ul><ul><ul><li>Real world effect </li></ul></ul>SOA Service Description Model
    20. 21. SOA Service Composition <ul><li>SOA Characteristics </li></ul><ul><li>Services have well defined Service Contracts </li></ul><ul><li>Services are encapsulated </li></ul><ul><li>Services share a message bus and messages exchanged are well documented </li></ul><ul><li>Services can be discovered dynamically </li></ul><ul><li>Services are loosely coupled </li></ul><ul><li>Systems of services are assembled at runtime </li></ul>Routing based on service identity (equivalent to PSI routing in IMS) <ul><li>Service bus functions: </li></ul><ul><li>Supports an asynchronous message based communication protocol that uses a common format encoding scheme (SOAP/XML) </li></ul><ul><li>Routes, Translates and can Store and Forward exchanged messages </li></ul><ul><li>Supports a Discovery mechanism </li></ul>Client
    21. 22. IMS-SOA Architecture <ul><li>Service Enablers: </li></ul><ul><li>Provide functionality which can be used by other end-user applications (ex. Location Service) </li></ul><ul><li>Unaware of the context in which they are used. Only the consumer service is aware. </li></ul><ul><li>Service Bus </li></ul><ul><li>Handles the communication between IMS Application Servers and the Service Enablers and the communication with SOA Application Servers. </li></ul><ul><li>Optimized for Server-to-Server communication </li></ul><ul><li>Besides providing support for standard open protocols (ex. SOAP), may provide support for Native Interface protocols (ex. MLP, MM7, SIP etc.) </li></ul><ul><li>Service Orchestration </li></ul><ul><li>The consumer AS that invokes the Service Enabler implements the SCIM function. An external Service Broker may be used as well. </li></ul><ul><li>IMS Service Enablers are invoked from SOA domain through the GW AS. </li></ul>CSCF IMS AS GW AS Service Bus SOA AS UDDI SOA IMS Orig. network SOAP/XML SB API SB API Schema Service Contract JSR 281 Enabler SB API SIP MLP MM7 Heterogeneous Service Bus IMS-SOA Architecture
    22. 23. Parlay X Web Services WS-I Basic Profile: WSDL + SOAP WS-I Secure Profile: WSDL + SOAP + WS-Security <ul><li>Parlay X Web Services is an abstraction of Parlay WS </li></ul><ul><li>Parlay X WS GW acts as a Service Broker SCIM </li></ul><ul><li>Enablers which only support WS-I Basic Profile are enhanced with additional WS functionality such as WS-Security, WS-Policy, WS-Addressing </li></ul><ul><li>Services defined so far (17) cover: call control, messaging (SMS, MMS), payment, location, geocoding and mapping, presence etc. </li></ul><ul><li>Described in WSDL. Service discovery is based on UDDI. </li></ul>
    23. 24. Agenda <ul><li>NG Service Platform </li></ul><ul><li>Multimedia Services Ontology </li></ul><ul><li>Service Composition Patterns </li></ul><ul><li>Adding Semantics to Service Composition </li></ul><ul><li>Enhancing the Business Model through Service Brokerage </li></ul>
    24. 25. The Semantic Web Tim Berners-Lee, 2001: “ The Semantic Web looks at applications that enable transformations, by being able to take large amounts of data and be able to run models on the fly - whether these are financial models for oil futures, discovering the synergies between biology and chemistry researchers in the Life Sciences, or getting the best price and service on a new pair of hiking boots.” <ul><li>Highlights: </li></ul><ul><li>Information on the Web is machine understandable => automatic service discovery, invocation and composition. </li></ul><ul><li>Modeled as a graph where nodes have semantic descriptions. In Web 1.0 and 2.0 node descriptions are only syntactic. </li></ul><ul><li>Uses ontologies to represent elements of a domain and their relationships (OWL-S, SWSF, IRS-III, WSMO) </li></ul>Non-semantic web tag: <item>cat</item> Semantic web tag: <item rdf:about=“”>cat</item> SWS Service Profile Semantic Modeling using OWL-S Service Grounding Service Model presented by implements interacts using SWS = Semantic Web Service
    25. 26. SWS Execution Engine <ul><li>Performs semantic information processing and ontology reasoning in order to: </li></ul><ul><ul><li>discover and select the matching service </li></ul></ul><ul><ul><li>mediate the data, the protocol or the business process associated to service invoked. </li></ul></ul><ul><ul><li>invoke the service </li></ul></ul><ul><li>Supports both the orchestration and choreography paradigms </li></ul><ul><li>Data exchanged by SWS is described as an ontology. </li></ul><ul><li>Can be looked at as a SOA implementation which allows to add/remove components at run-time. </li></ul>Resource DB Semantic Execution Environment Web Service Discovery Composition Engine Communication Handler Matchmaker Service Mediation Semantic/Ontology Reasoning
    26. 27. Semantic Service Composition <ul><li>Semantic Composition Paradigms: </li></ul><ul><li>Action Based : the Reasoner uses the semantic description of discovered services to match requester goal at each composition step (run-time). Execution takes place directly through the grounding of the services. </li></ul><ul><li>AI Planning : a task list is generated to achieve the composition objectives i.e. service selection and flow management. Compensation in case of failure and replanning is a challenge. Examples of AI Planning: Conditional Planning, Conformant Planning, Hierarchical Task Planning (HTP) </li></ul><ul><li>Hybrid (Xplan) : Combines guided local search with graph planning and a light form of HTP to produce a plan sequence of actions. </li></ul>There is not yet a unifying framework to allow interoperability between intelligent agents / reasoning engines. Y Z X Z X Y Planning - Set of actions - Pos./neg. effects - Initial state description - User’s goal Sequence PDDXML Parser Topology Handler Connectivity Graph Goal Determination Xplan-based Composition Enforced Hill Climbing Engine PDDXML plan description Planning Graph Generation PDDXML problem, domain description
    27. 28. Agenda <ul><li>NG Service Platform </li></ul><ul><li>Multimedia Services Ontology </li></ul><ul><li>Service Composition Patterns </li></ul><ul><li>Adding Semantics to Service Composition </li></ul><ul><li>Enhancing the Business Model through Service Brokerage </li></ul>
    28. 29. Service Brokerage in SOC <ul><li>Why we need Service Brokers: </li></ul><ul><li>Users are interested to customize service interaction model and run-time features based on context conditions (Ambient Intelligence, Location, Privacy Preferences etc.) </li></ul><ul><li>Control of the payment model. Users who do not want adds and are rather looking into QoS and Security/Privacy, need a Service Broker function in the network which can negotiate the service characteristics with multiple service providers based on user profile. </li></ul>Google business model: Users accept advertising and profiling in return to free services. AsSense, AdWorks - advertisers/publishers or youTube - content providers/users, perform brokerage at business level. <ul><li>Service Broker functions: </li></ul><ul><li>Ranks services offered by the Service Providers based on service characteristics. It may do this autonomously (rules based negotiation), or by interacting with the user </li></ul><ul><li>Matches the service interaction model with context conditions </li></ul><ul><li>Performs identity and trust brokering </li></ul><ul><li>Performs payment brokering </li></ul><ul><li>Handles synchronization between fine-grained services </li></ul>Service Consumer Service Description Service Provider invoke ( ) bindTo ( ) Service Broker find ( ) negotiate ( ) use offer described in contains description User / Service Profile User context Ambient context Temporal context Broker Context decisions
    29. 30. IMS Payment Brokerage <ul><li>The roles in Payment Model are similar to those in Credit Card industry: </li></ul><ul><ul><li>Consumer </li></ul></ul><ul><ul><li>Merchant = Content Provider who publishes, supplies and sells content. </li></ul></ul><ul><ul><li>Broker/Acquirer </li></ul></ul><ul><ul><li>Issuer = Mobile Operator. The Operator uses its existing billing relationship with the consumer to charge for content. </li></ul></ul><ul><li>IMS services standardized so far (MMtel, PoC, Image/Video Share) have been deployed in the operator domain as their target are the telecom communities (mass deployments). </li></ul><ul><li>Separate from these basic services, it is expected that many new community specific services (niche services) will be provided in the near future by Service Providers. These services use open communication protocols (instead of SIP) and do not handle charging of the user directly. Instead, they use their business and trust relationship with the operator, to delegate payment service. </li></ul><ul><li>The Payment Brokerage function facilitates the establishment of the business relation between 3rd Party Content/Service Providers and mobile operators. </li></ul>Payment Model
    30. 31. Conclusions <ul><li>Recent deployments of Multimedia and VoIP services in the Telcom and the Internet domain, have determined a blurring of roles in the value chain while at the same time enabling new business models. </li></ul><ul><li>Next Generation Services Convergence requires: </li></ul><ul><ul><li>Implementation of converged devices (multi-access devices) </li></ul></ul><ul><ul><li>Support of a multi-access edge network </li></ul></ul><ul><ul><li>Unified roaming and session management framework </li></ul></ul><ul><ul><li>Development of service enablers </li></ul></ul><ul><ul><li>Interoperability between the native Service Platform (SP) and external Service Overlay Networks </li></ul></ul><ul><li>The SP Interoperability Middleware has to provide support for: </li></ul><ul><ul><li>Service Composition and Brokerage </li></ul></ul><ul><ul><li>Service Mediation </li></ul></ul><ul><ul><li>Service Discovery </li></ul></ul><ul><li>Service Platform features like Multimodal Interaction, Interaction Management based on Ambient Intelligence, Content Management, Brokerage and Management of Semantic Information are desirable due to their significant impact on service usability. </li></ul>
    31. 32. Thank you for your attention! [email_address]