CN106162507A - A kind of virtualize the flexible management method of network function and device - Google Patents

A kind of virtualize the flexible management method of network function and device Download PDF

Info

Publication number
CN106162507A
CN106162507A CN201510158884.8A CN201510158884A CN106162507A CN 106162507 A CN106162507 A CN 106162507A CN 201510158884 A CN201510158884 A CN 201510158884A CN 106162507 A CN106162507 A CN 106162507A
Authority
CN
China
Prior art keywords
vnf
vnf instance
scaling
instance
deployment specification
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201510158884.8A
Other languages
Chinese (zh)
Inventor
祝伟宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201510158884.8A priority Critical patent/CN106162507A/en
Priority to PCT/CN2015/092444 priority patent/WO2016155291A1/en
Publication of CN106162507A publication Critical patent/CN106162507A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses and a kind of virtualize the flexible management method of network function and device, including: according to the parameter of virtualization network function VNF telescoping instruction, determine VNF example flexible after ability to be arrived, wherein, the parameter of VNF telescoping instruction include the mark of VNF example to be stretched and described VNF example flexible after ability parameter to be arrived；According to the ability that the VNF example determined is to be arrived after flexible, determine the deployment specification that VNF example should stretch；According to the deployment specification determined, VNF example is carried out scaling operation.The present invention specify which kind of parameter to carry out VNF scaling operation coordination by when different managing device initiation VNF stretches, and then avoids the flexible conflict of VNF.

Description

