Message-based scalable data transport protocol

• US 20040267934A1
• Filed: 06/30/2003
• Published: 12/30/2004
• Est. Priority Date: 06/30/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Patiejunas, Kestutis
• Granted Patent: US 7,720,973 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests

Abstract

The invention deploys a message-based data transport platform, in which a communication engine controls the delivery of server or other backup data or other large quantity data to a remote site based on message objects as fundamental units. Data sessions from one or more servers or other data sources may be buffered over established pipes for delivery to a remote data host which likewise contains messaging control. Relatively large message units may wait for communication over the channel in a queue, and be released when prior messaging is complete. Completion port or other polling or other mechanisms may indicate that connections have become open for use. In embodiments the message objects may be signed, or encrypted to safeguard against alteration or unauthorized viewing. The communication engine may rely upon TCP or other underlying transport mechanisms to effect lower level transmission.

Claims

1. A method for initiating the transmission of data, comprising:

establishing a connection from at least one data source to a destination;

generating at least one session to transmit data via the connection from the at least one data source to the destination;

queuing a set of messages from the at least one session for transmission over the connection to the destination; and

transmitting messages from the queued set of messages based upon completion information.

2. A method according to claim 1, wherein the step of establishing a connection comprises a step of establishing a connection in a pipe.

3. A method according to claim 1, wherein the step of establishing a connection comprises a step of authenticating at least one of the at least one source and the destination.

4. A method according to claim 3, wherein the step of authenticating comprises a step of authenticating both the at least one source and the destination.

5. A method according to claim 1, wherein the step of generating at least one session comprises a step of invoking an application programming interface.

6. A method according to claim 5, wherein the step of invoking an application programming interface comprises a step of receiving a session acceptance from the destination.

7. A method according to claim 1, wherein the step of queuing a set of messages comprises a step of queuing the set of messages in at least one input/output buffer.

8. A method according to claim 1, wherein the message completion information comprises results from a completion port operation of at least one of sending or receiving.

9. A method according to claim 8, further comprising a step of throttling message traffic in the at least one input/output buffer when the completion port is in a non-drained state.

10. A method according to claim 1, wherein the step of transmitting comprises a step of asynchronously transmitting messages from the queued set of messages.

11. A method according to claim 1, wherein the step of transmitting comprises a step of transmitting encrypted messages from the queued set of messages.

12. A method according to claim 1, wherein the step of transmitting comprises a step of transmitting via a transport layer.

13. A method for receiving a transmission of data in a destination, comprising:

establishing a connection with at least one data source;

accepting at least one session from the least one data source to communicate data via the connection; and

receiving messages from the at least one data source in a destination input/output buffer.

14. A method according to claim 13, wherein the step of establishing a connection comprises a step of establishing a connection in a pipe.

15. A method according to claim 13, wherein the step of establishing a connection comprises a step of authenticating the at least one source.

16. A method according to claim 13, wherein further comprising a step of storing the messages in storage.

17. A method according to claim 16, wherein the stored messages comprise a data backup of the at least one data source.

18. A transmissible message, the transmissible message being generated according to a method of:

establishing a connection from at least one data source to a destination;

establishing at least one session to transmit data via the connection from the at least one data source to the destination;

queuing at least one message from the at least one session for transmission over the connection to the destination; and

regulating the communication of the at least one queued message based upon completion information.

19. A method according to claim 18, wherein the step of establishing a connection comprises a step of establishing a connection in a pipe.

20. A method according to claim 18, wherein the step of establishing a connection comprises a step of authenticating at least one of the at least one source and the destination.

21. A method according to claim 20, wherein the step of authenticating comprises a step of authenticating both the at least one source and the destination.

22. A method according to claim 18, wherein the step of generating at least one session comprises a step of invoking an application programming interface.

24. A method according to claim 18, wherein the step of queuing the at least one message comprises a step of queuing the at least one message in at least one input/output buffer.

25. A method according to claim 18, wherein the message completion information comprises results from a completion port operation of at least one of sending or receiving.

26. A method according to claim 18, wherein the at least one message comprises at least one encrypted message.

23. A method according to claim 23 wherein the step of invoking an application programming interface comprises a step of receiving a session acceptance from the destination.