Systems and methods that utilize persisted push/pull state to provide reliable message publishing

• US 20050138112A1
• Filed: 12/18/2003
• Published: 06/23/2005
• Est. Priority Date: 12/18/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Klein, Johannes, Elien, Jean-Emile, Sagar, Akash J., Smith, Kevin B.
• Granted Patent: US 7,634,583 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

The present invention relates to systems and methods that facilitate pulling and/or receiving data from a client and posting the data for access by subscribing systems. The systems and methods include a message agent that generates a connection instance that can store connection-related information such as data conveyance state, data identification, and connection identification. Access to the connection instance can be provided to a machine, which can utilize the information to lock the connection and connection instance and begin pulling or receiving data from the client. As the machine pulls or receives data, the data can be published and the connection instance can be concurrently updated to reflect the present state of data conveyance. The information within the connection instance can be utilized to re-establish of severed connection, and to dynamically float the connection between machines to dynamically balance load, ensure reliability and recover from errors.

Claims

1. A system that facilitates data transfer from a remote component to a storage medium, comprising:

a connection management component that generates information for a connection with the remote component;

an information bank that stores the connection information; and

an interface component that utilizes the connection information to lock the connection and facilitate data transfer, the interface component dynamically updates the information stored in the information bank concurrently with the transfer of data in order to persist a data transfer state within the connection information.

2. The system of claim 1, the interface component employs on or more of the following connection protocols:

TCP/IP;

IPX/SPX;

UPD/IP;

FTP;

HTTP;

SOAP; and

a proprietary protocol.

3. The system of claim 1, the data is transferred via the interface component by at least one of pulling data from the remote component and receiving data pushed by the remote component.

4. The system of claim 1, the data is transferred as one or more of the following:

a stream;

a file;

one or more data packets; and

one or more data bursts.

5. The system of claim 1, the connection information comprises data related to at least one of the following:

a connection identity;

the storage medium identity;

an interface component identity;

a remote component identity;

a data receiving condition, a data transfer time-out, and a storage medium subscriber.

6. The system of claim 1, the interface component is concurrently employed in a plurality of servicing devices.

7. The system of claim 6, one of the plurality of servicing is provided with access to the connection information based at least in part on one or more of the following:

a request for a particular servicing device;

a present servicing device load;

an expected future servicing device load;

a servicing device capacity; and

a servicing device processing power.

8. The system of claim 6, access to the connection information is floated between the plurality of servicing devices based at least in part on one or more of the following:

a present servicing device load;

an expected servicing device load;

a servicing device capacity;

a servicing device processing power; and

an intelligent decision, in order to dynamically balance the transfer load across the plurality of servicing devices, the connection information is employed by the next servicing device to resume data transfer where it was paused.

9. The system of claim 6, access to the connection information is floated to another servicing device in order to recover from a voluntarily or involuntarily terminated connection, the connection information is employed by the new servicing device to resume data transfer where it was paused.

10. The system of claim 6, access to the connection information is voluntarily released by the servicing device based at least in part on one or more of the following:

a lapsed time-out, completion of data transfer, a transmission error, a transfer load threshold, and a signal indicating the connection is going to be floated, the connection information is employed by the next servicing device to resume data transfer where it was paused.

11. The system of claim 1, the interface component provides the connection management component with information related to one or more of the following:

the interface component;

the servicing devices selected to initiate the connection;

the remote component, a data receiving condition, a data transfer time-out, and a remote storage subscriber.

12. The system of claim 11, the information related to the interface component and the selected service device includes at least an identity of the interface component and an identity of the selected service device.

13. The system of claim 12, the identity of the interface component and/or the identity of the selected service device are utilized by the selected service device to lock the connection and connection information, wherein only the service device that owns the lock can facilitate data transfer from the remote component and update the connection information.

14. The system of claim 1, the interface component updates the data transfer state with information when a portion of data successfully or unsuccessfully is transferred

15. The system of claim 1 is employed in connection with a service window.

16. The system of claim 1, the interface component is invoked to initiate a connection with the remote component by one or more of the remote component, the storage medium, and a device subscribed to retrieve data from the storage medium.

17. A system that facilitates conveyance of one or more messages from a client to a database, comprising:

an adapter concurrently employed within one or more servers, the adapter is utilized to form a connection between the client and the database and facilitate conveyance of the one or more messages; and