Management method and device for virtualized network function expansion
Technical Field
The present invention relates to the field of management of wireless communication systems, and in particular, to a method and an apparatus for managing flexible functions of a virtualized network.
Background
In the field of Management of wireless communication systems, an interface between a Network Management System (NMS) and an Element Management System (EMS) is called an north interface (Itf-N). The EMS mainly completes an Element Management Layer (EML) function in an International Telecommunication Union (ITU) Telecommunication Management Network (TMN), that is, a management function of one or more mobile communication devices, and generally, the EMS between different device providers cannot be commonly used. The NMS mainly performs the Network Management Layer (NML) functions in the ITU TMN, and is responsible for the management of all network elements within a managed network. In the case where a plurality of device providers exist in a managed network (called a subnet), the purpose of managing the entire subnet can be achieved by respective EMS management.
At present, in order to improve the flexibility of a communication Network and reduce the management cost, an operator initiates and proposes a Network Function Virtualization (NFV) concept, and in the case of using an NFV technology, an original physical Network element device is replaced by a Virtualized Network Function (VNF) so that the Network Function is decoupled from specific hardware. As shown in fig. 1, the VNF is isolated from the underlying Network Function Virtualization Infrastructure (NFVI). For management of the VNF, conventional maintenance management functions are performed on the VNF through the EMS, and the lifecycle management functions of the VNF are performed through a VNF manager (VNFM). The underlying NFVI is managed by a Virtual Infrastructure Manager (VIM). Specific network traffic is typically accomplished through one or more VNFs. The management of network traffic is performed by an NFV orchestrator (NFVO). After network function virtualization is realized, when a network service instance is to be established from an application level, a VNF instance required by a network service needs to be generated first, and then one or more corresponding VNF instances form a network service instance, so that the network service is provided through the network service instance. One benefit after virtualization of network functions is: with the change of the network use condition, the resources used by the VNFs forming the network service can be dynamically adjusted, that is, the VNFs are scaled, so as to improve the utilization rate of the resources and achieve the purpose of energy saving.
At present, there is a preliminary study on how to scale (including expansion and contraction) the VNF, and an overall flow of scaling the VNF is given. Meanwhile, it is also proposed that the expansion and contraction of the VNF can be initiated by the EMS or the VNFM. However, the current research has not yet clarified how the EMS and the VNFM should coordinate when they initiate VNF scaling simultaneously (or at a short time interval) to avoid VNF scaling conflicts, and it has not yet clarified what parameters should be provided when the EMS initiates VNF scaling to coordinate with the VNFM to avoid VNF scaling conflicts.
Disclosure of Invention
In order to solve the above problems, the present invention provides a method and an apparatus for managing scaling of a virtualized network function, which can specify parameters through which VNF scaling operation coordination is performed when different management apparatuses initiate VNF scaling, thereby avoiding VNF scaling conflicts.
In order to achieve the above object, the present invention provides a method for managing scaling of a virtualized network function, comprising: determining the capability of a VNF instance to be reached after the VNF instance is stretched according to the parameter of a virtual network function VNF stretching instruction, wherein the parameter of the VNF stretching instruction comprises the identification of the VNF instance to be stretched and the capability parameter of the VNF instance to be reached after the VNF instance is stretched; determining a deployment specification to which the VNF instance is to be stretched according to the determined capability of the VNF instance to be reached after the VNF instance is stretched; and performing scaling operation on the VNF instance according to the determined deployment specification.
Further, after determining the deployment specification to which the VNF instance should scale, the management method further includes: and when the fact that the VNF instance has the scaling operation with the scaling target being the deployment specification is not checked to be in progress or is ready to be started, scaling operation is carried out on the VNF instance according to the determined deployment specification.
Further, when there are two or more VNF scaling instructions for the same VNF instance, the management method further includes: and determining parameters of the VNF scaling instruction of the VNF instance according to a preset scaling priority.
Further, the management method further comprises: presetting a VNF deployment specification definition in a VNFD (virtual network function descriptor) corresponding to a VNF instance;
the determining a deployment specification to which the VNF instance should scale comprises: and correspondingly searching a VNF deployment specification definition in a VNFD corresponding to the VNF instance according to the determined capability of the VNF instance to be reached after the VNF instance is stretched, and determining a deployment specification to which the VNF instance should be stretched.
Further, the scaling the VNF instance comprises: and according to the determined deployment specification, determining the quantity of resources required by the VNF instance after scaling, executing the operation of changing the resources of the VNF instance, and completing the scaling of the VNF instance.
Further, the performing the operation of changing the resource of the VNF instance comprises:
sending a request for approving the VNF scaling to a network function virtualization orchestrator NFVO; the NFVO checks whether the existing resources can meet the applied VNF scaling from a Virtual Infrastructure Manager (VIM); the VIM returns the checking and resource booking results to the NFVO; if the existing resources meet the requirements and the reservation is successful, the NFVO returns a response message for approving the VNF expansion;
after receiving a response message for approving the extension of the VNF, requesting to allocate corresponding resources to the VIM; and after the VIM allocates the corresponding resources, returning a confirmation message.
Further, the expression manner of the capability parameter to be reached after the VNF instance is scaled includes:
specifying capabilities that the VNF instance can provide after scaling; or,
the capacity of the VNF instance after scaling is specified as a percentage of the existing capacity.
Further, the VNF scaling instruction is initiated by a VNFM, an element management system EMS, an operation support system OSS, a service support system BSS, or a network management system NMS.
The invention also provides a management device for the extension and contraction of the virtual network function, which comprises the following components: the capability determining module is used for determining the capability to be reached after the VNF instances are stretched according to the parameters of the VNF stretching instruction, wherein the parameters of the VNF stretching instruction comprise the identification of the VNF instances to be stretched and the capability parameters to be reached after the VNF instances are stretched; the deployment specification determining module is used for determining deployment specifications to which the VNF instances are required to be stretched according to the determined capability of the VNF instances to be reached after stretching; and the processing module is used for performing telescopic operation on the VNF instance according to the determined deployment specification.
Further, the management apparatus further includes: a checking module, configured to check whether a scaling operation targeted for the deployment specification is already ongoing or is ready to be started by the VNF instance.
Further, the management apparatus further includes: the parameter determination module is configured to determine, when two or more VNF scaling instructions for the same VNF instance exist, a parameter of the VNF scaling instruction for the VNF instance according to a preset scaling priority.
Further, the management apparatus further includes: the setting module is used for presetting a VNF deployment specification definition in the VNFD corresponding to the VNF instance;
the deployment specification determining module is specifically configured to: and correspondingly searching a VNF deployment specification definition in a VNFD corresponding to the VNF instance according to the determined capability of the VNF instance to be reached after the VNF instance is stretched, and determining a deployment specification to which the VNF instance should be stretched.
Further, the processing module is specifically configured to: and according to the determined deployment specification, determining the quantity of resources required by the VNF instance after scaling, executing the operation of changing the resources of the VNF instance, and completing the scaling of the VNF instance.
Further, the expression manner of the capability parameter to be reached after the VNF instance is scaled includes:
specifying capabilities that the VNF instance can provide after scaling; or,
the capacity of the VNF instance after scaling is specified as a percentage of the existing capacity.
In the management scheme of the invention, the capability of the VNF instances to be reached after the VNF instances are stretched is determined according to the parameters of the VNF stretching instruction, wherein the parameters of the VNF stretching instruction comprise the identification of the VNF instances to be stretched and the capability parameters of the VNF instances to be reached after the VNF instances are stretched; determining a deployment specification to which the VNF instance is to be stretched according to the determined capability of the VNF instance to be reached after the VNF instance is stretched; and performing scaling operation on the VNF instance according to the determined deployment specification. The method and the device have the advantages that the capability parameters which are provided by the management device and are to be reached after the VNF is stretched when the VNF stretching instruction is initiated are determined, technical realization guarantee is provided for VNF stretching operation coordination, and VNF stretching conflict is avoided.
In addition, in the preferred embodiment of the present invention, after determining the deployment specification to which the VNF instance should be scaled according to the parameter of the VNF scaling instruction, when it is not checked that the scaling operation whose scaling target is the deployment specification is in progress or is ready to be started, the scaling operation is performed on the VNF instance according to the determined deployment specification. Or when two or more than two VNF scaling instructions for the same VNF instance exist, parameters of the VNF scaling instructions for the VNF instance are determined according to preset scaling priority, then deployment specifications to which the VNF instance should be scaled are determined according to the parameters of the VNF scaling instructions, and scaling operation is performed on the VNF instance according to the determined deployment specifications. Therefore, the purpose of coordinating the VNF scaling operation between different management devices (such as EMS and VNFM) is achieved, and VNF scaling conflict is avoided.
Drawings
FIG. 1 is an architecture diagram of prior art network function virtualization;
FIG. 2 is a flowchart illustrating a method for managing scaling of virtual network functions according to a preferred embodiment of the present invention;
fig. 3 is a flowchart of a management method for scaling of virtualized network functions according to an embodiment of the present invention;
fig. 4 is a flowchart of a management method for scaling the virtualized network function according to a second embodiment of the present invention;
fig. 5 is a flowchart of a management method for scaling the virtualized network function according to a third embodiment of the present invention;
fig. 6 is a flowchart of a management method for scaling the virtualized network function according to a fourth embodiment of the present invention.
Detailed Description
The preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, and it should be understood that the preferred embodiments described below are only for the purpose of illustrating and explaining the present invention, and are not to be construed as limiting the present invention.
Fig. 2 is a flowchart of a management method for scaling of virtualized network functions according to a preferred embodiment of the present invention. As shown in fig. 2, the method for managing scaling of the virtualized network function according to the preferred embodiment of the present invention includes:
step 11: and determining the capability of the VNF instance to be reached after the VNF instance is scaled according to the parameters of the VNF scaling instruction, wherein the parameters of the VNF scaling instruction comprise the identification of the VNF instance to be scaled and the capability parameter of the VNF instance to be reached after the VNF instance is scaled.
In this step, the expression manner of the capability parameter to be reached after the VNF instance is scaled includes:
specifying capabilities that the VNF instance can provide after scaling; or,
the capacity of the VNF instance after scaling is specified as a percentage of the existing capacity.
In this step, the VNF scaling command is initiated by a Virtualized Network Function Manager (VNFM), an Element Management System (EMS), an Operation Support System (OSS), a service support system (BSS), or a Network Management System (NMS). The EMS sends the VNF scaling instruction to the VNFM, which may be initiated manually or automatically by a function module located in the EMS, which is not limited in the present invention. When an OSS/BSS/NMS initiates a VNF telescopic instruction, the OSS/BSS/NMS firstly sends the instruction to an EMS, and the EMS forwards the instruction to a VNFM; or, the OSS/BSS/NMS sends the instruction to the NFVO first, and the NFVO forwards the instruction to the VNFM. When the OSS/BSS/NMS initiates the VNF scaling instruction, the OSS/BSS/NMS sends the VNF scaling instruction to the VNFM, which may be initiated manually or automatically by a function module located in the OSS/BSS/NMS, which is not limited in the present invention.
In this regard, the scaling of the VNF instance mentioned in the preferred embodiment of the present invention includes scale out or scale up and scale in or scale down.
Wherein, the dilatation includes two kinds of condition:
extension (scale out): when the VNF is a VDU that can be composed of multiple Virtualization Deployment Units (VDUs), adding VDU instances that compose the VNF instances to increase the capability of the VNF instances;
scale up (scale up): that is, the configuration of a Virtual Machine (VM) running a VNF instance is increased, such as adding a CPU, a memory, a network port, and the like, to increase the capability of the VNF instance;
similarly, shrinkage includes two cases:
shrinkage (scale in): namely, when the VNF can be composed of multiple VDUs, the VDU instances composing the VNF instance are reduced to reduce the capability of the VNF instance;
scale down: i.e. reducing the configuration of the Virtual Machine (VM) running the VNF instance, such as reducing CPU, memory, network ports, etc., to reduce the capacity of the VNF instance.
Step 12: and determining the deployment specification to which the VNF instance is to be stretched according to the determined capability to be reached after the VNF instance is stretched.
The method also comprises the following steps: a VNF deployment specification definition in a Virtualized Network Function Descriptor (VNFD) corresponding to a VNF instance is preset. The method comprises the following specific steps: and correspondingly searching the VNF deployment specification definition in the VNFD corresponding to the VNF instance according to the determined capability of the VNF instance to be reached after the VNF instance is stretched, and determining the deployment specification to which the VNF instance should be stretched.
Among them, the Virtualized Network Function Descriptor (VNFD) includes the following attributes related to the present invention:
monitoring _ parameter, which describes which parameters the VNF type will monitor, one or more of the parameters may be used to determine the deployment specification of the VNF type and also indicate the capabilities that the VNF type can provide, and examples of the parameters include but are not limited to: number of Calls Per Second (CPS), flow per second (flowper second), number of subscribers (number-of-subscribers), etc.;
the VNF deployment specification (deployment specification) is used to describe how many levels of capabilities the VNF type can provide, and the VNF deployment specification uses one or more of the above monitoring parameters as its deployment specification key indicators (flag _ key) to represent different deployment specifications, for example, when the number of calls per second is used as a key indicator, different values of the number of calls per second can be used to represent different deployment specifications of the VNF, for example, the deployment specification can be represented as 1 ten thousand calls per second, 5 ten thousand calls per second, 10 ten thousand calls per second, and the like.
Step 13: and performing scaling operation on the VNF instance according to the determined deployment specification.
The method comprises the following specific steps: and according to the determined deployment specification, determining the quantity of resources required by the VNF instance after the VNF instance is stretched, executing the operation of changing the resources of the VNF instance, and completing the stretching of the VNF instance.
Wherein the performing the operation of changing the resource of the VNF instance comprises:
sending a request to approve a VNF scaling to a Network Function Virtualization Orchestrator (NFVO); the NFVO checks from the Virtual Infrastructure Manager (VIM) whether the existing resources can meet the VNF scaling of the application; the VIM returns the checking and resource booking results to the NFVO; if the existing resources meet the requirements and the reservation is successful, the NFVO returns a response message for approving the VNF expansion;
after receiving a response message for approving the extension of the VNF, requesting to allocate corresponding resources to the VIM; and after the VIM allocates the corresponding resources, returning a confirmation message.
In one embodiment, after step 12, the method further comprises: and when the fact that the VNF instance has the scaling operation with the scaling target of the deployment specification is in progress or is ready to be started is not checked, scaling operation is conducted on the VNF instance according to the determined deployment specification.
In another embodiment, when there are two or more VNF scaling instructions for the same VNF instance, the method further comprises: and determining parameters of the VNF scaling instruction of the VNF instance according to a preset scaling priority.
The present invention will be described in detail with reference to specific examples.
Example one
Fig. 3 is a flowchart of a management method for scaling a virtualized network function according to an embodiment of the present invention. As shown in fig. 3, the steps of the first embodiment are described in detail:
step 100: manually or automatically deciding at the EMS that VNF scaling is to be initiated;
step 101: the EMS sends a VNF scaling instruction to the VNFM, wherein parameters of the VNF scaling instruction comprise an identifier of a VNF instance to be scaled and a capability parameter to be reached after the VNF instance is scaled;
step 102: the VNFM determines the capability of the VNF instance to be reached after the VNF instance is stretched according to the received parameter of the VNF stretching instruction;
step 103: the VNFM correspondingly searches a VNF deployment specification definition in a VNFD corresponding to the VNF instance according to the capability to be reached after the VNF instance is stretched, and determines the deployment specification to which the VNF instance should be stretched;
specifically, the step is to correspondingly search for a VNF deployment specification definition in the VNFD corresponding to the VNF instance according to a value of a parameter "capability to be reached after the VNF is scaled up and down", for example, the VNF deployment specification definition in the VNFD corresponding to the VNF instance is 3K, and obtain a minimum specification that can meet the capability requirement, for example, the capabilities that can be provided by the deployment specifications supported by the VNF in the VNFD corresponding to the VNF instance are CPS of 1K, 5K, and 10K, respectively, and the deployment specification determined here is a specification corresponding to CPS of 5K;
step 104: the VNFM performs telescopic operation on the VNF instance according to the determined deployment specification;
step 105: the VNFM informs the EMS that the scaling operation of the above-described VNF instance is completed.
Wherein, the step 104 specifically comprises the following steps:
step 1041: the VNFM sends a request for approving VNF scaling to the NFVO;
step 1042: the NFVO checks whether the existing resources can meet the applied VNF expansion from the VIM, and if the existing resources can meet the applied VNF expansion, the resources are reserved;
step 1043: the VIM returns the checking and resource booking results to the NFVO;
step 1044: if the existing resources meet the requirements and the reservation is successful, the NFVO returns a response message for approving the extension of the VNF to the VNFM;
step 1045: the VNFM requests the VIM to allocate corresponding resources;
step 1046: and after the VIM allocates the corresponding resources, returning an acknowledgement message to the VNFM.
Example two
Fig. 4 is a flowchart of a management method for scaling the virtualized network function according to a second embodiment of the present invention. The second embodiment can avoid the conflict generated when the EMS and the VNFM respectively initiate the same VNF scaling operation on the same VNF instance at the same time or in a shorter time period. As shown in fig. 4, the steps of the second embodiment of the present invention are described in detail:
step 201: the VNFM receives a VNF scaling instruction from the EMS, wherein parameters of the VNF scaling instruction comprise an identification (such as vnfr _ id) of a VNF instance to be scaled, and capability parameters (such as deployment _ flag-flag _ key) to be reached after the VNF instance is scaled;
step 202: the VNFM performs preprocessing according to a parameter of a received VNF scaling instruction, for example, determines which VNF instance is to be scaled according to an identifier (vnfr _ id) of a VNF instance to be scaled, and determines an ability to be reached after the VNF instance is scaled according to a capability parameter (default _ flag-flag _ key) to be reached after the VNF instance is scaled, for example, when the VNF instance is a virtual Packet data network Gateway (vPGW), the capability parameter to be reached after the VNF instance is scaled is call times per second (call per second) of 10K, that is, 1 ten thousand calls per second is supported at maximum;
step 203: correspondingly searching a VNF deployment specification definition in a VNFD corresponding to the VNF instance according to the capability of the VNF instance to reach after the VNF instance is stretched, and determining the deployment specification to which the VNF instance should be stretched;
step 204: the VNFM checks whether the VNF instance has a scaling target of the deployment specification being performed or is ready to be started, and if the scaling target of the deployment specification being performed or is ready to be started, the VNFM ignores the received VNF scaling instruction, and the process is ended, otherwise, the process proceeds to step 205;
step 205: the VNFM determines the quantity of resources required by the VNF instance after stretching according to the determined deployment specification, specifically, the quantity of resources such as a CPU (central processing unit), an internal memory, a storage space and the like required by the VDU corresponding to the VNF instance after stretching is determined;
step 206: the VNFM executes the operation of changing the resources of the VNF instance according to the quantity of the resources needed by the VNF instance after the VNF instance is stretched, and the VNF instance is stretched; the specific implementation of this step is the same as that described in step 104 of the first embodiment, and therefore, the detailed description thereof is omitted;
step 207: and the VNFM informs the EMS that the VNF instance has been scaled, so that the EMS performs corresponding subsequent operations on the VNF instance, such as configuration of relevant parameters.
EXAMPLE III
Fig. 5 is a flowchart of a management method for scaling the virtualized network function according to a third embodiment of the present invention. Embodiment three may avoid conflicts when the EMS and the VNFM initiate any scaling operations to the same VNF instance at the same time or within a short period of time. As shown in fig. 5, the steps of the third embodiment are described in detail as follows:
step 301: the VNFM receives a VNF scaling instruction from the EMS, wherein parameters of the VNF scaling instruction include, but are not limited to: identification of a VNF instance to be scaled, and a capability parameter to be reached after the VNF instance is scaled;
step 302: the VNFM determines the capability of the VNF instance to be reached after the VNF instance is stretched according to the received parameter of the VNF stretching instruction;
step 303: correspondingly searching a VNF deployment specification definition in a VNFD corresponding to the VNF instance according to the capability of the VNF instance to reach after the VNF instance is stretched, and determining the deployment specification to which the VNF instance should be stretched;
step 304: the VNFM checks whether the VNFM also initiates a scaling instruction for the VNF instance, if not, the step 306 is executed; if yes, go to step 305;
step 305: checking a preset expansion priority of a system, and determining a deployment specification of the VNF instance after expansion; specifically, if the priority of the EMS is high, determining that the deployment specification of the VNF instance after stretching is the deployment specification determined according to the parameters sent by the EMS; otherwise, the deployment specification after the VNF instance is scaled is the deployment specification determined by the VNFM itself.
Step 306: the VNFM determines the quantity of resources required by the VNF instance after expansion and contraction according to the determined deployment specification;
step 307: the VNFM executes the operation of changing the resources of the VNF instance according to the quantity of the resources needed by the VNF instance after the VNF instance is stretched, and the VNF instance is stretched; the specific implementation process of the VNF instance scaling operation is the same as that in the first embodiment, and therefore, the details are not described herein;
step 308: and the VNFM informs the EMS that the VNF instance has been scaled, so that the EMS performs corresponding subsequent operations on the VNF instance, such as configuration of relevant parameters.
In addition, in this embodiment, after the VNFM receives the VNF scaling instruction, it is determined whether two or more VNF scaling instructions of the same VNF instance exist, if two or more VNF scaling instructions of the same VNF instance exist, the specific processing refers to steps 305 to 308, and if not, the specific processing refers to steps 306 to 308. And therefore will not be described herein.
Example four
Fig. 6 is a flowchart of a management method for scaling the virtualized network function according to a fourth embodiment of the present invention. As shown in fig. 6, the steps of the fourth embodiment of the present invention are specifically described: :
step 401: the NMS initiates an instruction for scaling a VNF instance, and sends the instruction for scaling the VNF instance to the EMS, wherein parameters of the VNF scaling instruction comprise an identifier of the VNF instance to be scaled and capability parameters to be reached after the VNF is scaled;
step 402: after receiving a VNF scaling instruction sent by the NMS for the VNF instance, the EMS forwards the VNF scaling instruction to the VNFM;
step 403: after receiving a VNF expansion instruction sent by an EMS, the VNFM determines the capability of the VNF instance to be reached after expansion according to the received parameter of the VNF expansion instruction;
step 404: correspondingly searching a VNF deployment specification definition in a VNFD corresponding to the VNF instance according to the capability of the VNF instance to reach after the VNF instance is stretched, and determining the deployment specification to which the VNF instance should be stretched;
step 405: the VNFM checks whether the VNF instance has a scaling target of the deployment specification being performed or is ready to be started, and if the scaling target of the deployment specification being performed or is ready to be started, the VNFM ignores the received VNF scaling instruction, and the process is ended, otherwise, the process proceeds to step 406;
step 406: the VNFM determines the quantity of resources required by the VNF instance after expansion and contraction according to the determined deployment specification;
step 407: the VNFM executes the operation of changing the resources of the VNF instance according to the quantity of the resources needed by the VNF instance after the VNF instance is stretched, and the VNF instance is stretched; the specific implementation process of the VNF instance scaling operation is the same as that in the first embodiment, and therefore, the details are not described herein;
step 408: the VNFM notifies the EMS that the VNF instance has been scaled, so that the EMS performs corresponding subsequent operations on the VNF instance, such as configuration of related parameters;
step 409: the EMS notifies the NMS that the scaling of the VNF instance has been completed.
EXAMPLE five
The difference between the method for expanding and contracting the function of the virtualized network provided by the fifth embodiment of the invention and the fourth embodiment is that: in the fifth embodiment, the VNF scaling instruction is initiated by the OSS. Specifically, the OSS initiates an instruction to scale one VNF instance, and sends the instruction to scale the VNF instance to the EMS; the parameters of the VNF scaling instruction comprise an identifier of a VNF instance to be scaled and a capability parameter to be reached after the VNF instance is scaled; after receiving a VNF scaling instruction of the VNF instance sent by the OSS, the EMS forwards the VNF scaling instruction to the VNFM; the subsequent processing is the same as steps 403 to 408 in the fourth embodiment, and therefore, the description thereof is omitted; finally, after completion of VNF scaling, the EMS notifies the OSS that scaling of the VNF instance has been completed.
EXAMPLE six
The difference between the method for expanding and contracting the function of the virtualized network provided by the sixth embodiment of the invention and the fourth embodiment is that: in the sixth embodiment, the VNF scaling instruction is initiated by the BSS. Specifically, the BSS initiates an instruction to scale one VNF instance, and sends the instruction to scale the VNF instance to the EMS; the parameters of the VNF scaling instruction comprise an identifier of a VNF instance to be scaled and a capability parameter to be reached after the VNF instance is scaled; after receiving a VNF scaling instruction of the VNF instance sent by the BSS, the EMS forwards the VNF scaling instruction to the VNFM; the subsequent processing is the same as steps 403 to 408 in the fourth embodiment, and therefore, the description thereof is omitted; finally, after the VNF scaling is completed, the EMS notifies the BSS that the scaling of the VNF instance has been completed.
EXAMPLE seven
The difference between the method for expanding and contracting the function of the virtualized network provided by the seventh embodiment of the present invention and the fourth embodiment is that: in the seventh embodiment, the VNF scaling instruction is initiated by the NMS. Specifically, the NMS initiates an instruction to scale one VNF instance, and sends the instruction to scale the VNF instance to the NFVO; the parameters of the VNF scaling instruction comprise an identifier of a VNF instance to be scaled and a capability parameter to be reached after the VNF instance is scaled; after receiving a VNF scaling instruction sent by NMS to the VNF instance, the NFVO forwards the VNF scaling instruction to a VNFM; the subsequent processing is the same as steps 403 to 408 in the fourth embodiment, and therefore, the description thereof is omitted; finally, after completion of the VNF scaling, the EMS notifies the NMS that the scaling of the VNF instance has been completed.
Example eight
The difference between the method for expanding and contracting the function of the virtualized network provided by the eighth embodiment of the present invention and the fourth embodiment is that: in an eighth embodiment, the VNF scaling instruction is initiated by the OSS and forwarded to the VNFM through the NFVO. Specifically, the OSS initiates an instruction to scale one VNF instance, and sends the instruction to scale the VNF instance to the NFVO; the parameters of the VNF scaling instruction comprise an identifier of a VNF instance to be scaled and a capability parameter to be reached after the VNF instance is scaled; after receiving a VNF scaling instruction of the VNF instance sent by the OSS, the NFVO forwards the VNF scaling instruction to the VNFM; the subsequent processing is the same as steps 403 to 407 of the fourth embodiment, and therefore, the description thereof is omitted; finally, after the VNF scaling is completed, the VNFM informs the NFVO that the scaling of the VNF instance is completed; NFVO informs the OSS that scaling of the VNF instance has been completed.
Example nine
The difference between the method for expanding and contracting the function of the virtualized network provided by the ninth embodiment of the present invention and the fourth embodiment is that: in the ninth embodiment, the VNF scaling command is initiated by the BSS and forwarded to the VNFM through the NFVO. Specifically, the BSS initiates an instruction to scale one VNF instance, and sends the instruction to scale the VNF instance to the NFVO; the parameters of the VNF scaling instruction comprise an identifier of a VNF instance to be scaled and a capability parameter to be reached after the VNF instance is scaled; after receiving a VNF scaling instruction of the VNF instance sent by the BSS, the NFVO forwards the VNF scaling instruction to a VNFM; the subsequent processing is the same as steps 403 to 407 of the fourth embodiment, and therefore, the description thereof is omitted; finally, after the VNF scaling is completed, the VNFM informs the NFVO that the scaling of the VNF instance is completed; NFVO informs the BSS that scaling of the VNF instance has been completed.
It should be noted that, the specific processing procedure of the EMS according to the parameter of the VNF scaling instruction refers to the VNFM, and therefore, the details are not described herein.
In addition, a management device for scaling the virtual network function according to a preferred embodiment of the present invention includes: the capability determining module is used for determining the capability to be reached after the VNF instances are stretched according to the parameters of the VNF stretching instruction, wherein the parameters of the VNF stretching instruction comprise the identification of the VNF instances to be stretched and the capability parameters to be reached after the VNF instances are stretched; the deployment specification determining module is used for determining deployment specifications to which the VNF instances are required to be stretched according to the determined capability of the VNF instances to be reached after stretching; and the processing module is used for performing telescopic operation on the VNF instance according to the determined deployment specification.
Wherein, the expression mode of the capability parameter to be reached after the VNF instance is scaled comprises:
specifying capabilities that the VNF instance can provide after scaling; or,
the capacity of the VNF instance after scaling is specified as a percentage of the existing capacity.
In a preferred embodiment, the management apparatus further includes: a checking module, configured to check whether a scaling operation targeted for the deployment specification is already ongoing or is ready to be started by the VNF instance.
In a preferred embodiment, the management apparatus further includes: the parameter determination module is configured to determine, when two or more VNF scaling instructions for the same VNF instance exist, a parameter of the VNF scaling instruction for the VNF instance according to a preset scaling priority.
In a preferred embodiment, the management apparatus further includes: and the setting module is used for presetting the VNF deployment specification definition in the VNFD corresponding to the VNF instance. The deployment specification determining module is specifically configured to: according to the capability of the VNF instance to be reached after the VNF instance is stretched, a VNF deployment specification definition in a VNFD corresponding to the VNF instance is correspondingly searched, and the deployment specification to which the VNF instance is stretched is determined.
In a preferred embodiment, the processing module is specifically configured to: and according to the determined deployment specification, determining the quantity of resources required by the VNF instance after scaling, executing the operation of changing the resources of the VNF instance, and completing the scaling of the VNF instance.
In addition, the specific processing procedure of the management device provided by the preferred embodiment of the present invention is the same as that described above, and therefore, the detailed description thereof is omitted here.
The foregoing shows and describes the general principles and broad features of the present invention and advantages thereof. The present invention is not limited to the above-described embodiments, which are described in the specification and illustrated only for illustrating the principle of the present invention, but various changes and modifications may be made within the scope of the present invention as claimed without departing from the spirit and scope of the present invention.

