Matching interest and availability of services in distributed federated service domains

• US 8,352,610 B2
• Filed: 11/25/2009
• Issued: 01/08/2013
• Est. Priority Date: 11/25/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Silva-Lepe, Ignacio, Iyengar, Arun Kwangil, Mikalsen, Thomas Arthur, Rouvellou, Isabelle M., Subramanian, Revathi
• Primary Examiner(s): Yohannes, Tesfay
• Application Number:
  US12/625,806
• Publication Number:
  US 20110125903A1
• Time in Patent Office: 1,140 Days
• Field of Search: 709/226, 709/206, 709/223, 370/235, 370/254
• US Class Current: 709/226
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine

Abstract

Systems, methods, apparatus and articles of manufacture are disclosed for tracking, propagation and matching of messages pertaining to the interest in and availability of services across autonomous service domains. In one embodiment of the invention, a system of distributed, federated service domains in a service-oriented environment is provided wherein each service domain comprises: a plurality of locally provided services; a plurality of service requesters; and a service registry comprising descriptions of: one or more locally provided services; and one or more requested services, each of the requested services being one of: a fulfilled reference to a foreign service; and an unfulfilled reference to a foreign service.

Claims

1. A system of distributed, federated service domains in a service-oriented environment, each service domain comprising:

a plurality of locally provided services;

a plurality of service requesters; and

a service registry comprising descriptions of;

one or more locally provided services; and

one or more requested services, each of the requested services being one of;

a fulfilled reference to a foreign service; and

an unfulfilled reference to a foreign service;

wherein each service domain is implemented via one or more processor devices;

wherein an unfulfilled requested service reference in the service registry is fulfilled once or multiple times; and

wherein the description of a service comprises a function interface, a non-functional criterion, or informal semantics.

2. The system of claim 1, wherein a federation service maintains a record of the distributed, federated service domains in the system.

3. The system of claim 1, wherein a locally provided service is composed with a service requester to form a mediation s/r, where s is a provided service component and r is a service requester component.

4. The system of claim 1, wherein an entry for a locally provided service in the registry comprises a list of dependent service domains, each dependent service domain containing in its registry a fulfilled reference including a description of this provided service.

5. A method for matching interest and availability of services in a service-oriented environment, the method comprising steps of:

instantiating two or more service domains, each service domain configured to send and receive interest, availability and connectivity messages to and from other service domains;

sending from a service domain an availability message for a service s1 to other domains, wherein the availability message comprises a description of the service s1 to match with, and a reference to its domain, and wherein the service domain locally registers availability of the service s1, and waits to hear for interest in the service s1;

receiving at the service domain an interest message, wherein the interest message comprises a description of the service s1 to match with, and a reference to the sender domain, the service domain then sending a connectivity message to the sender domain, if the service s1 is locally available, where the connectivity message comprises a proxy to the locally provided service s1;

sending from the service domain an interest message for a service s2 to other domains, wherein the interest message comprises a description of the service s2 to match with, and a reference to its domain, wherein the service domain locally registers an unfulfilled reference to the service s2, and waits to hear for a connectivity message for the service s2;

receiving at the service domain an availability message, wherein the availability message comprises a description of the service s2 to match with, and a reference to the sender domain, wherein the service domain then sends an interest message for the service s2 to the sender domain, if an unfulfilled reference to the service s2 is registered locally, wherein the interest message comprises a description of the service s2 to match with, and a reference to its domain; and

receiving at the service domain a connectivity message, wherein the connectivity message comprises a proxy to the foreign provided service s2, wherein the service domain then replaces the unfulfilled reference to the service s2 with the proxy to the service s2 in its local registry;

wherein each of the steps is implemented via one or more processor devices.

6. The method of claim 5, wherein the step of the service domain receiving a connectivity message further comprises replacing the unfulfilled reference to the service s2 with a single proxy or keeping the reference as unfulfilled and collecting multiple proxies, depending on whether the reference may be fulfilled once or multiple times.

7. The method of claim 5, wherein the description of the service s1 or s2 comprises a functional interface, a non-functional criterion, or informal semantics.

8. The method of claim 5, wherein the step of the service domain waiting to hear for a connectivity message for the service s2 further comprises timing out after a configurable amount of time and sending further interest messages until interest is fulfilled.

9. The method of claim 5, wherein the service domain sends an interest, availability, or connectivity message to any subset of service domains maintained in the service-oriented environment.

10. The method of claim 5, wherein the step of the service domain sending an availability message for the service s1, where the service s1 is composed into a mediation s1/r, happens after interest for the mediation'"'"'s requester component r is fulfilled, such that when the service s1 is a component of a mediation s1/r, the service domain sends interest for r first, and availability of s1 is not sent until the service domain receives a connectivity message for r.

