METHODS OF FORWARDING/RECEIVING DATA PACKETS USING UNICAST AND/OR MULTICAST COMMUNICATIONS AND RELATED LOAD BALANCERS AND SERVERS

• US 20140372616A1
• Filed: 06/17/2013
• Published: 12/18/2014
• Est. Priority Date: 06/17/2013
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Arisoylu, Mustafa, Ganesh, Jayasenan Sundara, Anand, Prashant, Sawant, Nandan Mahadeo
• Application Number:
  US13/919,375
• Publication Number:
  US 20140372616A1
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer

Abstract

Data packets may be forwarded to servers identified by respective server IDs. A mapping table includes bucket IDs identifying respective buckets. The mapping table maps: a first bucket ID to a first server ID as a current server ID; a second bucket ID to a second server IDs as a current server ID; and the first bucket ID to a third server ID as an old server ID. A data packet of a data flow may be received, and a bucket ID may be computed for the data packet. Responsive to computing the first bucket ID as the bucket ID for the data flow and responsive to the mapping table mapping the first bucket ID to the to the first server ID as the current server ID and to the third server ID as the old server ID, the data packet may be transmitted to the first server and/or to the third server.

Claims

1. A method of forwarding data packets to a plurality of servers with each server being identified by a respective server identification (ID), the method comprising:

defining a mapping table including a plurality of bucket identifications (IDs) identifying a respective plurality of buckets, wherein the mapping table maps a first of the plurality of bucket IDs to a first of the server IDs for a first of the plurality of servers as a current server ID for the first bucket ID, wherein the mapping table maps a second of the plurality of bucket IDs to a second of the server IDs for a second of the plurality of servers as a current server ID for the second bucket ID, and wherein the mapping table maps the first bucket ID to a third of the plurality of server IDs for a third of the plurality of servers as an old server ID for the first bucket ID;

receiving a data packet of a data flow wherein the data packet includes information for the data flow;

computing a bucket ID for the data packet as a function of the information for the data flow, wherein the bucket ID for the data flow is computed as the first bucket ID; and

responsive to computing the first bucket ID as the bucket ID for the data flow and responsive to the mapping table mapping the first bucket ID to the to the first server ID as the current server ID and to the third server ID as the old server ID, transmitting the data packet to the first server and/or to the third server using the first server ID and/or using the third server ID from the mapping table.

2. The method of claim 1 wherein transmitting the data packet to the first server and/or to the third server comprises,

responsive to the mapping table mapping the first bucket ID to the first server ID as the current server ID and to the third server ID as the old server IDs and responsive to the data packet being an initial data packet for the data flow, transmitting the data packet as a unicast to the first server using the first server ID.

3. The method of claim 1 wherein transmitting the data packet to the first server and/or to the third server comprises,

responsive to the mapping table mapping the first bucket ID to the first server ID as the current server ID and to the third server ID as the old server IDs and responsive to the data packet being a non-initial data packet for the data flow, transmitting the data packet as a multicast to the first and third servers using the first and third server IDs.

4. The method of claim 1 wherein transmitting the first data packet to the first server and/or to the third server comprises,

responsive to mapping table mapping the first bucket ID to the first server ID as the current server ID and to the third server ID as the old server ID, transmitting the data packet as a multicast to the first and third servers using the first and third server IDs.

5. The method of claim 1 further comprising:

after mapping the first data packet using the mapping table, revising the mapping table to remove the mapping of the first bucket ID to the third server ID as an old server ID for the first bucket ID.

6. The method of claim 5 wherein the data packet is a first data packet and the data flow is a first data flow, the method further comprising:

after revising the mapping table, receiving a second data packet of a second data flow wherein the second data packet includes information for the second data flow;

computing a bucket ID for the second data packet as a function of the information for the second data flow, wherein the bucket ID for the second data flow is computed as the first bucket ID; and

responsive to computing the first bucket ID as the bucket ID for the second data flow and responsive to the mapping table mapping the first bucket ID to the to the first server ID as the current server ID, transmitting the second data packet as a unicast to the first server using the first server ID from the mapping table.

7. The method of claim 1 wherein computing the bucket ID for the data packet comprises performing a hash function on the information for the data flow.

8. The method of claim 7 wherein the information for the data flow includes a data flow identification (ID) for the data flow, and wherein performing the hash function comprises performing the hash function on the data flow ID.

9. The method of claim 1 wherein a number of the plurality of bucket IDs in the mapping table is greater than a number of the servers and server IDs, and wherein the mapping table provides a same server ID for more than one of the bucket IDs.

10. A load balancer configured to forward data packets to a plurality of servers with each server being identified by a respective server identification (ID), the load balancer comprising:

a network interface configured to receive data packets from an outside network;

a server interface configured to forward data packets to the servers;

memory configured to store a mapping table including a plurality of bucket identifications (IDs) identifying a respective plurality of buckets, wherein the mapping table maps a first of the plurality of bucket IDs to a first of the server IDs for a first of the plurality of servers as a current server ID for the first bucket ID, wherein the mapping table maps a second of the plurality of bucket IDs to a second of the server IDs for a second of the plurality of servers as a current server ID for the second bucket ID, and wherein the mapping table maps the first bucket ID to a third of the plurality of server IDs for a third of the plurality of servers as an old server ID for the first bucket ID; and

a processor coupled to the network interface, to the server interface, and to the memory, the processor being configured to,

receive a data packet of a data flow through the network interface wherein the data packet includes information for the data flow,

compute a bucket ID for the data packet as a function of the information for the data flow, wherein the bucket ID for the data flow is computed as the first bucket ID, and

transmit the data packet through the server interface to the first server and/or to the third server using the first server ID and/or using the third server ID from the mapping table responsive to computing the first bucket ID as the bucket ID for the data flow and responsive to the mapping table mapping the first bucket ID to the to the first server ID as the current server ID and to the third server ID as the old server ID.