Claims (14)

1. A management method for virtualized network function scaling is characterized by comprising the following steps:
determining the capability of a VNF instance to be reached after the VNF instance is stretched according to the parameter of a virtual network function VNF stretching instruction, wherein the parameter of the VNF stretching instruction comprises the identification of the VNF instance to be stretched and the capability parameter of the VNF instance to be reached after the VNF instance is stretched;
determining a deployment specification to which the VNF instance is to be stretched according to the determined capability of the VNF instance to be reached after the VNF instance is stretched;
and performing scaling operation on the VNF instance according to the determined deployment specification.
2. The management method of claim 1, wherein after determining a deployment specification to which the VNF instance should scale, further comprising:
and when the fact that the VNF instance has the scaling operation with the scaling target being the deployment specification is not checked to be in progress or is ready to be started, scaling operation is carried out on the VNF instance according to the determined deployment specification.
3. The method of managing as set forth in claim 1, wherein when there are two or more VNF scaling instructions for the same VNF instance, further comprising: and determining parameters of the VNF scaling instruction of the VNF instance according to a preset scaling priority.
4. The management method according to any one of claims 1 to 3, further comprising: presetting a VNF deployment specification definition in a VNFD (virtual network function descriptor) corresponding to a VNF instance;
the determining a deployment specification to which the VNF instance should scale comprises: and correspondingly searching a VNF deployment specification definition in a VNFD corresponding to the VNF instance according to the determined capability of the VNF instance to be reached after the VNF instance is stretched, and determining a deployment specification to which the VNF instance should be stretched.
5. A management method according to any one of claims 1 to 3, characterized in that: the scaling operation of the VNF instance comprises: and according to the determined deployment specification, determining the quantity of resources required by the VNF instance after scaling, executing the operation of changing the resources of the VNF instance, and completing the scaling of the VNF instance.
6. The management method according to claim 5, characterized in that: the performing the operation of changing the resources of the VNF instance comprises:
sending a request for approving the VNF scaling to a network function virtualization orchestrator NFVO; the NFVO checks whether the existing resources can meet the applied VNF scaling from a Virtual Infrastructure Manager (VIM); the VIM returns the checking and resource booking results to the NFVO; if the existing resources meet the requirements and the reservation is successful, the NFVO returns a response message for approving the VNF expansion;
after receiving a response message for approving the extension of the VNF, requesting to allocate corresponding resources to the VIM; and after the VIM allocates the corresponding resources, returning a confirmation message.
7. The management method according to claim 1, characterized in that: the expression mode of the capability parameter to be reached after the VNF instance is scaled comprises the following steps:
specifying capabilities that the VNF instance can provide after scaling; or,
the capacity of the VNF instance after scaling is specified as a percentage of the existing capacity.
8. The management method according to claim 1, characterized in that: the VNF expansion instruction is initiated by a VNFM, an element management system EMS, an operation support system OSS, a service support system BSS or a network management system NMS.
9. A management apparatus for scaling a virtual network function, comprising:
the capability determining module is used for determining the capability to be reached after the VNF instances are stretched according to the parameters of the VNF stretching instruction, wherein the parameters of the VNF stretching instruction comprise the identification of the VNF instances to be stretched and the capability parameters to be reached after the VNF instances are stretched;
the deployment specification determining module is used for determining deployment specifications to which the VNF instances are required to be stretched according to the determined capability of the VNF instances to be reached after stretching;
and the processing module is used for performing telescopic operation on the VNF instance according to the determined deployment specification.
10. The management apparatus according to claim 9, further comprising: a checking module, configured to check whether a scaling operation targeted for the deployment specification is already ongoing or is ready to be started by the VNF instance.
11. The management apparatus according to claim 9, further comprising: the parameter determination module is configured to determine, when two or more VNF scaling instructions for the same VNF instance exist, a parameter of the VNF scaling instruction for the VNF instance according to a preset scaling priority.
12. The management apparatus according to any one of claims 9 to 11, further comprising: the setting module is used for presetting a VNF deployment specification definition in the VNFD corresponding to the VNF instance;
the deployment specification determining module is specifically configured to: and correspondingly searching a VNF deployment specification definition in a VNFD corresponding to the VNF instance according to the determined capability of the VNF instance to be reached after the VNF instance is stretched, and determining a deployment specification to which the VNF instance should be stretched.
13. The management device according to any one of claims 9 to 11, wherein the processing module is specifically configured to: and according to the determined deployment specification, determining the quantity of resources required by the VNF instance after scaling, executing the operation of changing the resources of the VNF instance, and completing the scaling of the VNF instance.
14. The management apparatus according to claim 9, wherein: the expression mode of the capability parameter to be reached after the VNF instance is scaled comprises the following steps:
specifying capabilities that the VNF instance can provide after scaling; or,
the capacity of the VNF instance after scaling is specified as a percentage of the existing capacity.
CN201510158884.8A 2015-04-03 2015-04-03 A kind of virtualize the flexible management method of network function and device Pending CN106162507A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201510158884.8A CN106162507A (en) 2015-04-03 2015-04-03 A kind of virtualize the flexible management method of network function and device
PCT/CN2015/092444 WO2016155291A1 (en) 2015-04-03 2015-10-21 Method and apparatus for managing virtualized network function scaling

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510158884.8A CN106162507A (en) 2015-04-03 2015-04-03 A kind of virtualize the flexible management method of network function and device

