Network service header metadata for load balancing

• US 9,660,909 B2
• Filed: 03/20/2015
• Issued: 05/23/2017
• Est. Priority Date: 12/11/2014
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Pignataro, Carlos M., Guichard, James N., Quinn, Paul, Ward, David D.
• Primary Examiner(s): Elallam, Ahmed
• Application Number:
  US14/664,629
• Publication Number:
  US 20160173373A1
• Time in Patent Office: 795 Days
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04W 72/52 based on load

Abstract

A method for load balancing based on metadata in a network service header. The method includes receiving a packet or frame of a traffic flow, wherein the packet or frame has a payload and the network service header including metadata and service path information for the traffic flow identifying the service path, and the metadata comprises classification information of the packet or frame, extracting, by a service header processor of the load balancer, the classification information of the metadata from the packet or frame, and applying, by a load balancing function of the load balancer, a load balancing policy on the packet or frame based on the classification information of the metadata.

Claims

1. A method for load balancing based on metadata in a network service header, the method comprising:

receiving, at a load balancer in a service path, a packet or frame of a traffic flow, wherein the packet or frame has a payload and the network service header including metadata and service path information for the traffic flow identifying the service path, the metadata comprises classification information of the packet or frame, and the classification information has application information associated with the traffic flow;

extracting, by a service header processor of the load balancer, the application formation;

receiving, at the load balancer, an encoding scheme of the application information; and

applying, by a load balancing function of the load balancer, a load balancing policy on the packet or frame based on the application information to distribute traffic flows across a plurality of servers.

2. The method of claim 1, wherein the network service header that includes the metadata and the service path information is a result of an initial classification of the packet or frame performed by an initial service classifier.

3. The method of claim 1, wherein the classification information of the packet or frame of the metadata originates from an orchestrator system external to a service path prescribed by the service path information.

4. The method of claim 1, wherein:

the classification information of the packet or frame of the metadata is a result of metadata augmentation by a service node upstream of the load balancer in the service path; and

the metadata augmentation by the service node upstream of the load balancer comprises performing a classification of the packet or frame which supplements an initial classification of the packet or frame and augmenting metadata in the network service header with further metadata from the classification.

5. The method of claim 1, wherein the load balancer is not capable of deducing the classification information of the packet or frame based on the packet or frame.

6. The method of claim 1, wherein applying the load balancing policy on the packet or frame does not include processing the payload of the packet or frame.

7. The method of claim 1, wherein applying the load balancing policy on the packet or frame does not include processing the layer 7 Hypertext Transfer Protocol header of the packet or frame.

8. The method of claim 1, wherein the application information comprises an encoded value which identifies an application with which the traffic flow is associated.

9. The method of claim 1, wherein the load balancer is a server load balancer or an application delivery controller in the service path, wherein the service path is prescribed by the service path information.

10. The method of claim 1, wherein the application information comprises one or more of the following:

information identifying the application type, application data, subscriber information, service level information, virtual private networks member ship information, and virtual routing and forwarding membership information.

11. The method of claim 1, wherein the encoding scheme is received via a control plane of the service path.

12. A load balancer in a service path for load balancing based on metadata in a network service header, the load balancer comprising:

at least one memory element having instructions stored thereon;

at least one processors coupled to the at least one memory element and configured to execute the instructions to cause the load balancer to;

receive a packet or frame of a traffic flow, wherein the packet or frame has a payload and the network service header including metadata and service path information for the traffic flow identifying the service path, the metadata comprises classification information of the packet or frame, and the classification information has application information associated with the traffic flow;

extract, by a service header processor of the load balancer, the application information;

receive an encoding scheme of the application information; and

apply, by a load balancing function of the load balancer, a load balancing policy on the packet or frame based on the application information to distribute traffic flows across a plurality of servers.

13. The load balancer of claim 12, wherein the network service header that includes the metadata and the service path information is a result of an initial classification of the packet or frame performed by an initial service classifier.

14. The load balancer of claim 12, wherein the classification information of the packet or frame of the metadata originates from an orchestrator system external to a service path prescribed by the service path information.

15. The load balancer of claim 12, wherein the classification information of the packet or frame of the metadata is a result of metadata augmentation by a service node upstream of the load balancer in the service path;

and

the metadata augmentation by the service node upstream of the load balancer comprises performing a classification of the packet or frame which supplements an initial classification of the packet or frame and augmenting metadata in the network service header with further metadata from the classification.

16. The load balancer of claim 12, wherein the load balancer is not capable of deducing the classification information of the packet or frame of the metadata from the packet or frame.

17. A computer-readable non-transitory medium comprising one or more instructions for load balancing based on metadata in a network service header, that when executed on a processor configure the processor to:

receive, at a load balancer in a service path, a packet or frame of a traffic flow, wherein the packet or frame has a payload and the network service header including metadata and service path information for the traffic flow identifying the service path, the metadata comprises classification information of the packet or frame, and the classification information has application information associated with the traffic flow;

extract, by a service header processor of the load balancer, the application information; and

apply, by a load balancing function of the load balancer, a load balancing policy on the packet or frame based on the application information to distribute traffic flows across a plurality of servers.

18. The computer-readable non-transitory medium of claim 17, wherein applying the load balancing policy on the packet or frame does not include processing the payload of the packet or frame.

19. The computer-readable non-transitory medium of claim 17, wherein applying the load balancing policy on the packet or frame does not include processing the layer 7 Hypertext Transfer Protocol header of the packet or frame.

20. The computer-readable non-transitory medium of claim 17, wherein the application information comprises an encoded value identifies an application with which the traffic flow is associated.