System and method to facilitate the assignment of service functions for service chains in a network environment

• US 9,825,769 B2
• Filed: 06/02/2015
• Issued: 11/21/2017
• Est. Priority Date: 05/20/2015
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Batz, Robert M., Campbell, Ian McDowell, Bosch, Hendrikus G. P.
• Primary Examiner(s): Wu, Jianye
• Application Number:
  US14/728,010
• Publication Number:
  US 20160344803A1
• Time in Patent Office: 903 Days
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 12/1407 Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 2101/668 Internet protocol [IP] address subnets
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/0897 by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 43/028 by filtering
• CPC Class Codes: H04L 61/25 of the same type
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04M 15/66 Policy and charging system
• CPC Class Codes: H04M 15/8044 Least cost routing
• CPC Class Codes: H04M 15/8214 Data or packet based

Abstract

A method is provided in one example embodiment and may include receiving a first Internet protocol (IP) flow for an IP session for a subscriber; selecting a first service function group from a plurality of service function groups to perform one or more services for the IP session for the subscriber, wherein each of the plurality of service function groups comprises a plurality of service function chain types and wherein each service function chain type comprises an ordered combination of one or more service functions; assigning the IP session for the subscriber to the first service function group; and forwarding the first IP flow for the IP session of the subscriber across a first service function chain type for the first service function group based, at least in part, on a service policy for the subscriber.

Claims

1. A method comprising:

instantiating a plurality of service function instances for each of one or more hosts, wherein each service function instance corresponds to a particular service function type;

grouping each of the plurality of service function instances into one or more service function groups, wherein at least one service function instance is a member of at least two service function groups established across one or more hosts;

establishing a service function path for each of a plurality of service function chain types associated with the one or more service function groups, wherein each service function chain type comprises an ordered combination of one or more of the service function instances within each service function group and wherein at least one service function chain type associated with at least one service function group can comprise a number of service function instances that is less than a total number of service function instances associated with the at least one service function group; and

maintaining loading information for each of the plurality of service function groups based, at least in part, on a number of subscriber Internet protocol (IP) flows assigned to each service function group.

2. The method of claim 1, wherein at least one service function instance is a member of only one service function group for a particular host.

3. The method of claim 1, wherein the loading information is maintained in a service function group load balancing table, which includes a load balancing metric for each of the one or more service function groups.

4. The method of claim 3, further comprising:

determining each of the plurality of service function groups is unavailable to support additional subscriber IP flows;

instantiating one or more new service function instances based, at least in part, on the determination;

grouping the one or more new service function instances into a new service function group; and

establishing a service function path for each of the plurality of service function chain types associated with new service function group.

5. The method of claim 4, further comprising:

adding the new service function group and a load balancing metric associated with the new service function group into the service function group load balancing table, wherein the load balancing metric indicates that the new service function group is available to support additional IP flows.

6. The method of claim 1, further comprising:

determining a failure of a particular service function instance of a particular service function group;

instantiating a new service function instance to replace the particular service function instance;

grouping the new service function instance into the particular service function group; and

establishing a new service function path for one or more service function chain types for the particular service function group.

7. The method of claim 1, further comprising:

determining a particular service function instance of a particular service function group is underutilized;

grouping the particular service function instance into a new service function group; and

adding the new service function group and a load balancing metric associated with the new service function group into a service function group load balancing table.

8. One or more non-transitory tangible media encoding logic that includes instructions for execution by a processor, wherein the execution causes the processor to perform operations, comprising:

instantiating a plurality of service function instances for each of one or more hosts, wherein each service function instance corresponds to a particular service function type;

grouping each of the plurality of service function instances into one or more service function groups, wherein at least one service function instance is a member of at least two service function groups established across one or more hosts;

establishing a service function path for each of a plurality of service function chain types associated with the one or more service function groups, wherein each service function chain type comprises an ordered combination of one or more of the service function instances within each service function group and wherein at least one service function chain type associated with at least one service function group can comprise a number of service function instances that is less than a total number of service function instances associated with the at least one service function group; and

