Method and apparatus for an end-to-end send-to framework

• US 7,827,233 B1
• Filed: 07/16/2004
• Issued: 11/02/2010
• Est. Priority Date: 07/16/2004
• Status: Active Grant

• Current Assignee: Syniverse ICX LLC
• Original Assignee: Syniverse ICX Corp. (Syniverse Corp.)
• Inventors: Fleming, Jonah Kaj, Swinton, William, Bodmer, Brian, Bodnar, Eric
• Primary Examiner(s): Nawaz; Asad M
• Assistant Examiner(s): HUQ, FARZANA B
• Application Number:
  US10/893,470
• Time in Patent Office: 2,300 Days
• Field of Search: 709/203, 709/204, 709/206, 709/207, 709/224, 709/227, 709/228
• US Class Current: 709/203
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• 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
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

A method and apparatus for providing a send-to framework is described. The method enables a round-trip mechanism between a stateless device and a third party service provider. In one embodiment, the method includes interposing a central server between the stateless device and the third party service provider, which maintains a state for the stateless device, and in one embodiment communicates the state to the third party service provide and/or the stateless device.

Claims

1. A system comprising:

a send-to framework to enable a round-trip mechanism between a stateless device and a third party service provider, by maintaining state data in a server, associated with messages sent to and from the stateless device,

adding, by the server, the state data to the messages sent to and from the stateless device, wherein the state data comprises an identifier assigned to a message to track message exchanges between the stateless device and the third party service provider,

forwarding, by the server, the messages sent from the stateless device, including the state data, to the third party service provider,

receiving, by the server, a response from the third party service provider,

determining, by the server, whether to direct the response to the stateless device, forwarding, by the server, the response sent from the third party service provider, including the state data, to the stateless device based on a determination to direct the response to the stateless device,

wherein the state data includes background information associated with at least one of;

a previous message sent to the stateless device and a previous message sent from the stateless device, and

maintaining, by the server, the state data such that when a message is received from the stateless device, the server forwards the message to the third party service provider including proper state data.

2. The system of claim 1, further comprising:

a personal address book provider to enable a user to select a service from the personal address book, the service provided by the third party service provider.

3. The system of claim 2, wherein the service does not identify the third party service provider with specificity.

4. The system of claim 2, wherein the third party provider can push content into the user'"'"'s personalized address book.

5. The system of claim 2, further comprising:

a composer launched upon selection of the service, the composer to enable the user to construct a request for the third party.

6. The system of claim 5, wherein the composer is run from a server.

7. The system of claim 1, further comprising:

a syntactic checker to ensure that the message to the third party is complete.

8. The system of claim 1, further comprising:

a third party selector to select a destination third party.

9. The system of claim 1, further comprising:

a format logic to format the message for the third party.

10. The system of claim 1, further comprising:

a data serving system to provide data to the third party in reply to the response.

11. A method of providing state data to communicate between a stateless device and a third party service provider, the method comprising

forwarding, by a server, a request from the stateless device to the third party service provider, wherein the request includes state data added by the server, the state data comprising an identifier assigned to the request to track message exchanges between the stateless device and the third party service provider;

receiving, by the server, a response from the third party service provider;

determining, by the server, whether to direct the response to the stateless device,

adding state data, by the server, to the response based on a determination to direct the response to the stateless device, wherein the state data includes background information associated with the request from the stateless device forwarded to the third party service provider;

forwarding, by the server, the response from the third party service provider, including the state data, to the stateless device, the state data utilized by the stateless device to associate the response with the request, and

maintaining, by the server, the state data such that when a message is received from the stateless device, the server forwards the message to the third party service provider including proper state data.

12. The method of claim 11, further comprising:

providing a personal address book including a listing of at least one service provided by a third party provider to the user, enabling the user to select a service from the personal address book.

13. The method of claim 11, further comprising:

receiving a follow-on message from the stateless device, in response to the response;

adding state data to the follow-on message; and

forwarding the follow-on message including the state data to the third party service provider.

14. A central server to enable communication between a stateless device and a state full third party, the central server comprising;

a processor;

a state tracking logic to assign an identifier to a message sent from the stateless device to the third party service provider to track message exchanges between the stateless device and the third party, to maintain state data associated with messages sent to and from the stateless device, wherein the state data includes background information associated with at least one of;

a previous message sent to the stateless device and a previous message sent from the stateless device;

a format logic to add the state data to messages sent to and from the stateless device;

a receiving logic to receive a response from the third party service provider; and

a directing logic to determine whether the response should be directed to the stateless device and to forward the response to the stateless device.

15. The central server of claim 14, further comprising:

an address book constructor to create personal address book for a user, the personal address book enabling the user to select a service provided by the third party service provider.

16. The central server of claim 15, further comprising:

a third party database to list a plurality of third party service providers able to fulfill a service requested from the user; and

a third party selector to select a third party to fulfill the service request from the user.