Application aware systems and methods to process user loadable network applications

• US 10,389,835 B2
• Filed: 01/10/2017
• Issued: 08/20/2019
• Est. Priority Date: 01/10/2017
• Status: Active Grant

• Current Assignee: A10 Networks Incorporated
• Original Assignee: A10 Networks Incorporated
• Inventors: Jalan, Rajkumar, Sampat, Rishi, Sankar, Swaminathan
• Primary Examiner(s): Sison, June Y
• Application Number:
  US15/403,109
• Publication Number:
  US 20180198879A1
• Time in Patent Office: 952 Days
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields

Abstract

Described herein are methods and systems for application aware fastpath processing over a data network. In some examples, application fastpath operates to facilitate application specific fastpath processing of data packets transferred between a client device and a server device over a network session of a data network.

Claims

1. A servicing node comprising:

a fastpath module for processing data packets, the fastpath module stored in memory at the servicing node and executed by at least one processor, wherein the fastpath module;

receives an application service request data packet from a client device, over a network session between the client device and the servicing node;

obtains one or more network addresses from the application service request data packet and matches the obtained one or more network addresses with a session table for the network session between the client device and the servicing node;

determines that the one or more network addresses match an ingress session of the session table, the session table storing an indication for processing application service request data packets associated with the ingress session using a network application residing at the servicing node, wherein the network application includes a user-loadable network application loaded into the servicing node by a user of the servicing node;

stores the application service request data packet into an ingress message;

based on the indication, sending the ingress message to the network application for processing; and

upon the processing, transmits the application service request data packet to a server using egress session information.

2. The servicing node of claim 1, wherein the servicing node is a server load balancer.

3. The servicing node of claim 1, wherein the servicing node is an application delivery controller.

4. The servicing node of claim 1, wherein the ingress message is an application layer message.

5. The servicing node of claim 1, wherein the fastpath module further:

processes the application service request data packet according to an application layer protocol used by the network application.

6. The servicing node of claim 5, wherein the application layer protocol is one of:

HTTP, SIP, FTP, secure HTTP, instant messaging protocol, file transfer protocol, streaming protocol, or real time streaming protocol.

7. The servicing node of claim 1, wherein the fastpath module is a high performance TCP stack.

8. The servicing node of claim 1, wherein the fastpath module

transmits the ingress message to the network application via fastpath processing.

9. The servicing node of claim 1, wherein the fastpath module further:

receives a response data packet from the server;

determines that the data packet is associated to the egress session;

processes the data packet according to egress session information; and

sends the processed data packet to the client device using ingress session information.

10. The servicing node of claim 9, wherein the egress session information and the ingress session information are stored in the session table.

11. The servicing node of claim 9, wherein the egress session and the ingress session are TCP sessions.

12. The servicing node of claim 9, wherein the egress session and the ingress session are HTTP sessions.

13. The servicing node of claim 9, wherein the egress session and the ingress session are SIP sessions.

14. A method for processing data packets via a fastpath module stored in memory at a servicing node and executed by at least one processor, the method comprising:

receiving an application service request data packet from a client device, over a network session between the client device and the servicing node;

obtaining one or more network addresses from the application service request data packet and matching the obtained one or more network addresses with a session table for the network session between the client device and the servicing node;

determining that the one or more network addresses match an ingress session of the session table, the session table storing an indication for processing application service request data packets associated with the ingress session using a network application residing at the servicing node, wherein the network application includes a user-loadable network application loaded to the servicing node by a user of the servicing node;

storing the application service request data packet into an ingress message;

based on the indication, sending the ingress message to the network application for processing; and

upon the processing, transmitting the application service request data packet to a server using egress session information.

15. The method of claim 14, wherein the servicing node is an application delivery controller.

16. The method of claim 14, wherein the ingress message is an application layer message.

17. The method of claim 14, further comprising:

processing the application service request data packet according to an application layer protocol used by the network application.

18. The method of claim 17, wherein the application layer protocol is one of:

HTTP, SIP, FTP, secure HTTP, instant messaging protocol, file transfer protocol, streaming protocol, or real time streaming protocol.

19. The method of claim 14,

wherein the ingress message is transmitted to the network application via fastpath processing.

20. The method of claim 14, further comprising:

receiving a response data packet from the server;

determining that the data packet is associated to the egress session;

processing the data packet according to egress session information; and

sending the processed data packet to the client device using ingress session information.