System and method for conversation based on web service addressing

• US 8,271,602 B2
• Filed: 01/11/2006
• Issued: 09/18/2012
• Est. Priority Date: 01/11/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Jin, Lei, Zotter, Brian
• Primary Examiner(s): NGUYEN, THU HA T
• Application Number:
  US11/329,898
• Publication Number:
  US 20070162549A1
• Time in Patent Office: 2,442 Days
• Field of Search: 709204-207, 709/217, 370/260, 715/733, 715/753
• US Class Current: 709/207
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

Embodiments of the present invention introduces mechanisms that allow conversational Web services to have long running business transactions between multiple parties with persistent states. Web service addressing is used to exchange conversational identifiers between the client(s) who requests the service and the server who provides it. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system to provide a conversational service, comprising:

a service provider operable to;

accept a service request message for the conversational service from a first client, wherein the service request message contains a callback address of the first client in a header of the service request message, wherein the callback address is based on a web service addressing protocol and is independent of an underlying transport protocol;

define the conversational service as a contract based on the web service addressing protocol, wherein the first client implements the contract and the contract allows the first client to communicate with the service provider;

create a conversation and a conversation identification;

automatically perform a callback address lookup that is transparent to the first client and is independent of the underlying transport protocol; and

provide a response associated with the conversation identification to the first client associated with the callback address using an intermediary service, wherein the response is in a uniform format independent of the underlying transport protocol,

wherein the intermediary service operates to

translate the response from the uniform format into a format acceptable by the first client; and

relay information between the service provider and the first client.

2. The system according to claim 1, further comprising:

a second client operable to;

accept the conversation identification contained in a construct from the service provider; and

participate in the conversation with the first client by embedding the conversation identification in its response to the service provider.

3. The system according to claim 2, wherein:

the construct can be an endpoint reference or a message information header.

4. The system according to claim 2, wherein:

the service provider operable to at least one of;

providing the conversation identification to the second client in the construct;

putting the conversation to sleep while waiting for a response from the second client; and

notifying the first client upon receiving the response from the second client.

5. The system according to claim 2, wherein:

the first client, the second client and the service provider are operable to communicate asynchronously via the conversation identification.

6. The system according to claim 1, wherein:

the first client can be a web service.

7. The system according to claim 1, wherein:

the service provider is further operable to extract the conversation identification from the first client'"'"'s service request message.

8. The system according to claim 1, wherein:

the conversational service can be a state machine.

9. The system according to claim 1, wherein:

the conversational service is operable to provide a plurality of methods.

10. The system according to claim 9, wherein:

the service provider is further operable to define access permission for at least one of the first client and the second client to the plurality of methods of the conversational service.

11. The system according to claim 1, wherein:

the service provider is further operable to save the conversation in a persistent store that allows multiple parties to access over a lifecycle of the conversation.

12. The system according to claim 1, wherein:

the service provider is further operable to notify the first client directly of getting the service request message in a format that is acceptable by the first client, before responding to the first client with the response later, via the intermediary service, when the response becomes available, wherein the uniform format is not acceptable by the first client.

13. The system according to claim 1, wherein:

the service request message is associated with a handler chain that is adapted to be saved by the first client when the service request is submitted asynchronously and the handler chain is used later to handle the response received by the first client.

14. The system according to claim 1, wherein:

the service provider can define a call back stub based on the contract, wherein the call back stub is a software component that is annotated and is populated with information needed for a callback operation.

15. The system according to claim 14, wherein:

the service provider can automatically process the service request message with the header to obtain the address of the first client and provide the address of the first client to the call back stub so that a response can be sent back to the first client at a callback time.

16. A method to provide conversational service via web service addressing, comprising:

accepting a service request message for a conversational service from a first client, wherein the service request message contains a callback address of the first client in a header of the service request message, wherein the callback address is based on a web service addressing protocol and is independent of an underlying transport protocol;

defining the conversational service as a contract based on the web service addressing protocol, wherein the first client implements the contract and the contract allows the first client to communicate with the service provider;

processing the service request message and creating a conversation and a conversation identification;

automatically performing a callback address lookup that is transparent to the party and is independent of the underlying transport protocol;

providing, via a service provider, a response associated with the conversation identification to the first client associated with the callback address using an intermediary service, wherein the response is in a uniform format independent of underlying transport protocol;

translating, via the intermediary service, the response from the uniform format into a format acceptable by the first client; and

relaying information between the service provider and the first client.

17. The method according to claim 16, further comprising:

providing the conversation identification contained in a construct to a second client;

putting the conversation to sleep while waiting for a response from the second client;

accepting the conversation identification in the construct from the service provider; and

participating in the conversation with the first client by embedding the conversation identification in a response to the service provider.

18. The method according to claim 17, further comprising at least one of:

notifying the first client upon receiving the response from the second client; and

communicating among the first client, the second client, and the service provider asynchronously via the conversation identification.

19. The method according to claim 16, further comprising at least one of:

extracting the conversation identification from the service request;

persisting the conversation in memory or in a persistent store;

managing the conversation via the conversational service, which can be a state machine; and

defining access permission for the party to a plurality of methods provided by the conversational service.

20. A machine readable medium having instructions stored thereon that when executed cause a system to:

accept a service request message for a conversational service from a first client, wherein the service request message contains a callback address of the first client in a header of the service request message, wherein the callback address is based on a web service addressing protocol and is independent of an underlying transport protocol;

define the conversational service as a contract based on the web service addressing protocol, wherein the first client implements the contract and the contract allows the first client to communicate with the service provider;

process the service request message and creating a conversation and a conversation identification;

automatically performing a callback address lookup that is transparent to the first client and is independent of the underlying transport protocol;

provide, via a service provider, a response associated with the conversation identification to the first client associated with the callback address using an intermediary service, wherein the response is in a uniform format independent of underlying transport protocol;

translate, via the intermediary service, the response from the uniform format into a format acceptable by the first client; and

relay information between the service provider and the first client.

21. A system to provide conversational service via web service addressing, comprising:

means for accepting a service request message for a conversational service from a first client, wherein the service request message contains a callback address of the first client in a header of the service request message, wherein the callback address is based on a web service addressing protocol and is independent of an underlying transport protocol;

means for defining the conversational service as a contract based on the web service addressing protocol, wherein the first client implements the contract and the contract allows the first client to communicate with the service provider;

means for processing the service request message and creating a conversation and a conversation identification;

means for automatically performing a callback address lookup that is transparent to the first client and is independent of the underlying transport protocol;

means for providing, via a service provider, a response associated with the conversation identification to the first client associated with the callback address using an intermediary service, wherein the response is in a uniform format independent of underlying transport protocol;

means for translating, via the intermediary service, the response from the uniform format into a format acceptable by the first client; and

means for relaying information between the service provider and the first client.