Application protocol offloading

• US 20030154298A1
• Filed: 01/14/2003
• Published: 08/14/2003
• Est. Priority Date: 01/14/2002
• Status: Active Grant

• Current Assignee: Array Networks Incorporated (Hitachi, Ltd.)
• Original Assignee: Array Networks Incorporated (Hitachi, Ltd.)
• Inventors: Lu, Lawrence T.
• Granted Patent: US 7,149,808 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/2871 Implementation details of single intermediate entities
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• 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
• CPC Class Codes: H04L 69/12 Protocol engines
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

In a network communication system involving a client and a server, communications are separated and forwarded into multiple subsystems for processing independently and concurrently. A protocol offloading system for processing information transmitted between a client and a server is provided. The protocol offloading system includes a first subsystem for processing protocol information and a second subsystem, independent of the first subsystem, for processing the actual data.

Claims

1. A protocol offloading system for processing information transmitted between a client and a server, the information containing protocol information and actual data, the protocol offloading system comprising:

a first subsystem for processing the protocol information; and

a second subsystem, independent of the first subsystem, for processing the actual data.

2. The system of claim 1, wherein the first subsystem contains multiple protocol handlers each dedicated to a specific protocol.

3. The system of claim 2, further comprising a protocol event engine for receiving a request from a client and directing the request to an appropriate one of the multiple handlers.

4. The system of claim 3, wherein the protocol event engine forwards requests which cannot be mapped to an appropriate one of the multiple handlers directly to the server.

5. The system of claim 1, wherein the first and second subsystems are separate computers communicating on a bus or network.

6. The system of claim 1, wherein the protocol is HTTP.

7. The system of claim 1, wherein the protocol is selected from the group consisting of FTP, SMTP, XML.

8. A method for performing protocol offloading associated with communication of information between a client and a server, the information containing protocol information and actual data, the method comprising:

identifying the protocol information for processing in a first subsystem; and

processing the actual data in a second subsystem, independent of the first subsystem.

9. The method of claim 8, wherein the first subsystem is one of multiple protocol handlers each dedicated to a specific protocol.

10. The method of claim 9, further comprising receiving a request from a client and directing the request to an appropriate one of the multiple handlers.

11. The method of claim 10, further comprising forwarding requests which cannot be mapped to an appropriate one of the multiple handlers directly to the server.

12. The method of claim 8, wherein the first and second subsystems are separate computers communicating on a bus or network.

13. The method of claim 8, wherein the protocol is HTTP.

14. The method of claim 8, wherein the protocol is selected from the group consisting of FTP, SMTP, XML.