Source: https://patents.google.com/patent/US9537775B2/en
Timestamp: 2019-04-22 15:37:58+00:00

Document:
Methods, systems, and computer readable media for managing Diameter overload information within a telecommunications network are disclosed. One embodiment of a system for implementing the subject matter described herein includes at a virtualization orchestrator (VO) having a hardware processor and within the telecommunications network, receiving overload information, determining a network virtualization operation to perform based on the received information, and performing the network virtualization operation.
The subject matter described herein relates to methods and systems for processing Diameter messages. More particularly, the subject matter described herein relates to methods, systems, and computer readable media for managing Diameter load and overload information within a telecommunications network.
Diameter is an authentication, authorization and accounting (AAA) protocol for computer networks, and is a successor to RADIUS. The Diameter base protocol is defined in International Engineering Task Force (IETF) request for comments (RFC) 6733 which is incorporated by reference herein in its entirety. Diameter messages use a per user framework and exist in the format of request-answer messages. Diameter answer messages travel back to the request source via the same path through which the request message was routed using hop-by-hop transport.
Diameter messages may be exchanged between Diameter nodes for performing various functions. For example, a mobility management entity (MME) and a home subscriber server (HSS) may interact for authentication, authorization, and/or accounting (AAA) purposes. The amount of Diameter messages exchanged between Diameter nodes may increase or decrease depending on various environmental and circumstantial conditions and scenarios. Overload can occur at a Diameter node when the amount of Diameter messages exchanged exceeds the processing capabilities of the node. When an overload has occurred, network resources such as processing and storage units may be allocated or relocated to accommodate the overload condition.
However, an overload condition may occur suddenly and/or unexpectedly due to unforeseeable circumstantial events. For example, a natural disaster such as an earth quake may occur without warning in a highly populated city such as Los Angeles or San Francisco. Naturally, cellular networks within these cities may suddenly be flooded with phone calls or text messages to family members, or pictures and videos to news agencies. This sudden onset of activity may overload networks or elements thereof, and causes the networks to get sluggish and possibly fail. Various network resources may be relocated manually to compensate the overload conditions, but such operations can be sometimes slow and redundant.
Accordingly, there exists a need for methods, systems, and computer readable media for managing Diameter load and overload information efficiently and quickly.
According to one aspect, the subject matter described herein may include a method for using overload information for managing network virtualization. The method may include at a virtualization orchestrator comprising a hardware processor and for managing virtual networks within a telecommunications network receiving overload information, determining a network virtualization operation to perform based on the received information, and performing the network virtualization operation.
According to another aspect, the subject matter described herein comprises a system for using overload information for managing network virtualization. The system may include a virtualization orchestrator for managing virtual networks within a telecommunications network. Furthermore, the virtualization orchestrator may include a network interface for receiving overload information, and a rules engine for determining a network virtualization operation based on the received information and for performing the network virtualization operation.
In context of telecommunications networks, the terms “load” and “overload” have somewhat overlapping meanings: for example, a node may be said to be “loaded” when its utilization is greater than 0% and less than an engineered capacity and “overloaded” when its utilization is greater than the engineered loading capacity. For example, a node that is part of a matched pair of nodes that provide the same function in a distributed manner may be considered “overloaded” if its utilization is greater than 50%, since the other 50% must be reserved for use in case the other node in the pair fails and causes the failing node's traffic to be handled by the remaining node. Similarly, if a node reports its utilization as being less than some overload threshold, such as message may be considered a “load indication”, but if the node reports its utilization as being greater than the threshold, such a message may be considered an “overload indication”. In other words, the difference between a “load message” and an “overload message” may be a matter of degree. For simplicity, the terms “load” and “overload” will be used synonymously herein unless explicitly stated otherwise. Thus, as used herein, the terms “load information” and “overload information” are synonymous and refer to information that indicates the load level, rate, throughput, or capacity at which a Diameter node or group of nodes are currently operating under.
FIG. 4 is a flow chart illustrating an exemplary method for using overload information for managing network virtualization according to an embodiment of the subject matter described herein.
In accordance with the subject matter disclosed herein, systems, methods, and computer readable media are provided for managing Diameter load and overload information within a telecommunications network.
For example in some embodiments, it may be desirable for a telecommunications network virtualization orchestrators to utilize Diameter overload information generated by various Diameter nodes for more efficient network resource allocation. Diameter overload information may be extracted by Diameter nodes from Diameter messages. The Diameter nodes may then forward the overload information to be further processed by a virtualization orchestrator. In other embodiments, Diameter overload information may be supplied by external data sources such as an external network. For example, an external data collection network and/or a cloud network may be connected to the telecommunications network and supplying Diameter overload information to the virtualization orchestrator via an interface module. The virtualization orchestrator may utilize the overload information to generate network virtualization operation commands to network virtualization modules within the telecommunications network. The network virtualization modules can function accordingly to add or remove network resources to accommodate overload occurrences or a reduction in network load.
FIG. 1 is a diagram illustrating an exemplary embodiment of a system for using overload information for managing network virtualization according to an embodiment of the subject matter described herein. Exemplary environment 100 may include one or more networks and may include one or more Diameter nodes, such as Diameter clients (DC) 102-106, a Diameter agent (DA) 108, Diameter servers (DS) 112-116, and a virtualization orchestrator 122 which may include a rules engine 120 and an events interface module 118.
Each of Diameter clients 102-106 may represent any suitable entity (e.g., a computing platform include at least one processor and memory) for requesting one or more services from Diameter servers 112-116. For example, Diameter client 102 may send a Diameter request message for requesting one or more services at an application hosted by Diameter server 112. Each of Diameter servers 112-116 may represent any suitable entity (e.g., a computing platform include at least one processor and memory) for providing or performing one or more services for Diameter clients 102-106. For example, Diameter server 112 may send a Diameter answer message (e.g. a Diameter response message) in response to receiving and processing a Diameter request message.
Exemplary Diameter clients 102-106 or Diameter servers 112-116 may include a mobility management entity (MME), a home subscriber server (HSS), an authentication, authorization, and accounting (AAA) server, a Bearer Binding and Event Reporting Function (BBERF), a serving gateway (SGW), a packet data network gateway (PDN GW), a charging data function (CDF), an online charging system, an offline charging system, a policy charging enforcement function (PCEF), a policy charging and rules function (PCRF), a subscriber profile repository (SPR), a Diameter agent, a network node, a policy engine, a policy server, an application function (AF), an application server, a Diameter signaling agent, a long term evolution (LTE) node, an Internet protocol (IP) multimedia subsystem (IMS) network node, a server, a correlation node, a node, a database, a signaling gateway, a gateway, a monitoring node, a Diameter message processor, a data collection platform, a multi-protocol signaling gateway, a multi-protocol signaling router, or a computing platform.
DA 108 may be any suitable entity for performing Diameter overload control and/or related functions described herein. For example, DA 108 may be implemented on a computing platform with one or more processors and one or more network interfaces for receiving or transmitting messages. Examples of DA 108 may include, but are not limited to, a DSR, a DRN, a Diameter routing agent, a Diameter relay agent, a Diameter redirect agent, a Diameter translation agent, or a Diameter proxy agent.
In some embodiments, DA 108 may include functionality for receiving, processing and/or routing various messages (e.g., protocol data units (PDUs)) and may include various communications interfaces for communication with Diameter nodes, e.g., 3rd Generation Partnership Project (3GPP) LTE communications interfaces and other (e.g., non-LTE) communications interfaces. In some embodiments, receiving, processing, and/or routing functionality may be included in one or more modules. For example, DA 108 may include or have access to one or more modules for receiving Diameter signaling messages associated with multiple different Diameter signaling interfaces, e.g., S9, S6a, S11, Cx, and Dx.
Furthermore, DA 108 may receive Diameter messages via other Diameter interfaces. For example, DA 108 may receive Diameter messages via an LTE interface, an IMS interface, an IETF specification interface, a 3GPP specification interface, a Third Generation Partnership Project 2 (3GPP2) specification interface, a European Telecommunications Standards Institute (ETSI) specification interface, an International Telecommunications Union (ITU) specification interface, a PacketCable specification interface, a MultiService Forum (MSF) specification interface, an Sh interface, a Dx interface, a Ro interface, a Rf interface, an Sp interface, a Gx interface, a Rx interface, a Gz interface, a Gy interface, a Gq interface, a Zh interface, a Dz interface, a Zn interface, a Ty interface, a Tx interface, a Dw interface, a Wa interface, a Wd interface, a Wx interface, a Wm interface, a Wg interface, a Pr interface, a Gr interface, a Gr+ interface, a Gi interface, a Wo interface, a Wf interface, a Re interface, an S6 interface, an S2 interface, an SW interface, an Sta interface, an S7 interface, an H2 interface, an E2 interface, an E4 interface, an E5 interface, a A3 interface, a A4 interface, a Rr interface, a Gq′ interface, a TC-6 interface, a TC-7 interface, a TC-8 interface, a TC-9 interface, a TC-10 interface, a TC-11 interface, a DB-0 interface, a DB-2 interface, a BI-1 interface, a LOC-1 interface, an Rw interface, a Pkt-mm-2 interface, a P-CSCF-PAM interface, a Pkt-laes-2 interface, an MM10 interface, an MZ interface, a Gmb interface, or a Zn′ interface.
In some embodiments, DA 108 may facilitate communication between Diameter clients 102-106 and Diameter servers 112-116. For example, Diameter client 102 may send a Diameter request message (e.g., a Diameter session establishment request message) to DA 108. The Diameter request message may require one or more services from Diameter servers 112. DA 108 may route, relay, and/or translate requests or responses between Diameter client 102 and a Diameter server 112. After receiving and processing the Diameter request message, Diameter server 112 may send a Diameter response message (e.g., a Diameter session establishment response message) to DA 108. The Diameter response message may be in response to a Diameter request message originated by Diameter client 102. DA 108 may provide the Diameter response message to Diameter client 102.
Furthermore, DA 108, or a module therein, may perform one or more functions prior to providing a Diameter message to another node. In some embodiments, the DA 108 may be configured to generate overload information from load information received from Diameter nodes. For example, load information may be stored in one or more attribute value pairs (AVPs) located in a payload portion of Diameter messages exchanged between multiple Diameter nodes. Load AVPs may contain any information for specifying load information or load metrics. Various algorithms may be used to generate load metrics, and some algorithms may generate load metrics that reflect utilization of resources. For example, load metrics may indicate a percentage of resources utilized or available at a Diameter node. In some embodiments, a load AVP may utilize an Unsigned32 data type format and may include a number between 0 and 232−1 (4,294,967,295) for representing load, where 0 is “completely unloaded” and 4,294,967,295 is “maximum capacity”.
The DA 108 may be configured to extract load information, such as the load AVP from the Diameter messages, and predict overload using the load information when load increases and/or spikes. Similarly, load information may also be examined to determine a rate of load increase, with a particular rate triggering some behavior. In some embodiments, overload conditions may be predicted in response to an increase in aggregate load up to and/or in excess of a predefined aggregate load. Signal processing can be applied to load information to detect complex patterns over time. In addition, the DA 108, or a module therein, may modify the Diameter message by inserting or including Diameter overload information or other related data in the modified Diameter message. For example, Diameter overload information may be stored in one or more AVPs located in a payload portion of the modified diameter message.
In some embodiments, DA 108 may direct the Diameter overload information to a cloud network virtualization orchestrator via any suitable mechanism, such as an events interface module. The exemplary mechanisms by which Diameter agent 108 communicates the Diameter overload information will be described in detail below with respect to FIG. 2.
While FIG. 1 depicts DA 108 communicating with (e.g., receiving Diameter messages from) various Diameter nodes, it will be appreciated that DA 108 may communicate with the nodes depicted and other nodes (not depicted) via additional and/or different interfaces. It will also be appreciated that DA 108 may include fewer, additional, or different modules and/or components.
In some embodiments, the Diameter agent 108 may direct the Diameter overload information to a virtualization orchestrator 122. For example, DA 108 may be connected to a rules engine 120 of a virtualization orchestrator 122 via interface modules, and a network message that includes Diameter overload information can be directed to the rules engine by the DA 108. In some embodiments, the DA 108 may be in communication with an events interface 118 module of the virtualization orchestrator 122. The events interface 118 may be configured to be a bi-directional interface module, supplying analytic data and network virtualization operation commands to the virtualization orchestrator 122, and direct messages such as network coordination commands back to the DA 108.
In some embodiments, the rules engine 120 may receive Diameter overload information from the DA 108 via the events interface module 118. The rules engine 120 may be connected to a rules database 132 which may stores a set of provision rules of the cloud network, a state database 124 which may monitor and store state information of the network, and a topology database 126 which may supply network topology data to the rules engine 120. In addition, the rules engine 120 may be connected to a Graphical User Interface (GUI) 130, which may be configured to supply network status to an end user.
In some embodiments, the rules engine 120 may be configured to process the received Diameter overload information. The rules engine 120 may apply network operation rules from the rules database 132, coupled with current network state data supplied by the state database 124 and status of the current network topology extracted from the topology database 126 to generate network virtualization operation commands to the telecommunications network. For example, when the Diameter overload information indicates that one or more Diameter nodes need a reduction in the number of service requests, the rules engine 120 may generate request commands to the telecommunications network to deploy additional resources to mitigate the effects of the overload. Similarly, the rules engine 120 may generate commands to direct the telecommunications network to make reduction in the deployed resources when the Diameter overload information indicates abatement in the network overload, or a reduction in load.
In some embodiments, the generated commands can be directed to various applications and products within the telecommunications network via an application coordination interface module. For example, the application coordination interface module may be a policy charging and rules function (PCRF) 128 module configured to interact with applications and products within the telecommunications network. The PCRF 128 plugin may be used to control topology and provisioning configuration to the various resources within the telecommunications network. In addition, the PCRF 128 plugin may be configured to be a bi-directional interface module and supply network performance indicators such as processor and disk usage or network usages back to the rules engine 120.
In some embodiments, the rules engine 120 may direct network virtualization operation commands to an orchestration coordination interface module 130. The orchestration coordination interface 130 may be a bi-directional interface module configured to interact with a second orchestrator managing a larger telecommunications network. The rules engine 120 may direct commands and service requests to the second orchestrator via the orchestration coordination interface 130 and receive back AVI type status information about the larger telecommunications network.
In some embodiments, load and overload information may be directed to the virtualization orchestrator 122 from Diameter nodes 136 such as policy and charging rules function (PCRF) plugin modules, cloud management plugins, and/or information collection modules. It should be noted that the diagram as shown in FIG. 1 is provided to explain the subject matter and not as a limitation.
FIG. 2 is a message flow diagram illustrating exemplary messaging for collecting and directing Diameter overload information according to an embodiment of the subject matter described herein. At line 200, DA 108 receives network load information from DCs 102, 104, 106 and DSs 112, 114, 116. For example, the DA 108 may extract AVP type load information from service messages exchanged between the DCs 102, 104, 106 and the DSs 112, 114, 116.
At line 202, the DA 108 may process the received load information and generate a modified Diameter message which includes Diameter overload information to the rules engine 120 of the virtualization orchestrator 122. In some embodiments, the DA 108 may extract load information and perform a prediction on overload conditions using the load information. For example, the DA 108 may apply an algorithm adapted to aggregate load information received from multiple nodes, or apply an algorithm adapted to average load information for one specific node of a group of nodes, depending on the need of the network.
At line 204, the rules engine 120 may process the received Diameter overload information by applying network operation rules from the rules database 132, coupled with current network state data supplied by the state database 124 and status of the current network topology extracted from the topology database 126, and generate network virtualization operation commands to the telecommunications network. In some embodiments, when network overload has occurred or is imminent, the rules engine can generate service requests to network virtualization modules to reallocate resources to mitigate the effects of overload conditions. Network virtualization modules may bring additional resources online in response to the overload conditions. For example, more gateways, switches, registration nodes may be allocated as needed.
FIG. 3 is a flow chart illustrating an exemplary process, generally designated 300, for managing network load and overload information according to an embodiment of the subject matter described herein. Referring to FIG. 3, in block 302, network load and overload information can be received by a Diameter agent 108. For example, DA 108 may facilitate communication between Diameter clines 102-106 and Diameter servers 112-116, DA 108 may route, relay, and/or translate Diameter messages such as service requests or responses between the DCs 102-106 and the DSs 112-116. Furthermore, Diameter messages received by the DA 108 may contain network load information in forms of AVPs located in the payload portions. These AVPs may contain any information for specifying load information or load metrics. Various algorithms may be used to generate load metrics, and some algorithms may generate load metrics that reflect utilization of resources. For example, load metrics may indicate a percentage of resources utilized or available at a Diameter node. In some embodiments, a load AVP may utilize an Unsigned32 data type format and may include a number between 0 and 232−1 (4,294,967,295) for representing load, where 0 is “completely unloaded” and 4,294,967,295 is “maximum capacity”.
In block 304, the DA 108 can generate overload information from the received load information. For example, load information may be used by the DA 108 to predict overload when load increases and/or spikes, or to determine a rate of load increase when a particular rate triggers some behavior. In some embodiments, signal processing can be applied to load information to detect complex patterns over time and overload conditions may be predicted. The DA 108 may then modify Diameter message by inserting or including Diameter overload information or other related data.
In block 306, overload information may be directed by the DA 108 to a rules engine 120 of a virtualization orchestrator 122. For example, DA 108 may direct a modified diameter message to the rules engine 120, and the message may contain Diameter overload information such as a load AVP in its payload portion. In some embodiments, the modified Diameter message can be transmitted via an interface module. For example, and events interface 118 may be utilized to communicate the message from the DA 108 to the rules engine 120.
In block 308, the rules engine 120 may generate network virtualization operation commands based on the received overload information. In some embodiments, the rules engine 120 may be connected to a rules database 132 which may be configured to provide network provision rules, a state database 124 which monitors and stores network state information, and a topology database 126 which may supply network topology data to the rules engine 120. Network virtualization operation commands can be generated by the rules engine 120 based on the received overload information, coupled with current network topology and state. For example, service requests can be generated to various applications and blocks within the telecommunications network to reallocate resources to mitigate the effects of overload conditions.
In block 310, the rules engine 120 may communicate the virtualization operation commands to network virtualization modules within the telecommunications network. In some embodiments, virtualization operation commands may be directed by the rules engine 120 to a resource manager module, and network topology can be modified accordingly to mitigate the effects of overload conditions. For example, additional gateways and switches can be deployed in response to an imminent network overload, or resources can be reduced when there is an indication in the reduction of network load.
FIG. 4 is a flow chart illustrating an exemplary method, generally designated 400, for using overload information for managing network virtualization according to an embodiment of the subject matter described herein. Referring to FIG. 4, in block 402, overload information may be received by the virtualization orchestrator 122. For example, overload information may be directed by the DA 108 to a rules engine 120 of the virtualization orchestrator 122.
In block 404, the rules engine 120 may determine a network virtualization operation to perform based on the received information. In some embodiments, the rules engine 120 may be connected to a rules database 132 which may be configured to provide network provision rules, a state database 124 which monitors and stores network state information, and a topology database 126 which may supply network topology data to the rules engine 120. Network virtualization operation commands can be generated by the rules engine 120 based on the received overload control information, coupled with current network topology and state information. For example, service requests can be generated for various applications and blocks within the telecommunication network to reallocate resources to mitigate the effects of overload conditions.
In block 406, the determined network operation may be performed by the virtualization orchestrator 122. For example, the rules engine 120 may communicate the virtualization operation commands to network virtualization modules within the telecommunication network. In some embodiments, virtualization operation commands may be directed by the rules engine 120 to a resource manager module, and network topology can be modified accordingly to mitigate the effects of overload conditions. For example, additional gateways and switches can be deployed in response to an imminent network overload, or resources can be reduced when there is an indication in the reduction of network load.
performing the network virtualization operation to direct the telecommunications network to deploy additional resources to mitigate a Diameter overload indicated by the Diameter overload information by deploying, in response to the Diameter overload indicated by the Diameter overload information, one or more additional virtual gateways or one or more additional virtual switches or both in the telecommunications network using one or more network virtualization modules.
2. The method of claim 1 wherein receiving Diameter overload information comprises receiving network load and overload information from a Diameter agent for facilitating communication between a plurality of Diameter clients and a plurality of Diameter servers.
3. The method of claim 2 wherein receiving Diameter overload information comprises receiving information directly from at least one of: a policy and charging rules function (PCRF) plugin module, a cloud management plugin, or an information collection module.
4. The method of claim 1 wherein receiving Diameter overload information comprises receiving information including an attribute value pair (AVP) or a Diameter message.
5. The method of claim 1 wherein determining a network virtualization operation to perform comprises using a state database for maintaining network state information.
6. The method of claim 1 wherein determining a network virtualization operation to perform comprises using information collected from within a telecommunications network.
7. The method of claim 6 wherein using information collected within the telecommunications network comprises using network performance indicators transmitted via a PCRF plugin and wherein performing the network virtualization operation to direct the telecommunications network to deploy additional resources comprises directing commands to the PCRF plugin, which is configured to control topology and provisioning of configuration within the telecommunications network.
8. The method of claim 1 wherein determining a network virtualization operation to perform comprises using information received from an entity external to the telecommunications network.
wherein determining the network virtualization operation to perform comprises using the rules engine for analyzing the received Diameter overload information and status of a current network topology of the telecommunications network and identifying the network virtualization operation to be performed based on the Diameter overload information and the status of the current network topology.
10. The system of claim 9 wherein the rules engine performs the network virtualization operation via a network virtualization module.
11. The system of claim 9 wherein the virtualization orchestrator receives the Diameter overload information from a Diameter agent for facilitating communication between a plurality of Diameter clients and a plurality of Diameter servers.
12. The system of claim 9 wherein the Diameter load information comprises information including an attribute value pair (AVP).
13. The system of claim 9 wherein the received Diameter load information comprises a Diameter message.
14. The system of claim 9 wherein the virtualization orchestrator further comprises at least one of: a rules database for providing network virtualization operation rules; a state database for maintaining network state information; and a topology database for maintaining network topology information.
15. The system of claim 9 wherein the rules engine is configured to determine a network virtualization operation using information received from an entity external to the network.
16. The system of claim wherein the rules engine is configured to determine a network virtualization operation using information collected from within the telecommunications network.
17. The system of claim 16 wherein the information collected from within the telecommunications network includes information collected from a PCRF plugin for directing network performance indicators, and wherein performing the network virtualization operation comprises directing commands to the PCRF plugin, which is configured to control topology and provisioning of configuration within the telecommunications network.
18. The system of claim 9 wherein the network virtualization operation comprises one of: assigning at least one additional network resource to a network component, and removing at least one network resource from a network component.
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study on Diameter overload control mechanisms (Release 12)" 3GPP TR 29.809 V0.3.0, pp. 1-51 (Jun. 2013).
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 11)," 3GPP TS 23,203, V11.8.0 pp. 1-179 (Dec. 2012).
"Network Function Virtualization (NFV) Management and Orchestration," ETSI, Group Specification, GS NFV-MAN 001 V0.0.11, pp. 1-74 (Oct. 18, 2013).
"Software-Defined Networking: The New Norm for Networks," ONF White Paper, Open Networking Foundation, pp. 1-12 (Apr. 13, 2012).
"Split Architecture for Large Scale Wide Area Networks," SPARC ICT-258457 Deliverable D3.3, pp. 1-129 (Dec. 1, 2011).
Advisory Action Before the Filing of an Appeal Brief for U.S. Appl. No. 14/166,772 (Jan. 11, 2016).
Advisory Action for U.S. Appl. No. 13/863,351 (Nov. 25, 2015).
Applicant-Initiated Interview Summary for U.S. Appl. No. 13/956,304 (Feb. 1, 2016).
Applicant-Initiated Interview Summary for U.S. Appl. No. 14/092,898 (Jan. 14, 2016).
Applicant-Initiated Interview Summary for U.S. Appl. No. 14/166,772 (Dec. 22, 2015).
Applicant-Initiated Interview Summary for U.S. Appl. No. 14/166,790 (Apr. 14, 2016).
Applicant-Initiated Interview Summary for U.S. Appl. No. 14/182,864 (Dec. 16, 2015).
Applicant-Initiated Interview Summary for U.S. Appl. No. 14/313,610 (Apr. 26, 2016).
Bhardwaj, "Roaming Hubbing & LTE," GSMA London, pp. 1-11 (May 19, 2009).
Chapman et al., "Software architecture definition for on-demand cloud provisioning," Cluster Computing, vol. 15, No. 2, pp. 79-100 Feb. 27, 2011).
Commonly-assigned, co-pending International Application No. PCT/US15/12250 for "Methods, Systems, and Computer Readable Media for a Cloud-Based Virtualization Orchestrator," (Unpublished, filed Jan. 21, 2015).
Commonly-assigned, co-pending U.S. Appl. No. 14/166,790 for "Methods, Systems, and Computer Readable Media for a Cloud-Based Virtualization Orchestrator," (Unpublished, filed Jan. 28, 2014).
Commonly-assigned, co-pending U.S. Appl. No. 14/692,710 for "Methods, Systems, and Computer Readable Media for Multi-Layer Orchestration in Software Defined Networks (SDNs)," (Unpublished, filed Apr. 21, 2015).
Commonly-assigned, co-pending U.S. Appl. No. 14/720,412 for "Methods, Systems, and Computer Readable Media for Short and Long Term Policy and Charging Rules Function (PCRF) Load Balancing," (Unpublished, filed May 22, 2015).
Communication of European publication number and information on the application of Article 67(3) EPC for European Application No. 13776083.1 (Jan. 21, 2015).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742921.7 (Sep. 12, 2012).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 14710682.7 (Nov. 25, 2015).
Communication of European publication Number and information on the application of Article 67(3) EPC for European Patent Application No. 14755210.3 (Jul. 6, 2016).
Dörnemann et al., "On-Demand Resource Provisioning for BPEL Workflows Using Amazon's Elastic Compute Cloud," 9th IEEE/ACM International Symposium on Cluster Computing and the Grid, pp. 140-147 (May 18, 2009).
Extended European Search Report for European Application No. 11742921.7 (Dec. 14, 2015).
Extended European Search Report for European Application No. 13776083.1 (Dec. 14, 2015).
Fajardo et al., "Diameter Base Protocol," RFC 6733, pp. 1-6 (Oct. 2012).
Final Office Action for U.S. Appl. No. 12/425,998 (Jun. 8, 2011).
Final Office Action for U.S. Appl. No. 13/572,156 (Dec. 29, 2014).
Final Office Action for U.S. Appl. No. 13/863,351 (Sep. 11, 2015).
Final Office Action for U.S. Appl. No. 13/956,304 (Nov. 3, 2015).
Final Office Action for U.S. Appl. No. 13/956,307 (Nov. 5, 2015).
Final Office Action for U.S. Appl. No. 14/086,950 (Jul. 1, 2016).
Final Office Action for U.S. Appl. No. 14/166,722 (Oct. 7, 2015).
First Office Action for Chinese Application No. 201180008578.6 (May 8, 2014).
Interview Summary for U.S. Appl. No. 12/425,998 (Mar. 1, 2011).
Interview Summary for U.S. Appl. No. 12/425,998 (Sep. 14, 2011).
Interview Summary for U.S. Appl. No. 13/026,144 (Mar. 4, 2013).
Jiao et al., "The Diameter Capabilities Update Application," RFC 6737, pp. 1-6 (Oct. 2012).
Kuthan et al., "Denial of Service Attacks Targeting a SIP VoIP Infrastructure: Attack Scenarios and Prevention mechanisms", IEEE Networks Magazine, vol. 20, No. 5 (Sep. 2006).
Letter regarding Notice Before Examination for Israel Patent Application No. 221425 (Jan. 11, 2015).
Letter Regarding Notice of Allowance for Israel Patent Application No. 2214525 (Jul. 10, 2016).
Letter regarding Notice of Grant for Chinese Patent Application No. 201180008578.6 (Jun. 4, 2015).
Letter regarding Office Action for Israel Patent Application No. 221425 (Apr. 20, 2016).
Letter regarding Office Action for Israel Patent Application No. 221425 (May 31, 2015).
Non-Final Office Action for U.S. Appl. No. 12/425,998 (Nov. 29, 2010).
Non-Final Office Action for U.S. Appl. No. 13/863,351 (Mar. 17, 2016).
Non-Final Office Action for U.S. Appl. No. 13/863,351 (Mar. 27, 2015).
Non-Final Office Action for U.S. Appl. No. 13/956,300 (Apr. 8, 2015).
Non-Final Office Action for U.S. Appl. No. 13/956,304 (May 4, 2015).
Non-Final Office Action for U.S. Appl. No. 13/956,307 (Apr. 23, 2015).
Non-Final Office Action for U.S. Appl. No. 14/086,950 (Dec. 4, 2015).
Non-Final Office Action for U.S. Appl. No. 14/092,898 (Oct. 8, 2015).
Non-Final Office Action for U.S. Appl. No. 14/166,772 (Mar. 27, 2015).
Non-Final Office Action for U.S. Appl. No. 14/166,772 (May 5, 2016).
Non-Final Office Action for U.S. Appl. No. 14/166,790 (Feb. 2, 2016).
Non-Final Office Action for U.S. Appl. No. 14/182,864 (Sep. 23, 2015).
Non-Final Office Action for U.S. Appl. No. 14/313,610 (Jan. 11, 2016).
Notice of Allowance and Fee(s) Due & Examiner-Initiated Interview Summary for U.S. Appl. No. 13/956,300 (Oct. 23, 2015).
Notice of Allowance and Fee(s) Due and Examiner-Initiated Interview Summary for U.S. Appl. No. 13/572,156 (Apr. 6, 2015).
Notice of Allowance and Fee(s) Due and Examiner-Initiated Interview Summary for U.S. Appl. No. 13/956,307 (Feb. 12, 2016).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/026,144 (May 1, 2013).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/956,304 (Mar. 16, 2016).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 14/182,800 (Nov. 10, 2015).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 14/182,864 (Feb. 17, 2016).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 14/313,610 (May 20, 2016).
Notification of Transmittal of the International Search Report and the Written Opinion for the International Searching Authority, or the Declaration for International Application No. PCT/US2014/048651 (Nov. 17, 2014).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, of the Declaration for International Application No. PCT/US2014/066469 (Feb. 20, 2015).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024642 (Oct. 28, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2013/036664 (Jul. 2, 2013).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2014/016853 (Jun. 6, 2014).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2014/016860 (Jun. 4, 2014).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2014/048644 (Oct. 17, 2014).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2014/066240 (May 13, 2015).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for PCT International Application No. PCT/US2015/012250 (Mar. 31, 2015).
Second Office Action for Chinese Patent Application No. 201180008578.6 (Dec. 9, 2014).
Supplemental Notice of Allowability for U.S. Appl. No. 13/956,300 (Dec. 1, 2015).
Supplemental Notice of Allowability for U.S. Appl. No. 14/182,800 (Dec. 1, 2015).
Wendong et al., "Autonomicity Design in OpenFlow Based Software Defined Networking," GC'12 Workshop: The 4th IEEE International Workshop on Management of Emerging Networks and Services, pp. 818-823 (Dec. 3 2012).

References: Application No. 13776083
 Application No. 11742921
 Application No. 14710682
 Application No. 14755210
 Application No. 11742921
 Application No. 13776083
 Application No. 201180008578
 Application No. 221425
 Application No. 2214525
 Application No. 201180008578
 Application No. 221425
 Application No. 221425
 Application No. 201180008578