11. A method of processing data packets at a server, the method comprising:

defining a server flow table for the server, the server flow table including data flow identifications for data flows being processed by the server;

receiving a data packet of a data flow at the server wherein the data packet includes information for the data flow;

responsive to the data packet being an initial data packet of the data flow for the server, adding a data flow identification of the data flow to the server flow table; and

responsive to the data packet being an initial data packet of the data flow for the server, processing the data packet at the server.

12. The method of claim 11 wherein the data packet includes information identifying the data packet as an initial data packet of the data flow, wherein adding the data flow identification comprises adding the data flow identification of the data flow to the server flow table responsive to the information identifying the data packet as the initial data packet of the data flow, and wherein processing the data packet at the server comprises processing the data packet at the server responsive to the information identifying the data packet as the initial data packet of the data flow.

13. The method of claim 12 wherein the data packet comprises a first data packet and the data flow comprises a first data flow, the method further comprising:

receiving a second data packet of a second data flow at the server wherein the second data packet includes information identifying the second data packet as a non-initial data packet of the second data flow; and

responsive to the information identifying the second data packet as a non-initial data packet of the second data flow and responsive to a data flow identification for the second data packet being included in the server flow table for the server, processing the second data packet at the server.

14. The method of claim 12 wherein the data packet comprises a first data packet and the data flow comprises a first data flow, the method further comprising:

receiving a second data packet of a second data flow at the server wherein the second data packet includes information identifying the second data packet as a non-initial data packet of the second data flow; and

responsive to the information identifying the second data packet as a non-initial data packet of the second data flow and responsive to a data flow identification for the second data packet being excluded from the server flow table for the server, dropping the second data packet at the server.

15. The method of claim 11 further comprising:

defining a list of bucket identifications (IDs) for buckets that map to the server;

wherein adding the data flow identification to the server flow table comprises adding the data flow identification to the server flow table responsive to the data packet being a multicast data packet addressed to the server and to another server and responsive to the data flow identification for the data packet mapping to a bucket ID included in the list of bucket IDs for buckets that map to the server, and

wherein processing the data packet comprises processing the data packet at the server responsive to the data packet being a multicast data packet addressed to the server and to another server and responsive to the data flow identification for the data packet mapping to a bucket ID included in the list of bucket IDs for buckets that map to the server.

16. The method of claim 11, wherein adding the data flow identification to the server flow table comprises adding the data flow identification to the server flow table responsive to the data packet being a unicast data packet addressed to the server and responsive to the data flow identification being excluded from the server flow table, and wherein processing the data packet comprises processing the data packet at the server table responsive to the data packet being a unicast data packet addressed to the server and responsive to the data flow identification being excluded from the server flow table.

17. The method of claim 16 further comprising:

defining a list of bucket identifications (IDs) for the server; and

responsive to the data packet being a unicast data packet addressed to the server and responsive to the data flow identification being excluded from the server flow table, computing a bucket ID for the data packet as a function of the information for the data flow.

18. The method of claim 11, wherein the data packet includes information identifying the data packet as an initial data packet of the data flow,

wherein adding the data flow identification to the server flow table comprises adding the data flow identification to the server flow table responsive to the data packet being a unicast data packet addressed to the server and responsive to the information identifying the data packet as the initial data packet of the data flow, and

wherein processing the data packet comprises processing the data packet at the server table responsive to the data packet being a unicast data packet addressed to the server and responsive to the information identifying the data packet as the initial data packet of the data flow.

19. The method of claim 18 further comprising:

defining a list of bucket identifications (IDs) for the server; and

responsive to the data packet being a unicast data packet addressed to the server and responsive to the information identifying the data packet as the initial data packet of the data flow, computing a bucket ID for the data packet as a function of the information for the data flow.

20. The method of claim 19 wherein the information for the data flow includes an identification of the data flow, and wherein computing the bucket ID comprises computing the bucket ID as a function of the identification of the data flow.

21. The method of claim 19 wherein the data packet is a first data packet and the data flow is a first data flow, the method further comprising:

receiving a second data packet of a second data flow at the server wherein the second data packet includes information for the second data flow;

responsive to the information for the data flow identifying the data packet as an initial data packet of the second data flow and responsive to the data packet being a multicast data packet addressed to the server and to another server, computing a bucket ID for the second data packet as a function of the information for the second data flow; and

responsive to the bucket ID for the second data packet being excluded from the list of bucket IDs for the server, dropping the data packet.

22. The method of claim 11 wherein the data packet is a first data packet and the data flow is a first data flow, the method further comprising:

receiving a second data packet of a second data flow at the server wherein the second data packet includes information for the second data flow; and

responsive to the information for the second data flow including a data flow identification matching a data flow identifications of the server flow table, processing the data packet at the server.

23. The method of claim 22 further comprising:

receiving a third data packet of a third data flow at the server wherein the third data packet includes information for the third data flow; and

responsive to the information identifying the third data packet as a non-initial data packet of the third data flow and responsive to the information for the third data flow including a data flow identification that does not match one of the data flow identifications of the server flow table, dropping the third data packet at the server.

24. A server configured to process data packets, the server comprising:

a load balancer interface configured to receive data packets from a load balancer;

a memory configured to store a server flow table for the server, the server flow table including data flow identifications for data flows being processed by the server; and

a processor coupled to the load balancer interface and to the memory, wherein the processor is configured to,

receive a data packet of a data flow through the load balancer interface, wherein the data packet includes information for the data flow,

add a data flow identification of the data flow to the server flow table in memory responsive to the data packet being an initial data packet of the data flow for the server, and

process the data packet responsive to the data packet being an initial data packet of the data flow for the server.