a message agent that generates a connection instance based at least in part on a unique identity associated with one of the servers and the adapter and provides the connection instance to one of the servers;

the adapter dynamically updates the connection instance with a message conveyance state concurrently with message conveyance to save a present message conveyance state.

18. The system of claim 17 further comprises an API that facilitates coupling the adapter with the client.

19. The system of claim 17, the connection instance comprises information related to at least one of the following:

a connection identity;

a server identity;

an adapter identity;

a client identity;

a data receiving condition, a data transfer time-out, and a database subscriber.

20. The system of claim 19, the connection identity is a keep-alive message.

21. The system of claim 17, the server receiving the connection instance is selected based at least in part on one or more of the following:

a request for a particular server;

a present server load;

an expected future server load;

a server capacity; and

a server processing power.

22. The system of claim 17, the server receiving the connection instance utilizes at least a portion of the information within the connection instance to lock the connection and the connection instance and facilitate conveyance of the one or more messages, wherein only the server owning the lock can interact with the client and update the connection instance.

23. The system of claim 22, the server owning the lock on the connection voluntarily releases the lock based on at least one of the following:

a present server load;

an expected server load;

a server capacity;

a server processing power; and

an intelligent decision, in order to dynamically load balance message conveyance across the one or more servers, the new server owning the lock utilizes the information within the connection instance to resume message conveyance at the point where it was stopped.

24. The system of claim 22, the server owning the lock on the connection voluntarily releases the lock based at least in part on one or more of the following:

a lapsed time-out, completion of data transfer, a transmission error, a transfer load threshold, and a signal indicating the connection is going to be floated.

25. The system of claim 17, the connection instance is employed to detect a failed message conveyance and facilitate re-submission of the message by providing a message identification.

26. The system of claim 17 is employed in connection with a service window.

27. A method that facilitates data transfer from a client to a database, comprising:

generating a connection instance for a connection between the client and an adapter associated with the database, the connection instance stores at least information related to the state of the data transfer;

concurrently receiving data and updating the connection instance with at least a present state of data transfer; and

utilizing the present state to provide for at least one of data transfer reliability, error recovery and dynamic load balancing.

28. The method of claim 27 further comprises providing one of a plurality of machines employing the adapter with a keep-alive message associated with the connection instance, the machine receiving the keep-alive message locks the connection and connection instance and facilitates data transfer.

29. The method of claim 28 further comprises unlocking the connection and connection instance and floating the keep-alive message to another of the plurality of machines, the new machine receiving the keep-alive message locks the connection and connection instance and facilitates data transfer.

30. A method that facilitates transferring a message from a client to a database, comprising:

invoking an adapter coupled to the client;

providing a machine employing the adapter with a connection instance identification;

employing the connection instance identification to concurrently receive data and update the connection instance with at least a present state of data transfer; and

utilizing the information within the connection instance to provide for at least one of data transfer reliability, error recovery and dynamic load balancing.

31. The method of claim 30 further comprises populating the connection instance with at least one of the following:

a connection identity;

an adapter identity;

a client identity;

a data receiving condition, a data transfer time-out, and a database subscriber.

32. The method of claim 30, the connection identity is a keep-alive message.

33. A data packet transmitted between two or more computer components that facilitates message conveyance between a client and a machine employing an adapter suitable to communicate with the client, comprising:

a component that creates an instance associated with the connection between the client and the machine;

a component that utilizes the information within the instance to lock the connection and the instance;

a component that receives a message from the client and concurrently updates the instance with at least state information; and

a component that utilizes the information within the instance to provide for at least one of data transfer reliability, error recovery and dynamic load balancing.

34. A computer readable medium storing computer executable components to facilitate message conveyance between a client and an adapter, comprising:

a component that creates an connection instance for the connection between the client and the adapter;

a component that provides access to the connection instance to a machine employing the adapter, the machine locks the connection and the connection instance, receives messages from the client and concurrently updates message conveyance state information stored within the connection instance; and

a component that employs the connection instance to provide for at least one of data transfer reliability, error recovery and dynamic load balancing

35. A system that facilitates data transfer from a remote device to a database, comprising:

means for identifying a connection between the remote device and an adapter;

means for locking the connection between the remote device and the adapter;

means for receiving data from the remote device and storing the data in the database; and

means for floating the connection between a plurality of machines employing the adapter to provide for at least one of data transfer reliability, error recovery and dynamic load balancing.