Telecom SOA Use Cases and Gap Analysis Version 1.0

OASIS TC Committee Draft

20 January 2009

Editor Note: The URL’s will be fixed in the next revision of the document.

Specification URIs:

This Version:

http://docs.oasis-open.org/tc-short-name] / /filename] .html

http://docs.oasis-open.org/tc-short-name] / /filename] .doc

http://docs.oasis-open.org/tc-short-name] / /filename] .pdf

Previous Version:

http://docs.oasis-open.org/tc-short-name] / /filename] .html

http://docs.oasis-open.org/tc-short-name] / /filename] .doc

http://docs.oasis-open.org/tc-short-name] / /filename] .pdf

Latest Version:

http://docs.oasis-open.org/tc-short-name] / /filename] .html

http://docs.oasis-open.org/tc-short-name] / /filename] .doc

http://docs.oasis-open.org/tc-short-name] / /filename] .pdf

Technical Committee:

OASIS SOA for Telecom (SOA-TEL) Technical Committee

Chair(s):

MIke Giordano, , Chair

John Storrie, , Chair

Editor(s):

Abbie Barbir,

Related work:

This specification replaces or supercedes:

·  Not Applicable

This specification is related to:

·  Not Applicable

Declared XML Namespace(s):

Not Applicable

Abstract:

TBD

Status:

This document was last revised or approved by the OASIS SOA for Telecom (SOA-Tel) TC on the above date. The level of approval is also listed above. Check the “Latest Version” or “Latest Approved Version” location noted above for possible later revisions of this document.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/ soa-tel/.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees soa-tel/ipr.php.

The non-normative errata page for this specification is located at http://www.oasis-open.org/committees/ soa-tel/.

Notices

Copyright © OASIS® 2009. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The names "OASIS", here] are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

Table of Contents

1 Introduction 5

1.1 Terminology 5

1.2 Normative References 5

1.3 Non-Normative References 5

2 Web Services Related Gaps 6

2.1 Assumed standards Landscape and Architecture 6

2.2 Transaction Endpoints Specification 7

2.2.1 Scenario 7

2.2.2 Use Case 7

2.2.3 Possible Gaps 8

2.2.4 Editor Note: This is a place holder for possible Workaround 9

2.3 Service Non Functional Properties (NFP) 10

2.4 Service Discovery 10

2.5 Service Level Agreements (SLA) 10

2.5.1 Composed services and their part in Web Services Service Level Agreements (WSLA) 10

2.6 Telecom WS SOA Profile 11

2.7 Service Orchestration (BPEL) 11

3 Web 2.0 and Telco 2.0 12

3.1 Gaps Related to Parlay-X 12

4 Other Stacks 13

# Conformance 14

A. Acknowledgements 15

B. Non-Normative Text 16

C. Revision History 17

ntifier] 20 January 2009

Copyright © OASIS® 2009. All Rights Reserved. Page 12 of 17

1  Introduction

ed]

TBD

1.1 Terminology

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].

1.2 Normative References

[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.

Reference] ion]

1.3 Non-Normative References

Reference] ion]

2  Web Services Related Gaps

This section provides example uses cases that cover gaps that are related to web services standards as they apply to telecom services.

2.1 Assumed standards Landscape and Architecture

The figure in this section reflects the current understanding on the relationship between various standardization bodies to the work of this TC.

Editor Note:

Need to develop a very high level architecture that illustrates how the uses cases will work. The architecture should include the role of mediation (proxies for thin and fat clients, mobility and other scenarios)

2.2 Transaction Endpoints Specification

2.2.1 Scenario

The issue presented in this contribution derives from a concrete case, implemented within Telecom Italia’s SOA Middleware.

Telecom Italia is in the process of deploying a SOA infrastructure, of which some of the constituting elements are an ESB (Enterprise Service Bus), a BPM (Business Process Manager), some “Service Consumers (systems or applications), some “Service Providers” (systems or applications).

An aspect to be considered is that to satisfy performance criteria it has been decided that the ESB must be intrinsically “stateless” (i.e. it must not store any persistence information on destination of incoming service requests).

Moreover, the “number” of ESBs can vary, i.e. there can be interconnetted trunks of different vendors’ ESBs.

2.2.2 Use Case

The following Use Case describes Telecom Italia’s technical problem. To improve readability the depicted use case presents only one instance of ESB, but the possible solution to the problem must satisfy also the cases of multiple instances of ESB.

A Service Consumer (C1 or C2) invokes a Service, implemented as a Web Service (Web Service A).

Such WSA is achieved as an “itinerary” with the composition of more elementary services, provided by Provider P1 and Provider P2.

The ESB provides intermediary services for final exposition, enrichment and Data reconciliation and routing.

·  Case A: C1 is the originator and final receiver.

·  Case B: C2 is the originator and final receiver.

Figure 1 Scenario Implementation

Figure 2 Scenario Flow

Use Case Steps:

Case A

