This invention relates generally to optimization of network resources in a virtualized network.
Network Function Virtualization (NFV) is a concept that provides for abstraction of network resources, for example, implementing telecommunication and/or data network functionality, into logical platforms known as “virtual machines.” For example, network functions traditionally embodied in static network appliances can be abstracted into multiple, software-based virtual machines. Software-Defined Networking (SDN) is a related concept by which control and data planes are decoupled, and management and control of supported network devices is logically centralized into programmable, software-based platforms. Generally, therefore, NFV and SDN define virtualization technologies that enable centralized management and control of today's complex networks, and which promise greater flexibility and scalability than traditional networks. To that end, there is a continuing need to configure virtualized network resources in optimized ways to realize efficiencies of flexibility and scalability associated with certain network functions.
This need is addressed and a technical advance is achieved in the art by a method and apparatus for dynamic reconfiguration of resources in a virtualized network. In one example, this reconfiguration involves dynamic instantiation of new policy/rules in a virtual firewall appliance (e.g., SIP firewall), which may be in a pre-existing SIP firewall or in a new or different SIP firewall. In another example, it involves migration of policy/rules from a first virtualized SIP firewall to a second virtualized SIP firewall. More generally, the reconfiguration may be expressed in one example as dynamic instantiation of a new configuration in a virtual network function (VNF) appliance, such as a virtual machine (VM), which may be in a pre-existing or in a new or different VM. In another example, it involves migration of a configuration from a first to a second VM. The VNF appliance(s) may exhibit generally any virtualized network functionality (i.e., not limited to firewall or security functionality).
The foregoing and other advantages of the invention will become apparent upon reading the following detailed description and upon reference to the drawings in which:
In one example, the network 100 comprises an IP network based on the Session Initiation Protocol (SIP) call control protocol. For example, the network 100 may define the core portion of an IP Multimedia Subsystem (IMS) network, which is a SIP-based converged network (i.e., having mobile users as well as fixed-access users). Thus, in one example, the VMs 101, 103, 105 provide virtualized functionality that supports IMS services, such as may include without limitation, SIP-based voice-over-IP services. In such case, IMS users (not shown) communicate with one or more of the VMs to accomplish, without limitation, SIP registrations, SIP session requests, and user authentications to initiate voice-over-IP calls.
In one embodiment, VM 105 defines a virtualized SIP firewall, loosely defined as a computational resource that blocks attacks mounted through SIP messages. For example and without limitation, the VM 105 operating as a virtualized SIP firewall must deal with Distributed Denial of Service (DDoS) attacks, which attempt to overload the network with large numbers of illegitimate (“spoofed”) SIP calls so as to deny service to legitimate users. Accordingly, in one embodiment, the VM 105 may block certain senders or IP addresses that are suspected sources of DDoS attacks.
The VM 105 is deployed in a first instance as a pre-existing and pre-y) configured virtualized SIP firewall for the network 100. That is, it is a computational resource that addresses known threats (i.e., with known threat signatures), according to execution of pre-existing and pre-configured policies and/or rules. According to embodiments described herein, the flexibility of virtualization is used to dynamically instantiate a second instance of a virtualized SIP firewall when new or unknown threats are detected or suspected. For example, as will be described in greater detail hereinafter, the VM 105 may be dynamically adapted to execute newly defined or newly adapted policy/rules, thereby defining a second instance of virtualized SIP firewall, replacing or supplementing the functionality of the previously configured virtualized SIP firewall to address the newly identified threats. In another example, a second instance of virtualized SIP firewall may be realized in a different pre-existing resource or in a newly-created resource to execute new functionality (e.g., newly defined policy/rules) or to migrate certain functionality of the previously configured SIP firewall to address newly identified threats in potentially vulnerable parts of the network.
As shown, the virtualized network 100 includes an analytics engine 111 to monitor the network 100, and an autonomics module 113 operable to receive intelligence data from the analytics engine 111. The autonomics module 113 is operable to identify actions to be taken responsive to the intelligence information and to formulate instructions to an orchestration module 115 (hereinafter, “orchestrator”) to carry out the actions. The orchestrator 115 provides instructions via network virtualization and automation engine 117 to the VMM 109 to control the VMs 101, 103, 105 to carry out the instructions and to perform virtualized functions of the network 100.
The analytics engine 111 is operable to monitor and collect intelligence associated with the network 100 via methods of data analytics. In one embodiment, the analytics engine 111 detects attacks to the network 100 through use of anomaly detection algorithms (in one example, machine-learning-based anomaly detection algorithms) on real-time or stream-based data. The algorithms can be built on commercial or open-source technologies. Machine-learning algorithms can provide real-time information as to anomalies taking place in the network, and can detect new, unknown, or previously known threats. For example, in the instance of the network 100 defining a SIP-based network, such as an IMS network, the analytics engine 111 may execute machine-learning algorithm to detect DDoS attacks or suspected DDoS attacks from characteristics of SIP-based message traffic generated externally from user devices communicating via the network or attempting to gain access to the network, or from characteristics of SIP message traffic generated within the network 100. As will be appreciated, an attack can be detected using any number of suitable methods, either known or yet to be devised.
In one embodiment, responsive to detecting an attack or suspected attack, the analytics engine 111 communicates data representing intelligence information to the autonomics module 113. For example and without limitation, the analytics engine may detect and identify malicious IP addresses that are suspected sources of DDoS attacks and communicate to the autonomics module a continually-updated list of the malicious IP addresses that are (knowingly or unknowingly) participating in the attack. The analytics engine might further report the nature and/or severity of the attacks, the network resources or portions of the network that have been compromised or that are most vulnerable to the attacks, or the like.
The autonomics module 113 receives intelligence information from the analytics engine 111 and identifies actions, if any, that should be taken responsive to the received intelligence. In one embodiment, the autonomics module 113 identifies actions according to a configurable policy that maps certain intelligence to certain actions. For example, the autonomics module may be pre-configured with a policy to block malicious IP addresses identified by the analytics engine as suspected sources of DDoS attacks. Accordingly, in the instance that the autonomics module 113 receives information about malicious IP addresses from the analytics engine, the autonomics module may make a determination governed by the pre-configured policy to block the identified IP addresses for a period of time. Alternatively or additionally, the policy may dictate instantiation of new virtual resources or migration of certain network resources or functionality to other parts of the network.
Consistent with principles of Software-Defined Networking (SDN), the autonomics module 113 is generally defined as a controller, operating in a control plane, that makes decisions and formulates instructions based on a configurable policy, but which is decoupled from the data plane and does not itself control execution of the virtualized resources of the underlying network infrastructure. Rather, the autonomics module 113 communicates instructions to the orchestrator 115, which operates in the data plane, to control execution of underlying hardware resources that are necessary to realize virtualized network functions. Therefore, the orchestrator 115 is generally defined as a controller, operating in the data plane, to control execution of network hardware to realize virtualized network functions. Accordingly, responsive to receiving instructions from the autonomics module 113, the orchestrator 115 promulgates data representing information or instructions to automation engine 117, VMM 109 and to the relevant VMs 101, 103, 105 to coordinate execution of instruction(s) to control or change some aspect of the virtualized network 100.
As will be appreciated, the elements of
In the example of
In the example of
In the example of
As will be appreciated, principles of the invention are not limited to examples of virtual firewall appliance (e.g., SIP firewall) or other security appliances. It is contemplated that embodiments of the invention may be realized to dynamically instantiate new or different functionality in pre-existing resources other than security appliances, or to migrate or supplement certain functionality other than security functionality into new or different resources in different parts of the network. The generalized embodiments are shown in
In each of
In the example of
In the example of
In the example of
The term “dynamic reconfiguration,” and the terms “instantiation,” “instantiating” and other derivative terms as used herein in the context of dynamic instantiation of a virtual network function (VNF), which in one example comprises a SIP firewall, is generally defined as a change in configuration or implementation of a VNF that occurs substantially “automatically” (i.e., without human intervention) based on automated execution of instructions initiated from the orchestrator 115 responsive to instruction(s) from the autonomics module 113 and intelligence from the analytics engine 111. It is contemplated, without limitation, that dynamic instantiation of a VNF can occur substantially quickly (e.g., on the order of seconds). Suffice it to say that dynamic reconfiguration can occur much more rapidly than reconfiguration that involves human intervention to reprogram or upload new software programs, replace or add physical components, or the like.
Number | Date | Country | |
---|---|---|---|
62115479 | Feb 2015 | US |