Systems and methods for handling a multi-connection protocol between a client and server traversing a multi-core system

• US 8,289,975 B2
• Filed: 06/22/2009
• Issued: 10/16/2012
• Est. Priority Date: 06/22/2009
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Suganthi, Josephine, Shetty, Anil
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): Hsiung, Hai-Chang
• Application Number:
  US12/489,286
• Publication Number:
  US 20100322252A1
• Time in Patent Office: 1,212 Days
• Field of Search: 370/395.5
• US Class Current: 370/395.53
• CPC Class Codes: H04L 61/2503 Translation of Internet protocol [IP] addresses
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 69/12 Protocol engines
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

The present application is directed towards systems and methods for handling a multi-connection protocol communication between a client and a server traversing a multi-core system. The multi-connection protocol comprises a first connection and a second connection, which may be used respectively for control communications and data communications. Because different cores in the multi-core system may handle the first connection and second connection, the present invention provides systems and methods for efficiently coordinating protocol management between a plurality of cores.

Claims

1. A method of handling a multi-connection protocol communication between a client and a server traversing a multi-core system, the multi-connection protocol comprising a

control connection and a data connection, the method comprising:

a) receiving, by a first packet processing engine of a first core of a multi-core system, a port command via a control connection from a client to a server to establish a data connection with the server via a multi-connection protocol, the port command comprising an internet protocol address of the client and a port number of the client;

b) determining, by the first packet processing engine based on the port command, a second core of the multi-core system to which a flow distributor will forward a data connection request from the server;

c) sending, by the first core, to the second core a first message comprising information on the port command;

d) establishing, by a second packet processing engine of the second core, a listening service on a mapped internet protocol address of and a mapped port number of the multi-core system;

e) sending, by the second core, to the first core a second message identifying the mapped internet protocol address and mapped port number;

f) modifying, by the first packet processing engine, the port command to identify the mapped internet protocol address of the multi-core system as the internet protocol address of the client and the mapped port number as the port number of the client, and

g) sending, by the second core upon closing of the data connection, to the first core a message indicating the data connection was closed.

2. The method of claim 1, wherein step (b) further comprises determining, by the first packet processing engine, the second core based on performing a hash of a 4-tuple of the data connection request to be sent by the server.

3. The method of claim 1, wherein step (b) further comprises determining, by the first packet processing engine, the second core based on the internet protocol address and the port number of the client and the server'"'"'s internet protocol address and port number.

4. The method of claim 1, wherein step (c) further comprises communicating by the first core to the second core via the first message information on the control connection.

5. The method of claim 1, wherein step (d) further comprises allocating, by the second core, the mapped port number of the multi-core system from a plurality of port numbers not in use by the multi-core system.

6. The method of claim 1, wherein step (d) further comprises allocating, by the second core the mapped internet protocol address of the multi-core system from a plurality of internet protocol addresses hosted by the multi-core system.

7. The method of claim 1, wherein step (e) further comprises sending, by the second core to the first core the second message indicating the listening service was established.

8. The method of claim 1, wherein step (f) further comprises forwarding, by the first packet processing engine, the modified port command to the server.

9. The method of claim 1, further comprising receiving, by the listening service of the second core, the data connection request from the server.

10. A system for handling a multi-connection protocol communication between a client and a server traversing a multi-core system, the multi-connection protocol comprising a control connection and a data connection, the system comprising:

a first packet processing engine executing on a first core of a multi-core system receiving a port command via a control connection from a client to a server to establish a data connection with the server via a multi-connection protocol, the port command comprising an internet protocol address of the client and a port number of the client, determining, based on the port command, a second core of the multi-core system to which a flow distributor will forward a data connection request from the server, the first core sending to the second core a first message comprising information on the port command; and

a second packet processing engine executing on the second core, establishing a listening service on a mapped internet protocol address of and a mapped port number of the multi-core system, the second core sending to the first core a second message identifying the mapped internet protocol address and mapped port number, wherein the first packet processing engine modifies the port command to identify the mapped internet protocol address of the multi-core system as the internet protocol address of the client and the mapped port number as the port number of the client, and the second core sends, upon closing of the data connection, to the first core a message indicating the data connection was closed.

11. The system of claim 10, wherein the first packet processing engine determines the second core based on performing a hash of a 4-tuple of the data connection request to be sent by the server.

12. The system of claim 10, wherein the first packet processing engine determines the second core based on the internet protocol address and the port number of the client and the server'"'"'s internet protocol address and port number.

13. The system of claim 10, wherein the first core communicates to the second core via the first message information on the control connection.

14. The system of claim 10, wherein the second core allocates the mapped port number of the multi-core system from a plurality of port numbers not in use by the multi-core system.

15. The system of claim 10, wherein the second core allocates the mapped internet protocol address of the multi-core system from a plurality of internet protocol addresses hosted by the multi-core system.

16. The system of claim 10, wherein the second core sends to the first core the second message indicating the listening service was established.

17. The system of claim 10, wherein the first packet processing engine forwards the modified port command to the server.

18. The method of claim 10, wherein the listening service of the second core receives the data connection request from the server.