Publications (1)

Publication Number Publication Date
CN106162507A true CN106162507A (en) 2016-11-23

Family

ID=57003858

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510158884.8A Pending CN106162507A (en) 2015-04-03 2015-04-03 A kind of virtualize the flexible management method of network function and device

Country Status (2)

Country Link
CN (1) CN106162507A (en)
WO (1) WO2016155291A1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018119826A1 (en) * 2016-12-29 2018-07-05 华为技术有限公司 Network service update method, nfvo, and nfv system
CN108287746A (en) * 2017-01-09 2018-07-17 大唐移动通信设备有限公司 It is a kind of to the virtual resource dilatation of EPC network elements or the method and device of capacity reducing
CN108848564A (en) * 2018-06-26 2018-11-20 中国联合网络通信集团有限公司 Method, controller and the network system of resource allocation are carried out to Virtual Media Gateway
CN110830272A (en) * 2018-08-07 2020-02-21 中国移动通信有限公司研究院 Operation control method, device and equipment of VNF (virtual network element)
CN111698104A (en) * 2019-03-12 2020-09-22 华为技术有限公司 Operation and maintenance operation method, device, equipment and storage medium of virtual network function

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018174897A1 (en) * 2017-03-24 2018-09-27 Nokia Technologies Oy Methods and apparatuses for multi-tiered virtualized network function scaling
US10958517B2 (en) 2019-02-15 2021-03-23 At&T Intellectual Property I, L.P. Conflict-free change deployment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8276140B1 (en) * 2011-11-14 2012-09-25 Google Inc. Adjustable virtual network performance
CN103607349A (en) * 2013-11-14 2014-02-26 华为技术有限公司 Method for determining route in virtual network and provider edge equipment
WO2014169870A1 (en) * 2013-08-05 2014-10-23 中兴通讯股份有限公司 Virtual network element automatic loading and virtual machine ip address acquisition method and system, and storage medium
CN104468688A (en) * 2013-09-13 2015-03-25 株式会社Ntt都科摩 Method and apparatus for network virtualization

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8276140B1 (en) * 2011-11-14 2012-09-25 Google Inc. Adjustable virtual network performance
WO2014169870A1 (en) * 2013-08-05 2014-10-23 中兴通讯股份有限公司 Virtual network element automatic loading and virtual machine ip address acquisition method and system, and storage medium
CN104468688A (en) * 2013-09-13 2015-03-25 株式会社Ntt都科摩 Method and apparatus for network virtualization
CN103607349A (en) * 2013-11-14 2014-02-26 华为技术有限公司 Method for determining route in virtual network and provider edge equipment

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018119826A1 (en) * 2016-12-29 2018-07-05 华为技术有限公司 Network service update method, nfvo, and nfv system
CN108287746A (en) * 2017-01-09 2018-07-17 大唐移动通信设备有限公司 It is a kind of to the virtual resource dilatation of EPC network elements or the method and device of capacity reducing
CN108287746B (en) * 2017-01-09 2021-04-16 大唐移动通信设备有限公司 Method and device for expanding or contracting virtual resources of EPC network element
CN108848564A (en) * 2018-06-26 2018-11-20 中国联合网络通信集团有限公司 Method, controller and the network system of resource allocation are carried out to Virtual Media Gateway
CN108848564B (en) * 2018-06-26 2022-08-09 中国联合网络通信集团有限公司 Method, controller and network system for resource allocation of virtual media gateway
CN110830272A (en) * 2018-08-07 2020-02-21 中国移动通信有限公司研究院 Operation control method, device and equipment of VNF (virtual network element)
CN110830272B (en) * 2018-08-07 2022-09-13 中国移动通信有限公司研究院 Operation control method, device and equipment of VNF (virtual network element)
CN111698104A (en) * 2019-03-12 2020-09-22 华为技术有限公司 Operation and maintenance operation method, device, equipment and storage medium of virtual network function

