System and method for composite business interactions in electronic commerce

• US 7,401,117 B2
• Filed: 06/10/2002
• Issued: 07/15/2008
• Est. Priority Date: 06/10/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Tarafdar, Ashis, Janakiraman, Pradeep, Dan, Asit, Dias, Daniel Manuel
• Primary Examiner(s): LIN, WEN TAI
• Application Number:
  US10/165,926
• Publication Number:
  US 20030229503A1
• Time in Patent Office: 2,227 Days
• Field of Search: None
• US Class Current: 709/203
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

A method, system, computer program product, and data structure for processing requests for services in a networked data processing system is provided. In one embodiment a request is received by a service provider. The request includes defined allowable actions and request definition compositions. The request also includes a plurality of actions wherein the relationships between the plurality of actions are defined. The service provider processes the plurality of actions according to the defined relationships and generates a response.

Claims

1. A method for processing service requests in a network environment, the method comprising:

receiving a request with defined allowable actions and request definition compositions, wherein the request comprises a plurality of actions with defined relationships between the plurality of actions;

processing the plurality of actions according to the defined relationships;

generating a response to the plurality of actions; and

wherein each action renders a reportable service, and formats of the request definition compositions and the defined relationship are defined by a service contract between a requester and a service provider, wherein the defined relationships comprises integrity rules to be followed during execution of the request, said rules comprising at least two of specifying a priority order in which the actions are to be executed, instructions that no action is to be finalized unless all of the actions can be finalized, and instructions that the actions are to be executed until a constraint specification is violated.

2. The method as recited in claim 1, wherein the request definition compositions comprise instructions for selection of an action for execution from a group of the plurality of actions.

3. The method as recited in claim 1, wherein the request definition compositions comprise instructions for execution of a group of actions from the plurality of actions.

4. The method as recited in claim 1, wherein the request comprise groups of actions organized in hierarchical groups and wherein the request definition compositions comprise instructions regarding order of execution of actions within groups and order of execution of groups.

5. The method as recited in claim 1, wherein the defined relationships comprise instructions to use the resulting output of one of the plurality of actions as the input of another one of the plurality of actions.

6. The method as recited in claim 1, wherein the plurality of actions are arranged in groups of actions with varying definitions defining relationships between actions within a group and between various groups.

7. The method as recited in claim 1, wherein the integrity rules may be applied at a group level.

8. The method as recited in claim 1, wherein the request is generated, received, processed, and the response generated in a local environment.

9. The method as recited in claim 1, wherein the request comprises a message header, a transactor, and an input message set, wherein the transactor comprises a plurality of actions and relationships between the plurality of actions and the input message set comprises a plurality of input messages and input identifications.

10. The method as recited in claim 9, wherein the message header includes a sender identification.

11. The method as recited in claim 1, wherein the response comprises a message header, a transactor, and an output message set, wherein the output message set comprises a plurality of output messages and output identifications.

12. The method as recited in claim 1, wherein the defined allowable actions and request definition compositions are defined by a service contract.