Out-of-band data transmission

• US 5,867,650 A
• Filed: 07/10/1996
• Issued: 02/02/1999
• Est. Priority Date: 07/10/1996
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Osterman, Lawrence William
• Primary Examiner(s): Geckil, Mehmet B.
• Application Number:
  US08/679,632
• Time in Patent Office: 937 Days
• Field of Search: 395/200.6, 395/200.68, 395/200.69, 395/200.33, 395/200.31
• US Class Current: 709/203
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A computer-implemented method uses out-of-band data transmission to reduce overhead associated with data transmission between a client process and a server process in a computer system employing a request-response protocol. Initially, a data transmission connection is established between the client process and the server process using the request-response protocol. Thereafter, data is transmitted between the client process and the server process using the connection, and without using the request-response protocol to transmit the data.

Claims

1. In a distributed computing system which includes a plurality of client systems each running one or more client processes, and a plurality of server systems each running one or more server processes, and wherein each client system is connected either directly or logically to one or more said server systems, and wherein a client process communicates with at least one server process using remote procedure call (RPC) protocol, a method of permitting transmission of large amounts of data between the client process and the server process without using the RPC protocol to transmit the data, but while retaining the accuracy and security provided by the RPC protocol, the method comprising the steps of:

initiating a client process at a client system and allocating a reception object at the client system which is designated for receiving data that is required to be transmitted by one of the server processes to the initiated client process, said allocation occurring before the client process sends a request for said data to said one server process;

sending a secure RPC request from the initiated client process to said one server process for the data, said RPC request identifying and verifying the reception object so as to establish an out-of-band communication procedure for the data which will thereafter permit transmission from the server system to the identified reception object of the client system using a low level protocol instead of the RPC protocol, but thereby still maintaining security of the identified reception object and corresponding out-of-band transmission;

said one server process responding by using the RPC protocol to the secure RPC request from the initiated client process by connecting to the identified reception object and confirming to the initiated client process that the connection has been made; and

said server process thereafter transmitting the data to the identified reception object of the client system using the established out-of-band communication procedure.

2. The method of claim 1 further comprising the step of returning an error message from the server process to the client process if an error occurs during transmission of the data in response to the RPC request, so that transmission delays are avoided during said step of transmitting the data in the event of such an error.

3. The method of claim 1, wherein the step of transmitting data comprises:

having the client process send a read request to the server process;

having the server process write data to the reception object in response to the read request;

having the client process read data from the reception object; and

having the server process respond to the read request once the requested data has been written to the reception object.

4. The method of claim 3, wherein the read request and the response thereto are made using the request-response protocol.

5. The method of claim 1, wherein the reception object comprises a TCP/IP socket.

6. The method of claim 1, wherein the reception object comprises a shared memory region.

7. The method of claim 1, wherein the client process and the server process are located on a common computer.

8. The computer software of claim 7, wherein the instructions for causing the computer system to transmit data comprise:

instructions for having the client process send a read request to the server process;

instructions for having the server process write data to the reception object in response to the read request;

instructions for having the client process read data from the reception object; and

instructions for having the server process respond to the read request once the requested data has been written to the reception object.

9. The computer software of claim 8, wherein the read request and the response thereto are made using the request-response protocol.

10. In a distributed computing system which includes a plurality of client systems each running one or more client processes, and a plurality of server systems each running one or more server processes, and wherein each client system is connected either directly or logically to one or more said server systems, and wherein a client process communicates with at least one server process using remote procedure call (RPC) protocol, a computer program product for implementing, within the distributed system, a method of permitting transmission of large amounts of data between the client process and the server process without using the RPC protocol to transmit the data, but while retaining the accuracy and security provided by the RPC protocol, the computer program product comprising:

a computer readable medium for carrying program code means; and

wherein the program code means comprises computer readable instructions for implementing a method comprising the steps of;

Initiating a client process at a client system and allocating a reception object at the client system which is designated for receiving data that is required to be transmitted by one of the server processes to the initiated client process, said allocation occurring before the client process sends a request for said data to said one server process;

sending a secure RPC request from the initiated client process to said one server process for the data, said RPC request identifying and verifying the reception object so as to establish an out-of-band communication procedure for the data which will thereafter permit transmission from the server system to the identified reception object of the client system using a low level protocol instead of the RPC protocol, but thereby still maintaining security of the identified reception object and corresponding out-of-band transmission;

said one server process responding by using the RPC protocol to the secure RPC request from the initiated client process by connecting to the identified reception object and confirming to the initiated client process that the connection has been made; and

said server process thereafter transmitting the data to the identified reception object of the client system using the established out-of-band communication procedure.

11. The computer program product of claim 10 wherein said method further comprises the step of returning an error message from the server process to the client process if an error occurs during transmission of the data in response to the RPC request, so that transmission delays are avoided during said step of transmitting the data in the event of such an error.

12. The method of claim 10, wherein the reception object comprises a TCP/IP socket.

13. The computer software of claim 10, wherein the reception object comprises a shared memory region.

14. The computer software of claim 10, wherein the client process and the server process are located on a common computer.