Network content processor including packet engine

• US 20060242313A1
• Filed: 06/07/2006
• Published: 10/26/2006
• Est. Priority Date: 05/06/2002
• Status: Abandoned Application

• Current Assignee: Lewiz Communications
• Original Assignee: Lewiz Communications
• Inventors: Truong, Thanh, Tien, David, Le, Chinh H.
• Application Number:
  US11/449,058
• Publication Number:
  US 20060242313A1
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

Packets received over a network are routed using a packet engine of the invention based on information contained in layer 4 or above. The information for switching is contained in the header information of the packet. Based on this higher level information, the packet engine may drop the packet, redirect the packet, load balance the packet, perform bandwidth provisioning (e.g., limit the speed of a connection), or adjust quality of service (e.g., change priority or rearrange a queue of packets to be handled), or combinations of these.

Claims

1. A method of processing packets received over a network comprising:

receiving a data packet from a client into a content processor;

performing packet header extraction and checksum checking on the data packet;

updating a connection table with extracted header information generated from the packet header extraction;

checking a connection state between the content processor and a target server to determine that a connection with the target server can be established;

building a synchronize packet using information in the connection table;

sending the synchronize packet to the target server;

building a new data packet including the received data packet from the client and information from the connection table; and

forwarding the new data packet to the target server when the target server indicates the target server is ready to receive data,

wherein a plurality of new data packets are stored in the content processor until the target server is ready to receive data and a sufficient amount of data is received from the client, thereby freeing available server resources.

2. The method of claim 1 further comprising:

based on the extracted header information, determining whether the data packet is from a wireless client;

if the packet is from a wireless client, terminating any connection between the client and the target server until a sufficient amount of data is received from the wireless client.

3. The method of claim 2 further comprising:

switching the wireless client to a subsequent server that is faster than a non-wireless client.

4. The method of claim 1 further comprising changing a priority of the data packet in a queue of packets.

5. The method of claim 1 further comprising lowering a priority of the data packet.

6. The method of claim 1 further comprising increasing a priority of the data packet.

7. A network content processor device configured to process data packets, the device comprising:

a packet processor configured to receive data packets from a client, edit the data packets, and forward the data packets to a target server;

a policy-based classifier containing a policy database for classifying network traffic per flow; and

a protocol parser configured to receive information from the packet processor and to form a query to search in the policy database of the policy-based classifier,

wherein the data packets are stored in the packet processor until the target server is ready to receive the data packets and a sufficient amount of data is received from the client, thereby freeing available server resources.

8. The device of claim 7 wherein based on the policy database, the device is configured to determine whether the client is a wireless client,

wherein if the client is a wireless client, the device acts as a proxy to terminate any communication between the client and the server until a sufficient amount of data is received from the client, thereby minimizing communication between the wireless client and the server.

9. The device of claim 8 wherein the wireless client is switched to a subsequent server that is faster than a non-wireless client, the switching being based on the policy database.

10. The device of claim 8 wherein multiple protocols are supported.

11. The device of claim 10 wherein the multiple protocols comprise binary and/or text based protocols.

12. The device of claim 10 wherein the multiple protocols include TCP/IP and HTTP.