System and method for message-based scalable data transport

• US 20040267935A1
• 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,693,998 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 69/10 Streamlined, light-weight or high-speed protocols, e.g. express transfer protocol [XTP] or byte stream
• CPC Class Codes: H04L 69/12 Protocol engines
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

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 system for managing the transmission of data, comprising:

an input interface to receive a plurality of message objects generated from data from at least one data source;

a transport interface to a transport layer; and

a communication engine, communicating with the input interface and the transport interface, the communication engine buffering the message objects for transmission to the remote destination via the transport layer.

2. A system according to claim 1, wherein the at least one data source comprises a network.

3. A system according to claim 2, wherein the network comprises at least one server.

4. A system according to claim 3, wherein the network comprises a local area network.

5. A system according to claim 1, wherein the transport layer comprises a Transport Control Protocol layer.

6. A system according to claim 1, wherein the remote destination comprises a storage host.

7. A system according to claim 1, wherein the communication engine queues the message objects in at least one output buffer.

8. A system according to claim 1, wherein the at least one data source comprises a plurality of data sources.

9. A system according to claim 8, wherein each of the data sources is associated with at least one corresponding session.

10. A system according to claim 9, wherein the communication engine binds at least one session to at least one of a plurality of connections to the remote destination.

11. A system according to claim 10, wherein the communication engine binds more than one session to at least one of the connections to the remote destination.

12. A system according to claim 1, wherein the buffering of the message objects is performed at least in part according to a state of a message completion port.

13. A method for managing the transmission of data, comprising:

receiving data from at least one data source;

transforming the data to a plurality of message objects; and

buffering the message objects for transmission to a remote destination via a transport layer.

14. A method according to claim 13, wherein the at least one data source comprises a network.

15. A method according to claim 14, wherein the network comprises at least one server.

16. A method according to claim 15, wherein the network comprises a local area network.

17. A method according to claim 13, wherein the transport layer comprises a Transport Control Protocol layer.

18. A method according to claim 13, wherein the remote destination comprises a storage host.

19. A method according to claim 13, wherein the step of buffering the message objects comprises a step of queuing the message objects in at least one output buffer.

20. A method according to claim 13, wherein the at least one data source comprises a plurality of data sources.

21. A method according to claim 20, wherein each of the data sources is associated with at least one corresponding session.

22. A method according to claim 21, further comprising a step of binding at least one session to at least one of a plurality of connections to the remote destination.

23. A method according to claim 22, wherein the step of binding comprises a step of binding more than one session to at least one of the connections to the remote destination.

24. A method according to claim 13, wherein the step of buffering the message objects is performed at least in part according to a state of a message completion port.

25. A database, the database receiving data via a method comprising:

receiving data from at least one data source;

transforming the data to a plurality of message objects; and

buffering the message objects for transmission to the database via a transport layer.

26. A database according to claim 25, wherein the at least one data source comprises a network.

27. A database according to claim 26, wherein the network comprises at least one server.

28. A database according to claim 27, wherein the network comprises a local area network.

29. A database according to claim 25, wherein the transport layer comprises a Transport Control Protocol layer.

30. A database according to claim 25, wherein the database comprises a storage host.

31. A database according to claim 25, wherein the step of buffering the message objects comprises a step of queuing the message objects in at least one output buffer.

32. A database according to claim 25, wherein the at least one data source comprises a plurality of data sources.

36. A database according to claim 25, wherein the step of buffering the message objects is performed at least in part according to a state of a message completion port.

33. A database according to claim 33, wherein each of the data sources is associated with at least one corresponding session.

34. A database according to claim 33, wherein the method further comprises a step of binding at least one session to at least one of a plurality of connections to the remote destination.

35. A database according to claim 34, wherein the step of binding comprises a step of binding more than one session to at least one of the connections to the remote destination.

37. A message object, the message object being generated according to a method of:

receiving data from at least one data source; and

transforming the data to a plurality of message objects in a communication engine; and

buffering at least one of the message objects for transmission to a remote destination via a transport layer.

38. A message object according to claim 37, wherein the at least one data source comprises a network.

39. A message object according to claim 38, wherein the network comprises at least one server.

40. A message object according to claim 39, wherein the network comprises a local area network.

41. A message object according to claim 37, wherein the transport layer comprises a Transport Control Protocol layer.

42. A message object according to claim 37, wherein the remote destination comprises a storage host.

43. A message object according to claim 37, wherein the step of buffering the at least one message object comprises a step of queuing the at least one message object in at least one output buffer.

44. A message object according to claim 37, wherein the at least one data source comprises a plurality of data sources.

45. A message object according to claim 44, wherein each of the data sources is associated with at least one corresponding session.

46. A message object according to claim 45, wherein the method further comprises a step of binding at least one session to at least one of a plurality of connections to the remote destination.

47. A message object according to claim 46, wherein the step of binding comprises a step of binding more than one session to at least one of the connections to the remote destination.

48. A message object according to claim 37, wherein the step of buffering the at least one message object is performed at least in part according to a state of a message completion port.