Scalability of providing packet flow management

• US 10,103,991 B2
• Filed: 12/17/2015
• Issued: 10/16/2018
• Est. Priority Date: 12/07/2006
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Agarwal, Kaitki, Ghai, Rajat
• Primary Examiner(s): Huynh, Khoa
• Application Number:
  US14/972,677
• Publication Number:
  US 20160112323A1
• Time in Patent Office: 1,034 Days
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/72 Routing based on the source address
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 45/7453 using hashing
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/2483 involving identification of individual flows
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/102 Gateways arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1046 Call controllers; Call servers
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: Y10S 707/912 Applications of a database
• CPC Class Codes: Y10S 707/913 Multimedia
• CPC Class Codes: Y10S 707/918 Location

Abstract

Systems and methods for managing packet flows in a communication network are provided. Packet information can be cached on different levels and used to avoid external queries. The cache information can also be correlated with other types of information, such as location information, to be able to serve that information quicker than if one or more external queries were to be made. A demux manager can provide routing and session setup, by routing packets that already have a session to the session manager and assigning packets to a session manager if they are not already assigned to a session. The tiered architecture also provides scalability to many users and minimizes delays even during high call volumes because the load can be distributed well across the gateway'"'"'s resources.

Claims

1. A method comprising:

receiving a plurality of packets at a gateway;

in response to a determination, by a network processing unit (NPU) of the gateway, that a first hash lookup, for a first packet of the plurality of packets, produces a hit in a hash list, forwarding the packet to a first process instance of one or more process instances of the gateway, the first process instance corresponding to the hit in the hash list, wherein the first process instance is to store call state data including information about the states of sessions handled by the first process instance;

in response to a determination, by the NPU of the gateway, that a second hash lookup, for a second packet of the plurality of packets, does not produce a hit in the hash list, forwarding the second packet to a demux manager of the gateway;

in response to a determination, by the demux manager, that a third hash lookup, for the second packet, does not produce a hit in a second hash list, determining to add a second process instance to handle a new packet flow associated with the second packet, the determination based at least on load information of the first process instance, wherein the second process instance is configured to store call state data including information about the states of sessions handled by the second process instance;

routing, by the first process instance, the first packet towards a destination address of the first packet; and

routing, by the second process instance, the second packet towards a destination address of the second packet.

2. The method of claim 1, further comprising sending from the first process instance a limited set of criteria to set up a flow in a network processing unit to forward packets that match the limited set of criteria.

3. The method of claim 1, wherein the hit is based on an originating subscriber address.

4. The method of claim 1, wherein the hit is based on a destination subscriber address.

5. The method of claim 1, wherein the hit is based on an originating subscriber address and a destination subscriber address.

6. The method of claim 1, wherein the first process instance comprises at least a portion of a call session control function (CSCF).

7. The method of claim 1, wherein each process instance comprises a Proxy call session control function (CSCF), an Interrogating CSCF, and a Serving CSCF.

8. The method of claim 1, further comprising selecting a process instance of the first or second process instances for a packet flow based on a load of one or more of the one or more process instances.

9. At least one non-transitory media comprising logic that when executed is operable to:

receive a plurality of packets at a gateway;

in response to a determination, by a network processing unit (NPU) of the gateway, that a first hash lookup, for a first packet of the plurality of packets, produces a hit in a hash list, forward the packet to a first process instance of one or more process instances of the gateway, the first process instance corresponding to the hit in the hash list, wherein the first process instance is to store call state data including information about the states of sessions handled by the first process instance;

in response to a determination, by the NPU of the gateway, that a second hash lookup, for a second packet of the plurality of packets, does not produce a hit in the hash list, forward the second packet to a demux manager of the gateway;

in response to a determination, by the demux manager, that a third hash lookup, for the second packet, does not produce a hit in a second hash list, determine to add a second process instance to handle a new packet flow associated with the second packet, the determination based at least on load information of the first process instance, wherein the second process instance is configured to store call state data including information about the state of sessions handled by the second process instance;

route, by the first process instance, the first packet towards a destination address of the first packet; and

route, by the second process instance, the second packet towards a destination address of the second packet.

10. The at least one media of claim 9, wherein the logic when executed is further operable to send from the first process instance a limited set of criteria to set up a flow in a network processing unit to forward packets that match the limited set of criteria.

11. The at least one media of claim 9, wherein the hit is based on an originating subscriber address.

12. The at least one media of claim 9, wherein the hit is based on a destination subscriber address.

13. The at least one media of claim 9, wherein the hit is based on an originating subscriber address and a destination subscriber address.

14. The at least one media of claim 9, wherein the first process instance comprises at least a portion of a call session control function (CSCF).

15. The at least one media of claim 9, wherein each process instance comprises a Proxy call session control function (CSCF), an Interrogating CSCF, and a Serving CSCF.

16. The at least one media of claim 9, wherein the logic when executed is further operable to select a process instance of the first or second process instances for a packet flow based on a load of one or more of the one or more process instances.

17. A gateway comprising:

at least one interface; and

at least one network processing unit (NPU) configured to;

receive a plurality of packets from the at least one interface;

in response to determining that a first hash lookup, for a first packet of the plurality of packets, produces a hit in a hash list, forward the packet to a first process instance of one or more process instances of the gateway, the first process instance corresponding to the hit in the hash list, wherein the first process instance is configured to store call state data including information about the states of sessions handled by the first process instance;

in response to determining that a second hash lookup, for a second packet of the plurality of packets, does not produce a hit in the hash list, forward the second packet to a demux manager;

wherein the demux manager is configured to, upon determining that a third hash lookup, for the second packet, does not produce a hit in a second hash list, determine to add a second process instance to handle a new packet flow associated with the second packet, the determination based at least on load information of the first process instance, wherein the second process instance is configured to store call state data including information about the states of sessions handled by the second process instance;

wherein the first process instance is configured to route the first packet towards a destination address of the first packet; and

wherein the second process instance is configured to route the second packet towards a destination address of the second packet.