11. The method of claim 5, wherein the step of the service domain receiving an interest message for a service s1 further comprises the service domain adding a reference to a list of dependent service domains for the service s1.

12. An article of manufacture comprising a non-transitory computer readable storage medium tangibly embodying computer readable program code which, when executed by a computer, causes the computer to carry out the steps of claim 5.

13. A method for matching negative interest and negative availability of services in a service-oriented environment, the method comprising steps of:

instantiating two or more service domains, each service domain configured to send and receive negative availability messages to and from other service domains;

sending from a service domain a negative availability message for a service to other domains, wherein the negative availability message comprises a description of the service to match with, and a reference to its domain; and

receiving at the service domain a negative availability message, wherein the negative availability message comprises a description of a service to match with, and a reference to the sender domain, and wherein the service domain then replaces a fulfilled reference to the service with an unfulfilled reference to the service, if a fulfilled reference to the service is registered locally, and sends an interest message for the service to other domains;

wherein each of the steps is implemented via one or more processor devices; and

wherein the description of the service comprises a functional interface, a non-functional criterion, or informal semantics.

14. The method of claim 13, wherein, when negative interest in a service occurs in the service domain, the service domain removes its reference to the service, fulfilled or unfulfilled, from its local registry, if said reference to the service is registered locally.

15. The method of claim 13, wherein in the step of the service domain sending negative availability for the service, the message is sent to each service domain in a list of dependent service domains for the service.

16. An article of manufacture comprising a non-transitory computer readable storage medium tangibly embodying computer readable program code which, when executed by a computer, causes the computer to carry out the steps of claim 13.

17. Apparatus for use in a service-oriented environment, the apparatus comprising:

a memory associated with an instantiated service domain; and

at least one processor device associated with the instantiated service domain, coupled to the memory, and configured to;

send from the service domain an availability message for a service s1 to one or more other instantiated service domains in the service-oriented environment, wherein the availability message comprises a description of the service s1 to match with, and a reference to its domain, and wherein the service domain is caused to locally register availability of the service s1, and to wait to hear for interest in the service s1;

receive at the service domain an interest message, wherein the interest message comprises a description of the service s1 to match with, and a reference to the sender domain, and cause the service domain to then send a connectivity message to the sender domain, if the service s1 is locally available, where the connectivity message comprises a proxy to the locally provided service s1;

send from the service domain an interest message for a service s2 to other domains, wherein the interest message comprises a description of the service s2 to match with, and a reference to its domain, wherein the service domain is caused to locally register an unfulfilled reference to the service s2, and waits to hear for a connectivity message for the service s2;

receive at the service domain an availability message, wherein the availability message comprises a description of the service s2 to match with, and a reference to the sender domain, wherein the service domain is then caused to send an interest message for the service s2 to sender domain, if an unfulfilled reference to the service s2 is registered locally, wherein the interest message comprises a description of the service s2 to match with, and a reference to its domain; and

receive at the service domain a connectivity message, wherein the connectivity message comprises a proxy to the foreign provided service s2, wherein the service domain is then caused to replace the unfulfilled reference to the service s2 with the proxy to the service s2 in its local registry.

18. The apparatus of claim 17, wherein the service domain is further caused to replace the unfulfilled reference to the service s2 with a single proxy or keep the reference as unfulfilled and collect multiple proxies, depending on whether the reference may be fulfilled once or multiple times.

19. Apparatus for use in a service-oriented environment, the apparatus comprising:

a memory associated with an instantiated service domain; and

at least one processor device associated with the instantiated service domain, coupled to the memory, and configured to;

send from the service domain a negative availability message for a service to one or more other instantiated service domains in the service-oriented environment, wherein the negative availability message comprises a description of the service to match with, and a reference to its domain; and

receive at the service domain a negative availability message, wherein the negative availability message comprises a description of a service to match with, and a reference to the sender domain, and wherein the service domain is caused to replace a fulfilled reference to the service with an unfulfilled reference to the service, if a fulfilled reference to the service is registered locally, and send an interest message for the service to other domains;

wherein the description of the service comprises a functional interface, a non-functional criterion, or informal semantics.

20. The apparatus of claim 19, wherein, when negative interest in a service occurs in the service domain, the at least one processor device is further configured to cause the service domain to remove its reference to the service, fulfilled or unfulfilled, from its local registry, if said reference to the service is registered locally.

21. The apparatus of claim 19, wherein when the service domain is caused to send negative availability for the service, the message is sent to each service domain in a list of dependent service domains for the service.