Also Published As

Publication number Publication date
WO2016155291A1 (en) 2016-10-06

Similar Documents

Publication Publication Date Title
CN106162507A (en) A kind of virtualize the flexible management method of network function and device
US20210377111A1 (en) Intent Processing Method, Apparatus, and System
US11425604B2 (en) User plane resource management method, user plane network element, and control plane network element
CN109862581B (en) Communication method and device
EP3800926A1 (en) Alarm method and device
EP3512233A1 (en) Method for managing network slice and management unit
CN106227582B (en) Elastic telescopic method and system
US10924966B2 (en) Management method, management unit, and system
US20200344204A1 (en) Session management method and apparatus
CN105634780B (en) Method and device for realizing VNF elastic expansion
EP3133771A1 (en) Virtual machine resource changing method, device and virtual network function device
KR20170056350A (en) NFV(Network Function Virtualization) resource requirement verifier
CN106685784A (en) Virtualized network function VNF instance scaling method and VNF instance scaling device
CN106031116A (en) Method, apparatus and system for associating NS with VNF
EP3755047B1 (en) Load migration method and destination controller
CN107534577B (en) Method and equipment for instantiating network service
CN106161171B (en) Method and device for establishing network service instance
CN110418324B (en) Method, device and system for determining registration area
EP3376711B1 (en) Management method and device for managing instruction transmission for automatic vnf scaling function
WO2017128820A1 (en) Virtualized network function management method, network device and system
CN112748982A (en) Instantiation request generation method, interface virtual machine configuration method, NFVO and VIM
CN114828120B (en) Communication method, device, system and storage medium
CN113098705A (en) Authorization method and device for life cycle management of network service

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20161123

RJ01 Rejection of invention patent application after publication