maintaining loading information for each of the plurality of service function groups based, at least in part, on a number of subscriber Internet protocol (IP) flows assigned to each service function group.

9. The media of claim 8, wherein at least one service function instance is a member of only one service function group for a particular host.

10. The media of claim 8, wherein the loading information is maintained in a service function group load balancing table, which includes a load balancing metric for each of the one or more service function groups.

11. The media of claim 10, wherein the execution causes the processor to perform further operations, comprising:

determining each of the plurality of service function groups is unavailable to support additional subscriber IP flows;

instantiating one or more new service function instances based, at least in part, on the determination;

grouping the one or more new service function instances into a new service function group; and

establishing a service function path for each of the plurality of service function chain types associated with new service function group.

12. The media of claim 11, wherein the execution causes the processor to perform further operations, comprising:

adding the new service function group and a load balancing metric associated with the new service function group into the service function group load balancing table, wherein the load balancing metric indicates that the new service function group is available to support additional IP flows.

13. The media of claim 8, wherein the execution causes the processor to perform further operations, comprising:

determining a failure of a particular service function of a particular service function group;

instantiating a new service function to replace the particular service function;

grouping the new service function into the particular service function group; and

establishing a new service function path for one or more service function chain types for the particular service function group.

14. The media of claim 8, wherein the execution causes the processor to perform further operations, comprising:

determining a particular service function instance of a particular service function group is underutilized;

grouping the particular service function instance into a new service function group; and

adding the new service function group and a load balancing metric associated with the new service function group into a service function group load balancing table.

15. An apparatus comprising:

at one memory element for storing data; and

at least one processor for executing instructions associated with the data, wherein the executing causes the apparatus to perform operations, comprising;

instantiating a plurality of service function instances for each of one or more hosts, wherein each service function instance corresponds to a particular service function type;

grouping each of the plurality of service function instances into one or more service function groups, wherein at least one service function instance is a member of at least two service function groups established across one or more hosts;

establishing a service function path for each of a plurality of service function chain types associated with the one or more service function groups, wherein each service function chain type comprises an ordered combination of one or more of the service function instances within each service function group and wherein at least one service function chain type associated with at least one service function group can comprise a number of service function instances that is less than a total number of service function instances associated with the at least one service function group; and

maintaining loading information for each of the plurality of service function groups based, at least in part, on a number of subscriber Internet protocol (IP) flows assigned to each service function group.

16. The apparatus of claim 15, wherein the loading information is maintained in a service function group load balancing table, which includes a load balancing metric for each of the one or more service function groups.

17. The apparatus of claim 16, wherein the executing causes the apparatus to perform operations, comprising:

determining each of the plurality of service function groups is unavailable to support additional subscriber IP flows;

instantiating one or more new service function instances based, at least in part, on the determination;

grouping the one or more new service function instances into a new service function group; and

establishing a service function path for each of the plurality of service function chain types associated with new service function group.

18. The apparatus of claim 17, wherein the executing causes the apparatus to perform operations, comprising:

adding the new service function group and a load balancing metric associated with the new service function group into the service function group load balancing table, wherein the load balancing metric indicates that the new service function group is available to support additional IP flows.

19. The apparatus of claim 15, wherein the executing causes the apparatus to perform operations, comprising:

determining a failure of a particular service function instance of a particular service function group;

instantiating a new service function instance to replace the particular service function instance;

grouping the new service function instance into the particular service function group; and

establishing a new service function path for one or more service function chain types for the particular service function group.

20. The apparatus of claim 15, wherein the executing causes the apparatus to perform operations, comprising:

determining a particular service function instance of a particular service function group is underutilized;

grouping the particular service function instance into a new service function group; and

adding the new service function group and a load balancing metric associated with the new service function group into a service function group load balancing table.