Service provision system and method

• US 20030036917A1
• Filed: 04/25/2002
• Published: 02/20/2003
• Est. Priority Date: 04/25/2001
• Status: Abandoned Application

• Current Assignee: Metallect Corp.
• Original Assignee: Metallect Corp.
• Inventors: McGrane, William B., Hite, Thomas D.
• Application Number:
  US10/133,611
• Publication Number:
  US 20030036917A1
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/06 Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A service provision method is disclosed. The method comprises creating a plurality of service descriptions to a desired level of exposure, the plurality of service descriptions each having a plurality of parameters. The method also comprises mapping at least a subset of the plurality of parameters from at least one of the plurality of service descriptions to create an Application Integration Metaservice (AIM) linking a set of preconditions necessary to satisfy a request for an effect of one of the plurality of service descriptions and the effect. The AIM is operable to be used to determine a metaservice to be executed utilizing the effect of the at least one of the plurality of service descriptions.

Claims

1. A service provision method, comprising:

creating a plurality of service descriptions to a desired level of exposure, the plurality of service descriptions each having a plurality of parameters;

mapping at least a subset of the plurality of parameters from at least one of the plurality of service descriptions to create an Application Integration Metaservice (AIM) linking a set of preconditions necessary to satisfy a request for an effect of one of the plurality of service descriptions and the effect; and

wherein the AIM is operable to be used to determine a metaservice to be executed utilizing the effect of the at least one of the plurality of service descriptions.

2. The method of claim 1, further comprising causing the metaservice to be executed.

3. The method of claim 1, further comprising creating the at least one of the plurality of service descriptions by populating a data structure consistent with standards known as Extensible Markup Language (XML).

4. The method of claim 1, further comprising performing the mapping by utilizing one of the group consisting of a solver and a Rete algorithm.

5. The method of claim 1, wherein the metaservice includes at least one of the group consisting of a Web services call, a function call, a database call, a network transaction, a retail transaction, an education transaction, a financial transaction, a corporate transaction, an ASP transaction, a travel transaction, and a medical transaction.

6. The method of claim 1, wherein the set of preconditions is one of the group consisting of no precondition, and a valid authentication code.

7. The method of claim 1, further comprising selecting the metaservice to be executed by using aggregate information within the AIM.

8. A service provision system, comprising:

a storage medium; and

a server interoperably coupled with the storage medium and operable to;

create a plurality of service descriptions to a desired level of exposure, the plurality of service descriptions each having a plurality of parameters;

store at least a subset of the plurality of service descriptions in the storage medium;

map at least a subset of the plurality of parameters from at least one of the plurality of service descriptions to create an AIM linking the output of one of the plurality of service descriptions and a set of preconditions necessary to satisfy a request for the output; and

wherein the AIM is operable to be used to determine a metaservice to be executed utilizing the output of the one of the plurality of service descriptions.

9. The system of claim 8, wherein the storage medium is a cache.

10. The system of claim 8, wherein the storage medium is a database.

11. The system of claim 8, wherein the storage medium comprises an ontology.

12. The system of claim 8, wherein the server comprises an execution engine operable to cause the metaservice to be executed upon request.

13. The system of claim 8, wherein the server is operable to map utilizing one of the group consisting of a solver and a Rete algorithm.

14. The system of claim 8, wherein the server is further operable to select an AIM to be executed by using aggregate information within the AIM.

15. An execution engine, comprising:

a computing platform;

logic interoperably coupled with the platform and operable to cause a metaservice to be executed; and

wherein the metaservice comprises at least one of an effect of one of a plurality of service descriptions created to a desired level of exposure and a set of preconditions necessary to satisfy a request for the effect.

16. The execution engine of claim 15, wherein one of the group consisting of a solver and a Rete algorithm is utilized to map possible links between the plurality of service descriptions create at least one AIM.

17. The execution engine of claim 15, wherein the logic is further operable to call at least one software agent process to execute at least a portion of the metaservice.

18. The execution engine of claim 15, wherein the logic is further operable to select the metaservice to be executed by using aggregate information within an AIM.

19. The execution engine of claim 15, wherein the logic is further operable to receive status information and select another metaservice within an AIM to be executed in response to the status information.

20. The execution engine of claim 15, wherein the logic comprises executable software instructions.

21. The execution engine of claim 15, wherein the plurality of service descriptions are created by populating a data structure consistent with standards known as XML.

22. A service description, comprising:

a data structure;

an effect stored within the data structure operable to be optionally mapped to a set of preconditions of another data structure; and

another set of preconditions stored within the data structure necessary to satisfy a request for the effect, according to a desired level of exposure.

23. The service description of claim 22, wherein the data structure is compatible with standards known as XML.

24. The service description of claim 22, further comprising aggregate information operable to be used to select metaservices to be executed.

25. The service description of claim 24, wherein the aggregate information comprises information from the group consisting of cost information, resource information, transaction duration time, and metadata allowing differentiation of metaservices.

26. The service description of claim 22, further comprising at least one of the group consisting of binding information, parameter information, connection information, service information, and a base address.

27. The service description of claim 22, wherein the effect is one of the group consisting of a Web call, a function call, a database call, a network transaction, a retail transaction, an education transaction, a financial transaction, a corporate transaction, an ASP transaction, a travel transaction, and a medical transaction.