·  C1 invokes WSA, exposed by ESB.

·  WSA is executed with the internal composition (transparent to C1) and with intermediary services provided by the ESB.

·  At the end of the internal interactions, the ESB forwards the response to C1.

Case B

·  C2 invokes WSA, exposed by ESB.

·  WSA is executed with the internal composition (transparent to C2) and with intermediary services provided by the ESB.

·  At the end of the internal interactions, the ESB forwards the response to C2.

2.2.3 Possible Gaps

To Telecom Italia’s knowledge and expertise, in presence of an ESB offering intermediary services, there is no formal way to specify the endpoint (e.g. C1 or C2) to which the final result of a “process/transaction" (i.e. asynch response) result should be sent.

2.2.4 Editor Note: This is a place holder for possible Workaround

This issue could be solved with the following “workaround” solution, which in any case is not mandatory but exploits some “optional” features of WS-Addressing.

Note:

This proposal does not require any “persistence” on any intermediary and is fully compliant with WS-Addressing specification.

Telecom Italia asks if, apart from the proposed workaround, there is another standard reference solution for the highlighted problem.

Should there be no other solution apart from the proposed workaround; TI proposes to extend the WS-Addressing specification in order that the “Message Properties” include a new tag (provisionally named “Final Destination”) to specify the process/transaction result.

Moreover the proposal is to make the utilization of this new tag as Mandatory whenever it is necessary to specify a “final destination”, i.e. in presence of a non-direct “requester-consumer” situation.

Proposed Workaround:

CASE A:

  1. C1 invokes WS-A and specifies in the replyTo section of the WS-Addressing header the EPR (Endpoint Reference) where it wants to receive the async response (C1).
    (Example: http://service1.sc.local/response).
  1. The ESB invokes WSB and specifies in the replyTo section of the WS-Addressing header the EPR (Endpoint Reference) where it wants to receive the async response (Example: http://service1.esb.local/response). By doing so it takes the replyTo section received by C1 and embeds it in the referenceParameters section of replyTo. P1 is obliged by WS-Addressing specification to return the referenceParameters in the To section when sending the async response.
  1. P1 returns the async response to the replyTo address (Example: http://service1.esb.local/response) specified by the ESB, together with the referenceParameters section.
  1. The ESB invokes WSC and specifies in the replyTo section of the WS-Addressing header the EPR (Endpoint Reference) where it wants to receive the async response (Example: http://service2.esb.local/response). By doing so it takes the referenceParameters section received by WSB and embeds it in the replyTo section. P2 is obliged by WS-Addressing specification to return the referenceParameters in the To section when sending the async response.
  1. P2 returns the async response to the ESB replyTo address (Example: http://service2.esb.local/response) specified by the ESB, which includes the referenceParameters section.
  1. The ESB gets the replyTo info, embedded in the referenceParameters received from P2, to address the async response to C1.

CASE B:

Same as Case 1 with C2 originator and final destination.

2.3 Service Non Functional Properties (NFP)

Editor Note: This section is a place holder for Non Functional Properties. Contributions are encouraged.

2.4 Service Discovery

Editor Note: This section is a place holder for Discovery. Contributions are encouraged.

Ø  To discover available services and may be other devices in a network

Ø  Many techniques for service discovery

Ø  UDDI for Web services

Ø  Jini for Java objects

Ø  Simple Service Discovery Protocol (SSDP) used for Universal plug-and-play (UPnP)

Ø  DNS Service Discovery (DNS-SD)

Ø  Bluetooth Service Discovery Protocol (SDP)

Ø  Service Location Protocol (SLP)

Ø  How about HTTP Discovery?

2.5 Service Level Agreements (SLA)

Editor Note: This is a place Holder for material on SLA

Ø  Need to differentiate between service SLA and measuring service SLA compliance

Ø  Services may need to have a service compliance interface (testing to verify claims against SLA)

Ø  Relationship to service composition

Ø  W-SLA, service testting and monitoring

Ø  Relation to Non-functional properties

2.5.1 Composed services and their part in Web Services Service Level Agreements (WSLA)

Ø  Need a taxonomy or ontology of service behaviors

Ø  Need an approach to calculating behaviors of composed services

o  Service failure is one of many identified behaviors

2.6 Telecom WS SOA Profile

Editor Note: This is a place Holder for material on Telecom SOA Profile. The main issue here is to identify the minimum number of WS specifications that need to be supported by Telecom Providers and establishing an interoperability profile to implement them in a composed fashion. Contributions are encouraged. Current specifications include:

4  WS Addressing

4  WS reliable messaging

4  WS security

4  SOAP over JMS

4  General improvement of specs with guidelines to avoid proliferation of solutions

4  WS-Policy

2.7 Service Orchestration (BPEL)

Editor Note: This is a place Holder for material on BPEL. Use cases are encouraged.

•  BPEL originally designed for IT application space

•  Purpose: integrate long running inter-machine business processes